Method for connecting at least one IP-enabled device to a cloud-based customer application using a cloud-based registration application

Abstract

The invention relates to a method for connecting at least one IP-enabled device (101, 111) to a cloud-based customer application (81) using a cloud-based registration application (91), wherein the cloud-based customer application (81) and the cloud-based registration application (91) are designed to exchange data over a communication connection (20). A first IP-enabled device (111) transmits its individual identifiers to the registration application (91) over a temporarily established communication connection (30), wherein the registration application (91) compares these identifiers with identifiers that it has received from the customer application (81). In the event of a match, the registration application (91) transmits the connection data, likewise obtained beforehand from the customer application (81), to the first IP-enabled device (111). The first IP-enabled device (111) establishes a secure connection to the customer application (81) using the connection data.

Description

[0001] Method for connecting at least one IP-enabled device to a cloud-based customer application using a cloud-based registration application

[0002] Description

[0003] The invention relates to a method for connecting at least one IP-enabled device to a cloud-based customer application using a cloud-based registration application, wherein the cloud-based customer application and the cloud-based registration application are configured for exchanging data.

[0004] German patent DE 102013 018 596 A1 discloses a network system comprising a first network infrastructure at a first location and a second network infrastructure at a second location. Each network infrastructure preferably has several network participants, which can be configured as control devices or field devices. The first network infrastructure has a coupling unit through which it connects to a cloud-based application hosted in a cloud computing infrastructure. The second network infrastructure also connects to the cloud-based application. To enable communication between the two network infrastructures, a network participant of the second network infrastructure is integrated into the first network infrastructure.For this purpose, the coupling unit is also designed to emulate the network participant of the second network infrastructure in conjunction with the cloud computing-based application and thus integrate it into the first network infrastructure as an emulated network participant.

[0005] The present invention is based on the objective of providing a method that enables the simple and cost-effective connection of at least one IP-enabled device to a cloud-based customer application. According to one aspect, the invention preferably relates to a method for connecting at least one IP-enabled device to a cloud-based customer application using a cloud-based registration application, wherein the cloud-based customer application and the cloud-based registration application are configured to exchange data via a communication connection, which is established, in particular, temporarily. Via this temporarily established communication connection, a first IP-enabled device transmits at least its unique identifier to the registration application, which then compares this identifier with a unique identifier that it has received from the customer application.If a match is found, the registration application transmits the connection data, which was also previously received from the customer application, to the first IP-enabled device. Using the connection data, the first IP-enabled device preferably establishes a secure communication connection to the customer application (81).

[0006] The aforementioned technical problem is solved by the process steps of claim 1.

[0007] Accordingly, a method is provided which makes it possible, in particular, to connect at least one IP-capable device to a cloud-based customer application using a cloud-based registration application, wherein the cloud-based customer connection and the cloud-based registration application are designed for exchanging data.The method preferably comprises the following steps: a) providing a first IP-enabled device, wherein the first IP-enabled device stores initial connection data for establishing a communication connection to the cloud-based registration application, and wherein the first IP-enabled device is assigned at least one unique identifier; b) establishing, using the initial connection data, a communication connection from the first IP-enabled device to the cloud-based registration application; c) transmitting the at least one unique identifier assigned to the first IP-enabled device from the first IP-enabled device to the cloud-based registration application via the established communication connection; d) transferring at least one unique identifier to the cloud-based customer application; e) transferring the at least one unique identifier transferred in step d) from the cloud-based customer application to the cloud-based application.

[0008] Registration application; f) Transferring second connection data, by means of which a communication connection to the cloud-based customer application can be established, from the cloud-based customer application to the cloud-based registration application; g) Checking, by the cloud-based registration application, whether the at least one unique identifier passed in step d) matches the at least one unique identifier of the first IP-enabled device transferred in step c); if so h) Transferring the second connection data from the cloud-based registration application to the first IP device; and i) Establishing, using the second connection data transferred in step h), a communication connection from the first IP-enabled device to the cloud-based customer application in order to connect the first IP-enabled device to the cloud-based customer application.

[0009] It should be noted that the at least one unique identifier passed in step d) is preferably the at least one unique identifier of an IP-enabled device which is to be connected to the cloud-based customer application.

[0010] To enable efficient connection of the first IP-enabled device to the cloud-based customer application, step f) is preferably executed immediately after step g). Step f) comprises the following steps:

[0011] Transferring a confirmation message from the cloud-based registration application to the cloud-based customer application if a match has been found in step g);

[0012] Transferred, upon receipt of the confirmation message, the second connection data from the cloud-based customer application to the cloud-based registration application.

[0013] In order to transfer the second connection data and the at least one identifier passed in step d) to the cloud-based registration application, it is expedient to first establish a communication connection from the cloud-based customer application to the cloud-based registration application in step e), preferably via an IP-based network such as the Internet.

[0014] Advantageously, in step e), a communication connection can be established from the cloud-based customer application to the cloud-based registration application by addressing at least one unique identifier passed in step d). This communication connection can be a secure Layer 2 tunnel connection.

[0015] It should be noted that the communication links established in step b) and / or i) can also preferably be established via an IP-based network, such as the Internet.

[0016] The communication link established in step i) is preferably established from the first IP-enabled device to the cloud-based customer application using the Layer 2 Tunneling Protocol (L2TP) network protocol. To enable secure data transmission over the established communication link, the Internet Protocol Security (IPsec) protocol stack, for example, can be implemented in the first IP-enabled device.

[0017] It is expedient that after step i) has been carried out, the communication connection established in step b) between the first IP-enabled device and the cloud-based registration application is terminated and the at least one unique identifier of the first IP-enabled device transferred to the cloud-based registration application in step c) is deleted.

[0018] It is expedient for step d) to comprise the following steps:

[0019] Registering an authorized person to the cloud-based customer application using a communication device, such as a PC or mobile phone; and providing the at least one unique identifier to the communication device and transferring the at least one unique identifier from the communication device to the cloud-based customer application.

[0020] In step c), it is advantageous to store at least one unique identifier of the first IP-enabled device, for example, in a database that the cloud-based registration application can access.

[0021] It should be noted that the cloud-based customer application and the cloud-based registration application can run on a shared host computer or on different host computers within a cloud-based computer network. Alternatively, the cloud-based customer application and the cloud-based registration application can be hosted on different cloud-based computer networks.

[0022] An advantageous extension provides that step a) comprises the following steps: providing at least one additional IP-enabled device, wherein the first IP-enabled device and the at least one additional IP-enabled device are located at different locations, wherein the initial connection data for establishing a communication connection to the cloud-based registration application is stored in the at least one additional IP-enabled device, wherein at least one unique identifier is assigned to the at least one additional IP-enabled device, and wherein steps b) to i) are repeated for the at least one additional IP-enabled device. According to an advantageous further development, the cloud-based customer application may implement a switch functionality or a data logger.

[0023] Thanks to the method according to the invention, multiple IP-enabled devices, which may be located at different, even widely separated, locations, can be connected to the cloud-based customer application in a simple and cost-effective manner. In this way, a local network can be set up across several different locations.

[0024] It should be noted that the first and at least one subsequent IP-enabled device can each constitute a network participant in a separate local network, with each of the IP-enabled devices being configured, for example, as a router or control device with integrated router functionality. Each of the IP-enabled devices can have one IP-based interface for connecting to the cloud-based customer application and another IP-based interface assigned to the respective local network.

[0025] To increase security, each IP-enabled device can be assigned at least two different individual identifiers.

[0026] A unique identifier can be printed on the respective IP-enabled device, for example as a 2D martix code or in plain text. Another unique identifier can be printed on a slip of paper placed inside the packaging of the respective IP-enabled device.

[0027] The invention will be explained in more detail below with reference to an exemplary embodiment in conjunction with the accompanying drawings. These show:

[0028] Figure 1 shows a schematic representation of an exemplary network system with two local networks and two cloud-based computer networks hosting a cloud-based customer application and a cloud-based registration application, respectively, and Figure 2 shows the exemplary network system shown in Figure 1 after successful connection of the two local networks to the cloud-based customer application.

[0029] Detailed description of the invention

[0030] Figure 1 shows a schematic representation of an exemplary network system 200, which can be used, for example, in the implementation and configuration of a cross-site automation system.

[0031] For example, network system 200 comprises two separate cloud-based computer networks 80 and 90, each comprising several interconnected computers and data storage devices in a manner known per se. For simplicity, Figure 1 shows a customer-based cloud platform 83 and a data storage device 82 implemented in cloud-based computer network 80, and a cloud platform 93 and a data storage device 92 implemented in cloud-based computer network 90.

[0032] According to an exemplary implementation shown in Figure 1, assume that a customer has created a cloud-based customer application 81 in the cloud platform 83 of the cloud-based computer network 80 using, for example, a personal computer 70. The cloud platform 83 acts as a programming interface for the customer. It is known that, in order to create the cloud-based customer application 81, the customer must have created an account in the cloud platform 83 of the cloud-based computer network 80 in a manner known per se, to which they can log in, for example, using two-factor authentication in a manner known per se. Once the customer has logged into their customer account, they can, for example, create the cloud-based customer application 81 in the cloud platform 83.The cloud-based customer application 81 can, for example, implement a software-implemented switch to which several geographically distributed local networks, such as the two geographically separated local networks 100 and 110, can be connected. It should be noted that the cloud-based customer application 81 can also implement a central data collector, a so-called data logger, which can collect data provided by the two networks 100 and 110 and store it in the data storage 82 as soon as the two networks 100 and 110 are connected to the cloud-based customer application 81. The method by which the two local networks 100 and 110 can be connected to the cloud-based customer application 81 is explained in detail below.For example, let's assume that local network 100 is to be installed in a factory hall in Berlin and local network 110 is to be installed in a factory hall in Munich, or has already been installed. Using cloud-based customer application 81, which, for example, performs switching functionality, a cross-site automation system can then be implemented for the customer.

[0033] The two local networks, 100 and 110, can each form a LAN (Local Area Network) or a WLAN (Wireless Local Area Network). In this case, it is assumed that both local networks, 100 and 110, are configured as fieldbus systems with multiple network participants. Communication via such a fieldbus system can be based, for example, on the Profibus standard or an Industrial Ethernet standard such as Profinet.

[0034] For illustrative purposes only, the local network 100 has four network participants 101-104. Network participant 101 is an IP-enabled device, which can be configured, for example, as a router or as a control unit, preferably with an integrated software and / or hardware router. The local network 100 can be connected to the cloud-based customer application 81 via the IP-enabled device 101, as will be explained in more detail below. For this purpose, the IP-enabled device 101 can have an IP-based interface 101.1, which is shown in Figure 2. The IP-based interface 101.1 can be permanently or temporarily assigned an IP address known to the cloud-based customer application 81. Furthermore, as shown in Figure 2, the IP-enabled device 101 can have another IP-enabled interface 101.2, which serves for communication with the other network participants 102-104.The network participants 102-104 can each be configured as a field device, for example as an actuator or sensor.

[0035] Similarly, the local network 110 can have four network participants 111-114. The network participant 111 is an IP-enabled device, which can be configured, for example, as a router or as a control device, preferably having an integrated software and / or hardware router. The local network 110 can be connected to the cloud-based customer application 81 via the IP-enabled device 111, as will be explained in more detail below. For this purpose, the IP-enabled device 111 can have an IP-based interface 111.1, which is shown in Figure 2. The IP-based interface 111.1 can be permanently or temporarily assigned an IP address known to the cloud-based customer application 81. Furthermore, as shown in Figure 2, the IP-enabled device 111 can have another IP-enabled interface 111.2, which serves for communication with the other network participants 112-114.The network participants 112-114 can each be configured as a field device, for example as an actuator or sensor.

