Data fusion communication method and device, vehicle and medium

Abstract

The invention relates to the technical field of vehicles, in particular to a data fusion communication method and device, a vehicle and a medium, and the method comprises the steps: obtaining a plurality of pieces of sensor data received in a service data bus service process; converting the sensor data into corresponding formatted data; and generating a corresponding publisher instance and a corresponding data theme according to the formatted data structure, screening formatted data corresponding to a target data theme according to the target data theme subscribed by the client, encrypting and serializing the formatted data, and transmitting the formatted data to the data subscription end. Therefore, the problems that in the related technology, repeated redundant data exists in theme data created by all application processes, multiple applications have requirements for out-of-domain data, the software development and maintenance cost is increased, manpower and time resources are wasted, and data transmission is lack of safety are solved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a data fusion communication method, device, vehicle and medium. Background Art

[0002] In the related technology, the common method of cabin-driver integrated communication is to directly create a DDS / SOMEIP subscriber instance inside the application of an intelligent cockpit system, directly subscribe to receive data from the intelligent driving domain in the application process, then perform deserialization operations, and then perform decryption operations to finally obtain the data in plain text. After obtaining the plain text data in the intelligent driving domain, the application process performs business calculations based on its own business logic. If there are multiple applications that have demand for out-of-domain data, each application reuses this method to obtain data; the general steps are:

[0003] Step 1: In the intelligent driving system, run an application, create a DDS / SOMEIP publisher instance in the application process, and publish the data topic to the outside; Step 2: In the intelligent driving system, the application involved in step 1 performs encryption operations on the data to be published, then performs serialization operations, and then sends it out; Step 3: An application in the intelligent cockpit system creates a DDS / SOMEIP subscriber instance in the application process and subscribes to the data topic it needs; Step 4: In the intelligent cockpit system, the application involved in step 3 receives the data sent by the DDS / SOMEIP publisher; Step 5: In the intelligent cockpit system, the application involved in step 3 deserializes the received data, and then performs decryption operations to obtain plaintext data; Step 6: In the intelligent cockpit system, the application involved in step 3 uses the plaintext data obtained in step 5 to perform business logic calculations.

[0004] In summary, if there are multiple application processes in this application that create multiple DDS / SOMEIP publisher instances to publish topics to the outside world, there will be duplicate and redundant data between the data corresponding to each topic due to the different application providers and implementers; the generation timing, timestamp and encryption mechanism are not unified; the existence of multiple applications that have requirements for off-domain data leads to a large number of repeated parts in software development work, which increases the cost of software development and maintenance, and wastes manpower and time resources; in terms of sensitive data, there is a lack of unified filtering and desensitization processing, and for applications with data desensitization requirements, it is impossible to unify configuration management, etc. Summary of the invention

[0005] The present application provides a data fusion communication method, device, vehicle and medium to solve the problems in the related technology that the subject data created by each application process has duplicate redundant data, and the existence of multiple applications that have demand for off-domain data increases the cost of software development and maintenance, wastes manpower and time resources, and lacks security in data transmission.

[0006] The first aspect of the present application provides a data fusion communication method, which is applied to a data publishing end, wherein the method includes the following steps: acquiring multiple sensor data received within a business data bus service process; converting the sensor data into corresponding formatted data; generating a corresponding publisher instance and a corresponding data topic according to the formatted data structure, and according to a target data topic subscribed by a client, screening the formatted data corresponding to the target data topic, encrypting and serializing the data, and then transmitting it to the data subscriber.

[0007] The second aspect of the present application provides a data fusion communication method, which is applied to a data subscription end, wherein the method includes the following steps: obtaining data corresponding to a target data topic that a client requests to subscribe to and sent by a data publishing end; deserializing the data and restoring it to original formatted data, and decrypting the original formatted data to generate plaintext data; calling a preset interface according to the plaintext data to trigger a whitelist access control module, wherein the whitelist access control module matches the corresponding query results according to the plaintext data; and generating a subscription result according to the query result.

[0008] Optionally, before obtaining the data corresponding to the target data topic that the client requests to subscribe to and sent by the data publisher, it includes: obtaining the target data topic that the client requests to subscribe to; generating a subscriber instance according to the target data topic, and sending it to the data publisher.

