Automobile service data acquisition method based on safe and reliable SOA (Service-Oriented Architecture)

Abstract

The invention discloses a safe and reliable SOA-based service data acquisition method for an automobile, and the method comprises the steps: enabling the generation, auditing, encryption and deployment processes of a service configuration file to be automated and integrated to a service providing end, guaranteeing the authenticity, integrity and confidentiality of the service configuration file, achieving the centralized management and control of system resource overhead, and improving the safety and reliability of the system. Therefore, the security and reliability of SOA communication in the vehicle are improved.

Description

Technical Field

[0001] This invention relates to the field of automotive electronics and software architecture technology, and in particular to a method for acquiring service data for automobiles based on secure and reliable SOA. Background Technology

[0002] As automotive electronic and electrical architectures become more centralized, SOA (Service-Oriented Architecture) is widely used for communication between different domain controllers within the vehicle. In this architecture, service providers register their services in a directory, and service consumers discover and invoke the required services by querying this directory. This "directory" is typically defined by a service configuration file, such as service.config, which contains key information such as the service name, service instance address (e.g., IP address and port), and communication protocol.

[0003] Currently, the common practice is for developers to manually write or modify the service configuration file during the development phase and compile it directly into the firmware image (img), which is then burned into the domain controller along with the software version.

[0004] However, the current approach suffers from inadequate security and reliability. Regarding security: plaintext configuration files are vulnerable to malicious tampering during transmission or storage. Attackers can redirect service addresses to malicious nodes, masquerading as legitimate services, such as autonomous driving decision-making services, to launch attacks and seriously endanger driving safety. Furthermore, existing methods lack a mechanism to verify the integrity of configuration files, failing to detect whether they have been illegally modified. Regarding reliability: manual configuration modifications are prone to errors, such as configuring an address to an unreachable or incorrect terminal, leading to service communication failures and impacting the reliability of vehicle functions. Moreover, developers may configure too many service instances or threads for convenience, and the lack of a unified resource auditing and control process can result in excessive system load during operation, affecting overall performance and stability. Summary of the Invention

[0005] The purpose of this invention is to provide a method for obtaining service data in automobiles based on secure and reliable SOA. This method can automate and integrate the generation, review, encryption, and deployment processes of service configuration files into the service provider, ensuring the authenticity, integrity, and confidentiality of service configuration files, while achieving centralized control over system resource overhead, thereby improving the security and reliability of in-vehicle SOA communication.

[0006] A method for acquiring service data for automobiles based on secure and reliable SOA, the key of which includes the following steps:

[0007] S1: Construct an SOA service data acquisition system, which includes a service provider and N in-vehicle domain controllers. , ...

[0008] S2: The service provider generates N service configuration files. , ... N service configuration files , ... With the N domain controllers , ... In a one-to-one correspondence, the service provider also configures the N service profiles respectively. , ... Encryption is performed, generating N encrypted service configuration files. , ... ;

[0009] S3: The service provider encrypts the N service configuration files. , ... Distributed one-to-one to the N domain controllers , ... ;

[0010] S4: The N domain controllers , ... Configure encryption files for each of the N services. , ... Decryption is performed, and the service configuration file, which is parsed and restored to correspond one-to-one with the domain controller's services, is loaded. , ... .

[0011] The above method stores and transmits service configuration files in encrypted form, effectively preventing malicious tampering or snooping on the service configuration files when they are distributed to and stored in the domain controller. Even if an attacker obtains the service configuration files, they cannot directly obtain or modify valid service configuration information, greatly improving the ability to resist malicious attacks.

[0012] Furthermore, the service provider is equipped with a service configuration formulation unit, an audit unit, and a compilation server, wherein the service configuration formulation unit and the audit unit communicate bidirectionally, and the audit unit is connected to the compilation server;

[0013] The compilation server is equipped with a compilation module and an encryption module;

[0014] Each of the domain controllers is equipped with a firmware image and a decryption module, and the firmware image stores encrypted service configuration files.

[0015] Furthermore, step S2 includes the following steps:

[0016] S21: The service configuration formulation unit constructs a global service configuration table, which has data record areas corresponding one-to-one with the N domain controllers. , ... Each data record area contains the service configuration data of the corresponding domain controller;

