Dds-based on-off vehicle body cross-domain communication security system and automobile

Abstract

The application relates to the technical field of cross-segment communication, and provides a DDS-based on-vehicle body cross-domain communication security architecture and a car, wherein the architecture comprises an on-vehicle body communication domain, an off-vehicle body communication domain and a conversion domain; the on-vehicle body communication domain is used for transmitting on-vehicle body communication data, and the off-vehicle body communication domain is used for transmitting off-vehicle body communication data; the on-vehicle body communication domain comprises an on-vehicle body interface module, the off-vehicle body communication domain comprises an off-vehicle body interface module, and the conversion domain comprises a first area and a second area; the on-vehicle body communication domain and the off-vehicle body communication domain respectively communicate with the on-vehicle body interface module and the off-vehicle body interface module through DDS, and the on-vehicle body interface module and the off-vehicle body interface module respectively communicate with the first area and the second area through in-process communication, thereby realizing DDS-based on-vehicle body cross-domain communication.

Description

Technical Field

[0001] This invention relates to the field of cross-network segment communication technology, and provides a DDS-based cross-domain communication security architecture for vehicles and vehicles. Background Technology

[0002] DDS (Data Distribution Service) is a data-centric communication protocol used for communication in distributed software applications. It describes the communication application programming interface (API) and communication semantics that support communication between data providers and data consumers.

[0003] With the development of intelligent connected vehicles, user demands are increasing, and "software-defined vehicles" has become an industry consensus. To truly realize software-defined vehicles and software-driven innovation, from a technical perspective, automotive software architecture is moving from "signal-oriented" to "service-oriented (SOA)." DDS (Data Distribution Service) is a next-generation distributed real-time communication middleware protocol. Its high real-time performance, high reliability, open architecture, and decoupled publish / subscribe capabilities greatly accelerate and simplify the development of distributed systems, making it highly suitable for the automotive field. It not only meets the needs of large-scale data transmission in the intelligent driving domain but also satisfies the SOA architecture.

[0004] However, existing DDS solutions are all designed within the same domain, and only entities within the same domain can communicate; entities in different domains have no logical relationship. Therefore, for the entire vehicle, all functions and services must belong to the same data domain. This is detrimental to data isolation and control, as well as security design. Furthermore, due to industry collaboration models and the separate development approach for upper and lower vehicle components, the functions and services of the upper and lower vehicle components will inevitably not reside in the same domain, and current methods for implementing communication between different DDS domains are not yet fully developed. Summary of the Invention

[0005] This invention provides a vehicle and a vehicle based on DDS (Digital Data System) for cross-domain communication between upper and lower vehicle bodies, enabling communication between different DDS domains.

[0006] According to a first aspect of the present invention, a DDS-based cross-domain communication safety system for boarding and alighting vehicles is provided, comprising:

[0007] The vehicle body communication domain includes an upper body communication domain, a lower body communication domain, and a conversion domain. The upper body communication domain is used to transmit upper body communication data, and the lower body communication domain is used to transmit lower body communication data. The upper body communication domain and the lower body communication domain are different communication domains.

[0008] The upper vehicle body communication domain includes an upper vehicle body interface module, the lower vehicle body communication domain includes a lower vehicle body interface module, and the conversion domain includes a first region and a second region;

[0009] The upper vehicle body communication data is transmitted to the first area through the upper vehicle body interface module, and the lower vehicle body communication data is transmitted to the second area through the lower vehicle body interface module;

[0010] The first area is used to receive and save the upper body communication data, and to obtain the lower body communication data in the second area, and to transmit the obtained lower body communication data to the upper body communication domain through the upper body interface module;

[0011] The second area is used to receive and save the lower vehicle body communication data, and to obtain the upper vehicle body communication data in the first area, and to transmit the obtained upper vehicle body communication data to the lower vehicle body communication domain through the lower vehicle body interface module.

[0012] Optionally, the upper vehicle body communication domain includes a plurality of first participants, and the lower vehicle body communication domain includes a plurality of second participants;

[0013] The first participant is used to send the upper body communication data to the upper body interface module and receive the lower body communication data transmitted through the upper body interface module; the second participant is used to send the lower body communication data to the lower body interface module and receive the upper body communication data transmitted through the lower body interface module.

[0014] Optionally, the upper body interface module includes several third participants corresponding to the first participant; the third participants are used to receive the upper body communication data transmitted by the first participant and transmit the upper body communication data to the first area;

[0015] The third participant is also configured to: receive the vehicle body communication data acquired by the first region, and transmit the vehicle body communication data to the first participant.

