Time domain scheduling method, apparatus and system

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.

Description

Time-domain scheduling methods, devices and systems

[0001] This application claims priority to Chinese Patent Application No. 202411567257.5, filed November 4, 2024, entitled "Time-Domain Scheduling Method, Apparatus and System", and also claims priority to Chinese Patent Application No. 202411765956.0, filed November 29, 2024, entitled "Time-Domain Scheduling Method, Apparatus and System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a time-domain scheduling method, apparatus and system. Background Technology

[0003] 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.

[0004] 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.

[0005] 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

[0006] 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.

[0007] 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.

[0008] 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.

[0009] 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 malfunction, the aforementioned service information could not be successfully transmitted to the control node, and thus the control node would not issue a scheduling message based on this service information; or, although the control node received the service information, it could not issue a scheduling message due to a control node malfunction; or, due to a link malfunction, the scheduling message issued by the control node could not be transmitted to the network node. Once it is determined that the first network node has timed out of receiving the scheduling message, the first network node sends an alarm message to the control node to indicate this timeout situation.

[0010] Optionally, the timeout duration can be statically configured in the network node, or it can be indicated to the first network node by other nodes. For example, before receiving service information sent by the first network node (such as after the initialization and synchronization of the control node and network nodes, or during the initialization process), the control node can send a configuration message to the first network node to indicate the timeout duration. The first network node can determine the timeout duration based on the configuration message.

[0011] Additionally, the control node can query the timeout duration on the first network node. For example, the control node can also send a reporting request message to the first network node, which requests the first network node to report the timeout duration to the control node (i.e., requests to report the time-domain scheduling timer parameters); the first network node can then send a duration reporting message to the control node indicating the timeout duration based on the reporting request message.

[0012] Optionally, 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 message type, where S≥1. This eliminates the need to design separate message structures for the configuration message, the reporting request message, and the duration reporting message, reducing the complexity of message structure design. For example, the configuration message, the reporting request message, and the duration reporting message all include a message length and processing requirement field (comprising two bytes), and the S-th bit is the second bit in the message length and processing requirement field (the second bit of the first byte of those two bytes).

[0013] For example, the status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or the reporting request message. When the S-th bit is a binary bit, it has two status values: 0 and 1. In the message sent by the control node to the first network node (such as the configuration message or the reporting request message mentioned above), the two status values ​​of the S-th bit are used to indicate the configuration message type and the reporting request message type, respectively; for example, status value 0 indicates the configuration message type and status value 1 indicates the reporting request message type; or, status value 1 indicates the configuration message type and status value 0 indicates the reporting request message type. In the message sent by the first network node to the control node (such as the duration reporting message), one of the status values ​​of the S-th bit (such as 0 or 1) is used to indicate the duration reporting message type.

[0014] The control node can also control the first network node to update the timeout duration. For example, assuming the timeout duration is a first duration, the control node can also send an update message to the first network node, instructing it to update the timeout duration to a second duration, which is different from the first. The first network node can then update its timeout duration from the first to the second duration based on this update message.

[0015] Secondly, a time-domain scheduling method is provided, the method being executed by a first network node, which is any one of at least one network node in a fiber-to-the-room (FTTR) network. The method includes: after sending service information to a control node in the FTTR network, if the first network node does not receive a scheduling message from the control node within a timeout period after sending the service information, it sends an alarm message to the control node; the service information is information about service data that the first network node needs to transmit over the air interface; 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.

[0016] Optionally, before sending service information to the control node in the FTTR network, the first network node may also receive a configuration message sent by the control node to indicate the timeout duration, and determine the timeout duration according to the configuration message.

[0017] Optionally, the method further includes: a first network node receiving a reporting request message sent by the control node, and sending a duration reporting message to the control node indicating the timeout duration according to the reporting request message. The reporting request message is used to request the network node to report the timeout duration to the control node.

[0018] Optionally, before sending service information to the control node in the FTTR network, the first network node may also receive a configuration message sent by the control node to indicate the timeout duration; and determine 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 message type, where S≥1.

[0019] Optionally, the status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or the reporting request message.

[0020] For example, 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.

[0021] Optionally, the timeout duration is a first duration, and the method further includes: a first network node receiving an update message sent by the control node, and updating the timeout duration from the first duration to a second duration according to the update message. The update message is used to indicate that the timeout duration is updated to the second duration, and the first duration is different from the second duration;

[0022] Thirdly, a time-domain scheduling device is provided, which belongs to the control node in a fiber-to-the-room (FTTR) network. The time-domain scheduling device includes: a first receiving module and a second receiving module. The second receiving module is used to receive service information sent by a first network node, the service information being 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 first receiving module is used to receive 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 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. In some cases, the control node may be unable to receive the service information due to link failures or other reasons; in this case, the time-domain scheduling device does not include a second receiving module.

