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

Description

2 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 by means of 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, in particular a temporary one. Via a temporary communication connection, one IP-enabled device transmits at least its unique identifier to the registration application, wherein the registration application combines this identifier with a unique identifier that it has received from the customer application.10 compares. Upon match, the registration application transmits the connection data, 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). 15 The aforementioned technical problem is solved by the method step of claim 1. Accordingly, a method is provided which, in particular, enables the connection of at least 20 at least one IP-enabled 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 configured for exchanging data. The method preferably comprises the following steps: 25 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) Establish, using the first connection data, a communication connection from the first IP-enabled device to the cloud-based registration application; BE2024 / 5901 3 c) Transmit at least one unique identifier assigned to the first IP device from the first IP-enabled device via the established communication connection to the cloud-based registration application; d) Transfer at least one unique identifier to the cloud-based customer application; e) Transfer at least one unique identifier from the cloud-based customer application to the cloud-based registration application; f) Transfer 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) Verify through the cloud-based registration application,whether at least one unique identifier passed in step d) matches at least one unique identifier of the first IP-enabled device passed in step c); if yes, 15 h) transfer the second connection data from the cloud-based registration application to the first IP device; and i) establish, using the second connection data transferred in step h), a communication connection from the first IP-enabled device to the cloud-based customer application to connect the first IP-enabled device to the cloud-based customer application. Note that at least one unique identifier passed in step d) is preferably one unique identifier of an IP-enabled device to be connected to the cloud-based customer application. 25 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: 30. Transmitting a confirmation message from the cloud-based registration application to the cloud-based customer application if a match has been established in step g) BE2024 / 5901 4; 5. Transmitting, upon responding to the confirmation message, the second connection data from the cloud-based customer application to the cloud-based registration application. 6. In order to be able to transmit the second connection data and 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.10 Advantageously, in step e) by addressing at least one individual identifier, a communication connection can be established from the cloud-based customer application to the cloud-based registration application. The communication connection can be a 15 secure Layer 2 tunnel connection. It should be noted that the communication connections established in step b) and / or i) can also preferably be established via an IP-based network, such as the Internet.20 The communication connection 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 connection,25. The Internet Protocol Security (IPsec) protocol stack may be implemented in the first IP-enabled device, for example. It is expedient that, after completion of step i), the communication link established in step b) between the first IP-enabled device and the cloud-based registration application is closed and the least unique identifier of the first IP-enabled device transferred to the cloud-based registration application is deleted. It is expedient that step d) includes the following steps: logging an authorized person into the cloud-based customer application using their communication device, such as a PC or mobile phone; and providing the least unique identifier to the communication device and transferring the least unique identifier from the communication device to the cloud-based customer application. 10. In step c), at least one unique identifier of the first IP-enabled device can be entered, for example, in a database.The data that the cloud-based registration application can access will be stored. 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. An advantageous extension provides that step a) includes the following steps: Deploying at least one additional IP-enabled device, wherein the first IP-enabled device and the at least one additional IP-enabled device are located in different locations, wherein the at least one additional IP-enabled device stores the initial connection data for establishing a communication connection to the cloud-based registration application, and wherein the at least one additional IP-enabled device is assigned at least one unique identifier.and wherein the steps (ebbisi) are repeated for at least one additional IP-enabled device. 30 BE2024 / 5901 6 According to an advantageous further development, the cloud-based customer application can implement a switch functionality or a data logger. Thanks to the method according to the invention, several 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. It should be noted that the first and at least one subsequent IP-enabled device can each form a separate local network with up to 10 network participants, 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 that is assigned to the respective local network.15 exhibit. To increase security, at least two different unique identifiers can be assigned to each IP-enabled device. 20 One unique identifier can, for example, be printed on the respective IP-enabled device as a 2D martix code or in plain text. Another unique identifier can, for example, be printed on a slip of paper that is placed in the packaging of the respective IP-enabled device. 25 The invention is explained in more detail below with reference to an embodiment in conjunction with the accompanying drawings. In these, Figure 1 shows, in schematic representation, an exemplary network system with two local area networks and two cloud-based computer networks, which 30 host a cloud-based customer application and a cloud-based registration application, respectively.and BE2024 / 5901 7 Figure 2 the exemplary network system shown in Figure 1 after a successful connection of the two local networks to the cloud-based customer application. 5 Detailed description of the invention Figure 1 shows a schematic representation of an exemplary network system 200, which can be incorporated, for example, in the implementation and configuration of a multi-site automation system. 10 The network system 200 has, for example, two separate cloud-based computer networks 80 and 90, each having several interconnected computers and data storage devices in a manner known per se. For the sake of simplicity, Figure 1 shows a customer-based cloud platform 83 and a data storage device 15 82, which are implemented in the cloud-based computer network 80, and a cloud platform 93 and a data storage device 92, which are implemented in the cloud-based computer network 90. Assumed according to an exemplary implementation shown in Figure 1,20 that a customer, for example, using a personal computer 70, has created a cloud-based customer application 81 in the cloud platform 83 of the cloud-based computer network 80. The cloud platform 83 appears to the customer as a programming interface. It is known that, in order to create the cloud-based customer application 81, the customer must have created an account 25 in the cloud platform 83 of the cloud-based computer network 80 in a manner known to them, which they can log in to, for example, via two-factor authentication. 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, which can connect, for example, several geographically distributed local area networks, such as the two BE2024 / 5901 8 Local networks 100 and 110, which are located far apart from each other, can be connected. It should be noted at this point that...that the cloud-based customer application 81 can also implement a central data collector, the so-called data logger, which can, for example, collect data provided by the two networks 100 and 110 and store it in the data storage 82 as soon as the two networks 1005 and 110 are connected to the cloud-based customer application 81. The way in which the two local networks 100 and 110 can be connected to the cloud-based customer application 81 is explained in detail below. Suppose, for example, that the local network 100 is to be installed in a factory hall in Berlin and the local network 110 is to be installed in a factory hall in Munich 10, or has already been installed. With the help of the,For example, a cloud-based customer application executing switch functionality81 can then be implemented, for example, as a cross-site automation system for the customer. 15 The two local networks 100 and 110 can, for example, each form a LAN (Local Area Network) or a WLAN (Wireless Local Area Network). In the present case, it is assumed that the two local networks 100 and 110 are each configured as a fieldbus system with multiple network participants. Communication via such a fieldbus system can, for example, be based on the 20 Profibus standard or an Industrial Ethernet standard, such as Profinet. For illustrative purposes only, the local network 100 has four network participants 101-104. Network participant 101 is an IP-enabled device, which is, for example, a router or a control device that preferably has an integrated software and / or hardware-implemented router.The IP-enabled device 101 can connect the local network 100 to the cloud-based customer application 81, as 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-30 address, which is known to the cloud-based customer application 81. Furthermore, as shown in Figure 2, the IP-enabled device 101 can have another IP-enabled BE2024 / 5901 9 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. Similarly, the local network 110 can have four network participants 111-1145. The network participant 111 is an IP-enabled device, which is, for example, a router or a control device that preferably has an integrated software and / or hardware-implemented router.The IP-enabled device 111 can connect the local network 110 to the cloud-based customer application 81, as 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 that is 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 15 network participants 112-114. The network participants 112-114 can each be configured as a field device, for example as an actuator or sensor. It should be noted here that IP-enabled devices, in this case the two IP-enabled devices 101 and 111, which are to be connected to the cloud-based customer application 20 81,Each device 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 delivery, in the form of a 2D matrix code or in plain text. Additionally, for example, a further unique identifier, which is printed on an insert, can be included in the packaging of each IP-enabled device. For the sake of illustration, let us assume that the two IP-enabled devices 101 and 111 are each assigned two unique identifiers, referred to as passwords in Figure 1. 30 Furthermore, it is assumed that its cloud-based registration application 91 in the cloud platform 93 of the cloud-based computer network 90 has been created by an operator 10. In the cloud-based registration application 91, during a connection process, the IP-enabled devices, in this example the IP-enabled devices 101 and 111, which are to be connected to the cloud-based customer application 81,temporarily registered. The cloud-based registration application 91 is further trained to check whether IP-enabled 5 devices have been logged in or registered that a customer wishes to connect to the cloud-based customer application 81. At this point, it is noted that, depending on the implementation, the cloud-based customer application 81 and the cloud-based registration application 91 may also be hosted by 10 a common cloud-based computer network, for example, the cloud-based computer network 80. In this respect, it is conceivable thatthat the cloud-based customer application 81 and the cloud-based registration application were created in the cloud platform 83 of the cloud-based computer network 80 and are hosted there. 15 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. First, assume that prior to delivery, initial connection data, preferably permanently stored, has been stored in the first IP-enabled device 111 and the second IP-enabled device 101, which is required to establish a 25 communication connection to the cloud-based registration application 91. The initial connection data includes, in particular, a Uniform Resource Identifier (URI),the cloud-based registration application91 uniquely addresses. In addition, at least one unique identifier is assigned to each IP-enabled device111 and each IP-enabled device101. For example, each IP-enabled device101 and 111 is assigned two unique identifiers, namely, for example, a device-specific password, which may be printed directly on the IP-enabled device BE2024 / 5901 11 101 and 111, for example, as a 2D matrix code, and furthermore, for example, a device-specific serial number, which may be printed, for example, on a slip of paper enclosed with the packaging. It is further assumed that the IP-enabled device111 has already been unpacked5 and set up by an operator in the factory hall at the Munich location and connected to a public IP-based data network, for example, the Internet. It is further assumed thatthat the cloud-based customer application 81 knows second connection data. The second connection data can, for example, be transmitted from the customer via the PC 70 to the cloud platform 83 during a configuration phase and stored in the data store 82, with the cloud-based customer application 81 having access to the data store 82. The second connection data contains the unique address of the cloud-based customer application 15. The unique address can be in the form of a Uniform Resource Locator (URI). Using the second connection data, as will be explained later, the two IP-enabled devices 101 and 111 can each establish a communication connection, for example, 20, to the cloud-based customer application 81 via a public data network, such as the Internet. In addition, the cloud-based customer application 81 knows the address of the cloud-based registration application 91.where the address can again be in the form of a Uniform Resource Identifier (URI). The address of the cloud-based registration application91 can, for example, be transferred from the customer via the PC70 to the cloud platform83 during25 a configuration phase and stored in the data storage 82. 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 key on the IP-enabled device 111 or perform another active action on the device 111 to initiate the connection setup. In other words, the IP-enabled device 111 is preferably configured to establish a communication connection to the cloud-based registration application 81 upon manual key press. Alternatively, the IP-enabled device 1115 could also be configured toto automatically establish a communication connection 30 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 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 15 in the data storage 92. To connect the IP-enabled device 111 and thus the local network 110 to a 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, and selects the customer application 81 if there are several different customer applications, for example by selecting a predefined,The cloud-based customer application 81 specifies the identifier via the 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 1025. Within the cloud-based customer application 81, which, for example, implements a switch, the customer can again select a specific port of the switch to which the IP-enabled device 111 is to be connected. 30 BE2024 / 5901 13 Subsequently, as shown in step 2 of Figure 1, the customer enters the known individual identifiers of the IP-enabled device 111 into their computer 70.which transmits the individual identifiers via the communication connection 10 to the customer application 81. In this way, for example, the two individual identifiers of the IP-enabled device 111 are transferred to the cloud-based 5 customer application 81. According to an exemplary implementation, the cloud-based customer application 81 establishes a communication connection 20, for example via the 10 Internet, to the cloud-based registration application 91 by addressing the two identifiers received from the 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 15 now 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 20 in step 4 via the communication connection 20 to the cloud-based customer application 81. Responding to the confirmation message, the cloud-based customer application 81 transmits the second connection data via the communication connection 20 to the cloud-based registration application 91 in step 5. The connection data includes, as already mentioned, the address of the cloud-based customer application 81, which in turn may be specified in the form of a Uniform Resource Identifier (URI). The cloud-based registration application 91 is preferably configured toIn step 6, the 30 connection data received by the cloud-based customer application 81 is transmitted via the communication link 30 to the IP-enabled device 111, and then the BE2024 / 5901 14 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 are deleted. The cloud-based customer application 81 is preferably trained to terminate the communication link 20 to the cloud-based registration application 91 after successful transmission of the unique identifiers of the IP-enabled device 111 and 5 of the second connection data. 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 link 30 to the cloud-based registration application 91. 10 The IP-enabled device 111 is further trained toto establish a communication connection 60 to the cloud-based customer application 81 using the second connection data obtained 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 can, for example, be implemented in the first IP-enabled device 111. The cloud-based customer application 81, which implements, for example, a switch, now ensures that the communication connection 60 is connected to the port selected by the customer.25 The cloud-based customer application81 can be trained toto inform the customer via PC70 or a mobile phone that the IP device 111 and thus the local network 110 has been properly connected. The address of the PC70 or the mobile phone required for this is known to the cloud-based customer application 81. Advantageously, in 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. According to an alternative implementation, in step 3 the cloud-based customer application 81 can not only use the individual identifiers 5 of the IP device 111 received from computer 70,but also immediately transmit 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. 10 The connection of the IP-enabled device 101 or the local network 100 to the cloud-based customer application 81 preferably takes place analogously to the connection of the IP-enabled device 111. It is further assumed that the IP-enabled device 101 has already been unpacked 15 and set up by an operator in the factory hall at the Berlin location and connected to a public IP-based data network, for example, the Internet. It is further assumed, for example, that the connection of the IP-enabled device 101 takes place first,After the IP-enabled device 111 has been connected to the cloud-based customer application 81, 20 a temporary communication connection 40 (dashed line in Figure 1) is now established over the Internet from the first IP-enabled device 101 to the cloud-based registration application 91 using the initial connection data. For this purpose, the customer can, for example, press a special 25 key or perform another active action on the IP-enabled device 101 to initiate the connection setup. In other words, the IP-enabled device 101 is preferably configured to establish a communication connection to the cloud-based registration application 81 in response to a manual key press. Alternatively, the IP-enabled device 101 could also be configured 30 to automatically establish a communication connection 40 to the registration application 91 as soon as it has been connected to the Internet. BE2024 / 5901 16 It should also be noted thatthat 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 915 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. 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, and selects the customer application 81 if there are several different customer applications, for example by selecting a pre-defined,The cloud-based customer application 81 specifies the identifier via the computer 70. 15 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. Within the cloud-based customer application 81, which, for example, implements a switch 20, the customer can no longer select a specific port of the switch to which the IP-enabled device 101 is to be connected. The customer then enters the known unique identifiers of the IP-enabled device 101 into their computer 70.the individual identifiers are transmitted via the communication connection 10 to the customer application 81. In this way, for example, the two individual identifiers of the IP-enabled device 101 are transmitted to the cloud-based customer application 81. According to an exemplary implementation, the cloud-based customer application 30 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 the computer 70. Subsequently, the cloud-based customer application 81 transmits the individual identifiers of the IP-enabled device 101, entered by the customer via their computer 70, to the registration application 91. According to a preferred implementation, the cloud-based registration application91 now checks whether the transmitted unique identifiers match the two unique identifiers previously transmitted to it by the IP-based device101 and stored, for example, in the data storage92. If a match is found,The cloud-based registration application 91 generates a confirmation message and transmits this message via the communication link 20 to the cloud-based customer application 81. 10 Under Responding to the Confirmation Message, the cloud-based customer application 81 transmits the second connection data via the communication link 20 to the cloud-based registration application 91. The connection data includes, as already mentioned, the address of the cloud-based customer application 81, which in turn can be specified in the form of a Uniform Resource Identifier (URI) 15. The cloud-based registration application 91 is preferably designed to transmit the connection data received by the cloud-based customer application 81 via the communication connection 30 to the IP-enabled device 101 20 and then 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 designed toto dismantle the communication connection20to the cloud-based registration application91after successful transmission of the individual25 identifiers of the IP-enabled device101and the second connection data. After the IP-enabled device 101 has received the second connection data from the cloud-based registration application 91, the IP-enabled device 101 establishes the communication connection 40 to the cloud-based registration application 91. 30 BE2024 / 5901 18 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 5 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 establish. To enable secure communication transmission over the communication link 60, 10 the Internet Protocol Security (IPsec) can be used for secure communication. The cloud-based customer application 81, which, for example, implements a switch, now ensures that the communication link 50 is connected to the port selected by the customer. 15 The cloud-based customer application 81 can be configured to inform the customer via the PC 70 or a mobile phone,that the IP device 101 and thus the local network 100 has been properly connected. The address of the PC 70 or the mobile phone required for this is known to the cloud-based customer application 81. Advantageously, in a configuration phase 20 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. According to an alternative implementation, the cloud-based customer application 25 81 can transmit not only the individual identifiers of the IP device 111 received from the computer 70, but also the second connection data, to the cloud-based registration application 91 simultaneously. In this case, no confirmation message is generated by the registration application 91 and transmitted to the customer application 81. 30 BE2024 / 5901 19 It should be noted that several IP-enabled devices, which are to be connected to the cloud-based customer application 81, can also be connected to the cloud-based registration application 91 simultaneously.can be logged in. For example, the two IP-enabled devices 101 and 111 can each be activated simultaneously by an operator to establish a communication connection 40 or 30 and 5 to transmit the 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 the PC 70 to the cloud-based customer application 81 and from there forwarded via an established connection 20 to the cloud-based registration application 9110. 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 those of the two IP-enabled devices 101 and 111. The received individual identifiers must match. If this is the case,For example, a confirmation message is transmitted from the cloud-based registration application 91 to the cloud-based customer application 81. Upon responding to the confirmation message, the cloud-based customer application transmits the second connection data to the cloud-based registration application 91, which transmits this connection data to the two IP-enabled devices 101 and 111. As previously explained by way of example, the communication connections 30 and 40 are then closed, and the individual identifiers of the IP-enabled devices 101 and 111, as well as the second connection data, which have preferably been cached in the data store 92, are deleted by the cloud-based registration application 91. Using the second connection data 25, the IP-enabled devices 101 and 111 then each establish a communication connection 50 and 60, respectively, to the cloud-based customer application.