Computing power engine disaster recovery and energy saving method, communication equipment, storage medium and program product

Abstract

The embodiment of the invention provides a computing power engine disaster recovery and energy saving method, communication equipment, a storage medium and a program product. The method comprises the steps that the node state of a main engine node, opened target characteristic services and the number of service terminals are acquired; determining a first target service component in the main engine node according to the target characteristic service; according to the node state and the number of the service terminals, the operation states of the first target service component and a second target service component of the standby engine node are controlled, and the second target service component corresponds to the target characteristic service. According to the embodiment of the invention, an energy-saving strategy for dynamically scheduling the service components of the main engine node and the standby engine node to be on-line and off-line can be triggered based on the number of the service terminal users, and the main engine node and the standby engine node can perform load sharing and disaster recovery energy saving according to the number of the characteristic services and the number of the service concurrent terminal users. The energy consumption of the computing power engine is reduced as much as possible.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a computing power engine disaster recovery and energy-saving method, communication equipment, storage medium, and program product. Background Art

[0002] Computing engines are a type of product used in MEC. Currently, computing engines are being promoted in industrial park scenarios, primarily for applications in mining, ports, steel, airports, and other industrial park services. Industrial park services require high reliability. When a computing engine fails, it must ensure normal operation of the park's services. Therefore, computing engines must support redundant backups and elastic scalability.

[0003] Among them, the main demand points for disaster recovery deployment of computing power engines include disaster recovery requirements and load sharing requirements. Disaster recovery requirements refer to local disaster recovery and remote disaster recovery. Load sharing requirements refer to the situation where there are multiple 5G base stations in the same park. The processing capacity of one computing power engine cannot meet the computing power requirements, and multiple computing power engines are required to share the business load.

[0004] Computing engine disaster recovery deployment usually requires setting up active and standby engine nodes. In addition to platform components such as TCF and CONAP, active and standby engine nodes also include dozens of other service components such as positioning services, traffic diversion services, and IP identification services. However, since both active and standby engine nodes maintain hot backup status for all service components, their energy-saving effect is poor. Summary of the Invention

[0005] The embodiments of the present application provide a computing power engine disaster recovery and energy-saving method, communication equipment, storage medium and program product, which are intended to improve the energy-saving effect of computing power engine nodes.

[0006] In a first aspect, an embodiment of the present application provides a computing power engine disaster recovery and energy saving method, which is applied to a primary engine node. The method includes:

[0007] Obtain the node status of the active engine node, the enabled target feature services, and the number of service terminals;

[0008] Determining a first target service component in the active engine node according to the target characteristic service;

[0009] The operating states of the first target service component and the second target service component of the standby engine node are controlled according to the node state and the number of service terminals, wherein the second target service component corresponds to the target characteristic service.

[0010] In a second aspect, an embodiment of the present application provides a computing power engine disaster recovery and energy saving method, which is applied to a backup engine node. The method includes:

[0011] Obtain the node status of the active engine node and the target feature services enabled;

[0012] determining a second target service component in the standby engine node according to the target characteristic service;

[0013] The running state of the second target service component is controlled according to the node state or the load adjustment instruction sent by the active engine node.

[0014] In a third aspect, an embodiment of the present application provides a communication device, including:

[0015] at least one processor;

[0016] at least one memory for storing at least one program;

[0017] When at least one of the programs is executed by at least one of the processors, the computing power engine disaster recovery and energy saving method of the first aspect mentioned above is executed, or the computing power engine disaster recovery and energy saving method of the second aspect mentioned above is executed.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a program executable by a processor, wherein the program executable by the processor is executed by the processor to execute the computing power engine disaster recovery and energy-saving method such as the first aspect mentioned above, or the computing power engine disaster recovery and energy-saving method such as the second aspect mentioned above.

[0019] In a fifth aspect, an embodiment of the present application provides a computer program product, comprising a computer program or computer instructions, wherein the computer program or the computer instructions are stored in a computer-readable storage medium, and the processor of a computer device reads the computer program or the computer instructions from the computer-readable storage medium, and the processor executes the computer program or the computer instructions, so that the computer device executes the computing power engine disaster recovery and energy-saving method as described in the first aspect above, or the computing power engine disaster recovery and energy-saving method as described in the second aspect above.

[0020] According to the computing power engine disaster recovery and energy-saving method, communication equipment, storage medium and program product provided in the embodiments of the present application, since the embodiments of the present application can control the operating status of the first target service component of the active engine node and the second target service component of the backup engine node according to the node status and the number of service terminals, the embodiments of the present application can trigger the energy-saving strategy of dynamically scheduling the service components of the active engine node and the backup engine node to go online and power off based on the number of service terminal users. The active engine node and the backup engine node can perform load sharing and disaster recovery energy saving according to the characteristic services and the number of concurrent terminal users of the service, thereby reducing the energy consumption of the computing power engine as much as possible. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 This is a schematic diagram of the architecture of the computing power engine disaster recovery system provided in an embodiment of the present application.

[0022] Figure 2 This is a flow chart of a computing power engine disaster recovery and energy saving method performed by a primary engine node side, provided by an embodiment of the present application;

[0023] Figure 3 yes Figure 2 A flowchart of a sub-step of step S230 in the computing power engine disaster recovery and energy saving method shown;

[0024] Figure 4 yes Figure 3 A flowchart of a sub-step of step S330 in the computing power engine disaster recovery and energy saving method shown;

[0025] Figure 5 yes Figure 3 Another sub-step flowchart of step S330 in the computing power engine disaster recovery and energy saving method shown;

[0026] Figure 6 yes Figure 3 Another sub-step flowchart of step S330 in the computing power engine disaster recovery and energy saving method shown;

[0027] Figure 7 yes Figure 2 Another sub-step flowchart of step S230 in the computing power engine disaster recovery and energy saving method shown;

[0028] Figure 8 This is a flowchart of deactivating a primary engine node in a computing power engine disaster recovery and energy-saving method provided by an embodiment of the present application;

[0029] Figure 9 This is a flowchart of a computing power engine disaster recovery and energy saving method performed by a backup engine node side, provided by an embodiment of the present application;

[0030] Figure 10 yes Figure 9 A flowchart of a sub-step of step S930 in the computing power engine disaster recovery and energy saving method shown;

[0031] Figure 11 yes Figure 10 A flowchart of a sub-step of step S1030 in the computing power engine disaster recovery and energy saving method shown;

[0032] Figure 12 yes Figure 10 Another sub-step flowchart of step S1030 in the computing power engine disaster recovery and energy saving method shown;