[0023] Optionally, the time-domain scheduling device further includes: a first sending module, configured to send a configuration message indicating the timeout duration to the first network node before the second receiving module receives the service information sent by the first network node.

[0024] Optionally, the time-domain scheduling device further includes a second sending module and a third receiving module. The second sending module is used to 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; the third receiving module is used to receive a duration reporting message sent by the first network node according to the reporting request message, which indicates the timeout duration.

[0025] Optionally, the time-domain scheduling device further includes: a first sending module, configured to send a configuration message indicating the timeout duration to the first network node before the second receiving module receives the service information sent by the first network node. 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 message type, where S≥1.

[0026] Optionally, the status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or the reporting request message.

[0027] Optionally, 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.

[0028] Optionally, the timeout duration is a first duration, and the time-domain scheduling device further includes: a third sending module, used to send an update message to the first network node, the update message being used to indicate that the timeout duration is updated to a second duration, the first duration being different from the second duration.

[0029] Fourthly, a time-domain scheduling device is provided, which belongs to a first network node, which is any one of at least one network node in a fiber-to-the-room (FTTR) network. The time-domain scheduling device includes a first sending module and a second sending module. The first sending module is used to send service information to a control node in the FTTR network, wherein the service information is information about service data that the first network node needs to transmit over the air interface. The second sending module is used 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.

[0030] Optionally, the time-domain scheduling device further includes: a second receiving module, configured to receive a configuration message sent by the control node indicating the timeout duration before the first sending module sends service information to the control node in the FTTR network; and a determining module, configured to determine the timeout duration based on the configuration message.

[0031] Optionally, the time-domain scheduling device further includes: a first receiving module, configured to receive 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; and a third sending module, configured to send a duration reporting message indicating the timeout duration to the control node according to the reporting request message.

[0032] Optionally, the time-domain scheduling device further includes: a second receiving module, configured to receive a configuration message sent by the control node indicating the timeout duration before the first sending module sends service information to the control node in the FTTR network; determine 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 message type, where S≥1.

[0033] Optionally, the status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or the reporting request message.

[0034] Optionally, 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.

[0035] Optionally, the timeout duration is a first duration, and the time-domain scheduling device further includes: a third receiving module, configured to receive an update message sent by the control node, the update message indicating that the timeout duration be updated to a second duration, wherein the first duration is different from the second duration; and an update module, configured to update the timeout duration from the first duration to the second duration according to the update message.

[0036] Fifthly, a time-domain scheduling device is provided, which belongs to the control node in a fiber-to-the-room (FTTR) network. The time-domain scheduling device includes an interface and a processor. The interface is used to perform the sending and receiving operations in the method provided by any design in the first aspect, and the processor is used to perform operations other than sending and receiving (i.e., processing operations) in the method provided by any design in the first aspect. For example, the interface is used to receive service information sent by a first network node, the service information being 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 interface is also used to receive an alarm message sent by the first network node when it does not receive a scheduling message sent by the control node within a timeout period after sending the service information; 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.

[0037] In a sixth aspect, a time-domain scheduling device is provided, which belongs to a first network node in a fiber-to-the-room (FTTR) network. The first network node is any one of at least one network node in the FTTR network. The time-domain scheduling device includes an interface and a processor. The interface is used to perform the sending and receiving operations in the method provided in any design of the second aspect, and the processor is used to perform operations other than sending and receiving (i.e., processing operations) in the method provided in any design of the second aspect. For example, the interface is used to send service information to a control node in the FTTR network, the service information being information about service data that the first network node needs to transmit over the air interface; the interface is also used to send an alarm message to the control node if a scheduling message sent by the control node is not received within a timeout period after sending the service information; 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.

[0038] In a seventh aspect, a time-domain scheduling system is provided, the time-domain scheduling system comprising a control node and at least one network node in a fiber-to-the-room (FTTR) network; the control node is used to execute the time-domain scheduling method described in any design of the first aspect; the first network node is used to execute the time-domain scheduling method described in any design of the second aspect, wherein the first network node is any one of the at least one network node.

[0039] Eighthly, this application provides a time-domain scheduling apparatus, comprising: a processor and a memory, wherein the memory stores a program, and the processor is configured to run the program to execute the time-domain scheduling method described in either the first or second aspect.

[0040] Ninthly, this application provides a computer storage medium storing a computer program, which, when run on a computer, causes the computer to execute the time-domain scheduling method described in either the first or second aspect.

[0041] In a tenth aspect, this application also provides a computer program product containing instructions that, when the computer program product is run on a computer, cause the computer to execute the time-domain scheduling method described in either the first or second aspect.

[0042] In an eleventh aspect, this application also provides a chip for implementing the time-domain scheduling method as described in either the first or second aspect.

