Time domain scheduling method and apparatus, and system

Abstract

The present invention relates to the technical field of communications, and provides a time domain scheduling method and apparatus, and a system. The time domain scheduling method is executed by a control node in an FTTR network. The time domain scheduling method comprises: a control node, after enabling a time domain scheduling function, receiving an alarm message sent by a first network node, the control node being used to perform time-domain scheduling of at least one network node in the FTTR network in the time domain scheduling function, the first network node being any network node among the at least one network node, and the alarm message being used for indicating whether the first network node exits time domain scheduling. The present application is helps to prevent random backoff collision of an air interface, and can improve transmission efficiency in a network. The present application is used in FTTR networks.

Description

Time-domain scheduling methods, devices and systems

[0001] This application claims priority to Chinese patent application filed on November 4, 2024, with application number 202411567239.7 and 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, which is executed by a control node in an FTTR network. The method includes: after enabling the time-domain scheduling function, the control node receives an alarm message sent by a first network node. The control node is used to perform time-domain scheduling on at least one network node in the FTTR network under the time-domain scheduling function; the first network node is any one of the at least one network node; and the alarm message is used to indicate whether the first network node has exited the time-domain scheduling.

[0008] In the time-domain scheduling method provided in this application embodiment, both the control node and the aforementioned at least one network node will enable the time-domain scheduling function. Then, time-domain scheduling can be performed on the at least one network node under the time-domain scheduling function. When the control node performs time-domain scheduling on the at least one network node, it allocates air interface resources to each network node (also known as centralized scheduling) and sends a scheduling message to the network node indicating the air interface resources allocated to that network node. The 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) on the air interface resources indicated by the scheduling message, and transmit data on the acquired air interface after winning the competition. 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; this application embodiment does not limit this. For example, at least two network nodes may have different time-domain and / or frequency-domain allocated air interface resources.

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

[0010] Furthermore, the first network node can also send alarm messages to the control node to alert it and instruct the first network node whether to exit time-domain scheduling. This enriches the functionality of the first network node.

[0011] Furthermore, alarm messages can be implemented in various ways. For example, an alarm message can also indicate that the first network node has exited time-domain scheduling, or that the first network node has not exited time-domain scheduling. Alternatively, an alarm message can indicate that the first network node continues to participate in time-domain scheduling, the first network node requests to exit time-domain scheduling, or the first network node has already exited time-domain scheduling. If an alarm message indicates that the first network node continues to participate in time-domain scheduling, it means that the first network node has not exited time-domain scheduling. An alarm message indicating that the first network node continues to participate in time-domain scheduling can also be replaced by an alarm message indicating that the first network node only reports an alarm and does not exit time-domain scheduling. If an alarm message indicates that the first network node requests to exit time-domain scheduling, it means that the first network node needs to exit time-domain scheduling and has not yet exited; therefore, in this case, the alarm message indicates that the first network node has not exited time-domain scheduling. If an alarm message indicates that the first network node has exited time-domain scheduling, it means that the first network node has currently exited time-domain scheduling; therefore, in this case, the alarm message indicates that the first network node has exited time-domain scheduling.

[0012] On the one hand, when an alarm message indicates that the first network node has exited time-domain scheduling, the first network node can exit time-domain scheduling before sending an alarm message to the control node. Upon receiving the alarm message, the control node can stop time-domain scheduling for the first network node. After exiting time-domain scheduling, the first network node can independently determine air interface resources, compete for air interface space on those resources, and transmit data after successfully acquiring the air interface, without being controlled by the control node.

[0013] On the other hand, when the alarm message is used to indicate that the first network node has not withdrawn from the time-domain scheduling (for example, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or the first network node applies to withdraw from the time-domain scheduling), the control node can perform the alarm message-related operation in either of the following two ways.

[0014] Method 1: The control node can stop performing time-domain scheduling on the first network node based on the alarm message and send an exit indication message to the first network node. The exit indication message is used to instruct the first network node to exit the time-domain scheduling. After receiving the exit indication message, the first network node can exit the time-domain scheduling. After exiting the time-domain scheduling, the first network node can compete for the air interface on its own and transmit data after winning the air interface, without being controlled by the control node.

[0015] Method 2: 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 its scheduling order is in the time-domain scheduling process. Optionally, the control node can increase the priority of the first network node to the highest or second highest level. In this way, by increasing the priority of the first network node, it can be scheduled by the controller in the time domain more quickly. In Method 2, 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, and the earlier it can compete for the air interface resources allocated to it, thereby enabling it to transmit data as soon as possible.

[0016] Optionally, the first network node sends the alarm message if it does not receive the 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 via 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; the alarm message is also used to indicate the unscheduled duration; the unscheduled duration is the duration during which the first network node has not received the scheduling message after sending service information. The longer the unscheduled duration, the higher the priority of the first network node after the upgrade. Of course, the unscheduled duration may also be unrelated to this priority, and this embodiment of the application does not limit this.