[0009] Optionally, before invoking a preset excuse according to the plaintext data to trigger a whitelist access control module, the method includes: identifying a type of the subscriber instance; and executing a target operation according to the type of the subscriber instance.

[0010] Optionally, executing the target operation according to the type of the subscriber instance includes: if the type of the subscriber instance is an out-of-domain data topic, registering a data callback interface with a local business data bus service process, and calling an interface for subscribing to the out-of-domain data topic.

[0011] Optionally, calling a preset excuse based on the plaintext data to trigger a whitelist access control module includes: checking whether the application initiating registration is in the whitelist that allows access to out-of-domain data; if the registered application is not in the whitelist that allows access to out-of-domain data, returning a registration failure result; if the registered application is in the whitelist that allows access to out-of-domain data, creating a subscriber instance according to actual needs to subscribe to out-of-domain data.

[0012] The third aspect of the present application provides a data fusion communication device, which is applied to a data publishing end, wherein the device includes: a first acquisition module, used to acquire multiple sensor data; a conversion module, used to convert the sensor data into corresponding formatted data; a transmission module, used to generate a corresponding publisher instance and a corresponding data topic according to the formatted data structure, and according to the target data topic subscribed by the client, screen the formatted data corresponding to the target data topic, encrypt and serialize it, and then transmit it to the data subscriber.

[0013] The fourth aspect of the present application provides a data fusion communication device, which is applied to a data subscription end, wherein the device includes: a second acquisition module, used to obtain data corresponding to a target data topic that a client requests to subscribe to and sent by a data publishing end; a restoration module, used to deserialize and restore the data to original formatted data, and decrypt the original formatted data to generate plaintext data; a trigger module, used to call a preset interface according to the plaintext data to trigger a whitelist access control module, wherein the whitelist access control module matches the corresponding query result according to the plaintext data; and a generation module, used to generate a subscription result according to the query result.

[0014] A fifth aspect of the present application provides a vehicle, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to perform the data fusion communication method as described in the above embodiment.

[0015] A sixth aspect of the present application provides a computer-readable storage medium on which a computer program is stored. The program is executed by a processor to perform the data fusion communication method as described in the above embodiment.

[0016] Therefore, this application has at least the following beneficial effects:

[0017] (1) In the local business data bus service process of the embodiment of the present application, local sensor data is received, and business processing and formatting are performed on the data; a publisher instance is created, a topic is published, data is encrypted, serialized, and sent; the local business data bus service and its developers uniformly check data duplication and redundancy, reasonably arrange the data generation sequence, uniformly timestamp the data, and select a unified encryption method to encrypt the data, thereby ensuring data security and avoiding duplicate data.

[0018] (2) In the embodiment of the present application, the operations of creating a subscriber instance, subscribing to a topic, receiving data, deserializing, and decrypting data are all run in the local business data bus process; only one corresponding code module is stored in the business data bus project, and there is no duplication, which simplifies the modification / expansion / upgrade work of the software module.

[0019] (3) The embodiment of the present application uses a system cache to provide multiple application processes with the same data requirements. Even if there are multiple application processes subscribing to the same topic data locally, the DDS / SOMEIP publisher only needs to transmit the data to the client once. At the same time, only one topic data is saved in the system cache for the same topic in the system, which reduces network bandwidth usage, reduces network transmission traffic, and avoids repeated application of system memory to save data with the same content.

[0020] (4) In terms of data security, the embodiment of the present application performs unified data decryption operations and unified whitelist access control in the business data bus service process; the whitelist is pre-configured by the developer and can be modified as needed; the upper-layer applications in the smart cockpit system, whether developed by the developer or by a third party, cannot directly access the entire set of data encryption and decryption algorithms. At the same time, the whitelist mechanism can also effectively prevent malware from obtaining sensitive data, thereby improving data security.

[0021] (5) In terms of sensitive data desensitization, the embodiment of the present application performs unified data filtering and desensitization processing in the business data bus service process, combines the whitelist mechanism, and allocates desensitized data and original data according to business needs;

