Abstract:
A method for deterministic auto-configuration of a device upon connection to an apparatus includes as a first step, during a first-time connection of the device to the apparatus, a generation of a device-specific configuration data structure, wherein this configuration data structure identifies the configuration data of the device and/or the apparatus, which configuration data was determined during a first-time connection of the device to the apparatus. The next step is storing of the configuration data structure in the device and/or in the apparatus. During a renewed connection of the device to the apparatus, the first-time configuration data of the device and/or the apparatus is determined by means of the configuration data structure, and the device and/or the apparatus correspondingly furnishes the first-time configuration data. The system is equipped in such a way as to execute the stated method.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application claims priority to PCT Application No. PCT/EP2015/057207, having a filing date of Apr. 1, 2015, based off of DE Application No. 102014206989.0 having a filing date of Apr. 11, 2014, the entire contents of which are hereby incorporated by reference. 
     
    
     FIELD OF TECHNOLOGY 
       [0002]    The following relates to an apparatus and a method for the deterministic autoconfiguration of a device in the course of connection to an apparatus. 
       BACKGROUND 
       [0003]    An automatic configuration of a device in the course of connection to another device or an apparatus, which is also designated as plug-and-play functionality, is known in the case of computers, which are supplemented, for example, by additional internal or external components, such as, for example, a memory expansion, a hard drive, or a computer mouse. An automatic configuration of devices via an IP-based network is also known, for example under the designation “universal plug-and-play”. However, autoconfiguration, or plug-and-play functionality, also plays an important role in automation systems. By the autoconfiguration of field and control devices an automation system can easily be set up. DE 10 2010 063 437 A1 describes, for example, a method for the configuration of one or a plurality of devices in an Ethernet-based communications network with which a location-dependent automatic configuration of the devices is enabled in a simple manner. 
         [0004]    There exists on the other hand, however, the requirement that an automation system, for example, or even a train control and train communications system, functions reliably. For this purpose a fixed configuration would be advantageous. Regulations can also require that only one particular inspected and approved configuration is used in regular operation. 
         [0005]    To utilize the requirements for stable network operation with functioning or else authorized configurations for devices that are only plugged into an apparatus or connected to the latter temporarily, and may also be required to be plugged into various apparatuses a number of times, the previous autoconfiguration methods are not suitable. For example, in some operating systems, such as Windows 7, or firmware, such as for example, the BIOS, a non-volatile database is used for extended system configuration data (ESCD), which stores plug-and-play configurations. The said ESCD database is used by the operating system to allocate resources and configuration data for devices such as expansion components. The operating system updates such a configuration database whenever the hardware configuration alters after a new allocation of resources is determined. Thus, in the event of a temporary unplugging and a later reconnection of the device to the apparatus, an automatic configuration of the device is not ensured that the device is connected with the same configuration that was used previously. 
       SUMMARY 
       [0006]    An aspect relates to adjusting the flexibility of an autoconfiguration function, for example, when applied in an automation environment, such that stable operation is ensured. 
         [0007]    The inventive method for the deterministic autoconfiguration of a device in the course of connection to an apparatus comprises as a first step the generation of a device-specific configuration data structure in the event of a first-time connection of the device to the apparatus, wherein the said configuration data structure identifies the configuration data of the device and/or the apparatus, which configuration data have been determined in the course of a first-time connection of the device to the apparatus. The next step is the storage of the configuration structure in the device and/or in the apparatus. In the event of a renewed connection of the device to the apparatus, the first-time configuration data of the device and/or the apparatus are determined by means of the configuration data structure, and the device and/or the apparatus is/are set up in accordance with the first-time configuration data. 
         [0008]    A first-time connection is characterized in that no configuration data structure is present that can be assigned to the apparatus and/or to the device. In the context of embodiments of the invention, a first-time connection can therefore e.g. also exist if a stored configuration data structure has been deleted, or marked as invalid, or if to date connections have only been made in which no configuration data structure has been generated and stored. 
         [0009]    This enables a device or the apparatus, into which the device is plugged, or to which the device is connected, to be configured in the same manner as was the case in a first-time connection of the device to the apparatus. Thus a device can be flexibly deployed, and when it is reconnected to the apparatus its previous configuration can simply be reproduced. 
         [0010]    In an advantageous form of an embodiment, fixedly prescribed device identification information, which is transmitted from the device at least in the case of the first-time connection to the apparatus for the purposes of identifying the device, is recorded in the configuration data structure and the first-time configuration data of the device and/or the apparatus are determined by means of the device identification information. 
         [0011]    This makes it possible for no information concerning the first-time configuration data or else only the configuration data structure to be stored on the device itself. In the event of a renewed connection of the device to the apparatus, and the transmission of the device identification information from the device to the apparatus, the first-time configuration data can be identified by means of the device identification information in the apparatus, and can be transmitted to the device. The device can thus be a component with a simple structure, for example, a sensor in an automation network, which does not need any memory capacity for the purposes of storing a configuration data structure or the first-time configuration data itself. All that is needed is memory capacity in the apparatus for the configuration data structure and the first-time configuration data. 
         [0012]    In a further form of an embodiment, the configuration data structure comprises a configuration identifier, which is determined in the course of a first-time connection of the device to the apparatus. 
         [0013]    If, for example, the configuration data structure is stored in the device and in the apparatus, then, in the event of a renewed connection of the device to the apparatus, the device can transmit the configuration identifier to the apparatus, and via the configuration identifier can determine the associated first-time configuration data in the apparatus. The configuration data are then transferred to the device, and the device, and possibly also the apparatus, is configured in accordance with the configuration data. This makes possible a simply structured look-up table in the apparatus, and thus an autoconfiguration of the device and the apparatus that can be executed in a short period of time. Thus, the same configuration identifier can be used for various devices with, for example, various items of device identification information, since in the event of a renewed connection of the device to the apparatus the configuration data are identified by means of the configuration identifier, and not, for example, by means of the device identification information itself. 
         [0014]    In an advantageous form of an embodiment, the configuration data structure comprises the configuration data of the device and/or the apparatus. 
         [0015]    Here, in the event of a renewed connection of the device to the apparatus, a check must simply be made as to whether the same configuration data structure is present in the device and also in the apparatus. A transfer of the configuration data itself is not necessary, since these are already contained in the configuration data structure. The device and the apparatus can implement the appropriate configuration independently. 
         [0016]    In a further advantageous form of an embodiment, the configuration data structure comprises a hash value of the configuration data, and the setting up of the device and/or the apparatus with the reactivated configuration data is then solely executed if the hash value of the reactivated configuration data agrees with the hash value in the configuration data structure. 
         [0017]    By this means, any alteration or manipulation of the configuration data in the device and/or in the apparatus can be detected, and any implementation of an altered or manipulated configuration can thus be detected and prevented. 
         [0018]    In an advantageous form of an embodiment, the configuration data are stored only after a successful test of the configuration. 
         [0019]    By this means, a functioning configuration is ensured, both in the case of the first-time connection, and also in the event of any subsequent connection of the device to the apparatus. 
         [0020]    In an advantageous form of an embodiment, the configuration data structure comprises information concerning the type of the device. 
         [0021]    In the event of connection of another device of the same type to the apparatus, the other device can be automatically configured in accordance with the configuration data of a configuration data structure that is already present for the same type of device. 
         [0022]    Thus, for example, in the course of a changeover of device or component a transfer of the data for the previous device of the same type can be executed automatically. By this means, for example, a simple changeover of a replacement part with subsequent autoconfiguration can be executed in accordance with the previous device that has been exchanged. 
         [0023]    In an advantageous form of an embodiment, the configuration data structure comprises an item of information concerning a predetermined plant configuration version, and only a connection of device and apparatus with the same plant configuration identifier is authorized. 
         [0024]    By this means, it can be ensured that an autoconfiguration is only executed between devices and/or apparatuses with identical configuration state. As a result it is impossible to connect together arbitrary devices. 
         [0025]    In an advantageous form of an embodiment, the configuration data structure is stored only after a successful function test, and/or after a successful comparison of the device identification information and/or configuration data with previously configured data, and/or after a confirmation by an administrator. 
         [0026]    With a recording of the configuration data structure after a successful function test, it is achieved that an identical configuration is reliably reactivated in the course of each replugging-in. If the configuration data structure is only stored after a successful comparison of the device identification information and/or the configuration data with previously configured data, then security rules can be linked with the identifiers, which rules must exist for an autoconfiguration. The confirmation of an administrator can, for example, ensure that devices that have not yet been connected to date can only be connected to an apparatus in a particular mode of operation, for example in a maintenance mode of the plant. 
         [0027]    In an advantageous form of an embodiment, further configuration data structures with further related configuration data can be determined and stored for a device. 
         [0028]    This enables various configurations to be authorized for a device/apparatus combination. Here, the said various configurations can be selected as a function of further parameters such as, for example, various plant configuration identifiers, so that a device can operate together with an apparatus in various plant configurations. 
         [0029]    In an advantageous form of an embodiment, a device can be configured solely with the first-time configuration data structure and the related configuration data. 
         [0030]    In an advantageous form of an embodiment, the configuration data structure has a temporal period of validity, which is prescribed by the device and/or by the apparatus. 
         [0031]    In an advantageous form of an embodiment, after the expiry of a period of validity the configuration data structure is identified as stopped, or deleted. 
         [0032]    In an advantageous form of an embodiment, the configuration data structure has a spatial period of validity, and a renewed connection of the device to the apparatus is only possible in the geographical region that corresponds to the spatial validity data. 
         [0033]    In an advantageous form of an embodiment, the configuration data structure is used for the purposes of authenticating and/or authorizing the device and/or the apparatus in a subsequent communications connection. 
         [0034]    By means of the configuration data structure, the exact device/apparatus combination is characterized and authenticated. 
         [0035]    In a further advantageous form of an embodiment, the configuration data structure is used in the course of a key exchange in a subsequent communications connection of the device and/or the apparatus. 
         [0036]    The inventive system for the deterministic autoconfiguration of a device in the course of connection to an apparatus comprises at least one device and at least one apparatus, wherein the device and the apparatus are designed so as to generate a device-specific configuration data structure in the event of a first-time connection of the device to the apparatus, wherein the said configuration data structure identifies the configuration data of the device and/or of the apparatus, which configuration data have been determined in the course of a first-time connection of the device to the apparatus. Furthermore, the device and the apparatus are designed so as to store the configuration data structure in the device and/or in the configuration, and in the event of a renewed connection of the device to the apparatus, determine the first-time configuration data of the device and/or the apparatus by means of the configuration data structure, and set up the device and/or the apparatus in accordance with the reactivated first-time configuration data. 
         [0037]    Thus, in particular a functioning and tested configuration can be reproduced in the course of a renewed connection of the device to the apparatus, and can thus ensure the proper functioning of the apparatus with the device. 
         [0038]    In an advantageous form of an embodiment of the system, the device is an internal component of the apparatus that can be plugged into an apparatus, or the device is a pluggable peripheral component of an apparatus, or the device is a network component, or an application on a network component, which is connected to the apparatus, which is a communications network with network components and/or control units. 
         [0039]    Furthermore, a device and an apparatus are claimed, which are designed so as to execute the method as claimed in claims  1  to  16 . Furthermore, a computer program product is claimed with program commands for the purposes of executing the method. 
     
    
     
       BRIEF DESCRIPTION 
         [0040]    Some of the embodiments will be described in detail, with reference to the following figures, wherein like designations denote like members, wherein: 
           [0041]      FIG. 1  shows a first example of embodiment of an inventive system in a schematic representation; 
           [0042]      FIG. 2  shows a second example of embodiment of an inventive system with additional servers for the purposes of determining configuration data in a schematic representation; 
           [0043]      FIG. 3  shows an example of embodiment of an inventive configuration data structure in a schematic representation; and 
           [0044]      FIG. 4  shows an example of embodiment of the inventive method as a flow chart. 
       
    
    
       [0045]    In all figures the parts corresponding to one another are allocated the same reference symbols. 
       DETAILED DESCRIPTION 
       [0046]    By means of  FIGS. 1 and 2  various systems are shown, in which an autoconfiguration of a device takes place in the course of connection to an apparatus. Hereinafter the terms “connect” and “plug in” are used synonymously. 
         [0047]    The system  10  comprises various external devices  13 . 1 ,  13 . 4 , which can, for example, be plugged into an apparatus  11  as pluggable peripheral components. Furthermore, a device  12 , for example, an expansion card, is connected to the apparatus  11  as a pluggable internal component. The apparatus  11  can be, for example, a control device within an automation plant. The latter is connected to an automation network, here to the communications network  15 . By means of autoconfiguration, sensors and/or actuators, here, for example, the devices  13 . 1 ,  13 . 4 , can be connected to the apparatus  11 , i.e. the control device. An expansion module, here the device  12 , for example an input-output module, can also be connected to the apparatus  11 , i.e. to the control device, by means of autoconfiguration. Sensors and/or actuators  13 . 2 ,  14 . 2  can in turn be plugged into the expansion module  12 . In this case the expansion module  12  has the role of an apparatus, to which devices  13 . 2 ,  14 . 2  are connected. 
         [0048]    In order that the apparatus  11 ,  12  can operate together with the connected devices  13 . 1 ,  14 . 1 , and/or  13 . 2 ,  14 . 2 , the devices  13 . 1 ,  14 . 1  and the apparatus  11  must be configured appropriately, i.e. communications parameters, such as, e.g. port numbers or addresses, must be arranged, for example, between the apparatus  11  and the device  13 . 1 ,  14 . 1 . Furthermore, certain control functions in the devices  13 . 1 ,  14 . 1  can be activated and thus configured for the purposes of executing certain tasks in conjunction with the apparatus. Correspondingly adjustments can be made to the configuration of the apparatus  11 , or also to further components, connected, for example, via the communications network  15 . 
         [0049]    In a first-time autoconfiguration procedure, a connection is made between a device and an apparatus, wherein the device is identified by the apparatus, and as a result the apparatus determines a configuration, and the said configuration is communicated to the device and activated, in order to utilize the device. This is represented in  FIG. 2  with the example of a device  23 , which is connected into a distributed system  20 , for example, an automation network. Here the apparatus  21  is to be understood to be the communications network  15 , with network components and/or control units, such as, for example, a configuration server  22  or a context server  27 . After the device  23  has been connected via a communications network  15  to the apparatus  21 , the device  23  establishes contact with, for example, the configuration server  22 , and transfers device identification information ID and possibly further attributes Atts to the server  22 . An autoconfiguration unit  25  in the configuration server  22  checks, for example by means of a security directive, whether the device  23  may be connected to the apparatus  21 . Furthermore, the server  22 , by interrogating a context server  27 , can check whether, for example, a connection between the device  23  and the apparatus  21  is allowed in the current operating state of the system. If this is the case, a configuration unit  25  determines, for example, the configuration data CONFIG for the device  23 , together with a device-specific configuration data structure KDS, and transmits these via the communications network  15  to the device  23 . The exchange of messages is symbolized in  FIG. 2  by the arrows. 
         [0050]    The device  23  is subsequently configured in accordance with the received configuration data CONFIG. Here the configuration data structure KDS is stored either in the device  23 , for example in a memory  24  provided for this purpose, or in the apparatus  21 , for example in the configuration unit  25  in the configuration server  22 , or in both. 
         [0051]    If the device  23  is now separated from the apparatus  21 , and at a later point in time is reconnected to the apparatus  21 , the first-time configuration data CONFIG of the device  23  and/or the apparatus  21  are determined by means of the configuration data structure KDS, and the device  23  and/or the apparatus  21  are set up corresponding to the reactivated first-time configuration data. Here the configuration data can also relate to further network components, which must be adjusted in the course of a connection of the device  23  to the apparatus  21 . The said configuration data are communicated to the other appropriate network components. 
         [0052]    What is important in the event of a renewed connection of the device  23  to the apparatus  21  is the fact that the same configuration data are reused as in the case of the first-time connection of the device  23  to the apparatus  21 . Here the configuration data structure KDS identifies the said first-time configuration and/or the corresponding configuration data. 
         [0053]    In order to guarantee a functional system  10 ,  20 , in an example of embodiment only such first-time configuration data and a related configuration data structure KDS are stored, if the corresponding configuration of the device and/or the apparatus has previously been tested successfully. 
         [0054]    The configuration data structure KDS, as represented, for example, in  FIG. 3 , can thereby comprise various items of information and/or parameters, and according to the parameters and/or items of information included can be stored either in the device  23 , or in the apparatus, or in both. In  FIG. 3  an exemplary configuration data structure KDS is represented. The configuration data structure KDS comprises at least one or also a combination of the parameters and/or items of information shown. 
         [0055]    In a first example of an embodiment, in the course of the first-time connection of the device  23  to the apparatus  21 , for example in the configuration server  22  in  FIG. 2 , the configuration data are determined for the device and/or the apparatus  21 . 
         [0056]    Furthermore, a configuration data structure KDS is generated, which comprises, for example, the device identification information  31  of the device  23 . Identified by the configuration data structure KDS, the configuration data determined are now stored, for example in a configuration unit  25  of the configuration server  22 . In the event of a renewed connection of the device  23  to the apparatus  21 , the device  23  transmits the device identification information  31  to the apparatus  21 . Thereupon the apparatus  21  determines the configuration data structure KDS with the corresponding device identification information  31  and the configuration data additionally stored. These are transmitted to the device  23  and the device is there set up accordingly. 
         [0057]    In addition, a hash value  34  can be contained in the configuration data structure KDS; this has been formed from the first-time configuration data. In this case the device  23  reactivates the first-time configuration data only if a hash value, formed by the device  23  via the configuration data delivered from the apparatus  21 , agrees with the hash value  34  in the configuration data structure. Thus any alteration of the configuration data sent from the apparatus, compared with the first-time configuration data, is detected, and any implementation is prevented. 
         [0058]    The configuration data structure KDS can also contain a configuration identifier  32 . Instead of the device identification information  31  the said configuration identifier  32  can be transmitted in the event of a renewed connection of the device  23  to the apparatus  21 . In this case the first-time configuration data of the device  23  can also be identified in the apparatus  21  with this configuration identifier  32  and stored accordingly. 
         [0059]    In addition, the configuration data structure KDS can comprise information concerning the type  33  of the device  23 . If the device  23  transmits the said configuration data structure KDS in the course of a renewed connection to the apparatus  21 , a transfer of configuration data of the same device type can take place, dependent, for example, upon a security directive set up in the system  22 . This makes possible, for example, the exchange of identical devices, or of replacement parts, which are configured in accordance with the previous device. If the device  23  delivers an item of information concerning the device type  33  for which no first-time configuration data are present in the apparatus  21 , an error message or an alarm is outputted. 
         [0060]    The configuration data structure KDS can comprise further information such as, for example, a plant configuration identifier  36 . The latter is utilized for the purpose of executing only one autoconfiguration of device and apparatus with a particular, and/or with an identical, plant configuration state, which is expressed in terms of the same plant configuration identifier  36 . Thus it is ensured that only devices with, for example, the same configuration version, that is to say, with the same configuration state, are used in a plant. 
         [0061]    The configuration data structure KDS can comprise further parameters  37 , for example, a temporal period of validity or spatial validity data. The temporal period of validity can be prescribed by the device  23  and/or by the apparatus  21 . After expiry of the period of validity the configuration data structure KDS is identified as blocked, or deleted. In this manner a later unintentional reactivation of the configuration data in the course of connecting the device to the apparatus is no longer possible. Similarly devices  23  are thus prevented from being configured with an outdated configuration and newly introduced into a system. 
         [0062]    By virtue of the spatial validity data the execution of an autoconfiguration with the stored first-time configuration data is only newly authorized if the configuration of the device takes place in a predetermined spatial environment, for example in the same environment as in the case of the first-time configuration, in the course of which the configuration data structure KDS and the related first-time configuration data have been stored. 
         [0063]    However, a configuration data structure KDS can also contain the configuration data itself, and/or a description of the configuration data  35 . If such a configuration data structure KDS with a description of the configuration data  35  is generated in the course of a first-time connection of the device  23  to the apparatus  21 , and is stored both in the device and in the apparatus, in the event of a later renewed connection of the device  23  to the apparatus  21  all that is necessary is, for example, the transmission of one of the parameters of the configuration data structure KDS from the device  23  to the apparatus  21 , and a confirmation of the said parameter of the configuration data structure by the apparatus  21 . Thereupon the device  23  can independently extract the configuration data  35  from the configuration data structure KDS and implement the same. For its part the apparatus  21  can do the same. By this means the quantity of data to be transferred is reduced, less bandwidth is required, and any manipulation of the configuration data on the transfer path is prevented. 
         [0064]    If in contrast to the above only the device identification information  31  is contained in the configuration data structure KDS, and in the apparatus a linking of the device identification information  31  with the first-time configuration data, then even very simply structured devices  23  can execute a deterministic autoconfiguration, since only the device identification information  31  needs to be stored on the device, but not any other configuration data. The latter are transmitted from the apparatus  21  to the device  23 . 
         [0065]    In one form of an embodiment, the configuration data structure KDS is only stored in the device  23  and/or in the apparatus  21  after a successful function test. This ensures that an identical configuration is reliably reactivated in the course of each further plugging of the device  23  into the apparatus  21 . However, the configuration data structure KDS can also only agree with previously established data, for example, from planning data and/or with a previously established system configuration, after a successful comparison of the device identification information  31  and/or the configuration data. However, the storage of the configuration data structure KDS can also take place only if the latter is confirmed by an administrator. Thus it can come about, for example, that a device that has not yet been used is connected and utilized only in a particular mode of operation. 
         [0066]    Devices  13 ,  14 ,  23  can determine and store further configuration data structures KDS with further related configuration data. Such devices  13 ,  14 ,  23  can, for example, comprise various configuration data structures for the purposes of connecting to various apparatuses  11 ,  12 . A device can, however, also have a plurality of configuration data structures for the purposes of renewed connection to the same apparatus  11 ; the said configuration data structures belonging, for example, to various plant configuration versions. Thus, one autoconfiguration can be retained for various plant configuration versions. 
         [0067]    On the other hand, there are devices that can be reactivated only with the first-time configuration data structure and the related configuration data, in the event of a renewed connection to the apparatus. Here any alteration of the configuration after the first-time connection of the device  13 ,  14 ,  23  to the apparatus  11 ,  12 ,  21  is not authorized. 
         [0068]    In one variant a configuration data structure KDS can be utilized in the authentication phase of a subsequent communications connection. For this purpose the configuration data structure KDS is sent along at the same time as a parameter, or an attribute certificate, in the course of the device authentication. With the use of the configuration data structure in the course of an authorization it can be ensured that the device may only construct a communications connection in a certain configuration, and that this also can be checked at the remote station, that is to say, at the communications partner. 
         [0069]    The configuration data structure KDS can also be used in the key exchange phase of a subsequent communications connection. In this manner it can be ensured, for example, that a session key is tied to an existing configuration, and cannot inadvertently be used by the device in the event of any change of the configuration. This is particularly of advantage if the configuration of a device has altered between two autoconfiguration activities. The apparatus  21  is designed, as are the apparatuses  11  and  12 , such that the functions and methods described can be executed on them. The same is true for the devices  12 ,  13 ,  14 ,  23  described, together with the systems  10  and  20 . 
         [0070]    In  FIG. 4 , a sequence is represented for a deterministic autoconfiguration by means of a flow chart. The autoconfiguration process begins in step  40 , in that a device  12 ,  13 ,  14 ,  23  is plugged into, that is to say, is connected to, an apparatus  11 ,  12 ,  21 . In step  41 , for example, identification data of the plugged-in device are firstly transmitted to the apparatus  11 ,  12 ,  21 , and are there checked in accordance with, for example, a security directive. If in step  42  any deviation of the device from the security directive is established, for example, an error message is outputted in step  43 , and no configuration is executed. 
         [0071]    If no deviation is established in step  42  a check is made in the device  13 ,  14 ,  23  and/or in the apparatus  11 ,  12 ,  21  as to whether a configuration data structure KDS is present in the local memory, see step  44 . If it ensues in step  45  that no configuration data structure KDS is yet present, a configuration data structure KDS is generated and stored in accordance with one of the examples cited above, see step  48 . In step  49  the configuration is set up in the device and/or in the apparatus. In step  50  the autoconfiguration process is therefore completed. The device  13 ,  14 ,  23  can then operate together with the apparatus  11 ,  12 ,  21  in its configuration as determined. 
         [0072]    If the device  13 ,  14 ,  23  is separated, that is to say, unplugged, from the apparatus  11 ,  12 ,  21 , the method as described begins once again with step  40 , with a renewed plugging of the device  13 ,  14 ,  23  into the apparatus  11 ,  12 ,  21 . 
         [0073]    If the identification data, which in step  41  are transmitted to the apparatus, are already part of the configuration data structure KDS, then step  41  corresponds to step  44 , and the process can then be pursued further directly with step  46 , namely the reading of the configuration data structure KDS and the reactivation of the first-time configuration data. 
         [0074]    Thus, on the one hand the flexibility of an autoconfiguration is utilized, for example for applications in an automation environment, and at the same time stable operation of an automation plant is ensured by means of the first-time configuration data that have already been checked. 
         [0075]    Although the present invention has been disclosed in the form of preferred embodiments and variations thereon, it will be understood that numerous additional modifications and variations could be made thereto without departing from the scope of the invention. 
         [0076]    For the sake of clarity, it is to be understood that the use of ‘a’ or ‘an’ throughout this application does not exclude a plurality, and ‘comprising’ does not exclude other steps or elements.