[0017] 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 the 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 an abnormality in the control node or by an abnormality in the communication link between the control node and the first 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 alert it to this timeout situation.

[0018] When the alarm condition is that the first network node does not receive a scheduling message within the timeout period after sending service information, the alarm message can also be used to indicate the unscheduled duration and the waiting time of the first network node's buffer queue's head packet. The longer the waiting time, the higher the priority of the promoted first network node. Of course, this priority can also be independent of the waiting time.

[0019] When the control node performs alarm message-related operations using method 2, if the alarm message indicates the aforementioned unscheduled duration, the control node can further increase the priority of the first network node based on this unscheduled duration, ensuring that the increased priority of the first network node is positively correlated with the unscheduled duration. For example, if the unscheduled duration is greater than a first duration threshold, the priority of the first network node is increased to the first priority; if the unscheduled duration is less than or equal to the first duration threshold, the priority of the first network node is increased to the second priority; the first priority is higher than the second priority. Therefore, the longer the unscheduled duration, the higher the increased priority of the first network node.

[0020] When the control node performs alarm message-related operations using method 2, if the alarm message indicates the aforementioned waiting time, the control node can further increase the priority of the first network node based on the waiting time, ensuring that the increased priority of the first network node is positively correlated with the waiting time. For example, if the waiting time is greater than a second time threshold, the priority of the first network node is increased to the third priority; if the waiting time is less than or equal to the second time threshold, the priority of the first network node is increased to the fourth priority; the third priority is higher than the fourth priority. Therefore, the longer the waiting time, the higher the increased priority of the first network node.

[0021] Optionally, the alarm message includes: a field indicating whether to exit time-domain scheduling, a field indicating unscheduled duration, and a field indicating first packet delay; the field indicating whether to exit time-domain scheduling is used to indicate whether the first network node has exited the time-domain scheduling; the field indicating unscheduled duration is used to indicate the unscheduled duration; and the field indicating first packet delay is used to indicate the waiting time of the first data packet in the first network node's buffer queue.

[0022] Secondly, a time-domain scheduling method is provided. This method is executed by a first network node in an FTTR network, where the first network node is any one of at least one network node in the FTTR network. The method includes: after enabling the time-domain scheduling function, the first network node sends an alarm message to the control node. The first network node is used to be time-domain scheduled by the control node under the time-domain scheduling function; the alarm message is used to indicate whether the first network node has exited the time-domain scheduling.

[0023] Furthermore, alarm messages can be implemented in various ways. For example, alarm messages can be used to indicate: the first network node continues to participate in time-domain scheduling, the first network node requests to withdraw from time-domain scheduling, or the first network node has withdrawn from time-domain scheduling.

[0024] On the one hand, if the alarm message is used to indicate that the first network node has exited the time-domain scheduling, the first network node will exit the time-domain scheduling before sending the alarm message to the control node.

[0025] On the other hand, when the alarm message is used to instruct the first network node to continue participating in time-domain scheduling, or when the first network node applies to withdraw from time-domain scheduling, the first network node can also receive a withdrawal instruction message sent by the control node after sending the alarm message to the control node. The withdrawal instruction message is used to instruct the first network node to withdraw from the time-domain scheduling. Afterward, the first network node withdraws from the time-domain scheduling according to the withdrawal instruction message.

[0026] Optionally, after enabling the time-domain scheduling function, the method further includes: sending service information to the control node, wherein the service information is information about service data that the first network node needs to transmit via the air interface; sending an alarm message to the control node, including: sending the 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, wherein the alarm message is also used to indicate the unscheduled duration, wherein the unscheduled duration is the duration during which the first network node has not received the scheduling message after sending the service information; the scheduling message is sent based on the service information, wherein the scheduling message is used to indicate the air interface resources allocated to the first network node; optionally, the alarm message is also used to indicate the waiting time of the head packet in the buffer queue of the first network node.

[0027] Optionally, the alarm message is also used to indicate the waiting time of the first network node's cache queue's head packet.

[0028] Optionally, the alarm message includes: a field indicating whether to exit time-domain scheduling, a field indicating unscheduled duration, and a field indicating first packet delay; the field indicating whether to exit time-domain scheduling is used to indicate whether the first network node has exited the time-domain scheduling; the field indicating unscheduled duration is used to indicate the unscheduled duration; and the field indicating first packet delay is used to indicate the waiting time of the first data packet in the first network node's buffer queue.

[0029] Thirdly, a time-domain scheduling device is provided, which belongs to the control node in an FTTR network. The time-domain scheduling device includes an activation module and a receiving module. The activation module is used to activate the time-domain scheduling function, and the control node is used to perform time-domain scheduling on at least one network node in the FTTR network under the time-domain scheduling function. The receiving module is used to receive an alarm message sent by a first network node; the first network node is any one of the at least one network node, and the alarm message is used to indicate whether the first network node has exited the time-domain scheduling.

[0030] Optionally, the alarm message is used to indicate that the first network node has exited the time-domain scheduling; the time-domain scheduling device further includes: a first stop module, used to stop time-domain scheduling of the first network node.

