Aggregator device for standardized access to multiple network segments of fieldbus systems

Abstract

A description is given of an aggregator device designed to form a plurality of first data connections to a plurality of field access devices, wherein the field access devices are connected to a plurality of different network segments of a fieldbus system. The aggregator device is designed to form at least one second data connection to at least one host computer. The aggregator device is designed to receive first data traffic from the at least one host computer via at least one second data connection and to forward the first data traffic via at least one of the first data connections to the field access device of the network segment in which the specific fieldbus component to which the first data traffic is directed is located. The aggregator device is also designed to receive second data traffic from the fieldbus component in one of the network segments via at least one of the first data connections and to forward the second data traffic to at least one of the host computers via at least one second data connection.

Description

Technical Field

[0001] The present invention relates to an aggregator device and a fieldbus system comprising a plurality of network segments and the aggregator device. Background Art

[0002] Field devices for acquiring and / or influencing process variables are often used in automation technology. Examples of such field devices are level measuring devices, mass flow meters, pressure and temperature measuring devices, etc., which as sensors detect the corresponding process variables of level, flow rate, pressure and temperature.

[0003] Many fieldbus systems consist of a number of separate network segments that are managed separately from one another. Such a division increases the reliability of the entire system, since in the event of a fault only one network segment will be affected and the other network segments remain operational. A disadvantage of such fieldbus systems is that the access rights to the host computers of the individual network segments must be established separately. Summary of the invention

[0004] The object of the invention is to simplify access to individual network segments in a fieldbus system having a plurality of network segments.

[0005] This object is achieved by the features indicated in claims 1 and 9 .

[0006] Advantageous developments of the invention are indicated in the dependent claims.

[0007] The aggregator device according to an embodiment of the present invention is designed to form a plurality of first data connections to a plurality of field access devices, wherein the field access devices are connected to a plurality of different network segments of a fieldbus system. The aggregator device is designed to form at least one second data connection to at least one host computer. The aggregator device is designed to receive a first data service from at least one host computer via at least one of the second data connections, and to forward the first data service via at least one of the first data connections to a field access device of a network segment in which a specific fieldbus component to which the first data service is directed is located. The aggregator device is also designed to receive a second data service from a fieldbus component in one of the network segments via at least one of the first data connections, and to forward the second data service to at least one of the host computers via at least one of the second data connections.

[0008] The aggregator device of the present invention provides centralized access to network segments of a segmented fieldbus system. During operation, the aggregator device is connected to a field access device via a first data connection and to a host computer via at least one second data connection. Data traffic directed by the host computer to a specific fieldbus component is routed by the aggregator device to the field access device of the network segment where the specific fieldbus component is located. The fieldbus component can be a field device, a gateway device, or another fieldbus component. Conversely, the aggregator device receives data traffic from the fieldbus components in the network segment and forwards the data traffic to at least one host computer. The aggregator device provides the host computer with centralized access to the field access devices of various network segments. The individual network segments can be arranged at the same location, but can also be arranged at multiple locations separated from each other.

[0009] The use of an upstream aggregator device reduces the administrative effort in a fieldbus system comprising a plurality of fieldbus segments. Previously, it was necessary to register a host computer on each field access device separately and to configure a firewall on each field access device so that the host computer was allowed to access a specific network segment. Since many service technicians are granted access rights to the host computers of the various network segments of their fieldbus system, the administrative effort is considerable. In contrast, in the solution according to the invention, each host computer is registered centrally only once at the aggregator device. For example, a firewall can be set up on the aggregator device and then configured so that a specific host computer can access the aggregator device and therefore also all field access devices of the network segment. Alternatively, access rights can also be granted to a host computer or user only for a specific network segment and / or a specific fieldbus component and / or a specific function of a fieldbus component. Such access rights can be established, for example, with the aid of an authorization profile created for a specific host computer or a specific user. Since specific access rights only need to be established centrally once on the aggregator device, the administrative effort will be significantly less than in previous solutions. Since all configuration changes are made, for example, only at the central firewall, instead of at many decentralized firewalls as before, the security standards are also improved, and thus the transparency is improved.

[0010] For a service technician seeking to access a specific fieldbus component within a fieldbus system via his host computer, access to this fieldbus component is simplified due to the presence of the aggregator device. The first data service received from the host computer is automatically routed by the aggregator device to the field access device of the network segment in which the addressed fieldbus component is located. The service technician thus only has to select the desired fieldbus component via the field access software of his host computer. The service technician does not have to deal with the issue of the network segment in which a specific fieldbus component is located, because the routing is automatically performed by the aggregator device. This is particularly advantageous in the case of extensive automation networks comprising multiple field devices, gateway devices and other fieldbus components. Thus, standardized access to all fieldbus components of the entire fieldbus system is possible from the host computer.