[0036] It should be noted here that each IP-enabled device, in this case the two IP-enabled devices 101 and 111, which are to be connected to the cloud-based customer application 81, is assigned at least one unique identifier. Such a unique identifier can, for example, be printed on the respective IP-enabled device and / or stored in the IP-enabled device, particularly before its delivery, in the form of a 2D matrix code or in plain text. Additionally, for example, another unique identifier, which is included on an insert, can be provided in the packaging of each IP-enabled device. For the sake of illustration, let us assume that each of the two IP-enabled devices 101 and 111 is assigned two unique identifiers, referred to as passwords in Figure 1.

[0037] Furthermore, it is assumed that a cloud-based registration application 91 has been created by an operator in the cloud platform 93 of the cloud-based computer network 90. ​​During a connection process, the IP-enabled devices, in this example IP-enabled devices 101 and 111, which are to be connected to the cloud-based customer application 81, are temporarily registered with the cloud-based registration application 91. The cloud-based registration application 91 is also configured to check whether IP-enabled devices have been registered that a customer wishes to connect to the cloud-based customer application 81.

[0038] It should be noted that, depending on the implementation, the cloud-based customer application 81 and the cloud-based registration application 91 can also be hosted by a shared cloud-based computer network, for example, the cloud-based computer network 80. It is conceivable that the cloud-based customer application 81 and the cloud-based registration application were created and are hosted on the cloud platform 83 of the cloud-based computer network 80.

[0039] The procedure for connecting at least one IP-enabled device to the cloud-based customer application 81 is explained in more detail below, particularly using the IP device 111 as an example. According to the embodiment shown in Figure 1, the two IP-enabled devices 101 and 111, or the two networks 100 and 110, are to be connected to the cloud-based customer application 81.

[0040] It is initially assumed that prior to delivery, initial connection data, preferably permanently stored, is present in both the first IP-enabled device 111 and the second IP-enabled device 101. This initial connection data is required to establish a communication connection to the cloud-based registration application 91. In particular, this initial connection data includes a Uniform Resource Identifier (URI) that uniquely addresses the cloud-based registration application 91. Furthermore, at least one unique identifier is assigned to both the IP-enabled device 111 and the IP-enabled device 101.For example, the IP-enabled devices 101 and 111 are each assigned two individual identifiers, namely, for example, a device-specific password, which may be printed directly on the IP-enabled devices 101 and 111, for example, as a 2D matrix code, and furthermore, for example, a device-specific serial number, which may be printed on a slip of paper included in the packaging.

[0041] It is further assumed that the IP-capable device 111 has already been unpacked and set up by an operator in the factory hall at the Munich site and connected to a public IP-based data network, for example the Internet.

[0042] Furthermore, it is assumed that the cloud-based customer application 81 is aware of secondary connection data. This secondary connection data can, for example, be transmitted from the customer via PC 70 to the cloud platform 83 during a configuration phase and stored in data storage 82, with the cloud-based customer application 81 having access to data storage 82. The secondary connection data contains the unique address of the cloud-based customer application. This unique address can be in the form of a Uniform Resource Locator (URI).

[0043] Using the second set of connection details, as will be explained later, the two IP-enabled devices 101 and 111 can each establish a communication connection to the cloud-based customer application 81, for example, via a public data network such as the internet. Furthermore, the cloud-based customer application 81 knows the address of the cloud-based registration application 91, which can be in the form of a Uniform Resource Identifier (URI). The address of the cloud-based registration application 91 can, for example, be transmitted from the customer via PC 70 to the cloud platform 83 during a configuration phase and stored in the data storage 82.

