An execution management module, system and vehicle

Abstract

The present invention belongs to the technical field of automotive open system architecture, and specifically relates to an execution management module, a system and a vehicle. The module includes: an execution component, a pipeline communication component and an external interface component; the execution component includes a dynamic service unit, a static service unit and a data reading unit; the data reading unit is used to read the application configuration list and the machine configuration list; the static service unit is used to start the execution management module and the application program according to the machine configuration list; the external interface component is used to receive the process operation data and transmit it to the independently encapsulated service application interface subunit, health management interface subunit, status management interface subunit, and update subunit; the static service unit is also used to perform corresponding operations on the process operation data. Among them, each subunit in the dynamic service unit is independently encapsulated, so that each function does not affect each other, reduces coupling, and improves the flexibility and expandability of the module.

Description

Technical Field

[0001] The present invention relates to the technical field of automotive open system architecture, and particularly to an execution management module, a system and a vehicle. Background Art

[0002] With the rapid development of electronic and electrical architecture, software functions, and even vehicle-cloud collaborative control, as well as the emergence of new applications and new requirements such as the intelligence, networking, and new energy of automobiles, the automotive open system architecture (AUTOSAR, AUTOmotive OpenSystem Architecture) platform has proposed AP AUTOSAR to support high-performance computing. It is a new type of software architecture platform that adopts a distributed working mode, enabling independent development of ECU applications without mutual influence.

[0003] AP AUTOSAR mainly includes a hardware / virtual layer, a basic layer, a service layer, and an application layer. The EM (Execution Management) module belongs to the service layer among them, and is mainly responsible for system initialization and the startup and shutdown of application programs (AP applications). It uses the information contained in the Manifest (application configuration file) to perform these tasks, including how to start these tasks and the limitations of these tasks.

[0004] The execution management module needs to provide service interfaces to application programs and some other functions and services within the platform. However, during the implementation process within the execution management module, since the service layer does not abstract the implementation of each function clearly enough, there is a relatively large coupling, which increases the resource consumption of the system and also affects the flexibility and expandability of the execution management module. Summary of the Invention

[0005] In order to solve the above technical problems, the specific technical solutions in this article are as follows:

[0006] On the one hand, this article provides an execution management module, and the module includes: an execution component, a pipeline communication component, and an external interface component; the execution component is connected to the external interface component through the pipeline communication component;

[0007] The execution component includes a dynamic service unit, a static service unit, and a data reading unit;

[0008] The data reading unit is used to read the application configuration list and the machine configuration list;

[0009] The static service unit is used to start the corresponding machine according to the machine configuration list and start the corresponding process according to the execution order of the application program processes in the application configuration list;

[0010] The external interface component is used to receive the process running data of the application program, the health management module, the status management module, and / or the update module. The process running data includes: process startup status, process execution status, process switching instruction, and / or machine configuration list reload instruction;

[0011] The dynamic service unit includes an independently encapsulated service application interface subunit, a health management interface subunit, a status management interface subunit, and / or an update subunit. The service application interface subunit, the health management interface subunit, the status management interface subunit, and / or the update subunit are respectively connected to the external interface component through a pipeline communication component to receive the corresponding process startup status, process execution status, process switching instruction, and / or machine configuration list reload instruction and perform corresponding operations.

[0012] Further, the external interface component includes: an application program interface, and the application program interface is connected to the service application interface subunit through the pipeline communication component;

[0013] The application program interface is called by the application program to report the process startup status of the application program to the service application interface subunit, so that the static service unit configures the required data files for the process of the application program according to the process startup status during the execution of the management daemon process, and sets the status of the application program to the status corresponding to the execution process during the execution of the management daemon process.

[0014] Further, the external interface component further includes: a health management interface, and the health management interface is connected to the health management interface subunit through the pipeline communication component;

[0015] The health management interface is called by the health management module to send the process execution status obtained by the health management module to the health management interface subunit, so that the static service unit compares the process execution status with the process status in the application configuration list and restarts the process when the comparison fails.

[0016] Further, the external interface component further includes: a status management interface, and the status management interface is connected to the status management interface subunit through the pipeline communication component;

[0017] The status management interface is called by the status management module to transmit the process switching instruction obtained by the status management module to the status management interface subunit, so that the static service unit switches to the corresponding process according to the process switching instruction and returns the status conversion result to the status management module after starting the process.

[0018] Further, the external interface component further includes: an update interface, and the update interface is connected to the update subunit through the pipeline communication component;