[0031] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or that the first network node applies to withdraw from the time-domain scheduling.

[0032] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or that the first network node applies to withdraw from the time-domain scheduling; the time-domain scheduling device further includes a second stop module and a sending module. The second stop module is used to stop performing the time-domain scheduling on the first network node according to the alarm message; the sending module is used to send an exit indication message to the first network node, the exit indication message being used to instruct the first network node to withdraw from the time-domain scheduling.

[0033] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or the first network node applies to withdraw from the time-domain scheduling; the time-domain scheduling device further includes: an elevation module, used to elevate the priority of the first network node according to the alarm message; the higher the priority of the network node, the earlier the network node is scheduled in the time-domain scheduling process.

[0034] Optionally, the first network node is configured to send the alarm message if it does not receive the 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 via 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; the alarm message is also used to indicate the unscheduled duration; the unscheduled duration is the duration during which the first network node does not receive the scheduling message after sending service information.

[0035] Optionally, the alarm message is also used to indicate the waiting time of the first data packet at the head of the cache queue in the first network node; the longer the waiting time, the higher the priority of the first network node after the upgrade.

[0036] Optionally, the alarm message includes: a field indicating whether to exit time-domain scheduling, a field indicating unscheduled duration, and a field indicating first packet delay; the field indicating whether to exit time-domain scheduling is used to indicate whether the first network node has exited the time-domain scheduling; the field indicating unscheduled duration is used to indicate the unscheduled duration; and the field indicating first packet delay is used to indicate the waiting time of the first data packet in the first network node's buffer queue.

[0037] Fourthly, a time-domain scheduling device, wherein the time-domain scheduling device belongs to a first network node in an FTTR network, the first network node being any one of at least one network node in the FTTR network, the time-domain scheduling device comprising: an activation module and a first transmission module. The activation module is used to activate the time-domain scheduling function, under which the first network node is time-domain scheduled by the control node; the first transmission module is used to send an alarm message to the control node, the alarm message indicating whether the first network node has exited the time-domain scheduling.

[0038] Optionally, the alarm message is used to indicate that the first network node has exited the time-domain scheduling; the time-domain scheduling device further includes: a first exit module, used to exit the time-domain scheduling before the first sending module sends an alarm message to the control node.

[0039] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or that the first network node applies to withdraw from the time-domain scheduling.

[0040] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or that the first network node applies to withdraw from the time-domain scheduling; the time-domain scheduling device further includes: a receiving module and a second withdrawal module. The receiving module is used to receive a withdrawal indication message sent by the control node after the first sending module sends an alarm message to the control node, the withdrawal indication message being used to instruct the first network node to withdraw from the time-domain scheduling; the second withdrawal module is used to withdraw from the time-domain scheduling according to the withdrawal indication message.

[0041] Optionally, the time-domain scheduling device further includes: a second sending module, configured to send service information to the control node, wherein the service information is information about service data that the first network node needs to transmit via the air interface; the first 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, wherein the alarm message is further configured to indicate the unscheduled duration, wherein the unscheduled duration is the duration during which the first network node has not received the scheduling message after sending the service information; the scheduling message is sent based on the service information, and the scheduling message is configured to indicate the air interface resources allocated to the first network node.

[0042] Optionally, the alarm message is also used to indicate the waiting time of the first network node's cache queue's head packet.

[0043] Optionally, the alarm message includes: a field indicating whether to exit time-domain scheduling, a field indicating unscheduled duration, and a field indicating first packet delay; the field indicating whether to exit time-domain scheduling is used to indicate whether the first network node has exited the time-domain scheduling; the field indicating unscheduled duration is used to indicate the unscheduled duration; and the field indicating first packet delay is used to indicate the waiting time of the first data packet in the first network node's buffer queue.

[0044] Fifthly, a time-domain scheduling device is provided, which belongs to a 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 processor is used to enable the time-domain scheduling function, and the control node is used to perform time-domain scheduling on at least one network node in the FTTR network under the time-domain scheduling function; the interface is used to receive an alarm message sent by a first network node; the first network node is any one of the at least one network node, and the alarm message is used to indicate whether the first network node has exited the time-domain scheduling.

[0045] 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 processor is used to enable a time-domain scheduling function, under which the first network node is time-domain scheduled by the control node; the interface is used to send an alarm message to the control node, the alarm message indicating whether the first network node has exited the time-domain scheduling.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0066] In this embodiment of the application, the advantages of MFU's collaborative management of SFU under FTTR network are utilized. The MFU centrally decides the order in which SFU compete for the channel, so as to avoid random backoff conflicts as much as possible, thereby optimizing the overall network performance.

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

[0068] 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:

[0069] S101, the control node and at least one network node in the FTTR network all enable the time-domain scheduling function, and the control node is used to perform time-domain scheduling on the at least one network node under the time-domain scheduling function.

[0070] Both the control node and the network node 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.