[0017] S22: The service configuration formulation unit sends the global service configuration table to the review unit, and the review unit reviews the N data record areas respectively. , ... The service configuration data in the system were reviewed one by one;

[0018] If any service configuration data in any data record area fails the review, it is marked as unapproved service configuration data and the service configuration data is fed back to the service configuration designation unit for modification;

[0019] If any service configuration data passes the review, the service configuration data will be sent directly to the compilation module.

[0020] S23: The compilation module respectively calculates based on N data record areas , ... The service configuration data in the data is used to generate the N domain controllers. , ... The service configuration files that correspond one-to-one , ... And respectively in the N service configuration files , ... The above is configured with the N domain controllers , ... One-to-one corresponding type markers;

[0021] S24: The encryption module respectively verifies the N service configuration files. , ... Encryption is performed to generate encrypted service configuration files that correspond one-to-one with the N domain controllers. , ... .

[0022] The above method, through a mandatory audit process, pre-screens and constrains the resource consumption of service configuration data contained in each data record area, avoiding excessive occupation and waste of system resources and ensuring the stability and performance of the entire vehicle software system. Furthermore, all modifications to service configuration data are made through the audit unit, leaving clear modification records and audit logs, facilitating problem tracking and identification.

[0023] Meanwhile, the above method generates service configuration files through automated scripts in the compilation module, eliminating erroneous service configuration data introduced by manual modification, ensuring the accuracy of service configuration data in the service configuration file, and ensuring the reliable establishment of service communication links.

[0024] Furthermore, each of the service configuration data includes the address of the corresponding domain controller, port number, maximum number of threads required, and service discovery timeout.

[0025] The steps for the audit module to audit any one of the service configuration data include:

[0026] The auditing unit audits the address of the domain controller;

[0027] If the domain controller's address is incorrect, the auditing unit marks the domain controller's address and sends it back to the service configuration specification unit for modification.

[0028] If the domain controller's address is correct, the auditing unit audits the domain controller's port number;

[0029] If the port number of the domain controller is incorrect, the auditing unit marks the port number of the domain controller and sends the feedback to the service configuration specification unit for modification;

[0030] If the domain controller's port number is correct, the auditing unit determines whether the domain controller's required maximum number of threads equals the maximum standard number of threads. for:

[0031]

[0032] in, The frequency of the signals serving the domain controller. To round up;

[0033] If the maximum number of threads required by a domain controller is not equal to the maximum standard number of threads, the auditing unit marks the maximum number of threads required by the domain controller and sends the feedback to the service configuration specification unit for modification.

[0034] If the maximum number of threads required by the domain controller is equal to the standard maximum number of threads, the audit unit determines whether the service discovery timeout of the domain controller is equal to the standard service discovery timeout:

[0035] If the service discovery timeout of a domain controller is not equal to the standard service discovery timeout, the auditing unit marks the service discovery timeout of the domain controller and sends the feedback to the service configuration specification unit for modification.

[0036] If the service discovery timeout of the domain controller is equal to the standard service discovery timeout, then the service configuration data is sent to the compilation module.

[0037] The standard service discovery timeout for each domain controller is preset based on the domain controller model and the domain controller's execution functions.

[0038] Furthermore, the encryption module encrypts any service configuration file, including the following steps:

[0039] S241: The encryption module identifies the type flag carried in the service configuration file and selects the encryption strategy corresponding to the type flag according to the encryption strategy mapping table;

[0040] S242: The encryption module uses the corresponding encryption strategy to encrypt the service configuration file and generate an encrypted service configuration file;

[0041] S243: The encryption module sets encryption markers on the service configuration encryption file that correspond one-to-one with the encryption policy according to the corresponding encryption policy.

[0042] The above method introduces an automatic tag recognition mechanism, establishes a mapping relationship between type tags and differentiated encryption algorithms, and uses any type tag as an index to search in the encryption policy mapping table to match the corresponding encryption policy for any service configuration file. Each encryption policy is designed for the different security needs and performance requirements of each domain controller, realizing fine-grained configuration of security policies and building a complete, end-to-end differentiated encryption-decryption link, providing flexible and powerful security protection for the whole vehicle software system.

[0043] Furthermore, the encryption strategy may be as follows: the encryption strategy mapping table records all the type tags, each type tag maps to an encryption key, and each encryption key is set with a corresponding encryption algorithm;