[0011] It is advantageous if the first data service is a data service for parameterization, configuration and status monitoring of fieldbus components. Parameters of a specific fieldbus component can be read and modified by the host computer. Preferably, the second data service comprises at least one parameter value of a specific fieldbus component.

[0012] Preferably, the routing information is stored on a part of the aggregator device. For example, such routing information indicates to which network segment the first data traffic directed to a specific fieldbus component must be routed. This enables the aggregator device to automatically route the first data traffic received from the host computer to the network segment where the specific fieldbus component is located.

[0013] A fieldbus system according to an embodiment of the present invention comprises a plurality of network segments, wherein each network segment comprises at least one field access device, at least one fieldbus and at least one fieldbus component. At least one field access device is designed to allow access to the fieldbus components in a particular network segment. In addition, the fieldbus system comprises an aggregator device as described above, which is designed to form a plurality of first data connections to at least some of the field access devices in different network segments. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In the following, the invention is outlined in more detail with the aid of exemplary embodiments depicted in the drawings. The drawings show:

[0015] Figure 1 A fieldbus system comprising a plurality of network segments is shown, wherein the network segments comprise field access devices via which fieldbus components in the respective network segments can be accessed;

[0016] Figure 2 A fieldbus system comprising a plurality of network segments is shown, wherein access to field access devices in each network segment is provided via an upstream aggregator box;

[0017] Figure 3 A host computer is shown having device access software installed thereon, wherein the device access software provides a plurality of driver structures for accessing different network segments. DETAILED DESCRIPTION

[0018] In modern industrial plants, different functional areas are often covered by several separate network segments. The division of fieldbus systems into separate network segments is mainly done for organizational reasons, for example in order to map the modular structure of an industrial plant or to clearly define the responsibilities of different network segments. In addition, the reliability of the entire system is increased by the division into several separate network segments. For example, if a specific automation network fails, this failure will only affect one part of the plant, while the rest of the industrial plant remains operational.

[0019] Figure 1 A fieldbus system 1 is shown which comprises three different network segments 2-1, 2-2 and 2-3. In the first network segment 2-1 a field access device 3-1 is arranged, via which the fieldbus components of the first network segment 2-1 can be accessed from a host computer. The field access device 3-1 is connected to a fieldbus 4, wherein two field devices 5 and 6 and a gateway device 7 are also connected to the fieldbus 4. Connected to the gateway device 7 are two field devices 8 and 9.

[0020] The second network segment 2-2 comprises a field access device 3-2 via which fieldbus components of the second network segment 2-2 can be accessed. The field access device 3-2 is connected to a fieldbus 10, wherein two field devices 11 and 12 are also connected to the fieldbus 10.

[0021] The third network segment 2-3 comprises a field access device 3-3 via which the fieldbus components of the third network segment 2-3 can be accessed. The field access device 3-3 is connected to a fieldbus 13 to which two field devices 14 and 15 are also connected.

[0022] In this regard, a separate field access device 3-1, 3-2, 3-3 is provided for each of the three network segments 2-1, 2-2 and 2-3. For parameterization, configuration and status monitoring of fieldbus components within a specific network segment 2-1, 2-2, 2-3, an external host computer 16 can access specific fieldbus components within the network segment via the specific field access device 3-1, 3-2, 3-3.

[0023] The parameterization, configuration and status monitoring of the field devices of the fieldbus network are performed by means of device access software installed on the host computer 16. The device access software can be, for example, a frame application according to one of the standards FDT, FDT2, FDI device packages, OPC unified architecture, etc., into which the drivers required for the various fieldbus components can be integrated. The various fieldbus components of the network segments 2-1, 2-2, 2-3 can be accessed via the device access software. In particular, the parameters of the individual components of the network segments 2-1, 2-2, 2-3 can be read, presented and modified from the device access software. In addition, the device access software allows status monitoring (condition monitoring) of the components of the network segments 2-1, 2-2, 2-3. The data exchange required for these tasks is usually handled via so-called non-periodic data services.

[0024] However, in order to be able to access the various fieldbus segments 2-1, 2-2, 2-3 from the host computer 16, the host computer 16 must be registered on each field access device 3-1, 3-2, 3-3. In particular, the firewalls 17-1, 17-2, 17-3 installed on the field access devices 3-1, 3-2, 3-3, respectively, must be configured so that the host computer 16 is allowed to access specific network segments and is not blocked by the firewall. However, in addition to the host computer 16, a plurality of other host computers 18, 19 are usually used, wherein the host computers can be, for example, stationary computers, but also portable computers, mobile devices, tablet computers or smartphones. Since each service technician usually has his own host computer for parameterization, configuration and status monitoring of field devices, a plurality of different host computers 16, 18, 19 must be granted access to the network segments 2-1, 2-2, 2-3. In order to reliably prevent unauthorized access to a network segment, the configuration of a specific firewall 17-1, 17-2, 17-3 must therefore always be kept up-to-date and adapted to the host computers 16, 18, 19 currently in use. In this respect, the segmentation of an automation system into a plurality of network segments 2-1, 2-2, 2-3 results in a great deal of management effort. In practice, this can lead, for example, to the security measures being completely deactivated by the manufacturer or not being implemented at all.

