CN116010934B - Domain controller process communication method, device, vehicle and storage medium - Google Patents
Domain controller process communication method, device, vehicle and storage medium Download PDFInfo
- Publication number
- CN116010934B CN116010934B CN202310018025.3A CN202310018025A CN116010934B CN 116010934 B CN116010934 B CN 116010934B CN 202310018025 A CN202310018025 A CN 202310018025A CN 116010934 B CN116010934 B CN 116010934B
- Authority
- CN
- China
- Prior art keywords
- communicated
- processes
- opposite
- domain controller
- communication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 373
- 230000008569 process Effects 0.000 title claims abstract description 348
- 238000004891 communication Methods 0.000 title claims abstract description 105
- 230000004044 response Effects 0.000 claims abstract description 11
- 230000007246 mechanism Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 4
- 238000012217 deletion Methods 0.000 abstract description 5
- 230000037430 deletion Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000011664 signaling Effects 0.000 description 4
- 230000006978 adaptation Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000009924 canning Methods 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 230000008447 perception Effects 0.000 description 2
- 239000000725 suspension Substances 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000002485 combustion reaction Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Abstract
The disclosure relates to a domain controller process communication method, a device, a vehicle and a storage medium in the technical field of vehicle communication, comprising: in response to peer-to-peer communication of processes, determining identity certificates of two processes to be communicated, which are opposite to each other in communication, wherein the identity certificates are issued by a CA (certificate authority) for each domain controller; determining an authority file of a process to be communicated of the opposite terminal; and establishing process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file of the processes to be communicated of the opposite ends. The CA issues the identity certificate aiming at each domain controller of the vehicle, does not issue the identity certificate aiming at each process, reduces the number of the identity certificates, improves the convenience of software upgrading and replacing of the domain controllers, only downloads the OTA update package when increasing the processes, does not need to issue the identity certificate of the processes newly, does not need to delete the corresponding identity certificate when deleting the processes, only needs to delete the corresponding authority files, and improves the convenience of process addition and deletion.
Description
Technical Field
The disclosure relates to the technical field of vehicle communication, and in particular relates to a domain controller process communication method, a domain controller process communication device, a vehicle and a storage medium.
Background
In the domain controller of the vehicle, corresponding license files, management files and identity certificates are issued to the processes for each process in the domain controller, as shown in fig. 1, a permission file (permission file), an identity certificate (identity certificate) and a private key are issued to the process P1 in the same domain controller, and similarly, corresponding permission files, identity certificates and private keys are issued to the process P2 in the same domain controller as the process P1. At the same time, CA (Certification Authority) will issue different identity certificates (Identity certificate) and rights certificates (permissions certificate) to process P1 and process P2. It can be seen that each process needs to issue an identity certificate, and operations such as canning, updating and suspension of the identity certificate are complex, so that the identity certificate management is inconvenient.
Disclosure of Invention
In order to overcome the problems in the related art, the present disclosure provides a domain controller process communication method, device, vehicle and storage medium.
According to a first aspect of an embodiment of the present disclosure, there is provided a domain controller process communication method, including:
determining identity certificates of two processes to be communicated which are opposite to each other in communication by responding to opposite-end communication between the processes, wherein the identity certificates are issued by a CA for each domain controller;
determining an authority file of a process to be communicated of the opposite terminal;
and establishing process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file corresponding to the processes to be communicated of the opposite ends.
Optionally, the determining, in response to the peer communication between the processes, the identity certificates of the two processes to be communicated that are opposite to each other, includes:
responding to opposite-end communication between processes, and determining whether two processes to be communicated which are opposite-end communication are in the same domain controller;
if two processes to be communicated which are opposite to each other are in the same domain controller, reading identity certificates of the domain controllers where the two processes to be communicated are located;
if two processes to be communicated which are opposite to each other are not in the same domain controller, the identity certificate of the domain controller where the local process is located is sent to the process to be communicated of the opposite end.
Optionally, the identity certificate is stored in a trust space of the corresponding domain controller, and only the identity certificate of the corresponding domain controller is stored in the trust space.
Optionally, if the two processes to be communicated that are opposite to each other are not in the same domain controller, the sending the identity certificate of the domain controller where the local process is located to the process to be communicated that is opposite to each other includes:
if two processes to be communicated which are opposite to each other are not in the same domain controller, the local process reads the corresponding identity certificate from the trust space of the domain controller;
and sending the identity certificate read by the local process to the opposite process to be communicated.
Optionally, if the two processes to be communicated that are opposite to each other are in the same domain controller, the step of reading the identity certificate of the domain controller where the two processes to be communicated are located includes:
if two processes to be communicated which are opposite to each other are in the same domain controller, the two processes to be communicated respectively and directly read the identity certificate from the trust space of the domain controller.
Optionally, the determining the permission file of the process to be communicated of the opposite terminal includes:
inquiring a permission label corresponding to a process to be communicated of an opposite end according to a process label of the process to be communicated of the opposite end, wherein an operating system of a domain controller of the process to be communicated of the opposite end is added for each process in the domain controller, the permission label is added for each permission file in the domain controller by the operating system, and the process label of the process is bound with the permission label based on a forced access control mechanism of a selinux;
and determining the authority file of the process to be communicated of the opposite terminal according to the inquired authority label.
Optionally, the authority file of the process is bound with the identity certificate of the domain controller based on a Subject Name matching rule of a ignore CN field, and the CN field has a one-to-one correspondence with the domain controller.
According to a second aspect of the embodiments of the present disclosure, there is provided a domain controller process communication apparatus, including:
a first determining module configured to determine identity certificates of two processes to be communicated, which are opposite to each other in communication, in response to opposite-end communication between the processes, wherein the identity certificates are issued by a CA for each domain controller;
the second determining module is configured to determine a right file of a process to be communicated of the opposite end;
the communication module is configured to establish process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file corresponding to the processes to be communicated of the opposite ends.
Optionally, the first determining module is configured to:
responding to opposite-end communication between processes, and determining whether two processes to be communicated which are opposite-end communication are in the same domain controller;
if two processes to be communicated which are opposite to each other are in the same domain controller, reading identity certificates of the domain controllers where the two processes to be communicated are located;
if two processes to be communicated which are opposite to each other are not in the same domain controller, the identity certificate of the domain controller where the local process is located is sent to the process to be communicated of the opposite end.
Optionally, the identity certificate is stored in a trust space of the corresponding domain controller, and only the identity certificate of the corresponding domain controller is stored in the trust space.
Optionally, the first determining module is configured to, if two processes to be communicated, which are opposite to each other, are not in the same domain controller, read the corresponding identity certificate from the trust space of the domain controller where the process of the home terminal is located;
and sending the identity certificate read by the local process to the opposite process to be communicated.
Optionally, the first determining module is configured to, if two processes to be communicated that are opposite to each other are in the same domain controller, directly read the identity certificate from the trust space of the domain controller where the two processes to be communicated are located, respectively.
Optionally, the second determining module is configured to:
inquiring a permission label corresponding to a process to be communicated of an opposite end according to a process label of the process to be communicated of the opposite end, wherein an operating system of a domain controller of the process to be communicated of the opposite end is added for each process in the domain controller, the permission label is added for each permission file in the domain controller by the operating system, and the process label of the process is bound with the permission label based on a forced access control mechanism of a selinux;
and determining the authority file of the process to be communicated of the opposite terminal according to the inquired authority label.
Optionally, the authority file of the process is bound with the identity certificate of the domain controller based on a Subject Name matching rule of a ignore CN field, and the CN field has a one-to-one correspondence with the domain controller.
According to a third aspect of embodiments of the present disclosure, there is provided a vehicle comprising:
a first processor;
a first memory for storing processor-executable instructions;
wherein the first processor is configured to:
determining identity certificates of two processes to be communicated which are opposite to each other in communication by responding to opposite-end communication between the processes, wherein the identity certificates are issued by a CA for each domain controller;
determining an authority file of a process to be communicated of the opposite terminal;
and establishing process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file corresponding to the processes to be communicated of the opposite ends.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon computer program instructions which, when executed by a second processor, implement the steps of the method of any of the first aspects.
The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects:
determining identity certificates of two processes to be communicated, which are opposite to each other in communication, by responding to opposite-end communication of the processes, wherein the identity certificates are issued by a CA (certificate authority) for each domain controller; determining an authority file of a process to be communicated of the opposite terminal; and establishing process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file of the processes to be communicated of the opposite ends. The CA issues the identity certificate aiming at each domain controller of the vehicle, does not issue the identity certificate aiming at each process, reduces the number of the identity certificates, improves the convenience of software upgrading and replacing of the domain controllers, only needs to download the OTA update package when the process is added, does not need to issue the identity certificate of the process newly, does not need to delete the corresponding identity certificate when the process is deleted, only needs to delete the corresponding authority file, and improves the convenience of process addition and deletion.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic diagram of each process in a domain controller issuing an identity certificate in the related art.
Fig. 2 is a flow chart illustrating a method of domain controller process communication according to an exemplary embodiment.
Fig. 3 is a flow chart illustrating one implementation of step S11 in fig. 2 according to an exemplary embodiment.
FIG. 4 is a schematic diagram illustrating an issuing of an identity certificate for a domain controller, according to an example embodiment.
Fig. 5 is a block diagram illustrating a domain controller process communication device according to an example embodiment.
FIG. 6 is a functional block diagram of a vehicle shown in an exemplary embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
It should be noted that, all actions of acquiring signals, information or data in the present application are performed under the condition of conforming to the corresponding data protection rule policy of the country of the location and obtaining the authorization given by the owner of the corresponding device.
Before describing the domain controller process communication method, device, vehicle and storage medium provided by the embodiments of the present disclosure, the state of the art is first described, in the end-to-end encryption communication between domain controllers, the domain controllers first need to authenticate each other based on an asymmetric encryption system, then exchange keys of each other, and finally encrypt vehicle data with piled encryption keys, so that a private key, an identity certificate and a rights file of the process need to be prepared before communication with the opposite end in the domain controller, where the rights file is used to indicate that the process has corresponding rights. All the domain controls are interconnected through buses such as Ethernet. The authentication between processes is completed by mutually exchanging the identity certificate and the authority file of each other, whether the processes are between the domain controllers or between the processes in the domain controllers. After authentication is completed, the symmetric private key is exchanged again to complete encrypted transmission. It can be seen that each process needs to issue a certificate, and operations such as canning, updating and suspension of the certificate are complex, so that certificate management and the like are inconvenient.
In addition, the process in each domain control needs CA to issue a corresponding identity certificate, the CA signs the authority file, then the identity certificate is matched with the authority file, so that under the condition that the process is newly added, the new certificate is canned, the authority file is required to be changed, and the authority file is matched with the identity certificate after being changed, and the whole vehicle internal matching is involved, so that a large number of authority signatures are required to be manufactured.
In view of this, the embodiments of the present disclosure provide a domain controller process communication method, which aims to reduce the number of identity certificates, improve the convenience of software upgrade and replacement of the domain controller, and improve the convenience of process addition and deletion.
Fig. 2 is a flowchart illustrating a domain controller process communication method applied to a vehicle according to an exemplary embodiment, and the domain controller process communication method includes the following steps as shown in fig. 2.
In step S11, in response to the peer communication between the processes, identity certificates of two processes to be communicated that are the opposite ends of the communication are determined.
Wherein the identity certificate is issued by the CA for each domain controller.
In the embodiment of the disclosure, the opposite-end communication between the processes is usually verification of the identity certificate and the authority file when the communication is performed for the first time, and after the process communication is established, the subsequent process communication can directly call the corresponding identity certificate and the authority file.
Therein, referring to fig. 4, the CA no longer issues an identity certificate for each process, but issues an identity certificate for the domain controller, that is, processes within different domain controllers have different identity certificates, and processes within the same domain controller have the same identity certificate.
Describing the example shown in fig. 4, the CA issues an identity certificate 1 for the domain controller 1, an identity certificate 2 for the domain controller 2, an identity certificate 3 for the domain controller 3, and an identity certificate 4 for the domain controller 4. When the process is established, the process directly calls the identity certificate corresponding to the domain controller. For example, the identity certificate of the domain controller 1 is directly invoked when the process A1 is established in the domain controller 1, and similarly, the identity certificate of the domain controller 1 is invoked when the process A2 is established in the domain controller 1. The same principle is that the identity certificate of the domain controller 2 is directly invoked when the process B1 is established in the domain controller 2, and similarly, the identity certificate of the domain controller 2 is invoked when the process B2 is established in the domain controller 2. The principle of the process in the other domain controllers for establishing the call identity certificate is the same, and will not be described here again.
In step S12, a permission file of the process to be communicated of the opposite end is determined.
In the embodiment of the disclosure, the authority files of each process are different, and the identity certificates of different processes in the same domain controller are the same, so that different processes in the same domain controller need to be distinguished through the authority files.
In step S13, process communication between two processes to be communicated, which are opposite communication ends, is established according to the identity certificate and the rights file corresponding to the processes to be communicated of the opposite ends.
According to the technical scheme, the identity certificates of the two processes to be communicated, which are opposite to each other in communication, are determined by responding to the opposite-end communication of the processes, and the identity certificates are issued by the CA for each domain controller. And determining the authority file of the process to be communicated of the opposite terminal. And establishing process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file of the processes to be communicated of the opposite ends. The CA issues the identity certificate aiming at each domain controller of the vehicle, does not issue the identity certificate aiming at each process, reduces the number of the identity certificates, improves the convenience of software upgrading and replacing of the domain controllers, only needs to download the OTA update package when the process is added, does not need to issue the identity certificate of the process newly, does not need to delete the corresponding identity certificate when the process is deleted, only needs to delete the corresponding authority file, and improves the convenience of process addition and deletion.
Optionally, referring to fig. 3, in step S11, in response to peer communication between processes, determining identity certificates of two processes to be communicated that are opposite to each other, including:
in step S111, in response to the peer communication between the processes, it is determined whether two to-be-communicated processes that are the opposite of each other are in the same domain controller.
In the embodiment of the disclosure, whether the opposite end processes are in the same domain controller can be determined according to the signaling sources of the opposite end processes, and in general, the processes in the domain controller cannot send signaling in a bus mode, and the processes between the different domain controllers send signaling in a bus mode. Referring to fig. 4, the different domain controllers communicate with the gateway via a bus, for example, the different domain controllers may communicate with the ethernet gateway via an ethernet bus.
In step S112, if two processes to be communicated are at opposite communication ends and are in the same domain controller, the identity certificate of the domain controller where the two processes to be communicated are located is read.
With continued reference to fig. 4, if two processes to be communicated, which are opposite to each other, are the process A1 and the process A2 in the domain controller 1, respectively, both the process A1 and the process A2 may directly read the identity certificate of the domain controller 1. The identity certificate principle of the opposite end communication read domain controller among the processes in other domain controllers is the same, and is not repeated here.
In step S113, if two processes to be communicated, which are opposite to each other, are not in the same domain controller, the identity certificate of the domain controller where the local process is located is sent to the opposite process to be communicated.
With continued reference to fig. 4, if two processes to be communicated, which are opposite to each other, are the process A1 in the domain controller 1 and the process B1 in the domain controller 2, respectively, the process B1 sends the identity certificate of the domain controller 2 to the process A1, and the process A1 sends the identity certificate of the domain controller 1 to the process B1. The principle that the processes of other different domain controllers send the identity certificate of the domain controller where the home terminal process is located is the same, and will not be described here again.
In the technical scheme, when the processes in the same domain controller establish process communication, the processes are not required to send any more, so that the signaling consumption in the bus can be reduced, and only when the processes among different domain controllers establish process communication, the identity certificate of the domain controller where the process of the opposite terminal is located needs to be received and written.
Optionally, the identity certificate is stored in a trust space of the corresponding domain controller, and only the identity certificate of the corresponding domain controller is stored in the trust space.
With continued reference to fig. 4, a trust space is established in each domain controller, the identity certificate of the corresponding domain controller is stored in the trust space, and each process in the domain controller can read the stored identity certificate from the trust space.
Optionally, if two processes to be communicated, which are opposite to each other, are not in the same domain controller, the sending the identity certificate of the domain controller where the home terminal process is located to the opposite process to be communicated, includes:
if two processes to be communicated which are opposite to each other are not in the same domain controller, the local process reads the corresponding identity certificate from the trust space of the domain controller.
And sending the identity certificate read by the local process to the opposite process to be communicated.
Continuing with the foregoing embodiment, if two to-be-communicated processes that are opposite to each other are the process A1 in the domain controller 1 and the process B1 in the domain controller 2, respectively, the process B1 reads the identity certificate from the trust space of the domain controller 2 and sends the identity certificate of the domain controller 2 to the process A1, and the process A1 reads the identity certificate from the trust space of the domain controller 1 and sends the identity certificate of the domain controller 1 to the process B1. Optionally, if two processes to be communicated that are opposite to each other are in the same domain controller, reading the identity certificate of the domain controller where the two processes to be communicated are located, including:
if two processes to be communicated which are opposite to each other are in the same domain controller, the two processes to be communicated respectively and directly read the identity certificate from the trust space of the domain controller.
As described in the foregoing embodiment, if two processes to be communicated, which are opposite to each other, are the process A1 and the process A2 in the domain controller 1, respectively, the process A1 and the process A2 may directly read the identity certificate of the domain controller 1 from the trust space of the domain controller 1.
Optionally, determining the authority file of the process to be communicated of the opposite terminal includes:
inquiring the authority label corresponding to the process to be communicated of the opposite end according to the process label of the process to be communicated of the opposite end, wherein an operating system of a domain controller of the process to be communicated of the opposite end is added for each process in the domain controller, the authority label is added for each authority file in the domain controller by the operating system, and the process label of the process is bound with the authority label based on a forced access control mechanism of selinux.
And determining the authority file of the process to be communicated of the opposite terminal according to the inquired authority label.
In the embodiment of the disclosure, an operating system of the domain controller, such as Linux and Apple macOS, adds a permission label to the permission file and marks a process to the process. Then, the access rights of the process to the rights file are restricted by the predefined control rights. Thus, different processes can bind different rights files.
The authority file of the process is bound to the process through mac forced access control of selinux, and the identity certificate is stored in a trust space of the domain controller.
Optionally, the authority file of the process is bound to the identity certificate of the domain controller based on a Subject Name matching rule that ignores a CN (Common Name) field, and the CN field has a one-to-one correspondence with the domain controller.
Referring to table 1, the field of the Subject Name may be saved as follows:
| Property | Value |
| Subject | cn= TBOX@1234567890, OU =pki, o=vendor identification PKI, c=cn |
TABLE 1
The identification of the CN field can be used for the identity certificate revocation of the domain controller, so that the CN field and the domain controller have a one-to-one correspondence, that is, the identification of one CN field of one domain controller. Therefore, in order to reduce the number of updated rights files, the matching of the Subject Name ignores the CN number, and the related information of the domain controller is put in the "OU" field in the table. In this way, when The process is added and updated, only a new or updated OTA (Over The Air technology) package is needed to be downloaded, a new identity certificate is not required to be issued for The process, and when The process is deleted, the identity certificate is not required to be deleted, and only The authority file of The corresponding process is required to be deleted.
The technical scheme of the disclosure can realize the exchange of the authority files and the identity certificates of the process in a manner of conventional certificate exchange of the follow.
Based on the same concept, the embodiment of the present disclosure further provides a domain controller process communication device, referring to fig. 5, the domain controller process communication device 500 includes: a first determination module 510, a second determination module 520, and a communication module 530.
Wherein the first determining module 510 is configured to determine, in response to peer communication between processes, identity certificates of two processes to be communicated that are opposite to each other in communication, wherein the identity certificates are issued by CA for each of the domain controllers;
the second determining module 520 is configured to determine a permission file of the process to be communicated of the opposite terminal;
the communication module 530 is configured to establish process communication between two processes to be communicated, which are opposite to each other, according to the identity certificate and the rights file corresponding to the processes to be communicated.
In the method, the CA issues the identity certificate for each domain controller of the vehicle, does not issue the identity certificate for each process any more, reduces the number of the identity certificates, improves the convenience of software upgrading and replacement of the domain controllers, only needs to download the OTA update package when the process is added, does not need to newly issue the identity certificate of the process, does not need to delete the corresponding identity certificate when the process is deleted, only needs to delete the corresponding authority file, and improves the convenience of process addition and deletion.
Optionally, the first determining module 510 is configured to:
responding to opposite-end communication between processes, and determining whether two processes to be communicated which are opposite-end communication are in the same domain controller;
if two processes to be communicated which are opposite to each other are in the same domain controller, reading identity certificates of the domain controllers where the two processes to be communicated are located;
if two processes to be communicated which are opposite to each other are not in the same domain controller, the identity certificate of the domain controller where the local process is located is sent to the process to be communicated of the opposite end.
Optionally, the identity certificate is stored in a trust space of the corresponding domain controller, and only the identity certificate of the corresponding domain controller is stored in the trust space.
Optionally, the first determining module 510 is configured to, if two processes to be communicated that are opposite to each other are not in the same domain controller, read the corresponding identity certificate from the trust space of the domain controller where the process is located;
and sending the identity certificate read by the local process to the opposite process to be communicated.
Optionally, the first determining module 510 is configured to, if two processes to be communicated that are opposite to each other are in the same domain controller, directly read the identity certificate from the trust space of the domain controller where the two processes to be communicated are located, respectively.
Optionally, the second determining module 520 is configured to:
inquiring a permission label corresponding to a process to be communicated of an opposite end according to a process label of the process to be communicated of the opposite end, wherein an operating system of a domain controller of the process to be communicated of the opposite end is added for each process in the domain controller, the permission label is added for each permission file in the domain controller by the operating system, and the process label of the process is bound with the permission label based on a forced access control mechanism of a selinux;
and determining the authority file of the process to be communicated of the opposite terminal according to the inquired authority label.
Optionally, the authority file of the process is bound with the identity certificate of the domain controller based on a Subject Name matching rule of a ignore CN field, and the CN field has a one-to-one correspondence with the domain controller.
The specific manner in which the respective modules perform the operations of the domain controller process communication apparatus 500 in the above embodiment has been described in detail in the embodiment related to the method, and will not be described in detail herein.
Further, the modules illustrated as separate components may or may not be physically separate. Also, each module may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. When implemented in hardware, may be implemented in whole or in part in the form of an integrated circuit or chip.
The disclosed embodiments also provide a vehicle including:
a first processor;
a first memory for storing processor-executable instructions;
wherein the first processor is configured to:
determining identity certificates of two processes to be communicated which are opposite to each other in communication by responding to opposite-end communication between the processes, wherein the identity certificates are issued by a CA for each domain controller;
determining an authority file of a process to be communicated of the opposite terminal;
and establishing process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file corresponding to the processes to be communicated of the opposite ends.
It may be noted that, when the first processor in the embodiments of the present disclosure executes the executable instructions in the first memory, the domain controller process communication method in any one of the foregoing embodiments may be implemented.
The disclosed embodiments also provide a computer readable storage medium having stored thereon computer program instructions which, when executed by a second processor, implement the steps of the domain controller process communication method of any of the previous embodiments.
Fig. 6 is a block diagram of a vehicle 600, according to an exemplary embodiment. For example, vehicle 600 may be a hybrid vehicle, but may also be a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other type of vehicle. The vehicle 600 may be an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle.
Referring to fig. 6, a vehicle 600 may include various subsystems, such as an infotainment system 610, a perception system 620, a decision control system 630, a drive system 640, and a computing platform 650. Wherein the vehicle 600 may also include more or fewer subsystems, and each subsystem may include multiple components. In addition, interconnections between each subsystem and between each component of the vehicle 600 may be achieved by wired or wireless means.
In some embodiments, the infotainment system 610 may include a communication system, an entertainment system, a navigation system, and the like.
The perception system 620 may include several sensors for sensing information of the environment surrounding the vehicle 600. For example, the sensing system 620 may include a global positioning system (which may be a GPS system, a beidou system, or other positioning system), an inertial measurement unit (inertial measurement unit, IMU), a lidar, millimeter wave radar, an ultrasonic radar, and a camera device.
Decision control system 630 may include a computing system, a vehicle controller, a steering system, a throttle, and a braking system.
The drive system 640 may include components that provide powered movement of the vehicle 600. In one embodiment, the drive system 640 may include an engine, an energy source, a transmission, and wheels. The engine may be one or a combination of an internal combustion engine, an electric motor, an air compression engine. The engine is capable of converting energy provided by the energy source into mechanical energy.
Some or all of the functions of the vehicle 600 are controlled by the computing platform 650. The computing platform 650 may include at least one third processor 651 and a second memory 652, the third processor 651 may execute instructions 653 stored in the second memory 652.
The third processor 651 may be any conventional processor, such as a commercially available CPU. The processor may also include, for example, an image processor (Graphic Process Unit, GPU), a field programmable gate array (Field Programmable Gate Array, FPGA), a System On Chip (SOC), an application specific integrated Chip (Application Specific Integrated Circuit, ASIC), or a combination thereof.
The second memory 652 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
In addition to instructions 653, the second memory 652 may also store data such as road maps, route information, the position, direction, speed, etc. of the vehicle. The data stored by the second memory 652 may be used by the computing platform 650.
In embodiments of the present disclosure, the third processor 651 may execute instructions 653 to perform all or part of the steps of the domain controller process communication method described above.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (9)
1. A method for domain controller process communication, comprising:
determining identity certificates of two processes to be communicated which are opposite to each other in communication by responding to opposite-end communication between the processes, wherein the identity certificates are issued by a CA for each domain controller;
determining an authority file of a process to be communicated of the opposite terminal;
establishing process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file corresponding to the processes to be communicated of the opposite ends;
the determining, in response to peer-to-peer communication between processes, identity certificates of two processes to be communicated, each of which is a communication peer, includes:
responding to opposite-end communication between processes, and determining whether two processes to be communicated which are opposite-end communication are in the same domain controller;
if two processes to be communicated which are opposite to each other are in the same domain controller, reading identity certificates of the domain controllers where the two processes to be communicated are located;
if two processes to be communicated which are opposite to each other are not in the same domain controller, the identity certificate of the domain controller where the local process is located is sent to the process to be communicated of the opposite end.
2. The method of claim 1, wherein the identity certificate is stored in a trust space of the corresponding domain controller, wherein only the identity certificate of the corresponding domain controller is stored in the trust space.
3. The method according to claim 2, wherein if the two processes to be communicated that are opposite to each other are not in the same domain controller, sending the identity certificate of the domain controller in which the home process is located to the process to be communicated that is opposite to each other, includes:
if two processes to be communicated which are opposite to each other are not in the same domain controller, the local process reads the corresponding identity certificate from the trust space of the domain controller;
and sending the identity certificate read by the local process to the opposite process to be communicated.
4. The method according to claim 2, wherein if two processes to be communicated that are opposite to each other are in the same domain controller, the step of reading the identity certificate of the domain controller in which the two processes to be communicated are located includes:
if two processes to be communicated which are opposite to each other are in the same domain controller, the two processes to be communicated respectively and directly read the identity certificate from the trust space of the domain controller.
5. The method according to claim 1, wherein determining the rights file of the process to be communicated of the peer includes:
inquiring a permission label corresponding to a process to be communicated of an opposite end according to a process label of the process to be communicated of the opposite end, wherein an operating system of a domain controller of the process to be communicated of the opposite end is added for each process in the domain controller, the permission label is added for each permission file in the domain controller by the operating system, and the process label of the process is bound with the permission label based on a forced access control mechanism of a selinux;
and determining the authority file of the process to be communicated of the opposite terminal according to the inquired authority label.
6. The method of any of claims 1-5, wherein the rights file for a process is bound to an identity certificate of the domain controller based on a Subject Name matching rule that ignores a CN field, the CN field having a one-to-one correspondence with the domain controller.
7. A domain controller process communication device, comprising:
a first determining module configured to determine identity certificates of two processes to be communicated, which are opposite to each other in communication, in response to opposite-end communication between the processes, wherein the identity certificates are issued by a CA for each domain controller;
the second determining module is configured to determine a right file of a process to be communicated of the opposite end;
the communication module is configured to establish process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file corresponding to the processes to be communicated of the opposite ends;
the first determination module is configured to: responding to opposite-end communication between processes, and determining whether two processes to be communicated which are opposite-end communication are in the same domain controller; if two processes to be communicated which are opposite to each other are in the same domain controller, reading identity certificates of the domain controllers where the two processes to be communicated are located; if two processes to be communicated which are opposite to each other are not in the same domain controller, the identity certificate of the domain controller where the local process is located is sent to the process to be communicated of the opposite end.
8. A vehicle, characterized by comprising:
a first processor;
a first memory for storing processor-executable instructions;
wherein the first processor is configured to:
in response to peer-to-peer communication between processes, determining identity certificates of two processes to be communicated which are opposite to each other in communication, wherein the identity certificates are issued by a CA for each domain controller;
determining an authority file of a process to be communicated of the opposite terminal;
establishing process communication of two processes to be communicated, which are opposite communication ends, according to the identity certificate and the authority file corresponding to the processes to be communicated of the opposite ends;
the determining, in response to peer-to-peer communication between processes, identity certificates of two processes to be communicated, each of which is a communication peer, includes:
responding to opposite-end communication between processes, and determining whether two processes to be communicated which are opposite-end communication are in the same domain controller;
if two processes to be communicated which are opposite to each other are in the same domain controller, reading identity certificates of the domain controllers where the two processes to be communicated are located;
if two processes to be communicated which are opposite to each other are not in the same domain controller, the identity certificate of the domain controller where the local process is located is sent to the process to be communicated of the opposite end.
9. A computer readable storage medium having stored thereon computer program instructions, which when executed by a second processor, implement the steps of the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310018025.3A CN116010934B (en) | 2023-01-06 | 2023-01-06 | Domain controller process communication method, device, vehicle and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310018025.3A CN116010934B (en) | 2023-01-06 | 2023-01-06 | Domain controller process communication method, device, vehicle and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116010934A CN116010934A (en) | 2023-04-25 |
| CN116010934B true CN116010934B (en) | 2023-12-12 |
Family
ID=86024521
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310018025.3A Active CN116010934B (en) | 2023-01-06 | 2023-01-06 | Domain controller process communication method, device, vehicle and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116010934B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| NO20032996D0 (en) * | 2002-06-28 | 2003-06-27 | Microsoft Corp | Domain-based trust models for content rights management |
| CN102244656A (en) * | 2010-05-11 | 2011-11-16 | 微软公司 | Domain access system |
| CN108881131A (en) * | 2017-06-23 | 2018-11-23 | 中国人民解放军理工大学 | The efficient handover mechanism of host identities authentication information under a kind of SDN multiple domain mobile network environment |
| CN109541987A (en) * | 2018-10-17 | 2019-03-29 | 同济大学 | A kind of plug and play type intelligent automobile domain controller and method with redundancy structure |
| CN110943957A (en) * | 2018-09-21 | 2020-03-31 | 郑州信大捷安信息技术股份有限公司 | Safety communication system and method for vehicle intranet |
| CN111683060A (en) * | 2020-05-20 | 2020-09-18 | 国汽(北京)智能网联汽车研究院有限公司 | Communication message verification method, device and computer storage medium |
| CN111901119A (en) * | 2020-06-21 | 2020-11-06 | 苏州浪潮智能科技有限公司 | Security domain isolation method, system and device based on trusted root |
| CN112740617A (en) * | 2020-03-19 | 2021-04-30 | 华为技术有限公司 | Certificate list updating method and device |
| CN115022092A (en) * | 2022-08-05 | 2022-09-06 | 中汽数据(天津)有限公司 | Vehicle software upgrading method, device and storage medium |
| CN115225492A (en) * | 2022-07-06 | 2022-10-21 | 中国第一汽车股份有限公司 | Remote upgrading method and system |
| CN115378737A (en) * | 2022-10-24 | 2022-11-22 | 中汽数据(天津)有限公司 | Cross-domain device communication trust method, device, equipment and medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11194562B2 (en) * | 2017-05-19 | 2021-12-07 | Blackberry Limited | Method and system for hardware identification and software update control |
-
2023
- 2023-01-06 CN CN202310018025.3A patent/CN116010934B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| NO20032996D0 (en) * | 2002-06-28 | 2003-06-27 | Microsoft Corp | Domain-based trust models for content rights management |
| CN102244656A (en) * | 2010-05-11 | 2011-11-16 | 微软公司 | Domain access system |
| CN108881131A (en) * | 2017-06-23 | 2018-11-23 | 中国人民解放军理工大学 | The efficient handover mechanism of host identities authentication information under a kind of SDN multiple domain mobile network environment |
| CN110943957A (en) * | 2018-09-21 | 2020-03-31 | 郑州信大捷安信息技术股份有限公司 | Safety communication system and method for vehicle intranet |
| CN109541987A (en) * | 2018-10-17 | 2019-03-29 | 同济大学 | A kind of plug and play type intelligent automobile domain controller and method with redundancy structure |
| CN112740617A (en) * | 2020-03-19 | 2021-04-30 | 华为技术有限公司 | Certificate list updating method and device |
| CN111683060A (en) * | 2020-05-20 | 2020-09-18 | 国汽(北京)智能网联汽车研究院有限公司 | Communication message verification method, device and computer storage medium |
| CN111901119A (en) * | 2020-06-21 | 2020-11-06 | 苏州浪潮智能科技有限公司 | Security domain isolation method, system and device based on trusted root |
| CN115225492A (en) * | 2022-07-06 | 2022-10-21 | 中国第一汽车股份有限公司 | Remote upgrading method and system |
| CN115022092A (en) * | 2022-08-05 | 2022-09-06 | 中汽数据(天津)有限公司 | Vehicle software upgrading method, device and storage medium |
| CN115378737A (en) * | 2022-10-24 | 2022-11-22 | 中汽数据(天津)有限公司 | Cross-domain device communication trust method, device, equipment and medium |
Non-Patent Citations (2)
| Title |
|---|
| 一种兼容功能安全和信息安全的车载网络解决方案;王星炜;;中国汽车(11);全文 * |
| 软件定义汽车之E/E架构迭代演变;闫红梅;谢忠红;奚美丽;王建萍;;汽车与配件(18);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116010934A (en) | 2023-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200264864A1 (en) | Vehicle-mounted device upgrade method and related device | |
| JP6228093B2 (en) | system | |
| US9374355B2 (en) | Programming vehicle modules from remote devices and related methods and systems | |
| CN113411769B (en) | Systems, methods, and apparatus for secure telematics communications | |
| WO2015080108A1 (en) | Program update system and program update method | |
| US9253200B2 (en) | Programming vehicle modules from remote devices and related methods and systems | |
| CN107409045B (en) | Management device, management method, and storage medium | |
| CN110214308B (en) | Control device, program update method, and computer program | |
| US9464905B2 (en) | Over-the-air vehicle systems updating and associate security protocols | |
| CN111556836A (en) | Secure firmware update for remote vehicles | |
| US20190377336A1 (en) | Method and system for distributed ledger technology communications for vehicles | |
| US11182485B2 (en) | In-vehicle apparatus for efficient reprogramming and controlling method thereof | |
| US11456874B2 (en) | Vehicle control system for cybersecurity and financial transactions | |
| CN110098935B (en) | Provider network device and security certificate programming system | |
| CN111198867A (en) | Device, vehicle, network component and method for generating an identification of an equipment state | |
| CN116010934B (en) | Domain controller process communication method, device, vehicle and storage medium | |
| US20180285885A1 (en) | Modules, systems, and methods for incentivizing green driving | |
| JP6860464B2 (en) | System and management method | |
| CN112737786A (en) | Verifying vehicles traveling within a particular area | |
| KR20150089697A (en) | Secure system and method for smart cars using a mobile device | |
| US20230327882A1 (en) | Non-reputable vehicle change history | |
| US20200136837A1 (en) | Storage medium including computing capability for authentication | |
| CN111989890A (en) | System, method and device for provisioning and processing geographic location information for V2X devices | |
| KR102025808B1 (en) | Driving assistance Apparatus for Vehicle and Control method thereof | |
| JP7419287B2 (en) | Vehicle program update management system and vehicle program update management method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |