Time-domain scheduling methods, devices and systems

Abstract

A time-domain scheduling method, apparatus, and system belong to the field of communication technology. The method is executed by a control node in an FTTR network. In this method, the control node sends an enable instruction message to a first network node to indicate whether to enable the time-domain scheduling function, and receives an enable confirmation message from the first network node confirming the enable of the time-domain scheduling function. The first network node is any one of at least one network node in the FTTR network. The enable confirmation message indicates whether the first network node has enabled the time-domain scheduling function. This application helps avoid random backoff conflicts on the air interface and can improve transmission efficiency in the network. This application is applicable to FTTR networks.

Description

[0001] This application is a divisional application. The original application has the application number 202411569906.5 and the original application date is November 4, 2024. The entire contents of the original application 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 subFTTR 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: the control node sending an enable instruction message to a first network node to indicate whether to enable the time-domain scheduling function, and then receiving an enable confirmation message for the time-domain scheduling function from the first network node. The first network node is any one of at least one network node in the FTTR network; the enable confirmation message indicates whether the first network node enables the time-domain scheduling function.

[0008] After confirming that the first network node has successfully enabled the time-domain scheduling function, the control node can begin time-domain scheduling of the first network node. Once all at least one network node has enabled the time-domain scheduling function, the control node can perform time-domain scheduling on that at least one network node. When performing time-domain scheduling on the at least one network node, the control node allocates air interface resources to each network node (also known as centralized scheduling) and sends scheduling messages to the network nodes indicating the air interface resources allocated to them. Network nodes can compete for air interface resources (air interface is also a channel, so competing for air interface is also competing for channel) on the air interface resources indicated in 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 air interface resources allocated in different time and / or frequency domains. During the time-domain scheduling process, the control node needs to allocate air interface resources to the network nodes 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 do not interfere with each other.

[0009] As can be seen, in the time-domain scheduling method provided in this application embodiment, the control node instructs the network nodes to enable the time-domain scheduling function, so as to facilitate the centralized control of at least one network node by the control node. This allows the control node to send scheduling messages instructing each network node to compete for air interface resources on the corresponding air interface, and then transmit data on the acquired air interface after successfully competing for it. Therefore, this method helps to avoid random backoff conflicts between network nodes, reduces interference between air interfaces of network nodes, improves air interface efficiency, reduces retransmission rate, reduces latency, and increases throughput.

[0010] For example, the activation indication message includes: a time-domain scheduling activation field and a version number field; the time-domain scheduling activation field is used to indicate that the time-domain scheduling function is activated; the version number field is used to indicate the version number of the time-domain scheduling function.

[0011] Optionally, when the activation confirmation message is used to indicate that the first network node has not enabled the time-domain scheduling function, the activation confirmation message is also used to indicate the reason why the time-domain scheduling function has not been enabled. It is understood that the first network node may have failed to enable the time-domain scheduling function for various reasons, such as the first network node disabling the aforementioned time-domain scheduling function, or the first network node not supporting this time-domain scheduling function (e.g., the version number of the time-domain scheduling function supported by the first network node is different from the version number of the time-domain scheduling function in the previous activation indication message). Feeding back the reason why the time-domain scheduling function has not been enabled to the control node facilitates the control node's handling of the reason, or facilitates the control node's feedback of the reason to the staff for handling.

[0012] For example, the activation confirmation message includes: a feedback type field, a time-domain scheduling activation field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling activation field is used to indicate that the time-domain scheduling function is enabled; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0013] Optionally, after receiving the enable confirmation message for the time-domain scheduling function sent by the first network node, the control node may also send a disable instruction message to the first network node to indicate whether to disable the time-domain scheduling function; then, it receives the disable confirmation message for the time-domain scheduling function sent by the first network node, the disable confirmation message being used to indicate whether the first network node disables the time-domain scheduling function.

[0014] Optionally, the shutdown indication message includes: a time-domain scheduling shutdown field and a version number field; the time-domain scheduling shutdown field is used to indicate the shutdown of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0015] Optionally, when the shutdown confirmation message is used to indicate that the first network node has not shut down the time-domain scheduling function, the shutdown confirmation message is also used to indicate the reason for not shutting down the time-domain scheduling function.

[0016] For example, the closure confirmation message includes: a feedback type field, a time-domain scheduling closure field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling closure field is used to indicate that the time-domain scheduling function is closed; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0017] Optionally, before sending an enable instruction message to the first network node to indicate the enabling of the time-domain scheduling function, the control node may also send a configuration message to the first network node, the configuration message being used to indicate at least one functional parameter of the time-domain scheduling function.

[0018] For example, the configuration message includes a timer field, and the at least one functional parameter includes the timeout duration of the timer, the timer field being used to indicate the timeout duration.

[0019] Optionally, before sending the enable instruction message for enabling the time-domain scheduling function to the first network node, the control node may also determine whether the time-domain scheduling function needs to be enabled. If it is determined that the time-domain scheduling function needs to be enabled, the control node may send the enable instruction message to the first network node.

[0020] 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 receiving an activation instruction message from a control node in the FTTR network, the first network node activates the time-domain scheduling function according to the activation instruction message; subsequently, the first network node sends an activation confirmation message for the time-domain scheduling function to the control node, the activation confirmation message indicating whether the first network node has activated the time-domain scheduling function.

[0021] Optionally, the activation indication message includes: a time-domain scheduling activation field and a version number field; the time-domain scheduling activation field is used to indicate the activation of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0022] Optionally, when the enable confirmation message is used to indicate that the first network node has not enabled the time-domain scheduling function, the enable confirmation message is also used to indicate the reason why the time-domain scheduling function has not been enabled.

[0023] Optionally, the activation confirmation message includes: a feedback type field, a time-domain scheduling activation field, and a version number field; The feedback type field is used to indicate whether the execution was successful and the reason for failure; the time domain scheduling enable field is used to indicate that the time domain scheduling function is enabled; the version number field is used to indicate the version number of the time domain scheduling function.

