Rate control method and apparatus, and communication device, storage medium and computer program product

Abstract

The present application relates to a rate control method and apparatus, and a communication device, a storage medium and a computer program product. The method comprises: sending an intra-station request message to a distributed entity, wherein the intra-station request message comprises at least one of first information and a multimodal identifier; the first information includes at least one of rate control information, a congestion notification request indication and a congestion feedback indication, the rate control information being used for indicating that a quality-of-service (QoS) flow supports uplink and / or downlink rate control; and the multimodal identifier is used for indicating that the QoS flow is associated with a multimodal communication service.

Description

Rate control methods, devices, communication equipment, storage media, and computer program products

[0001] Related applications

[0002] This application claims priority to Chinese patent application filed on March 28, 2025, with application number 202510385151.1, entitled "Rate control method, apparatus, communication device, storage medium and computer program product", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of wireless communication technology, and in particular to a rate control method, apparatus, communication equipment, storage medium, and computer program product. Background Technology

[0004] With the development of wireless communication technology, in complex network environments with multiple users and multiple services operating concurrently, it is necessary to control the rate of services in order to ensure that all types of services can obtain network resources that match their needs.

[0005] In traditional technologies, under the centralized unit (CU) / distributed unit (DU) separation architecture, the centralized unit contains MAC layer information, and the rate adjustment of traffic is achieved through the granularity of the data radio bearer (DRB) or logical channel group (LCG) in the MAC layer information.

[0006] However, current traditional methods, which rely on DRB or LCG information in the MAC layer for flow control, have a coarse granularity, resulting in poor rate control accuracy. Summary of the Invention

[0007] This application provides a rate control method, apparatus, communication device, storage medium, and computer program product, which can perform differentiated rate control on specific services in the traffic according to first information, thereby improving the accuracy of rate control.

[0008] This application provides a rate control method in a first aspect, the method being applied to a centralized entity of a first base station, the method comprising: sending an intra-station request message to a separate entity; the intra-station request message including at least one of first information and a multimodal identifier, the first information including at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information being used to indicate that a service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control; the multimodal identifier being used to indicate that the QoS Flow is associated with a multimodal communication service.

[0009] In one embodiment, before sending the in-station request message to the separated entity, the method further includes: receiving a first network message sent by a network node or a first radio resource control (RRC) message sent by a user equipment; the first network message includes one or more bearer information, the bearer information including at least one of a protocol data unit (PDU) session identifier, a QoS flow identifier, QoS flow-related rate control information, and a multimodal identifier; the first RRC message includes at least one of a QoS flow identifier and a rate control indication.

[0010] In one embodiment, the first network message includes a core network message issued by the core network or an inter-site message sent by the second base station. The core network message includes any one of the following: a handover request message, a PDU session establishment request message, a PDU session resource establishment request, a PDU session resource modification request, an initial context establishment request, and a user equipment (UE) context modification request. The inter-site message includes any one of the following: a handover request message and a handover response message.

[0011] In one embodiment, the in-site request message includes either a first in-site request message or a second in-site request message.

[0012] In one embodiment, the first information in the first site request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, data radio bearer (DRB) configuration information, and first configuration information.

[0013] In one embodiment, the DRB configuration information includes a DRB identifier and QoS Flow information mapped to the DRB; the QoS Flow information includes at least one of: a QoS Flow identifier, a QoS Flow service quality QoS configuration, a first indication information list, a congestion notification request indication, and a congestion feedback indication; the first indication information list contains the rate control information, and the first indication information list is used to indicate that one or more QoS Flows are configured with rate control indications; the congestion notification request indication indicates that at least one QoS Flow is congested; the congestion feedback indication is used to instruct the separate entity to report the congestion status of one or more QoS Flows or DRBs.

[0014] In one embodiment, the first configuration information includes: a Media Access Control Layer Control Element (MAC CE); the MAC CE includes at least one of a maximum number of QoS Flows, a rate multiplier, a first rate table, or a second rate table; the first rate table or the second rate table is used to indicate the quantized rate value, and each value in the first rate table or the second rate table corresponds to a specific rate value.

[0015] In one embodiment, the first intra-site request message is a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0016] In one embodiment, the first information in the second intra-site request message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, a QoS list, and / or at least one second indication information; the second indication information is used to indicate that one or more QoS Flows are congested or that the expected rate cannot be guaranteed.

[0017] In one embodiment, the method further includes: sending a first intra-site message to a separate entity, the first intra-site message including a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, and a second RRC message; the second RRC message including rate control configuration information; the rate control configuration information including at least one of the following: the number of first configuration sets included in the first MAC CE, a rate multiple, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an enable second MAC CE indication; the first configuration set or the second configuration set respectively includes at least one of the following: logical channel identifier (LCID), direction, bit rate, rate multiple, and reserved bits; the first intra-site message is used to instruct the separate entity to send the second RRC message to the user equipment.

[0018] In one embodiment, the method further includes: receiving a first internal response message from the separate entity in response to the internal request message, and determining that all or part of the configuration information in the internal request message has been successfully configured.

[0019] In one embodiment, the method further includes: if the in-station request message includes a congestion feedback indication, receiving a second in-station message reported by the separated entity, the second in-station message including at least one QoS Flow or DRB identifier and congestion indication information; the congestion indication information is used to indicate that at least one QoS Flow or DRB is congested.

[0020] In one embodiment, the method further includes: determining the congestion status result based on the User Plane Packet Data Convergence Protocol (PDCP) layer of the centralized entity.

[0021] This application provides a rate control method in a second aspect, the method being applied to a separate entity, the method comprising: receiving an intra-site request message sent by a centralized entity; the intra-site request message including at least one of the first information and a multimodal identifier, the first information including at least one of rate control information, a congestion notification request indication, and a congestion feedback indication, the rate control information being used to indicate that a QoS Flow supports uplink and / or downlink rate control; the multimodal identifier being used to indicate that the QoS Flow is associated with a multimodal communication service; sending a first intra-site response message to the centralized entity; and sending a first MAC CE to a user equipment.

[0022] In one embodiment, the method further includes: receiving second MAC CE information sent by the user equipment.

[0023] In one embodiment, before sending the first intra-site response message to the centralized entity, the method further includes: determining at least one of a candidate QoS Flow set and / or DRB, QoS Flow report congestion information based on the first information; and constructing the first intra-site response message based on the configuration result of the candidate QoS Flow set and / or the DRB, the QoS Flow report congestion information, or at least one of the other.

[0024] In one embodiment, the method further includes: receiving a first intra-station message sent by the centralized entity, and sending a second RRC message in the first intra-station message to the user equipment; the second RRC message includes rate control configuration information.

[0025] In one embodiment, the method further includes generating a first MAC CE based on rate control configuration information and congestion status results in the first intra-station message.

[0026] In one embodiment, the method further includes: sending a first MAC CE to a user equipment; the first MAC CE includes at least one first configuration set.

[0027] In one embodiment, the first in-station response message includes a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message.

[0028] In one embodiment, the method further includes: receiving a second MAC CE sent by a user equipment; the second MAC CE includes at least one second configuration set.

[0029] In one embodiment, the method further includes: receiving a congestion feedback indication configured by the centralized entity, and reporting a second intra-site message to the centralized entity, the second intra-site message including at least one QoS FLOW or DRB identifier and congestion indication information; the congestion indication information is used to indicate that at least one QoS FLOW or DRB is congested.

[0030] This application provides a rate control method in a third aspect, the method being applied to a user equipment, the method comprising: receiving a first MAC CE sent by a wireless network node, or sending a second MAC CE to the wireless network node; the first MAC CE including at least one first configuration set; the first configuration set including rate control information, the rate control information being used to indicate that at least one QoS Flow supports uplink and / or downlink rate control; the second MAC CE including at least one second configuration set; the second configuration set including suggestion information of the rate control information; the suggestion information being used to suggest that the wireless network node adjust the rate of the QoS Flow.

[0031] In one embodiment, the method further includes sending a first RRC message to a network node, the first RRC message including at least one of an identifier of at least one QoS Flow and a rate control indication.

[0032] In one embodiment, the method further includes: receiving a second RRC message sent by the wireless network node; the second RRC message includes rate control configuration information; the rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, a rate multiple, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an enable second MAC CE indication; the second RRC message is used to configure the first MAC CE or the second MAC CE.

[0033] In one embodiment, the method further includes: after receiving the second RRC message, determining the configuration information of the first MAC CE and / or the second MAC CE based on the rate control configuration information.

[0034] In one embodiment, the method further includes: after receiving a first MAC CE, negotiating the rate of the QoS Flow with a peer entity based on the configuration information carried in the first MAC CE.

[0035] In one embodiment, the method further includes: when it is detected that the uplink QoS Flow or DRB rate cannot reach the target rate configured by the network, sending a second MAC CE to the wireless network node; the configuration information carried in the second MAC CE is determined by a second RRC message.

[0036] In one embodiment, the wireless network node includes a base station, a base station control plane entity, a base station centralized entity, or a base station separate entity.

[0037] This application provides a rate control method in a fourth aspect, the method being applied to a control plane entity of a first base station, the method comprising: sending an in-station request message to a separate entity; the in-station request message including at least one of service quality requirement first information and a multimodal identifier, the first information including at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information being used to indicate that a service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control; the multimodal identifier being used to indicate that the QoS Flow is associated with a multimodal communication service.

[0038] In one embodiment, before sending the first intra-site request message to the separated entity, the method further includes: receiving a first network message sent by a network node or a first radio resource control (RRC) message sent by a user equipment; the first network message includes one or more bearer information, the bearer information including at least one of a protocol data unit (PDU) session identifier, a QoS flow identifier, QoS flow-related rate control information, and a multimodal identifier; the first RRC message includes at least one of a QoS flow identifier and a rate control indication.

[0039] In one embodiment, the first network message includes a core network message issued by the core network or an inter-site message sent by the second base station. The core network message includes any one of the following: a handover request message, a PDU session establishment request message, a PDU session resource establishment request, a PDU session resource modification request, an initial context establishment request, and a user equipment (UE) context modification request. The inter-site message includes any one of the following: a handover request message and a handover response message.

[0040] In one embodiment, the in-site request message includes either a first in-site request message or a second in-site request message.

[0041] In one embodiment, the first information in the first site request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, data radio bearer (DRB) configuration information, and first configuration information.

[0042] In one embodiment, the first intra-site request message is a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0043] In one embodiment, the DRB configuration information includes a DRB identifier and QoS Flow information mapped to the DRB; the QoS Flow information includes at least one of: a QoS Flow identifier, a QoS Flow service quality QoS configuration, a first indication information list, a congestion notification request indication, and a congestion feedback indication; the first indication information list contains the rate control information, and the first indication information list is used to indicate that one or more QoS Flows are configured with rate control indications; the congestion notification request indication indicates that at least one QoS Flow is congested; the congestion feedback indication is used to instruct the separate entity to report the congestion status of one or more QoS Flows or DRBs.

[0044] In one embodiment, the first configuration information includes: a Media Access Control Layer Control Element (MAC CE); the MAC CE includes at least one of a maximum number of QoS Flows, a rate multiplier, a first rate table, or a second rate table; the first rate table or the second rate table is used to indicate the quantized rate value, and each value in the first rate table or the second rate table corresponds to a specific rate value.