[0044] Now, using the initial connection data, a temporary communication connection 30 (dashed line in Figure 1) is established via the internet from the first IP-enabled device 111 to the cloud-based registration application 91. For this purpose, the customer can, for example, press a special button or perform another active action on the IP-enabled device 111 to initiate the connection. In other words, the IP-enabled device 111 is preferably configured to establish a communication connection to the cloud-based registration application 81 when a button is manually pressed. Alternatively, the IP-enabled device 111 could also be configured to automatically establish a communication connection 30 to the registration application 91 as soon as it is connected to the internet.

[0045] It should also be noted that the two individual identifiers of the IP-enabled device 111 are either pre-stored in the device 111 or can be manually entered on the IP-enabled device 111. After the communication connection 30 to the cloud-based registration application 91 has been established, the IP-enabled device 111 transmits the two individual identifiers to the cloud-based registration application 91 for identification purposes in step 1, as shown in Figure 1. The identifiers can be stored in the data storage 92.

[0046] To connect the IP-enabled device 111, and thus the local network 110, to its cloud-based customer application 81, the customer first logs into its account on the cloud platform 83 via its computer 70, or alternatively via a mobile phone. If there are several different customer applications, the customer selects application 81, for example, by entering a predefined identifier specifying the cloud-based customer application 81 via computer 70. The communication link between PC 70 and the cloud-based customer application 81, or the cloud platform 83, is indicated by the dashed line 10.

[0047] Within the cloud-based customer application 81, which, for example, implements a switch, the customer can now select a specific port of the switch to which the IP-enabled device 111 is to be connected. Subsequently, as shown in step 2 of Figure 1, the customer enters the known unique identifiers of the IP-enabled device 111 into their computer 70, which transmits these unique identifiers to the customer application 81 via the communication link 10. In this way, for example, the two unique identifiers of the IP-enabled device 111 are transferred to the cloud-based customer application 81.

[0048] According to an exemplary implementation, the cloud-based customer application 81 establishes a communication connection 20, for example via the internet, to the cloud-based registration application 91 by addressing the two identifiers received from computer 70. In step 3, the cloud-based customer application 81 then transmits the individual identifiers of the IP-enabled device 111, entered by the customer via their computer 70, to the registration application 91. According to a preferred implementation, the cloud-based registration application 91 then checks whether the individual identifiers transmitted in step 3 match the two individual identifiers that were previously transmitted to it by the IP-based device 111 and stored, for example, in the data storage 92.If a match is found, the cloud-based registration application 91 generates a confirmation message and transmits this message in step 4 via communication link 20 to the cloud-based customer application 81. Upon receiving the confirmation message, the cloud-based customer application 81 transmits the second connection data in step 5 via communication link 20 to the cloud-based registration application 91. As mentioned previously, the connection data includes the address of the cloud-based customer application 81, which in turn can be specified in the form of a Uniform Resource Identifier (URI).

[0049] The cloud-based registration application 91 is preferably configured, in step 6, to transmit the connection data received from the cloud-based customer application 81 via the communication link 30 to the IP-enabled device 111 and subsequently to delete the identifiers of the IP device 111 stored in the data store 92 and the second connection data received by the cloud-based customer application 81. The cloud-based customer application 81 is preferably configured to terminate the communication link 20 to the cloud-based registration application 91 after successful transmission of the individual identifiers of the IP-enabled device 111 and the second connection data.

[0050] After the IP-enabled device 111 has received the second connection data from the cloud-based registration application 91, the IP-enabled device 111 terminates the communication connection 30 to the cloud-based registration application 91.

[0051] The IP-enabled device 111 is further configured to establish a communication connection 60 to the cloud-based customer application 81 using the second connection data received from the cloud-based registration application 91. The communication connection 60 is preferably a secure Layer 2 communication connection, i.e., a connection at the data link layer of the OSI reference model. The IP-enabled device 111 can preferably establish the communication connection 60 over an IP-based data network, e.g., the Internet, using the Layer 2 Tunneling Protocol (L2TP) network protocol. To enable secure data transmission over the established communication connection 60, the Internet Protocol Security (IPsec) protocol stack, for example, can be implemented in the first IP-enabled device 111.The cloud-based customer application 81, which implements a switch, for example, now ensures that the communication link 60 is connected to the port selected by the customer.