[0024] Optionally, after sending the activation confirmation message of the time-domain scheduling function to the control node, the first network node may also receive a shutdown indication message sent by the control node to indicate that the time-domain scheduling function should be shut down, and start shutting down the time-domain scheduling function according to the shutdown indication message; then, the first network node sends a shutdown confirmation message of the time-domain scheduling function to the control node, the shutdown confirmation message being used to indicate whether the first network node should shut down the time-domain scheduling function.

[0025] Optionally, the shutdown indication message includes: a time-domain scheduling shutdown field and a version number field; the time-domain scheduling shutdown field is used to indicate the shutdown of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0026] Optionally, when the shutdown confirmation message is used to indicate that the first network node has not shut down the time-domain scheduling function, the shutdown confirmation message is also used to indicate the reason for not shutting down the time-domain scheduling function.

[0027] Optionally, the shutdown confirmation message includes: a feedback type field, a time-domain scheduling shutdown field, and a version number field; The feedback type field is used to indicate whether the execution was successful and the reason for failure; the time domain scheduling disable field is used to indicate that the time domain scheduling function is disabled; the version number field is used to indicate the version number of the time domain scheduling function.

[0028] Optionally, the method further includes: before receiving an enable instruction message sent by a control node in the FTTR network to indicate the enabling of the time-domain scheduling function, the first network node receives a configuration message sent by the control node, the configuration message being used to indicate at least one functional parameter of the time-domain scheduling function; after enabling the time-domain scheduling function, the first network node runs the time-domain scheduling function according to the at least one functional parameter.

[0029] Optionally, the configuration message includes a timer field, and the at least one functional parameter includes the timeout duration of the timer, the timer field being used to indicate the timeout duration.

[0030] 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 transmitting module and a first receiving module. The first transmitting module is used to send an activation indication message to a first network node, which is any one of at least one network node in the FTTR network, to indicate whether the first network node has activated the time-domain scheduling function. The first receiving module is used to receive an activation confirmation message for the time-domain scheduling function sent by the first network node, which indicates whether the first network node has activated the time-domain scheduling function.

[0031] Optionally, the activation indication message includes: a time-domain scheduling activation field and a version number field; the time-domain scheduling activation field is used to indicate the activation of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0032] Optionally, when the enable confirmation message is used to indicate that the first network node has not enabled the time-domain scheduling function, the enable confirmation message is also used to indicate the reason why the time-domain scheduling function has not been enabled.

[0033] Optionally, the activation confirmation message includes: a feedback type field, a time-domain scheduling activation field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling activation field is used to indicate that the time-domain scheduling function is enabled; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0034] Optionally, the time-domain scheduling device further includes: a second sending module, configured to send a shutdown indication message to the first network node to indicate that the time-domain scheduling function is to be shut down; and a second receiving module, configured to receive a shutdown confirmation message of the time-domain scheduling function sent by the first network node, wherein the shutdown confirmation message is used to indicate whether the first network node has shut down the time-domain scheduling function.

[0035] Optionally, the shutdown indication message includes: a time-domain scheduling shutdown field and a version number field; the time-domain scheduling shutdown field is used to indicate the shutdown of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0036] Optionally, when the shutdown confirmation message is used to indicate that the first network node has not shut down the time-domain scheduling function, the shutdown confirmation message is also used to indicate the reason for not shutting down the time-domain scheduling function.

[0037] Optionally, the closure confirmation message includes: a feedback type field, a time-domain scheduling closure field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling closure field is used to indicate that the time-domain scheduling function is closed; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0038] Optionally, the time-domain scheduling device further includes: a third sending module, configured to send a configuration message to the first network node, the configuration message being used to indicate at least one functional parameter of the time-domain scheduling function.

[0039] Optionally, the configuration message includes a timer field, and the at least one functional parameter includes the timeout duration of the timer, the timer field being used to indicate the timeout duration.

[0040] Optionally, the time-domain scheduling device further includes: a judgment module, used to judge whether the time-domain scheduling function needs to be enabled; and a first sending module, used to send the enable instruction message to the first network node when the judgment module determines that the time-domain scheduling function needs to be enabled.

[0041] Fourthly, a time-domain scheduling device is provided, the time-domain scheduling device belonging to a first network node, the first network node being any one of at least one network node in a fiber-to-the-room (FTTR) network, the time-domain scheduling device comprising: a first receiving module, configured to receive an activation indication message sent by a control node in the FTTR network, indicating the activation of a time-domain scheduling function; an activation module, configured to activate the time-domain scheduling function according to the activation indication message; and a first sending module, configured to send an activation confirmation message of the time-domain scheduling function to the control node, the activation confirmation message indicating whether the first network node has activated the time-domain scheduling function.

[0042] Optionally, the activation indication message includes: a time-domain scheduling activation field and a version number field; the time-domain scheduling activation field is used to indicate the activation of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0043] Optionally, when the enable confirmation message is used to indicate that the first network node has not enabled the time-domain scheduling function, the enable confirmation message is also used to indicate the reason why the time-domain scheduling function has not been enabled.

[0044] Optionally, the activation confirmation message includes: a feedback type field, a time-domain scheduling activation field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling activation field is used to indicate that the time-domain scheduling function is enabled; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0045] Optionally, the time-domain scheduling device further includes: a second receiving module, configured to receive a shutdown indication message sent by the control node, indicating to disable the time-domain scheduling function; a shutdown module, configured to start disabling the time-domain scheduling function according to the shutdown indication message; and a second sending module, configured to send a shutdown confirmation message of the time-domain scheduling function to the control node, the shutdown confirmation message indicating whether the first network node disables the time-domain scheduling function.

[0046] Optionally, the shutdown indication message includes: a time-domain scheduling shutdown field and a version number field; the time-domain scheduling shutdown field is used to indicate the shutdown of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0047] Optionally, when the shutdown confirmation message is used to indicate that the first network node has not shut down the time-domain scheduling function, the shutdown confirmation message is also used to indicate the reason for not shutting down the time-domain scheduling function.

[0048] Optionally, the closure confirmation message includes: a feedback type field, a time-domain scheduling closure field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling closure field is used to indicate that the time-domain scheduling function is closed; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0049] Optionally, the time-domain scheduling device further includes: a third receiving module, configured to receive a configuration message sent by the control node before receiving an activation indication message sent by the control node in the FTTR network, the configuration message indicating at least one functional parameter of the time-domain scheduling function; and a running module, configured to run the time-domain scheduling function according to the at least one functional parameter after the activation module activates the time-domain scheduling function.