[0044] The encryption key of the type tag mapping is combined with the corresponding encryption algorithm to encrypt the corresponding service configuration file;

[0045] The encryption strategy may be: the encryption strategy mapping table records all the type tags, and each type tag is mapped to an encryption key and at least one encryption algorithm;

[0046] The encryption key of the type tag mapping is combined with any encryption algorithm of the same type tag mapping to encrypt the corresponding service configuration file.

[0047] A single encryption key can be freely combined with multiple encryption methods to perform secondary encryption on specific service configuration files, further improving the encryption effectiveness of the service configuration files.

[0048] Furthermore, the encryption tokens include encryption key tokens that correspond one-to-one with the encryption keys, and encryption algorithm tokens that correspond one-to-one with the encryption methods.

[0049] Furthermore, the encryption policy mapping table, all the keys, and all the encryption methods are pre-installed in the secure storage area of ​​the encryption module.

[0050] The encryption policy mapping table, keys, and encryption methods are not distributed to the domain controller.

[0051] Furthermore, any one of the domain controllers decrypts the corresponding service configuration encryption file, including the following steps:

[0052] S41: The decryption module reads the service configuration encryption file from the firmware image;

[0053] S42: The decryption module identifies the encryption marker carried in the service configuration encryption file and selects the decryption strategy corresponding to the encryption marker carried according to the decryption strategy mapping table;

[0054] S43: The decryption module uses the corresponding decryption strategy to decrypt the service configuration encrypted file and generate the service configuration file.

[0055] The encryption module injects encryption tokens into the encrypted data, providing guidance for dynamic decryption when the domain controller runs service configuration files.

[0056] Furthermore, the decryption strategy mapping table records all the encryption key tags and all the encryption algorithm tags, wherein: each encryption key tag corresponds to a decryption key, and each encryption algorithm tag corresponds to a decryption method;

[0057] The decryption key of the encryption key mark mapping is combined with the decryption method of the encryption algorithm mark mapping to decrypt the corresponding service configuration encryption file;

[0058] The decryption policy mapping table, all decryption keys, and all decryption methods are pre-installed in the secure storage area of ​​the domain controller.

[0059] Beneficial effects: 1. The present invention introduces an audit unit to pre-examine and constrain the resource consumption of service instances contained in each data record area, thereby achieving control over resource allocation and leaving clear modification records and audit logs on the audit unit, which facilitates the tracking and delineation of problems.

[0060] 2. This invention also introduces an automated script that automatically converts the domain controller address, port number, maximum number of threads required, and service discovery timeout in each data record area into a service configuration file. This avoids errors caused by manual intervention, ensures the accuracy of the service configuration data in the service configuration file, and ensures the reliable establishment of the service communication link.

[0061] 3. The service configuration files in this invention are stored and transmitted in encrypted form, effectively preventing malicious tampering or eavesdropping during the distribution and storage of service configuration files. Even if an attacker obtains the encrypted service configuration file, they cannot directly obtain or modify valid service configuration information, greatly enhancing the ability to resist malicious attacks.

[0062] 4. This invention introduces an automatic type tag identification mechanism during the encryption process. Through the mapping relationship between type tags and differentiated encryption strategies, it realizes fine-grained configuration of encryption of different service configuration files. Encryption tags are injected into the encrypted files, providing guidance for dynamic decryption when the domain controller runs the service configuration files. This constructs a complete, end-to-end differentiated encryption-decryption link, providing flexible and powerful security.

[0063] In summary, this invention enables domain controllers in automobiles to have high reliability, traceability, high security, and high flexibility in both the process of obtaining and using service configuration files. Attached Figure Description

[0064] Figure 1 This is a schematic diagram of the process of the present invention;

[0065] Figure 2 A schematic diagram of the data acquisition system architecture for SOA services. Detailed Implementation

[0066] The specific embodiments and working principles of the present invention will be further described in detail below with reference to the accompanying drawings.

[0067] like Figure 1 As shown, a method for acquiring service data for automobiles based on secure and reliable SOA includes the following steps:

[0068] S1: Construct an SOA service data acquisition system, which includes a service provider and N in-vehicle domain controllers. , ... ;

[0069] like Figure 2 As shown, the service provider is equipped with a service configuration formulation unit, an audit unit, and a compilation server. The service configuration formulation unit and the audit unit communicate bidirectionally, and the audit unit is connected to the compilation server.