[0045] In one embodiment, the first information in the second intra-site request message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, a QoS list, and / or at least one second indication information; the second indication information is used to indicate that one or more QoS Flows are congested or that the expected rate cannot be guaranteed.

[0046] In one embodiment, the method further includes: sending a first intra-site message to a separate entity, the first intra-site message including a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, and a second RRC message; the second RRC message including rate control configuration information; the rate control configuration information including at least one of the following: the number of first configuration sets included in the first MAC CE, a rate multiple, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an enable second MAC CE indication; the first configuration set or the second configuration set respectively includes at least one of the following: logical channel identifier (LCID), direction, bit rate, rate multiple, and reserved bits; the first intra-site message is used to instruct the separate entity to send the second RRC message to the user equipment.

[0047] In one embodiment, the method further includes: receiving a first internal response message from the separate entity in response to the internal request message, and determining that all or part of the configuration information in the internal request message has been successfully configured.

[0048] In one embodiment, the method further includes: if the in-site request message includes a congestion feedback indication, receiving a second in-site message reported by the separated entity, the second in-site message including at least one QoS FLOW or DRB identifier and congestion indication information; the congestion indication information is used to indicate that at least one QoS Flow or DRB is congested.

[0049] In one embodiment, the method further includes: sending a control plane intra-site request message to a user plane entity; the control plane intra-site request message includes at least one of QoS Flow information, PDU session information, and congestion state report indication information associated with the QoS Flow or PDU session; the congestion state report indication information includes at least one of uplink, downlink, or bidirectional; receiving a user plane intra-site response message sent by the user plane entity; the user plane intra-site response message includes at least one of QoS Flow information, PDU session information, and congestion state information associated with the QoS Flow or PDU session; the congestion state information includes at least one of uplink, downlink, or bidirectional.

[0050] In one embodiment, after receiving the user plane in-station response message sent by the user plane entity, the method further includes: determining a congestion status result based on the user plane in-station response message; the congestion status result includes at least one QoS Flow experiencing congestion.

[0051] In one embodiment, the method further includes: determining a congestion status result based on the User Plane Packet Data Convergence Protocol (PDCP) layer of the centralized entity.

[0052] This application provides a rate control apparatus in a fifth aspect, the apparatus being applied to a centralized entity, the apparatus comprising: a first sending module for sending an intra-site request message to a separate entity; the intra-site request message including at least one of the first information and a multimodal identifier, the first information including at least one of rate control information, a congestion notification request indication, and a congestion feedback indication, the rate control information being used to indicate that a QoS Requirement Flow supports uplink and / or downlink rate control; the multimodal identifier being used to indicate that the QoS Flow is associated with a multimodal communication service.

[0053] In one embodiment, the apparatus further includes: a first receiving module, configured to receive a first network message sent by a network node or a first radio resource control (RRC) message sent by a user equipment; the first network message includes one or more bearer information, the bearer information including at least one of a protocol data unit (PDU) session identifier, a QoS flow identifier, QoS flow-related rate control information, and a multimodal identifier; the first RRC message includes at least one of a QoS flow identifier and a rate control indication.

[0054] In one embodiment, the first network message includes a core network message issued by the core network or an inter-site message sent by the second base station. The core network message includes any one of the following: a handover request message, a PDU session establishment request message, a PDU session resource establishment request, a PDU session resource modification request, an initial context establishment request, and a user equipment (UE) context modification request. The inter-site message includes any one of the following: a handover request message and a handover response message.

[0055] In one embodiment, the in-site request message includes either a first in-site request message or a second in-site request message.

[0056] In one embodiment, the first information in the first site request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, data radio bearer (DRB) configuration information, and first configuration information.

[0057] In one embodiment, the DRB configuration information includes a DRB identifier and QoS Flow information mapped to the DRB; the QoS Flow information includes at least one of: a QoS Flow identifier, a QoS Flow service quality QoS configuration, a first indication information list, a congestion notification request indication, and a congestion feedback indication; the first indication information list contains the rate control information, and the first indication information list is used to indicate that one or more QoS Flows are configured with rate control indications; the congestion notification request indication indicates that at least one QoS Flow is congested; the congestion feedback indication is used to instruct the separate entity to report the congestion status of one or more QoS Flows or DRBs.

[0058] In one embodiment, the first configuration information includes: a Media Access Control Layer Control Element (MAC CE); the MAC CE includes at least one of a maximum number of QoS Flows, a rate multiplier, a first rate table, or a second rate table; the first rate table or the second rate table is used to indicate the quantized rate value, and each value in the first rate table or the second rate table corresponds to a specific rate value.

[0059] In one embodiment, the first intra-site request message is a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0060] In one embodiment, the first information in the second intra-site request message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, a QoS list, and / or at least one second indication information; the second indication information is used to indicate that one or more QoS Flows are congested or that the expected rate cannot be guaranteed.

[0061] In one embodiment, the apparatus further includes: a second sending module, configured to send a first intra-station message to a separate entity, the first intra-station message including a first user equipment identifier assigned by the centralized entity to the user equipment, a second user equipment identifier assigned by the separate entity to the user equipment, and a second RRC message; the second RRC message including rate control configuration information; the rate control configuration information including at least one of the following: the number of first configuration sets included in the first MAC CE, a rate multiple, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an enable second MAC CE indication; the first configuration set or the second configuration set respectively includes at least one of the following: logical channel identifier (LCID), direction, bit rate, rate multiple, and reserved bits; the first intra-station message is used to instruct the separate entity to send the second RRC message to the user equipment.

[0062] In one embodiment, the apparatus further includes: a second receiving module, configured to receive a first internal response message from the separate entity in response to the internal request message, and to determine that all or part of the configuration information in the internal request message has been successfully configured.

[0063] In one embodiment, the apparatus further includes: a third receiving module, configured to receive a second intra-site message reported by the separated entity if the intra-site request message includes a congestion feedback indication, the second intra-site message including at least one QoS Flow or DRB identifier and congestion indication information; the congestion indication information being used to indicate that at least one QoS Flow or DRB is congested.

[0064] In one embodiment, the apparatus further includes: a first determining module, configured to determine a congestion status result based on the User Plane Packet Data Convergence Protocol (PDCP) layer of the centralized entity.

[0065] This application provides a rate control apparatus in a sixth aspect, the apparatus being applied to a separate entity, the apparatus comprising: a fourth receiving module for receiving an intra-site request message sent by a centralized entity; the intra-site request message including at least one of first information and a multimodal identifier, the first information including at least one of rate control information, a congestion notification request indication, and a congestion feedback indication, the rate control information being used to indicate that a QoS Flow supports uplink and / or downlink rate control; the multimodal identifier being used to indicate that the QoS Flow is associated with a multimodal communication service; a third sending module for sending a first intra-site response message to the centralized entity; and a fourth sending module for sending a first MAC CE to a user equipment.

[0066] In one embodiment, the apparatus further includes a fifth receiving module for receiving second MAC CE information sent by the user equipment.

[0067] In one embodiment, the apparatus further includes: a second determining module, configured to determine at least one of a candidate QoS Flow set and / or DRB and QoS Flow report congestion information based on the first information; and a constructing module, configured to construct a first intra-site response message based on the configuration result of the candidate QoS Flow set and / or the DRB and the QoS Flow report congestion information.

[0068] In one embodiment, the apparatus further includes: a sixth receiving module, configured to receive a first intra-station message sent by the centralized entity, and send a second RRC message in the first intra-station message to the user equipment; the second RRC message includes rate control configuration information.

[0069] In one embodiment, the apparatus further includes a generation module for generating a first MAC CE based on rate control configuration information and congestion status results in a first intra-station message.

[0070] In one embodiment, the apparatus further includes: a fifth transmitting module for transmitting a first MAC CE to a user equipment; the first MAC CE includes at least one first configuration set.

[0071] In one embodiment, the first in-station response message includes a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message.

[0072] In one embodiment, the apparatus further includes: a seventh receiving module for receiving a second MAC CE sent by a user equipment; the second MAC CE includes at least one second configuration set.

[0073] In one embodiment, the apparatus further includes: an eighth receiving module, configured to receive a congestion feedback indication configured by the centralized entity, and report a second intra-site message to the centralized entity, the second intra-site message including at least one QoS FLOW or DRB identifier, and congestion indication information; the congestion indication information is used to indicate that at least one QoS FLOW or DRB is congested.

[0074] This application provides a rate control apparatus in a seventh aspect, the apparatus being applied to a user equipment, the apparatus comprising: a transceiver module configured to receive a first MAC CE sent by a wireless network node, or to send a second MAC CE to the wireless network node; the first MAC CE including at least one first configuration set; the first configuration set including rate control information, the rate control information being configured to indicate that at least one QoS Flow supports uplink and / or downlink rate control; and the second MAC CE including at least one second configuration set; the second configuration set including suggestion information of the rate control information; the suggestion information being configured to suggest that the wireless network node adjust the rate of the QoS Flow.

[0075] In one embodiment, the apparatus further includes: a sixth sending module, configured to send a first RRC message to a network node, the first RRC message including at least one of a QoS Flow identifier and a rate control indication.

[0076] In one embodiment, the apparatus further includes: a ninth receiving module, configured to receive a second RRC message sent by the wireless network node; the second RRC message includes rate control configuration information; the rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, a rate multiple, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an enable second MAC CE indication; the second RRC message is used to configure the first MAC CE or the second MAC CE.

[0077] In one embodiment, the apparatus further includes a third determining module, configured to determine the configuration information of the first MAC CE and / or the second MAC CE based on the rate control configuration information after receiving the second RRC message.

[0078] In one embodiment, the apparatus further includes a negotiation module, configured to, upon receiving a first MAC CE, negotiate the rate of the QoS Flow with a peer entity based on the configuration information carried in the first MAC CE.

[0079] In one embodiment, the apparatus further includes a seventh sending module, configured to send a second MAC CE to the wireless network node when it is detected that the uplink QoS Flow or DRB rate cannot reach the target rate configured by the network; the configuration information carried in the second MAC CE is determined by a second RRC message.

[0080] This application provides a communication device in an eighth aspect, comprising: a transmitter; the transmitter being configured to send an in-station request message to a separate entity; the in-station request message including at least one of first information and a multimodal identifier, the first information including at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information being configured to indicate that a QoS Requirement Flow supports uplink and / or downlink rate control; the multimodal identifier being configured to indicate that the QoS Flow is associated with a multimodal communication service.

[0081] This application provides a non-volatile computer-readable storage medium storing a computer program thereon, which, when executed by a processor, performs the following steps: sending an in-station request message to a separate entity; the in-station request message includes at least one of the first information and a multimodal identifier, the first information including at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information being used to indicate that a QoS Requirement Flow supports uplink and / or downlink rate control; the multimodal identifier being used to indicate that the QoS Flow is associated with a multimodal communication service.

[0082] This application provides a computer program product in a tenth aspect, including a computer program that, when executed by a processor, causes the processor to implement the rate control method provided in the embodiments of this application. The method may include: sending an in-station request message to a separate entity; the in-station request message includes at least one of first information and a multimodal identifier, the first information including at least one of rate control information, a congestion notification request indication, and a congestion feedback indication; the rate control information indicating that a QoS Requirement Flow supports uplink and / or downlink rate control; and the multimodal identifier indicating that the QoS Flow is associated with a multimodal communication service.

[0083] The aforementioned rate control method, apparatus, communication equipment, storage medium, and computer program product send an in-station request message to a separate entity. The in-station request message includes at least one of first information and a multimodal identifier. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication. The rate control information indicates that the QoS Flow of a service requires support for uplink and / or downlink rate control. The multimodal identifier indicates that the QoS Flow is associated with a multimodal communication service. By using this method, an in-station request message containing at least the first information or a multimodal identifier is sent to the separate entity, instructing the separate entity to perform rate control according to the rate control information. This achieves differentiated rate control of specific services within the traffic according to the QoS Flow, thereby improving the accuracy of rate control. Attached Figure Description

[0084] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0085] Figure 1 is an application environment diagram of the rate control method according to an embodiment of this application.

[0086] Figure 2 is a flowchart illustrating a rate control method applied to a centralized entity according to an embodiment of this application.

[0087] Figure 3 is a schematic diagram of the triggering process of the rate control method according to an embodiment of this application.

[0088] Figure 4 is a schematic diagram of the interaction between separate entities and centralized entities according to an embodiment of this application.

[0089] Figure 5 is a schematic diagram of the process by which a separate entity responds to a centralized entity according to an embodiment of this application.

[0090] Figure 6 is a schematic diagram of the process by which a separate entity responds to a centralized entity according to another embodiment of this application.

[0091] Figure 7 is a flowchart illustrating one method for determining congestion status results according to an embodiment of this application.

[0092] Figure 8 is a flowchart illustrating a rate control method applied to a separated entity according to an embodiment of this application.

[0093] Figure 9 is a schematic diagram of the process of interaction between a separate entity and a user device according to an embodiment of this application.

[0094] Figure 10 is a schematic diagram of the process by which a separate entity configures its rate according to an in-station request in one embodiment of this application.

[0095] Figure 11 is a schematic flowchart illustrating how a separate entity responds to a request from a centralized entity according to an embodiment of this application.

[0096] Figure 12 is a schematic flowchart of rate control of a separate entity according to an embodiment of this application.

[0097] Figure 13 is a schematic diagram of the process of interaction between the separated entity and the user equipment according to another embodiment of this application.

[0098] Figure 14 is a schematic diagram of the process of interaction between the separated entity and the user equipment according to another embodiment of this application.

[0099] Figure 15 is a schematic diagram of the process by which a separate entity responds to a congestion feedback instruction from a centralized entity according to an embodiment of this application.

[0100] Figure 16 is a flowchart illustrating a rate control method applied to a user equipment according to an embodiment of this application.

[0101] Figure 17 is a schematic diagram of the process by which a user equipment provides feedback to a network node according to service requirements in one embodiment of this application.

[0102] Figure 18 is a schematic diagram of the process of user equipment pre-configuring according to the second RRC message according to an embodiment of the present application.

[0103] Figure 19 is a schematic diagram of the process by which a user equipment determines configuration information based on a second RRC message according to an embodiment of this application.

[0104] Figure 20 is a schematic diagram of the process of a user equipment performing QoS Flow rate negotiation based on a first MAC CE according to an embodiment of the present application.

[0105] Figure 21 is a schematic diagram of the process by which a user equipment feeds back a second MAC CE to a wireless network node according to an embodiment of this application.

[0106] Figure 22 is a schematic diagram of the interaction between the control surface entity and the user surface entity according to an embodiment of this application.

[0107] Figure 23 is a schematic flowchart illustrating the process of determining the congestion status result of the control plane entity according to an embodiment of this application.

[0108] Figure 24 is a structural block diagram of a rate control device applied to a centralized entity according to an embodiment of this application.

[0109] Figure 25 is an internal structure diagram of an access network device according to an embodiment of this application. Detailed Implementation

[0110] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0111] Figure 1 is a schematic diagram of an application scenario of a rate control method provided in an embodiment of this application. As shown in Figure 1, the scenario includes a user equipment 100 and an access network device 200. The user equipment 100 and the access network device 200 transmit data via a network.

[0112] The access network equipment 200 can be a base station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a base station in a 5G network, etc., and is not limited here.

[0113] When supporting a CU / DU separation architecture, the access network device 200 is divided into a Centralized Unit (CU) and a Distributed Unit (DU). The Centralized Unit can be further divided into the gNodeB Centralized Unit-Control Plane (gNB-CU-CP) and the gNodeB Centralized Unit-User Plane (gNB-CU-UP). Taking a gNB as an example, a gNB may contain one gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs. The gNB-CU-CP connects to the gNB-DU via the F1-C interface, the gNB-CU-UP connects to the gNB-DU via the F1-U interface, and the gNB-CU-UP connects to the gNB-CU-CP via the E1 interface. A gNB-DU can only connect to one gNB-CU-CP, and a gNB-CU-UP can only connect to one gNB-CU-CP.

[0114] To enhance system reliability, a single gNB-DU and / or gNB-CU-UP can connect to multiple gNB-CU-CPs. Specifically, a gNB-DU can connect to multiple gNB-CU-UPs under the control of the same gNB-CU-CP; similarly, a gNB-CU-UP can connect to multiple gNB-DUs under the control of the same gNB-CU-CP. The connection between gNB-CU-UPs and gNB-DUs is established by the gNB-CU-CP using Bearer Context Management. The gNB-CU-CP selects the appropriate gNB-CU-UP based on the service required by the UE. If multiple CU-UPs exist, they belong to the same security domain. During intra-gNB-CU-CP handovers within a gNB, data forwarding between gNB-CU-UPs can be supported via the Xn-U interface.

[0115] User equipment 100 may be a wireless terminal, which may be a device providing voice and / or other service data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The wireless terminal may communicate with one or more core networks via a Radio Access Network (RAN). The wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone), or a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device, which exchanges voice and / or data with the radio access network. The wireless terminal may also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, access terminal, user terminal, user agent, user device, or user equipment, without limitation herein.

[0116] In traditional technologies, both 4G and 5G have proposed adaptive rate adjustment functions for voice IMS services. However, because VoNR (Voice over NR) uses EVS coding, the CMR field position is not fixed, making it impossible for base stations to achieve adaptive coding rates through CMR alone. Therefore, to achieve adaptive coding rates in 5G networks, the newly introduced Recommended bitrate technology is needed. The base station sends the recommended physical layer rate to the user equipment (UE) via MAC layer control information, and the UE determines whether to reduce or increase the voice coding rate. Specifically, this process can be triggered by the gNodeB detecting changes in the UE's air interface rate, or by the UE detecting changes in uplink air interface capabilities and actively querying the gNodeB for the recommended rate.

[0117] However, Extended Reality (XR) services introduce concepts such as multimodality and Protocol Data Unit (PDU) sets. In Augmented Reality (AR) / Virtual Reality (VR) applications, multimodal communication services combine ultra-low latency with high availability / reliability. When access network equipment supporting XR service functions adopts a CU / DU separation architecture, because the gNB-DU currently contains MAC layer information, its congestion control only supports evaluation at the DRB or LCG granularity. This results in the gNB-DU being unable to clearly identify which service quality of service (QoS) flow data flows need to be controlled through MAC CE, and the gNB-DU also lacks understanding of the mapping relationship between Logical Channel Identification (LCID) or Logical Channel Group (LCG) and QoS Flow. Currently, both the F1 and E1 interfaces lack QoS Flow information, preventing the gNB-CU-CP from determining which bearers can be admitted and what rate reduction requirements are needed for admission control. Furthermore, in the current F1 protocol, the gNB-DU does not notify the gNB-CU-CP or gNB-CU of necessary information from the MAC CE; that is, the gNB-CU-CP or gNB-CU cannot receive the relevant suggestions from the uplink MAC CE, thus failing to trigger closed-loop adjustments by the gNB-CU-CP or gNB-CU.

[0118] Therefore, traditional rate control techniques cannot meet the service rate adjustment requirements of XR. Based on the above-mentioned traditional techniques, this application provides a rate control method. By sending an in-site request message containing at least first information or a multimodal identifier to a separation entity, the separation entity is instructed to perform rate control according to the rate control information in the first information. This enables the separation entity to control the QoS Flow according to QoS Flow and MAC CE, achieving differentiated rate control of specific services in the traffic at the QoS granularity, thereby improving the accuracy of rate control.

[0119] It should be noted that the beneficial effects or technical problems solved by the embodiments of this application are not limited to this one, but may also be other implicit or related problems. For details, please refer to the description of the embodiments below.

[0120] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0121] In one embodiment, as shown in FIG2, a rate control method is provided. Taking the application of this method to the centralized entity of the first base station in FIG1 as an example, the method includes the following steps S201.

[0122] Step S201: Send an internal request message to the separated entity.

[0123] The in-site request message includes at least one of the following: first information and a multimodal identifier. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication. The rate control information indicates that the service quality requirement flow (QoS) requires uplink and / or downlink rate control. The multimodal identifier indicates that the QoS flow is associated with a multimodal communication service.

[0124] In this embodiment, the centralized entity can be a CU or a CU-CP, and the separated entity can be a DU. Taking the CU as an example, after the CU receives a core network message issued by the core network for a certain user equipment, or after the CU receives a first RRC message sent by the user equipment through the DU, the CU itself can obtain QoS Flow related information indication, which can be at least one of the first information and the multimodal identifier. Then, the CU sends an intra-site request message containing the first information and / or the multimodal identifier to the separated entity (DU), so that the separated entity can control the QoS Flow according to the rate control information specified in the first information.

[0125] For example, after receiving a core network message from the SMF, the centralized entity parses the message to determine the rate control information related to the QoS Flow. Based on this information, it determines the first information or multimodal identifier and generates an intra-site request message. Then, the centralized entity (CU) generates the intra-site request message according to the F1 control protocol (F1AP) and sends it to the separate entities. Specifically, the rate control information included in the first information can be QoS parameter configurations for different modal data flows, including the QoS Flow ID, multimodal identifier, the modality type corresponding to the multimodal identifier, uplink bandwidth, downlink bandwidth, and delay budget.

[0126] In the above rate control method, by sending an in-site request message containing at least the first information or a multimodal identifier to the separation entity, the separation entity is instructed to perform rate control according to the rate control information in the first information. This enables the separation entity to control the QoS Flow according to QoS Flow and MAC CE, thereby realizing differentiated rate control of specific services in the traffic at the granularity of QoS, and thus improving the accuracy of rate control.

[0127] In one embodiment, as shown in FIG3, before step 202, the method may further include the following step S301.

[0128] Step S301: Receive the first network message sent by the network node or the first RRC message sent by the user equipment.

[0129] The first network message includes one or more bearer information. The bearer information includes at least one of the following: Protocol Data Unit (PDU) session identifier, QoS Flow identifier, QoS Flow-related rate control information, and multimodal identifier. The first RRC message includes at least one of the following: QoS Flow identifier and rate control indication.

[0130] In this embodiment, the centralized entity receives a first network message sent by a network node or a first RRC message sent by a user equipment through a signaling interface (e.g., N3 / N9 interface). The network node can be the core network or other base stations.

[0131] In one embodiment, the first network message includes a core network message sent by the core network or an inter-station message sent by the second base station. The core network message includes any of the following:

[0132] Handover request message, PDU session establishment request message, PDU session resource establishment request, PDU session resource modification request, initial context establishment request, and user equipment (UE) context modification request.

[0133] Inter-station messages include any of the following: switch request messages and switch response messages.