[0050] Optionally, the configuration message includes a timer field, and the at least one functional parameter includes the timeout duration of the timer, the timer field being used to indicate the timeout duration.

[0051] 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 interface is used to send an activation indication message to a first network node indicating whether to activate the time-domain scheduling function; the first network node is any one of at least one network node in the FTTR network; the interface is also used to receive an activation confirmation message for the time-domain scheduling function sent by the first network node, the activation confirmation message indicating whether the first network node has activated the time-domain scheduling function.

[0052] 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 receive an activation indication message sent by a control node in the FTTR network, indicating whether to activate the time-domain scheduling function; the processor is used to activate the time-domain scheduling function according to the activation indication message; and the interface is used to send an activation confirmation message of the time-domain scheduling function to the control node, the activation confirmation message indicating whether the first network node has activated the time-domain scheduling function.

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

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

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

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

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

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

[0059] Figure 1 A schematic diagram of an FTTR network provided in an embodiment of this application; Figure 2 A schematic diagram of another FTTR network provided in an embodiment of this application; Figure 3 A schematic diagram of another FTTR network provided in an embodiment of this application; Figure 4 A flowchart illustrating a time-domain scheduling method provided in an embodiment of this application; Figure 5 A schematic diagram of an enable instruction message provided in an embodiment of this application; Figure 6 This is a schematic diagram illustrating an activation confirmation message provided in an embodiment of this application; Figure 7 A flowchart illustrating another time-domain scheduling method provided in this application embodiment; Figure 8 A schematic diagram of a shutdown instruction message provided in an embodiment of this application; Figure 9 A schematic diagram of a closing confirmation message provided in an embodiment of this application; Figure 10 A schematic diagram of a scheduling message provided in an embodiment of this application; Figure 11 A block diagram of a time-domain scheduling device provided in an embodiment of this application; Figure 12 A block diagram of another time-domain scheduling device provided in an embodiment of this application. Detailed Implementation

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

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

[0062] This application's embodiments are applicable 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. The SFU can be an edge optical network terminal (edgeONT) or an access point (AP), that is, it can act as a network node in a wireless network. Please refer to... Figure 1 In FTTR application scenarios, a main FTTR unit (MFU) is deployed to manage the SFU. The MFU can be an optical gateway, optical network terminal (ONT), or passive optical network (PON) gateway, etc., which means it can act as a control node in the wireless network.

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

[0064] As an example, let's consider an MFU as an optical gateway and an SFU as an edge ONT. See [link / reference] Figure 2The diagram illustrates a topology of an optical communication system applied to FTTR. The 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 EdgeONT. 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 one 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 solutions, this improves the real-time performance of optical gateway management. Terminal devices can access the edge ONTs to achieve network communication.

[0065] As another example, let's take the MFU as the optical gateway, implemented using an ONT, and the SFU as the AP. See [link / reference] Figure 3 The diagram shows a different optical communication system topology for home networks. 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.

[0066] FTTR optical communication systems can employ PON. PON can be gigabit-capable PON (GPON), Ethernet passive optical network (EPON), 10 Gb / s Ethernet passive optical network (10G-EPON), time and wavelength division multiplexing passive optical network (TWDM-PON), 10 gigabit-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.

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

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

[0069] See Figure 4 The following is an interactive flowchart of a time-domain scheduling method provided in an embodiment of this application, such as... Figure 4 As shown, the time-domain scheduling method provided in this application includes: S101, The control node sends an activation instruction message to the first network node to indicate the activation of the time-domain scheduling function.

[0070] Both the control node and the network node can belong to the FTTR network. The control node can be called an MFU, master node, master device, etc., and the network node can be called an SFU, slave node, slave device, etc. The first network node is any one of at least one network node. The at least one network node can be one network node or multiple network nodes. In this embodiment, multiple network nodes are used as an example.

[0071] Prior to S101, the control node could determine whether the time-domain scheduling function needed to be enabled. For example, the control node might execute judgment logic based on collected network parameters to determine whether the function needed to be enabled; or it might determine whether the time-domain scheduling function needed to be enabled based on instructions triggered by staff. After determining that the time-domain scheduling function needed to be enabled, the control node could send a start indication message to each network node. This start indication message indicates the time-domain scheduling function and whether it was enabled. Optionally, if the time-domain scheduling function had at least one version, the start indication message could also indicate the version number of the time-domain scheduling function. Of course, the start indication message could also omit the version number.

[0072] For example, such as Figure 5 As shown, the activation indication message includes: an activation field, a time-domain scheduling field, and a version number field. The activation field indicates that the function is enabled, the time-domain scheduling field indicates the time-domain scheduling function, and the version number field indicates the version number of the time-domain scheduling function. The activation field, time-domain scheduling field, and version number field can be configured according to... Figure 5 The fields are arranged from left to right. Of course, the enable field, time-domain scheduling field, and version number field may not be arranged in this order, and this application embodiment does not limit this. In this application embodiment, the enable indication message includes a version number field as an example. When the enable indication message does not indicate the version number of the time-domain scheduling function, the enable indication message may not include a version number field.

[0073] Additionally, the enable field may include one or more bytes, and one of the various status values ​​of the enable field (such as 0, 1, 2, etc.) is used to indicate that the function is enabled. The time-domain scheduling field may include one or more bytes, and one of the various status values ​​of the time-domain scheduling field (such as 0, 1, 2, etc.) is used to indicate the time-domain scheduling function. The version number field may include one or more bytes (such as four bytes), and one of the various status values ​​of the version number field is used to indicate the aforementioned version number. It is understood that the number of bytes in these fields may also differ from the number of bytes exemplified herein, and this embodiment of the application does not limit this.

[0074] Optionally, the structure of the enable indication message can also be the same as... Figure 5 The structures shown are different. For example, the activation indication message includes: a time-domain scheduling activation field and a version number field; the time-domain scheduling activation field is used to indicate that the time-domain scheduling function is enabled; the version number field is used to indicate the version number of the time-domain scheduling function.