[0033] Figure 13This is a flowchart of a computing power engine disaster recovery and energy saving method provided by an embodiment of the present application in which no load adjustment instruction sent by the active engine node is received;

[0034] Figure 14 yes Figure 9 Another sub-step flowchart of step S930 in the computing power engine disaster recovery and energy saving method shown;

[0035] Figure 15 This is a flowchart of deactivating a primary engine node in a computing power engine disaster recovery and energy-saving method provided by an embodiment of the present application;

[0036] Figure 16 This is a schematic diagram of the energy saving and activation strategy of the service components of the main engine node when the computing power engine node is powered on, provided by an embodiment of the present application;

[0037] Figure 17 This is a flow chart of activating a standby engine node positioning service component to share computing power load, as provided in one embodiment of the present application;

[0038] Figure 18 This is a flow chart of a standby engine node positioning service component entering dormant standby from load sharing, provided by an embodiment of the present application;

[0039] Figure 19 This is a flowchart of deactivating a primary engine node after it returns to normal, provided by an embodiment of the present application;

[0040] Figure 20 This is a schematic diagram of a controller for executing a computing power engine disaster recovery and energy-saving method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0042] It should be noted that although the device schematics illustrate functional module divisions and the flowcharts illustrate logical sequences, in certain circumstances, the steps shown or described may be performed in a sequence that differs from the module divisions in the device or the sequence in the flowcharts. The terms "first," "second," and so on, in the specification, claims, and drawings, are used to distinguish similar items and are not necessarily used to describe a specific sequence or precedence.

[0043] In the embodiments of the present application, words such as "further," "exemplarily," or "optionally" are used to indicate examples, illustrations, or descriptions and should not be interpreted as being more preferred or advantageous over other embodiments or designs. The use of words such as "further," "exemplarily," or "optionally" is intended to present related concepts in a concrete manner.

[0044] In some cases, computing engines are used as products for MEC (Multi-access Edge Computing). Currently, computing engines are being promoted in industrial park scenarios, primarily for applications in mining, ports, steel, airports, and other industrial park services. Industrial park services require high reliability. When a computing engine fails, it is necessary to ensure normal operation of the park service. Therefore, the computing engine must support redundant backups and elastic scalability.

[0045] Among them, the main requirements for disaster recovery deployment of computing power engines include disaster recovery requirements and load sharing requirements. Disaster recovery requirements refer to local disaster recovery and remote disaster recovery. Load sharing requirements refer to the fact that there are multiple 5G (5th Generation Mobile Communication Technology) base stations in the same park. The processing capacity of one computing power engine cannot meet the computing power requirements, and multiple computing power engines are needed to share the business load.

[0046] Currently, disaster recovery for MEC products in the communications and computing sectors primarily utilizes solutions such as port disaster recovery, board disaster recovery, and network element disaster recovery. For the commercially available and widely promoted VGC (Virtual Baseband Processing Board) single-board NE (NodeEngine) in disaster recovery scenarios for positioning or other specialized services, the network element disaster recovery solution is primarily employed. Product analysis reveals that NE network elements consume significant power. Furthermore, the computing power provided by a single NE supports over 5,000 concurrent users of the UTDOA (Uplink Time Difference of Arrival) positioning service, and campus services are relatively simple. However, upon launch of the NE product, all supported service components are online.

[0047] Computing engine disaster recovery deployment usually requires the setup of active and standby engine node devices. In addition to platform components such as TCF (TECS Cloud Foundation) and CONAP (Cloudnative open Network Application Platform), active and standby engine nodes also include dozens of other service components, including positioning services, traffic diversion services, and IP identification services. Service components account for more than 30% of the total. However, since both active and standby engine nodes maintain a hot backup state for all service components, their energy-saving effect is poor.

[0048] Based on the above situation, the embodiments of the present application propose a computing power engine disaster recovery energy-saving method, communication equipment, storage medium and program product, aiming to improve the energy-saving effect of computing power engine nodes.

[0049] The following further describes various embodiments of the computing power engine disaster recovery system of the present application in conjunction with the accompanying drawings.

[0050] like Figure 1 As shown, Figure 1 This is a schematic diagram of the computing power engine disaster recovery system provided in an embodiment of the present application.

[0051] In one embodiment, the computing engine disaster recovery system includes but is not limited to a primary engine node 110 and a backup engine node 120 , wherein the primary engine node 110 and the backup engine node 120 can communicate with each other.

[0052] Among them, the active engine node 110 and the backup engine node 120 can be computing engines independent of the base station, or they can be computing engines built into the base station, namely the base station engine NE, which is designed specifically for 5G private networks and aims to sink edge computing capabilities to the base station to achieve full integration of computing power with the existing network. By adding a new board card to the BBU (Baseband Unit) of the base station, the active NE and the backup NE can provide local diversion services, offloading data to the local server on the base station side, thereby meeting the enterprise's demand for data not leaving the campus, while providing low-latency, high-reliability network services.

[0053] The main features and advantages of NEs are as follows: First, Localized Services: By integrating computing power into base stations, NEs enable local data processing and storage, reducing data transmission paths, lowering latency, and improving data security. Second, Rapid Deployment: Deploying NEs requires no additional hardware; simply adding a card to an existing base station simplifies the deployment process and shortens deployment time. Third, Cost-Effectiveness: Compared to traditional edge computing platforms, NEs offer lower hardware costs and a more streamlined form factor, helping to control overall costs. Fourth, Service Flexibility: NEs support a variety of traffic diversion strategies, such as those based on IP quintuples, DSN domain names, and PLMN IDs, to meet diverse service requirements. Fifth, Quality of Service (QoS) assurance: NEs provide refined QoS guarantees to ensure network performance for critical services. Sixth, Self-Service Portal: NEs offer a visual enterprise self-service portal to facilitate network configuration and management. Seventh, Industry Application Support: NEs are suitable for a variety of industry applications, such as smart manufacturing and smart campuses, and can provide customized network services for these applications.

[0054] Among them, the backup engine node 120 generally refers to a backup base station engine designed in a communication network to ensure high network availability and business continuity. For example, when a major failure occurs in the main engine node 110, the backup engine node 120 can quickly take over the communication service to ensure that critical communications are not interrupted. In addition, the backup engine node 120 can also include additional hardware redundancy, power backup, and synchronization mechanisms with the main base station to ensure that services can be quickly switched and restored in an emergency. Among them, the design and configuration of this engine needs to take into account fast switching and recovery capabilities so that when the main engine node 110 fails, the backup engine node 120 can seamlessly take over the communication task.