[0134] In this embodiment of the application, the core network message issued by the core network is used as an example for illustration. The bearer information contained in the core network message is used to generate in-site request messages and realize QoS differentiated resource scheduling for service requests.

[0135] If a QoS Flow-related configuration information in a core network message contains a multimodal identifier, the QoS Flow is determined to be a multimodal service; if a QoS Flow-related configuration information in a core network message contains QoS Flow-related rate control information, the QoS Flow can perform rate control or rate negotiation with the user equipment.

[0136] In an exemplary embodiment, when a user uses a holographic remote collaboration platform based on XR services, the platform's XR services integrate multimodal data streams, such as holographic video streams (3D images), haptic feedback streams, spatial audio streams, and control signal streams. When the Session Management function (SMF) detects a service request carrying a multimodal identifier, it determines that the service request is an XR service request, meaning that multimodal resources need to be dynamically allocated. Then, it classifies different types of data streams using the multimodal identifier, obtains core network messages, and finally sends the core network messages to a centralized entity in the network nodes.

[0137] In this embodiment, through parsing and action, the centralized entity of the network node can accurately identify the special requirements of multimodal XR services and dynamically allocate resources to support their stringent performance indicators, ensuring end-to-end service quality and guaranteeing the accuracy of rate control.

[0138] In one embodiment, the in-site request message may include either a first in-site request message or a second in-site request message.

[0139] In one embodiment, the first information in the first site request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, data radio bearer (DRB) configuration information, and first configuration information.

[0140] In one embodiment, the first information in the second intra-site request message includes a first user equipment identifier assigned to the user equipment by a centralized entity, a second user equipment identifier assigned to the user equipment by a separate entity, a QoS list, and / or at least one second indication information. The second indication information is used to indicate that one or more QoS flows are congested or that the expected rate cannot be guaranteed.

[0141] In this embodiment, within the Radio Access Network (RAN), base stations (e.g., CUs and DUs in a CU / DU architecture) need to transmit QoS-related configuration or status information via intra-station signaling. In this embodiment, based on the purpose and content of the first information, two intra-station request message formats are distinguished: a first intra-station request is used to issue QoS-related configurations during the initial configuration phase, and a second intra-station request is used to transmit congestion status or rate guarantee anomaly indications during runtime.

[0142] The centralized entity receives and parses the QoS parameter templates (e.g., rate, latency, multimodal identifiers) from the core network messages, providing an initial end-to-end QoS configuration policy. The centralized entity further breaks down and refines the QoS parameter template parameters to the base station level (from CU to DU) via a first intra-station request message, completing the mapping between the Data Radio Bearer (DRB) and QoS Flow, physical layer resource configuration, and assigning a first UE identifier to the user equipment by the centralized entity and a second UE identifier to the user equipment by the separate entities. Alternatively, the centralized entity uses a second intra-station request message to provide real-time feedback on congestion or rate anomalies, forming a closed-loop control to ensure the QoS targets in the core network requests remain effective in a dynamic network environment.

[0143] In this embodiment, the QoS configuration is divided into initial static configuration and real-time dynamic feedback through the first intra-site request message and the second intra-site request message, which avoids frequent full updates and can flexibly cope with the high complexity requirements of multimodal XR services, while ensuring the accuracy of resource allocation and network stability.

[0144] In one embodiment, the DRB configuration information may include a DRB identifier and QoS Flow information mapped to the DRB; the QoS Flow information includes at least one of the following: a QoS Flow identifier, a QoS Flow service quality (QoS) configuration, a first indication information list, a congestion notification request indication, and a congestion feedback indication. The first indication information list contains rate control information and is used to indicate that one or more QoS Flows are configured with rate control indications. The congestion notification request indication indicates that at least one QoS Flow is congested. The congestion feedback indication is used to instruct a separate entity to report the congestion status of one or more QoS Flows or DRBs.

[0145] In one embodiment, the first configuration information may include: a Media Access Control Element (MAC CE); the MAC CE includes at least one of a maximum number of QoS Flows, a rate multiplier, a first rate table, or a second rate table; the first rate table or the second rate table is used to indicate the quantized rate value, and each value in the first rate table or the second rate table corresponds to a specific rate value.

[0146] The rate multiplier indicates that the multiplier supported by the first MAC CE or the second MAC CE can be at least one of 2X, 4X, 5X, 10X, and 20X.

[0147] In this embodiment, when a user equipment initiates a multimodal XR service request, the core network determines QoS parameters based on the service type of the XR service and encapsulates these QoS parameters into a session management request, which is then sent to the centralized unit via the core network request. The centralized unit allocates one or more DRBs for the session, determines the QoS Flow set carried by each DRB, and assigns a QoS configuration and a first indication information list to each QoS Flow, as well as setting the congestion notification request indication. The centralized entity sets MAC layer control parameters according to the service requirements of the XR service request, including the maximum number of QoS Flows, rate multipliers, and references to rate tables.

[0148] The QoS Flow identifier is used to map different application layer services to their corresponding DRBs; the QoS configuration defines the parameters of the QoS Flow, such as the QoS Flow quantity template and priority level; the first indication information list includes the rate control indication corresponding to the QoS Flow. For example, the rate control mode of the QoS Flow without filtering can include enforcement mode (ENFORCE) or monitoring mode (MONITOR). Enforcement mode strictly limits the rate (e.g., a minimum guaranteed rate of 50Mbps for haptic streams), while monitoring mode only monitors the actual rate and does not enforce intervention (e.g., video streams are allowed ±10% fluctuation); the congestion notification request indication is used to indicate whether congestion status needs to be actively reported. For example, if the congestion notification request indication for haptic streams is set to "true", then when congestion occurs, the DU will notify the CU to intervene in real time.

[0149] For the components of the first configuration information, the maximum number of QoS Flows in the Media Access Control Element (MAC CE) defines the maximum number of QoS Flows allowed to be carried on a single DRB, which is used to avoid excessive resource contention and prevent low-priority Flows from occupying too many channel resources; the rate multiplier is a coefficient used to dynamically adjust the rate, so as to quickly reduce the rate of non-critical Flows when sudden interference or congestion occurs, or to allocate bandwidth proportionally when there is a priority conflict; the first rate table can define a fixed priority policy, and the second rate table can define a dynamic elastic policy, and the defined rate control policy can be quickly switched by switching the table index without reconfiguring the complete parameters. This embodiment does not limit the division of the first rate table and the second rate table.

[0150] In this embodiment, the hierarchical parameters of DRB / QoS Flow and the dynamic mechanism of MAC CE enable refined resource management of centralized and separate entities within the base station. Furthermore, the hierarchical rate control for XR multimodal services is achieved through the QoS Flow information in the DRB configuration information and the MAC CE in the first configuration information, thereby improving the accuracy of rate management in XR service scenarios.

[0151] In one embodiment, the first intra-site request message may be a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0152] In one embodiment, as shown in FIG4, the method may further include the following step S401.

[0153] Step S401: Send the first intra-station message to the separated entity.

[0154] The first in-station message may include a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, and a second RRC message. The second RRC message includes rate control configuration information.

[0155] The rate control configuration information may include at least one of the following: the number of first configuration sets included in the first MAC CE, the rate multiplier, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an instruction to enable the second MAC CE.

[0156] The first configuration set or the second configuration set may each include at least one of LCID, direction, bit rate, rate multiple, and reserved bits. The first intra-station message is used to instruct the separation entity to send a second RRC message to the user equipment.

[0157] The first MAC CE is sent from the network node to the user equipment, and the second MAC CE is sent from the user equipment to the network node.

[0158] In this embodiment, the centralized entity sends a first intra-site message carrying the user equipment identifier and rate control configuration to the decentralized entity, triggering a process whereby the decentralized entity sends a second RRC message to the user equipment. When it is necessary to adjust the user equipment transmission rate, the centralized entity initiates the process of generating the first intra-site message, and sends the second RRC message to the user equipment through the decentralized entity, thereby achieving pre-configuration of rate control for the user equipment. First, the centralized entity performs parameter filling, embedding the first user identifier assigned by the centralized entity to the user equipment and the second user identifier assigned by the decentralized entity into the first intra-site message, and encapsulating the rate control information into the second RRC message. Then, the centralized entity sends a third intra-site request to the decentralized entity, and the decentralized entity sends the second RRC message to the user equipment according to the instructions of the first intra-site message.

[0159] In this embodiment, the first intra-station message can instruct the separate entity to send a second RRC message to the user equipment, which helps to achieve effective configuration and accurate indication of the user equipment rate control, optimize the network user experience and resource allocation of the user equipment, and provide a configuration basis for fine-grained rate control.

[0160] In one embodiment, as shown in FIG5, the method may further include the following step S501.

[0161] Step S501: Receive the first internal response message from the separate entity in response to the internal request message, and determine that all or part of the configuration information in the internal request message has been successfully configured.

[0162] In this embodiment, after receiving the intra-site request message from the centralized entity, the decoupled entity performs relevant rate configuration based on the intra-site request message and feeds back the rate configuration result to the centralized entity in the form of a first intra-site response message. After receiving the first intra-site response message from the decoupled entity in response to the intra-site request message, the centralized entity parses the first intra-site response message to obtain the configuration result of the decoupled entity in response to the intra-site request message. The configuration result of the decoupled entity can be a successful configuration of all or part of the configuration information in the intra-site request message. For example, the first intra-site response message includes an overall status code, detailed configuration status, and the error reason if configuration failure occurs.

[0163] Optionally, the separate entity can also feed back the configuration information corresponding to the configuration information in the site request message to the centralized entity.

[0164] In this embodiment, by distinguishing between successful configuration of all or part of the configuration information and between "partial success" and "complete failure", the successfully configured parameters can be retained, minimizing the impact of configuration failure on XR services, reducing service interruption time, and ensuring rapid recovery through partial retransmission. This achieves the robustness and reliability of the configuration process through a refined signaling feedback mechanism and intelligent configuration judgment logic.

[0165] In one embodiment, as shown in FIG6, the method may further include the following step S601.

[0166] Step S601: If the in-station request message includes a congestion feedback indication, receive the second in-station message reported by the separated entity.

[0167] The second in-station message includes at least one QoS Flow or DRB identifier, and congestion indication information. The congestion indication information indicates that at least one QoS Flow or DRB is congested.

[0168] In this embodiment of the application, when the intra-site request message sent by the centralized entity to the separated entity contains a congestion feedback indication, it indicates that the intra-site request message involves the need to report network congestion-related information. The centralized entity needs to further collect relevant congestion information. The separated entity reports a second intra-site message according to the indication of the intra-site request message. Then, the centralized entity receives the second intra-site message reported by the separated entity to confirm the congestion indication information corresponding to the QoS Flow or the congestion indication information corresponding to the DRB identifier.

[0169] In one embodiment, as shown in FIG7, the method may further include the following step S701.

[0170] Step S701: Determine the congestion status result based on the User Plane Packet Data Convergence Protocol (PDCP) layer of the centralized entity.