[0075] S102. The first network node starts to enable the time domain scheduling function according to the enable instruction message.

[0076] Upon receiving the activation instruction message, the first network node can activate the time-domain scheduling function according to the message. During the activation process, the first network node can stop competing for the air interface (the air interface is also the channel, so competing for the air interface is equivalent to competing for the channel) and stop transmitting data. The first network node can also perform other operations during the activation process, which will not be elaborated upon in this embodiment.

[0077] S103. The first network node sends an activation confirmation message for the time-domain scheduling function to the control node. The activation confirmation message is used to indicate whether the first network node has successfully executed the activation of the time-domain scheduling function.

[0078] When the enable confirmation message is used to indicate that the first network node has failed to enable the time-domain scheduling function, it also indicates the reason why the time-domain scheduling function has not been enabled. It is understandable that the first network node may have failed to enable the time-domain scheduling function for various reasons, such as disabling the function or not supporting it (e.g., the version number of the time-domain scheduling function supported by the first network node is different from the version number in the enable confirmation message).

[0079] Optionally, such as Figure 6As shown, the activation confirmation message includes: a feedback type field, an activation field, a time-domain scheduling field, and a version number field. The feedback type field indicates whether the execution was successful and the reason for failure. The activation field indicates that the function is enabled. The time-domain scheduling field indicates the time-domain scheduling function. The version number field indicates the version number of the time-domain scheduling function. In this embodiment, the activation confirmation message includes a version number field as an example. When the activation confirmation message does not indicate the version number of the time-domain scheduling function, the activation confirmation message may not include a version number field.

[0080] The feedback type field, enable field, time domain scheduling field, and version number field can be configured according to... Figure 6 The fields are arranged in order from left to right. Of course, the feedback type field, enable field, time domain scheduling field, and version number field may not be arranged in this order. This application embodiment does not limit this.

[0081] Additionally, the feedback type field may include one or more bytes. One of the various status values ​​in the feedback type field (e.g., 0) indicates successful execution, and at least one of the various status values ​​in the feedback type field (e.g., 1, 2) indicates execution failure, along with the reason for the failure. When the at least one status value includes at least two status values, the reasons indicated by these at least two status values ​​are different. The enable field may include one or more bytes. One of the various status values ​​in the enable field (e.g., 0, 1, 2, etc.) indicates that the function is enabled. The time-domain scheduling field may include one or more bytes. One of the various status values ​​in the time-domain scheduling field (e.g., 0, 1, 2, etc.) indicates the time-domain scheduling function. The version number field may include one or more (e.g., four) bytes. One of the various status values ​​in the version number field indicates the aforementioned version number.

[0082] It is understood that the number of bytes in these fields may differ from the number of bytes exemplified herein, and the correspondence between the status values ​​of these fields and the content they indicate may also differ from the example herein. This application embodiment does not limit this.

[0083] Optionally, the structure of the confirmation message can also be the same as... Figure 6 The structures shown are different. For example, there are feedback type field, time domain scheduling enable field, and version number field. The feedback type field is used to indicate whether the execution was successful and the reason for failure. The time domain scheduling enable field is used to indicate that the time domain scheduling function is enabled. The version number field is used to indicate the version number of the time domain scheduling function.

[0084] The above S101 to S103 can be executed during the initialization process of the control node and the network node. After the initialization process, the control node and the network node can be synchronized, and then the operation of time-domain scheduling of the first network node can be executed after synchronization.

[0085] After confirming that the first network node has successfully enabled time-domain scheduling, the control node can begin time-domain scheduling of the first network node. Once all at least one network node has enabled time-domain scheduling, the control node can perform time-domain scheduling on that at least one network node. When performing time-domain scheduling on the at least one network node, the control node allocates air interface resources to each network node (also known as centralized scheduling) and sends scheduling messages to the network nodes indicating the air interface resources allocated to them. Network nodes can compete for air interface resources (air interface is also a channel, so competing for air interface is also competing for channel) on the air interface resources indicated in 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 air interface resources allocated in different time and / or frequency domains.

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

[0087] When the control node receives an activation confirmation message from the first network node indicating that the first network node has successfully enabled the time-domain scheduling function, it can determine that the first network node has successfully enabled the time-domain scheduling function. At this time, the control node can send a scheduling message to the first network node to indicate the air interface resources allocated to the first network node.

[0088] When an acknowledgment message indicates that the first network node has failed to enable time-domain scheduling, the control node will not perform time-domain scheduling on that first network node. Furthermore, the control node can take appropriate action based on the reason for the failure in the acknowledgment message, such as presenting the reason to the staff.

[0089] The scheduling message sent by the control node to the first network node needs to indicate air interface resources. For example, the scheduling message sent by the control node to the first network node includes multiple fields, one of which is an air interface resource field indicating air interface resources. The structure of the scheduling message sent by the control node to the first network node can be as follows: Figure 10 As shown, the scheduling message includes: a scheduling type field, a scheduling mode field, a start time field, and an air interface resource field. These fields can be arranged sequentially; however, they can also be arranged differently. Figure 10 The data is arranged from left to right. Additionally, the aforementioned start time field indicates the start time of the time period occupied by the air interface resources.

[0090] In summary, the time-domain scheduling method provided in this application involves a control node instructing network nodes to enable time-domain scheduling functionality. This facilitates centralized control of at least one network node by the control node. The control node then sends scheduling messages to instruct each network node to compete for air interface resources. Once a network node successfully competes for an air interface, it transmits data 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.

[0091] The activation of the aforementioned time-domain scheduling function is controlled by the control node, and the deactivation of the aforementioned time-domain scheduling function can also be controlled by the control node. Of course, the deactivation of the time-domain scheduling function can also be independent of the control node; for example, the first network node can automatically deactivate the time-domain scheduling function within a specified time period after it has been activated.

[0092] Optionally, such as Figure 7 As shown, after the first network node sends the aforementioned start confirmation message to the control node in S103, the time-domain scheduling method provided in this application embodiment further includes: S201, The control node sends a shutdown instruction message to the first network node to indicate the shutdown of the time-domain scheduling function.

