Method for data acquisition using a plurality of mobile data determination devices
The method enhances data acquisition by allowing mobile data determination devices to select and perform data collection activities tailored to their specific capabilities and context, addressing inefficiencies in existing systems.
Patent Information
- Application Number
- PCT/EP2024/068751
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-09-27
- Filing Date
- 2024-07-03
- Publication Date
- 2025-04-03
AI Technical Summary
Existing data acquisition systems with mobile data determination devices are limited in their ability to account for individual device properties, skills, and dynamic conditions, such as geographical location and data protection settings, leading to inefficient data collection.
A method for data acquisition that involves a data acquisition unit communicating with a large number of mobile data determination devices, allowing for the selection and provisioning of data collection activities based on device-specific criteria, including data collection capacity and properties, using a pull principle rather than a push process.
This approach enables efficient and targeted data collection by ensuring that each mobile data determination device performs data collection activities that are suitable to its capabilities and context, thereby improving the quality and relevance of collected data.
Smart Images

Figure EP2024068751_03042025_PF_FP_ABST
Abstract
Description
[0001] Method for data acquisition using a plurality of mobile data acquisition devices
[0002] Description
[0003] The present invention relates to a method for data acquisition using a plurality of mobile data acquisition devices.
[0004] Data acquisition systems with a data acquisition device are known. Such a data acquisition device can, for example, be implemented centrally in a backend server. The backend server can, in particular, be configured to send, receive, and permanently store data.
[0005] The data acquisition device can comprise a computing unit of the data acquisition device as well as a data and program memory and at least one communication interface of the data acquisition device, which is designed to communicate with a data determination device.
[0006] The data acquisition device is embodied in a device. The device comprises, for example, a vehicle and / or a mobile phone and / or a navigation device. The device comprises, for example, several different sensors. Such sensors include, for example, an inertial sensor and / or a position sensor that determines a position using a global navigation satellite system, for example, the Global Positioning System (GPS). Such sensors alternatively or additionally include, for example, a temperature sensor and / or a speed sensor.
[0007] The data acquisition device and the data determination device communicate at least indirectly, for example wirelessly, for example by means of mobile radio, for example according to the Global System for Mobile Communications (GSM) standard, whereby GSM is a mobile radio standard for fully digital mobile radio networks, which can be used for example for packet-switched data transmission.
[0008] The data transfer between the data acquisition device and the data acquisition device is typically initiated by the server using the so-called push method. The disadvantage of this is that properties such as the software versions currently running on the data acquisition device, capabilities such as the sensors installed in the data acquisition device, or restrictions such as data protection restrictions of the individual data acquisition device can only be taken into account to a limited extent. This also applies to dynamic properties of the data acquisition device, such as the geographical location or current data protection settings.
[0009] The object of the invention is therefore to improve the collection of data to be obtained from a large number of mobile data acquisition devices.
[0010] The object of the invention is achieved by a method for data acquisition with a data acquisition unit that can communicate with a plurality of mobile and mutually independent data acquisition devices, in particular designed as a vehicle or connectable to a vehicle, each of which comprises at least one control unit that is configurable or configured to carry out at least one selection from a plurality of different data acquisition activities, wherein the method comprises the following steps: a) receiving a request from a data acquisition device by the data acquisition unit, wherein the request comprises information about a data collection capacity of the data acquisition device and information about one or more properties of the data acquisition device and wherein the request comprises a request for instructions for carrying out data collection activities;b) Determining the suitability of data discovery campaigns from the plurality of data discovery campaigns for execution on the requesting data discovery device, comprising: b1) Determining, by the data acquisition unit, those data discovery campaigns from the plurality of data discovery campaigns that meet one or more predetermined criteria for the data discovery campaigns when executed on the requesting data discovery device; and b2) Determining, by the data acquisition unit, data discovery activities of the data discovery campaigns that can be executed on the requesting data discovery device depending on the data collection capacity of the data discovery device; c) Creating a provisioning list by the data acquisition unit that includes the executable data discovery activities of the data discovery campaigns that meet the predetermined criteria;d) transmitting the provisioning list and instructions for carrying out the data collection activities defined in the provisioning list from the data collection unit to the requesting data collection device;
[0011] The method according to the invention enables over-the-air provisioning of data acquisition or data collection functionalities in mobile data acquisition devices, such as motor vehicles. Provisioning is requested from the respective data acquisition device according to the pull principle, specifically at a suitable time, for example, when a motor vehicle is started.
[0012] The data acquisition unit, for example a backend server, comprises an algorithm that responds to the request of the individual data acquisition devices with a provisioning list and instructions for the provisioning list depending on currently pending data acquisition campaigns and the data collection capability provided by the motor vehicle.
[0013] Data collection capacity refers to the ability of a data acquisition device to detect and collect data. Data collection capacity is determined by the type, number, location, and quality of the sensors connected to the data acquisition device.
[0014] Properties of the data acquisition device are understood to be those properties of the data acquisition device that characterize the data acquisition device at least substantially independently of its data collection capacity. Such properties can include vehicle properties such as the chassis number, the vehicle's home market or country of origin, the vehicle type (model, design, drive type, transmission type, right-hand / left-hand drive, etc.), the vehicle's special equipment, the installed control units and associated hardware and software versions, and data protection menu settings.
[0015] A data acquisition device is understood, in particular, to be a device that can both acquire and collect data, for example, by performing a data collection activity. In particular, the data acquisition device can record, forward, and optionally store collected data for a certain period of time. Alternatively or additionally, the data acquisition device can further process collected data. For example, specific values can be calculated or estimated from data acquired for various measured variables, and the values resulting from these calculations or estimates can be transmitted to the data acquisition unit.
[0016] Data acquisition activities that can be executed on the data acquisition device are those data acquisition activities that can be executed due to the technical requirements offered by the data acquisition device, i.e. those activities that can be executed or carried out with the existing sensors and, if applicable, the existing control unit, and from which it can be expected that the collected data can achieve the purpose of the data collection and collect the required amount of data with the required quality.
[0017] Executing a selection from a plurality of different data acquisition activities by a control unit can be carried out in particular by implementing a software program on the control unit, wherein the software program comprises instructions for activating and / or controlling and / or establishing a connection with one or more sensors of the existing sensor system.
[0018] An advantageous embodiment of the invention includes that the request from the data determination device to the data acquisition unit is triggered by an event, in particular wherein the event comprises starting and / or driving off of the data determination device designed as a vehicle and / or of a vehicle coupled to the data determination device, and / or wherein in particular the event comprises the detection of a change in a road type on which the data determination device is located, in particular by the data determination device, and / or in particular wherein the event comprises the data determination device leaving and / or entering a specific limited geographical area, in particular detected by the data determination device, and / or in particular wherein the event comprises a change in the data protection settings applicable to the respective data determination device.
[0019] In this way, the request is triggered on the individual data collection device or the individual vehicle. Requests from multiple data collection devices therefore reach the data collection unit at different times, or at least randomly at the same time. This makes it possible to deliver an up-to-date provisioning list to the individual data collection device or the requesting vehicle, even if active data collection campaigns stored on the data collection unit change or if new data collection campaigns are added to the data collection unit. For example, it is also possible to update execution programs for certain data collection activities as needed during the execution of a data collection campaign.
[0020] Furthermore, it can be advantageous if certain changes in dynamically changing characteristics of the individual vehicle or the individual data collection device are used to initiate the request, or in other words as a trigger. In addition to various other triggers, a change in the data protection provisions currently applicable to the respective data collection device can be used individually or in combination. Alternatively or additionally, the assumption or reaching of a certain position of the individual vehicle or the individual data collection device, such as crossing a geographical boundary such as a city border or entering a certain landscape such as a forest area and / or mountainous area with a gradient of the respective road, or the onset of dawn or dusk can be used as a trigger.
[0021] Furthermore, an advantageous embodiment may include the request from the data acquisition device to the data acquisition unit being triggered in a time-controlled manner, in particular at regular intervals and / or at specific times or times of day. In particular, it may be advantageous to use specific times of day, for example, a time during the day and a time at night, to trigger the request. This makes it possible to influence the distribution of data collected in a data collection activity, for example, to adjust the amount or number of data collected during the day to the amount or number of data collected at night. This allows statements to be made based on the collected data, taking time-of-day factors into account.
[0022] For example, such a request can be triggered at regular intervals depending on a specific event, for example regularly after the requesting vehicle is started or independently of an event at specific time intervals.
[0023] Furthermore, it may be advantageous if the request from the data acquisition device to the data acquisition unit includes information about data collection activities already active on the data acquisition device, and / or that the instructions for carrying out the determined, executable data acquisition activities include instructions as to whether and which data collection activities active on the data acquisition device should be stopped or removed or prioritized or deprioritized or continued unchanged and / or the instructions for carrying out the determined, executable data acquisition activities include instructions as to which data collection activities should be re-executed, in particular wherein a control program is installed to carry out the new data collection activities to be carried out, which control program can control or controls the new data collection activities to be carried out.
[0024] Through these measures, individual data collection devices can be provisioned in such a way that they carry out the data collection activities to be carried out very efficiently.
[0025] In a further advantageous embodiment, the data acquisition unit receives a plurality of requests from different data acquisition devices, in particular data acquisition devices having at least partially individually different data acquisition capacities, wherein the data acquisition unit evaluates the information contained in the plurality of requests regarding the, in particular individually different, data acquisition capacities of the data acquisition devices and determines a, in particular spatial and / or temporal, distribution of executable data acquisition activities.
[0026] In this way, it is possible to carry out data collection campaigns very efficiently using a large number or a fleet of data collection devices, in particular vehicles or motor vehicles. The data collection devices included in the large number or fleet can be designed very differently, both with regard to the technical vehicle characteristics of the vehicles or vehicle types coupled to the data collection devices and with regard to the individual data collection capabilities of the individual data collection devices or the vehicles coupled or connected to them. From the large number of individually different data collection devices, specific data collection devices can be specifically selected with which one or more specific data collection campaigns can be carried out optimally, so that the data collected is as meaningful as possible.
[0027] At the same time, it is possible to provision precisely tailored data collection devices. In other words, each individual data collection device is only tasked with those data collection activities that it is capable of performing based on its individual sensor technology, and for which the data to be collected can be expected to meet the technical purpose of the data collection campaign and the predefined quality criteria. This increases the usefulness of the data collection campaigns and increases the efficiency of implementing the multitude of data collection campaigns.
[0028] In a further advantageous embodiment, it is provided that the data acquisition unit receives a plurality of requests from different data acquisition devices, wherein the requests comprise information on one or more properties, in particular a chassis number and / or a place of first registration of the vehicle and / or the type of control unit and / or specifics of the vehicle design, of the data acquisition device, wherein the data acquisition unit evaluates the information contained in the plurality of requests on the properties of the data acquisition device and determines a distribution, in particular spatial and / or temporal, of the properties of the plurality of data acquisition devices.
[0029] This ensures that data collection activities provisioned for an individual data collection device can be selected based on the vehicle's characteristics. For example, it can ensure that only those data collection activities are provisioned that can also be executed on the control unit of the data collection device.
[0030] Furthermore, it is advantageous if the data collected on the requesting data collection device when carrying out the data collection activities defined in the provisioning list are transmitted to the data collection unit, in particular in real time or at regular intervals or after completion of the defined data collection activities, in particular wherein the data of the plurality of requesting data collection devices which carry out the data collection activities of the same data collection campaign are combined in the data collection unit.
[0031] This allows the data collected on various data collection devices assigned to a specific data collection campaign to be centrally consolidated on the data collection unit, where it can be centrally processed and evaluated. In particular, the data collection unit can check whether the data collection campaign has been fully executed and, if necessary, provision additional requesting data collection devices with corresponding data collection activities.
[0032] Furthermore, it may be advantageous if the determination of data acquisition activities that can be executed on the requesting data acquisition device by the data acquisition unit comprises at least the following steps: - Filtering of stored data acquisition campaigns marked as active by the data acquisition unit, wherein filtering is carried out according to one or more of the following criteria:
[0033] - according to the degree of coverage; and / or
[0034] - according to current geographical position; and / or
[0035] - according to the characteristics of the data acquisition device, in particular according to the chassis number and / or the place of first registration of the vehicle and / or the type of control unit and / or specifics of the vehicle design and / or the characteristics of the sensors available to the data acquisition device and / or belonging to a defined fleet of vehicles; and / or
[0036] - according to component restrictions; and / or
[0037] - according to privacy settings;
[0038] - Generating a list of the data discovery campaigns resulting from the filtering step with the associated data collection activities; and / or
[0039] - Generation of the provisioning list for the requesting data collection device, comprising instructions for the installation and / or retention and / or removal of data collection activities currently running on the requesting data collection device and comprising instructions for the installation of newly executed data collection activities, in particular including transfer and installation of the code of an executable program for executing the newly executed data collection activities and including configuration data for configuring the executable program.
[0040] A component restriction refers, in particular, to limitations regarding a component of the data acquisition device to be used in the data acquisition campaign. For example, these can be limitations due to the computing capacity of a control unit or limitations on the storage capacity for data to be stored, collected, or program data to be stored for data acquisition activities. Filtering the data acquisition campaigns on the data acquisition unit and creating an individualized provisioning list there, which is precisely tailored to the individual data acquisition device, increases the efficiency of the data acquisition campaigns, but is also beneficial for those requesting data acquisition devices that are not assigned data collection activities because they are not suitable. This allows for advantageous resource savings.Furthermore, it can be advantageous if at least one or more of the properties of the data ascertainment device are varying or variable properties, in particular the current geographical position and / or data protection settings that can be specified and changed by the data ascertainment device, wherein the request of the data ascertainment device comprises at least one value of the varying or variable property that is current at the time of the request, in particular wherein a change in the value of the varying or variable property after triggering a, for example, previous, request causes or can cause a triggering of a further request that transmits the changed value of the varying or variable property to the data acquisition unit as information.
[0041] It is a particular advantage of the invention that dynamically changing properties of the data acquisition device can be taken into account when creating the provisioning list.
[0042] Furthermore, it is advantageous if the plurality of data acquisition devices at least partially each have different control units and / or differently configured control units, in particular wherein different or differently configured control units each execute or can execute programs in different programming languages and / or wherein the instructions for carrying out the data collection activity defined in the provisioning list and / or the provisioning list are transmitted in a programming language executable on the control unit of the requesting data acquisition device.
[0043] This measure makes it possible to include data acquisition devices in the data acquisition campaigns that have different or differently configured control units, but otherwise meet all the requirements to participate in a specific data acquisition campaign. The individual provisioning lists are thus also adapted to the different requirements of the respective control units. For example, these different requirements are met by transmitting the provisioning list and the associated instructions in a programming language executable on the control unit.
[0044] The object of the invention is further achieved by a computer program product with program code means which causes one or more electronic computing devices, when the program code means are processed by the electronic computing device(s), to carry out a method having the features of one of patent claims 1 to 10. The object is further achieved by a computer-readable storage medium with such a computer program product.
[0045] Furthermore, the object of the invention is achieved by a system which comprises a data acquisition unit and at least one or more data determination devices for carrying out a method having the features of one of patent claims 1 to 10.
[0046] Advantageous embodiments and further developments according to the invention emerge from the respective dependent patent claims and also from the following description.
[0047] The invention will be further explained below using exemplary embodiments with reference to the drawings. They show a schematic representation:
[0048] FIG 1 is a flowchart illustrating the sequence of a method in an exemplary embodiment of the invention;
[0049] FIG. 1 shows a flowchart for an embodiment of the method according to the invention. A plurality of mobile and mutually independent data acquisition devices DEVi, DEV2,..., DEV n is intended to collect data of various types. A data collection device (DEV) can be, for example, a vehicle, in particular a motor vehicle, or a vehicle-mounted or non-vehicle-mounted navigation device.
[0050] A data acquisition device DEV comprises a sensor system that can record and transmit various sensor data. For example, such sensor data can be vehicle position data, operating data such as engine running time and performance data, engine consumption data, or the charge level of a vehicle battery, or even vehicle-independent data such as ambient temperature or similar. The various data acquisition devices DEV1, DEV2, ..., DEV n can have different types of sensors, meaning they can have different capabilities to record sensor data.
[0051] The data acquisition devices DEV1, ... , DEV n can be connected or linked via a wireless connection to a data acquisition unit DEE, a so-called backend server. The data acquisition unit DEE can be used to carry out so-called data acquisition campaigns DEK1, DEK2, ..., DEKn controlled and managed. Data collection campaigns (DEK) of this type are defined to collect specific data in a specific quantity or sample size and of a specific quality.
[0052] For example, a data collection campaign DEK can be defined in which data on a battery charge level and ambient temperature are to be collected on those data collection devices DEV that belong to the same vehicle type. Of course, a very wide range of data collection campaigns can be defined and are fundamentally only limited by the available sensors on the data collection devices.
[0053] N data collection campaigns DEK are stored on the data collection unit DEE. Each of the n data collection campaigns defines a multitude of individual data collection activities An, A12, Ai n to A n i, ... , A nn, for example, a data collection campaign DEK1 may include both the same and different data collection activities as another data collection campaign DEK2.
[0054] For example, a data collection activity An corresponds to collecting data on the battery charge level over time, A12 to collecting data on the ambient temperature over time and A13 to determining the information “vehicle type” of its data determination device DEV.
[0055] To control the data acquisition campaigns DEK, a data acquisition device, in the exemplary embodiment DEV1, sends a request to the data acquisition unit DEE as to which data acquisition campaigns and / or activities should be executed on the special data acquisition device DEV1. Such a request can be triggered, for example, by an event such as starting and / or driving off a data acquisition device DEV1 embodied as a vehicle. n and / or one with the data acquisition device DEV1 n coupled vehicle. Alternatively or additionally, the event may be, for example, the detection of a change in the type of road on which the data acquisition device DEV1 n which is done in particular by the data acquisition device DEV1 n can be recorded or determined by itself.
[0056] Alternatively or additionally, the event may be the exit and / or entry of the data acquisition device (DEV1 n ) to a specific limited geographical area, which is also determined by the data acquisition device (DEV1 n ) itself can be recorded or determined.
[0057] A request can be triggered by an event or time. The request also contains all properties of the data acquisition device DEV required for the filter functions of the data acquisition unit DEE, such as vehicle properties or vehicle characteristics, as well as all data acquisition campaigns DEK or activities currently running on the data acquisition device DEV. After the request is received by the data acquisition unit DEE, the request is validated in a first step. This means that the request is checked for correctness according to syntactical and functional criteria.
[0058] From a large number of requests from individual data acquisition devices DEVs, the data acquisition unit DEE determines and determines the characteristic space of various features of the data acquisition devices DEV, for example “vehicle type”, “control unit type”, “battery type”, etc. across the entire fleet of data acquisition devices DEVi to DEV n Based on the transmitted expression spaces, data discovery campaigns are then defined and prepared. For example, certain activities are cryptographically signed and filter functionalities, so-called filter expressions, are created and validated.
[0059] To create a response to the request of a specific data acquisition device DEV, the data acquisition campaigns DEK stored in the data acquisition unit DEE are filtered to determine whether they can be executed on the requesting data acquisition device DEV, whether the requesting data acquisition device DEV can deliver data of the required quality, and whether the data acquisition device is included in a subset of the fleet from which the data is to originate.
[0060] The following filter criteria Ki, ... , K n can be used, for example.
[0061] A filter criterion can, for example, be a geographical location or position. For a data discovery campaign, it can be specified that the data discovery campaign DEK should only be provisioned in a specific geographical area, for example, only those data discovery devices DEV that are located in this specific geographical area should be provisioned.
[0062] Another filter criterion can be specific vehicle characteristics. A so-called filter expression can be specified, which is evaluated as true or false based on vehicle characteristics contained in the data acquisition device's request. The filter expression is implemented in a special domain-specific language. Data acquisition campaigns (DEK) are only considered if the filter expression evaluates to true based on the vehicle's request. Vehicle characteristics that can be filtered by include, for example, the chassis number, the vehicle's home market or country, the vehicle type (model, build type, drive type, transmission type, right-hand / left-hand drive, etc.), the vehicle's special equipment, the installed control units and associated hardware and software versions, as well as data protection menu settings. Another filter criterion can be a fleet membership of the data acquisition device (DEV).A sub-fleet of an entire fleet of data acquisition devices can be specified. With this filter criterion, data acquisition campaigns are only considered if the requesting vehicle is part of the predefined sub-fleet. Alternatively, it is also possible to specify that only a certain percentage of the requesting data acquisition devices should be provisioned with a specific data acquisition campaign. Accordingly, a filter criterion is checked to determine whether the requesting vehicle falls within or outside the specified percentage.
[0063] Another filter criterion can be component restrictions. In the data acquisition unit (DEE), so-called component restrictions are maintained in a similar way to the data acquisition campaigns. In this filtering step, the relevant components and restrictions for data acquisition campaigns (DEK) are derived from the associated activities, and the latter are checked against the vehicle request. Such a component restriction can, for example, be a limited CPU or memory configuration of the data acquisition device of the requesting vehicle.
[0064] In general, a filter expression can be constructed using language expressions based on Boolean logic.
[0065] In response to a request from an individual data collection device DEVi, the data collection unit DEE provides an individual provisioning list, i.e., one tailored or adapted to the requesting data collection device DEVi, as well as instructions tailored or adapted to the requesting data collection device DEVi as to which data collection campaigns or activities on the data collection device DEVi should be stopped, removed, continued, restarted, or reinstalled and restarted. If a data collection campaign DEK or activity A ne u, the instructions also include metadata and executable code.
[0066] After completing the filtering steps, the provisioning list is created and transmitted with instructions to the requesting data acquisition device (DEV), which then performs the corresponding activities and transmits the collected data either in real time or after completion of the data acquisition campaign or at another suitable time to the data acquisition unit (DEE), where the data from the other data acquisition devices executing the same data acquisition campaign is merged.
[0067] DEVi . n data acquisition device
[0068] DEE data acquisition unit
[0069] DEKi . n Data collection campaign Al . n data collection activity
[0070] Kl n filter criterion
Claims
Patent claims 1. Method for data acquisition with a data acquisition unit (DEE) which is connected to a plurality of mobile and independent data acquisition devices (DEVi) which are in particular designed as a vehicle or can be coupled to a vehicle. n ), each comprising at least one control device that is configurable or configured to perform at least one selection from a plurality of different data acquisition activities (Ai n ), the method comprising the following steps: a) receiving a request from a data acquisition device (DEVi n ) by the data acquisition unit (DEE), wherein the request contains information on a data collection capacity of the data acquisition device (DEVi n ) and information about one or more properties of the data acquisition device (DEVi n) and where the request includes a request for instructions to carry out data collection activities (Ai n ); b) determining the suitability of data collection campaigns (DEKi n ) from the multitude of data collection campaigns (DEKi n ) for the process on the requesting data acquisition device (DEVi n ), comprising: b1) Determination by the data collection unit (DEE) of those data collection campaigns (DEKi n ) from the multitude of data collection campaigns (DEKi n ) that apply one or more predetermined criteria to the data collection campaigns (DEKi n ) if they are stored on the requesting data acquisition device (DEVi n ) are executed; and b2) Determination by the data acquisition unit (DEE) of the data stored on the requesting data acquisition device (DEVi n ) executable data collection activities of the data collection campaigns (DEKi n) depending on the data collection capacity of the data acquisition device (DEVi n ); c) Creation of a provisioning list by the data collection unit (DEE) containing the executable data collection activities of the data collection campaigns (DEKi) that meet the predetermined criteria n ) includes; d) Submitting the provisioning list and instructions for carrying out the tasks specified in the Provisioning list defined data collection activities (Ai n ) of the Data Acquisition Unit (DEE) to the requesting data acquisition device (DEVi n ); 2. Method according to claim 1, characterized in that the request of the data acquisition device (DEVi n ) to the data acquisition unit (DEE) is triggered by an event, in particular wherein the event is a starting and / or starting of the data acquisition device (DEVi n) and / or one connected to the data acquisition device (DEVi n ) coupled vehicle, and / or wherein in particular the event comprises the detection of a change in a road type on which the data acquisition device (DEVi n ), in particular by the data acquisition device (DEVi n ), and / or in particular wherein the event is the leaving and / or entering of the data acquisition device (DEVi n ) to a specific limited geographical area, in particular by the data collection device (DEVi n ) and / or in particular wherein the event is a change in the data acquisition device (DEVi n ) applicable data protection settings.
3. Method according to one of the preceding claims, characterized in that the request of the data acquisition device (DEVi n) to the data acquisition unit (DTE) is triggered in a time-controlled manner, in particular at regular intervals and / or at specific times or times of day.
4. Method according to one of the preceding claims, characterized in that the request of the data acquisition device (DEVi n ) to the data acquisition unit (DEE) information on the data acquisition device (DEVi n ) active data collection activities (Ai n ) and / or that the instructions for carrying out the identified, executable data discovery activities include instructions as to whether and which data discovery activities are to be carried out on the data discovery device (DEVi n ) active data collection activities (Ai n ) should be stopped or removed or prioritized or deprioritized or continued unchanged and / or the instructions for carrying out the identified, executable data collection activities include instructions which data collection activities (Ai n ) are to be carried out again, in particular where the new data collection activities (Ai n ) a control program is installed which can or controls the new data collection activities to be carried out.
5. Method according to one of the preceding claims, characterized in that the data acquisition unit (DEE) receives a plurality of requests from different data acquisition devices (DEVi) which in particular have at least partially individually different data collection capacities. n ), wherein the data acquisition unit (DEE) uses the information contained in the plurality of requests to determine the, in particular individually different, data collection capacities of the data acquisition devices (DEVi n) and a, in particular spatial and / or temporal, distribution of executable data collection activities (Ai n ) certainly.
6. Method according to one of the preceding claims, characterized in that the data acquisition unit (DEE) receives a plurality of requests from different data acquisition devices (DEVi n ), wherein the requests contain information on one or more properties, in particular a chassis number and / or a place of first registration of the vehicle and / or the type of control unit and / or specifics of the vehicle design, of the data acquisition device (DEVi n ), wherein the data acquisition unit (DEE) uses the information contained in the plurality of requests regarding the properties of the data acquisition device (DEVi n) and a, in particular spatial and / or temporal, distribution of the properties of the plurality of data acquisition devices (DEVi n ) certainly.
7. Method according to one of the preceding claims, characterized in that when carrying out the data collection activities (Ai) defined in the provisioning list n ) on the requesting data acquisition device (DEVi n ), in particular in real time or at regular intervals or after completion of the defined data collection activities (Ai n ), are transmitted to the data acquisition unit (DEE), in particular wherein in the data acquisition unit (DEE) the data of the plurality of requesting data acquisition devices (DEVi n ) are merged, which the data collection activities (Ai n ) of the same data collection campaign.
8. Method according to one of the preceding claims, characterized in that the determination of the data on the requesting data determination device (DEVi n ) executable data collection activities by the data collection unit (DTE) comprises at least the following steps: - Filtering of saved and active data collection campaigns (DEKi n ) by the data acquisition unit (DTE), filtering according to one or more of the following criteria: - according to the degree of coverage; and / or - according to current geographical position; and / or - according to the characteristics of the data acquisition device (DEVi n), in particular by chassis number and / or place of first registration of the vehicle and / or type of control unit and / or specifics of the vehicle design and / or properties of the sensors available to the data acquisition device and / or belonging to a defined fleet of vehicles; and / or - according to component restrictions; and / or - according to privacy settings; - Generation of a list of the data collection campaigns resulting from the filter step (DEKi n ) with the associated data collection activities (Ai n ); and / or - Generation of the provisioning list for the requesting data acquisition device (DEVi n ), including instructions for the installation and / or retention and / or removal of the data acquisition device (DEVi n ) active data collection activities (Ai n) and comprehensive instructions for installing new data collection activities (Ai n ), in particular including the code of an executable program to carry out the new data collection activities to be carried out (Ai n ) and including configuration data for configuring the executable program.
9. Method according to one of the preceding claims, characterized in that at least one or more of the properties of the data acquisition device (DEVi n ) varying or variable properties, in particular the current geographical position and / or the data acquisition device (DEVi n ) predefinable and changeable data protection settings, whereby the request of the data collection device (DEVi n ) comprises at least one value of the varying or variable property that is current at the time of the request, in particular wherein a change in the value of the varying or variable property after triggering a request causes or can cause a further request to be triggered, which transmits the changed value of the varying or variable property to the data acquisition unit (DEE) as information.
10. Method according to one of the preceding claims, characterized in that the plurality of data acquisition devices (DEVi n) at least partially each have different control units and / or differently configured control units, in particular wherein different or differently configured control units each execute or can execute programs in different programming languages and / or wherein the instructions for carrying out the data collection activity (Ai) defined in the provisioning list n ) and / or the provisioning list in a file stored on the control unit of the requesting data acquisition device (DEVi n ) executable programming language.
11. A computer program product comprising program code means which causes one or more electronic computing devices to carry out a method according to one of claims 1 to 10 when the program code means are processed by the electronic computing device(s).
12. A computer-readable storage medium comprising at least one computer program product according to claim 11.
13. System comprising a data acquisition unit (DEE) and at least one or more data acquisition devices (DEVi n ) for carrying out the method according to one of claims 1 to 10.
Citation Information
Patent Citations
Method for data collection
US20200082710A1
Dynamic vehicle data extraction service
WO2023097157A1