Rate control method, terminal and network side equipment

Abstract

The invention discloses a rate control method, a terminal and network side equipment, and belongs to the technical field of wireless communication, and the rate control method comprises the steps that a first node sends first information to a second node, and the first information comprises at least one of congestion information, rate control information and rate adjustment information.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technology, specifically relating to a rate control method, a terminal, and a network-side device. Background Technology

[0002] Currently, one solution for controlling the data transmission rate between the network and the terminal involves the base station notifying the application server through the core network. The application server then increases or decreases the rate, and based on feedback from the terminal, the rate adjustment is completed after multiple data transmissions with the terminal. This control method is time-consuming and inefficient. Summary of the Invention

[0003] This application provides a rate control method, a terminal, and a network-side device, which can reduce the time consumed by rate control and improve rate control efficiency.

[0004] In a first aspect, a rate control method is provided, the method comprising: a first node sending first information to a second node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0005] Secondly, a rate control method is provided, the method comprising: a second node receiving first information sent by a first node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0006] Thirdly, a rate control device is provided, comprising: a sending module for sending first information to a second node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0007] Fourthly, a rate control device is provided, comprising: a receiving module for receiving first information sent by a first node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0008] Fifthly, a rate control device is provided, the device being configured to perform the steps of the method described in the first or second aspect.

[0009] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first or second aspect.

[0010] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is used to implement the steps of the method as described in the first or second aspect, and the communication interface is used to couple with the processor.

[0011] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first or second aspect.

[0012] A ninth aspect provides a network-side device, including a processor and a communication interface, wherein the processor is configured to implement the steps of the method as described in the first or second aspect, and the communication interface is configured to be coupled to the processor.

[0013] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first or second aspect.

[0014] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method described in the first aspect, and the network-side device can be used to perform the steps of the method described in the second aspect; or, the terminal can be used to perform the steps of the method described in the second aspect, and the network-side device can be used to perform the steps of the method described in the first aspect.

[0015] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the methods described in the first or second aspect.

[0016] In a thirteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first or second aspect.

[0017] In this embodiment of the application, the first node sends first information to the second node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information. The first information can assist the second node in adjusting or controlling the rate, and rate control can be completed without multiple feedbacks, thereby reducing the time consumption of rate control and improving the efficiency of rate control. Attached Figure Description

[0018] Figure 1 This diagram illustrates a block diagram of a wireless communication system to which embodiments of this application may be applied; Figure 2 This illustration shows a flowchart of a rate control method provided in an embodiment of this application. Figure 3 This illustration shows another flowchart of the rate control method provided in an embodiment of this application; Figure 4 This illustration shows another flowchart of the rate control method provided in an embodiment of this application; Figure 5 This illustration shows another flowchart of the rate control method provided in an embodiment of this application; Figure 6 This illustration shows a structural schematic diagram of a rate control device provided in an embodiment of this application; Figure 7 This invention provides another schematic diagram of the rate control device according to an embodiment of the present application. Figure 8 This illustration shows a structural diagram of a communication device provided in an embodiment of this application; Figure 9 This illustration shows a hardware structure diagram of a terminal provided in an embodiment of this application; Figure 10 This illustration shows a hardware structure diagram of a network-side device according to an embodiment of this application; Figure 11 This illustration shows a schematic diagram of the hardware structure of another network-side device provided in an embodiment of this application. Detailed Implementation

[0019] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0020] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0021] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc.; an indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0022] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0023] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.In this context, a base station may be referred to as a Node B (NB), an Evolved Node B (eNB), a Next Generation Node B (gNB), a New Radio Node B (NR Node B), an Access Point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a Radio Base Station, a Radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The base station is not limited to any specific technical terminology. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for introduction, and the specific type of base station is not limited.

[0024] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support Function. Support Functions (BSF), Application Functions (AF), Location Management Functions (LMF), Gateway Mobile Location Centres (GMLC), and Network Data Analytics Functions (NWDAF), etc. It should be noted that this application embodiment only uses core network equipment in the NR system as an example for description, and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will also be within the scope of protection of this application.

[0025] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0026] The rate control method, terminal, and network-side device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0027] Figure 2 This diagram illustrates a flow chart of a rate control method provided in an embodiment of this application, which can be executed by a first node. Figure 2 As shown, the method may include the following steps.

[0028] S202: The first node sends first information to the second node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0029] In this embodiment, congestion information refers to congestion information in the network where the first node and the second node reside. Rate control information and rate adaptation information refer to information related to controlling and adjusting the rate between the first node and the second node, or information related to controlling and adjusting the rate of the first node or the second node, such as the coding rate. This rate can be the rate from the first node to the second node, or it can be the rate from the second node to the first node; the specific direction is not limited.

[0030] For example, the rate can be the uplink rate from the user equipment (UE) to the base station, or the downlink rate from the base station to the UE, etc., and is not specifically limited.

[0031] In this application embodiment, the rate involved in the first information may include at least one of the following: bit rate, codec rate, data rate, resource rate, and source rate.

[0032] In this embodiment, the first node and the second node are different devices, and can be implemented in various ways, including but not limited to one of the following: 1) The first node is a base station, and the second node is a terminal, core network node, or application layer node; 2) The first node is the terminal, and the second node is the base station, core network node, or application layer node; 3) The first node is a core network node, and the second node is a base station or terminal; 4) The first node is an application layer node, and the second node is a base station or terminal.

[0033] The aforementioned application layer nodes can be, for example, servers provided by a service provider, or application servers provided by third-party services, etc., and are not specifically limited to any particular type.

[0034] In this embodiment of the application, the first information can be used to assist the second node in adjusting or controlling the rate, or the first information can be used by the second node to adjust or control the rate based on the first information.

[0035] In this embodiment of the application, the first information may include at least one of the following: 1) Rate adjustment indicator; 2) Rate information; 3) Congestion information; 4) Network load information; 5) Channel information; 6) Quality of Service (QoS) information; 7) Uplink indication; whereby the uplink indication is used to indicate adjustments or control of the uplink rate; 8) Downlink indication; wherein, the downlink indication is used to indicate adjustment or control of the downlink rate; 9) Identification information.

[0036] Based on the information provided in the first part, more information can be provided to the second node, which helps the second node to adjust or control the rate more accurately, thereby improving the precision of rate adjustment or control.

[0037] In this embodiment, the aforementioned rate adjustment indication may include at least one of the following: increasing rate, increasing rate level, decreasing rate, decreasing rate level, keeping rate unchanged, keeping rate level unchanged, rate adjustment factor, and rate level adjustment factor. The rate adjustment factor (scalling factor) can be used to maintain the existing rate or rate level, or to decrease or increase the existing rate or rate level by a certain factor. For example, a rate adjustment factor less than 1 corresponds to decreasing the rate or rate level; a rate adjustment factor greater than 1 corresponds to increasing the rate or rate level; and a rate adjustment factor equal to 1 keeps the current rate or rate level unchanged. This method of providing rate adjustment indication in the first information provides more refined rate indication information to the second node, helping the second node to adjust or control the rate more accurately, thereby improving the accuracy of rate adjustment or control.

[0038] And / or, In this embodiment, the aforementioned rate information may include at least one of the following: rate, rate level, and rate range. For example, the rate may be 800 Mbps or 600 Mbps, the rate level may be slow, medium, or fast, and the rate range may be 200 Mbps-400 Mbps or 400 Mbps-600 Mbps, etc. This method of providing rate information in the first information provides more refined rate information to the second node, helping the second node to adjust or control the rate more accurately, thereby improving the accuracy of rate adjustment or control.

[0039] And / or, In this embodiment, the congestion information may include at least one of the following: whether congestion exists, congestion level, congestion cause, congestion channel, congestion scenario, congestion-related service, congestion-related session, congestion-related Quality of Service flow, congestion-related Data Radio Bearer (DRB), congestion-related Logical Channel (LCH), and congestion-related channel. For example, the congestion level may be light, medium, or heavy; the congestion cause may be high data concurrency; and the congestion-related service may be gaming. This method of providing congestion information in the first information provides more detailed network environment information to the second node, helping the second node to adjust or control the rate more accurately, thereby improving the accuracy of rate adjustment or control.

[0040] And / or, In this embodiment, the network load information may include at least one of the following: load level, whether overloaded, lightly loaded, heavily loaded, load cause, load association cause, load association scenario, load association service, load association session, load association QoS flow, load association DRB, load association LCH, and load association channel. The load level may be classified as light, medium, heavy, or other levels, and the load association service may be video playback, etc. This method of providing network load information in the first piece of information can provide more refined network status information to the second node, helping the second node to more accurately adjust or control the rate, thereby improving the accuracy of rate adjustment or control.

[0041] And / or, In this embodiment, the aforementioned channel information may include at least one of the following: channel measurement results, channel measurement level, channel condition, and channel condition. Channel condition includes parameters such as good, average, and poor channel conditions. Channel measurement results include the received signal strength of the serving cell, the quality of the serving cell, timing advance, and relevant information about neighboring cells. This method of providing channel information in the first set of information provides more refined network transmission information to the second node, helping the second node to more accurately adjust or control the rate, thereby improving the accuracy of rate adjustment or control.

[0042] And / or, In this embodiment, the aforementioned QoS information may include at least one of the following: QoS parameters, QoS requirements, QoS allocation, and QoS mapping information. For example, QoS parameters include bandwidth management, latency and jitter, congestion control, service level, and priority. QoS mapping information includes flow classification, policies, and labels. This method of providing QoS information within the first set of information enables the provision of more refined quality control information to the second node, helping the second node to more accurately adjust or control the rate, thereby improving the accuracy of rate adjustment or control.

[0043] And / or, In this embodiment, the identification information may include at least one of the following: UE ID, QoS flow ID, session ID, bearer ID, DRB ID, and LCH ID. The UE ID may be, for example, the UE ID or the Cell Radio Network Temporary Identifier (C-RNTI). Providing identification information in the first set of information allows for more granular control object information to be provided to the second node, helping it to more accurately adjust or control the rate, thereby improving the precision of rate adjustment or control.

[0044] In this application embodiment, the granularity of the first information may include at least one of the following: terminal (per-UE), QoS flow (per-QoS flow), session (per-Session), bearer (per-bearer), DRB (per-DRB), LCH (per-LCH).

[0045] In the case where the granularity of the first information is per-UE, the first information may include at least one of the following: UE rate adjustment indication, UE rate information, UE congestion information, UE network load information, UE channel information, UE uplink indication, UE downlink indication, and UE ID. In this scenario, the first information can reflect the current overall status of the UE, thereby enabling rate adjustment or rate control for all services of the UE.

[0046] In the case where the granularity of the first information is per-QoS flow, the first information may include at least one of the following: rate adjustment indication for each QoS flow, rate information for each QoS flow, congestion information for each QoS flow, network load information for each QoS flow, channel information for each QoS flow, uplink indication for each QoS flow, downlink indication for each QoS flow, and ID for each QoS flow. In this scenario, the first information can reflect the current status of the QoS flow of the first node, thereby enabling precise rate adjustment or rate control of the data flow corresponding to one or more QoS flows of the first node.

[0047] In the case where the granularity of the first information is per-session, the first information may include at least one of the following: rate adjustment indication for each session, rate information for each session, congestion information for each session, network load information for each session, channel information for each session, uplink indication for each session, downlink indication for each session, and ID for each session. In this scenario, the first information can reflect the current status of the first node's session, thereby enabling precise rate adjustment or rate control of the data streams corresponding to one or more sessions.

