System node management method and device, electronic equipment and storage medium

Abstract

The invention discloses a system node management method and device, electronic equipment and a storage medium, and the method comprises the steps: determining a system mode in SSM system state management, the SSM system state management comprises an SSM system state management Master and an SSM system state management Agent, the SSM system state management Master is used for determining node function change and control mode change, and the SSM system state management Agent is used for determining the SSM system state management Agent; the SSM system state management Agent is decoupled from a service and judges whether a node list is consistent or not; and changing the mode according to the switching condition of the system mode so as to manage the system node. According to the invention, dynamic management is realized. On one hand, mode switching is carried out according to different service requirements, and on the other hand, starting operation of different functions of the system is achieved by defining modes.

Description

Technical Field

[0001] The present application relates to the field of intelligent connected vehicle technology, and in particular to a system node management method, device, electronic device, and storage medium. Background Art

[0002] With the development of intelligent connected vehicles, more and more intelligent connected vehicles use multi-domain controllers to support high-computing self-driving capability calculations. Therefore, in the overall autonomous driving system, it is necessary to manage the multi-domain controllers, the start and stop of nodes in the entire system, and the survival status of nodes. In addition, for different services, it is even necessary to switch or change the list of started nodes.

[0003] In the existing solution, each domain controller configures the startup items separately, fixes the startup list, and then judges the startup results of the overall system nodes. In this way, if different functions need to be matched, the startup items need to be changed, and the versions need to be updated and packaged again, which greatly increases the maintenance investment and update cycle of smart connected vehicles. Summary of the invention

[0004] The embodiments of the present application provide a system node management method, device, electronic device, and storage medium to achieve dynamic management, switch modes according to different business needs, and start and run different functions of the system by defining modes.

[0005] The present application embodiment adopts the following technical solutions:

[0006] In a first aspect, an embodiment of the present application provides a system node management method, wherein the method includes:

[0007] Determine the system mode in the SSM system status management, the SSM system status management includes the SSM system status management Master and the SSM system status management Agent, the SSM system status management Master is used to determine the node function change and the control mode change, the SSM system status management Agent is decoupled from the business and determines whether the node list is consistent;

[0008] The system mode is changed according to the switching condition of the system mode to manage the system nodes.

[0009] In some embodiments, the method further comprises:

[0010] According to actual business needs, the definition of the system mode is increased to obtain a new system mode;

[0011] The mode is changed according to the newly added system mode to realize the startup change of the functional node.

[0012] In some embodiments, determining the system mode in the SSM system state management includes:

[0013] Determine that the system mode includes at least one of the following: low power consumption IDLE mode, running RUN mode, and stopping OTA mode;

[0014] According to the system mode, determine the list of nodes that need to exist;

[0015] If the actual node list is consistent with the node list that needs to exist, it is determined that the system mode is in a ready state.

[0016] In some embodiments, the SSM system status management Master is also used to

[0017] A list of nodes that need to exist in each SSM system state management Agent is generated according to the system mode and sent to the corresponding SSM system state management Agent.

[0018] In some embodiments, the SSM system status management Agent is also used to

[0019] Make the currently existing node list consistent with the node list that needs to exist.

[0020] In some embodiments, the system mode includes a state machine, and the mode change is performed according to the switching condition of the system mode to manage the system node, including:

[0021] According to the change conditions of the system mode, the state machine is switched;

[0022] According to the switching result of the system mode, the node list that needs to exist of each SSM system status management agent is regenerated.

[0023] In some embodiments, the performing of mode change according to the switching condition of the system mode to manage the system node further includes:

[0024] When each SSM system state management agent has a normal heartbeat, and the list of surviving nodes sent through the heartbeat is consistent with the requirements of the system mode, the system mode is in the ready state;

[0025] When the surviving node list reported by each SSM system status management agent is inconsistent with the required surviving node list for a long time and a timeout event occurs, the system mode is not in the ready state, and the reason for failure to be ready is reported to the display end.

[0026] In a second aspect, an embodiment of the present application further provides a system node management device, wherein the device includes:

[0027] A system mode determination module is used to determine the system mode in the SSM system state management. The SSM system state management includes the SSM system state management Master and the SSM system state management Agent. The SSM system state management Master is used to determine the node function change and the control mode change. The SSM system state management Agent is decoupled from the business and determines whether the node list is consistent.

[0028] The mode changing module is used to change the mode according to the switching condition of the system mode to manage the system nodes.

[0029] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor; and a memory arranged to store computer executable instructions, wherein the executable instructions, when executed, cause the processor to perform the above method.

[0030] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores one or more programs. When the one or more programs are executed by an electronic device including multiple application programs, the electronic device executes the above method.

[0031] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: determine the system mode in the SSM system status management, the SSM system status management includes the SSM system status management Master and the SSM system status management Agent, the SSM system status management Master is used to determine the node function changes and control mode changes, the SSM system status management Agent is decoupled from the business and determines whether the node list is consistent. Then, according to the switching conditions of the system mode, the mode is changed to manage the system nodes. The above method is applied to intelligent connected vehicles, mode switching is performed according to different business needs, and the startup and operation of different system functions are achieved by defining the mode. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0033] Figure 1 A schematic diagram of the implementation architecture of the system node management method in the embodiment of the present application;

[0034] Figure 2 A schematic diagram of a process flow of a system node management method in an embodiment of the present application;

[0035] Figure 3 This is a schematic diagram of a system mode state machine in an embodiment of the present application;

[0036] Figure 4 This is a flow chart of system mode conversion in the embodiment of this application;

[0037] Figure 5 This is a schematic diagram of the structure of a system node management device in an embodiment of the present application;

[0038] Figure 6 This is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0040] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0041] The present application embodiment provides a system node management method, such as Figure 2 As shown, a schematic diagram of the system node management method in an embodiment of the present application is provided, and the method at least includes the following steps S210 to S220:

[0042] SSM (system status management) system status management.

[0043] Step S210, determine the system mode in the SSM system status management, the SSM system status management includes the SSM system status management Master and the SSM system status management Agent, the SSM system status management Master is used to determine the node function changes and control mode changes, the SSM system status management Agent is decoupled from the business and determines whether the node list is consistent.

[0044] In a domain controller, each version usually has a fixed startup configuration. Different iterations will be generated for different functional iterations. When the version function is determined, the functional nodes that need to be started are defined. In the existing solution, the startup node content is customized according to the required functional items, and the version is generated and packaged. New functions require new version iterations or version switching. In this application, SSM system status management is adopted, and the startup and operation of different system functions are realized by determining the system mode in the SSM system status management.

[0045] like Figure 1As shown, the system node management method in the present application adopts a distributed architecture, and the SSM system status management is divided into two parts: Master and Agent, and the Master and Agent use python's flask to communicate. The system node management method in the present application proposes a management method for system mode control. The system mode is a state machine, and the status information that can be included includes but is not limited to the Agent list, the list of surviving nodes, the status of software and hardware, etc. The SSM Master receives the current list of nodes and node status through the heartbeat protocol. The SSM Master also sends the list of nodes that need to exist to the SSM Agent. It can be understood that the SSM Agent includes multiple, SSM Agent1, SSM Agent2, and SSM AgentX to form a distributed domain controller combination system.

[0046] It can be understood that the function of the SSM system status management Master is mainly used to determine the node function change and control mode change. Specifically, the SSM system status management Master generates a node list that needs to exist in each agent according to the system mode and sends it to the SSM Agent.

[0047] It can be understood that the SSM system status management agent is decoupled from the business and determines whether the node list is consistent. Specifically, the SSM system status management agent is responsible for making the node list currently existing in the local machine or container consistent with the node list that needs to exist.

[0048] Step S220: changing the mode according to the switching condition of the system mode to manage the system nodes.

