Data management system and method

Abstract

Data management system 1 for managing a data packet with data (e.g. timestamp, velocity, location) related to an event (e.g. a car accident, crash or collision) 12, in which a first entity (e.g. a car or autonomous motor vehicle) 10 was present. The first entity comprising at least one data capture device 14 for capturing the data from the event in communication with at least one electronic computing device 16 configured to encrypt the data packet with a security key 3 generated from parameters from the event. A data module 18 wirelessly transmits the encrypted data packet to a host (e.g. insurance database, a cloud based network or blockchain) accessible by at least one third entity (e.g. another vehicle involved in the incident) 30, whereby the data packet may only be decrypted by the third entity having independently generated the same security key. Furthermore, the present invention relates to a method for managing data using the data management system, a computer program product, a non-transitory computer readable storage medium, as well as to an assistance system.

Description

FIELD OF THE INVENTION

[0001] The present invention relates to the field of automobiles. More specifically, the present invention relates to a data management system for managing at least one data packet from data related to an event according to claim 1. Furthermore, the present invention relates to a corresponding method for managing data using the data management system, to a computer program product, to a corresponding non-transitory computer-readable storage medium, as well as to a corresponding assistance system for an at least in part automated vehicle. BACKGROUND INFORMATION

[0002] Document CN 114070848 A discloses a search method and search system for neighboring vehicles in traffic accidents. This demonstrates the challenge of searching for key vehicles in events, particularly traffic accidents. A server contains the precise position of many vehicles, which is privacy-sensitive and must be protected. However, the authentication of the search is not disclosed in this patent.

[0003] Document GB 2447674 A discloses the use of environmental data for generating a graphical key. This patent covers key generation, especially mentioning other sensors like microphones, but it does not disclose its application in traffic accidents or its use in an encrypted event search application. Furthermore, there is no mention of a blockchain in the system's architecture.

[0004] Document CN 109067835 A discloses a data processing method for accident data based on blockchain data. The approach to data collection is different than in the present invention. In this patent, the central server sends requests at the time of the accident.

[0005] Document CN 108446992 A discloses a network-connected precise accident processing method for automobiles based on blockchain technology. One aspect of this patent addresses privacy concerns and data security. The patent uses encryption to expose private information only to a previously defined user group, especially automobile manufacturers.

[0006] Finally, CN 109993847 B discloses a blockchain-based architecture for traffic accident information and working methods.

[0007] Therefore, when capturing events, especially when capturing accident situations, it is necessary to collect information about this event, meaning that all information about the accident position or event must be captured for further event processing. To enable this, it is proposed to query various vehicles in the immediate vicinity or to apply them to collect additional information about the accident position or event. For example, the respective vehicles passing by the event or accident position can collect all information through their respective sensor devices, especially cameras or optical sensing devices, or other sensor modules, which can be transmitted to a central cloud or beyond. This allows third entities to access this data, enabling evaluation and exchange of information. Subsequently, various tasks can be initiated by this information, for example, both a first-aid call or other actions can be initiated. Furthermore, information for later further processing methods can also be introduced, such as information storage and transmission for insurance and / or legally relevant instances. However, it is particularly necessary to provide data protection and anonymity protection, making authentication measures and methods to protect the general data of respective vehicles crucial. SUMMARY OF THE INVENTION

[0008] The object of the invention is to enhance data security and data privacy for individual entities within a data management system for data related to events, in which the entities were part of.

[0009] This object is achieved by a data management system having the features of claim 1 and by a method, a computer program product, a non-transitory computer-readable storage medium and an assistance sytem according to the invention. Advantageous embodiments and further developments can be found in the dependent claims.

[0010] An aspect of the invention relates to a data management system designed for managing data packets derived from events or past events. In these events, at least one first entity was present. This first entity includes at least one data capture device for acquiring data from an event. Additionally, the first entity comprises electronic computing device(s) in communication with the data capture devices. These electronic computing devices are configured to encrypt the data packets using security keys generated from event parameters. The data management system also features a data module for wirelessly transmitting the encrypted data packets to a host, which acts as a second entity. The host is responsible for providing the data packets to third entities. Importantly, only the third entities possessing the corresponding security keys can decrypt the data packets.

