DE102020205994A1 - Concept for exchanging encrypted data - Google Patents

Abstract

The present invention relates to computer-implemented methods, devices and computer programs for exchanging encrypted messages. A computer-implemented method for the encrypted provision of data from a data source for a plurality of devices, the method comprising obtaining (110) one or more addresses from one or more electronic mailboxes of the plurality of devices. The method includes obtaining (120) cryptographic keys of the plurality of devices. The method further comprises generating (130) one or more messages for the plurality of devices based on the data, with individually encrypted messages being generated for the devices of the plurality of devices based on the cryptographic keys. The method further comprises providing (140) the one or more encrypted messages via at least one electronic mailbox based on the one or more addresses of the one or more electronic mailboxes of the plurality of devices.

Description

The present invention relates to computer-implemented methods, devices and computer programs for exchanging encrypted messages.

A popular approach in cryptography for encrypting data to be sent to a recipient without first agreeing on a secret key that must be exchanged between the two communication partners in a tap- and tamper-proof way is asymmetric cryptography. Each participant generates a key pair from a private and public key.

As can already be seen from the name, the public key does not hold a secret, but can be distributed to the public (there are, for example, public key servers through which one can make one's own public key accessible to the general public).

If a sender wants to transmit information to a recipient in encrypted form, he asks him (or on one of the public key servers described above) the public key of this person, which can be used to send a message to him (and only to him) encrypt.

The special thing about asymmetric cryptography is that this message, which is encrypted with the public key, can only be decrypted with the associated private key. The private key of such a key pair should therefore be kept strictly secret.

In contrast, with symmetrical cryptography, the encryption and decryption of a message takes place with the same key, so that with this type of encrypted communication such a key must first be exchanged on a secure channel (e.g. a personal meeting), which at the same time Describes the advantage of asymmetric cryptography, since here, due to the fact that the public key is public, no such secure exchange has to take place. If two people want to communicate with each other in encrypted form, they only need to know the other person's public key, which is usually not a problem.

Another functionality of asymmetric cryptography is the signing of messages. If the sender of a message wants to digitally sign it in order to prove that it actually originates from him, he can sign it with his private key. The recipient can then use the sender's public key to check the signature of the message - that is, to ensure its authenticity. Since the private key is secret, the recipient can be relatively certain that the message actually came from the expected person.

In the future, more and more devices connected to a network (such as the Internet) (so-called “IoT Devices”) will provide data - such as in process networks (such as those in the context of Supply chains, English "Supply Chains"). A challenge here can be to ensure that the data received actually originate from the expected device and not from a sender masquerading as the device from which the data appears to be. In addition, it can be a challenge, on the one hand, to provide the data to a plurality of data targets and, on the other hand, to ensure that the respective data is only available to authorized data targets.

There is a need to provide an improved concept for an encrypted exchange of data from a data source with one or more other devices.

This need is met by exemplary embodiments of the present disclosure.

Embodiments of the present disclosure are based on the knowledge that data can be transmitted via distributed databases, such as databases that are based on distributed ledger technology (literally translated: distributed ledger technology). Although communication between the communication partners is public there, depending on the implementation, the data can be provided individually for each device from a data source through targeted encryption without the actual data being read or manipulated by unauthorized persons. This is supported in particular by the fact that subsequent manipulations or manipulations at individual nodes can be traced in distributed ledger technology-based distributed databases. Alternatively, the concept can also be transferred to centralized data beacons.

Various exemplary embodiments of the present invention relate to a (first) computer-implemented method for the encrypted provision of data from a data source for a plurality of devices (or generally “participants” in a communication, for example a process network). The method includes obtaining one or more addresses from one or more electronic mailboxes of the plurality of devices. The method includes obtaining cryptographic keys of the plurality of devices. The method further comprises generating one or more messages for the plurality of devices based on the data. Individually encrypted messages based on the cryptographic keys are generated for the devices of the plurality of devices. The method further comprises providing the one or more encrypted messages via at least one electronic mailbox based on the one or more addresses of the one or more electronic mailboxes of the plurality of devices. Thanks to the device-specific encryption, the data can be made available securely and in a targeted manner even via a public resource such as an electronic mailbox in a distributed database.

For example, the data can be provided via the one or more messages in such a way that the accessibility of the data within the respective encrypted message for the plurality of devices is controlled via the encryption of the messages.

Different approaches can be chosen. On the one hand, the data can be encrypted at the data record level. This can be done, for example, in that an individually encrypted message is generated for each device of the plurality of devices. The individually encrypted message can include the data that should be accessible to the respective device.

On the other hand, the data can be encrypted at the attribute level. For example, a message can be generated for the plurality of devices. The data can be encrypted within the message individually for the majority of devices. In other words, the devices can receive the same message but decrypt different parts of the message. Alternatively, the parts of the message to be encrypted differently (ie the attributes or groups of attributes) can be sent in different technical messages, which are then reassembled on the recipient side to form the actual message with different visibilities.

For example, obtaining the cryptographic key of the plurality of devices can include retrieving a public key of the respective device from the electronic mailbox of the device. This ensures that the data is accessed using the device's current public key.

In general, two types of cryptographic keys can be used to encrypt data individually for the devices. On the one hand, device-specific public keys of the devices can be used to provide the respective devices with the data individually. If the same data of a closed group is to be transmitted to devices, cryptographic keys can be used for group communication, for example. Consequently, the cryptographic keys can comprise one or more device-specific public keys and / or one or more cryptographic keys for a group of devices.

In some exemplary embodiments, the one or more messages are provided via an electronic mailbox of the data source or via an electronic group mailbox. In these cases, the method can furthermore include providing notifications about the provision of the one or more messages for the devices, via the electronic mailboxes of the respective devices. In other words, the data can be held in the data source's electronic mailbox or in a group mailbox, and the devices are notified of this via notifications to their own electronic mailboxes.

Alternatively, the one or more messages can be delivered directly via the electronic mailboxes of the devices, so that no additional notification is required.

In general, the electronic mailboxes can be accessible via a distributed database. This can enable distributed storage of the data. A distributed database can offer greater security, since redundancy can avoid a single point of failure, which could be exploited to thwart or manipulate the exchange of data. In addition, manipulations can be traced if necessary.

For example, the distributed database can be based on a distributed ledger technology. Correspondingly, addresses of the electronic mailbox of the data source and of the one or more electronic mailboxes of the plurality of devices (that is to say the addresses of the electronic mailboxes) can be addresses on the distributed ledger. Distributed ledger technology combines the redundancy of distributed databases with protection against manipulation on individual nodes.

For example, the distributed database can be based on a plurality of nodes. The provision and / or receipt of data via an electronic mailbox via the distributed database can be based on a random selection of one or several nodes of the plurality of nodes for providing and / or receiving the information are based. The random selection can prevent the manipulation of a few preselected nodes from sabotaging the data exchange. By using several nodes, redundancy can be increased, and thus also the reliability of data transmission.

Embodiments of the present invention also provide a (second) computer-implemented method for the encrypted receipt of data from a data source by a device (or generally “subscriber”). The method includes receiving a message from a data source via an electronic mailbox accessible via a distributed database. The message includes data that is individually encrypted for the device (or for a group of devices) by the data source. The method further comprises decrypting the data based on a cryptographic key of the device. A distributed database can offer greater security for data transmission, since a single point of failure can be avoided through redundancy and manipulations can be traced if necessary. Individual encryption enables secure data transmission via a publicly accessible, distributed database.

In general, two types of cryptographic keys can be used to encrypt data individually for the devices. On the one hand, device-specific public keys of the devices can be used to provide the respective devices with the data individually. If the same data of a closed group is to be transmitted to devices, cryptographic keys can be used for group communication, for example. Consequently, the data can be encrypted based on a device-specific public key of the device. Alternatively, the data can be encrypted based on a cryptographic key for a group.

In some exemplary embodiments, the message can be received via an electronic mailbox of the data source or via a group mailbox. In these cases, the method can further include receiving notification of the message via an electronic mailbox of the device. Alternatively, the message can be received via an electronic mailbox of the device, whereby the notification can be omitted.

Embodiments of the present disclosure also create a program with a program code for performing at least one of the methods when the program code is executed on a computer, a processor, a control module or a programmable hardware component.

Embodiments also create a computer-implemented device for the encrypted provision of data from a data source for a plurality of devices (subscribers). The device includes an interface for communication with the plurality of devices. The device further comprises one or more processors designed to carry out the first method.

Embodiments also provide a computer-implemented device for the encrypted receipt of data from a data source by a device (subscriber). The device comprises an interface for communication with the data source. The device comprises one or more processors designed to carry out the second method.

• 1a zeigt ein Flussdiagramm eines Ausführungsbeispiels eines Verfahrens zum verschlüsselten Bereitstellen von Daten einer Datenquelle für eine Mehrzahl von Geräten;
• 1b zeigt ein Blockdiagramm eines Ausführungsbeispiels einer Vorrichtung zum verschlüsselten Bereitstellen von Daten einer Datenquelle für eine Mehrzahl von Geräten;
• 2a zeigt ein Flussdiagramm eines Ausführungsbeispiels eines Verfahrens zum verschlüsselten Erhalten von Daten einer Datenquelle durch ein Gerät; und
• 2b zeigt ein Blockdiagramm eines Ausführungsbeispiels einer Vorrichtung zum verschlüsselten Erhalten von Daten einer Datenquelle durch ein Gerät.

Further advantageous configurations are described in more detail below with reference to the exemplary embodiments shown in the drawings, to which exemplary embodiments are generally but not limited as a whole. Show it:

• 1a shows a flowchart of an exemplary embodiment of a method for the encrypted provision of data from a data source for a plurality of devices;
• 1b shows a block diagram of an embodiment of a device for encrypted provision of data from a data source for a plurality of devices;
• 2a shows a flowchart of an embodiment of a method for encrypted receipt of data from a data source by a device; and
• 2 B shows a block diagram of an embodiment of a device for encrypted receipt of data from a data source by a device.

Various embodiments will now be described more fully with reference to the accompanying drawings, in which some embodiments are shown.

In the following description of the attached figures, which only show a few exemplary embodiments, the same reference symbols can designate the same or comparable components. Furthermore, summarizing reference symbols can be used for components and objects which, however, occur several times in an exemplary embodiment or in a drawing are described jointly with regard to one or more features.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as assigned to them by one of ordinary skill in the art to which the exemplary embodiments belong. It should also be clarified that terms, such as those defined in commonly used dictionaries, are to be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and not in an idealized or excessively formal sense are to be interpreted unless expressly defined herein.

1a shows a flowchart of an embodiment of a computer-implemented method for the encrypted provision of data from a data source for a plurality of devices. The method includes obtaining 110 from one or more addresses from one or more electronic mailboxes of the plurality of devices. The method includes obtaining 120 of cryptographic keys of the plurality of devices. The method includes generating 130 of one or more messages for the plurality of devices based on the data. Individually encrypted messages based on the cryptographic keys are generated for the devices of the plurality of devices. The method includes providing 140 the one or more encrypted messages via at least one electronic mailbox based on the one or more addresses of the one or more electronic mailboxes of the plurality of devices.

1b FIG. 3 shows a block diagram of an exemplary embodiment of a corresponding computer-implemented device 10 for the encrypted provision of data from a data source 100 for a variety of devices 200 . The device includes an interface 12th to communicate with the plurality of devices. The method also includes one or more processors 14th that are coupled to the interface. In general, the functionality of the device is provided by the one or more processors, for example with the aid of the interface. For example, the one or more processors can be designed to carry out internal calculations of the device and to coordinate the communication with the plurality of devices. The interface can be used to carry out communication. The one or more processors are designed to carry out the method of FIG 1a , for example in conjunction with the interface. As a result, the device, and in particular the one or more processors of the devices, is further developed by the features of the method. 1b also shows the data source 100 with the device 10 .

Various exemplary embodiments of the present invention relate to a computer-implemented method, a computer-implemented device and a computer program for providing data from a data source for a plurality of devices from the point of view of the data source. In principle, both the data source and the one or more devices can be devices of the Internet of Things, for example. loT devices or loT devices. This generally includes devices that communicate (independently) with other devices, ie a device of the Internet of Things can be characterized as a device that is "networked", that is, designed to communicate with one or more other devices. In the following, reference is made in particular to vehicles. The data source can thus be a vehicle, for example, or one or more of the plurality of devices can be vehicles. In particular, the data source can also be a component of a vehicle, and the plurality of devices can also be (other) vehicle components, such as control units of the vehicle. In principle, the roles can also be interchanged - a data source can also be a device and a device can also be a data source - depending on which entity provides the data and which entity receives the data. The data source can therefore also be designed to perform the method of 2a perform, and one of the plurality of devices can be configured to perform the method of 1a to execute. The data source and the plurality of devices are in communication with one another, for example via a distributed database. The distributed database can be accessible via a computer network, for example.

The method includes obtaining 110 from one or more addresses from one or more electronic mailboxes of the plurality of devices. In principle, the majority of devices can be addressed via two different types of electronic mailboxes. On the one hand, each device can have its own electronic mailbox, i.e. each device can be assigned a device-specific electronic mailbox. On the other hand, the majority of devices can also communicate via so-called electronic group mailboxes, that is to say mailboxes that are used by several devices to receive messages. The respective device can either monitor the group mailbox in order to receive newly received messages, or the device can receive a notification of the receipt of a message in the electronic group mailbox via its device-specific electronic mailbox. Another possibility is that Messages are stored in the electronic mailbox of the data source, and the respective device or group of devices receives a notification about the message in its device- or group-specific electronic mailbox. Therefore, the one or more addresses of the one or more electronic mailboxes can include addresses of the device-specific electronic mailboxes of the devices and / or addresses of one or more electronic group mailboxes that are used by the plurality of devices.

The method further includes obtaining 120 the cryptographic keys of the majority of devices. Analogous to the mailboxes, a distinction is again made between two types of cryptographic keys. For example, the cryptographic keys can include one or more device-specific public keys of the plurality of devices. These can be, for example, the respective public keys of an asymmetric key pair of the devices. For example, the cryptographic key for each device of the plurality of devices can comprise a device-specific key. For example, obtaining the cryptographic key of the plurality of devices can include retrieving a (device-specific) public key of the respective device from the electronic mailbox of the device. Alternatively or additionally, the cryptographic keys can comprise one or more cryptographic keys for a group of devices, for example a cryptographic group key. The cryptographic group key can be a public group key of an asymmetric key pair for the respective group, or the cryptographic group key can be a symmetric group key that is exchanged in encrypted form between the data source and the plurality of devices (e.g. based on asymmetric encryption using the public key the devices and the data source).

In general, the addresses of the devices and / or the cryptographic keys can be obtained in several ways. For example, the one or more addresses and / or the cryptographic keys can be read out from a memory of the data source, for example from firmware (hardware programming) of the data source or from a trusted execution environment of the data source. Alternatively or additionally, the one or more addresses and / or the cryptographic keys can be called up from a trustworthy central point. Alternatively or additionally, the one or more addresses and / or the cryptographic keys can be made known by the respective devices, for example by notifying the data source via the electronic mailbox of the data source.

The method further includes generating 130 the one or more messages for the plurality of devices based on the data. Individually encrypted messages based on the cryptographic keys (and based on the data) are generated for the devices of the plurality of devices. The data can be, for example, data generated by the data source. For example, the data source can be a sensor or comprise a sensor, for example a sensor of a vehicle, and the data can be sensor data from the sensor. Alternatively, the data source can be a control device of a vehicle, and the data can be status information of the control device.

The data is encrypted individually for the majority of devices. The encryption converts the data to be encrypted into a format based on the recipient's cryptographic (public) key using a cryptographic arithmetic operation, so that the encrypted data can only be converted back with the corresponding (private) key. In some embodiments, “individually encrypted” does not necessarily mean that the data is encrypted separately for each device. For example, the data can be provided via the one or more messages in such a way that the accessibility of the data within the respective encrypted message for the plurality of devices is controlled via the encryption of the messages. In some exemplary embodiments, the data for a group of vehicles (that is to say for example a real subset of the plurality of vehicles) can be encrypted with a group key; for other vehicles, the data can be encrypted with the respective device-specific public key. In some exemplary embodiments, however, the data are individually (for example separately) encrypted for each device of the plurality of devices. In addition, there are also several options for generating the one or more messages. In one variant, a separate message can be generated for each vehicle of the plurality of vehicles (which can be encrypted, for example, based on the device-specific public key of the vehicle). The content of the message can be completely encrypted based on a (single) cryptographic key. Such a procedure can also be referred to as "encryption at data record level", since the entire data record (content) of the message is encrypted with the same key. An individually encrypted message can be generated for each device of the plurality of devices. The individually encrypted message can be those Include data that should be accessible for the respective device. Alternatively, a (single) message can comprise several components, with the different components being able to be encrypted differently. In other words, a (single) message can be generated for the plurality of devices. The data can be encrypted within the message individually for the majority of devices. In other words, the components of the message can be intended for different devices of the plurality of devices and can accordingly also be encrypted differently. Mixed forms are also possible.

In some exemplary embodiments, the one or more messages are further signed by the data source with the private key of the data source. The devices providing the messages can then verify the authenticity of the messages based on the data source's public key. Accordingly, the method may include signing the one or more messages.

The method further comprises providing 140 the one or more encrypted messages via at least one electronic mailbox based on the one or more addresses of the one or more electronic mailboxes of the plurality of devices. As already presented, several implementations are possible here. For example, the one or more messages can be provided via an electronic mailbox of the data source or via an electronic group mailbox. In these cases, the method can also include providing notifications 150 on providing the one or more messages for the devices via the electronic mailboxes of the devices (based on the addresses of the electronic mailboxes of the devices). In other words, the data source can make the data available in a generally accessible mailbox (the data source or the group) and notify the individual devices about this. The respective devices can then pick up the messages from the generally accessible mailbox. Alternatively, the one or more messages can be delivered (directly) via the electronic mailboxes of the devices.

As already mentioned above, the communication between the data source and the majority of devices is based on so-called electronic mailboxes. The electronic mailboxes can for example be kept outside the data source / the respective devices, for example by a distributed (decentralized) database or by a centralized database. In principle, the electronic mailboxes can be publicly accessible so that, for example, every device that has access to the distributed database can write to the respective mailbox and / or read out the respective mailbox. In other words, the electronic mailbox of the data source and the one or more electronic mailboxes of the plurality of devices can be accessible via a distributed database, or alternatively via a centralized database. The distributed database is characterized in that it is not under the control of a single entity, but is offered in a distributed manner by a plurality of (computing) nodes. In other words, the distributed database can be based on a plurality of nodes. Data of the distributed database is replicated between the computing nodes of the plurality of nodes. The nodes can add data to the distributed database and are then replicated to the other nodes. One possible implementation of such a distributed database is based on distributed ledger technology. In other words, the distributed database can be based on a distributed ledger technology. Various distributed ledger technologies are conceivable for this, such as blockchain or a directed acyclic graph (DAG, directed acyclic graph). Addresses of the electronic mailboxes of the data source and of the plurality of devices can consequently be addresses on the distributed ledger.

The addressed electronic mailboxes can be, for example, data stores that are provided by the distributed database or the centralized database. These data memories can be addressed by the process partners involved, such as the data source and the majority of devices, but also other devices with access to the distributed or centralized database, for example with the option of reading data from the data memory and storing data in the data memory . In order to send a message / data to another entity, this message / data can either be stored in the data memory that corresponds to the electronic mailbox of the other entity, or the message / data can be stored in a data memory that is an electronic mailbox of the sending party Entity, and in addition a notification can be stored in the data store corresponding to the electronic mailbox of the other entity. The electronic mailboxes are arranged outside of the respective devices, in the distributed or centralized database. In the context of distributed ledger technology, an electronic mailbox is a data memory that is accessible via an address on the distributed ledger and on which data can be stored via the distributed ledger.

As a result, the data exchanged via the electronic mailboxes is stored in the distributed ledger. In order to increase reliability, two approaches can be chosen. On the one hand, the respective data can be inserted into the distributed database on several nodes. On the other hand, the nodes can be selected based on a random method. In other words, the provision and / or the receipt of data via an electronic mailbox via the distributed database can be based on a random selection of one or more nodes of the plurality of nodes for the provision and / or receipt of the information. In other words, the device for providing / transmitting data can transmit the corresponding data to (a random selection of) several / several nodes in the distributed database via an electronic mailbox. In order to retrieve / receive data from a mailbox, the device can receive / retrieve the corresponding data from (a random selection of) multiple nodes of the distributed database, and then compare the data of the various nodes in order to obtain unmanipulated data.

the interface 12th can for example correspond to one or more inputs and / or one or more outputs for receiving and / or transmitting information, for example in digital bit values based on a code, within a module, between modules, or between modules of different entities. For example, the interface 12th be designed to communicate via the distributed database. The distributed database can be accessed via a computer network, for example via a public computer network such as the Internet, or via a non-public computer network. The interface can 12th be designed to access the distributed database via a computer network. The distributed database can be accessed by transmitting and receiving digital data packets, for example through the use of interfaces provided by computing nodes from which the distributed database is provided.

In exemplary embodiments, the one or more processors can correspond to any controller or processor or a programmable hardware component. For example, the functionality of the one or more processors can also be implemented as software that is programmed for a corresponding hardware component. In this respect, the one or more processors can be implemented as programmable hardware with appropriately adapted software. Any processors such as digital signal processors (DSPs) can be used. Embodiments are not restricted to a specific type of processor. There are arbitrary processors or a plurality of processors for implementing the one or more processors 14th conceivable.

More details and aspects of the method and apparatus of FIG 1a and / or 1b are mentioned in connection with the concept or examples that are before or after (e.g. 2a or 2 B) to be discribed. The method and apparatus of the 1a and / or 1b may include one or more additional optional features that correspond to one or more aspects of the proposed concept or the examples described, as described before or after.

2a shows a flowchart of an embodiment of a computer-implemented method for the encrypted receipt of data from a data source by a device. The method includes obtaining 210 a message from a data source through an electronic mailbox accessible through a distributed database. The message includes data that is individually encrypted for the device by the data source. The method further includes decryption 220 of the data based on a cryptographic key of the device.

2 B FIG. 3 shows a block diagram of an exemplary embodiment of a corresponding computer-implemented device 20th to receive encrypted data from a data source 100 through a device 200 . The device includes an interface 22nd for communication with the data source (e.g. via the distributed database). The device includes one or more processors 24 that are coupled to the interface. In general, the functionality of the device is provided by the one or more processors, for example with the aid of the interface. For example, the one or more processors can be designed to carry out internal calculations of the device and to coordinate communication with the data source or other communication partners. The interface can be used to carry out communication. The one or more processors are designed to carry out the method of FIG 2a , for example in conjunction with the interface. As a result, the device, and in particular the one or more processors of the devices, is further developed by the features of the method. 2 B also shows the device 200 with the device 20th .

While the embodiments related to 1a and 1b were presented, refer to the data source, refer the embodiments of 2a and 2 B on one device 200 the majority of devices such as those related to the 1a and 1b were presented. Correspondingly, the message received can also correspond to the message received from the data source of 1a and / or 1b has been provided.

The method includes obtaining 210 the message from the data source via an electronic mailbox accessible via a distributed database. The message includes data that is encrypted individually for the device (or group of devices) by the data source (such as in connection with 1a and / or 1b). The message can be received, for example, via an electronic mailbox of the data source or via an electronic group mailbox. In these cases, the device can be notified of the receipt of the message via its own electronic mailbox. For example, the method can furthermore comprise receiving a notification of the message via an electronic mailbox of the device. Alternatively, the message can be received directly from an electronic mailbox on the device. "Receiving the message via an electronic mailbox" corresponds, for example, to retrieving the message from the respective mailbox. For example, the respective mailbox (for example the electronic group mailbox or the electronic mailbox of the device) can be monitored by the device and the respective message can be retrieved if it has been stored in the respective mailbox.

The method further includes decrypting 220 of the data based on the device's cryptographic key. Here come, as well as in connection with the 1a and / or 1b, different types of cryptographic keys are considered. For example, the data can be encrypted based on a device-specific public key of the device. In this case, the data can be decrypted based on a device-specific private key of the device. Alternatively or additionally, the data can be encrypted for a group based on a cryptographic key. In this case, the data can be decrypted based on a symmetric key for the group or based on a private key for the group.

In at least some exemplary embodiments, the message of the data source is signed by the data source, for example with a private key of the data source, and can therefore also be checked based on the public key of the data source in order to check whether the message also originates from the data source. The method can thus also include checking 230 a signature of the message, for example to determine whether the message originated from the data source. The check can be based on the public key of the data source. This can be accessed, for example, from a public key server or from an electronic mailbox at the data source.

the interface 22nd can for example correspond to one or more inputs and / or one or more outputs for receiving and / or transmitting information, for example in digital bit values based on a code, within a module, between modules, or between modules of different entities. For example, the interface 22nd be designed to communicate via the distributed database. The distributed database can be accessed via a computer network, for example via a public computer network such as the Internet, or via a non-public computer network. The interface can 22nd be designed to access the distributed database via a computer network. The distributed database can be accessed by transmitting and receiving digital data packets, for example through the use of interfaces provided by computing nodes from which the distributed database is provided.

In embodiments, the one or more processors 24 correspond to any controller or processor or a programmable hardware component. For example, the functionality of the one or more processors can also be implemented as software that is programmed for a corresponding hardware component. In this respect, the one or more processors can be implemented as programmable hardware with appropriately adapted software. Any processors such as digital signal processors (DSPs) can be used. Embodiments are not restricted to a specific type of processor. There are arbitrary processors or a plurality of processors for implementing the one or more processors 24 conceivable.

More details and aspects of the method and apparatus of FIG 2a and / or 2b are mentioned in connection with the concept or examples that are before or after (e.g. 1a and / or 1b). The method and apparatus of the 2a and / or 2b may include one or more additional optional features that correspond to one or more aspects of the proposed concept or the examples described, as described before or after.

Embodiments of the present invention relate to communication encryption between devices, such as loT devices, for example via distributed ledger networks.

The mode of operation of the invention is described using an example from the context of “supply chains”, but is useful and applicable for every scenario that has the features described above. Specifically, the present example is about the outbound logistics process (outbound logistics process), i.e. the dispatch of finished vehicles. Numerous partners (such as logisticians, shipping companies, service providers, banks, insurance companies, etc.) and of course the vehicles that have just rolled off the assembly line take part in this process as process instances.

A participant within this process network would like to be able to be sure that the received data comes from the affected vehicle (or participant in general) itself and that it is actually a vehicle of the process partner (i.e. the OEM, original equipment manufacturer, original equipment manufacturer). In the same way, the manufacturer / OEM would like to be sure that the received data actually originate from their “own” vehicle (which acts autonomously with regard to the data delivery) and that an attacker has not usurped its identity. In summary, nobody (not the manufacturer, nor other participants, nor any attacker) should be allowed to send messages on behalf of a data supplier (here: vehicle). The vehicle can, for example, be a device 200 and / or a data source 100 from 1a until 2 B , and the participant in the process network of a data source 100 from 1a and / or 1b.

A possible implementation of data provision by other process participants is presented below. In such a network it can happen that data is not only shared by the main data provider (e.g. a loT device), but the other participants also contribute data (e.g. additions, such as status changes, etc.). In such cases, you can proceed as follows: Section 1.1: The provider of the date (hereinafter referred to as "BD"; with its own letter box LA _BD , for example the data source 100 from 1a and / or 1b) creates a new address on the distributed ledger (ie a type of additional mailbox, hereinafter referred to as “L _AAdd itionalDate”). This can be done either per data to be distributed or once per process instance for several data (in principle this could only be done once per process participant, but since there are usually different process participants per process instance, the data is mixed there). As described later, this step is optional.

Section 1.2: The BD reads the mailbox addresses (LAX) of all other process participants (e.g. the majority of devices of the 1a until 2 B) from his own mailbox LA _BD and determines from each mailbox the public key of the respective process participant and thus of course also that of the loT device (or in the example that of the vehicle).

Section 1.3: The BD generates a message for each process participant (device of the plurality of devices) which contains the information to be distributed and encrypts this with the respective public key of the corresponding participant. For example, these messages are all sent to the LA _{AdditionalDate} address.

Section 1.4: The BD sends a notification of the new _{information stored in LA AdditionalDate} (including address) to the mailboxes of all those involved in the process (e.g. the electronic mailboxes of the majority of devices).

Section 1.5: The loT device can also publish this information in its own message channel (for documentation or to reach other recipients who may not be known to BD). This approach also enables other process participants to contribute data. The detour via the address LA _{AdditionalDate} (see Sections 1.1 and 1.4) is (only) intended for documentation purposes. Instead of channeling the messages about a new date in LA _{AdditionalDate} and informing the process participants via a message to their mailboxes, it is of course also possible as an alternative to propagate the new information directly to the mailboxes of the process participants.

In some exemplary embodiments, the process initiator can determine the parties involved in the process. This gives this process participant, as a “man-in-the-middle” (man in the middle), certain control options. In order to reduce this risk, the communication partners regularly participating in such process networks can exchange their public keys and mailbox addresses directly.

Some exemplary embodiments also create a control of the visibility at the “data record” and “attribute” level. The security in distributed ledger networks comes about through a large number of decentrally stored copies of the same data, so that an attacker would have to compromise a large part of the network or the copies in order to gain access to the network data manipulate. Public DLT networks are more likely to have a large number of copies. But even if transparency is a basic idea of such networks, you want to or can and if necessary you may not distribute your data unencrypted.

Using the procedure described in the present disclosure, the visibility of data can be controlled both at the data record level (that is to say for an individual data entry with generally several associated attributes) and at the attribute level. If a loT device sends a certain status message, for example, it may be due to technical or security requirements that not everyone is allowed to see this entire status message, but that it can only be deciphered for individual participants in the process network (control of visibility at data record level) or indeed the message itself is visible to all participants in the network, but individual attributes of such a message (e.g. the GPS position (position according to a global positioning system), or the like) may only be visible to selected participants (control of visibility on Attribute level). Mixed forms are of course also possible. Since the data is encrypted with the respective public key of each participant, only the respective participant can decrypt it (with his private key). The data producer / distributor can control, on the basis of roles, visibility groups or individual authorizations, using the appropriate public key, which attributes should be visible to which participant / role, since the data packets are distributed individually in encrypted form.

If there are large overlaps here, i.e. different process participants have the same visibility authorizations for the same data records or attributes, it makes sense to provide such authorizations with a common key pair in order to reduce the data redundancy on the exchange medium (e.g. the distributed ledger).

• Abschnitt 2.1: Der Bereitsteller des Datums (nachfolgend weiterhin „BD“ genannt) erzeugt für jede Rolle/Rechtsgruppe einen symmetrischen Schlüssel (SGX) und einen Gruppen-Briefkasten (LA-GX) und sendet den Schlüssel und die Adresse von LA-GX verschlüsselt mit dem öffentlichen Schlüssel des jeweiligen Teilnehmers an diesen Gruppenteilnehmer.
• Abschnitt 2.2: Der BD verschlüsselt Daten und/oder Attribute auf Basis von Rollen/Rechtegruppen. Die für mehrere Teilnehmer einsehbaren Daten verschlüsselt er mit dem Gruppenschlüssel SGX. Der Rest wird weiterhin teilnehmerbezogen mit dem öffentlichen Schlüssel des jeweiligen Teilnehmers verschlüsselt.
• Abschnitt 2.3: Der BD sendet die mit dem Gruppenschlüssel verschlüsselten Daten an den Gruppen-Briefkasten LA-GX und die mit den öffentlichen Schlüsseln der Teilnehmer verschlüsselten Daten an die Briefkästen der Teilnehmer.
• Abschnitt 2.4: Jeder Teilnehmer prüft nicht nur seinen persönlichen Briefkasten, sondern auch den der Gruppe auf neue Nachrichten. Die Nachrichten des Gruppen-Briefkastens entschlüsselt er mit dem erhaltenen Gruppenschlüssel, Nachrichten an seinen persönlichen Briefkasten weiterhin mit seinem privaten Schlüssel. Anschließend fügt er die über die unterschiedlichen Kanäle erhaltenen Daten gegebenenfalls wieder zusammen.

This is done, for example, as follows:

• Section 2.1: The provider of the date (hereinafter referred to as "BD") generates a symmetrical key (SGX) and a group mailbox (LA-GX) for each role / rights group and sends the key and the address of LA-GX in encrypted form the public key of the respective participant to this group participant.
• Section 2.2: The BD encrypts data and / or attributes on the basis of roles / groups of rights. He encrypts the data that can be viewed by several participants with the group key SGX. The remainder will continue to be encrypted with the respective participant's public key in relation to the participant.
• Section 2.3: The BD sends the data encrypted with the group key to the group mailbox LA-GX and the data encrypted with the public keys of the participants to the mailboxes of the participants.
• Section 2.4: Each participant not only checks their personal mailbox, but also that of the group for new messages. He decrypts the messages in the group mailbox with the received group key, messages to his personal mailbox with his private key. It then reassembles the data received via the different channels, if necessary.

Some exemplary embodiments of the present disclosure also create a reduction in vulnerability through random distribution. DLT networks are characterized, among other things, by the fact that there are numerous decentralized entry points into the network (so-called "nodes"). Each node (at least the so-called "full nodes") save the entire transaction history of the network and thus protect it from manipulation. If a participant would like to use such a network for data storage, he selects a node and transfers the data to be saved to him.

A node cannot change the data if it has not generated it itself (since it is usually signed with the private key of the sender and a manipulation would therefore quickly become apparent), but it could, however, make individual transactions transferred to it before inserting them into discard the ledger.

If the same node were selected as the entry point into the DLT network for all transactions emitted by a loT device, external attackers could possibly identify these nodes and disable them through an attack and thus the distribution of data from the affected loT device prevent. In order to minimize the risk of manipulation from such attacks, the transactions emitted are in some exemplary embodiments stored by the loT device at randomly selected nodes (ie at a random selection of one or more nodes of the plurality of nodes) for inclusion in the ledger, see above communication between the device and the network is unpredictable.

At least some exemplary embodiments can be used apart from distributed ledger networks. As already described above, the use of exemplary embodiments of the present disclosure is not necessarily coupled to distributed ledger networks. Even in an environment in which the data exchange takes place via a centralized architecture, the described procedure for a secure key exchange can ensure the authenticity of messages and their senders. Security can be reduced because the central component as “man in the middle” has more extensive options for intervention than in a decentralized network structure. Compared to central “trust authorities”, exemplary embodiments, in particular exemplary embodiments which are based on decentralized databases, offer significantly increased immunity to external and malicious influences. Exemplary embodiments can be used, for example, in V2X communication (communication between vehicles and other communication partners, the X standing for different types of communication partners). Embodiments can also be used in cases in which data is exchanged, for example, in process networks with partners / (sub-) suppliers (in the supply chain).

Another exemplary embodiment is a computer program for carrying out at least one of the methods described above when the computer program runs on a computer, a processor or a programmable hardware component. Another exemplary embodiment is also a digital storage medium that is machine-readable or computer-readable and that has electronically readable control signals that can interact with a programmable hardware component in such a way that one of the methods described above is carried out.

The features disclosed in the above description, the following claims and the attached figures can be important and implemented both individually and in any combination for the realization of an exemplary embodiment in its various configurations.

Although some aspects have been described in connection with a device, it goes without saying that these aspects also represent a description of the corresponding method, so that a block or a component of a device is also to be understood as a corresponding method step or as a feature of a method step. Analogously to this, aspects that have been described in connection with or as a method step also represent a description of a corresponding block or details or features of a corresponding device.

Depending on the specific implementation requirements, embodiments of the invention can be implemented in hardware or in software. The implementation can be carried out using a digital storage medium such as a floppy disk, a DVD, a Blu-Ray disk, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, a hard disk or other magnetic memory or optical memory are carried out on the electronically readable control signals are stored, which can interact or cooperate with a programmable hardware component in such a way that the respective method is carried out.

A programmable hardware component can be a processor, a computer processor (CPU = Central Processing Unit), a graphics processor (GPU = Graphics Processing Unit), a computer, a computer system, an application-specific integrated circuit (ASIC = Application-Specific Integrated Circuit), an integrated Circuit (IC = Integrated Circuit), a one-chip system (SOC = System on Chip), a programmable logic element or a field-programmable gate array with a microprocessor (FPGA = Field Programmable Gate Array).

The digital storage medium can therefore be machine-readable or computer-readable. Some exemplary embodiments thus include a data carrier which has electronically readable control signals which are able to interact with a programmable computer system or a programmable hardware component in such a way that one of the methods described herein is carried out. One embodiment is thus a data carrier (or a digital storage medium or a computer-readable medium) on which the program for performing one of the methods described herein is recorded.

In general, embodiments of the present invention can be implemented as a program, firmware, computer program or computer program product with a program code or as data, the program code or the data being effective to carry out one of the methods when the program is run on a processor or a programmable hardware component runs. The program code or the data can, for example, also be stored on a machine-readable carrier or data carrier. The program code or the data can be present as source code, machine code or bytecode, as well as other intermediate code, among other things.

A further exemplary embodiment is also a data stream, a signal sequence or a sequence of signals which represents the program for performing one of the methods described herein. The data stream, the signal sequence or the sequence of signals can, for example, be configured to be transferred via a data communication connection, for example via the Internet or another network. Embodiments are thus also data-representing signal sequences which are suitable for transmission over a network or a data communication connection, the data representing the program.

A program according to an exemplary embodiment can implement one of the methods while it is being carried out, for example, by reading out memory locations or writing data or several data into them, which may result in switching operations or other operations in transistor structures, in amplifier structures or in other electrical, optical, magnetic or components working according to another functional principle. Correspondingly, by reading out a memory location, data, values, sensor values or other information can be recorded, determined or measured by a program. A program can therefore record, determine or measure quantities, values, measured quantities and other information by reading out one or more memory locations, and by writing to one or more memory locations it can cause, initiate or carry out an action and control other devices, machines and components .

The above-described embodiments are merely illustrative of the principles of the present invention. It is to be understood that modifications and variations of the arrangements and details described herein will be apparent to other skilled persons. It is therefore intended that the invention be limited only by the scope of protection of the following patent claims and not by the specific details presented herein on the basis of the description and the explanation of the exemplary embodiments.

List of reference symbols

10

Device for a data source

12th

interface

14th

One or more processors

20th

Device for a device

22nd

interface

24

One or more processors

100

Data Source

110

Obtaining addresses from electronic mailboxes from devices

120

Obtaining cryptographic keys

130

Generate one or more messages

135

Sign the one or more messages

140

Providing the one or more messages

150

Providing a notification

200

One or more devices

210

Receive a message

220

Decrypting data

230

Check a signature of the message

Claims (15)

A computer-implemented method for the encrypted provision of data from a data source for a plurality of devices, the method comprising: Obtaining (110) one or more addresses from one or more electronic mailboxes of the plurality of devices; Obtaining (120) cryptographic keys of the plurality of devices; Generating (130) one or more messages for the plurality of devices based on the data, individually encrypted messages being generated for the devices of the plurality of devices based on the cryptographic keys; Providing (140) the one or more encrypted messages via at least one electronic mailbox based on the one or more addresses of the one or more electronic mailboxes of the plurality of devices. The procedure according to Claim 1 , the data being provided via the one or more messages in such a way that the accessibility of the data within the respective encrypted message for the plurality of devices is controlled via the encryption of the messages. The method according to one of the Claims 1 or 2 , wherein an individually encrypted message is generated for each device of the plurality of devices, the individually encrypted message include those data that should be accessible for the respective device. The method according to one of the Claims 1 or 2 , wherein a message is generated for the plurality of devices, the data within the message being encrypted individually for the plurality of devices. The method according to one of the Claims 1 until 4th wherein obtaining the cryptographic keys of the plurality of devices comprises retrieving a public key of the respective device from the electronic mailbox of the device. The method according to one of the Claims 1 until 5 , wherein the cryptographic keys comprise one or more device-specific public keys and / or one or more cryptographic keys for a group of devices. The method according to one of the Claims 1 until 6th wherein the one or more messages are provided via an electronic mailbox of the data source or via an electronic group mailbox, further comprising providing notifications about the provision of the one or more messages for the devices via the electronic mailboxes of the devices. The method according to one of the Claims 1 until 6th wherein the one or more messages are delivered through the electronic mailboxes of the devices. The method according to one of the Claims 1 until 8th , the electronic mailboxes being accessible via a distributed database. A computer-implemented method for the encrypted receipt of data from a data source by a device, the method comprising: Receiving (210) a message from a data source via an electronic mailbox accessible via a distributed database, the message including data individually encrypted for the device from the data source; Decrypting (220) the data based on a cryptographic key of the device. The procedure according to Claim 10 , wherein the data is encrypted based on a device-specific public key of the device, or wherein the data is encrypted based on a cryptographic key for a group. The method according to one of the Claims 10 or 11th wherein the message is received via an electronic mailbox of the data source or via a group mailbox, wherein the method further comprises receiving notification of the message via an electronic mailbox of the device, or wherein the message is received via an electronic mailbox of the device. Program with a program code for performing at least one of the methods according to one of the preceding claims, when the program code is executed on a computer, a processor, a control module or a programmable hardware component. A computer-implemented device (10) for the encrypted provision of data from a data source (100) for a plurality of devices (200), the device comprising: an interface (12) for communication with the plurality of devices; and one or more processors (14) designed to carry out the method according to one of the Claims 1 until 9 . A computer-implemented device (20) for receiving encrypted data from a data source (100) by a device (200), the device comprising: an interface (22) for communication with the data source; and one or more processors (24) designed to carry out the method according to one of the Claims 10 until 12th .

Images