[0055] The primary engine node 110 and the backup engine node 120 differ primarily in their application purpose and scenario. The primary engine node 110 primarily provides 5G private network services, emphasizing edge computing capabilities and localized services, while the backup engine node 120 focuses on network reliability and disaster recovery, ensuring rapid communication restoration in the event of a primary network failure. In actual applications, the deployment and configuration of these two engines may vary depending on the network scale, business requirements, and security policies.

[0056] In addition, in one embodiment, the computing power engine disaster recovery system also includes but is not limited to a first base station 210, a second base station 220 and a terminal 300, wherein the first base station 210 communicates with the active engine node 110 and the backup engine node 120 respectively, the second base station 220 communicates with the active engine node 110 and the backup engine node 120 respectively, and the terminal 300 communicates with the first base station 210 and the second base station 220 respectively.

[0057] It should be noted that the terminal 300 may be a mobile terminal device or a communication device module fixed on an industrial product, and the embodiment of the present application does not specifically limit this.

[0058] In addition, in one embodiment, the computing power engine disaster recovery system also includes but is not limited to 5GC (5G Core, 5G core network) 400 and a network side switching device 500, wherein 5GC400 communicates with the first base station 210 and the second base station 220 respectively through the network side switching device 500.

[0059] In addition, in one embodiment, the computing power engine disaster recovery system also includes but is not limited to a campus side switching device 600 and a campus device access terminal 700, wherein the active engine node 110 and the backup engine node 120 communicate with the campus device access terminal 700 through the campus side switching device 600 respectively.

[0060] Based on the implementation scenarios and hardware structures of the computing power engine disaster recovery system of each of the above embodiments, various embodiments of the computing power engine disaster recovery and energy saving method of the present application are proposed below.

[0061] like Figure 2 As shown, Figure 2 This is a flowchart of a computing power engine disaster recovery and energy-saving method performed by the active engine node side provided by an embodiment of the present application; the computing power engine disaster recovery and energy-saving method can be applied to the active engine node of the above embodiment, including but not limited to step S210, step S220 and step S230.

[0062] Step S210: Obtain the node status of the active engine node, the enabled target feature services, and the number of service terminals;

[0063] Step S220: Determine the first target service component in the active engine node according to the target characteristic service;

[0064] Step S230: Control the running status of the first target service component and the second target service component of the standby engine node according to the node status and the number of service terminals, wherein the second target service component corresponds to the target characteristic service.

[0065] In one embodiment, after the active engine node and the standby engine node are powered on, the active engine node first obtains its own node status, the activated target feature services, and the number of service terminals; then, because different feature services use different service components, the active engine node determines its own first target service component based on the target feature service, and the standby engine node also determines its own second target service component based on the target feature service activated by the active engine node; then, the active engine node controls the operating status of the first target service component and the second target service component of the standby engine node based on the node status and the number of service terminals, thereby executing the corresponding energy-saving strategy.

[0066] Among them, the above-mentioned node status may include a normal operating status, a fault status, or other status types, and the embodiments of the present application do not make specific limitations on this.

[0067] In addition, the above-mentioned target feature services may refer to positioning services, Internet of Vehicles services, low-latency video services, IPI services, or other service types. The embodiments of this application do not make specific limitations on this.

[0068] In addition, the above-mentioned number of service terminals refers to the number of terminals corresponding to the target characteristic service. For example, when the target characteristic service is a positioning service, the number of service terminals refers to the number of terminals providing the positioning service.

[0069] Since the embodiment of the present application can control the operating status of the first target service component of the active engine node and the second target service component of the backup engine node according to the node status and the number of service terminals, the embodiment of the present application can trigger the energy-saving strategy of dynamically scheduling the service components of the active engine node and the backup engine node to go online and power off based on the number of service terminal users. The active engine node and the backup engine node can perform load sharing and disaster recovery energy saving according to the characteristic services and the number of concurrent terminal users, thereby reducing the energy consumption of the computing power engine as much as possible.

[0070] In addition, if Figure 3 As shown, Figure 3 yes Figure 2 A sub-step flowchart of step S230 in the computing power engine disaster recovery and energy saving method is shown; regarding the above-mentioned step S230, it includes but is not limited to step S310, step S320 and step S330.

[0071] Step S310: Determine that the node status indicates that the active engine node is in a normal state;

[0072] Step S320: Control the first platform component and the first target service component in the active engine node to remain online, and control the remaining service components in the active engine node to enter a dormant state.

[0073] Step S330: Adjust the operating state of the second target service component according to the number of service terminals and a preset threshold.

[0074] In one embodiment, if the active engine node is in a normal state, the active engine node only needs to control the first platform component and the first target service component corresponding to the target feature service to be online. As for the remaining service components except the first target service component, since the currently executed target feature service only requires the first target service component, the active engine node will control the remaining service components except the first target service component to enter a dormant state. Then, the active engine node will also obtain the number of service terminals in real time, and compare the number of service terminals with a preset threshold to obtain a comparison result, and finally adjust the operating state of the second target service component according to the comparison result.

[0075] The first platform component in the active engine node may include a TCF platform component, a CONAP platform component, or other types of platform components, which are not specifically limited in this embodiment of the present application.

[0076] In addition, for the above-mentioned preset threshold value, its value can be pre-set, and the number of the preset threshold value can be one or more. The embodiment of the present application does not specifically limit the value and number of the preset threshold value.

[0077] In addition, the online state and sleep state mentioned above are two different power management modes. The online state generally refers to a fully started and running state, with all applications and services working normally and users able to perform any operations. The online state does not involve any energy-saving measures and therefore consumes more power. The sleep state is a deep power-saving mode. In this state, since components are turned off, almost no power is consumed.

[0078] It should be noted that, regarding the above step S330, adjusting the operating state of the second target service component according to the number of service terminals and the preset threshold, the following steps may include but are not limited to: Figures 4 to 6 There are three implementation scenarios, as follows:

[0079] like Figure 4 As shown, Figure 4 yes Figure 3A sub-step flowchart of step S330 in the computing power engine disaster recovery and energy saving method is shown; regarding the above-mentioned step S330, it includes but is not limited to step S410 and step S420.

[0080] Step S410: Determine whether the number of service terminals is greater than a first threshold;

[0081] Step S420: Send a load sharing instruction to the standby engine node to switch the second target service component from the dormant state to the online state.