[0052] The cloud-based customer application 81 can be configured to notify the customer via PC 70 or a mobile phone that the IP device 111, and thus the local network 110, has been properly connected. The address of PC 70 or the mobile phone required for this is known to the cloud-based customer application 81. Advantageously, during a configuration phase of the cloud-based customer application 81, the address of the customer's computer 70 or mobile phone can be communicated and preferably stored in the data storage 82.

[0053] According to an alternative implementation, in step 3, the cloud-based customer application 81 can transmit not only the individual identifiers of the IP device 111 received from computer 70, but also the second connection data to the cloud-based registration application 91. In this case, no confirmation message is generated by the registration application 91 and transmitted to the customer application 81 in step 4.

[0054] The connection of the IP-enabled device 101 or the local network 100 to the cloud-based customer application 81 is preferably carried out analogously to the connection of the IP-enabled device 111.

[0055] Let us now assume that the IP-enabled device 101 has already been unpacked and set up by an operator in the factory hall at the Berlin site and connected to a public IP-based data network, such as the internet. Furthermore, let us assume, for the sake of argument, that the connection of the IP-enabled device 101 only takes place after the IP-enabled device 111 has been connected to the cloud-based customer application 81.

[0056] Now, using the initial connection data, a temporary communication connection 40 (dashed line in Figure 1) is established via the internet from the first IP-enabled device 101 to the cloud-based registration application 91. For this purpose, the customer can, for example, press a special button or perform another active action on the IP-enabled device 101 to initiate the connection. In other words, the IP-enabled device 101 is preferably configured to establish a communication connection to the cloud-based registration application 81 when a button is manually pressed. Alternatively, the IP-enabled device 101 could also be configured to automatically establish a communication connection 40 to the registration application 91 as soon as it is connected to the internet.It should also be noted that the two individual identifiers of the IP-enabled device 101 are either pre-stored in the device 101 or can be manually entered on the IP-enabled device 101. After the communication connection 40 to the cloud-based registration application 91 has been established, the IP-enabled device 101 transmits its two individual identifiers to the cloud-based registration application 91 for identification purposes. The identifiers can be stored in the data storage 92.

[0057] To connect the IP-enabled device 101, and thus the local network 100, to the cloud-based customer application 81, the customer first logs into their account on the cloud platform 83 via their computer 70, or alternatively via a mobile phone. If there are several different customer applications, they select application 81, for example, by entering a predefined identifier specifying the cloud-based customer application 81 on their computer 70. The communication link between the PC 70 and the cloud-based customer application 81, or the cloud platform 83, is indicated by the dashed line 10.

[0058] Within the cloud-based customer application 81, which implements a switch, for example, the customer can now select a specific port of the switch to which the IP-enabled device 101 is to be connected.

[0059] The customer then enters the known individual identifiers of the IP-enabled device 101 into their computer 70, which transmits the individual identifiers to the customer application 81 via the communication link 10. In this way, for example, the two individual identifiers of the IP-enabled device 101 are transferred to the cloud-based customer application 81.

[0060] According to an exemplary implementation, cloud-based customer application 81 establishes a communication connection 20, for example via the internet, to cloud-based registration application 91 by addressing the two identifiers received from computer 70. Subsequently, cloud-based customer application 81 transmits the individual identifiers of the IP-enabled device 101, entered by the customer via their computer 70, to registration application 91. According to a preferred implementation, cloud-based registration application 91 then checks whether the transmitted individual identifiers match the two individual identifiers that were previously transmitted to it by the IP-based device 101 and stored, for example, in data storage 92.If a match is found, the cloud-based registration application 91 generates a confirmation message and transmits this message to the cloud-based customer application 81 via communication link 20. Upon receiving the confirmation message, the cloud-based customer application 81 transmits the second connection data to the cloud-based registration application 91 via communication link 20. As mentioned previously, the connection data includes the address of the cloud-based customer application 81, which in turn can be specified in the form of a Uniform Resource Identifier (URI).