[0048] In the case where the granularity of the first information is per-bearer, the first information may include at least one of the following: rate adjustment indication for each bearer, rate information for each bearer, congestion information for each bearer, network load information for each bearer, channel information for each bearer, uplink indication for each bearer, downlink indication for each bearer, and ID for each bearer. In this scenario, the first information can reflect the current status of the first node's bearers, thereby enabling precise rate adjustment or rate control for one or more bearers. Furthermore, since the mapping relationship of bearers can be obtained based on the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0049] In the case where the granularity of the first information is per-DRB, the first information may include at least one of the following: rate adjustment indication for each DRB, rate information for each DRB, congestion information for each DRB, network load information for each DRB, channel information for each DRB, uplink indication for each DRB, downlink indication for each DRB, and ID of each DRB. In this scenario, the first information can reflect the current status of the DRBs of the first node, thereby enabling precise rate adjustment or rate control for the rates corresponding to one or more DRBs. Furthermore, since the mapping relationship of DRBs can be obtained from the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0050] In the case where the granularity of the first information is per-LCH, the first information may include at least one of the following: rate adjustment indication for each LCH, rate information for each LCH, congestion information for each LCH, network load information for each LCH, channel information for each LCH, uplink indication for each LCH, downlink indication for each LCH, and ID for each LCH. In this scenario, the first information can reflect the current status of the LCH of the first node, thereby enabling precise rate adjustment or rate control for one or more LCHs. Furthermore, since the mapping relationship of LCHs can be obtained from the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0051] In this embodiment of the application, the above method may include at least one of the following methods: 1) The granularity of the first information includes the terminal, and the first information includes the terminal identifier.

[0052] 2) The granularity of the first information includes QoS flow, the first information includes QoS flow identifier, or the first information includes QoS flow identifier and at least one of the following: terminal identifier, session identifier, bearer identifier, DRB identifier, LCH identifier.

[0053] 3) The granularity of the first information includes the session, the first information includes the session identifier, or the first information includes the session identifier and at least one of the following: terminal identifier, QoS flow identifier, bearer identifier, DRB identifier, LCH identifier.

[0054] 4) The granularity of the first information includes the bearer, the first information includes the bearer identifier, or the first information includes the bearer identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, DRB identifier, LCH identifier.

[0055] 5) The granularity of the first information includes DRB, the first information includes DRB identifier, or the first information includes DRB identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, LCH identifier.

[0056] 6) The granularity of the first information includes LCH, the first information includes LCH identifier, or the first information includes LCH identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, DRB identifier.

[0057] The aforementioned first information can include combinations of various identifiers, which is very flexible and can meet the needs of controlling or adjusting the rate of different objects.

[0058] In one implementation of this application embodiment, the first information may not carry identification information; wherein, the object indicated or applicable by the first information may include at least one of the following: 1) The granularity of the first information includes the terminal, and the first information indicates or applies to all QoS flows, all sessions, all bearers, all DRBs, or all LCHs of the terminal.

[0059] In this approach, the first piece of information can reflect the overall status of the terminal, enabling rate adjustment or control of all services on the terminal.

[0060] 2) The granularity of the first information includes QoS flows, and the first information indicates or applies to all QoS flows.

[0061] In this approach, the first information can reflect the current QoS flow status of the first node, enabling precise rate adjustment or control of one or more QoS flows of the first node. For example, rate adjustment or control can be performed on the current QoS flow, or on the five QoS flows starting from the third QoS flow after the current QoS flow.

[0062] 3) The granularity of the first message includes the session, and the first message indicates or applies to all sessions.

[0063] In this approach, the first information can reflect the current session status of the first node, enabling precise rate adjustment or control of one or more sessions of the first node.

[0064] 4) The granularity of the first information includes the carrier, and the first information indicates or applies to all carriers.

[0065] In this approach, the first information can reflect the current carrying status of the first node, enabling precise rate adjustment or control of one or more carrying operations on the first node. Furthermore, the first information can also include the carrying mapping relationship, which the MAC layer can obtain. Therefore, the first node can instruct the first information through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0066] 5) The granularity of the first information includes DRBs, and the first information indicates or applies to all DRBs.

[0067] In this approach, the first information can reflect the current status of the first node's DRBs, enabling precise rate adjustment or control of one or more DRBs on the first node. Furthermore, the first information can also include the mapping relationship between DRBs. The MAC layer can obtain this mapping relationship, thus allowing the first node to indicate the first information through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0068] 6) The granularity of the first information includes LCH, and the first information indicates or applies to all LCH.

[0069] In this approach, the first information can reflect the current status of the LCH of the first node, enabling precise rate adjustment or control of one or more LCHs of the first node. Furthermore, the first information can also include the mapping relationship of the LCHs. The MAC layer can obtain this mapping relationship, so the first node can indicate the first information through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0070] In this embodiment of the application, the above method may further include: The upper layer of the first node sends the first mapping information to the lower layer of the first node to help the lower layer determine the first information.

[0071] The term "bottom layer" refers to one or more layers below the "upper layer," without specific limitations. The "upper layer" includes at least one of the following: application layer, TCP / IP layer, SDAP layer, PDCP layer, RLC layer, and MAC layer.

[0072] For example, the upper layer is the SDAP layer, and the lower layer is one or more of the PDCP layer, RLC layer, MAC layer, and PHY layer below the SDAP layer.

[0073] In this embodiment of the application, in the scenario where the upper layer of the first node sends the first mapping information to the lower layer of the first node, the content of the first mapping information can have multiple forms, including at least one of the following: 1) When the granularity of the first information includes QoS flows, the first mapping information may include at least one of the following: QoS flow mapping relationship; in this scenario, the upper layer includes SDAP layer or PDCP layer; The mapping relationship between QoS flows and sessions; in this scenario, the upper layer includes the TCP / IP layer or the SDAP layer; The mapping relationship between QoS flows and bearers; in this scenario, the upper layer includes the RLC layer or the SDAP layer; The mapping relationship between QoS flows and DRBs; in this scenario, the upper layer includes either the PDCP layer or the SDAP layer; The mapping relationship between QoS flows and LCH; in this scenario, the upper layer includes the MAC layer or SDAP layer.

[0074] 2) When the granularity of the first information includes a session, the first mapping information may include at least one of the following: Session mapping relationship; in this scenario, the upper layer includes the TCP / IP layer or the SDAP layer; The mapping relationship between sessions and QoS flows; in this scenario, the upper layer includes the TCP / IP layer or the SDAP layer; The mapping relationship between sessions and bearers; in this scenario, the upper layers include RLC and TCP / IP layers; The mapping relationship between sessions and DRBs; in this scenario, the upper layer includes either the PDCP layer or the TCP / IP layer; The mapping relationship between sessions and LCH; in this scenario, the upper layers include the PHY layer, MAC layer, or TCP / IP layer.

[0075] 3) When the granularity of the first information includes the bearer, the first mapping information may include at least one of the following: The mapping relationship between the bearer and the QoS flow; in this scenario, the upper layer includes the RLC layer or the SDAP layer; The mapping relationship between the bearer and the session; in this scenario, the upper layers include RLC and TCP / IP layers; The mapping relationship between the bearer and the DRB; in this scenario, the upper layer includes either the PDCP layer or the RLC layer; Mapping relationship between the bearer and LCH.

[0076] It's worth noting that when the first information has multiple granularities, if duplicate mapping relationships exist in the first mapping information, these duplicate relationships can be deleted, retaining only the unique ones. For example, if the granularity of the first information includes QoS flows, the corresponding first mapping information includes the mapping relationship between QoS flows and sessions. If the granularity of the first information includes sessions, the corresponding first mapping information includes the mapping relationship between sessions and QoS flows. If the granularity of the first information includes both QoS flows and sessions, then the corresponding first mapping information includes only one set of mapping relationships between sessions and QoS flows.

[0077] In this embodiment of the application, the above method may further include: The upper layer of the first node sends the first mapping information to the lower layer of the first node to assist the lower layer in determining the first information. The first mapping information includes at least one of the following: 1) Mapping relationship between LCH and DRB; 2) Mapping relationship between LCH and bearer; 3) The mapping relationship between LCH and session; 4) Mapping relationship between LCH and QoS flows; 5) Mapping relationship between DRB and bearer; 6) The mapping relationship between DRB and session; 7) Mapping relationship between DRB and QoS flow; 8) The mapping relationship between the bearer and the session; 9) Mapping relationship between bearer and QoS flow.

[0078] Both of the above methods involve the upper layer of the first node sending the first mapping information to the lower layer of the first node, where the lower layer determines the first information. This method solves the problem that the lower layer cannot know the mapping relationship of the upper layer, and is suitable for rate control or adjustment in scenarios where the lower layer cannot know the mapping relationship of the upper layer. Alternatively, in this embodiment, the lower layer of the first node can send the first mapping information to the upper layer of the first node, where the upper layer determines the first information. This method solves the problem that the upper layer cannot know the mapping relationship of the lower layer, and is suitable for rate control or adjustment in scenarios where the upper layer cannot know the mapping relationship of the lower layer. Regardless of the method, the first information can be determined and then sent to the second node to assist the second node in rate adjustment or control.

[0079] In this embodiment of the application, the above method may further include: The lower layer of the first node sends the first mapping information to the upper layer of the first node to help the upper layer determine the first information.

[0080] The term "upper layer" refers to one or more layers above the lower layer, without specific limitations. The lower layer includes at least one of the following: TCP / IP layer, SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer.

[0081] For example, the bottom layer is the MAC layer, and the upper layer is one or more of the TCP / IP, SDAP, PDCP, or RLC layers above the MAC layer.

[0082] In this embodiment of the application, in the scenario where the first mapping information is sent from the lower layer of the first node to the upper layer of the first node, the content of the first mapping information can have multiple forms, including at least one of the following: 1) The granularity of the first information includes LCH, and the first mapping information includes at least one of the following: LCH mapping relationship; Mapping relationship between LCH and DRB; Mapping relationship between LCH and bearer; Mapping relationship between LCH and session; Mapping relationship between LCH and QoS flow.

[0083] 2) The granularity of the first information includes DRB, and the first mapping information includes at least one of the following: Mapping relationship between DRB and LCH; Mapping relationship between DRB and bearer; Mapping relationship between DRB and session; Mapping relationship between DRB and QoS flow.

[0084] 3) The granularity of the first information includes the carrier, and the first mapping information includes at least one of the following: Mapping relationship between the bearer and the LCH; Mapping relationship between bearer and DRB; Mapping relationship between bearer and session; Mapping relationship between bearers and QoS flows.

[0085] 4) The granularity of the first information includes the session, and the first mapping information includes at least one of the following: Session mapping relationships; The mapping relationship between sessions and QoS flows; The mapping relationship between sessions and bearers; The mapping relationship between sessions and DRBs; The mapping relationship between sessions and LCH.

[0086] In this embodiment of the application, the above method may further include: The lower layer of the first node sends the first mapping information to the upper layer of the first node to assist the upper layer in determining the first information. The first mapping information includes at least one of the following: 1) QoS flow mapping relationship; 2) Mapping relationship between QoS flows and sessions; 3) Mapping relationship between QoS flows and bearers; 4) Mapping relationship between QoS flows and DRBs; 5) Mapping relationship between QoS flows and LCH; 6) Session mapping relationship; 7) The mapping relationship between sessions and QoS flows; 8) The mapping relationship between sessions and bearers; 9) The mapping relationship between sessions and DRBs; 10) The mapping relationship between sessions and LCH.

[0087] In this embodiment of the application, the first information may be carried in at least one of the following messages: Non-Access Stratum (NAS) message, Radio Resource Control (RRC) message, Medium Access Control Control Element (MAC CE) message, Downlink Control Information (DCI) message, and Uplink Control Information (UCI) message.

[0088] In this embodiment of the application, the aforementioned RRC message may include at least one of the following: RRC reconfiguration message, connection establishment message, UE Assistance Information (UAI), RRC reconfiguration completion message, and connection establishment completion message.

[0089] For example, the first information can be carried through NAS messages and DCI messages, or through RRC reconfiguration information, or through UAI messages, etc.

[0090] The first node can select the appropriate message to carry the first information based on the application scenario and actual needs, which is very flexible, applicable to a wide range of scenarios, and highly practical.

[0091] The method provided in this application embodiment sends first information to a second node through a first node. The first information includes at least one of the following: congestion information, rate control information, and rate adjustment information. The first information can assist the second node in adjusting or controlling the rate without multiple feedbacks, enabling faster and more accurate rate control, reducing the time consumption of rate control, and improving the efficiency of rate control.

[0092] Figure 3 This diagram illustrates a flow chart of a rate control method provided in an embodiment of this application, which can be executed by a first node. Figure 3 As shown, the method may include the following steps.

[0093] S302: The first node receives a request message or query message sent by the second node.

