Comparison of data sets between field devices and a database

Abstract

Method (100) for comparing data sets (2) between at least one field device (1), which serves for the control and / or monitoring of an industrial process and has a radio interface (1a), and a database (3) on a server (4), wherein the radio interface (1a) of the field device (1) has no connection to the server (4), wherein the comparison is mediated by a mobile device (5) which is equipped both for establishing a radio connection with the radio interface (1a) of the field device (1) and is connectable to the server (4), wherein the mobile device (5) • data records (2) intended for transmission to the field device (1) are retrieved from the database (3) (120), stored at least transiently (130), and transmitted to the field device (1) (150) at a second location where the connection to the server (4) is available, but not the radio connection to the field device (1), in response to the fact that, after moving the mobile device (5) to a first location where the radio connection to the radio interface (1a) of the field device (1) is available (140), the data records (2) are received from the database (3) (120), stored at least transiently (130), and / or • Data records (2) intended for transmission to the database (3) are received (170) from the field device (1) at a first location where the radio connection to the radio interface (1a) of the field device (1), but not the connection to the server (4), is available, stored at least transiently (180) and transmitted to the database (3) in response to the fact that, after moving the mobile device (5) to a second location where a connection to the server (4) is available (190) (200).

Description

[0001] The invention relates to the comparison of data sets between field devices used for monitoring and / or controlling industrial processes and an external database to which there is no permanently available connection. State of the art

[0002] Field devices are used to monitor and, in particular, to control industrial processes. These field devices are typically connected at their point of use in an industrial plant to narrowband interfaces, such as current interfaces, on which analog information is encoded in the form of currents between 4 and 20 mA. A direct connection of the field devices to the industrial plant's LAN is generally not provided.

[0003] Field devices are generally designed for universal use in a wide variety of situations and can be configured with numerous parameters for their specific application. This is done by connecting a PC or laptop to the field device via a suitable interface. Most field devices also have a function that allows the complete configuration data to be downloaded as a backup file and later restored.

[0004] It is also common to use the option of changing settings via controls on the field device itself. The backup file must then be updated regularly so that a restore process returns the field device to its last working state.

[0005] DE 600 33 178 T2 discloses a method for transferring data between a central infrastructure and one or more devices or sensors by means of a “transceiver”, which can also be mobile.

[0006] DE 103 09 454 A1 discloses a method for collecting data from a large number of consumption meters, such as heat cost allocators.

[0007] DE 10 2015 116 806 A1 discloses a permanently installed “access point” that enables communication between field devices and an existing network infrastructure, thus simplifying centralized management of field devices. Task and solution

[0008] The purpose of the invention is to simplify the centralized management of field devices.

[0009] This problem is solved according to the invention by a method according to the main claim and by a computer program according to the dependent claim. Further advantageous embodiments are described in the dependent claims relating thereto. Disclosure of the invention

[0010] Within the scope of the invention, a method for comparing data records between at least one field device, which serves to control and / or monitor an industrial process, and a database on a server has been developed. This database can store a multitude of data records for each field device, which have been transmitted by the field device or are to be transmitted to the field device. In particular, the database can use the field device's unalterable serial number as the primary key and can also be organized according to other characteristics specified by the operator of the industrial plant, such as a name assigned during the initial setup of the field device, which logically provides information about its purpose and location.

[0011] The field device features a radio interface that can be used, for example, for initial setup with a PC or laptop. The radio interface can operate with any protocol and is specifically designed for establishing a short-range radio connection.

[0012] For example, Bluetooth, Bluetooth Low Energy, LPWAN, 6lowpan, LoRa, or other transmission standards can be used. Bluetooth and Bluetooth Low Energy are particularly advantageous because these standards are generally supported by general-purpose devices such as smartphones, tablets, and laptops.

[0013] The procedure now assumes the given situation that the radio interface of the field device has no connection to the server with the database and that there is no other permanent network connection between the field device and the server.