[0011] Therefore, to achieve this object of the invention, a highly secure encryption method has been implemented, enabling the involved entities to securely capture, transmit, and store data. The encryption is based on specific event parameters that can only be captured by those who were present at the event. In particular, the security key, which may also be referred to as a terroir-key (TERROIR), an encrypted key, ID, network key, or identification file, is created for identity authentication and can be transmitted via a blockchain. The security key is referred to as a 'terroir key' due to its reliance on positionbased parameters. It is important to note that vehicles never report or transmit the security key itself.

[0012] To address the objectives of the invention and enhance data security and system security, it is specified that an encrypted, position-dependent security key or 'terroir key' can be generated for identity authentication, depending on data obtained from the same event observed and / or documented by the data capture device.

[0013] The data capture devices can take various forms, such as vehicle cameras, vehicle sensor devices, and others. These devices are responsible for capturing data for the data packets, which can include visual information, sensor readings, or other relevant data associated with the event witnessed. The choice of data capture device may depend on the specific requirements of the data management system and the nature of the events being recorded. For example, in the context of a traffic accident event, cameras may be used to capture images and videos, while sensor devices could record vehicle telemetry data and audio devices could record sounds in the surrounding.

[0014] The captured data is then processed and encrypted by the electronic computing device, which is coupled to the data capture devices. These electronic computing device generates the security key or terroir-key from parameters extracted from the event. The encryption process ensures the data's confidentiality and security during transmission and storage.

[0015] Subsequently, the encrypted data packets are wirelessly transmitted to a host, serving as the second entity. The host acts as a central repository for the encrypted data packets, making them accessible to third entities when needed. Importantly, only those third entities possessing the corresponding security keys can decrypt and access the data within the packets, ensuring data security and privacy.

[0016] The newly generated position-dependent security key is therefore generated based on the event itself. This ensures that the entity, device, vehicle, or key device generating the security key was indeed in the proximity of the event. For instance, if the distance from the event is too great, the positioning module may provide inaccurate information, which is then stored in the security key, indicating that the key vehicle was not in the immediate vicinity.

[0017] In summary, if an entity was not present at the event, it is not possible for that entity to generate a security key, thus preventing access to the data. This ensures that access to the data is restricted to those who were actually present at the event and, therefore, authorized to decrypt and access the data. This contributes to the security and data privacy within the data management system.

[0018] In an advantageous embodiment of the invention, it is provided that the parameters for generating the security key can be captured by all entities that witnessed the event.

[0019] In another advantageous embodiment of the invention, it is provided that the parameters for generating the security key are defined by at least one information about a position relative to the event and / or a timestamp and / or other vehicle parameters. More paramters may include, for example the number of vehicles involved in the incident, GPS coordinates of the position, speed of the leading vehicle involved in the incident, distance between the leading vehicle and the nearest witness vehicle or other vehicle, sounds generated during the incident, current environmental temperatures, distance to the nearest visible speed limit sign or other POI, time of the incident, etc.

[0020] In another advantageous embodiment of the invention, it is provided that access rights to the encrypted data of the data packet are managed by the host as the second entity, based on the nature of the event.

[0021] In another advantageous embodiment of the invention, it is provided that the data packet includes at least contact details of the entity capturing the data of the corresponding event.

[0022] In a further advantageous embodiment of the invention, it is provided that initially only the security key ma be transmittable, and subsequently, depending on verification, a data packet is transmittable. It is intended to determine the key initially to keep data streaming low, with data packet transmission only occurring upon key verification. This means that data packet transmission may only carried out once the key has been approved as such, and identity authentication has been performed, especially to save data exchange.

[0023] In summary, each position-dependent security key or terroir key has attributes, including, for example, a timestamp, a timestamp algorithm, a duration, respective sensor data, a combination algorithm, a sensor pass filter, an entropy measurement filter, and possibly other information. In alternative embodiments, different quantities and combinations of the aforementioned aspects can be applied. The timestamp algorithm is an algorithm used by all entities, participants or witnesses to synchronize the timestamp. An example of this is, for instance, the highest peak value in the audio recording within 30 seconds after the observed event. The sensors used in the timestamp algorithm are independent of the observation of the event. For example, even in the case of an accident detected via radar or visual processing systems or other optical detection devices, the audio sensor defined in the timestamp algorithm is used to create the timestamp. To generate the position-dependent security key or terroir key, sensor information is collected, especially over the duration of the incident. This data can be processed by sensor pass filters. These filters can modify data, for example, to increase the likelihood of matching between vehicles or to discard data and increase the entropy in the final key. An example of such a filter is a peak detection algorithm combined with duration conversion. After the peak detection algorithm has created a series of peak or non-peak events, another or additional filter can be applied to generate a one-dimensional series of peak or non-peak durations, which can be applied as input for the combination algorithm.