[0094] In this embodiment of the application, the above-mentioned request message is used to request first information, and the above-mentioned query message is used to query the first information.

[0095] The granularity of the request message or query message may include at least one of the following: terminal, QoS stream, session, bearer, DRB, LCH.

[0096] S304: The first node sends first information to the second node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0097] In the above method, the first node sending the first message to the second node can be triggered by the first node receiving a request message or query message from the second node. That is, receiving a request message or query message from the second node triggers the first node to send the first message to the second node. Of course, the first node can also decide whether to send the first message to the second node. That is, after receiving a request message or query message from the second node, the first node can send the first message to the second node or not, and there is no specific limitation.

[0098] In this embodiment of the application, when the first node is configured with a trigger condition for sending first information, in addition to using the received request message or query message sent by the second node as the trigger condition, other trigger conditions can also be used. Therefore, the first node can send the first information in at least one of the following situations: 1) The first node determines whether the rate needs to be adjusted or controlled; 2) The first node determines that it needs to notify the second node of the first piece of information; 3) The first node receives a request message or an inquiry message sent by the second node. The request message is used to request the first information, and the inquiry message is used to inquire about the first information.

[0099] For example, the first node determines that the rate needs to be adjusted or controlled, and determines that the second node needs to be notified of the first information.

[0100] The above-mentioned triggering conditions allow the first node to send the first message under appropriate circumstances. The first node can choose flexibly, which is easy to implement.

[0101] The method provided in this application embodiment sends first information to a second node through a first node. The first information includes at least one of the following: congestion information, rate control information, and rate adjustment information. The first information can assist the second node in adjusting or controlling the rate without multiple feedbacks, enabling faster and more accurate rate control, reducing the time consumption of rate control, and improving the efficiency of rate control.

[0102] Figure 4 This diagram illustrates a flow chart of a rate control method provided in an embodiment of this application, which can be executed by a second node. Figure 4As shown, the method may include the following steps.

[0103] S402: The second node receives the first information sent by the first node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0104] In this embodiment, congestion information refers to congestion information in the network where the first node and the second node reside. Rate control information and rate adjustment information refer to information related to controlling and adjusting the rate between the first node and the second node, or information related to controlling and adjusting the rate of the first node or the second node, such as the coding rate. This rate can be the rate from the first node to the second node, or it can be the rate from the second node to the first node; the specific direction is not limited.

[0105] In this application embodiment, the rate involved in the first information may include at least one of the following: bit rate, encoding rate, data rate, resource rate, and source rate.

[0106] For example, the first information may include bit rate and encoding rate, or the first information may include encoding rate, data rate and resource rate.

[0107] The rates involved in the first information can be combined in various ways, enabling the second node to adjust or control a variety of different rates.

[0108] In this embodiment, the first node and the second node are different devices, and can be implemented in various ways, including but not limited to one of the following: 1) The first node is a base station, and the second node is a terminal, a core network node, or an application layer node; for example, the first node is a base station and the second node is a terminal; or the first node is a base station and the second node is a core network node; 2) The first node is a terminal, and the second node is a base station, core network node, or application layer node; for example, the first node is a terminal and the second node is a base station; or the first node is a terminal and the second node is an application layer node; 3) The first node is a core network node, and the second node is a base station or terminal; 4) The first node is an application layer node, and the second node is a base station or terminal.

[0109] The aforementioned application layer nodes can be, for example, servers provided by a service provider, or application servers provided by third-party services, etc., and are not specifically limited to any particular type.

[0110] The first and second nodes mentioned above are different devices, which can realize rate control or adjustment in various scenarios by combining multiple devices.

[0111] In this embodiment of the application, the first information may include at least one of the following: 1) Rate adjustment indicator; 2) Rate information; 3) Congestion information; 4) Network load information; 5) Channel information; 6) Quality of Service (QoS) information; 7) Uplink indication; whereby the uplink indication is used to indicate adjustments or control of the uplink rate; 8) Downlink indication; wherein, the downlink indication is used to indicate adjustment or control of the downlink rate; 9) Identification information.

[0112] Based on the information provided in the first part, more information can be provided to the second node, which helps the second node to adjust or control the rate more accurately, thereby improving the precision of rate adjustment or control.

[0113] In this embodiment, the aforementioned rate adjustment instruction may include at least one of the following: increasing rate, increasing rate level, decreasing rate, decreasing rate level, keeping rate unchanged, keeping rate level unchanged, rate adjustment factor, and rate level adjustment factor. The rate adjustment factor (scalling factor) can be used to maintain the existing rate or rate level, or to decrease or increase the existing rate or rate level by a certain factor. For example, a rate adjustment factor less than 1 corresponds to decreasing the rate or rate level; a rate adjustment factor greater than 1 corresponds to increasing the rate or rate level; and a rate adjustment factor equal to 1 keeps the current rate or rate level unchanged.

[0114] And / or, In this embodiment, the aforementioned rate information may include at least one of the following: rate, rate level, and rate range. This method of providing rate information within the first information provides more refined rate information to the second node, helping the second node to adjust or control the rate more precisely, thereby improving the accuracy of rate adjustment or control.

[0115] And / or, In this embodiment of the application, the congestion information may include at least one of the following: whether there is congestion, congestion level, congestion cause, congestion channel, congestion scenario, congestion-related service, congestion-related session, congestion-related quality of service flow, congestion-related data radio bearer (DRB), congestion-related logical channel (LCH), and congestion-related channel.

[0116] And / or, In this embodiment of the application, the aforementioned network load information may include at least one of the following: load level, whether overloaded, whether lightly loaded, whether heavily loaded, load cause, load association cause, load association scenario, load association service, load association session, load association QoS flow, load association DRB, load association LCH, and load association channel. The load level may be classified as light, medium, heavy, or other levels.

[0117] And / or, In this embodiment of the application, the aforementioned channel information may include at least one of the following: channel measurement results, channel measurement level, channel status, and channel condition. The channel status may include good, average, or poor conditions.

[0118] And / or, In this embodiment of the application, the QoS information may include at least one of the following: QoS parameters, QoS requirements, QoS allocation, and QoS mapping information.

[0119] And / or, In this embodiment of the application, the aforementioned identification information may include at least one of the following: UE ID, QoS flow ID, session ID, bearer ID, DRB ID, and LCH ID. The UE ID may be, for example, the UE ID or the Cell Radio Network Temporary Identifier (C-RNTI).

[0120] In this application embodiment, the granularity of the first information may include at least one of the following: terminal (per-UE), QoS flow (per-QoS flow), session (per-Session), bearer (per-bearer), DRB (per-DRB), LCH (per-LCH).

[0121] In the case where the granularity of the first information is per-UE, the first information may include at least one of the following: UE rate adjustment indication, UE rate information, UE congestion information, UE network load information, UE channel information, UE uplink indication, UE downlink indication, and UE ID. In this scenario, the first information can reflect the current overall status of the UE, thereby enabling rate adjustment or rate control for all services of the UE.

[0122] In the case where the granularity of the first information is per-QoS flow, the first information may include at least one of the following: rate adjustment indication for each QoS flow, rate information for each QoS flow, congestion information for each QoS flow, network load information for each QoS flow, channel information for each QoS flow, uplink indication for each QoS flow, downlink indication for each QoS flow, and ID for each QoS flow. In this scenario, the first information can reflect the current status of the QoS flow of the first node, thereby enabling precise rate adjustment or rate control of the data flow corresponding to one or more QoS flows of the first node.

[0123] In the case where the granularity of the first information is per-session, the first information may include at least one of the following: rate adjustment indication for each session, rate information for each session, congestion information for each session, network load information for each session, channel information for each session, uplink indication for each session, downlink indication for each session, and ID for each session. In this scenario, the first information can reflect the current status of the first node's session, thereby enabling precise rate adjustment or rate control of the data streams corresponding to one or more sessions.

[0124] In the case where the granularity of the first information is per-bearer, the first information may include at least one of the following: rate adjustment indication for each bearer, rate information for each bearer, congestion information for each bearer, network load information for each bearer, channel information for each bearer, uplink indication for each bearer, downlink indication for each bearer, and ID for each bearer. In this scenario, the first information can reflect the current status of the first node's bearers, thereby enabling precise rate adjustment or rate control for one or more bearers. Furthermore, since the mapping relationship of bearers can be obtained based on the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0125] In the case where the granularity of the first information is per-DRB, the first information may include at least one of the following: rate adjustment indication for each DRB, rate information for each DRB, congestion information for each DRB, network load information for each DRB, channel information for each DRB, uplink indication for each DRB, downlink indication for each DRB, and ID of each DRB. In this scenario, the first information can reflect the current status of the DRBs of the first node, thereby enabling precise rate adjustment or rate control for the rates corresponding to one or more DRBs. Furthermore, since the mapping relationship of DRBs can be obtained from the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0126] In the case where the granularity of the first information is per-LCH, the first information may include at least one of the following: rate adjustment indication for each LCH, rate information for each LCH, congestion information for each LCH, network load information for each LCH, channel information for each LCH, uplink indication for each LCH, downlink indication for each LCH, and ID for each LCH. In this scenario, the first information can reflect the current status of the LCH of the first node, thereby enabling precise rate adjustment or rate control for one or more LCHs. Furthermore, since the mapping relationship of LCHs can be obtained from the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0127] In this embodiment of the application, the above method may include at least one of the following methods: 1) The granularity of the first information includes the terminal, and the first information includes the terminal identifier.

[0128] 2) The granularity of the first information includes QoS flow, the first information includes QoS flow identifier, or the first information includes QoS flow identifier and at least one of the following: terminal identifier, session identifier, bearer identifier, DRB identifier, LCH identifier.

[0129] 3) The granularity of the first information includes the session, the first information includes the session identifier, or the first information includes the session identifier and at least one of the following: terminal identifier, QoS flow identifier, bearer identifier, DRB identifier, LCH identifier.

[0130] 4) The granularity of the first information includes the bearer, the first information includes the bearer identifier, or the first information includes the bearer identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, DRB identifier, LCH identifier.

[0131] 5) The granularity of the first information includes DRB, the first information includes DRB identifier, or the first information includes DRB identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, LCH identifier.

[0132] 6) The granularity of the first information includes LCH, the first information includes LCH identifier, or the first information includes LCH identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, DRB identifier.

[0133] In one implementation, the step S402 above may further include: The second node adjusts or controls the rate based on the first information.

[0134] In another implementation, the step S402 described above may further include: The second node adjusts or controls the rate in at least one of the following ways: 1) After receiving the first message and after a preset time period, the second node begins to adjust or control the rate; the preset time period can be determined by the protocol, network configuration, or terminal, and the value can be 0 or non-zero, with no specific limitation. This method determines the start time of rate adjustment or control.

[0135] 2) The second node adjusts or controls the rate within a preset time period; the preset time period can be determined by protocol agreement, network configuration, or terminal, and the specific value is not limited. This method determines the duration of rate adjustment or control; for example, a time window can be set as the preset time period.

[0136] 3) The second node adjusts or controls the rate starting from a preset data unit; where the preset data unit includes the current data unit or the Nth data unit after the current data unit, where N is a positive integer; for example, N is 1, 3, or 6, etc. This method determines the starting position of the data unit for rate adjustment or control.

[0137] 4) The second node adjusts or controls the rate of a preset number of data units; where the preset number can be one or more. For example, the rate can be adjusted or controlled for 2 or 5 data units. This method determines the length of the data units for rate adjustment or control.

[0138] In this application embodiment, the above data unit may include at least one of the following: session, quality of service stream, burst packet, frame, protocol data unit (PDU), PDU set, dataset, service data unit (SDU).

[0139] In this embodiment of the application, the above method may further include: The lower layer of the second node sends the second mapping information to the upper layer of the second node to assist the upper layer in adjusting or controlling the rate.

[0140] The term "upper layer" refers to one or more layers above the lower layer, without specific limitations. The lower layer includes at least one of the following: TCP / IP layer, SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer.

[0141] For example, the bottom layer is the MAC layer, and the upper layer is one or more of the TCP / IP, SDAP, PDCP, or RLC layers above the MAC layer.

[0142] In this embodiment of the application, in the scenario where the second mapping information is sent from the lower layer of the second node to the upper layer of the second node, the content of the second mapping information can have multiple forms, including at least one of the following: 1) The granularity of the first information includes LCH, and the second mapping information includes at least one of the following: LCH mapping relationship; in this scenario, the underlying layer includes either the MAC layer or the PHY layer; The mapping relationship between LCH and DRB; in this scenario, the underlying layer includes either the MAC layer or the PDCP layer; The mapping relationship between LCH and bearer; in this scenario, the underlying layer includes either the MAC layer or the RLC layer; The mapping relationship between LCH and session; in this scenario, the underlying layers include the PHY layer, MAC layer, or TCP / IP layer; The mapping relationship between LCH and QoS flow; in this scenario, the underlying layer includes either the MAC layer or the SDAP layer.

[0143] 2) The granularity of the first information includes DRB, and the second mapping information includes at least one of the following: The mapping relationship between DRB and LCH; in this scenario, the underlying layer includes either the MAC layer or the PDCP layer; The mapping relationship between DRB and bearer; in this scenario, the underlying layer includes either PDCP layer or RLC layer; The mapping relationship between DRB and session; in this scenario, the underlying layer includes either the PDCP layer or the TCP / IP layer; The mapping relationship between DRB and QoS flow; in this scenario, the underlying layer includes either PDCP layer or SDAP layer.

[0144] 3) The granularity of the first information includes the carrier, and the second mapping information includes at least one of the following: The mapping relationship between the bearer and the LCH; in this scenario, the underlying layer includes either the MAC layer or the RLC layer; The mapping relationship between the bearer and the DRB; in this scenario, the underlying layer includes either the PDCP layer or the RLC layer; The mapping relationship between the bearer and the session; in this scenario, the underlying layers include RLC and TCP / IP layers; The mapping relationship between the bearer and the QoS flow; in this scenario, the underlying layer includes the RLC layer or the SDAP layer.

[0145] 4) The granularity of the first information includes the session, and the second mapping information includes at least one of the following: Session mapping relationship; in this scenario, the underlying layer includes either the TCP / IP layer or the SDAP layer; The mapping relationship between sessions and QoS flows; in this scenario, the underlying layers include the TCP / IP layer or the SDAP layer; The mapping relationship between sessions and bearers; in this scenario, the underlying layers include RLC and TCP / IP layers; The mapping relationship between sessions and DRBs; in this scenario, the underlying layers include the PDCP layer or the TCP / IP layer; The mapping relationship between sessions and LCH; in this scenario, the underlying layers include the PHY layer, MAC layer, or TCP / IP layer.

[0146] In this embodiment of the application, the above method may further include: The lower layer of the second node sends the second mapping information to the upper layer of the second node to assist the upper layer in adjusting or controlling the rate; wherein, the second mapping information includes at least one of the following: 1) QoS flow mapping relationship; 2) Mapping relationship between QoS flows and sessions; 3) Mapping relationship between QoS flows and bearers; 4) Mapping relationship between QoS flows and DRBs; 5) Mapping relationship between QoS flows and LCH; 6) Session mapping relationship; 7) The mapping relationship between sessions and QoS flows; 8) The mapping relationship between sessions and bearers; 9) The mapping relationship between sessions and DRBs; 10) The mapping relationship between sessions and LCH.

[0147] Both of the above methods involve the lower layer of the second node sending the second mapping information to the upper layer of the second node, whereby the upper layer adjusts or controls the rate. This method solves the problem that the upper layer cannot know the mapping relationship of the lower layer. Alternatively, in this embodiment, the upper layer of the second node can send the second mapping information to the lower layer of the second node, whereby the lower layer adjusts or controls the rate. This method also solves the problem that the lower layer cannot know the mapping relationship of the upper layer. Regardless of the method, the second node can perform rate adjustment or control.

[0148] In this embodiment of the application, the above method may further include: The upper layer of the second node sends the second mapping information to the lower layer of the second node to assist the lower layer in adjusting or controlling the rate.

[0149] The term "bottom layer" refers to one or more layers below the "upper layer," without specific limitations. The "upper layer" includes at least one of the following: application layer, TCP / IP layer, SDAP layer, PDCP layer, RLC layer, and MAC layer.

[0150] For example, the upper layer is the SDAP layer, and the lower layer is one or more of the PDCP layer, RLC layer, MAC layer, and PHY layer below the SDAP layer.

[0151] In this embodiment of the application, in the scenario where the upper layer of the second node sends the second mapping information to the lower layer of the second node, the content of the second mapping information can have multiple forms, including at least one of the following: 1) If the granularity of the first information includes QoS flows, the second mapping information includes at least one of the following: QoS flow mapping relationship; Mapping relationship between QoS flows and sessions; Mapping relationship between QoS flows and bearers; Mapping relationship between QoS flows and DRBs; Mapping relationship between QoS flows and LCH.

[0152] 2) If the granularity of the first information includes a session, the second mapping information includes at least one of the following: Session mapping relationships; The mapping relationship between sessions and QoS flows; The mapping relationship between sessions and bearers; The mapping relationship between sessions and DRBs; The mapping relationship between sessions and LCH.

[0153] 3) If the granularity of the first information includes the bearer, the second mapping information includes at least one of the following: Mapping relationship between bearers and QoS flows; Mapping relationship between bearer and session; Mapping relationship between bearer and DRB; Mapping relationship between the bearer and LCH.

[0154] In this embodiment of the application, the above method may further include: The upper layer of the second node sends the second mapping information to the lower layer of the second node to assist the lower layer in adjusting or controlling the rate. The second mapping information includes at least one of the following: 1) Mapping relationship between LCH and DRB; 2) Mapping relationship between LCH and bearer; 3) The mapping relationship between LCH and session; 4) Mapping relationship between LCH and QoS flows; 5) Mapping relationship between DRB and bearer; 6) The mapping relationship between DRB and session; 7) Mapping relationship between DRB and QoS flow; 8) The mapping relationship between the bearer and the session; 9) Mapping relationship between bearer and QoS flow.

[0155] The method provided in this application embodiment receives first information sent by a first node through a second node. The first information includes at least one of the following: congestion information, rate control information, and rate adjustment information. The first information can assist the second node in adjusting or controlling the rate without multiple feedbacks, enabling faster and more accurate rate control, reducing the time consumption of rate control, and improving the efficiency of rate control.

[0156] Figure 5 This diagram illustrates a flow chart of a rate control method provided in an embodiment of this application, which can be executed by a second node. Figure 5 As shown, the method may include the following steps.

[0157] S502: The second node sends a request message or a query message to the first node, wherein the request message is used to request first information, and the query message is used to query first information.

[0158] In this application embodiment, the granularity of the request message or query message may include at least one of the following: terminal, QoS stream, session, bearer, DRB, LCH.

[0159] In this embodiment of the application, the above-mentioned request message or query message can be sent at a preset time or after the prohibition timer has ended.

[0160] In this embodiment of the application, the prohibited period is used to control whether or not request messages or query messages can be sent, and to control when request messages or query messages are sent.

[0161] The prohibited period can include a start time and duration; the time range corresponding to the duration is the prohibited period. The handling mechanism for prohibited periods includes at least one of the following: 1) At the start time of the prohibition period (i.e., the start time of the prohibition timer), the second node can send a request message or a query message to the first node; for example, if the prohibition period is t1~t2, at time t1, the second node can send a request message or a query message to the first node. 2) During the prohibited period (i.e., during the operation of the prohibit timer), the second node is prohibited from sending request messages or query messages to the first node; for example, if the prohibited period is t1~t2, the second node is prohibited from sending request messages or query messages to the first node at any time between t1 and t2. 3) After the prohibition period ends (i.e., the prohibition timer ends), the second node can send a request message or a query message to the first node; for example, if the prohibition period is t1~t2, after time t2, the second node can send a request message or a query message to the first node.

[0162] The above processing mechanism can control when the second node sends request messages or query messages to the first node, thus avoiding the second node frequently sending request messages or query messages to the first node and saving network overhead.

[0163] In one implementation, the granularity of the prohibited period may include at least one of the following: terminal, QoS flow, session, bearer, DRB, LCH.

[0164] And / or, In another implementation, the prohibited period may include prohibited periods for uplink and downlink, or the prohibited period may include: prohibited periods for request messages or query messages corresponding to uplink rate adjustment or control, and prohibited periods for request messages or query messages corresponding to downlink rate adjustment or control.

[0165] The prohibited time period can be set to be shared by uplink and downlink, or it can be set to be exclusive to uplink and downlink respectively. The method is flexible and can be adapted to different needs.

[0166] In cases where the granularity of the prohibited period is per-UE, the UE (i.e., the second node) executes according to at least one of the following mechanisms: 1) At the start of the prohibited period, the UE may send a request message or a query message to the first node; 2) During the prohibited period, the UE is prohibited from sending request messages or query messages to the first node; 3) After the prohibited period ends, the UE can send a request message or an inquiry message to the first node.

[0167] Specifically, when the granularity of the prohibited period is per-session, per-QoS flow, per-DRB, per-bearer, or per-LCH, the second node executes according to at least one of the following mechanisms: 1) At the start time of the prohibited period corresponding to a certain session, QoS flow, DRB, bearer, or LCH, the second node can send a request or query message for the corresponding session, QoS flow, DRB, bearer, or LCH to the first node.

[0168] For example, at the start time of the prohibited period corresponding to a certain session, the second node can send a request or query message for that session to the first node; 2) During the prohibited period corresponding to a certain session, QoS flow, DRB, bearer, or LCH, the second node is prohibited from sending the corresponding session, QoS flow, DRB, bearer, or LCH request or query message to the first node.

[0169] For example, during the prohibited period corresponding to a certain LCH, the second node is prohibited from sending the request or query message for that LCH to the first node; In this scenario, the terminal can initiate requests or queries for other sessions, QoS flows, DRB, bearer, or LCH if the prohibited period corresponding to the requests or queries for other sessions, QoS flows, DRB, bearer, or LCH is not running.

[0170] 3) After the prohibited period for a certain session, QoS flow, DRB, bearer, or LCH ends, the second node can send a request or query message to the first node for the corresponding session, QoS flow, DRB, bearer, or LCH again.

[0171] For example, after the prohibited period for a certain DRB ends, the second node can send another request or query message for that DRB to the first node.

[0172] By setting different granularities for prohibited time periods, it is possible to precisely control the timing of the second node sending request or query messages to the first node at different granularities. This not only avoids the second node frequently sending request or query messages to the first node, thus saving network overhead, but also achieves precise control and improves control accuracy.

[0173] S504: The second node receives the first information sent by the first node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0174] The method provided in this application embodiment receives first information sent by a first node through a second node. The first information includes at least one of the following: congestion information, rate control information, and rate adjustment information. The first information can assist the second node in adjusting or controlling the rate without multiple feedbacks, enabling faster and more accurate rate control, reducing the time consumption of rate control, and improving the efficiency of rate control.

[0175] The format of the first information in the above embodiments is explained in detail below.

[0176] The first node can send the first message to the second node via MAC CE message.

[0177] The first piece of information in a MAC CE message can occupy one or more bits, and its length is not limited.

[0178] For example, the first information includes rate information and identification information, and the specific format is shown in Table 1 below.

[0179] Table 1

[0180] The MAC CE message includes a DRB ID or QoS flow ID, and the corresponding rate information. It also includes uplink UL and / or downlink DL indications. In the table, the rate information occupies 1 bit in Oct2 and 5 bits in Oct2, while the DRB ID or QoS flow ID occupies 6 bits. This is one implementation method; other bit lengths can be used, and there are no specific limitations.

[0181] The above method can provide accurate rate control or adjustment because the application layer or application server of the terminal does not know the specific LCID mapping, but knows the specific QoS flow or DRB mapping. Therefore, for latency-sensitive services, in order to respond quickly to network conditions such as congestion, the rate can be directly and accurately adjusted or controlled according to different DRBs or QoS flows, thereby avoiding the problems of inaccurate and untimely rate adjustment or control caused by LCID.

[0182] The implementation process of the above embodiments is further illustrated below using specific scenarios as examples.