[0043] The effects of the second to eleventh aspects mentioned above can be referred to the effects of the corresponding designs in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0044] Figure 1 is a schematic diagram of an FTTR network provided in an embodiment of this application;

[0045] Figure 2 is a schematic diagram of another FTTR network provided in an embodiment of this application;

[0046] Figure 3 is a schematic diagram of another FTTR network provided in an embodiment of this application;

[0047] Figure 4 is a flowchart of a time-domain scheduling method provided in an embodiment of this application;

[0048] Figure 5 is a schematic diagram of a configuration message provided in an embodiment of this application;

[0049] Figure 6 is a block diagram of a time-domain scheduling device provided in an embodiment of this application;

[0050] Figure 7 is a block diagram of another time-domain scheduling device provided in an embodiment of this application. Detailed Implementation

[0051] With the development of networks, the number of devices in home networks is increasing, and the probability of multiple devices competing for the channel at the same time is also increasing. Therefore, multiple devices competing for the channel at the same time may cause random backoff collisions, resulting in packet transmission failures, reduced network throughput, and increased service latency.

[0052] In view of this, embodiments of this application provide a time-domain scheduling method to provide a feasible way to avoid random backoff conflicts at the air interface, thereby improving the efficiency of data transmission through the channel and improving the overall network performance.

[0053] This application embodiment can be applied to fiber-to-the-room (FTTR) networks, where fiber optic cables are laid to every room, and home gateways are interconnected by deploying sub-FTTR units (SFUs) in each room. FTTR can meet the high bandwidth and latency requirements of new business applications such as online education, home office, and home entertainment. An SFU can be an edge optical network terminal (edge ​​ONT) or an access point (AP), that is, it can act as a network node in a wireless network. Referring to Figure 1, in an FTTR application scenario, a main FTTR unit (MFU) is deployed to manage the SFUs. An MFU can be an optical gateway, optical network terminal (ONT), or passive optical network (PON) gateway, that is, it can act as a control node in a wireless network.

[0054] In an FTTR network, the MFU (Master Unit) acts as both the ONT (On-Network Terminal) in a fiber-to-the-home / office (FTTH / O) network and the upstream device for the SFU (Support Unit), managing the SFU. SFUs can be deployed in various rooms of a home or office to provide signal to terminals. An SFU functions as an ONT and can also function as a wireless access point (AP). Multiple SFUs can be deployed in an FTTR network, each connected to the MFU via an optical splitter. The MFU can centrally manage and configure all SFUs. The MFU can also be called a "master device," "master gateway," or "master optical modem," while the SFU can be called a "slave gateway," "slave optical modem," or "slave device." The terminals (also called terminal devices) can include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, and computer-embedded mobile devices. Examples include personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). Terminals can also be computers, tablets, e-readers, or smart home devices such as smart TVs and smart speakers. As an example and not a limitation, in this embodiment, the terminal can also be a wearable device. Wearable devices, also known as wearable smart devices or smart wearable devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Wearable smart devices in a broad sense include those that are feature-rich, large in size, and can perform all or part of their functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets, smart helmets, and smart jewelry for vital sign monitoring.

[0055] As an example, let's take the MFU as the optical gateway and the SFU as the edge ONT. Figure 2 shows a schematic diagram of an optical communication system topology applied to FTTR. An optical communication system applied to FTTR includes at least an optical gateway, a splitter, and multiple edge ONTs. In this embodiment, the edge ONT can also be called an EDGE ONT or an Edge ONT. The optical gateway can communicate with multiple EDGE ONTs separately through the splitter. The optical communication system also includes an OLT. The optical gateway is deployed between the OLT and the edge ONTs. In the FTTR scenario, the optical gateway connects to the home information box via fiber optic cable, and then connects to each room via the splitter. Each room deploys an edge ONT, and the optical gateway at the information box collaboratively manages multiple edge ONTs. Multiple ONTs in the FTTR network are connected to the optical gateway via optical fiber, and control and management resources do not occupy Wi-Fi air interfaces. Compared with multi-AP Wi-Fi cascading schemes, this improves the real-time performance of optical gateway management. Terminal devices can access the edge ONTs to achieve network communication.

[0056] As another example, consider an MFU (Medium-Operated Unit) as the optical gateway, implemented using an ONT (Optical Network Terminal), and an SFU (Self-Service Unit) as the access point (AP). Figure 3 shows a schematic diagram of another optical communication system topology for a home network application. The optical communication system includes at least an ONT and multiple APs. The ONT is used for collaborative management of the APs deployed in each room.

[0057] FTTR optical communication systems can employ PON. PON can be gigabit-capable PON (GPON), Ethernet passive optical network (EPON), 10Gb / s ethernet passive optical network (10G-EPON), time and wavelength division multiplexing passive optical network (TWDM-PON), 10gigabit-capable passive optical network (XG-PON), or 10-gigabit-capable symmetric passive optical network (XGS-PON), etc. Future advancements will increase PON speeds to 25Gbps, 50Gbps, or even 100Gbps; therefore, this application also allows for the application of PONs with even higher transmission rates.

