A global configuration management system and method for multi-control domain vehicle systems

Abstract

The application discloses a kind of global configuration management systems and methods for multi-control domain vehicle-mounted system, and the centralized management of multi-control domain configuration is realized by configuration management server, Redis sentry node cluster, Redis master-slave node cluster.The application uses Redis server as configuration storage engine, realizes role-based access control by adding built-in attribute in configuration data, supports fine-grained permission management, avoids configuration from being modified unintentionally;Adopting master-slave replication ensures the consistency of data, supports version management, persistent storage and automatic backup recovery of configuration data, while providing complete configuration change audit and rollback mechanism.The application solves the problems of configuration dispersion, low update efficiency and insufficient security in traditional configuration management methods, significantly improves the efficiency, security and maintainability of vehicle-mounted system configuration management, and provides solid technical support for the development of intelligent networked vehicles.

Description

Technical Field

[0001] This invention relates to the field of vehicle system technology, and in particular to a global configuration management system and method for multi-control domain vehicle systems. Background Technology

[0002] With the rapid development of automotive electronics technology and the popularization of intelligent connected vehicles, modern vehicles have evolved into complex distributed systems, typically containing multiple control domains such as the powertrain domain, intelligent driving domain, cockpit domain, and infotainment domain. Each control domain requires independent configuration management, and this configuration data directly affects the vehicle's performance, safety, and user experience.

[0003] In traditional configuration management systems, each control domain typically employs an independent configuration management scheme, resulting in fragmented configuration data storage and difficulty in unified management. When configuration changes are required, manual intervention is often necessary, which is inefficient and prone to errors. Furthermore, the lack of a global configuration view hinders overall system optimization, making configuration coordination between control domains a significant challenge.

[0004] Configuration synchronization is another pressing issue. Existing configuration updates mostly use a polling method, resulting in poor real-time performance and a complex, error-prone synchronization process. When configuration synchronization fails, there is a lack of effective automatic recovery mechanisms, often requiring manual intervention and increasing operational costs. Furthermore, the lack of an effective configuration change notification mechanism makes it difficult for related systems to respond to configuration changes in a timely manner, impacting overall system performance.

[0005] There are also significant shortcomings in system availability and data consistency. Traditional configuration management systems are mostly deployed from a single point, posing a high risk of failure. When the configuration server fails, the recovery time is long, severely impacting the normal operation of the system. Furthermore, due to the lack of automatic failover mechanisms and effective version control, inconsistencies in configuration data may lead to abnormal system behavior and even security issues.

[0006] To address the aforementioned issues, existing technologies have proposed several solutions, such as using centralized configuration management servers, storing configuration information in databases, and implementing simple configuration synchronization mechanisms. However, these solutions still have significant shortcomings and cannot meet the high concurrency, high availability, and intelligent requirements of modern intelligent connected vehicles. Therefore, a new technical solution is urgently needed to solve these problems and provide a more efficient, reliable, and secure global configuration management service. Summary of the Invention

[0007] To address the shortcomings of existing technologies, the present invention aims to provide a global configuration management system and method for multi-control domain vehicle systems.

[0008] To achieve the objectives of this invention, the technical solution adopted is as follows:

[0009] A global configuration management system for multi-control domain vehicle systems includes a configuration client, a configuration management server, a Redis sentinel node cluster, and a Redis master-slave node cluster. The configuration client is an application / service centrally managed and initializes its services by requesting configuration data from the configuration management server during startup. The configuration management server manages the global configuration, providing API interfaces for adding, deleting, modifying, and querying data, and connecting to the Redis server. The Redis sentinel node cluster monitors the status of the Redis master-slave nodes. The Redis master-slave node cluster is used for persistent storage and data synchronization of the configuration.

[0010] Furthermore, each control domain has a global configuration management server that provides configuration management functions for the configuration clients of that control domain.

[0011] Furthermore, the Redis master-slave node cluster stores all configuration data for all control domains, and the configuration data for each control domain is stored in different keys using the HOSTNAME.

[0012] Furthermore, the configuration management server enables access control, version management, and history recording of configurations by embedding built-in attribute fields in the configuration data.

[0013] Furthermore, the configuration management server achieves automatic failover by subscribing to primary / standby switchover events through sentinel nodes; the primary / standby switchover events subscribed to by the sentinel nodes include: primary server failure detection, new primary server election, configuration synchronization triggering, and client reconnection notification.

[0014] Furthermore, Redis master and slave nodes use the Rejson module to manage JSON-formatted configuration data. The ReJSON module supports storing, querying, and modifying JSON data directly in Redis, and allows for quick location and access to fields in the JSON data using the JSONPath syntax.