[0025] In the solution according to the invention it is proposed to provide an aggregator box which is connected upstream of the field access devices 3-1, 3-2, 3-3 and which allows the host computer to standardize the access to the various network segments. Figure 2A fieldbus system 20 comprising such an aggregator box 21 is shown. The aggregator box 21 is connected to a field access device 3-1 of a first network segment 2-1 via a data connection 22-1, to a field access device 3-2 of a second network segment 2-2 via a data connection 22-2, and to a field access device 3-3 of a third network segment 2-3 via a data connection 22-3. Preferably, the data connections 22-1, 22-2, 22-3 between the aggregator box 21 and the field access devices 3-1, 3-2, 3-3 are implemented as Ethernet connections. Each of the data connections 22-1 to 22-3 can be configured as a wired data connection or a wireless data connection. Some data connections can be configured as wired data connections and others as wireless data connections.

[0026] Additionally, one or more host computers 16, 18, 19 may be connected to the aggregator box 21. Figure 2 In the example shown, the aggregator box 21 is connected to the host computer 16 via a data connection 23, wherein the data connection 23 may preferably be a wired or wireless Ethernet connection. The host computer 16 may be used to access fieldbus components in any of the three network segments 2-1, 2-2, 2-3 via the aggregator box 21. In this way, parameterization or configuration of field devices, gateway devices and other fieldbus components in the three network segments 2-1, 2-2, 2-3 may be performed by the host computer 16, for example. In addition, the device status and selected parameters of the field devices, gateway devices and other fieldbus components in the three network segments 2-1, 2-2, 2-3 may be queried from the host computer 16 and displayed to the user.

[0027] In the following, it will be discussed how to access a specific fieldbus component of one of the network segments 2-1, 2-2, 2-3 from the host computer 16, for example in order to parameterize the fieldbus component. For this purpose, the host computer 16 sends data traffic addressed to the specific fieldbus component to the aggregator box 21 via the data connection 23. This data traffic is addressed, for example, to the field device 5 in the first network segment 2-1. A routing device 24 is provided on a part of the aggregator box 21, in which routing information 25 is kept available. The routing information 25 indicates to which network segment 2-1, 2-2, 2-3 the data traffic directed to the specific fieldbus component must be forwarded. Based on this routing information 25, the routing device 24 of the aggregator box 21 can find out that the field device 5 is located in the first network segment 2-1, so that the data traffic received from the host computer 16 must be routed to the first network segment 2-1. In this regard, the routing device 24 transmits the data traffic to the field access device 3-1 via the data connection 22-1 and from there to the field device 5. In Figure 2This data transmission is illustrated in FIG by arrow 26. Preferably, the data connections 23 and 22-1 are designed as Ethernet connections, so that data traffic can be transmitted in the form of Ethernet packets from the host computer 16 via the aggregator box 21 to the field access device 3-1.

[0028] In the opposite direction, data traffic can be transmitted from the field device 5 via the field access device 3-1 of the first network segment 2-1 and via the data connection 22-1 to the aggregator box 21. The aggregator box 21 receives the data traffic and forwards it to the host computer 16 via the data connection 23. Figure 2 This data traffic is shown in FIG. 1 by arrow 27. Preferably, the data is again transmitted in the form of Ethernet data traffic from the field device 5 via the aggregator box 21 to the host computer 16. On a part of the host computer 16, for example, the parameter values ​​received from the field device 5 can be presented to a user by means of device access software.

[0029] In the case where multiple host computers are connected to the aggregator box 21, the aggregator box 21 preferably forwards data traffic received from the fieldbus component only to the host computer or those host computers to which the data traffic is intended. Typically, the data traffic received from the fieldbus component is a response to a request from a specific host computer. In this case, the aggregator box 21 only forwards the data traffic received from the fieldbus component to the host computer that initiated the request. The information required to be able to associate the response with the request remains available on a portion of the aggregator box 21. Alternatively, however, the data traffic received from the field access device may also be related to an event related to one or more host computers, for example. In this case, the aggregator box 21 forwards the received data traffic to all those host computers related to the specific event.

[0030] The advantage of providing an aggregator box 21 is that it is only necessary to register the various host computers 16, 18, 19 on the aggregator box 21. A firewall 28 is provided on a portion of the aggregator box 21 and is designed to prevent unauthorized access to the automation network. Therefore, the firewall 28 must be configured to allow access to the individual network segments 2-1, 2-2, 2-3 from any one of the host computers 16, 18, 19. However, the access authorization may also be limited to specific pre-specifiable network segments 2-1, 2-2, 2-3 or specific pre-specified fieldbus components or specific functions of fieldbus components. For this purpose, the aggregator box 21 may, for example, store an authorization profile for a specific host computer 16, 18, 19 or for a specific user, which authorization profile individually establishes access authorization for a specific host computer or user to a specific network segment and / or a specific fieldbus component and / or a specific function of a fieldbus component.