[0024] The data between the sensors is combined in particular according to the combination algorithm of the security key. A simple version could specify an order of sensors or sensor information and the concatenation thereof. Finally, the positiondependent security key or terroir key is compared with an entropy measurement filter, which determines whether the event has enough randomness to be considered a secure security key or position-dependent security key.

[0025] In summary, the position-dependent security key or terroir key or positiondependent security key was generated by parameters, such as timestamp, sensor information, filter and more. A timestamp algorithm synchronizes timestamps independently of sensors. Sensor information is collected during an event and processed by filters, such as peak detection and duration conversion. This data is combined according to a combination algorithm. Finally, an entropy measurement filter evaluates the randomness of the event to confirm the security of the key. This allows securely encrypted data to be uploaded and used in certain events.

[0026] In other words, the invention can be described as follows.

[0027] For the use of the event dependent security key or terroir key, additional sensor data, such as videos and other telematics information are encrypted with this key and recorded in a database or blockchain for insurance purposes. Only the devices present during the incident have access to this key, allowing them to access additional data from other involved vehicles. This reduces privacy concerns and avoids the creation of a centralized surveillance database. A dashcam product could utilize this key and the database to automatically provide other dashcam recordings in the event of an accident without receiving or sharing continuous video feeds from users. Further blockchain applications expand decentralized participant identification, such as participation in an immutable "insurance data consortium" or automated enforcement of liability claims.

[0028] Digital Witness: Vehicles or other entities not involved in an incident can upload encrypted data about the event to a distributed blockchain, making the existence of this data known to all subscribers and therefore entities whithin the data management system. The problem arises when, for example, an unmanned Level 4 vehicle is involved in an accident with a human driver, complicating insurance settlement as both the vehicle's sensors and the human driver may be considered unreliable. The solution is for other vehicles nearby at the time of the accident to "report" their sensor data such as speed, position, and video feeds. The challenge is that this data can potentially be private, especially the video feeds, and should not be shared with entities (individuals, companies) that were not present. The insight here is that it is acceptable to share this data with other "witnesses" who were actually present.

[0029] Insurance Use Case: Vehicles acting as witnesses and detecting potential issues contribute their data to the data management system, with timestamps and a position relative to the event or geographic coordinates (e.g., latitude and / or longitude) publicly visible. These sensor data are encrypted with the security key of their respective organizations, such as insurance companies. In the event of a claim, the autonomous vehicle can determine which entities were witnesses. A decryption request can be made upon agreement from the entities, the data management system, or the organization. Therefore, the requesting entity possesses the security key, but access to the data packets is only granted after approval. Further advantages of the data management system or blockchain lie in the distributed storage of data packets and decentralized notification of their existence.

[0030] Parameters, attributes and refinements: parameters are "common facts" about the incident that, when refined and ordered, represent the common secret for security key generation. Paramteres may include, for example: - Number of cars involved in the incident - GPS coordinates of the position - Speed of the leading car involved in the incident - Distance between the leading car and the nearest "witness" vehicle - Sounds generated during the incident - Current ambient temperature - Distance to the nearest visible speed limit sign or other POI - Time of the incident

[0031] Parameters have a definition, units, and an attribute type. The definition describes the measurement and limits of the paramter. Many are time-related and defined in terms of time before / after the event. For example, a parameter for audio recordings might be defined as the sounds 5 seconds before the detected incident. These can be either measured or signal attributes.

[0032] Measured parameters: These are parameters that already have a single numeric value, such as counts of events, speed, temperature, or distances. These can be refined by normalizing units, with metric units preferred for greater accuracy. For example, normalizing the speed from 42.355 mph to 42 or to a lower precision in a base other than 10.

[0033] Signal parameters: These are parameters that are a series of data, such as an audio recording, time-based position data, etc.