[0082] In one embodiment, if the number of service terminals is greater than the first threshold, it indicates that the current computing power burden of the active engine node is large. Therefore, in order to ensure the quality of service, the active engine node can generate a load sharing instruction and send it to the backup engine node. When the backup engine node receives the load sharing instruction, it will activate the second target service component, so that the second target service component switches from a dormant state to an online state, thereby sharing the computing power load of the target feature service. The active engine node and the backup engine node jointly share the computing power load of the target feature service.

[0083] It can be understood that the above-mentioned first threshold value can be pre-set or determined based on the computing power parameters of the main engine node. For example, the first threshold value can be equal to the maximum computing power parameter of the main engine node, or slightly lower than the maximum computing power parameter of the main engine node, thereby ensuring that the main engine node does not work overloaded.

[0084] like Figure 5 As shown, Figure 5 yes Figure 3 Another sub-step flowchart of step S330 in the computing power engine disaster recovery and energy saving method is shown; regarding the above-mentioned step S330, it includes but is not limited to step S510 and step S520.

[0085] Step S510: Determine whether the number of service terminals is less than a second threshold;

[0086] Step S520: Send a load-sharing removal instruction to the standby engine node to switch the second target service component from an online state to a dormant state, wherein the second threshold value is less than the first threshold value.

[0087] In one embodiment, when the active engine node and the backup engine node jointly share the computing load of the target feature service, the active engine node will also obtain the number of service terminals in real time. If the number of service terminals is less than the second threshold, it indicates that the current computing load of the target feature service is low and can be borne by the active engine node alone. In this regard, in order to improve energy saving, the active engine node will generate a load sharing instruction and send it to the backup engine node. After receiving the load sharing instruction, the backup engine node will release the load sharing of the second target service component and control the second target service component to sleep, thereby reducing the power consumption of the second target service component. At this time, the active engine node alone bears the computing load of the target feature service.

[0088] It can be understood that, regarding the above-mentioned second threshold, its value is smaller than the first threshold, wherein the second threshold may be pre-set, and the embodiment of the present application does not specifically limit the value of the second threshold.

[0089] like Figure 6 As shown, Figure 6 yes Figure 3 Another sub-step flowchart of step S330 in the computing power engine disaster recovery and energy saving method is shown; regarding the above-mentioned step S330, it includes but is not limited to step S610 and step S620.

[0090] Step S610: Determine whether the number of service terminals is greater than or equal to the second threshold or less than or equal to the first threshold;

[0091] Step S620: Keep the second target service component in a dormant state.

[0092] In one embodiment, when the active engine node solely bears the computing power load of the target feature service, if the number of service terminals is between the first threshold value and the second threshold value, it indicates that the current computing power burden of the active engine node is medium and can be borne by the active engine node alone. At this time, the active engine node can generate a load maintenance instruction and send it to the backup engine node. After the backup engine node receives the load maintenance instruction, it will keep the second target service component in a dormant state, and the active engine node will bear the computing power load of the target feature service alone; alternatively, the active engine node may not need to send an instruction to the backup engine node. As long as the backup engine node has not received the load maintenance instruction, the backup engine node will always keep the second target service component in a dormant state, so that the active engine node will always bear the computing power load of the target feature service alone.

[0093] In addition, if Figure 7 As shown, Figure 7 yes Figure 2Another sub-step flowchart of step S230 in the computing power engine disaster recovery and energy saving method shown; regarding the above-mentioned step S230, it includes but is not limited to step S710 and step S720.

[0094] Step S710: Determine that the node status indicates that the active engine node is in a fault state;

[0095] Step S720: Send a fault message to the standby engine node to switch the second target service component from the dormant state to the online state.

[0096] In one embodiment, if the active engine node is in a faulty state, the active engine node cannot continue to guarantee the target feature service. In this case, the active engine node generates a fault message and sends it to the backup engine node. When the backup engine node receives the fault message, it activates the second target service component, so that the second target service component switches from a dormant state to an online state, thereby sharing the computing power load of the target feature service. At this time, the backup engine node bears the computing power load of the target feature service alone.

[0097] In addition, if Figure 8 As shown, Figure 8 This is a flowchart of deactivating the main engine node in the computing power engine disaster recovery and energy saving method provided by an embodiment of the present application; the computing power engine disaster recovery and energy saving method also includes but is not limited to step S810 and step S820.

[0098] Step S810: When the node status returns to normal, a deactivation message sent by the standby engine node is received;

[0099] Step S820: Control all service components in the active engine node to go offline and sleep according to the deactivation message.

[0100] In one embodiment, after the active engine node recovers from a faulty state to a normal state, the backup engine node now solely bears the computing load of the target feature service. Therefore, in order to reduce engine switching operations and alleviate problems caused by engine switching, the backup engine node can send a deactivation message to the active engine node. When the active engine node receives the deactivation message, it will control all service components in the active engine node to hibernate and go offline, thereby achieving energy saving.

[0101] Based on the various embodiments of the computing power engine disaster recovery and energy saving method executed by the active engine node in the above-mentioned embodiments, the various embodiments of the computing power engine disaster recovery and energy saving method executed by the backup engine node in the present application are respectively proposed below.

[0102] like Figure 9 As shown, Figure 9This is a flowchart of a computing power engine disaster recovery and energy-saving method provided by an embodiment of the present application and executed by the backup engine node side; the computing power engine disaster recovery and energy-saving method can be applied to the backup engine node of the above embodiment, including but not limited to step S910, step S920 and step S930.

[0103] Step S910: Obtain the node status of the active engine node and the enabled target feature service;

[0104] Step S920: Determine a second target service component in the standby engine node according to the target characteristic service;

[0105] Step S930: Control the running state of the second target service component according to the node state or the load adjustment instruction sent by the active engine node.

[0106] In one embodiment, after the active engine node and the backup engine node are powered on, first, the active engine node will obtain its own node status, the activated target feature services, and the number of service terminals. In addition, the backup engine node will also obtain the node status and the activated target feature services of the active engine node; then, because different feature services will use different service components, the active engine node will determine its own first target service component based on the target feature service, and the backup engine node will also determine its own second target service component based on the target feature service activated by the active engine node; then, the active engine node will control the operating status of the first target service component and the second target service component of the backup engine node based on the node status and the number of service terminals, thereby executing the corresponding energy-saving strategy.

[0107] It should be noted that since the computing power engine disaster recovery and energy-saving method executed by the backup engine node side in the embodiment of the present application corresponds to the computing power engine disaster recovery and energy-saving method executed by the active engine node side in any of the above-mentioned embodiments, the specific implementation methods and technical effects of the computing power engine disaster recovery and energy-saving method executed by the backup engine node side in the embodiment of the present application can refer to the specific implementation methods and technical effects of the computing power engine disaster recovery and energy-saving method executed by the active engine node side in any of the above-mentioned embodiments.