[0031] In this case, it is no longer necessary to register the host computer 16, 18, 19 on each field access device 3-1, 3-2, 3-3. Since access to the automation network is centrally performed via the aggregator box 21, it is not necessary to perform access control on a portion of the field access devices 3-1, 3-2, 3-3. Since access is centrally controlled via the firewall 28 installed on the aggregator box 21, it is not absolutely necessary to provide this firewall on the field access device 3-1, 3-2, 3-3 in each case, which means that it can be omitted. Figure 1 However, alternatively, the firewalls on the field access devices 3-1, 3-2, 3-3 may also be retained.

[0032] Furthermore, other additional functionalities may be provided in the interaction between the field access devices 3-1, 3-2, 3-3 and the aggregator box 21. For example, at least one of the field access devices 3-1, 3-2, 3-3 may be designed to indicate to the aggregator box 21 that a particular field access device is operational and access to a particular network segment 2-1, 2-2, 2-3 is possible according to a pre-specified schedule, preferably at regular time intervals.

[0033] According to another embodiment, provision can be made that the field access devices 3-1, 3-2, 3-3 acquire data about the device status and device health (“asset health”) of the fieldbus components located in a specific network segment 2-1, 2-2, 2-3 and transmit them according to a pre-specified schedule—preferably at regular time intervals—to the aggregator box 21. The information about the device status can then be displayed to a user, who is connected to the aggregator box 21 via his host computer 16, in an overview of all network segments 2-1, 2-2, 2-3 of the entire fieldbus system 20. Based on the overall view of the fieldbus system 20, the user can then decide which parameters he wants to query from the individual field devices, gateway devices and other fieldbus components and possibly modify them.

[0034] Before data can be exchanged between the aggregator box 21 and the field access devices 3-1, 3-2, 3-3 via the data connections 22-1, 22-2, 22-3, the aggregator box 21 and the field access devices 3-1, 3-2, 3-3 must mutually identify each other and exchange their device identifiers so that the data traffic in question can be routed to the respective other communication participants. Various possibilities are described below as to how the aggregator box 21 and the field access devices 3-1, 3-2, 3-3 can mutually identify each other and exchange their device identifiers.

[0035] According to the first option, the device identifiers of the field access devices 3-1, 3-2, 3-3 are stored in advance in the aggregator box 21. For example, the device identifiers of the connected field access devices 3-1, 3-2, 3-3 can be manually input to the aggregator box 21. Then, the aggregator box 21 can identify itself to the field access devices 3-1, 3-2, 3-3 and transmit its own device identifier to the field access devices 3-1, 3-2, 3-3. In this way, the aggregator box 21 and the field access devices 3-1, 3-2, 3-3 can mutually inform each other of their device identifiers. In the case of Ethernet connection, for example, the IP addresses of the field access devices 3-1, 3-2, 3-3 and the aggregator box 21 are used as device identifiers.

[0036] According to a second option, provision can be made for the device identifier of the aggregator box 21 to be stored in each case by the field access device 3-1, 3-2, 3-3. For example, it can be specified in each field access device 3-1, 3-2, 3-3 that the data exchange with the host computer is to be routed via the aggregator box 21 whose device identifier is stored in the field access device 3-1, 3-2, 3-3. For example, the device identifier of the aggregator box 21 can be manually entered into the field access device in advance. The field access device 3-1, 3-2, 3-3 can then identify itself to the aggregator box 21 and transmit its own device identifier to the aggregator box 21 in each case. In this way, the aggregator box 21 and the field access devices 3-1, 3-2, 3-3 can mutually inform each other of their device identifiers. In the case of an Ethernet connection, for example, the IP addresses of the field access devices 3-1, 3-2, 3-3 and the aggregator box 21 are used as device identifiers.

[0037] According to another option, it can be provided that the field access devices 3-1, 3-2, 3-3 send broadcast messages according to a pre-specified schedule, preferably at regular intervals, wherein the device identifier of the specific field access device is indicated in the broadcast message. The aggregator box 21 receives the broadcast messages of the field access devices 3-1, 3-2, 3-3 and retrieves the specific device identifier of the field access devices 3-1, 3-2, 3-3 connected to the aggregator box 21 from the broadcast messages. In a next step, the aggregator box 21 can identify itself to the field access devices 3-1, 3-2, 3-3 and transmit its own device identifier to the field access devices 3-1, 3-2, 3-3. Based on the broadcast messages of the field access devices 3-1, 3-2, 3-3, the aggregator box 21 and the field access devices 3-1, 3-2, 3-3 inform each other of their device identifiers. In the case of an Ethernet connection, for example, the IP addresses of the field access devices 3-1, 3-2, 3-3 and the aggregator box 21 are used as device identifiers.