[0183] In the first scenario, the UL rate needs to be adjusted or controlled. The first node gNB sends the first information to the second node UE, and the UE determines the rate adjustment or control based on the first information.

[0184] The UE determining rate adjustment or control based on the first information may include at least one of the following steps: 1) The UE AS access layer determines the rate to be adjusted or controlled based on the first information, and then notifies the UE application layer; 2) The UE sends the received first information to the application layer, which then determines the rate to be adjusted or controlled. In the first scenario mentioned above, the UE application layer adjusts or controls the rate based on the first information. This can be done directly based on the first information provided by the RAN-side gNB, without needing to go through the gNB, the core network, and then to the application server to instruct the terminal to adjust the uplink rate. This can greatly shorten the delay of control or adjustment, and is particularly suitable for time-sensitive services, such as those with high real-time requirements.

[0185] In the second scenario, the DL rate needs to be adjusted or controlled. The first node gNB sends the first information to the second node UE, and the UE can perform at least one of the following steps: 1) The UE AS access layer determines the rate to be adjusted or controlled based on the first information, and then notifies the UE application layer. The UE application layer negotiates with the application server to adjust or control the DL rate. 2) The UE sends the received first information to the application layer. The UE application layer determines the rate to be adjusted or controlled based on the first information, and then notifies the application server. 3) The UE sends the received first information to the application layer, the UE application layer notifies the application server of the first information, and then the application server determines the rate to be adjusted or controlled based on the first information. 4) The UE sends the received first information to the application layer. The UE application layer notifies the application server of the first information. Then, the application server and the UE negotiate to determine the rate to be adjusted or controlled based on the first information.

[0186] In the third scenario, the first node UE sends the first information to the second node gNB. The gNB can send the first information to the application server through the CN. The application server then determines the rate to be adjusted or controlled based on the first information.

[0187] In the second and third scenarios mentioned above, since the terminal understands both the service requirements and the current network environment (including channel conditions or congestion), the DL rate can be determined more accurately through negotiation between the terminal application layer and the application server. This is particularly suitable for latency-sensitive services and can shorten the delay of control or adjustment.

[0188] Figure 6 This illustration shows a structural schematic diagram of a rate control device provided in an embodiment of this application, such as... Figure 6 As shown, the device 600 is applied to the first node and may include a sending module 601.

[0189] The sending module 601 is used to send first information to the second node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0190] In this embodiment of the application, the first information is used to assist the second node in adjusting or controlling the rate, or the first information is used by the second node to adjust or control the rate based on the first information.

[0191] In this embodiment of the application, the first information includes at least one of the following: 1) Rate adjustment indicator; 2) Rate information; 3) Congestion information; 4) Network load information; 5) Channel information; 6) QoS information; 7) Upward indication; 8) Downward indication; 9) Identification information.

[0192] In this embodiment of the application, the above-mentioned device may include at least one of the following: 1) The rate adjustment indication includes at least one of the following: increase rate, rate increase level, decrease rate, rate decrease level, rate unchanged, rate level unchanged, rate adjustment factor, rate level adjustment factor.

[0193] 2) Rate information includes at least one of the following: rate, rate class, and rate range.

[0194] 3) Congestion information includes at least one of the following: whether there is congestion, congestion level, congestion cause, congestion channel, congestion scenario, congestion-related services, congestion-related sessions, congestion-related QoS flow, congestion-related Data Radio Bearer (DRB), congestion-related Logical Channel (LCH), and congestion-related channel.

[0195] 4) Network load information includes at least one of the following: load level, whether overloaded, whether lightly loaded, whether heavily loaded, load cause, load association cause, load association scenario, load association service, load association session, load association QoS flow, load association DRB, load association LCH, and load association channel.

[0196] 5) Channel information includes at least one of the following: channel measurement results, channel measurement level, channel status, and channel conditions.

[0197] 6) QoS information includes at least one of the following: QoS parameters, QoS requirements, QoS allocation, and QoS mapping information.

[0198] 7) The identification information includes at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, DRB identifier, and LCH identifier.

[0199] In this application embodiment, the granularity of the first information includes at least one of the following: terminal, QoS flow, session, bearer, DRB, LCH.

[0200] In the case where the granularity of the first information is per-UE, the first information may include at least one of the following: UE rate adjustment indication, UE rate information, UE congestion information, UE network load information, UE channel information, UE uplink indication, UE downlink indication, and UE ID. In this scenario, the first information can reflect the current overall status of the UE, thereby enabling rate adjustment or rate control for all services of the UE.

[0201] In the case where the granularity of the first information is per-QoS flow, the first information may include at least one of the following: rate adjustment indication for each QoS flow, rate information for each QoS flow, congestion information for each QoS flow, network load information for each QoS flow, channel information for each QoS flow, uplink indication for each QoS flow, downlink indication for each QoS flow, and ID for each QoS flow. In this scenario, the first information can reflect the current status of the QoS flow of the first node, thereby enabling precise rate adjustment or rate control of the data flow corresponding to one or more QoS flows of the first node.

[0202] In the case where the granularity of the first information is per-session, the first information may include at least one of the following: rate adjustment indication for each session, rate information for each session, congestion information for each session, network load information for each session, channel information for each session, uplink indication for each session, downlink indication for each session, and ID for each session. In this scenario, the first information can reflect the current status of the first node's session, thereby enabling precise rate adjustment or rate control of the data streams corresponding to one or more sessions.

[0203] In the case where the granularity of the first information is per-bearer, the first information may include at least one of the following: rate adjustment indication for each bearer, rate information for each bearer, congestion information for each bearer, network load information for each bearer, channel information for each bearer, uplink indication for each bearer, downlink indication for each bearer, and ID for each bearer. In this scenario, the first information can reflect the current status of the first node's bearers, thereby enabling precise rate adjustment or rate control for one or more bearers. Furthermore, since the mapping relationship of bearers can be obtained based on the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0204] In the case where the granularity of the first information is per-DRB, the first information may include at least one of the following: rate adjustment indication for each DRB, rate information for each DRB, congestion information for each DRB, network load information for each DRB, channel information for each DRB, uplink indication for each DRB, downlink indication for each DRB, and ID of each DRB. In this scenario, the first information can reflect the current status of the DRBs of the first node, thereby enabling precise rate adjustment or rate control for the rates corresponding to one or more DRBs. Furthermore, since the mapping relationship of DRBs can be obtained from the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0205] In the case where the granularity of the first information is per-LCH, the first information may include at least one of the following: rate adjustment indication for each LCH, rate information for each LCH, congestion information for each LCH, network load information for each LCH, channel information for each LCH, uplink indication for each LCH, downlink indication for each LCH, and ID for each LCH. In this scenario, the first information can reflect the current status of the LCH of the first node, thereby enabling precise rate adjustment or rate control for one or more LCHs. Furthermore, since the mapping relationship of LCHs can be obtained from the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0206] In this embodiment of the application, the above-mentioned device may include at least one of the following: 1) The granularity of the first information includes the terminal, and the first information includes the terminal identifier.

[0207] 2) The granularity of the first information includes QoS flow, the first information includes QoS flow identifier, or the first information includes QoS flow identifier and at least one of the following: terminal identifier, session identifier, bearer identifier, DRB identifier, LCH identifier.

[0208] 3) The granularity of the first information includes the session, the first information includes the session identifier, or the first information includes the session identifier and at least one of the following: terminal identifier, QoS flow identifier, bearer identifier, DRB identifier, LCH identifier.

[0209] 4) The granularity of the first information includes the bearer, the first information includes the bearer identifier, or the first information includes the bearer identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, DRB identifier, LCH identifier.

[0210] 5) The granularity of the first information includes DRB, the first information includes DRB identifier, or the first information includes DRB identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, LCH identifier.

[0211] 6) The granularity of the first information includes LCH, the first information includes LCH identifier, or the first information includes LCH identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, DRB identifier.

[0212] In this embodiment of the application, when the first information does not carry identification information, the object indicated or to which the first information is applicable may include at least one of the following: 1) The granularity of the first information includes the terminal, and the first information indicates or applies to all QoS flows, all sessions, all bearers, all DRBs, or all LCHs.

[0213] 2) The granularity of the first information includes QoS flows, and the first information indicates or applies to all QoS flows.

[0214] 3) The granularity of the first message includes the session, and the first message indicates or applies to all sessions.

[0215] 4) The granularity of the first information includes the carrier, and the first information indicates or applies to all carriers.

[0216] 5) The granularity of the first information includes DRBs, and the first information indicates or applies to all DRBs.

[0217] 6) The granularity of the first information includes LCH, and the first information indicates or applies to all LCH.

[0218] In this application embodiment, the rate involved in the first information includes at least one of the following: bit rate, encoding rate, data rate, resource rate, and source rate.

[0219] In this embodiment of the application, the sending module 601 sends the first information under at least one of the following circumstances: 1) The first node determines whether the rate needs to be adjusted or controlled; 2) The first node determines that it needs to notify the second node of the first piece of information; 3) The first node receives a request message or an inquiry message sent by the second node. The request message is used to request the first information, and the inquiry message is used to inquire about the first information.

[0220] In this embodiment of the application, the above-mentioned device is further used for: Before sending the first message to the second node, receive the request message or query message sent by the second node.

[0221] Among them, the request message is used to request the first information, and the query message is used to query the first information.

[0222] The granularity of the aforementioned request or query messages includes at least one of the following: terminal, QoS stream, session, bearer, DRB, LCH.

[0223] In this embodiment of the application, the above-mentioned device is further used for: The upper layer sends the first mapping information to the lower layer to assist the lower layer in determining the first information. The first mapping information includes at least one of the following: 1) The granularity of the first information includes QoS flows, and the first mapping information includes at least one of the following: QoS flow mapping relationship; Mapping relationship between QoS flows and sessions; Mapping relationship between QoS flows and bearers; Mapping relationship between QoS flows and DRBs; Mapping relationship between QoS flows and LCH.

[0224] 2) The granularity of the first information includes the session, and the first mapping information includes at least one of the following: Session mapping relationships; The mapping relationship between sessions and QoS flows; The mapping relationship between sessions and bearers; The mapping relationship between sessions and DRBs; The mapping relationship between sessions and LCH.

[0225] 3) The granularity of the first information includes the carrier, and the first mapping information includes at least one of the following: Mapping relationship between bearers and QoS flows; Mapping relationship between bearer and session; Mapping relationship between bearer and DRB; Mapping relationship between the bearer and LCH.

[0226] In this embodiment of the application, the above-mentioned device is further used for: The upper layer sends the first mapping information to the lower layer to assist the lower layer in determining the first information. The first mapping information includes at least one of the following: 1) Mapping relationship between LCH and DRB; 2) Mapping relationship between LCH and bearer; 3) The mapping relationship between LCH and session; 4) Mapping relationship between LCH and QoS flows; 5) Mapping relationship between DRB and bearer; 6) The mapping relationship between DRB and session; 7) Mapping relationship between DRB and QoS flow; 8) The mapping relationship between the bearer and the session; 9) Mapping relationship between bearer and QoS flow.

[0227] In this embodiment of the application, the above-mentioned device is further used for: The lower layer sends the first mapping information to the upper layer to assist the upper layer in determining the first information. The first mapping information includes at least one of the following: 1) The granularity of the first information includes LCH, and the first mapping information includes at least one of the following: LCH mapping relationship; Mapping relationship between LCH and DRB; Mapping relationship between LCH and bearer; Mapping relationship between LCH and session; Mapping relationship between LCH and QoS flow.

[0228] 2) The granularity of the first information includes DRB, and the first mapping information includes at least one of the following: Mapping relationship between DRB and LCH; Mapping relationship between DRB and bearer; Mapping relationship between DRB and session; Mapping relationship between DRB and QoS flow.

[0229] 3) The granularity of the first information includes the carrier, and the first mapping information includes at least one of the following: Mapping relationship between the bearer and the LCH; Mapping relationship between bearer and DRB; Mapping relationship between bearer and session; Mapping relationship between bearers and QoS flows.

[0230] 4) The granularity of the first information includes the session, and the first mapping information includes at least one of the following: Session mapping relationships; The mapping relationship between sessions and QoS flows; The mapping relationship between sessions and bearers; The mapping relationship between sessions and DRBs; The mapping relationship between sessions and LCH.

