Docker container-based AUTOSAR development configuration system and configuration method

Abstract

The invention discloses an AUTOSAR development configuration system and method based on a Docker container, and the system comprises an interaction layer container which is used for the interaction between the system and a user, and comprises a user interface, an authority management interface, a configuration management interface, a code generation interface and a test interface; the application layer container is used for configuring and testing key functions of the AUTOSAR and comprises an authority management module, a configuration management module, a code generation module and a test module; and the output layer container is used for outputting the code file and the configuration file and comprises a code file output module and a configuration file output module. According to the invention, the problems of strong environmental dependence, high resource occupation, complex version management, low deployment efficiency and the like of the existing AUTOSAR development configuration tool can be improved.

Description

Technical Field

[0001] The present invention relates to the technical field of automotive electronics, and in particular to an AUTOSAR development configuration system and configuration method based on a Docker container. Background Art

[0002] As a standardized automotive electronic software architecture, the AUTomotive Open System Architecture (AUTOSAR) provides a unified platform and specifications for the development of automotive electronic systems. AUTOSAR facilitates the exchange and update of vehicle electronic system software and provides a foundation for the efficient management of increasingly complex vehicle electronic and software systems.

[0003] At present, AUTOSAR development configuration mainly relies on complex locally installed software environments, such as Vector's tool chain (such as DAI, CANoe, etc.). These tools provide a complete solution for the development of automotive electronic control systems, including software architecture design, application software development, ECU software integration and verification, etc. However, the use of these tools usually requires installation and configuration on specific operating systems (such as Windows or Linux) and hardware platforms. For example, Vector's tool chain requires users to install multiple software components on the local computer, including development environment, debugging tools, communication protocol stack, etc., and requires complex configuration according to project requirements. In addition, existing AUTOSAR development configuration tools usually need to be used in conjunction with specific hardware devices (such as simulators, debuggers), further increasing the complexity of the development environment. Although this development method that relies on the local environment is more comprehensive in terms of functionality, it has obvious shortcomings in flexibility, portability and resource utilization efficiency. Summary of the Invention

[0004] In view of the shortcomings of the existing technology, the present invention provides an AUTOSAR development configuration system and configuration method based on Docker containers.

[0005] The technical solution adopted by the present invention to solve its technical problem is:

[0006] In a first aspect, the present invention provides an AUTOSAR development and configuration system based on a Docker container, comprising:

[0007] The interactive layer container is used for interaction between the system and the user, including: user interface, permission management interface, configuration management interface, code generation interface and test interface;

[0008] Application layer container, used for configuration and testing of AUTOSAR key functions, including: permission management module, configuration management module, code generation module and test module;

[0009] The output layer container is used for outputting code files and configuration files, including: code file output module and configuration file output module.

[0010] Furthermore, the user interface is the entrance for interaction between the system and the user, supports switching and operation between multiple functional modules, and supports multi-language switching; the permission management interface supports multiple authentication methods, and the system administrator can assign different permission levels to different users through the permission management interface; the configuration management interface supports users to perform AUTOSAR configuration; the code generation interface is used to convert the AUTOSAR configuration into executable code; and the test interface is used to verify the correctness of the generated AUTOSAR configuration and code.

[0011] Furthermore, the rights management module can cooperate with the rights management interface to verify the user's login credentials and operating permissions; the configuration management module is used to process the AUTOSAR configuration information input in the configuration management interface; the code generation module supports multiple programming languages ​​and code specifications and can generate corresponding code files according to the AUTOSAR configuration information; the test module can run test programs to verify the correctness of the AUTOSAR configuration and code.

[0012] Furthermore, the code file output module is used to store and export the code file generated by the application layer container; the configuration file output module is used to store and export the configuration file generated by the application layer container.

[0013] In a second aspect, the present invention provides a configuration method for an AUTOSAR development configuration system based on a Docker container, comprising the following steps:

[0014] S1. Write Docker container configuration, build Docker image, and configure Docker data;

[0015] S2. After Docker data is persisted, run the Docker container;

[0016] S3. Establish a network connection, run the user interface, log in as a user, and confirm whether the user data is updated. If so, update the Docker data and return to step S2; if not, perform graphical configuration;

[0017] S4. Confirm whether an AUTOSAR configuration file already exists. If not, generate an AUTOSAR configuration file and re-perform graphical configuration; if so, generate an AUTOSAR code file;

[0018] S5. Manage the AUTOSAR code files using git version management and store them in the cloud. Test and verify the AUTOSAR code files.

[0019] Furthermore, step S1 specifically includes:

[0020] Write the core file Dockerfile for Docker container configuration, select the base image required for system operation, install the dependency packages required for system operation in the Dockerfile file, and define the container startup command and service port in the Dockerfile file;

[0021] Use the Docker command docker build to build the Dockerfile file into a runnable Docker image. After the build is complete, the Docker image is stored in the local image repository. Users can view the image list using the Docker command docker images.

[0022] Furthermore, establishing a network connection includes:

[0023] Configure the network settings of the Docker container, assign a separate IP address to the Docker container, and expose the services inside the container to the external network through port mapping; limit the container's access to the external network by setting firewall rules and access control lists.

[0024] Furthermore, the AUTOSAR code file includes: a communication stack component, a basic software management component, a diagnostic function component and an operating system component, and each component has its own storage directory and file naming rules.

[0025] Furthermore, testing AUTOSAR code files supports both automated testing and manual testing.

[0026] The beneficial effects of the present invention are:

[0027] Containerization technology enables AUTOSAR development configuration to run on any Docker-supported platform, eliminating the need for complex local environment configuration and reducing dependence on the development environment. Leveraging the lightweight nature of Docker containers, system resource usage is reduced, improving development efficiency and resource utilization. Docker images enable versioning of tools, allowing users to quickly switch and manage different versions of development configuration tools. This enables rapid deployment and startup of development configuration tools, supporting team collaboration and continuous integration environments, and reducing development costs. Docker volume mounting enables persistent storage of configuration files and generated code, ensuring data security. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The present invention will be further described below with reference to the accompanying drawings and examples.

[0029] Figure 1 This is an architectural diagram of the AUTOSAR development and configuration system based on Docker containers of the present invention.

[0030] Figure 2 It is a flow chart of the AUTOSAR development and configuration method based on Docker container of the present invention. DETAILED DESCRIPTION

[0031] The present invention will now be described in further detail with reference to the accompanying drawings, which are simplified schematic diagrams that illustrate the basic structure of the present invention in a schematic manner.

[0032] In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, features defined as "first" or "second" may explicitly or implicitly include one or more of such features. In the description of the present invention, unless otherwise specified, "multiple" means two or more.

[0033] In the description of the present invention, it should be noted that, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood in a broad sense. For example, they may refer to fixed, detachable, or integral connections; mechanical or electrical connections; direct or indirect connections through an intermediate medium; and internal communication between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on the specific circumstances.

[0034] Example 1

[0035] like Figure 1 As shown, this embodiment provides an AUTOSAR development and configuration system based on Docker containers, including an interaction layer container, an application layer container, and an output layer container. The interaction layer container is used for system-user interaction and includes a user interface, a permissions management interface, a configuration management interface, a code generation interface, and a test interface. The application layer container is used for configuring and testing key AUTOSAR functions and includes a permissions management module, a configuration management module, a code generation module, and a test module. The output layer container is used for outputting code files and configuration files and includes a code file output module and a configuration file output module.

[0036] The following describes the various interfaces of the interaction layer container.

[0037] The user interface is the entry point for interaction between the system and the user, and its design focuses on simplicity and ease of use. The user interface supports switching and operation between multiple functional modules, allowing users to complete complex tasks through intuitive menus, buttons, and interactive elements. The user interface adopts a responsive design, adapting to screen sizes of various sizes, providing a good user experience for both desktop monitors and mobile devices. Furthermore, the interface supports multilingual switching to meet the needs of users in different regions.

[0038] In the implementation of the user interface, HTML, CSS, and JavaScript can be used to build the user interface. HTML is used to define the page structure, CSS is used for style design, and JavaScript is used to implement the interactive logic. In addition, front-end frameworks (such as React, Vue.js, or Angular) can be used to improve development efficiency and user experience. These frameworks provide a rich component library and state management tools, which can quickly build complex user interfaces. To ensure that the user interface can provide a good experience on different devices, this embodiment adopts a responsive design. By using CSS media queries and flexible layout technologies (such as Flexbox or Grid), the user interface can be adaptively laid out on devices such as desktop monitors, tablets, and mobile phones. For example, when the screen size is small, the elements of the user interface will automatically adjust their layout to accommodate the smaller screen space. Taking into account the needs of users in different regions, the user interface also supports multi-language switching. Through internationalization (i18n) technology, resources such as interface text and prompt information can be localized. Users can select the interface language according to their language preferences, and the system will dynamically load the corresponding language resource files.