[0014] To enable data synchronization between the field device and the database, the procedure involves using a mobile device to facilitate this synchronization. This mobile device must be equipped to establish a radio connection with the field device's radio interface and also be connectable to the server. Specifically, the mobile device can initially be located at a location within radio range of the field device's radio interface but without a connection to the server containing the database. Subsequently, the mobile device can be located at a second location where a connection to the server is available (e.g., via Wi-Fi or cable), but this second location is then outside the radio range of the field device's radio interface. Additionally, there can be third locations where both a radio connection to the field device and a connection to the server are available.Such third places could be, for example, exposed locations, such as higher-lying areas, in an industrial plant.

[0015] The mobile device receives specific data records from the database for transmission to the field device, stores them at least temporarily, and transmits them to the field device as soon as a radio connection to the field device's radio interface is available. If the mobile device is located at a third location where both a connection to the server and a radio connection to the field device are simultaneously available, the data records can be forwarded to the field device immediately after being received from the database. However, if the mobile device receives the data records at a second location where only a connection to the server is available, the data records can be forwarded to the field device as soon as the mobile device moves to a first or third location within radio range of the field device's radio interface.

[0016] Alternatively, or particularly in combination, certain data records are received from the field device for transmission to the database, stored at least temporarily, and then transmitted to the database in response to the availability of a connection to the server. This transmission can also occur immediately after the data records have been received from the field device, provided the mobile device is located at a third location where, in addition to the radio connection to the field device, a connection to the server is also available. If the mobile device received the data records at an initial location where only the radio connection to the field device is available, the data records can be transferred to the database as soon as the mobile device moves to a second or third location where a connection to the server is available.

[0017] The mobile device thus serves as a transport vehicle for the physical transfer of data records between the database and the field device, or, in most industrial applications, a multitude of field devices. The mobile device therefore replaces the intermittent network connection between the field device and the server. This enables centralized management of field devices using the database, without necessarily incurring the costs of directly connecting all field devices to the company intranet. The transfer of cached data records can be fully or partially automated without user intervention on the mobile device, for example, running in the background.This offers a significant advantage over the previous method of managing field devices via a PC or laptop directly connected to the device: When data was loaded from a field device to a laptop, other IT systems, and especially a central database, were unaware of this until the data was manually loaded into the database from the laptop at a later time. If this was forgotten, the data was only stored locally on the laptop. With a sufficiently large number of laptops in use, it was easy to lose track of where the most recent backup of a field device's data was located. This created a risk that, in the event of a malfunction requiring a rapid replacement of the field device, an outdated backup would be restored, causing the field device to behave differently than expected.The newly created communication path between the field devices and the database makes it possible to work with only one central storage location for the data records, which is always kept up to date.

[0018] This communication path offers security advantages over a permanent network connection between the field device and the server. By transmitting only the data previously cached on the mobile device to the receiving device, the communication path is inherently limited to data records that have been formally accepted as valid by the mobile device. For example, if an attacker injects a manipulated data packet with an excessively long data field into the database with the aim of forcing their will on a field device through a buffer overflow, this data packet will be rejected as invalid by the mobile device and not cached.In contrast to a permanent network connection, the communication path cannot be misused from the outset to send data to arbitrary system services running on the field device and to gain access to an interactive command line through a successful attack on such a system service (e.g., the web server used to display a user interface). This is particularly advantageous given that, after security vulnerabilities are discovered in, for example, popular web server software, it can take some time before corresponding updates for the hardware platform and operating system used on the field devices are available. Experience also shows that even when updates are available, they are not always installed promptly by the field device operators.Direct attack on the radio interface of the field device requires, especially when the field device is used in an enclosed hall, sufficient physical proximity.

[0019] A variety of mobile devices, such as smartphones, laptops, tablets, or other battery-powered devices, can be used to compare the data sets. For example, a corresponding app can be installed on the mobile devices of employees who regularly move between locations where the company's Wi-Fi network with the server is available and the production hall with the field devices.