[0070] The compilation server is equipped with a compilation module and an encryption module. The encryption module has a pre-set encryption policy mapping table in its secure storage area, as well as all keys and encryption methods recorded on the encryption policy mapping table.

[0071] Each of the domain controllers is equipped with a firmware image and a decryption module, wherein: the firmware image stores encrypted service configuration files, and the secure storage area of ​​the domain controller contains a pre-configured decryption policy mapping table, as well as all decryption keys and all decryption methods recorded in the decryption policy mapping table:

[0072] S2: The service provider generates N service configuration files. , ... N service configuration files , ... With the N domain controllers , ... In a one-to-one correspondence, the service provider also configures the N service profiles respectively. , ... Encryption is performed, generating N encrypted service configuration files. , ... ;

[0073] S21: The service configuration formulation unit constructs a global service configuration table, which has data record areas corresponding one-to-one with the N domain controllers. , ... Each data record area contains the service configuration data of the corresponding domain controller;

[0074] When building the global service configuration table, developers upload the service configuration data required by N domain controllers to N data record areas respectively. , ... ;

[0075] S22: The service configuration formulation unit sends the global service configuration table to the review unit, and the review unit reviews the N data record areas respectively. , ... The service configuration data in the database is reviewed one by one. Each service configuration data includes the address of the corresponding domain controller, port number, maximum number of threads required, and service discovery timeout.

[0076] The steps for the audit module to audit any one of the service configuration data include:

[0077] The auditing unit audits the address of the domain controller;

[0078] If the domain controller's address is incorrect, the auditing unit marks the domain controller's address and sends it back to the service configuration specification unit for modification.

[0079] If the domain controller's address is correct, the auditing unit audits the domain controller's port number;

[0080] If the port number of the domain controller is incorrect, the auditing unit marks the port number of the domain controller and sends the feedback to the service configuration specification unit for modification;

[0081] If the domain controller's port number is correct, the auditing unit determines whether the domain controller's required maximum number of threads equals the maximum standard number of threads. for:

[0082]

[0083] in, The frequency of the signals serving the domain controller. To round up;

[0084] If the maximum number of threads required by a domain controller is not equal to the maximum standard number of threads, the auditing unit marks the maximum number of threads required by the domain controller and sends the feedback to the service configuration specification unit for modification.

[0085] If the maximum number of threads required by the domain controller is equal to the standard maximum number of threads, the audit unit determines whether the service discovery timeout of the domain controller is equal to the standard service discovery timeout:

[0086] If the service discovery timeout of a domain controller is not equal to the standard service discovery timeout, the auditing unit marks the service discovery timeout of the domain controller and sends the feedback to the service configuration specification unit for modification.

[0087] If the service discovery timeout of the domain controller is equal to the standard service discovery timeout, then the service configuration data is sent to the compilation module.

[0088] The standard service discovery timeout for each of the above domain controllers should be set based on the domain controller's chip type and operating software.

[0089] S23: The compilation module respectively calculates based on N data record areas , ... The service configuration data in the data is used to generate the N domain controllers. , ... The service configuration files that correspond one-to-one , ... And respectively in the N service configuration files , ... The above is configured with the N domain controllers , ... One-to-one corresponding type markers;

[0090] S24: The encryption module respectively verifies the N service configuration files. , ... Encryption is performed to generate encrypted service configuration files that correspond one-to-one with the N domain controllers. , ... ;

[0091] The encryption module encrypts any service configuration file, including the following steps:

[0092] S241: The encryption module identifies the type marker carried by the service configuration file, and uses the carried type marker as an index to search and match on the encryption policy mapping table, and selects the encryption policy corresponding to the carried type marker. Each encryption policy includes a key and an encryption method.

[0093] S242: The encryption module uses the corresponding encryption strategy to encrypt the service configuration file and generate an encrypted service configuration file;

[0094] S243: The encryption module sets encryption markers on the service configuration encryption file according to the corresponding encryption policy. The encryption markers include encryption key markers that correspond to the encryption key and encryption algorithm markers that correspond to the encryption method.

[0095] Example 1:

[0096] The encryption strategy is as follows: the encryption strategy mapping table records all the type tags, each type tag maps to an encryption key, and each encryption key is set with a corresponding encryption algorithm;