[0061] The cloud-based registration application 91 is preferably configured to transmit the connection data received by the cloud-based customer application 81 to the IP-enabled device 101 via the communication link 30 and subsequently to delete the identifiers of the IP device 101 stored in the data store 92 and the second connection data received by the cloud-based customer application 81. The cloud-based customer application 81 is preferably configured to terminate the communication link 20 to the cloud-based registration application 91 after successful transmission of the individual identifiers of the IP-enabled device 101 and the second connection data.

[0062] After the IP-enabled device 101 receives the second connection data from the cloud-based registration application 91, it terminates the communication connection 40 to the cloud-based registration application 91. The IP-enabled device 101 is further configured to establish a communication connection 50 to the cloud-based customer application 81 using the second connection data received from the cloud-based registration application 91. The communication connection 50 is preferably a secure Layer 2 communication connection, i.e., a connection at the data link layer of the OSI reference model. The IP-enabled device 101 can preferably establish the communication connection 50 over an IP-based data network, e.g., the Internet, using the Layer 2 Tunneling Protocol (L2TP) network protocol.To enable secure communication transmission over communication link 60, Internet Protocol Security (IPsec) can be used. The cloud-based customer application 81, which, for example, implements a switch, now ensures that communication link 50 is connected to the port selected by the customer.

[0063] The cloud-based customer application 81 can be configured to notify the customer via PC 70 or a mobile phone that the IP device 101, and thus the local network 100, has been properly connected. The address of PC 70 or the mobile phone required for this is known to the cloud-based customer application 81. Advantageously, during a configuration phase of the cloud-based customer application 81, the address of the customer's computer 70 or mobile phone can be communicated and preferably stored in the data storage 82.

[0064] According to an alternative implementation, the cloud-based customer application 81 can transmit not only the individual identifiers of the IP device 111 received from computer 70, but also the second connection data simultaneously to the cloud-based registration application 91. In this case, no confirmation message is generated by the registration application 91 and transmitted to the customer application 81. It should be noted that several IP-enabled devices intended to be connected to the cloud-based customer application 81 can be registered with the cloud-based registration application 91 simultaneously. For example, the two IP-enabled devices 101 and 111 could each be activated simultaneously by an operator to establish a communication connection 40 or 30, respectively, and transmit their respective device-specific identifiers to the cloud-based registration application 91.Subsequently, the corresponding device-specific identifiers of the IP-enabled devices 101 and 111 can be transmitted by the customer via PC 70 to the cloud-based customer application 81 and from there forwarded via an established connection 20 to the cloud-based registration application 91. According to an advantageous implementation, the cloud-based registration application 91 checks whether the device-specific identifiers received by the cloud-based customer application 81 concerning the IP-enabled devices 101 and 111 match the individual identifiers received by the two IP-enabled devices 101 and 111. If this is the case, a confirmation message, for example, is transmitted from the cloud-based registration application 91 to the cloud-based customer application 81.Upon receiving the confirmation message, the cloud-based customer application transmits the second connection data to the cloud-based registration application 91, which then transmits this connection data to the two IP-enabled devices 101 and 111. As previously explained, the communication connections 30 and 40 are subsequently terminated, and the individual identifiers of the IP-enabled devices 101 and 111, as well as the second connection data (which was preferably cached in data storage 92), are deleted by the cloud-based registration application 91. Using the second connection data, the IP-enabled devices 101 and 111 then each establish a communication connection 50 and 60, respectively, to the cloud-based customer application.

[0065] Figure 2 shows a successful connection of the two IP-enabled devices 101 and 111, or a connection of the two local networks 100 and 110, to the cloud-based customer application 81. Connections to the cloud-based registration application 91 no longer exist in this case. Furthermore, all data relating to the two IP-enabled devices 101 and 111, as well as the connection data of the customer application 81, have been deleted by the registration application 91.