[0108] In addition, if Figure 10 As shown, Figure 10 yes Figure 9 A sub-step flowchart of step S930 in the computing power engine disaster recovery and energy saving method is shown; regarding the above-mentioned step S930, it includes but is not limited to step S1010, step S1020 and step S1030.

[0109] Step S1010: Determine that the node status indicates that the active engine node is in a normal state;

[0110] Step S1020: Control the second platform component in the standby engine node to remain online, and control all service components in the standby engine node to be in a dormant state;

[0111] Step S1030: Control the running state of the second target service component according to the load adjustment instruction sent by the active engine node.

[0112] In one embodiment, if the active engine node is in a normal state, the active engine node can bear the computing power load of the target feature service alone. Therefore, the backup engine node can control its own second platform component to remain online and control all its own service components to be in a dormant state, thereby improving energy saving effects. Then, the active engine node will also obtain the number of service terminals in real time, and compare the number of service terminals with a preset threshold to obtain a comparison result. Finally, the corresponding load adjustment instruction is sent to the backup engine node based on the comparison result. After receiving the load adjustment instruction, the backup engine node will adjust the operating status of the second target service component.

[0113] It should be noted that, regarding the control of the running state of the second target service component according to the load adjustment instruction sent by the active engine node in step S1030, it may include but is not limited to: Figure 11 or Figure 12 There are two implementation scenarios, as follows:

[0114] like Figure 11 As shown, Figure 11 yes Figure 10 A sub-step flowchart of step S1030 in the computing power engine disaster recovery and energy saving method is shown; regarding the above-mentioned step S1030, it includes but is not limited to step S1110 and step S1120.

[0115] Step S1110: Determine whether the load adjustment instruction is a load sharing instruction;

[0116] Step S1120: Control the second target service component to switch from a dormant state to an online state, wherein the load sharing instruction is generated by the active engine node when the number of service terminals is greater than a first threshold.

[0117] In one embodiment, if the number of service terminals is greater than the first threshold, it indicates that the current computing power burden of the active engine node is large. Therefore, in order to ensure the quality of service, the active engine node can generate a load sharing instruction and send it to the backup engine node. When the backup engine node receives the load sharing instruction, it will activate the second target service component, so that the second target service component switches from a dormant state to an online state, thereby sharing the computing power load of the target feature service. The active engine node and the backup engine node jointly share the computing power load of the target feature service.

[0118] like Figure 12 As shown, Figure 12 yes Figure 10 Another sub-step flowchart of step S1030 in the computing power engine disaster recovery and energy saving method shown; regarding the above-mentioned step S1030, it includes but is not limited to step S1210 and step S1220.

[0119] Step S1210: Determine whether the load adjustment instruction is a load sharing removal instruction;

[0120] Step S1220: Control the second target service component to switch from an online state to a dormant state, wherein the load sharing instruction is generated by the active engine node when the number of service terminals is less than a second threshold.

[0121] In one embodiment, when the active engine node and the backup engine node jointly share the computing load of the target feature service, the active engine node will also obtain the number of service terminals in real time. If the number of service terminals is less than the second threshold, it indicates that the current computing load of the target feature service is low and can be borne by the active engine node alone. In this regard, in order to improve energy saving, the active engine node will generate a load sharing instruction and send it to the backup engine node. After receiving the load sharing instruction, the backup engine node will release the load sharing of the second target service component and control the second target service component to sleep, thereby reducing the power consumption of the second target service component. At this time, the active engine node alone bears the computing load of the target feature service.

[0122] like Figure 13 As shown, Figure 13 This is a flowchart of a computing power engine disaster recovery and energy-saving method provided by an embodiment of the present application in which no load adjustment instruction sent by the main engine node is received; the computing power engine disaster recovery and energy-saving method also includes but is not limited to steps S1310 and S1320.

[0123] Step S1310: Determine that no load adjustment instruction sent by the active engine node is received;

[0124] Step S1320: Keep the second target service component in a dormant state.

[0125] In one embodiment, when the active engine node solely bears the computing power load of the target feature service, if the number of service terminals is between the first threshold value and the second threshold value, it indicates that the current computing power load of the active engine node is medium and can be borne by the active engine node alone. At this time, the active engine node does not need to send instructions to the backup engine node. As long as the backup engine node has not received the load maintenance instruction, the backup engine node will always keep the second target service component in a dormant state, so that the active engine node will always bear the computing power load of the target feature service alone.

[0126] In addition, if Figure 14 As shown, Figure 14 yes Figure 9 Another sub-step flowchart of step S930 in the computing power engine disaster recovery and energy saving method shown; regarding the above-mentioned step S930, it includes but is not limited to step S1410 and step S1420.

[0127] Step S1410: Determine that the node status indicates that the active engine node is in a fault state;

[0128] Step S1420: Control the second platform component and the second target service component in the standby engine node to remain online.

[0129] In one embodiment, if the active engine node is in a faulty state, the active engine node cannot continue to guarantee the target feature service. In this case, the active engine node generates a fault message and sends it to the backup engine node. When the backup engine node receives the fault message, it activates the second target service component, so that the second target service component switches from a dormant state to an online state, thereby sharing the computing power load of the target feature service. At this time, the backup engine node bears the computing power load of the target feature service alone.

[0130] In one embodiment, determining in step S1410 that the node status indicates that the active engine node is in a faulty state may be determined in at least one of the following ways, which are specifically as follows:

[0131] The first way: a fault message is received from the active engine node, and it is determined that the active engine node is in a fault state.

[0132] The second way: if no normal status message is received from the active engine node within a preset time period, it is determined that the active engine node is in a fault state.

[0133] Among them, the above-mentioned preset time length can be pre-set, and the embodiment of the present application does not specifically limit the value of the preset time length.

[0134] In addition, if Figure 15 As shown, Figure 15This is a flowchart of deactivating the main engine node in the computing power engine disaster recovery and energy saving method provided by an embodiment of the present application; after executing the above step S1420, the computing power engine disaster recovery and energy saving method also includes but is not limited to step S1510 and step S1520.

[0135] Step S1510: Determine whether the active engine node has returned to normal;

[0136] Step S1520: Send a deactivation message to the active engine node to put all service components in the active engine node into hibernation and offline.

[0137] In one embodiment, after the active engine node recovers from a faulty state to a normal state, the backup engine node now solely bears the computing load of the target feature service. Therefore, in order to reduce engine switching operations and alleviate problems caused by engine switching, the backup engine node can send a deactivation message to the active engine node. When the active engine node receives the deactivation message, it will control all service components in the active engine node to hibernate and go offline, thereby achieving energy saving.