[0171] In this embodiment, the centralized entity or control plane entity determines the congestion status through the Packet Data Convergence Protocol (PDCP) layer. The PDCP layer includes PDCP buffer status, packet loss rate, retransmission rate, etc. The centralized entity or control plane entity obtains the current buffer usage, packet loss rate, retransmission rate, and other indicators from the centralized entity's PDCP layer, and records the PDCP layer status information for each QoS Flow or PDU session. Based on network configuration and performance requirements, a congestion threshold is set, and finally, the PDCP layer status of each QoS Flow or PDU session is checked to see if it exceeds the set threshold, thus obtaining the congestion status result. The centralized entity or control plane entity can push the congestion status result to the core network for dynamic resource adjustment, or the centralized entity or control plane entity can initiate congestion control policies locally.

[0172] In this embodiment, by providing real-time congestion status feedback, the CU's cache size, bandwidth reservation, or QoS guarantee level are automatically adjusted to achieve rapid congestion response, improving the accuracy and real-time performance of congestion detection. It also supports fine-grained resource management and optimization, thereby improving the precision of rate adjustment.

[0173] In one embodiment, as shown in FIG8, a rate control method is provided, which is illustrated by taking the application of the method to the separated entity in FIG1 as an example, and includes the following steps S801 to S803.

[0174] Step S801: Receive the site request message sent by the centralized entity.

[0175] The in-site request message may include at least one of first information and a multimodal identifier. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication. The rate control information is used to indicate that the QoS Flow supports uplink and / or downlink rate control. The multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service.

[0176] In this embodiment of the application, within the RAN architecture, the centralized entity is responsible for higher-layer protocol processing (e.g., RRC, PDCP), while the separate entity is responsible for physical layer implementation. The separate entity receives intra-site request messages sent by the centralized entity, parses the intra-site request messages, and extracts first information. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication, and may further include a QoS Flow list that needs to support uplink / downlink rate control. The rate control information may be a rate cap or an instruction to activate / deactivate rate control.

[0177] Step S802: Send the first intra-station response message to the centralized entity.

[0178] In this embodiment, the separate entity sends the first intra-site response message to the centralized entity through a dedicated physical signaling channel (e.g., RAN in-band signaling). For example, gNB-DU sends the first intra-site response message to gNB-CU-CP through the F1-C channel.

[0179] Optionally, if the centralized entity updates session management parameters and may report the configuration results back to the core network (SMF), the separated entity will be configured according to the renegotiated QoS parameters (e.g., reduced rate requirements) or switch to an alternative path.

[0180] Step S803: Send the first MAC CE to the user equipment.

[0181] In this embodiment of the application, the separate entity configures and adjusts the rate control of the user equipment according to the in-station request message sent by the centralized entity, generates a first MAC CE, and sends the first MAC CE to the user equipment, instructing the user equipment to perform rate control according to the configuration information of the first MAC CE.

[0182] In this embodiment, through the collaboration of the centralized entity and the decentralized entity, the decentralized entity receives the in-site request message containing the first information and performs rate control according to the rate control information in the first information, thereby realizing differentiated rate control of specific services in the traffic according to QoS Flow, and thus improving the accuracy of rate control.

[0183] In one embodiment, as shown in FIG9, the method further includes the step S901.

[0184] Step S901: Receive the second MAC CE information sent by the user equipment.

[0185] In this embodiment, the second MAC CE information may carry rate adjustment information requested by the user equipment based on its own situation, or the second MAC CE information may also contain user equipment demand information for certain resource blocks. The centralized entity receiving the second MAC CE information sent by the user equipment can obtain the real-time status and demands of the user equipment. Through the second MAC CE information, the decentralized entity (wireless network node) can better manage and schedule resources to meet the communication needs of the user equipment. For example, if the second MAC CE information indicates that the current signal quality of the user equipment is poor, the decentralized entity can adjust the resource allocation for that user equipment to ensure communication quality.

[0186] In one embodiment, as shown in FIG10, before step 802, the method further includes the following steps S1001 to S1002.

[0187] Step S1001: Determine at least one of the candidate QoS Flow set and / or DRB, QoS Flow report congestion information based on the first information.

[0188] In this embodiment, the separation entity filters out the QoS Flows that need adjustment based on the first information carried in the in-site request message, forming a candidate QoS Flow set and / or QoS Flow report congestion information. Furthermore, the separation entity can also map the QoS Flow to the DRB according to the RAN architecture characteristics, or determine the QoS Flow report congestion information and configure it according to the in-site request message.

[0189] Step S1002: Based on the configuration results of at least one of the candidate QoS Flow set and / or DRB, QoS Flow report congestion information, construct the first intra-site response message.

[0190] In this embodiment of the application, during the configuration process based on the intra-site request message, the separated entity constructs a first intra-site response message by recording the configuration results of each QoS Flow and DRB. For example, the first intra-site response message may indicate that part or all of the configuration for the intra-site request message is successful, or the first intra-site response message may also carry congestion information.

[0191] In one embodiment, as shown in FIG11, the method may further include the following step S1101.

[0192] Step S1101: Receive the first intra-station message sent by the centralized entity, and send the second RRC message in the first intra-station message to the user equipment.

[0193] The second RRC message includes rate control configuration information.

[0194] In this embodiment, the decoupling entity receives a first intra-site message from the central entity and sends the second RRC message carried in the first intra-site message to the user equipment, instructing the user equipment to perform pre-configuration. Specifically, the decoupling entity converts the parsed second RRC message format into instructions that the user equipment can directly execute, and ensures that it is transmitted through the local radio interface. The decoupling entity uses the content of the second RRC message to generate downlink control signaling conforming to the 3GPP protocol, fills the instruction with rate control parameters, uses the user terminal identifier as the basis for user equipment addressing, and marks the instruction as high priority according to the priority field or service type in the configuration information to ensure rapid terminal response. Finally, the decoupling entity sends the second RRC message to the user equipment through the radio interface, and then the user equipment parses the second RRC message, extracts the rate control configuration information for pre-configuration, and may feed back the configuration execution result to the base station, realizing a closed loop between the network node and the user equipment.

[0195] In this embodiment, by encapsulating and forwarding the second RRC message, the reliability of the separate entity combined with the RRC higher-layer signaling and the fast response capability of the MAC layer are realized to pre-configure the user equipment, laying the foundation for subsequent rate control of the user equipment based on the first information.

[0196] In one embodiment, as shown in FIG12, the method may further include the following step S1201.

[0197] Step S1201: Generate the first MAC CE based on the rate control configuration information and congestion status results in the first station message.

[0198] In this embodiment, the separating entity generates a first MAC CE based on the rate control configuration information and congestion status result in the first intra-site message. Furthermore, the rate control configuration information can be carried in a third intra-site request issued by the central entity, or it can be carried in a second MAC CE sent by the user equipment to the separating entity. The separating entity determines the QoS Flow identifier corresponding to the traffic requiring rate control, the set maximum uplink or downlink rate, etc.

[0199] In one embodiment, as shown in FIG13, the method may further include the following step S1301.

[0200] Step S1301: Send the first MAC CE to the user equipment.

[0201] The first MAC CE includes at least one first configuration set.

[0202] In this embodiment of the application, the separation entity sends the first MAC CE to the user equipment through the physical layer (e.g., through the PDCCH / PUCCH channel) to trigger the real-time rate adjustment of the user equipment.

[0203] In one embodiment, the first intra-site response message may include a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message.

[0204] In one embodiment, as shown in FIG14, the method may further include the following step S1401.

[0205] Step S1401: Receive the second MAC CE sent by the user equipment.

[0206] The second MAC CE includes at least one second configuration set.

[0207] In this embodiment, the second configuration set includes at least one of LCID, direction, bit rate, rate multiple, and reserved bits. The number of second configuration sets included in the second MAC CE is determined by the number of second configuration sets in the first RRC message.

[0208] The separation entity receives the second MAC CE proactively reported by the user equipment (UE), parses the configuration information carried within, and performs corresponding resource management or state synchronization operations. Specifically, the UE efficiently reports its local configuration-required rate adjustment requests to the network node via the second MAC CE, without waiting for higher-layer signaling. After receiving the second MAC CE from the UE, the separation entity parses it to obtain LCID, direction, bit rate, etc., and maps this information to its local resource management logic (e.g., adjusting QoS parameters). It also processes the rate multiplier accordingly; for example, if the original base rate is 20Mbps, and a rate multiplier of 2 is received, it is adjusted to 40Mbps.

[0209] In this embodiment, by actively feeding back the second MAC CE from the user equipment, fast and flexible terminal-base station closed-loop control is achieved, enabling network resources to be adjusted on demand, avoiding the rigidity of fixed configurations, and improving the flexibility of rate control.

[0210] In one embodiment, as shown in FIG15, the method further includes the step S1501.

[0211] Step S1501: Receive the congestion feedback indication configured by the centralized entity and report the second intra-station message to the centralized entity.

[0212] The second in-station message includes at least one QoS FLOW or DRB identifier, as well as congestion indication information; the congestion indication information is used to indicate that at least one QoS FLOW or DRB is congested.

[0213] In one embodiment, as shown in FIG16, a rate control method is provided, which is illustrated by taking the application of the method to the user equipment in FIG1 as an example, and includes the following steps S1601.

[0214] Step S1601: Receive the first MAC CE sent by the wireless network node, or send the second MAC CE to the wireless network node.

[0215] The first MAC CE includes at least one first configuration set; the first configuration set includes rate control information, which is used to indicate that at least one QoS Flow supports uplink and / or downlink rate control.

[0216] The second MAC CE includes at least one second configuration set; the second configuration set includes recommendation information for rate control information; the recommendation information is used to suggest that the wireless network node adjust the rate for QoS Flow.

[0217] In this embodiment, the user equipment (UE) receives a first MAC CE sent by a separate entity in the network node. This allows the network node to inform the UE of its ability or instructions to perform rate control on the QoS Flow via the first MAC CE. Alternatively, the UE can send a second MAC CE to the network node to proactively report its local status, such as bandwidth requirements or rate adjustment requests. The first MAC CE issued by the network node is used to notify the UE that it supports a dynamically rate-adjusted QoS Flow and carries specific rules or restrictions for rate control. The second MAC CE is used by the UE to feed back real-time performance indicators of its local QoS Flow (e.g., rate demand, congestion warning) to the network node.

[0218] In this embodiment, a closed-loop mechanism for dynamic rate control is established through bidirectional communication between the user equipment and the network node: the network node proactively informs the user equipment of the QoS Flow and its rules supporting uplink / downlink rate control via the first MAC CE, enabling the equipment to clearly understand the rate adjustment range; simultaneously, the user equipment uses the second MAC CE to provide real-time feedback on its local status (e.g., bandwidth requirements, congestion warnings, etc.), assisting the network node in dynamically optimizing resource allocation. This closed-loop process forms a continuously interactive feedback link, ensuring that the network can accurately adjust the QoS Flow rate based on the device's real-time performance indicators, and also ensuring that the device efficiently executes rate control according to network policies. This significantly improves end-to-end service quality, reduces congestion risk, optimizes network resource utilization, and enhances the system's adaptability and response efficiency to dynamic service demands.

[0219] In one embodiment, as shown in FIG17, the method may further include the following step S1701.

[0220] Step S1701: Send the first RRC message to the network node.

[0221] The first RRC message includes at least one of the following: an identifier of at least one QoS Flow and a rate control indication.