[0097] The encryption key of the type tag mapping is combined with the corresponding encryption algorithm to encrypt the corresponding service configuration file;

[0098] For example: the encryption policy mapping table records the cockpit tag corresponding to the cockpit domain controller and the intelligent driving tag corresponding to the intelligent driving domain controller, wherein:

[0099] The cockpit tag map has an encryption key Key_Cockpit, which is equipped with the encryption algorithm AES-256-GCM;

[0100] The intelligent driving tag mapping has an encryption key Key_ADU, which is equipped with the national standard encryption algorithm SM4.

[0101] Taking the encrypted cockpit domain configuration service file as an example: First, the encryption module identifies the cockpit tag carried in the encrypted cockpit domain configuration service file, and searches the encryption policy mapping table with the cockpit tag as an index. According to the cockpit tag mapping relationship recorded in the encryption policy mapping table, the encryption module calls the encryption key Key_Cockpit and the encryption algorithm AES-256-GCM from the secure storage area of ​​the encryption module to encrypt the cockpit domain configuration service file, generating an encrypted cockpit domain configuration service file. Then, the encryption module sets the encryption key tag Cockpit, which corresponds one-to-one with the encryption key Key_Cockpit, and the encryption algorithm tag AES-256-GCM, which corresponds one-to-one with the encryption algorithm AES-256-GCM, on the encrypted cockpit domain configuration service file according to the encryption key Key_Cockpit and the encryption algorithm tag AES-256-GCM.

[0102] Example 2:

[0103] The encryption strategy is as follows: the encryption strategy mapping table records all the type tags, and each type tag is mapped to an encryption key and at least one encryption algorithm;

[0104] The encryption key of the type tag mapping is combined with any encryption algorithm of the same type tag mapping to encrypt the corresponding service configuration file;

[0105] For example: the encryption policy mapping table records the cockpit tag corresponding to the cockpit domain controller and the intelligent driving tag corresponding to the intelligent driving domain controller, wherein:

[0106] The cockpit tag is mapped to the encryption key Key_Cockpit, and the cockpit tag is also mapped to the encryption algorithms AES-256-GCM and AES-256-CBC.

[0107] The intelligent driving tag is mapped to an encryption key Key_ADU, and the intelligent driving tag is also mapped to the national cryptographic algorithm SM4.

[0108] Taking the encrypted cockpit domain configuration service file as an example:

[0109] Method 1: First, the encryption module identifies the cockpit marker carried in the encrypted cockpit domain configuration service file and searches the encryption policy mapping table using the cockpit marker as an index. Based on the cockpit marker mapping relationship recorded in the encryption policy mapping table, it retrieves the encryption key Key_Cockpit and encryption algorithm AES-256-GCM from the encryption module's secure storage area to encrypt the cockpit domain configuration service file, generating an encrypted cockpit domain configuration service file. Then, the encryption module sets an encryption marker Cockpit corresponding one-to-one with the encryption key Key_Cockpit and an encryption algorithm marker AES-256-GCM corresponding one-to-one with the encryption algorithm AES-256-GCM on the encrypted cockpit domain configuration service file.

[0110] Method 2: First, the encryption module identifies the cockpit tag carried in the encrypted cockpit domain configuration service file and searches the encryption policy mapping table using the cockpit tag as an index. Based on the cockpit tag mapping relationship recorded in the encryption policy mapping table, it retrieves the encryption key Key_Cockpit and encryption algorithm AES-256-CBC from the encryption module's secure storage area to encrypt the cockpit domain configuration service file, generating an encrypted cockpit domain configuration service file. Then, the encryption module sets an encryption tag Cockpit corresponding one-to-one with the encryption key Key_Cockpit and an encryption algorithm tag AES-256-CBC corresponding one-to-one with the encryption algorithm AES-256-CBC on the encrypted cockpit domain configuration service file.

[0111] In both of the above methods, the encryption module randomly selects the AES-256-GCM and AES-256-CBC encryption algorithms for the cockpit tag mapping.

[0112] S3: The service provider encrypts the N service configuration files. , ... Distributed one-to-one to the N domain controllers , ... Within the firmware image;

[0113] S4: The N domain controllers , ... Configure encryption files for each of the N services. , ... Decryption is performed, and the service configuration file, which is parsed and restored to correspond one-to-one with the domain controller's services, is loaded. , ... ;