[0058] In this embodiment, the advantages of MFU's collaborative management of SFU in FTTR network are utilized. The MFU centrally decides the order in which SFU compete for channels to avoid random backoff conflicts, thereby optimizing the overall network performance.

[0059] The method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0060] Referring to Figure 4, which is an interactive flowchart of a time-domain scheduling method provided in an embodiment of this application, as shown in Figure 4, the time-domain scheduling method provided in this embodiment includes:

[0061] S101. The first network node sends service information to the control node. The service information is the service data that the first network node needs to transmit over the air interface. The first network node is any one of at least one network node in the FTTR network.

[0062] Both the control node and the first network node can belong to the FTTR network. The control node can be called MFU, master node, master device, etc., and the network node can be called SFU, slave node, slave device, etc.

[0063] When a first network node needs time-domain scheduling from a controlled node, it can send service information to the control node. This service information consists of the service data that the first network node needs to transmit over the air interface, and it cannot be empty. For example, if the first network node has service data that needs to be transmitted over the air interface, the network node can determine that it needs time-domain scheduling from the control node, and at this time, it can send the service information.

[0064] At least one of the aforementioned network nodes can send service information to the control node. In this embodiment, the control node can receive service information sent by the network nodes. After receiving the service information sent by 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, and finally send scheduling messages to each network node.

[0065] S102. The control node sends a scheduling message to the first network node based on the service information. The scheduling message is used to indicate the air interface resources allocated to the first network node.