[0138] Based on the various embodiments of the computing power engine disaster recovery and energy saving method executed by the active engine node or the backup engine node in the above-mentioned embodiments, the overall embodiments of the computing power engine disaster recovery and energy saving method of the present application are proposed below.

[0139] In response to the current status of the above-mentioned NE disaster recovery application scenarios, the embodiment of the present application proposes an energy-saving strategy that triggers dynamic scheduling of the online and offline service components of the disaster recovery NE based on the number of positioning service terminal users. The disaster recovery NE can perform load sharing and disaster recovery energy saving based on the positioning service and the number of concurrent terminal users, thereby reducing the energy consumption of the disaster recovery NE as much as possible.

[0140] When the base station has a built-in computing power engine, the computing power engine in the first base station can be recorded as NE1, that is, NE1 is a regular node; the computing power engine in the second base station can be recorded as NE2, that is, NE2 is a disaster recovery node.

[0141] Scenario 1: NE disaster recovery scenario. The number of concurrent users of positioning service terminals is relatively small. NE1 goes online to provide positioning computing services. Except for the TCF and CONAP platform components and positioning service components, which remain online, other service components of NE1 enter a dormant state and go offline for standby. Meanwhile, NE2 only keeps the TCF, CONAP and other platform components online, while other service components go offline for standby.

[0142] For the above scenario 1, when NE1's computing power meets the business computing power requirements of the park, the energy-saving strategies of other service components of NE1 can be as follows: Figure 16 As shown, Figure 16This is a schematic diagram of the energy saving and activation strategy of the service components of the main engine node when the computing power engine node is powered on, provided by an embodiment of the present application; the process includes but is not limited to the following steps:

[0143] Step S1610: NE1 and NE2 are powered on;

[0144] Step S1621: NE1 node role acquisition;

[0145] Step S1622: NE1 is determined to be the active engine node;

[0146] Step S1623: NE1 node activates service acquisition;

[0147] Step S1624: NE1 node activates the UTDOA positioning service;

[0148] Step S1625: Determine whether the number of UTDOA positioning service terminal users is lower than a first threshold;

[0149] Step S1626: The non-UTDOA location service component of the NE1 node goes offline;

[0150] Step S1631: NE2 node role acquisition;

[0151] Step S1632: Determine NE2 as a standby engine node;

[0152] Step S1633: NE2 node activates service acquisition;

[0153] Step S1634: NE2 synchronizes NE1's feature service data and monitors NE1's status messages in real time.

[0154] Step S1635: NE2 node does not detect NE1's request or abnormal message;

[0155] Step S1636: The non-UTDOA positioning service component of the NE2 node goes offline.

[0156] Specifically, NE1 and NE2 devices are powered on, and the system detects that the activated feature service type is the UTDOA positioning service. The component management module of NE1 takes non-platform components and non-positioning service components offline and puts them on standby according to the activated feature service type; after NE2 is powered on, it acts as a disaster recovery node and puts all service components other than non-platform components into hibernation and standby, while monitoring the status of NE1 in real time.

[0157] Scenario 2: When the number of concurrent users of the positioning service terminal continues to increase and reaches a threshold, the computing power provided by NE1 is about to or has reached the positioning service computing power limit, and NE2 is required to provide computing power load sharing. This triggers the NE2 positioning service component to enter the active state and go online to provide computing power load sharing.

[0158] For the above scenario 2, the energy saving and activation strategy of NE2 service component can be as follows: Figure 17 or Figure 18 The details are as follows:

[0159] like Figure 17 As shown, Figure 17 This is a flow chart of activating a standby engine node location service component to share computing power load, as provided in one embodiment of the present application. The flow includes but is not limited to the following steps:

[0160] Step S1710: NE1 and NE2 operate normally.

[0161] Step S1721: The number of terminal users of NE1's positioning service increases.

[0162] Step S1722: Prediction of the number of concurrent users of the NE1 node positioning service;

[0163] Step S1723: Determine whether the number of users is greater than a first threshold, if not, execute step S1724; if yes, execute step S1725;

[0164] Step S1724: NE1 maintains the computing power acceptance state;

[0165] Step S1725: NE1 sends a load sharing request to NE2.

[0166] Step S1731: The number of terminal users of NE2's positioning service increases.

[0167] Step S1732: NE2 node monitors the positioning service load sharing counter;

[0168] Step S1733: Determine whether a load sharing request is received, if not, execute step S1734; if yes, execute step S1735;

[0169] Step S1734: NE2 keeps each service component in a dormant state.

[0170] Step S1735: NE2 activates the location service component;

[0171] Step S1736: NE2 performs positioning service computing load sharing.

[0172] Step S1737: NE1 performs positioning service computing load sharing.

[0173] like Figure 18 As shown, Figure 18 This is a flow chart of a standby engine node location service component entering dormant standby mode from load balancing, as provided in one embodiment of the present application. The flow includes but is not limited to the following steps:

[0174] Step S1810: NE1 and NE2 operate normally.

[0175] Step S1821: The number of terminal users of NE1's positioning service decreases.

[0176] Step S1822: Predict the number of concurrent users of the NE1 node positioning service;

[0177] Step S1823: Determine whether the number of users is less than a second threshold, if not, execute step S1824; if yes, execute step S1825;

[0178] Step S1824: NE1 maintains the load sharing state.

[0179] Step S1825: NE1 sends a load sharing removal request to NE2.

[0180] Step S1831: The number of terminal users of NE2's positioning service decreases.

[0181] Step S1832: NE2 node monitors the location service load sharing counter;

[0182] Step S1833: Determine whether a load sharing removal request is received, if not, execute step S1834; if yes, execute step S1835;

[0183] Step S1834: NE2 maintains the positioning service load sharing state;

[0184] Step S1835: NE2 releases the location service load sharing and the component goes into hibernation.

[0185] Step S1836: NE1 provides computing power services for all terminals of the positioning service.

[0186] Specifically, first, the nouns are explained as follows:

[0187] PositioningUserNum: the number of real-time online terminal users of UTDOA positioning service;

[0188] maxPositionUserNum: Maximum number of terminal users supported by a single NE for UTDOA positioning services;

[0189] PositionUserNumHighThres: the high threshold of the number of terminal users of the positioning service;

[0190] PositionUserNumLowThres: the low threshold of the number of terminal users of the positioning service;