[0222] In this embodiment, when the XR service applied by the user equipment changes, the user equipment can send a first RRC message to the network node. The network node's decoupled entity (DU) dynamically receives the QoS requirements or status information reported by the user equipment to perform real-time rate control on the user equipment. Specifically, the QoS Flow identifier is used to distinguish the traffic that needs to be controlled; for example, the QoS Flow identifier can be used to distinguish between holographic video streams and haptic feedback streams. The QoS Flow-related rate control indication represents the suggested uplink and downlink rate limits and the effective time, etc. The multimodal identifier is used to determine whether rate control is needed for the current service request according to the first information.

[0223] In this embodiment, real-time feedback between the user equipment and the network node is realized through the first RRC message, realizing a closed loop of rate adjustment between the network node and the user equipment, and the user equipment instructs the network node according to the QoS Flow dimension, so that the network node can adjust the rate according to the first information, which can meet the complex service requirements of XR services and ensure the stability of XR services.

[0224] In one embodiment, as shown in FIG18, the method may further include the following step S1801.

[0225] Step S1801: Receive the second RRC message sent by the wireless network node.

[0226] The second RRC message includes rate control configuration information; the rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, the rate multiple, the first rate table or the second rate table, the number of second configuration sets included in the second MAC CE, and an instruction to enable the second MAC CE; the second RRC message is used to configure the first MAC CE or the second MAC CE.

[0227] In one embodiment, as shown in FIG19, the method may further include the following step S1901.

[0228] Step S1901: After receiving the second RRC message, determine the configuration information of the first MAC CE and / or the second MAC CE according to the rate control configuration information.

[0229] In this embodiment, the second RRC message is used to pre-configure relevant parameters of the rate control mechanism between the user equipment and the network node, defining the interaction format, range, and conditions of the subsequent first MAC CE or second MAC CE. After receiving the second RRC message from the network node, the user equipment determines the configuration information of the first MAC CE and / or the second MAC CE according to the rate control configuration information in the second RRC message, and performs pre-configuration. In an exemplary embodiment, taking the network node configuring burst transmission capability for the UE's video stream (QoS FlowA) as an example, the second RRC configuration allows the first MAC CE to carry two configuration sets, with a rate multiplier range of 1 to 3 times, enabling the first rate table (containing {10, 20, 30, 40 Mbps}), and enabling the second MAC CE, allowing the user equipment to carry one second configuration set each time it sends a second MAC CE. In subsequent processes, the network node informs the user equipment through the first MAC CE that the uplink rate of QoS FlowA can be increased to a preset base value × 3 (e.g., 10 Mbps × 3 = 30 Mbps), and references 30 Mbps in the first rate table.

[0230] In this embodiment, the user equipment is pre-configured through the second RRC message, enabling the second MAC CE capability to allow the user equipment to actively provide feedback on its needs. The RRC configuration determines the on / off state of this function, balancing network control and user experience, and achieving closed-loop processing of rate control.

[0231] In one embodiment, as shown in FIG20, the method may further include the following step S2001.

[0232] Step S2001: After receiving the first MAC CE, negotiate the QoS Flow rate with the peer entity based on the configuration information carried in the first MAC CE.

[0233] Peer entities include second user equipment, servers, etc.

[0234] In this embodiment of the application, in scenarios of direct device-to-device communication (e.g., end-to-end, Device-to-Device, D2D) or multi-user collaborative communication, after receiving the first MAC CE, the first user equipment may need to negotiate the QoS Flow rate with the second user equipment to ensure that both parties can obtain appropriate resources and quality of service during communication. Alternatively, in scenarios where a user equipment interacts with a server, the server acts as the service provider, and the first MAC CE received by the user equipment may originate from the server or be forwarded through network nodes. In this case, the user equipment needs to negotiate the QoS Flow rate with the server to meet the rate requirements of different services (e.g., video streaming, file downloading, etc.).

[0235] Specifically, the user equipment (UE) proposes a rate to its peer entity based on the configuration information in the first MAC CE, combined with its own capabilities and needs. Upon receiving the proposal, the peer entity evaluates it according to its own circumstances and provides feedback. The two parties may engage in multiple interactions before finally determining a QoS Flow rate acceptable to both.

[0236] In this embodiment, the user equipment can negotiate the QoS Flow rate with the peer entity and allocate an appropriate transmission rate for the QoS Flow based on the current network conditions, service requirements, and resource availability, thereby improving the utilization of network resources and ensuring the quality of service for communication.

[0237] In one embodiment, as shown in FIG21, the method may further include the following step S2101.

[0238] Step S2101: When it is detected that the uplink QoS Flow or DRB rate cannot reach the target rate configured by the network, a second MAC CE is sent to the wireless network node.

[0239] The configuration information carried in the second MAC CE is determined by the second RRC message.

[0240] In this embodiment of the application, when the user equipment detects that the uplink QoS Flow or DRB rate cannot reach the target rate configured by the network, it generates a second MAC CE according to the rate adjustment requirements of the communication service and sends the second MAC CE to the wireless network node.

[0241] In one embodiment, a wireless network node may include a base station, a base station control plane entity, a base station centralized entity, or a base station separate entity.

[0242] In one embodiment, a rate control method is provided, which is illustrated by taking the application of the method to a control surface entity as an example, and includes the following steps:

[0243] Send an internal request message to the separated entity.

[0244] The in-site request message includes at least one of the following: first information and a multimodal identifier. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication. The rate control information indicates that the service quality requirement flow (QoS) requires uplink and / or downlink rate control. The multimodal identifier indicates that the QoS flow is associated with a multimodal communication service.

[0245] In this embodiment, the control plane entity CU-CP can interact with the separate entity DU according to the same rate control principle as the centralized entity CU in the above embodiments to achieve rate control for user equipment. The detailed rate control process for the control plane entity side in this embodiment will not be described again.

[0246] In one embodiment, as shown in FIG22, the method further includes the steps S2201 to S2202.

[0247] Step S2201: Send a control plane in-station request message to the user plane entity.

[0248] The control plane intra-site request message may include at least one of QoS Flow information, PDU session information, and congestion state report indication information associated with QoS Flow or PDU session; the congestion state report indication information may include at least one of uplink, downlink, or bidirectional.

[0249] In this embodiment, the control plane entity actively queries the user plane entity for the congestion status of a specific QoS Flow or PDU session in order to perform QoS assurance or congestion control subsequently. The control plane entity identifies the QoS Flow that needs to be queried for congestion status based on the QoS Flow information, identifies the corresponding PDU session identifier, associates it with a specific end-to-end session, and then instructs the user plane entity to report the direction of the congestion status according to the congestion status report indication information. For example, if the congestion status report indication information is "uplink," then the user plane entity needs to report the congestion status in the uplink direction of that QoS Flow / session.

[0250] Step S2202: Receive the user plane in-site response message sent by the user plane entity.

[0251] The user plane in-site response message may include at least one of QoS Flow information, PDU session information, and congestion status information associated with QoS Flow or PDU session; the congestion status information may include at least one of uplink, downlink, or bidirectional.

[0252] In this embodiment, the user plane entity encapsulates the detected actual congestion status data, QoS Flow information, and PDU session information into a user plane intra-site response message based on the fourth intra-site request message, and feeds it back to the control plane entity, so that the control plane entity can dynamically adjust the rate control strategy based on the user plane intra-site response message.

[0253] In this embodiment, real-time monitoring of congestion status is achieved through real-time interaction between user plane entities and control plane entities, ensuring that network resources are dynamically adjusted to adapt to the service requirements of XR services. Furthermore, rate control strategies are adjusted according to the specific QoS Flow or PDU session congestion status, which can improve the accuracy of rate control and increase resource utilization.

[0254] In one embodiment, as shown in FIG23, after step 2202, the method may include the following step S2301.

[0255] Step S2301: Determine the congestion status result based on the user plane response message.

[0256] The congestion status result includes at least one QoS Flow experiencing congestion.

[0257] In this embodiment, the control plane entity determines whether at least one QoS Flow or PDU session is congested by using the congestion status information carried in the fourth-station intra-response message, thereby obtaining a congestion status result. The control plane entity first parses the fourth-station intra-response message to obtain congestion status information, QoS Flow information, and PDU session information, and then parses the direction of congestion in the congestion status information, such as uplink congestion, downlink congestion, or bidirectional congestion. If at least one QoS Flow (or a PDU session associated with a QoS Flow) is marked as congested (e.g., "uplink congestion" or "bidirectional congestion"), the control plane entity triggers subsequent processing; if none of the QoS Flows report congestion, the current congestion status result is "no congestion" or "normal state".

[0258] In this embodiment, by refining the QoS Flow and congestion direction, the location and cause of congestion can be accurately pinpointed, avoiding blind adjustments to all resources, providing real-time data support for the control plane, and quickly responding to changes in network status. At the same time, differentiated rate control is adopted at the PDU session or QoS Flow level to ensure the adaptability of rate control to service requirements.

[0259] It should be understood that although the steps in the flowchart of Figure 2-23 are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in Figure 2-23 may include multiple steps or stages, which are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

[0260] In one embodiment, as shown in FIG24, a rate control device 2400 is provided, comprising: a first transmitting module 2401, wherein:

[0261] The first sending module 2401 is used to send an intra-site request message to the separated entity; the intra-site request message includes at least one of first information and a multimodal identifier, the first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information is used to indicate that the service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control; the multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service.

[0262] In one embodiment, the device 2400 further includes:

[0263] The first receiving module is configured to receive a first network message sent by a network node or a first radio resource control (RRC) message sent by a user equipment; the first network message includes one or more bearer information, the bearer information including at least one of protocol data unit (PDU) session identifier, QoS flow identifier, QoS flow-related rate control information, and multimodal identifier; the first RRC message includes at least one of at least one of QoS flow identifier and rate control indication.

[0264] In one embodiment, the first network message includes a core network message issued by the core network or an inter-station message sent by the second base station, wherein the core network message includes any one of the following:

[0265] Handover request message, PDU session establishment request message, PDU session resource establishment request, PDU session resource modification request, initial context establishment request, user equipment (UE) context modification request;

[0266] Inter-station messages include any of the following: switch request messages and switch response messages.

[0267] In one embodiment, the in-site request message includes either a first in-site request message or a second in-site request message.

[0268] In one embodiment, the first information in the first site request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, data radio bearer (DRB) configuration information, and first configuration information.

[0269] In one embodiment, the DRB configuration information includes a DRB identifier and QoS Flow information mapped to the DRB; the QoS Flow information includes at least one of the following: a QoS Flow identifier, a QoS Flow service quality QoS configuration, a first indication information list, a congestion notification request indication, and a congestion feedback indication; the first indication information list contains rate control information and is used to indicate that one or more QoS Flows are configured with rate control indications; the congestion notification request indication indicates that at least one QoS Flow is congested; the congestion feedback indication is used to instruct a separate entity to report the congestion status of one or more QoS Flows or DRBs.

[0270] In one embodiment, the first configuration information includes: a Media Access Control Element (MAC CE); the MAC CE includes at least one of a maximum number of QoS Flows, a rate multiplier, a first rate table, or a second rate table; the first rate table or the second rate table is used to indicate the quantized rate value, and each value in the first rate table or the second rate table corresponds to a specific rate value.

[0271] In one embodiment, the first intra-site request message is either a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0272] In one embodiment, the first information in the second intra-site request message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, a QoS list, and / or at least one second indication information; the second indication information is used to indicate that one or more QoS Flows are congested or that the expected rate cannot be guaranteed.

[0273] In one embodiment, the device 2400 further includes:

