Method and apparatus for adapting complex application software to adaptive car open system architecture

Abstract

The embodiment of the application provides a method and device for adapting complex application software to an adaptive automobile open system architecture, and belongs to the technical field of automobile electronics. The method comprises the following steps: obtaining a software function requirement of a business program for the adaptive automobile open system architecture; configuring an upper computer based on the software function requirement, generating a configuration file and a framework code; performing secondary packaging on the framework code, generating a secondarily packaged program, and linking the secondarily packaged program to a public library of the automobile open system architecture; compiling the secondarily packaged program linked to the public library of the automobile open system architecture, generating a dynamic library or a static library; linking the business program to the dynamic library or the static library; compiling the business program linked to the dynamic library or the static library, generating an integrated business program; and deploying the integrated business program into a folder of a target file system according to the automobile open system architecture specification. The application has the advantages of high flexibility and small function integration difficulty.

Description

Technical Field

[0001] This invention relates to the field of automotive electronics technology, specifically to a method for adapting an adaptive automotive open system architecture to complex application software, an apparatus for adapting an adaptive automotive open system architecture to complex application software, a machine-readable storage medium, and a processor. Background Technology

[0002] The automotive industry is currently becoming a leading technological direction in the new round of technological revolution and industrial development, with software-defined vehicles representing the mainstream development approach for the future. At present, the demand for intelligent, safe, and technologically advanced automotive software is increasing, leading to ever-higher requirements for program security and operation.

[0003] Autosar (AUTomotive Open System Architecture) is a global alliance of leading companies in the automotive and software industries that develops and establishes standardized software frameworks and open E / E system architectures for intelligent mobility. The Adaptive Platform Autosar (AutosarAP) addresses the new market demands of next-generation vehicles for high performance, connectivity, and continuous over-the-air (OTA) software updates, serving as a software integration platform for multiple vendors.

[0004] However, integrating the functionality of the Adaptive Platform Autosar (AutosarAP) architecture into business applications presents challenges due to high integration difficulty and low flexibility. Developers using this architecture need to possess both application and Autosar development skills. Adjusting functionality requires repeated code tweaking, resulting in low reusability. Summary of the Invention

[0005] The purpose of this application is to provide a method and apparatus for adapting an adaptive automotive open system architecture to complex application software, so as to solve the problems of high integration difficulty and low flexibility in integrating business programs into the functions of the adaptive automotive open system architecture in the prior art.

[0006] To achieve the above objectives, the first aspect of this application provides a method for adapting an adaptive automotive open system architecture to complex application software, comprising:

[0007] Obtain the software functional requirements of the business program for the adaptive vehicle open system architecture;

[0008] Based on the aforementioned software functional requirements, the host computer is configured to generate configuration files and framework code;

[0009] The framework code is then encapsulated to generate a secondary encapsulated program, which is then linked to the public library of the Adaptive Automotive Open System Architecture.

[0010] Compile the secondary encapsulation program that links to the public library of the adaptive vehicle open system architecture to generate a dynamic library or a static library;

[0011] Link the business program to the dynamic library or static library;

[0012] The business programs linked to the dynamic or static libraries are compiled to generate the integrated business programs;

[0013] The integrated business program is deployed to a folder in the target file system in accordance with the Adaptive Automotive Open System Architecture specification.

[0014] In this embodiment of the application, the method further includes: modifying the configuration file according to the attributes of the business program to obtain a new configuration file.

[0015] In this embodiment of the application, the software functional requirements include execution management component requirements; the step of configuring the host computer based on the software functional requirements and generating configuration files and framework code includes:

[0016] Based on the requirements of the execution management component, the host computer is configured to generate the configuration file and framework code of the execution management component.

[0017] In this embodiment, the framework code of the execution management component includes a status reporting function; the secondary encapsulation of the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive automotive open system architecture, includes: when the business program needs to integrate the function of reporting running status, the status reporting function is secondary encapsulated to generate a secondary encapsulated status reporting function, and the secondary encapsulated status reporting function is linked to the public library of the adaptive automotive open system architecture.