[0016] Optionally, the first participant includes: a first data publisher and a first data subscriber;

[0017] The first data publisher is used to create the upper body communication data and transmit the upper body communication data to the third participant;

[0018] The first data subscriber is used to obtain communication data of the disembarkation body from the third participant.

[0019] Optionally, the third participant includes: a third data publisher and a third data subscriber;

[0020] The third data publisher is used to transmit the upper body communication data to the first area;

[0021] The third data subscriber is used to obtain the vehicle body communication data acquired in the first region.

[0022] Optionally, the first area includes: a first data reader and a first data writer;

[0023] The first data reader is used to acquire communication data of the vehicle body in the second area;

[0024] The first data writer is used to acquire and save the vehicle body communication data of the third participant.

[0025] Optionally, the third participant communicates with the first region via in-process communication.

[0026] Optionally, the vehicle interface module includes several fourth participants corresponding to the second participant; the fourth participants are used to receive the vehicle communication data transmitted by the second participant and transmit the vehicle communication data to the second area.

[0027] The fourth participant is also used to: receive the upper body communication data acquired by the second region, and transmit the upper body communication data to the second participant.

[0028] Optionally, the second participant includes: a second data publisher and a second data subscriber;

[0029] The second data publisher is used to create the vehicle body communication data and transmit the vehicle body communication data to the vehicle body interface module;

[0030] The second data subscriber is used to obtain the upper vehicle body communication data in the lower vehicle body interface module.

[0031] Optionally, the fourth participant includes: a fourth data publisher and a fourth data subscriber;

[0032] The fourth data publisher is used to transmit the communication data of the vehicle body to the second area;

[0033] The fourth data subscriber is used to obtain the upper body communication data in the second region.

[0034] Optionally, the second area includes: a second data reader and a second data writer;

[0035] The second data reader is used to acquire the upper vehicle body communication data in the first area;

[0036] The second data writer is used to acquire and save the communication data of the disembarking body of the fourth participant.

[0037] Optionally, the fourth participant communicates with the second region via in-process communication.

[0038] According to a second aspect of the present invention, an automobile is provided, including the cross-domain communication safety system for upper and lower vehicle bodies as described in the first aspect of the present invention.

[0039] The DDS-based cross-domain communication safety system for upper and lower vehicle bodies provided by this invention transmits communication data from both the upper and lower vehicle body communication domains to a conversion domain. Specifically, upper vehicle body communication data is transmitted to a first region via an upper vehicle body interface module, where it is received and stored. Lower vehicle body communication data is transmitted to a second region via a lower vehicle body interface module, where it is received and stored. Furthermore, the first region obtains lower vehicle body communication data from the second region and transmits it to the upper vehicle body communication domain; the second region obtains upper vehicle body communication data from the first region and transmits it to the lower vehicle body communication domain. The upper and lower vehicle body communication data are transmitted via DDS to the upper and lower vehicle body interface modules respectively, and these modules transmit the data to the first and second regions respectively via intra-process communication, ultimately achieving communication between different domains. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 This is a schematic diagram of the cross-domain communication safety system between the upper and lower vehicle bodies in one embodiment of the present invention;

[0042] Figure 2 This is a schematic diagram of a cross-domain communication structure between the upper and lower vehicle bodies in one embodiment of the present invention;

[0043] Explanation of reference numerals in the attached figures:

[0044] 10- Upper body communication domain;

[0045] 101 - First Participant;

[0046] 1011 - The primary data publisher;

[0047] 1012 - First Data Subscriber;

[0048] 102 - Upper body interface module;

[0049] 1021 - The third participant mentioned above;

[0050] 10211 - Third-party data publisher;

[0051] 10212 - Third-party data subscriber;

[0052] 20-Lower body communication domain;

[0053] 201 - Second Participant;

[0054] 2011 - Second data publisher;

[0055] 2012 - Second Data Subscriber;

[0056] 202-Undercar body interface module;

[0057] 2021 - Fourth participant;

[0058] 20211 - Fourth data publisher;

[0059] 20212 - Fourth Data Subscriber;

[0060] 30-Transition domain;

[0061] 301 - Zone 1;

[0062] 3011 - First data reader;

[0063] 3012 - First data writer;

[0064] 302 - Second Zone;

[0065] 3021 - Second data reader;

[0066] 3022 - Second data writer. Detailed Implementation

[0067] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0068] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0069] The technical solution of the present invention will be described in detail below with reference to specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0070] Please refer to Figure 1 This invention provides a DDS-based cross-domain communication safety system for boarding and alighting vehicles, comprising:

[0071] The vehicle body communication domain 10, the lower vehicle body communication domain 20, and the conversion domain 30 are included. The upper vehicle body communication domain 10 is used to transmit upper vehicle body communication data, and the lower vehicle body communication domain 20 is used to transmit lower vehicle body communication data. The upper vehicle body communication domain and the lower vehicle body communication domain are different communication domains.

[0072] The upper vehicle body communication domain 10 includes an upper vehicle body interface module 102, the lower vehicle body communication domain 20 includes a lower vehicle body interface module 202, and the conversion domain 30 includes a first region 301 and a second region 302.

[0073] The upper body communication data is transmitted to the first area 301 through the upper body interface module 102, and the lower body communication data is transmitted to the second area 302 through the lower body interface module 202.

[0074] The first area 301 is used to receive and save the upper body communication data, and to obtain the lower body communication data in the second area, and to transmit the obtained lower body communication data to the upper body communication domain through the upper body interface module.

[0075] The second region 302 is used to receive and save the lower vehicle body communication data, and to obtain the upper vehicle body communication data in the first region 301, and to transmit the obtained upper vehicle body communication data to the lower vehicle body communication domain through the lower vehicle body interface module 202.

[0076] The first participant communicates with the upper vehicle interface module via DDS, and the upper vehicle interface module communicates with the first region via in-process communication; the second participant communicates with the lower vehicle interface module via DDS, and the lower vehicle interface module communicates with the second region via in-process communication.

[0077] Specifically, the upper vehicle body communication domain includes a number of first participants 101, and the lower vehicle body communication domain includes a number of second participants 201.

[0078] The first participant 101 is used to send the upper body communication data to the upper body interface module 102 and receive the lower body communication data transmitted through the upper body interface module 102; the second participant 201 is used to send the lower body communication data to the lower body interface module 304 and receive the upper body communication data transmitted through the lower body interface module 304.

[0079] The upper body interface module 102 includes a plurality of third participants 3011 corresponding to the first participant 101; the third participant 1021 is used to receive the upper body communication data transmitted by the first participant 101 and transmit the upper body communication data to the first region 301.

[0080] The vehicle body interface module 202 includes a plurality of fourth participants 2021 corresponding to the second participant 201; the fourth participants 2021 are used to receive the vehicle body communication data transmitted by the second participant 201 and transmit the vehicle body communication data to the second region 302.

[0081] Please refer to Figure 2 The first region 301 includes: a first data reader 3031 and a first data writer 3012; the first data reader 3011 is used to acquire the lower vehicle body communication data in the second region 302; the first data writer 3012 is used to acquire and save the upper vehicle body communication data in the third participant 1021.

[0082] The second region 302 includes: a second data reader 3041 and a second data writer 3022; the second data reader 3021 is used to acquire upper vehicle communication data in the first region 301; the second data writer 3022 is used to acquire and save lower vehicle communication data in the fourth participant 2021.

[0083] Specifically, the first participant 101 includes a first data publisher 1011 and a first data subscriber 1012. The first data publisher 1011 is used to create the upper vehicle communication data and transmit the upper vehicle communication data to the third participant 1021. The first data subscriber 1012 is used to obtain the lower vehicle communication data from the third participant 1021.

[0084] The third participant 1021 includes a third data publisher 10211 and a third data subscriber 10212. The third data publisher 10211 transmits the upper vehicle communication data to the first area 301; the third data subscriber 10212 receives the lower vehicle communication data from the first area 301. Therefore, the third participant 1021 is also used to receive the lower vehicle communication data from the first area 301 and transmit the lower vehicle communication data to the first participant 101.

[0085] The second participant 201 includes a second data publisher 2011 and a second data subscriber 2012; the second data publisher 2011 is used to create lower vehicle body communication data and transmit the lower vehicle body communication data to the lower vehicle body interface module 202. The second data subscriber 2012 is used to obtain the upper vehicle body communication data in the lower vehicle body interface module 202.

[0086] The fourth participant 2021 includes: the fourth data publisher 20211 and the fourth data subscriber 20212;

[0087] The fourth data publisher 20211 is used to transmit the lower vehicle communication data to the second area 302; the fourth data subscriber 20212 is used to obtain the upper vehicle communication data in the second area 302. Therefore, the fourth participant 2021 is also used to: receive the upper vehicle communication data obtained by the second area 302, and transmit the upper vehicle communication data to the second participant 201.

[0088] The third participant communicates with the first region via in-process communication; the fourth participant communicates with the second region via in-process communication.

