Gateway, system and method for running gateway

Abstract

The present invention relates to a gateway for calling telemetry data from a field device and transmitting the called telemetry data to a cloud server, wherein the gateway comprises a cloud communication component, which is configured to predetermine a periodic request time, at which an internal gateway request for a current variable value of a variable of the telemetry data should be made, and a field device communication component, which is configured to make a variable call for the current variable value from the field device at the periodic call time. The gateway is configured to adjust the phase of the periodic call time relative to the periodic request time so that the corresponding current variable value has been called from the field device and exists in the field device communication component at the request time of the corresponding gateway request.

Description

Technical Field

[0001] The present invention relates to a gateway for calling telemetry data from a field device and for transmitting the called telemetry data to a cloud server, wherein the gateway includes a cloud communication component, which is constructed to predetermine a periodic request time, to make an internal gateway request for the current variable value of a variable of the telemetry data at the periodic request time, and to transmit the current variable value provided in response to the internal gateway request to the cloud server.

[0002] The gateway further includes a field device communication component configured to make a variable call for a current variable value from the field device and provide the cloud communication component with the current variable value received at the time of the variable call. Background Art

[0003] Conventionally, variable calls are triggered by the internal gateway request, so that the field device communication component starts the variable call only after the corresponding gateway request. Waiting times may occur during the communication between the gateway and the field device, so that the variable call may take a certain amount of time and thus the current variable value of the requested variable cannot be provided immediately after the gateway request. Summary of the invention

[0004] The object of the present invention is to quickly provide the cloud communication component with current variable values. Preferably, the cloud communication component should not be modified for this purpose.

[0005] This object is achieved by a gateway according to claim 1 .

[0006] The field device communication component of the gateway is configured to perform a variable call for the current variable value from the field device at the time of the periodic call and to provide the cloud communication component with the current variable value received at the time of the variable call in response to the gateway request. Preferably, the variable call is no longer triggered by the corresponding gateway request, but is instead performed periodically (in particular independently of the corresponding gateway request). The gateway request is thus decoupled from the variable call, in particular in such a way that the variable call is not triggered by the gateway request. In particular, the gateway request and the variable call occur simultaneously.

[0007] The gateway is configured to adjust the phase of the periodic call time relative to the periodic request time so that the corresponding current variable value provided by the field device communication component to the cloud communication component in response to the corresponding gateway request has been called from the field device and exists in the field device communication component at the request time of the gateway request. The variable call is placed before the corresponding gateway request in time. Therefore, the field device communication component performs the variable call before the corresponding gateway request in time. At the moment of each gateway request, the corresponding variable call has ended and the current variable value already exists in the field device communication component, so that the current variable value can be directly transmitted to the cloud communication component after the gateway request. Therefore, the current variable value can be quickly provided to the cloud communication component.

[0008] Advantageous developments are the subject matter of the dependent claims.

[0009] The invention further relates to a system comprising a valve device and a gateway, wherein the gateway is designed to retrieve the telemetry data from the valve device and / or via the valve device.

[0010] The present invention also relates to a method for operating a gateway for calling telemetry data from a field device and transmitting the called telemetry data to a cloud server, the method comprising the following steps:

[0011] - by means of a cloud communication component of the gateway, predefining a periodic request time, at which an internal gateway request is made for a current variable value of a variable of the telemetry data, and transmitting the current variable value provided in response to the internal gateway request to the cloud server,

[0012] - by means of the field device communication component, performing a variable call of the current variable value from the field device at a periodic call time, and providing the cloud communication component with the current variable value called at the time of the variable call in response to the gateway request,

[0013] - Adjust the phase of the periodic call time relative to the periodic request time so that the corresponding current variable value provided by the field device communication component to the cloud communication component in response to the corresponding gateway request has been called from the field device and exists in the field device communication component at the request time of the gateway request.

[0014] Preferably, the method is performed using a gateway as described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Further exemplary details and exemplary embodiments are explained below with reference to the accompanying drawings.

[0016] Figure 1shows a schematic diagram of a system having a gateway, field devices and a cloud server,

[0017] Figure 2 shows an exemplary design of a system with a valve arrangement,

[0018] Figure 3 shows an exemplary design of a system in which a gateway is arranged on a carrier part of the valve device,

[0019] Figure 4 Two timing diagrams are shown, in which the request time and the call time are plotted,