[0071] In the time-domain scheduling method provided in this application embodiment, both the control node and the at least one network node mentioned above will enable the time-domain scheduling function. Then, time-domain scheduling can be performed on the at least one network node under the time-domain scheduling function. When the control node performs time-domain scheduling on the at least one network node, it allocates air interface resources to each network node (also known as centralized scheduling) and sends a scheduling message to the network node indicating the air interface resources allocated to that network node. During the time-domain scheduling process, the control node needs to allocate air interface resources for the network node within the time-domain resources. The aforementioned time-domain resources may 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; the data transmitted on the transmission resources for different time periods within these transmission resources do not interfere with each other. The network node can compete for the air interface (the air interface is also the channel, so competing for the air interface is also competing for the channel) on the air interface resources indicated by the scheduling message, and transmit data on the acquired air interface after winning the competition. When the at least one network node includes multiple network nodes, the air interface resources allocated to different network nodes may be the same or different; this application embodiment does not limit this. For example, at least two network nodes may have different time and / or frequency domains for their allocated air interface resources.

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

[0073] In addition, the activation of time-domain scheduling functions on control nodes and network nodes can be controlled by staff or by the control node itself. When controlled by the control node, it can send an activation instruction message to the network node (this action can be considered as the control node having already activated the time-domain scheduling function), instructing the network node to activate the time-domain scheduling function.

[0074] S102, The first network node sends an alarm message to the control node; the first network node is any one of at least one network node, and the alarm message is used to indicate whether the first network node has exited the time domain scheduling.

[0075] The first network node can send an alarm message to the control node when the alarm conditions are met. These alarm conditions can be implemented in various ways. For example, alarm conditions may include: the first network node receiving an alarm command from a terminal; the alarm message sending period arriving; or the first network node not receiving a scheduling message within the timeout period after sending service information.

[0076] Taking the alarm condition as an example where the first network node does not receive a scheduling message within the unscheduled period after sending service information. During the time-domain scheduling of at least one network node in the FTTR network by the control node, the first network node sends service information to the control node, and the control node sends a scheduling message to the first network node based on the service information. The service information is the information of the service data that the first network node needs to transmit through the air interface, and this service information is not empty. The scheduling message is used to indicate the air interface resources allocated to the first network node.

[0077] 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 alert it to this timeout situation.

[0078] After sending service information, the first network node can start a timer with a timeout duration (which can be called a time-domain scheduling timer parameter). If the first network node has not received a scheduling message after the timer expires, it can send an alarm message to the control node. If the first network node receives a scheduling message before the timer expires, it can close the timer.

[0079] When the alarm condition is that the first network node does not receive a scheduling message within the timeout period after sending service information, the alarm message can also be used to indicate the unscheduled duration (the duration during which the first network node has not received a scheduling message after sending service information, which can be the timeout period or longer). The alarm message can also be used to indicate the waiting time of the head packet in the first network node's buffer queue. Of course, this alarm message may also not indicate the unscheduled duration or the waiting time.

[0080] The aforementioned timeout duration can be statically configured in the first network node, or it can be indicated to the first network node by other nodes. For example, the timeout duration can be indicated by a scheduling message sent by the control node, demonstrating that the control node can configure timers (also called timers) in the first network node. Alternatively, the timeout duration can be indicated by a configuration message sent by the control node. In this case, the control node will send a configuration message indicating the timeout duration to the first network node before sending the scheduling message (e.g., after the initialization and synchronization of the control node and network node, or during the initialization process). For example, the configuration message may include a timer field indicating the aforementioned timeout duration. Furthermore, the control node can update the timeout duration via configuration messages. For instance, after sending a configuration message to the first network node, the control node can send another configuration message (indicating the updated timeout duration), after which the first network node can update the timeout duration based on this configuration message.

[0081] In summary, the time-domain scheduling method provided in this application allows for centralized control of at least one network node via a control node. The control node sends scheduling messages instructing each network node to compete for air interface resources, and after successfully acquiring an air interface, data is transmitted 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. Furthermore, the first network node can send alarm messages to the control node to alert it and instruct it whether to exit time-domain scheduling. This enriches the functionality of the first network node.

[0082] Furthermore, there are several ways to implement alarm messages.

[0083] For example, alarm information can also indicate: the first network node has exited time-domain scheduling, or the first network node has not exited time-domain scheduling.

[0084] For example, alarm messages are used to indicate: the first network node continues to participate in time-domain scheduling, the first network node applies to withdraw from time-domain scheduling, or the first network node has withdrawn from time-domain scheduling.

[0085] If the alarm message instructs the first network node to continue participating in time-domain scheduling, it indicates that the first network node has not withdrawn from time-domain scheduling. The alarm message is used to instruct the first network node to continue participating in time-domain scheduling, but it can also be replaced by an alarm message to instruct the first network node to only report alarms and not withdraw from time-domain scheduling.

[0086] If the alarm message indicates that the first network node requests to exit time-domain scheduling, it means that the first network node needs to exit time-domain scheduling, but has not yet exited time-domain scheduling. Therefore, the alarm message is used to indicate that the first network node has not exited time-domain scheduling.