[0019] The update interface is called by the update module, and is used for transmitting the machine configuration list reload instruction obtained by the update module to the update subunit, so that the static service unit reloads the machine configuration list according to the machine configuration list reload instruction.

[0020] Further, the pipeline communication component connects the service application interface subunit and the application program interface, the health management interface subunit and the health management interface, the status management interface subunit and the status management interface, and the update interface and the update subunit through a named pipe.

[0021] On the other hand, this article provides an execution management system, and the system includes the above-mentioned execution management module and persistence module;

[0022] The persistence module is connected to the data reading unit in the execution management module, and is used for persistently storing the read application configuration list and machine configuration list into the data reading unit.

[0023] Further, the system further includes: a log storage module, and the log storage module is connected to the static service unit in the execution management module, and is used for storing the execution log of the static service unit.

[0024] Further, it further includes a health management module, a status management module and an update module all connected to the external interface component.

[0025] On the other hand, this article provides a vehicle, and the vehicle is provided with an on-board computer, and the on-board computer includes the above-mentioned execution management system.

[0026] With the above technical solution, an execution management module, system and vehicle in this text read the application configuration list and machine configuration list through a data reading unit. The static service unit starts the corresponding machine and application program according to the application configuration list and machine configuration list. Then, through the service application interface sub-unit, health management interface sub-unit, status management interface sub-unit, and update sub-unit that are independently encapsulated, different states of the detection process or different instructions are received, so that status data or instructions for different purposes are isolated from each other, avoiding the fusion of status data and reducing the coupling of status data. In addition, the service application interface sub-unit, health management interface sub-unit, status management interface sub-unit, and update sub-unit in this application can be configured according to user needs, that is, the user can selectively turn off or turn on the above sub-units to meet different user needs, while being able to save system resources and increase the flexibility and scalability of the execution management function cluster (execution management module).

[0027] To make the above and other purposes, features and advantages of this text more obvious and understandable, the following specifically gives preferred embodiments and, in conjunction with the accompanying drawings, the detailed description is as follows. Brief Description of the Drawings

[0028] In order to more clearly illustrate the technical solutions in the embodiments of this text or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of this text. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0029] Figure 1 It shows a schematic diagram of the architecture of an execution management function cluster provided in the embodiments of this text. Detailed Embodiments

[0030] The following will clearly and completely describe the technical solutions in the embodiments of this text in conjunction with the drawings in the embodiments of this text. Obviously, the described embodiments are only some of the embodiments of this text, rather than all of them. Based on the embodiments in this text, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope protected by this text.

[0031] It should be noted that the terms "first", "second", etc. in the specification, claims and above-mentioned drawings of this article are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, device, product or equipment that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or equipment.

[0032] To solve the above problems, embodiments of this article provide an execution management module and system. Please refer to Figure 1 , Figure 1 which shows a schematic architecture diagram of an execution management function cluster provided in the embodiments of this article. The execution management function cluster in AP AUTOSAR (Adaptive Platform AUTOSAR) can be understood as the execution management module in AP AUTOSAR. Specifically, the module includes: an execution component, a pipeline communication component, and an external interface component; the execution component is connected to the external interface component through the pipeline communication component;

[0033] The execution component includes a dynamic service unit, a static service unit, and a data reading unit;

[0034] The data reading unit is used to read the application configuration list and the machine configuration list;

[0035] The static service unit is used to start the corresponding machine according to the machine configuration list and start the corresponding process according to the execution order of the application program processes in the application configuration list;

[0036] The external interface component is used to receive the process running data of the application program, the health management module, the status management module, and / or the update module. The process running data includes: process start status, process execution status, process switching instruction, and / or machine configuration list reload instruction;

[0037] The dynamic service unit includes a service application interface subunit, a health management interface subunit, a status management interface subunit, and / or an update subunit that are independently encapsulated. The service application interface subunit, the health management interface subunit, the status management interface subunit, and / or the update subunit are respectively connected to the external interface component through a pipeline communication component to receive the corresponding process startup status, process execution status, process switching instruction, and / or machine configuration list reload instruction and perform corresponding operations.

[0038] Specifically, the service application interface subunit is used to receive the process startup status; the health management interface subunit is used to receive process execution status data, the status management interface subunit is used to receive process switching instructions, and the update subunit is used to receive machine configuration list reload instructions;

[0039] The static service unit is used to perform corresponding operations according to the process operation data in the dynamic service unit. The corresponding operations include configuring files required for process execution for the process, restarting the process, switching the process, and reloading the machine configuration list.