[0049] Determine whether to change the mode based on the switching conditions of the system mode. For example, the mode change will be made only when the switching conditions are met, otherwise the mode change will not be made. The management of system nodes is achieved through mode changes. For example, the switching conditions can be determined by autonomous driving instructions or OTA upgrade instructions.

[0050] In the prior art, the startup script is implemented through a shell script. The node startup of each vehicle model is started through a docker container. The container starts and runs the shell. Switching different functional nodes requires sending a custom signal to the shell, which is not flexible enough and has poor scalability.

[0051] The system node management method in the embodiment of the present application is centered on the system mode. Different modes determine different lists of nodes that need to survive, and different node startups determine whether the functions are ready. Through simple and limited mode switching, complex multi-node coordination function changes can be achieved.

[0052] Through the above method, different system modes determine different lists of nodes that need to survive, and different node startups determine whether the function is ready. Through simple and limited mode switching, complex multi-node coordination function changes can be achieved. Different from the traditional node configuration that can only be fixed, it can effectively reduce maintenance success and improve the scalability and flexibility of the overall system.

[0053] Through the above method, the use of the SSM system state management Master and the SSM system state management Agent has better scalability. It also supports multiple distributed domain controllers and multiple container management. Through the Agent quantity management and the current node survival management, the overall system state management goal can be achieved.

[0054] Different from related technologies, each version needs to be managed separately, and switching nodes with conflicting functions requires a lot of development. If dual-track format support is implemented, two new nodes need to be dynamically started, which leads to long development cycles and high maintenance iteration costs. The above method can effectively reduce maintenance costs and improve the scalability and flexibility of the overall system.

[0055] Different from the related technologies, it is difficult to detect whether the node has been started and whether it has been started, and the nodes need to be compared one by one, which leads to poor monitoring effect of the nodes. Through the above method, the maintainability, scalability and visualization of the system node management are improved, and at the same time, it is ensured that the functional nodes can be dynamically managed and pulled up.

[0056] Different from the related technologies, if you want to add a new low-power mode or add a new OTA upgrade, it is not easy to support business needs and has poor scalability. The above method has better scalability, supports multiple distributed domain controllers, supports the management of multiple containers, and can achieve the overall system status management goal through Agent quantity management and current node survival management.

[0057] In one embodiment of the present application, the method further includes: according to actual business needs, adding the definition of the system mode to obtain a new system mode; performing a mode change according to the new system mode to implement a startup change of a functional node.

[0058] Based on actual product / business requirements, the definition of system mode is increased, and the startup change of functional nodes is achieved through mode control. The system using the SSM system state management Master and the SSM system state management Agent has better scalability, supports multiple distributed domain controllers, supports the management of multiple containers, and can achieve the overall system state management goal through Agent quantity management and current node survival management.

[0059] In one embodiment of the present application, determining the system mode in the SSM system status management includes: the system mode includes at least one of the following: low-power IDLE mode, running RUN mode, and stopping OTA mode; according to the system mode, determining a list of nodes that need to exist; if the actual node list is consistent with the list of nodes that need to exist, determining that the system mode is in a ready state.

[0060] like Figure 3 As shown, the system mode state machine includes: low power IDLE mode, RUN mode and OTA stop mode. Low power IDLE mode refers to the low power mode of the domain controller, RUN mode refers to the working mode of the domain controller, and OTA stop mode refers to the remote upgrade mode of the domain controller.

[0061] It should be noted that when defining the current system mode, in order to reduce complexity, the system state machine only includes the state (system mode) that the system is expected to be in, and does not include the actual state of the current system.

[0062] Please continue to refer to Figure 2 If the system mode is defined, the node list that needs to exist is implicitly determined. When the actual node list and the node list that needs to exist are completely consistent, the system mode is considered ready.

[0063] Please continue to refer to Figure 2 ,You can also further improve the granularity and breadth of system management by expanding the list and increasing the collection of overall hardware status and software status, making it easier to globally identify the availability of related functions.