[0020] Figure 5 shows a timing diagram that plots the time interval between the end of a variable call and a gateway request, and

[0021] Figure 6 Two timing diagrams are shown, in which the request and call times of variables of different periodicity classes are plotted. DETAILED DESCRIPTION

[0022] Figure 1 A system 100 is shown, which includes a gateway 1, a field device 2 and a cloud server 3. The system 100 is an exemplary application environment of the gateway 1. The gateway 1 can also be provided alone, that is, without the field device 2 and / or the cloud server 3. The gateway 1 is particularly designed for industrial use, such as for industrial automation. Suitably, the gateway 1 is an Internet of Things gateway. According to a possible embodiment, an industrial facility is provided, in particular an industrial manufacturing facility, which includes a gateway 1, a field device 2 and / or a cloud server 3.

[0023] The gateway 1 is used to call telemetry data from the field device 2 and transmit the called telemetry data to the cloud server 3. The telemetry data includes one or more variables that, for example, map the state of the field device 2. The one or more variables are in particular state data. For example, the variables map the engine current and / or temperature. Exemplarily, the telemetry data includes at least 10, at least 20 or at least 30 variables. The field device 2 in particular includes an actuator unit (such as a valve unit) and / or a sensor unit.

[0024] The gateway 1 includes a field device communication component 4 and a cloud communication component 5, each of which is preferably implemented as a software component. By way of example, the gateway 1 has a computer unit 6, such as a microcontroller, and the field device communication component 4 and / or the cloud communication component 5 are implemented on the computer unit 6. The field device communication component 4 controls the communication between the gateway 1 and the field device 2. The cloud communication component 5 controls the communication between the gateway 1 and the cloud server 3.

[0025] The gateway 1 is embodied in particular as a gateway module having a gateway module housing 7, in which a computer unit 6 is preferably arranged. The gateway 1 is communicatively connected to the field device 2 via a field device communication connection 8 (e.g. a bus, in particular a fieldbus). The gateway 1 is connected to the cloud server 3 via a cloud communication connection 9 (e.g. a wide area network, in particular the Internet).

[0026] For example, the gateway 1 is designed for packet-based communication with the field device 2, in particular based on TCP / IP or UDP / IP, preferably via Ethernet or via a tunnel in a field bus, such as Ethercat. In addition, the communication between the gateway 1 and the field device 2 can be carried out in parallel with Profinet, in particular without a tunnel.

[0027] The telemetry data are preferably used for pure monitoring and in particular do not include control commands. In parallel with the telemetry data, the field device 2 expediently transmits and / or receives process data, in particular control commands. Expediently, the process data and the telemetry data are transmitted via the same field device communication connection 8.

[0028] The cloud server 3 is expediently arranged at a different geographical location than the gateway 1 and / or the field device 2. The field device 2 (and optionally the gateway 1) is arranged at the field level.

[0029] The gateway 1 is particularly configured to communicate with the field device 2 according to a first communication protocol, and to communicate with the cloud server using a second communication protocol different from the first communication protocol. The gateway 1 preferably performs protocol conversion between the first communication protocol and the second communication protocol. The first communication protocol and / or the second communication protocol may be, for example, an Internet of Things communication protocol.

[0030] Figure 2 An exemplary development of a system 100 having a valve device 10 is shown. Figure 1 The explanation also applies appropriately to Figure 2 .

[0031] The valve device 10 can represent the field device 2. The valve device 10 is implemented in particular as a valve group. Exemplarily, the valve device 10 includes a carrier part 11 and a plurality of modules arranged on the carrier part 11. These modules include, for example, a control module 12 and / or an I / O module 13 and / or one or more valve modules 14. The gateway 1 obtains one or more variables in particular from the valve device 10, preferably from the control module 12, the I / O module 13 and / or one or more valve modules 14. The gateway 1 is configured to call the telemetry data from the valve device 10.

[0032] Optionally, the system 100 may further include a field device 2, which is communicatively connected to the gateway 1 via the valve device 10, in particular, via the I / O module and / or via the control module 12. The gateway 1 is configured to retrieve the telemetry data from the field device 2 via the valve device 10.

[0033] Exemplarily, the gateway 1 is not arranged on the carrier part 11. In particular, the gateway 1 is arranged at a distance from the valve device 10, in particular the carrier part 11. The gateway 1 is communicatively connected to the valve device 10, for example, via a cable.

[0034] Figure 3 Another exemplary expansion of system 100 is shown. Figure 3 In the embodiment, the gateway 1 is arranged on the carrier part 11 of the valve device 10. The gateway 1 is in particular implemented as a gateway module. In other aspects, it is suitable as Figure 2 is constructed like the previously explained system 100 shown in Figure 3 The system 100 shown in FIG.

[0035] The following should be referenced Figure 4 The cloud communication component 5 and the field device communication component 4 are discussed in more detail.

[0036] The cloud communication component 5 is configured to predetermine a periodic request time at which an internal gateway request for a current variable value of a variable of the telemetry data should be made, and to transmit the current variable value provided in response to the internal gateway request to the cloud server. Preferably, the cloud communication component 5 requests the current variable values ​​of a plurality of variables. Exemplarily, the current variable values ​​of at least two variables are requested.

[0037] The cloud communication component 5 preferably predetermines a plurality of request sequences, wherein each request sequence is assigned to a corresponding variable. Each request sequence includes a corresponding periodic request time, at which an internal gateway request for the current variable value of the assigned variable is made. Exemplarily, the cloud communication component 5 predetermines a first request sequence, which is assigned to the first variable and includes a first periodic request time AZ1, at each first periodic request time AZ1 a first internal gateway request GA1 for the current variable value of the first variable is made. In addition, the cloud communication component 5 exemplarily predetermines a second request sequence, which is assigned to the second variable and includes a second periodic request time AZ2, at each second periodic request time AZ2 a second internal gateway request GA2 for the current variable value of the second variable is made.

[0038] Preferably, the cloud communication component 5 can predetermine one or more other request sequences, which are assigned to the corresponding variables and define corresponding periodic request times, at which corresponding gateway requests for the current values ​​of the assigned variables are made. For example, the cloud communication component 5 predetermines at least 10, at least 20 or at least 30 request sequences.

[0039] Exemplarily, the gateway requests are made sequentially, in particular in such a way that directly consecutive gateway requests relate to different variables.

[0040] Preferably, the cloud communication component 5 makes a gateway request to the field device communication component 4. Alternatively or additionally, the cloud communication component 5 can provide time information in which the request time is predefined to the field device communication component 4. Based on the time information, the field device communication component 4 can make a gateway request itself.

[0041] The request moments have corresponding request periods. Exemplarily, the first request moment AZ1 has a first request period AP1 and / or the second request moment AZ2 has a second request period AP2. Exemplarily, the first request period AP1 is equal to the second request period AP2. Alternatively, the first request period AP1 may be different from the second request period AP2. Exemplarily, the second request sequence is phase-shifted relative to the first request sequence.

[0042] The field device communication component 4 is designed to provide the cloud communication component 5 with the corresponding current variable value of the corresponding variable in response to each internal gateway request GA1 , GA2 .

[0043] The cloud communication component 5 is designed to transmit the corresponding current variable value provided in response to each internal gateway request GA1 , GA2 to the cloud server 3 .

[0044] The field device communication component 4 is configured to perform a variable call VA1 for one or more current variable values ​​from the field device 2 at a periodic call time ABZ1. Each variable call VA1 includes a field device query from the gateway 1 to the field device 2. The field device query indicates one or more variables for which the field device 2 should provide one or more current variable values. Each variable call VA1 also includes a field device response from the field device 2 to the gateway 1. The field device response includes one or more current variable values. The periodic call time ABZ1 has a call period VAP1.

[0045] The field device communication component 4 is configured to provide the cloud communication component 5 with the corresponding current variable value received at the variable call VA1 in response to the corresponding gateway request. Exemplarily, the field device communication component 4 is configured to provide the cloud communication component 5 with the first current variable value of the first variable received at the variable call VA1 in response to the first gateway request GA1. In addition, the field device communication component 4 is configured to provide the cloud communication component 5 with the second current variable value of the second variable received at the variable call VA1 in response to the second gateway request GA2.

[0046] The gateway 1 is designed to adjust the phase of the periodic call time ABZ1 relative to the periodic request time AZ1, AZ2 so that the corresponding current variable value provided by the field device communication component 4 to the cloud communication component 5 in response to the corresponding gateway request GA1, GA2 has been called from the field device 2 at the gateway request time of the gateway request GA1, GA2 and is present in the field device communication component 4. The term "phase" refers in particular to the time interval or time offset between the call time ABZ1 and the first request time AZ1.

[0047] Thus, first a variable call VA1 occurs, in which the field device communication component 4 calls the current variable value of the variable from the field device 2, and only then does the cloud communication component 5 issue an internal gateway request GA1, GA2 to the field device communication component 4, which causes the field device communication component 4 to provide the called current variable value to the cloud communication component 5. By way of example, after each variable call VA1, a plurality of gateway requests GA1, GA2 are sequentially issued for the current variable value called by the variable call. This results in an overall sequence in which variable calls VA1 and sequential gateway requests GA1, GA2 are performed alternately.

[0048] Therefore, the field device communication component 4 is configured to perform a "pre-fetch" of the current variable value. The gateway 1 is preferably configured to temporarily store the called current variable value in a memory, in particular a working memory, of the gateway 1, preferably between the variable call and the gateway request. In particular, the gateway 1 is configured to cache the called current variable value.

[0049] By using a buffering method in the case of data acquisition via a field device communication connection 8 with a time delay (eg a field network), the current variable value can be ready before a corresponding gateway request is made.

[0050] The field device communication component 4 is expediently designed to provide an older variable value to the cloud communication component 5 in response to the gateway request, if the variable call has not yet been completed at the request time of the associated gateway request (for example due to a latency of the field device communication connection 8 ). The older variable value comes, for example, from a previous variable call.

[0051] The field device communication component 4 is preferably configured to determine a request cycle of a request moment and to determine a phase of a call moment and / or a call cycle based on the determined request cycle. Exemplarily, the field device communication component 4 is configured to determine the request cycle by time measurement, for example, by measuring the time interval between successive request moments of a request sequence. In particular, the gateway 1 is configured to determine the request cycle of each variable during operation by means of measurement technology.

[0052] Furthermore, the field device communication component 4 can be designed to determine the request cycle based on cycle information. The cycle information preferably includes the request cycle and is provided, for example, by the cloud communication component.

[0053] Preferably, the field device communications module 4 adjusts the request cycle VAP1 to the determined first request cycle AP1.

[0054] Preferably, the field device communication module 4 continuously determines the first request cycle AP1 and continuously adapts the phase and / or the request cycle VAP1 based on the determined first request cycle AP1.

[0055] Preferably, the gateway 1 is designed to phase-regulate the phases of the periodic call moments ABZ1. In particular, the gateway 1 is designed to regulate the phases so as to minimize the time interval ZA between the end of the corresponding variable call VA and the subsequent gateway request GA1, in response to which the current variable value called at the variable call VA is provided for transmission to the cloud server.

[0056] Preferably, the gateway 1 has a phase-locked loop, which is implemented in software, for example. The gateway 1 is particularly configured to dynamically shift the periodic call time ABZ1 using the phase-locked loop during operation, so that the time interval ZA1 is minimized. The time interval ZA1 is Figure 5 The time interval ZA1 can also be referred to as the data age of the variable value called up at the request time AZ1. The time interval ZA1 is preferably minimized to a minimum value, which is in particular greater than zero, for example 50 ms.

[0057] The field device communications module 4 is designed in particular to adjust the phases so that the call time ABZ1 occurs approximately at least a call waiting time (ie the duration of the variable call VA1 ) before the associated first request time AZ1 . The call time ABZ1 is in particular the start time of the variable call VA1 .

[0058] The following should be referenced Figure 6 A design is discussed in which the cloud communication component 5 predetermines a request sequence with different request cycles. The above explanations about the variable call of the first and second variables and the gateway request preferably correspond to the design explained below, in particular to the first and second variables and / or the third and fourth variables discussed there.

[0059] The telemetry data includes a plurality of different variables, for example, four different variables. A corresponding request sequence with a corresponding periodic request moment is assigned to each of the plurality of different variables. Exemplarily, a first request sequence with a first periodic request moment AZ1 is assigned to a first variable, a second request sequence with a second periodic request moment AZ2 is assigned to a second variable, a third request sequence with a third periodic request moment AZ3 is assigned to a third variable, and a fourth request sequence with a fourth periodic request moment AZ4 is assigned to a fourth variable.

[0060] The cloud communication component 5 is configured to make a corresponding gateway request for a corresponding current variable value at a respectively assigned request time for each variable of the plurality of different variables. Exemplarily, the cloud communication component 5 makes a first gateway request GA1 for a first current variable value at a first request time AZ1 for a first variable, makes a second gateway request GA2 for a second current variable value at a second request time AZ2 for a second variable, makes a third gateway request GA3 for a third current variable value at a third request time AZ3 for a third variable, and makes a fourth gateway request GA4 for a fourth current variable value at a fourth request time AZ4 for a fourth variable.

[0061] The request sequence includes request sequences whose request cycles are different. For example, the first request sequence is different from the third request sequence and the fourth request sequence in terms of its request cycle. In addition, the second request sequence is different from the third request sequence and the fourth request sequence in terms of its request cycle. For example, the first request sequence and / or the second request sequence has a first request cycle AP1, and the third request sequence and / or the fourth request sequence has a third request cycle AP3. The third request cycle AP3 is different from the first request cycle AP1, in particular, at least twice the first request cycle AP1.

[0062] The gateway 1 is preferably configured to classify each variable into one of a plurality of different cycle categories according to the request cycle of the respectively assigned request sequence, so that variables with the same request cycle belong to the same cycle category. The classification is preferably performed in such a way that each cycle belongs to only one cycle category.

[0063] Exemplarily, the gateway 1 classifies the first variable and / or the second variable into the first cycle category according to the first request cycle AP1. In particular, the gateway 1 determines that the first variable and the second variable have the same request cycle AP1, and classifies the first variable and the second variable into the first cycle category based on the determination.

[0064] Exemplarily, the gateway 1 classifies the third variable and / or the fourth variable into the second period category according to the third request period AP3. In particular, the gateway 1 determines that the third variable and the fourth variable have the same request period AP1, and classifies the third variable and the fourth variable into the second period category based on the determination.

[0065] The gateway 1 classifies variables with different request periods into different period categories. Therefore, the gateway 1 classifies the first variable and / or the second variable into a period category different from that of the third variable and / or the fourth variable.

[0066] The gateway 1 is preferably designed to continuously monitor the request cycle, in particular during operation, and to reclassify the associated variables when the request cycle changes. If the request cycle of a variable changes, the variable is classified into different cycle categories.

[0067] The field device communication component 4 is preferably constructed to call the current variable value of the variable of the same cycle category from the field device 2 by means of a public variable call. Preferably, the public variable call is carried out within the scope of block transmission. Thus, a reduction in waiting time can be achieved compared to the sum of the waiting times of the individual calls. For example, the public variable call is carried out by outputting a field device query to the field device 2 by the field device communication component, wherein the field device query indicates multiple variables of the same cycle category. The public field device query is, for example, a data telegram and / or a data packet. Exemplarily, in response to the public field device query, the field device 2 transmits a public field device response, in which the current variable values ​​of multiple variables of the same cycle category are contained in the public field device response. The public field device response is, for example, a data telegram and / or a data packet. The above-mentioned data packet of the field device query and / or the field device response is particularly a packet of the 5th to 7th layers of the OSI model. For example, the data packet is a sub-packet of a TCP / IP packet.

[0068] The field device communication module 4 preferably performs its own variable call for each cycle class. In particular, for each cycle class, its own public field device query and / or its own public field device response is performed.

[0069] By way of example, the field device communication module 4 uses its own call cycle to execute the variable call of each cycle class. Preferably, the call cycle is the same as the request cycle of the corresponding cycle class.

[0070] The field device communication module 4 is designed in particular to perform a dedicated variable call for each cycle class, so that the current variable values ​​of variables of different cycle classes are called from the field device 2 by means of different variable calls. The field device communication module 4 preferably performs a variable call for each cycle class at a corresponding call time. Each cycle class is assigned its own call time.

[0071] By way of example, the field device communication module 4 calls the current variable values ​​of the variables of the first cycle category by means of the first common variable call VA1, which is respectively carried out at the first call time ABZ1. With each first common variable call VA1, the current variable values ​​of all variables of the first cycle category are called. The first common variable call VA1 is carried out with a first call cycle VAP1, which is in particular equal to the first request cycle AP1. Preferably, in each first common variable call VA1, the variable values ​​of the variables that do not belong to the first cycle category are not called.

[0072] By way of example, the field device communication component 4 calls the current variable values ​​of the variables of the second cycle category by means of the second common variable call VA2, which is respectively performed at the second call time ABZ2. With each second common variable call VA2, the current variable values ​​of all variables of the second cycle category are called. The second common variable call VA2 is performed with a second call cycle VAP2, which is in particular equal to the third request cycle AP3. The second call cycle VAP2 is different from the first call cycle VAP1, in particular at least twice the first call cycle. Preferably, in each second common variable call VA2, the variable values ​​of the variables that do not belong to the second cycle category are not called.

[0073] Corresponding to the first and second cycle categories discussed above, there may also be one or more other cycle categories, and thus other common variable calls with corresponding call cycles.

[0074] Exemplarily, after each variable call, multiple gateway requests for the current variable value called with the variable call are sequentially made. After each first variable call VA1, a first and a second gateway request GA1, GA2 are sequentially made. After each second variable call VA2, a third and a fourth gateway request GA3, G4 are sequentially made.

[0075] The field device communications module 4 is preferably designed to adjust the corresponding call cycle for each cycle class, in particular to the request cycle of the assigned request sequence.

[0076] The field device communications module 4 is expediently designed to adjust the respective phase of the call time relative to the request time for each cycle class.

[0077] Preferably, the field device communications module 4 continuously determines the request cycle and continuously adapts the phase and / or the call cycle based on the determined request cycle.

[0078] The gateway 1 is preferably configured to perform a phase adjustment of the phase of the periodic call moment for each cycle category. In particular, the gateway 1 is configured to adjust the phase for each cycle category so as to minimize the time interval between the end of the corresponding variable call and the subsequent gateway request, in response to which the current variable value called at the time of the variable call is provided for transmission to the cloud server. Exemplarily, the gateway adjusts the phase of the first periodic call moment ABZ1 so that the first time interval ZA1 between the end of the corresponding first variable call VA1 and the subsequent first gateway request GA1 is minimized. Exemplarily, the gateway adjusts the phase of the second periodic call moment ABZ2 so that the second time interval ZA2 between the end of the corresponding second variable call VA1 and the subsequent third gateway request GA3 is minimized.

[0079] Preferably, the request cycle and / or call cycle of these cycle categories is an integer multiple of a minimum cycle configured in particular in the gateway 1. The minimum cycle may also be referred to as cycle resolution. The minimum cycle is, for example, 50 ms.

Claims

1. A gateway (1) for calling up telemetry data from a field device (2) and for transmitting the called up telemetry data to a cloud server (3), wherein the gateway (1) comprises a cloud communication component (5), the cloud communication component being configured to predetermine a periodic request time (AZ1, AZ3, AZ3, AZ4), to make an internal gateway request (GA1, GA2, GA3, GA4) for a current variable value of a variable of the telemetry data at the periodic request time, and to transmit the current variable value provided in response to the internal gateway request (GA1, GA2, GA3, GA4) to the cloud server (3), and a field device communication component (4), the field device communication component being configured to make a variable call (V) for the current variable value from the field device (2) at the periodic call time (ABZ1, ABZ2). A1, VA2), and in response to the gateway request (GA1, GA2, GA3, GA4), provides the cloud communication component (5) with the current variable value received at the time of the variable call (VA1, VA2), wherein the gateway (1) is constructed to adjust the phase of the periodic call time (ABZ1, ABZ2) relative to the periodic request time (AZ1, AZ2, AZ3, AZ4), so that the corresponding current variable value provided by the field device communication component (4) to the cloud communication component (5) in response to the corresponding gateway request (GA1, GA2, GA3, GA4) has been called from the field device (2) and exists in the field device communication component (4) at the request time (AZ1, AZ2, AZ3, AZ4) of the gateway request (GA1, GA2, GA3, GA4), wherein The gateway (1) is constructed to perform phase adjustment on the phase of the periodic call time (ABZ1, ABZ2) and minimize the time interval (ZA1, ZA2) between the end of the corresponding variable call (VA1, VA2) and the subsequent gateway request (GA1, GA3) by the phase adjustment, and provide the current variable value called at the time of the variable call for transmission to the cloud server in response to the gateway request, wherein the phase is the time offset between the periodic call time (ABZ1, ABZ2) and the periodic request time (AZ1, AZ2, AZ3, AZ4).