[0022] (6) The business data bus service of the embodiment of the present application provides a unified API interface and a unified data format; the business data bus service provides a unified interface for subscribing to data topics, a unified data callback interface, and a unified data format. For changes in the data format provided by the external DDS / SOMEIP publisher, the business data bus service will make modifications and adaptations to isolate the shock caused by the data format change, so that the shock will not be transmitted to the upper-level application.

[0023] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0025] Figure 1 A flowchart of a data fusion communication method provided according to an embodiment of the present application;

[0026] Figure 2 A flowchart of a data fusion communication method provided according to another embodiment of the present application;

[0027] Figure 3A schematic diagram of publishing and subscribing to data topics between the smart cockpit domain and the smart driving domain according to an embodiment of the present application;

[0028] Figure 4 A flowchart of a process for reading data within a service data bus according to an embodiment of the present application;

[0029] Figure 5 A flowchart of a process of writing data into a service data bus according to an embodiment of the present application;

[0030] Figure 6 A flowchart of a whitelist control process for a subscription operation provided according to an embodiment of the present application;

[0031] Figure 7 A block diagram of a data fusion communication device provided according to an embodiment of the present application;

[0032] Figure 8 A block diagram of a data fusion communication device provided according to another embodiment of the present application;

[0033] Fig. 9 It is a schematic diagram of the structure of a vehicle provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0034] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0035] The existing technology has the following defects: (1) In the intelligent driving domain, if there are multiple application processes that create multiple DDS / SOMEIP publisher instances to publish topics externally, the following problems cannot be guaranteed due to different application providers and implementers:

[0036] A. Is there any duplicate or redundant data between the data corresponding to each topic?

[0037] B. Whether the generation sequence of each subject data is strictly and uniformly controlled, and whether the timestamps of each subject data are uniformly generated;

[0038] C. Whether the encryption mechanism for each subject data is uniformly implemented;

[0039] (2) Within the smart cockpit domain, if there are multiple applications that require data outside the domain, the method steps in Question 2 need to be reused, resulting in a large amount of duplication in software development work, which increases software development and maintenance costs and wastes manpower and time resources.

[0040] (3) In the smart cockpit domain, when the software system is running, multiple applications obtain data with the same content, resulting in repeated transmission of the same data and multiple allocations of system memory (to store the same data). This occupies a larger network bandwidth, consumes more network traffic (internal vehicle Ethernet), and also occupies more system memory resources and computing power resources;

[0041] (4) In terms of data security within the smart cockpit domain, there is a lack of unified data decryption and user security authentication. For encrypted data from outside the domain, the decryption operation can only be repeated in each application process. This process exposes the entire data security mechanism of cross-domain communication to all application software and application developers, bringing great risks of leakage;

[0042] (5) There is a lack of unified filtering and desensitization processing for sensitive data within the smart cockpit domain, and there is no unified configuration management for applications that require data desensitization.

[0043] (6) For data information from outside the domain, there is no secondary encapsulation in the data structure and format. Once the data structure and format outside the domain change, each application can only modify its own code to adapt, and cannot effectively isolate the shock caused by the change.

[0044] Therefore, in order to solve the above-mentioned problem, the present application proposes a data fusion communication method, device, vehicle and medium.

[0045] Specifically, Figure 1 A flowchart of a data fusion communication method provided in an embodiment of the present application.

[0046] like Figure 1 As shown, the data fusion communication method is applied to a data publishing end, wherein the method comprises the following steps:

[0047] In step S101, a plurality of sensor data received inside the business data bus service process is obtained.

[0048] It is understandable that the embodiment of the present application can obtain multiple sensor data received within the business data bus service process, so as to subsequently convert the sensor data into corresponding formatted data.

[0049] It should be noted that multiple sensor data may include vehicle status information, environmental perception information, etc.

[0050] In step S102 , the sensor data is converted into corresponding formatted data.

[0051] It is understandable that the embodiments of the present application can convert the sensor data into corresponding formatted data, so as to facilitate the subsequent generation of a corresponding publisher instance and a corresponding data topic according to the formatted data structure.

[0052] It should be noted that the raw sensor data is cleaned to remove invalid or abnormal values; the validity and consistency of the data are verified to ensure data quality; the raw data is converted into a structured format, such as JSON, XML or a custom binary format, for subsequent processing and transmission; and the data is encoded according to the requirements of the DDS / SOMEIP protocol to make it a transmittable format.