[0039] In addition, the user interface can use RESTful APIs (a stateless, layered architectural style based on the HTTP protocol) to access and operate resources using URIs (Uniform Resource Identifiers). In this system, the backend service defines a series of API interfaces to process user requests and return data. For example, users can use these API interfaces to submit AUTOSAR configuration information, obtain code generation results, or query test reports. JSON or XML is used as the data transmission format. JSON is lightweight, easy to read and write, and suitable for use in web development. In this system, all API interfaces use JSON format for data transmission. The user interface uses JavaScript libraries such as fetch or axios to send HTTP requests and receive JSON data returned by the backend service. To ensure data security, the API interfaces use HTTPS for encrypted transmission. Furthermore, access control can be implemented on the API interfaces through authentication mechanisms such as OAuth 2.0 to ensure that only authorized users can call the interfaces. The API interfaces can also implement rate limiting and anti-crawling measures to prevent malicious attacks.

[0040] The permissions management interface is a core component of system security. It ensures that only authorized users can access critical system functions through user authentication and permission allocation. The permissions management interface supports multiple authentication methods, including username and password, fingerprint recognition, and facial recognition. System administrators can also use the permissions management interface to assign different permission levels to different users. For example, standard users can only view fault data, while advanced users can perform operations such as configuration management and code generation. Furthermore, the permissions management interface supports an audit log function, recording user login time, operation content, and other information for subsequent traceability and security audits.

[0041] The configuration management interface is the core area for AUTOSAR configuration. It provides a graphical operating environment where users can complete complex configuration tasks by dragging and dropping components and setting parameters. The interface supports multiple configuration templates, allowing users to quickly select the appropriate template for different application scenarios. Furthermore, the interface supports real-time parameter validation. If a user-entered parameter does not meet specifications, the system will immediately display an error message and provide the correct input format. Users can save configuration parameters for future reuse and load saved configuration files for modification and update.

[0042] In the implementation of the configuration management interface, the configuration management interface adopts a graphical drag-and-drop and parameter filling method. Users can complete the configuration by dragging components to the workspace and filling in the parameters of the components. The configuration management interface provides a rich component library, including hardware interface components, communication protocol components, and diagnostic function components. Users can set parameters such as baud rate, address, and diagnostic code through the component's property panel. To ensure that the user-input configuration parameters are correct, the configuration management interface supports real-time verification. When the user inputs parameters, the system immediately checks whether the parameters meet the specifications and displays the verification results on the configuration management interface. If the parameters are incorrect, the system will prompt the user with the error reason and provide the correct input format. For example, if the user inputs a baud rate that is not within the allowed range, the system will prompt the user to input the correct baud rate value. To improve configuration efficiency, the system provides multiple preset configuration templates. Users can select the appropriate template based on their application scenarios and modify and extend it. The template contains common configuration parameters and component combinations, allowing users to quickly complete the configuration through simple modifications. After the user completes the configuration, they can save the configuration parameters to the local or server through the interface's save button. The saved configuration file is in a structured format (such as JSON or XML), making it easy to read and modify later. The system supports configuration version management, allowing users to assign version numbers and description information to each saved configuration file, facilitating subsequent version comparison and rollback operations. Users can also import previously saved configuration files through the configuration management interface's load button. The system will automatically parse the configuration file and restore the configuration parameters to the interface, allowing users to continue modifying and extending them. The load function supports multiple file formats, including local files and server files. Users can also export configuration files in various formats, such as JSON, XML, or CSV, through the configuration management interface's export button. The exported configuration files can be used for backup, sharing, or integration with other systems. The export function also supports customizing the exported content, allowing users to select part or all of the configuration parameters based on their needs.

[0043] The code generation interface is used to convert AUTOSAR configurations into executable code. After completing the AUTOSAR configuration, users can generate code through the code generation interface. The code generation interface provides a detailed code generation progress bar and log information, allowing users to monitor the progress and status of code generation in real-time. The generated code files are stored in different components for easy viewing and downloading. In addition, the code generation interface supports code preview functionality, allowing users to view the structure and content of the code directly after generation, ensuring that the generated code meets expectations.

[0044] The test interface is an essential tool for verifying the correctness of generated AUTOSAR configurations and code. It offers a wide range of testing capabilities, including both automated and manual testing modes. The automated testing module automatically runs the test process based on pre-set test cases and generates detailed test reports, including information such as the pass rate and failure reasons. The manual testing mode allows users to customize test scenarios, simulating actual operating environments to verify the functionality of the configuration and code. The test interface also supports saving and exporting test results. Users can export test reports to PDF or Excel formats for subsequent analysis and documentation.