[0064] In one embodiment of the present application, the SSM system status management Master is further used to generate a node list that needs to exist in each SSM system status management Agent according to the system mode and send it to the corresponding SSM system status management Agent.

[0065] The SSM system status management Master generates a list of nodes that need to exist in each Agent according to the system mode and sends it to the Agent. The SSM system status management Master decides on function changes and changes the overall control mode.

[0066] In one embodiment of the present application, the SSM system status management Agent is also used to make the currently existing node list consistent with the node list that needs to exist.

[0067] The SSM system status management agent is responsible for making the node list currently existing in the local machine (this container) consistent with the node list that needs to exist. The SSM system status management agent is decoupled from the business and only focuses on whether the node list is consistent.

[0068] In one embodiment of the present application, the system mode includes a state machine, and the mode change is performed according to the switching conditions of the system mode to manage the system nodes, including: switching the state machine according to the change conditions of the system mode; and regenerating the list of nodes that need to exist for each SSM system status management Agent according to the switching results of the system mode.

[0069] It can be understood that the conditions for changing the system mode mainly come from network messages from external systems, mainly from messages transmitted by the autonomous driving middleware ros or ros2.

[0070] like Figure 4 As shown, the old system mode can be implemented by changing the system mode or the system configuration, and changing the target node list to perform the system mode change event.

[0071] The system mode change event can be divided into system mode / configuration changed again, system mode requirements are met, and timeout through ready=no / first_ready=no / timeout=no.

[0072] (1) System mode / configuration is changed again - Change abort event - New system mode. (2) All conditions required by the system mode are met - Change success event - ready = yes / first_ready = yes / timeout =? - System mode ready event. If an exception occurs, system mode unready event - ready = no / first_ready = yes / timeout =? - New system mode.

[0073] (3) Timeout - Change timeout event - ready = no / first_ready = no / timeout = yes - new system mode.

[0074] like Figure 4 As shown, the switching conditions of the system mode are defined, and the mode is changed when the conditions are triggered. The SSM system state management Master receives the change conditions of the system mode, switches the state machine, and regenerates the node list that needs to exist for each Agent according to the system mode switch.

[0075] In one embodiment of the present application, the mode change is performed according to the switching conditions of the system mode to manage the system nodes, and also includes: when each SSM system status management Agent has a normal heartbeat, and the list of surviving nodes sent through the heartbeat is consistent with the requirements of the system mode, the system mode is in a ready state; when the surviving node list reported by each SSM system status management Agent is inconsistent with the required surviving list for a long time and a timeout event occurs, the system mode is not in a ready state, and the reason for failure to be ready is reported to the display end.

[0076] like Figure 4 As shown in the figure, when each Agent has a normal heartbeat and the list of surviving nodes sent through the heartbeat is consistent with the requirements of the system mode, the system mode is in the ready state.

[0077] When the list of surviving nodes reported by the Agent is inconsistent with the list of nodes that need to be surviving for a long time, a timeout event occurs. At this time, it is considered that the mode is not ready, and the SSM system status management needs to report the reason for failure to be ready to the display end.

[0078] It can be understood that the display end may be a device or a carrier with a display function, which is not specifically limited in the embodiments of the present application.

[0079] The present application embodiment also provides a system node management device 500, such as Figure 5 As shown, a schematic diagram of the structure of a system node management device in an embodiment of the present application is provided, wherein the system node management device 500 at least includes: a system mode determination module 510, a mode change module 520, wherein:

[0080] In one embodiment of the present application, the system mode determination module 510 is specifically used to: determine the system mode in the SSM system status management, the SSM system status management includes the SSM system status management Master and the SSM system status management Agent, the SSM system status management Master is used to determine node function changes and control mode changes, the SSM system status management Agent is decoupled from the business and determines whether the node list is consistent.

