WO2021197331A1 - 流控消息的传输方法和设备 - Google Patents

流控消息的传输方法和设备 Download PDF

Info

Publication number
WO2021197331A1
WO2021197331A1 PCT/CN2021/083996 CN2021083996W WO2021197331A1 WO 2021197331 A1 WO2021197331 A1 WO 2021197331A1 CN 2021083996 W CN2021083996 W CN 2021083996W WO 2021197331 A1 WO2021197331 A1 WO 2021197331A1
Authority
WO
WIPO (PCT)
Prior art keywords
flow control
threshold
timer
control message
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/083996
Other languages
English (en)
French (fr)
Inventor
文鸣
刘进华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2021197331A1 publication Critical patent/WO2021197331A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a method and device for transmitting flow control messages.
  • the use of a flow control mechanism can solve the problem of downlink data congestion.
  • the downlink data congestion means that the data received by the IAB child node from its IAB parent node is too late to be sent to the downstream IAB node or terminal device, which causes data accumulation.
  • the data of an IAB child node When the data of an IAB child node accumulates to the risk of buffer overflow, it will send a Flow Control Feedback (Flow Control Feedback), or Flow Control Message (FCM), to its parent node to alert congestion and receive flow control.
  • the IAB parent node of the message will control the transmission rate of downlink data sent to the IAB child node.
  • the IAB child node when the IAB child node meets the trigger condition, it triggers the Hop by Hop (HbH) option to the IAB parent node to feedback the flow control message.
  • HbH Hop by Hop
  • the trigger condition of the flow control message is not perfect and will As a result, flow control messages are frequently triggered. Therefore, it is necessary to provide relevant solutions to optimize the triggering and transmission mechanism of flow control messages.
  • the purpose of the embodiments of the present application is to provide a method and device for transmitting flow control messages, so as to solve the problem that flow control messages are triggered frequently due to insufficient trigger conditions of flow control messages in related technologies.
  • a method for transmitting a flow control message is provided, the method is executed by a first communication device, and the method includes: based on at least one of the following: the running status of the timer, the buffered data status, and the received round
  • the inquiry message is used to determine whether the trigger condition of the flow control message is met; if the trigger condition is met, the flow control message is sent.
  • a method for transmitting flow control messages is provided.
  • the method is executed by a second communication device.
  • the method includes: receiving a flow control message;
  • the trigger condition is determined based on at least one of the following: the running status of the timer, the buffered data status, and the received polling message.
  • a communication device including: a processing module, configured to determine whether the trigger condition of the flow control message is satisfied based on at least one of the following: the running condition of the timer, the buffered data condition, and the received polling message ; Sending module for sending the flow control message if the trigger condition is met.
  • a communication device including: a receiving module for receiving a flow control message; wherein the flow control message is sent by a first communication device when a trigger condition is satisfied, and the trigger condition is Determined based on at least one of the following: the running status of the timer, the buffered data status, and the received polling message.
  • a communication device in a fifth aspect, includes a processor, a memory, and a computer program that is stored on the memory and can run on the processor.
  • the computer program When the computer program is executed by the processor, The steps of the method for transmitting a flow control message as described in any one of the first aspect and the second aspect are implemented.
  • a computer-readable storage medium is provided, and a computer program is stored on the computer-readable storage medium. The method of transmission of flow control messages.
  • the trigger condition is satisfied based on at least one of the running condition of the timer, the buffered data condition of the communication device, and the received polling message, and send it when the trigger condition is satisfied.
  • Flow control messages communication equipment will not send flow control messages too frequently, saving signaling overhead.
  • Fig. 1 is a schematic flowchart of a method for transmitting a flow control message according to an embodiment of the present application
  • Fig. 2 is a schematic flowchart of a method for transmitting a flow control message according to an embodiment of the present application
  • Fig. 3 is a schematic flowchart of a method for transmitting a flow control message according to an embodiment of the present application
  • Fig. 4 is a schematic flowchart of a method for transmitting a flow control message according to an embodiment of the present application
  • Fig. 5 is a schematic flowchart of a method for transmitting a flow control message according to an embodiment of the present application
  • Fig. 6 is a schematic flowchart of a method for transmitting a flow control message according to an embodiment of the present application
  • Fig. 7 is a schematic flowchart of a method for transmitting a flow control message according to an embodiment of the present application.
  • Fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • Fig. 9 is a schematic structural diagram of a communication device according to another embodiment of the present application.
  • Fig. 10 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • 5G Fifth Generation
  • NR New Radio
  • IAB Integrated Access Backhaul
  • terminal equipment may include, but is not limited to, a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile phone (Mobile Telephone), a user equipment (User Equipment, UE), and a mobile phone (handset).
  • the terminal equipment can communicate with one or more core networks through a radio access network (Radio Access Network, RAN), for example, the terminal equipment can be a mobile phone (or It is called a "cellular" phone), a computer with wireless communication function, etc.
  • the terminal device can also be a portable, pocket-sized, handheld, built-in computer or a mobile device in a vehicle.
  • a network device is a device deployed in a wireless access network to provide wireless communication functions for terminal devices.
  • the network device may be a base station, and the base station may include various forms of macro base stations, micro base stations, relay stations, and access points.
  • the names of devices with base station functions may be different.
  • an evolved NodeB evolved NodeB, eNB or eNodeB
  • 3G third generation
  • NodeB Node B
  • 5G 5G system
  • gNB Generation Node B
  • gNB network equipment in subsequent evolved communication systems, etc., however, the terminology does not constitute a restriction.
  • an embodiment of the present application provides a method 100 for transmitting flow control messages.
  • the method may be executed by a communication device.
  • the method may be executed by software or hardware installed on the communication device.
  • the device may be an IAB child node in the IAB network; it may also be a relay node.
  • the method 100 includes the following steps.
  • S102 Based on at least one of the following: the running condition of the timer, the buffered data condition, and the received polling message, it is determined whether the triggering condition of the flow control message is satisfied.
  • the running status of the timer includes, for example: the timer is running; the timer is not running.
  • the buffered data situation of the communication device includes, for example, whether the amount of data buffered by the communication device exceeds a certain data volume threshold; whether the waiting time of the data buffered by the communication device exceeds a certain time threshold, where the waiting time of the buffered data can be the earliest buffer
  • the data waiting time can also be the average waiting time of data cached within a certain range (such as all).
  • this embodiment determines whether the trigger condition of the flow control message is met based on the running status of the timer. For example, if the timer is running, the trigger condition is not met.
  • this embodiment determines whether the trigger condition of the flow control message is satisfied based on the running condition of the timer and the buffered data condition of the communication device. For example, if the first timer is not running and the buffered data exceeds the first threshold, it is determined that the trigger condition of the flow control message is satisfied. It can be understood that if the first timer is running or the buffered data does not exceed the first threshold, the trigger condition of the flow control message is not met.
  • this embodiment determines whether the triggering condition of the flow control message is satisfied based on the buffered data condition of the communication device. For example, if the data buffered by the communication device exceeds the second threshold for the first time or exceeds the second threshold again, it is determined that the trigger condition of the flow control message is satisfied; wherein, after the trigger condition of the flow control message is determined to be satisfied, if the buffered data If the data exceeds the second threshold and does not exceed the third threshold, the trigger condition is not met, and the third threshold is higher than the second threshold.
  • this embodiment determines whether the triggering condition of the flow control message is satisfied based on the received polling message. For example, if the polling message is received, it is determined that the triggering condition of the flow control message is satisfied.
  • the terminal device may also construct the flow control message before sending the flow control message.
  • FCM flow control message
  • the flow control message transmission method provided by the embodiment of the application can determine whether the trigger condition is satisfied based on at least one of the running condition of the timer, the buffered data condition of the communication device, and the received polling message, and when the condition is satisfied The flow control message is generated and sent under the trigger condition, and the communication device will not send the flow control message too frequently, saving signaling overhead.
  • S102 of Embodiment 100 may include: if the first timer is not running and the buffered data exceeds the first threshold, determining that the trigger condition of the flow control message is satisfied. It can be understood that if the first timer is running or the buffered data does not exceed the first threshold, the trigger condition of the flow control message is not met.
  • the buffered data mentioned in this embodiment exceeds the first threshold. It can be that the data volume of the buffered data exceeds the first threshold (or called the first data volume threshold), or the waiting time of the buffered data exceeds the first threshold. Threshold (or called the first time threshold).
  • timers mentioned in the various embodiments of this specification include the first timer and the second and third timers mentioned later. Based on the realization functions of these timers, some other technical terms may also be used. Instead, for example, flow control prohibit timer (FC prohibit timer), delay timer (delay timer), etc.
  • FC prohibit timer flow control prohibit timer
  • delay timer delay timer
  • the above-mentioned first timer may also be started or restarted.
  • the generation of the flow control message is no longer triggered during the running period of the first timer, that is, the triggering condition of the flow control message is not met during the running period of the first timer.
  • the method further includes: if the buffered data does not exceed the first threshold, for example, less than or equal to A certain preset threshold (the preset threshold is lower than or equal to the first threshold), the congestion release message is sent to the parent node or upstream node, so that the parent node or upstream node of the communication device can understand the flow control situation of the communication device in time .
  • the preset threshold is lower than or equal to the first threshold
  • the congestion release message can be sent to the parent node or the upstream node.
  • the flow control message can be sent again, and the first timer can be restarted. Trigger flow control messages.
  • the foregoing embodiment sends a congestion release message.
  • the communication device when the communication device is an IAB child node, it sends a congestion release message to the IAB parent node, so that the IAB parent node determines that the IAB child node congestion warning is released; when the communication device is a relay node At this time, it sends a congestion release message to the upstream relay node or other network equipment, so that the upstream relay node or other network equipment determines that the congestion warning is released.
  • the IAB parent node when it sends a flow control message to the IAB parent node, the IAB parent node starts a fifth timer (the fifth timer may have the same duration as the first timer, but also It may be different from the duration of the first timer), if the IAB parent node does not receive the flow control message again when the fifth timer runs, it is determined that the congestion warning is released.
  • the fifth timer may have the same duration as the first timer, but also It may be different from the duration of the first timer
  • the IAB parent node After the IAB child node sends a flow control message to the IAB parent node, the IAB parent node takes flow control measures after receiving the flow control message. After the flow control measures are configured, if the IAB parent node does not receive it again For the flow control message of the IAB child node, the IAB parent node considers that the IAB child node congestion warning is lifted; if the IAB parent node receives the flow control message from the IAB child node again, the flow control measures are taken again.
  • This embodiment does not need to perform operations of sending and receiving congestion release messages, which is convenient for further saving signaling overhead and improving communication efficiency; at the same time, it is convenient for the IAB parent node to learn the flow control situation of the IAB child node in time.
  • S102 of the embodiment 100 may include: if the buffered data exceeds the second threshold for the first time or exceeds the second threshold again, determining that the trigger condition of the flow control message is satisfied; where After determining that the trigger condition of the flow control message is met, if the buffered data exceeds the second threshold and does not exceed the third threshold, the trigger condition is not met, that is, the flow control message is not triggered to be generated, and the third threshold is higher than The second threshold.
  • the buffered data mentioned in this embodiment exceeds the second threshold. It can be that the data amount of the buffered data exceeds the second threshold (or called the second data volume threshold), or the waiting time of the buffered data exceeds the second threshold. Threshold (or called the second time threshold); in the same way, the buffered data does not exceed the third threshold, it can be that the data volume of the buffered data does not exceed the third threshold (or called the third data volume threshold), or it can be The waiting time of the buffered data does not exceed the third threshold (or called the third time threshold).
  • This embodiment adopts a progressive flow control message triggering and generation mechanism.
  • the flow control message is sent only when the buffered data exceeds these thresholds, and the buffered data When it is between two adjacent thresholds, the generation of flow control messages is not triggered, which can also avoid frequent triggering of flow control messages, which is convenient for saving signaling overhead.
  • the flow control message is sent, if the buffered data continues to grow, if the buffered data exceeds the third threshold, it is determined that the trigger condition of the flow control message is met, and the flow control message is sent again.
  • the flow control message is used to alert the parent node or upstream node of the communication device to further reduce the downstream traffic.
  • the buffered data mentioned in this embodiment exceeds the third threshold. It can be that the data volume of the buffered data exceeds the third threshold (or called the third data volume threshold), or it can be that the waiting time of the buffered data exceeds the third threshold. Threshold (or called the third time threshold).
  • the progressive flow control message triggering and generation mechanism provided in this embodiment, although only the second threshold and the third threshold are introduced, in fact, more thresholds can be set, for example, the fifth threshold , Etc., where the fifth threshold is greater than the third threshold.
  • the trigger condition is not met, that is, the flow control message is not triggered to be generated until the buffered data exceeds the fifth threshold.
  • the progressive flow control message triggering and generation mechanism provided in the above embodiment can also be used in combination with a timer, which will constitute another embodiment, that is, the data in the buffer exceeds the above third threshold.
  • the second timer can be started or restarted, wherein the flow control message is not triggered during the running period of the second timer, that is, during the running period of the second timer The trigger condition of the flow control message is not met.
  • the progressive flow control message triggering method introduced in each of the foregoing embodiments may further include the following steps: if the buffered data does not exceed the fourth threshold, sending a congestion release message; wherein, the fourth threshold Less than or equal to the second threshold.
  • the first threshold mentioned in the foregoing embodiments may refer to the data amount of cached data or the waiting time of cached data; the second threshold mentioned in the foregoing embodiments includes the data amount of cached data. Or the waiting time of the buffered data; the third threshold mentioned in the previous embodiments includes the data amount of the buffered data or the waiting time of the buffered data; the fourth threshold mentioned in the previous embodiments includes the buffered data The amount of data or the waiting time of the cached data.
  • the ** threshold (referring to at least one of the first threshold to the fourth threshold) described in the previous embodiments does not exceed or exceeds the ** threshold, specifically, the amount of data buffered does not exceed or exceeds the ** threshold, or The waiting time of the cached data does not exceed or exceed the ** threshold.
  • sending the flow control message includes the following steps: if a polling message is received, one of the following 1) and 2) can be executed.
  • flow control messages can be sent periodically to avoid frequent triggering of flow control messages, which is convenient for saving signaling overhead; or, by introducing a third timer, this embodiment can also avoid frequent flow control messages. Trigger to save signaling overhead.
  • the periodically sending multiple flow control messages includes: starting a fourth timer after each flow control message is sent, and sending again after the fourth timer expires Flow control message.
  • the number of the multiple flow control messages is N (N is an integer greater than or equal to 2); wherein, if the N flow control messages are sent, the flow control messages are no longer started.
  • the fourth timer is an integer greater than or equal to 2.
  • N is carried in the polling message, where N is defined by the protocol (pre-) or configured by the network device (pre-), and the parent node or upstream node sending the polling message can obtain get.
  • This embodiment is an event-triggered flow control message, specifically a flow control message triggering mechanism based on the running condition of a timer and the condition of buffered data. As shown in FIG. 2, this embodiment includes the following steps.
  • the data cached by the IAB child node exceeds the first threshold and meets the trigger condition of the flow control message, as shown in Figure 2 for trigger condition 1 (or called trigger1).
  • the IAB child node sends a flow control message 1 (FCM1) to the IAB parent node, and starts the first timer (FC prohibit timer).
  • FCM1 flow control message 1
  • the first timer expires. At this time, if the buffered data still exceeds the first threshold, see trigger condition 3 (or called trigger3) in Figure 2, so it triggers the generation and transmission of flow control message 2 (FCM2), and restarts The first timer.
  • trigger condition 3 or called trigger3 in Figure 2
  • the first timer started by FCM2 times out, and the cached data does not exceed the first threshold at this time, that is, FCM3 will not be triggered.
  • the IAB parent node does not receive FCM3, and considers that the child node congestion warning is lifted.
  • the IAB sub-node may also send a congestion release message to indicate the congestion warning release. As shown in Figure 3, there are the following two methods.
  • the release condition for example, the buffered data is less than or equal to the sixth threshold, and the sixth threshold is less than or equal to the first threshold).
  • the IAB child node sends a congestion resolved message to the IAB parent node, as shown by the solid line in Figure 3.
  • the IAB parent node receives the congestion release message and considers that the child node congestion warning is released.
  • the trigger condition 4 (or called trigger4) in Figure 3 triggers the flow control release message.
  • the IAB child node sends a flow control release message to the IAB parent node, as shown in the dashed line shown in Figure 3 for the congestion release message.
  • the parent node receives the congestion release message and considers that the child node congestion warning is released.
  • the flow control message is triggered by polling, and it is triggered periodically.
  • this embodiment includes the following steps.
  • the network side configures the value of the number of polling periodic triggers N; specifically, it can be configured to the IAB parent node.
  • the IAB parent node sends a polling message 1 (polling1) to the IAB child node, and the polling1 message includes the value of N.
  • the IAB child node After receiving the polling1 message, the IAB child node periodically sends N flow control messages (it has nothing to do with the event trigger mechanism based on embodiment 100, that is, regardless of whether there is a timer that is started after the event is triggered, the child node receives the Polling1 message.
  • the flow control message can always be triggered directly afterwards).
  • the IAB child node starts the fourth timer after sending a flow control message, and generates and sends the flow control message again after the fourth timer expires.
  • the fourth timer When the number of times that the IAB child node sends flow control messages reaches N, the fourth timer is no longer started. That is, the flow control message is triggered N times in total, but the fourth timer is triggered N-1 times.
  • the parent node since Polling is configured on the network side, in actual applications, it will not happen that the parent node sends a Polling message to instruct the child node to send a flow control message when the polling message triggered periodically has not ended. That is, during the period when the fourth timer is on, no additional polling message will appear based on the implementation of the network side. Therefore, the function of the fourth timer is mainly to periodically trigger the child node to respond to the polling message sent by the parent node, which is a non-prohibited type.
  • this embodiment includes the following steps:
  • the IAB parent node sends a polling message 1 (polling1) to the IAB child node.
  • the IAB child node After receiving the polling1 message, the IAB child node sends FCM1 to inform the IAB parent node of the current buffered data status; at the same time, the IAB child node starts the third timer; during the operation of the third timer, it will not trigger any flow control transmission information.
  • the IAB parent node again sends a polling message 2 (polling 2) to the IAB child node during the running of the third timer.
  • the IAB child node receives the polling 2 message, and since it is still in the third timer period, it does not send FCM.
  • the IAB child node sends FCM2 to the IAB parent node and starts a new third timer.
  • flow control messages are triggered progressively.
  • this embodiment includes the following steps.
  • the parent node of the IAB receives the FCM A message and adopts relatively low-level flow control measures to reduce data transmission to the child nodes of the IAB.
  • the IAB parent node receives the FCM B message and starts to take a higher degree of flow control measures to reduce the data transmission to the child nodes.
  • the event trigger condition is not reached after the second timer expires, for example, the amount of buffered data falls within the fourth threshold, and the fourth threshold is less than or equal to the second threshold.
  • the IAB child node sends a congestion resolved message to the IAB parent node.
  • the IAB parent node receives the congestion release message and considers that the IAB child node congestion warning is released.
  • the IAB child node sends a congestion release message to the IAB parent node.
  • the IAB parent node receives the congestion release message and considers that the child node congestion warning is released.
  • Fig. 7 is a schematic diagram of the implementation process of the flow control message transmission method according to the embodiment of the present application, which can be applied to the side of the second communication device (such as the IAB parent node). As shown in FIG. 7, the method 700 includes the following steps.
  • S702 Receive a flow control message, the flow control message is sent by the first communication device when a trigger condition is met, and the trigger condition is determined based on at least one of the following: the running condition of the timer, the buffered data condition, and the received Polling message.
  • the embodiment of the present application can determine whether the trigger condition is satisfied based on at least one of the running condition of the timer, the buffered data condition of the communication device, and the received polling message, and send the flow control when the trigger condition is satisfied. Message, communication equipment will not send flow control messages too frequently, saving signaling overhead.
  • the trigger condition includes: the first timer is not running, and the data buffered by the first communication device exceeds a first threshold.
  • the method further includes: receiving a congestion release message; wherein, the congestion release message is when the first communication device has finished running the first timer and the buffered data does not exceed Sent under the first threshold.
  • the method further includes: if the flow control message is not received again, determining that the congestion warning is released; or starting or restarting a fifth timer, and when the fifth timer has finished running If the flow control message is not received again, it is determined that the congestion warning is released.
  • the trigger condition includes: the data buffered by the first communication device exceeds a second threshold for the first time or exceeds the second threshold again; wherein, after the trigger condition is satisfied, If the data buffered by the first communication device exceeds the second threshold and does not exceed the third threshold, the trigger condition is not met, and the third threshold is higher than the second threshold.
  • the trigger condition further includes: the data buffered by the first communication device exceeds the third threshold.
  • the method further includes: receiving a congestion release message; wherein, the congestion release message is sent by the first communication device when the buffered data does not exceed a fourth threshold, so The fourth threshold is less than or equal to the second threshold.
  • the first threshold includes the data amount of cached data or the waiting time of cached data
  • the second threshold includes the data amount of cached data or the waiting time of cached data
  • the third threshold includes the data amount of the buffered data or the waiting time of the buffered data.
  • the method further includes: sending a polling message; periodically receiving multiple flow control messages, or receiving flow control messages and starting a third timer, and running on the third timer No flow control messages are received during this period.
  • the periodically receiving multiple flow control messages includes: starting a fourth timer after each flow control message is received, and receiving again after the fourth timer expires The flow control message.
  • the number of the multiple flow control messages is N; wherein, if the N flow control messages are received, the fourth timer is no longer started.
  • the polling message carries the N; wherein, the N is defined by a protocol or configured by a network device.
  • Fig. 8 is a schematic structural diagram of a communication device (for example, an IAB child node) according to an embodiment of the present application. As shown in FIG. 8, the communication device 800 includes the following modules.
  • the processing module 802 is configured to determine whether the trigger condition of the flow control message is satisfied based on at least one of the following: the running condition of the timer, the buffered data condition, and the received polling message.
  • the sending module 804 is configured to send the flow control message if the trigger condition is met.
  • the embodiment of the present application can determine whether the trigger condition is satisfied based on at least one of the running condition of the timer, the buffered data condition of the communication device, and the received polling message, and send the flow control when the trigger condition is satisfied. Message, communication equipment will not send flow control messages too frequently, saving signaling overhead.
  • the processing module 802 is configured to: if the first timer is not running and the buffered data exceeds the first threshold, determine that the trigger condition of the flow control message is satisfied.
  • the communication device 800 further includes a start module, configured to start or restart the first timer.
  • the sending module 804 is further configured to send a congestion release message if the buffered data does not exceed the first threshold when the first timer has finished running.
  • the processing module 802 is configured to determine that the trigger condition of the flow control message is satisfied if the buffered data exceeds the second threshold for the first time or exceeds the second threshold again; After the trigger condition of the flow control message, if the buffered data exceeds the second threshold and does not exceed the third threshold, the trigger condition is not met, and the third threshold is higher than the second threshold.
  • the processing module 802 is further configured to: if the buffered data exceeds the third threshold, determine that the trigger condition of the flow control message is satisfied.
  • the communication device 800 further includes a start module, configured to start or restart a second timer; wherein, the flow control message is not triggered during the operation of the second timer.
  • a start module configured to start or restart a second timer; wherein, the flow control message is not triggered during the operation of the second timer.
  • the sending module 804 is further configured to send a congestion release message if the buffered data does not exceed a fourth threshold; wherein, the fourth threshold is less than or equal to the second threshold .
  • the first threshold includes the data amount of cached data or the waiting time of cached data
  • the second threshold includes the data amount of cached data or the waiting time of cached data
  • the third threshold includes the data amount of the buffered data or the waiting time of the buffered data.
  • the sending module 804 is configured to: if a polling message is received, periodically send multiple flow control messages, or send a flow control message and start a third timer. The flow control message is not triggered during the running of the third timer.
  • the sending module 804 is configured to: start a fourth timer after each flow control message is sent, and send the flow control message again after the fourth timer expires.
  • the number of the multiple flow control messages is N; wherein, the sending module 804 is further configured to: if the N flow control messages are sent, no longer start the The fourth timer.
  • the N is carried in the polling message.
  • the terminal device 800 can refer to the process of the method 100 corresponding to the embodiment of the present application, and each unit/module in the terminal device 800 and the other operations and/or functions described above are used to implement the corresponding methods in the method 100.
  • Fig. 9 is a schematic structural diagram of a communication device (for example, an IAB parent node) according to an embodiment of the present application. As shown in FIG. 9, the communication device 900 includes the following modules.
  • the receiving module 902 is configured to receive a flow control message; wherein the flow control message is sent by the first communication device when a trigger condition is met, and the trigger condition is determined based on at least one of the following: operation of a timer Circumstances, buffered data conditions, polling messages received.
  • the embodiment of the present application can determine whether the trigger condition is satisfied based on at least one of the running condition of the timer, the buffered data condition of the communication device, and the received polling message, and send the flow control when the trigger condition is satisfied. Message, communication equipment will not send flow control messages too frequently, saving signaling overhead.
  • the trigger condition includes: the first timer is not running, and the data buffered by the first communication device exceeds a first threshold.
  • the receiving module 902 is further configured to receive a congestion release message; wherein, the congestion release message is when the first communication device has finished running the first timer and the buffered data has not Sent when the first threshold is exceeded.
  • the communication device 900 further includes a congestion warning release module, configured to: if the flow control message is not received again, determine that the congestion warning is released; or start or restart the fifth timer, In the case where the fifth timer ends, if the flow control message is not received again, it is determined that the congestion warning is released.
  • a congestion warning release module configured to: if the flow control message is not received again, determine that the congestion warning is released; or start or restart the fifth timer, In the case where the fifth timer ends, if the flow control message is not received again, it is determined that the congestion warning is released.
  • the trigger condition includes: the data buffered by the first communication device exceeds a second threshold for the first time or exceeds the second threshold again; wherein, after the trigger condition is satisfied, If the data buffered by the first communication device exceeds the second threshold and does not exceed the third threshold, the trigger condition is not met, and the third threshold is higher than the second threshold.
  • the trigger condition further includes: the data buffered by the first communication device exceeds the third threshold.
  • the receiving module 902 is further configured to receive a congestion release message; wherein, the congestion release message is sent by the first communication device when the buffered data does not exceed the fourth threshold,
  • the fourth threshold is less than or equal to the second threshold.
  • the first threshold includes the data amount of cached data or the waiting time of cached data
  • the second threshold includes the data amount of cached data or the waiting time of cached data
  • the third threshold includes the data amount of the buffered data or the waiting time of the buffered data.
  • the communication device 900 further includes a sending module for sending polling messages; the receiving module 902 is also used for: periodically receiving multiple flow control messages, or receiving flow control messages and starting the first Three timers, no flow control messages are received during the running of the third timer.
  • the receiving module 902 is configured to: start a fourth timer after each flow control message is received, and receive the flow control message again after the fourth timer expires.
  • the number of the multiple flow control messages is N; wherein, the receiving module 902 is configured to: if the N flow control messages are received, no longer start the fourth timing Device.
  • the polling message carries the N; wherein, the N is defined by a protocol or configured by a network device.
  • the terminal device 900 can refer to the process of the method 700 corresponding to the embodiment of the present application, and each unit/module in the terminal device 900 and the other operations and/or functions described above are used to implement the corresponding methods in the method 700.
  • FIG. 10 is a structural diagram of a network device applied in an embodiment of the present application, which can implement the details of the method embodiments shown in FIG. 1 to FIG. 7 and achieve the same effect.
  • the network device 1000 includes: a processor 1001, a transceiver 1002, a memory 1003, and a bus interface, where:
  • the network device 1000 further includes: a computer program that is stored in the memory 1003 and can run on the processor 1001, and the computer program is executed by the processor 1001 to implement the method shown in FIGS. 1 to 7 Example steps.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 1001 and various circuits of the memory represented by the memory 1003 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 1002 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on a transmission medium.
  • the processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1003 can store data used by the processor 1001 when performing operations.
  • the embodiment of the present application also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the computer program is executed by a processor, any one of the method embodiments shown in FIGS. 1 to 7 is implemented.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk, or optical disk, etc.
  • the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.
  • a terminal which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开了一种流控消息的传输方法和设备，用以解决相关技术中流控消息的触发条件不够完善，导致流控消息被频繁触发的问题。该方法可以由通信设备执行，所述方法包括：基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件；如果满足所述触发条件，则发送所述流控消息。

