Search

CN-122002556-A - Time domain scheduling method, device and system

CN122002556ACN 122002556 ACN122002556 ACN 122002556ACN-122002556-A

Abstract

A time domain scheduling method, device and system belong to the technical field of communication. The method comprises the steps that a control node in a FTTR network receives an alarm message sent by a first network node when the first network node does not receive a scheduling message sent by the control node within a timeout period after sending the service information, the service information is information of service data which needs to be transmitted through an air interface by the first network node, the FTTR network comprises at least one network node, the first network node is any network node in the at least one network node, the scheduling message is sent based on the service information, and the scheduling message is used for indicating the air interface resources distributed to the first network node. The application can improve the sending efficiency in the network and is used for FTTR networks.

Inventors

  • QIU HAO
  • WU XUMING
  • WEI FENG

Assignees

  • 华为技术有限公司

Dates

Publication Date
20260508
Application Date
20241129
Priority Date
20241104

Claims (18)

  1. 1. A time domain scheduling method, the method being performed by a first network node, the first network node being any one of at least one network node in a fiber to room FTTR network, the method comprising: transmitting service information to a control node in the FTTR network, wherein the service information is information of service data which needs to be transmitted through an air interface by the first network node; And if the scheduling message sent by the control node is not received within the timeout period after the service information is sent, sending an alarm message to the control node, wherein the scheduling message is sent based on the service information and is used for indicating the air interface resource allocated to the first network node.
  2. 2. The method of claim 1, wherein prior to sending traffic information to a control node in the FTTR network, the method further comprises: Receiving a configuration message sent by the control node and used for indicating the timeout duration; and determining the timeout duration according to the configuration message.
  3. 3. The method according to claim 1 or 2, characterized in that the method further comprises: receiving a report request message sent by the control node, wherein the report request message is used for requesting the network node to report the timeout duration to the control node; And sending a time length report message for indicating the time-out time length to the control node according to the report request message.
  4. 4. The method of claim 3, wherein prior to said sending traffic information to a control node in said FTTR network, said method further comprises receiving a configuration message sent by said control node indicating said timeout period; the configuration message, the report request message and the duration report message have the same structure; And the S bit in the configuration message, the report request message and the time length report message is used for indicating the type of the message, wherein S is more than or equal to 1.
  5. 5. The method of claim 4, wherein the status value of the S-th bit in the long report message is the same as the status value of the S-th bit in the configuration message or the report request message.
  6. 6. The method of claim 4 or 5, wherein the configuration message, the report request message, and the duration report message each include a message length and a processing requirement field, and the S-th bit is a 2-th bit in the message length and processing requirement field.
  7. 7. The method of any one of claims 1 to 6, wherein the timeout period is a first period, the method further comprising: Receiving an update message sent by the control node, wherein the update message is used for indicating that the timeout duration is updated to a second duration, and the first duration is different from the second duration; And updating the timeout duration from the first duration to the second duration according to the update message.
  8. 8. A time domain scheduling method, the method performed by a control node in a fiber to room FTTR network, the method comprising: The method comprises the steps of receiving alarm information sent by a first network node when a scheduling message sent by a control node is not received within a timeout period after service information is sent, wherein the service information is information of service data which is needed to be transmitted by the first network node through an air interface, the FTTR network comprises at least one network node, the first network node is any network node in the at least one network node, the scheduling message is sent based on the service information, and the scheduling message is used for indicating the air interface resources distributed to the first network node.
  9. 9. The method of claim 8, further comprising receiving traffic information sent by the first network node prior to receiving the alert message.
  10. 10. The method according to claim 8 or 9, characterized in that the method further comprises: and before receiving the alarm message, sending a configuration message for indicating the timeout duration to the first network node.
  11. 11. The method according to any one of claims 8 to 10, further comprising: sending a report request message to the first network node, where the report request message is used to request the first network node to report the timeout duration to the control node; And receiving a time length report message which is sent by the first network node according to the report request message and used for indicating the time-out time length.
  12. 12. The method of claim 11, further comprising, prior to receiving the alert message, sending a configuration message to the first network node indicating the timeout period; the configuration message, the report request message and the duration report message have the same structure; And the S bit in the configuration message, the report request message and the time length report message is used for indicating the type of the message, wherein S is more than or equal to 1.
  13. 13. The method of claim 12, wherein the status value of the S-th bit in the long report message is the same as the status value of the S-th bit in the configuration message or the report request message.
  14. 14. The method of claim 12 or 13, wherein the configuration message, the report request message, and the duration report message each include a message length and a processing requirement field, and the S-th bit is a 2-th bit in the message length and processing requirement field.
  15. 15. The method of any one of claims 8 to 14, wherein the timeout period is a first period, the method further comprising: And sending an update message to the first network node, wherein the update message is used for indicating that the timeout duration is updated to be a second duration, and the first duration is different from the second duration.
  16. 16. A time domain scheduling device, wherein the time domain scheduling device belongs to a first network node, the first network node is any network node in at least one network node in a fiber-to-room FTTR network, the time domain scheduling device comprises: A first sending module, configured to send service information to a control node in the FTTR network, where the service information is information of service data that needs to be transmitted by the first network node through an air interface; And the second sending module is used for sending an alarm message to the control node if the scheduling message sent by the control node is not received within the timeout period after the service information is sent, wherein the scheduling message is sent based on the service information and is used for indicating the air interface resource distributed to the first network node.
  17. 17. A time domain scheduler, the time domain scheduler belonging to a control node in a fiber-to-room FTTR network, the time domain scheduler comprising: The control node comprises a first receiving module, a first scheduling module and a second receiving module, wherein the first receiving module is used for receiving an alarm message sent by a first network node when a scheduling message sent by the control node is not received within a timeout period after service information is sent, the service information is information of service data which is needed to be transmitted by the first network node through an air interface, the FTTR network comprises at least one network node, the first network node is any network node in the at least one network node, the scheduling message is sent based on the service information, and the scheduling message is used for indicating the air interface resource distributed to the first network node.
  18. 18. A time domain scheduling system comprising a control node in a fiber to room FTTR network and at least one network node in the FTTR network; a first network node for performing the time domain scheduling method of any one of claims 1 to 7, the first network node being any one of the at least one network node; the control node is configured to perform the time domain scheduling method of any one of claims 8 to 15.