[0020] In a particularly advantageous embodiment, before a data record is transmitted from the database or field device to the mobile device, a timestamp, version number, and / or hash value of the data record is compared with a reference value stored on the mobile device. If the comparison reveals no difference, the transmission of the data record is suppressed. Conversely, if the comparison reveals a difference, the data record is transmitted to the mobile device, and the timestamp, version number, and / or hash value of this data record is set as the new reference value on the mobile device. This avoids repeated, unnecessary transmissions of identical data records over the radio interface, thus saving capacity on the radio channel, which is sometimes shared by many field devices.For example, if the same mobile device repeatedly moves within the radio range of the radio interface of the same field device and then out of that range again, the current data set is only transmitted once from the field device to the mobile device. Such a situation can occur, for instance, if the user of the mobile device repeatedly moves into areas where the radio connection to the radio interface is blocked.

[0021] In a further advantageous embodiment, a plan is stored on the mobile device specifying which field devices are to receive at least one data record from each, and / or to which field devices at least one data record is to be transmitted. The mobile device issues an instruction to a user of the mobile device, prompting them to bring the mobile device within radio range of the radio interface of at least one of the field devices listed in the plan.

[0022] For example, it might be intended to distribute a specific firmware and / or configuration settings update to all deployed field devices on a particular day, taking advantage of the fact that the mobile device user typically comes within radio range of each field device to be updated during their normal workday. It may happen that the user cannot reach certain field devices, for example, because they were delayed by a malfunction elsewhere. If the mobile device then detects at a specific time that the transfer of data records to some field devices has not yet been completed, a corresponding notification can be issued to the user.

[0023] In particular, an instruction to the user of the mobile device to move the mobile device in a specific direction to approach a location within radio range of the radio interface of the at least one field device shown in the plan can be derived, for example, from the radio environment sensed by at least one radio receiver of the mobile device, and / or from at least one image sensed by a camera of the mobile device, and / or from at least one sound sensed by a microphone of the mobile device, and / or from acceleration values ​​sensed by at least one accelerometer of the mobile device. This instruction may be more understandable to the user than an instruction to approach the mobile device to a field device with a specific name.

[0024] In a further advantageous embodiment, the mobile device, upon coming within radio range of the radio interface of at least one field device, queries the database to determine whether a data record is ready for transmission to that field device, and / or the mobile device schedules this request for the next time a connection to the server is available. In this way, the mobile device preferentially caches data records that have a realistic prospect of being transferred to the respective target field device in a timely manner. Data records for field devices that the user of the mobile device does not typically come into contact with, on the other hand, only occupy unnecessary storage space in the mobile device's cache.

[0025] After a database query has been successfully completed, further queries concerning the same field device are advantageously suppressed for a predetermined period. This period is determined by the typical frequency with which data records are updated in the respective application. This prevents the server from being bombarded with an unnecessarily high number of queries from numerous mobile devices.

[0026] It is advantageous to assign an expiration date to data records stored on the mobile device. These records are discarded by the mobile device if they have not yet been transmitted to the field device or database by this expiration date. This prevents a large number of outdated records from accumulating in the mobile device's local memory during extended use. Such "dead records" pose a latent risk of being inadvertently replaced by newer records, potentially leading to malfunctions.

[0027] In a further advantageous embodiment, the mobile device, in response to having saved a data record from a field device and having not connected to the server for a specified period of time, issues an instruction to a user of the mobile device to establish a connection with the server. This instruction may, in particular, include moving the mobile device in a specific direction to bring it closer to a location where it can connect to the server. This improves the timeliness of the information in the database.