[0089] In this embodiment of the invention, intra-process communication refers to the communication method between processes in the system. Since different domains exchange data through DDS, the exchange of data between different domains needs to be achieved through inter-process communication (i.e., intra-process communication mentioned in this embodiment of the invention).

[0090] In a specific example, the intra-process communication in this embodiment of the invention is pipe communication. Both the upper vehicle communication domain and the lower vehicle communication domain have multiple data to be transmitted to each other. At this time, multiple data correspond to multiple processes. When multiple processes of the upper vehicle enter the first area from the upper vehicle interface module, or when multiple processes of the lower vehicle enter the second area from the lower vehicle interface module, a pipe needs to be established between different domains. The multiple processes of the upper vehicle or the multiple processes of the lower vehicle sequentially enter the conversion domain through the pipe, so that multiple data from the upper vehicle communication domain or the multiple data from the lower vehicle communication domain enter the conversion domain, and data interaction is realized in the conversion domain. The interacted data is then transmitted to the corresponding lower vehicle communication domain or upper vehicle communication domain through intra-process communication.

[0091] In this embodiment of the invention, the intra-process communication method selected is pipe communication. Of course, other intra-process communication methods (such as message queuing, shared memory, sockets, etc.) are also within the scope of protection of this invention.

[0092] Please continue to refer to this. Figure 2 In a specific example, in the upper vehicle communication domain, the first data publisher of the first participant creates upper vehicle communication data A that needs to be transmitted to the lower vehicle communication domain; simultaneously, in the lower vehicle communication domain, the second data publisher of the second participant creates lower vehicle communication data B that needs to be transmitted to the upper vehicle communication domain. At this point, the third data subscriber in the upper vehicle interface module obtains data A created by the first data publisher through DDS communication, and the third data publisher publishes data A. The first data writer in the first area obtains and saves data A from the third data publisher through intra-process communication (such as pipe communication). That is, upper vehicle communication data A has been saved in the first area. Simultaneously, the fourth data subscriber in the lower vehicle interface module obtains data B created by the second data publisher through DDS communication, and the fourth data publisher publishes data B. The second data writer in the second area obtains and saves data B from the fourth data publisher through intra-process communication. That is, lower vehicle communication data B has been saved in the second area.

[0093] The data reader in the first region obtains the lower vehicle communication data B from the second data writer via DDS communication, and the first data writer publishes data B. The third data subscriber obtains the data B published by the first data writer via intra-process communication, and the third data publisher publishes data B. The first data subscriber then obtains the data B published by the third data publisher via DDS communication. In other words, the upper vehicle communication domain obtains the lower vehicle communication data B from the lower vehicle communication domain. The data reader in the second region obtains the upper vehicle communication data A from the first data writer via DDS communication, and the second data writer publishes data A. The fourth data subscriber obtains the data A published by the second data writer via intra-process communication, and the fourth data publisher publishes data A. The second data subscriber then obtains the data A published by the fourth data publisher via DDS communication. In other words, the lower vehicle communication domain obtains the upper vehicle communication data A from the upper vehicle communication domain. Thus, the cross-domain communication between the upper and lower vehicle bodies is completed.

[0094] In addition, other methods, such as: passing communication data from different domains into a certain interface through DDS communication, and then exchanging data between different domains through intra-process communication within that interface, ultimately achieving cross-domain communication, are also within the scope of protection of this invention as long as they do not depart from the scope of protection of this invention.

[0095] In the DDS-based cross-domain communication safety system for upper and lower vehicle bodies provided by this invention, communication data within the upper vehicle body communication domain and the lower vehicle body communication domain are transmitted to a conversion domain. Specifically, upper vehicle body communication data is transmitted to a first region via an upper vehicle body interface module, and the first region receives and saves the upper vehicle body communication data via the upper vehicle body interface module. Lower vehicle body communication data is transmitted to a second region via a lower vehicle body interface module, and the second region receives and saves the lower vehicle body communication data via the lower vehicle body interface module. Furthermore, the first region obtains lower vehicle body communication data from the second region and transmits the lower vehicle body communication data to the upper vehicle body communication domain; the second region obtains upper vehicle body communication data from the first region and transmits the upper vehicle body communication data to the lower vehicle body communication domain. The upper and lower vehicle body communication data are transmitted to the upper and lower vehicle body interface modules respectively via DDS, and the upper and lower vehicle body interface modules transmit the upper and lower vehicle body communication data to the first and second regions respectively via intra-process communication, ultimately achieving communication between different domains.