2. The gateway (1) according to claim 1, wherein: The field device communication component (4) is constructed to determine a request cycle (AP1, AP2, AP3) of the request time (AZ1, AZ2, AZ3, AZ4) and to determine a phase and / or a call cycle (VAP1, VAP2) of the call time (ABZ1, ABZ2) based on the determined request cycle (AP1, AP2, AP3).

3. The gateway (1) according to claim 1 or 2, wherein: The telemetry data comprises a plurality of different variables, and a corresponding request sequence with a corresponding periodic request time (AZ1, AZ2, AZ3, AZ4) is assigned to each of the plurality of different variables, and wherein the cloud communication component (5) is constructed to make a corresponding gateway request (GA1, GA2, GA3, GA4) for the corresponding current variable value at the respectively assigned request time (AZ1, AZ2, AZ3, AZ4) for each of the plurality of different variables.

4. The gateway (1) according to claim 3, wherein: The request sequence has different request periods (AP1, AP2, AP3).

5. The gateway (1) according to claim 4, wherein: The gateway (1) is constructed to classify each variable into one of a plurality of different cycle categories according to the request cycle (AP1, AP2, AP3) of the respectively assigned request sequence, so that variables with the same request cycle (AP1, AP2, AP3) belong to the same cycle category.

6. The gateway (1) according to claim 5, wherein: The field device communications module (4) is designed to call up current variable values ​​of variables of the same cycle class from the field device by means of a common variable call (VA1, VA2).

7. The gateway (1) according to claim 5 or 6, wherein: The field device communication module (4) is designed to execute a separate variable call (VA1, VA2) for each cycle class, so that current variable values ​​of variables of different cycle classes are called from the field device (2) by means of different variable calls (VA1, VA2).

8. The gateway (1) according to any one of the preceding claims, wherein: The gateway (1) is designed as a gateway module having a gateway module housing (7).

9. A system (100) comprising a valve device (10) and a gateway (1) according to any one of claims 1 to 8, wherein the gateway (1) is configured to call telemetry data from the valve device (15) and / or via the valve device (15).

10. The system (100) according to claim 9, characterized in that The valve device (10) comprises a carrier part (11) and a plurality of modules (12, 13, 14) arranged on the carrier part.

11. A method for operating a gateway (1) for calling telemetry data from a field device (2) and transmitting the called telemetry data to a cloud server (3), the method comprising the following steps: - by means of the cloud communication component (5) of the gateway, a periodic request time (AZ1, AZ2, AZ3, AZ4) is specified at which an internal gateway request (GA1, GA2, GA3, GA4) for a current variable value of a variable of the telemetry data is to be made, and the current variable value provided in response to the internal gateway request (GA1, GA2, GA3, GA4) is transmitted to the cloud server (4), - using the field device communication component (4), at a periodic call time (ABZ1, ABZ2), a variable call (VA1, VA2) is made from the field device (2) for the current variable value, and in response to the gateway request (GA1, GA2, GA3, GA4), the current variable value called at the time of the variable call (VA1, VA2) is provided to the cloud communication component (5), - adjusting the phase of the periodic call time (VA1, VA2) relative to the periodic request time (GA1, GA2, GA3, GA4) so ​​that the corresponding current variable value provided by the field device communication component (4) to the cloud communication component (5) in response to the corresponding gateway request (GA1, GA2, GA3, GA4) has been called from the field device (2) and is present in the field device communication component (4) at the request time (AZ1, AZ2, AZ3, AZ4) of the gateway request (GA1, GA2, GA3, GA4), wherein ... to the cloud communication component (5) by the field device communication component (4) in response to the corresponding gateway request (GA1, GA2, GA3, GA4) is provided to the cloud communication component (5) The phase of the periodic call moment (ABZ1, ABZ2) is phase-regulated and the time interval (ZA1, ZA2) between the end of the corresponding variable call (VA1, VA2) and the subsequent gateway request (GA1, GA3) is minimized by the phase regulation, and the current variable value called at the time of the variable call is provided in response to the gateway request for transmission to the cloud server, wherein the phase is the time offset between the periodic call moment (ABZ1, ABZ2) and the periodic request moment (AZ1, AZ2, AZ3, AZ4).

Images