System for establishing communication connection between first device and server over network and method for authorizing configuration of first device by second device

Abstract

The invention discloses a method for authorizing configuration of a first device through a second device and a system for establishing communication connection between the first device and a server through a network. The method comprises the following steps: displaying at least part of a randomly generated first code through a first device; acquiring the first code by means of the optical sensor through the second device; collecting a second code attached to the surface of the first device through a second device; confirming the second device to the server; authenticating, by the server, an identity of the second device; sending, by the first device, a first representation of the code to the server over the network; sending, by the second device, a second representation of the code to the server; and authorizing, by the server, configuration of the first device by the second device based on the representation.

Description

Technical Field

[0001] The present invention relates to a method for establishing a communication connection between a first device and a server through a network

[0002] A system and a method for authorizing configuration of a first device by a second device. Background Art

[0003] Configuring the device in a safety-related facility may require specific safety measures to be taken.

[0004] This can prevent unauthorized personnel from configuring the device. For example, it can be stipulated that the device must be authorized in advance.

[0005] Therefore, configuration from unauthorized devices will fail.

[0006] Prevent configuration by unauthorized personnel. Summary of the invention

[0007] The method according to the present invention comprises: displaying a code by a first device; displaying a code by a second device

[0008] The optical sensor collects the code; confirms the second device to the server; the server authenticates the first

[0009] sending a representation of the code to the server via the second device; and

[0010] The server authorizes configuration of the first device by the second device based on the representation.

[0011] Here, the concept of "device" used in the current specification and claims is particularly

[0012] It is understood to be an electronic device, which includes a processor and a memory, wherein in the memory

[0013] The electronic device stores various instructions that can be executed by the processor, and the electronic device includes a sensor if necessary.

[0014] A sensor and / or actuator, which is used to connect to a sensor or actuator or to establish a communication with a sensor.

[0015] The first device may be, for example, a control device. The second device may be, for example, a

[0016] The control device may be a portable device having an energy storage device for supplying energy to the second device.

[0017] Modular fieldbus nodes. In addition, the control device can be a modular fieldbus node

[0018] The front end or input / output module (I / O module) of the point.

[0019] In this regard, the concept of "front end" used within the scope of the present specification is

[0020] The term "I / O module" as used within the scope of the present specification is particularly understood as a device that can be connected to a front end or is connected to a front end during operation, which connects one or more field devices to the front end and, if necessary, to a higher-level control device (via the front end).

[0021] The I / O module may have one or more inputs and / or outputs, which are arranged to connect field devices. If a field device is connected to the I / O module, it may be necessary to configure the I / O module in order to operate the field device. Through the configuration, for example, it is possible to specify in detail which data are derived from the signals read in through the inputs of the I / O module and transmitted to the front end. In addition, it is possible to specify in detail by the configuration which signals are derived from the data received from the front end and output at the output of the I / O module. In addition, after the initial configuration, it may be necessary to change or update the configuration records stored on the I / O module, for example when the assigned tasks and / or the environment of the I / O module change or when a defective I / O module needs to be replaced.

[0022] If the front end is put into operation or (other) I / O modules are connected to the front end in series, it may be necessary to configure the front end (in order to operate the I / O modules). By means of the configuration, it may be specified, for example, how the front end communicates with a superior control unit and whether the data (or which data) of the I / O modules are processed by the front end or forwarded to the superior control unit. Furthermore, by means of the configuration, it may be specified whether the data (or which data) of the superior control unit are processed by the front end or forwarded to the I / O modules. Furthermore, after the initial configuration, it may be necessary to change or update the configuration records stored on the front end, for example when the assigned tasks and / or the environment of the front end change or when a defective front end needs to be replaced.

[0023] The term "configuration record" as used within the scope of the present description is understood in particular to mean a record that describes how a process image is generated (for example, how data are derived from signals read in at the inputs of an I / O module and how these data are transmitted, for example, via a bus to a front end or from the front end to a superior control unit) and / or which data are forwarded from a superior control unit to the I / O module, or how signals are derived from data transmitted from the front end to the I / O module (these signals are output, for example, at the outputs of the I / O module).