[0096] This invention also provides a vehicle, including the DDS-based cross-domain communication safety system for vehicles above and below, as described above.

[0097] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A DDS-based boarding and alighting body cross-domain communication security system, characterized in that, The application relates to a vehicle body communication system, comprising: An upper vehicle body communication domain, a lower vehicle body communication domain and a conversion domain; the upper vehicle body communication domain is used for transmitting upper vehicle body communication data, the lower vehicle body communication domain is used for transmitting lower vehicle body communication data; the upper vehicle body communication domain and the lower vehicle body communication domain are different communication domains; The upper vehicle body communication domain comprises an upper vehicle body interface module, the lower vehicle body communication domain comprises a lower vehicle body interface module, and the conversion domain comprises a first area and a second area; The upper vehicle body communication data is transmitted to the first area through the upper vehicle body interface module, and the lower vehicle body communication data is transmitted to the second area through the lower vehicle body interface module; The first area is used for receiving and saving the upper vehicle body communication data, acquiring lower vehicle body communication data in the second area and transmitting the acquired lower vehicle body communication data to the upper vehicle body communication domain through the upper vehicle body interface module; The second area is used for receiving and saving the lower vehicle body communication data, acquiring upper vehicle body communication data in the first area and transmitting the acquired upper vehicle body communication data to the lower vehicle body communication domain through the lower vehicle body interface module; The upper vehicle body communication domain comprises a plurality of first participants, and the lower vehicle body communication domain comprises a plurality of second participants; The first participants are used for sending the upper vehicle body communication data to the upper vehicle body interface module and receiving lower vehicle body communication data transmitted through the upper vehicle body interface module; and the second participants are used for sending the lower vehicle body communication data to the lower vehicle body interface module and receiving upper vehicle body communication data transmitted through the lower vehicle body interface module; The first participants and the upper vehicle body interface module communicate through DDS, the upper vehicle body interface module and the first area communicate through an intra-process, the second participants and the lower vehicle body interface module communicate through DDS, and the lower vehicle body interface module and the second area communicate through an intra-process; The upper vehicle body interface module comprises a plurality of third participants corresponding to the first participants; the third participants are used for receiving the upper vehicle body communication data transmitted by the first participants and transmitting the upper vehicle body communication data to the first area; The third participants are also used for receiving the lower vehicle body communication data acquired by the first area and transmitting the lower vehicle body communication data to the first participants; The lower vehicle body interface module comprises a plurality of fourth participants corresponding to the second participants; the fourth participants are used for receiving the lower vehicle body communication data transmitted by the second participants and transmitting the lower vehicle body communication data to the second area; The fourth participants are also used for receiving the upper vehicle body communication data acquired by the second area and transmitting the upper vehicle body communication data to the second participants. The third participant and the first region are communicated by in-process communication, the fourth participant and the second region are communicated by in-process communication, when the in-process communication is pipe communication, a pipe is established between different domains, and a plurality of processes of the upper body or a plurality of processes of the lower body enter the conversion domain through the pipe in turn, so that a plurality of data of the upper body communication domain or a plurality of data of the lower body communication domain enter the conversion domain, the interaction of the data is realized in the conversion domain, and each data after the interaction is transmitted to the corresponding lower body communication domain or upper body communication domain through the pipe communication.

2. The DDS-based on-off body cross-domain communication security system according to claim 1, wherein the first participant comprises a first data publisher and a first data subscriber.

3. The DDS-based on-off body cross-domain communication security system according to claim 1, wherein the third participant comprises a third data publisher and a third data subscriber.

4. The DDS-based on-off body cross-domain communication security system according to claim 3, wherein the first region comprises a first data reader and a first data writer.

5. The DDS-based on-off body cross-domain communication security system according to claim 1, wherein the second participant comprises a second data publisher and a second data subscriber.

6. The DDS-based on-off body cross-domain communication security system according to claim 1, wherein the fourth participant comprises a fourth data publisher and a fourth data subscriber.

7. The DDS-based on-off body cross-domain communication security system according to claim 6, wherein the second region comprises a second data reader and a second data writer.

8. The DDS-based on-off body cross-domain communication security system according to claim 7, wherein the second region comprises a second data reader and a second data writer. ​ ​ ​ ​ ​ 5. The DDS-based onboarding body cross-domain communication security system of claim 4, wherein, ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 9.The DDS-based onboarding body cross-domain communication security system of claim 8, wherein, The fourth participant communicates with the second region through in-process communication.

10. An automobile characterized by comprising: The DDS-based boarding / alighting body cross-domain communication security system of any one of claims 1-9.

Images