Energy saving method, device, equipment and communication system for passive optical network
Patent Information
- Application Number
- CN202510438488.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-08
- Publication Date
- 2026-10-16
Smart Images

Figure CN122934111A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of optical communication technology, and in particular to an energy-saving method, apparatus, device and communication system for passive optical networks. Background Technology
[0002] A passive optical network (PON) is a point-to-multipoint fiber optic network. A PON consists of an optical line terminal (OLT), an optical network terminal (ONU), and an optical distribution network (ODN). The OLT is connected to the ONU through the ODN.
[0003] Because of the large number of devices in PON, the power consumption of PON is relatively high. Therefore, it is necessary to provide methods to reduce the power consumption of PON. Summary of the Invention
[0004] This application provides an energy-saving method, apparatus, device, and communication system for passive optical networks (PONs), which can reduce the power consumption of PONs. The technical solution adopted is as follows:
[0005] In a first aspect, this application provides an energy-saving method for a passive optical network (PON). The method is applied to a master device connected to at least one sub-device. The method includes: sending a first energy-saving request to an OLT (Optical Linear Transmission Unit), wherein the first energy-saving request instructs the master device to request energy-saving processing; receiving a first energy-saving consent message from the OLT, wherein the first energy-saving consent message instructs the master device to consent to energy-saving processing; and performing energy-saving processing on a port connected to the OLT in the master device using a first energy-saving parameter, wherein the first energy-saving parameter is determined based on a second energy-saving parameter of the at least one sub-device, and the time period during which the port is in a low-power state overlaps with the time period during which the at least one sub-device is in a low-power state.
[0006] In the scheme shown in this application, the master device sends an energy-saving request to the OLT to request energy-saving processing. After the OLT agrees to the master device's energy-saving processing, the master device uses a first energy-saving parameter to perform energy-saving processing on the uplink port, which is the port in the master device connected to the OLT. Since the first energy-saving parameter is determined based on the energy-saving parameters of the sub-devices connected to the master device, and the time period when the uplink port is in a low-power state overlaps with the time period when the sub-device is in a low-power state, energy-saving processing may also be performed on the uplink port while the sub-device is performing energy-saving processing, thereby reducing the overall power consumption of the PON.
[0007] In one optional approach, both the first and second energy-saving parameters include a start time parameter and an energy-saving duration parameter. The start time parameter indicates the time at which energy-saving processing begins using the energy-saving duration parameter, while the energy-saving duration parameter indicates the duration of the wake-up state and the duration of the low-power state. This makes it easier for the sub-device to control energy-saving processing of the uplink port of the master device while performing energy-saving processing.
[0008] In one alternative approach, the time period during which the uplink port of the master device is in a wake-up state overlaps with the time period during which the at least one sub-device is in a wake-up state, enabling the master device to send or receive data from the sub-device in a timely manner.
[0009] In one alternative approach, before sending the first energy-saving request to the OLT, the master device uses the energy-saving parameters of at least one sub-device to determine the first energy-saving parameter and carries the first energy-saving parameter in the first energy-saving request. In this way, since the sub-device is managed by the master device, the master device can accurately determine the energy-saving parameter when coordinating energy saving, and can also reduce the management burden on the OLT.
[0010] In one alternative approach, before performing energy-saving processing, the master device receives a first energy-saving parameter sent by the OLT, enabling the master device to perform energy-saving processing based on the energy-saving parameter sent by the OLT.
[0011] In one alternative approach, before sending an energy-saving request to the OLT, the master device receives a second energy-saving request from a first sub-device among the at least one sub-devices. This second energy-saving request instructs the first sub-device to request energy-saving processing. The master device determines the second energy-saving parameters of the first sub-device and sends a second energy-saving agreement message and the second energy-saving parameters to the first sub-device. In this way, the sub-devices can also proactively request energy-saving processing to reduce the power consumption of the PON.
[0012] In one alternative approach, before sending the second energy-saving consent message and the second energy-saving parameters of the first sub-device to the first sub-device, the master device determines that it agrees to the first sub-device performing energy-saving processing, and then sends the energy-saving information of the first sub-device to the OLT. In this way, the master device decides to agree to the sub-device performing energy-saving processing and reports this to the OLT. Alternatively, the master device sends a third energy-saving request to the OLT, the third energy-saving request including the second energy-saving parameters. The master device receives the third energy-saving consent message from the OLT and then sends the second energy-saving consent message and the second energy-saving parameters of the first sub-device to the first sub-device. In this way, the OLT decides to agree to the sub-device performing energy-saving processing.
[0013] In one alternative approach, the master device can further determine that the second sub-device among the at least one sub-devices has stopped energy-saving processing, and then send a first energy-saving rejection message to the second sub-device to instruct it to stop energy-saving processing. This way, when a sub-device needs to stop energy-saving processing, it can be notified promptly to ensure that the sub-device stops energy-saving processing.
[0014] In one alternative approach, when the master device determines that the second sub-device needs to stop energy-saving processing, it can do so based on the service traffic information of at least one sub-device, or the OLT can decide whether the second sub-device needs to stop energy-saving processing. The master device then receives a second energy-saving rejection message from the OLT. In this way, when the master device or the OLT determines that a sub-device needs to stop energy-saving processing, it can instruct the sub-device to do so, thereby reducing the impact of energy-saving processing on services.
[0015] In an alternative approach, the master device can also receive a fourth energy-saving request sent by the second sub-device when it needs to stop energy-saving processing. The master device can also send a fifth energy-saving request to the OLT to instruct it to stop energy-saving processing. This way, when the sub-device needs to stop energy-saving processing, it can do so promptly, thereby reducing the impact of energy saving on services.
[0016] In one alternative approach, the master device is the main FTTR unit (MFU) in the fiber-to-the-room (FTTR) network, and the sub-FTTR unit (SFU) is the sub-FTTR unit in the FTTR network.
[0017] Secondly, this application provides an energy-saving method for passive optical networks (OLTs), the method comprising:
[0018] Receive a first energy-saving request sent by the master device, wherein the first energy-saving request is used to instruct the master device to request energy-saving processing;
[0019] A first energy-saving consent message is sent to the master device to instruct the master device to perform energy-saving processing on the port connected to the optical line terminal using a first energy-saving parameter. The first energy-saving parameter is determined based on a second energy-saving parameter of at least one sub-device connected to the master device, and the time period during which the port is in a low-power state overlaps with the time period during which the at least one sub-device is in a low-power state.
[0020] In one alternative approach, both the first energy-saving parameter and the second energy-saving parameter include a start time parameter and an energy-saving duration parameter. The start time parameter indicates the time point at which energy-saving processing begins using the energy-saving duration parameter, and the energy-saving duration parameter indicates the duration of being in the wake-up state and the duration of being in the low-power state.
[0021] In one alternative approach, the first energy-saving request includes the first energy-saving parameter; or...
[0022] After receiving the first energy-saving request sent by the master device, the method further includes:
[0023] The first energy-saving parameter is determined based on the second energy-saving parameter of the at least one sub-device;
[0024] Send the first energy-saving parameter to the main device.
[0025] In one alternative approach, after sending the first energy-saving agreement message to the master device, the OLT uses the first energy-saving parameters to perform energy-saving processing on the ports in the optical line terminal connected to the master device. This enables energy-saving processing of the ports in the OLT connected to the master device, further reducing the power consumption of the PON.
[0026] In an alternative approach, the method further includes:
[0027] The system receives a third energy-saving request sent by the master device, wherein the third energy-saving request includes a second energy-saving parameter of the first sub-device, and the third energy-saving request is used to instruct the first sub-device to request energy-saving processing.
[0028] A third energy-saving consent message is sent to the master device, wherein the third energy-saving consent message is used to indicate that the first sub-device is authorized to perform energy-saving processing.
[0029] In one alternative approach, the method includes:
[0030] It is determined that the second sub-device in the at least one sub-device stops energy-saving processing;
[0031] Send an energy-saving rejection message to the master device, wherein the energy-saving rejection message is used to instruct the second sub-device to exit the energy-saving state.
[0032] The effects of the second aspect and the optional methods within the second aspect are the same as those of the first aspect and the optional methods within the first aspect, and will not be repeated here.
[0033] Thirdly, this application provides a PON energy-saving device that has the function of implementing the first aspect or any optional method of the first aspect. The device includes at least one module for implementing the method provided by the first aspect or any optional method of the first aspect.
[0034] Fourthly, this application provides a PON energy-saving device that has the function of implementing the second aspect or any optional method of the second aspect described above. The device includes at least one module for implementing the method provided by the second aspect or any optional method of the second aspect.
[0035] Fifthly, this application provides a communication device, which is an OLT. The OLT includes a processor, a memory, and a communication interface. The processor is used to execute program instructions in the memory to implement the method provided in the first aspect or any optional method of the first aspect. The communication interface is used to communicate with other devices (such as a host device).
[0036] In a sixth aspect, this application provides a communication device, which is a main device, including a processor, a memory, and a communication interface; the processor is used to execute program instructions in the memory to implement the method provided in the second aspect or any optional method of the second aspect, and the communication interface is used to communicate with other devices (such as OLTs and sub-devices).
[0037] In a seventh aspect, this application provides a communication system, the communication system including a master device and an OLT, the master device being used to implement the method provided by the first aspect or any optional method of the first aspect, and the OLT being used to implement the method provided by the second aspect or any optional method of the second aspect.
[0038] Eighthly, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause a master device to perform the method provided in the first aspect or any alternative manner of the first aspect.
[0039] Ninthly, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the OLT to perform the method provided in the second aspect or any alternative method of the second aspect.
[0040] In a tenth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. A processor of a host device reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the host device to perform the method provided in the first aspect or any optional method of the first aspect.
[0041] In one aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the OLT reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the OLT to perform the method provided in the second aspect or any alternative method of the second aspect described above.
[0042] In a twelfth aspect, this application provides a communication device for performing the method provided in the first aspect or any of the alternative methods of the first aspect.
[0043] In a thirteenth aspect, this application provides a communication device for performing the method provided in the second aspect or any of the alternative methods of the second aspect. Attached Figure Description
[0044] Figure 1 This is a schematic diagram of the PON architecture provided in an exemplary embodiment of this application;
[0045] Figure 2 This is a schematic diagram of a link in a PON provided in an exemplary embodiment of this application;
[0046] Figure 3 This is a schematic diagram of an energy-saving method for PON provided in an exemplary embodiment of this application;
[0047] Figure 4 This is a schematic diagram of an energy-saving process provided by another exemplary embodiment of this application;
[0048] Figure 5 This is a schematic diagram of an energy-saving method for PON provided in another exemplary embodiment of this application;
[0049] Figure 6 This is a schematic diagram of the SFU energy-saving process provided in an exemplary embodiment of this application;
[0050] Figure 7 This is a schematic diagram of energy-saving parameters provided in an exemplary embodiment of this application;
[0051] Figure 8 This is a schematic diagram of energy-saving parameters provided in another exemplary embodiment of this application;
[0052] Figure 9 This is a schematic diagram of energy-saving parameters provided in yet another exemplary embodiment of this application;
[0053] Figure 10 This is a schematic diagram of energy-saving parameters provided in another exemplary embodiment of this application;
[0054] Figure 11 This is a schematic diagram of energy-saving parameters provided in another exemplary embodiment of this application;
[0055] Figure 12 This is a schematic diagram of a PON energy-saving method provided in yet another exemplary embodiment of this application;
[0056] Figure 13 This is a schematic diagram of a PON energy-saving method provided in another exemplary embodiment of this application;
[0057] Figure 14 This is a schematic diagram of the SFU application energy-saving process provided in another exemplary embodiment of this application;
[0058] Figure 15 This is a schematic diagram of the SFU energy-saving process provided in yet another exemplary embodiment of this application;
[0059] Figure 16 This is a schematic diagram of the SFU energy-saving process provided in another exemplary embodiment of this application;
[0060] Figure 17 This is a schematic diagram of the energy-saving process of an MFU application provided in another exemplary embodiment of this application;
[0061] Figure 18 This is a schematic diagram of an exemplary embodiment of the present application providing an OLT instruction to stop energy-saving processing;
[0062] Figure 19 This is a schematic diagram of the process of instructing the MFU to stop energy-saving processing according to an exemplary embodiment of this application;
[0063] Figure 20 This is a schematic diagram of an exemplary embodiment of the present application illustrating the process of an SFU requesting to stop energy-saving processing;
[0064] Figure 21 This is a schematic diagram of the SFU deployment process provided in an exemplary embodiment of this application;
[0065] Figure 22 This is a schematic diagram of the SFU online process provided in another exemplary embodiment of this application;
[0066] Figure 23This is a schematic diagram of a PON energy-saving device provided in an exemplary embodiment of this application;
[0067] Figure 24 This is another structural schematic diagram of an energy-saving device for PON provided in an exemplary embodiment of this application;
[0068] Figure 25 This is a schematic diagram of the structure of a device provided in an exemplary embodiment of this application. Detailed Implementation
[0069] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0070] In PON, each ONU sends an energy-saving request to the OLT during energy-saving processing, and the OLT instructs the ONU to perform energy-saving processing. With the development of network technology, FTTR has gradually emerged. A key question arises: while the optical link (i.e., SFU) within the FTTR is in sleep mode, how can the optical link between the MFU and the OLT also be put into sleep mode to further reduce PON power consumption? Therefore, this application provides a method for energy saving in passive optical networks. In this method, when considering the energy-saving parameters of the MFU, the energy-saving parameters of the connected SFU are referenced, enabling coordinated energy saving to reduce the overall power consumption of the PON. That is, the uplink port (the port connected to the OLT) and downlink port (the port connected to the SFU) of the MFU can sleep and wake up simultaneously. While the optical link within the FTTR is in sleep mode, the optical link between the MFU and the OLT can also be put into sleep mode, reducing both power consumption and message transmission latency.
[0071] The following describes the terminology and concepts involved in the embodiments of this application.
[0072] 1. Awake state refers to the aware state, which includes, but is not limited to, dozeaware, sleep-aware, or watch-aware states. In the aware state, both the receiving and transmitting functions of the device are enabled; the device is an OLT, MFU, or SFU in a PON.
[0073] 2. Simultaneous sleep and wake-up refers to a period of time during which multiple devices are simultaneously awake, and / or a period of time during which multiple devices are simultaneously in a low-power state.
[0074] The system architecture of an embodiment of this application is described below.
[0075] Figure 1 A schematic diagram of the communication system architecture is provided; see [link / reference]. Figure 1The system architecture includes an OLT, a main device, and sub-devices. In this embodiment, the main device is an MFU in an FTTR network, and the sub-device is an SFU in an FTTR network. The OLT connects to the MFU via an ODN, and the MFU connects to the SFU via an optical splitter. The MFU acts as an optical network terminal (ONT) or ONU in a fiber-to-the-home (FTTH) or fiber-to-the-office (FTTO) network, and also as an upstream device for the SFU, managing it. The SFU can be deployed in various rooms of a home or office to provide signals to user terminals, including but not limited to terminals, tablets, laptops, or IoT devices. The SFU has the functions of an ONT or ONU and can also function as a wireless access point (AP). Optionally, the MFU also has the function of a wireless access point.
[0076] The MFU (Master Component Unit) can manage and configure all SFUs (Sub-Fiber Units). The MFU can also be called a "master node," "master device," "master gateway," or "master optical modem," while the SFU can be called a "sub-node," "sub-device," "sub-gateway," or "sub-optical modem." The MFU is also called the main optical network unit, and the SFU is also called a sub-optical network unit. Figure 1 The diagram shows the connection between MFU and SFU1 and SFU2.
[0077] exist Figure 1 In this context, the link between the OLT and MFU is called the uplink (link 0), the link between the MFU and SFU1 is called the downlink (link 1), and the link between the MFU and SFU2 is called the downlink (link 2). See also... Figure 2 .
[0078] The execution subject of the embodiments of this application is described below.
[0079] The energy-saving mechanism of a passive optical network (PON) is primarily implemented by the PON's energy-saving device. Optionally, this device can be a hardware device, such as an OLT (Optical Line Terminal) or a main unit. Alternatively, it can be a software device, such as a software program running on the hardware device.
[0080] The energy-saving method process of PON is described below.
[0081] Figure 3 A PON energy-saving method flow is provided, see steps S101 to S103.
[0082] In step S101, the MFU sends a first energy-saving request to the OLT, wherein the first energy-saving request is used to instruct the MFU to request energy-saving processing.
[0083] In this embodiment, when the energy-saving conditions are met, the MFU sends a first energy-saving request to the OLT. The first energy-saving request is used to instruct the MFU to request energy-saving processing.
[0084] In one alternative approach, the MFU determines that energy-saving conditions are met when it determines that more than a target percentage of SFUs are being processed for energy saving. The target percentage could be 60%, etc.
[0085] Optionally, the MFU determines whether energy-saving conditions are met when it determines that all connected SFUs are performing energy-saving processing.
[0086] In step S102, the OLT sends a first energy-saving consent message to the MFU, instructing the MFU to use the first energy-saving parameters to perform energy-saving processing on the ports in the MFU connected to the OLT.
[0087] The first energy-saving parameter is determined by the second energy-saving parameter of at least one SFU connected to the MFU. Both the first and second energy-saving parameters include an energy-saving duration parameter and a start time parameter. The energy-saving duration parameter includes the duration of being in the wake-up state and the duration of being in the low-power state. The duration of being in the wake-up state can be the shortest duration of a single wake-up state, referred to as the minimum aware interval. The duration of being in the low-power state can be the longest duration of a single low-power state, referred to as the maximum sleep interval. The start time parameter is used to indicate the time point at which the energy-saving duration parameter is used for energy-saving processing.
[0088] In this embodiment, after receiving the first energy-saving request, the OLT determines whether the MFU can perform energy-saving processing. If it determines that the MFU can perform energy-saving processing, it sends a first energy-saving consent message to the MFU, which instructs the OLT to allow the MFU to perform energy-saving processing. If it determines that the MFU cannot perform energy-saving processing, it sends an energy-saving rejection message to the MFU, which instructs the OLT to reject the MFU from performing energy-saving processing.
[0089] In one optional approach, the power-saving duration parameter also includes one or more of the following: minimum active held interval, itransinit, or itxinit. The minimum active held interval refers to the shortest duration for maintaining an active state, where both receive and transmit functions are enabled. itransinit refers to the initialization time for the transmit / receive functions of the MFU's uplink port, such as the time required for the uplink port's transmit / receive functions to return to normal operation after being disabled. This uplink port is the port in the MFU connected to the OLT. The transmit / receive functions include transmitting and receiving functions; the transmitting function refers to the MFU's function of sending data to the OLT, and the receiving function refers to the MFU's function of receiving data sent by the OLT. itxinit refers to the initialization time for the transmit function of the MFU's uplink port, such as the time required for the uplink port's transmit function to return to normal operation after being disabled.
[0090] Optionally, each of the above energy-saving duration parameters is counted in units of 125 microseconds.
[0091] In an alternative approach, the start time parameter can be either the system time or the value of the superframe counter (SFC). When using the system time, the synchronization function between the MFU and the OLT needs to be enabled.
[0092] In one alternative approach, the OLT uses the MFU's service traffic information to determine whether the MFU can perform energy-saving processing. For example, if the service traffic sent to the MFU is less than a certain threshold and / or the service traffic originating from the MFU is less than a certain threshold within a certain period, then it is determined that the MFU can perform energy-saving processing; otherwise, it is determined that energy-saving processing cannot be performed. Here, service traffic originating from the MFU includes service traffic received by the OLT from the MFU, and service traffic sent to the MFU includes service traffic sent by the OLT to the MFU and / or service traffic sent by the SFU to the MFU.
[0093] In step S103, the MFU uses the first energy-saving parameter to perform energy-saving processing on the uplink port of the MFU.
[0094] In this embodiment, after receiving the first energy-saving consent message, the MFU obtains the first energy-saving parameters of the MFU, and from these parameters, it obtains the start duration parameter and the energy-saving duration parameter. Then, at the time indicated by the start duration parameter, the MFU uses the energy-saving duration parameter to perform energy-saving processing on the uplink port, which is the port in the MFU connected to the OLT, i.e., the port connected to the OLT. Figure 2The port connected to link 0 in the middle link. When the MFU uses the first power-saving parameter to save power on the uplink port, there is a period of time when the uplink port and the SFU are simultaneously in a low-power state. In this way, the MFU and SFU can perform coordinated power saving.
[0095] In one alternative approach, when power-saving the uplink port, the uplink port switches back and forth between a low-power state and a wake-up state. There are several possibilities for the low-power state, and the following three possibilities are provided: Case 1: The receive and transmit functions are always turned off. The state shown in Case 1 is called the sleep state; Case 2: The receive function is always turned on and the transmit function is turned off. The state shown in Case 2 is called the listen state; Case 3: The transmit function is always turned off, but the receive function is turned on briefly (it can be turned on periodically or not periodically), and the receive function is turned off the rest of the time. The state shown in Case 3 is called the watch state.
[0096] In the wake-up state, both the receive and transmit functions are enabled simultaneously. Thus, during uplink port power-saving processing, if the low-power state is as shown in Case 1, the power-saving process is equivalent to periodically enabling both receive and transmit functions simultaneously, and disabling them at other times. This process is called cyclic sleep. See [link to relevant documentation]. Figure 4 (a) In this context, if the low-power state is as shown in case 2, then during the power-saving process, it is equivalent to keeping the receiving function on continuously, but periodically turning on the transmitting function and turning it off the rest of the time. This process is called "dozing off." See [link to relevant documentation]. Figure 4 (b) If the low-power state is as shown in case 3, then during the power-saving process, it is equivalent to periodically and simultaneously turning on the transmitting and receiving functions. However, during the period when the transmitting function is turned off, the receiving function will also be briefly turned on periodically. This process is called watchful sleep. See [link to relevant documentation]. Figure 4 (c) in the middle.
[0097] It should be noted that the low-power state is also called the sleep state. The above is merely an example of the low-power state, and the embodiments of this application are not limited thereto. In addition, the energy-saving processes described below can all be understood in accordance with the above description, and will not be described in detail hereafter.
[0098] In one alternative approach, after the OLT sends a first energy-saving agreement message to the MFU, the OLT can perform energy-saving processing on its downlink port connected to the MFU according to the first energy-saving parameters. For example, it can obtain a start time parameter and an energy-saving duration parameter from the first energy-saving parameters, and then perform energy-saving processing on the downlink port using the energy-saving duration at the time indicated by the start time parameter. This energy-saving processing of the MFU's uplink port and the OLT's downlink port can also be understood as... Figure 2 Energy saving is performed on link 0 in the process.
[0099] exist Figure 3 In the process shown, the first energy-saving parameter is determined by the MFU or the OLT, which will be explained below.
[0100] 1. The first energy-saving parameter is determined by the MFU. When sending the first energy-saving request to the OLT, the MFU recommends the first energy-saving parameter to the OLT. Figure 5 A schematic diagram illustrating the interactions between the MFU, SFU, and OLT is provided. Figure 5 The following explanation uses SFU1 and SFU2 connected to MFU as an example.
[0101] In step S201, the SFU and MFU complete the interaction to start energy-saving processing, and the SFU performs energy-saving processing.
[0102] In this embodiment, the interaction process of energy-saving processing between the SFU and MFU is described in [reference needed]. Figure 6 The process shown is illustrated in steps S2011 to S2014. Figure 6 The process of applying for energy-saving treatment for other SFUs is similar to that of SFU1, using SFU1 as an example.
[0103] In step S2011, SFU1 sends an energy-saving request to MFU, which instructs SFU1 to request energy-saving processing.
[0104] In this embodiment, SFU1 determines that the energy-saving conditions are met and sends an energy-saving request to MFU. This energy-saving request instructs SFU1 to request energy-saving processing. For example, for SFU1, if SFU1 has low traffic for a period of time and there are no low-latency requirement services (the absence of low-latency requirement services can also be understood as the absence of latency-sensitive services), or if the average temperature of SFU1 continuously exceeds a temperature threshold for a period of time, SFU1 determines that the energy-saving conditions are met. Alternatively, if the actual latency value of SFU1's services is lower than the latency requirement value by more than a certain threshold for a period of time, SFU1 determines that the energy-saving conditions are met.
[0105] In step S2012, the MFU sends an energy-saving consent message to the SFU1, which instructs the SFU1 to perform energy-saving processing.
[0106] In this embodiment, the MFU can use service traffic information and / or temperature to determine whether to agree to energy-saving processing by the SFU1. If it agrees to energy-saving processing by the SFU1, it sends an energy-saving agreement message to the SFU1. This message indicates that it agrees to the energy-saving processing by the SFU1. The service traffic information may include information on the service traffic sent and / or received on the SFU. After receiving the energy-saving agreement message, the SFU1 can perform some necessary operations for energy-saving processing, or it can choose not to perform any processing. For example, if the service traffic information indicates that the traffic volume is relatively small and there are no low-latency requirement services, and / or the amount of data sent by the MFU to the SFU1 does not exceed a first threshold, then the MFU agrees to the energy-saving processing by the SFU1; otherwise, it disagrees. As another example, if the average temperature of the SFU1 is greater than a second threshold, and / or the maximum temperature is greater than a third threshold, then the MFU agrees to the energy-saving processing by the SFU1; otherwise, it disagrees. This is because when the temperature of the SFU1 is too high, it needs to perform energy-saving processing in a timely manner to reduce the temperature. The second threshold is less than the third threshold, and the second and third thresholds are set according to the actual deployment environment.
[0107] In addition, when the MFU does not agree to the SFU1 performing energy-saving processing, the MFU sends an energy-saving rejection message to the SFU1, which is used to indicate that it does not agree to the SFU1 performing energy-saving processing.
[0108] In one optional approach, the MFU receives service traffic information sent by the SFU1. The SFU1 can collect service traffic information and send it to the MFU. For example, the SFU1 may periodically collect service traffic information after going live, or periodically collect service traffic information during a specified time period of the day, such as when the number of historically associated sites is less than a threshold value (set based on experience), or when service traffic is determined to be low. This service traffic information can be from the period most recently in time.
[0109] The service traffic information includes, but is not limited to, one or more of the following: traffic size, traffic priority, or service type. Traffic size refers to the total transmitted and received traffic, which is the sum of traffic from various interfaces, including network ports, Universal Serial Bus (USB) interfaces, telephone interfaces, Wi-Fi interfaces, and optical interfaces. Traffic priority refers to the transmission priority of traffic; higher priority traffic is transmitted first, and lower priority traffic is transmitted later. Generally, high-priority traffic requires low latency or has a lower tolerance for latency, resulting in a lower latency requirement. Low-priority traffic is not sensitive to latency or has a higher tolerance for latency, resulting in a more lenient latency requirement. Service type reflects the latency requirements of the service. For example, services such as online games, web conferencing, or voice communication are latency-sensitive and have a lower tolerance for latency, resulting in a lower latency requirement. Services such as file transfer are non-latency-sensitive and have a higher tolerance for latency, resulting in a more lenient latency requirement. All latency mentioned here and below refers to transmission latency.
[0110] Optionally, the service traffic information may also include the actual latency value of the current service, which includes the actual average latency value over a recent period and / or the maximum value.
[0111] Optionally, business traffic information may also include the number of associated sites. Generally, the more associated sites, the greater the traffic.
[0112] Optionally, SFU1 can also send its own temperature information over a period of time to MFU, which includes one or more of the following: average temperature, maximum temperature, or minimum temperature.
[0113] Optionally, the energy-saving consent message and the energy-saving rejection message can be the same message carrying different parameters, or they can be different messages. For example, the energy-saving consent message includes a consent identifier, and the energy-saving rejection message includes a rejection identifier.
[0114] In one alternative approach, after receiving the energy-saving consent message, SFU1 can also send service traffic information to MFU, so that MFU can use the latest service traffic information to determine the energy-saving parameters of SFU1.
[0115] In step S2013, the MFU interacts with the SFU1 to obtain the second energy-saving parameter of the SFU1.
[0116] In this embodiment, the MFU determines the second energy-saving parameter of the SFU1. The MFU sends the second energy-saving parameter to the SFU1 through the ONU management and control interface (OMCI) message, the Wi-Fi management and control interface (WMCI) message, or other messages. The definition of the second energy-saving parameter is described above and will not be repeated here.
[0117] In one alternative approach, when the MFU and SFU interact with the second energy-saving parameter, they may also carry an indicator indicating whether to carry a start time parameter. If the indicator is present, the start time parameter is carried; otherwise, it is not. When the start time parameter is not carried, the SFU uses the time agreed upon with the MFU to begin energy-saving processing.
[0118] In one alternative approach, the process by which the MFU determines the second energy-saving parameter of the SFU1 is as follows:
[0119] If SFU1 is the first SFU to undergo energy-saving processing, then MFU uses the service traffic volume of SFU1 to determine the second energy-saving duration parameter of SFU1. For example, MFU determines the target service traffic range to which the service traffic volume of SFU1 belongs, and in the correspondence between service traffic range and energy-saving duration parameter, determines the energy-saving duration parameter corresponding to the target service traffic range, and sets this energy-saving duration parameter as the energy-saving duration parameter of SFU1. Furthermore, MFU determines the start time parameter of SFU1 to be the time point closest to the current time point, which is a time point after SFU1 receives the second energy-saving parameter.
[0120] If SFU1 is not the first SFU to perform energy-saving processing, then the second energy-saving parameter of SFU1 is determined using the second energy-saving parameter of the SFU that has already started energy-saving processing. Assume that SFU2 started energy-saving processing before SFU1. If the service traffic information of SFU1 is similar to that of SFU2, then the energy-saving duration parameter of SFU2 is determined as the energy-saving duration parameter of SFU1, and the time point at which SFU2 next switches from a low-power state to a wake-up state is determined as the start time point of SFU1. Thus, after receiving the second energy-saving parameter, SFU1 switches to a low-power state, and then switches to a wake-up state at that time point to synchronize with SFU2. Alternatively, the energy-saving duration parameter of SFU2 is determined as the energy-saving duration parameter of SFU1, and the time point at which SFU2 next switches from a wake-up state to a low-power state is determined as the start time point of SFU1. Thus, after receiving the second energy-saving parameter, SFU1 remains in a wake-up state, and then switches to a low-power state at that start time to synchronize with SFU2. This method allows SFU1 and SFU2 to switch from a low-power state to a wake-up state simultaneously, or from a wake-up state to a low-power state simultaneously.
[0121] If the service traffic information of SFU1 is not similar to that of SFU2, consider that the energy-saving duration parameters of SFU1 and SFU2 are different, but satisfy a certain relationship. For SFU1, the longest duration of a single low-power state is denoted as L1, and the shortest duration of a single wake-up state is denoted as L2. For SFU2, the longest duration of a single low-power state is denoted as L3, and the shortest duration of a single wake-up state is denoted as L4. The relationship between them satisfies formula (1).
[0122] L1+L2=N*(L3+L4) (1)
[0123] SFU2 is any SFU among the SFUs connected to the MFU that has undergone energy-saving processing. In this embodiment, for ease of calculation, SFU2 has the minimum L3+L4 or the maximum L3+L4.
[0124] The value of N is determined based on the difference between the service traffic information of SFU1 and SFU2. For example, if the service traffic information of SFU1 indicates a low latency requirement compared to SFU2, the value of N is less than 1, so that the wake-up interval of SFU1 is shorter and the data transmission latency is reduced. If the service traffic information of SFU1 indicates a more lenient latency requirement and less traffic compared to SFU2, the value of N is greater than 1, so that the wake-up interval of SFU1 is longer and it stays in a low-power state more often, so as to achieve better energy saving. When the service traffic information of SFU2 is similar to that of SFU1, N equals 1.
[0125] In one example, for SFU1, the latency requirement value indicated by the service traffic information is weighted by the reciprocal of the traffic size to obtain the first weighted value of SFU1. For SFU2, the latency requirement value indicated by the service traffic information is weighted by the reciprocal of the traffic size to obtain the second weighted value of SFU2. The ratio of the first weighted value to the second weighted value is determined and set as N.
[0126] In another example, N is determined by considering the relationship between the actual latency value and the latency requirement value, and / or the traffic volume. The central idea is: if the actual latency value of a latency-sensitive service does not meet the latency requirement value, less energy should be considered; if the traffic volume is too large, less energy should be considered. For example, for SFU1, the difference between the actual latency value and the latency requirement value of the latency-sensitive service is determined. If this difference is greater than 0, the average of the differences corresponding to the latency-sensitive services on SFU1 is taken to obtain a first average value. Then, the first average value is weighted with the traffic volume indicated by the traffic information of the service to obtain a first weighted value. For SFU2, the difference between the actual latency value and the latency requirement value of the latency-sensitive service is determined. If this difference is greater than 0, the average of the differences corresponding to the latency-sensitive services on SFU2 is taken to obtain a second average value. Then, the second average value is weighted with the traffic volume indicated by the traffic information of the service to obtain a second weighted value. The ratio of the second weighted value to the first weighted value is determined, and this ratio is set as N.
[0127] Optionally, in both examples, if the ratio is not close to 1, it indicates that the service traffic information of SFU1 and SFU2 is not similar; if the ratio is close to 1, it indicates that the service traffic information of SFU1 and SFU2 is similar.
[0128] Optionally, in both examples, for ease of calculation, if the ratio is greater than 1 and is not an integer, it is rounded down to N; if the ratio is less than 1 and is not an integer fraction, it is converted to the nearest integer fraction, which is N.
[0129] In another example, the MFU inputs the service traffic information of SFU1, the service traffic information of SFU2, and the second energy-saving parameter into a calculation formula or neural network model to obtain L1+L2.
[0130] It should be noted that the above are only a few possible implementation methods, and the embodiments of this application do not limit the method for determining whether business traffic information is similar.
[0131] Optionally, when the value of N is greater than or equal to 1, N is a positive integer.
[0132] Optionally, after determining the values of L1+L2, the sizes of L1 and L2 can be allocated according to a preset ratio, or the sizes of L1 and L2 can be determined according to the traffic characteristics indicated by the SFUI's service traffic information. For example, if the latency indicated by the traffic characteristics corresponds to a ratio, the sizes of L1 and L2 are allocated according to this ratio; if the L2 corresponding to the first latency is greater than the L2 corresponding to the second latency, the first latency is less than the second latency. As another example, if the traffic size indicated by the traffic characteristics corresponds to an allocation ratio, the sizes of L1 and L2 are allocated according to this allocation ratio; if the L2 corresponding to the first traffic size is greater than the L2 corresponding to the second traffic size, the first traffic size is greater than the second traffic size. As yet another example, if the first average value mentioned above corresponds to an allocation ratio, the sizes of L1 and L2 are allocated according to this allocation ratio.
[0133] Optionally, the MFU can use the service traffic information of SFU1 to determine traffic characteristics. These traffic characteristics include latency and / or traffic volume, with the latency determined based on the latency requirement value and / or the actual latency value. For example, if the traffic priority is high and / or the service type includes low-latency services, the latency is determined to be low; if the traffic priority is low and the service type does not include services with low latency requirements, the latency is determined to be high. The specific value of the latency requirement value can be determined based on the specific traffic priority value, the number of low-latency service requirements, and the specific service type. Generally, the higher the traffic priority, the lower the latency requirement value; the more low-latency services there are, the lower the latency requirement value; different service types correspond to different latency requirement values. This is just an example. The latency can also be determined based on the latency requirement value and the actual latency value. When considering the actual latency value, if the difference between the latency requirement value and the actual latency value of the latency-sensitive service is greater than 0 and less than the specified threshold, and / or the traffic priority is high, then the latency is determined to be relatively low.
[0134] Optionally, in order to align the timing of multiple SFUs switching from low-power state to wake-up state as much as possible, or to align the timing of multiple SFUs switching from wake-up state to low-power state as much as possible, so as to achieve the effect of sleeping and waking up at the same time, the time point indicated by the start time parameter can have a variety of possible situations.
[0135] The first scenario involves simultaneous switching to wake-up state, meaning that when multiple SFUs are performing energy-saving processing, there may be times when they simultaneously switch to wake-up state.
[0136] In one alternative approach, such as Figure 7As shown, MFU expects SFU2 to be in a low-power state when SFU1 receives the start time parameter. The start time parameter is used to indicate the first time point, which is the time point when SFU1 switches from the low-power state to the wake-up state.
[0137] The MFU determines the time when SFU2 will next switch from a low-power state to a wake-up state as the first time point. After receiving the second power-saving parameter, SFU1 immediately switches from a wake-up state to a low-power state, and then switches from a low-power state to a wake-up state upon reaching the first time point, waking up together with SFU2. Subsequently, SFU1 uses the power-saving duration parameter for power-saving processing. In this method, the actual time point when SFU1 begins power saving is the first time it switches from a wake-up state to a low-power state, and the time point when it begins using the power-saving duration parameter for power-saving processing is the first time point.
[0138] In another alternative approach, such as Figure 8 As shown, the MFU anticipates that SFU2 will be in a low-power state when SFU1 receives the start time parameter. The start time parameter indicates the third time point, which is the time when SFU1 switches from the wake-up state to the low-power state. The MFU determines the third time point by adding a duration A to the fourth time point, where duration A is the duration of a single wake-up state indicated in SFU2's second power-saving parameter. The fourth time point is the time when SFU2 will next switch from the low-power state to the wake-up state.
[0139] In another alternative approach, the MFU anticipates that SFU2 will be in a wake-up state when SFU1 receives the start time parameter. The start time parameter indicates a third time point, which is the time when SFU1 switches from the wake-up state to the low-power state. The MFU determines the third time point by adding a duration A to the fourth time point, and the fourth time point is the time when SFU2 last switched from the low-power state to the wake-up state.
[0140] In the latter two methods of the first scenario, when SFU1 receives the first power-saving parameter, it does not immediately switch from the wake-up state to the low-power state. Instead, it switches from the wake-up state to the low-power state at the third time point. Subsequently, SFU1 uses the power-saving duration parameter for power-saving processing. In this way, the actual time point at which SFU1 starts power saving and the time point at which it starts using the power-saving duration parameter for power saving are the same, both being the third time point.
[0141] In the latter two methods of the first scenario, the start time parameter can be used directly to indicate the third time point, or it can be used indirectly to indicate the third time point. For example, the start time parameter is used to indicate the fourth time point. After SFU1 obtains the fourth time point from the first energy-saving parameter, it adds the duration A to the fourth time point to obtain the third time point.
[0142] The second scenario involves simultaneous switching to a low-power state. This occurs when multiple SFUs are performing energy-saving processing, and there are times when they simultaneously switch to a low-power state.
[0143] In one alternative approach, such as Figure 9 As shown, the start time parameter is used to indicate the first time point, which is the time point when SFU1 switches from the low power state to the wake-up state.
[0144] The MFU subtracts the duration A from the second time point to determine the first time point. The second time point is the time when SFU2 will next switch from the wake-up state to the low-power state. The duration A is the duration of a single wake-up state indicated in the second power-saving parameter of SFU2. After receiving the second power-saving parameter, SFU1 immediately switches from the wake-up state to the low-power state, and then switches from the low-power state to the wake-up state when the first time point is reached, so as to enter the low-power state together with SFU2. Subsequently, SFU1 uses the power-saving duration parameter for power-saving processing. In this method, the actual time point when SFU1 starts power saving is the time point when it first switches from the wake-up state to the low-power state, and the time point when it starts power-saving processing is the first time point.
[0145] In this method, the start time parameter can be used directly to indicate the first time point or indirectly. For example, the start time parameter can be used to indicate the second time point. After SFU1 obtains the second time point from the second energy-saving parameter, it subtracts the duration A in the energy-saving duration parameter from the second time point to obtain the first time point.
[0146] In another alternative approach, such as Figure 10 As shown, the MFU determines the time when SFU2 will next switch from the wake-up state to the low-power state as the third time point. In this method, when SFU1 receives the second power-saving parameter, it does not immediately switch from the wake-up state to the low-power state, but rather switches from the wake-up state to the low-power state when the third time point is reached. Subsequently, SFU1 uses the power-saving duration parameter for power-saving processing. In this way, the actual time point at which SFU1 starts power saving and the time point at which it starts using the power-saving duration parameter for power saving are the same, both being the third time point.
[0147] In the illustrated methods, the relationship between the energy-saving duration parameters of SFU1 and SFU2 is: L1+L2=2*(L3+L4), which indicates that the service latency requirement of SFU1 is more lenient than that of SFU2. This is just an example and is not limited in the embodiments of this application.
[0148] In step S2014, SFU1 uses the second energy-saving parameter to perform energy-saving processing, and after the MFU performs energy-saving processing on each connected SFU, it performs energy-saving processing on the downlink port, which is the downlink port of the MFU connecting to the SFU.
[0149] In this embodiment, after receiving the second energy-saving parameter, SFU1 sends a confirmation message to MFU. Furthermore, SFU1 obtains the start time parameter and energy-saving duration parameter from the second energy-saving parameter, and performs energy-saving processing using the energy-saving duration parameter at the time indicated by the start time parameter. In this way, different SFUs can select different energy-saving parameters for different possible service traffic information, but maintain a certain relationship to ensure a period of simultaneous sleep and wake-up. Therefore, when all SFUs connected to the downlink port of MFU are in a low-power state, synchronous energy-saving processing can also be implemented on that downlink port, achieving optimal energy-saving and performance scheduling. For example, when all SFUs connected to MFU are in a low-power state, the downlink port is also set to a low-power state; when at least one SFU is in a wake-up state, the downlink port of MFU is also put into a wake-up state. This is equivalent to... Figure 2 Both Link 1 and Link 2 in the process are energy-saving.
[0150] In step S202, the MFU sends a first energy-saving request to the OLT, wherein the first energy-saving request is used to instruct the MFU to perform energy-saving processing, and the first energy-saving request includes a first energy-saving parameter.
[0151] In this embodiment, the MFU determines that the energy-saving conditions are met and sends a first energy-saving request to the OLT. The first energy-saving request includes a first energy-saving parameter, the contents of which are described above and will not be repeated here.
[0152] In an alternative approach, the first energy-saving request further includes a first identifier, which is used to indicate whether the first energy-saving request includes an identifier of recommended energy-saving parameters. In step S202, the value of the first identifier indicates that the first energy-saving request includes recommended energy-saving parameters.
[0153] In one alternative approach, the MFU determines the first energy-saving parameter as follows:
[0154] If the MFU is connected to a single SFU, the power-saving duration parameter of that SFU is used as the power-saving duration parameter for the uplink port of the MFU, and a start duration parameter is also determined to ensure that the MFU and SFU have a period of time when they are simultaneously in a wake-up state and / or a period of time when they are simultaneously in a low-power state. If the MFU is connected to multiple SFUs, the power-saving duration parameters of these multiple SFUs are used to determine the first power-saving parameter of the MFU.
[0155] One example of determining the power-saving duration parameter is that the MFU determines the minimum power-saving cycle of the multiple SFUs. A power-saving cycle is equal to the sum of the shortest duration of being in the wake-up state and the longest duration of being in the low-power state. The MFU determines the minimum power-saving cycle as the power-saving duration in the first power-saving parameter. Then, it determines the maximum value of the shortest duration of being in the wake-up state among the multiple SFUs and determines this maximum value as the shortest duration of being in the wake-up state in the first power-saving parameter. Subtracting this shortest duration from the power-saving duration yields the longest duration of being in the low-power state in the first power-saving parameter.
[0156] Another example of determining the power-saving duration parameter is that the MFU determines the maximum value of the shortest wake-up time among the multiple SFUs as the shortest wake-up time in the first power-saving parameter. By setting the start time parameter, the uplink port of the MFU can transmit and receive data as long as any SFU is in the wake-up state. Furthermore, the MFU determines the SFU with the minimum longest low-power state time among the multiple SFUs as the target SFU. The shortest wake-up time and the longest low-power state time of this target SFU are added together to obtain a value equal to the sum of L5 and L6, where L5 is the longest low-power state time in the first power-saving parameter, and L6 is the shortest wake-up time in the first power-saving parameter.
[0157] Another example of determining the power saving duration parameter is that the MFU determines the maximum value of the shortest duration of the wake-up state among the multiple SFUs, adds the first duration to the maximum value, and determines it as the shortest duration of the wake-up state among the first power saving parameters. Furthermore, the first duration is subtracted from L5 obtained in the previous example to obtain the longest duration of the low power state among the first power saving parameters.
[0158] For an example of determining the start time parameter, see [link to example]. Figure 7 If multiple SFUs simultaneously enter the wake-up state at the same time, the i-th time point closest to the current time point is determined as the starting time point in the first energy-saving parameter. In this method, after receiving the first energy-saving parameter, the MFU directly enters the low-power state and is woken up at the starting time point to enter the wake-up state.
[0159] For another example of determining the start time parameter, see [link to relevant documentation]. Figure 8 The starting time parameter in the first power-saving parameter is determined by identifying the k-th time from which a particular SFU (System Function Unit) transitions from wake-up to low-power state, most recently relative to the current time. In this method, after receiving the first power-saving parameter, the MFU (Master Function Unit) directly enters the low-power state and is woken up at this starting time point to enter the wake-up state.
[0160] For another example of determining the start time parameter, see [link to relevant documentation]. Figure 9 If multiple SFUs simultaneously enter a low-power state, the j-th time point closest to the current time point is determined as the starting time point in the first power-saving parameter. In this method, after receiving the first power-saving parameter, the MFU remains in a wake-up state and enters a low-power state at the starting time point.
[0161] For another example of determining the start time parameter, see [link to relevant documentation]. Figure 10 The starting time parameter in the first power-saving parameter is determined by identifying the k-th time from which a particular SFU (Streaming Function Unit) transitions from a low-power state to a wake-up state, most recently relative to the current time. In this method, the MFU (Streaming Function Unit) remains awake after receiving the first power-saving parameter and then enters a low-power state at that starting time.
[0162] The values of i, j, and k are determined based on the actual time point at which the MFU receives the first energy-saving consent message. Generally, the values of i, j, and k are chosen such that the time point indicated by the start time parameter is after the first energy-saving simultaneous message has been received. For example, i is less than or equal to 3, such as i equal to 1, j less than or equal to 3, and k less than or equal to 3.
[0163] It should be noted that, in Figures 7 to 10 In the SFU synchronous energy-saving scheme shown, the first energy-saving parameter can be determined using any of the methods in the examples above, and is not limited to this. Figures 7 to 10 The scheme shown is as follows. Furthermore, when determining the first energy-saving parameter, a scheduling approach that balances energy saving and performance should be adopted.
[0164] It should also be noted that the above are only a few ways to determine the first energy-saving parameter. In the embodiments of this application, other methods can also be used to determine the first energy-saving parameter, as long as the following conditions are met: when at least one SFU is in a wake-up state, the MFU is in a wake-up state, and the uplink port of the MFU and each SFU are simultaneously in a low-power state for a period of time.
[0165] In step S203, the OLT sends a first energy-saving consent message to the MFU.
[0166] In this embodiment, the OLT determines whether it agrees to the MFU performing energy-saving processing. If it agrees, it sends a first energy-saving agreement message to the MFU.
[0167] In addition, if the OLT does not agree to the MFU's energy-saving processing, it sends a first energy-saving rejection message to the MFU.
[0168] Step S204: OLT and MFU interact to set energy-saving parameters.
[0169] In this embodiment, step S204 is an optional step. The OLT and MFU exchange energy-saving parameters via OMCI messages.
[0170] In one alternative approach, after sending a first energy-saving consent message to the MFU, the OLT sends a first energy-saving parameter to the MFU. After receiving the first energy-saving parameter, the MFU executes step S205 and sends a confirmation message to the OLT so that the OLT knows that the MFU has received the first energy-saving parameter.
[0171] Optionally, the first energy-saving parameter issued by the OLT is the same as the first energy-saving parameter reported by the MFU to the OLT.
[0172] Alternatively, the first power-saving parameter issued by the OLT may differ from the first power-saving parameter reported by the MFU to the OLT. For example, if the OLT determines that the duration of the low-power state in the first power-saving parameter is too long, it can shorten the longest duration of the low-power state; or if the OLT determines that the duration of the wake-up state in the first power-saving parameter is too short, it can extend the shortest duration of the wake-up state.
[0173] In one alternative approach, when the OLT sends the first energy-saving parameter to the MFU, it may also carry a second identifier. This second identifier indicates whether a start time parameter is included. If the second identifier indicates that a start time parameter is included, then the first energy-saving parameter includes the start time parameter; otherwise, it does not. If the start time parameter is not included, the OLT and MFU pre-agree on a start time point. Upon reaching this start time point, energy-saving processing is performed using an energy-saving duration parameter. For example, the OLT and MFU agree that the start time point is the time point after receiving the first energy-saving parameter and the target duration has elapsed.
[0174] In step S205, the MFU uses the first energy-saving parameter to perform energy-saving processing on the port connected to the OLT in the MFU.
[0175] In this embodiment, after receiving the first energy-saving consent message, the MFU obtains the start time parameter and energy-saving duration parameter from the first energy-saving parameters. At the time indicated by the start time parameter, the energy-saving duration parameter is used to perform energy-saving processing on the uplink port, which is the port in the MFU connected to the OLT.
[0176] In one alternative approach, while the MFU is saving energy, the OLT can also use a first energy-saving parameter to perform energy-saving processing on the ports in the OLT connected to the MFU. That is, the OLT obtains a start time parameter and an energy-saving duration parameter from the first energy-saving parameter. At the time indicated by the start time parameter, it uses the energy-saving duration parameter to perform energy-saving processing on the downlink port, which is the port in the OLT connected to the MFU. Thus, for... Figure 2This is equivalent to energy-saving processing for links 0, 1, and 2. See [link / reference] Figure 11 There are periods when all three links are simultaneously in a wake-up state and periods when they are simultaneously in a low-power state. This not only does not delay data transmission, but also saves energy for the PON as a whole.
[0177] It should be noted that the power-saving processing of the downlink port by the OLT is optional. The downlink port may also be exempt from power-saving processing, and the parameters used for power-saving processing may be different from the first power-saving parameters. However, when the MFU is in the wake-up state, the OLT will necessarily be in the wake-up state.
[0178] In an alternative approach, without executing step S204, the MFU uses the energy-saving parameter carried in the first energy-saving request as the first energy-saving parameter when performing energy-saving processing. Thus, after the OLT sends the first energy-saving agreement message to the MFU, the two do not need to exchange energy-saving parameters again.
[0179] Optionally, the first energy-saving consent message may carry an indication identifier, which is used to indicate to the MFU that the energy-saving parameter for energy-saving processing is the first energy-saving parameter reported by the MFU.
[0180] For ease of understanding, this application also provides a schematic diagram of the MFU requesting energy saving process, see [link to relevant documentation]. Figure 12 .
[0181] 2. The OLT determines the first energy-saving parameter of the MFU. Figure 13 The process for energy-saving processing of MFU applications is provided, see steps S301 to S306.
[0182] In step S301, the MFU sends a first energy-saving request to the OLT, wherein the first energy-saving request is used to instruct the MFU to request energy-saving processing.
[0183] The process of step S301 is described in the same way as that of step S101, and will not be repeated here.
[0184] In step S302, the OLT decides whether to agree to the MFU performing energy-saving treatment.
[0185] In this embodiment, the OLT uses the service traffic information of the MFU to determine whether the MFU can perform energy-saving processing. For example, if the service traffic sent to the MFU is less than a certain threshold, it is determined that the MFU can perform energy-saving processing; otherwise, it is determined that energy-saving processing cannot be performed.
[0186] Step S303: If the MFU is allowed to perform energy-saving processing, the OLT determines the first energy-saving parameter to be used by the MFU based on the energy-saving parameters of each SFU connected to the MFU.
[0187] In this embodiment, the process by which the OLT determines the first energy-saving parameter is the same as the process by which the MFU determines the first energy-saving parameter, and will not be described again here.
[0188] In step S304, the OLT sends a first energy-saving consent message to the MFU, wherein the first energy-saving consent message is used to instruct the MFU to perform energy-saving processing.
[0189] Step S305: The OLT interacts with the MFU to obtain the first energy-saving parameter of the MFU.
[0190] The process of interacting with the first energy-saving parameter in step S305 is described in step S204 and will not be repeated here.
[0191] In step S306, the MFU uses the first energy-saving parameter to perform energy-saving processing on the uplink port, which is the port in the MFU that connects to the OLT.
[0192] Optionally, the OLT uses a first energy-saving parameter to perform energy-saving processing on the downlink port, which is the port in the OLT that connects to the MFU. The process of the OLT performing energy-saving processing on this downlink port is described above and will not be repeated here.
[0193] After step S305, after the OLT and MFU exchange energy-saving parameters, the OLT can also use the first energy-saving parameter to perform energy-saving processing on the downlink port connected to the MFU.
[0194] exist Figure 13 In the process shown, when an SFU applies for energy-saving processing, the decision can be made by the OLT or the MFU, as explained below.
[0195] a. When an SFU applies for energy-saving treatment, the MFU makes the decision. See [link / reference]. Figure 14 Steps S401 to S405 in the process shown.
[0196] In step S401, SFU1 sends a second energy-saving request to MFU, wherein the second energy-saving request is used to instruct SFU1 to request energy-saving processing.
[0197] In this embodiment, the process by which SFU1 determines to make an energy-saving request is described below. Figure 6 The description in the text will not be repeated here.
[0198] In step S402, the MFU sends a second energy-saving consent message to the SFU1.
[0199] In this embodiment, the MFU receives a second energy-saving request and determines whether to agree to the energy-saving processing of SFU1. If it agrees, step S403 is executed; otherwise, an energy-saving rejection message is sent to SFU1. After agreeing to the energy-saving processing of SFU1, the MFU determines the second energy-saving parameter of SFU1. The process by which the MFU determines whether to agree to the energy-saving processing of SFU1 and determines the second energy-saving parameter is described above and will not be repeated here.
[0200] In step S403, the MFU and SFU1 interact to obtain the second energy-saving parameter.
[0201] In this embodiment, after the MFU sends the second energy-saving consent message to the SFU1, it sends the second energy-saving parameter to the SFU1. After receiving the second energy-saving parameter, the SFU1 executes step S404 and sends a confirmation message to the MFU so that the MFU knows that the SFU1 has received the second energy-saving parameter.
[0202] In step S404, SFU1 uses the second energy-saving parameter to perform energy-saving processing.
[0203] In this embodiment, after receiving the second energy-saving parameter, SFU1 obtains the start time parameter and energy-saving duration parameter from the second energy-saving parameter, and performs energy-saving processing using the energy-saving duration parameter at the time indicated by the start time parameter. After SFU1 performs energy-saving processing, MFU sends SFU1's data to SFU1 during SFU1's wake-up time period.
[0204] In step S405, the MFU sends the energy-saving information of SFU1 to the OLT.
[0205] In this embodiment, the MFU also sends energy-saving information of SFU1 to the OLT. This energy-saving information includes the identifier of SFU1 and a second energy-saving parameter of SFU1. After receiving the second energy-saving parameter, the OLT can record it. When the MFU subsequently requests energy-saving processing, the second energy-saving parameter can be used to determine the first energy-saving parameter.
[0206] b. When an SFU applies for energy-saving treatment, the decision is made by the OLT. See [link / reference]. Figure 15 In the process shown, steps S501 to S506 are... Figure 15 The diagram shows that SFU1 and SFU2 are requesting energy-saving processing.
[0207] In step S501, the SFU sends a second energy-saving request to the MFU, wherein the second energy-saving request is used to instruct the SFU to request energy-saving processing.
[0208] In step S502, the MFU sends a third energy-saving request to the OLT, wherein the third energy-saving request includes the second energy-saving parameter and is used to instruct the SFU to request energy-saving processing.
[0209] In this embodiment, after receiving the second energy-saving request from the SFU, the MFU determines whether to agree to the SFU's energy-saving processing. If it agrees, it sends a third energy-saving request to the OLT. The third energy-saving request includes the second energy-saving parameters and the SFU's identifier. If it disagrees, it sends an energy-saving rejection message to the SFU. This way, the MFU is closer to the SFU and has a better understanding of the SFU's situation. Since the MFU is the first to determine whether to agree to the SFU's energy-saving processing, if the MFU determines that the SFU cannot perform energy-saving processing, the SFU will inevitably be unable to do so. This eliminates the need for the OLT to make a decision on whether the SFU should perform energy-saving processing, reducing both data transmission and message processing volume. The process by which the MFU determines whether to agree to the SFU's energy-saving processing is described above and will not be repeated here. Alternatively, after receiving the second energy-saving request from the SFU, the MFU may not determine whether to agree to the SFU's energy-saving processing and directly send a third energy-saving request to the OLT.
[0210] In one alternative approach, the third energy-saving request includes a third identifier, which indicates whether FTTR PON energy-saving information is included. If the third identifier is an identifier that includes FTTR PON energy-saving information, then the third energy-saving request includes the SFU identifier and the second energy-saving parameter. Here, the identifier for FTTR PON energy-saving information is represented using the SFU identifier.
[0211] In an alternative approach, the second energy-saving parameter may also include one or more of the active held interval, itransinit, and Itxinit, defined in the same way as those defined above, except that this applies to the SFU rather than the MFU.
[0212] In step S503, the OLT sends a third energy-saving consent message to the MFU, wherein the third energy-saving consent message is used to instruct the SFU to perform energy-saving processing.
[0213] In this embodiment, after receiving the third energy-saving request sent by the MFU, the OLT determines whether to agree to the SFU performing energy-saving processing. If it agrees, it sends a third energy-saving agreement message to the MFU, which is used to indicate that it agrees to the SFU performing energy-saving processing.
[0214] The process by which the OLT determines whether to approve the energy-saving treatment of the SFU is the same as the process by which the MFU determines whether to approve the energy-saving treatment of the SFU, as described above, and will not be repeated here.
[0215] In addition, after rejecting the SFU from performing energy-saving processing, the OLT sends an energy-saving rejection message to the MFU, which is used to instruct the SFU to reject energy-saving processing.
[0216] In step S504, the MFU sends a second energy-saving consent message to the SFU.
[0217] In step S504, if the OLT sends a third energy-saving consent message to the SFU, the MFU sends a second energy-saving consent message to the SFU. If the OLT sends an energy-saving rejection message to the MFU, the MFU also sends an energy-saving rejection message to the SFU.
[0218] Step S505: The MFU and SFU interact to obtain the second energy-saving parameter.
[0219] In step S506, the SFU uses the second energy-saving parameter to perform energy-saving processing.
[0220] exist Figure 15 In the process shown, if the OLT disagrees with using the second energy-saving parameter reported by the MFU, it also determines the second energy-saving parameter for SFU1 and sends it to the MFU so that SFU1 can use the second energy-saving parameter determined by the OLT to perform energy-saving processing.
[0221] When the OLT decides whether the SFU should perform energy-saving treatment, Figure 13 In the process shown, the OLT determines the first energy-saving parameter. In another method, the MFU determines the first energy-saving parameter and sends it to the OLT in the first energy-saving request.
[0222] The above description enables the OLT, MFU, and SFU to achieve coordinated hibernation.
[0223] For ease of understanding, this application also provides a flowchart of energy-saving processing for MFU and SFU applications, see [link / reference]. Figure 16 and Figure 17 .
[0224] The previous section described the energy-saving process of SFU and MFU. The following section describes the process of stopping energy-saving processing of SFU and MFU. There are several ways to stop energy-saving processing of SFU and MFU; three options are provided below, which enable coordinated wake-up of OLT, MFU, and SFU.
[0225] Method 1: The OLT instructs the SFU and MFU to stop energy-saving processing. See [link / reference] Figure 18 Steps S601 to S603. In Figure 18 The following example illustrates how to instruct SFU1 to stop energy-saving processing. SFU1 is the second sub-device.
[0226] In step S601, the OLT determines that SFU1 has stopped energy-saving processing and sends a second energy-saving rejection message to the MFU. The second energy-saving rejection message is used to instruct SFU1 to stop energy-saving processing.
[0227] In this embodiment, the OLT determines that SFU1 should stop energy-saving processing based on the service traffic of SFU1. For example, the OLT determines that service data of a specific service type needs to be sent to SFU1, or that low-latency service data needs to be sent to SFU1, or that a large amount of service data needs to be sent to SFU1, etc., and the OLT determines that SFU1 should stop energy-saving processing. Then the OLT sends a second energy-saving rejection message to the MFU, which includes the identifier of SFU1 and a shutdown identifier.
[0228] In step S602, the OLT and MFU stop energy-saving processing, and the MFU sends a first energy-saving rejection message to SFU1, which is used to instruct SFU1 to stop energy-saving processing.
[0229] In this embodiment, the MFU receives a second energy-saving rejection message, stops energy-saving processing, and parses the identifier and shutdown identifier of SFU1 from the second energy-saving rejection message. The MFU then sends a first energy-saving rejection message to the SFU1 indicated by the SFU1 identifier, the first energy-saving rejection message including the shutdown identifier.
[0230] In step S603, SFU1 stops energy-saving processing.
[0231] In this embodiment, SFU1 receives a first energy-saving rejection message, parses the shutdown flag from the first energy-saving rejection message, and stops the energy-saving process.
[0232] In one alternative approach, if the OLT determines that all SFUs connected to the MFU have stopped power-saving processing, the second power-saving rejection message carries a shutdown flag but does not carry any SFU flags. This second power-saving rejection message is used to instruct the MFU's uplink port to stop power-saving processing and to instruct the MFU to wake up all connected SFUs. Upon receiving the second power-saving rejection message, the MFU stops power-saving processing on its uplink port and sends a first power-saving rejection message to each connected SFU.
[0233] Optionally, the second energy-saving rejection message may also include the number of SFUs that stop energy-saving processing.
[0234] Method 2: The MFU decides to stop energy-saving processing and instructs the SFU to stop energy-saving processing. See [link to relevant documentation]. Figure 19 Steps S701 to S704.
[0235] In step S701, the MFU determines that the SFU1 has stopped energy-saving processing and sends a first energy-saving rejection message to the SFU1. The first energy-saving rejection message is used to instruct the SFU1 to stop energy-saving processing.
[0236] In this embodiment, the MFU determines that SFU1 should stop energy-saving processing based on the service traffic information of SFU1. For example, the MFU determines that there is service data of a specific service type to be sent to SFU1, or the MFU determines that there is low-latency service data to be sent to SFU1, or the MFU determines that a large amount of service data to be sent to SFU1, etc., and the MFU determines that SFU1 should stop energy-saving processing. Then the MFU sends a first energy-saving rejection message to SFU1, which includes the identifier of SFU1 and a shutdown identifier.
[0237] After determining that SFU1 has stopped power-saving processing, MFU stops power-saving processing on the uplink port.
[0238] In step S702, SFU1 and MFU stop energy-saving processing.
[0239] In this embodiment, SFU1 receives a first energy-saving rejection message, parses the shutdown flag from the first energy-saving rejection message, and stops the energy-saving process.
[0240] In step S703, the MFU sends a power-saving request to the OLT, which includes an awake flag.
[0241] In this embodiment, after the MFU stops power-saving processing on the uplink port, it sends a power-saving request to the OLT. Upon receiving the power-saving request, the OLT records that the MFU has stopped power-saving processing, and the OLT's downlink port also stops power-saving processing. The OLT can then exchange service data with the MFU.
[0242] In step 703, an energy-saving request is sent; in another scenario, an energy-saving exit message can be sent.
[0243] Step S704, the OLT stops energy-saving processing (this step exists in the mode where the OLT also performs energy-saving processing).
[0244] Method 3: SFU1 applies to stop energy-saving treatment, see [link / reference] Figure 20 Steps S801 to S804.
[0245] In step S801, SFU1 determines to stop energy-saving processing and sends a fourth energy-saving request to MFU. The fourth energy-saving request is used to instruct SFU1 to request to stop energy-saving processing.
[0246] In this embodiment, SFU1 determines whether to stop energy-saving processing based on service traffic information. For example, SFU1 determines that an associated station (STA) has a large amount of data to send and decides to stop energy-saving processing; or, SFU1 determines that service data with low latency requirements needs to be sent; or, SFU1 identifies a newly associated STA. SFU1 sends a fourth energy-saving request to MFU, which includes a wake-up identifier.
[0247] In step S802, the MFU stops energy-saving processing.
[0248] In this embodiment, after receiving the fourth power-saving request, the MFU stops power-saving processing on the uplink port.
[0249] In step S803, the MFU sends a fifth energy-saving request to the OLT, which instructs the MFU to request the cessation of energy-saving processing.
[0250] In this embodiment, after the MFU stops power-saving processing on the uplink port, it sends a fifth power-saving request to the OLT. After receiving the fifth power-saving request, the OLT records that the MFU has stopped power-saving processing, and the OLT can then interact with the MFU to exchange service data.
[0251] In one alternative approach, when the SFU requests energy-saving treatment and the OLT makes the decision, i.e., [the following is adopted] Figure 15 During the process, the fifth energy-saving request also includes the identifier of SFU1 to instruct SFU1 to stop energy-saving processing. The OLT can record that SFU1 has stopped energy-saving processing and can subsequently send business data to SFU1.
[0252] In step S804, the OLT stops energy-saving processing.
[0253] The following describes the process of launching SFU.
[0254] In this embodiment of the application, the OLT can also record the SFU's information when the SFU comes online. Figure 21 and Figure 22 The SFU deployment process is provided; see [link / reference]. Figure 21 For steps S901 to S904, see [link / reference]. Figure 22 Steps S1001 to S1003. Figure 21 and Figure 22 The difference in the illustrated process is that, Figure 21 In the process, the identifier for SFU1 is assigned by the OLT. Figure 22 In this context, the identifier for SFU1 is assigned by MFU.
[0255] In step S901, SFU1 sends an online message to MFU.
[0256] In this embodiment, when SFU1 is powered on and online, it sends an online message to MFU. The online message includes some necessary information about MFU so that MFU can recognize SFU.
[0257] In step S902, the MFU sends an online notification of SFU1 to the OLT.
[0258] In this embodiment, after receiving the online message, the MFU reports the online notification of SFU1 to the OLT. After receiving the online notification, the OLT records SFU1 as a sub-device of the MFU and assigns an identifier to SFU1. Under the same MFU, this identifier uniquely indicates SFU1.
[0259] In step S903, the OLT sends the identifier assigned to SFU1 to the MFU.
[0260] In step S904, the MFU sends the identifier to the SFU1.
[0261] In this embodiment, the MFU sends the identifier to the SFU1, and the SFU1 can carry the identifier when sending data to distinguish it from other SFUs.
[0262] Step S1001: SFU1 sends an online message to MFU.
[0263] In step S1002, the MFU sends the identifier assigned to SFU1 to SFU1.
[0264] In this embodiment, after receiving the online message of SFU1, MFU assigns an identifier to SFU1.
[0265] In step S1003, the MFU sends a notification of SFU1’s online status to the OLT, which includes the identifier assigned to SFU1 by the MFU.
[0266] In this embodiment, after receiving the online notification, the OLT records the identifier of SFU1 and records SFU1 as a sub-device of MFU.
[0267] In this embodiment, the energy-saving request can be a sleep request message in the PON protocol, or other custom messages; this embodiment does not limit the type of message. The energy-saving requests here include the first to fifth energy-saving requests mentioned above.
[0268] The energy-saving consent message can be a sleep allow message in the PON protocol, carrying an on flag, or it can be other custom messages; this application embodiment does not limit this. The energy-saving consent messages here include the first, second, and third energy-saving consent messages mentioned above.
[0269] The energy-saving rejection message can be a Sleep Allow message in the PON protocol, carrying an off flag, or it can be other custom messages; this application embodiment does not limit this. The energy-saving rejection message here includes the first energy-saving rejection message and the second energy-saving rejection message mentioned above.
[0270] In this embodiment of the application, the energy saving request can also be used to instruct the application to enter the energy saving mode. Requesting to enter the energy saving mode means requesting to enable the energy saving function, but the energy saving process has not yet been actually performed.
[0271] In this embodiment of the application, in order to better manage the state, the OLT can store the state machine of the MFU to record the state of the uplink port of the MFU, and the MFU can also store the state machine of the SFU to record the state of the SFU. In addition, the OLT can also store the state of the SFU to record the state of the SFU.
[0272] It should be noted that in this embodiment, the example is that after all SFUs connected to the MFU have undergone energy-saving processing, the MFU requests to perform energy-saving processing. In another approach, the MFU can also perform energy-saving processing after some SFUs have undergone energy-saving processing. In this case, if SFU3, which has not yet undergone energy-saving processing, requests to perform energy-saving processing, the energy-saving parameters of SFU3 can be considered when determining the energy-saving parameters of SFU3, as well as the energy-saving parameters of the MFU, so that the energy-saving parameters of SFU3 match the energy-saving parameters of the MFU. This matching includes, but is not limited to: the time period during which SFU3 is in the wake-up state overlaps with the time period during which the MFU is in the wake-up state, and the time period during which SFU3 is in the low-power state overlaps with the time period during which the MFU is in the low-power state.
[0273] It should also be noted that the SFU identifier was used to indicate the SFU in the previous text. In fact, the link identifier between the SFU and the MFU can also be used to indicate the SFU.
[0274] In addition, when applying for energy-saving treatment, the SFU can also bring its own determined energy-saving parameters. The MFU decides whether the energy-saving parameters are available. If they are available, the energy-saving parameters are used directly; otherwise, the energy-saving treatment is determined for the SFU.
[0275] In this embodiment, coordinated energy-saving processing is performed on the links connecting the uplink and downlink ports of the MFU, enabling simultaneous sleep and wake-up, thereby reducing service latency while saving energy. Specifically, it enables better energy-saving scheduling, minimizing wake-up during sleep periods, thus achieving better energy saving and service performance. It also reduces segmented wake-up latency of the PON links at both ends, avoids repeated exits and re-entry into energy-saving mode, and eliminates energy-saving parameter negotiation, ensuring more stable operation of the energy-saving mode.
[0276] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.
[0277] This application uses the example of FTTR network and MFU uplink port collaborative energy saving for illustration, but it can also be applied to any scenario where the master device manages the sub-device, and this application does not limit it.
[0278] Figure 23 This is a structural diagram of the energy-saving device for PON provided in the embodiments of this application. Figure 23 The illustrated device can be implemented as part or all of the apparatus through software, hardware, or a combination of both. This device is used as a main device, which is connected to at least one sub-device, and is used to implement the method flow of MFU execution in the embodiments of this application. The device includes:
[0279] The sending module 110 is used to send a first energy-saving request to the optical line terminal, wherein the first energy-saving request is used to instruct the main device to request energy-saving processing;
[0280] The receiving module 120 is configured to receive a first energy-saving consent message sent by the optical line terminal, wherein the first energy-saving consent message is used to indicate that the main device is authorized to perform energy-saving processing;
[0281] The energy-saving module 130 is used to perform energy-saving processing on the port connected to the optical line terminal in the main device using a first energy-saving parameter, wherein the first energy-saving parameter is determined based on a second energy-saving parameter of the at least one sub-device, and the time period during which the port is in a low-power state overlaps with the time period during which the at least one sub-device is in a low-power state.
[0282] In one alternative approach, both the first energy-saving parameter and the second energy-saving parameter include a start time parameter and an energy-saving duration parameter. The start time parameter indicates the time point at which energy-saving processing begins using the energy-saving duration parameter, and the energy-saving duration parameter indicates the duration of being in the wake-up state and the duration of being in the low-power state.
[0283] In one alternative approach, the period during which the port is in a wake-up state overlaps with the period during which the at least one sub-device is in a wake-up state.
[0284] In one alternative approach, the first energy-saving request includes the first energy-saving parameter; the energy-saving module 130 is further configured to determine the first energy-saving parameter based on the second energy-saving parameter of the at least one sub-device before sending the first energy-saving request to the optical line terminal.
[0285] In an alternative embodiment, the receiving module 120 is further configured to receive the first energy-saving parameter sent by the optical line terminal before performing energy-saving processing using the first energy-saving parameter.
[0286] In an alternative embodiment, the energy-saving module 130 is further configured to determine, before sending a first energy-saving request to the optical line terminal, that each sub-device connected to the main device should undergo energy-saving processing.
[0287] In an alternative embodiment, the receiving module 120 is further configured to receive a second energy-saving request sent by a first sub-device among the at least one sub-device before sending an energy-saving request to the optical line terminal, wherein the second energy-saving request is used to instruct the first sub-device to request energy-saving processing.
[0288] The energy-saving module 130 is also used to determine the second energy-saving parameter of the first sub-device;
[0289] The sending module 110 is further configured to send a second energy-saving consent message and a second energy-saving parameter of the first sub-device to the first sub-device.
[0290] In an optional embodiment, the energy-saving module 130 is further configured to, before sending the second energy-saving consent message and the second energy-saving parameters of the first sub-device to the first sub-device, determine whether to allow the first sub-device to perform energy-saving processing, and send the energy-saving information of the first sub-device to the optical line terminal; or...
[0291] The sending module 110 is further configured to send a third energy-saving request to the optical line terminal, wherein the third energy-saving request includes the second energy-saving parameter, and the third energy-saving request is used to instruct the first sub-device to request energy-saving processing;
[0292] The receiving module 120 is further configured to receive a third energy-saving consent message sent by the optical line terminal, wherein the third energy-saving consent message is used to indicate consent to the first sub-device to perform energy-saving processing.
[0293] In an alternative embodiment, the receiving module 120 is further configured to determine that the second sub-device among the at least one sub-device has stopped energy-saving processing;
[0294] The sending module 110 is further configured to send a first energy-saving rejection message to the second sub-device, wherein the first energy-saving rejection message is used to instruct the second sub-device to stop energy-saving processing.
[0295] In an alternative embodiment, the receiving module 120 is further configured to:
[0296] Based on the service traffic information of the at least one sub-device, it is determined that the second sub-device should stop energy-saving processing; or...
[0297] The device receives a second energy-saving rejection message sent by the optical line terminal, wherein the second energy-saving rejection message is used to instruct the second sub-device to stop energy-saving processing.
[0298] In an optional manner, the receiving module 120 is further configured to receive a fourth energy-saving request sent by a second sub-device among the at least one sub-device, wherein the fourth energy-saving request is used to instruct the second sub-device to request to stop energy-saving processing;
[0299] The sending module 110 is further configured to send a fifth energy-saving request to the optical line terminal, wherein the fifth energy-saving request is used to instruct the master device to request to stop energy-saving processing.
[0300] Figure 24 This is a structural diagram of the energy-saving device for PON provided in the embodiments of this application. Figure 24 The illustrated device can be implemented as part or all of the apparatus through software, hardware, or a combination of both. This device is used in an OLT (Optical Linear Technology) to implement the method flow executed by the OLT in the embodiments of this application. The device includes:
[0301] The receiving module 210 is configured to receive a first energy-saving request sent by the master device, wherein the first energy-saving request is used to instruct the master device to request energy-saving processing;
[0302] The sending module 220 is used to send a first energy-saving consent message to the master device to instruct the master device to use a first energy-saving parameter to perform energy-saving processing on the port in the master device connected to the optical line terminal, wherein the first energy-saving parameter is determined based on a second energy-saving parameter of at least one sub-device connected to the master device, and the time period during which the port is in a low-power state overlaps with the time period during which the at least one sub-device is in a low-power state.
[0303] In one alternative approach, both the first energy-saving parameter and the second energy-saving parameter include a start time parameter and an energy-saving duration parameter. The start time parameter indicates the time point at which energy-saving processing begins using the energy-saving duration parameter, and the energy-saving duration parameter indicates the duration of being in the wake-up state and the duration of being in the low-power state.
[0304] In one alternative approach, the first energy-saving request includes the first energy-saving parameter; or, the sending module is further configured to: after receiving the first energy-saving request sent by the master device, determine the first energy-saving parameter based on the second energy-saving parameter of the at least one sub-device;
[0305] Send the first energy-saving parameter to the main device.
[0306] In an alternative embodiment, the device further includes an energy-saving module for: after sending a first energy-saving consent message to the master device, using the first energy-saving parameters to perform energy-saving processing on the port in the optical line terminal connected to the master device.
[0307] In an optional manner, the receiving module 210 is further configured to receive a third energy-saving request sent by the master device, wherein the third energy-saving request includes a second energy-saving parameter of the first sub-device, and the third energy-saving request is used to instruct the first sub-device to request energy-saving processing;
[0308] The sending module 220 is further configured to send a third energy-saving consent message to the master device, wherein the third energy-saving consent message is used to indicate consent to the first sub-device to perform energy-saving processing.
[0309] In an alternative embodiment, the apparatus further includes an energy-saving module for determining that a second sub-device among the at least one sub-device stops energy-saving processing;
[0310] The sending module 220 is further configured to send an energy-saving rejection message to the master device, wherein the energy-saving rejection message is used to instruct the second sub-device to stop energy-saving processing.
[0311] Figure 23 and Figure 24 For a detailed explanation of the energy-saving process of the device shown in the PON, please refer to the descriptions in the previous embodiments; it will not be repeated here. Figure 23 The device shown can be the MFU mentioned earlier. Figure 24 The device shown can be the OLT mentioned above.
[0312] This application also provides a communication device, which is the MFU mentioned above, for interacting with the SFU and the OLT.
[0313] This application also provides another communication device, namely the OLT mentioned above, for interacting with the MFU.
[0314] This application also provides a communication device 100. For example... Figure 25 As shown, the communication device 100 includes a bus 102, a processor 104, a memory 106, and a communication interface 108. The processor 104, the memory 106, and the communication interface 108 communicate with each other via the bus 102. The communication device 100 is the MFU and OLT mentioned above. It should be understood that this application does not limit the number of processors and memories in the communication device 100.
[0315] Bus 102 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 25 The bus 102 may be represented by a single line, but this does not mean that there is only one bus or one type of bus. The bus 102 may include a path for transmitting information between various components of the communication device 100 (e.g., memory 106, processor 104, communication interface 108).
[0316] The processor 104 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).
[0317] Memory 106 may include volatile memory, such as random access memory (RAM). Memory 106 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).
[0318] The memory 106 stores executable program code, and the processor 104 executes the aforementioned energy-saving method of PON using this executable program code. That is, the memory 106 stores program instructions for executing the aforementioned energy-saving method of PON.
[0319] The communication interface 108 can be an optical module to enable communication between the communication device 100 and other devices or communication networks.
[0320] Optionally, when the communication device 100 is an MFU, the MFU also includes a Wi-Fi function module for providing wireless services.
[0321] This application also provides a computer program product including program instructions stored in a computer-readable storage medium. The OLT's processor reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the OLT to perform the energy-saving PON method flow described above.
[0322] This application also provides a computer program product, which includes program instructions stored in a computer-readable storage medium. The processor of the host device reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the host device to perform the PON energy-saving method flow described above.
[0323] This application also provides a communication system, which includes the OLT and master device mentioned above.
[0324] Those skilled in the art will recognize that the method steps and units described in the embodiments disclosed in this application can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0325] In the embodiments provided in this application, it should be understood that the disclosed system architecture, apparatus, and methods can be implemented in other ways. For example, the apparatus 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 or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, or may be electrical, mechanical, or other forms of connection.
[0326] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.
[0327] Furthermore, the modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or in software.
[0328] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0329] In this application, the terms "first" and "second," etc., are used to distinguish identical or similar items that have substantially the same function and purpose. It should be understood that there is no logical or temporal dependency between "first" and "second," nor does it limit the quantity or order of execution. It should also be understood that although the following description uses the terms "first" and "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are merely used to distinguish one element from another. For example, without departing from the scope of the various examples, a first sub-device can be referred to as a second sub-device, and similarly, a second sub-device can be referred to as a first sub-device. Both the first and second sub-devices can be sub-devices, and in some cases, they can be separate and distinct sub-devices.
[0330] The phrase "at least one" in the preceding text can be understood as one or more.
[0331] The phrase "A and / or B" in the preceding text can be understood to include three cases: A, B, and A and B.
[0332] The above description is merely an exemplary 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 such 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. An energy-saving method for passive optical networks, characterized in that, The method is applied to a master device, the master device being connected to at least one sub-device, and the method includes: Send a first power saving request to the optical line terminal, wherein the first power saving request is used to instruct the master device to request power saving processing; Receive a first energy-saving consent message sent by the optical line terminal, wherein the first energy-saving consent message is used to indicate that the main device agrees to perform energy-saving processing; The first energy-saving parameter is used to perform energy-saving processing on the port connected to the optical line terminal in the main device, wherein the first energy-saving parameter is determined based on the second energy-saving parameter of the at least one sub-device, and the time period during which the port is in a low-power state overlaps with the time period during which the at least one sub-device is in a low-power state.
2. The method according to claim 1, characterized in that, Both the first energy-saving parameter and the second energy-saving parameter include a start time parameter and an energy-saving duration parameter. The start time parameter is used to indicate the time point at which the energy-saving processing begins using the energy-saving duration parameter, and the energy-saving duration parameter is used to indicate the duration of being in the wake-up state and the duration of being in the low-power state.
3. The method according to claim 1 or 2, characterized in that, The time period during which the port is in a wake-up state overlaps with the time period during which the at least one sub-device is in a wake-up state.
4. The method according to any one of claims 1 to 3, characterized in that, The first energy-saving request includes the first energy-saving parameter; before sending the first energy-saving request to the optical line terminal, the method further includes: The first energy-saving parameter is determined based on the second energy-saving parameter of the at least one sub-device.
5. The method according to any one of claims 1 to 4, characterized in that, Before performing energy-saving processing using the first energy-saving parameter, the method further includes: Receive the first energy-saving parameter sent by the optical line terminal.
6. The method according to any one of claims 1 to 5, characterized in that, Before sending the first power-saving request to the optical line terminal, the method further includes: Energy-saving measures are implemented for each sub-device connected to the main device.
7. The method according to any one of claims 1 to 6, characterized in that, Before sending the first power-saving request to the optical line terminal, the method further includes: Receive a second energy-saving request sent by a first sub-device among the at least one sub-devices, wherein the second energy-saving request is used to instruct the first sub-device to request energy-saving processing; Determine the second energy-saving parameter of the first sub-device; Send a second energy-saving consent message and the second energy-saving parameters of the first sub-device to the first sub-device.
8. The method according to claim 7, characterized in that, Before sending the second energy-saving consent message and the second energy-saving parameters of the first sub-device to the first sub-device, the method further includes: The system confirms and agrees to allow the first sub-device to perform energy-saving processing, and sends the energy-saving information of the first sub-device to the optical line terminal; or... Send a third energy-saving request to the optical line terminal, wherein the third energy-saving request includes a second energy-saving parameter of the first sub-device, and the third energy-saving request is used to instruct the first sub-device to request energy-saving processing; The system receives a third energy-saving consent message sent by the optical line terminal, wherein the third energy-saving consent message is used to indicate that the first sub-device is authorized to perform energy-saving processing.
9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: It is determined that the second sub-device in the at least one sub-device stops energy-saving processing; Send a first energy-saving rejection message to the second sub-device, wherein the first energy-saving rejection message is used to instruct the second sub-device to stop energy-saving processing.
10. The method according to claim 9, characterized in that, The step of determining that the second sub-device in the at least one sub-device stops energy-saving processing includes: Based on the service traffic information of the at least one sub-device, it is determined that the second sub-device should stop energy-saving processing; or... The device receives a second energy-saving rejection message sent by the optical line terminal, wherein the second energy-saving rejection message is used to instruct the second sub-device to stop energy-saving processing.
11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Receive a fourth energy-saving request sent by a second sub-device among the at least one sub-devices, wherein the fourth energy-saving request is used to instruct the second sub-device to request to stop the energy-saving process; A fifth energy-saving request is sent to the optical line terminal, wherein the fifth energy-saving request is used to instruct the master device to stop energy-saving processing.
12. An energy-saving method for passive optical networks, characterized in that, Applied to optical line terminals, the method includes: Receive a first energy-saving request sent by the master device, wherein the first energy-saving request is used to instruct the master device to request energy-saving processing; A first energy-saving consent message is sent to the master device to instruct the master device to perform energy-saving processing on the port connected to the optical line terminal using a first energy-saving parameter. The first energy-saving parameter is determined based on a second energy-saving parameter of at least one sub-device connected to the master device, and the time period during which the port is in a low-power state overlaps with the time period during which the at least one sub-device is in a low-power state.
13. The method according to claim 12, characterized in that, Both the first energy-saving parameter and the second energy-saving parameter include a start time parameter and an energy-saving duration parameter. The start time parameter is used to indicate the time point at which the energy-saving processing begins using the energy-saving duration parameter, and the energy-saving duration parameter is used to indicate the duration of being in the wake-up state and the duration of being in the low-power state.
14. The method according to claim 12 or 13, characterized in that, The first energy-saving request includes the first energy-saving parameter; or, after receiving the first energy-saving request sent by the master device, the method further includes: The first energy-saving parameter is determined based on the second energy-saving parameter of the at least one sub-device; Send the first energy-saving parameter to the main device.
15. The method according to any one of claims 12 to 14, characterized in that, After sending the first energy-saving consent message to the master device, the method further includes: The first energy-saving parameter is used to perform energy-saving processing on the port in the optical line terminal that connects to the main device.
16. The method according to any one of claims 12 to 15, characterized in that, The method further includes: The system receives a third energy-saving request sent by the master device, wherein the third energy-saving request includes a second energy-saving parameter of the first sub-device, and the third energy-saving request is used to instruct the first sub-device to request energy-saving processing. A third energy-saving consent message is sent to the master device, wherein the third energy-saving consent message is used to indicate that the first sub-device is authorized to perform energy-saving processing.
17. The method according to any one of claims 12 to 16, characterized in that, The method includes: It is determined that the second sub-device in the at least one sub-device stops energy-saving processing; A power saving rejection message is sent to the master device, wherein the power saving rejection message is used to instruct the second sub-device to stop power saving processing.
18. An energy-saving device for a passive optical network, characterized in that, The device is applied to a main device, the main device being connected to at least one sub-device, and the device includes: The sending module is used to send a first energy-saving request to the optical line terminal, wherein the first energy-saving request is used to instruct the master device to request energy-saving processing; The receiving module is used to receive an energy-saving consent message sent by the optical line terminal, wherein the energy-saving consent message is used to indicate that the main device is authorized to perform energy-saving processing; The energy-saving module is used to perform energy-saving processing on the port connected to the optical line terminal in the main device using a first energy-saving parameter, wherein the first energy-saving parameter is determined based on a second energy-saving parameter of the at least one sub-device, and the time period during which the port is in a low-power state overlaps with the time period during which the at least one sub-device is in a low-power state.
19. An energy-saving device for a passive optical network, characterized in that, The device, applied to optical line terminals, includes: The receiving module is configured to receive a first energy-saving request sent by the master device, wherein the first energy-saving request is used to instruct the master device to request energy-saving processing; The sending module is used to send a first energy-saving consent message to the master device to instruct the master device to use a first energy-saving parameter to perform energy-saving processing on the port in the master device connected to the optical line terminal, wherein the first energy-saving parameter is determined based on a second energy-saving parameter of at least one sub-device connected to the master device, and the time period during which the port is in a low-power state overlaps with the time period during which the at least one sub-device is in a low-power state.
20. A communication system, characterized in that, The communication system includes a main device and an optical line terminal; The main device is used to perform the method according to any one of claims 1 to 11; The optical line terminal is used to perform the method according to any one of claims 12 to 17.
21. A communication device, characterized in that, The communication device includes a communication interface, a processor, and a memory; The communication interface is used to communicate with other devices; The processor is configured to execute program instructions in the memory to perform the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 17.
22. A communication device, characterized in that, The communication device is used to perform the method according to any one of claims 1 to 11.
23. A communication device, characterized in that, The communication device is used to perform the method according to any one of claims 12 to 17.
24. A computer-readable storage medium, characterized in that, Includes program instructions, which, when executed by a communication device, cause the communication device to perform the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 17.