[0066] After receiving service information, the control node can allocate air interface resources to the first network node based on the service information, and then indicate the air interface resources to the first network node through a scheduling message, so that the first network node can compete for the air interface (the 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 application embodiment does not limit this. For example, the air interface resources allocated to at least two network nodes are different in the time domain and / or frequency domain. During the time domain scheduling process, the control node needs to allocate air interface resources to the network nodes in the time domain resources. The aforementioned time domain resources can include transmission resources for different time periods (the size of the time period may not be fixed), and these transmission resources do not affect each other, and the data transmitted on the transmission resources in different time periods do not interfere with each other.

[0067] 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. This 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.

[0068] S103. If the first network node does not receive the scheduling message sent by the control node within the timeout period after sending the service information, it sends an alarm message to the control node.

[0069] S104. If the first network node receives a scheduling message from the control node within the timeout period after sending the service information, it competes for the air interface on the air interface resources according to the scheduling message, and transmits data on the air interface it wins.

[0070] For example, after each transmission of service information, the first network node starts a timer (which can be called a time-domain scheduling timer or simply a timer). When the timer reaches its timeout duration (which can be called the time-domain scheduling timer parameter), it checks whether a scheduling message has been received. If the scheduling message is not received, the first network node sends an alarm message to the control node. If the first network node receives the scheduling message before the timer reaches its timeout duration, the first network node closes the timer and can compete for air interface access and transmit data based on the scheduling message.

[0071] 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 malfunction, the aforementioned service information could not be successfully transmitted to the control node, and thus the control node would not issue a scheduling message based on this service information; or, although the control node received the service information, it could not issue a scheduling message due to a control node malfunction; or, due to a link malfunction, the scheduling message issued by the control node could not be transmitted to the network node. Once it is determined that the first network node has timed out of receiving the scheduling message, the first network node sends an alarm message to the control node to indicate this timeout situation.

[0072] In summary, the time-domain scheduling method provided in this application embodiment enables centralized control of at least one network node through a control node. The control node sends scheduling messages to instruct each network node to compete for air interface resources, and after successfully acquiring an air interface, data is transmitted on that interface. Therefore, this method helps avoid random backoff conflicts between network nodes, reduces interference between network nodes' air interfaces, improves air interface efficiency, reduces retransmission rate, reduces latency, and increases throughput. Furthermore, after sending service information to the control node, the first network node can detect whether it has received a scheduling message from the control node within a timeout period after sending the service information. If the scheduling message is not received within this timeout period, the first network node can send an alarm message to the control node to alert it of a timeout in receiving the scheduling message.

[0073] Optionally, the timeout duration can be statically configured in the network node, or it can be indicated to the first network node by other nodes. For example, before S101 (such as after the initialization and synchronization of the control node and network nodes, or during the initialization process), the control node can send a configuration message to the first network node to indicate the timeout duration. The first network node can determine the timeout duration based on this configuration message.

[0074] A configuration message includes a header and a payload. The header indicates the configuration message type, and the payload indicates the timeout duration. As shown in Figure 5, the header includes a type field, which indicates the configuration message type. The payload includes a timeout field (or timer field), which indicates the timeout duration.

[0075] For example, the type field may include one byte, two bytes, or more bytes. One of several status values ​​in the type field indicates the configuration message type; this status value can be any of the status values ​​such as 0, 1, 2, etc. Alternatively, a single bit in the type field may also indicate the configuration message type; this status value can also be any of the status values ​​such as 0, 1, 2, etc. For example, when the type field includes two bytes, a status value of the second bit of the first byte indicates the configuration message type. The timeout field may include one byte, two bytes, or more bytes. Furthermore, the unit for the first timeout duration can be microseconds, milliseconds, etc.

[0076] In S104 above, if the first network node receives the scheduling message before the timer reaches its timeout duration, the first network node may not close the timer but instead update it to restart the timer. After updating the timer, if the timer reaches its timeout duration, the first network node may also detect whether it received a scheduling message during the time period between the timer update and the timer reaching its timeout duration. If the first network node receives a scheduling message during this time period, it may close the timer or update it again. If the first network node does not receive a scheduling message during this time period, it sends an alarm message to the control node and closes or updates the timer again.

[0077] It is evident that if the first network node receives a scheduling message before the timer reaches its timeout duration (the timer has not expired), the first network node may close or update the timer.

[0078] Whether the first network node closes or updates the timer depends on the number of times the control node sends scheduling messages.

[0079] For example, suppose the control node sends a scheduling message to the first network node based on the service information; then, if the first network node does not receive the scheduling message when the timer expires (timer expires), it will send an alarm message to the control node and shut down the timer; if the first network node receives the scheduling message before the timer expires, it will shut down the timer.

[0080] For example, suppose the control node sends scheduling messages to the first network node multiple times based on service information to allocate air interface resources to the first network node multiple times (the air interface resources allocated to the first network node in different messages can be the same or different). Then, the number of times the control node sends scheduling messages to the first network node based on service information is 1 greater than the number of times the first network node updates its timer.

[0081] For example, if the control node sends x (x > 1) scheduling messages to the first network node based on service information, then the first network node can start a timer after sending the service information. Afterward, the first network node performs x target operations.

[0082] Each of the first x-1 target operations includes: when the timer in this target operation reaches its timeout duration (timer expires), if no scheduling message is received, an alarm message will be sent to the control node, and the timer will be updated to restart. If a scheduling message is received before the timer in this target operation reaches its timeout duration (timer has not expired), the timer will be updated to restart. The timer in the first target operation is the timer started by the first network node after sending service information; the timers in the x target operations other than the first target operation are the timers updated in the previous target operation.

[0083] The xth target operation includes: when the timer in this target operation reaches its timeout duration (timer timeout), if no scheduling message is received, an alarm message will be sent to the control node and the timer will be turned off so that the timer restarts; if a scheduling message is received before the timer in this target operation reaches its timeout duration (timer has not timed out), the timer will be turned off.

[0084] Optionally, in any of the first x-1 target operations, if the first network node does not receive a scheduling message when the timer for that target operation reaches its timeout duration, it will send an alarm message to the control node and shut down the timer. In this case, the first network node does not need to execute subsequent target operations.

[0085] Additionally, the control node can query the timeout duration on the first network node. For example, the control node can also send a reporting request message to the first network node, which requests the first network node to report the timeout duration to the control node (i.e., requests to report the time-domain scheduling timer parameters); the first network node can then send a duration reporting message to the control node indicating the timeout duration based on the reporting request message.

[0086] The duration reporting message includes a header and a payload. The header indicates the message type, and the payload indicates the timeout duration. As shown in Figure 5, the header includes a type field indicating the message type. The payload includes a timeout field indicating the timeout duration. For example, the type field may contain one byte, two bytes, or more. One of several status values ​​in the type field indicates the message type; this status value can be any value from 0, 1, 2, etc. Alternatively, a single bit in the type field may indicate the message type; this status value can also be any value from 0, 1, 2, etc. For example, when the type field contains two bytes, the second bit of the first byte indicates the message type. The timeout field may contain one byte, two bytes, or more. In addition, the unit for the first timeout duration can be microseconds, milliseconds, etc.

[0087] The reporting request message includes a header and a payload. The header indicates the type of the reporting request message. As shown in Figure 5, the header includes a type field, which indicates the type of the reporting request message. For example, the type field may include one byte, two bytes, or more bytes. One of several status values ​​in the type field indicates the configuration message type; this status value can be any value from 0, 1, 2, etc. Alternatively, a single bit in the type field may indicate the reporting request message type; this status value can also be any value from 0, 1, 2, etc. For example, when the type field includes two bytes, the status value of the second bit of the first byte indicates the duration reporting request message type.

[0088] It is understood that the control node may not need to query the timeout duration on the first network node, and this application embodiment does not limit this.

[0089] Optionally, the configuration message, reporting request message, and duration reporting message have the same structure. In this case, as shown in Figure 5, the payload of the reporting request message can also include a duration field, but the status value of this duration field is used to indicate that the duration field is not effective.

[0090] When the configuration message, report request message, and duration report message have the same structure, the S-th bit in each message type (S≥1) is used to indicate the message type. For example, the S-th bit in the configuration message indicates that the message type is configuration; the S-th bit in the report request message indicates that the message type is report request; and the S-th bit in the duration report message indicates that the message type is duration report. This eliminates the need to design separate message structures for each message type, reducing the complexity of message structure design.

[0091] For example, configuration messages, reporting request messages, and duration reporting messages all include a message length and processing requirement field (which consists of two bytes), with the Sth bit being the second bit in the message length and processing requirement field (the second bit of the first byte of these two bytes).

[0092] Optionally, the status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or reporting request message. When the S-th bit is a binary bit, it has two status values: 0 and 1. In the message sent by the control node to the first network node (such as the configuration message or reporting request message mentioned above), the two status values ​​of the S-th bit are used to indicate the configuration message type and the reporting request message type, respectively; for example, status value 0 indicates the configuration message type and status value 1 indicates the reporting request message type; or, status value 1 indicates the configuration message type and status value 0 indicates the reporting request message type. In the message sent by the first network node to the control node (such as the duration reporting message), one of the status values ​​of the S-th bit (such as 0 or 1) is used to indicate the duration reporting message type.

[0093] Of course, the structures of at least two of the configuration message, reporting request message, and duration reporting message can be different. For example, the payload of the aforementioned reporting request message may not include a duration field. In addition, the duration indicated by the aforementioned configuration message and duration reporting message may also be indicated through the message header rather than through the message payload; this embodiment of the application does not limit this.

[0094] In addition, in some optional implementations, the status value of the duration field in the configuration message may not indicate the timeout duration. For example, the status value of the duration field in the configuration message may be used to indicate that the duration field is not effective (or the configuration information is not effective). In this case, the corresponding network node will not be able to obtain the timeout duration, and will not execute the process shown in Figure 4 based on the timeout duration.

[0095] In this embodiment of the application, when the field indicates that the field is not effective, the state value of the field can be any state value, such as the state value where all bits in the field are at their maximum value, or the state value where all bits in hexadecimal are F (representing 16).

[0096] Furthermore, in this embodiment of the application, a field (any field in this embodiment) is used to indicate the content it is meant to indicate through its status value. Optionally, when some fields indicate content, the field or some bits of the field may be empty (NULL). For example, when the Sth bit in the message sent by the control node to the first network node is empty, the message is used to indicate the reporting request message type.

[0097] The control node can also control the first network node to update the timeout duration. For example, assuming the timeout duration is a first duration, the control node can also send an update message to the first network node, instructing it to update the timeout duration to a second duration, which is different from the first. The first network node can then update its timeout duration from the first to the second duration based on this update message.

[0098] For example, the update message includes a message header and a payload. The message header indicates the update message type, and the payload indicates the second duration. The structure of the update message can refer to the structure of the configuration message described above, and will not be repeated here in the embodiments of this application.

[0099] It is understood that the control node may not control the update timeout duration of the first network node, and this application embodiment does not limit this.

[0100] Furthermore, after receiving the aforementioned alarm message, the control node can display the alarm message to the staff; the control node can also adjust the time-domain scheduling for the first network node based on the alarm message. The process of time-domain scheduling for the first network node can be referred to in S101, S102, and S104 above.

[0101] For example, assuming the control node does not exit time-domain scheduling after sending an alarm message, the control node can increase the priority of the first network node based on the alarm message. The higher the priority of the network node, the earlier it will be scheduled in the time domain. Optionally, the control node can increase the priority of the first network node to the highest or second highest level. This allows the first network node to be scheduled by the controller more quickly, thus enabling it to receive the scheduling message as soon as possible. For example, the control node can schedule network nodes in a certain order; the earlier the scheduling order, the earlier the network node receives the scheduling message. This allows the network node to compete for the allocated air interface resources as early as possible based on the scheduling message, thereby enabling it to transmit data as soon as possible.

[0102] This example illustrates that a higher network node priority results in a higher scheduling order during time-domain scheduling. Alternatively, a higher network node priority could mean that the network node is allocated more air interface resources during time-domain scheduling. Or, a higher network node priority could mean both higher scheduling order and more allocated air interface resources during time-domain scheduling.

[0103] For example, assuming the control node does not exit time-domain scheduling after sending an alarm message, the control node can also stop time-domain scheduling for the first network node based on the alarm message. In this case, the control node also needs to send an exit indication message to the first network node to instruct the first network node to also exit time-domain scheduling, so that the first network node can resume to determine its own air interface resources and compete for air interfaces on the determined air interface resources.

[0104] As another example, the first network node can also proactively exit time-domain scheduling before sending an alarm message. In this case, the control node can stop time-domain scheduling of the first network node based on the alarm message, and the control node does not need to send an exit instruction message to the first network node.

[0105] This application embodiment also provides a time-domain scheduling device, which belongs to the control node in the FTTR network. As shown in FIG6, the time-domain scheduling device includes: a first receiving module 601 and a second receiving module 602. The second receiving module 602 is used to receive service information sent by a first network node, the service information being 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 first receiving module 601 is used to receive an alarm message sent by the first network node when it does not receive a scheduling message sent by the control node within a timeout period after sending the service information; 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 operations performed by the second receiving module 602 can refer to the operations related to the control node in S101 of the aforementioned embodiment, and the operations performed by the first receiving module 601 can refer to the operations related to the control node in S103 of the aforementioned embodiment. In some cases, the control node may be unable to receive the service information due to reasons such as link failure. In this case, the time-domain scheduling device does not include a second receiving module.

[0106] Optionally, the time-domain scheduling device further includes: a first sending module (not shown in Figure 6), configured to send a configuration message indicating the timeout duration to the first network node before the second receiving module receives the service information sent by the first network node.

[0107] Optionally, the time-domain scheduling device further includes: a second sending module (not shown in Figure 6) and a third receiving module (not shown in Figure 6). The second sending module is used to 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; the third receiving module is used to receive a duration reporting message sent by the first network node according to the reporting request message, which indicates the timeout duration.

[0108] Optionally, the time-domain scheduling device further includes: a first sending module (not shown in Figure 6), configured to send a configuration message indicating the timeout duration to the first network node before the second receiving module receives the service information sent by the first network node. 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 message type, where S≥1.

[0109] Optionally, the status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or the reporting request message.

[0110] Optionally, 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.

[0111] Optionally, the timeout duration is a first duration, and the time-domain scheduling device further includes: a third sending module (not shown in Figure 6), used to send an update message to the first network node, the update message being used to indicate that the timeout duration is updated to a second duration, the first duration being different from the second duration.

[0112] This application embodiment also provides another time-domain scheduling device, which belongs to a first network node in the FTTR network. The first network node is any one of at least one network node in the FTTR network, as shown in FIG7. The time-domain scheduling device includes: a first sending module 701 and a second sending module 702. The first sending module 701 is used to send service information to the control node in the FTTR network. The service information is information about service data that the first network node needs to transmit through the air interface. The second sending module 702 is used to send an alarm message to the control node if it does not receive a scheduling message 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. The operation performed by the first sending module 701 can refer to the operation related to the first network node in S101 of the aforementioned embodiment, and the operation performed by the second sending module 702 can refer to the operation related to the first network node in S103 of the aforementioned embodiment.

[0113] Optionally, the time-domain scheduling device further includes: a second receiving module (not shown in Figure 7), configured to receive a configuration message sent by the control node indicating the timeout duration before the first sending module sends service information to the control node in the FTTR network; and a determining module, configured to determine the timeout duration based on the configuration message.

[0114] Optionally, the time-domain scheduling device further includes: a first receiving module (not shown in Figure 7), used to receive 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; and a third sending module (not shown in Figure 7), used to send a duration reporting message indicating the timeout duration to the control node according to the reporting request message.

[0115] Optionally, the time-domain scheduling device further includes: a second receiving module (not shown in Figure 7), configured to receive a configuration message sent by the control node indicating the timeout duration before the first sending module sends service information to the control node in the FTTR network; determine 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 message type, where S≥1.

[0116] Optionally, the status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or the reporting request message.

[0117] Optionally, 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.

[0118] Optionally, the timeout duration is a first duration, and the time-domain scheduling device further includes: a third receiving module (not shown in Figure 7), used to receive an update message sent by the control node, the update message being used to indicate that the timeout duration is updated to a second duration, the first duration being different from the second duration; and an update module (not shown in Figure 7), used to update the timeout duration from the first duration to the second duration according to the update message.

[0119] This application also provides a time-domain scheduling device, which belongs to the control node in the FTTR network. The time-domain scheduling device includes an interface and a processor. The interface is used to execute the sending and receiving operations performed by the control node in any of the methods provided in this application. The processor is used to execute operations other than sending and receiving (i.e., processing operations) performed by the control node in any of the methods provided in this application. For example, the interface is used to receive service information sent by a first network node, the service information being 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 interface is also used to receive an alarm message sent by the first network node when it does not receive a scheduling message sent by the control node within a timeout period after sending the service information; 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.

[0120] This application also provides a time-domain scheduling device, which belongs to a first network node in a Fiber to the Room (FTTR) network. The first network node is any one of at least one network node in the FTTR network. The time-domain scheduling device includes an interface and a processor. In any design provided in this application, the sending and receiving operations are performed by the first network node. The processor is used to perform operations other than sending and receiving (i.e., processing operations) performed by the first network node in any design provided in this application. For example, the interface is used to send service information to a control node in the FTTR network. The service information is information about service data that the first network node needs to transmit over the air interface. The interface is also used to send an alarm message to the control node if a scheduling message is not 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.

[0121] This application also provides a time-domain scheduling system, which includes a control node and at least one network node in an FTTR network; the control node is used to execute the operations performed by the control node in any of the time-domain scheduling methods described in any of the embodiments of this application; the first network node is used to execute the operations performed by the first network node in any of the time-domain scheduling methods provided in any of the embodiments of this application, wherein the first network node is any one of the at least one network node.

[0122] This application provides a time-domain scheduling device, including: a processor and a memory, wherein the memory stores a program, and the processor is used to run the program to perform the operations performed by a control node or a first network node in any of the time-domain scheduling methods provided in the embodiments of this application.

[0123] This application provides a computer storage medium storing a computer program. When the computer program is run on a computer, it causes the computer to perform operations executed by a control node or a first network node in any of the time-domain scheduling methods provided in the embodiments of this application.

[0124] This application also provides a computer program product containing instructions that, when the computer program product is run on a computer, cause the computer to perform operations executed by a control node or a first network node in any of the time-domain scheduling methods provided in the embodiments of this application.

[0125] This application also provides a chip for implementing the operations performed by a control node or a first network node in any of the time-domain scheduling methods provided in the embodiments of this application.

[0126] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented entirely or partially as a computer program product, which includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium, or a semiconductor medium (e.g., solid-state drive), etc.

[0127] In this application, the terms "first" and "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. The term "at least one" refers to one or more, and "multiple" refers to two or more, unless otherwise expressly defined. The term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects are in an "or" relationship.

[0128] The method embodiments and device embodiments provided in this application can be referenced interchangeably, and this application does not limit them. The order of operations in the method embodiments provided in this application can be appropriately adjusted, and operations can be added or removed as appropriate. Any variations that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application, and therefore will not be elaborated further.

[0129] In the corresponding embodiments provided in this application, it should be understood that the disclosed devices, etc., can be implemented in other configurations. For example, the device embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical or other forms.

[0130] The modules described as separate components may or may not be physically separate. The components described as modules may or may not be physical units; they may be located in one place or distributed across multiple devices. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0131] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A time-domain scheduling method, characterized in that, The method is performed by a first network node, which is any one of at least one network node in a fiber-to-the-room (FTTR) network. 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.