[0114] Each of the domain controllers decrypts the corresponding service configuration encryption file, including the following steps:

[0115] S41: The decryption module reads the service configuration encryption file from the firmware image;

[0116] S42: The decryption module identifies the encryption marker carried in the service configuration encryption file and selects the decryption strategy corresponding to the encryption marker carried according to the decryption strategy mapping table;

[0117] S43: The decryption module uses the corresponding decryption strategy to decrypt the service configuration encrypted file and generate the service configuration file.

[0118] The decryption strategy is as follows: the decryption strategy mapping table records all the encryption key tags and all the encryption algorithm tags, wherein: each encryption key tag corresponds to a decryption key, and each encryption algorithm tag corresponds to a decryption method;

[0119] The decryption key of the encryption key mark mapping is combined with the decryption method of the encryption algorithm mark mapping to decrypt the corresponding service configuration encryption file;

[0120] Here, we take the cockpit domain configuration service encrypted file in Embodiment 1 above as an example for decryption: First, the decryption module in the cockpit domain controller reads the cockpit domain service configuration encrypted file from the firmware image in the cockpit domain controller. The decryption module identifies the encryption tag Cockpit and the encryption method tag AES-256-GCM carried in the cockpit domain configuration service encrypted file, and searches in the decryption policy mapping table using the encryption tag Cockpit and the encryption method tag AES-256-GCM as indices respectively. According to the mapping relationship of the encryption tag Cockpit and the encryption method tag AES-256-GCM recorded in the decryption policy mapping table, the decryption key Key_Cockpit and the decryption algorithm AES-256-GCM are called from the secure storage area of ​​the cockpit domain controller to decrypt the cockpit domain configuration service encrypted file and generate the cockpit domain configuration service file.

[0121] In the above method, type and encryption tags can be set on the filename, which makes it easier for the encryption and decryption modules to quickly identify and call the corresponding encryption and decryption strategies.

Claims

1. A method for acquiring service data for automobiles based on secure and reliable SOA, characterized in that, Includes the following steps: S1: Construct an SOA service data acquisition system, which includes a service provider and N in-vehicle domain controllers. , ... ; S2: The service provider generates N service configuration files. , ... N service configuration files , ... With the N domain controllers , ... In a one-to-one correspondence, the service provider also configures the N service profiles respectively. , ... Encryption is performed, generating N encrypted service configuration files. , ... ; S3: The service provider encrypts the N service configuration files. , ... Distributed one-to-one to the N domain controllers , ... ; S4: The N domain controllers , ... Configure encryption files for each of the N services. , ... Decryption is performed, and the service configuration file, which is parsed and restored to correspond one-to-one with the domain controller's services, is loaded. , ... .

2. The method for acquiring service data of automobiles based on secure and reliable SOA according to claim 1, characterized in that, The service provider is equipped with a service configuration formulation unit, an audit unit, and a compilation server. The service configuration formulation unit and the audit unit communicate bidirectionally, and the audit unit is connected to the compilation server. The compilation server is equipped with a compilation module and an encryption module; Each of the domain controllers is equipped with a firmware image and a decryption module, and the firmware image stores encrypted service configuration files.

3. The method for acquiring service data of a vehicle based on a secure and reliable SOA according to claim 2, characterized in that, Step S2 includes the following steps: S21: The service configuration formulation unit constructs a global service configuration table, which has data record areas corresponding one-to-one with the N domain controllers. , ... Each data record area contains the service configuration data of the corresponding domain controller; S22: The service configuration formulation unit sends the global service configuration table to the review unit, and the review unit reviews the N data record areas respectively. , ... The service configuration data in the system were reviewed one by one; If any service configuration data in any data record area fails the review, it is marked as unapproved service configuration data and the service configuration data is fed back to the service configuration designation unit for modification; If any service configuration data passes the review, the service configuration data will be sent directly to the compilation module. S23: The compilation module respectively calculates based on N data record areas , ... The service configuration data in the data is used to generate the N domain controllers. , ... The service configuration files that correspond one-to-one , ... And respectively in the N service configuration files , ... The above is configured with the N domain controllers , ... One-to-one corresponding type markers; S24: The encryption module respectively verifies the N service configuration files. , ... Encryption is performed to generate encrypted service configuration files that correspond one-to-one with the N domain controllers. , ... .