[0015] A global configuration management method for multi-control domain vehicle systems includes starting the configuration management service, reading the configuration by the configuration client, and notifying configuration changes.

[0016] Further, configure the server startup steps:

[0017] (1) Initialize the configuration management server and establish a connection with the Redis Sentinel node cluster;

[0018] (2) Subscribe to master-slave failover notifications; the configuration management server subscribes to master-slave failover events through the Redis sentinel node to achieve automatic failover;

[0019] (3) Obtain Redis master-slave node information through the Redis Sentinel node;

[0020] (4) Establish a connection with the Redis master-slave node;

[0021] (5) Subscribe to configuration change notifications.

[0022] Further, configure the client to read the configuration steps:

[0023] (1) Subscribe to configuration change events from the configuration server;

[0024] (2) Send a configuration request to the configuration server;

[0025] (3) The configuration server reads the configuration from the Redis server;

[0026] (4) The configuration server returns the configuration data to the configuration client;

[0027] (5) Configure the client to initialize the service according to the obtained configuration.

[0028] Further, configure the change notification steps:

[0029] (1) Administrators / users send update configuration requests to the configuration management server through configuration tools;

[0030] (2) The configuration management server reads the configuration from the Redis server, verifies the permissions, updates the configuration and adds the configuration change record, and then rewrites it to the Redis master and slave nodes;

[0031] (3) The Redis master and slave nodes send configuration change notifications to the configuration management servers of all control domains;

[0032] (4) After receiving the configuration change notification, the configuration management server forwards it to the configuration client;

[0033] (5) When the configuration client receives the configuration change notification, it updates its own configuration parameters and makes them effective.

[0034] The beneficial effects of this invention are as follows: Compared with existing technologies, this invention achieves global configuration management for multi-control domain vehicle systems by using a Redis Sentinel + master-slave cluster deployment scheme. In terms of configuration management, real-time notification of configuration changes is achieved through Redis's publish-subscribe mechanism, and the ReJSON module efficiently manages JSON-formatted configuration data. Regarding data security, role-based access control is implemented through built-in attributes, supporting fine-grained permission management to prevent unintentional configuration modifications, while providing complete operation auditing and change traceability functions. For data consistency, a master-slave replication mechanism ensures configuration data synchronization, and version control ensures the traceability of configuration changes. In terms of performance optimization, Redis's in-memory storage characteristics improve configuration access efficiency. This invention significantly improves the efficiency, security, and maintainability of vehicle system configuration management, providing solid technical support for the development of intelligent connected vehicles. Attached Figure Description

[0035] Figure 1 This is a schematic diagram of a global configuration management system for multi-control domain vehicle systems as described in this invention;

[0036] Figure 2 This is a flowchart of a global configuration management method for a multi-control domain vehicle system as described in this invention;

[0037] Figure 3 This is a diagram illustrating the master-slave failover mechanism;

[0038] Figure 4 This is a diagram illustrating the data synchronization mechanism. Detailed Implementation

[0039] The technical solution of the present invention will be further described below with reference to the accompanying drawings and embodiments. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and should not be used to limit the scope of protection of this application.

[0040] like Figure 1 As shown, the global configuration management system for multi-control domain vehicle systems described in this invention includes a configuration client, a configuration management server, a Redis sentinel node cluster, and a Redis master-slave node cluster. The configuration client is the application / service whose configuration is centrally managed; during startup, it requests configuration data from the configuration management server to initialize its service. The configuration management server primarily manages the global configuration, providing API interfaces for adding, deleting, modifying, and querying data, and connecting to the Redis server. The Redis sentinel node cluster monitors the status of the Redis master-slave nodes. The Redis master-slave node cluster (Redis server) is used to implement persistent storage and data synchronization of the configuration.

[0041] Each control domain has its own configuration management server, which provides configuration management for other services / applications (configuration clients) within that control domain. The Redis master-slave node cluster stores all configuration data for all control domains, with each control domain's configuration data stored in different keys using the HOSTNAME.

[0042] During the configuration data preparation phase, the global configuration data for each control domain is imported into a Redis server. In the Redis server, the configuration data for each control domain is distinguished by a key value, formatted as "gcm_$HOSTNAME", where $HOSTNAME is the hostname of the control domain. For example, the configuration data for the power domain is stored under the key "gcm_power_domain", the configuration data for the intelligent driving domain is stored under the key "gcm_adas_domain", the configuration data for the cockpit domain is stored under the key "gcm_cockpit_domain", and the configuration data for the infotainment domain is stored under the key "gcm_infotainment_domain". This naming convention ensures the uniqueness of the configuration data while facilitating management and retrieval.