[0034] Refinements are adjustments, such as normalization or other modifications, to bring the data into a type and range compatible with other vehicles. One example is precision. The speed of the leading vehicle in the accident to the fourth decimal place (42.3552 mph) will never precisely match the measurement of another vehicle. There are different types of parameters, each of which may have its own refinement method. For example, signal parameters can be refined by applying a filter such as a peak detection algorithm.

[0035] Regarding the question of whether vehicles report the security key they calculated and how it is determined which vehicles observed the same event, it is important to note that vehicles never report or transmit the security key itself. Instead, they use the security key they generated to encrypt the data. This is done using symmetric encryption, allowing other vehicles that generate the same key to decrypt the encrypted data. The prerequisite for this is that these vehicles must have observed the same environmental data to generate the same key.

[0036] The same principle applies when distinguishing between vehicles involved in an incident compared to vehicles that observed the event or incident.

[0037] Regarding how this system could be implemented on a public blockchain: Each vehicle would create a new block once it detects an event. This block would contain, for example, some plaintext data such as latitude, longitude, and timestamp, as well as the vehicle's sensor data encrypted with the terroir key. This would allow other vehicles to use the plaintext values to identify relevant blocks through searching and then use the terroir key to decrypt the sensor data. If the sensor data is too large to fit on the blockchain, the vehicle could store the data in another cloud-based, publicly accessible solution, such as AWS S3 or any hosting service. In this case, a new key would be generated and encrypted with the terroir key.

[0038] Furthermore, it is possible to implement this system on other devices such as mobile phones, recording devices on road infrastructure, building surveillance cameras, and similar devices as the entities.

[0039] Further advantages, features, and details of the invention derive from the following description of preferred embodiments as well as from the drawing. The features and feature combinations previously mentioned in the description as well as the features and feature combinations mentioned in the following description of the figure and / or shown in the figure alone can be employed not only in the respectively indicated combination but also in any other combination or taken alone without leaving the scope of the invention. BRIEF DESCRIPTION OF THE DRAWING

[0040] The novel features and characteristic of the disclosure are set forth in the appended claims. The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and / or methods in accordance with embodiments of the present subject matter are now described below, by way of example only, and with reference to the accompanying figures.

[0041] The drawing shows in:

[0042] Fig. 1 a schematic visual diagram to visualize a data management system.

[0043] In the figure the same elements or elements having the same function are indicated by the same reference signs. DETAILED DESCRIPTION

[0044] In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0045] While the disclosure is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawing and will be described in detail below. It should be understood, however, that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.

[0046] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion so that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus preceded by “comprises” or “comprise” does not or do not, without more constraints, preclude the existence of other elements or additional elements in the system or method.

[0047] In the following detailed description of the embodiment of the disclosure, reference is made to the accompanying drawing that forms part hereof, and in which is shown by way of illustration a specific embodiment in which the disclosure may be practiced. This embodiment is described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

[0048] Fig. 1 illustrates a schematic diagram to visualize an exemplary data management system 1 for managing at least one data packet from data related to an event 12 in an event environment 2. In Fig. 1, the event 12 is depicted as a car accident involving two different entities 10, 30 represented as vehicles, whereby a first vehicle 10a represents the first entity 10, that was present and that will need support from the data management system 1.

[0049] Additionally, the third entity 30 is represented as another vehicle involved in the event 12, and a fourth entity 40 is also depicted as a vehicle present at the scene of the event 12 and, therefore, acting as a witness.

[0050] Furthermore, a fifth entity 50 and a sixth entity 60 are shown as vehicles that were also in the vicinity of the event 12.

[0051] In this visualization of the data manangement system 1, the event 12 is depicted by a lightning symbol, which signifies the occurred accident between the first entity 10 and the third entity 30. Additionally, the area in close proximity is delineated by a dashed line, which, to be more precise, represents a position 12a relative to the event 12, during a specified time with a timestamp 12b.

[0052] Additionally all shown entities 10, 30, 40, 50, 60 on the road include a respective data module 18 for wirelessly transmitting the encrypted data packet to a host, which is represented as the second entity 20 and depicted by a cloud symbol. Specifically, the second entity 20 is the host, such as a cloud or a server with a database, for example, of an insurance company or an automobile manufacturer, responsible for capturing respective data packets in such events 12. It is intended that the second entity 20 provides the respective data packet of the respective entities 10, 30, 40, 50, 60 to any entity being involved in the event, for example, the third entity 30.