[0087] If the alarm message indicates that the first network node has exited time-domain scheduling, it means that the first network node has not yet exited time-domain scheduling. Therefore, the alarm message is used to indicate that the first network node has exited time-domain scheduling.

[0088] In addition, the first network node exiting time-domain scheduling can also be understood as the first network node disabling the time-domain scheduling function.

[0089] Upon receiving an alarm message, the control node can perform operations related to that alarm message. For example, it can display the alarm message to staff; or it can determine, based on the alarm message, whether it is necessary to control the first network node to exit time-domain scheduling, and if it is determined that it is not necessary to control the first network node to exit time-domain scheduling, whether it is necessary to perform operations to enable the first network node to be scheduled quickly.

[0090] On the one hand, when an alarm message indicates that the first network node has exited time-domain scheduling, the first network node can exit time-domain scheduling before sending an alarm message to the control node. Upon receiving the alarm message, the control node can stop time-domain scheduling for the first network node. After exiting time-domain scheduling, the first network node can independently determine air interface resources, compete for air interface space on those resources, and transmit data after successfully acquiring the air interface, without being controlled by the control node.

[0091] On the other hand, when the alarm message is used to instruct the first network node to continue participating in time-domain scheduling, or when the first network node requests to withdraw from time-domain scheduling, the control node can perform the alarm message-related operation in either of the following two ways.

[0092] Method 1: The control node can stop time-domain scheduling of the first network node based on the alarm message. Furthermore, since the first network node has not yet exited time-domain scheduling, the control node also needs to send an exit indication message to the first network node, instructing it to exit time-domain scheduling. After receiving this exit indication message, the first network node can exit time-domain scheduling. After exiting time-domain scheduling, the first network node can independently compete for the air interface and transmit data after successfully acquiring it, without being controlled by the control node.

[0093] Method 2: The control node can elevate the priority of the first network node based on alarm messages. The higher the priority of a network node, the earlier it will be scheduled during the time-domain scheduling process. Optionally, the control node can elevate the priority of the first network node to the highest or second highest level. In this way, by increasing the priority of the first network node, it can be scheduled by the controller in the time domain more quickly. In Method 2, the control node can schedule network nodes in a certain order. The earlier a network node is scheduled, the earlier it 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.

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

[0095] When the control node performs alarm message-related operations using method 2, if the alarm message indicates the aforementioned unscheduled duration, the control node can further increase the priority of the first network node based on this unscheduled duration, ensuring that the increased priority of the first network node is positively correlated with the unscheduled duration. For example, if the unscheduled duration is greater than a first duration threshold, the priority of the first network node is increased to the first priority; if the unscheduled duration is less than or equal to the first duration threshold, the priority of the first network node is increased to the second priority; the first priority is higher than the second priority. Therefore, the longer the unscheduled duration, the higher the increased priority of the first network node.

[0096] When the control node performs alarm message-related operations using method 2, if the alarm message indicates the aforementioned waiting time, the control node can further increase the priority of the first network node based on the waiting time, ensuring that the increased priority of the first network node is positively correlated with the waiting time. For example, if the waiting time is greater than a second time threshold, the priority of the first network node is increased to the third priority; if the waiting time is less than or equal to the second time threshold, the priority of the first network node is increased to the fourth priority; the third priority is higher than the fourth priority. Therefore, the longer the waiting time, the higher the increased priority of the first network node.

[0097] The first network node stores the data to be transmitted in a buffer queue. Upon receiving a scheduling message, the first network node transmits the data packet at the head of the buffer queue according to the scheduling message, thus achieving sequential transmission of each data packet in the buffer queue. The alarm message sent by the first network node can also indicate the waiting time of the current head data packet, which is the time between the completion of the previous head data packet transmission and the time the alarm message is sent. If the waiting time of the head data packet is long, the priority of the promoted first network node will be higher, so that the control node will allocate air interface resources to the first network node first and send scheduling messages to the first network node first, ensuring that the head data packet is transmitted as soon as possible.

[0098] In addition, when the alarm message is used to indicate both the unscheduled duration and the waiting duration, the control node can also increase the priority of the first network node based on the unscheduled duration and the waiting duration, so that the priority of the first network node after the increase is positively correlated with both the unscheduled duration and the waiting duration.

[0099] It is understandable that regardless of whether the alarm message is used to instruct the first network node to continue participating in time-domain scheduling or to request to withdraw from time-domain scheduling, the control node can execute the alarm message-related operations using either Method 1 or Method 2. Therefore, regardless of whether the first network node sends an alarm message to instruct it to continue participating in time-domain scheduling or to request to withdraw from time-domain scheduling, the control node can agree with the content indicated by the alarm message and thus execute the alarm message-related operations using Method 1 or Method 2, which are compatible with the alarm message. Of course, the control node can also disagree with the content indicated by the alarm message and thus execute the alarm message-related operations using Method 1 or Method 2, which are not compatible with the alarm message. For example, when the alarm message is used to instruct the first network node to continue participating in time-domain scheduling, the method compatible with the alarm message is Method 2; when the alarm message is used to instruct the first network node to request to withdraw from time-domain scheduling, the method compatible with the alarm message is Method 1.