[0043] Redis master and slave nodes use the Rejson module to manage JSON-formatted configuration data. The Rejson module supports direct storage, querying, and modification of JSON data within Redis without manual serialization / deserialization. It uses JSONPath syntax to quickly locate and access specific fields within the JSON data, supports atomic operations to ensure data consistency, provides efficient data compression storage to reduce memory consumption, and supports fast querying and updating of complex JSON structures. Built-in attribute fields are embedded in the configuration data to implement access control, version management, and history recording functionality.

[0044] like Figure 2 As shown, the global configuration management method is mainly divided into the configuration management service startup process, the configuration client reading configuration process, and the configuration change process.

[0045] The configuration management service startup process consists of stages 1 to 6. The startup process is the same for each control domain. It mainly involves obtaining Redis master-slave node information by connecting to the Redis sentinel node, then connecting to the Redis master-slave node and subscribing to configuration changes, and then initializing the configuration service.

[0046] The specific steps include:

[0047] (1) Initialize the configuration management server and establish a connection with the Redis Sentinel node cluster;

[0048] (2) Subscribe to master-slave failover notifications; the configuration management server subscribes to master-slave failover events through the Redis sentinel node to achieve automatic failover;

[0049] (3) Obtain Redis master-slave node information through the Redis Sentinel node;

[0050] The specific implementation of obtaining Redis master-slave node information through the Redis Sentinel node includes: sending a command to the Redis Sentinel node to obtain the Redis server; parsing the Redis server information returned by the Redis Sentinel node; and verifying the Redis server status.

[0051] (4) Establish a connection with the Redis master-slave node;

[0052] (5) Subscribe to configuration change notifications.

[0053] The configuration client reads configuration information through stages 7-12. The configuration client reads configuration information through stages 7-12 is the same for each control domain. It mainly involves sending a read configuration request to the configuration management server by calling the API interface provided by the configuration management server. After receiving the read configuration request, the configuration management server reads the configuration information from the Redis server and returns it to the configuration client. The configuration client initializes and starts its own services based on the obtained configuration information.

[0054] The specific steps include:

[0055] (1) Subscribe to configuration change events from the configuration server;

[0056] (2) Send a configuration request to the configuration server;

[0057] (3) The configuration server reads the configuration from the Redis server;

[0058] (4) The configuration server returns the configuration data to the configuration client;

[0059] (5) Configure the client to initialize the service according to the obtained configuration.

[0060] The configuration change process mainly includes stages 13-20. During operation, when a user / administrator in the cockpit domain sends a configuration modification request to the configuration management server through the configuration management tool, the configuration management server first retrieves the configuration information from the Redis server, then verifies permissions, updates the configuration, adds a configuration change record, and then writes it back to the Redis server. Configuration changes on the Redis server trigger a configuration change notification to the configuration management server in the intelligent driving domain. The configuration management server in the intelligent driving domain then notifies the configuration client in the intelligent driving domain of the configuration change. Upon receiving the configuration change notification, the configuration client in the intelligent driving domain updates the configuration and makes it effective.

[0061] The specific steps include:

[0062] (1) Administrators / users send update configuration requests to the configuration management server through configuration tools;

[0063] (2) The configuration management server reads the configuration from the Redis server, verifies the permissions, updates the configuration and adds the configuration change record, and then rewrites it to the Redis master and slave nodes;

[0064] (3) The Redis master and slave nodes send configuration change notifications to the configuration management servers of all control domains;

[0065] (4) After receiving the configuration change notification, the configuration management server forwards it to the configuration client;

[0066] (5) When the configuration client receives the configuration change notification, it updates its own configuration parameters and makes them effective.

[0067] like Figure 3 As shown, Redis high availability is achieved through a master-slave failover mechanism. This mechanism enables automatic failover through four steps: master server failure detection, new master server election, configuration synchronization triggering, and client reconnection notification. After a Redis master-slave failover occurs, all configuration management servers in the control domain receive a failover event notification. The configuration management server then reconnects based on the new Redis master-slave node information and resubscribes to configuration data change notifications.

[0068] like Figure 4 As shown, Redis high availability implementation includes a data synchronization mechanism. This mechanism ensures data consistency through master-slave replication, incremental synchronization, full synchronization, and synchronization verification.

[0069] The configuration management server implements access control, version management, and history tracking by adding built-in attribute fields to the existing configuration data. Specifically, the system adds a `__builtin_attribute` field to the JSON structure of the configuration data. This field contains multiple built-in attributes, which are stored together with the configuration data in a Redis database. Efficient management and access are achieved through the ReJSON module, ensuring both the security of the configuration data and providing complete version control and history tracking capabilities. See Table 1.

[0070] Table 1

[0071] Built-in attributes Attribute meaning __opera_perm Role operation permissions __read_only Mark configuration read-only status __view_ownership / __view_ownership_list Configure query permissions __subscribe_client Client information for subscribing to this configuration __last_reader / __last_editor / __last_value Configuration access and modification history __is_deleted Configured deletion status __module_conf_path Configured module path