Description

流控消息的传输方法和设备
交叉引用
本申请要求在2020年03月30日提交中国专利局、申请号为202010238754.6、发明名称为“流控消息的传输方法和设备”的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种流控消息的传输方法和设备。
背景技术
在自回传(Integrated Access Backhaul，IAB)网络中，采用流控机制可以解决下行数据拥塞的问题。其中，下行数据拥塞是指IAB子节点从其IAB父节点收到的数据来不及发送给下游IAB节点或者终端设备而造成数据堆积。当IAB子节点的数据堆积到有缓存溢出风险时，会向其父节点发送流控反馈(Flow Control Feedback)，或者称流控消息(Flow Control Message，FCM)，以警示拥塞，接收到流控消息的IAB父节点会控制给该IAB子节点发送下行数据的传输速率。
相关技术中，当IAB子节点满足触发条件之后，就触发往IAB父节点的逐跳选项(Hop by Hop，HbH)进行流控消息的反馈，然而，该流控消息的触发条件不够完善，会导致流控消息被频繁触发。因此，有必要提供相关的方案来优化流控消息的触发和传输机制。
发明内容
本申请实施例的目的是提供一种流控消息的传输方法和设备，用以解决相关技术中流控消息的触发条件不够完善，导致流控消息被频繁触发的问题。
第一方面，提供了一种流控消息的传输方法，所述方法由第一通信设备执行，所述方法包括：基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件；如果满足所述触发条件，则发送所述流控消息。
第二方面，提供了一种流控消息的传输方法，所述方法由第二通信设备执行，所述方法包括：接收流控消息；其中，所述流控消息是第一通信设备在满足触发条件的情况下发送的，所述触发条件是基于如下至少之一确定的：定时器的运行情况，缓存数据情况，接收到的轮询消息。
第三方面，提供了一种通信设备，包括：处理模块，用于基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件；发送模块，用于如果满足所述触发条件，则发送所述流控消息。
第四方面，提供了一种通信设备，包括：接收模块，用于接收流控消息；其中，所述流控消息是第一通信设备在满足触发条件的情况下发送的，所述触发条件是基于如下至少之一确定的：定时器的运行情况，缓存数据情况，接收到的轮询消息。
第五方面，提供了一种通信设备，该通信设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第一方面和第二方面中任意一个方面所述的流控消息的传输方法的步骤。
第六方面，提供了一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如第一方面和第二方面中任意一个方面所述的流控消息的传输方法。
在本申请实施例中，可以基于定时器的运行情况、通信设备的缓存数据情况和接收到的轮询消息这三者的至少之一确定是否满足触发条件，并在满足触发条件的情况下发送流控消息，通信设备不会过于频繁地发送流控消息，节约信令开销。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的 不当限定。在附图中：
图1是根据本申请的一个实施例的流控消息的传输方法的示意性流程图；
图2是根据本申请的一个实施例的流控消息的传输方法的示意性流程图；
图3是根据本申请的一个实施例的流控消息的传输方法的示意性流程图；
图4是根据本申请的一个实施例的流控消息的传输方法的示意性流程图；
图5是根据本申请的一个实施例的流控消息的传输方法的示意性流程图；
图6是根据本申请的一个实施例的流控消息的传输方法的示意性流程图；
图7是根据本申请的一个实施例的流控消息的传输方法的示意性流程图；
图8是根据本申请的一个实施例的通信设备的结构示意图；
图9是根据本申请的另一个实施例的通信设备的结构示意图；
图10是根据本申请的一个实施例的网络设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。本说明书各个实施例中的“和/或”表示前后两者的至少之一。
应理解，本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)或全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、5G系统，或者说新无线(New Radio，NR)系统，自回传(Integrated Access Backhaul，IAB)系统，或者为后续演进通信系统。
在本申请实施例中，终端设备可以包括但不限于移动台(Mobile Station， MS)、移动终端(Mobile Terminal)、移动电话(Mobile Telephone)、用户设备(User Equipment，UE)、手机(handset)及便携设备(portable equipment)、车辆(vehicle)等，该终端设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，例如，终端设备可以是移动电话(或称为“蜂窝”电话)、具有无线通信功能的计算机等，终端设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
本申请实施例中，网络设备是一种部署在无线接入网中用以为终端设备提供无线通信功能的装置。所述网络设备可以为基站，所述基站可以包括各种形式的宏基站，微基站，中继站，接入点等。在采用不同的无线接入技术的系统中，具有基站功能的设备的名称可能会有所不同。例如在LTE网络中，称为演进的节点B(Evolved NodeB，eNB或eNodeB)，在第三代(3rd Generation，3G)网络中，称为节点B(Node B)，在5G系统中称为下一代节点B(gNB)，或者后续演进通信系统中的网络设备等等，然用词并不构成限制。
如图1所示，本申请的一个实施例提供一种流控消息的传输方法100，该方法可以由通信设备执行，换言之，该方法可以由安装在通信设备的软件或硬件来执行，该通信设备可以是IAB网络中的IAB子节点；也可以是中继节点(relay)，该方法100包括如下步骤。
S102：基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件。
该实施例中，定时器的运行情况例如包括：定时器正在运行；定时器没有运行。通信设备的缓存数据情况例如包括：通信设备缓存的数据量是否超出一定的数据量门限；通信设备缓存的数据的等待时间是否超出一定的时间门限，其中，缓存的数据的等待时间可以是最早缓存数据的等待时间，还可以是一定范围内(如全部)缓存的数据的平均等待时间。
在一个例子中，该实施例基于定时器的运行情况确定是否满足流控消息的触发条件，例如，定时器正在运行，则不满足触发条件。
在另一个例子中，该实施例基于定时器的运行情况和通信设备的缓存数据情况，确定是否满足流控消息的触发条件。例如，如果第一定时器没有运行，且缓存的数据超出第一门限，则确定满足流控消息的触发条件。可以理解，如果第一定时器正在运行或者缓存的数据没有超出第一门限，则不满足流控消息的触发条件。
在再一个例子中，该实施例基于通信设备的缓存数据情况，确定是否满足流控消息的触发条件。例如，如果通信设备缓存的数据第一次超出第二门限或再次超出所述第二门限，则确定满足流控消息的触发条件；其中，在确定满足流控消息的触发条件之后，如果缓存的数据超出所述第二门限且不超出第三门限，则不满足所述触发条件，所述第三门限高于所述第二门限。
在又一个例子中，该实施例基于接收到的轮询消息，确定是否满足流控消息的触发条件，例如，接收到轮询消息，则确定满足流控消息的触发条件。
在其他的例子中，还可以基于定时器的运行情况以及接收到的轮询消息，确定是否满足流控消息的触发条件。
S104：如果满足所述触发条件，则发送所述流控消息。
可以理解，该实施例中，如不满足上述触发条件，则直接结束流程。
可以理解，该实施例中，终端设备在发送流控消息之前，还可以生成(construct)该流控消息。
需要说明的是，本说明书各个实施例中提到的流控消息(Flow Control Message，FCM)还可以用其他的技术术语来替代，例如流控反馈(Flow Control Feedback)等。
本申请实施例提供的流控消息的传输方法，可以基于定时器的运行情况、通信设备的缓存数据情况和接收到的轮询消息这三者的至少之一确定是否满足触发条件，并在满足触发条件的情况下生成并发送流控消息，通信设备不会过于频繁地发送流控消息，节约信令开销。
可选地，作为一个实施例，实施例100的S102可以包括：如果第一定时 器没有运行，且缓存的数据超出第一门限，则确定满足流控消息的触发条件。可以理解，如果第一定时器正在运行或者缓存的数据没有超出第一门限，则不满足流控消息的触发条件。
该实施例中提到的缓存的数据超出第一门限，可以是缓存的数据的数据量超过第一门限(或称作第一数据量门限)，还可以是缓存的数据的等待时间超过第一门限(或称作第一时间门限)。
本说明书各个实施例中提到的定时器，包括第一定时器以及后文提到的第二定时器和第三定时器，基于这些定时器的实现功能，还可以用一些其他的技术术语来替代，例如，流控禁止定时器(FC prohibit timer)，延迟定时器(delay timer)等。
该实施例在确定满足流控消息的触发条件之后，还可以开启或重启上述第一定时器。其中，在该第一定时器的运行期间内不再触发生成流控消息，也即，在第一定时器的运行期间内不满足流控消息的触发条件。
可选地，在开启或重启所述第一定时器之后，所述方法还包括：在第一定时器运行结束的情况下，如果缓存的数据未超出所述第一门限，例如，小于或等于一定的预设门限(该预设门限低于或等于第一门限)，则向父节点或上游节点发送拥塞解除消息，便于通信设备的父节点或上游节点能够及时地了解通信设备的流控情况。
在其他的实施例中，在开启或重启所述第一定时器之后，无论第一定时器运行是否结束，如果缓存的数据未超出所述第一门限，例如，小于或等于一定的预设门限(该预设门限低于或等于第一门限)，则可以向父节点或上游节点发送拥塞解除消息。
可以理解，在第一定时器运行结束的情况下，如果缓存的数据仍然超出第一门限，则可以再次发送流控消息，并重启该第一定时器，在该第一定时器的运行期间不在触发流控消息。
上述实施例通过发送拥塞解除消息的方式，例如，在通信设备是IAB子 节点，其向IAB父节点发送拥塞解除消息，使得IAB父节点确定IAB子节点拥塞预警解除；在通信设备是中继节点时，其向上游中继节点或其它网络设备发送拥塞解除消息，使得上游中继节点或其它网络设备确定拥塞预警解除。
可选地，在其他的实施例中，在第一定时器运行结束的情况下，如果缓存的数据未超出所述第一门限，则无需发送拥塞解除消息。该实施例例如，在通信设备是IAB子节点时，其向IAB父节点发送流控消息后，IAB父节点启动第五定时器(该第五定时器可以和第一定时器的时长相同，也可以和第一定时器的时长不同)，如果IAB父节点在第五定时器运行结束时未再次收到流控消息，则确定拥塞预警解除。该实施例又例如，IAB子节点给IAB父节点发送流控消息后，IAB父节点收到该流控消息后采取流控措施，该流控措施配置完成之后，如果IAB父节点没有再次收到该IAB子节点的流控消息，则IAB父节点认为IAB子节点拥塞预警解除；如果IAB父节点再次收到该IAB子节点的流控消息，则再次采取流控措施。
该实施例无需执行拥塞解除消息发送和接收的操作，便于进一步节约信令开销，提高通信效率；同时，便于IAB父节点能够及时地了解IAB子节点的流控情况。
可选地，作为一个实施例，实施例100的S102可以包括：如果缓存的数据第一次超出第二门限或再次超出所述第二门限，则确定满足流控消息的触发条件；其中，在确定满足流控消息的触发条件之后，如果缓存的数据超出所述第二门限且不超出第三门限，则不满足所述触发条件，即不在触发生成流控消息，所述第三门限高于所述第二门限。
该实施例中提到的缓存的数据超出第二门限，可以是缓存的数据的数据量超过第二门限(或称作第二数据量门限)，还可以是缓存的数据的等待时间超过第二门限(或称作第二时间门限)；同理，缓存的数据不超出第三门限，可以是缓存的数据的数据量不超过第三门限(或称作第三数据量门限)，还可 以是缓存的数据的等待时间不超过第三门限(或称作第三时间门限)。
该实施例采用递进式的流控消息的触发和生成机制，通过设置多个不同(依次递增)的门限值，仅仅在缓存的数据超过这些门限的时刻发送流控消息，在缓存的数据处于两个相邻的门限之间时则不触发生成流控消息，同样可以避免流控消息被频繁触发，便于节约信令开销。
可选地，在上述实施例中，在发送流控消息后，如果缓存的数据继续增长，在缓存的数据超出所述第三门限的情况下，则确定满足流控消息的触发条件，再次发送流控消息，该流控消息用以警示通信设备的父节点或上游节点进一步降低下行流量。
该实施例中提到的缓存的数据超出第三门限，可以是缓存的数据的数据量超过第三门限(或称作第三数据量门限)，还可以是缓存的数据的等待时间超过第三门限(或称作第三时间门限)。
需要说明的是，该实施例提供的递进式的流控消息的触发和生成机制，虽然只介绍了第二门限和第三门限，实际上还可以设置更多的门限，例如，第五门限，等等，其中，第五门限大于第三门限。
这样，在缓存的数据超出所述第三门限且不超出第五门限时，则不满足所述触发条件，也即不在触发生成流控消息，直至缓存的数据超出第五门限的时刻再发送一条流控消息等等。
可选地，在上述实施例提供的递进式的流控消息的触发和生成机制还可以和定时器结合使用，这将构成另一实施例，也即，在缓存的数据超出上述第三门限，则确定满足流控消息的触发条件之后，还可以开启或重启第二定时器，其中，在该第二定时器的运行期间不触发流控消息，也即在该第二定时器的运行期间不满足流控消息的触发条件。
可选地，前文各个实施例介绍的递进式的流控消息的触发方法，还可以包括如下步骤：如果缓存的数据不超出第四门限，则发送拥塞解除消息；其中，所述第四门限小于或等于所述第二门限。
可选地，前文各个实施例中提到的第一门限可以是指缓存的数据的数据量或缓存的数据的等待时间；前文各个实施例中提到的第二门限包括缓存的数据的数据量或缓存的数据的等待时间；前文各个实施例中提到的第三门限包括缓存的数据的数据量或缓存的数据的等待时间；前文各个实施例中提到的第四门限包括缓存的数据的数据量或缓存的数据的等待时间。
这样，在前文各个实施例介绍的不超出或超出**门限(指第一门限至第四门限的至少之一)，具体可以是缓存的数据的数据量不超出或超出**门限，或者是缓存的数据的等待时间不超出或超出**门限。
可选地，实施例100提到的如果满足所述触发条件，则发送所述流控消息，包括如下步骤：如果接收到轮询消息，则可以执行以下1)和2)两者之一。
1)周期性地发送多个流控消息。该流控消息的发送和前文各个实施例可以是相互独立的进程。例如，即使在前文实施例提到的定时器(如第一定时器)的运行期间内，也可以发送该周期性的流控消息。
2)发送流控消息并启动第三定时器，在所述第三定时器运行期间不触发流控消息。该流控消息的发送方式和前文各个实施例可以结合，例如，在第三定时器运行期间，不再触发生成任何流控消息。
该实施例可以通过周期性发送流控消息的方式，可以避免流控消息被频繁触发，便于节约信令开销；或者，该实施例通过引入的第三定时器，也可以避免流控消息被频繁触发，便于节约信令开销。
可选地，作为一个实施例，所述周期性地发送多个流控消息，包括：每发送完一个所述流控消息后启动第四定时器，在所述第四定时器超时后再次发送流控消息。
可选地，作为一个实施例，所述多个流控消息的数量是N(N是大于或等于2的整数)；其中，如果发送完N个所述流控消息，则不再启动所述第四定时器。
可选地，作为一个实施例，N是所述轮询消息携带的，其中，N为协议(预)定义的或网络设备(预)配置的，发送轮询消息的父节点或上游节点可以获取得到。
为详细说明本申请上述各个实施例介绍的流控消息的传输方法，以下将结合几个具体的实施例进行介绍。
需要说明的是，以下几个实施例在介绍时是以IAB网络中的IAB子节点和IAB父节点为例进行介绍。可以理解，下述实施例同样适用于中继节点和其上游节点。
实施例一：
该实施例是基于事件触发的流控消息，具体是基于定时器的运行情况和缓存数据的情况的流控消息触发机制，如图2所示，该实施例包括如下步骤。
1、IAB子节点缓存的数据超出第一门限，满足流控消息的触发条件，见图2中的触发条件1(或称作trigger1)。
2、IAB子节点向IAB父节点发送流控消息1(FCM1)，并且开启第一定时器(FC prohibit timer)。
3、在第一定时器运行期间内，缓存的数据继续超出第一门限，见图2中的触发条件2(或称作trigger2)；由于在禁止触发期间(即第一定时器的限制)，因此不会触发流控消息的发送。
4、第一定时器超时，此时如果缓存的数据仍然超出第一门限，见图2中的触发条件3(或称作trigger3)，因此触发生成并发送流控消息2(FCM2)，并且重启第一定时器。
5、由FCM2开启的第一定时器超时，且此时缓存的数据未超出第一门限，即不会触发FCM3。
6、IAB父节点未接收到FCM3，认为子节点拥塞预警解除。
在实施例一的流控消息的触发条件不变的情况下，IAB子节点还可以采用发送拥塞解除消息的方式指示拥塞预警解除，如图3所示，有以下两种方 式。
方式一：
1、在第一定时器超时后，如果到达解除条件(例如，缓存的数据小于或等于第六门限，该第六门限小于或等于第一门限)。
2、IAB子节点向IAB父节点发送拥塞解除消息(congestion solved message)，见图3中的实线所示。
3、IAB父节点接收到拥塞解除消息，认为子节点拥塞预警解除。
方式二：
或者，如图3中虚线的拥塞解除消息所示。
1、无论第一定时器是否超时，当IAB子节点的缓存数据回退至一定的门限(例如，缓存的数据小于或等于第六门限，该第六门限小于或等于第一门限)以下，见图3中的触发条件4(或称作trigger4)，触发流控解除消息。
2、IAB子节点向IAB父节点发送流控解除消息，见图3虚线所示的拥塞解除消息消息。
3、父节点接收到拥塞解除消息，认为子节点拥塞预警解除。
实施例二：
基于轮询(Polling)触发的流控消息，且为周期触发。
如图4所示，该实施例包括如下步骤。
1、网络侧配置polling周期性触发次数N的值；具体可以配置给IAB父节点。
2、IAB父节点向IAB子节点发送轮询消息1(polling1)，该polling1消息包括N的值。
3、IAB子节点收到polling1消息后，周期发送N个流控消息(与基于实施例100的事件触发的机制无关，即无论当前是否有事件触发后开启的定时器，子节点在收到Polling后总是能直接触发流控消息)。
具体地，IAB子节点每发送完一个流控消息后都启动第四定时器，在第 四定时器超时后再次生成并发送流控消息。
当IAB子节点发送流控消息的次数达到N后，不再启动第四定时器。即总共触发N次流控消息，但是触发N-1次第四定时器。
该实施例中，由于Polling是网络侧配置，因此在实际应用中，不会出现父节点在周期性触发的polling消息没有结束时，再发送一个Polling消息指示子节点发送流控消息。即在第四定时器开启期间，基于网络侧的实现，不会出现另外的polling消息。所以该第四定时器的作用主要是周期性触发子节点响应父节点发出的polling消息，非禁止类型。
实施例三：
基于Polling触发的流控消息，单次触发发送。
如图5所示，该实施例包括如下步骤：
1、IAB父节点向IAB子节点发送轮询消息1(polling1)。
2、IAB子节点收到polling1消息后，发送FCM1，告知IAB父节点当前的缓存数据状况；同时，IAB子节点开启第三定时器；在第三定时器的运行期间不再触发发送任何流控消息。
3、IAB父节点在第三定时器运行期间再次向IAB子节点发送轮询消息2(polling 2)。
4、IAB子节点接收到polling 2消息，由于当前仍处在第三定时器计时期间，因此不发送FCM。
5、第三定时器超时，IAB子节点向IAB父节点发送FCM2，并且开启一个新的第三定时器。
实施例四
基于事件触发的流控消息，递进触发流控消息。
如图6所示，该实施例包括如下步骤。
1、IAB子节点缓存的数据第一次达到第二门限或者再次超过第二门限时，见图6中的“触发条件A”；此时发送FCM A，表示当前IAB子节点的拥塞 严重程度较轻。
2、IAB父节点收到FCM A消息，采取程度较低的流控措施，减少对IAB子节点的数据传输。
3、当IAB子节点的缓存数据值一直增长到大于第三门限时，见图6中的“触发条件B”；此时发送FCM B，表示当前IAB子节点的拥塞程度较为严重；同时开启第二定时器。
4、IAB父节点收到FCM B消息，开始采取程度较高的流控措施，减少对子节点的数据传输。
该实施例四指示拥塞预警解除方式一：
1、在第二定时器超时后未达到事件触发条件，例如，缓存的数据量降到第四门限以内，第四门限小于或等于第二门限。
2、IAB子节点向IAB父节点发送拥塞解除消息(congestion solved message)。
3、IAB父节点接收到拥塞解除消息，认为IAB子节点拥塞预警解除。
该实施例四指示拥塞预警解除方式二：
或者如图6中虚线拥塞解除消息(congestion solved message)所示。
1、无论第二定时器是否超时，当IAB子节点的缓存数据回退至第四门限(第四门限小于或等于第二门限)以下，见图6中的“触发条件C”；触发拥塞解除消息。
2、IAB子节点向IAB父节点发送拥塞解除消息。
3、IAB父节点接收到拥塞解除消息，认为子节点拥塞预警解除。
以上结合图1至图6详细描述了根据本申请实施例的流控消息的传输方法。下面将结合图7详细描述根据本申请另一实施例的流控消息的传输方法。可以理解的是，该实施例与图1所示的方法中的通信设备侧的描述相同，为避免重复，适当省略相关描述。
图7是本申请实施例的流控消息的传输方法实现流程示意图，可以应用 在第二通信设备(如IAB父节点)侧。如图7所示，该方法700包括如下步骤。
S702：接收流控消息，该流控消息是第一通信设备在满足触发条件的情况下发送的，该触发条件是基于如下至少之一确定的：定时器的运行情况，缓存数据情况，接收到的轮询消息。
本申请实施例提可以基于定时器的运行情况、通信设备的缓存数据情况和接收到的轮询消息这三者的至少之一确定是否满足触发条件，并在满足触发条件的情况下发送流控消息，通信设备不会过于频繁地发送流控消息，节约信令开销。
可选地，作为一个实施例，所述触发条件包括：第一定时器没有运行，且所述第一通信设备缓存的数据超出第一门限。
可选地，作为一个实施例，所述方法还包括：接收拥塞解除消息；其中，所述拥塞解除消息是所述第一通信设备在所述第一定时器运行结束、且缓存的数据未超出所述第一门限的情况下发送的。
可选地，作为一个实施例，所述方法还包括：如果未再次接收到所述流控消息，则确定拥塞预警解除；或者启动或重启第五定时器，在所述第五定时器运行结束的情况下，如果未再次收到所述流控消息，则确定拥塞预警解除。
可选地，作为一个实施例，所述触发条件包括：所述第一通信设备缓存的数据第一次超出第二门限或再次超出所述第二门限；其中，在满足所述触发条件之后，如果所述第一通信设备缓存的数据超出所述第二门限且不超出第三门限，则不满足所述触发条件，所述第三门限高于所述第二门限。
可选地，作为一个实施例，所述触发条件还包括：所述第一通信设备缓存的数据超出所述第三门限。
可选地，作为一个实施例，所述方法还包括：接收拥塞解除消息；其中，所述拥塞解除消息是所述第一通信设备在缓存的数据不超出第四门限的情况 下发送的，所述第四门限小于或等于所述第二门限。
可选地，作为一个实施例，所述第一门限包括缓存的数据的数据量或缓存的数据的等待时间；所述第二门限包括缓存的数据的数据量或缓存的数据的等待时间；所述第三门限包括缓存的数据的数据量或缓存的数据的等待时间。
可选地，作为一个实施例，所述方法还包括：发送轮询消息；周期性地接收多个流控消息，或接收流控消息并启动第三定时器，在所述第三定时器运行期间不接收流控消息。
可选地，作为一个实施例，所述周期性地接收多个流控消息，包括：每接收完一个所述流控消息后启动第四定时器，在所述第四定时器超时后再次接收所述流控消息。
可选地，作为一个实施例，所述多个流控消息的数量是N；其中，如果接收完N个所述流控消息，则不再启动所述第四定时器。
可选地，作为一个实施例，所述轮询消息中携带所述N；其中，所述N为协议定义的或网络设备配置的。
以上结合图1至图7详细描述了根据本申请实施例的流控消息的传输方法。下面将结合图8详细描述根据本申请实施例的通信设备。
图8是根据本申请实施例的通信设备(例如，IAB子节点)的结构示意图。如图8所示，通信设备800包括如下模块。
处理模块802，用于基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件。
发送模块804，用于如果满足所述触发条件，则发送所述流控消息。
本申请实施例提可以基于定时器的运行情况、通信设备的缓存数据情况和接收到的轮询消息这三者的至少之一确定是否满足触发条件，并在满足触发条件的情况下发送流控消息，通信设备不会过于频繁地发送流控消息，节约信令开销。
可选地，作为一个实施例，处理模块802，用于：如果第一定时器没有运行，且缓存的数据超出第一门限，则确定满足流控消息的触发条件。
可选地，作为一个实施例，所述通信设备800还包括启动模块，用于：开启或重启所述第一定时器。
可选地，作为一个实施例，所述发送模块804，还用于：在所述第一定时器运行结束的情况下，如果缓存的数据未超出所述第一门限，则发送拥塞解除消息。
可选地，作为一个实施例，处理模块802，用于如果缓存的数据第一次超出第二门限或再次超出所述第二门限，则确定满足流控消息的触发条件；其中，在确定满足流控消息的触发条件之后，如果缓存的数据超出所述第二门限且不超出第三门限，则不满足所述触发条件，所述第三门限高于所述第二门限。
可选地，作为一个实施例，处理模块802，还用于：如果缓存的数据超出所述第三门限，则确定满足流控消息的触发条件。
可选地，作为一个实施例，所述通信设备800还包括启动模块，用于开启或重启第二定时器；其中，在所述第二定时器的运行期间不触发流控消息。
可选地，作为一个实施例，所述发送模块804，还用于：如果缓存的数据不超出第四门限，则发送拥塞解除消息；其中，所述第四门限小于或等于所述第二门限。
可选地，作为一个实施例，所述第一门限包括缓存的数据的数据量或缓存的数据的等待时间；所述第二门限包括缓存的数据的数据量或缓存的数据的等待时间；所述第三门限包括缓存的数据的数据量或缓存的数据的等待时间。
可选地，作为一个实施例，所述发送模块804，用于：如果接收到轮询消息，则周期性地发送多个流控消息，或发送流控消息并启动第三定时器，在所述第三定时器运行期间不触发流控消息。
可选地，作为一个实施例，所述发送模块804，用于：每发送完一个所述流控消息后启动第四定时器，在所述第四定时器超时后再次发送流控消息。
可选地，作为一个实施例，所述多个流控消息的数量是N；其中，所述发送模块804，还用于：如果发送完N个所述流控消息，则不再启动所述第四定时器。
可选地，作为一个实施例，所述N是所述轮询消息中携带的。
根据本申请实施例的终端设备800可以参照对应本申请实施例的方法100的流程，并且，该终端设备800中的各个单元/模块和上述其他操作和/或功能分别为了实现方法100中的相应流程，并且能够达到相同或等同的技术效果，为了简洁，在此不再赘述。
图9是根据本申请实施例的通信设备(例如，IAB父节点)的结构示意图。如图9所示，通信设备900包括如下模块。
接收模块902，用于接收流控消息；其中，所述流控消息是第一通信设备在满足触发条件的情况下发送的，所述触发条件是基于如下至少之一确定的：定时器的运行情况，缓存数据情况，接收到的轮询消息。
本申请实施例提可以基于定时器的运行情况、通信设备的缓存数据情况和接收到的轮询消息这三者的至少之一确定是否满足触发条件，并在满足触发条件的情况下发送流控消息，通信设备不会过于频繁地发送流控消息，节约信令开销。
可选地，作为一个实施例，所述触发条件包括：第一定时器没有运行，且所述第一通信设备缓存的数据超出第一门限。
可选地，作为一个实施例，接收模块902，还用于接收拥塞解除消息；其中，所述拥塞解除消息是所述第一通信设备在所述第一定时器运行结束、且缓存的数据未超出所述第一门限的情况下发送的。
可选地，作为一个实施例，通信设备900还包括拥塞预警解除模块，用于：如果未再次接收到所述流控消息，则确定拥塞预警解除；或者启动或重 启第五定时器，在所述第五定时器运行结束的情况下，如果未再次收到所述流控消息，则确定拥塞预警解除。
可选地，作为一个实施例，所述触发条件包括：所述第一通信设备缓存的数据第一次超出第二门限或再次超出所述第二门限；其中，在满足所述触发条件之后，如果所述第一通信设备缓存的数据超出所述第二门限且不超出第三门限，则不满足所述触发条件，所述第三门限高于所述第二门限。
可选地，作为一个实施例，所述触发条件还包括：所述第一通信设备缓存的数据超出所述第三门限。
可选地，作为一个实施例，接收模块902，还用于接收拥塞解除消息；其中，所述拥塞解除消息是所述第一通信设备在缓存的数据不超出第四门限的情况下发送的，所述第四门限小于或等于所述第二门限。
可选地，作为一个实施例，所述第一门限包括缓存的数据的数据量或缓存的数据的等待时间；所述第二门限包括缓存的数据的数据量或缓存的数据的等待时间；所述第三门限包括缓存的数据的数据量或缓存的数据的等待时间。
可选地，作为一个实施例，通信设备900还包括发送模块，用于发送轮询消息；接收模块902，还用于：周期性地接收多个流控消息，或接收流控消息并启动第三定时器，在所述第三定时器运行期间不接收流控消息。
可选地，作为一个实施例，接收模块902，用于：每接收完一个所述流控消息后启动第四定时器，在所述第四定时器超时后再次接收所述流控消息。
可选地，作为一个实施例，所述多个流控消息的数量是N；其中，接收模块902，用于：如果接收完N个所述流控消息，则不再启动所述第四定时器。
可选地，作为一个实施例，所述轮询消息中携带所述N；其中，所述N为协议定义的或网络设备配置的。
根据本申请实施例的终端设备900可以参照对应本申请实施例的方法 700的流程，并且，该终端设备900中的各个单元/模块和上述其他操作和/或功能分别为了实现方法700中的相应流程，并且能够达到相同或等同的技术效果，为了简洁，在此不再赘述。
本说明书中的各个实施例采用递进的方式描述，每个实施例重点说明的通常是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。对于设备实施例而言，由于其与方法实施例基本相似，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
此外，在说明书和权利要求书中使用术语“第一”、“第二”和“第三”等来区分不同的定时器，并且这些术语不必描述次序或时间顺序。应当理解，这样使用的术语在适当的环境下是可交换的，并且本文所描述的发明的实施方案能够以本文所描述或说明的次序之外的其它次序来操作。
请参阅图10，图10是本申请实施例应用的网络设备的结构图，能够实现图1至图7所示的方法实施例的细节，并达到相同的效果。如图10所示，网络设备1000包括：处理器1001、收发机1002、存储器1003和总线接口，其中：
在本申请实施例中，网络设备1000还包括：存储在存储器上1003并可在处理器1001上运行的计算机程序，计算机程序被处理器1001、执行时实现图1至图7所示的方法实施例的步骤。
在图10中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1001代表的一个或多个处理器和存储器1003代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1002可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器1001负责管理总线架构和通常的处理，存储器1003可以存储处理器1001在执行操作时所使用的数据。
本申请实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述图1至图7所示的方法实施例中任意一个方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (29)

  1. 一种流控消息的传输方法，所述方法由第一通信设备执行，所述方法包括：
    基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件；
    如果满足所述触发条件，则发送所述流控消息。
  2. 根据权利要求1所述的方法，其中，所述基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件，包括：
    如果第一定时器没有运行，且缓存的数据超出第一门限，则确定满足流控消息的触发条件。
  3. 根据权利要求2所述的方法，其中，所述确定满足流控消息的触发条件之后，所述方法还包括：
    开启或重启所述第一定时器。
  4. 根据权利要求3所述的方法，其中，开启或重启所述第一定时器之后，所述方法还包括：
    在所述第一定时器运行结束的情况下，如果缓存的数据未超出所述第一门限，则发送拥塞解除消息。
  5. 根据权利要求1所述的方法，其中，所述基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件，包括：
    如果缓存的数据第一次超出第二门限或再次超出所述第二门限，则确定满足流控消息的触发条件；
    其中，在确定满足流控消息的触发条件之后，如果缓存的数据超出所述第二门限且不超出第三门限，则不满足所述触发条件，所述第三门限高于所 述第二门限。
  6. 根据权利要求5所述的方法，其中，所述基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件，还包括：
    如果缓存的数据超出所述第三门限，则确定满足流控消息的触发条件。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    开启或重启第二定时器；
    其中，在所述第二定时器的运行期间不触发流控消息。
  8. 根据权利要求5至7任一项所述的方法，其中，所述方法还包括：
    如果缓存的数据不超出第四门限，则发送拥塞解除消息；
    其中，所述第四门限小于或等于所述第二门限。
  9. 根据权利要求2或5所述的方法，其中，
    所述第一门限包括缓存的数据的数据量或缓存的数据的等待时间；
    所述第二门限包括缓存的数据的数据量或缓存的数据的等待时间；
    所述第三门限包括缓存的数据的数据量或缓存的数据的等待时间。
  10. 根据权利要求1所述的方法，其中，所述如果满足所述触发条件，则发送所述流控消息，包括：
    如果接收到轮询消息，则
    周期性地发送多个流控消息，或
    发送流控消息并启动第三定时器，在所述第三定时器运行期间不触发流控消息。
  11. 根据权利要求10所述的方法，其中，所述周期性地发送多个流控消息，包括：
    每发送完一个所述流控消息后启动第四定时器，在所述第四定时器超时后再次发送流控消息。
  12. 根据权利要求11所述的方法，其中，所述多个流控消息的数量是N； 其中，如果发送完N个所述流控消息，则不再启动所述第四定时器。
  13. 根据权利要求12所述的方法，其中，所述N是所述轮询消息中携带的。
  14. 一种流控消息的传输方法，所述方法由第二通信设备执行，所述方法包括：
    接收流控消息；
    其中，所述流控消息是第一通信设备在满足触发条件的情况下发送的，所述触发条件是基于如下至少之一确定的：定时器的运行情况，缓存数据情况，接收到的轮询消息。
  15. 根据权利要求14所述的方法，其中，所述触发条件包括：
    第一定时器没有运行，且所述第一通信设备缓存的数据超出第一门限。
  16. 根据权利要求15所述的方法，其中，所述方法还包括：
    接收拥塞解除消息；
    其中，所述拥塞解除消息是所述第一通信设备在所述第一定时器运行结束、且缓存的数据未超出所述第一门限的情况下发送的。
  17. 根据权利要求15所述的方法，其中，所述方法还包括：
    如果未再次接收到所述流控消息，则确定拥塞预警解除；或者
    启动或重启第五定时器，在所述第五定时器运行结束的情况下，如果未再次收到所述流控消息，则确定拥塞预警解除。
  18. 根据权利要求14所述的方法，其中，所述触发条件包括：
    所述第一通信设备缓存的数据第一次超出第二门限或再次超出所述第二门限；
    其中，在满足所述触发条件之后，如果所述第一通信设备缓存的数据超出所述第二门限且不超出第三门限，则不满足所述触发条件，所述第三门限高于所述第二门限。
  19. 根据权利要求18所述的方法，其中，所述触发条件还包括：
    所述第一通信设备缓存的数据超出所述第三门限。
  20. 根据权利要求18或19所述的方法，其中，所述方法还包括：
    接收拥塞解除消息；
    其中，所述拥塞解除消息是所述第一通信设备在缓存的数据不超出第四门限的情况下发送的，所述第四门限小于或等于所述第二门限。
  21. 根据权利要求15或18所述的方法，其中，
    所述第一门限包括缓存的数据的数据量或缓存的数据的等待时间；
    所述第二门限包括缓存的数据的数据量或缓存的数据的等待时间；
    所述第三门限包括缓存的数据的数据量或缓存的数据的等待时间。
  22. 根据权利要求14所述的方法，其中，所述方法还包括：
    发送轮询消息；
    周期性地接收多个流控消息，或
    接收流控消息并启动第三定时器，在所述第三定时器运行期间不接收流控消息。
  23. 根据权利要求22所述的方法，其中，所述周期性地接收多个流控消息，包括：
    每接收完一个所述流控消息后启动第四定时器，在所述第四定时器超时后再次接收所述流控消息。
  24. 根据权利要求23所述的方法，其中，所述多个流控消息的数量是N；其中，如果接收完N个所述流控消息，则不再启动所述第四定时器。
  25. 根据权利要求24所述的方法，其中，所述轮询消息中携带所述N；其中，所述N为协议定义的或网络设备配置的。
  26. 一种通信设备，包括：
    处理模块，用于基于如下至少之一：定时器的运行情况，缓存数据情况，接收到的轮询消息，确定是否满足流控消息的触发条件；
    发送模块，用于如果满足所述触发条件，则发送所述流控消息。
  27. 一种通信设备，包括：
    接收模块，用于接收流控消息；
    其中，所述流控消息是第一通信设备在满足触发条件的情况下发送的，所述触发条件是基于如下至少之一确定的：定时器的运行情况，缓存数据情况，接收到的轮询消息。
  28. 一种通信设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至25中任一项所述的流控消息的传输方法。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至25中任一项所述的流控消息的传输方法。