[0024] For example, field devices can be connected to the inputs and / or outputs, which provide status signals or process control signals. In this context, the term "field device" as used within the scope of the present description is understood in particular to mean sensors and / or actuators that are connected (signaling-wise) to (e.g., connected to) an I / O module. Furthermore, the term "input" or "output" as used within the scope of the present description is understood in particular to mean electrical terminals, such as connection pins.

[0025] According to the first embodiment of the present invention, the method may also include: the first device sends a first message to the server through the network, wherein the first message contains first information about the identity of the first device; the server sends a second message to the first device through the network and exports the code from the second message through the first device.

[0026] The first device may be configured to send a first message to the server via the network once the first device is connected to the network or in response to an input from a commissioning engineer. Such input may include, for example, manipulating a switch mounted on the first device or a touch-sensitive display mounted on the first device.

[0027] The server may be configured to send a second message in response to a first message. For example, as described in the previous paragraph, once the first device is connected to the network, the first device may send a first message to the server via the network, and the server may send a second message to the second device in response to receipt of the first message and distribute the content (e.g., code) of the second message to the first device.

[0028] The server may be configured to send a second message in response to a third message from the second device, wherein the third message includes second information about the identity of the first device. The method may further include: collecting a second code by the second device using an optical sensor, and deriving second information about the identity of the first device from the second code. The second code may be attached to a surface of the first device. The second code may be a one-dimensional or two-dimensional barcode.

[0029] This allows commissioning engineers to specifically select the devices to be configured.

[0030] According to a second embodiment of the present invention, the code may be a first code that is at least partially randomly generated, and the method further comprises collecting, by a second device, a second code attached to a surface of the first device. In addition, a representation of the first code may be included in a second representation of the code, and the method further comprises: sending, by the first device, the first representation of the code to a server via a network; sending, by the second device, the second representation of the code to the server, and authorizing, by the server, configuration of the first device via the second device based on the representation.

[0031] The desire to configure the first device by means of the second device is thus signaled to the server in that the server receives representations of the code from both the first device and the second device and can determine by comparing the code that the commissioning engineer wishes to configure the first device and, under certain circumstances, also permits this.

[0032] The second code may be a one-dimensional or two-dimensional barcode. The second code may describe the first device (e.g., by specifying a manufacturer identification, model number, etc.) and / or identify the first device (e.g., by specifying a unique device number, such as a serial number or a public key "publickey"). The second code may also include a network address of the server (e.g., an IP address). The combination of the first code and the second code may form a unique device key.

[0033] Displaying the first code may include displaying the first elements that make up the first code in order. For example, the first elements may be displayed in order on a digital display screen or by activating / deactivating one or more signal lights. For example, the first elements may be displayed in order by flashing one or more signal lights.

[0034] The first device may be arranged to initiate display of the first code in response to a request from the second device or a manual input at the first device.

[0035] The first device may also be configured to end display of the first code in response to a request from the second device or a manual input at the first device.

[0036] The system according to the invention comprises a first device and a second device, wherein the second device is configured to confirm to a server and send to the server a representation of a code optically displayed by the first device. The server can be configured to check the representation and authorize configuration of the first device by the second device based on the result of the check.