[0072] The beneficial effects of this invention are as follows: Compared with the prior art, this invention implements role-based access control through built-in attributes, supports fine-grained permission management, and avoids unintentional modification of configurations; it uses the ReJSON module to manage JSON-formatted configuration data, supporting atomic operations and path queries on configuration data; and it ensures data consistency through a master-slave replication mechanism, realizing version management and change traceability of configuration data. It has advantages such as centralized configuration management, precise permission control, guaranteed data consistency, and traceable operations, effectively solving the problems existing in traditional configuration management methods and providing solid technical support for the development of intelligent connected vehicles.

[0073] The applicant of this invention has provided a detailed description of the embodiments of the invention in conjunction with the accompanying drawings. However, those skilled in the art should understand that the above embodiments are merely preferred embodiments of the invention. The detailed description is only intended to help readers better understand the spirit of the invention and is not intended to limit the scope of protection of the invention. On the contrary, any improvements or modifications made based on the inventive spirit of the invention should fall within the scope of protection of the invention.

Claims

1. A global configuration management system for a multi-control domain vehicle system, characterized in that, The application comprises a configuration client, a configuration management server, a Redis sentinel node cluster and a Redis master-slave node cluster; wherein the configuration client is an application / service managed by the configuration management server, and requests configuration data from the configuration management server to initialize the service in the start-up stage; the configuration management server realizes the management of global configuration, provides data adding, deleting, modifying and inquiring API interfaces upward, and connects with the Redis server downward; the Redis sentinel node cluster is used for monitoring the state of the Redis master-slave node; the Redis master-slave node cluster is used for realizing the persistent storage and data synchronization of the configuration; the Redis master-slave node uses the Rejson module to manage the configuration data in the json format, and the ReJSON module supports storing, inquiring and modifying the JSON data directly in the Redis, and quickly positioning and accessing specific fields in the JSON data through the JSONPath syntax.

2. The global configuration management system for multi-control domain vehicle system according to claim 1, wherein, Each control domain has a global configuration management server, which provides configuration management functions for the configuration clients in the control domain.

3. The global configuration management system for multi-control domain vehicle system according to claim 1, wherein, The Redis master-slave node cluster stores all the configuration data of the control domains, and the configuration data of each control domain is stored in different keys through HOSTNAME.

4. The global configuration management system for multi-control domain vehicle system according to claim 1, wherein, The configuration management server realizes the permission control, version management and history record functions of the configuration by embedding built-in attribute fields in the configuration data.

5. The global configuration management system for multi-control domain vehicle system according to claim 1, wherein, The configuration management server realizes automatic failover by subscribing to the master-slave switching event through the sentinel node. The sentinel node subscribing to the master-slave switching event comprises: master server failure detection, new master server election, configuration synchronization triggering and client reconnection notification.

6. A method for global configuration management of a multi-control domain vehicle system, based on the global configuration management system for a multi-control domain vehicle system according to any one of claims 1-5, characterized in that, It comprises configuration management service start, configuration client reading configuration and configuration change notification.

7. The method for managing global configuration of a multi-control domain oriented in-vehicle system according to claim 6, wherein, The configuration server start-up step: (1) initializing the configuration management server and establishing a connection with the Redis sentinel node cluster; (2) subscribing to the master-slave switching notification; the configuration management server realizes automatic failover by subscribing to the master-slave switching event through the Redis sentinel node; (3) obtaining the Redis master-slave node information through the Redis sentinel node; (4) establishing a connection with the Redis master-slave node; (5) subscribing to the configuration change notification.

8. The method for global configuration management of a multi-control domain oriented in-vehicle system according to claim 6, wherein, The configuration client reading configuration step: (1) subscribing to the configuration change event to the configuration server; (2) sending a configuration acquisition request to the configuration server; (3) the configuration server reading the configuration from the Redis server; (4) the configuration server returning the configuration data to the configuration client; (5) the configuration client initializing the service according to the acquired configuration.

9. The method for global configuration management of a multi-control domain oriented in-vehicle system according to claim 6, wherein, The configuration change notification step: (1) the administrator / user sends an update configuration request to the configuration management server through the configuration tool; (2) the configuration management server reads the configuration from the Redis server, checks the permission, updates the configuration and adds the configuration change record, and then writes into the Redis master-slave node again; (3) the Redis master-slave node sends the configuration change notification to the configuration management servers of all control domains; (4) the configuration management server forwards the configuration change notification to the configuration client after receiving the configuration change notification; (5) The configuration client receives the configuration change notification, updates its own configuration parameters and makes them effective.

Images