[0274] The second sending module is used to send a first intra-station message to the separate entity, wherein the first intra-station message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, and a second RRC message; the second RRC message includes rate control configuration information.

[0275] The rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, the rate multiplier, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an instruction to enable the second MAC CE;

[0276] The first configuration set or the second configuration set respectively includes at least one of the following: logical channel identifier (LCID), direction, bit rate, rate multiple, and reserved bits; the first intra-station message is used to instruct the separation entity to send a second RRC message to the user equipment.

[0277] In one embodiment, the device 2400 further includes:

[0278] The second receiving module is used to receive the first internal response message from the separate entity in response to the internal request message, and to determine whether all or part of the configuration information in the internal request message has been successfully configured.

[0279] In one embodiment, the device 2400 further includes:

[0280] The third receiving module is used to receive a second intra-site message reported by the separated entity if the intra-site request message includes a congestion feedback indication. The second intra-site message includes at least one QoS Flow or DRB identifier and congestion indication information. The congestion indication information is used to indicate that at least one QoS Flow or DRB is congested.

[0281] In one embodiment, the device 2400 further includes:

[0282] The first determining module is used to determine the congestion status result based on the user plane packet data aggregation protocol (PDCP) layer of the centralized entity.

[0283] Specific limitations regarding the rate control device can be found in the limitations of the rate control method described above, and will not be repeated here. Each module in the aforementioned rate control device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware or independently of the processor in the computer device, or stored in software in the memory of the computer device, so that the processor can call and execute the operations corresponding to each module.

[0284] Figure 25 is a schematic diagram of the structure of an access network device provided in an embodiment of this application. The access network device may include a receiver 2501, a memory 2502, a processor 2503, at least one communication bus 2504, and a transmitter 2505. The communication bus 2504 is used to realize communication connections between components. The memory 2502 may include a high-speed RAM memory, and may also include non-volatile memory (NVM), such as at least one disk storage device. The memory 2502 can store various programs for performing various processing functions and implementing the method steps of this embodiment. In this embodiment, the transmitter 2505 can be a radio frequency processing module or a baseband processing module in the access network device, and the receiver 2501 can also be a radio frequency processing module or a baseband processing module in the access network device. The transmitter 2505 and receiver 2501 can be integrated together to form a transceiver. Both the transmitter 2505 and receiver 2501 can be coupled to the processor 2503, and can perform receiving or transmitting actions under the instruction or control of the processor 2503.

[0285] In this embodiment, the transmitter 2505 is used to send an intra-site request message to the separated entity; the intra-site request message includes at least one of first information and a multimodal identifier, the first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information is used to indicate that the service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control; the multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service.

[0286] Receiver 2501 is used to receive a first network message sent by a network node or a first radio resource control (RRC) message sent by a user equipment; the first network message includes one or more bearer information, the bearer information including at least one of protocol data unit (PDU) session identifier, QoS flow identifier, QoS flow-related rate control information, and multimodal identifier; the first RRC message includes at least one of at least one of QoS flow identifier and rate control indication.

[0287] In one embodiment, the first network message includes a core network message issued by the core network or an inter-station message sent by the second base station, wherein the core network message includes any one of the following:

[0288] Handover request message, PDU session establishment request message, PDU session resource establishment request, PDU session resource modification request, initial context establishment request, user equipment (UE) context modification request;

[0289] Inter-station messages include any of the following: switch request messages and switch response messages.

[0290] In one embodiment, the in-site request message includes either a first in-site request message or a second in-site request message.

[0291] In one embodiment, the first information in the first site request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, data radio bearer (DRB) configuration information, and first configuration information.

[0292] In one embodiment, the DRB configuration information includes a DRB identifier and QoS Flow information mapped to the DRB; the QoS Flow information includes at least one of the following: a QoS Flow identifier, a QoS Flow service quality QoS configuration, a first indication information list, a congestion notification request indication, and a congestion feedback indication; the first indication information list contains rate control information and is used to indicate that one or more QoS Flows are configured with rate control indications; the congestion notification request indication indicates that at least one QoS Flow is congested; the congestion feedback indication is used to instruct a separate entity to report the congestion status of one or more QoS Flows or DRBs.

[0293] In one embodiment, the first configuration information includes: a Media Access Control Element (MAC CE); the MAC CE includes at least one of a maximum number of QoS Flows, a rate multiplier, a first rate table, or a second rate table; the first rate table or the second rate table is used to indicate the quantized rate value, and each value in the first rate table or the second rate table corresponds to a specific rate value.

[0294] In one embodiment, the first intra-site request message is either a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0295] In one embodiment, the first information in the second intra-site request message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, a QoS list, and / or at least one second indication information; the second indication information is used to indicate that one or more QoS Flows are congested or that the expected rate cannot be guaranteed.

[0296] In one embodiment, transmitter 2505 is specifically used to send a first intra-station message to a separate entity. The first intra-station message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, and a second RRC message. The second RRC message includes rate control configuration information.

[0297] The rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, the rate multiplier, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an instruction to enable the second MAC CE;

[0298] The first configuration set or the second configuration set respectively includes at least one of the following: logical channel identifier (LCID), direction, bit rate, rate multiple, and reserved bits; the first intra-station message is used to instruct the separation entity to send a second RRC message to the user equipment.

[0299] In one embodiment, receiver 2501 is specifically configured to receive a first internal response message from the separate entity in response to the internal request message, and determine that all or part of the configuration information in the internal request message has been successfully configured.

[0300] In one embodiment, receiver 2501 is specifically configured to receive a second intra-site message reported by a separate entity if the intra-site request message includes a congestion feedback indication. The second intra-site message includes at least one QoS Flow or DRB identifier and congestion indication information. The congestion indication information is used to indicate that at least one QoS Flow or DRB is congested.

[0301] In one embodiment, the processor 2503 is specifically configured to determine the congestion status result based on the User Plane Packet Data Convergence Protocol (PDCP) layer of the centralized entity.

[0302] In one embodiment, a non-volatile computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, causes the processor to perform the following steps:

[0303] Send an in-station request message to the separated entity; the in-station request message includes at least one of first information and a multimodal identifier, the first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information is used to indicate that the service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control; the multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service.

[0304] In one embodiment, when a computer program is executed by a processor, the processor further performs the following steps:

[0305] The system receives a first network message sent by a network node or a first radio resource control (RRC) message sent by a user equipment. The first network message includes one or more bearer information, which includes at least one of the following: protocol data unit (PDU) session identifier, QoS flow identifier, QoS flow-related rate control information, and multimodal identifier. The first RRC message includes at least one of the following: at least one QoS flow identifier and rate control indication.

[0306] In one embodiment, the first network message includes a core network message issued by the core network or an inter-station message sent by the second base station, wherein the core network message includes any one of the following:

[0307] Handover request message, PDU session establishment request message, PDU session resource establishment request, PDU session resource modification request, initial context establishment request, user equipment (UE) context modification request;

[0308] Inter-station messages include any of the following: switch request messages and switch response messages.

[0309] In one embodiment, the in-site request message includes either a first in-site request message or a second in-site request message.

[0310] In one embodiment, the first information in the first site request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the separate entity, data radio bearer (DRB) configuration information, and first configuration information.

[0311] In one embodiment, the DRB configuration information includes a DRB identifier and QoS Flow information mapped to the DRB; the QoS Flow information includes at least one of the following: a QoS Flow identifier, a QoS Flow service quality QoS configuration, a first indication information list, a congestion notification request indication, and a congestion feedback indication; the first indication information list contains rate control information and is used to indicate that one or more QoS Flows are configured with rate control indications; the congestion notification request indication indicates that at least one QoS Flow is congested; the congestion feedback indication is used to instruct a separate entity to report the congestion status of one or more QoS Flows or DRBs.

[0312] In one embodiment, the first configuration information includes: a Media Access Control Element (MAC CE); the MAC CE includes at least one of a maximum number of QoS Flows, a rate multiplier, a first rate table, or a second rate table; the first rate table or the second rate table is used to indicate the quantized rate value, and each value in the first rate table or the second rate table corresponds to a specific rate value.

[0313] In one embodiment, the first intra-site request message is either a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0314] In one embodiment, the first information in the second intra-site request message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, a QoS list, and / or at least one second indication information; the second indication information is used to indicate that one or more QoS Flows are congested or that the expected rate cannot be guaranteed.

[0315] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0316] Send a first intra-site message to the decoupled entity. The first intra-site message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decoupled entity, and a second RRC message. The second RRC message includes rate control configuration information.

[0317] The rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, the rate multiplier, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an instruction to enable the second MAC CE;

[0318] The first configuration set or the second configuration set respectively includes at least one of the following: logical channel identifier (LCID), direction, bit rate, rate multiple, and reserved bits; the first intra-station message is used to instruct the separation entity to send a second RRC message to the user equipment.

[0319] In one embodiment, when a computer program is executed by a processor, the processor further performs the following steps:

[0320] Receive the first internal response message from the separate entity in response to the internal request message, and determine whether all or part of the configuration information in the internal request message has been successfully configured.

[0321] In one embodiment, when a computer program is executed by a processor, the processor further performs the following steps:

[0322] If the intra-site request message includes a congestion feedback indication, receive a second intra-site message reported by the separate entity. The second intra-site message includes at least one QoS Flow or DRB identifier and congestion indication information. The congestion indication information is used to indicate that at least one QoS Flow or DRB is congested.

[0323] In one embodiment, when a computer program is executed by a processor, the processor further performs the following steps:

[0324] The congestion status is determined based on the User Plane Packet Data Convergence Protocol (PDCP) layer of the centralized entity.

[0325] This application also provides a computer program product containing program instructions, which, when executed on a computer, cause the computer to perform the following steps:

[0326] Send an in-station request message to the separated entity; the in-station request message includes at least one of first information and a multimodal identifier, the first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information is used to indicate that the service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control; the multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service.

[0327] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0328] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0329] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A rate control method applied to a centralized entity of a first base station, the method comprising: Send an internal request message to the separated entity; The in-site request message includes at least one of first information and a multimodal identifier. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication. The rate control information is used to indicate that the service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control. The multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service.

2. The method according to claim 1, wherein before sending the in-site request message to the separated entity, the method further comprises: Receive a first network message sent by a network node or a first Radio Resource Control (RRC) message sent by a user equipment; The first network message includes one or more bearer information, the bearer information including at least one of Protocol Data Unit (PDU) session identifier, QoS Flow identifier, QoS Flow related rate control information, and multimodal identifier; the first RRC message includes at least one of at least one of QoS Flow identifier and rate control indication.

3. The method according to claim 2, wherein the first network message includes a core network message issued by the core network or an inter-station message sent by the second base station, and the core network message includes any one of the following: Handover request message, PDU session establishment request message, PDU session resource establishment request, PDU session resource modification request, initial context establishment request, user equipment (UE) context modification request; The inter-station messages include any one of the following: handover request messages and handover response messages.

4. The method according to claim 1, wherein the intra-site request message includes either a first intra-site request message or a second intra-site request message.

5. The method according to claim 4, wherein the first information in the first intra-station request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, data radio bearer (DRB) configuration information, and first configuration information.