[0045] The following describes each module of the application layer container.

[0046] The permissions management module is the security mechanism for the application layer container. Working closely with the permissions management interface of the interaction layer container, the permissions management module verifies user login credentials and operational permissions. When a user attempts to access system functions, the permissions management module verifies their permission level in real time and only allows them to proceed if their permissions allow. Furthermore, the permissions management module supports dynamic permission adjustment, allowing system administrators to adjust user permissions in real time based on system performance, ensuring system security. The permissions management module also works in conjunction with the audit log module to record user operations and provide data support for security audits.

[0047] The configuration management module is one of the core functions of the application layer container, and is used to process the AUTOSAR configuration information entered in the configuration management interface. The configuration management module supports the setting of multiple configuration parameters, including but not limited to hardware interface parameters, communication protocol parameters, diagnostic function parameters, etc. The configuration management module can parse and verify the configuration information entered by the user to ensure the integrity and correctness of the configuration. The configuration management module also supports configuration version management. Users can create multiple configuration versions and switch and compare between different versions. In addition, the configuration management module can save the configuration information in a structured file format to facilitate subsequent code generation and test verification.

[0048] The code generation module is a key function of the application layer container. The code generation module generates the corresponding code files based on the AUTOSAR configuration information entered by the user. The code generation module supports multiple programming languages ​​and code specifications and can generate high-quality, maintainable code. During the code generation process, the code generation module will dynamically generate a code framework based on the configuration information and fill in the specific implementation logic. To improve the readability and maintainability of the code, the code generation module also supports code formatting and comment generation functions. The generated code files will be classified and stored according to different components. For example, the code of components such as ComStack, BswM, Diagnostic and OS will be stored in different directories. In addition, the code generation module also supports incremental code updates. When the user makes small modifications to the configuration, the code generation module can only generate the code for the modified part, improving the efficiency of code generation.

[0049] Regarding code generation, the code generation module dynamically generates code based on the parameters entered by the user in the configuration management interface. The generated code includes multiple components, such as the Com Stack (communication stack component), BswM (basic software management component), Diagnostic (diagnostic function component), and OS (operating system component). The code generation module supports code formatting and optimization to improve code readability and maintainability. Generated code files are stored by component: for example, Com Stack code is stored in the com_stack directory, and BswM code is stored in the bswm directory. Each component's code file has a clear directory structure and file naming conventions, making it easy to find and use. The code files also include detailed comments explaining the code's functionality and implementation logic. The code formatting function formats the generated code according to preset formatting rules. For example, it adjusts code indentation, spacing, and line breaks to make the code more neat and readable. Formatting rules can be customized based on user preferences, such as selecting different indentation methods (spaces or tabs) and line width limits. The code optimization feature optimizes the generated code by removing redundant code, merging similar code blocks, and optimizing variable naming. These optimizations can improve code efficiency and maintainability. The code optimization feature also supports custom optimization rules.

[0050] The test module is a functional module in the application layer container used to verify the correctness of the AUTOSAR configuration and code. The test module supports both automated and manual testing modes to meet the needs of different users. The automated test mode automatically runs the test process according to preset test cases. The test cases cover a variety of common scenarios and boundary conditions, and can fully verify the configuration and code functionality. The test module generates a detailed test report, including information such as test pass rate, failure reasons, and test coverage. The manual test mode allows users to customize test scenarios and verify the configuration and code functionality by simulating the actual operating environment. The test module also supports saving and exporting test results. Users can export test reports to PDF or Excel format for subsequent analysis and recording.

[0051] The following describes each module of the output layer container.

[0052] The code file output module is used to store and export the code files generated by the application layer container. The generated code files are classified and stored according to different components. For example, the codes of components such as Com Stack, BswM, Diagnostic and OS are stored in different directories. Each code file is accompanied by detailed comments and documentation to facilitate user understanding and use. The code file output module supports export in multiple file formats. Users can choose to export code files as source code files, compressed package files, or installation package files. In addition, the code file output module also supports code version management. Users can view different versions of code files and perform version comparison and rollback operations.