[0040] Specifically, in the automotive open system architecture, the Adaptive Platform (AP, Adaptive Autosar) regards the hardware running on it as a Machine. Specifically, the above-mentioned Machine can be a real physical Machine, a fully virtualized Machine, a semi-virtualized OS, an OS-level virtualized container, or any other virtualization environment.

[0041] It can be understood that there can be one or more Machines in the adaptive automotive open system architecture, and only one AP instance runs on one Machine. Generally, it is considered that this "hardware" includes a chip that can accommodate one or more Machines. The machine in the embodiments of this specification can be understood as in the execution management module, that is, before the execution management module starts, it can start the corresponding machines in sequence according to the pre-configured machine configuration list to complete the operation of the execution management module.

[0042] Specifically, the execution management module is a functional cluster. This functional cluster can provide an external interface component to the application program and external modules to achieve connection with the application program and other modules. The static service unit is responsible for the configuration of the application program and accepts information from other modules to control the startup, shutdown, restart, and switching of the adaptive application process.

[0043] Specifically, the static service unit is the execution part of the Adaptive Platform (AP, Adaptive Autosar) in the entire automotive open system architecture. It is mainly used to sequentially start the corresponding machines in the order of the machines in the machine configuration list, and after all or some of the machines in the machine configuration list are started, start or stop the processes of the corresponding application programs according to the application configuration list.

[0044] Specifically, the external interface component is the external interface of the execution management function cluster (execution management module), which is called by other modules (such as application programs, state management modules, health management modules, and update modules) to enable them to interact with the execution management function cluster. For example: status reports of application programs (adaptive applications); state switching of machines or functional groups in the state management module (sm); information acquisition or entry into a safe state by the health management module (phm); reloading of the machine configuration list by the update module (ucm), etc.

[0045] Among them, the dynamic service unit realizes data interaction with the external interface component through the pipeline communication component, is used to receive the information transmitted when the external interface component is called by other modules, and the static service unit performs corresponding processing according to the above-transmitted information, such as: reloading the machine configuration list, switching the states of machines and functional groups, starting or stopping application programs, restarting application programs, and acquiring execution information.

[0046] Among them, reloading the machine configuration list can be used to reload the machine to facilitate the restart of the system. Switching the states of machines and functional groups can be used to switch the states of different machines or different functional groups. Among them, a functional group can be understood as the process of an application program. Acquiring execution information can be understood as the execution progress of a specific machine or application program.

[0047] Specifically, the Execution Manifest file (application configuration list) of the APP (application program) and the Machine Manifest (machine configuration list) are stored in the data reading unit. The configuration information of the APP is stored in the application configuration list, and different APPs are associated with different system states (Machine State) in the Manifest file. That is, the Execution Manifest is used to elaborate on the information related to the deployment during the operation of the application program. The Execution Manifest is bound to the actual code executed by the application program to support the integration of the executable program on the machine.

[0048] The Machine Manifest provides definitions of machine status, functional group status, entry / exit timeouts, memory usage, etc. The definitions in the Machine Manifest enable the EM to operate within the limits set in the machine configuration manifest without overusing resources.

[0049] It can be understood that the Machine Manifest records status-related configurations of the machine status for running application programs and their corresponding functional group statuses. That is, the Machine Manifest is bound to the software for creating AP instances. When APAUTOSAR starts, the execution management module can start the corresponding machine according to the Machine Manifest read in the data reading unit, and then notify the start status management module (SM) after the machine runs. The status management module can notify the execution management module to switch the machine's or functional group's status. After the switch is successful, the corresponding application program is started or the application program process is closed according to the application configuration manifest.

[0050] After the process in the application program starts, the execution management module can receive the reported process start status, process execution status, process switch instruction, and machine configuration manifest reload instruction through the independently encapsulated service application interface subunit, health management interface subunit, status management interface subunit, and update subunit respectively.

[0051] Specifically, the subunits in the dynamic service unit can be configured according to the user's needs. For example, if the user only needs the service application interface subunit and the health management interface subunit, then only the service application interface subunit and the health management interface subunit can be configured, without configuring the status management interface subunit and the update subunit.

[0052] In an optional embodiment, corresponding switches can also be configured for each subunit in the dynamic service unit to facilitate enabling or disabling the corresponding functions.

[0053] Among them, the process start status indicates whether the process has started. After the process starts, the static service unit can configure the data files required for the process according to the process start status.