[0191] In one embodiment, if the maximum number of end-users supported by the UTDOA positioning service of a certain model of NE product for concurrent Periodic positioning is 5000, that is: maxPositionUserNum = 5000; then the first threshold threshold PositionUserNumHighThres = 5000 is set; assuming that the NE disaster recovery network load sharing adopts the load balancing mode, then the second threshold threshold PositionUserNumLowThres = 2500; during device operation, when NE1 detects that the number of end-users of the concurrent positioning service reaches the first threshold threshold, that is: PositioningUserNum ≥ 5000, then NE1 continuously sends a load sharing request to NE2.

[0192] If NE2 detects the load sharing request sent by NE1 within a continuous period of time, such as 5s or 10s, then NE2 sends a status change message to the component management module of NE according to the enabled UTDOA positioning service, and the component management module activates the components related to the UTDOA positioning service to go online, and performs computing power load sharing according to the EDS disaster recovery plan.

[0193] When NE1 detects that the number of online service end-users of UTDOA positioning concurrency drops to reach the second threshold threshold, that is: PositioningUserNum < PositionUserNumLowThres (PositioningUserNum < 2500), then NE1 sends a de-load sharing request to NE2. If NE2 detects the de-load sharing request sent by NE1 within a continuous period of time, such as 10s or 60s, it回迁 the computing power service of the UTDOA positioning service to NE1, and then NE2 transfers the non-platform components and positioning service components to sleep standby.

[0194] Scenario 3: When an unexpected failure occurs to NE1 (such as unexpected power-off, network disconnection, etc.), it triggers NE2 (non-hot standby) to quickly go online the positioning service components and restore the园区 positioning service.

[0195] For Scenario 3, the strategy for NE2 to be activated and provide the computing power requirements of the corresponding feature service when NE1 fails can be as Figure 19 shown Figure 19 is a schematic diagram of the process of de-activating after the primary engine node provided in an embodiment of the present application returns to normal; this process includes but is not limited to the following steps:

[0196] Step S1910, NE1 and NE2 are running normally;

[0197] Step S1921, NE1 fails;

[0198] Step S1922, the status of NE1 returns to normal;

[0199] Step S1931: Each service component of NE2 is saving energy;

[0200] Step S1932: NE2 receives a message indicating that NE1 is faulty, or does not receive a message indicating that NE1 is in a normal state for a period of time.

[0201] Step S1933: NE2 activates and wakes up the location service component;

[0202] Step S1934: NE2 takes over the campus positioning service computing service;

[0203] Step S1935: NE2 continues to send deactivation messages to NE1.

[0204] Step S1936: NE2 maintains the campus positioning service computing service;

[0205] Step S1941: receiving a deactivation message;

[0206] Step S1942: NE1 enters the deactivated state, and all service components go offline.

[0207] Specifically, if NE2 does not detect a normal status message from NE1 for a continuous period of time, for example, 5 seconds, or if NE2 receives a status fault message from NE1 (abnormal power off or link disconnection, etc.), NE2 sends an NE1 status indication message to the component management module. The component management module activates the relevant components of the UTDOA positioning service according to the status indication of NE1, takes over the positioning service data and needs of NE1, and quickly restores the positioning service within the campus. NE2 maintains data synchronization when NE1 is in normal status.

[0208] Based on the computing power engine disaster recovery and energy-saving methods of the above-mentioned embodiments, various embodiments of the controller, communication device, computer-readable storage medium and computer program product of the present application are proposed below.

[0209] like Figure 20 As shown, Figure 20 The controller 800 implemented in this application includes: a processor 810, a memory 820, and a computer program stored in the memory 820 and executable on the processor 810, wherein: Figure 20 In the figure, a processor 810 and a memory 820 are taken as an example.

[0210] The processor 810 and the memory 820 may be connected via a bus or other means. Figure 20 The bus connection is taken as an example.

[0211] The memory 820 is a non-transitory computer-readable storage medium that can be used to store non-transitory software programs and non-transitory computer executable programs. In addition, the memory 820 may include a high-speed random access memory and may also include a non-transitory memory, such as at least one disk storage device, a flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory 820 may optionally include a memory 820 remotely located relative to the processor 810, and these remote memories 820 may be connected to the controller 800 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0212] Those skilled in the art will understand that Figure 20 The device structure shown in the figure does not constitute a limitation on the controller 800, and the controller 800 may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0213] exist Figure 20 In the controller 800 shown, the processor 810 can be used to call the computing power engine disaster recovery and energy saving program stored in the memory 820, thereby implementing the above-mentioned computing power engine disaster recovery and energy saving method. Specifically, the non-transient software program and instructions required to implement the computing power engine disaster recovery and energy saving method of the above-mentioned embodiment are stored in the memory 820. When executed by the processor 810, the computing power engine disaster recovery and energy saving method of the above-mentioned embodiment is executed.

[0214] It is worth noting that since the controller 800 of the embodiment of the present application can execute the computing power engine disaster recovery and energy-saving method of any of the above-mentioned embodiments, the specific implementation methods and technical effects of the controller 800 of the embodiment of the present application can refer to the specific implementation methods and technical effects of the computing power engine disaster recovery and energy-saving method of any of the above-mentioned embodiments.

[0215] In addition, an embodiment of the present application further provides a communication device, which includes the controller of the above embodiment, and the communication device can execute the computing power engine disaster recovery and energy saving method of the above embodiment through the controller, for example, executing the above described Figures 2 to 19 The method steps in .

[0216] It is worth noting that since the communication equipment of the embodiment of the present application includes the controller of the above embodiment, and the controller of the above embodiment can execute the computing power engine disaster recovery and energy-saving method of any of the above embodiments, the specific implementation methods and technical effects of the communication equipment of the embodiment of the present application can refer to the specific implementation methods and technical effects of the computing power engine disaster recovery and energy-saving method of any of the above embodiments.

[0217] It should be noted that the communication device can be a primary engine node or a backup engine node. When the communication device is a primary engine node, the above-described Figures 2 to 8 When the communication device is a standby engine node, the above-described Figures 9 to 15 The method steps in .

[0218] In addition, an embodiment of the present application further provides a computer-readable storage medium, which stores computer-executable instructions, and the computer-executable instructions are used to execute the above-described robot control method. Figures 2 to 19 The method steps in .

[0219] It is worth noting that since the computer-readable storage medium of the embodiment of the present application can execute the computing power engine disaster recovery and energy-saving method of any of the above-mentioned embodiments, the specific implementation methods and technical effects of the computer-readable storage medium of the embodiment of the present application can refer to the specific implementation methods and technical effects of the computing power engine disaster recovery and energy-saving method of any of the above-mentioned embodiments.