[0053] The data packet may only be decrypted by the entities 10, 30, 40 that possess the corresponding security key 3. To generate this security key 3, any entity 10, 30, 40, 50, 60 requires parameters from the event 12. The parameters for generating the security key 3 may be captured by all entities 10, 30, 40 that witnessed the event 12. These parameters are defined by at least one piece of information about the position 12a relative to the event 12 and / or the timestamp 12b and / or predefined vehicle parameters 12c, such as a velocity v of the vehicle driving by.

[0054] Since these entities 10, 30, 40 were within the vicinity of the event 12, they possess the necessary security keys 3 to decrypt the data packets provided by the second entity 20. The other entities 50, 60, which were present outside the event 12, do not possess the respective security keys 3, as the required event parameters were not captured.

[0055] In other words, this Fig. 1 illustrates an event 12 in which, in the case of an accident, a first vehicle 10a and a second vehicle 10b are involved in a collision. Data related to this collision was fully captured by the first vehicle 10a, the second vehicle 10b, and the third vehicle 10c within the dashed circle and transmitted to a host 20 on a cloud. The host 20 receives the data packets of each vehicle 10a, 10b involved or each vehicle 10c that witnessed the event 12 and may make it available to everyone within the data management system 1 upon request, but these encrypted data packets may only be decrypted by the respective vehicles 10a, 10b, 10c that were present at the event 12 and therefore at the accident scene. Other vehicles 10d, 10e that drove past the event 12 or accident site before or after, for example, do not possess the parameters needed to create the security key 3, as they may have passed by too late or too early. Accordingly, they do not have the security keys 3 to decrypt the data packets.

[0056] Accordingly, it is envisaged that only entities 10, 30, 40 possessing the self generated security key 3 will have access to the data within the data packets. This establishes a data privacy mechanism regulated by one's presence or participation in the event 12 itself. This data protection mechanism ensures that only those entities 10, 30, 40 that were actually involved in or present at event 12, and therefore possess the necessary security keys 3, may access the data within the data packets.

[0057] This guarantees the confidentiality and security of the data, preventing unauthorized entities 50, 60, from accessing sensitive information. Therefore, this data management system 1 provides effective control over data access, ensuring data privacy and security in situations such as accidents or other events 12 where data is captured. Entities 10, 30, 40 in possession of the required security key 3 may decrypt and utilize the data, while others who were not involved in the event 12 do not have access to this data.

[0058] Therefore, the data management system 1 offers a variety of possibilities for data management. For example, access rights may be provided or managed, whereby the host or the second entity 20 grants more access rights to the accident participants and thus the participants in the event 12 than to the witnesses. Witnesses, for instance, may only have contact details or contact information provided to consult or inquire about legal matters. In other words, the access rights to the encrypted data of the data packet are managed by the host, based on the nature of the event 12. This means that the level of access granted to different entities is determined by the specific characteristics and circumstances of the event 12 itself.

[0059] Furthermore, the management system 1 may also provide data for a limited time only. Alternatively, a payment system for witnesses to provide data could be considered, allowing assistance to accident participants and event 12 participants by paying a predetermined fee.

[0060] These flexible approaches allow data management to be tailored to specific requirements and needs. This ensures both data privacy and fair use of information while also providing the option to make valuable data accessible for legal or other purposes.

[0061] Finally, it is envisaged to apply a method for managing data using the data management system 1, in which at least one data packet of data related to an event 12 or a past event 12 is managed. In this method, at least the first entity 10 was present, and the data from the data packet is captured by at least one data capture device 14 of the first entity 10. Subsequently, it is sent to the electronic computing device 16 of the first entity 10, which is coupled to the capture device 14. Within this process, the at least one data packet is encrypted with a security key 3 generated from predefined parameters of the event 12. The encrypted data packet is then transmitted to a host, acting as the second entity 20, through a data module 18 of the first entity 10. Through this transmission, the data packet is made available to a third entity 30 that possesses the security key 3, allowing for the decryption of the data packet.