Claims

Patent claims 1. A method for connecting at least one IP-enabled device (101, 111) to a cloud-based customer application (81) using a cloud-based registration application (91), wherein the cloud-based customer application (81) and the cloud-based registration application (91) are configured for exchanging data, the method comprising the following steps: a) providing a first IP-enabled device (111), wherein the first IP-enabled device (111) stores initial connection data for establishing a communication connection (30) to the cloud-based registration application (91), and wherein the first IP-enabled device (111) is assigned at least one unique identifier; b) establishing, using the initial connection data, a communication connection (30) from the first IP-enabled device (111) to the cloud-based registration application (91);c) Transferring at least one unique identifier assigned to the first IP device (111) from the first IP-enabled device (111) via the established communication link (30) to the cloud-based registration application (91); d) Transferring at least one unique identifier to the cloud-based customer application (81); e) Transferring at least one unique identifier transferred in step d) from the cloud-based customer application (81) to the cloud-based registration application (91); f) Transferring two connection details, by means of which a communication link to the cloud-based customer application (81) can be established, from the cloud-based customer application (81) to the cloud-based registration application (91);(g) Check, using the cloud-based registration application (91), whether the at least one unique identifier transmitted in step d) matches the at least one unique identifier of the first IP-enabled device (111) transmitted in step c); if so; h) Transferring the second connection data from the cloud-based registration application (91) to the first IP-enabled device (111); and i) Establishing, using the second connection data transferred in step h), a communication link (60) from the first IP-enabled device (111) to the cloud-based customer application (81) to connect the first IP-enabled device (111) to the cloud-based customer application (81).

2. The method of claim 1, wherein Step f) is performed immediately after step g) and comprises the following steps: Transfer of a confirmation message from the cloud-based registration application (91) to the cloud-based customer application (81) if a match has been established in step g); Transferred, upon responding to the confirmation message, the second connection data from the cloud-based customer application (81) to the cloud-based registration application (91).

3. Method according to claim 1 or 2, wherein Step e) includes the following further step: Establishing a communication link (20) from the cloud-based customer application (81) to the cloud-based registration application (91).

4. Method according to claim 3, wherein Step e) includes the following step: Establish, by addressing at least one unique identifier passed in step d), the communication link (20) from the cloud-based customer application (81) to the cloud-based registration application (91).

5. Method according to any one of the preceding claims, wherein, after execution of step i), the assembly constructed in step b) The communication link (30) between the first IP-enabled device (111) and the cloud-based registration application (91) is terminated and at least one unique identifier of the first IP-enabled device (111) transmitted to the cloud-based registration application (91) in step c) is deleted.

6. Method according to any one of the preceding claims, wherein Step d) comprises the following steps: Login of an authorized person to the cloud-based customer application (81) using a communication device (70); Providing at least one identifier to the communication device (70) and transmitting at least one identifier from the communication device (70) to the cloud-based customer application (81).

7. Method according to any one of the preceding claims, wherein Step c) includes the following further step: Storing at least one unique identifier of the first IP-enabled device (111).

8. A method according to any one of the preceding claims, wherein step a) comprises the following steps: Providing at least one additional IP-enabled device (101), wherein the first IP-enabled device (111) and the at least one additional IP-enabled device (101) are located at different locations, wherein the first connection data for establishing a communication connection (4) to the cloud-based registration application (91) are stored in the at least one additional IP-enabled device (101), and wherein at least one unique identifier is assigned to the at least one additional IP-enabled device (101), wherein steps b to i) are repeated for the at least one additional IP-enabled device (101).

9. Method according to any of the preceding claims, wherein the cloud-based customer application (81) implements a switch functionality.

10. Method according to one of the preceding claims, wherein each of the IP-capable devices (101, 111) is assigned at least two different individual identifiers.

Images