[0100] In addition, the alarm message may not be used to indicate at least one of the above-mentioned unscheduled duration and waiting duration. The adjusted priority may not be positively correlated with the unscheduled duration, and the adjusted priority may not be positively correlated with the waiting duration. This application embodiment does not limit this.

[0101] Optionally, the alarm message may include multiple fields. For example, as shown in Figure 5, the alarm message includes a field indicating whether the time-domain scheduling has been exited, a field indicating the duration of non-scheduling, and a field indicating the first packet delay. These fields can be arranged sequentially from left to right in Figure 5. However, they may not be arranged in this order. This embodiment uses the example of an alarm message including these fields as an example. It is understood that the alarm message may also include at least one of these fields. For instance, the alarm message may include the field indicating whether the time-domain scheduling has been exited, but not the fields indicating the duration of non-scheduling or the first packet delay.

[0102] The "Exit Time-Domain Scheduling" field indicates whether the first network node has exited time-domain scheduling. The "Unscheduled Duration" field indicates the aforementioned unscheduled duration; the "First Packet Delay" field indicates the aforementioned waiting time.

[0103] Furthermore, the "Exit Time-Domain Scheduling" field can include one or more bytes. Three of the various state values ​​for this field can respectively indicate that the first network node continues to participate in time-domain scheduling, that the first network node requests to exit time-domain scheduling, and that the first network node has already exited time-domain scheduling. For example, when the state value of the "Exit Time-Domain Scheduling" field is 0, it indicates that the first network node continues to participate in time-domain scheduling; when the state value is 1, it indicates that the first network node requests to exit time-domain scheduling; and when the state value is 2, it indicates that the first network node has already exited time-domain scheduling. Of course, the correspondence between the state values ​​of the "Exit Time-Domain Scheduling" field and the content it needs to indicate can also be different. For example, the state values ​​0 and 1 can be interchanged to indicate different content. Alternatively, at least one of the above state values ​​0, 1, and 2 can be changed to a state value other than 0, 1, or 2.

[0104] The Unscheduled Duration field can include one or more (e.g., four) bytes, and the unit of the duration indicated by the Unscheduled Duration field can be microseconds. The First Packet Delay field can include one or more (e.g., two) bytes, and the unit of the duration indicated by the First Packet Delay field can be milliseconds.

[0105] For example, one example of an alarm message can be shown in Table 1.

[0106] Table 1

[0107] In one alternative implementation, Table 1 can also be replaced with Table 2.

[0108] Table 2

[0109] It is understood that the number of bytes in each field in the embodiments of this application may also be different from the number of bytes exemplified here, and the correspondence between the status value of the field and the content it indicates may also be different from that exemplified in this application.

[0110] For example, in Table 1, the status value of 1 indicates that the first network node continues to participate in time-domain scheduling; the status value of 2 indicates that the first network node applies to withdraw from time-domain scheduling; and the status value of 0 indicates that the first network node has withdrawn from time-domain scheduling.

[0111] 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 "Whether to Exit Time-Domain Scheduling" field is empty, the message is used to instruct the first network node to continue participating in time-domain scheduling.

[0112] 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 an activation module 601 and a receiving module 602. The activation module 601 is used to activate the time-domain scheduling function, and the control node is used to perform time-domain scheduling on at least one network node in the FTTR network under the time-domain scheduling function. The receiving module 602 is used to receive an alarm message sent by a first network node; the first network node is any one of the at least one network node, and the alarm message is used to indicate whether the first network node has exited the time-domain scheduling. The operations performed by the activation module 601 can refer to the operations related to the control node in S101 of the aforementioned embodiment, and the operations performed by the receiving module 602 can refer to the operations related to the control node in S102 of the aforementioned embodiment.

[0113] Optionally, the alarm message is used to indicate that the first network node has exited the time-domain scheduling; the time-domain scheduling device further includes: a first stop module (not shown in FIG6), used to stop the time-domain scheduling of the first network node.

[0114] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or that the first network node applies to withdraw from the time-domain scheduling.

[0115] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or that the first network node applies to withdraw from the time-domain scheduling; the time-domain scheduling device further includes: a second stop module (not shown in Figure 6) and a sending module (not shown in Figure 6). The second stop module is used to stop the time-domain scheduling of the first network node according to the alarm message; the sending module is used to send an exit indication message to the first network node, the exit indication message being used to instruct the first network node to withdraw from the time-domain scheduling.

[0116] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or the first network node applies to withdraw from the time-domain scheduling; the time-domain scheduling device further includes: an elevation module (not shown in FIG6), used to elevate the priority of the first network node according to the alarm message; the higher the priority of the network node, the earlier the network node is scheduled in the time-domain scheduling process.

[0117] Optionally, the first network node sends the alarm message if it does not receive the 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 via 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; the alarm message is also used to indicate the unscheduled duration; the unscheduled duration is the duration during which the first network node has not received the scheduling message after sending service information. Optionally, the longer the unscheduled duration, the higher the priority of the first network node after the upgrade.

[0118] Optionally, the alarm message is further used to indicate the waiting time of the first network node's cached data packet at the head of the queue. Optionally, the longer the waiting time, the higher the priority of the first network node after the upgrade.

[0119] Optionally, the alarm message includes: a "whether to exit time-domain scheduling" field, an "unscheduled duration" field, and a "first packet delay" field; the "whether to exit time-domain scheduling" field indicates whether the first network node has exited the time-domain scheduling; the "unscheduled duration" field indicates the unscheduled duration; and the "first packet delay" field indicates the waiting time of the first data packet in the first network node's buffer queue. In this embodiment, the alarm message includes the "whether to exit time-domain scheduling" field, the "unscheduled duration" field, and the "first packet delay" field as an example. It can be understood that the alarm message may also include at least one of these fields. For example, the alarm message may include the "whether to exit time-domain scheduling" field but not the "unscheduled duration" field and the "first packet delay" field.

[0120] 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: an activation module 701 and a first transmission module 702. The activation module 701 is used to activate the time-domain scheduling function, and the first network node is used to be time-domain scheduled by the control node under the time-domain scheduling function. The first transmission module 702 is used to send an alarm message to the control node, and the alarm message is used to indicate whether the first network node has exited the time-domain scheduling. The operation performed by the activation 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 first transmission module 702 can refer to the operation related to the first network node in S102 of the aforementioned embodiment.

[0121] Optionally, the alarm message is used to indicate that the first network node has exited the time-domain scheduling; the time-domain scheduling device further includes: a first exit module, used to exit the time-domain scheduling before the first sending module sends an alarm message to the control node.

[0122] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or that the first network node applies to withdraw from the time-domain scheduling.

[0123] Optionally, the alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or that the first network node applies to withdraw from the time-domain scheduling; the time-domain scheduling device further includes: a receiving module and a second withdrawal module. The receiving module is used to receive a withdrawal indication message sent by the control node after the first sending module sends an alarm message to the control node, the withdrawal indication message being used to instruct the first network node to withdraw from the time-domain scheduling; the second withdrawal module is used to withdraw from the time-domain scheduling according to the withdrawal indication message.

[0124] Optionally, the time-domain scheduling device further includes: a second sending module, configured to send service information to the control node, wherein the service information is information about service data that the first network node needs to transmit via the air interface; the first 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, wherein the alarm message is further configured to indicate the unscheduled duration, wherein the unscheduled duration is the duration during which the first network node has not received the scheduling message after sending the service information; the scheduling message is sent based on the service information, and the scheduling message is configured to indicate the air interface resources allocated to the first network node.

[0125] Optionally, the alarm message is also used to indicate the waiting time of the first network node's cache queue's head packet.

[0126] Optionally, the alarm message includes: a "whether to exit time-domain scheduling" field, an "unscheduled duration" field, and a "first packet delay" field; the "whether to exit time-domain scheduling" field indicates whether the first network node has exited the time-domain scheduling; the "unscheduled duration" field indicates the unscheduled duration; and the "first packet delay" field indicates the waiting time of the first data packet in the first network node's buffer queue. In this embodiment, the alarm message includes the "whether to exit time-domain scheduling" field, the "unscheduled duration" field, and the "first packet delay" field as an example. It can be understood that the alarm message may also include at least one of these fields. For example, the alarm message may include the "whether to exit time-domain scheduling" field but not the "unscheduled duration" field and the "first packet delay" field.

[0127] 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's embodiments. 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's embodiments. For example, the processor is used to enable the time-domain scheduling function, and the control node is used to perform time-domain scheduling on at least one network node in the FTTR network under the time-domain scheduling function; the interface is used to receive an alarm message sent by a first network node; the first network node is any one of the at least one network node, and the alarm message is used to indicate whether the first network node has exited the time-domain scheduling.

[0128] 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 first network node performs the sending and receiving operations, while the processor performs other operations (i.e., processing operations) performed by the first network node in any design provided in this application. For example, the processor is used to enable the time-domain scheduling function, under which the first network node is time-domain scheduled by the control node; the interface is used to send an alarm message to the control node, indicating whether the first network node has exited the time-domain scheduling.

[0129] 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 the time-domain scheduling method described in any design of this application embodiment; the first network node is used to execute the operations performed by the first network node in the time-domain scheduling method provided in any design of this application embodiment, wherein the first network node is any one of the at least one network node.

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

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

[0132] 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 the operations executed by the control node or the first network node in any of the time-domain scheduling methods provided in the embodiments of this application.

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

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

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

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

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

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

[0139] 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 control node in a fiber-to-the-room (FTTR) network, and the method includes: Enable time-domain scheduling function, and the control node is used to perform time-domain scheduling on at least one network node in the FTTR network under the time-domain scheduling function. Receive an alarm message sent by a first network node; the first network node is any one of the at least one network nodes, and the alarm message is used to indicate whether the first network node has exited the time-domain scheduling.