[0081] In a domain controller, each version usually has a fixed startup configuration. Different iterations will be generated for different functional iterations. When the version function is determined, the functional nodes that need to be started are defined. In the existing solution, the startup node content is customized according to the required functional items, and the version is generated and packaged. New functions require new version iterations or version switching. In this application, SSM system status management is adopted, and the startup and operation of different system functions are realized by determining the system mode in the SSM system status management.

[0082] like Figure 1 As shown, the system node management method in the present application adopts a distributed architecture, and the SSM system status management is divided into two parts: Master and Agent, and the Master and Agent use python's flask to communicate. The system node management method in the present application proposes a management method for system mode control. The system mode is a state machine, and the status information that can be included includes but is not limited to the Agent list, the list of surviving nodes, the status of software and hardware, etc. The SSM Master receives the current list of nodes and node status through the heartbeat protocol. The SSM Master also sends the list of nodes that need to exist to the SSM Agent. It can be understood that the SSM Agent includes multiple, SSM Agent1, SSM Agent2, and SSM AgentX to form a distributed domain controller combination system.

[0083] It can be understood that the function of the SSM system status management Master is mainly used to determine the node function change and control mode change. Specifically, the SSM system status management Master generates a node list that needs to exist in each agent according to the system mode and sends it to the SSM Agent.

[0084] It can be understood that the SSM system status management agent is decoupled from the business and determines whether the node list is consistent. Specifically, the SSM system status management agent is responsible for making the node list currently existing in the local machine or container consistent with the node list that needs to exist.

[0085] In one embodiment of the present application, the mode changing module 520 is specifically used to: perform mode change according to the switching condition of the system mode to manage the system nodes.

[0086] The switching conditions of the system mode are used to determine whether to change the mode. For example, the mode change will be made only when the switching conditions are met, and the mode change will not be made if the conditions are not met. The management of system nodes is achieved through mode changes.

[0087] In the prior art, the startup script is implemented through a shell script. The node startup of each vehicle model is started through a docker container. The container starts and runs the shell. Switching different functional nodes requires sending a custom signal to the shell, which is not flexible enough and has poor scalability.

[0088] The system node management method in the embodiment of the present application is centered on the system mode. Different modes determine different lists of nodes that need to survive, and different node startups determine whether the functions are ready. Through simple and limited mode switching, complex multi-node coordination function changes can be achieved.

[0089] In one embodiment of the present application, it further includes: a demand change module for

[0090] According to actual business needs, the definition of the system mode is increased to obtain a new system mode;

[0091] The mode is changed according to the newly added system mode to realize the startup change of the functional node.

[0092] In one embodiment of the present application, the system mode determination module 510 is further used to

[0093] The system mode includes at least one of the following: low power consumption IDLE mode, running RUN mode, and stopping OTA mode;

[0094] According to the system mode, determine the list of nodes that need to exist;

[0095] If the actual node list is consistent with the node list that needs to exist, it is determined that the system mode is in a ready state.

[0096] In one embodiment of the present application, the system mode determination module 510 is further used to

[0097] A list of nodes that need to exist in each SSM system state management Agent is generated according to the system mode and sent to the corresponding SSM system state management Agent.

[0098] In one embodiment of the present application, the system mode determination module 510 is further used to

[0099] Make the currently existing node list consistent with the node list that needs to exist.

[0100] In one embodiment of the present application, the mode change module 520 is also used to

[0101] According to the change conditions of the system mode, the state machine is switched;

[0102] According to the switching result of the system mode, the node list that needs to exist of each SSM system status management agent is regenerated.

[0103] In one embodiment of the present application, the mode change module 520 is also used to

[0104] When each SSM system state management agent has a normal heartbeat, and the list of surviving nodes sent through the heartbeat is consistent with the requirements of the system mode, the system mode is in the ready state;

[0105] When the surviving node list reported by each SSM system status management agent is inconsistent with the required surviving node list for a long time and a timeout event occurs, the system mode is not in the ready state, and the reason for failure to be ready is reported to the display end.

[0106] It can be understood that the above-mentioned system node management device can implement each step of the system node management method provided in the above-mentioned embodiment, and the relevant explanations about the system node management method are applicable to the system node management device, which will not be repeated here.