[0018] In this embodiment of the application, compiling the secondary encapsulation program linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library includes: compiling the reporting status function of the secondary encapsulation linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library of the execution management component.

[0019] In this embodiment of the application, the software functional requirements include state management component requirements; the step of configuring the host computer based on the software functional requirements and generating configuration files and framework code includes: configuring the host computer based on the state management component requirements and generating configuration files and framework code for the state management component.

[0020] In this embodiment, the framework code of the state management component includes a state switching function; the secondary encapsulation of the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive automotive open system architecture, includes: when the business program needs to integrate the state switching function, performing secondary encapsulation of the state switching function to generate a secondary encapsulated state switching function, and linking the secondary encapsulated state switching function to the public library of the adaptive automotive open system architecture.

[0021] In this embodiment of the application, compiling the secondary encapsulation program linked to the public library of the adaptive vehicle open system architecture to generate a dynamic library or a static library includes: compiling the state switching function of the secondary encapsulation linked to the public library of the adaptive vehicle open system architecture to generate a dynamic library or a static library of the state management component.

[0022] In this embodiment of the application, the software functional requirements include health management component requirements; the step of configuring the host computer based on the software functional requirements and generating configuration files and framework code includes: configuring the host computer based on the health management component requirements and generating configuration files and framework code for the health management component.

[0023] In this embodiment, the framework code of the health management component includes monitoring functions; the secondary encapsulation of the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive automotive open system architecture, includes: secondary encapsulating the monitoring functions according to the monitoring method of the health management component to generate secondary encapsulated monitoring functions, and linking the secondary encapsulated monitoring functions to the public library of the adaptive automotive open system architecture.

[0024] In this embodiment of the application, compiling the secondary encapsulation program linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library includes: compiling the monitoring function of the secondary encapsulation linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library of the health management component.

[0025] In this embodiment of the application, the method further includes: verifying whether the integrated business program meets the expected requirements; if not, re-analyzing the corresponding software functional requirements, returning to the step of obtaining the software functional requirements of the business program for the adaptive automotive open system architecture, until the integrated business program meets the expected requirements.

[0026] A second aspect of this application provides an apparatus for adapting an open system architecture for automobiles to complex application software, the apparatus comprising:

[0027] The acquisition module is used to acquire the software functional requirements of the business program for the adaptive car open system architecture;

[0028] The configuration module is used to configure the host computer based on the software functional requirements, and generate configuration files and framework code;

[0029] The encapsulation module is used to perform secondary encapsulation on the framework code, generate a secondary encapsulated program, and link the secondary encapsulated program to the public library of the adaptive vehicle open system architecture.

[0030] The first compilation module is used to compile the secondary encapsulation program linked to the public library of the adaptive vehicle open system architecture, and generate dynamic or static libraries.

[0031] The linking module is used to link the business program to the dynamic library or static library;

[0032] The second compilation module is used to compile the business programs linked to the dynamic library or static library to generate the integrated business programs;

[0033] The deployment module is used to deploy the integrated business program to a folder in the target file system in accordance with the Adaptive Automotive Open System Architecture Specification.

[0034] A third aspect of this application provides a processor configured to execute the above-described method for adapting complex application software to an adaptive automotive open system architecture.

[0035] A fourth aspect of this application provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the aforementioned method for adapting complex application software to an adaptive automotive open system architecture.

[0036] Compared with the prior art, the above-mentioned technical solution of the present invention has the following beneficial effects:

[0037] (1) This invention repackages the framework program generated by the functional components of the AutosarAP (Autonomous Automotive Open System Architecture) and links it to the public library of the AutosarAP, so that the business program can have the functions of the AutosarAP without making a lot of modifications, which can meet the current needs of multi-threaded parallel development.