[0053] In step S103, a corresponding publisher instance and a corresponding data topic are generated according to the formatted data structure, and according to the target data topic subscribed by the client, the formatted data corresponding to the target data topic is screened, encrypted and serialized, and then transmitted to the data subscriber.

[0054] It can be understood that the embodiments of the present application can generate a corresponding publisher instance and a corresponding data topic based on the formatted data structure, and according to the target data topic subscribed by the client, screen the formatted data corresponding to the target data topic, encrypt and serialize it, and then transmit it to the data subscriber, thereby processing the data according to the time sequence and timestamp, avoiding data redundancy, improving resource utilization, encrypting the data, and ensuring data security.

[0055] Specifically, the formatted data corresponding to the target data subject is filtered for processing, including: adding metadata such as timestamp and source identifier to the data, and packaging the processed data into the data packet format required by the DDS / SOMEIP protocol; creating a DDS / SOMEIP publisher instance based on the processed data; publishing the data subject through the DDS / SOMEIP protocol for subscription by the smart cockpit system; using the data encryption algorithm library to encrypt the data to be published; converting the encrypted data into a serialized format suitable for network transmission; and sending the serialized data to subscribers through the DDS / SOMEIP protocol.

[0056] According to the data fusion communication method proposed in the embodiment of the present application, multiple sensor data received inside the business data bus service process are obtained, and the sensor data are converted into corresponding formatted data, and a corresponding publisher instance and a corresponding data topic are generated according to the formatted data structure, and according to the target data topic subscribed by the client, the formatted data corresponding to the target data topic is screened, encrypted and serialized, and then transmitted to the data subscriber, so that the data is processed according to the time sequence and timestamp, avoiding data redundancy, improving resource utilization, encrypting the data, and ensuring data security.

[0057] Figure 2 A flowchart of a data fusion communication method provided in an embodiment of the present application.

[0058] like Figure 2 As shown, the data fusion communication method is applied to a data subscription end, wherein the method comprises the following steps:

[0059] In step S201, data corresponding to the target data topic that the client requests to subscribe to and sent by the data publisher is obtained.

[0060] It is understandable that the embodiment of the present application can obtain data corresponding to the target data topic sent by the data publisher and requested by the client to subscribe, so as to facilitate the subsequent deserialization and restoration of the data to the original formatted data.

[0061] In an embodiment of the present application, before obtaining the data corresponding to the target data topic that the client requests to subscribe to sent by the data publishing end, it includes: obtaining the target data topic that the client requests to subscribe to; generating a subscriber instance according to the target data topic, and sending it to the data publishing end.

[0062] It can be understood that the embodiment of the present application can obtain the target data topic that the client requests to subscribe to; generate a subscriber instance according to the target data topic, and send it to the data publishing end, thereby improving data processing efficiency.

[0063] In an embodiment of the present application, before calling a preset excuse according to plain text data to trigger a whitelist access control module, it includes: identifying the type of subscriber instance; and executing a target operation according to the type of subscriber instance.

[0064] It can be understood that the embodiments of the present application can identify the type of subscriber instance; perform target operations according to the type of subscriber instance to perform different processing methods on different data, reduce maintenance costs, and save resources.

[0065] For example, if the type of the subscriber instance is an out-of-domain data topic, the data callback interface is registered with the local business data bus service process, and the interface for subscribing to the out-of-domain data topic is called.

[0066] In step S202, the data is deserialized and restored to the original formatted data, and the original formatted data is decrypted to generate plaintext data.

[0067] It is understandable that the embodiments of the present application can deserialize the data to restore it to the original formatted data, and decrypt the original formatted data to generate plaintext data, so as to facilitate the subsequent generation of subscription results.

[0068] In step S203, the preset excuse is called according to the plain text data to trigger the whitelist access control module, wherein the whitelist access control module matches the corresponding query result according to the plain text data and generates a subscription result according to the query result.

[0069] It can be understood that the embodiments of the present application can call a preset excuse based on plaintext data to trigger a whitelist access control module, wherein the whitelist access control module matches the corresponding query results according to the plaintext data, and generates a subscription result based on the query results. The whitelist access control module is used to manage data security, which can effectively prevent malware from obtaining sensitive data.