[0028] In a further particularly advantageous embodiment, an optical and / or acoustic signaling device on the field device is activated when at least one data record is pending transmission from the mobile device to a field device and the mobile device comes within radio range of the field device's radio interface. Confirmation is obtained from the mobile device user that the data record should be transmitted to this field device. This informs the user that the field device's behavior may change after receiving the data record, thus preventing this change from being entirely unexpected. Furthermore, it provides a fallback mechanism in case errors have crept into the database regarding the mapping between field device serial numbers and their actual installation locations.Such errors can occur, for example, when field devices are replaced with new ones or when functionally identical field devices are swapped without this being recorded in the database. The user notices the error when, before the update in conjunction with the confirmation request, the signal transmitter of a different field device is activated than expected.

[0029] As described above, the data set advantageously contains configuration data with user-adjustable parameters for the operation of at least one field device, and / or firmware, and / or a memory image of the field device. The database, in conjunction with the newly established communication channel via the mobile device, can then be used to centrally manage the configuration of a large number of field devices.

[0030] Advantageously, at least one data record contains measurement values ​​acquired by the field device. This allows particularly large volumes of measurement results, such as image data or longer histories of measurement values, whose transmission is not time-critical, to be transferred to the database without blocking a narrowband interface (such as a 4-20 mA current interface) to which the field device is connected for too long.

[0031] The process can be implemented in software, particularly without any hardware changes, and can be installed on the mobile device, the server, and / or the field device. There is flexibility regarding where many functions are located. For example, the mobile device can proactively query the field device or the server for new data records (pull). Alternatively, the mobile device can listen for the field device or server to transmit data records to it on its own initiative (push).

[0032] Thus, the invention also relates to a computer program with machine-readable instructions which, when executed on a computer, and / or on a mobile device, and / or on a field device, cause the computer, the mobile device, or the field device to execute the described method. Special description section

[0033] The subject matter of the invention is explained below with reference to figures, without thereby limiting the subject matter of the invention. The following are shown: Fig. 1: Exemplary embodiment of method 100; Fig. 2: Possibilities for transmitting data sets 2 at several exemplary locations of the mobile device 5.

[0034] Fig. Figure 1 shows an embodiment of method 100. Fig. Figure 1a shows an exemplary path by which data records 2 can be processed starting from a database 3 until they finally reach a field device 1.

[0035] In step 110, it is first checked whether a timestamp 2a, a version number 2b, and / or a hash value 2c of data record 2 differs from a reference value 2d stored in mobile device 5. If this is not the case (truth value 0), the transmission 120 of data record 2 to mobile device 5 is suppressed in step 115. However, if the comparison reveals a difference (truth value 1), the data record is transmitted to mobile device 5 in step 120, and the reference value 2d is reset in step 125. In step 130, data record 2 is stored at least transiently in mobile device 5.

[0036] In step 131, data record 2 is assigned an expiration time 2e. In step 132, it is checked whether the expiration time 2e has been reached or exceeded at the current time t and whether data record 2 has yet been transmitted to field device 1. This check 132 can be performed immediately, but also significantly later, as in Fig. 1a drawn. For example, exam 132, as in Fig. 1a drawn, to be carried out periodically over time.

[0037] If the expiry time 2e is reached or exceeded and the data record 2 has not yet been transmitted to the field device 1, i.e., it is still in a corresponding queue, for example, it is discarded in step 133.

[0038] In conjunction with test 132, step 140 verifies whether the radio connection to radio interface 1a of field device 1 is available. Both tests 132 and 140 can, for example, be performed alternately or with different time intervals. Test 140 can also be event-driven, for example, when a specific movement of mobile device 5 is detected.

[0039] If the radio connection to radio interface 1a is available (truth value 1 in check 140), an optical and / or acoustic signal generator 1c of the field device 1 is optionally activated in step 141 to clearly indicate to the user 5a of the mobile device 5 to which device the data record 2 is to be transmitted. Confirmation from the user 5a can be obtained in the also optional step 142. In step 150, the data record 2 is transmitted to the field device 1.

[0040] Fig. Figure 1b shows an exemplary path by which data records 2 can be processed starting from a field device 1 until they finally reach the database 3.

[0041] Analogous to step 110, step 160 first checks whether a timestamp 2a, a version number 2b, and / or a hash value 2c of data record 2 differs from a reference value 2d stored in mobile device 5. If this is not the case (truth value 0), the transmission 170 of data record 2 to mobile device 5 is suppressed in step 165. However, if the comparison reveals a difference (truth value 1), the data record is transmitted to mobile device 5 in step 170, and the reference value 2d is reset in step 175. In step 180, data record 2 is stored at least transiently in mobile device 5.

[0042] In step 181, data record 2 is assigned an expiration time 2e. In step 12, it is checked whether the expiration time 2e has been reached or exceeded at the current time t and whether data record 2 has yet been transmitted to database 3. This check 182 can be performed immediately, but also significantly later, as in Fig. 1b drawn. For example, exam 182, as in Fig. 1b drawn, to be done periodically over time.

[0043] As part of this periodic check, for example, step 184 can also check whether the mobile device has not had a connection to server 4 for some time since storage 180. If this is the case (truth value 1 in check 184), then in step 185 an instruction can be issued to user 5a of mobile device 5 to instruct them to connect mobile device 5 to server 4.

[0044] If the expiry time 2e is reached or exceeded and the data record 2 has not yet been transmitted to the database 3, i.e., it is still in a corresponding queue, it is discarded in step 183.

[0045] In conjunction with check 182, step 190 verifies whether the connection to server 4 is available. Both checks, 182 and 190, can be performed alternately or with different time intervals. Check 190 can also be triggered by events, such as when the mobile device 5 registers that it has connected to a network (like a Wi-Fi network) or that it has been connected to a specific computer via cable, Bluetooth, or another connection.

[0046] If the connection to the server is available (truth value 1 in check 190), then in step 200 the data record 2 is transmitted to the database 3.

[0047] The procedures according to the Fig. 1a and Fig. 1b can progress independently of each other and be active simultaneously. For example, one and the same mobile device 5 can, in addition to data records 2 that it has taken from a first database 3 for forwarding to a first field device 1, also contain data records that it has taken from a second field device 1 for forwarding to a second database 3.

[0048] Another independent optional process that can be executed in procedure 100 is in Fig. Figure 1c illustrates this. In step 101, a plan 6 is stored on the mobile device 5, specifying which field devices 1 the mobile device 5 should communicate with. In step 102, an instruction is issued to the user 5a of the mobile device 5, instructing them to move the mobile device 5 within the radio range 1b of the radio interface of at least one field device 1 listed in the plan 6. Step 102 can include substep 102a, which enriches this instruction with a specific direction, based on measured values, in which the user 5a should move the mobile device 5 to get closer to the radio range 1b.

[0049] If the user enters radio range 1b in response to this instruction, this could, for example, affect the device in Fig. The process shown in 1a can be influenced by the radio range test 140 assuming the truth value 1.

[0050] Another independent optional process that can be executed in procedure 100 is in Fig. Figure 1d illustrates this. Triggered by the determination in step 103 that the mobile device enters the radio range 1b of the radio interface 1a of at least one field device 1, a query can be made in step 104a to database 3 to determine whether updated data records 2 exist for the field device 1. Alternatively, if this query 104a fails, a corresponding query can be scheduled in step 104b for the time when the connection to server 4 is available again.

[0051] If the query in step 104a has been performed, further similar queries concerning the same field device can be suppressed for a predetermined period of time.

[0052] Fig. Figure 2 shows the possibilities for transmitting data records at various locations between field device 1 and server 4 containing database 3. An area 4a is drawn around server 4, within which a connection between the mobile device 5 and server 4 is possible. This area 4a could, for example, represent the network coverage of an internal WLAN through which server 4 is accessible. The radio range 1b of the radio interface 1a of field device 1 is also shown. Fig. Figure 2 also shows the signal transmitter 1c, with which the field device 1 indicates that it feels addressed by the mobile device 5.