2. The method according to claim 1, characterized in that, The alarm message is used to indicate that the first network node has exited the time-domain scheduling. The method further includes: stopping time-domain scheduling of the first network node.

3. The method according to claim 1, characterized in that, The alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or the first network node applies to withdraw from the time-domain scheduling.

4. The method according to claim 3, characterized in that, The method further includes: Stop the time-domain scheduling of the first network node according to the alarm message; Send an exit indication message to the first network node, the exit indication message being used to instruct the first network node to exit the time-domain scheduling.

5. The method according to claim 3, characterized in that, The method further includes: The priority of the first network node is increased according to the alarm message; the higher the priority of the network node, the earlier the network node is scheduled in the time-domain scheduling process.

6. The method according to any one of claims 1 to 5, characterized in that, The alarm message includes: whether to exit time-domain scheduling; The "exit time-domain scheduling" field is used to indicate whether the first network node has exited the time-domain scheduling.

7. The method according to any one of claims 1 to 6, characterized in that, The first network node is used to send the alarm message if it does not receive the scheduling message sent by the control node within the timeout period after sending the service information; The service information refers to the service data that the first network node needs to transmit via 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; The alarm message is also used to indicate the unscheduled duration; the unscheduled duration is the duration during which the first network node does not receive the scheduling message after sending service information.

8. The method according to claim 7, characterized in that, The alarm message includes an unscheduled duration field; the unscheduled duration field is used to indicate the unscheduled duration.

9. The method according to any one of claims 1 to 8, characterized in that, The alarm message is also used to indicate the waiting time of the first data packet in the cache queue of the first network node.

10. The method according to claim 9, characterized in that, The alarm message includes a first packet delay field, which indicates the waiting time.

11. A time-domain scheduling method, characterized in that, The method is performed by a first network node in a fiber-to-the-room (FTTR) network, wherein the first network node is any one of at least one network node in the FTTR network, and the method includes: Enable time-domain scheduling function, and the first network node is used to be time-domain scheduled by the control node under the time-domain scheduling function; An alarm message is sent to the control node, the alarm message being used to indicate whether the first network node has exited the time-domain scheduling.

12. The method according to claim 11, characterized in that, The alarm message is used to indicate that the first network node has exited the time-domain scheduling. Before sending an alarm message to the control node, the method further includes: exiting the time-domain scheduling.

13. The method according to claim 11, characterized in that, The alarm message is used to indicate that the first network node continues to participate in the time-domain scheduling, or the first network node applies to withdraw from the time-domain scheduling.

14. The method according to claim 13, characterized in that, After sending an alarm message to the control node, the method further includes: The control node sends an exit indication message, which instructs the first network node to exit the time-domain scheduling. Exit the time-domain scheduling according to the exit instruction message.

15. The method according to any one of claims 11 to 14, characterized in that, The alarm message includes a field indicating whether the first network node has exited the time-domain scheduling.

16. The method according to any one of claims 11 to 15, characterized in that, After enabling the time-domain scheduling function, the method further includes: sending service information to the control node, wherein the service information is information about the service data that the first network node needs to transmit over the air interface; Sending an alarm message to the control node includes: sending the alarm message to the control node when no scheduling message is received from the control node within a timeout period after sending the service information; the alarm message is also used to indicate the unscheduled duration, which is the duration during which the first network node has not received the scheduling message 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.

17. The method according to claim 16, characterized in that, The alarm message includes: the unscheduled duration field; The unscheduled duration field is used to indicate the unscheduled duration.

18. The method according to any one of claims 11 to 17, characterized in that, The alarm message is also used to indicate the waiting time of the first data packet in the cache queue of the first network node.

19. The method according to claim 18, characterized in that, The alarm message includes: the first packet delay field; The first packet delay field is used to indicate the waiting time.

20. 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: An activation module is used to enable the time-domain scheduling function, and the control node is used to perform time-domain scheduling on at least one network node in the FTTR network under the time-domain scheduling function. A receiving module is used to receive an alarm message sent by a first network node; the first network node is any one of the at least one network node, and the alarm message is used to indicate whether the first network node has exited the time-domain scheduling.

21. A time-domain scheduling device, characterized in that, The time-domain scheduling device belongs to the first network node in the 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: The enabling module is used to enable the time-domain scheduling function, and the first network node is used to be time-domain scheduled by the control node under the time-domain scheduling function. The first sending module is used to send an alarm message to the control node, the alarm message being used to indicate whether the first network node has exited the time-domain scheduling.

22. A time-domain scheduling system, characterized in that, The time-domain scheduling system includes a control node and at least one network node in the fiber-to-room (FTTR) network. The control node is used to execute the time-domain scheduling method according to any one of claims 1 to 10; The first network node is used to execute the time-domain scheduling method according to any one of claims 11 to 19, wherein the first network node is any one of the at least one network node.

Images