Description

Time domain scheduling method, device and system The present application claims priority from chinese patent application with application number 202411567257.5, application name "time domain scheduling method, apparatus and system", whose entire contents are incorporated herein by reference, at 11/04 of 2024. Technical Field The present application relates to the field of communications technologies, and in particular, to a time domain scheduling method, apparatus, and system. Background Currently, in a fiber-in-room (fiber to the room, FTTR) network, individual slave FTTR devices (sub FTTR unit, SFU) share air interface resources. The SFU may contend for the channel in the air interface resource to obtain a transmission opportunity. However, with the development of communication technology, the number of SFUs is increasing, and the probability that multiple SFUs compete for channels at the same time is also increasing. Multiple SFUs compete for channels at the same time and may generate random backoff collision, resulting in packet failure, reduced network throughput, and increased service delay. Therefore, how to avoid random back-off collision of the air interface, it is worth researching to improve the transmission efficiency in the network. Disclosure of Invention The time domain scheduling method, the time domain scheduling device and the time domain scheduling system are beneficial to avoiding random back-off conflict of an air interface and improving the transmission efficiency in a network. In a first aspect, the application provides a time domain scheduling method, which is executed by a control node in FTTR networks, wherein the method comprises the steps that the control node receives an alarm message sent by a first network node, the first network node is used for sending the alarm message when the control node does not receive a scheduling message sent by the control node within a timeout period after sending service information, the service information is information of service data which needs to be transmitted by the first network node through an air interface, the FTTR networks comprise at least one network node, the first network node is any network node in the at least one network node, the scheduling message is sent based on the service information, and the scheduling message is used for indicating air interface resources allocated to the first network node. Optionally, the control node may also receive the service information before receiving the alarm message, which may be caused by a link failure or the like. The at least one network node may each send traffic information to the control node. In the embodiment of the present application, the control node may start receiving service information sent by the network node, after receiving the service information sent by each network node, the control node may perform centralized scheduling on the at least one network node to determine an air interface resource allocated to each network node, and finally send a scheduling message to each network node, so as to indicate the air interface resource to the first network node through the scheduling message, so that the first network node may conveniently compete for an air interface (an air interface is a channel, so that the competing air interface is a competing channel) on the air interface resource, and transmit data on the competing air interface. When the at least one network node includes a plurality of network nodes, the air interface resources allocated by different network nodes may be the same or different, which is not limited in the embodiment of the present application. For example, the time and/or frequency domains of the air interface resources allocated by at least two network nodes are different. It can be seen that, the air interface resources of the network node competing for the air interface are allocated by the control node, and centralized control on the at least one network node can be realized by the control node, so that the scheduling message sent by the control node indicates each network node to compete for the air interface on the corresponding air interface resources, and then after competing for the air interface, data is transmitted on the competing air interface. In this way, the control node can control the sequence of the network node transmitting data, which is beneficial to avoiding random back-off conflict between the network nodes, reducing interference between air interfaces of the network nodes, improving air interface efficiency, reducing retransmission rate, reducing time delay and improving throughput. It will be appreciated that the time interval between the network node sending traffic information and receiving the scheduling message is typically not too long (e.g. the above-mentioned timeout period is not exceeded). Therefore, if the first network node does not receive the scheduling message within the timeout period after sending the service in