[0053] If the mobile device 5 is within radio range 1b, but not in area 4a, the mobile device 5 can transfer previously stored data records 2 to the field device 1 and receive other data records 2 from the field device 1. If the user 5a then moves the mobile device 5 into area 4a, the data records 2 previously received from the field device can be transferred to database 3, and in exchange, new data records 2 can be taken from database 3 for forwarding to the field device 1.

[0054] In the special case that both server 4 and field device 1 are reachable simultaneously from the location of mobile device 5, the data records 2 can be forwarded immediately after their receipt. Reference symbol list 1 field device 1a Radio interface of the field device 1 1b Radio range of the radio interface 1a 1c Signal transmitter of field device 1 2 data sets 2a Timestamp of data record 2 2b Version number of dataset 2 2c Hash value of data set 2 2D comparison value 2e Expiry date for data record 2 3 Database 4 servers 4a Area where server 4 is reachable 5 mobile device 5a Users of the mobile device 5 6 Plan of the field equipment to be located 6 100 procedures 101 Creating Plan 6 102 Issuance of an instruction to locate radio range 1b 102a Specification of the instruction with one direction 103 Finding that mobile device 5 is within radio range 1b 104a Request to database 3 for current data records 2 104b Pre-booking, query database 3 if server 4 is reachable 105 Suppressing similar requests 104a for the same field device 1 110 Comparison of values ​​2a-2c with the comparison value 2d 115 Suppress transmission 120 120 Transferring data set 2 from database 3 to mobile device 5 125 Resetting the comparison value 2d to new value 2a-2c 130 Saving data set 2 on mobile device 5 131 Setting an expiry date 2e 132 Examination to determine whether expiry date 2e has expired without result 133 Discarding data set 2 140 Checking whether radio range 1b around field device 1 has been reached 141 Activation of signal transmitter 1c of field device 1 142 Obtaining confirmation from user 5a 150 Transmit data set 2 to field device 1 160 Comparison of values ​​2a-2c with the comparison value 2d 165 Suppressing transmission 120 170 Transmitting data set 2 from field device 1 to mobile device 5 175 Resetting the comparison value 2d to new value 2a-2c 180 Saving data set 2 to mobile device 5 181 Setting an expiry date 2e 182 Examination of whether expiry date 2e has expired without result 183 Discarding data set 2 184 Checking if there has been no contact with server for a while 4 185 Request to user 5a to establish contact with server 4 190 Checking if a connection to server 4 is available 200 Transmission of data set 2 to database 3

Claims