6. The method according to claim 5, wherein the DRB configuration information includes a DRB identifier and QoS Flow information mapped to the DRB; The QoS Flow information includes: The QoS Flow identifier, QoS Flow service quality configuration, first indication information list, congestion notification request indication, and congestion feedback indication are at least one of the following: the first indication information list contains the rate control information, and the first indication information list is used to indicate one or more QoS Flows configured with rate control indications; the congestion notification request indication indicates that at least one QoS Flow is congested. The congestion feedback indication is used to instruct the separate entity to report congestion status for one or more QoS Flows or DRBs.

7. The method according to claim 5, wherein the first configuration information includes: The Media Access Control (MAC) CE is a control element of the Media Access Control (MAC) layer. The MAC CE includes at least one of the following: maximum number of QoS Flows, rate multiplier, first rate table, or second rate table. The first rate table or second rate table is used to indicate the quantized rate value, and each value in the first rate table or second rate table corresponds to a specific rate value.

8. The method according to claim 4, wherein the first intra-site request message is a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

9. The method according to claim 4, wherein the first information in the second intra-station request message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, a QoS list and / or at least one second indication information; the second indication information is used to indicate one or more QoS Flow congestion or failure to guarantee the expected rate.

10. The method according to claim 1, further comprising: A first intra-site message is sent to the decentral entity. The first intra-site message includes a first user equipment identifier assigned to the user equipment by the central entity, a second user equipment identifier assigned to the user equipment by the decentral entity, and a second RRC message. The second RRC message includes rate control configuration information. The rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, the rate multiplier, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an instruction to enable the second MAC CE; The first configuration set or the second configuration set respectively includes at least one of the following: logical channel identifier (LCID), direction, bit rate, rate multiple, and reserved bits; the first intra-station message is used to instruct the separation entity to send the second RRC message to the user equipment.

11. The method according to claim 1, further comprising: Receive the first internal response message from the separate entity in response to the internal request message, and determine that all or part of the configuration information in the internal request message has been successfully configured.

12. The method according to claim 1, further comprising: If the intra-site request message includes a congestion feedback indication, the second intra-site message reported by the separated entity is received. The second intra-site message includes at least one QoS Flow or DRB identifier and congestion indication information. The congestion indication information is used to indicate that at least one QoS Flow or DRB is congested.

13. The method according to claim 1, further comprising: The congestion status result is determined based on the User Plane Packet Data Convergence Protocol (PDCP) layer of the centralized entity.

14. A rate control method applied to separating entities, the method comprising: Receive internal request messages sent by centralized entities; The in-site request message includes at least one of first information and a multimodal identifier. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication. The rate control information is used to indicate that the QoS Flow supports uplink and / or downlink rate control. The multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service. Send the first intra-station response message to the centralized entity; as well as Send the first MAC CE to the user equipment.

15. The method of claim 14, further comprising: Receive the second MAC CE information sent by the user equipment.

16. The method of claim 14, wherein before sending the first intra-station response message to the centralized entity, the method further comprises: Based on the first information, determine at least one of the candidate QoS Flow set and / or DRB, QoS Flow report congestion information; Based on the configuration results of at least one of the candidate QoS Flow set and / or the DRB and the QoS Flow report congestion information, a first intra-site response message is constructed.

17. The method of claim 14, further comprising: Receive the first intra-station message sent by the centralized entity, and send the second RRC message in the first intra-station message to the user equipment; The second RRC message includes rate control configuration information.

18. The method of claim 14, further comprising: The first MAC CE is generated based on the rate control configuration information and congestion status results in the first station message.

19. The method of claim 14, further comprising: Send a first MAC CE to the user equipment; the first MAC CE includes at least one first configuration set.

20. The method of claim 14, wherein the first intra-site response message includes a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message.

21. The method of claim 14, further comprising: Receive a second MAC CE sent by a user equipment; the second MAC CE includes at least one second configuration set.

22. The method of claim 14, further comprising: The congestion feedback indication configured by the centralized entity is received, and a second intra-site message is reported to the centralized entity. The second intra-site message includes at least one QoS FLOW or DRB identifier and congestion indication information. The congestion indication information is used to indicate that at least one QoS FLOW or DRB is congested.

23. A rate control method applied to a user equipment, the method comprising: Receive a first MAC CE sent by a wireless network node, or send a second MAC CE to the wireless network node; The first MAC CE includes at least one first configuration set; the first configuration set includes rate control information, which is used to indicate that at least one QoS Flow supports uplink and / or downlink rate control; The second MAC CE includes at least one second configuration set; the second configuration set includes suggestion information for rate control information; the suggestion information is used to suggest that the wireless network node adjust the rate of the QoS Flow.

24. The method of claim 23, further comprising: Send a first RRC message to the network node, the first RRC message including at least one of a QoS Flow identifier and a rate control indication.

25. The method of claim 23, further comprising: The system receives a second RRC message sent by the wireless network node. The second RRC message includes rate control configuration information. The rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, a rate multiple, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an enable second MAC CE indication. The second RRC message is used to configure the first MAC CE or the second MAC CE.

26. The method of claim 25, further comprising: Upon receiving the second RRC message, the configuration information of the first MAC CE and / or the second MAC CE is determined based on the rate control configuration information.

27. The method of claim 23, further comprising: Upon receiving the first MAC CE, the system negotiates the QoS Flow rate with the peer entity based on the configuration information carried in the first MAC CE.

28. The method of claim 23, further comprising: When it is detected that the uplink QoS Flow or DRB rate cannot reach the target rate configured by the network, a second MAC CE is sent to the wireless network node; The configuration information carried in the second MAC CE is determined by the second RRC message.

29. The method of claim 23, wherein the wireless network node includes a base station, a base station control plane entity, a base station centralized entity, or a base station separate entity.

30. A rate control method applied to the control plane entity of a first base station, the method comprising: Send an internal request message to the separated entity; The in-site request message includes at least one of the following: first information on service quality requirements and a multimodal identifier. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication. The rate control information is used to indicate that the service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control. The multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service.

31. The method of claim 30, wherein before sending the first intra-station request message to the separated entity, the method further comprises: Receive a first network message sent by a network node or a first Radio Resource Control (RRC) message sent by a user equipment; The first network message includes one or more bearer information, the bearer information including at least one of Protocol Data Unit (PDU) session identifier, QoS Flow identifier, QoS Flow related rate control information, and multimodal identifier; the first RRC message includes at least one of QoS Flow identifier and rate control indication.

32. The method according to claim 31, wherein the first network message includes a core network message issued by the core network or an inter-station message sent by the second base station, and the core network message includes any one of the following: Handover request message, PDU session establishment request message, PDU session resource establishment request, PDU session resource modification request, initial context establishment request, user equipment (UE) context modification request; The inter-station messages include any one of the following: handover request messages and handover response messages.

33. The method according to claim 30, wherein the intra-site request message includes either a first intra-site request message or a second intra-site request message.

34. The method of claim 33, wherein the first information in the first intra-station request message includes at least one of the following: a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, data radio bearer (DRB) configuration information, and first configuration information.

35. The method of claim 33, wherein the first intra-site request message is a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

36. The method of claim 34, wherein the DRB configuration information includes a DRB identifier and QoS Flow information mapped to the DRB; The QoS Flow information includes: The QoS Flow identifier, QoS Flow service quality configuration, first indication information list, congestion notification request indication, and congestion feedback indication are at least one of the following: the first indication information list contains the rate control information, and the first indication information list is used to indicate one or more QoS Flows configured with rate control indications; the congestion notification request indication indicates that at least one QoS Flow is congested. The congestion feedback indication is used to instruct the separate entity to report congestion status for one or more QoS Flows or DRBs.

37. The method of claim 34, wherein the first configuration information includes: The Media Access Control (MAC) CE is a control element of the Media Access Control (MAC) layer. The MAC CE includes at least one of the following: maximum number of QoS Flows, rate multiplier, first rate table, or second rate table. The first rate table or second rate table is used to indicate the quantized rate value, and each value in the first rate table or second rate table corresponds to a specific rate value.

38. The method of claim 33, wherein the first information in the second intra-site request message includes a first user equipment identifier assigned to the user equipment by the centralized entity, a second user equipment identifier assigned to the user equipment by the decentralized entity, a QoS list and / or at least one second indication information; the second indication information is used to indicate one or more QoS Flow congestion or failure to guarantee the expected rate.

39. The method of claim 30, further comprising: A first intra-site message is sent to the decentral entity. The first intra-site message includes a first user equipment identifier assigned to the user equipment by the central entity, a second user equipment identifier assigned to the user equipment by the decentral entity, and a second RRC message. The second RRC message includes rate control configuration information. The rate control configuration information includes at least one of the following: the number of first configuration sets included in the first MAC CE, the rate multiplier, a first rate table or a second rate table, the number of second configuration sets included in the second MAC CE, and an instruction to enable the second MAC CE; The first configuration set or the second configuration set respectively includes at least one of the following: logical channel identifier (LCID), direction, bit rate, rate multiple, and reserved bits; the first intra-station message is used to instruct the separation entity to send the second RRC message to the user equipment.

40. The method of claim 30, further comprising: Receive the first internal response message from the separated entity in response to the internal request message, and determine that all or part of the configuration information in the internal request message has been successfully configured.

41. The method of claim 30, further comprising: If the intra-site request message includes a congestion feedback indication, the second intra-site message reported by the separated entity is received. The second intra-site message includes at least one QoS Flow or DRB identifier and congestion indication information. The congestion indication information is used to indicate that at least one QoS Flow or DRB is congested.

42. The method of claim 30, further comprising: Send a control plane in-station request message to the user plane entity; The control plane intra-site request message includes at least one of QoS Flow information, PDU session information, and congestion status report indication information associated with QoS Flow or PDU session; the congestion status report indication information includes at least one of uplink, downlink, or bidirectional. Receive user plane in-station response messages sent by the user plane entity; the user plane in-station response messages include at least one of QoS Flow information, PDU session information, and congestion status information associated with QoS Flow or PDU session; the congestion status information includes at least one of uplink, downlink, or bidirectional.

43. The method of claim 42, wherein after receiving the user plane in-station response message sent by the user plane entity, the method further comprises: The congestion status result is determined based on the user plane in-station response message; The congestion status results include at least one QoS Flow experiencing congestion.

44. The method of claim 30, further comprising: The congestion status result is determined based on the User Plane Packet Data Convergence Protocol (PDCP) layer of the centralized entity.

45. A rate control device applied to a centralized entity, the device comprising: The first sending module is used to send in-station request messages to the separated entities; The in-site request message includes at least one of first information and a multimodal identifier. The first information includes at least one of rate control information, congestion notification request indication, and congestion feedback indication. The rate control information is used to indicate that the service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control. The multimodal identifier is used to indicate that the QoS Flow is associated with a multimodal communication service.

46. ​​A communication device, comprising: Transmitter; The transmitter is configured to send an in-station request message to a separate entity; the in-station request message includes at least one of first information and a multimodal identifier, the first information including at least one of rate control information, congestion notification request indication, and congestion feedback indication, the rate control information being used to indicate that a service quality requirement flow (QoS Flow) supports uplink and / or downlink rate control; the multimodal identifier being used to indicate that the QoS Flow is associated with a multimodal communication service.

47. A non-volatile computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, causes the processor to perform the steps of the method according to any one of claims 1 to 44.

48. A computer program product comprising a computer program, wherein when executed by a processor, the computer program causes the processor to perform the steps of the method according to any one of claims 1 to 44.

Images