[0070] In an embodiment of the present application, a whitelist access control module is triggered by calling a preset excuse based on plaintext data, including: checking whether the application initiating registration is in the whitelist that allows access to out-of-domain data; if the registered application is not in the whitelist that allows access to out-of-domain data, a registration failure result is returned; if the registered application is in the whitelist that allows access to out-of-domain data, a subscriber instance is created according to actual needs to subscribe to out-of-domain data.

[0071] It can be understood that the embodiment of the present application can check whether the application initiating registration is in the whitelist allowed to access out-of-domain data; if the registered application is not in the whitelist allowed to access out-of-domain data, a registration failure result is returned; if the registered application is in the whitelist allowed to access out-of-domain data, a subscriber instance is created according to actual needs to subscribe to out-of-domain data to ensure data security.

[0072] According to the data fusion communication method proposed in the embodiment of the present application, data corresponding to the target data topic that the client requests to subscribe to and sent by the data publishing end is obtained, the data is deserialized and restored to the original formatted data, and the original formatted data is decrypted to generate plaintext data. The preset interface is called according to the plaintext data to trigger the whitelist access control module, wherein the whitelist access control module matches the corresponding query results according to the plaintext data, and generates a subscription result according to the query results. The whitelist access control module is used to implement data security management, which can effectively prevent malicious software from obtaining sensitive data.

[0073] The following will be combined Figure 3-Figure 6 The data fusion communication method of the present application is described in detail, wherein the present application adopts an in-vehicle Ethernet gateway; hardware resources such as SOC, RAM, FLASH memory, and sensors such as cameras used in the smart cockpit system; SOC or MCU, RAM, FLASH memory, and sensor hardware devices such as cameras / lidar / millimeter wave radar used in the smart driving domain, and the smart driving system is used as the data publisher and the smart cockpit system is used as the subscriber as an example to describe, as follows:

[0074] 1. Processing flow of writing data inside the business data bus:

[0075] (1) receiving data from a data source (from a sensor);

[0076] (2) Perform business processing on the data and format the data structure;

[0077] (3) Data encryption to prevent data leakage during transmission;

[0078] (4) Data serialization, in preparation for data transmission;

[0079] (5) The data writer performs cross-domain data transmission.

[0080] 2. Processing flow of writing data inside the business data bus:

[0081] (1) receiving data from a data source (from a sensor);

[0082] (2) Perform business processing on the data and format the data structure;

[0083] (3) Data encryption to prevent data leakage during transmission;

[0084] (4) Data serialization, in preparation for data transmission;

[0085] (5) The data writer performs cross-domain data transmission.

[0086] 3. Whitelist control processing flow of subscription operation:

[0087] (1) The application that needs to subscribe to data calls the client interface corresponding to the local business data bus service;

[0088] (2) Trigger the subscription operation within the local business data bus service;

[0089] (3) Check the matching whitelist inside the local business data bus service;

[0090] If the corresponding application process does not have the subscription permission, the subscription failure is returned; if the corresponding application process has the subscription permission, a topic subscription operation is initiated to the publisher, and the publisher returns the subscription result.

[0091] 1. In the intelligent driving domain, the local business data bus service process receives local sensor data, processes and formats the data; creates a DDS / SOMEIP publisher instance and publishes the corresponding data topic to the outside world; in the local business data bus service, uniformly creates a DDS / SOMEIP publishing instance, publishes topics, encrypts data, serializes, and sends data;

[0092] The local business data bus service and its developers uniformly check data duplication and redundancy, reasonably arrange the data generation sequence, uniformly timestamp the data, and select a unified encryption method to encrypt the data;

[0093] 2. In the smart cockpit system, the application process registers the data callback interface with the local business data bus service process and calls the interface for subscribing to the out-of-domain data topic;

[0094] In the smart cockpit system, after receiving the subscription request in 1.2, the local business data bus service process first checks whether the application initiating the registration is in the whitelist that allows access to data outside the domain. If it is not in the whitelist, it returns a registration failure; if it is in the whitelist, it creates a DDS / SOMEIP subscriber instance to subscribe to data outside the domain. If subscribing to the same topic, only one DDS / SOMEIP subscriber instance is created.