[0038] (2) The present invention has the advantages of high flexibility, low difficulty in function integration, comprehensive functions and fast response speed.

[0039] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description

[0040] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings:

[0041] Figure 1 A schematic diagram of a software architecture according to an embodiment of this application is shown.

[0042] Figure 2 This illustration schematically shows the program architecture for adapting business procedures to an adaptive automotive open system according to an embodiment of this application;

[0043] Figure 3 The illustration shows a flowchart of a method for adapting an adaptive automotive open system architecture to complex application software according to an embodiment of this application;

[0044] Figure 4 This illustration schematically shows an overall flow diagram of a method for adapting an adaptive automotive open system architecture to complex application software according to an embodiment of this application;

[0045] Figure 5 This schematically illustrates a structural block diagram of an apparatus for adapting complex application software to an adaptive automotive open system architecture according to an embodiment of this application;

[0046] Figure 6 The diagram illustrates the internal structure of a computer device according to an embodiment of this application. Detailed Implementation

[0047] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for illustration and explanation of the embodiments of this application and are not intended to limit the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0048] The following are the terms used in this embodiment:

[0049] AP: Adaptive Platform Autosar, or AutosarAP for short.

[0050] EM: Execution Management Component.

[0051] SM: State Management Component.

[0052] PHM: Health Management Component.

[0053] TestDemo: Business application.

[0054] Figure 1 A schematic diagram illustrating a software architecture according to an embodiment of this application is shown. Figure 1 As shown, the first step is to list the required execution management components (EM), state management components (SM), and health management components (PHM) based on the business application TestDemo. For the requirements of the business application TestDemo, the Adaptive Platform Autosar (AutosarAP) host computer is configured to generate configuration JSON files and code framework files. The configuration JSON file specifies the corresponding software startup sequence, software function group division, and software monitoring item design. After the code framework is repackaged and compiled into a library for the business application to call, the business application can call the corresponding encapsulated API functions (the repackaged program) according to its needs to implement the designed functions of the execution management components (EM), state management components (SM), and health management components (PHM).

[0055] Figure 2 This illustration schematically depicts the program architecture for adapting business procedures to an adaptive automotive open system according to an embodiment of this application. For example... Figure 2 As shown, the program architecture lists the application functions included in the business program: Execution Management Component (EM), Status Management Component (SM), and Health Management Component (PHM). The Execution Management Component (EM) includes functions for reporting program execution and program termination. The Status Management Component (SM) includes state switching functions, with switching methods including single-in trigger mode, single-out trigger mode, and in-out trigger mode. The Health Management Component (PHM) includes active monitoring, cutoff monitoring, logical monitoring, and health channel monitoring. The cutoff monitoring method includes cutoff start point functions and cutoff end point functions; the logical monitoring method includes logical reporting functions 1 to N.

[0056] Figure 3 This illustration schematically depicts a flowchart of a method for adapting complex application software to an adaptive automotive open system architecture according to an embodiment of this application. Figure 3 As shown, in one embodiment of this application, a method for adapting an adaptive automotive open system architecture to complex application software is provided. This embodiment mainly applies this method to the above-mentioned... Figure 1 Taking the host computer in the example, the following steps are included:

[0057] Step 110: Obtain the software functional requirements of the business program for the adaptive car open system architecture.

[0058] In this embodiment, it is necessary to analyze the software functional requirements of the business code for AutosarAP, and based on these requirements, divide them into requirements for various sub-functions belonging to AutosarAP, such as the Execution Management Component (EM), State Management Component (SM), and Health Management Component (PHM). Therefore, the software functional requirements of the business program for the adaptive automotive open system architecture include requirements for the Execution Management Component (EM), the State Management Component (SM), and the Health Management Component (PHM).

[0059] Step 120: Configure the host computer based on the software functional requirements to generate configuration files and framework code.