[0038] According to another option, the aggregator box 21 can be designed to send broadcast messages according to a pre-specified schedule and preferably at regular intervals, wherein the device identifier of the aggregator box 21 can be indicated in the broadcast messages. These broadcast messages will then be received by the field access devices 3-1, 3-2, 3-3, so that the field access devices 3-1, 3-2, 3-3 are informed of the device identifier of the aggregator box 21. The field access devices 3-1, 3-2, 3-3 can then identify themselves to the aggregator box 21 with the specification of their own device identifier. Based on the broadcast messages of the aggregator box 21, the aggregator box 21 and the field access devices 3-1, 3-2, 3-3 mutually inform each other of their device identifiers. In the case of an Ethernet connection, for example, the IP addresses of the field access devices 3-1, 3-2, 3-3 and the aggregator box 21 are used as device identifiers.

[0039] According to a preferred embodiment of the present invention, a setting element may be provided on a portion of at least one of the field access devices 3-1, 3-2, 3-3 and may selectively cause it to enter a first setting or a second setting. If the setting element is in the first setting (hereinafter referred to as "true"), this means that an aggregator box 21 is provided in the automation network and data exchange with at least one host computer will be routed via the aggregator box 21. On the other hand, if the setting element is in the second setting (hereinafter referred to as "false"), this means that no aggregator box is provided in the automation network, so that data exchange will be performed directly between at least one host computer and a specific field access device.

[0040] The setting element may be, for example, a setting element implemented in hardware. For example, the setting element may be one of the following: a switch element, a changeover switch, a changeover element, a dip switch, a configuration element, a plug-in element, a plug, a jumper, a plug-in bridge, a short-circuit plug.

[0041] When the setting element is in the first setting "true", the field access devices 3-1, 3-2, 3-3 are connected to the aggregator box 21 via the data connections 22-1, 22-2, 22-3. For data exchange, the field access devices 3-1, 3-2, 3-3 and the aggregator box 21 must then exchange their device identifiers, i.e., for example, their IP addresses, with each other. For this purpose, one option is that the device identifier of the aggregator box 21 is pre-stored in each field access device 3-1, 3-2, 3-3 so that each field access device 3-1, 3-2, 3-3 can identify itself to the aggregator box 21.

[0042] Alternatively, it can be provided that the name of the aggregator box 21 to which the data traffic is subsequently addressed is generated on a part of each field access device 3-1, 3-2, 3-3 according to a pre-specified formation scheme. This name can be formed, for example, based on the local domain name in which the three field access devices 3-1, 3-2, 3-3 of the automation network are located. When the field access devices 3-1, 3-2, 3-3 are registered in a specific local network, an IP address will be assigned to the field access device by the DHCP server of the network, wherein within the framework of this DHCP assignment, the local domain name with which the field access device has been registered is transmitted to the field access device. Within a company, the local domain name can, for example, be a specific company domain name, for example a domain name such as "examplecompany.com". Based on this local domain name, the name of the aggregator box 21 to which the data traffic is subsequently addressed can then be formed by adding further name parts. Thus, the name of the aggregator is generated by means of a pre-specified formation rule based on the local domain name. For example, the name part "aggregator" and a separator can be connected to the local domain name "examplecompany.com" to form the name "aggregator.examplecompany.com". This name "aggregator.examplecompany.com" is then used by a specific field access device 3-1, 3-2, 3-3 to address data traffic to the aggregator box 21. The name "aggregator.examplecompany.com" can be converted to the IP address of the aggregator box 21 during operation with the help of a DNS server. The advantage of this process is that a name suitable for addressing the aggregator box 21 can be generated with the help of pre-specified formation rules on all field access devices 3-1, 3-2, 3-3 in a consistent manner based on the local domain name. In this embodiment, there is no need to pre-store the device identifier or IP address of the aggregator box 21 in the field access devices 3-1, 3-2, 3-3.

[0043] In order for the aggregator box 21 to be able to route data traffic received from the host computer 16 to the fieldbus components to which the data traffic is intended, it is necessary to know on a part of the routing device 24 which field devices, gateway devices and other fieldbus components are present in the respective network segments 2-1, 2-2, 2-3. Therefore, routing information 25 is stored in the routing device 24 and indicates, at least for a part of the fieldbus components, the associated network segments in which the fieldbus components are located. Preferably, the routing information 25 indicates for each fieldbus component the associated network segments in which the fieldbus components are located. In addition, information on the topology within the network segments may optionally be kept available.

