System status management method, device, equipment and medium
By defining process combinations and executing the control of the management module in the state management module, the unified state management of the autonomous driving middleware system is realized, solving the problem of increased logic modification caused by the differences in software architecture of different suppliers, and improving system stability and functions Achieve efficiency.
Patent Information
- Application Number
- CN202410995668.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-24
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2044-07-24
AI Technical Summary
In the autonomous driving middleware system, the software architectures of different suppliers are different, resulting in the need to change the management logic when managing the system state, which increases the probability of modification work and errors.
By defining different system states and corresponding process combinations in the state management module, the execution management module controls the start and stop of the process combination to achieve unified state management without changing the logic of the respective execution management module.
It reduces logic modification work, improves system stability and functional implementation speed, and avoids errors caused by logic differences.
Smart Images

Figure CN118519754B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a system status management method, device, equipment and medium. Background Art
[0002] According to the standard requirements of AUTOSAR AP (AUTOSAR Adaptive Platform, automotive software open system architecture adaptive platform), it is necessary to implement state management, execution management and health management in the autonomous driving middleware system. For these management modules, different suppliers have their own solutions, and different suppliers use their own solutions for management.
[0003] The software architectures provided by different suppliers are different. When implementing system status management of software architectures provided by multiple suppliers, it is often necessary to change their respective management logic, which greatly increases the modification work and the probability of error. Therefore, a system status management method is urgently needed to solve the above problems. Summary of the invention
[0004] In view of this, the purpose of the present invention is to provide a system status management method, device, equipment and medium, which can achieve unified status management and reduce logic modification work. The specific scheme is as follows:
[0005] In a first aspect, the present application discloses a system state management method, which is applied to a state management module, wherein the state management module is used to manage multiple states of the system, and the method comprises:
[0006] When receiving a state switching instruction for switching a first state to a second state, determining a first process combination corresponding to the first state and a second process combination corresponding to the second state;
[0007] Sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination;
[0008] After receiving the message that the process stop is completed returned by the first execution management module, a process start instruction is sent to the second execution management module in the second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination.
[0009] Optionally, sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination includes:
[0010] Determining the interdependence of the processes in the first process combination, so as to divide the processes in the first process combination into a plurality of first processes and a plurality of second processes; wherein the stopping of any second process depends on the stopping of a plurality of first processes;
[0011] Sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop the plurality of first processes, and after stopping each of the plurality of first processes, adding one to a target count value;
[0012] Determine whether the current target count value meets a first threshold value. If so, send a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop any second process, so as to stop each process in the first process combination.
[0013] Optionally, the first software architecture further includes a first health management module, and the second software architecture further includes a second health management module;
[0014] Accordingly, the system status management method further includes:
[0015] The first health information reported by the first health management module is obtained, and the second health information reported by the second health management module is obtained, and then it is determined whether to switch the current state in the state management module according to the first health information and the second health information.
[0016] Optionally, the determining whether to switch the current state in the state management module according to the first health information and the second health information includes:
[0017] If the first health information and the second health information are reported according to a preset reporting method, there is no need to switch the current state in the state management module;
[0018] If the first health information and the second health information are not reported according to the preset reporting method, switching the current state in the state management module;
[0019] The pre-set reporting method includes any one or a combination of scheduled reporting, expiration reporting or logical reporting.
[0020] Optionally, the first process management module and the second process management module respectively establish connections with a target shared memory gateway, so that each process in the first software architecture and each process in the second software architecture can communicate with each other through the target shared memory gateway.
[0021] Optionally, the process of sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination further includes:
[0022] Sending a request to stop communication to the target shared memory gateway;
[0023] A communication stop completion message returned by the target shared memory gateway is received.
[0024] Optionally, the process of sending a process start instruction to a second execution management module in a second software architecture corresponding to the second process combination so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination further includes:
[0025] Sending a request to initiate communication to the target shared memory gateway;
[0026] A communication startup completion message returned by the target shared memory gateway is received.
[0027] In a second aspect, the present application discloses a system state management device, which is applied to a state management module, wherein the state management module is used to manage multiple states of the system, and the device includes:
[0028] a process determination module, configured to, upon receiving a state switching instruction for switching a first state to a second state, determine a first process combination corresponding to the first state and a second process combination corresponding to the second state;
[0029] a process stopping module, configured to send a process stopping instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination;
[0030] A process startup module is used to send a process startup instruction to the second execution management module in the second software architecture corresponding to the second process combination after receiving a message indicating that the process stop is completed returned by the first execution management module, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination.
[0031] In a third aspect, the present application discloses an electronic device, comprising:
[0032] Memory, used to store computer programs;
[0033] The processor is used to execute the computer program to implement the system status management method disclosed above.
[0034] In a fourth aspect, the present application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the system status management method disclosed above is implemented.
[0035] It can be seen that the present application provides a system state management method, which is applied to a state management module, and the state management module is used to manage multiple states of the system. The method includes: when a state switching instruction for switching a first state to a second state is received, determining a first process combination corresponding to the first state and a second process combination corresponding to the second state; sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination; after receiving a message indicating that the process stop is completed returned by the first execution management module, sending a process start instruction to a second execution management module in a second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination.
[0036] In summary, the present application proposes a unified state management module, defines different system states in the state management module, and sets a process combination that needs to be started for each state. The process combination can come from different software system architectures or from the same software system architecture. Furthermore, when a state switching instruction is received for switching from the first state to the second state, the present application determines the process combination and software system architecture corresponding to the above two states respectively, and controls the respective process management modules to stop the corresponding processes through their respective execution management modules, and then controls the respective process management modules to start the corresponding processes through their respective execution management modules after stopping the corresponding processes, so as to realize the integration and management of two or more execution management and process management. That is, the present application realizes unified state management through the state management module, without changing the logic of the respective execution management modules, reducing the execution logic modification work, realizing system functions faster, and ensuring the stability of the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.
[0038] Figure 1 A flow chart of a system status management method disclosed in this application;
[0039] Figure 2 A schematic diagram of the architecture of a system status management method disclosed in this application;
[0040] Figure 3 A specific system status management method flow chart disclosed in this application;
[0041] Figure 4 A schematic diagram of the structure of a system status management device disclosed in this application;
[0042] Figure 5 This is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION
[0043] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0044] The software architectures provided by different suppliers are different. When implementing system state management of software architectures provided by multiple suppliers, it is often necessary to change their respective management logic, which greatly increases the modification work and the probability of error. Therefore, a system state management method is urgently needed to solve the above-mentioned problems. To this end, the embodiment of the present application proposes a system state management solution that can achieve unified state management and reduce logic modification work.
[0045] The present application embodiment discloses a system state management method, which is applied to a state management module, wherein the state management module is used to manage multiple states of the system. Figure 1 As shown, the method includes:
[0046] Step S11: when a state switching instruction for switching a first state to a second state is received, a first process combination corresponding to the first state and a second process combination corresponding to the second state are determined.
[0047] In this embodiment, different states of the system correspond to different process combinations, and the system includes an AUTOSAR Adaptive Platform (Autosar AP).
[0048] In one implementation, the process combination may be a combination of several processes. For example, the first state corresponds to process 1 and process 2. Process 1 and process 2 may come from different software architectures or from the same software architecture. The same is true for the second state.
[0049] In another embodiment, the process combination can be a combination composed of several process sub-combinations. For example, the first state corresponds to the first process sub-combination and the second process sub-combination. The first process sub-combination includes process 3 and process 4, and the second process sub-combination includes process 5 and process 6. The same applies to the second state.
[0050] On this basis, when a state switching instruction for switching the first state to the second state is received, a first process combination corresponding to the first state and a second process combination corresponding to the second state are determined.
[0051] Step S12: Sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination.
[0052] Figure 2 Provides an implementation scenario including two software architectures, see Figure 2As shown, the software architecture specifically includes a first software architecture and a second software architecture. The connection line between the state management module and the first execution management module indicates that the state management module sends a process stop instruction or a process start instruction to the first execution management module in the first software architecture corresponding to the first process combination.
[0053] In this embodiment, a process stop instruction is sent to the first execution management module in the first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination.
[0054] The following describes how to stop each process in the first process combination. First, determine the interdependence of each process in the first process combination so as to divide each process in the first process combination into a plurality of first processes and a plurality of second processes; wherein the stopping of any second process depends on the stopping of a plurality of first processes. Further, send a process stop instruction to the first execution management module in the first software architecture corresponding to the first process combination so that the first execution management module controls the first process management module in the first software architecture to stop the plurality of first processes, and after stopping each of the plurality of first processes, add one to the target count value. Finally, determine whether the current target count value meets the first threshold value. If so, send a process stop instruction to the first execution management module in the first software architecture corresponding to the first process combination so that the first execution management module controls the first process management module in the first software architecture to stop any second process, so as to stop each process in the first process combination.
[0055] For example, the first process combination includes process A, process B and process C, wherein the stopping of process A depends on the stopping of process B and process C, that is, process A can only stop after process B and process C are both stopped, while the stopping of process B and process C does not depend on the stopping of other processes, which is the mutual dependence relationship between the processes in the first process combination, so that process B and process C are the first process, and process A is the second process. Further, a process stop instruction is sent to the first execution management module in the first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop process B and process C. It should be noted that a counter needs to be maintained here, when process B stops, the first count value of the counter is increased by 1, and when process C stops, the first count value of the counter is increased by 1 again, and the value of the first counter is 2 at this time. If the first threshold is 2, the value of the first counter satisfies 2, and a process stop instruction is sent to the first execution management module in the first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop process A, so far, all processes in the first process combination have stopped.
[0056] In the above process, the software architecture is the upstream of the process, and the process is the downstream of the software architecture. The upstream represents the upper-level observer of the downstream, which will retain the array of downstream dependencies. Further, when the downstream state changes, it will trigger the registered observer to calculate the count value of the observer, that is, in addition to the first count values corresponding to process A, process B and process C mentioned above, the first software architecture as the upstream of the process, that is, the upper-level observer, also has a corresponding count value threshold. When process A stops, the value of the first counter is added by 1, changing from 2 to 3. Assuming that the threshold of the first software architecture is 3, it means that there are 3 processes in the first software architecture. When the value of the first counter meets 3, it means that all 3 processes in the first software architecture are stopped, and the first software architecture is also stopped. In addition, process management can be used as the downstream of state management or as the upstream of the process it manages. In summary, this embodiment implements notifications from state management to different execution management based on the upstream and downstream mode and the observer mode.
[0057] Step S13: After receiving the message indicating that the process stop is completed returned by the first execution management module, a process start instruction is sent to the second execution management module in the second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination.
[0058] Referring to the above process, when each process in the first process combination is stopped, the first state is also closed. If you want to switch to the second state at this time, you need to start each process in the second process combination.
[0059] See also Figure 2 As shown, the connection line between the state management module and the second execution management module indicates that the state management module sends a process start instruction or a process stop instruction to the second execution management module in the second software architecture corresponding to the second process combination.
[0060] In this embodiment, a process stop instruction is sent to the second execution management module in the second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to stop each process in the second process combination.
[0061] It should be pointed out that the process of process startup refers to the process of process stop, that is, first determine the mutual dependency relationship of each process in the second process combination, so as to divide each process in the second process combination into a third process that can be started without relying on the startup of other processes, and a fourth process that needs to rely on the startup of other processes to start. Further, send a process stop instruction to the second execution management module in the second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to stop the third process, and after each third process is started, add one to the corresponding count value. Finally, judge whether the current count value meets the threshold. If so, send a process stop instruction to the second execution management module in the second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to stop the fourth process, so as to stop each process in the second process combination.
[0062] See also Figure 2 As shown, the first process management module and the second process management module respectively establish connections with the target shared memory gateway, indicating that each process in the first software architecture and each process in the second software architecture communicate with each other through the target shared memory gateway. It can be understood that after stopping each process in the first process combination, a request to stop communication is sent to the target shared memory gateway, and a message of communication stop completion returned by the target shared memory gateway is received. After starting each process in the second process combination, a request to start communication is sent to the target shared memory gateway, and a message of communication start completion returned by the target shared memory gateway is received. In other words, considering that the first software architecture and the second software architecture may be software architectures of different communication architectures, the present application introduces a target shared memory gateway to realize mutual communication between software architectures of different communication architectures.
[0063] See also Figure 2 As shown, the first software architecture also includes a first health management module, and the second software architecture also includes a second health management module. In this way, in addition to passively switching the system state through state switching instructions, the present application can also collect health information reported by the health management module through the state management module, and determine whether to perform active state switching based on the reporting method of the health information.
[0064] Specifically, this embodiment obtains the first health information reported by the first health management module, and obtains the second health information reported by the second health management module, and then determines whether to switch the current state in the state management module based on the first health information and the second health information. If the first health information and the second health information are reported according to a pre-set reporting method, there is no need to switch the current state in the state management module; if the first health information and the second health information are not reported according to the pre-set reporting method, the current state in the state management module is switched; wherein the pre-set reporting method includes any one or a combination of scheduled reporting, expiration reporting or logical reporting. Exemplarily, for the timed reporting, this embodiment can set the period of the timed reporting to 5000ms. In this way, it is determined every 5000ms whether the health management module reports the health information. For the due reporting, this embodiment can set the due reporting range to 50-100ms. In this way, it is determined whether the health management module completes the reporting within 50-100ms. For the logical reporting, it is determined whether the health information reported by the health management module is the health information reported after the execution order of each process is completed.
[0065] In addition, the connection between the status management module and the first health management module or the second health management module indicates that the status management module notifies the health management module to stop the health management of the process, and the connection between the health management module and the first execution management module or the second execution management module indicates that the health management module is started or shut down through the execution management module.
[0066] Figure 3 A specific system status management method flow chart is provided, see Figure 3As shown, the user sends a state switching instruction to the state management module to switch the first state to the second state. After receiving the state switching instruction, the state management module sends a process stop instruction to the first execution management module. After receiving the instruction, the first execution management module stops the process through the first process management module. After the first process management module stops the process, it returns a message of the process stop completion to the first execution management module. Further, the state management module sends a request to stop communication to the target shared memory gateway, and the target shared memory gateway returns a message of the communication stop completion to the state management module. Further, the state management module sends a process stop instruction to the second execution management module. After receiving the instruction, the second execution management module stops the process through the second process management module. After the second process management module stops the process, it returns a message of the process stop completion to the second execution management module. Further, the state management module sends a request to stop communication to the target shared memory gateway, and the target shared memory gateway returns a message of the communication stop completion to the state management module, thereby realizing the closing of the first state. The startup of the second state refers to the above process, which will not be repeated here.
[0067] It can be seen that the present application provides a system state management method, which is applied to a state management module, and the state management module is used to manage multiple states of the system. The method includes: when a state switching instruction for switching a first state to a second state is received, determining a first process combination corresponding to the first state and a second process combination corresponding to the second state; sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination; after receiving a message indicating that the process stop is completed returned by the first execution management module, sending a process start instruction to a second execution management module in a second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination.
[0068] In summary, the present application proposes a unified state management module, defines different system states in the state management module, and sets a process combination that needs to be started for each state. The process combination can come from different software system architectures or from the same software system architecture. Furthermore, when a state switching instruction is received for switching from the first state to the second state, the present application determines the process combination and software system architecture corresponding to the above two states respectively, and controls the respective process management modules to stop the corresponding processes through their respective execution management modules, and then controls the respective process management modules to start the corresponding processes through their respective execution management modules after stopping the corresponding processes, so as to realize the integration and management of two or more execution management and process management. That is, the present application realizes unified state management through the state management module, without changing the logic of the respective execution management modules, reducing the execution logic modification work, realizing system functions faster, and ensuring the stability of the system.
[0069] Accordingly, the embodiment of the present application further discloses a system state management device, which is applied to a state management module, wherein the state management module is used to manage multiple states of the system, and the device comprises: Figure 4 As shown, the device comprises:
[0070] A process determination module 11, configured to determine a first process combination corresponding to the first state and a second process combination corresponding to the second state when receiving a state switching instruction for switching the first state to the second state;
[0071] A process stopping module 12 is used to send a process stopping instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination;
[0072] The process starting module 13 is used to send a process starting instruction to the second execution management module in the second software architecture corresponding to the second process combination after receiving the message of process stopping completion returned by the first execution management module, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination.
[0073] Among them, for more specific working processes of the above-mentioned modules, please refer to the corresponding contents disclosed in the aforementioned embodiments, which will not be repeated here.
[0074] It can be seen that the present application provides a system state management method, which is applied to a state management module, and the state management module is used to manage multiple states of the system. The method includes: when a state switching instruction for switching a first state to a second state is received, determining a first process combination corresponding to the first state and a second process combination corresponding to the second state; sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination; after receiving a message indicating that the process stop is completed returned by the first execution management module, sending a process start instruction to a second execution management module in a second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination.
[0075] In summary, the present application proposes a unified state management module, defines different system states in the state management module, and sets a process combination that needs to be started for each state. The process combination can come from different software system architectures or from the same software system architecture. Furthermore, when a state switching instruction is received for switching from the first state to the second state, the present application determines the process combination and software system architecture corresponding to the above two states respectively, and controls the respective process management modules to stop the corresponding processes through their respective execution management modules, and then controls the respective process management modules to start the corresponding processes through their respective execution management modules after stopping the corresponding processes, so as to realize the integration and management of two or more execution management and process management. That is, the present application realizes unified state management through the state management module, without changing the logic of the respective execution management modules, reducing the execution logic modification work, realizing system functions faster, and ensuring the stability of the system.
[0076] Furthermore, an embodiment of the present application also provides an electronic device. Figure 5 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the diagram cannot be regarded as any limitation on the scope of use of the present application.
[0077] Figure 5A schematic diagram of the structure of an electronic device 20 provided in an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a display screen 23, an input / output interface 24, a communication interface 25, a power supply 26, and a communication bus 27. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the system status management method disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.
[0078] In this embodiment, the power supply 26 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 25 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 24 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.
[0079] In addition, the memory 22, as a carrier for storing resources, may be a read-only memory, a random access memory, a disk or an optical disk, etc., and the resources stored thereon may include a computer program 221, and the storage method may be temporary storage or permanent storage. In addition to including a computer program that can be used to complete the system state management method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 221 may further include a computer program that can be used to complete other specific tasks.
[0080] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the system status management method disclosed above is implemented.
[0081] For the specific steps of the method, reference may be made to the corresponding contents disclosed in the aforementioned embodiments, which will not be described in detail here.
[0082] The various embodiments in this application are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.
[0083] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0084] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
[0085] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article 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, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0086] The above is a detailed introduction to a system status management method, device, equipment, and storage medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A system status management method, characterized in that: Applied to a state management module, the state management module is used to manage multiple states of the system, the method includes: When receiving a state switching instruction for switching a first state to a second state, determining a first process combination corresponding to the first state and a second process combination corresponding to the second state; Sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination; After receiving the process stop completion message returned by the first execution management module, sending a process start instruction to the second execution management module in the second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination; The state management module is a module independent of the first software architecture and the second software architecture.
2. The system status management method according to claim 1, characterized in that: The sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination, includes: Determining the interdependence of the processes in the first process combination, so as to divide the processes in the first process combination into a plurality of first processes and a plurality of second processes; wherein the stopping of any second process depends on the stopping of a plurality of first processes; Sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop the plurality of first processes, and after stopping each of the plurality of first processes, adding one to a target count value; Determine whether the current target count value meets a first threshold value. If so, send a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop any second process, so as to stop each process in the first process combination.
3. The system status management method according to claim 1, characterized in that: The first software architecture also includes a first health management module, and the second software architecture also includes a second health management module; Accordingly, the system status management method further includes: The first health information reported by the first health management module is obtained, and the second health information reported by the second health management module is obtained, and then it is determined whether to switch the current state in the state management module according to the first health information and the second health information.
4. The system status management method according to claim 3, characterized in that: The determining whether to switch the current state in the state management module according to the first health information and the second health information includes: If the first health information and the second health information are reported according to a preset reporting method, there is no need to switch the current state in the state management module; If the first health information and the second health information are not reported according to the preset reporting method, switching the current state in the state management module; The pre-set reporting method includes any one or a combination of scheduled reporting, expiration reporting or logical reporting.
5. The system status management method according to any one of claims 1 to 4, characterized in that: The first process management module and the second process management module respectively establish connections with a target shared memory gateway, so that each process in the first software architecture and each process in the second software architecture can communicate with each other through the target shared memory gateway.
6. The system status management method according to claim 5, characterized in that: The process of sending a process stop instruction to a first execution management module in a first software architecture corresponding to the first process combination so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination further includes: Sending a request to stop communication to the target shared memory gateway; A communication stop completion message returned by the target shared memory gateway is received.
7. The system status management method according to claim 5, characterized in that: The process of sending a process start instruction to a second execution management module in a second software architecture corresponding to the second process combination so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination also includes: Sending a request to initiate communication to the target shared memory gateway; A communication startup completion message returned by the target shared memory gateway is received.
8. A system status management device, characterized in that: Applied to a state management module, the state management module is used to manage multiple states of the system, the device comprises: a process determination module, configured to, upon receiving a state switching instruction for switching a first state to a second state, determine a first process combination corresponding to the first state and a second process combination corresponding to the second state; a process stopping module, configured to send a process stopping instruction to a first execution management module in a first software architecture corresponding to the first process combination, so that the first execution management module controls the first process management module in the first software architecture to stop each process in the first process combination; a process starting module, configured to, upon receiving a message indicating that the process stop is completed returned by the first execution management module, send a process starting instruction to the second execution management module in the second software architecture corresponding to the second process combination, so that the second execution management module controls the second process management module in the second software architecture to start each process in the second process combination; The state management module is a module independent of the first software architecture and the second software architecture.
9. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the system status management method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: Used to store a computer program; wherein, when the computer program is executed by a processor, the system status management method according to any one of claims 1 to 7 is implemented.