[0054] In an optional embodiment, the external interface component includes: an application program interface, and the application program interface is connected to the service application interface subunit through the pipeline communication component;

[0055] The application programming interface is called by an application program and is used to report the process startup status of the application program to the service application interface subunit, so that the static service unit configures the required data files for the process of the application program according to the process startup status during the execution of the management daemon process, and sets the status of the application program to the status corresponding to the execution process during the execution of the management daemon process.

[0056] It can be understood that different application programs will go through multiple processes during execution, and each process represents a state of the application program, that is, different processes have different states. When the service application interface module reports the process execution status, the static service unit can execute the next process or restart the reported execution process according to the reported process startup status during the execution of the management daemon process, configure the required data files for the started process, and set the status of the application program to the status corresponding to the execution process during the execution of the management daemon process. Among them, the data files required for process configuration can be understood as the files or programs that need to be called during the execution of the process.

[0057] Among them, the process execution status represents whether the process is executed correctly. After the process execution is completed, the static service unit can judge whether the process is executed correctly according to the process execution status in the health management interface subunit.

[0058] In an optional embodiment, the external interface component further includes: a health management interface, and the health management interface is connected to the health management interface subunit through the pipeline communication component;

[0059] The health management interface is called by the health management module and is used to send the process execution status obtained by the health management module to the health management interface subunit, so that the static service unit compares the process execution status with the process status in the application configuration list and restarts the process when the comparison fails.

[0060] Specifically, the health management module (phm) is used to receive the process execution status of the application program and transmit the process execution status to the health management interface subunit, so that the static service unit detects the process execution status. When it is detected that the process execution status of the application program is different from the status of the process executed by the static service unit, a recovery action is triggered, so that the static service unit restarts the process according to the recovery action.

[0061] It can be understood that the comparison process of the process status can be executed in the health management module or in the static service unit.

[0062] Among them, the process switching instruction can be a specification input by the user, which is used to execute the switching of the process.

[0063] In an alternative embodiment, the external interface component further includes: a status management interface, and the status management interface is connected to the status management interface subunit through the pipeline communication component;

[0064] The status management interface is called by the status management module and is used to transmit the process switching instruction obtained by the status management module to the status management interface subunit, so that the static service unit switches to the corresponding process according to the process switching instruction, and returns the status conversion result to the status management module after starting the process.

[0065] Specifically, the status management module can be used to receive all function groups and machine switching instructions running in AP AUTOSAR, and transmit the above switching instructions to the status management interface subunit. The static service unit can switch the machine or function group status according to the above switching instructions. It can be understood that the above switching instructions carry the corresponding execution content, that is, the specific switched machine or function group. When the static service unit starts or shuts down the process corresponding to the above switching instruction, the static service unit can return the status switching result to the status management module.

[0066] Among them, the machine state is the specific execution state of the machine, and the machine state can include the on state and the off state. The function group status switching instruction is used to represent the status switching of the function group, such as the switching of the process.

[0067] Specifically, the machine configuration list reload instruction is generated in the case of machine or application update. The machine configuration list reload instruction can be used to instruct the execution management module to reload the machine configuration list.

[0068] In an alternative embodiment, the external interface component further includes: an update interface, and the update interface is connected to the update subunit through the pipeline communication component;

[0069] The update interface is called by the update module and is used to transmit the machine configuration list reload instruction obtained by the update module to the update subunit, so that the static service unit reloads the machine configuration list according to the machine configuration list reload instruction.

[0070] Specifically, when the update subunit receives the machine configuration list reload instruction sent by the update module, the execution management module can reload the machine configuration list and perform corresponding operations according to the reloaded machine configuration list, such as the upgrade of the application program, etc.

[0071] With the above technical solution, an execution management module in this article reads the application configuration list and the machine configuration list through a data reading unit. The static service unit starts the corresponding machine and application program according to the application configuration list and the machine configuration list. Then, through the service application interface subunit, health management interface subunit, status management interface subunit, and update subunit, which are independently encapsulated, different states of the process are detected or different instructions are received, so that status data for different purposes are isolated from each other, avoiding the fusion of status data and reducing the coupling of status data. In addition, the service application interface subunit, health management interface subunit, status management interface subunit, and update subunit in this application can be configured according to user needs, that is, the user can selectively turn off or turn on the above subunits to meet different user needs, while saving system resources and increasing the flexibility and scalability of the execution management function cluster (execution management module).