[0220] In addition, an embodiment of the present application further provides a computer program product, including a computer program or computer instructions, the computer program or computer instructions are stored in a computer-readable storage medium, the processor of the computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the computer device executes the above-mentioned computing power engine disaster recovery and energy saving method. For example, the above-described Figures 2 to 19 The method steps in .

[0221] It is worth noting that since the computer program product of the embodiment of the present application can execute the computing power engine disaster recovery and energy-saving method of any of the above-mentioned embodiments, the specific implementation methods and technical effects of the computer program product of the embodiment of the present application can refer to the specific implementation methods and technical effects of the computing power engine disaster recovery and energy-saving method of any of the above-mentioned embodiments.

[0222] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0223] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above implementation mode. Technical personnel familiar with the art can also make various equivalent modifications or substitutions under the shared conditions that do not violate the spirit of the present application. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present application.

Claims

1. A computing power engine disaster recovery and energy saving method, characterized in that: Applied to the active engine node, the method includes: Obtain the node status of the active engine node, the enabled target feature services, and the number of service terminals; Determining a first target service component in the active engine node according to the target characteristic service; The operating states of the first target service component and the second target service component of the standby engine node are controlled according to the node state and the number of service terminals, wherein the second target service component corresponds to the target characteristic service.

2. The method according to claim 1, characterized in that The controlling the operating status of the first target service component and the second target service component of the standby engine node according to the node status and the number of service terminals includes: Determining that the node status indicates that the active engine node is in a normal state; controlling the first platform component and the first target service component in the active engine node to remain online, and controlling the remaining service components in the active engine node to enter a dormant state; The operating state of the second target service component is adjusted according to the number of service terminals and a preset threshold.

3. The method according to claim 2, characterized in that The adjusting the operating state of the second target service component according to the number of service terminals and a preset threshold value includes: When the number of the service terminals is greater than a first threshold, a load sharing instruction is sent to the standby engine node to switch the second target service component from a dormant state to an online state.

4. The method according to claim 3, characterized in that The step of adjusting the operating state of the second target service component according to the number of service terminals and a preset threshold value further includes: When the number of service terminals is less than a second threshold, a load sharing instruction is sent to the standby engine node to switch the second target service component from an online state to a dormant state, wherein the second threshold is less than the first threshold.

5. The method according to claim 4, characterized in that The step of adjusting the operating state of the second target service component according to the number of service terminals and a preset threshold value further includes: When the number of the service terminals is greater than or equal to the second threshold or less than or equal to the first threshold, the second target service component is kept in a dormant state.

6. The method according to claim 1, characterized in that The controlling the operating status of the first target service component and the second target service component of the standby engine node according to the node status and the number of service terminals includes: Determining that the node status indicates that the active engine node is in a fault state; A fault message is sent to the standby engine node to switch the second target service component from a dormant state to an online state.

7. The method according to claim 6, characterized in that The method further comprises: When the node status returns to normal, receiving a deactivation message sent by the standby engine node; All service components in the active engine node are controlled to go offline and sleep according to the deactivation message.

8. A computing power engine disaster recovery and energy saving method, characterized in that: Applied to a standby engine node, the method includes: Obtain the node status of the active engine node and the target feature services enabled; determining a second target service component in the standby engine node according to the target characteristic service; The running state of the second target service component is controlled according to the node state or the load adjustment instruction sent by the active engine node.

9. The method according to claim 8, characterized in that The controlling the running state of the second target service component according to the node state or the load adjustment instruction sent by the active engine node includes: Determining that the node status indicates that the active engine node is in a normal state; Controlling the second platform component in the standby engine node to remain online, and controlling all service components in the standby engine node to be in a dormant state; The running state of the second target service component is controlled according to the load adjustment instruction sent by the active engine node.

10. The method according to claim 9, characterized in that The controlling the operating state of the second target service component according to the load adjustment instruction sent by the active engine node includes: When the load adjustment instruction is a load sharing instruction, the second target service component is controlled to switch from a dormant state to an online state, wherein the load sharing instruction is generated by the active engine node when the number of service terminals is greater than a first threshold.

11. The method according to claim 10, characterized in that The controlling the running state of the second target service component according to the load adjustment instruction sent by the active engine node further includes: When the load adjustment instruction is a load-sharing instruction, the second target service component is controlled to switch from an online state to a dormant state, wherein the load-sharing instruction is generated by the active engine node when the number of service terminals is less than a second threshold.

12. The method according to claim 9, characterized in that After controlling all service components in the standby engine node to be in a dormant state, the method further includes: In the case of not receiving the load adjustment instruction sent by the active engine node, keeping the second target service component in a dormant state.

13. The method according to claim 8, characterized in that The controlling the running state of the second target service component according to the node state or the load adjustment instruction sent by the active engine node includes: Determining that the node status indicates that the active engine node is in a fault state; The second platform component and the second target service component in the standby engine node are controlled to remain online.

14. The method according to claim 13, characterized in that Determining that the node status indicates that the active engine node is in a fault state includes one of the following: receiving a fault message from the active engine node and determining that the active engine node is in a fault state; If no normal status message is received from the active engine node within a preset time period, it is determined that the active engine node is in a fault state.

15. The method according to claim 13, characterized in that After controlling the second platform component and the second target service component in the standby engine node to remain online, the method further includes: When it is determined that the active engine node has recovered to normal, a deactivation message is sent to the active engine node to put all service components in the active engine node into hibernation and offline.

16. A communication device, characterized in that: include: at least one processor; at least one memory for storing at least one program; When at least one of the programs is executed by at least one of the processors, the computing power engine disaster recovery and energy saving method as described in any one of claims 1 to 7, or the computing power engine disaster recovery and energy saving method as described in any one of claims 8 to 15.

17. A computer-readable storage medium, characterized in that A processor-executable program is stored therein, and when the processor-executable program is run by the processor, the computing power engine disaster recovery and energy-saving method as described in any one of claims 1 to 7, or the computing power engine disaster recovery and energy-saving method as described in any one of claims 8 to 15 is executed.

18. A computer program product comprising a computer program or computer instructions, characterized in that The computer program or the computer instruction is stored in a computer-readable storage medium, the processor of the computer device reads the computer program or the computer instruction from the computer-readable storage medium, and the processor executes the computer program or the computer instruction, so that the computer device executes the computing power engine disaster recovery and energy-saving method as described in any one of claims 1 to 7, or the computing power engine disaster recovery and energy-saving method as described in any one of claims 8 to 15.

Images