[0095] In the smart cockpit system, once the local business data bus service process receives the out-of-domain data corresponding to the subscribed topic, it deserializes it, performs the corresponding decryption and desensitization operations, and writes the processed data into the cache (shared memory or message queue) in the local system. Another thread notifies the application that registered the interface and reads the data in the system cache within the application process.

[0096] 3. In the smart cockpit domain, create a DDS / SOMEIP subscriber instance, subscribe to topics, receive data, deserialize, and decrypt data, all of which are run in the local business data bus process;

[0097] Only one corresponding code module is stored in the business data bus project, and there is no duplication, which simplifies the modification / expansion / upgrade of the software module;

[0098] 4. In the smart cockpit domain, use a system cache (shared memory or message queue) to provide it to multiple application processes with the same data requirements;

[0099] Even if there are multiple local application processes subscribing to the same topic data, the DDS / SOMEIP publisher only needs to transmit the data to the client once. At the same time, in the smart cockpit system, only one copy of the topic data is saved in the system cache for the same topic. This reduces network bandwidth usage, reduces network transmission traffic, and avoids repeated application of system memory to save data with the same content;

[0100] 5. In terms of data security, in the business data bus service process of the smart cockpit system, unified data decryption operations and unified whitelist access control are performed. The whitelist is pre-configured by the developer and can be modified as needed.

[0101] The upper-layer applications in the smart cockpit system, whether they are self-developed applications or third-party applications, cannot directly access the entire set of data encryption and decryption algorithms. At the same time, the whitelist mechanism can also effectively prevent malicious software from obtaining sensitive data;

[0102] 6. In terms of sensitive data desensitization, in the business data bus service process in the smart cockpit system, unified data filtering and desensitization processing is performed, combined with the whitelist mechanism, and desensitized data and original data are allocated according to business needs;

[0103] 7. The business data bus service in the intelligent cockpit system provides a unified API interface and a unified data format;

[0104] The business data bus service provides a unified interface for subscribing to data topics, a unified data callback interface, and a unified data format. For changes in the data format provided by the external DDS / SOMEIP publisher, the business data bus service will make modifications and adaptations to isolate the shock caused by the data format change so that the shock will not be transmitted to the upper-level application.

[0105] It should be noted that the conditions required for this application are: in-vehicle Ethernet; both the smart cockpit system and the smart driving domain are connected to the same in-vehicle Ethernet network; SOA middleware DDS / SOMEIP protocol stack library; data encryption / decryption algorithm library; whitelist for obtaining out-of-domain data; data filtering and desensitizing algorithm library; business data bus service within the smart cockpit system; business data bus service within the intelligent driving system.

[0106] The business bus services in the two systems have different uses and functions because they are located in different domains, but they all focus on the business data in their own domains. What they have in common is that they both provide business data that meets the needs of upper-level applications, and provide upper-level applications with a unified API access interface, as well as a unified data structure and format.

[0107] In summary, (1) this application uniformly creates DDS / SOMEIP publishing instances, publishes topics, encrypts data, serializes, and sends data in the local business data bus service in the intelligent driving domain;

[0108] The local business data bus service and its developers uniformly check data duplication and redundancy, reasonably arrange the data generation sequence, uniformly timestamp the data, and select a unified encryption method to encrypt the data;

[0109] (2) In the smart cockpit domain, the operations of creating a DDS / SOMEIP subscriber instance, subscribing to topics, receiving data, deserializing, and decrypting data are all run in the local business data bus process;

[0110] Only one corresponding code module is stored in the business data bus project, and there is no duplication, which simplifies the modification / expansion / upgrade of the software module;

[0111] (3) In the smart cockpit domain, a system cache (shared memory or message queue) is used to provide multiple application processes with the same data requirements;

[0112] Even if there are multiple local application processes subscribing to the same topic data, the DDS / SOMEIP publisher only needs to transmit the data to the client once. At the same time, in the smart cockpit system, only one copy of the topic data is saved in the system cache for the same topic. This reduces network bandwidth usage, reduces network transmission traffic, and avoids repeated application of system memory to save data with the same content;

[0113] (4) In terms of data security, in the business data bus service process of the smart cockpit system, unified data decryption operations and unified whitelist access control are performed. The whitelist is pre-configured by the developer and can be modified as needed.