[0093] Prior to S201, the control node could determine whether the time-domain scheduling function needed to be disabled (for example, the control node could execute judgment logic based on the collected network parameters to determine whether the function needed to be disabled); or the control node could determine whether the time-domain scheduling function needed to be disabled under the instruction triggered by the staff.

[0094] When the time-domain scheduling function needs to be disabled, the control node can send a shutdown indication message to each network node. This shutdown indication message indicates the time-domain scheduling function and its closure. Optionally, if the time-domain scheduling function has at least one version, the shutdown indication message can also indicate the version number of the time-domain scheduling function (of course, the shutdown indication message may not indicate this version number). Furthermore, if the control node is still sending scheduling messages to network nodes at this time, the control node needs to stop sending scheduling messages to network nodes.

[0095] For example, such as Figure 8 As shown, the shutdown indication message includes: a shutdown field, a time-domain scheduling field, and a version number field. The shutdown field indicates the function is disabled, the time-domain scheduling field indicates the time-domain scheduling function, and the version number field indicates the version number of the time-domain scheduling function. The shutdown field, time-domain scheduling field, and version number field can be configured according to... Figure 8 The fields are arranged from left to right. Of course, the shutdown field, time-domain scheduling field, and version number field may not be arranged in this order, and this embodiment does not limit this. In this embodiment, the shutdown indication message includes a version number field as an example. When the shutdown indication message does not indicate the version number of the time-domain scheduling function, the shutdown indication message may not include a version number field.

[0096] Additionally, the "Close" field may include one or more bytes, and one of the various status values ​​of the "Open" field (such as 0, 1, 2, etc.) is used to indicate that the function is closed. The "Time Domain Scheduling" field may include one or more bytes, and one of the various status values ​​of the "Time Domain Scheduling" field (such as 0, 1, 2, etc.) is used to indicate the time domain scheduling function. The "Version Number" field may include one or more (e.g., four) bytes, and one of the various status values ​​of the "Version Number" field is used to indicate the aforementioned version number. It is understood that the number of bytes in these fields may also differ from the number of bytes exemplified herein, and this embodiment of the application does not limit this.

[0097] The structure of a close instruction message can be the same as that of an open instruction message. For example, the close field in a close instruction message can have the same structure as the open field in an open instruction message. These two fields can be collectively referred to as switch fields. The time domain scheduling field in a close instruction message can be the same as that in an open instruction message. The version number field in a close instruction message can be the same as that in an open instruction message. For example, Table 1 below will illustrate one structure of open and close instruction messages.

[0098] For example, the close instruction message and the open instruction message are collectively referred to as instruction messages, and an example of such instruction messages can be shown in Table 1.

[0099]

[0100] It is understandable that the number of bytes in the fields of Table 1 may differ from the number of bytes in the example given here, and the correspondence between the status values ​​of the fields in Table 1 and the content they indicate may also differ from the example given in Table 1. For example, a status value of 0 in the switch field of Table 1 indicates that the switch is off, and a status value of 1 indicates that the switch is on. Another example is that a status value of 1 in the time-domain scheduling field of Table 1 indicates that the function type that needs to be enabled or disabled is the time-domain scheduling function.

[0101] Optionally, the structure of the close indication message can also be the same as... Figure 8 The structure shown is different. For example, the shutdown indication message includes: a time-domain scheduling shutdown field and a version number field; the time-domain scheduling shutdown field is used to indicate that the time-domain scheduling function is shut down; the version number field is used to indicate the version number of the time-domain scheduling function.

[0102] Accordingly, the above indication message may also include: a time-domain scheduling switch field and a version number field. The time-domain scheduling off field is used to indicate whether the time-domain scheduling function is enabled or disabled; the version number field is used to indicate the version number of the time-domain scheduling function. In this case, the indication message shown in Table 1 can be changed to the indication message shown in Table 2.

[0103]

[0104] It is understandable that the status value 0 of the time-domain scheduling switch field in Table 2 could indicate that it is off, and the status value 1 could indicate that it is on.

[0105] S202, The first network node shuts down the time-domain scheduling function according to the shutdown instruction message.

[0106] After receiving the shutdown instruction message, the first network node can perform operations related to shutting down the time-domain scheduling function based on the shutdown instruction message. For example, it can resume the contention for the air interface and transmit data in S102. In this way, the first network node can exit the mode controlled by the control node (or the mode of contention for the air interface based on the scheduling message sent by the control node).

[0107] S203. The first network node sends a shutdown confirmation message to the control node. The shutdown confirmation message is used to indicate whether the first network node has successfully shut down the time-domain scheduling function.

[0108] When the closure confirmation message is used to indicate that the first network node has failed to close the time-domain scheduling function, the closure confirmation message is also used to indicate the reason why the time-domain scheduling function has not been closed.

[0109] Optionally, such as Figure 9As shown, the close confirmation message includes: a feedback type field, a close field, a time-domain scheduling field, and a version number field. The feedback type field indicates whether the execution was successful and the reason for failure. The close field indicates that the function is closed. The time-domain scheduling field indicates the time-domain scheduling function. The version number field indicates the version number of the time-domain scheduling function. In this embodiment, the close confirmation message includes a version number field as an example. When the close confirmation message does not indicate the version number of the time-domain scheduling function, the close confirmation message may not include a version number field.

[0110] The feedback type field, the close field, the time domain scheduling field, and the version number field can be configured according to... Figure 9 The fields are arranged in order from left to right. Of course, the feedback type field, the close field, the time domain scheduling field, and the version number field may not be arranged in this order. This application embodiment does not limit this.

[0111] Additionally, the feedback type field may include one or more bytes. One of the various status values ​​of the feedback type field (e.g., 0) indicates successful execution, and at least one of the various status values ​​of the feedback type field (e.g., 1, 2) indicates execution failure, along with the reason for the failure. When the at least one status value includes at least two status values, the reasons indicated by the at least two status values ​​are different. The close field may include one or more bytes. One of the various status values ​​of the close field (e.g., 0, 1, 2, etc.) indicates the closure of the function. The time-domain scheduling field may include one or more bytes. One of the various status values ​​of the time-domain scheduling field (e.g., 0, 1, 2, etc.) indicates the time-domain scheduling function. The version number field may include one or more (e.g., four) bytes. One of the various status values ​​of the version number field indicates the aforementioned version number. It is understood that the number of bytes in these fields may differ from the number of bytes exemplified herein, and the correspondence between the status values ​​of these fields and the content they indicate may also differ from the example provided herein. This application embodiment does not limit this.