[0062] Furthermore, it is envisaged that each vehicle 10a, 10b, 10c, 10d, 10e comprises an assistance system designed for at least partially automated motor vehicles, such as the first entity 10. This assistance system includes at least one data capture device 14, one electronic computing device 16 coupled to the capture device 14, and a data module 18 connected to the electronic computing device 16 and a vehicle-mounted terminal and / or one module. The assistance system is configured to perform functions like encrypting at least one data packet of data related to an event 12 witnessed by the automated motor vehicle 10a using a security key 3 generated based on parameters of the event 12, wirelessly transmitting the encrypted data packet to a host acting as the second entity 20, gathering data from encrypted data packets received from the host using the data module 18, and decrypting the encrypted data packets using the security key 3. This configuration ensures that each vehicles 10a, 10b, 10c, 10d, 10e equipped with the assistance system may actively participate in the data management process of the data management system 1, providing valuable information related to events 12 they where part of or the witness while maintaining data security through encryption and decryption mechanisms.

[0063] In summary, the discussed data management system 1 of the invention facilitates the secure and standardized handling of data from events 12, involving various entities, including vehicles, through encryption with a security key 3 or a “terroir key”, controlled access, and tailored data provision, ultimately enhancing data privacy and security while enabling valuable information sharing. Signs data management system event environment security key first entitiy vehicle vehicle vehicle vehicle vehicle event position timestamp vehicle parameters capture device electronic computing device data module second entity (host) third enitity fourth entity fifth entity sixth entity velocity

Claims

1. Data management system (1) for managing at least one data packet from data related to an event (12), in which at least one first entity (10) was present, the first entitiy (10) comprising at least one data capture device (14) for capturing the data from the event (12) and comprising at least one electronic computing device (16) in communication with the capture device (14), which is configured to encrypt the data packet with a security key (3) generated from parameters from the event (12), and comprising a data module (18) for wirelessly transmitting the encrypted data packet to a host ,as a second entity (20), accessible by at least one third entity (30), whereby the data packet may only be decrypted by the third entity (30) having independently generated the same security key (3).

2. Data management system (1) according to claim 1, characterized in thatthe parameters for generating the security key (3) may be captured by all entities (10, 30) that witnessed the event (12).

3. Data management system (1) according to claim 1 or 2, characterized in thatthe parameters for generating the security key (3) are defined by at least one information about a position (12a) relative to the event (12) and / or a timestamp (12b) and / or a predefined vehicle parameters (12c).

4. Data management system (1) according to any of the preceding claims, characterized in thataccess rights to the encrypted data of the data packet are managed by the host.

5. Data management system (1) according to any of the preceding claims, characterized in thatthe data packet includes at least contact details of the entity (10, 20) capturing the data of the corresponding data packet.

6. Data management system (1) according to any of the preceding claims, characterized in thatthe at least one third entity (30) may encrypt at least one data packet of data related to an event (12) captured by at least one of its own data capture device, in which the data packet is encrypted with a security key generated from predefined parameters of the event (12), in wich the encrypted data packet is then transmitted to the host.

7. A method for managing data using a data management system (1), in which at least one data packet of data related to an event (12) is managed, wherein at least one first entity (10) was present, in which the data from the event (12) is captured by at least one data capture device (14) of the first entity (10) and sent to an electronic computing device (16) of the first entity (10) coupled to the capture device (14), in which the data packet is encrypted with a security key (3) generated from predefined parameters of the event (12), in wich the encrypted data packet is then transmitted to a host, as a second entity (20), accessible by at least one third entity (30), whereby the data packet may only be decrypted by the third entity (30) having independently generated the same security key (3).

8. A computer program product comprising program code means for performing a method according to claim 7.

9. A non-transitory computer-readable storage medium comprising at least the computer program product according to claim 8.

10. An assistance system for an at least in part automated motor vehicle (10a) as the first entity (10), comprising at least one data capture device (14), one electronic computing device (16) coupled to the capture device (14), and a data module (18) coupled to the electronic computing device (16) and a vehicle-mounted terminal and / or one module, wherein the assistance system is configured for encrypting at least one data packet of data of an event (12) witnessed by the automated motor vehicle (10a) with a security key (3) generated by parameters of the event (12) andfor wirelessly transmitting the encrypted data packet to a host, as a second entity (20), accessible by at least one third entity (30), whereby the data packet may only be decrypted by the third entity (30) having independently generated the same security key (3).19

Images