[0044] The information required by the aggregator box 21 is determined by the field access devices 3-1, 3-2, 3-3 of the network segments 2-1, 2-2, 2-3, for example by the specific field access device performing a topology scan of the specific network segment. Such a topology scan may be performed automatically, for example, by the specific field access device 3-1, 3-2, 3-3 at a pre-specified time or at pre-specified time intervals. Alternatively, such a topology scan may be started from the aggregator box 21. When performing a topology scan, the specific field access device determines the hierarchical structure of fieldbus segments, field devices, gateway devices and other fieldbus components within the fieldbus network 2-1. For example, the field access device 3-1 will determine that field devices 5 and 6 and gateway device 7 are connected to the fieldbus 4, wherein two field devices 8 and 9 are connected to the gateway device 7. Subsequently, the topology information for the network segment 2-1 determined by the field access device 3-1 is transmitted from the field access device 3-1 to the aggregator box 21, for example in the form of a file 29-1. A topology scan of the associated network segment 2-2 or 2-3 is also performed by the field access devices 3-2 and 3-3, and the topology information thus determined is transmitted from the particular field access device 3-2, 3-3 to the aggregator box 21 in the form of files 29-2, 29-3. The topology information contained in the files 29-1, 29-2, 29-3 is used as a basis for processing and providing routing information 25. The routing device 24 uses this routing information as a basis for routing data traffic received from the aggregator box 21 to the correct network segment. Thus, the routing information 25 may contain topology information for the network segment 2-1, 2-2, 2-3, which is determined in the context of the topology scan.

[0045] However, it is not absolutely necessary for the routing of data traffic that the routing information 25 contains complete topology information for network segments 2-1, 2-2, and 2-3. In this regard, it can be provided according to an alternative preferred solution that the routing information 25 is the allocation information that allocates the fieldbus components to each network segment. The allocation information indicates at least a part of the fieldbus components of the network segment to which a specific fieldbus component is allocated. For example, the routing information 25 can indicate the associated network segment of each device identifier of the fieldbus component to which the data traffic can be directed. Based on this, the routing device 24 can determine which network segment the data traffic addressed to the specific fieldbus component must be routed to. The allocation information can also be configured, for example, so that it indicates which fieldbus components are located in the network segment for each network segment. Such allocation information is sufficient to enable data traffic to be routed to the correct network segment.

[0046] Therefore, the advantage of using the aggregator box 21 is that data traffic received from the host computer 16 is automatically routed to the correct network segment and the correct destination address. A user who wishes to access a particular field device via his host computer, such as a portable computer, therefore does not have to deal with the issue of arranging the network segment for that particular field device.

[0047] Figure 3 Schematically shown in FIG. 1 is a host computer 16 on which the device access software 30 is installed. Information on the properties and parameters of field devices, gateways, remote I / Os, etc., required by the device access software 30 is usually provided by the manufacturers of the different devices in the form of device description files or device drivers. With Profibus-DP, Profibus-PA, Fieldbus Foundation and HART fieldbus protocols, for example, device descriptions according to the DTM (Device Type Manager), DD (Device Description), EDD (Enhanced Device Description) and FDI device package standards are used.

[0048] In the FDT / DTM standard, DTM (Device Type Manager) is provided in the form of a dynamically loadable library (DLL) or an executable file (executable file). Various DTMs for various components of the fieldbus network are integrated into a general FDT framework application, wherein FDT stands for "field device tool". Thus, a general framework application is provided, into which DTMs for various devices and from different manufacturers can be integrated. The FDT2 standard is introduced as a successor standard to FDT. In addition, the FDI device package standard has been established as a successor standard to FDT and EDD, wherein FDI stands for "field device integration". In addition to the Profibus, Fieldbus Foundation and HART fieldbus protocols discussed above, related thereto are the so-called industrial Ethernet protocols, which include EtherNet / IP, PROFINET and EtherCAT fieldbus protocols, etc. In the EtherNet / IP fieldbus protocol, a device description file corresponding to the EDS (electronic data sheet) standard is provided to describe both cyclic data exchange and acyclic data exchange. In addition, the OPC Unified Architecture standard (abbreviated as OPC UA) of the OPC Foundation is becoming increasingly important.

[0049] like Figure 3As can be seen, an associated hierarchical driver structure 31-1, 31-2, 31-3 for each of the three network segments 2-1, 2-2, 2-3 exists in the device access software 30, and the hierarchical driver structure reflects the structure of the specific network segment. The first driver structure 31-1 for the first network segment 2-1 includes a communication driver 32, a gateway driver 33, and device drivers 34 to 37. The second driver structure 31-2 includes a communication driver 38 and two device drivers 39 and 40. The third driver structure 31-3 includes a communication driver 41 and device drivers 42 and 43. For example, if a user wants to access the field device 11 in the second network segment 2-2, the data traffic is generated via the device driver 39 and the communication driver 38, and is routed to the field access device 3-2 of the second network segment 2-2 via the aggregator box 21 and then forwarded to the field device 11. In the reverse direction, data traffic from the field device 11 travels via the network segment 2 - 2 and the aggregator box 21 to the communication driver 38 , and from there to the device driver 39 .