4. The method for acquiring service data of a vehicle based on a secure and reliable SOA according to claim 3, characterized in that, Each of the service configuration data includes the address of the corresponding domain controller, port number, maximum number of threads required, and service discovery timeout. The steps for the audit module to audit any one of the service configuration data include: The auditing unit audits the address of the domain controller; If the domain controller's address is incorrect, the auditing unit marks the domain controller's address and sends it back to the service configuration specification unit for modification. If the domain controller's address is correct, the auditing unit audits the domain controller's port number; If the port number of the domain controller is incorrect, the auditing unit marks the port number of the domain controller and sends the feedback to the service configuration specification unit for modification; If the domain controller's port number is correct, the auditing unit determines whether the domain controller's required maximum number of threads equals the maximum standard number of threads. for: in, The frequency of the signals serving the domain controller. To round up; If the maximum number of threads required by a domain controller is not equal to the maximum standard number of threads, the auditing unit marks the maximum number of threads required by the domain controller and sends the feedback to the service configuration specification unit for modification. If the maximum number of threads required by the domain controller is equal to the standard maximum number of threads, the audit unit determines whether the service discovery timeout of the domain controller is equal to the standard service discovery timeout: If the service discovery timeout of a domain controller is not equal to the standard service discovery timeout, the auditing unit marks the service discovery timeout of the domain controller and sends the feedback to the service configuration specification unit for modification. If the service discovery timeout of the domain controller is equal to the standard service discovery timeout, then the service configuration data is sent to the compilation module.

5. A method for acquiring service data for automobiles based on secure and reliable SOA according to claim 3, characterized in that, The encryption module encrypts any service configuration file, including the following steps: S241: The encryption module identifies the type flag carried in the service configuration file and selects the encryption strategy corresponding to the type flag according to the encryption strategy mapping table; S242: The encryption module uses the corresponding encryption strategy to encrypt the service configuration file and generate an encrypted service configuration file; S243: The encryption module sets encryption markers on the service configuration encryption file that correspond one-to-one with the encryption policy according to the corresponding encryption policy.

6. The method for acquiring service data of a vehicle based on a secure and reliable SOA according to claim 5, characterized in that, The encryption strategy may be as follows: the encryption strategy mapping table records all the type tags, each type tag maps to an encryption key, and each encryption key is configured with a corresponding encryption algorithm; The encryption key of the type tag mapping is combined with the corresponding encryption algorithm to encrypt the corresponding service configuration file; The encryption strategy may be: the encryption strategy mapping table records all the type tags, and each type tag is mapped to an encryption key and at least one encryption algorithm; The encryption key of the type tag mapping is combined with any encryption algorithm of the same type tag mapping to encrypt the corresponding service configuration file.

7. A method for acquiring service data for automobiles based on secure and reliable SOA according to claim 6, characterized in that, The encryption tokens include encryption key tokens that correspond one-to-one with the encryption keys and encryption algorithm tokens that correspond one-to-one with the encryption methods.

8. A method for acquiring service data for automobiles based on secure and reliable SOA according to claim 6, characterized in that, The encryption policy mapping table, all the keys, and all the encryption methods are pre-stored in the secure storage area of ​​the encryption module.

9. A method for acquiring service data for automobiles based on secure and reliable SOA according to claim 7, characterized in that, Each of the domain controllers decrypts the corresponding service configuration encryption file, including the following steps: S41: The decryption module reads the service configuration encryption file from the firmware image; S42: The decryption module identifies the encryption marker carried in the service configuration encryption file and selects the decryption strategy corresponding to the encryption marker carried according to the decryption strategy mapping table; S43: The decryption module uses the corresponding decryption strategy to decrypt the service configuration encrypted file and generate the service configuration file.

10. A method for acquiring service data for automobiles based on secure and reliable SOA according to claim 9, characterized in that, The decryption strategy is as follows: the decryption strategy mapping table records all the encryption key tags and all the encryption algorithm tags, wherein: each encryption key tag corresponds to a decryption key, and each encryption algorithm tag corresponds to a decryption method; The decryption key of the encryption key mark mapping is combined with the decryption method of the encryption algorithm mark mapping to decrypt the corresponding service configuration encryption file; The decryption policy mapping table, all decryption keys, and all decryption methods are pre-installed in the secure storage area of ​​the domain controller.

Images