[0072] In an alternative embodiment, the pipe communication component connects the service application interface subunit and the application program interface, the health management interface subunit and the health management interface, the status management interface subunit and the status management interface, and the update interface and the update subunit through named pipes.

[0073] Specifically, named pipes (Named Pipes) can support reliable, unidirectional or bidirectional data communication between different processes on the same computer or between different processes on different computers across a network. Named pipes exist in the file system in the form of FIFO files. Even processes that have no kinship with the process that created the FIFO can communicate with each other through the FIFO as long as they can access the path. Therefore, processes that are not related through the FIFO can also exchange data. In the embodiments of this specification, the service application interface subunit and the application program interface, the health management interface subunit and the health management interface, the status management interface subunit and the status management interface, and the update interface and the update subunit are connected through named pipes.

[0074] It can be understood that the named pipes are configured in the above pipe communication component.

[0075] The embodiments of this specification further isolate the above status data or instructions for different purposes through named pipes, further avoiding data coupling.

[0076] On the other hand, this article provides an execution management system, which includes the execution management module and the persistence module in the automotive open system architecture described above. The execution management module includes: an execution component, a pipe communication component, and an external interface component;

[0077] The execution component includes a dynamic service unit, a static service unit, and a data reading unit;

[0078] The persistence module is connected to the data reading unit in the execution management module, and is used to persistently store the read application configuration list and machine configuration list into the data reading unit.

[0079] Specifically, persistence is a mechanism for converting program data between a persistent state and a transient state. That is, transient data (such as data in memory, which cannot be permanently saved) is persisted into persistent data (such as being persisted into a database and being able to be saved for a long time). Persistence means saving data (such as an object in memory) to a storage device that can be permanently saved (such as a disk). The main application of persistence is to store objects in memory in a database, or in a disk file, an XML data file, etc. In the embodiments of this specification, the read application configuration list and machine configuration list are persisted in the data storage component. It can be understood that the persisted application configuration list and machine configuration list stored in the data storage component are not immutable, and operations such as update, deletion, or replacement can also be performed on them.

[0080] In an optional embodiment, the system further includes: a log storage module, which is connected to the static service unit in the execution management module and is used to store the execution logs of the static service unit.

[0081] Specifically, the execution logs can record data that needs to be concerned about, and analyze the abnormal data that needs to be concerned about to form an alarm, such as a status abnormal instruction, and can also record the execution process of each process in the application program; as well as the application program update data packet uploaded by the update module, etc.

[0082] Specifically, the log storage module can record the received data corresponding to each type and the corresponding execution process according to the types of the service application interface subunit, the health management interface subunit, the status management interface subunit, and the update subunit, ensure that the execution logs are stored according to different categories, ensure the accuracy of recording the execution logs, and at the same time ensure that the data received by different subunits do not affect each other, and are also convenient for later operation and maintenance personnel to search.

[0083] In an optional embodiment, the system further includes a health management module, a status management module, and an update module, all of which are connected to the external interface component.

[0084] Specifically, the health management module can be connected to the health management interface subunit through the health management interface in the external interface component; the status management module can be connected to the status management interface subunit through the status management interface in the external interface component; the update module can be connected to the update subunit through the update interface in the external interface component.

[0085] The execution management system provided in this document has the technical features of the above-mentioned execution management module. Therefore, it also has the technical effects of the above-mentioned execution management module, and will not be repeated here.

[0086] On the other hand, this document provides a vehicle, which is provided with an on-board computer, and the on-board computer includes the above-mentioned execution management system.

[0087] Since each component or module in the execution management system has been described in the above-mentioned execution management module part, that is, an execution management system and a vehicle have the same technical effects as the execution management module in AP AUTOSAR, and will not be repeated here.

[0088] It should be noted that each embodiment in this specification is described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. The same or similar parts among the embodiments can be referred to each other. The test method provided by the embodiments of the present invention has the same implementation principle and the technical effects generated as those of the foregoing system embodiments. For the sake of brief description, for the parts not mentioned in the method embodiments, reference can be made to the corresponding content in the foregoing system embodiments.

[0089] It should be understood that in various embodiments of this document, the sequence numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of this document.

[0090] It should also be understood that in the embodiments of this document, the term "and / or" is only a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally represents an "or" relationship between the associated objects before and after.

[0091] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of the examples have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this article.

[0092] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0093] In the several embodiments provided in this article, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed couplings or direct couplings or communication connections to each other can be indirect couplings or communication connections through some interfaces, devices, or units, and can also be electrical, mechanical, or other forms of connection.

