WO-2026092115-A1 - TIME DOMAIN SCHEDULING METHOD, APPARATUS AND SYSTEM

WO2026092115A1WO 2026092115 A1WO2026092115 A1WO 2026092115A1WO-2026092115-A1

Abstract

A time domain scheduling method, apparatus and system, relating to the technical field of communications. The method comprises: a control node in an FTTR network receives an alarm message sent by a first network node when a scheduling message sent by the control node is not received within a timeout duration after service information is sent, wherein the service information is information of service data that needs to be transmitted by the first network node by means of an air interface; the FTTR network comprises at least one network node, and the first network node is any one of the at least one network node; and the scheduling message is sent on the basis of the service information, and the scheduling message is used for indicating an air interface resource allocated to the first network node. The present application can improve the efficiency of sending in a network, and the present application is used in an FTTR network.

Inventors

QIU, Hao
WU, Xuming
WEI, FENG

Assignees

华为技术有限公司

Dates

Publication Date: 20260507
Application Date: 20251013
Priority Date: 20241104

Claims (18)

A time-domain scheduling method, characterized in that the method is executed by a first network node, wherein the first network node is any one of at least one network node in a fiber-to-the-room (FTTR) network, and the method includes: Send service information to the control node in the FTTR network, wherein the service information is the service data that the first network node needs to transmit over the air interface; If no scheduling message is received from the control node within the timeout period after sending the service information, an alarm message is sent to the control node; the scheduling message is sent based on the service information and is used to indicate the air interface resources allocated to the first network node.
The method according to claim 1, characterized in that, before sending service information to the control node in the FTTR network, the method further includes: Receive a configuration message sent by the control node indicating the timeout duration; The timeout duration is determined based on the configuration message.
The method according to claim 1 or 2, characterized in that the method further comprises: The network node receives a reporting request message sent by the control node, the reporting request message being used to request the network node to report the timeout duration to the control node; According to the reporting request message, a duration reporting message indicating the timeout duration is sent to the control node.
The method according to claim 3, characterized in that, before sending service information to the control node in the FTTR network, the method further includes: receiving a configuration message sent by the control node indicating the timeout duration; and determining the timeout duration according to the configuration message; The configuration message, the reporting request message, and the duration reporting message have the same structure; The S-th bit in the configuration message, the reporting request message, and the duration reporting message is used to indicate the type of message, where S≥1.
According to the method of claim 4, the state value of the S-th bit in the duration reporting message is the same as the state value of the S-th bit in the configuration message or the reporting request message.
According to the method of claim 4 or 5, the configuration message, the reporting request message, and the duration reporting message all include a message length and processing requirement field, and the Sth bit is the second bit in the message length and processing requirement field.
The method according to any one of claims 1 to 6, wherein the timeout duration is a first duration, and the method further includes: The system receives an update message sent by the control node, the update message indicating that the timeout duration be updated to a second duration, the first duration being different from the second duration; According to the update message, the timeout duration is updated from the first duration to the second duration.
A time-domain scheduling method, characterized in that the method is executed by a control node in a fiber-to-room (FTTR) network, the method comprising: The system receives an alarm message sent by the first network node when it does not receive a scheduling message from the control node within a timeout period after sending service information; the service information is information about service data that the first network node needs to transmit over the air interface; the FTTR network includes at least one network node, and the first network node is any one of the at least one network node; the scheduling message is sent based on the service information, and the scheduling message is used to indicate the air interface resources allocated to the first network node.
The method according to claim 8 is characterized in that the method further includes: receiving service information sent by the first network node before receiving the alarm message.
The method according to claim 8 or 9, characterized in that the method further comprises: Before receiving the alarm message, a configuration message indicating the timeout duration is sent to the first network node.
The method according to any one of claims 8 to 10, characterized in that the method further comprises: Send a reporting request message to the first network node, the reporting request message being used to request the first network node to report the timeout duration to the control node; Receive a duration reporting message sent by the first network node in accordance with the reporting request message, which indicates the timeout duration.
The method according to claim 11, wherein the method further comprises: sending a configuration message indicating the timeout duration to the first network node before receiving the alarm message; The configuration message, the reporting request message, and the duration reporting message have the same structure; The S-th bit in the configuration message, the reporting request message, and the duration reporting message is used to indicate the type of message, where S≥1.
According to the method of claim 12, the state value of the S-th bit in the duration reporting message is the same as the state value of the S-th bit in the configuration message or the reporting request message.
According to the method of claim 12 or 13, the configuration message, the reporting request message, and the duration reporting message all include a message length and processing requirement field, and the Sth bit is the second bit in the message length and processing requirement field.
The method according to any one of claims 8 to 14, wherein the timeout duration is a first duration, and the method further comprises: An update message is sent to the first network node, the update message indicating that the timeout duration is updated to a second duration, the first duration being different from the second duration.
A time-domain scheduling device, characterized in that the time-domain scheduling device belongs to a first network node, the first network node being any one of at least one network node in a fiber-to-the-room (FTTR) network, the time-domain scheduling device comprising: The first sending module is used to send service information to the control node in the FTTR network. The service information is the information of the service data that the first network node needs to transmit over the air interface. The second sending module is configured to send an alarm message to the control node if no scheduling message is received from the control node within a timeout period after sending the service information; the scheduling message is sent based on the service information and is used to indicate the air interface resources allocated to the first network node.
A time-domain scheduling device, characterized in that the time-domain scheduling device belongs to the control node in a fiber-to-the-room (FTTR) network, and the time-domain scheduling device comprises: The first receiving module is configured to receive an alarm message sent by the first network node when it fails to receive a scheduling message sent by the control node within a timeout period after sending service information; the service information is information about service data that the first network node needs to transmit over the air interface; the FTTR network includes at least one network node, and the first network node is any one of the at least one network node; the scheduling message is sent based on the service information, and the scheduling message is used to indicate the air interface resources allocated to the first network node.
A time-domain scheduling system, characterized in that the time-domain scheduling system includes a control node in a fiber-to-the-room (FTTR) network and at least one network node in the FTTR network; The first network node is used to execute the time-domain scheduling method according to any one of claims 1 to 7, wherein the first network node is any one of the at least one network node; The control node is used to execute the time-domain scheduling method according to any one of claims 8 to 15.