[0053] The configuration file output module is used to store and export configuration files generated by the application layer container. The generated configuration files are stored in a structured file format, such as XML, JSON, or YAML. The configuration file contains the configuration information entered by the user in the interaction layer container, as well as the parsing and processing results of the configuration information by the application layer container. The configuration file output module supports exporting in multiple file formats. Users can choose to export the configuration file as a text file, compressed file, or database file. In addition, the configuration file output module also supports configuration version management, allowing users to view different versions of the configuration file and perform version comparison and rollback operations.

[0054] Example 2

[0055] like Figure 2 As shown, this embodiment provides a configuration method for an AUTOSAR development configuration system based on a Docker container, comprising the following steps:

[0056] S1. Write Docker container configuration, build Docker image, and configure Docker data.

[0057] S2, after Docker data persistence processing, running Docker container.

[0058] S3, establishing network connection, running user interface, user identity login, confirming whether user data is updated, if yes, carrying out Docker data update and returning to step S2; if no, carrying out graphical configuration.

[0059] S4, confirming whether AUTOSAR configuration file exists, if no, generating AUTOSAR configuration file and re-performing graphical configuration; if yes, generating AUTOSAR code file.

[0060] S5, carrying out git version management to AUTOSAR code file and storing in cloud, and testing and verifying AUTOSAR code file.

[0061] It should be noted that the Docker container is an open source application container engine, which allows developers to package their applications and dependent packages into a portable container in a unified manner, and then publish to any server installed with docker engine (including popular Linux machines, windows machines), and also can realize virtualization.

[0062] Step S1 specifically comprises: writing core file Dockerfile of Docker container configuration, selecting basic image required by system running, installing dependent package required by system running in the Dockerfile file, defining startup command and service port of the container in the Dockerfile file. The Dockerfile file is built into a runnable Docker image through the Docker command docker build, after the construction is completed, the Docker image is stored in the local image warehouse, and the user views the image list through the Docker command docker images.

[0063] More specifically, the Dockerfile is the core file for configuring a Docker container. It defines the container's operating environment, installed dependencies, and enabled services. When writing a Dockerfile, you need to select an appropriate base image based on the system's operating requirements, such as Ubuntu or CentOS. Then, install the required dependencies, such as the programming language environment, database server, and development tools, in the Dockerfile. Furthermore, you need to define the container's startup commands and service ports to ensure the container can start properly and provide external services. Once written, you can use the Docker command docker build to build the Dockerfile into a Docker image. The image contains all the necessary environment and tools to run the system. Building a Docker image is the process of converting a Dockerfile into a runnable Docker image. The Docker command docker build allows you to build the image step by step according to the instructions in the Dockerfile. During the build process, Docker will install dependencies, copy files, and set environment variables according to the steps specified in the Dockerfile. After the build is complete, the generated Docker image is stored in the local image repository, and users can view the image list using the Docker command docker images. In addition, you can also push the built image to public image repositories such as Docker Hub to facilitate deployment and operation on different machines.

[0064] Running a Docker container is the process of running a Docker image. Using the Docker command docker run, you can specify parameters such as the image name, port mappings, and volume mounts to start the container. When starting a Docker container, you can use volume mounts to store data within the container.

[0065] Establishing a network connection involves configuring the Docker container's network settings to support communication with external systems (such as Git repositories, emulated devices, etc.). Multiple network modes are supported, including bridge, host, and overlay. In this system, bridge networking is preferred because it provides an isolated network environment for the container while allowing it to communicate with the external network. By configuring Docker's network settings, each container can be assigned a unique IP address and services within the container can be exposed to the external network through port mapping. To communicate with the Git repository, the container must be able to access the external network. Configuring Docker's network settings ensures that the container can interact with the Git repository using HTTP or HTTPS. For example, users can use the Git client within the container to clone the repository, push code, or pull the latest code version. For emulated devices, the container can communicate with the emulated device using TCP / IP, receiving simulation data or sending control commands. Security is a key consideration when configuring the network. By setting firewall rules and access control lists (ACLs), you can restrict the container's access to the external network, allowing only necessary communication traffic. In addition, encryption protocols (such as TLS / SSL) can be used to protect the security of data during transmission to prevent data leakage or tampering.

[0066] By using the version management of Docker images, you can support the rapid switching and deployment of different versions of development configuration tools.

[0067] In summary, the AUTOSAR development and configuration system and configuration method based on Docker containers of the present invention have the following advantages:

[0068] Environment independence: Through containerization technology, the AUTOSAR development configuration tool can run on any platform that supports Docker containers, eliminating the need for complex local environment configuration. This eliminates the development configuration tool's dependence on the local development environment and lowers the development threshold.