[0060] In this embodiment, for the Execution Management Component (EM) requirement, the host computer is configured based on the EM requirement to generate the EM configuration file and the EM framework code. For the State Management Component (SM) requirement, the host computer is configured based on the State Management Component requirement to generate the State Management Component configuration file and the State Management Component framework code. For the Health Management Component (PHM) requirement, the host computer is configured based on the Health Management Component requirement to generate the Health Management Component configuration file and the Health Management Component framework code.

[0061] Step 130: Perform secondary encapsulation on the framework code to generate a secondary encapsulated program, and link the secondary encapsulated program to the public library of the Adaptive Automotive Open System Architecture.

[0062] In this embodiment, the framework code includes the framework code of the Execution Management Component (EM), the framework code of the Status Management Component (SM), and the framework code of the Health Management Component (PHM).

[0063] The framework code for the Execution Management Component (EM) includes functions for reporting status. For example... Figure 4 As shown, for the Execution Management Component (EM) requirement, when a business application needs to integrate the function of reporting runtime status, the reporting status function is re-encapsulated (i.e., refactored) to generate a re-encapsulated reporting status function, which is then linked to the public library of the Adaptive Automotive Open System Architecture. The method also includes modifying a portion of the EM's configuration file (i.e., the JSON configuration file) based on the business application's attributes (the application's name) to obtain a new EM configuration file.

[0064] The framework code for the State Management Component (SM) includes state transition functions. For example... Figure 4As shown, for the State Management Component (SM) requirement, it is necessary to statistically analyze the switching function requirements and switching methods of functional groups. When a business application needs to integrate state switching functionality, the state switching function is re-encapsulated (i.e., the state switching function is refactored) to generate a re-encapsulated state switching function, which is then linked to the public library of the Adaptive Automotive Open System Architecture. The method also includes modifying a portion of the State Management Component's configuration file (i.e., the JSON configuration file) based on the business application's attributes (the name of the business application) to obtain a new configuration file for the State Management Component.

[0065] The framework code for the Health Management Component (PHM) includes monitoring functions. For example... Figure 4 As shown, for the Health Management Component (PHM) requirement, it is necessary to statistically analyze the monitoring methods of the PHM component, and then re-encapsulate (i.e., refactor) the monitoring functions based on these methods to generate a re-encapsulated monitoring function. This re-encapsulated monitoring function is then linked to the public library of the Adaptive Automotive Open System Architecture. The method also includes modifying a portion of the PHM component's configuration file (i.e., the JSON configuration file) based on the business program's attributes (the name of the business program) to obtain a new configuration file for the PHM component.

[0066] The monitoring methods of the health management component, i.e., the program's execution methods, include two types: single-run and persistent execution. If the program is a single-run, the underlying AP framework program is directly encapsulated to form a new API function. If the program is persistent, such as the live monitoring of the health management component (PHM), the process library is linked, and the API function is encapsulated according to functional design requirements. When the function is called, the API function creates a thread to continuously run PHM monitoring.

[0067] For the Deadline and Logical monitoring items of the Health Management Component (PHM), the business program needs to execute different programs at different branches and nodes. The functional functions are encapsulated into a mechanism with parameters, and different operations are performed according to the data passed in the parameters. This constitutes the reporting of the start and end points of the Deadline, and the reporting of branches 1, ..., N of the Logical. The above-mentioned encapsulated program is linked to the common library of the Status Management Component (SM) in the Autosar AP, and the encapsulated program is compiled to generate a static library or a dynamic library of the Status Management Component (SM).

[0068] Step 140: Compile the secondary encapsulation program linked to the public library of the Adaptive Vehicle Open System Architecture to generate a dynamic library or a static library.

[0069] In this embodiment, the secondary encapsulated program includes a secondary encapsulated status reporting function, a secondary encapsulated state switching function, and a secondary encapsulated monitoring function. For the Execution Management Component (EM) requirement, the secondary encapsulated status reporting function linked to the Adaptive Automotive Open System Architecture public library is compiled to generate a dynamic or static library for the Execution Management Component. For the State Management Component (SM) requirement, the secondary encapsulated state switching function linked to the Adaptive Automotive Open System Architecture public library is compiled to generate a dynamic or static library for the State Management Component. For the Health Management Component (PHM) requirement, the secondary encapsulated monitoring function linked to the Adaptive Automotive Open System Architecture public library is compiled to generate a dynamic or static library for the Health Management Component.

[0070] Step 150: Link the business program to the dynamic library or static library.

[0071] In this embodiment, linking the business program to the dynamic or static library allows the business program to call the secondary encapsulated program, which is essentially a secondary encapsulated API function. The business program can then call the corresponding secondary encapsulated API function to implement the functions designed for the Execution Management Component (EM), State Management Component (SM), and Health Management Component (PHM).

[0072] Step 160: Compile the business program linked to the dynamic library or static library to generate the integrated business program.

[0073] Step 170: Deploy the integrated business program to a folder in the target file system in accordance with the Adaptive Automotive Open System Architecture Specification.

[0074] Figure 3 This is a flowchart illustrating a method for adapting an adaptive automotive open system architecture to complex application software in one embodiment. It should be understood that, although... Figure 3 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 3 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0075] In one embodiment, such as Figure 5As shown, an apparatus for adapting an adaptive automotive open system architecture to complex application software is provided, including an acquisition module 210, a configuration module 220, an encapsulation module 230, a first compilation module 240, a linking module 250, a second compilation module 260, and a deployment module 270, wherein:

[0076] The acquisition module 210 is used to acquire the software functional requirements of the business program for the adaptive car open system architecture.

[0077] Configuration module 220 is used to configure the host computer based on the software functional requirements and generate configuration files and framework code.

[0078] The encapsulation module 230 is used to perform secondary encapsulation on the framework code, generate a secondary encapsulated program, and link the secondary encapsulated program to the public library of the adaptive vehicle open system architecture.

[0079] The first compilation module 240 is used to compile programs that are secondary encapsulated and linked to the public library of the Adaptive Vehicle Open System Architecture, generating dynamic or static libraries.

[0080] Link module 250 is used to link the business program to the dynamic library or static library.

[0081] The second compilation module 260 is used to compile the business programs linked to the dynamic library or static library to generate the integrated business programs.

[0082] Deployment module 270 is used to deploy the integrated business program to a folder in the target file system in accordance with the Adaptive Automotive Open System Architecture specification.

[0083] The device for adapting complex application software to the adaptive automotive open system architecture includes a processor and a memory. The aforementioned acquisition module 210, configuration module 220, encapsulation module 230, first compilation module 240, linking module 250, second compilation module 260, and deployment module 270 are all stored in the memory as program units. The processor executes the aforementioned program modules stored in the memory to implement the corresponding functions.

[0084] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and adjusting kernel parameters allows for methods to adapt the open system architecture of an automotive system to complex application software.

[0085] The memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0086] This application provides a storage medium storing a program that, when executed by a processor, implements the aforementioned method for adapting complex application software to an adaptive automotive open system architecture.

[0087] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 6 As shown in the figure, the computer device includes a processor A01, a network interface A02, a display screen A04, an input device A05, and a memory (not shown) connected via a system bus. The processor A01 provides computing and control capabilities. The memory includes internal memory A03 and a non-volatile storage medium A06. The non-volatile storage medium A06 stores an operating system B01 and a computer program B02. The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 stored in the non-volatile storage medium A06. The network interface A02 is used for communication with external terminals via a network connection. When the computer program is executed by the processor A01, it implements a method for adapting complex application software to an adaptive automotive open system architecture. The display screen A04 can be a liquid crystal display (LCD) or an e-ink display. The input device A05 can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0088] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0089] In one embodiment, the apparatus for adapting complex application software to an adaptive automotive open system architecture provided in this application can be implemented as a computer program, which can be implemented in, for example... Figure 6 The computer device shown runs on this system. The computer device's memory can store various program modules that constitute the device for adapting complex application software to the adaptive vehicle open system architecture, for example... Figure 5 The diagram shows an acquisition module 210, a configuration module 220, an encapsulation module 230, a first compilation module 240, a linking module 250, a second compilation module 260, and a deployment module 270. The computer program comprised of these modules causes the processor to execute the steps of the methods for adapting complex application software to an adaptive automotive open system architecture, as described in the various embodiments of this application.