Description

Time-domain scheduling methods, devices and systems This application claims priority to Chinese Patent Application No. 202411567257.5, filed on November 4, 2024, entitled "Time-Domain Scheduling Method, Apparatus and System", and also claims priority to Chinese Patent Application No. 202411765956.0, filed on November 29, 2024, entitled "Time-Domain Scheduling Method, Apparatus and System", the entire contents of which are incorporated herein by reference. Technical Field This application relates to the field of communication technology, and in particular to a time-domain scheduling method, apparatus and system. Background Technology Currently, in fiber-to-the-room (FTTR) networks, each sub-FTTR unit (SFU) shares air interface resources. SFUs compete for channels within these resources to gain transmission opportunities. However, with the development of communication technology, the number of SFUs is increasing, and the probability of multiple SFUs competing for the channel at the same time is also increasing. Multiple SFUs competing for the channel at the same time may cause random backoff collisions, leading to packet transmission failures, reduced network throughput, and increased service latency. Therefore, how to avoid random backoff collisions in the air interface and improve the transmission efficiency in the network is worth studying. Summary of the Invention This application provides a time-domain scheduling method, apparatus, and system, which helps to avoid random backoff conflicts at the air interface and improves transmission efficiency in the network. Firstly, this application provides a time-domain scheduling method, executed by a control node in an FTTR network. The method includes: the control node receiving an alarm message from a first network node; the first network node sending the alarm message if it does not receive a scheduling message from the control node within a timeout period after sending service information; the service information being information about service data that the first network node needs to transmit over the air interface; the FTTR network including at least one network node, the first network node being any one of the at least one network nodes; and the scheduling message being sent based on the service information, indicating the air interface resources allocated to the first network node. Optionally, the control node may also receive the service information before receiving the alarm message; however, the control node may also be unable to receive the service information due to link failures or other reasons. At least one of the aforementioned network nodes can send service information to the control node. In this embodiment, the control node can begin receiving service information sent by the network nodes. After receiving the service information from each network node, the control node can centrally schedule the at least one network node to determine the air interface resources allocated to each network node. Finally, the control node sends a scheduling message to each network node to indicate the air interface resources to the first network node, facilitating the first network node to compete for the air interface (air interface is also a channel, so competing for the air interface is also competing for the channel) and transmit data on the air interface it has won. When the at least one network node includes multiple network nodes, the air interface resources allocated to different network nodes can be the same or different, and this embodiment does not limit this. For example, at least two network nodes may have air interface resources allocated to them in different time and/or frequency domains. As can be seen, the air interface resources that network nodes compete for are allocated by the control node. The control node enables centralized control of at least one network node, instructing each node to compete for the corresponding air interface resources via scheduling messages. Once a node wins the air interface, it transmits data on that interface. In this way, the control node can control the order in which network nodes transmit data, which helps avoid random backoff conflicts between network nodes, reduces interference between air interfaces, improves air interface efficiency, reduces retransmission rate, reduces latency, and increases throughput. Understandably, the time interval between a network node sending service information and receiving a scheduling message is usually not too long (e.g., it will not exceed the aforementioned timeout period). Therefore, if the first network node does not receive a scheduling message within the timeout period after sending the service information, it indicates that the first network node has timed out of receiving the scheduling message. This situation may be caused by a control node malfunction or a communication link malfunction between the control node and the first network node. For example, due to a link m