[0231] In this embodiment of the application, the above-mentioned device is further used for: The lower layer sends the first mapping information to the upper layer to assist the upper layer in determining the first information. The first mapping information includes at least one of the following: 1) QoS flow mapping relationship; 2) Mapping relationship between QoS flows and sessions; 3) Mapping relationship between QoS flows and bearers; 4) Mapping relationship between QoS flows and DRBs; 5) Mapping relationship between QoS flows and LCH; 6) Session mapping relationship; 7) The mapping relationship between sessions and QoS flows; 8) The mapping relationship between sessions and bearers; 9) The mapping relationship between sessions and DRBs; 10) The mapping relationship between sessions and LCH.

[0232] In this embodiment of the application, the first information is carried in at least one of the following messages: Non-Access Stratum (NAS) message, Radio Resource Control (RRC) message, Media Access Control (MAC) Control Element (CE) message, Downlink Control Information (DCI) message, and Uplink Control Information (UCI) message.

[0233] In this embodiment of the application, the RRC message includes at least one of the following: RRC reconfiguration message, connection establishment message, terminal assistance information (UAI), RRC reconfiguration complete message, and connection establishment complete message.

[0234] In this embodiment, the first node and the second node are different devices, and there can be various scenarios, including but not limited to the following: 1) The first node is a base station, and the second node is a terminal, core network node, or application layer node; or, 2) The first node is a terminal, and the second node is a base station, core network node, or application layer node; or, 3) The first node is a core network node, and the second node is a base station or terminal; or, 4) The first node is an application layer node, and the second node is a base station or terminal.

[0235] The apparatus provided in this application embodiment can execute the method in any of the method embodiments with the first node as the execution subject. For details, please refer to the description in the method embodiments, which will not be repeated here.

[0236] The apparatus provided in this application embodiment sends first information to a second node through a first node. The first information includes at least one of the following: congestion information, rate control information, and rate adjustment information. The first information can assist the second node in adjusting or controlling the rate without multiple feedbacks, enabling faster and more accurate rate control, reducing the time consumption of rate control, and improving the efficiency of rate control.

[0237] Figure 7 This illustration shows a structural schematic diagram of a rate control device provided in an embodiment of this application, such as... Figure 7 As shown, the device 700 is applied to the second node and may include a receiving module 701.

[0238] The receiving module 701 is used to receive first information sent by the first node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0239] In this embodiment of the application, the first information includes at least one of the following: 1) Rate adjustment indicator; 2) Rate information; 3) Congestion information; 4) Network load information; 5) Channel information; 6) QoS information; 7) Upward indication; 8) Downward indication; 9) Identification information.

[0240] In this embodiment of the application, the above-mentioned device may include at least one of the following: 1) The rate adjustment indication includes at least one of the following: increase rate, rate increase level, decrease rate, rate decrease level, rate unchanged, rate level unchanged, rate adjustment factor, rate level adjustment factor.

[0241] 2) Rate information includes at least one of the following: rate, rate class, and rate range.

[0242] 3) Congestion information includes at least one of the following: whether there is congestion, congestion level, congestion cause, congestion channel, congestion scenario, congestion-related services, congestion-related sessions, congestion-related QoS flow, congestion-related Data Radio Bearer (DRB), congestion-related Logical Channel (LCH), and congestion-related channel.

[0243] 4) Network load information includes at least one of the following: load level, whether overloaded, whether lightly loaded, whether heavily loaded, load cause, load association cause, load association scenario, load association service, load association session, load association QoS flow, load association DRB, load association LCH, and load association channel.

[0244] 5) Channel information includes at least one of the following: channel measurement results, channel measurement level, channel status, and channel conditions.

[0245] 6) QoS information includes at least one of the following: QoS parameters, QoS requirements, QoS allocation, and QoS mapping information.

[0246] 7) The identification information includes at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, DRB identifier, and LCH identifier.

[0247] In this application embodiment, the granularity of the first information includes at least one of the following: terminal, QoS flow, session, bearer, DRB, LCH.

[0248] In the case where the granularity of the first information is per-UE, the first information may include at least one of the following: UE rate adjustment indication, UE rate information, UE congestion information, UE network load information, UE channel information, UE uplink indication, UE downlink indication, and UE ID. In this scenario, the first information can reflect the current overall status of the UE, thereby enabling rate adjustment or rate control for all services of the UE.

[0249] In the case where the granularity of the first information is per-QoS flow, the first information may include at least one of the following: rate adjustment indication for each QoS flow, rate information for each QoS flow, congestion information for each QoS flow, network load information for each QoS flow, channel information for each QoS flow, uplink indication for each QoS flow, downlink indication for each QoS flow, and ID for each QoS flow. In this scenario, the first information can reflect the current status of the QoS flow of the first node, thereby enabling precise rate adjustment or rate control of the data flow corresponding to one or more QoS flows of the first node.

[0250] In the case where the granularity of the first information is per-session, the first information may include at least one of the following: rate adjustment indication for each session, rate information for each session, congestion information for each session, network load information for each session, channel information for each session, uplink indication for each session, downlink indication for each session, and ID for each session. In this scenario, the first information can reflect the current status of the first node's session, thereby enabling precise rate adjustment or rate control of the data streams corresponding to one or more sessions.

[0251] In the case where the granularity of the first information is per-bearer, the first information may include at least one of the following: rate adjustment indication for each bearer, rate information for each bearer, congestion information for each bearer, network load information for each bearer, channel information for each bearer, uplink indication for each bearer, downlink indication for each bearer, and ID for each bearer. In this scenario, the first information can reflect the current status of the first node's bearers, thereby enabling precise rate adjustment or rate control for one or more bearers. Furthermore, since the mapping relationship of bearers can be obtained based on the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0252] In the case where the granularity of the first information is per-DRB, the first information may include at least one of the following: rate adjustment indication for each DRB, rate information for each DRB, congestion information for each DRB, network load information for each DRB, channel information for each DRB, uplink indication for each DRB, downlink indication for each DRB, and ID of each DRB. In this scenario, the first information can reflect the current status of the DRBs of the first node, thereby enabling precise rate adjustment or rate control for the rates corresponding to one or more DRBs. Furthermore, since the mapping relationship of DRBs can be obtained from the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0253] In the case where the granularity of the first information is per-LCH, the first information may include at least one of the following: rate adjustment indication for each LCH, rate information for each LCH, congestion information for each LCH, network load information for each LCH, channel information for each LCH, uplink indication for each LCH, downlink indication for each LCH, and ID for each LCH. In this scenario, the first information can reflect the current status of the LCH of the first node, thereby enabling precise rate adjustment or rate control for one or more LCHs. Furthermore, since the mapping relationship of LCHs can be obtained from the MAC layer, the first information can also be indicated through the MAC layer, eliminating the need for complex inter-layer interactions and improving processing efficiency.

[0254] In this embodiment of the application, the above-mentioned device may include at least one of the following: 1) The granularity of the first information includes the terminal, and the first information includes the terminal identifier.

[0255] 2) The granularity of the first information includes QoS flow, the first information includes QoS flow identifier, or the first information includes QoS flow identifier and at least one of the following: terminal identifier, session identifier, bearer identifier, DRB identifier, LCH identifier.

[0256] 3) The granularity of the first information includes the session, the first information includes the session identifier, or the first information includes the session identifier and at least one of the following: terminal identifier, QoS flow identifier, bearer identifier, DRB identifier, LCH identifier.

[0257] 4) The granularity of the first information includes the bearer, the first information includes the bearer identifier, or the first information includes the bearer identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, DRB identifier, LCH identifier.

[0258] 5) The granularity of the first information includes DRB, the first information includes DRB identifier, or the first information includes DRB identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, LCH identifier.

[0259] 6) The granularity of the first information includes LCH, the first information includes LCH identifier, or the first information includes LCH identifier and at least one of the following: terminal identifier, QoS flow identifier, session identifier, bearer identifier, DRB identifier.

[0260] In this embodiment of the application, when the first information does not carry identification information, the object indicated or to which the first information is applicable may include at least one of the following: 1) The granularity of the first information includes the terminal, and the first information indicates or applies to all QoS flows, all sessions, all bearers, all DRBs, or all LCHs.

[0261] 2) The granularity of the first information includes QoS flows, and the first information indicates or applies to all QoS flows.

[0262] 3) The granularity of the first message includes the session, and the first message indicates or applies to all sessions.

[0263] 4) The granularity of the first information includes the carrier, and the first information indicates or applies to all carriers.

[0264] 5) The granularity of the first information includes DRBs, and the first information indicates or applies to all DRBs.

[0265] 6) The granularity of the first information includes LCH, and the first information indicates or applies to all LCH.

[0266] In this application embodiment, the rate involved in the first information includes at least one of the following: bit rate, encoding rate, data rate, resource rate, and source rate.

[0267] In this embodiment of the application, the above-mentioned device is further used to: adjust the rate or control the rate according to the first information.

[0268] In this embodiment of the application, the above-described device is further configured to: adjust or control the rate in at least one of the following ways: 1) After receiving the first message and after a preset time has elapsed, the rate will be adjusted or controlled. 2) Adjust or control the speed within a preset time period; 3) Adjust or control the rate starting from a preset data unit; wherein, the preset data unit includes: the current data unit or the Nth data unit after the current data unit, where N is a positive integer; 4) Adjust or control the rate of a preset number of data units; wherein, the preset number is one or more.

[0269] In the embodiments of this application, the data unit includes at least one of the following: session, quality of service stream, burst packet, frame, protocol data unit (PDU), PDU set, dataset, and service data unit (SDU).

[0270] In this embodiment of the application, the above-mentioned device is further used for: Before receiving the first information from the first node, a request message or a query message is sent to the first node. The request message is used to request the first information, and the query message is used to query the first information.

[0271] The granularity of the aforementioned request or query messages includes at least one of the following: terminal, QoS stream, session, bearer, DRB, LCH.

[0272] In one implementation, the request message or query message is sent at a preset time or after a prohibited period ends. In this embodiment, the prohibited period is used to control whether or not the request message or query message can be sent, and to control when the request message or query message is sent.

[0273] The prohibited period can include a start time and duration; the time range corresponding to the duration is the prohibited period. The handling mechanism for prohibited periods includes at least one of the following: 1) At the start time of the prohibited period (i.e., the start time of the prohibit timer), the second node can send a request message or a query message to the first node; 2) During the prohibited period (i.e., during the operation of the prohibit timer), the second node is prohibited from sending request messages or query messages to the first node; 3) After the prohibition period ends (i.e., the prohibition timer ends), the second node can send a request message or a query message to the first node.

[0274] The above method can avoid the second node frequently sending request or query messages to the first node, thereby saving network overhead.

[0275] In this application embodiment, the granularity of the prohibited time period includes at least one of the following: terminal, QoS flow, session, bearer, DRB, LCH.

[0276] And / or, In this embodiment of the application, the prohibited period includes prohibited periods for uplink and downlink, or the prohibited period includes: prohibited periods for request messages or query messages corresponding to uplink rate adjustment or control, and prohibited periods for request messages or query messages corresponding to downlink rate adjustment or control.

[0277] In cases where the granularity of the prohibited period is per-UE, the UE (i.e., the second node) executes according to at least one of the following mechanisms: 1) At the start of the prohibited period, the UE may send a request message or a query message to the first node; 2) During the prohibited period, the UE is prohibited from sending request messages or query messages to the first node; 3) After the prohibited period ends, the UE can send a request message or an inquiry message to the first node.

[0278] Specifically, when the granularity of the prohibited period is per-session, per-QoS flow, per-DRB, per-bearer, or per-LCH, the second node executes according to at least one of the following mechanisms: 1) At the start time of the prohibited period corresponding to a certain session, QoS flow, DRB, bearer or LCH, the second node can send a request or query message for the corresponding session, QoS flow, DRB, bearer or LCH to the first node. 2) During the prohibited period corresponding to a certain session, QoS flow, DRB, bearer, or LCH, the second node is prohibited from sending the corresponding session, QoS flow, DRB, bearer, or LCH request or query message to the first node. In this scenario, the terminal can initiate requests or queries for other sessions, QoS flows, DRB, bearer, or LCH if the prohibited period corresponding to the requests or queries for other sessions, QoS flows, DRB, bearer, or LCH is not running.