[0090] Figure 6 The computer device shown can be used as follows Figure 5 The acquisition module 210 in the device for adapting complex application software to an adaptive automotive open system architecture, as shown, executes step 110. The computer device can execute step 120 via the configuration module 220. The computer device can execute step 130 via the encapsulation module 230. The computer device can execute step 140 via the first compilation module 240. The computer device can execute step 150 via the link module 250. The computer device can execute step 160 via the second compilation module 260. The computer device can execute step 170 via the deployment module 270.

[0091] This application provides a device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs the following steps:

[0092] Step 110: Obtain the software functional requirements of the business program for the adaptive car open system architecture.

[0093] Step 120: Configure the host computer based on the software functional requirements to generate configuration files and framework code.

[0094] Step 130: Perform secondary encapsulation on the framework code to generate a secondary encapsulated program, and link the secondary encapsulated program to the public library of the Adaptive Automotive Open System Architecture.

[0095] Step 140: Compile the secondary encapsulation program linked to the public library of the Adaptive Vehicle Open System Architecture to generate a dynamic library or a static library.

[0096] Step 150: Link the business program to the dynamic library or static library.

[0097] Step 160: Compile the business program linked to the dynamic library or static library to generate the integrated business program.

[0098] Step 170: Deploy the integrated business program to a folder in the target file system in accordance with the Adaptive Automotive Open System Architecture Specification.

[0099] In one embodiment, the method further includes: modifying the configuration file according to the attributes of the business program to obtain a new configuration file.

[0100] In this embodiment, the generated JSON configuration file can be modified according to the name of the business program to ensure that the JSON configuration file is consistent with the business program's binary file. When the execution management component (EM), status management component (SM), and health management component (PHM) run, they can perform corresponding operations based on the JSON configuration file. Taking the execution management component (EM) as an example, after reading the JSON configuration file, it will correctly launch the business program according to the functional group division. Similarly, the health management component (PHM) can correctly monitor the execution status of the business program.

[0101] In one embodiment, the software functional requirements include execution management component requirements; configuring the host computer based on the software functional requirements to generate configuration files and framework code includes: configuring the host computer based on the execution management component requirements to generate configuration files and framework code for the execution management component.

[0102] In one embodiment, the framework code of the execution management component includes a status reporting function; the secondary encapsulation of the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive automotive open system architecture, includes: when the business program needs to integrate the function of reporting running status, performing secondary encapsulation of the status reporting function to generate a secondary encapsulated status reporting function, and linking the secondary encapsulated status reporting function to the public library of the adaptive automotive open system architecture.

[0103] In one embodiment, compiling the secondary encapsulation program linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library includes: compiling the reporting status function of the secondary encapsulation linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library of the execution management component.

[0104] In one embodiment, the software functional requirements include state management component requirements; configuring the host computer based on the software functional requirements and generating configuration files and framework code includes: configuring the host computer based on the state management component requirements and generating configuration files and framework code for the state management component.

[0105] In one embodiment, the framework code of the state management component includes a state switching function; the secondary encapsulation of the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive automotive open system architecture, includes: when the business program needs to integrate the state switching function, performing secondary encapsulation of the state switching function to generate a secondary encapsulated state switching function, and linking the secondary encapsulated state switching function to the public library of the adaptive automotive open system architecture.