[0114] The upper-layer applications in the smart cockpit system, whether they are self-developed applications or third-party applications, cannot directly access the entire set of data encryption and decryption algorithms. At the same time, the whitelist mechanism can also effectively prevent malicious software from obtaining sensitive data;

[0115] (5) In terms of sensitive data desensitization, in the business data bus service process of the intelligent cockpit system, unified data filtering and desensitization processing is performed, combined with the whitelist mechanism, and desensitized data and original data are allocated according to business needs;

[0116] (6) The business data bus service in the smart cockpit system provides a unified API interface and a unified data format;

[0117] The business data bus service provides a unified interface for subscribing to data topics, a unified data callback interface, and a unified data format. For changes in the data format provided by the external DDS / SOMEIP publisher, the business data bus service will make modifications and adaptations to isolate the shock caused by the data format change so that the shock will not be transmitted to the upper-level application.

[0118] Next, the data fusion communication device proposed according to the embodiment of the present application is described with reference to the accompanying drawings.

[0119] Figure 7 It is a block diagram of a data fusion communication device according to an embodiment of the present application.

[0120] like Figure 7 As shown, the data fusion communication device 10 is applied to a data publishing end, wherein the device includes: a first acquisition module 110 , a conversion module 120 and a transmission module 130 .

[0121] Among them, the first acquisition module 110 is used to acquire multiple sensor data; the conversion module 120 is used to convert the sensor data into corresponding formatted data; the transmission module 130 is used to generate a corresponding publisher instance and a corresponding data topic according to the formatted data structure, and according to the target data topic subscribed by the client, screen the formatted data corresponding to the target data topic, encrypt and serialize it, and then transmit it to the data subscriber.

[0122] It should be noted that the above explanations of the data fusion communication method embodiment are also applicable to the data fusion communication device of this embodiment, and will not be repeated here.

[0123] According to the data fusion communication device proposed in the embodiment of the present application, multiple sensor data received inside the business data bus service process are obtained, and the sensor data is converted into corresponding formatted data, and a corresponding publisher instance and a corresponding data topic are generated according to the formatted data structure, and according to the target data topic subscribed by the client, the formatted data corresponding to the target data topic is screened, encrypted and serialized, and then transmitted to the data subscriber, so that the data is processed according to the time sequence and timestamp, avoiding data redundancy, improving resource utilization, encrypting the data, and ensuring data security.

[0124] Next, the data fusion communication device proposed according to the embodiment of the present application is described with reference to the accompanying drawings.

[0125] Figure 8 It is a block diagram of a data fusion communication device according to an embodiment of the present application.

[0126] like Figure 8 As shown, the data fusion communication device 20 is applied to a data subscription end, wherein the device includes: a second acquisition module 210 , a restoration module 220 and a trigger module 230 .

[0127] Among them, the second acquisition module 210 is used to obtain the data corresponding to the target data topic that the client requests to subscribe to sent by the data publishing end; the restoration module 220 is used to deserialize the data and restore it to the original formatted data, and decrypt the original formatted data to generate plaintext data; the trigger module 230 is used to call the preset interface according to the plaintext data to trigger the whitelist access control module, wherein the whitelist access control module matches the corresponding query results according to the plaintext data, and generates a subscription result according to the query results.

[0128] It should be noted that the above explanations of the data fusion communication method embodiment are also applicable to the data fusion communication device of this embodiment, and will not be repeated here.

[0129] According to the data fusion communication device proposed in the embodiment of the present application, data corresponding to the target data topic that the client requests to subscribe to and sent by the data publishing end is obtained, the data is deserialized and restored to the original formatted data, and the original formatted data is decrypted to generate plaintext data. The preset interface is called according to the plaintext data to trigger the whitelist access control module, wherein the whitelist access control module matches the corresponding query results according to the plaintext data, and generates a subscription result according to the query results. The whitelist access control module is used to implement data security management, which can effectively prevent malicious software from obtaining sensitive data.

[0130] Fig. 9 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. The vehicle may include:

[0131] A memory 901 , a processor 902 , and a computer program stored in the memory 901 and executable on the processor 902 .

