Parameter data processing method and device, equipment, medium and product
By introducing a management model of general configuration repository and project configuration repository into the intelligent driving system, combined with user permission management, the problem of inconsistent parameter management is solved, and efficient and secure parameter integration and version management are achieved, thereby improving the adaptation efficiency and maintainability of the intelligent driving system.
Patent Information
- Application Number
- CN202511102491.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-06
- Publication Date
- 2025-11-21
AI Technical Summary
The parameter management methods in existing intelligent driving systems are not efficient and flexible enough, and there is a lack of a unified parameter management system. This results in high project adaptation costs, complex version control, low integration efficiency, and limited access control, which seriously restricts the rapid iteration and large-scale deployment of intelligent driving systems.
It adopts a management model of general configuration repository and project configuration repository, and centrally manages configuration updates through user permissions, generates intelligent driving packages, realizes unified storage and management of parameters, avoids repeated modifications, and supports parallel development of multiple projects.
It significantly reduces parameter maintenance costs, improves parameter management efficiency and system maintainability, supports parallel development and efficient integration of multiple projects, and ensures configuration consistency and security.
Smart Images

Figure CN120994218A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of intelligent driving software development technology, and in particular to a method, apparatus, device, medium and product for processing parameter data. Background Technology
[0002] The intelligent driving industry, as a technological field that deeply integrates artificial intelligence and automotive engineering, is developing rapidly, gradually realizing the automated perception, decision-making, and control of vehicles. In this industry, the management of algorithms and parameters is a key link in system development and implementation. Especially in the context of collaborative development of multiple vehicle models and multiple projects, how to efficiently and accurately maintain and adapt parameters has become an important factor affecting development efficiency and product quality.
[0003] In current intelligent driving system development, a common approach is to share core algorithm code and adapt projects by independently maintaining calibration parameters. These parameters typically include a large number of shared configurations, but in practice, whether the parameters are centrally managed or distributed among various modules, each project or module often maintains its own independent parameter repository or configuration file.
[0004] However, this decentralized parameter management approach results in a lack of a unified view. Adjustments to common parameters require simultaneous modification in multiple independent repositories or modules, which is cumbersome and error-prone, significantly increasing maintenance costs and severely hindering the rapid iteration and large-scale deployment of intelligent driving systems. Summary of the Invention
[0005] The parameter data processing methods, apparatus, devices, media, and products provided in the embodiments of this application are used to improve the effect of parameter processing.
[0006] In a first aspect, embodiments of this application provide a method for processing parameter data, including:
[0007] Retrieve the target configuration parameters sent by the user;
[0008] Based on the target configuration parameters and user permissions, the configuration files in the first parameter repository in the parameter repository are updated. The parameter repository includes a general configuration repository and a project configuration repository. The general configuration repository is used to store general parameters applicable to each specific project in the intelligent driving service, and the project configuration repository is used to store personalized parameters for specific projects in the intelligent driving service. Different project configuration repositories correspond to different specific projects. The first parameter repository is either a project configuration repository or a general configuration repository.
[0009] Based on the updated first and second parameter repositories, an intelligent driving package for intelligent driving services is generated; the second parameter repository is a parameter repository in the parameter repository that corresponds to the first parameter repository but is of a different type.
[0010] In one possible implementation, the configuration file in the first parameter repository of the parameter repository is updated according to the target configuration parameters and the user's permissions, including:
[0011] Based on the user's permissions, determine the first parameter repository in the parameter repository that corresponds to the permissions;
[0012] Iterate through the first parameter repository to determine the configuration files within it;
[0013] Write the target configuration parameters to the configuration file to update the configuration file in the first parameter repository.
[0014] In one possible implementation, when the first parameter repository is a project configuration repository,
[0015] Write the target configuration parameters to the configuration file to update the configuration file in the first parameter repository, including:
[0016] Determine the parameter type of the target configuration parameter;
[0017] Based on the parameter type of the target configuration parameter, the target configuration parameters of different parameter types are written into the corresponding configuration files to update the configuration files in the first parameter repository.
[0018] In one possible implementation, based on the parameter type of the target configuration parameter, target configuration parameters of different parameter types are written into corresponding configuration files to update the configuration files in the first parameter repository, including:
[0019] If the same target configuration parameter exists in different configuration files, the target configuration parameter will be written to the configuration file that meets the priority requirement according to the priority of the configuration files, so as to update the configuration file in the first parameter repository.
[0020] In one possible implementation, the configuration file includes a base configuration file for storing basic parameters, a model configuration file for storing vehicle parameters, and a project configuration file for storing difference parameters.
[0021] Among them, the priority of the project configuration file is higher than that of the vehicle configuration file, and the priority of the vehicle configuration file is higher than that of the basic configuration file.
[0022] In one possible implementation, when the first parameter repository is a project configuration repository, the method further includes:
[0023] If the target configuration file in the project configuration repository is updated, the configuration parameters in the second parameter repository corresponding to the target configuration file will be updated based on the result of the update.
[0024] Based on the updated first and second parameter repositories, generate an intelligent driving package for intelligent driving services.
[0025] In one possible implementation, the method further includes:
[0026] In response to the user's selection action, determine the target item configuration repository in the parameter repository;
[0027] Adjust the configuration file of the target project's configuration repository based on the user's adjustment operations on the target project's configuration repository;
[0028] In response to the user's creation operation, the adjusted target project configuration repository is created in the parameter repository as the project configuration repository to be created.
[0029] Secondly, embodiments of this application provide a parameter data processing apparatus, comprising:
[0030] The acquisition module is used to acquire the target configuration parameters sent by the user.
[0031] The update module is used to update the configuration files in the first parameter repository in the parameter repository according to the target configuration parameters and the user's permissions. The parameter repository includes a general configuration repository and a project configuration repository. The general configuration repository is used to store general parameters applicable to each specific project in the intelligent driving service, and the project configuration repository is used to store personalized parameters for specific projects in the intelligent driving service. The specific projects corresponding to different project configuration repositories are different. The first parameter repository is either a project configuration repository or a general configuration repository.
[0032] The generation module is used to generate an intelligent driving package for intelligent driving services based on the updated first parameter repository and second parameter repository; the second parameter repository is a parameter repository in the parameter repository that corresponds to the first parameter repository but is of a different type.
[0033] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;
[0034] The memory stores instructions that the computer executes;
[0035] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.
[0036] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.
[0037] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.
[0038] The parameter data processing method, apparatus, device medium, and product provided in this application effectively solve the problem of fragmented views caused by decentralized parameter management by dividing the parameter repository into a general configuration repository and a project configuration repository, and centrally managing configuration updates based on user permissions. When it is necessary to adjust common parameters, only one modification needs to be made in the general configuration repository. The system can then automatically integrate this modification with the personalized parameters in each project configuration repository when generating the intelligent driving package. This avoids the tedious operation of repeated and synchronous modifications in multiple independent repositories or modules, significantly reduces the risk of errors and maintenance costs, and thus improves the effectiveness of parameter management. Attached Figure Description
[0039] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0040] Figure 1 A schematic diagram illustrating a scenario for the parameter data processing method provided in this application;
[0041] Figure 2 Flowchart of the parameter data processing method provided in this application Figure 1 ;
[0042] Figure 3 Flowchart of the parameter data processing method provided in this application Figure 2 ;
[0043] Figure 3a This is a schematic diagram of the structure of the general configuration repository provided in the embodiments of this application;
[0044] Figure 3b This is a schematic diagram of the structure of the project configuration repository provided in an embodiment of this application;
[0045] Figure 3c This is a schematic diagram of the updated file structure of the configuration file provided in an embodiment of this application;
[0046] Figure 4 A schematic diagram of the structure of the parameter data processing device provided in this application;
[0047] Figure 5 A schematic diagram of the structure of the electronic device provided in this application.
[0048] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation
[0049] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0050] First, let me explain the terms used in this application:
[0051] A parameter repository can refer to a unified storage space or directory structure used for centralized storage and management of various configuration parameters in an intelligent driving system. It can be divided into a general configuration repository and a project configuration repository based on different user permissions.
[0052] A general configuration repository can refer to a repository for storing common parameters applicable to all projects and vehicle models. These common parameters can refer to basic configuration items that can be reused in multiple projects and vehicle models without modification. They can include default parameters of core modules in the intelligent driving service and parameter data of resources such as deployment scripts shared by the project.
[0053] A project configuration repository can refer to a configuration storage space set up for specific project needs, used to store parameter configuration information related to the project. Personalized parameters can refer to parameter data that are adjusted or overridden based on general parameters according to specific project or customer needs, used to achieve purposes such as enabling functions, optimizing parameters, and adapting to specific vehicle models.
[0054] The Intelligent Driving Package refers to a complete software and parameter package automatically generated by internally configured scripts after parameter configuration and updates, used for deploying and running intelligent driving services. It may include core algorithm code, runtime configuration parameters, vehicle model adaptation information, and other information to ensure correct operation in specific projects.
[0055] In current intelligent driving system development, the commonly adopted management model is that the core algorithm shares a single codebase, while each project maintains its own calibration parameters based on vehicle model and requirements. However, there are two main approaches in existing technologies: one is centralized parameter management, where projects have no dependencies, but shared parameters need to be repeatedly maintained in multiple repositories; the other is parameter distribution to various modules, with integration personnel responsible for parameter calibration. Both approaches have revealed problems such as low efficiency, operational complexity, and difficulty in permission management in actual implementation. Especially when multiple vehicle models and multiple projects are being developed in parallel, modifying common parameters requires synchronization across repositories, leading to a sharp increase in maintenance costs and unintuitive integration results.
[0056] The core problem currently facing the technology is that the parameter management method is not efficient and flexible enough, and there is a lack of a unified parameter management system. This leads to high project adaptation costs, complex version control, low integration efficiency, and limited permission management, which seriously restricts the rapid iteration and large-scale deployment of intelligent driving systems.
[0057] In the industry, algorithm developers are typically responsible for developing the core algorithms and abstracting the calibrated or configurable functionalities into configuration items, which are then centrally defined in configuration files. These configuration parameters have a high reusability across different projects, usually requiring only adjustments to a portion based on specific project needs. Integration developers, on the other hand, are responsible for project delivery, with their main task being the configuration and calibration of these algorithm parameters.
[0058] The parameter data processing method provided in this application embodiment is adapted to this division of labor model. Parameter management needs to be centralized, and all configuration parameters should be stored uniformly and organized according to established rules to facilitate efficient management and configuration by integration personnel, as well as unified control of permissions. Based on this, to address the needs of parallel development across multiple projects and vehicle models, and the management pressure of numerous branch versions, a management model of a general configuration repository and a project configuration repository is introduced to improve development and adaptation efficiency. The general configuration repository maintains common parameters shared by all projects, while the project repository manages the personalized configurations required by each project. The project repository supports independent modification of individual configuration items. For parameters that multiple projects depend on, updates can be made only in the general configuration repository, eliminating the need for repeated modifications in each project. This significantly reduces adaptation costs and improves the efficiency of parallel development and migration across multiple projects.
[0059] Figure 1 A schematic diagram illustrating the scenario of the parameter data processing method provided in this application, such as... Figure 1As shown, the specific application scenario of this application is a parameter data processing system. This system can be a parameter repository for centralized management and maintenance of various configuration parameters in the intelligent driving system. This parameter repository can include a general configuration repository and project configuration repositories. There are multiple project configuration repositories, and the general configuration repository is connected to each of these multiple project configuration repositories.
[0060] All application layer parameter files that need to be reused in multiple projects are managed uniformly in the base_parameters general configuration repository. At the same time, resources shared by projects, such as the intelligent driving package deployment script, are also centrally stored here.
[0061] Each project parameter repository (e.g., project1_parameters, project2_parameters, etc.) depends on base_parameters as its basic configuration source, and the project parameter repositories are isolated from each other and have no direct dependencies.
[0062] The base_parameters maintains a corresponding relationship with the parameter repositories of each project in terms of branch management. For example, the master branch corresponds to master, and release_x.x corresponds to release_x.x, ensuring the consistency and controllability of version evolution.
[0063] The parameter data processing method in this embodiment does not impose any particular restrictions on the implementation of the execution subject, as long as the execution subject can obtain the target configuration parameters sent by the user; update the configuration file in the first parameter repository in the parameter repository according to the target configuration parameters and the user's permissions; wherein, the parameter repository includes a general configuration repository and a project configuration repository, the general configuration repository is used to store general parameters applicable to each specific project in the intelligent driving service, the project configuration repository is used to store personalized parameters for specific projects in the intelligent driving service, and the specific projects corresponding to different project configuration repositories are different, the first parameter repository is either a project configuration repository or a general configuration repository; generate an intelligent driving package for the intelligent driving service according to the updated first parameter repository and the second parameter repository; the second parameter repository can be a parameter repository in the parameter repository that corresponds to the first parameter repository but is of a different type.
[0064] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.
[0065] Figure 2 Flowchart of the parameter data processing method provided in this application Figure 1 ,like Figure 2 As shown, the method includes:
[0066] S201. Obtain the target configuration parameters sent by the user.
[0067] Users can include algorithm developers and integration developers. Algorithm developers are engineers responsible for developing and optimizing core algorithms. They can define and adjust configurable parameters in the general configuration repository to ensure the performance and adaptability of the algorithm in different scenarios. Integration developers are technical personnel responsible for project delivery and adaptation. They configure, calibrate, and verify the algorithm parameters in each project according to the specific vehicle model and project requirements to achieve the final application of intelligent driving services.
[0068] Target configuration parameters refer to a set of parameters that users wish to use to update configuration files in the code repository. These parameters are used to adjust or configure the behavior of relevant functional modules in the intelligent driving system. They can encompass general parameters (common configurations applicable to multiple projects) and project-specific parameters (personalized settings for a specific vehicle model or project), represented in a structured format (such as JSON, YAML, etc.), and correspond to specific configuration files in the code repository. By writing target configuration parameters into a designated configuration file, the system can update the general configuration repository or project configuration repository in the parameter repository, thereby supporting rapid adaptation and integration of algorithm functions.
[0069] In this embodiment, the target configuration parameters can be manually entered, edited and submitted by the user in the configuration management interface or command line tool, or they can be generated and uploaded from the test or calibration system through an automated process.
[0070] S202. Update the configuration files in the first parameter repository in the parameter repository according to the target configuration parameters and user permissions. The parameter repository includes a general configuration repository and a project configuration repository. The general configuration repository is used to store general parameters applicable to each specific project in the intelligent driving service. The project configuration repository is used to store personalized parameters for specific projects in the intelligent driving service. Different project configuration repositories correspond to different specific projects. The first parameter repository is either a project configuration repository or a general configuration repository.
[0071] User permissions refer to the scope of operations and control over the parameter repository granted based on user roles (such as algorithm developers, integration developers, project administrators, etc.). These permissions determine the range of parameters a user can access, view, modify, or submit. For example, algorithm developers may have permission to modify the general configuration repository and the modules they are responsible for, while integration developers primarily have permission to configure and calibrate specific project configuration repositories, but not to modify core general parameters. Access control prevents unauthorized parameter changes, ensures configuration security and traceability, and supports efficient collaboration among multiple teams within a shared parameter system.
[0072] The first parameter repository refers to the storage area for the target configuration parameters that need to be updated in this operation. This storage area can be a general configuration repository or a project configuration repository for a specific project. When the target configuration parameters involve common settings shared by multiple projects (such as sensor calibration basic parameters, global behavior policy thresholds, etc.), the first parameter repository is a general configuration repository; when the target configuration parameters are only personalized for a specific vehicle model or project (such as steering response gain for a certain vehicle model, perception sensitivity in a specific scenario, etc.), the first parameter repository is the project configuration repository for that specific project. The system automatically identifies and locates the first parameter repository that needs to be updated based on the user's permissions, ensuring that configuration changes fall within the correct management scope.
[0073] S203. Generate an intelligent driving package for intelligent driving services based on the updated first parameter warehouse and second parameter warehouse; the second parameter warehouse is a parameter warehouse in the parameter warehouse that corresponds to the first parameter warehouse but is of a different type.
[0074] The second parameter repository refers to a storage area containing parameters that correspond to but differ in type from the currently updated first parameter repository during the generation of the intelligent driving package. For example, when the first parameter repository is a general configuration repository, the second parameter repository is a specific project configuration repository; conversely, if the first parameter repository is a project configuration repository, the second parameter repository can be the corresponding general configuration repository. Thus, by merging and packaging the parameters from both, the final intelligent driving package ensures that it includes both the latest general configurations and retains the project-specific personalized settings, achieving configuration consistency and flexibility, and supporting efficient adaptation and deployment for projects of different vehicle models.
[0075] The parameter data processing method provided in this application can be deployed on a compilation server to achieve separate management of parameters and code based on the Git repository system. During execution, the system first obtains the target configuration parameters submitted by the user, and determines the range of operable parameters based on the user's identity and permissions, thus identifying the first parameter repository that needs to be updated. Subsequently, the configuration file is automatically updated in the corresponding parameter repository to ensure that parameter changes comply with permission control and version management requirements. After the parameter update is completed, the system further integrates the updated first parameter repository with the corresponding second parameter repository, automatically generates a complete parameter set matching the target project according to preset rules, and packages it along with the algorithm code into a smart driving package.
[0076] In some embodiments, preset rules can refer to a series of automated logic and strategies followed during the integration of the general configuration repository and the project configuration repository to generate the intelligent driving package. These rules may include parameter priority, inheritance and overriding, parameter validation, version matching, access control, and packaging naming conventions. For example, the system can set project configuration parameters to take precedence over general parameters, support partial overriding of general configurations by personalized configurations, perform format and value validation before parameter updates to ensure configuration validity, and automatically match compatible parameter combinations based on the version relationship between the project and the general parameter repository. Through these rules, the system can achieve automated merging, validation, and integration during parameter updates and packaging, ensuring that the parameters of the final generated intelligent driving package are complete, consistent, and traceable, meeting the needs of efficient development and secure delivery of multiple projects.
[0077] Therefore, the parameter data processing method provided in this application embodiment can realize separate management of parameters and code, and can set fine-grained permissions for different repositories. For example, integration personnel can only access the parameter repository and cannot access the algorithm code repository, thereby realizing secure, efficient and automated parameter configuration and version integration, significantly improving the parameter management efficiency and system maintainability under the parallel development of multiple projects.
[0078] Figure 3 Flowchart of the parameter data processing method provided in this application Figure 2 ,like Figure 3 As shown, in this embodiment... Figure 2 Based on the embodiments, the steps of updating the configuration files in the first parameter repository of the parameter repository according to the target configuration parameters and the user's permissions are described in detail. The method includes:
[0079] S301. Based on the user's permissions, determine the first parameter repository in the parameter repository that corresponds to the permissions;
[0080] S302. Traverse the first parameter repository and determine the configuration file in the first parameter repository;
[0081] S303. Write the target configuration parameters into the configuration file to update the configuration file in the first parameter repository.
[0082] User permissions can be determined through interfaces connected to parameter repositories. For example, interfaces used by code developers can connect to the general configuration repository in the parameter repository, while interfaces used by integration developers can connect to the corresponding project configuration repository. Depending on their permissions, some developers' interfaces can also connect to multiple parameter repositories.
[0083] By reading the directory structure of the first parameter repository, the system automatically scans the list of existing configuration files and parses their filenames, paths, and parameter structures to determine which operable configuration files are contained in the current parameter repository. This traversal process can be based on a recursive scan of the directory structure of the file system or version control system (such as Git), combined with the naming rules or metadata identifiers of the configuration files, to identify valid parameter configuration files for subsequent parameter writing and updating processes.
[0084] In this embodiment of the application, when the first parameter repository is a general configuration repository, Figure 3a This is a schematic diagram of the structure of the general configuration repository provided in the embodiments of this application; as shown below. Figure 3a As shown, the top-level directory of the general configuration repository (ads_base_parameters) can include three subdirectories: params, scripts, and apply_base.
[0085] The params directory is used to store various modular parameter files. This directory can include a modules subdirectory, which contains a planning module and a control module. The planning module contains YAML configuration files such as a.yaml and b.yaml, which are used to store parameter settings for different functional modules. b.yaml can be used to store configuration files that will be referenced or used in multiple places.
[0086] The scripts directory stores script files used for parameter repository operations, such as install.sh and profile.sh, which facilitate automated deployment and environment configuration;
[0087] The apply_base directory provides tools for manipulating parameters, enabling flexible adjustment and application of these parameters.
[0088] When the first parameter repository is the project configuration repository Figure 3b This is a schematic diagram of the structure of the project configuration repository provided in the embodiments of this application; as follows: Figure 3b As shown, the top-level directory of the project configuration repository (project_parameters) can include three directories: params, apply_base, and scripts.
[0089] The `params` directory contains three subdirectories: `modules`, `vehicle_model`, and `amend`. `modules` stores basic parameters, further subdivided into the `diagnosis` module and the `em` module. The `diagnosis` module stores the `dia.yaml` configuration file, while the `em` module stores the configuration files `em1.yaml` to `emn.yaml`. The `vehicle_model` directory stores vehicle parameters, where, depending on the vehicle model, the corresponding parameters can be stored in the corresponding `vehicle.yaml` file. The `amend` directory stores parameters that differ from those in the general configuration repository, and can contain files such as `amend_x86.yaml` and `amend_arm64.yaml` for adjusting parameters based on different hardware platforms.
[0090] The apply_base directory provides tools for manipulating parameters, allowing users to flexibly modify and apply configurations. Example commands include apply_base -v_model1 -a amend_arm64.yaml.
[0091] The scripts directory is used to store relevant script files, supporting automated deployment and environment configuration.
[0092] After the configuration file is determined, the target configuration parameters sent by the user can be written into the corresponding configuration file in the first parameter repository according to the preset file format and path, thereby realizing the update operation of the configuration content in the parameter repository.
[0093] In the embodiments of this application, Figure 3c This is a schematic diagram of the updated file structure of the configuration file provided in the embodiments of this application, as shown below. Figure 3c As shown, the directory structure of the configuration file (xxx / config) demonstrates how the configuration files are organized. It includes multiple subdirectories and files: planning / xx and control / xxx are derived from the combined configuration of params / modules + vehicle_model + amend, respectively, and are used for planning and control functions; the vehicle.yaml file under the vehicle directory defines the parameters related to the vehicle model; and diagnosis / xxx is used to store the configuration related to diagnosis.
[0094] In this embodiment, when the first parameter repository is a project configuration repository, the target configuration parameters are written to a configuration file to update the configuration file in the first parameter repository, including:
[0095] Determine the parameter type of the target configuration parameter;
[0096] Based on the parameter type of the target configuration parameter, the target configuration parameters of different parameter types are written into the corresponding configuration files to update the configuration files in the first parameter repository.
[0097] The parameter types of target configuration parameters can refer to categories categorized according to their intended use and scope of application. For example, target configuration parameter types can include basic parameters, vehicle model parameters, and difference parameters. Basic parameters refer to configurations applicable to general functional modules and are stored in the corresponding module files in the `modules` directory. Vehicle model parameters refer to configurations defined for different vehicle models and can be written to the corresponding vehicle model files in the `vehicle_model` directory. Difference parameters, representing the differences between common modules and basic configurations, can be categorized in the `amend` directory and are used to describe content that needs to be additionally covered or adjusted based on the general configuration.
[0098] In this embodiment, the categorized writing method improves the readability and maintainability of parameter configuration, ensuring that different types of parameters are properly assigned and avoiding configuration chaos. It also supports differentiated configuration management, facilitating independent updates and version control for specific modules, vehicle models, or common foundational parts, thus enhancing system flexibility and scalability. Furthermore, it facilitates rapid configuration location and troubleshooting, improving development, debugging, and deployment efficiency.
[0099] In this embodiment of the application, target configuration parameters of different parameter types are written into corresponding configuration files according to their parameter types to update the configuration files in the first parameter repository, including:
[0100] If the same target configuration parameter exists in different configuration files, the target configuration parameter will be written to the configuration file that meets the priority requirement according to the priority of the configuration files, so as to update the configuration file in the first parameter repository.
[0101] In this embodiment of the application, the configuration file includes a basic configuration file for storing basic parameters, a vehicle model configuration file for storing vehicle parameters, and a project configuration file for storing difference parameters.
[0102] Among them, the priority of the project configuration file is higher than that of the vehicle configuration file, and the priority of the vehicle configuration file is higher than that of the basic configuration file.
[0103] Priority refers to the order in which the same target configuration parameter is written, based on the loading order of the configuration file paths, when multiple configuration files contain the same parameter. In this embodiment, the priority order can be: module (basic configuration file) < vehicle_model (vehicle model configuration file) < amend (project configuration file), meaning the basic configuration file has the lowest priority, followed by the vehicle model configuration file, and the project configuration file has the highest priority. When parameters with the same name exist, the configuration in the higher-priority path will override the content in the lower-priority path. Therefore, by supporting hierarchical management and differentiated overriding of configurations, especially with parameters in the amend file organized in YAML format, fine-grained modification at the field level can be achieved, improving configuration flexibility and accuracy.
[0104] The parameter data processing method provided in this application determines the corresponding first parameter repository based on user permissions and writes the target configuration parameters into the corresponding configuration files according to their types. By combining the priority rules among the basic configuration file, vehicle model configuration file, and project configuration file, hierarchical management and precise coverage of parameter updates are achieved. This not only ensures reasonable access and modification permissions for configuration parameters for users with different permissions but also improves the structure and maintainability of parameter configurations. It ensures that when parameters with the same name exist, the configuration with higher priority takes effect, avoiding configuration conflicts and improving the flexibility, security, and deployment efficiency of configurations.
[0105] In this embodiment of the application, when the first parameter repository is a project configuration repository, the method further includes:
[0106] If the target configuration file in the project configuration repository is updated, the configuration parameters in the second parameter repository corresponding to the target configuration file will be updated based on the result of the update.
[0107] Based on the updated first and second parameter repositories, generate an intelligent driving package for intelligent driving services.
[0108] When the first parameter repository is a project configuration repository, to improve the flexibility of modifications and allow for specific adjustments to a particular project, the target configuration file in the project configuration repository can be updated. After the target configuration file is updated, the corresponding configuration parameters in the general configuration repository are synchronously updated based on the update results, ensuring consistency and synergy between upper and lower layer configurations. Based on this, and combining the updated first and second parameter repositories, the system will automatically generate a smart driving package for intelligent driving services, achieving unified packaging and efficient delivery of configuration parameters, and improving the automation and accuracy of version building and deployment.
[0109] In this embodiment of the application, the target configuration file can be the Amend file in the project configuration repository, and the parameters in the file have the same nested structure as the base parameter.
[0110] For example, the file base_parameters / modules / planning / a.yaml contains several configuration parameters:
[0111] {
[0112] "config1:1.1"
[0113] "config2:1.2"
[0114] "config3:1.3"
[0115] "config4:1.4"
[0116] }
[0117] If you want to change `config2` to `2.2` in `base_parameters` within the project configuration repository, then write the following in the `amend_arm64.yaml` file within the project configuration repository:
[0118] {
[0119] "planning":
[0120] a":
[0121] "config2":2.2
[0122] }
[0123] After writing the above content, the corresponding content can be updated in the general configuration repository, and the updated content can be used in the process of generating the intelligent driving package corresponding to the project.
[0124] In this embodiment of the application, the method further includes:
[0125] In response to the user's selection action, determine the target item configuration repository in the parameter repository;
[0126] Adjust the configuration file of the target project's configuration repository based on the user's adjustment operations on the target project's configuration repository;
[0127] In response to the user's creation operation, the adjusted target project configuration repository is created in the parameter repository as the project configuration repository to be created.
[0128] In response to user selections, the system identifies the target project configuration repository in the parameter repository and dynamically modifies its internal configuration files based on user adjustments to meet the specific project's adaptation requirements. Simultaneously, in response to user creation actions, the adjusted target project configuration repository can be created as a new project configuration repository within the parameter repository, facilitating project reuse and configuration migration for integration developers. This allows developers to easily create new project parameter repositories by referencing existing project configurations, clearly identify and adjust key configuration items requiring adaptation, and improve development efficiency and configuration consistency.
[0129] Therefore, the parameter data processing method provided in this application, compared with the prior art, fully considers the complex adaptation needs of multiple vehicle models and projects in intelligent driving systems, and proposes a parameter management mechanism based on a two-layer structure of basic parameter repository and personalized parameter repository. In traditional methods, parameters are often embedded in code or are difficult to form independent common configuration items. Different projects may directly modify any configuration in the basic parameters, resulting in chaotic management and poor reusability. However, this application isolates the parameters, constructs a flexibly expandable basic parameter repository and project parameter repository, and supports explicitly specifying the basic parameter items to be covered in the project parameter repository, realizing fine-grained modification of configuration items at any level. At the same time, it provides a multi-file merging and reverse synchronization mechanism for configuration files, solving the problem of cumbersome modification of multiple independent configuration files, and improving the platform level of parameter management and project adaptation efficiency.
[0130] Furthermore, separating parameters from code ensures the security of code permissions; centralized parameter management makes rules transparent and adaptation clear, allowing integration developers to quickly identify configuration items that need modification and easily create new project parameter repositories; algorithm developers only need to maintain a complete set of basic parameters, focusing on algorithm iteration without needing to worry about project adaptation details. This simplifies the configuration process, clarifies the division of labor, and automates the generation of project integration packages, effectively reducing parameter maintenance costs and improving the adaptability and development collaboration efficiency of the intelligent driving system in multi-project, multi-vehicle scenarios.
[0131] Figure 4 A schematic diagram of the structure of the parameter data processing device provided in this application is shown below. Figure 4 As shown, the parameter data processing device 40 provided in this embodiment includes:
[0132] Module 401 is used to obtain the target configuration parameters sent by the user;
[0133] The update module 402 is used to update the configuration file in the first parameter repository in the parameter repository according to the target configuration parameters and the user's permissions. The parameter repository includes a general configuration repository and a project configuration repository. The general configuration repository is used to store general parameters applicable to each specific project in the intelligent driving service. The project configuration repository is used to store personalized parameters for specific projects in the intelligent driving service. Different project configuration repositories correspond to different specific projects. The first parameter repository is either a project configuration repository or a general configuration repository.
[0134] The generation module 403 is used to generate an intelligent driving package for intelligent driving services based on the updated first parameter repository and second parameter repository; the second parameter repository is a parameter repository in the parameter repository that corresponds to the first parameter repository but is of a different type.
[0135] In one possible implementation, the update module 402 can also be specifically used for:
[0136] Based on the user's permissions, determine the first parameter repository in the parameter repository that corresponds to the permissions;
[0137] Iterate through the first parameter repository to determine the configuration files within it;
[0138] Write the target configuration parameters to the configuration file to update the configuration file in the first parameter repository.
[0139] In one possible implementation, when the first parameter repository is a project configuration repository, the update module 402 can also be specifically used for:
[0140] Determine the parameter type of the target configuration parameter;
[0141] Based on the parameter type of the target configuration parameter, the target configuration parameters of different parameter types are written into the corresponding configuration files to update the configuration files in the first parameter repository.
[0142] In one possible implementation, the update module 402 can also be specifically used for:
[0143] If the same target configuration parameter exists in different configuration files, the target configuration parameter will be written to the configuration file that meets the priority requirement according to the priority of the configuration files, so as to update the configuration file in the first parameter repository.
[0144] In one possible implementation, the configuration files in update module 402 include a base configuration file for storing basic parameters, a vehicle model configuration file for storing vehicle parameters, and a project configuration file for storing difference parameters.
[0145] Among them, the priority of the project configuration file is higher than that of the vehicle configuration file, and the priority of the vehicle configuration file is higher than that of the basic configuration file.
[0146] In one possible implementation, when the first parameter repository is a project configuration repository, the generation module 403 can also be specifically used for:
[0147] If the target configuration file in the project configuration repository is updated, the configuration parameters in the second parameter repository corresponding to the target configuration file will be updated based on the result of the update.
[0148] Based on the updated first and second parameter repositories, generate an intelligent driving package for intelligent driving services.
[0149] In one possible implementation, the generation module 403 can also be specifically used for:
[0150] In response to the user's selection action, determine the target item configuration repository in the parameter repository;
[0151] Adjust the configuration file of the target project's configuration repository based on the user's adjustment operations on the target project's configuration repository;
[0152] In response to the user's creation operation, the adjusted target project configuration repository is created in the parameter repository as the project configuration repository to be created.
[0153] The parameter data processing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.
[0154] Figure 5 A schematic diagram of the structure of the electronic device provided in this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus 504.
[0155] In a specific implementation, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-described method.
[0156] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.
[0157] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.
[0158] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.
[0159] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.
[0160] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.
[0161] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.
[0162] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.
[0163] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.
[0164] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.
[0165] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0166] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0167] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0168] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.
[0169] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.
Claims
1. A method of processing parametric data, characterized by, The method comprises: obtaining a target configuration parameter sent by a user; updating a configuration file in a first parameter warehouse in a parameter warehouse according to the target configuration parameter and a permission of the user; wherein the parameter warehouse comprises a general configuration warehouse and a project configuration warehouse, the general configuration warehouse is used to store general parameters applicable to each specific project in intelligent driving service, the project configuration warehouse is used to store individualized parameters of a specific project in the intelligent driving service, and different project configuration warehouses correspond to different specific projects, and the first parameter warehouse is the project configuration warehouse or the general configuration warehouse; generating an intelligent driving package for the intelligent driving service according to the first parameter warehouse and a second parameter warehouse after being updated. The second parameter warehouse is a parameter warehouse corresponding to the first parameter warehouse and having a different type in the parameter warehouse.
2. The method of claim 1, wherein, The updating of the configuration file in the first parameter warehouse according to the target configuration parameter and the permission of the user comprises: determining the first parameter warehouse corresponding to the permission in the parameter warehouse according to the permission of the user; traversing the first parameter warehouse to determine the configuration file in the first parameter warehouse; writing the target configuration parameter into the configuration file to update the configuration file in the first parameter warehouse.
3. The method of claim 2, wherein, When the first parameter warehouse is a project configuration warehouse, the writing of the target configuration parameter into the configuration file to update the configuration file in the first parameter warehouse comprises: determining a parameter type of the target configuration parameter; writing the target configuration parameter of different parameter types into the corresponding configuration file according to the parameter type of the target configuration parameter to update the configuration file in the first parameter warehouse.
4. The method of claim 3, wherein, The writing of the target configuration parameter of different parameter types into the corresponding configuration file according to the parameter type of the target configuration parameter to update the configuration file in the first parameter warehouse comprises: if there are the same target configuration parameters in different configuration files, writing the target configuration parameter into the configuration file meeting the priority requirement according to the priority between the configuration files to update the configuration file in the first parameter warehouse.
5. The method of claim 4, wherein, The configuration file comprises a basic configuration file used to store basic parameters, a vehicle type configuration file used to store vehicle parameters, and a project configuration file used to store difference parameters. The priority of the project configuration file is higher than that of the vehicle type configuration file, and the priority of the vehicle type configuration file is higher than that of the basic configuration file.
6. The method according to any one of claims 1 to 5, characterized in that, When the first parameter warehouse is a project configuration warehouse, the method further comprises: if the target configuration file in the project configuration warehouse is updated, updating the configuration parameter corresponding to the target configuration file in the second parameter warehouse according to the result of updating the target configuration file; generating an intelligent driving package for the intelligent driving service according to the first parameter warehouse and the second parameter warehouse after being updated.
7. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: determining a target project configuration warehouse in the parameter warehouse in response to a selection operation of a user; Adjust the configuration file of the target project configuration repository according to the user's adjustment operation on the target project configuration repository; In response to the user's creation operation, the adjusted target project configuration repository is created in the parameter repository as the project configuration repository to be created.
8. A parameter data processing apparatus, characterized by comprising: include: The acquisition module is used to acquire the target configuration parameters sent by the user. An update module is used to update the configuration file in the first parameter repository in the parameter repository according to the target configuration parameters and the user's permissions; wherein, the parameter repository includes a general configuration repository and a project configuration repository, the general configuration repository is used to store general parameters applicable to each specific project in the intelligent driving service, and the project configuration repository is used to store personalized parameters for specific projects in the intelligent driving service, and different specific projects correspond to different project configuration repositories, and the first parameter repository is the project configuration repository or the general configuration repository; The generation module is used to generate an intelligent driving package for the intelligent driving service based on the updated first parameter repository and second parameter repository; the second parameter repository is a parameter repository in the parameter repository that corresponds to the first parameter repository but is of a different type.
9. An electronic device, comprising: include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-7.
10. A computer-readable storage medium / computer program product, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-7; and / or, The computer program product includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-7.