[0112] The structure of a close confirmation message can be the same as that of an open confirmation message. For example, the feedback type field in a close confirmation message can be the same as the feedback type field in an open confirmation message; the close field in a close confirmation message can have the same structure as the open field in an open confirmation message. These two fields can be collectively referred to as switch fields; the time domain scheduling field in a close confirmation message can be the same as the time domain scheduling field in an open confirmation message; and the version number field in a close confirmation message can be the same as the version number field in an open confirmation message. For example, Table 1 below will illustrate one structure of open and close confirmation messages.

[0113] For example, both closing and opening confirmation messages are collectively referred to as confirmation messages, and an example of such a confirmation message can be shown in Table 3.

[0114]

[0115] It is understandable that the number of bytes in the fields of Table 3 may differ from the number of bytes in the example given here, and the correspondence between the status values ​​of the fields in Table 3 and the content they indicate may also differ from the example given in Table 3.

[0116] For example, in Table 3, the status values ​​0 and 1 of the feedback type field both indicate failure, while status value 2 indicates success. In addition, status value 0 also indicates that the failure is due to the network node disabling the time-frequency scheduling function, and status value 1 also indicates that the failure is due to the protocol version not being supported.

[0117] For example, in Table 3, a status value of 0 for the switch field indicates that it is off, and a status value of 1 indicates that it is on.

[0118] For example, in Table 3, the status value 1 of the time-domain scheduling field indicates that the function type that needs to be enabled or disabled is the time-domain scheduling function.

[0119] Furthermore, in this embodiment of the application, a field (any field in this embodiment of the application) is used to indicate the content indicated by the field through its status value. Optionally, when some fields indicate content, the field or some bits of the field may also be empty (NULL). For example, when the time-domain scheduling field or some bits in Table 1 are empty, the time-domain scheduling field is used to indicate that the function type that needs to be enabled or disabled is the time-domain scheduling function.

[0120] Optionally, the structure of the close confirmation message can also be the same as... Figure 9 The structures shown are different. For example, the closing confirmation message includes: a feedback type field, a time-domain scheduling closing field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling closing field is used to indicate that the time-domain scheduling function is closed; the version number field is used to indicate the version number of the time-domain scheduling function.

[0121] Accordingly, the aforementioned confirmation message may also include: a feedback type field, a time-domain scheduling switch field, and a version number field. The feedback type field indicates whether the execution was successful and the reason for failure; the time-domain scheduling disable field indicates whether the time-domain scheduling function is enabled or disabled; and the version number field indicates the version number of the time-domain scheduling function. In this case, the indication message shown in Table 3 can be changed to the indication message shown in Table 4.

[0122]

[0123] It is understandable that, in Table 4, the status values ​​0 and 1 in the feedback type field could both indicate failure, while status value 2 could indicate success. Specifically, status value 0 could also indicate that the failure was due to the network node disabling the time-frequency scheduling function, and status value 1 could indicate that the failure was due to protocol version incompatibility. Alternatively, in Table 4, a status value of 0 in the time-domain scheduling switch field could indicate that it is off, and a status value of 1 could indicate that it is on.

[0124] Optionally, before the control node sends an enable instruction message to the first network node to indicate the need to enable the time-domain scheduling function (and after determining that the time-domain scheduling function needs to be enabled), the control node may also send a configuration message to the first network node. The configuration message indicates at least one functional parameter of the time-domain scheduling function. After successfully enabling the time-domain scheduling function, the first network node can run the time-domain scheduling function according to the at least one functional parameter. For example, the configuration message includes a timer field (also called a timer field), and the at least one functional parameter includes the timeout duration of the timer (also called a timer), which is used to indicate the timeout duration. The first network node can start the timer after sending service information. If the first network node has not received a scheduling message when the timer reaches its timeout duration, the first network node can send an alarm message to the control node. If the first network node receives a scheduling message before the timer reaches its timeout duration, the first network node can close the timer.

[0125] When a closure confirmation message is used to indicate that the first network node has not closed the time-domain scheduling function, the control node can take corresponding actions based on the reason for the unsuccessful execution in the closure confirmation message, such as presenting the reason to the staff.

[0126] It is understood that the names of the messages in this application embodiment may also be different from the names given in this application embodiment. For example, the above-mentioned start indication message and start / stop message can both be called feature parameter configuration message.

[0127] This application also provides a time-domain scheduling device, which belongs to the control node in the FTTR network, such as... Figure 11As shown, the time-domain scheduling device includes a first transmitting module 1101 and a first receiving module 1102. The first transmitting module 1101 is used to send an activation indication message to a first network node, indicating whether to enable the time-domain scheduling function; the first network node is any one of at least one network node in an FTTR network. The first receiving module 1102 is used to receive an activation confirmation message for the time-domain scheduling function sent by the first network node, the activation confirmation message indicating whether the first network node has enabled the time-domain scheduling function. The operations performed by the first transmitting module 1101 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 1102 can refer to the operations related to the control node in S103 of the aforementioned embodiment.

[0128] Optionally, the activation indication message includes: a time-domain scheduling activation field and a version number field; the time-domain scheduling activation field is used to indicate the activation of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0129] Optionally, when the enable confirmation message is used to indicate that the first network node has not enabled the time-domain scheduling function, the enable confirmation message is also used to indicate the reason why the time-domain scheduling function has not been enabled.

