METHOD AND DEVICE FOR OPERATING A VEHICLE ELECTRICAL SYSTEM, COMPUTER PROGRAM AND COMPUTER PROGRAM PRODUCT
The selective implementation of IPsec security for specific message types in vehicle networks addresses the challenge of versatile and secure communication, achieving flexible and secure data transmission across different protocols.
Patent Information
- Application Number
- DE102016221496
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2016-11-02
- Publication Date
- 2024-11-07
- Estimated Expiration
- 2036-11-02
AI Technical Summary
Existing vehicle communication systems face challenges in enabling versatile and secure communication across different communication protocols in a vehicle electrical system, particularly when IPsec security is not feasible for all communication partners.
Implementing IPsec security selectively for certain message types based on message type determination, using firewalls and OSI layers to manage secure and unsecured data traffic in parallel, ensuring secure communication while allowing unsecured data transmission where necessary.
Enables versatile and highly secure communication in vehicle on-board networks by allowing IPsec-secured and unsecured data traffic to coexist, ensuring high security levels where feasible and flexibility where not.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] The invention relates to a method for operating a vehicle electrical system. The invention further relates to a device for operating the vehicle electrical system. The invention further relates to a computer program and a computer program product for operating the vehicle electrical system.
[0002] In modern vehicles, many different control units communicate with each other via an on-board network. Many different communication protocols can be used for this purpose.
[0003] DE 10 2014 200 558 A1 relates to a method for controlling a supplicant's access to an Ethernet network via an authenticator; wherein the method comprises authenticating the supplicant with the authenticator using an authentication protocol; determining the transit time of a message between the supplicant and the authenticator; and controlling the supplicant's access to the Ethernet network based on the successful authentication and the determined transit time. EP 1 496 665 A2 relates to a method for determining security settings in an automation network for data access by a first participant to a second participant via the automation network, wherein the first participant determines the security settings of the second participant and makes its own security settings depending on the security settings of the second participant.
[0004] The object underlying the invention is to enable versatile communication in a vehicle's on-board network.
[0005] The problem is solved by the features of the independent patent claim. Advantageous embodiments are characterized in the dependent claims.
[0006] The invention is characterized by a method for operating a vehicle electrical system. The invention is further characterized by a device for operating the vehicle electrical system. The device is configured to carry out the method for operating the vehicle electrical system or an optional embodiment of the method.
[0007] The process for operating the vehicle's on-board network begins with the receipt of a message. Upon receiving the message, the system determines, depending on the message type, whether the message is secured with IPsec. If IPsec security is determined, the system checks whether the message is indeed secured using IPsec. If the message is secured with IPsec, it is processed further.
[0008] IPsec security specifically includes the use of the IPsec (Internet Protocol Security) protocol suite according to RFC 2401 or RFC 4301 for message security.
[0009] Further processing of the message includes, in particular, processing of the message's payload data, such as storing, forwarding, or using the payload data for an application.
[0010] The requirement that IPsec encryption is provided for certain message types implies that specified communication partners, such as specified sensors and / or control devices, can send their data without IPsec encryption, and other communication partners, such as specified sensors and / or control devices, must send their data with IPsec encryption.
[0011] This allows IPsec and unencrypted data traffic to be implemented in parallel within a vehicle's onboard network, depending on the message type. This enables versatile communication within the vehicle's onboard network. This is particularly advantageous when IPsec message encryption is not technically possible for some communication partners within the network, but is for others. This allows for a very high level of security in communication on the data bus, as IPsec message encryption can be implemented for all message types where it is feasible.
[0012] According to an optional configuration, the verification of whether the message is secured using IPsec is carried out by means of a firewall that only allows IPsec-secured messages on specified ports.
[0013] This makes it very easy to prevent messages from specific communication partners or certain types of messages from reaching an application. It is therefore very easy to specify IPsec protection for certain types of messages. Furthermore, it is very easy to adjust the settings later using a firewall.
[0014] According to another optional configuration, the verification of whether the message is secured using IPsec is carried out via an interface of OSI Level 7 and OSI Level 3, which checks whether the message is secured at OSI Level 3 IPsec.
[0015] Since it is normally no longer visible at OSI Level 7 whether a message was saved, an interface to Level 3 can be used to check whether the message was saved. This allows it to be determined retrospectively at OSI Level 7, i.e., at the application layer, whether the message was saved.
[0016] According to another optional configuration, the validity of the message is checked depending on the IPsec security and the message is processed further depending on the verification.
[0017] According to another optional configuration, depending on the IPsec security, the authenticity of a communication partner of the message is checked and, depending on the verification, the message is processed further.
[0018] Verifying authenticity makes it possible to detect and easily prevent man-in-the-middle attacks and similar threats.
[0019] Authenticity is verified, in particular, through key management.
[0020] According to another optional configuration, the message's payload data is unencrypted.
[0021] Because the user data is unencrypted, message content can be checked during security checks, especially in the development environment, but also later in field use.
[0022] According to a further optional configuration, depending on a unique, one-time-use code, the determination of whether an IPsec backup of the message is necessary and the verification of whether the message is secured using IPsec are deactivated, so that an IPsec-free message transmission can be implemented.
[0023] According to another aspect, the invention is characterized by a computer program, wherein the computer program is configured to carry out the method for operating a vehicle electrical system or an optional embodiment of the method.
[0024] According to another aspect, the invention is characterized by a computer program product comprising an executable program code, wherein the program code, when executed by a data processing device, performs the method for operating the vehicle's on-board network or an optional embodiment of the method.
[0025] The computer program product includes, in particular, a medium readable by the data processing device on which the program code is stored.
[0026] Exemplary embodiments of the invention are explained in more detail below with reference to the schematic drawing. It shows: Fig. 1. A flowchart for operating a vehicle electrical system.
[0027] The Fig. Figure 1 shows a flowchart of a program for operating a vehicle electrical system. The program can be executed, in particular, by a control device.
[0028] The control device includes, in particular, a processing unit, a program and data memory, and, for example, one or more communication interfaces. The program and data memory and / or the processing unit and / or the communication interfaces can be integrated into a single unit and / or distributed across multiple units.
[0029] The control device can also be described as a device for operating a vehicle's electrical system.
[0030] For this purpose, a program for the vehicle's on-board network is stored in the program and data memory of the control device.
[0031] The program is started in step S1, in which variables can be initialized if necessary.
[0032] In step S3, a message is received.
[0033] In step S5, when receiving the message, it is determined, depending on the message type, whether an IPsec backup of the message is specified.
[0034] The message is sent and received in particular within the framework of the SOME / IP (Scalable service-Oriented MiddlewarE over IP) protocol framework, especially according to the AUTOSAR 4.1 or 4.2 specification.
[0035] If an IPsec encryption of the message is specified, the program continues in step S7. If no IPsec encryption is specified, the message is processed directly.
[0036] Step S7 checks whether the message is secured using IPsec.
[0037] The verification of whether the message is secured using IPsec is carried out, for example, by means of a firewall that only allows IPsec-secured messages on specified ports.
[0038] Alternatively or additionally, the verification of whether the message is secured using IPsec is carried out via an interface of OSI Level 7 and OSI Level 3, which checks whether the message is secured at OSI Level 3 IPsec.
[0039] If the message is secured using IPsec, the program continues in step S9.
[0040] If the message is not secured using IPsec, the message will be ignored, or in other words, not processed further.
[0041] In step S11, the message is processed further.
[0042] Alternatively or additionally, the validity of the message can optionally be checked before step S11, depending on the IPsec security, and the message can be processed further depending on the check.
[0043] Alternatively or additionally, depending on the IPsec security, the authenticity of a communication partner of the message can optionally be checked before step S11, and the message can be processed further depending on the verification.
[0044] In step S13, the program is terminated and can be restarted in step S1 if necessary.
[0045] Further processing of the message includes, in particular, processing the message's payload, such as storing, forwarding, or using the payload for an application. With IPsec encryption, the payload is unencrypted.
[0046] The method described above allows IPsec and unencrypted data traffic to be implemented in parallel within the vehicle's on-board network, depending on the message type. This enables versatile and highly secure communication within the vehicle's on-board network, as IPsec encryption can be implemented for all message types where this is possible.
Claims
[1] Method for operating a vehicle electrical system, in which - a message is received, - when receiving the message, depending on the message type, it is determined whether IPsec security of the message is specified, whereby it is determined from which communication partner the message was sent, whereby first specified communication partners can send their data without IPsec security, and second specified communication partners must send their data with IPsec security, - if it has been determined that IPsec security of the message is specified, it is checked whether the message is secured using IPsec, - if the message is secured using IPsec, the message is further processed. [2] Method according to claim 1, wherein the check as to whether the message is secured by means of IPsec is carried out by means of a firewall which only allows IPsec-secured messages on predetermined ports. [3] Method according to claim 1 or 2, wherein the verification of whether the message is secured by means of IPsec is carried out by means of an OSI Level 7 and OSI Level 3 interface, by means of which it is verified whether the message is secured at OSI Level 3 IPsec. [4] Method according to one of the preceding claims, wherein the validity of the message is checked depending on the IPsec security, and the message is further processed depending on the check. [5] Method according to one of the preceding claims, wherein the authenticity of a communication partner of the message is checked depending on the IPsec security, and the message is further processed depending on the check. [6] Method according to one of the preceding claims, wherein payload data of the message is unencrypted. [7] Method according to one of the preceding claims, in which, depending on a unique one-time-use code, the determination of whether an IPsec security of the message is necessary and the checking of whether the message is secured by means of IPsec are deactivated, so that an IPsec-free message transmission can be realized. [8] Device for operating a vehicle electrical system, wherein the device is designed to carry out a method according to one of claims 1 to 7. [9] Computer program for operating a vehicle electrical system, wherein the computer program is designed to carry out a method according to one of claims 1 to 7 when executed on a data processing device. [10] A computer program product comprising executable program code, wherein the program code, when executed by a data processing device, carries out the method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Secure network access protection via authenticated time measurement
DE102014200558A1
Method and apparatus for security configuration in an automisation network
EP1496665A2
Method and device for the secure transmission of data
DE102009051383A1