Claims

1. An aggregator device (21) designed to form a plurality of first data connections (22-1, 22-2, 22-3) to a plurality of field access devices (3-1, 3-2, 3-3), wherein: The aggregator device (21) and the field access devices (3-1, 3-2, 3-3) are able to mutually identify each other and exchange their device identifiers, wherein the field access devices (3-1, 3-2, 3-3) are connected to a plurality of different network segments (2-1, 2-2, 2-3) of a fieldbus system (20), wherein the aggregator device (21) is designed to form at least one second data connection (23) to at least one host computer (16, 18, 19), wherein the aggregator device (21) is designed to: receive a first data service (26) from the at least one host computer (16, 18, 19) via at least one of the second data connections (23), and forward the first data service (26) via at least one of the first data connections (22-1, 22-2, 22-3) to a field access device (3-1) of a network segment (2-1) in which a specific fieldbus component to which the first data service (26) is directed is located, wherein the first data service (26) includes reading and changing parameters of the specific fieldbus component, and receiving a second data service (27) from a fieldbus component in one of the network segments (2-1, 2-2, 2-3) via at least one of the first data connections (22-1, 22-2, 22-3) and forwarding the second data service (27) to at least one of the host computers (16, 18, 19) via at least one of the second data connections (23); wherein the at least one host computer (16, 18, 19) is registered only once at the aggregator device (21) in order to authorize access to different network segments (2-1, 2-2, 2-3) via different corresponding field access devices (3-1, 3-2, 3-3).

2. The aggregator device according to claim 1, characterized in that At least one of the following: - the aggregator device is designed to provide standardized access to a fieldbus system comprising a plurality of network segments; - the first data service is a data service for parameterization, configuration and status monitoring of fieldbus components; - said second data traffic received from a fieldbus component in one of said network segments comprises at least one parameter value of said specific fieldbus component; - said aggregator device is designed to selectively forward said second data traffic received from a fieldbus component in one of said network segments to a host computer or host computers to which said second data traffic is intended; - The aggregator device is implemented as a standalone aggregator apparatus or in the form of a software module executable on a computer.

3. The aggregator device according to claim 1 or claim 2, characterized in that At least one of the following: - the plurality of first data connections include at least one of the following: at least one wireless data connection, at least one wired data connection; - The at least one second data connection comprises at least one of the following: at least one wireless data connection, at least one wired data connection.

4. The aggregator device according to claim 1 or claim 2, characterized in that The aggregator device is designed to forward the first data traffic to a field access device of a network segment in which the specific fieldbus component is located based on the fieldbus component indicated as a destination address of the first data traffic.

5. The aggregator device according to claim 1 or claim 2, characterized in that Routing information is stored on a portion of the aggregator device, the routing information indicating to which network segment first data traffic directed to a particular fieldbus component is to be routed.

6. The aggregator device according to claim 5, characterized in that At least one of the following: - the aggregator device is designed to forward, based on the routing information, a first data traffic received from at least one of the host computers to a network segment in which a fieldbus component to which the first data traffic is directed is located; - the routing information is topology information, the topology information specifying the topology of the network segments connected to the aggregator device; - at least one of the field access devices is designed to determine topology information of an associated network segment by means of scanning and to transmit said topology information to the aggregator device; - at least one of the field access devices is designed to determine, by means of scanning, fieldbus components present in the associated network segment; - at least one of the field access devices is designed to determine, by means of scanning, the fieldbus components present in the associated network segment and to transmit the scan results in the form of at least one file from the specific field access device to the aggregator device; - the at least one site access device is designed to automatically perform a scan of the associated network segment at pre-specified time intervals; - said aggregator device is designed to initiate a scan on a portion of said at least one site access device.

7. The aggregator device according to claim 5, characterized in that At least one of the following: - Routing information is allocation information for allocating the fieldbus components to the respective network segments; - The routing information is distribution information indicating, at least for a part of the fieldbus components, in which network segment the specific fieldbus component is located.

8. The aggregator device according to claim 1 or claim 2, characterized in that At least one of the following: - said aggregator device is designed to authenticate said at least one host computer; - said aggregator device is designed to authorize said at least one host computer; - the aggregator device is designed to assign access rights to the at least one host computer for full or partial access to specific network segments and / or specific fieldbus components and / or specific functions of fieldbus components; - the aggregator device comprises a firewall, wherein the at least one host computer can register with the firewall of the host computer; - the aggregator device has an encryption and decryption unit for encrypting and decrypting data traffic exchanged with the at least one host computer.