2. 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.

3. The method according to claim 1 or 2, characterized in that, The method further includes: 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.

4. 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 based on 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.

5. The method according to claim 4, characterized in that, The status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or the reporting request message.

6. The method according to claim 4 or 5, characterized in that, The configuration message, the reporting request message, and the duration reporting message all include a message length and a processing requirement field, and the Sth bit is the second bit in the message length and processing requirement field.

7. The method according to any one of claims 1 to 6, characterized in that, 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.

8. A time-domain scheduling method, characterized in that, The method is performed by a control node in a fiber-to-the-room (FTTR) network, and the method includes: 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.

9. The method according to claim 8, characterized in that, The method further includes: receiving service information sent by the first network node before receiving the alarm message.

10. The method according to claim 8 or 9, characterized in that, The method further includes: Before receiving the alarm message, a configuration message indicating the timeout duration is sent to the first network node.

11. The method according to any one of claims 8 to 10, characterized in that, The method further includes: 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.

12. The method according to claim 11, characterized in that, The method further includes: 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.

13. The method according to claim 12, characterized in that, The status value of the S-th bit in the duration reporting message is the same as the status value of the S-th bit in the configuration message or the reporting request message.

14. The method according to claim 12 or 13, characterized in that, The configuration message, the reporting request message, and the duration reporting message all include a message length and a processing requirement field, and the Sth bit is the second bit in the message length and processing requirement field.

15. The method according to any one of claims 8 to 14, characterized in that, The timeout duration is a first duration, and the method further includes: An update message is sent to the first network node, the update message indicating that the timeout duration be updated to a second duration, the first duration being different from the second duration.

16. A time-domain scheduling device, characterized in that, The time-domain scheduling device belongs to a first network node, which is any one of at least one network node in a fiber-to-the-room (FTTR) network. The time-domain scheduling device includes: 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.

17. A time-domain scheduling device, characterized in that, The time-domain scheduling device is a control node in the fiber-to-the-room (FTTR) network, and the time-domain scheduling device includes: 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.

18. A time-domain scheduling system, characterized in that, The time-domain scheduling system includes a control node in the fiber-to-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.

Images