[0107] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 6 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0108] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0109] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0110] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a system node management device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0111] Determine the system mode in the SSM system status management, the SSM system status management includes the SSM system status management Master and the SSM system status management Agent, the SSM system status management Master is used to determine the node function change and the control mode change, the SSM system status management Agent is decoupled from the business and determines whether the node list is consistent;

[0112] The system mode is changed according to the switching condition of the system mode to manage the system nodes.

[0113] The above application Figure 2 The method performed by the system node management device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in software form. The above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in a decoding processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0114] The electronic device may also perform Figure 2 The method executed by the system node management device in Figure 2 The functions of the illustrated embodiment will not be described in detail in the embodiments of the present application.

[0115] The present application also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute Figure 2 The method executed by the system node management device in the illustrated embodiment is specifically used to execute:

[0116] Determine the system mode in the SSM system status management, the SSM system status management includes the SSM system status management Master and the SSM system status management Agent, the SSM system status management Master is used to determine the node function change and the control mode change, the SSM system status management Agent is decoupled from the business and determines whether the node list is consistent;

[0117] The system mode is changed according to the switching condition of the system mode to manage the system nodes.

[0118] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0119] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0120] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0121] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0122] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0123] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0124] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0125] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0126] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0127] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A system node management method, wherein: The method comprises: Determine the system mode in the SSM system status management, the SSM system status management includes the SSM system status management Master and the SSM system status management Agent, the SSM system status management Master is used to determine the node function change and the control mode change, the SSM system status management Agent is decoupled from the business and determines whether the node list is consistent; The mode is changed according to the switching condition of the system mode to manage the system nodes.

2. The method of claim 1, wherein: The method further comprises: According to actual business needs, the definition of the system mode is increased to obtain a new system mode; The mode is changed according to the newly added system mode to realize the startup change of the functional node.

3. The method of claim 1, wherein: Determining the system mode in the SSM system state management includes: The system mode includes at least one of the following: low power consumption IDLE mode, running RUN mode, and stopping OTA mode; According to the system mode, determine the list of nodes that need to exist; If the actual node list is consistent with the node list that needs to exist, it is determined that the system mode is in a ready state.

4. The method of claim 3, wherein: The SSM system status management Master is also used A list of nodes that need to exist in each SSM system state management Agent is generated according to the system mode and sent to the corresponding SSM system state management Agent.

5. The method of claim 3, wherein: The SSM system status management agent is also used to Make the currently existing node list consistent with the node list that needs to exist.

6. The method of claim 1, wherein: The system mode includes a state machine, and the mode change is performed according to the switching condition of the system mode to manage the system node, including: According to the change conditions of the system mode, the state machine is switched; According to the switching result of the system mode, the node list that needs to exist of each SSM system status management agent is regenerated.

7. The method of claim 1, wherein: The method of performing a mode change according to the switching condition of the system mode to manage the system node also includes: When each SSM system state management agent has a normal heartbeat, and the list of surviving nodes sent through the heartbeat is consistent with the requirements of the system mode, the system mode is in the ready state; When the surviving node list reported by each SSM system status management agent is inconsistent with the required surviving node list for a long time and a timeout event occurs, the system mode is not in the ready state, and the reason for failure to be ready is reported to the display end.

8. A system node management device, wherein: The device comprises: A system mode determination module is used to determine the system mode in the SSM system state management. The SSM system state management includes the SSM system state management Master and the SSM system state management Agent. The SSM system state management Master is used to determine the node function change and the control mode change. The SSM system state management Agent is decoupled from the business and determines whether the node list is consistent. The mode changing module is used to change the mode according to the switching condition of the system mode to manage the system nodes.

9. An electronic device, comprising: processor; as well as A memory arranged to store computer executable instructions, which when executed cause the processor to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of application programs, causes the electronic device to execute any one of the methods of claims 1 to 7.

Images