[1] Method (100) for comparing data sets (2) between at least one field device (1), which serves for the control and / or monitoring of an industrial process and has a radio interface (1a), and a database (3) on a server (4), wherein the radio interface (1a) of the field device (1) has no connection to the server (4), wherein the comparison is mediated by a mobile device (5) which is equipped both for establishing a radio connection with the radio interface (1a) of the field device (1) and is connectable to the server (4), wherein the mobile device (5) • data records (2) intended for transmission to the field device (1) are retrieved from the database (3) (120), stored at least transiently (130), and transmitted to the field device (1) (150) at a second location where the connection to the server (4) is available, but not the radio connection to the field device (1), in response to the fact that, after moving the mobile device (5) to a first location where the radio connection to the radio interface (1a) of the field device (1) is available (140), the data records (2) are received from the database (3) (120), stored at least transiently (130), and / or • Data records (2) intended for transmission to the database (3) are received (170) from the field device (1) at a first location where the radio connection to the radio interface (1a) of the field device (1), but not the connection to the server (4), is available, stored at least transiently (180) and transmitted to the database (3) in response to the fact that, after moving the mobile device (5) to a second location where a connection to the server (4) is available (190) (200). [2] Method (100) according to claim 1, wherein, prior to the transmission (120, 170) of a data record (2) from the database (3) or from the field device (1) to the mobile device (5), a timestamp (2a), a version number (2b), and / or a hash value (2c) of the data record (2) are compared with a comparison value (2d) stored in the mobile device (5) (110, 160), wherein • in response to the fact that the comparison (110, 160) yields no difference, the transmission (120, 170) of the data set (2) is suppressed (115, 165), and • in response to the fact that the comparison (110, 160) yields a difference, the data set (2) is transmitted to the mobile device (5) (120, 170) and in the mobile device (5) the timestamp (2a), the version number (2b), and / or the hash value (2c) of this data set (2) is set as the new comparison value (2d) (125, 175). [3] Method (100) according to one of claims 1 to 2, wherein a plan (6) is stored on the mobile device (5) (101) from which field devices (1) at least one data record (2) is to be received, and / or to which field device (1) at least one data record (2) is to be transmitted, wherein the mobile device (5) issues an instruction to a user (5a) of the mobile device (5) (102) to cause the user to bring the mobile device (5) into radio range (1b) of the radio interface (1a) of at least one of the field devices (1) listed in the plan (6). [4] Method (100) according to claim 3, wherein an instruction to the user (5a) of the mobile device (5) is determined from the radio environment sensed by at least one radio receiver of the mobile device (5), and / or from at least one image sensed by a camera of the mobile device (5), and / or from at least one sound sensed by a microphone of the mobile device (5), and / or from acceleration values ​​sensed by at least one accelerometer of the mobile device (5), to move the mobile device (5) in a certain direction in order to bring the mobile device (5) closer to a location where it is within radio range (1b) of the radio interface (1a) of the at least one field device (1) shown in the plan (6). [5] Method (100) according to any one of claims 1 to 4, wherein the mobile device (5), in response to coming within radio range (1b) of the radio interface (1a) of at least one field device (1) (103), queries the database (3) (104a) to see if a data record (2) is available for transmission to this field device (1), and / or schedules this query for the next time a connection to the server (4) is available (104b). [6] Method (100) according to claim 5, wherein after the query (104a) has been made to the database (3), further queries relating to the same field device (1) are suppressed for a predetermined period of time (105). [7] Method (100) according to any one of claims 1 to 6, wherein data records (2) are provided with an expiry time (2e) during storage (130, 180) by the mobile device (5) (131, 181) and wherein these data records (2) are discarded by the mobile device (5) (133, 183) if they could not yet be transmitted from the mobile device (2) to the field device (1) or to the database (3) at this expiry time (2e) (132, 182). [8] Method (100) according to any one of claims 1 to 7, wherein the mobile device (5), in response to having stored a data record (2) from a field device (1) (180) and having not had a connection to the server (4) for a specified period of time (184), issues an instruction to a user (5a) of the mobile device (5) (185) to cause the user to connect the mobile device (5) to the server (4). [9] Method (100) according to claim 8, wherein the instruction includes moving the mobile device (5) in a certain direction to bring the mobile device (5) closer to a location (4a) where it can connect to the server (4). [10] Method (100) according to any one of claims 1 to 9, wherein in response to at least one data set being ready for transmission from the mobile device (5) to a field device (130) and the mobile device (5) coming within radio range of the radio interface (1a) of this field device (1) (140), an optical and / or acoustic signal generator (1c) of this field device (1) is activated (141) and confirmation is obtained from the user (5a) of the mobile device (5) (142) that the data set (2) is to be transmitted (150) to this field device (1). [11] Method (100) according to any one of claims 1 to 10, wherein at least one data set (2) contains configuration data with user-adjustable parameters for the operation of at least one field device (1), and / or firmware, and / or a memory image of the field device (1). [12] Method (100) according to any one of claims 1 to 11, wherein at least one data set (2) contains measured values ​​that the field device (1) has recorded. [13] Computer program containing machine-readable instructions which, when executed on a computer, and / or on a mobile device (5), and / or on a field device (1), cause the computer, the mobile device (5), or the field device (1) to execute a method (100) according to any one of claims 1 to 12.

Images