[0037] According to a first embodiment of the invention, the second device may also be configured to read in a one-dimensional or two-dimensional barcode and derive information about the identity of the first device from the one-dimensional or two-dimensional barcode and send it to the server. The one-dimensional or two-dimensional barcode may be attached to the surface of the first device. The information contained in the one-dimensional or two-dimensional barcode may describe the first device (e.g. by specifying a manufacturer's logo, a model number, etc.) and / or identify the first device (e.g. by a unique device number). The one-dimensional or two-dimensional barcode may also contain a network address of the server (e.g. an IP address).

[0038] According to a second embodiment of the present invention, the second device can be configured to send a first code and a second code attached to the surface of the first device and collected by the second device to the server. Here, the combination of the first code and the second code can form a unique device key.

[0039] The first device may be arranged to generate the first code at least partly randomly and to authenticate by sending the first code and a first representation of the second code to the server.

[0040] It is also to be understood that all features described in connection with the system may also be features of the method and vice versa. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The invention is explained below in a detailed description based on exemplary embodiments, wherein reference is made to the accompanying drawings.

[0042] In the figure:

[0043] Figure 1 shows a fieldbus system;

[0044] Figure 2 A fieldbus node and a fieldbus device connected to the fieldbus node are shown;

[0045] Figure 3a , Figure 3b and Figure 3c A first device, a second device, and a server are shown; and

[0046] Figure 4 A flow chart illustrating a method of authorizing configuration of a first device by a second device.

[0047] In this case, identical or functionally similar elements are denoted by the same reference symbols in the figures. DETAILED DESCRIPTION

[0048] Figure 1 The block diagram of a fieldbus system 10 is shown. The fieldbus system 10 comprises a superior control unit 20, to which a plurality of fieldbus nodes 100 are connected via a fieldbus 30. The superior control unit 20 can be used not only for monitoring but also for regulating a device (not shown) controlled by the fieldbus system 10. When the superior control unit 20 monitors a device, the superior control unit 20 can receive status data periodically or aperiodically from the fieldbus node 100, the status data describing the status of the device and generating a fault signal or an alarm signal when the status of the device deviates (substantially) from the expected / permitted state or state range. When the superior control unit 20 (not only monitors but also) regulates a device, the superior control unit 20 can receive status data periodically or aperiodically from the fieldbus node 100 and determine the control data transmitted to the fieldbus node 100 taking into account the status data.

[0049] Figure 2An exemplary modular fieldbus node 100 is shown, comprising a front end 110 and two I / O modules 120 and 130 connected in series to the front end 110, to which field devices 140, 150, 160 and 170, such as sensors and actuators, are connected. During operation, the I / O modules 120 and 130 read in sensor signals via inputs and generate status data from the sensor signals, which are transmitted to the front end 110 via a local bus 180. The front end 110 can process these status data locally and / or (if necessary in a modified form) forward these status data to a higher-level control unit 20. The higher-level control unit 20 (or the front end 110 in the case of local processing) can generate control data taking into account these status data.

[0050] The control data generated by the superior control unit 20 can be transmitted to the (same or another) front end 110 via the fieldbus 30. The control data transmitted to the front end 110 (or generated by the front end 110) are forwarded / transmitted (in a modified form if necessary) to the I / O modules 120 and 130. The I / O modules 120 and 130 receive the control data and output control signals corresponding to the control data at outputs connected to the actuators. In this case, the data communication between the components of the fieldbus system 10, the mapping of sensor signals to status data, and the mapping of control data to control signals can be adapted to different usage scenarios by configuring the fieldbus node 100.

[0051] to this end, Figure 3a A fieldbus node 100 and a computer 40 are shown, which is designed to start the configuration of the fieldbus node 100 (i.e. the front end 110 and / or the I / O modules 120 and 130 of the fieldbus node 100). The computer 40 can have a display device, on which a graphical interface of a configuration program can be presented. The graphical interface can allow the ideal topology of the fieldbus node 100 to be graphically presented and the parameters required for the configuration to be assigned to the front end 110 and / or the I / O modules 120 and 130 (and in particular their inputs and / or outputs), or to call up an assigned configuration created on another computer and stored on the computer 40. Subsequently, a configuration record can be formed from all parameters for the front end 110 and each I / O module 120 and 130 (or for all together), which must be transmitted to the front end 110 and the I / O modules 120 and 130 of the fieldbus node 100 and stored there in order to configure them.

[0052] However, in order to protect the front end 110 and the I / O modules 120 and 130 of the fieldbus node 100 from being configured by unauthorized persons, they are arranged to accept configuration records only from a remotely arranged server 50, or only if the server 50 has issued an acceptance of the configuration record. In order to obtain the thus necessary cooperation of the server 50, the computer 40 must prove to the server 50 that it is in the vicinity of the fieldbus node 100 and therefore has direct physical access to the fieldbus node 100. This proof is provided by the fieldbus node 100 displaying a code which is captured by the computer 40 with the aid of an optical sensor 42 and sent to the server 50.

[0053] like Figure 3a , Figure 3b and Figure 3c As shown in , the field bus node 100 (for example, the front end 110 or one of the I / O modules 120 and 130) can be equipped with a plurality of lamps 102, 104 and 106 that output a code in sequence. For example, the code can consist of a series of elements, each of which is a 3-bit value that can be displayed when using the lamps 102, 104 and 106. The code can be generated at least partially randomly by the field bus node 100 and sent to the server 50 via a (if necessary encrypted) network connection. Alternatively, the code can also be received by the server 50 via a (if necessary encrypted) network connection. For example, the field bus node 100 is configured to log in to the server 50 (for example, using an identification and a password) and request the code when starting or in response to a manual input or signal. It is also conceivable that the code is permanently stored on the field bus node 100 and backed up on the server 50 or can be reconstructed or retrieved by the server 50.

[0054] It is also conceivable that the sending of a code from the server 50 to the fieldbus node 100 is triggered by the computer 40. For example, the computer 40 is configured to send a message to the server 50 via the network, wherein the message contains information about the identity of the fieldbus node 100. The identity of the fieldbus node 100 can be stored on the computer 40, entered by a user of the computer 40 or captured using an optical sensor 42. For example, the fieldbus node 100 is provided with a code that can be captured by the optical sensor 42. For example, a one-dimensional or two-dimensional barcode can be attached or affixed to the housing of the fieldbus node 100, which barcode contains information for identifying the fieldbus node 100. Furthermore, a link to a program can be contained in the one-dimensional or two-dimensional barcode, which evaluates the code displayed when using the lights 102, 104 and 106 and sends it to the server 50 and / or the network address of the server 50.

[0055] Furthermore, it can be provided that not only the computer 40 is configured to send a message containing information about the identity of the fieldbus node 100 to the server 50 via the network, but that the fieldbus node 100 is also configured in this way. The server 50 can then use the information about the identity of the fieldbus node 100 to associate the message of the computer 40 with the message of the fieldbus node 100 and to check whether the optically displayed code is consistent. In this case, the server 50 does not need to retain any information about the identity of the fieldbus node 100 or the connection between the identity of the fieldbus node 100 and the code optically displayed by the fieldbus node 100.

[0056] The computer 40 can also log in to the server 50 (e.g. using an identification and a password) before sending the acquired code via the (optionally encrypted) network connection. For example, a user account on the server 50 can be assigned to the unit that possesses the fieldbus node 100. The fieldbus node 100 can be assigned to a user account. The computer 40 can be, for example, a mobile phone, a tablet, a laptop, a "smart watch" or "smart glasses" which are connected to the local network via a wireless connection and can establish a connection to the server 50 via a router of the local network and the Internet.

[0057] Alternatively, the computer 40 may be, for example, a mobile phone, a tablet computer, a laptop computer, a "smart watch" or "smart glasses", which are connected to a wireless mobile network via a wireless connection and can establish a connection with the server 50 via a router of the wireless mobile network and the Internet. In addition, a program may be run on the mobile phone, tablet computer, laptop computer, "smart watch" or "smart glasses", and the program is provided with a network address of the server 50, wherein the user of the mobile phone, tablet computer, laptop computer, "smart watch" or "smart glasses" may call a login page of the server 50 by starting the program or entering the network address.

[0058] After logging into the server 50, the code can be sent to the server 50 by the computer 40. The server 50 can check the code and, if the check is successful, authorize the configuration of the fieldbus node 100 by the computer 40. This can be achieved, for example, by the server 50 forwarding the configuration record from the computer 40 to the fieldbus node 100, signaling the fieldbus node 100 to accept the configuration record received from the computer 40, or putting the fieldbus node 100 in a state ready to receive and accept the configuration record from the computer 40.

[0059] Figure 4A flow chart of a method for authorizing the configuration of a first device, for example a fieldbus node 100, by a second device, for example a computer 40, is shown. The method begins with a step 200 of displaying a code by the first device. Step 200 can be performed, for example, by the fieldbus node 100 by sequentially outputting the code by means of the lights 102, 104 and 106. A subsequent step 210 of the method is the acquisition of the code by the second device by means of an optical sensor. Step 210 can be performed, for example, by the computer 40 by recording and evaluating the light sequence by means of a camera installed in the computer 40 or connected to the computer 40. If the code has been acquired by the computer 40, this can be reported to the first device by a confirmation signal or a manual input on the first device, for example by means of a key, a dip switch or a touch-sensitive display, and the first device then stops displaying the code.

[0060] In steps 220 and 230, the second device is logged in to the server 50, and in step 240, the second device, which is now logged in, sends the code to the server 50. Steps 220, 230 and 240 can be performed, for example, by the computer 40 by calling a login page, entering login credentials and uploading the code or launching a specific application program set up to perform these steps on the computer 40. If the code is checked by the server 50 to be correct, the server 50 authorizes the configuration of the first device by the second device.

[0061] Reference numerals list

[0062] 10 Fieldbus systems

[0063] 20 Control unit

[0064] 30 Fieldbus

[0065] 40 Computer

[0066] 42 Optical Sensor

[0067] 50 servers

[0068] 100 fieldbus nodes

[0069] 102 Lights

[0070] 104 Lights

[0071] 106 Lights

[0072] 110 Front End

[0073] 120 I / O modules

[0074] 130 I / O modules

[0075] 140 Field equipment

[0076] 150 Field devices

[0077] 160 Field equipment

[0078] 170 Field equipment

[0079] 180 Local Bus

[0080] 200 steps

[0081] 210 Steps

[0082] 220 Steps

[0083] 230 Steps

[0084] 240 Steps

[0085] 250 steps

Claims

1. A method for authorizing configuration of a first device (100) by a second device (40), comprising: displaying, by a first device (100), a first code generated at least in part randomly; collecting the first code by means of an optical sensor (42) through a second device (40); collecting a second code attached to the surface of the first device (100) by a second device (40); confirming the second device (40) to the server (50); authenticating the identity of the second device (40) through the server (50); Sending a first representation of a code to a server (50) via a network by a first device (100); sending, by the second device (40), a second representation of the code to the server (50); The server (50) authorizes configuration of the first device (100) by the second device (40) based on the representation.

2. The method of authorizing configuration of a first device (100) by a second device (40) according to claim 1, wherein: The second code is a one-dimensional or two-dimensional barcode.

3. The method for authorizing configuration of a first device (100) by a second device (40) according to claim 1 or 2, wherein: Displaying the first code includes sequentially displaying first elements constituting the first code.

4. The method of authorizing configuration of a first device (100) by a second device (40) according to claim 3, wherein: The first element is displayed in sequence by flashing one or more signal lights (102, 104, 106).

5. The method for authorizing configuration of a first device (100) by a second device (40) according to any one of claims 1 to 4, wherein: The first device (100) is arranged to initiate display of a first code in response to a request from the second device (40) or a manual input at the first device (100).

6. The method for authorizing configuration of a first device (100) by a second device (40) according to any one of claims 1 to 5, wherein: The first device (100) is configured to terminate display of the first code in response to a request from the second device (40) or a manual input at the first device (100).

7. The method for authorizing configuration of a first device (100) by a second device (40) according to any one of claims 1 to 6, wherein: The first device (100) is a control device.

8. The method for authorizing configuration of a first device (100) by a second device (40) according to any one of claims 1 to 7, wherein: The second device (40) is a portable device having an energy storage device for supplying energy to the second device (40).

9. A system for establishing a communication connection between a first device (100) and a server (50) via a network, comprising: A first device (100); as well as A second device (40); The second device (40) is configured to confirm with the server (50); and The second device (40) is further configured to send to the server (50) a second representation of a first code optically displayed by the first device (100) and a second code attached to the surface of the first device (100) and collected by the second device (40).

10. The system for establishing a communication connection between a first device (100) and a server (50) through a network according to claim 9, wherein: The first device (100) is configured to: generating the first code at least in part randomly; and Authentication is performed by sending a first representation of the first code and the second code to a server (50).

Images