PCT/CN2021/083996 2020-03-30 2021-03-30 流控消息的传输方法和设备 Ceased WO2021197331A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010238754.6 2020-03-30
CN202010238754.6A CN113472492B (zh) 2020-03-30 2020-03-30 流控消息的传输方法和设备

Publications (1)

Publication Number Publication Date
WO2021197331A1 true WO2021197331A1 (zh) 2021-10-07

Family

ID=77866192

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/083996 Ceased WO2021197331A1 (zh) 2020-03-30 2021-03-30 流控消息的传输方法和设备

Country Status (2)

Country Link
CN (1) CN113472492B (zh)
WO (1) WO2021197331A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114827033A (zh) * 2022-04-15 2022-07-29 咪咕文化科技有限公司 数据流控方法、装置、设备与计算机可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101123573A (zh) * 2006-08-09 2008-02-13 普天信息技术研究院 在高速下行链路分组接入网络中分组数据单元的流控方法
US20150172198A1 (en) * 2013-12-18 2015-06-18 Marvell Israel (M.I.S.L) Ltd. Methods and network device for oversubscription handling
CN110366206A (zh) * 2018-03-26 2019-10-22 华为技术有限公司 一种信息传输方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127713B (zh) * 2007-09-05 2011-04-06 华为技术有限公司 通用流量控制装置及流量控制方法
CN101453758A (zh) * 2007-11-30 2009-06-10 华为技术有限公司 在通用接入网络实现流控管理的方法、设备及相应的系统
CN101534242B (zh) * 2008-03-11 2012-05-23 大唐移动通信设备有限公司 流量控制方法、系统和设备
CN102739510B (zh) * 2011-04-15 2016-07-27 中兴通讯股份有限公司 一种流控方法和装置
CN106612238B (zh) * 2015-10-21 2020-11-27 阿里巴巴集团控股有限公司 流量控制方法、装置和系统
CN110856222B (zh) * 2018-08-20 2022-06-28 华为技术有限公司 一种流量控制的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101123573A (zh) * 2006-08-09 2008-02-13 普天信息技术研究院 在高速下行链路分组接入网络中分组数据单元的流控方法
US20150172198A1 (en) * 2013-12-18 2015-06-18 Marvell Israel (M.I.S.L) Ltd. Methods and network device for oversubscription handling
CN110366206A (zh) * 2018-03-26 2019-10-22 华为技术有限公司 一种信息传输方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114827033A (zh) * 2022-04-15 2022-07-29 咪咕文化科技有限公司 数据流控方法、装置、设备与计算机可读存储介质
CN114827033B (zh) * 2022-04-15 2024-04-19 咪咕文化科技有限公司 数据流控方法、装置、设备与计算机可读存储介质