[0130] Optionally, the activation confirmation message includes: a feedback type field, a time-domain scheduling activation field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling activation field is used to indicate that the time-domain scheduling function is enabled; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0131] Optionally, the time-domain scheduling device further includes: a second transmission module ( Figure 11 (Not shown in the image), used to send a shutdown indication message to the first network node to indicate that the time-domain scheduling function is to be disabled; the second receiving module ( Figure 11 (not shown in the image) is used to receive a shutdown confirmation message for the time-domain scheduling function sent by the first network node. The shutdown confirmation message is used to indicate whether the first network node has shut down the time-domain scheduling function.

[0132] Optionally, the shutdown indication message includes: a time-domain scheduling shutdown field and a version number field; the time-domain scheduling shutdown field is used to indicate the shutdown of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0133] Optionally, when the shutdown confirmation message is used to indicate that the first network node has not shut down the time-domain scheduling function, the shutdown confirmation message is also used to indicate the reason for not shutting down the time-domain scheduling function.

[0134] Optionally, the closure confirmation message includes: a feedback type field, a time-domain scheduling closure field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling closure field is used to indicate that the time-domain scheduling function is closed; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0135] Optionally, the time-domain scheduling device further includes: a third transmission module ( Figure 11 (Not shown in the image), used to send a configuration message to the first network node, the configuration message being used to indicate at least one functional parameter of the time-domain scheduling function.

[0136] Optionally, the configuration message includes a timer field, and the at least one functional parameter includes the timeout duration of the timer, the timer field being used to indicate the timeout duration.

[0137] Optionally, the time-domain scheduling device further includes: a judgment module ( Figure 11 (not shown in the image) is used to determine whether the time-domain scheduling function needs to be enabled; the first sending module is used to send the enable instruction message to the first network node when the determining module determines that the time-domain scheduling function needs to be enabled.

[0138] In this embodiment of the application, the message transmitted between the control node and the sending node (such as the above-mentioned start indication message, start confirmation message, stop indication message, and stop confirmation message) is used to indicate the version number of the time domain scheduling function. Optionally, these messages may not be used to indicate the version number, and the corresponding message may not include the version number field used to indicate the version number.

[0139] 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, such as... Figure 12As shown, the time-domain scheduling device includes: a first receiving module 1201, used to receive an activation indication message sent by a control node in the FTTR network, indicating the activation of the time-domain scheduling function; an activation module 1202, used to activate the time-domain scheduling function according to the activation indication message; and a first sending module 1203, used to send an activation confirmation message of the time-domain scheduling function to the control node, the activation confirmation message indicating whether the first network node has activated the time-domain scheduling function. The operations performed by the first receiving module 1201 can refer to the operations related to the first network node in S101 of the aforementioned embodiment, the operations performed by the activation module 1202 can refer to the operations related to the first network node in S102 of the aforementioned embodiment, and the operations performed by the first sending module 1203 can refer to the operations related to the first network node in S103 of the aforementioned embodiment.

[0140] Optionally, the activation indication message includes: a time-domain scheduling activation field and a version number field; the time-domain scheduling activation field is used to indicate the activation of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0141] Optionally, when the enable confirmation message is used to indicate that the first network node has not enabled the time-domain scheduling function, the enable confirmation message is also used to indicate the reason why the time-domain scheduling function has not been enabled.

[0142] Optionally, the activation confirmation message includes: a feedback type field, a time-domain scheduling activation field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling activation field is used to indicate that the time-domain scheduling function is enabled; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0143] Optionally, the time-domain scheduling device further includes: a second receiving module ( Figure 12 (Not shown in the image), used to receive a shutdown instruction message sent by the control node indicating that the time-domain scheduling function should be disabled; shutdown module ( Figure 12 (not shown in the image), used to begin disabling the time-domain scheduling function according to the shutdown instruction message; second sending module ( Figure 12 (Not shown in the image), used to send a shutdown confirmation message for the time-domain scheduling function to the control node, the shutdown confirmation message being used to indicate whether the first network node has disabled the time-domain scheduling function.

[0144] Optionally, the shutdown indication message includes: a time-domain scheduling shutdown field and a version number field; the time-domain scheduling shutdown field is used to indicate the shutdown of the time-domain scheduling function; the version number field is used to indicate the version number of the time-domain scheduling function.

[0145] Optionally, when the shutdown confirmation message is used to indicate that the first network node has not shut down the time-domain scheduling function, the shutdown confirmation message is also used to indicate the reason for not shutting down the time-domain scheduling function.

[0146] Optionally, the closure confirmation message includes: a feedback type field, a time-domain scheduling closure field, and a version number field; the feedback type field is used to indicate whether the execution was successful and the reason for failure; the time-domain scheduling closure field is used to indicate that the time-domain scheduling function is closed; and the version number field is used to indicate the version number of the time-domain scheduling function.

[0147] Optionally, the time-domain scheduling device further includes: a third receiving module ( Figure 12 (Not shown in the image), used to receive a configuration message sent by the control node in the FTTR network before receiving an enable instruction message indicating the enabling of the time-domain scheduling function, the configuration message indicating at least one functional parameter of the time-domain scheduling function; running module ( Figure 12 (not shown in the image), used to run the time-domain scheduling function according to the at least one function parameter after the enabling module enables the time-domain scheduling function.

[0148] Optionally, the configuration message includes a timer field, and the at least one functional parameter includes the timeout duration of the timer, the timer field being used to indicate the timeout duration.

[0149] In this embodiment of the application, the message transmitted between the control node and the sending node (such as the above-mentioned start indication message, start confirmation message, stop indication message, and stop confirmation message) is used to indicate the version number of the time domain scheduling function. Optionally, these messages may not be used to indicate the version number, and the corresponding message may not include the version number field used to indicate the version number.

[0150] This application also provides a time-domain scheduling device, which belongs to a control node in an 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, and 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 interface is used to send an activation indication message to a first network node, indicating whether to enable the time-domain scheduling function; the first network node is any one of at least one network node in the FTTR network; the interface is also used to receive an activation confirmation message for the time-domain scheduling function sent by the first network node, the activation confirmation message indicating whether the first network node has enabled the time-domain scheduling function.

[0151] 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 interface receives an activation indication message from a control node in the FTTR network, indicating whether to activate the time-domain scheduling function; the processor activates the time-domain scheduling function according to the activation indication message; and the interface sends an activation confirmation message to the control node, indicating whether the first network node has activated the time-domain scheduling function.

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

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

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

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

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

[0157] 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, the processes or functions described in the embodiments of this application are generated entirely or partially. 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.

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

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

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

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

[0162] 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: Send an indication message to a first network node, which is any one of at least one network node in the FTTR network. The control node is connected to the first network node via optical fiber. The indication message is used to indicate whether the time domain scheduling function is enabled or disabled. The system receives a confirmation message sent by the first network node, the confirmation message indicating whether to enable the time-domain scheduling function.

2. The method according to claim 1, characterized in that, Both the instruction message and the confirmation message include a switch field. A value of 1 in the switch field indicates that the time-domain scheduling function is enabled, and a value of 0 in the switch field indicates that the time-domain scheduling function is disabled.

3. The method according to claim 2, characterized in that, When the indication message is used to indicate that the time-domain scheduling function is enabled, and the confirmation message is used to indicate that the first network node has not enabled the time-domain scheduling function, the confirmation message is also used to indicate the reason for the failure to execute.

4. The method according to claim 3, characterized in that, The confirmation message includes: a feedback type field and the switch field; The feedback type field is used to indicate whether the execution was successful, and the reason for failure.

5. The method according to any one of claims 1 to 4, characterized in that, At least one of the instruction message and the confirmation message includes a version number field, which is used to indicate the version number of the time-domain scheduling function.

6. The method according to any one of claims 1 to 5, characterized in that, Before sending an indication message to the first network node to indicate the activation of the time-domain scheduling function, the method further includes: A configuration message is sent to the first network node, the configuration message being used to indicate at least one functional parameter of the time-domain scheduling function.

7. The method according to claim 6, characterized in that, The configuration message includes a timer field, and the at least one functional parameter includes the timeout duration of the timer, the timer field being used to indicate the timeout duration.

8. The method according to any one of claims 1 to 7, characterized in that, Before sending an indication message to the first network node to indicate the activation of the time-domain scheduling function, the method further includes: Determine whether the time-domain scheduling function needs to be enabled; Send an instruction message to the first network node to indicate that the time-domain scheduling function is enabled, including: When it is determined that the time-domain scheduling function needs to be enabled, an instruction message is sent to the first network node to indicate that the time-domain scheduling function needs to be enabled.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: When the confirmation message sent by the first network node indicates that the time-domain scheduling function is enabled, a scheduling message is sent to the first network node.

10. The method according to claim 9, characterized in that, The scheduling message is used to indicate the air interface resources allocated to the first network node.

11. The method according to claim 10, characterized in that, The scheduling message includes: a scheduling type field, a scheduling mode field, and a start time field.

12. The method according to claim 11, characterized in that, The scheduling message also includes an air interface resource field, which indicates air interface resources.

13. The method according to any one of claims 1 to 12, characterized in that, The control node is the master FTTR device, and the network node is the slave FTTR device.

14. 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: The system receives an indication message sent by a control node in the FTTR network. The indication message is used to indicate whether the time-domain scheduling function is enabled or disabled. The control node and the first network node are connected via optical fiber. The time-domain scheduling function can be enabled or disabled according to the instruction message. A confirmation message is sent to the control node, which indicates whether the time-domain scheduling function is enabled.

15. The method according to claim 14, characterized in that, Both the instruction message and the confirmation message include a switch field. A value of 1 in the switch field indicates that the time-domain scheduling function is enabled, and a value of 0 in the switch field indicates that the time-domain scheduling function is disabled.

16. The method according to claim 15, characterized in that, When the indication message is used to indicate that the time-domain scheduling function is enabled, and the confirmation message is used to indicate that the time-domain scheduling function is not enabled, the enable confirmation message is also used to indicate the reason for the failure to execute successfully.

17. The method according to claim 16, characterized in that, The confirmation message includes: a feedback type field and the switch field; The feedback type field is used to indicate whether the execution was successful, and the reason for failure.

18. The method according to any one of claims 14 to 17, characterized in that, At least one of the instruction message and the confirmation message includes a version number field; The version number field is used to indicate the version number of the time-domain scheduling function.

19. The method according to any one of claims 14 to 18, characterized in that, The method further includes: Before receiving an indication message indicating the activation of the time-domain scheduling function, the control node sends a configuration message, which indicates at least one functional parameter of the time-domain scheduling function. After the time-domain scheduling function is enabled, the time-domain scheduling function is run according to the at least one function parameter.

20. The method according to claim 19, characterized in that, The configuration message includes a timer field, and the at least one functional parameter includes the timeout duration of the timer, the timer field being used to indicate the timeout duration.

21. The method according to any one of claims 14 to 20, characterized in that, The method further includes: After sending a confirmation message to the control node to indicate that the time-domain scheduling function is enabled, the system receives a scheduling message sent by the control node. The air interface is contested based on the scheduling message.

22. The method according to claim 21, characterized in that, The scheduling message is used to indicate the air interface resources allocated to the first network node; Competing for an air interface according to the scheduling message includes: competing for an air interface on the air interface resources indicated by the scheduling message.

23. The method according to claim 22, characterized in that, The scheduling message includes: a scheduling type field, a scheduling mode field, and a start time field.

24. The method according to claim 23, characterized in that, The scheduling message also includes an air interface resource field, which indicates air interface resources.

25. The method according to any one of claims 14 to 24, characterized in that, The control node is the master FTTR device, and the network node is the slave FTTR device.

26. A control node, characterized in that, The control node is connected to a first network node in the Fiber to the Room (FTTR) network via an optical fiber. The first network node is any one of at least one network node in the FTTR network. The control node is used to perform the method according to any one of claims 1 to 13.

27. A network node, characterized in that, The network node is any one of at least one network node in a fiber-to-the-room (FTTR) network, and the network node is connected to a control node in the FTTR network via optical fiber. The network node is used to perform the method described in any one of claims 14 to 25.

28. A time-domain scheduling system, characterized in that, Includes a control node in the fiber-to-the-room (FTTR) network and at least one network node in the FTTR network; The control node is used to execute the time-domain scheduling method according to any one of claims 1 to 13; The first network node is used to execute the time-domain scheduling method according to any one of claims 14 to 25, wherein the first network node is any one of the at least one network node, and the control node is connected to the first network node via an optical fiber.

29. The time-domain scheduling system according to claim 28, characterized in that, The control node is the master FTTR device, and the network node is the slave FTTR device.

Images