[0094] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they can be located in one place, or can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiments of this article.

[0095] In addition, the functional units in the various embodiments of this article can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0096] If an integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this article. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks, or optical discs.

[0097] Specific embodiments are used in this article to elaborate on the principles and implementation manners of this article. The description of the above embodiments is only used to help understand the method and its core idea of this article; at the same time, for those of ordinary skill in the art, according to the idea of this article, there will be changes in the specific implementation manners and application scopes. In summary, the content of this specification should not be construed as a limitation to this article.

Claims

1. An execution management module, characterized in that, The module includes: an execution component, a pipeline communication component, and an external interface component; the execution component is connected to the external interface component through the pipeline communication component; The execution component includes a dynamic service unit, a static service unit, and a data reading unit; The data reading unit is used to read the application configuration list and the machine configuration list; The static service unit is used to sequentially start the corresponding machines according to the order of the machines in the machine configuration list, and after all or some of the machines in the machine configuration list are started, start or stop the processes of the corresponding application programs according to the execution order of the application program processes in the application configuration list; The dynamic service unit is connected to the external interface component through the pipeline communication component; the external interface component is used to receive the process running data of the application program, the health management module, the status management module, and / or the update module; the process running data includes the process start status, the process execution status, the process switching instruction, and / or the machine configuration list reload instruction; the dynamic service unit is used to receive the process running data; Among them, the dynamic service unit includes an independently encapsulated service application interface subunit, a health management interface subunit, a status management interface subunit, and / or an update subunit; the service application interface subunit, the health management interface subunit, the status management interface subunit, and / or the update subunit are respectively connected to the external interface component through the pipeline communication component; the service application interface subunit is used to receive the process start status; the health management interface subunit is used to receive the process execution status data; the status management interface subunit is used to receive the process switching instruction; the update subunit is used to receive the machine configuration list reload instruction; The static service unit performs corresponding operations according to the process running data in the dynamic service unit; the corresponding operations include configuring files required for process execution for the process, restarting the process, switching the process, and reloading the machine configuration list.

2. The execution management module according to claim 1, characterized in that, The external interface component includes: an application program interface, and the application program interface is connected to the service application interface subunit through the pipeline communication component; The application program interface is called by the application program and is used to report the process start status of the application program to the service application interface subunit, so that the static service unit configures the required data files for the process of the application program according to the process start status during the execution of the management daemon process, and sets the status of the application program to the status corresponding to the execution process during the execution of the management daemon process.

3. The execution management module according to claim 1 or 2, characterized in that, The external interface component also includes: A health management interface, and the health management interface is connected to the health management interface subunit through the pipeline communication component; The health management interface is called by the health management module and is used to send the process execution status obtained by the health management module to the health management interface subunit, so that the static service unit compares the process execution status with the process status in the application configuration list and restarts the process when the comparison fails.

4. The execution management module according to claim 3, characterized in that, The external interface component further includes: a status management interface, and the status management interface is connected to the status management interface subunit through the pipeline communication component; The status management interface is called by the status management module, and is used for transmitting the process switching instruction obtained by the status management module to the status management interface subunit, so that the static service unit switches to the corresponding process according to the process switching instruction, and returns the status conversion result to the status management module after starting the process.

5. The execution management module according to claim 1, 2 or 4, characterized in that, The external interface component further includes: an update interface, and the update interface is connected to the update subunit through the pipeline communication component; The update interface is called by the update module, and is used for transmitting the machine configuration list reload instruction obtained by the update module to the update subunit, so that the static service unit reloads the machine configuration list according to the machine configuration list reload instruction.

6. The execution management module according to claim 5, characterized in that, The pipeline communication component connects the service application interface subunit and the application program interface, the health management interface subunit and the health management interface, the status management interface subunit and the status management interface, and the update interface and the update subunit through named pipes.

7. An execution management system, characterized in that, The system includes the execution management module and the persistence module according to any one of claims 1-6; The persistence module is connected to the data reading unit in the execution management module, and is used for persistently storing the read application configuration list and machine configuration list into the data reading unit.

8. The execution management system according to claim 7, characterized in that, The system further includes: a log storage module, and the log storage module is connected to the static service unit in the execution management module, and is used for storing the execution log of the static service unit.

9. The execution management system according to claim 7, characterized in that, It further includes a health management module, a status management module and an update module all connected to the external interface component.

10. A vehicle, characterized in that, The vehicle is provided with an on-board computer, and the on-board computer includes the execution management system according to any one of claims 7-9.

Images