[0279] 3) After the prohibited period for a certain session, QoS flow, DRB, bearer, or LCH ends, the second node can send a request or query message to the first node for the corresponding session, QoS flow, DRB, bearer, or LCH again.

[0280] In this embodiment of the application, the above-mentioned device is further used for: The lower layer sends the second mapping information to the upper layer to assist the upper layer in adjusting or controlling the rate. The second mapping information includes at least one of the following: 1) The granularity of the first information includes LCH, and the second mapping information includes at least one of the following: LCH mapping relationship; Mapping relationship between LCH and DRB; Mapping relationship between LCH and bearer; Mapping relationship between LCH and session; Mapping relationship between LCH and QoS flow.

[0281] 2) The granularity of the first information includes DRB, and the second mapping information includes at least one of the following: Mapping relationship between DRB and LCH; Mapping relationship between DRB and bearer; Mapping relationship between DRB and session; Mapping relationship between DRB and QoS flow.

[0282] 3) The granularity of the first information includes the carrier, and the second mapping information includes at least one of the following: Mapping relationship between the bearer and the LCH; Mapping relationship between bearer and DRB; Mapping relationship between bearer and session; Mapping relationship between bearers and QoS flows.

[0283] 4) The granularity of the first information includes the session, and the second mapping information includes at least one of the following: Session mapping relationships; The mapping relationship between sessions and QoS flows; The mapping relationship between sessions and bearers; The mapping relationship between sessions and DRBs; The mapping relationship between sessions and LCH.

[0284] In this embodiment of the application, the above-mentioned device is further used for: The lower layer sends the second mapping information to the upper layer to assist the upper layer in adjusting or controlling the rate. The second mapping information includes at least one of the following: 1) QoS flow mapping relationship; 2) Mapping relationship between QoS flows and sessions; 3) Mapping relationship between QoS flows and bearers; 4) Mapping relationship between QoS flows and DRBs; 5) Mapping relationship between QoS flows and LCH; 6) Session mapping relationship; 7) The mapping relationship between sessions and QoS flows; 8) The mapping relationship between sessions and bearers; 9) The mapping relationship between sessions and DRBs; 10) The mapping relationship between sessions and LCH.

[0285] In this embodiment of the application, the above-mentioned device is further used for: The upper layer sends the second mapping information to the lower layer to assist the lower layer in adjusting or controlling the rate. The second mapping information includes at least one of the following: 1) The granularity of the first information includes QoS flows, and the second mapping information includes at least one of the following: QoS flow mapping relationship; Mapping relationship between QoS flows and sessions; Mapping relationship between QoS flows and bearers; Mapping relationship between QoS flows and DRBs; Mapping relationship between QoS flows and LCH.

[0286] 2) The granularity of the first information includes the session, and the second mapping information includes at least one of the following: Session mapping relationships; The mapping relationship between sessions and QoS flows; The mapping relationship between sessions and bearers; The mapping relationship between sessions and DRBs; The mapping relationship between sessions and LCH.

[0287] 3) The granularity of the first information includes the carrier, and the second mapping information includes at least one of the following: Mapping relationship between bearers and QoS flows; Mapping relationship between bearer and session; Mapping relationship between bearer and DRB; Mapping relationship between the bearer and LCH.

[0288] In this embodiment of the application, the above-mentioned device is further used for: The upper layer sends the second mapping information to the lower layer to assist the lower layer in adjusting or controlling the rate. The second mapping information includes at least one of the following: 1) Mapping relationship between LCH and DRB; 2) Mapping relationship between LCH and bearer; 3) The mapping relationship between LCH and session; 4) Mapping relationship between LCH and QoS flows; 5) Mapping relationship between DRB and bearer; 6) The mapping relationship between DRB and session; 7) Mapping relationship between DRB and QoS flow; 8) The mapping relationship between the bearer and the session; 9) Mapping relationship between bearer and QoS flow.

[0289] In this embodiment of the application, the first information is carried in at least one of the following messages: Non-Access Stratum (NAS) message, Radio Resource Control (RRC) message, Media Access Control (MAC) Control Element (CE) message, Downlink Control Information (DCI) message, and Uplink Control Information (UCI) message.

[0290] In this embodiment of the application, the RRC message includes at least one of the following: RRC reconfiguration message, connection establishment message, terminal assistance information (UAI), RRC reconfiguration complete message, and connection establishment complete message.

[0291] In this embodiment, the first node and the second node are different devices, and there can be various scenarios, including but not limited to the following: 1) The first node is a base station, and the second node is a terminal, core network node, or application layer node; or, 2) The first node is a terminal, and the second node is a base station, core network node, or application layer node; or, 3) The first node is a core network node, and the second node is a base station or terminal; or, 4) The first node is an application layer node, and the second node is a base station or terminal.

[0292] The apparatus provided in this application embodiment can execute the method in any of the method embodiments with the second node as the execution subject. For details, please refer to the description in the method embodiments, which will not be repeated here.

[0293] The apparatus provided in this application embodiment receives first information sent by a first node through a second node. The first information includes at least one of the following: congestion information, rate control information, and rate adjustment information. The first information can assist the second node in adjusting or controlling the rate without multiple feedbacks, enabling faster and more accurate rate control, reducing the time consumption of rate control, and improving the efficiency of rate control.

[0294] This application provides a rate control device. As an example, the device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the types of terminals listed above, and the network-side device may include, but is not limited to, the types of network-side devices listed above. This application does not impose specific limitations on these types.

[0295] The rate control device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0296] The apparatus provided in this application embodiment can implement the various processes implemented in the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0297] like Figure 8 As shown in the illustration, this application also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps of the above-described method embodiments and achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions executed by the processor 801 implement the various steps of the above-described method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0298] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the above method embodiments. This terminal embodiment corresponds to the above method embodiments; all implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 6 Or the device shown in Figure 7. Specifically, Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application. The terminal 900 includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.

[0299] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 910 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0300] It should be understood that, in this embodiment, the input unit 904 may include a graphics processor 9041 and a microphone 9042. The graphics processor 9041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0301] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 901 can transmit it to the processor 910 for processing; in addition, the radio frequency unit 901 can send uplink data to the network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0302] The memory 909 can be used to store software programs or instructions, as well as various data. The memory 909 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 909 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 909 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0303] Processor 910 may include one or more processing units; optionally, processor 910 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 910.

[0304] The radio frequency unit 901 is used to send first information to the second node or receive first information sent by the first node, wherein the first information includes at least one of the following: congestion information, rate control information, and rate adjustment information.

[0305] The terminal provided in this application embodiment sends first information to a second node or receives first information sent by a first node. The first information includes at least one of the following: congestion information, rate control information, and rate adjustment information. The first information can assist the second node in adjusting or controlling the rate without multiple feedbacks, enabling faster and more accurate rate control, reducing the time consumption of rate control, and improving the efficiency of rate control.

[0306] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0307] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown above, where the network-side device is the execution subject. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0308] Specifically, embodiments of this application also provide a network-side device, which may be... Figure 6 Or the device shown in Figure 7. (e.g.) Figure 10 As shown, the network-side device 1000 includes: an antenna 101, a radio frequency (RF) device 102, a baseband device 103, a processor 104, and a memory 105. The antenna 101 is connected to the RF device 102. In the uplink direction, the RF device 102 receives information through the antenna 101 and transmits the received information to the baseband device 103 for processing. In the downlink direction, the baseband device 103 processes the information to be transmitted and sends it to the RF device 102. The RF device 102 processes the received information and transmits it through the antenna 101.

[0309] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 103, which includes a baseband processor.

[0310] The baseband device 103 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 10 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 105 via a bus interface to call the program in the memory 105 and execute the network device operation shown in the above method embodiment.

[0311] The network-side device may also include a network interface 106, such as a Common Public Radio Interface (CPRI).

[0312] Specifically, the network-side device 1000 in this application embodiment further includes: instructions or programs stored in memory 105 and executable on processor 104, wherein processor 104 calls the instructions or programs in memory 105 to execute. Figure 6 Alternatively, the methods executed by each module shown in Figure 7 can achieve the same technical effect. To avoid repetition, they will not be described in detail here.

[0313] Specifically, embodiments of this application also provide a network-side device. For example... Figure 11 As shown, the network-side device 1100 includes a processor 1101, a network interface 1102, and a memory 1103. The network interface 1102 is, for example, a common public radio interface (CPRI).

[0314] Specifically, the network-side device 1100 of this embodiment further includes: instructions or programs stored in memory 1103 and executable on processor 1101, wherein processor 1101 calls the instructions or programs in memory 1103 to execute. Figure 6 Alternatively, the methods executed by each module shown in Figure 7 can achieve the same technical effect. To avoid repetition, they will not be described in detail here.

[0315] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0316] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0317] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0318] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0319] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0320] This application also provides a rate control system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the rate control method described above, and the network-side device can be used to execute the steps of the rate control method described above.

[0321] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0322] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0323] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A rate control method characterized by, Comprising: The first node sends first information to the second node, wherein the first information comprises at least one of the following: congestion information, rate control information, rate adjustment information.

2. The method of claim 1, wherein, The first information is used to assist the second node to adjust or control rate, or the first information is used by the second node to adjust or control rate according to the first information.

3. The method according to claim 1 or 2, characterized in that, The first information comprises at least one of the following: Rate adjustment indication; Rate information; Congestion information; Network load information; Channel information; Quality of service (QoS) information; Uplink indication; Downlink indication; Identity information.

4. The method of claim 3, wherein, The rate adjustment indication comprises at least one of the following: increase rate, increase rate level, decrease rate, decrease rate level, rate unchanged, rate level unchanged, rate adjustment factor, rate level adjustment factor; And / or, The rate information comprises at least one of the following: rate, rate level, rate range; And / or, The congestion information comprises at least one of the following: whether congestion, congestion level, congestion cause, congestion channel, congestion scenario, congestion associated service, congestion associated session, congestion associated QoS flow, congestion associated data radio bearer (DRB), congestion associated logical channel (LCH), congestion associated channel; And / or, The network load information comprises at least one of the following: load level, whether overload, whether light load, whether heavy load, load cause, load associated cause, load associated scenario, load associated service, load associated session, load associated QoS flow, load associated DRB, load associated LCH, load associated channel; And / or, The channel information comprises at least one of the following: channel measurement result, channel measurement level, channel condition, channel condition; And / or, The QoS information comprises at least one of the following: QoS parameter, QoS requirement, QoS allocation, QoS mapping information; And / or, The identity information comprises at least one of the following: terminal identity, QoS flow identity, session identity, bearer identity, DRB identity, LCH identity.

5. The method according to any one of claims 1-4, characterized in that, The granularity of the first information comprises at least one of the following: terminal, QoS flow, session, bearer, DRB, LCH.

6. The method of claim 5, wherein, The granularity of the first information comprises terminal, and the first information comprises terminal identity; And / or, The granularity of the first information comprises QoS flow, and the first information comprises QoS flow identity, or the first information comprises QoS flow identity and at least one of the following: terminal identity, session identity, bearer identity, DRB identity, LCH identity; And / or, The granularity of the first information comprises session, and the first information comprises session identity, or the first information comprises session identity and at least one of the following: terminal identity, QoS flow identity, bearer identity, DRB identity, LCH identity; And / or, The granularity of the first information comprises a bearer, the first information comprises a bearer identifier, or the first information comprises a bearer identifier and at least one of the following: a terminal identifier, a QoS flow identifier, a session identifier, a DRB identifier, and an LCH identifier; and / or, The granularity of the first information comprises a DRB, the first information comprises a DRB identifier, or the first information comprises a DRB identifier and at least one of the following: a terminal identifier, a QoS flow identifier, a session identifier, a bearer identifier, and an LCH identifier; and / or, The granularity of the first information comprises an LCH, the first information comprises an LCH identifier, or the first information comprises an LCH identifier and at least one of the following: a terminal identifier, a QoS flow identifier, a session identifier, a bearer identifier, and a DRB identifier.