Also Published As

Publication number Publication date
CN113472492B (zh) 2023-04-07
CN113472492A (zh) 2021-10-01

Similar Documents

Publication Publication Date Title
US12484108B2 (en) Method for configuring DRX parameter for Sidelink, and terminal device
EP3742671B1 (en) Method and apparatus for acquiring link quality
CN112005613B (zh) 确定远程单元行为参数
RU2578666C2 (ru) Уменьшение избыточной сигнализации при переходах между состояниями управления радиоресурсами (rrc)
CN111512674B (zh) 一种传输数据的方法、终端设备和网络设备
WO2020019187A1 (zh) 一种信道监听方法及装置、终端设备、网络设备
CN113273246B (zh) 无线通信的方法、终端设备、接入网设备和核心网设备
RU2612609C2 (ru) Таймер индикации предпочтительного энергопотребления
KR102240644B1 (ko) 데이터 전송/수신 장치 및 방법, 및 통신 시스템
CN113196858B (zh) 用于发送释放辅助指示消息的方法及设备
WO2021031022A1 (zh) 链路切换的方法和通信设备
JP2015109698A (ja) パケット・モバイル通信システムにおける過負荷制御
WO2022205239A1 (zh) 边链路非连续接收命令的触发方法、装置和系统
CN113708889A (zh) 数据传输方法和设备
CN117121625A (zh) 侧链路不连续接收流程
CN111182581B (zh) 流控方法、目标节点、节点及施主节点
WO2010054544A1 (zh) 一种移动通讯分组域演进系统中寻呼的方法
JP2021510029A (ja) ビーム障害回復の構成方法、装置及び通信システム
WO2022126370A1 (en) Method and apparatus for multicast and broadcast services
CN116686329A (zh) 信号的发送和接收方法、装置和通信系统
WO2021197331A1 (zh) 流控消息的传输方法和设备
WO2020228821A1 (zh) 管理链路的方法和装置
WO2015165069A1 (zh) 用于传输下行数据的方法、移动性管理网元、接入网设备和服务网关
WO2020007232A1 (zh) 过载控制方法和装置
CN114466377B (zh) 网络实体通信方法及其相关无线通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21781343

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21781343

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 22.02.2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21781343

Country of ref document: EP

Kind code of ref document: A1