[0106] In one embodiment, compiling the secondary encapsulation program linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library includes: compiling the state switching function of the secondary encapsulation linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library of the state management component.

[0107] In one embodiment, the software functional requirements include health management component requirements; configuring the host computer based on the software functional requirements to generate configuration files and framework code includes: configuring the host computer based on the health management component requirements to generate configuration files and framework code for the health management component.

[0108] In one embodiment, the framework code of the health management component includes monitoring functions; the secondary encapsulation of the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive automotive open system architecture, includes: secondary encapsulating the monitoring functions according to the monitoring method of the health management component to generate secondary encapsulated monitoring functions, and linking the secondary encapsulated monitoring functions to the public library of the adaptive automotive open system architecture.

[0109] In one embodiment, compiling the secondary encapsulation program linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library includes: compiling the monitoring function of the secondary encapsulation linked to the public library of the Adaptive Automotive Open System Architecture to generate a dynamic library or a static library of the health management component.

[0110] In one embodiment, the method further includes: verifying whether the integrated business program meets the expected requirements; if not, re-analyzing the corresponding software functional requirements, returning to the step of obtaining the software functional requirements of the business program for the adaptive automotive open system architecture, until the integrated business program meets the expected requirements.

[0111] In this embodiment, after the business program is successfully compiled and the linking and compilation library of the business program is normal, it is verified whether the integrated business program meets the expected requirements. If it does not meet the requirements, the corresponding software requirements are re-analyzed, and the corresponding AutosarAP business program library is reconstructed with reference to the above process in steps 110 to 170, so as to achieve the purpose of meeting the requirements of the business program.

[0112] This application provides a method and apparatus for adapting an adaptive automotive open system architecture to complex application software. By re-encapsulating the framework program generated by the AutosarAP functional components and linking it to the public library of AutosarAP, the business program can have the functionality of AutosarAP without extensive modifications. This can meet the current needs of multi-threaded parallel development. At the same time, this method has the advantages of high flexibility, low difficulty in functional integration (the business logic does not need to know too much about the underlying implementation of Autosar), comprehensive functions, and fast response speed.

[0113] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0114] This application is described with reference to flowchart illustrations or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations or block diagrams, and combinations of blocks in the flowchart illustrations or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0115] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0116] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes or boxes Figure 1The steps of the function specified in one or more boxes.

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

[0118] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) or non-volatile memory, like read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

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

[0120] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0121] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for adapting an adaptive automotive open system architecture to complex application software, characterized in that, include: Obtain the software functional requirements of the business program for the adaptive vehicle open system architecture; Based on the aforementioned software functional requirements, the host computer is configured to generate configuration files and framework code; The framework code is then encapsulated to generate a secondary encapsulated program, which is then linked to the public library of the Adaptive Automotive Open System Architecture. Compile the secondary encapsulation program that links to the public library of the adaptive vehicle open system architecture to generate a dynamic library or a static library; Link the business program to the dynamic library or static library; The business programs linked to the dynamic or static libraries are compiled to generate the integrated business programs; The integrated business program is deployed to a folder in the target file system in accordance with the Adaptive Automotive Open System Architecture specification.

2. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 1, characterized in that, The method further includes: modifying the configuration file according to the attributes of the business program to obtain a new configuration file.

3. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 1, characterized in that, The software functional requirements include requirements for the execution management component; The configuration of the host computer based on the software functional requirements, generating configuration files and framework code, includes: Based on the requirements of the execution management component, the host computer is configured to generate the configuration file and framework code of the execution management component.

4. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 3, characterized in that, The framework code of the execution management component includes a status reporting function; The step of performing secondary encapsulation on the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive vehicle open system architecture, includes: When a business application needs to integrate the function of reporting running status, the reporting status function is encapsulated twice to generate a second encapsulated reporting status function, and the second encapsulated reporting status function is linked to the public library of the adaptive automotive open system architecture.

5. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 4, characterized in that, The compilation of the secondary encapsulation program linked to the public library of the adaptive vehicle open system architecture to generate a dynamic or static library includes: The secondary encapsulation of the reporting status function linked to the public library of the adaptive vehicle open system architecture is compiled to generate a dynamic or static library of the execution management component.

6. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 1, characterized in that, The software functional requirements include requirements for a state management component; The configuration of the host computer based on the software functional requirements, generating configuration files and framework code, includes: Based on the requirements of the state management component, the host computer is configured to generate the configuration file and framework code of the state management component.

7. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 6, characterized in that, The framework code of the state management component includes state switching functions; The step of performing secondary encapsulation on the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive automotive open system architecture, includes: When a business application needs to integrate state switching functionality, the state switching function is encapsulated a second time to generate a second-encapsulated state switching function, and the second-encapsulated state switching function is linked to the public library of the adaptive automotive open system architecture.

8. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 7, characterized in that, The compilation of the secondary encapsulation program linked to the public library of the adaptive vehicle open system architecture to generate a dynamic or static library includes: The secondary encapsulation of state switching functions linked to the public library of the adaptive vehicle open system architecture is compiled to generate a dynamic or static library of the state management component.

9. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 1, characterized in that, The software functional requirements include health management component requirements; The configuration of the host computer based on the software functional requirements, generating configuration files and framework code, includes: Based on the requirements of the health management component, the host computer is configured to generate the configuration file and framework code of the health management component.

10. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 9, characterized in that, The framework code of the health management component includes monitoring functions; The step of performing secondary encapsulation on the framework code to generate a secondary encapsulated program, and linking the secondary encapsulated program to the public library of the adaptive automotive open system architecture, includes: The monitoring function is encapsulated a second time according to the monitoring method of the health management component, and the encapsulated monitoring function is then linked to the public library of the adaptive automotive open system architecture.

11. The method for adapting complex application software to an adaptive automotive open system architecture according to claim 10, characterized in that, The compilation of the secondary encapsulation program linked to the public library of the adaptive vehicle open system architecture to generate a dynamic or static library includes: The monitoring functions that are secondary encapsulated and linked to the public library of the adaptive vehicle open system architecture are compiled to generate a dynamic or static library of the health management component.

12. The method for adapting complex application software to an adaptive automotive open system architecture according to any one of claims 1 to 11, characterized in that, The method further includes: Verify whether the integrated business program meets the expected requirements; if not, re-analyze the corresponding software functional requirements, return to the steps of obtaining the software functional requirements of the business program for the adaptive automotive open system architecture, until the integrated business program meets the expected requirements.

13. A device for adapting an adaptive automotive open system architecture to complex application software, characterized in that, The device includes: The acquisition module is used to acquire the software functional requirements of the business program for the adaptive car open system architecture; The configuration module is used to configure the host computer based on the software functional requirements, and generate configuration files and framework code; The encapsulation module is used to perform secondary encapsulation on the framework code, generate a secondary encapsulated program, and link the secondary encapsulated program to the public library of the adaptive vehicle open system architecture. The first compilation module is used to compile the secondary encapsulation program linked to the public library of the adaptive vehicle open system architecture, and generate dynamic or static libraries. The linking module is used to link the business program to the dynamic library or static library; The second compilation module is used to compile the business programs linked to the dynamic library or static library to generate the integrated business programs; The deployment module is used to deploy the integrated business program to a folder in the target file system in accordance with the Adaptive Automotive Open System Architecture Specification.

14. A processor, characterized in that, A method configured to perform an adaptive automotive open system architecture to adapt complex application software according to any one of claims 1 to 12.

15. A machine-readable storage medium storing instructions thereon, characterized in that, When executed by a processor, the instruction causes the processor to be configured to perform the method of adapting complex application software to an adaptive automotive open system architecture according to any one of claims 1 to 12.

Images