7. The method of claim 5, wherein, The first information does not carry identification information; wherein, The granularity of the first information comprises a terminal, and the first information indicates or applies to all QoS flows, all sessions, all bearers, all DRBs, or all LCHs; and / or, The granularity of the first information comprises a QoS flow, and the first information indicates or applies to all QoS flows; and / or, The granularity of the first information comprises a session, and the first information indicates or applies to all sessions; and / or, The granularity of the first information comprises a bearer, and the first information indicates or applies to all bearers; and / or, The granularity of the first information comprises a DRB, and the first information indicates or applies to all DRBs; and / or, The granularity of the first information comprises an LCH, and the first information indicates or applies to all LCHs.

8. The method according to any one of claims 1-7, characterized in that, The rate comprises at least one of the following: a bit rate, a coding rate, a data rate, a resource rate, and a source rate.

9. The method according to any one of claims 1-7, characterized in that, The first node sends the first information in at least one of the following cases: The first node determines that it is necessary to adjust or control the rate; The first node determines that it is necessary to inform the second node of the first information; The first node receives a request message or an inquiry message sent by the second node, wherein the request message is used to request the first information, and the inquiry message is used to inquire about the first information.

10. The method according to any one of claims 1-7, characterized in that, Before the first node sends the first information to the second node, the method further comprises: The first node receives a request message or an inquiry message sent by the second node, wherein the request message is used to request the first information, and the inquiry message is used to inquire about the first information, and the granularity of the request message or the inquiry message comprises at least one of the following: a terminal, a QoS flow, a session, a bearer, a DRB, and an LCH.

11. The method according to any one of claims 1-10, characterized in that, Further comprising: The upper layer of the first node sends first mapping information to the lower layer of the first node to assist the lower layer in determining the first information; wherein, The granularity of the first information comprises a QoS flow, and the first mapping information comprises at least one of the following: a QoS flow mapping relationship; a mapping relationship between a QoS flow and a session; a mapping relationship between a QoS flow and a bearer; a mapping relationship between a QoS flow and a DRB; a mapping relationship between a QoS flow and an LCH; and / or, The granularity of the first information comprises a session, and the first mapping information comprises at least one of the following: a session mapping relationship; A mapping relationship between the session and a QoS flow; A mapping relationship between the session and a bearer; A mapping relationship between the session and a DRB; A mapping relationship between the session and an LCH; And / or, The granularity of the first information includes a bearer, and the first mapping information includes at least one of the following: A mapping relationship between the bearer and a QoS flow; A mapping relationship between the bearer and a session; A mapping relationship between the bearer and a DRB; A mapping relationship between the bearer and an LCH.

12. The method according to any one of claims 1-10, characterized in that, Further comprising: An upper layer of the first node sends first mapping information to a lower layer of the first node to assist the lower layer in determining the first information; wherein the first mapping information includes at least one of the following: A mapping relationship between the LCH and a DRB; A mapping relationship between the LCH and a bearer; A mapping relationship between the LCH and a session; A mapping relationship between the LCH and a QoS flow; A mapping relationship between the DRB and a bearer; A mapping relationship between the DRB and a session; A mapping relationship between the DRB and a QoS flow; A mapping relationship between the bearer and a session; A mapping relationship between the bearer and a QoS flow.

13. The method according to any one of claims 1-10, characterized in that, Further comprising: A lower layer of the first node sends first mapping information to an upper layer of the first node to assist the upper layer in determining the first information; wherein The granularity of the first information includes an LCH, and the first mapping information includes at least one of the following: An LCH mapping relationship; A mapping relationship between the LCH and a DRB; A mapping relationship between the LCH and a bearer; A mapping relationship between the LCH and a session; A mapping relationship between the LCH and a QoS flow; And / or, The granularity of the first information includes a DRB, and the first mapping information includes at least one of the following: A mapping relationship between the DRB and an LCH; A mapping relationship between the DRB and a bearer; A mapping relationship between the DRB and a session; A mapping relationship between the DRB and a QoS flow; And / or, The granularity of the first information includes a bearer, and the first mapping information includes at least one of the following: A mapping relationship between the bearer and an LCH; A mapping relationship between the bearer and a DRB; A mapping relationship between the bearer and a session; A mapping relationship between the bearer and a QoS flow; And / or, The granularity of the first information includes a session, and the first mapping information includes at least one of the following: A session mapping relationship; A mapping relationship between the session and a QoS flow; A mapping relationship between the session and a bearer; A mapping relationship between the session and a DRB; A mapping relationship between the session and an LCH.

14. The method according to any one of claims 1-10, characterized in that, Further comprising: A lower layer of the first node sends first mapping information to an upper layer of the first node to assist the upper layer in determining the first information; wherein the first mapping information includes at least one of the following: A QoS flow mapping relationship; A mapping relationship between the QoS flow and a session; A mapping relationship between the QoS flow and a bearer; A mapping relationship between the QoS flow and a DRB; A mapping relationship between the QoS flow and an LCH; A session mapping relationship; A mapping relationship between the session and a QoS flow; A mapping relationship between the session and a bearer; A mapping relationship between the session and a DRB; A mapping relationship between the session and an LCH.

15. The method of any one of claims 1-14, wherein, The first information is carried in at least one of the following messages: a non-access stratum (NAS) message, a radio resource control (RRC) message, a medium access control control element (MAC CE) message, a downlink control information (DCI) message, and an uplink control information (UCI) message.

16. The method of claim 15, wherein, The RRC message comprises at least one of the following: an RRC reconfiguration message, a connection setup message, terminal assistance information (UAI), an RRC reconfiguration completion message, and a connection setup completion message.

17. The method of any of claims 1-16, wherein: the first node is a base station, and the second node is a terminal, a core network node, or an application layer node; or the first node is a terminal, and the second node is a base station, a core network node, or an application layer node; or the first node is a core network node, and the second node is a base station or a terminal; or the first node is an application layer node, and the second node is a base station or a terminal.

18. A rate control method, characterized by, comprising: the second node receives first information sent by the first node, wherein the first information comprises at least one of the following: congestion information, rate control information, and rate adjustment information.

19. The method of claim 18, wherein, further comprising: the second node adjusts a rate or controls a rate according to the first information.

20. The method of claim 18, wherein, after the second node receives the first information sent by the first node, further comprising: the second node starts to adjust the rate or control the rate after receiving the first information and after a preset time period elapses; the second node adjusts the rate or controls the rate within a preset time period; the second node starts to adjust the rate or control the rate from a preset data unit, wherein the preset data unit comprises a current data unit or an Nth data unit after the current data unit, and N is a positive integer; the second node adjusts the rate or controls the rate for a preset number of data units, wherein the preset number is one or more.

21. The method of claim 20, wherein, the data unit comprises at least one of the following: a session, a quality of service (QoS) flow, a burst packet, a frame, a protocol data unit (PDU), a PDU set, a data set, and a service data unit (SDU).

22. The method of any one of claims 18-21, wherein, before the second node receives the first information sent by the first node, further comprising: the second node sends a request message or an inquiry message to the first node, wherein the request message is used to request the first information, and the inquiry message is used to inquire about the first information.

23. The method of claim 22, wherein, the request message or the inquiry message is sent at a preset time or after a forbidden period ends.

24. The method of claim 23, wherein, a granularity of the forbidden period comprises at least one of the following: a terminal, a QoS flow, a session, a bearer, a DRB, and a logical channel (LCH); and / or the forbidden period comprises a forbidden period for uplink and a forbidden period for downlink, or the forbidden period comprises a forbidden period for a corresponding request message or inquiry message for uplink rate adjustment or control and a forbidden period for a corresponding request message or inquiry message for downlink rate adjustment or control. further comprising:

25. The method of any one of claims 18-24, wherein, a lower layer of the second node sends second mapping information to an upper layer of the second node to assist the upper layer to adjust the rate or control the rate, wherein a granularity of the first information comprises an LCH, and the second mapping information comprises at least one of the following: an LCH mapping relationship; an LCH-DRB mapping relationship; an LCH-bearer mapping relationship; an LCH-session mapping relationship; an LCH-QoS flow mapping relationship; and / or a granularity of the first information comprises a DRB, and the second mapping information comprises at least one of the following: a DRB-LCH mapping relationship; ​ ​ A mapping relationship between the DRB and a bearer; A mapping relationship between the DRB and a session; A mapping relationship between the DRB and a QoS flow; And / or, The granularity of the first information comprises a bearer, and the second mapping information comprises at least one of the following: A mapping relationship between the bearer and an LCH; A mapping relationship between the bearer and a DRB; A mapping relationship between the bearer and a session; A mapping relationship between the bearer and a QoS flow; And / or, The granularity of the first information comprises a session, and the second mapping information comprises at least one of the following: A session mapping relationship; A mapping relationship between the session and a QoS flow; A mapping relationship between the session and a bearer; A mapping relationship between the session and a DRB; A mapping relationship between the session and an LCH.

26. The method of any one of claims 18-24, wherein, Further comprising: The bottom layer of the second node sends second mapping information to the upper layer of the second node to assist the upper layer in adjusting a rate or controlling a rate; wherein the second mapping information comprises at least one of the following: A QoS flow mapping relationship; A mapping relationship between a QoS flow and a session; A mapping relationship between a QoS flow and a bearer; A mapping relationship between a QoS flow and a DRB; A mapping relationship between a QoS flow and an LCH; A session mapping relationship; A mapping relationship between a session and a QoS flow; A mapping relationship between a session and a bearer; A mapping relationship between a session and a DRB; A mapping relationship between a session and an LCH.

27. The method of any one of claims 18-24, wherein, Further comprising: The upper layer of the second node sends second mapping information to the bottom layer of the second node to assist the bottom layer in adjusting a rate or controlling a rate; wherein The granularity of the first information comprises a QoS flow, and the second mapping information comprises at least one of the following: A QoS flow mapping relationship; A mapping relationship between a QoS flow and a session; A mapping relationship between a QoS flow and a bearer; A mapping relationship between a QoS flow and a DRB; A mapping relationship between a QoS flow and an LCH; And / or, The granularity of the first information comprises a session, and the second mapping information comprises at least one of the following: A session mapping relationship; A mapping relationship between a session and a QoS flow; A mapping relationship between a session and a bearer; A mapping relationship between a session and a DRB; A mapping relationship between a session and an LCH. And / or, The granularity of the first information comprises a bearer, and the second mapping information comprises at least one of the following: A mapping relationship between the bearer and a QoS flow; A mapping relationship between the bearer and a session; A mapping relationship between the bearer and a DRB; A mapping relationship between the bearer and an LCH.

28. The method of any one of claims 18-24, wherein, Further comprising: The upper layer of the second node sends second mapping information to the bottom layer of the second node to assist the bottom layer in adjusting a rate or controlling a rate; wherein the second mapping information comprises at least one of the following: A mapping relationship between an LCH and a DRB; A mapping relationship between an LCH and a bearer; A mapping relationship between an LCH and a session; A mapping relationship between an LCH and a QoS flow; A mapping relationship between a DRB and a bearer; A mapping relationship between a DRB and a session; A mapping relationship between a DRB and a QoS flow; A mapping relationship between a bearer and a session; A mapping relationship between a bearer and a QoS flow.

29. A rate control apparatus characterized by comprising: Comprising: A sending module, configured to send first information to a second node, wherein the first information comprises at least one of the following: congestion information, rate control information, and rate adjustment information.

30. A rate control apparatus characterized by comprising: Comprising: A receiving module configured to receive first information sent by a first node, wherein the first information comprises at least one of the following: congestion information, rate control information, rate adjustment information.

31. A terminal, characterized by A computer program product comprising a computer readable storage medium having program code stored therein, the program code configured such that, on execution by a processor, the program code causes the steps of the rate control method according to any one of claims 1 to 28 to be performed.

32. A network-side device, comprising: A computer program product comprising a computer readable storage medium having program code stored therein, the program code configured such that, on execution by a processor, the program code causes the steps of the rate control method according to any one of claims 1 to 28 to be performed.

33. A readable storage medium, characterized by, A computer program product comprising a computer readable storage medium having program code stored therein, the program code configured such that, on execution by a processor, the program code causes the steps of the rate control method according to any one of claims 1 to 28 to be performed.

Images