9. A field bus system (20), comprising: A plurality of network segments (2-1, 2-2, 2-3), wherein each network segment (2-1, 2-2, 2-3) comprises at least one field access device (3-1, 3-2, 3-3), at least one field bus (4, 10, 13) and at least one field bus component, wherein the at least one field access device (3-1, 3-2, 3-3) is designed to allow access to the field bus component in a specific network segment (2-1, 2-2, 2-3), and An aggregator device (21) according to any one of claims 1 to 8, the aggregator device (21) being designed to form a plurality of first data connections (22-1, 22-2, 22-3) to at least some of the field access devices (3-1, 3-2, 3-3) in different network segments (2-1, 2-2, 2-3).

10. The field bus system according to claim 9, characterized in that: The fieldbus system is designed so that the aggregator device and the field access devices connected to the aggregator device inform each other of their specific device identifiers.

11. The field bus system according to claim 9 or claim 10, characterized in that: To identify a field access device connected to the aggregator device, a device identifier of the field access device connected to the aggregator device is stored in the aggregator device, wherein the aggregator device is designed to identify itself to the field access device connected to the aggregator device.

12. The field bus system according to claim 9 or claim 10, characterized in that At least one of the following: - the plurality of first data connections are Ethernet connections; - the at least one second data connection is at least one Ethernet connection; - the device identifier of the field access device is the IP address of the field access device; - The device identifier of the aggregator device is the IP address of the aggregator device.

13. The field bus system according to claim 9 or claim 10, characterized in that At least one of the following: - at least one of the field access devices connected to the aggregator device is designed to send broadcast messages according to a pre-specified schedule, wherein the aggregator device is designed to receive the broadcast messages from the field access devices connected to the aggregator device and to identify the field access devices connected to the aggregator device based on the received broadcast messages; - at least one of the field access devices connected to the aggregator device is designed to send broadcast messages according to a pre-specified schedule, wherein the aggregator device is designed to receive the broadcast messages from the field access devices connected to the aggregator device and to identify the field access devices connected to the aggregator device based on the received broadcast messages, wherein the at least one field access device is designed to transmit a device identifier of the field access device in the broadcast message to the aggregator device; -At least one of the field access devices connected to the aggregator device is designed to send broadcast messages according to a pre-specified schedule, wherein the aggregator device is designed to receive the broadcast messages from the field access devices connected to the aggregator device and identify the field access devices connected to the aggregator device based on the received broadcast messages, wherein the aggregator device is designed to identify itself to the field access devices when receiving the broadcast messages.

14. The field bus system according to claim 9 or claim 10, characterized in that At least one of the following: - the aggregator device is designed to send broadcast messages according to a pre-specified schedule, wherein the site access device is designed to receive the broadcast messages from the aggregator device and identify the aggregator device based on the received broadcast messages; - the aggregator device is designed to send broadcast messages according to a pre-specified schedule, wherein the field access device is designed to receive the broadcast messages from the aggregator device and identify the aggregator device based on the received broadcast messages, wherein the aggregator device is designed to transmit the device identifier of the aggregator device in the broadcast message to the field access device connected to the aggregator device; - the aggregator device is designed to send broadcast messages according to a pre-specified schedule, wherein the field access device is designed to receive the broadcast messages from the aggregator device and identify the aggregator device based on the received broadcast messages, wherein the field access device is designed to identify itself to the aggregator device when receiving the broadcast messages.

15. The field bus system according to claim 9 or claim 10, characterized in that At least one of the following: - the device identifier of the aggregator device is stored in a specific one of the field access devices, wherein the field access devices are designed to identify themselves to the aggregator device to which they are connected; - at least one of the field access devices has a setting element, by means of which it can be set whether an aggregator device is present in the fieldbus system of the aggregator device to which the field access device is connected, or whether the aggregator device is absent and data exchange takes place directly with at least one host computer; at least one of the field access devices has a setting element, by means of which it can be set whether an aggregator device is present in the fieldbus system of the aggregator device to which the field access device is connected, or whether the aggregator device is absent and data exchange takes place directly with at least one host computer, wherein the setting element is a setting element implemented in hardware; - based on the local domain name of the fieldbus system, the name of the aggregator device can be generated by means of pre-specified formation rules on the field access device and can be used to address the aggregator device; -Based on the local domain name of the fieldbus system, the name of the aggregator device can be generated with the help of pre-specified formation rules on the field access device and can be used to address the aggregator device, wherein the specific field access device is designed to combine the pre-specified name part with the local domain name of the fieldbus system to form the name of the aggregator device in order to generate the name of the aggregator device.

16. The field bus system according to claim 9 or claim 10, characterized in that: The fieldbus system additionally comprises at least one host computer connected to the aggregator device via at least one data connection.

17. The field bus system according to claim 9 or claim 10, characterized in that At least one of the following: - device access software is installed in the at least one host computer; - The device access software is a device access software according to one of the following standards: FDT, FDT2, FDI Device Package, OPC Unified Architecture.

Images