[0069] Efficient deployment: Leveraging the portability of Docker images, users can quickly deploy and switch between different versions of development configuration tools, improving development efficiency.

[0070] Resource optimization: Containerized development and configuration tools take up fewer resources and start up faster, further improving development efficiency.

[0071] Data security: Docker volume mounting enables persistent storage of configuration files and generated code, ensuring data security.

[0072] Team collaboration-friendly: supports multi-project development and team collaboration, is easy to use in a continuous integration environment, and improves team collaboration efficiency.

[0073] Cross-platform support: Due to the cross-platform nature of Docker, this invention supports running on multiple operating systems such as Windows, Linux, and macOS, further reducing environmental dependence.

[0074] With the above-described preferred embodiments of the present invention as a guide, and with reference to the above description, relevant personnel are fully capable of making various changes and modifications without departing from the technical spirit of this invention. The technical scope of this invention is not limited to the contents of the specification, but must be determined according to the scope of the claims.

Claims

1. An AUTOSAR development and configuration system based on Docker containers, characterized in that: include: The interactive layer container is used for interaction between the system and the user, including: user interface, permission management interface, configuration management interface, code generation interface and test interface; Application layer container, used for configuration and testing of AUTOSAR key functions, including: permission management module, configuration management module, code generation module and test module; The output layer container is used for outputting code files and configuration files, including: code file output module and configuration file output module.

2. The AUTOSAR development and configuration system based on Docker container according to claim 1, characterized in that: The user interface is the entrance for interaction between the system and the user, supporting switching and operation between multiple functional modules and supporting multi-language switching; The rights management interface supports multiple authentication methods, and the system administrator can assign different rights levels to different users through the rights management interface; The configuration management interface supports users to perform AUTOSAR configuration; The code generation interface is used to convert the AUTOSAR configuration into executable code; The test interface is used to verify the correctness of the generated AUTOSAR configuration and code.

3. The AUTOSAR development and configuration system based on Docker container according to claim 1, characterized in that: The rights management module can cooperate with the rights management interface to verify the user's login credentials and operating permissions; The configuration management module is used to process the AUTOSAR configuration information input by the configuration management interface; The code generation module supports multiple programming languages ​​and code specifications, and can generate corresponding code files according to AUTOSAR configuration information; The test module can run test programs to verify the correctness of AUTOSAR configuration and code.

4. The AUTOSAR development and configuration system based on Docker container according to claim 1, characterized in that: The code file output module is used to store and export the code file generated by the application layer container; The configuration file output module is used to store and export the configuration file generated by the application layer container.

5. A configuration method for an AUTOSAR development configuration system based on a Docker container according to any one of claims 1 to 4, characterized in that: The following steps are involved: S1. Write Docker container configuration, build Docker image, and configure Docker data; S2. After Docker data is persisted, run the Docker container; S3. Establish a network connection, run the user interface, log in as a user, and confirm whether the user data is updated. If so, update the Docker data and return to step S2; if not, perform graphical configuration; S4. Confirm whether an AUTOSAR configuration file already exists. If not, generate an AUTOSAR configuration file and re-perform graphical configuration; if so, generate an AUTOSAR code file; S5. Manage the AUTOSAR code files using git version management and store them in the cloud. Test and verify the AUTOSAR code files.

6. The configuration method of the AUTOSAR development configuration system based on the Docker container according to claim 5, characterized in that: Step S1 specifically includes: Write the core file Dockerfile for Docker container configuration, select the base image required for system operation, install the dependency packages required for system operation in the Dockerfile file, and define the container startup command and service port in the Dockerfile file; Use the Docker command docker build to build the Dockerfile file into a runnable Docker image. After the build is complete, the Docker image is stored in the local image repository. Users can view the image list using the Docker command docker images.

7. The configuration method of the AUTOSAR development configuration system based on the Docker container according to claim 5, characterized in that: Establishing a network connection involves: Configure the network settings of the Docker container, assign a separate IP address to the Docker container, and expose the services inside the container to the external network through port mapping; limit the container's access to the external network by setting firewall rules and access control lists.

8. The configuration method of the AUTOSAR development configuration system based on the Docker container according to claim 5, characterized in that: The AUTOSAR code file includes: a communication stack component, a basic software management component, a diagnostic function component and an operating system component, and each component has its own storage directory and file naming rules.

9. The configuration method of the AUTOSAR development configuration system based on the Docker container according to claim 5, characterized in that: Testing AUTOSAR code files supports both automated testing and manual testing.

Images