[0132] When the processor 902 executes the program, the data fusion communication method provided in the above embodiment is implemented.

[0133] Furthermore, the vehicle also includes:

[0134] The communication interface 903 is used for communication between the memory 901 and the processor 902 .

[0135] The memory 901 is used to store computer programs that can be executed on the processor 902 .

[0136] The memory 901 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0137] If the memory 901, the processor 902 and the communication interface 903 are implemented independently, the communication interface 903, the memory 901 and the processor 902 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0138] Optionally, in a specific implementation, if the memory 901, the processor 902 and the communication interface 903 are integrated on a chip, the memory 901, the processor 902 and the communication interface 903 can communicate with each other through an internal interface.

[0139] The processor 902 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0140] The embodiment of the present application further provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the above data fusion communication method is implemented.

[0141] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0142] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0143] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or N executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0144] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above embodiment, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one or a combination of multiple of the following technologies known in the art: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0145] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

Claims

1. A data fusion communication method, characterized in that: The method is applied to a data publishing terminal, wherein the method comprises the following steps: Obtain multiple sensor data received within the business data bus service process; Converting the sensor data into corresponding formatted data; A corresponding publisher instance and a corresponding data topic are generated according to the formatted data structure, and according to the target data topic subscribed by the client, the formatted data corresponding to the target data topic is screened, encrypted and serialized, and then transmitted to the data subscriber.

2. A data fusion communication method, characterized in that: The method is applied to a data subscription terminal, wherein the method comprises the following steps: Get the data corresponding to the target data topic that the client requests to subscribe to sent by the data publisher; Deserializing the data to restore it to original formatted data, and decrypting the original formatted data to generate plaintext data; The preset excuse is called according to the plaintext data to trigger the whitelist access control module, wherein the whitelist access control module matches the corresponding query result according to the plaintext data and generates a subscription result according to the query result.

3. The data fusion communication method according to claim 2, characterized in that: Before obtaining the data corresponding to the target data topic that the client requests to subscribe to and sent by the data publisher, the following steps are included: Get the target data topic that the client requests to subscribe to; A subscriber instance is generated according to the target data subject and sent to the data publishing end.

4. The data fusion communication method according to claim 3, characterized in that: Before the whitelist access control module is triggered by calling a preset excuse according to the plaintext data, the method includes: identifying the type of the subscriber instance; Performs a target operation based on the type of the subscriber instance.

5. The data fusion communication method according to claim 4, characterized in that: The performing a target operation according to the type of the subscriber instance includes: If the type of the subscriber instance is an out-of-domain data topic, a data callback interface is registered with the local business data bus service process, and an interface for subscribing to an out-of-domain data topic is called.

6. The data fusion communication method according to claim 4, characterized in that: The calling of a preset excuse according to the plaintext data to trigger a whitelist access control module includes: Check whether the application that initiated the registration is in the whitelist that allows access to data outside the domain; If the registered application is not in the whitelist that allows access to data outside the domain, a registration failure result is returned; If the registered application is in the whitelist that is allowed to access out-of-domain data, a subscriber instance is created according to actual needs to subscribe to the out-of-domain data.

7. A data fusion communication device, characterized in that: The device is applied to a data publishing terminal, wherein the device comprises: A first acquisition module, used for acquiring multiple sensor data; A conversion module, used for converting the sensor data into corresponding formatted data; The transmission module is used to generate a corresponding publisher instance and a corresponding data topic according to the formatted data structure, and according to the target data topic subscribed by the client, screen the formatted data corresponding to the target data topic, encrypt and serialize it, and then transmit it to the data subscriber.

8. A data fusion communication device, characterized in that: The device is applied to a data subscription terminal, wherein the device comprises: The second acquisition module is used to acquire data corresponding to the target data topic that the client requests to subscribe to and sent by the data publisher; A restoration module, used to deserialize the data to restore it to the original formatted data, and decrypt the original formatted data to generate plaintext data; The trigger module is used to call a preset excuse according to the plaintext data to trigger the whitelist access control module, wherein the whitelist access control module matches the corresponding query result according to the plaintext data and generates a subscription result according to the query result.

9. A vehicle, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the data fusion communication method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, it is used to implement the data fusion communication method according to any one of claims 1 to 6.

Images