Patent Publication Number: US-11641391-B2

Title: Integrated cloud system with lightweight gateway for premises automation

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of United States (U.S.) patent application Ser. No. 15/198,855, filed on Jun. 30, 2016, now U.S. Pat. No. 10,530,839. 
     This application claims the benefit of U.S. Patent Application No. 62/186,925, filed Jun. 30, 2015. 
     This application claims the benefit of U.S. Patent Application No. 62/186,974, filed Jun. 30, 2015. 
     This application claims the benefit of U.S. Patent Application No. 62/186,696, filed Jun. 30, 2015. 
     This application claims the benefit of U.S. Patent Application No. 62/186,825, filed Jun. 30, 2015. 
     This application claims the benefit of U.S. Patent Application No. 62/186,857, filed Jun. 30, 2015. 
     This application is a divisional application of U.S. patent application Ser. No. 15/198,531, filed Jun. 30, 2016, now U.S. Pat. No. 11,190,578. 
     This application is a continuation in part application of U.S. patent application Ser. No. 15/196,646, filed Jun. 29, 2016, now abandoned. 
     This application is a continuation in part application of U.S. patent application Ser. No. 12/189,780, filed Aug. 11, 2008, now abandoned. 
     This application is a continuation in part application of U.S. patent application Ser. No. 13/531,757, filed Jun. 25, 2012, now abandoned. 
     This application is a continuation in part application of U.S. patent application Ser. No. 12/197,958, filed Aug. 25, 2008, now U.S. Pat. No. 10,721,087. 
     This application is a continuation in part application of U.S. patent application Ser. No. 13/334,998, filed Dec. 22, 2011, now U.S. Pat. No. 9,531,593. 
     This application is a continuation in part application of U.S. patent application Ser. No. 12/539,537, filed Aug. 11, 2009, now U.S. Pat. No. 10,156,959. 
     This application is a continuation in part application of U.S. patent application Ser. No. 14/645,808, filed Mar. 12, 2015, now U.S. Pat. No. 10,127,801. 
     This application is a continuation in part application of U.S. patent application Ser. No. 13/104,932, filed May 10, 2011, now abandoned. 
     This application is a continuation in part application of U.S. patent application Ser. No. 13/929,568, filed Jun. 27, 2013, now U.S. Pat. No. 10,444,964. 
     This application is a continuation in part application of U.S. patent application Ser. No. 14/628,651, filed Feb. 23, 2015, now U.S. Pat. No. 10,091,014. 
     This application is a continuation in part application of U.S. patent application Ser. No. 13/718,851, filed Dec. 18, 2012, now U.S. Pat. No. 10,156,831. 
     This application is a continuation in part application of U.S. patent application Ser. No. 12/972,740, filed Dec. 20, 2010, now U.S. Pat. No. 9,729,342. 
     This application is a continuation in part application of U.S. patent application Ser. No. 13/954,553, filed Jul. 30, 2013, now U.S. Pat. No. 11,582,065. 
     This application is a continuation in part application of U.S. patent application Ser. No. 14/943,162, filed Nov. 17, 2015, now U.S. Pat. No. 10,062,245. 
     This application is a continuation in part application of U.S. patent application Ser. No. 15/177,915, filed Jun. 9, 2016, now U.S. Pat. No. 11,316,958. 
    
    
     TECHNICAL FIELD 
     The embodiments described herein relate generally to networking and, more particularly, to premises automation systems and methods. 
     BACKGROUND 
     There is a need for systems and methods that integrate cloud services and internet-connected devices with a user interface and other components and functions of a service provider system. This integration would enable third party and/or other connected devices (e.g., smart door bells, door locks, garage door operators, cameras, thermostats, lighting systems, lighting devices, etc.), and third party services to control or trigger automations in the service provider system using components and functions of the service provider system. This would enable end-users to integrate and use their previously-standalone internet-connected devices with each other as well as with their service provider-based service. 
     INCORPORATION BY REFERENCE 
     Each patent, patent application, and/or publication mentioned in this specification is herein incorporated by reference in its entirety to the same extent as if each individual patent, patent application, and/or publication was specifically and individually indicated to be incorporated by reference. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG.  1    is a block diagram of a system including a Cloud Hub (FlexCore) and 
       Virtual Gateway, also referred to herein as the Lightweight Gateway (LWG), under an embodiment. 
         FIG.  2    is a block diagram of a system including a Cloud Hub and Virtual Gateway showing the premises, service provider, and mobile environments, under an embodiment. 
         FIG.  3    is a flow diagram for Cloud Hub device installation, under an embodiment. 
         FIG.  4    is a block diagram showing communications of the LGW, under an embodiment. 
         FIG.  5    is a block diagram showing an object model of the LGW, under an embodiment. 
         FIG.  6    is a block diagram of the application architecture, under an embodiment. 
         FIG.  7    is a flow diagram for device state change, under an embodiment. 
         FIG.  8    is a flow diagram for media upload, under an embodiment. 
         FIG.  9    is a flow diagram for live video, under an embodiment. 
         FIG.  10    is a flow diagram for event trigger notification, under an embodiment. 
         FIG.  11    is a flow diagram for activation iHub, under an embodiment. 
         FIG.  12    is a flow diagram for activation LWG, under an embodiment. 
         FIG.  13    is a flow diagram for app sign-in (Web/Android app) iHub, under an embodiment. 
         FIG.  14    is a flow diagram for app sign-in (Web/Android app) LWG, under an embodiment. 
         FIG.  15    is a flow diagram for app session, device event (Web/Android app), under an embodiment. 
         FIG.  16    is a flow diagram for app sign-in (iOS) iHub, under an embodiment. 
         FIG.  17    is a flow diagram for app sign-in (iOS) LWG, under an embodiment. 
         FIG.  18    is a flow diagram for app session, device event (iOS app), under an embodiment. 
         FIG.  19    is a flow diagram for LWG remote arm, under an embodiment. 
         FIG.  20    is a flow diagram for iHub reboot, under an embodiment. 
         FIG.  21    is a flow diagram for iHub disconnect, under an embodiment. 
         FIG.  22    is a block diagram of the integrated security system, under an embodiment. 
         FIG.  23    is a block diagram of components of the integrated security system, under an embodiment. 
         FIG.  24    is a block diagram of the gateway including gateway software or applications, under an embodiment. 
         FIG.  25    is a block diagram of components of the gateway, under an embodiment. 
         FIG.  26    is a block diagram of IP device integration with a premise network, under an embodiment. 
         FIG.  27    is a block diagram of IP device integration with a premise network, under an alternative embodiment. 
         FIG.  28    is a block diagram of a touchscreen, under an embodiment. 
         FIG.  29    is an example screenshot of a networked security touchscreen, under an embodiment. 
         FIG.  30    is a block diagram of network or premise device integration with a premise network, under an embodiment. 
         FIG.  31    is a block diagram of network or premise device integration with a premise network, under an alternative embodiment. 
         FIG.  32    is a block diagram of the Integrated Cloud System (ICS) or platform, under an embodiment. 
         FIG.  33    is a flow diagram for Service Association, under an embodiment. 
         FIG.  34    is a flow diagram for Service Disassociation, under an embodiment. 
         FIG.  35    is a flow diagram for Card UI Interactions, under an embodiment. 
         FIG.  36    is an example rules interface for controlling triggers and actions involving third party devices integrated in the ICS, under an embodiment. 
         FIG.  37    is an example of a triggers portion of a rules interface for third party services integrated with the ICS, under an embodiment. 
         FIG.  38    is another example of an actions portion of a rules interface for integrated third party devices, under an embodiment. 
     
    
    
     DETAILED DESCRIPTION 
     Embodiments include a cloud hub located in a premises, and the cloud hub comprises adapters configured for coupling to premises devices. The cloud hub is configured as a gateway for the premises devices. The system includes a virtual gateway located in a cloud server environment and coupled to the cloud hub. The virtual gateway is configured as a server-side abstraction of the cloud hub. The cloud hub and the virtual gateway are configured as an automation platform that maintains state data of the premises devices, controls interaction among the premises devices, and monitors and manages the premises devices. 
     Embodiments include a system comprising a cloud hub located in a premises. The cloud hub comprises adapters coupled to premises devices, and the cloud hub is configured as a gateway for the premises devices. A virtual gateway is located in a cloud server environment and coupled to the cloud hub. The virtual gateway is configured as a server-side abstraction of the cloud hub. The cloud hub and the virtual gateway are configured as an automation platform that maintains state data of the premises devices, controls interaction among the premises devices, and monitors and manages the premises devices. A security system coupled to the virtual gateway. The security system includes security system components. 
       FIG.  1    is a block diagram of a system including a Cloud Hub and Virtual Gateway, also referred to herein as the Lightweight Gateway (LWG) or FlexCore, under an embodiment. The “Cloud Hub” is a dual purpose Z-Wave and Wi-Fi Access Point configured to enable full premises automation (e.g., Tier-1 sites). The Cloud Hub device couples or connects to the premises broadband connection and operates as a gateway for Z-Wave and camera traffic. Cloud Hub enables Z-Wave for premises and customer premises equipment (CPE) that do not currently support it, and provides a Wi-Fi sandbox for Direct Cameras. An example of a hardware platform configured as a Cloud Hub is the Sercomm NA301v2 device, but the embodiment is not so limited as numerous other devices can serve as the Cloud Hub. The detailed description herein includes aspects of the software and firmware of the Cloud Hub along with server and client application software. 
       FIG.  2    is a block diagram of a system including a Cloud Hub and Virtual Gateway showing the premises, service provider, and mobile environments, under an embodiment. The system of an embodiment includes the gateway (FlexCore) in the premises (e.g., home, office, etc.), and the gateway is coupled to a LWG in the operator (server/cloud) domain. The gateway includes one or more of a camera adapter to integrate premises cameras, an IP adapter to integrate premises IP devices, and a ZigBee protocol and hardware driver to integrate premises ZigBee devices. Components of the gateway of an embodiment are coupled to a radio frequency (RF) bridge as appropriate to a configuration of devices in the premises, and the RF bridge integrates additional premises devices (e.g., Z-Wave devices, proprietary devices, etc.) into the system. 
     The LWG and cloud-based infrastructure of an embodiment uses an existing service provider infrastructure, security, performance, and APIs, along with system components that are separated into modules executed on distributed in-premises systems. The LWG and cloud-based infrastructure includes a pluggable architecture that enables new device protocols and RF technologies to be added without the need to overhaul the core infrastructure. Use of a relatively small memory footprint on the CPE enables the infrastructure to execute on many devices, and this refactoring of local versus cloud services provides a virtual device (e.g., Internet of Things (IOT), etc.) gateway service that pushes as much as possible to the cloud while maintaining local performance and offline capabilities. 
     An embodiment includes a Lightweight Gateway (LWG) that is configured as the server-side abstraction for the Cloud Hub. The LWG is subordinate to the gateway object, and interacts with the server and the Cloud Hub device in much the same way that a RISSecurityPanel class does. As such, an embodiment re-factors the common code out of RISSecurityPanel into a class that both RISSecurityPanel and the Cloud Hub device can use. A new device definition is created for this type of device, and various changes to the StandardGateway class to control and manage the additional communication channel with the new device. 
     The Session Server configuration uses a gateway registry service to route incoming UDP packets from the CPE to the proper lightweight gateway instance via a one-to-one mapping of CPE-unique IDs to site IDs. With the addition of the Cloud Hub, a second CPE-unique ID is mapped to the same LWG instance as the primary security, monitoring and automation (SMA) client&#39;s CPE-unique ID. This is accomplished by leveraging the Device Registry, which maintains a mapping of CPE ID and device type to site ID. Further, the session server is modified to use this Device Registry to properly route income packets. 
     Regarding client application software or applications, the clients include UX additions to present the new Cloud Hub device. When the Cloud Hub is present, UX flow will potentially be different. For example, on a Cloud Hub system, Z-Wave devices are not added until the Cloud Hub is added. Also, deleting the Cloud Hub includes deleting the associated Z-Wave devices, and this uses special UX messaging. The activation app and the installer app will also need new flows for installing and managing these devices. 
     The Cloud Hub firmware of an example embodiment includes but is not limited to the following components: SMA Client: an always-on (i.e., always-TCP-connected) SMA client, supporting AES-256 encryption; ezwLib: port of the Icontrol embedded Z-Wave stack; Bootstrap Client for secure bootstrap of the master key, and then secure provisioning of the SMA Server connection information and initialization information; LED Driver to drive CPE LED that displays Server connectivity and Z-Wave status (CPE-dependent); Firmware Update Logic for fault-tolerant updates of the full CPE image (CPE-dependent); detailed/tunable error logging; Reset To Factory Default Logic for factory-default Z-Wave (erase node cache and security keys), WiFi (disable sandbox, reset SSID/PSK; CPE-dependent), and de-provision (erase SMA Server info). 
     In an example configuration, server-CPE communication is over SMAv1 protocol, except for bootstrapping and provisioning which uses the OpenHome “Off-Premise Bootstrap Procedure.” On the CPE, the OS and network layer (Wi-Fi sandbox, WPS, routing, etc.) are provided and managed by the CPE OEM (e.g., Sercomm). Wi-Fi provisioning and traffic is handled by the CPE OEM (e.g., Sercomm) without Cloud Hub intervention/signaling, except with respect to enabling/disabling and resetting to defaults. 
     The Cloud Hub device installation and bootstrap mechanism performs one or more of the following: associate the device with an existing site; securely deliver the SMA communication configuration, including master key, SMA server address, and network ports. An embodiment includes an off-premise bootstrapping procedure, also used for bootstrapping tunneling cameras, that includes a three-step process. 
       FIG.  3    is a flow diagram for Cloud Hub device installation, under an embodiment. During a first step, the Cloud Hub couples or connects to the Registry Gateway (e.g., via the pre-configured Registry Gateway URL) and retrieves its assigned siteID and the Credential Gateway URL. A second step includes the Cloud Hub retrieving its master key from the Credential Gateway using its siteID and Activation Key. A third step includes the Cloud Hub retrieving Session Gateway Information from the Credential Gateway. At the end of the Bootstrap phase, the Cloud Hub of an embodiment has obtained its master key and its Session Gateway address from the iControl Gateway. Each of these steps is described in detail below. 
     During normal operation, the CPE performs the first and third processes on every start-up/restart. The second process is followed only if there is no previously stored master key. Hence, security credentials can be re-bootstrapped by invalidating the existing master key. 
     The Cloud Hub uses the first step process or procedure at least to retrieve its SiteID and Credential Gateway URL. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                 Purpose 
                 Retrieve Credential Gateway URL and siteID using Cloud Hub  
               
               
                   
                 Serial Number as input 
               
               
                 Message Format 
                 HTTPS GET /&lt;Registry Gateway URL&gt;/&lt;Serial Number&gt; 
               
               
                   
                 HTTP/1.1 
               
               
                 Authentication  
                 None 
               
               
                 Mandatory Request 
                 Host 
               
               
                 Headers 
                 &lt;registryEntry serial=“&lt;Serial Number&gt;” href=“/&lt;Registry 
               
               
                   
                 Gateway URL&gt;/&lt;Serial Number&gt;”&gt; 
               
               
                   
                 &lt;functions&gt;...&lt;/functions &gt; 
               
               
                 200 OK response 
                 &lt;siteId&gt;&lt;siteID&gt;&lt;/siteId&gt; 
               
               
                   
                 &lt;gatewayUrl&gt;&lt;Credential Gateway URL&gt;&lt;/gatewayUrl&gt; 
               
               
                   
                 &lt;/registryEntry&gt; 
               
               
                 Error responses  
                 Standard HTTP response codes (e.g., 404) 
               
               
                 Example Request 
                 https://adminsirius3.icontrol.com/rest/icontrol/registry/serial/00603 
               
               
                   
                 504026c 
               
               
                   
                 &lt;registryEntry serial=“00:60:35:04:02:6c” 
               
               
                   
                 href=“/rest/icontrol/registry/serial/00603504026c”&gt; 
               
               
                   
                 &lt;functions count=“1”&gt; 
               
               
                   
                 &lt;function name=“delete” 
               
               
                   
                 action=“/rest/icontrol/registry/serial/00603504026c” 
               
               
                 Example 200 OK  
                 method=“DELETE”&gt; 
               
               
                 Response 
                 &lt;/functions&gt; 
               
               
                   
                 &lt;siteId&gt;00603504026c&lt;/siteId&gt; 
               
               
                   
                 &lt;gatewayUrl&gt;http://gsess-sirius3.icontrol.com/gw&lt;/gatewayUrl&gt; 
               
               
                   
                 &lt;/registryEntry&gt; 
               
               
                   
               
            
           
           
               
               
               
            
               
                 Variable Name  
                 Format  
                 Description/Notes 
               
               
                   
               
               
                 Registry Gateway 
                 URL  
                 Pre-configured in Cloud Hub firmware 
               
               
                 URL 
                   
                   
               
               
                 Serial Number  
                 12 byte hex string  
                 Pre-configured in Cloud Hub firmware 
               
               
                 siteID 
                 12-20 digit alpha 
                   
               
               
                   
                 numeric string 
                   
               
               
                 gatewayUrl  
                 URL prefix 
                 Prefix to use for Pending Master Key and 
               
               
                 otherwise known as 
                 protocol:host[:port]/p 
                 Connect Info requests. 
               
               
                 CredentialGatewayU  
                 ath 
                   
               
               
                 RL 
               
               
                   
               
            
           
         
       
     
     The Cloud Hub uses the second step process or procedure at least to retrieve its Pending Master Key. If the Master Key is already established from a previous successful Retreieve Credital procedure, this step is optional. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                 Purpose 
                 Retrieve device-specific Master Key using its siteID, serial 
               
               
                   
                 number and Activation Key as inputs 
               
               
                 Message Format 
                 HTTPS POST/&lt; 
               
               
                   
                 CredentialGatewayURL&gt;/GatewayService/&lt;siteID&gt;/PendingDevi 
               
               
                   
                 ceKey HTTP/1.1 
               
               
                 Authentication 
                 None 
               
               
                 Mandatory Request 
                 Host, Content-Length, Content-Type (application/x-www-form- 
               
               
                 Headers 
                 urlencoded ) 
               
               
                 POST body 
                 serial=&lt;Serial Number&gt;&amp;activationkey=&lt;ActivationKey&gt; 
               
               
                 200 OK response 
                 &lt;pendingPaidKey method=“server” expires=“&lt;pending master key 
               
               
                 with pending master 
                 expiration epoch millisecs&gt;” ts=“&lt;current epoch millisecs&gt;” 
               
               
                 key 
                 key=“&lt;master key&gt;” partner=“icontrol”/&gt; 
               
               
                 200 OK response 
                 Gateway responds with a method=“retry” if the Cloud Hub is not 
               
               
                 with retry 
                 yet activated within the system. Response includes timeout for 
               
               
                   
                 retry. 
               
               
                   
                 &lt;PendingPaidKey method=“retry” expires=“&lt;retry epoch 
               
               
                   
                 millisecs&gt;” ts=“&lt;current epoch millisecs&gt;” partner=“icontrol”/&gt; 
               
               
                 Other HTTP 
                 Standard HTTP error response codes for example 5xx indicate a 
               
               
                 responses 
                 temporary server issue and Cloud Hub devices should perform an 
               
               
                   
                 automatic retry in randomized 10 minute backoff 
               
               
                 Example POST body 
                 serial=555500000010&amp;activationkey=AABB12345678 
               
               
                 Example 200 OK 
                 &lt;pendingPaidKey method=“server” expires=“1308892493528” 
               
               
                 with pending key 
                 ts=“1308849293540” key=“398341159498190458” 
               
               
                 Response 
                 partner=“icontrol”/&gt; 
               
               
                 Example 200 OK 
                 &lt;pendingPaidKey method=“retry” expires=“1308849242148” 
               
               
                 response with retry 
                 ts=“1308849122148” partner=“icontrol”/&gt; 
               
               
                   
               
            
           
           
               
               
               
            
               
                 Variable Name 
                 Format 
                 Description/Notes 
               
               
                   
               
               
                 CredentialGatewayU 
                 Hostname[port] 
                 Retrieved via Step 1 - Retrieve 
               
               
                 RL 
                   
                 Gateway URL and SiteID 
               
               
                 siteID 
                 12 byte hexadecimal string 
                 Retrieved via Step 1 - Retrieve 
               
               
                   
                   
                 Gateway URL and SiteID 
               
               
                 ActivationKey 
                 10+ digit alpha numeric 
                 Pre-configured in Cloud Hub, 
               
               
                   
                 string 
                 generated by manufacturer and 
               
               
                   
                   
                 printed on device 
               
               
                 ‘method’ (in 200 OK 
                 String 
                 “server” or “retry” 
               
               
                 body) 
                   
                   
               
               
                 ‘key’ (in 200 OK 
                 Alphanumeric string 
                 Pending key returned by Gateway in 
               
               
                 body) 
                   
                 200 OK body 
               
               
                 ‘ts’ (in 200 OK body)  
                 Numeric string 
                 Gateway&#39;s timestamp in UTC time 
               
               
                 ‘expires’ (in 200 OK 
                 Numeric string 
                 UTC time when the current pending 
               
               
                 body) 
                   
                 key expires 
               
               
                 Pending Key 
                 Alphanumeric string 
                 Initial key retrieved from Gateway 
               
               
                   
                   
                 that is not yet confirmed with the 
               
               
                   
                   
                 Gateway. 
               
               
                 SharedSecret or 
                 Alphanumeric string 
                 Pending key becomes 
               
               
                 master key 
                   
                 &lt;SharedSecret&gt; after successful 
               
               
                   
                   
                 connection to Gateway (see below) 
               
               
                   
               
            
           
         
       
     
     During Cloud Hub activation, the Gateway responds to a Cloud Hub&#39;s request for Credential with 200 OK containing the PendingPaidKey XML body (with method=“server”) with a pending key field. The pending key field becomes active once the Cloud Hub connects to the Gateway over the SMA channel and is authenticated by using the pending key to encrypt the initial SMA exchange. Once authenticated (via a successful SMA session with the Gateway), the key is no longer pending and instead becomes active, or otherwise known as the Cloud Hub&#39;s&lt;SharedSecret&gt; or master key. The active master key (“&lt;SharedSecret&gt;”) will not automatically expire; however, the Gateway may update a Cloud Hub&#39;s&lt;SharedSecret&gt;. Once a pending key becomes active, subsequent requests for the PendingDeviceKey will receive method=“retry” responses unless a new activation process is initiated (this can be done by administrators and installers via the iControl admin and portal applications). 
     If the Cloud Hub does not connect to the server over the SMA channel and get authenticated using the key by the “expires” time specified in the PendingPaidKey XML body, then the pending key will expire and no longer be valid. 
     While Cloud Hub activation is underway, each request for the PendingPaidKey will receive a different key in the response, causing the previous pending key to be replaced with the new one. Upon a factory reset, the device will forget its key and return to the bootstrap process of polling for a PendingDeviceKey. 
     The Cloud Hub uses the third step process or procedure at least to retrieve Session Gateway Info, which includes SMA Gateway address. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                 Purpose 
                 Retrieve SMA Gateway hostname and port from Credential Gateway 
               
               
                 Message Format 
                 HTTPS GET /&lt;gatewayUrl&gt;/GatewayService/&lt;siteID&gt;/connectInfo 
               
               
                   
                 HTTP/1.1 
               
               
                 Authentication 
                 None 
               
               
                 Mandatory 
                 Host 
               
               
                 Request Headers 
                   
               
               
                   
                 &lt;connectInfo&gt; 
               
               
                   
                     &lt;session host=&lt;Session Gateway host&gt; port=[port] /&gt;&lt;ris 
               
               
                   
                 eventPort1=‘[port]’ eventPort2=‘[port]’ controlPort1=‘[port]’ 
               
               
                   
                 controlPort2=‘[port]”/&gt; 
               
               
                 200 OK response 
                     &lt;xmpp host=&lt;XMPP Gateway host&gt; port [port] /&gt; 
               
               
                   
                 (ignored) 
               
               
                   
                 &lt;/connectInfo&gt; 
               
               
                 Error responses 
                 Standard HTTP response codes (e.g., 404) 
               
               
                   
                 &lt;connectInfo&gt; 
               
               
                   
                 &lt;session host=‘gsess-aristotleqapicontrol.com’ port=‘443’/&gt;&lt;ris 
               
               
                   
                 eventPort1=‘11083’ eventPort2=‘11083’ controlPort1=‘11084’ 
               
               
                   
                 controlPort2=‘11084’/&gt; 
               
               
                 Example 200 OK 
                 &lt;xmpp host=‘gsess-aristotleqapicontrol.com’ port=‘5222’/&gt;&lt;media 
               
               
                 Response 
                 url=‘https://media- 
               
               
                   
                 aristotleqap.icontrol.com/gw/GatewayService’/&gt;&lt;/connectInfo&gt; 
               
               
                   
               
            
           
           
               
               
               
            
               
                 Variable Name 
                 Format 
                 Description/Notes 
               
               
                   
               
               
                 gatewayUrl 
                 https://hostname[:port]/path 
                 Retrieved Via Step 1 - Retrieve 
               
               
                   
                   
                 Gateway URL and SiteID 
               
               
                 siteID 
                 12-20 char alpha numeric string 
                 Retrieved Via Step 1 - Retrieve 
               
               
                   
                   
                 Gateway URL and SiteID 
               
               
                 XMPP Gateway 
                 Hostname and port 
                 These variables should be 
               
               
                 host:port 
                 IPAddress and port 
                 ignored by the Cloud Hub. 
               
               
                 Session Gateway 
                 Hostname 
                 Host and command port to use 
               
               
                 host 
                   
                 for SMA communication with 
               
               
                   
                   
                 the Gateway. 
               
               
                 session:port 
                 port 
                 This port variable should be 
               
               
                   
                   
                 ignored by the Cloud Hub. 
               
               
                   
                   
                 ports on Session Gateway host 
               
               
                   
                   
                 to which SMA async events 
               
               
                 ris:eventPort1/2 port 
                   
                 should be sent 
               
               
                 ris:controlPort1/2 port 
                   
                 ports on Session Gateway host 
               
               
                   
                   
                 for establishing the SMA control 
               
               
                   
                   
                 channel 
               
               
                   
               
            
           
         
       
     
     The Cloud Hub of an embodiment is a broadband-connected device, and it attempts to maintain an always-on TCP/IP connection with the server. Therefore, there is no need for a shoulder-tap mechanism, as is provided via SMS on typical tier-1 systems. No “wake-up” message is used as the Cloud Hub is effectively always awake. With conventional Tier-1 systems, the server tears down the TCP connection after several minutes of inactivity; for Cloud Hub, the TCP connection should stay up for as long as possible, with periodic server-originated SMA heartbeat messages (SMA Request Type 0), so that the CPE can supervise the connection as being truly active. 
     Incoming messages (e.g., UDP) to the session server and the Device Registry from the CPE are routed to the LWG instance associated with a given site ID. In a conventional current pre-CloudHub configuration, the session server uses the Gateway Registry, which is a one to one mapping of CPE-unique IDs to site IDs for this purpose. With the addition of the Cloud Hub, a second CPE-unique ID is introduced that is mapped to the same site ID (LWG instance) as the primary SMA client&#39;s CPE-unique ID. This is accomplished by leveraging the Device Registry service, which maintains a mapping of CPE ID and device type to site ID. The session server of an embodiment, upon receipt of a UDP packet, looks up or identifies the received packet&#39;s CPE-unique ID in the Gateway Registry and, if a corresponding site ID is found, routes the packet to the associated LWG instance. If a corresponding site ID is not found, the session server looks up the received CPE-unique ID with a general Cloud Hub device type ID and, if a corresponding site ID is found, routes the packet to the associated LWG instance. 
     The LGW includes use of message tunneling over REST. The Cloud Hub, UDP and TCP messages coming from the CPE and received by the session server are sent to the correct LWG via two REST endpoints. This enables the receiving LWGW instance to run on a session server other than the one at which the message was received. 
     In an embodiment, when a UDP SMA message arrives at a session server, if the LWG corresponding to the CPE-unique ID message is not already running on the given session server, then the session server starts a new LWG instance there, and if the corresponding LWGW is currently running on another session server, it will be gracefully shut down. In this way, the LWG is configured to move from one session server to another. 
     In alternative embodiments, the security panel messages continue to use the mechanism described herein (LWG migration), however, the Cloud Hub network traffic employs a mechanism similar to that used by Tunneling Cameras. More specifically: 
     1) Incoming UDP message to session server #1: session server #1 checks if LWG is running on session server #1. 
     
         
         
           
             If so, using a LocalRestClient, pass UDP message through to the LWG via a rest endpoint that calls through to the handleAsyncMessage method of the RIS device. 
             If not, check an LWG routing cache to see which session server is hosting the LWG. 
             If a routing entry is found, use AMQPRestClient to pass the UDP message through to the specific session server hosting the LWG via the same rest endpoint that calls through to the handleAsyncMessage method of the RIS device. 
             If no routing entry is found, or the session server returns 404 (e.g., stale routing entry), then the session server sends out a broadcast request using the AMQPRestClient to ask all session servers “who has this LWG”. 
             If a session server responds to the broadcast request, send the async event to that session server as described herein. 
             If no session server responds to the broadcast request, start the LWG on this session server (session server #1).
 
2) Incoming TCP message to session server #1: session server #1 checks if LWG is running on session server #1.
 
             Use process described in 1 above to determine which session server is hosting the LWG and pass the TCP message through accordingly, but using a different rest endpoint than UDP message handling. In the rest endpoint call, the name of the session server with the TCP connection is sent along with the request. 
             When the LWG receives TCP messages through the rest endpoint, it keeps track of the name of the session server with the TCP connection. The tunnel camera does this using a variable on the camera device and the cloud hub device could do the same.
 
3) Sending a command from LWG over TCP connection.
 
             When the LWG sends a command over the TCP connection, it sends a command via the AMQPRestClient to the session server hosting the TCP connection. It has this name saved from when it received the first TCP message for the given connection. 
             If the TCP session server hostname is not known, or responds with a  404  (e.g., TCP connection no longer there), then the LWG sends out a broadcast request using the AMQPRestClient to ask all session servers “who has this TCP connection”. 
             If a session server responds to the broadcast request, send the command to that session server as described herein. 
             If no session server responds to the broadcast request, then the LWG queues the command for a short time period (e.g., existing RIS device functionality). 
           
         
       
    
     The CloudHub firmware update of an embodiment is accomplished over an HTTPS connection from the CloudHub to a secure server, to download an entire bundled CPE image. This single image includes the CloudHub updatable firmware, including: OS image and drivers; SMA Client, which includes code for bootstrapping, AES-256 encryption, LED driver, firmware update logic, etc.; ezwLib Z-Wave stack. 
     A firmware update is initiated on the server by sending SMAv1 System Command (command type 31) with Sub-Command “Upgrade Client Firmware” (system command type 3). This command simply provides a URL pointing to the new firmware image. This will be an HTTPS URL for secure transfer of the image. When the Cloud Hub receives this command, it downloads the image from a secure server via HTTPS, verifies a digest checksum, and flashes the new image. 
     Progress of the image download is communicated by the CloudHub by sending async event “Firmware upgrade % completed” (CPE Report Type 12); flashing progress is communicated by the CloudHub setting/clearing system status “Firmware Update Start” (Miscellaneous System Status 15). 
     Flashing a new firmware image does not factory-default the device, and existing configuration, provisioning information, and encryption keys are retained. CloudHub of an embodiment is configured to use either a dual-image scheme or re-flashing bootloader, so that a power-cycle during image flashing will not brick CloudHub. 
     The SMA Client is configured to flash the Z-Wave chip firmware, when directed to do so via SMAv1 System Command (command type 31) with Sub-Command “Upgrade Client Firmware” (system command type 3), specifying a Z-Wave-specific filename. 
     SMAv1 security for tier-1 panel communication is enhanced by the out-of-band SMS channel from the server to the CPE. The cellular network is a more restricted private network relative to a broadband network, and this is advantageous for re-keying the master key, when needed. Since CloudHub of an embodiment is configured as an always-on TCP/IP connected device, another process is used in which a REST endpoint is created that uses an SMA set config command to “clear” the current master key and restart. Upon restart, when the CPE discovers it has no master key, it performs the bootstrap as described herein to obtain a new master key. 
     The Lightweight Gateway (LWG) is a general term for the gateway state machine that runs on the server, as described herein. There is also a gateway state machine that runs in the home and this is commonly referred to as the iHub, although that code can run on other CPE hardware. The gateway state machine is configured to maintain track of the state of CPE devices such as security panels and cameras. The gateway monitors and manages these devices, and also runs the rules engine and exports the gateway core API which includes all endpoints that begin with the prefix “/rest/[partner]/nw/[siteId]”. 
     The Lightweight Gateway is used for example when there is no conventional gateway in the home. In this configuration, devices like the security panel and cameras talk directly to the server either using the cellular network or using the premises broadband network. 
     The Lightweight Gateway of an embodiment communicates with a variety of security panels and protocols. The security panels include the Honeywell QC3/Lynx and QC5/Touch, which use a proprietary RIS/ECP protocol (Honeywell). The security panels also include DSC SCW and PowerSeries, which use the iControl SMA V1 protocol. The LWG also communicates or integrates with the 2 Gig Telular panel, which uses the iControl SMA V1 protocol and supports ZWave devices like switches, dimmers, thermostats and locks. In this configuration, the 2 Gig panel performs the role of the zwave device manager. 
     The LWG also communicates or integrates with the Honeywell TSS panel, which uses the iControl SMA V2 protocol and allows for complete remote panel programming via SMA. The security panels to which the LWG communicates also include 3GUC panels, which use SMA V1 protocol and can connect to SimonXT and other panels. 
     The LGW of an embodiment supports an XMPP Tunnel Camera (e.g., OpenHome). This camera couples or connects to the server via broadband using the corresponding protocol tunneled over XMPP. 
       FIG.  4    is a block diagram showing communications of the LGW, under an embodiment.  FIG.  5    is a block diagram showing an object model of the LGW, under an embodiment. 
     Regarding the system architecture, the LWG runs on a Session Server, as described herein. The session server sits on the Web Tier, at the edge of the data center. Other servers on the web tier include Apache servers and the Video Relay server, but are not so limited. 
     The LGW objects are hosted on the Session Server. They receive inbound communications from their corresponding security panel via the Panel Service Provider (i.e. Honeywell). The inbound communication of an embodiment is UDP packets from a dedicated TCP/IP port. The outbound communications are packaged into binary SMS messages and delivered to the security panel through third-party communication services, but are not so limited. 
     The App Tier includes servers like the web portal and the gateway app server. App tier servers have access to the persistence tier where the Database and NFS filesystem can be found. 
     The Web Tier of an embodiment does not have direct access to the persistence tier, but is not so limited. As a result, for NFS and Database access, the LWG invokes APIs on the gateway app server. The LWG uses the REST API on the gateway app server as well as the legacy GwSessionService (gwsess.war). Most of these requests are made using http, however, REST API requests can also be invoked using the AMQP transport layer (AMQPRestClient) in which case these requests are routed through a work queue on the RabbitMQ Broker. 
     Regarding asynchronous architecture, a production session server of an embodiment includes 26 GB of memory, 2 CPUs, and is sized for 200K LWGs, but is not so limited. Each LWG uses approximately 100 KB of memory but is not so limited. 
     The LWGs running on a session server share the same virtual machine (e.g., Java), so the LWG code is configured to be high asynchronous so as to avoid blocking shared resources or using too many threads. An embodiment includes shared network thread pools. These thread pools dispatch tasks for handling incoming network activity (e.g., UDP and TCP message processing, API Requests, etc). 
     Embodiments include GlobalScheduler thread pools. In this configuration there is a thread pool for non-blocking activity (tick pool), for external blocking requests (sync pool), and for camera operations (camera pool). 
     Because a large number of LWGs share the same memory, use is made of the StringCache when an object has a String member variable and that String is not likely to be unique. The StringCache is a shared lookup table of commonly used strings. When a code uses the StringCache then it has an int memory variable rather than a String, and this saves the LWG large amounts of memory. 
     The Session server keeps track of all the LWGs it is running using the /data/ic/logs/session serialized files. Every time a new LWG is started or stopped on the Session Server, these serialized files are updated accordingly. When the Session Server starts up after stopping (both gracefully and ungracefully), these serialized files tell it which LWGs to start. 
     An LWG can move from one Session Server to another. The LWG of an embodiment is assigned to primary/secondary Session Server combination, but is not so limited. This is determined by the LWG group in which the site resides. Each LWG group corresponds to a single primary Session Server and a single secondary Session Server. The LWG group also corresponds to a dedicated port on the load balancer. This dedicated port is configured to send all traffic to the primary Session Server when it is up, and to the secondary Session Server if it is down (active/standby configuration). If traffic destined for a given LWG comes in to a Session Server (either primary or secondary), the Session Server will check if the LWG is already running on that server. If it is not, then the Session Server will start the LWG and then pass to it the traffic. 
     When a LWG starts up on a Session Server, it first sends a GatewayConnect request for the given LWG site to the Gateway App server. The same GatewayConnect request is also used when an iHub connects to a Session Server. The GatewayConnect request includes the hostname of the Session Server. The Gateway App server writes the Session Server hostname to the database so that it knows to which Session Server a given Gateway is connected. This is used for routing REST API passthrough requests, for example. When the Gateway app processes the GatewayConnect request, it checks which Session Server the given site was last connected to and, if its different from the new session server, then the Gateway App server sends a disconnect request to the last session server. 
     When a Session server receives a disconnect request for a given site, if the site is an iHub then the Session server will disconnect that iHub if its still connected (it should not be). If the site is a LWG then the session server will shut down that LWG gracefully, allowing the LWG to perform a final sync (sending any recent events to the database for persistence) before removing the LWG from memory. 
     So, when a LWG starts up on a Session Server, the GatewayConnect request ensures that the LWG is no longer running on another Session Server. If the load balancer decides that the primary Session Server for a given port is down, it sends requests to the secondary Session Server. If the LWG is not already running on the secondary Session Server, the secondary Session Server starts the LWG, ensuring that it is not running anywhere else. 
     After the GatewayConnect request is completed, the LWG state machine is started up and it performs a “boot” Gateway sync. The “boot” Gateway Sync is a request made to the Gateway app server for a complete configuration and state snapshot of the given site. The Gateway app server reads the configuration and state from the DB and returns it to the LWG. The LWG is then able to start up and resume the state and configuration that it had when last run. 
     Alternatively to the “boot” Gateway Sync, there is a startup optimization that the LWG supports in which the contents of the “boot” Gateway Sync are written by the LWG to the NFS file system (using the Gateway app server&#39;s GetResourceFile, PutResourceFile, DeleteResourceFile apis) when the LWG is shut down gracefully. When the LWG starts up, it will first check for this file before performing the “boot” Gateway Sync. If the file is found then the “boot” Gateway Sync is skipped. 
     An embodiment performs traffic routing via broker. The Session Server includes an instance of the REST Server Framework, which includes the AMQP work and broadcast queue support. The tunnel camera feature makes extensive use of AMQP Rest Client and Rest Server messaging for announcing incoming camera connections, finding the Session Server with a given camera connected to it, sending camera requests and responses across different session servers (for example, when the Camera is connected to a different session server from its LWG). The Rest API endpoints are able to route requests to the LWG. 
       FIG.  6    is a block diagram of the application architecture, under an embodiment. Following are detailed descriptions of use case flows teaching the interaction of elements of the application architecture. 
       FIG.  7    is a flow diagram for device state change, under an embodiment. This flow shows the signal and data flow that results when a device state changes.
         1. iHub→Session Server   2. Session Server→Gateway Device State/Config   3. Gateway Device State/Config→DB   4. Gateway Device State/Config→Event Logging   5. Event Logging→DB   6. Event Logging→Broker (if user app is logged in to this site)       

       FIG.  8    is a flow diagram for media upload, under an embodiment. This flow shows the signal and data flow that results when media is uploaded to the server.
         1. iHub→Camera   2. Camera→iHub/Registry Web   3. iHub/Registry Web→Media Upload   4. Media Upload→File System (local file system)   5. Media Upload→Broker   6. Broker→Media Upload (for processing)   7. Media Upload→File System (network file system)   8. Media Upload→Event Logging   9. Event Logging→DB   10. Event Logging→Broker (if user app is logged in to this site)       

       FIG.  9    is a flow diagram for live video, under an embodiment. This flow shows the signal and data flow that results when a client application session accesses live video using the Relay Server.
         1. Subscriber→Portal/Mobile/Admin Web (live video request)   2. Portal/Mobile/Admin Web→Customer Portal (live video request)   3. Customer Portal→Relay Server   4. Customer Portal→Gateway Device State/Config   5. Gateway Device State/Config→Session Server   6. Session Server→iHub   7. iHub→Camera   8. iHub→Relay Server   9. Customer Portal→Portal/Mobile/Admin Web (live video response)   10. Portal/Mobile/Admin Web→Subscriber (live video response)   11. Subscriber→Relay   12. Relay→iHub   13. iHub→Camera       

       FIG.  10    is a flow diagram for event trigger notification, under an embodiment. This flow shows the signal and data flow that results when a device event triggers a notification to be sent to the customer.
         1. iHub→Session Server   2. Session Server→Gateway Device State/Config   3. Gateway Device State/Config→DB   4. Gateway Device State/Config→Broker (if notification to be sent)   5. Broker→Notification   6. Notification→DB   7. Notification→SMTP (if email notification)   8. Notification→Open Market (if SMS notification)       

       FIG.  11    is a flow diagram for activation iHub, under an embodiment. This flow shows the signal and data flow that results when an iHub or ngHub is activated.
         1. Admin/Ops→Portal/Mobile/Admin Web (create site)   2. Portal/Mobile/Admin Web→Installer Portal (create site)   3. Installer Portal→DB (create site)   4. iHub→iHub/Registry Web (request: get cert)   5. iHub/Registry Web→Gateway Device State/Config (request: get cert)   6. Gateway Device State/Config→DB (save cert)   7. Gateway Device State/Config→iHub/Registry Web (response: get cert)   8. iHub/Registry Web→iHub (response: get cert)   9. iHub→Session Server   10. Session Server→Gateway Device State/Config (authenticate)   11. Gateway Device State/Config→DB   12. Installer Portal→DB (finalize site creation, set owner)       

       FIG.  12    is a flow diagram for activation LWG, under an embodiment. This flow shows the signal and data flow that results when a cellular-only security panel is activated.
         1. Admin/Ops→Portal/Mobile/Admin Web (create site)   2. Portal/Mobile/Admin Web→Installer Portal (create site)   3. Installer Portal→DSC C24/Alarmnet (get SIM status)   4. Installer Portal→DB (create site)   5. Installer Portal→Session Server (start LWG)   6. Session Server→Lightweight Gateway (start LWG)   7. Installer Portal→Session Server (communication test)   8. Session Server→Lightweight Gateway (communication test)   9. Lightweight Gateway→SMS   10. SMS→SMPP   11. CPE Device→Session Server (UDP event)   12. Session Server→Lightweight Gateway   13. Lightweight Gateway→Gateway Device State/Config   14. Gateway Device State/Config→DB   15. Installer Portal→DB (finalize site creation, set owner)       

       FIG.  13    is a flow diagram for app sign-in (Web/Android app) iHub, under an embodiment. This flow shows the signal and data flow that results when a customer (subscriber) with an iHub or ngHub signs in to the Android Application. The flow is largely the same for the Web Portal.
         1. User→Portal/Mobile/Admin Web (authentication, get site config)   2. Portal/Mobile/Admin Web→Mobile Portal (authentication, get site config)   3. Mobile Portal→DB (authentication, get site config)   4. Mobile Portal→Broker (add event listener for site)   5. Mobile Portal→User (initial view data)   6. Mobile Portal→Session Server (client heartbeat)   7. Session Server→iHub (client heartbeat)   8. iHub→Session Server (sync)   9. Session Server→Gateway Device State/Config (sync)   10. Gateway Device State/Config→DB   11. Gateway Device State/Config→Broker (publish to listeners)   12. Broker→Mobile Portal (publish to listeners)   13. Mobile Portal→Portal/Mobile/Admin Web (update view data)   14. Portal/Mobile/Admin Web→User (update view data)       

       FIG.  14    is a flow diagram for app sign-in (Web/Android app) LWG, under an embodiment. This flow shows the signal and data flow that results when a customer with a cellular-only panel (LWG) signs in to the Android Application. The flow is largely the same for the Web Portal.
         1. User→Portal/Mobile/Admin Web (authentication, get site config)   2. Portal/Mobile/Admin Web→Mobile Portal (authentication, get site config)   3. Mobile Portal→DB (authentication, get site config)   4. Mobile Portal→Broker (add event listener for site)   5. Mobile Portal→User (initial view data)   6. Mobile Portal→Session Server (client heartbeat)   7. Session Server→Lightweight Gateway (client heartbeat)   8. Lightweight Gateway→SMS (request TCP connection from panel)   9. SMS→SMPP   10. Lightweight Gateway→Session Server (sync)   11. Session Server→Gateway Device State/Config (sync)   12. Gateway Device State/Config→DB   13. Gateway Device State/Config→Broker (publish to listeners)   14. Broker→Mobile Portal (publish to listeners)   15. Mobile Portal→Portal/Mobile/Admin Web (update view data)   16. Portal/Mobile/Admin Web→User (update view data)       

       FIG.  15    is a flow diagram for app session, device event (Web/Android app), under an embodiment. This flow shows the signal and data flow that results when a customer is already signed in to the Android Application and a device event occurs. The flow is largely the same for the Web Portal.
         1. Lightweight Gateway/iHub→Session Server (sync)   2. Session Server→Gateway Device State/Config (sync)   3. Gateway Device State/Config→DB   4. Gateway Device State/Config→Event Logging   5. Event Logging→DB   6. Event Logging→Broker (publish to listeners)   7. Broker→Mobile Portal (publish to listeners)   8. Mobile Portal→Portal/Mobile/Admin Web (update view data)   9. Portal/Mobile/Admin Web→User (update view data)       

       FIG.  16    is a flow diagram for app sign-in (iOS) iHub, under an embodiment. This flow shows the signal and data flow that results when a customer with an iHub or ngHub signs in to the iOS Application.
         1. User→Portal/Mobile/Admin Web (authentication, get site config)   2. Portal/Mobile/Admin Web→Application Interface (authentication, get site config)   3. Application Interface→DB (authentication, get site config)   4. Application Interface→Session Server (client heartbeat)   5. Session Server→iHub (client heartbeat)   6. User→Portal/Mobile/Admin Web (request: get current state, deltas)   7. Portal/Mobile/Admin Web→Application Interface (request: get current state, deltas)   8. Application Interface→Session Server (request: get current state, deltas)   9. Session Server→iHub (request: get current state, deltas)   10. iHub→Session Server (response: get current state, deltas)   11. Session Server→Application Interface (response: get current state, deltas)   12. Application Interface→Portal/Mobile/Admin Web (response: get current state, deltas)   13. Portal/Mobile/Admin Web→User (response: get current state, deltas)       

       FIG.  17    is a flow diagram for app sign-in (iOS) LWG, under an embodiment. This flow shows the signal and data flow that results when a customer with a cellular-only panel (LWG) signs in to the iOS Application.
         1. User→Portal/Mobile/Admin Web (authentication, get site config)   2. Portal/Mobile/Admin Web→Application Interface (authentication, get site config)   3. Application Interface→DB (authentication, get site config)   4. Application Interface→Session Server (client heartbeat)   5. Session Server→Lightweight Gateway (client heartbeat)   6. Lightweight Gateway→SMS (request TCP connection from panel)   7. SMS→SMPP   8. User→Portal/Mobile/Admin Web (request: get current state, deltas)   9. Portal/Mobile/Admin Web→Application Interface (request: get current state, deltas)   10. Application Interface→Session Server (request: get current state, deltas)   11. Session Server→Lightweight Gateway (request: get current state, deltas)   12. Lightweight Gateway→Session Server (response: get current state, deltas)   13. Session Server→Application Interface (response: get current state, deltas)   14. Application Interface→Portal/Mobile/Admin Web (response: get current state, deltas)   15. Portal/Mobile/Admin Web→User (response: get current state, deltas)       

       FIG.  18    is a flow diagram for app session, device event (iOS app), under an embodiment. This flow shows the signal and data flow that results when a customer is already signed in to the iOS Application and a device event occurs.
         1. User→Portal/Mobile/Admin Web (request: get current state, deltas)   2. Portal/Mobile/Admin Web→Application Interface (request: get current state, deltas)   3. Application Interface→Session Server (request: get current state, deltas)   4. Session Server→iHub/Lightweight Gateway (request: get current state, deltas)   5. iHub/Lightweight Gateway→Session Server (response: get current state, deltas)   6. Session Server→Application Interface (response: get current state, deltas)   7. Application Interface→Portal/Mobile/Admin Web (response: get current state, deltas)   8. Portal/Mobile/Admin Web→User (response: get current state, deltas)       

       FIG.  19    is a flow diagram for LWG remote arm, under an embodiment. This flow shows the signal and data flow that results when a LWG remotely arms a cellular-only panel.
         1. User→Portal/Mobile/Admin Web (request: arm panel)   2. Portal/Mobile/Admin Web→Application Interface (request: arm panel)   3. Application Interface→Session Server (request: arm panel)   4. Session Server→Lightweight Gateway (request: arm panel)   5. Lightweight Gateway→CPE Device (send command over TCP connection to device)   6. CPE Device→Session Server (UDP arm state change event)   7. Session Server→Lightweight Gateway (UDP arm state change event)   8. Lightweight Gateway→Session Server (response: arm panel)   9. Session Server→Application Interface (response: arm panel)   10. Application Interface→Portal/Mobile/Admin Web (response: arm panel)   11. Portal/Mobile/Admin Web→User (response: arm panel)       

       FIG.  20    is a flow diagram for iHub reboot, under an embodiment. This flow shows the signal and data flow that results when an iHub or ngHub reboots (includes references to the above flows).
         1. iHub→iHub/Registry Web (request: get server info)   2. iHub/Registry Web→Gateway Registry (request: get server info)   3. Registry→DB (request: get server info)   4. Registry→iHub/Registry Web (response: get server info)   5. iHub/Registry Web→iHub (response: get server info)   6. iHub→iHub/Registry Web (request: get connect info)   7. iHub/Registry Web→Gateway Device State/Config (request: get connect info)   8. Gateway Device State/Config→iHub/Registry Web (response: get connect info)   9. iHub/Registry Web→iHub (response: get connect info)   10. iHub→Session Server   11. Session Server→Gateway Device State/Config (authenticate request)   12. Gateway Device State/Config→DB   13. Gateway Device State/Config→Session Server (authenticate response)       

       FIG.  21    is a flow diagram for iHub disconnect, under an embodiment. This flow shows the signal and data flow that results when an iHub or ngHub disconnects from the server (includes references to the above flows).
         1. Session Server→Gateway Device State/Config (disconnect)   2. Gateway Device State/Config→DB       

     The system of embodiments including the Cloud Hub and Virtual Gateway as described in detail herein includes one or more components of the “integrated security system” described in detail herein and in the Related Applications, which are incorporated by reference herein. An example of the “integrated security system” is available as one or more of the numerous systems or platforms available from iControl Networks, Inc., Redwood City, Calif. The system of an embodiment described herein incorporates one or more components of the “integrated security system”. The system of an embodiment described herein is coupled to one or more components of the “integrated security system”. The system of an embodiment described herein integrates with one or more components of the “integrated security system”. 
     More particularly, the methods and processes of the integrated security system, and hence the full functionality, can be implemented in the system described herein including the Cloud Hub and Virtual Gateway. Therefore, embodiments of the systems described herein integrate broadband and mobile access and control with conventional security systems and premise devices to provide a tri-mode security network (broadband, cellular/GSM, POTS access) that enables users to remotely stay connected to their premises. The integrated security system, while delivering remote premise monitoring and control functionality to conventional monitored premise protection, complements existing premise protection equipment. The integrated security system integrates into the premise network and couples wirelessly with the conventional security panel, enabling broadband access to premise security systems. Automation devices (cameras, lamp modules, thermostats, etc.) can be added, enabling users to remotely see live video and/or pictures and control home devices via their personal web portal or webpage, mobile phone, and/or other remote client device. Users can also receive notifications via email or text message when happenings occur, or do not occur, in their home. 
     In accordance with the embodiments described herein, a wireless system (e.g., radio frequency (RF)) is provided that enables a security provider or consumer to extend the capabilities of an existing RF-capable security system or a non-RF-capable security system that has been upgraded to support RF capabilities. The system includes an RF-capable Gateway device (physically located within RF range of the RF-capable security system) and associated software operating on the Gateway device. The system also includes a web server, application server, and remote database providing a persistent store for information related to the system. 
     The security systems of an embodiment, referred to herein as the iControl security system or integrated security system, extend the value of traditional home security by adding broadband access and the advantages of remote home monitoring and home control through the formation of a security network including components of the integrated security system integrated with a conventional premise security system and a premise local area network (LAN). With the integrated security system, conventional home security sensors, cameras, touchscreen keypads, lighting controls, and/or Internet Protocol (IP) devices in the home (or business) become connected devices that are accessible anywhere in the world from a web browser, mobile phone or through content-enabled touchscreens. The integrated security system experience allows security operators to both extend the value proposition of their monitored security systems and reach new consumers that include broadband users interested in staying connected to their family, home and property when they are away from home. 
     The integrated security system of an embodiment includes security servers (also referred to herein as iConnect servers or security network servers) and an iHub gateway (also referred to herein as the gateway, the iHub, or the iHub client) that couples or integrates into a home network (e.g., LAN) and communicates directly with the home security panel, in both wired and wireless installations. The security system of an embodiment automatically discovers the security system components (e.g., sensors, etc.) belonging to the security system and connected to a control panel of the security system and provides consumers with full two-way access via web and mobile portals. The gateway supports various wireless protocols and can interconnect with a wide range of control panels offered by security system providers. Service providers and users can then extend the system&#39;s capabilities with the additional IP cameras, lighting modules or security devices such as interactive touchscreen keypads. The integrated security system adds an enhanced value to these security systems by enabling consumers to stay connected through email and SMS alerts, photo push, event-based video capture and rule-based monitoring and notifications. This solution extends the reach of home security to households with broadband access. 
     The integrated security system builds upon the foundation afforded by traditional security systems by layering broadband and mobile access, IP cameras, interactive touchscreens, and an open approach to home automation on top of traditional security system configurations. The integrated security system is easily installed and managed by the security operator, and simplifies the traditional security installation process, as described below. 
     The integrated security system provides an open systems solution to the home security market. As such, the foundation of the integrated security system customer premises equipment (CPE) approach has been to abstract devices, and allows applications to manipulate and manage multiple devices from any vendor. The integrated security system DeviceConnect technology that enables this capability supports protocols, devices, and panels from GE Security and Honeywell, as well as consumer devices using Z-Wave, IP cameras (e.g., Ethernet, wifi, and Homeplug), and IP touchscreens. The DeviceConnect is a device abstraction layer that enables any device or protocol layer to interoperate with integrated security system components. This architecture enables the addition of new devices supporting any of these interfaces, as well as add entirely new protocols. 
     The benefit of DeviceConnect is that it provides supplier flexibility. The same consistent touchscreen, web, and mobile user experience operate unchanged on whatever security equipment selected by a security system provider, with the system provider&#39;s choice of IP cameras, backend data center and central station software. 
     The integrated security system provides a complete system that integrates or layers on top of a conventional host security system available from a security system provider. The security system provider therefore can select different components or configurations to offer (e.g., CDMA, GPRS, no cellular, etc.) as well as have iControl modify the integrated security system configuration for the system provider&#39;s specific needs (e.g., change the functionality of the web or mobile portal, add a GE or Honeywell-compatible TouchScreen, etc.). 
     The integrated security system integrates with the security system provider infrastructure for central station reporting directly via Broadband and GPRS alarm transmissions. Traditional dial-up reporting is supported via the standard panel connectivity. Additionally, the integrated security system provides interfaces for advanced functionality to the CMS, including enhanced alarm events, system installation optimizations, system test verification, video verification, 2-way voice over IP and GSM. 
     The integrated security system is an IP centric system that includes broadband connectivity so that the gateway augments the existing security system with broadband and GPRS connectivity. If broadband is down or unavailable GPRS may be used, for example. The integrated security system supports GPRS connectivity using an optional wireless package that includes a GPRS modem in the gateway. The integrated security system treats the GPRS connection as a higher cost though flexible option for data transfers. In an embodiment the GPRS connection is only used to route alarm events (e.g., for cost), however the gateway can be configured (e.g., through the iConnect server interface) to act as a primary channel and pass any or all events over GPRS. Consequently, the integrated security system does not interfere with the current plain old telephone service (POTS) security panel interface. Alarm events can still be routed through POTS; however the gateway also allows such events to be routed through a broadband or GPRS connection as well. The integrated security system provides a web application interface to the CSR tool suite as well as XML, web services interfaces for programmatic integration between the security system provider&#39;s existing call center products. The integrated security system includes, for example, APIs that allow the security system provider to integrate components of the integrated security system into a custom call center interface. The APIs include XML web service APIs for integration of existing security system provider call center applications with the integrated security system service. All functionality available in the CSR Web application is provided with these API sets. The Java and XML-based APIs of the integrated security system support provisioning, billing, system administration, CSR, central station, portal user interfaces, and content management functions, to name a few. The integrated security system can provide a customized interface to the security system provider&#39;s billing system, or alternatively can provide security system developers with APIs and support in the integration effort. 
     The integrated security system provides or includes business component interfaces for provisioning, administration, and customer care to name a few. Standard templates and examples are provided with a defined customer professional services engagement to help integrate OSS/BSS systems of a Service Provider with the integrated security system. 
     The integrated security system components support and allow for the integration of customer account creation and deletion with a security system. The iConnect APIs provides access to the provisioning and account management system in iConnect and provide full support for account creation, provisioning, and deletion. Depending on the requirements of the security system provider, the iConnect APIs can be used to completely customize any aspect of the integrated security system backend operational system. 
     The integrated security system includes a gateway that supports the following standards-based interfaces, to name a few: Ethernet IP communications via Ethernet ports on the gateway, and standard XML/TCP/IP protocols and ports are employed over secured SSL sessions; USB 2.0 via ports on the gateway; 802.11b/g/n IP communications; GSM/GPRS RF WAN communications; CDMA 1×RTT RF WAN communications (optional, can also support EVDO and 3G technologies). 
     The gateway supports the following proprietary interfaces, to name a few: interfaces including Dialog RF network (319.5 MHz) and RS485 Superbus 2000 wired interface; RF mesh network (908 MHz); and interfaces including RF network (345 MHz) and RS485/RS232bus wired interfaces. 
     Regarding security for the IP communications (e.g., authentication, authorization, encryption, anti-spoofing, etc), the integrated security system uses SSL to encrypt all IP traffic, using server and client-certificates for authentication, as well as authentication in the data sent over the SSL-encrypted channel. For encryption, integrated security system issues public/private key pairs at the time/place of manufacture, and certificates are not stored in any online storage in an embodiment. 
     The integrated security system does not need any special rules at the customer premise and/or at the security system provider central station because the integrated security system makes outgoing connections using TCP over the standard HTTP and HTTPS ports. Provided outbound TCP connections are allowed then no special requirements on the firewalls are necessary. 
       FIG.  22    is a block diagram of the integrated security system  100 , under an embodiment. The integrated security system  100  of an embodiment includes the gateway  102  and the security servers  104  coupled to the conventional home security system  110 . At a customer&#39;s home or business, the gateway  102  connects and manages the diverse variety of home security and self-monitoring devices. The gateway  102  communicates with the iConnect Servers  104  located in the service provider&#39;s data center  106  (or hosted in integrated security system data center), with the communication taking place via a communication network  108  or other network (e.g., cellular network, internet, etc.). These servers  104  manage the system integrations necessary to deliver the integrated system service described herein. The combination of the gateway  102  and the iConnect servers  104  enable a wide variety of remote client devices  120  (e.g., PCs, mobile phones and PDAs) allowing users to remotely stay in touch with their home, business and family. In addition, the technology allows home security and self-monitoring information, as well as relevant third party content such as traffic and weather, to be presented in intuitive ways within the home, such as on advanced touchscreen keypads. 
     The integrated security system service (also referred to as iControl service) can be managed by a service provider via browser-based Maintenance and Service Management applications that are provided with the iConnect Servers. Or, if desired, the service can be more tightly integrated with existing OSS/BSS and service delivery systems via the iConnect web services-based XML APIs. 
     The integrated security system service can also coordinate the sending of alarms to the home security Central Monitoring Station (CMS)  199 . Alarms are passed to the CMS  199  using standard protocols such as Contact ID or SIA and can be generated from the home security panel location as well as by iConnect server  104  conditions (such as lack of communications with the integrated security system). In addition, the link between the security servers  104  and CMS  199  provides tighter integration between home security and self-monitoring devices and the gateway  102 . Such integration enables advanced security capabilities such as the ability for CMS personnel to view photos taken at the time a burglary alarm was triggered. For maximum security, the gateway  102  and iConnect servers  104  support the use of a mobile network (both GPRS and CDMA options are available) as a backup to the primary broadband connection. 
     The integrated security system service is delivered by hosted servers running software components that communicate with a variety of client types while interacting with other systems.  FIG.  23    is a block diagram of components of the integrated security system  100 , under an embodiment. Following is a more detailed description of the components. 
     The iConnect servers  104  support a diverse collection of clients  120  ranging from mobile devices, to PCs, to in-home security devices, to a service provider&#39;s internal systems. Most clients  120  are used by end-users, but there are also a number of clients  120  that are used to operate the service. 
     Clients  120  used by end-users of the integrated security system  100  include, but are not limited to, the following:
         Clients based on gateway client applications  202  (e.g., a processor-based device running the gateway technology that manages home security and automation devices).   A web browser  204  accessing a Web Portal application, performing end-user configuration and customization of the integrated security system service as well as monitoring of in-home device status, viewing photos and video, etc. Device and user management can also be performed by this portal application.   A mobile device  206  (e.g., PDA, mobile phone, etc.) accessing the integrated security system Mobile Portal. This type of client  206  is used by end-users to view system status and perform operations on devices (e.g., turning on a lamp, arming a security panel, etc.) rather than for system configuration tasks such as adding a new device or user.   PC or browser-based “widget” containers  208  that present integrated security system service content, as well as other third-party content, in simple, targeted ways (e.g. a widget that resides on a PC desktop and shows live video from a single in-home camera). “Widget” as used herein means applications or programs in the system.   Touchscreen home security keypads  208  and advanced in-home devices that present a variety of content widgets via an intuitive touchscreen user interface.   Notification recipients  210  (e.g., cell phones that receive SMS-based notifications when certain events occur (or don&#39;t occur), email clients that receive an email message with similar information, etc.).   Custom-built clients (not shown) that access the iConnect web services XML API to interact with users&#39; home security and self-monitoring information in new and unique ways. Such clients could include new types of mobile devices, or complex applications where integrated security system content is integrated into a broader set of application features.       

     In addition to the end-user clients, the iConnect servers  104  support PC browser-based Service Management clients that manage the ongoing operation of the overall service. These clients run applications that handle tasks such as provisioning, service monitoring, customer support and reporting. 
     There are numerous types of server components of the iConnect servers  104  of an embodiment including, but not limited to, the following: Business Components which manage information about all of the home security and self-monitoring devices; End-User Application Components which display that information for users and access the Business Components via published XML APIs; and Service Management Application Components which enable operators to administer the service (these components also access the Business Components via the XML APIs, and also via published SNMP MIBs). 
     The server components provide access to, and management of, the objects associated with an integrated security system installation. The top-level object is the “network.” It is a location where a gateway  102  is located, and is also commonly referred to as a site or premises; the premises can include any type of structure (e.g., home, office, warehouse, etc.) at which a gateway  102  is located. Users can only access the networks to which they have been granted permission. Within a network, every object monitored by the gateway  102  is called a device. Devices include the sensors, cameras, home security panels and automation devices, as well as the controller or processor-based device running the gateway applications. 
     Various types of interactions are possible between the objects in a system. Automations define actions that occur as a result of a change in state of a device. For example, take a picture with the front entry camera when the front door sensor changes to “open”. Notifications are messages sent to users to indicate that something has occurred, such as the front door going to “open” state, or has not occurred (referred to as an iWatch notification). Schedules define changes in device states that are to take place at predefined days and times. For example, set the security panel to “Armed” mode every weeknight at 11:00 pm. 
     The iConnect Business Components are responsible for orchestrating all of the low-level service management activities for the integrated security system service. They define all of the users and devices associated with a network (site), analyze how the devices interact, and trigger associated actions (such as sending notifications to users). All changes in device states are monitored and logged. The Business Components also manage all interactions with external systems as required, including sending alarms and other related self-monitoring data to the home security Central Monitoring System (CMS) 199. The Business Components are implemented as portable Java J2EE Servlets, but are not so limited. 
     The following iConnect Business Components manage the main elements of the integrated security system service, but the embodiment is not so limited:
         A Registry Manager  220  defines and manages users and networks. This component is responsible for the creation, modification and termination of users and networks. It is also where a user&#39;s access to networks is defined.   A Network Manager  222  defines and manages security and self-monitoring devices that are deployed on a network (site). This component handles the creation, modification, deletion and configuration of the devices, as well as the creation of automations, schedules and notification rules associated with those devices.   A Data Manager  224  manages access to current and logged state data for an existing network and its devices. This component specifically does not provide any access to network management capabilities, such as adding new devices to a network, which are handled exclusively by the Network Manager  222 .   To achieve optimal performance for all types of queries, data for current device states is stored separately from historical state data (a.k.a. “logs”) in the database. A Log Data Manager  226  performs ongoing transfers of current device state data to the historical data log tables.       

     Additional iConnect Business Components handle direct communications with certain clients and other systems, for example:
         An iHub Manager  228  directly manages all communications with gateway clients, including receiving information about device state changes, changing the configuration of devices, and pushing new versions of the gateway client to the hardware it is running on.   A Notification Manager  230  is responsible for sending all notifications to clients via SMS (mobile phone messages), email (via a relay server like an SMTP email server), etc.   An Alarm and CMS Manager  232  sends critical server-generated alarm events to the home security Central Monitoring Station (CMS) and manages all other communications of integrated security system service data to and from the CMS.   The Element Management System (EMS)  234  is an iControl Business Component that manages all activities associated with service installation, scaling and monitoring, and filters and packages service operations data for use by service management applications. The SNMP MIBs published by the EMS can also be incorporated into any third party monitoring system if desired.       

     The iConnect Business Components store information about the objects that they manage in the iControl Service Database  240  and in the iControl Content Store  242 . The iControl Content Store is used to store media objects like video, photos and widget content, while the Service Database stores information about users, networks, and devices. Database interaction is performed via a JDBC interface. For security purposes, the Business Components manage all data storage and retrieval. 
     The iControl Business Components provide web services-based APIs that application components use to access the Business Components&#39; capabilities. Functions of application components include presenting integrated security system service data to end-users, performing administrative duties, and integrating with external systems and back-office applications. 
     The primary published APIs for the iConnect Business Components include, but are not limited to, the following:
         A Registry Manager API  252  provides access to the Registry Manager Business Component&#39;s functionality, allowing management of networks and users.   A Network Manager API  254  provides access to the Network Manager Business Component&#39;s functionality, allowing management of devices on a network.   A Data Manager API  256  provides access to the Data Manager Business Component&#39;s functionality, such as setting and retrieving (current and historical) data about device states.   A Provisioning API  258  provides a simple way to create new networks and configure initial default properties.       

     Each API of an embodiment includes two modes of access: Java API or XML API. The XML APIs are published as web services so that they can be easily accessed by applications or servers over a network. The Java APIs are a programmer-friendly wrapper for the XML APIs. Application components and integrations written in Java should generally use the Java APIs rather than the XML APIs directly. 
     The iConnect Business Components also have an XML-based interface  260  for quickly adding support for new devices to the integrated security system. This interface  260 , referred to as DeviceConnect  260 , is a flexible, standards-based mechanism for defining the properties of new devices and how they can be managed. Although the format is flexible enough to allow the addition of any type of future device, pre-defined XML profiles are currently available for adding common types of devices such as sensors (SensorConnect), home security panels (PanelConnect) and IP cameras (CameraConnect). 
     The iConnect End-User Application Components deliver the user interfaces that run on the different types of clients supported by the integrated security system service. The components are written in portable Java J2EE technology (e.g., as Java Servlets, as JavaServer Pages (JSPs), etc.) and they all interact with the iControl Business Components via the published APIs. 
     The following End-User Application Components generate CSS-based HTML/JavaScript that is displayed on the target client. These applications can be dynamically branded with partner-specific logos and URL links (such as Customer Support, etc.). The End-User Application Components of an embodiment include, but are not limited to, the following:
         An iControl Activation Application  270  that delivers the first application that a user sees when they set up the integrated security system service. This wizard-based web browser application securely associates a new user with a purchased gateway and the other devices included with it as a kit (if any). It primarily uses functionality published by the Provisioning API.   An iControl Web Portal Application  272  runs on PC browsers and delivers the web-based interface to the integrated security system service. This application allows users to manage their networks (e.g. add devices and create automations) as well as to view/change device states, and manage pictures and videos. Because of the wide scope of capabilities of this application, it uses three different Business Component APIs that include the Registry Manager API, Network Manager API, and Data Manager API, but the embodiment is not so limited.   An iControl Mobile Portal  274  is a small-footprint web-based interface that runs on mobile phones and PDAs. This interface is optimized for remote viewing of device states and pictures/videos rather than network management. As such, its interaction with the Business Components is primarily via the Data Manager API.   Custom portals and targeted client applications can be provided that leverage the same Business Component APIs used by the above applications.   A Content Manager Application Component  276  delivers content to a variety of clients. It sends multimedia-rich user interface components to widget container clients (both PC and browser-based), as well as to advanced touchscreen keypad clients. In addition to providing content directly to end-user devices, the Content Manager  276  provides widget-based user interface components to satisfy requests from other Application Components such as the iControl Web  272  and Mobile  274  portals.       

     A number of Application Components are responsible for overall management of the service. These pre-defined applications, referred to as Service Management Application Components, are configured to offer off-the-shelf solutions for production management of the integrated security system service including provisioning, overall service monitoring, customer support, and reporting, for example. The Service Management Application Components of an embodiment include, but are not limited to, the following:
         A Service Management Application  280  allows service administrators to perform activities associated with service installation, scaling and monitoring/alerting. This application interacts heavily with the Element Management System (EMS) Business Component to execute its functionality, and also retrieves its monitoring data from that component via protocols such as SNMP MIBs.   A Kitting Application  282  is used by employees performing service provisioning tasks. This application allows home security and self-monitoring devices to be associated with gateways during the warehouse kitting process.   A CSR Application and Report Generator  284  is used by personnel supporting the integrated security system service, such as CSRs resolving end-user issues and employees enquiring about overall service usage. Pushes of new gateway firmware to deployed gateways is also managed by this application.       

     The iConnect servers  104  also support custom-built integrations with a service provider&#39;s existing OSS/BSS, CSR and service delivery systems  290 . Such systems can access the iConnect web services XML API to transfer data to and from the iConnect servers  104 . These types of integrations can compliment or replace the PC browser-based Service Management applications, depending on service provider needs. 
     As described above, the integrated security system of an embodiment includes a gateway, or iHub. The gateway of an embodiment includes a device that is deployed in the home or business and couples or connects the various third-party cameras, home security panels, sensors and devices to the iConnect server over a WAN connection as described in detail herein. The gateway couples to the home network and communicates directly with the home security panel in both wired and wireless sensor installations. The gateway is configured to be low-cost, reliable and thin so that it complements the integrated security system network-based architecture. 
     The gateway supports various wireless protocols and can interconnect with a wide range of home security control panels. Service providers and users can then extend the system&#39;s capabilities by adding IP cameras, lighting modules and additional security devices. The gateway is configurable to be integrated into many consumer appliances, including set-top boxes, routers and security panels. The small and efficient footprint of the gateway enables this portability and versatility, thereby simplifying and reducing the overall cost of the deployment. 
       FIG.  24    is a block diagram of the gateway  102  including gateway software or applications, under an embodiment. The gateway software architecture is relatively thin and efficient, thereby simplifying its integration into other consumer appliances such as set-top boxes, routers, touch screens and security panels. The software architecture also provides a high degree of security against unauthorized access. This section describes the various key components of the gateway software architecture. 
     The gateway application layer  302  is the main program that orchestrates the operations performed by the gateway. The Security Engine  304  provides robust protection against intentional and unintentional intrusion into the integrated security system network from the outside world (both from inside the premises as well as from the WAN). The Security Engine  304  of an embodiment comprises one or more sub-modules or components that perform functions including, but not limited to, the following:
         Encryption including 128-bit SSL encryption for gateway and iConnect server communication to protect user data privacy and provide secure communication.   Bi-directional authentication between the gateway and iConnect server in order to prevent unauthorized spoofing and attacks. Data sent from the iConnect server to the gateway application (or vice versa) is digitally signed as an additional layer of security. Digital signing provides both authentication and validation that the data has not been altered in transit.   Camera SSL encapsulation because picture and video traffic offered by off-the-shelf networked IP cameras is not secure when traveling over the Internet. The gateway provides for 128-bit SSL encapsulation of the user picture and video data sent over the internet for complete user security and privacy.   802.11b/g/n with WPA-2 security to ensure that wireless camera communications always takes place using the strongest available protection.   A gateway-enabled device is assigned a unique activation key for activation with an iConnect server. This ensures that only valid gateway-enabled devices can be activated for use with the specific instance of iConnect server in use. Attempts to activate gateway-enabled devices by brute force are detected by the Security Engine. Partners deploying gateway-enabled devices have the knowledge that only a gateway with the correct serial number and activation key can be activated for use with an iConnect server. Stolen devices, devices attempting to masquerade as gateway-enabled devices, and malicious outsiders (or insiders as knowledgeable but nefarious customers) cannot effect other customers&#39; gateway-enabled devices.       

     As standards evolve, and new encryption and authentication methods are proven to be useful, and older mechanisms proven to be breakable, the security manager can be upgraded “over the air” to provide new and better security for communications between the iConnect server and the gateway application, and locally at the premises to remove any risk of eavesdropping on camera communications. 
     A Remote Firmware Download module  306  allows for seamless and secure updates to the gateway firmware through the iControl Maintenance Application on the server  104 , providing a transparent, hassle-free mechanism for the service provider to deploy new features and bug fixes to the installed user base. The firmware download mechanism is tolerant of connection loss, power interruption and user interventions (both intentional and unintentional). Such robustness reduces down time and customer support issues. Gateway firmware can be remotely download either for one gateway at a time, a group of gateways, or in batches. 
     The Automations engine  308  manages the user-defined rules of interaction between the different devices (e.g. when door opens turn on the light). Though the automation rules are programmed and reside at the portal/server level, they are cached at the gateway level in order to provide short latency between device triggers and actions. 
     DeviceConnect  310  includes definitions of all supported devices (e.g., cameras, security panels, sensors, etc.) using a standardized plug-in architecture. The DeviceConnect module  310  offers an interface that can be used to quickly add support for any new device as well as enabling interoperability between devices that use different technologies/protocols. For common device types, pre-defined sub-modules have been defined, making supporting new devices of these types even easier. SensorConnect  312  is provided for adding new sensors, CameraConnect  316  for adding IP cameras, and PanelConnect  314  for adding home security panels. 
     The Schedules engine  318  is responsible for executing the user defined schedules (e.g., take a picture every five minutes; every day at 8 am set temperature to 65 degrees Fahrenheit, etc.). Though the schedules are programmed and reside at the iConnect server level they are sent to the scheduler within the gateway application. The Schedules Engine  318  then interfaces with SensorConnect  312  to ensure that scheduled events occur at precisely the desired time. 
     The Device Management module  320  is in charge of all discovery, installation and configuration of both wired and wireless IP devices (e.g., cameras, etc.) coupled or connected to the system. Networked IP devices, such as those used in the integrated security system, require user configuration of many IP and security parameters—to simplify the user experience and reduce the customer support burden, the device management module of an embodiment handles the details of this configuration. The device management module also manages the video routing module described below. 
     The video routing engine  322  is responsible for delivering seamless video streams to the user with zero-configuration. Through a multi-step, staged approach the video routing engine uses a combination of UPnP port-forwarding, relay server routing and STUN/TURN peer-to-peer routing. 
       FIG.  25    is a block diagram of components of the gateway  102 , under an embodiment. Depending on the specific set of functionality desired by the service provider deploying the integrated security system service, the gateway  102  can use any of a number of processors  402 , due to the small footprint of the gateway application firmware. In an embodiment, the gateway could include the Broadcom BCM5354 as the processor for example. In addition, the gateway  102  includes memory (e.g., FLASH  404 , RAM  406 , etc.) and any number of input/output (I/O) ports  408 . 
     Referring to the WAN portion  410  of the gateway  102 , the gateway  102  of an embodiment can communicate with the iConnect server using a number of communication types and/or protocols, for example Broadband  412 , GPRS  414  and/or Public Switched Telephone Network (PTSN)  416  to name a few. In general, broadband communication  412  is the primary means of connection between the gateway  102  and the iConnect server  104  and the GPRS/CDMA  414  and/or PSTN  416  interfaces acts as backup for fault tolerance in case the user&#39;s broadband connection fails for whatever reason, but the embodiment is not so limited. 
     Referring to the LAN portion  420  of the gateway  102 , various protocols and physical transceivers can be used to communicate to off-the-shelf sensors and cameras. The gateway  102  is protocol-agnostic and technology-agnostic and as such can easily support almost any device networking protocol. The gateway  102  can, for example, support GE and Honeywell security RF protocols  422 , Z-Wave  424 , serial (RS232 and RS485)  426  for direct connection to security panels as well as WiFi  428  (802.11b/g) for communication to WiFi cameras. 
     The integrated security system includes couplings or connections among a variety of IP devices or components, and the device management module is in charge of the discovery, installation and configuration of the IP devices coupled or connected to the system, as described above. The integrated security system of an embodiment uses a “sandbox” network to discover and manage all IP devices coupled or connected as components of the system. The IP devices of an embodiment include wired devices, wireless devices, cameras, interactive touchscreens, and security panels to name a few. These devices can be wired via ethernet cable or Wifi devices, all of which are secured within the sandbox network, as described below. The “sandbox” network is described in detail below. 
       FIG.  26    is a block diagram  500  of network or premise device integration with a premise network  250 , under an embodiment. In an embodiment, network devices  255 - 257  are coupled to the gateway  102  using a secure network coupling or connection such as SSL over an encrypted 802.11 link (utilizing for example WPA-2 security for the wireless encryption). The network coupling or connection between the gateway  102  and the network devices  255 - 257  is a private coupling or connection in that it is segregated from any other network couplings or connections. The gateway  102  is coupled to the premise router/firewall  252  via a coupling with a premise LAN  250 . The premise router/firewall  252  is coupled to a broadband modem  251 , and the broadband modem  251  is coupled to a WAN  200  or other network outside the premise. The gateway  102  thus enables or forms a separate wireless network, or sub-network, that includes some number of devices and is coupled or connected to the LAN  250  of the host premises. The gateway sub-network can include, but is not limited to, any number of other devices like WiFi IP cameras, security panels (e.g., IP-enabled), and security touchscreens, to name a few. The gateway  102  manages or controls the sub-network separately from the LAN  250  and transfers data and information between components of the sub-network and the LAN  250 /WAN  200 , but is not so limited. Additionally, other network devices  254  can be coupled to the LAN  250  without being coupled to the gateway  102 . 
       FIG.  27    is a block diagram  600  of network or premise device integration with a premise network  250 , under an alternative embodiment. The network or premise devices  255 - 257  are coupled to the gateway  102 . The network coupling or connection between the gateway  102  and the network devices  255 - 257  is a private coupling or connection in that it is segregated from any other network couplings or connections. The gateway  102  is coupled or connected between the premise router/firewall  252  and the broadband modem  251 . The broadband modem  251  is coupled to a WAN  200  or other network outside the premise, while the premise router/firewall  252  is coupled to a premise LAN  250 . As a result of its location between the broadband modem  251  and the premise router/firewall  252 , the gateway  102  can be configured or function as the premise router routing specified data between the outside network (e.g., WAN  200 ) and the premise router/firewall  252  of the LAN  250 . As described above, the gateway  102  in this configuration enables or forms a separate wireless network, or sub-network, that includes the network or premise devices  255 - 257  and is coupled or connected between the LAN  250  of the host premises and the WAN  200 . The gateway sub-network can include, but is not limited to, any number of network or premise devices  255 - 257  like WiFi IP cameras, security panels (e.g., IP-enabled), and security touchscreens, to name a few. The gateway  102  manages or controls the sub-network separately from the LAN  250  and transfers data and information between components of the sub-network and the LAN  250 /WAN  200 , but is not so limited. Additionally, other network devices  254  can be coupled to the LAN  250  without being coupled to the gateway  102 . 
     The examples described above with reference to  FIGS.  5  and  6    are presented only as examples of IP device integration. The integrated security system is not limited to the type, number and/or combination of IP devices shown and described in these examples, and any type, number and/or combination of IP devices is contemplated within the scope of this disclosure as capable of being integrated with the premise network. 
     The integrated security system of an embodiment includes a touchscreen (also referred to as the iControl touchscreen or integrated security system touchscreen), as described above, which provides core security keypad functionality, content management and presentation, and embedded systems design. The networked security touchscreen system of an embodiment enables a consumer or security provider to easily and automatically install, configure and manage the security system and touchscreen located at a customer premise. Using this system the customer may access and control the local security system, local IP devices such as cameras, local sensors and control devices (such as lighting controls or pipe freeze sensors), as well as the local security system panel and associated security sensors (such as door/window, motion, and smoke detectors). The customer premise may be a home, business, and/or other location equipped with a wired or wireless broadband IP connection. 
     The system of an embodiment includes a touchscreen with a configurable software user interface and/or a gateway device (e.g., iHub) that couples or connects to a premise security panel through a wired or wireless connection, and a remote server that provides access to content and information from the premises devices to a user when they are remote from the home. The touchscreen supports broadband and/or WAN wireless connectivity. In this embodiment, the touchscreen incorporates an IP broadband connection (e.g., Wifi radio, Ethernet port, etc.), and/or a cellular radio (e.g., GPRS/GSM, CDMA, WiMax, etc.). The touchscreen described herein can be used as one or more of a security system interface panel and a network user interface (UI) that provides an interface to interact with a network (e.g., LAN, WAN, internet, etc.). 
     The touchscreen of an embodiment provides an integrated touchscreen and security panel as an all-in-one device. Once integrated using the touchscreen, the touchscreen and a security panel of a premise security system become physically co-located in one device, and the functionality of both may even be co-resident on the same CPU and memory (though this is not required). 
     The touchscreen of an embodiment also provides an integrated IP video and touchscreen UI. As such, the touchscreen supports one or more standard video CODECs/players (e.g., H.264, Flash Video, MOV, MPEG4, M-JPEG, etc.). The touchscreen UI then provides a mechanism (such as a camera or video widget) to play video. In an embodiment the video is streamed live from an IP video camera. In other embodiments the video comprises video clips or photos sent from an IP camera or from a remote location. 
     The touchscreen of an embodiment provides a configurable user interface system that includes a configuration supporting use as a security touchscreen. In this embodiment, the touchscreen utilizes a modular user interface that allows components to be modified easily by a service provider, an installer, or even the end user. Examples of such a modular approach include using Flash widgets, HTML-based widgets, or other downloadable code modules such that the user interface of the touchscreen can be updated and modified while the application is running. In an embodiment the touchscreen user interface modules can be downloaded over the internet. For example, a new security configuration widget can be downloaded from a standard web server, and the touchscreen then loads such configuration app into memory, and inserts it in place of the old security configuration widget. The touchscreen of an embodiment is configured to provide a self-install user interface. 
     Embodiments of the networked security touchscreen system described herein include a touchscreen device with a user interface that includes a security toolbar providing one or more functions including arm, disarm, panic, medic, and alert. The touchscreen therefore includes at least one screen having a separate region of the screen dedicated to a security toolbar. The security toolbar of an embodiment is present in the dedicated region at all times that the screen is active. 
     The touchscreen of an embodiment includes a home screen having a separate region of the screen allocated to managing home-based functions. The home-based functions of an embodiment include managing, viewing, and/or controlling IP video cameras. In this embodiment, regions of the home screen are allocated in the form of widget icons; these widget icons (e.g. for cameras, thermostats, lighting, etc) provide functionality for managing home systems. So, for example, a displayed camera icon, when selected, launches a Camera Widget, and the Camera widget in turn provides access to video from one or more cameras, as well as providing the user with relevant camera controls (take a picture, focus the camera, etc.) 
     The touchscreen of an embodiment includes a home screen having a separate region of the screen allocated to managing, viewing, and/or controlling internet-based content or applications. For example, the Widget Manager UI presents a region of the home screen (up to and including the entire home screen) where internet widgets icons such as weather, sports, etc. may be accessed). Each of these icons may be selected to launch their respective content services. 
     The touchscreen of an embodiment is integrated into a premise network using the gateway, as described above. The gateway as described herein functions to enable a separate wireless network, or sub-network, that is coupled, connected, or integrated with another network (e.g., WAN, LAN of the host premises, etc.). The sub-network enabled by the gateway optimizes the installation process for IP devices, like the touchscreen, that couple or connect to the sub-network by segregating these IP devices from other such devices on the network. This segregation of the IP devices of the sub-network further enables separate security and privacy policies to be implemented for these IP devices so that, where the IP devices are dedicated to specific functions (e.g., security), the security and privacy policies can be tailored specifically for the specific functions. Furthermore, the gateway and the sub-network it forms enables the segregation of data traffic, resulting in faster and more efficient data flow between components of the host network, components of the sub-network, and between components of the sub-network and components of the network. 
     The touchscreen of an embodiment includes a core functional embedded system that includes an embedded operating system, required hardware drivers, and an open system interface to name a few. The core functional embedded system can be provided by or as a component of a conventional security system (e.g., security system available from GE Security). These core functional units are used with components of the integrated security system as described herein. Note that portions of the touchscreen description below may include reference to a host premise security system (e.g., GE security system), but these references are included only as an example and do not limit the touchscreen to integration with any particular security system. 
     As an example, regarding the core functional embedded system, a reduced memory footprint version of embedded Linux forms the core operating system in an embodiment, and provides basic TCP/IP stack and memory management functions, along with a basic set of low-level graphics primitives. A set of device drivers is also provided or included that offer low-level hardware and network interfaces. In addition to the standard drivers, an interface to the RS 485 bus is included that couples or connects to the security system panel (e.g., GE Concord panel). The interface may, for example, implement the Superbus 2000 protocol, which can then be utilized by the more comprehensive transaction-level security functions implemented in PanelConnect technology (e.g SetAlarmLevel (int level, int partition, char *accessCode)). Power control drivers are also provided. 
       FIG.  28    is a block diagram of a touchscreen  700  of the integrated security system, under an embodiment. The touchscreen  700  generally includes an application/presentation layer  702  with a resident application  704 , and a core engine  706 . The touchscreen  700  also includes one or more of the following, but is not so limited: applications of premium services  710 , widgets  712 , a caching proxy  714 , network security  716 , network interface  718 , security object  720 , applications supporting devices  722 , PanelConnect API  724 , a gateway interface  726 , and one or more ports  728 . 
     More specifically, the touchscreen, when configured as a home security device, includes but is not limited to the following application or software modules: RS 485 and/or RS-232 bus security protocols to conventional home security system panel (e.g., GE Concord panel); functional home security classes and interfaces (e.g. Panel ARM state, Sensor status, etc.); Application/Presentation layer or engine; Resident Application; Consumer Home Security Application; installer home security application; core engine; and System bootloader/Software Updater. The core Application engine and system bootloader can also be used to support other advanced content and applications. This provides a seamless interaction between the premise security application and other optional services such as weather widgets or IP cameras. 
     An alternative configuration of the touchscreen includes a first Application engine for premise security and a second Application engine for all other applications. The integrated security system application engine supports content standards such as HTML, XML, Flash, etc. and enables a rich consumer experience for all ‘widgets’, whether security-based or not. The touchscreen thus provides service providers the ability to use web content creation and management tools to build and download any ‘widgets’ regardless of their functionality. 
     As discussed above, although the Security Applications have specific low-level functional requirements in order to interface with the premise security system, these applications make use of the same fundamental application facilities as any other ‘widget’, application facilities that include graphical layout, interactivity, application handoff, screen management, and network interfaces, to name a few. 
     Content management in the touchscreen provides the ability to leverage conventional web development tools, performance optimized for an embedded system, service provider control of accessible content, content reliability in a consumer device, and consistency between ‘widgets’ and seamless widget operational environment. In an embodiment of the integrated security system, widgets are created by web developers and hosted on the integrated security system Content Manager (and stored in the Content Store database). In this embodiment the server component caches the widgets and offers them to consumers through the web-based integrated security system provisioning system. The servers interact with the advanced touchscreen using HTTPS interfaces controlled by the core engine and dynamically download widgets and updates as needed to be cached on the touchscreen. In other embodiments widgets can be accessed directly over a network such as the Internet without needing to go through the iControl Content Manager 
     Referring to  FIG.  28   , the touchscreen system is built on a tiered architecture, with defined interfaces between the Application/Presentation Layer (the Application Engine) on the top, the Core Engine in the middle, and the security panel and gateway APIs at the lower level. The architecture is configured to provide maximum flexibility and ease of maintenance. 
     The application engine of the touchscreen provides the presentation and interactivity capabilities for all applications (widgets) that run on the touchscreen, including both core security function widgets and third party content widgets.  FIG.  29    is an example screenshot  800  of a networked security touchscreen, under an embodiment. This example screenshot  800  includes three interfaces or user interface (UI) components  802 - 806 , but is not so limited. A first UI  802  of the touchscreen includes icons by which a user controls or accesses functions and/or components of the security system (e.g., “Main”, “Panic”, “Medic”, “Fire”, state of the premise alarm system (e.g., disarmed, armed, etc.), etc.); the first UI  802 , which is also referred to herein as a security interface, is always presented on the touchscreen. A second UI  804  of the touchscreen includes icons by which a user selects or interacts with services and other network content (e.g., clock, calendar, weather, stocks, news, sports, photos, maps, music, etc.) that is accessible via the touchscreen. The second UI  804  is also referred to herein as a network interface or content interface. A third UI  806  of the touchscreen includes icons by which a user selects or interacts with additional services or componets (e.g., intercom control, security, cameras coupled to the system in particular regions (e.g., front door, baby, etc.) available via the touchscreen. 
     A component of the application engine is the Presentation Engine, which includes a set of libraries that implement the standards-based widget content (e.g., XML, HTML, JavaScript, Flash) layout and interactivity. This engine provides the widget with interfaces to dynamically load both graphics and application logic from third parties, support high level data description language as well as standard graphic formats. The set of web content-based functionality available to a widget developer is extended by specific touchscreen functions implemented as local web services by the Core Engine. 
     The resident application of the touchscreen is the master service that controls the interaction of all widgets in the system, and enforces the business and security rules required by the service provider. For example, the resident application determines the priority of widgets, thereby enabling a home security widget to override resource requests from a less critical widget (e.g. a weather widget). The resident application also monitors widget behavior, and responds to client or server requests for cache updates. 
     The core engine of the touchscreen manages interaction with other components of the integrated security system, and provides an interface through which the resident application and authorized widgets can get information about the home security system, set alarms, install sensors, etc. At the lower level, the Core Engine&#39;s main interactions are through the PanelConnect API, which handles all communication with the security panel, and the gateway Interface, which handles communication with the gateway. In an embodiment, both the iHub Interface and PanelConnect API are resident and operating on the touchscreen. In another embodiment, the PanelConnect API runs on the gateway or other device that provides security system interaction and is accessed by the touchscreen through a web services interface. 
     The Core Engine also handles application and service level persistent and cached memory functions, as well as the dynamic provisioning of content and widgets, including but not limited to: flash memory management, local widget and content caching, widget version management (download, cache flush new/old content versions), as well as the caching and synchronization of user preferences. As a portion of these services the Core engine incorporates the bootloader functionality that is responsible for maintaining a consistent software image on the touchscreen, and acts as the client agent for all software updates. The bootloader is configured to ensure full update redundancy so that unsuccessful downloads cannot corrupt the integrated security system. 
     Video management is provided as a set of web services by the Core Engine. Video management includes the retrieval and playback of local video feeds as well as remote control and management of cameras (all through iControl CameraConnect technology). 
     Both the high level application layer and the mid-level core engine of the touchscreen can make calls to the network. Any call to the network made by the application layer is automatically handed off to a local caching proxy, which determines whether the request should be handled locally. Many of the requests from the application layer are web services API requests, although such requests could be satisfied by the iControl servers, they are handled directly by the touchscreen and the gateway. Requests that get through the caching proxy are checked against a white list of acceptable sites, and, if they match, are sent off through the network interface to the gateway. Included in the Network Subsystem is a set of network services including HTTP, HTTPS, and server-level authentication functions to manage the secure client-server interface. Storage and management of certificates is incorporated as a part of the network services layer. 
     Server components of the integrated security system servers support interactive content services on the touchscreen. These server components include, but are not limited to the content manager, registry manager, network manager, and global registry, each of which is described herein. 
     The Content Manager oversees aspects of handling widget data and raw content on the touchscreen. Once created and validated by the service provider, widgets are ‘ingested’ to the Content Manager, and then become available as downloadable services through the integrated security system Content Management APIs. The Content manager maintains versions and timestamp information, and connects to the raw data contained in the backend Content Store database. When a widget is updated (or new content becomes available) all clients registering interest in a widget are systematically updated as needed (a process that can be configured at an account, locale, or system-wide level). 
     The Registry Manager handles user data, and provisioning accounts, including information about widgets the user has decided to install, and the user preferences for these widgets. 
     The Network Manager handles getting and setting state for all devices on the integrated security system network (e.g., sensors, panels, cameras, etc.). The Network manager synchronizes with the gateway, the advanced touchscreen, and the subscriber database. 
     The Global Registry is a primary starting point server for all client services, and is a logical referral service that abstracts specific server locations/addresses from clients (touchscreen, gateway  102 , desktop widgets, etc.). This approach enables easy scaling/migration of server farms. 
     The touchscreen of an embodiment operates wirelessly with a premise security system. The touchscreen of an embodiment incorporates an RF transceiver component that either communicates directly with the sensors and/or security panel over the panel&#39;s proprietary RF frequency, or the touchscreen communicates wirelessly to the gateway over 802.11, Ethernet, or other IP-based communications channel, as described in detail herein. In the latter case the gateway implements the PanelConnect interface and communicates directly to the security panel and/or sensors over wireless or wired networks as described in detail above. 
     The touchscreen of an embodiment is configured to operate with multiple security systems through the use of an abstracted security system interface. In this embodiment, the PanelConnect API can be configured to support a plurality of proprietary security system interfaces, either simultaneously or individually as described herein. In one embodiment of this approach, the touchscreen incorporates multiple physical interfaces to security panels (e.g. GE Security RS-485, Honeywell RF, etc.) in addition to the PanelConnect API implemented to support multiple security interfaces. The change needed to support this in PanelConnect is a configuration parameter specifying the panel type connection that is being utilized. 
     So for example, the setARMState( ) function is called with an additional parameter (e.g., Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”, Parameters=“ExitDelay=30|Lights=OFF”, panelType=“GE Concord4 RS485”)). The ‘panelType’ parameter is used by the setARMState function (and in practice by all of the PanelConnect functions) to select an algorithm appropriate to the specific panel out of a plurality of alogorithms. 
     The touchscreen of an embodiment is self-installable. Consequently, the touchscreen provides a ‘wizard’ approach similar to that used in traditional computer installations (e.g. InstallShield). The wizard can be resident on the touchscreen, accessible through a web interface, or both. In one embodiment of a touchscreen self-installation process, the service provider can associate devices (sensors, touchscreens, security panels, lighting controls, etc.) remotely using a web-based administrator interface. 
     The touchscreen of an embodiment includes a battery backup system for a security touchscreen. The touchscreen incorporates a standard Li-ion or other battery and charging circuitry to allow continued operation in the event of a power outage. In an embodiment the battery is physically located and connected within the touchscreen enclosure. In another embodiment the battery is located as a part of the power transformer, or in between the power transformer and the touchscreen. 
     The example configurations of the integrated security system described above with reference to  FIGS.  5  and  6    include a gateway that is a separate device, and the touchscreen couples to the gateway. However, in an alternative embodiment, the gateway device and its functionality can be incorporated into the touchscreen so that the device management module, which is now a component of or included in the touchscreen, is in charge of the discovery, installation and configuration of the IP devices coupled or connected to the system, as described above. The integrated security system with the integrated touchscreen/gateway uses the same “sandbox” network to discover and manage all IP devices coupled or connected as components of the system. 
     The touchscreen of this alternative embodiment integrates the components of the gateway with the components of the touchscreen as described herein. More specifically, the touchscreen of this alternative embodiment includes software or applications described above with reference to  FIG.  3   . In this alternative embodiment, the touchscreen includes the gateway application layer  302  as the main program that orchestrates the operations performed by the gateway. A Security Engine  304  of the touchscreen provides robust protection against intentional and unintentional intrusion into the integrated security system network from the outside world (both from inside the premises as well as from the WAN). The Security Engine  304  of an embodiment comprises one or more sub-modules or components that perform functions including, but not limited to, the following:
         Encryption including 128-bit SSL encryption for gateway and iConnect server communication to protect user data privacy and provide secure communication.   Bi-directional authentication between the touchscreen and iConnect server in order to prevent unauthorized spoofing and attacks. Data sent from the iConnect server to the gateway application (or vice versa) is digitally signed as an additional layer of security. Digital signing provides both authentication and validation that the data has not been altered in transit.   Camera SSL encapsulation because picture and video traffic offered by off-the-shelf networked IP cameras is not secure when traveling over the Internet. The touchscreen provides for 128-bit SSL encapsulation of the user picture and video data sent over the internet for complete user security and privacy.   802.11b/g/n with WPA-2 security to ensure that wireless camera communications always takes place using the strongest available protection.   A touchscreen-enabled device is assigned a unique activation key for activation with an iConnect server. This ensures that only valid gateway-enabled devices can be activated for use with the specific instance of iConnect server in use. Attempts to activate gateway-enabled devices by brute force are detected by the Security Engine. Partners deploying touchscreen-enabled devices have the knowledge that only a gateway with the correct serial number and activation key can be activated for use with an iConnect server. Stolen devices, devices attempting to masquerade as gateway-enabled devices, and malicious outsiders (or insiders as knowledgeable but nefarious customers) cannot effect other customers&#39; gateway-enabled devices.       

     As standards evolve, and new encryption and authentication methods are proven to be useful, and older mechanisms proven to be breakable, the security manager can be upgraded “over the air” to provide new and better security for communications between the iConnect server and the gateway application, and locally at the premises to remove any risk of eavesdropping on camera communications. 
     A Remote Firmware Download module  306  of the touchscreen allows for seamless and secure updates to the gateway firmware through the iControl Maintenance Application on the server  104 , providing a transparent, hassle-free mechanism for the service provider to deploy new features and bug fixes to the installed user base. The firmware download mechanism is tolerant of connection loss, power interruption and user interventions (both intentional and unintentional). Such robustness reduces down time and customer support issues. Touchscreen firmware can be remotely download either for one touchscreen at a time, a group of touchscreen, or in batches. 
     The Automations engine  308  of the touchscreen manages the user-defined rules of interaction between the different devices (e.g. when door opens turn on the light). Though the automation rules are programmed and reside at the portal/server level, they are cached at the gateway level in order to provide short latency between device triggers and actions. 
     DeviceConnect  310  of the touchscreen touchscreen includes definitions of all supported devices (e.g., cameras, security panels, sensors, etc.) using a standardized plug-in architecture. The DeviceConnect module  310  offers an interface that can be used to quickly add support for any new device as well as enabling interoperability between devices that use different technologies/protocols. For common device types, pre-defined sub-modules have been defined, making supporting new devices of these types even easier. SensorConnect  312  is provided for adding new sensors, CameraConnect  316  for adding IP cameras, and PanelConnect  314  for adding home security panels. 
     The Schedules engine  318  of the touchscreen is responsible for executing the user defined schedules (e.g., take a picture every five minutes; every day at 8 am set temperature to 65 degrees Fahrenheit, etc.). Though the schedules are programmed and reside at the iConnect server level they are sent to the scheduler within the gateway application of the touchscreen. The Schedules Engine  318  then interfaces with SensorConnect  312  to ensure that scheduled events occur at precisely the desired time. 
     The Device Management module  320  of the touchscreen is in charge of all discovery, installation and configuration of both wired and wireless IP devices (e.g., cameras, etc.) coupled or connected to the system. Networked IP devices, such as those used in the integrated security system, require user configuration of many IP and security parameters, and the device management module of an embodiment handles the details of this configuration. The device management module also manages the video routing module described below. 
     The video routing engine  322  of the touchscreen is responsible for delivering seamless video streams to the user with zero-configuration. Through a multi-step, staged approach the video routing engine uses a combination of UPnP port-forwarding, relay server routing and STUN/TURN peer-to-peer routing. The video routing engine is described in detail in the Related Applications. 
       FIG.  30    is a block diagram  900  of network or premise device integration with a premise network  250 , under an embodiment. In an embodiment, network devices  255 ,  256 ,  957  are coupled to the touchscreen  902  using a secure network connection such as SSL over an encrypted 802.11 link (utilizing for example WPA-2 security for the wireless encryption), and the touchscreen  902  coupled to the premise router/firewall  252  via a coupling with a premise LAN  250 . The premise router/firewall  252  is coupled to a broadband modem  251 , and the broadband modem  251  is coupled to a WAN  200  or other network outside the premise. The touchscreen  902  thus enables or forms a separate wireless network, or sub-network, that includes some number of devices and is coupled or connected to the LAN  250  of the host premises. The touchscreen sub-network can include, but is not limited to, any number of other devices like WiFi IP cameras, security panels (e.g., IP-enabled), and IP devices, to name a few. The touchscreen  902  manages or controls the sub-network separately from the LAN  250  and transfers data and information between components of the sub-network and the LAN  250 /WAN  200 , but is not so limited. Additionally, other network devices  254  can be coupled to the LAN  250  without being coupled to the touchscreen  902 . 
       FIG.  31    is a block diagram  1000  of network or premise device integration with a premise network  250 , under an alternative embodiment. The network or premise devices  255 ,  256 ,  1057  are coupled to the touchscreen  1002 , and the touchscreen  1002  is coupled or connected between the premise router/firewall  252  and the broadband modem  251 . The broadband modem  251  is coupled to a WAN  200  or other network outside the premise, while the premise router/firewall  252  is coupled to a premise LAN  250 . As a result of its location between the broadband modem  251  and the premise router/firewall  252 , the touchscreen  1002  can be configured or function as the premise router routing specified data between the outside network (e.g., WAN  200 ) and the premise router/firewall  252  of the LAN  250 . As described above, the touchscreen  1002  in this configuration enables or forms a separate wireless network, or sub-network, that includes the network or premise devices  255 ,  156 ,  1057  and is coupled or connected between the LAN  250  of the host premises and the WAN  200 . The touchscreen sub-network can include, but is not limited to, any number of network or premise devices  255 ,  256 ,  1057  like WiFi IP cameras, security panels (e.g., IP-enabled), and security touchscreens, to name a few. The touchscreen  1002  manages or controls the sub-network separately from the LAN  250  and transfers data and information between components of the sub-network and the LAN  250 /WAN  200 , but is not so limited. Additionally, other network devices  254  can be coupled to the LAN  250  without being coupled to the touchscreen  1002 . 
     The gateway of an embodiment, whether a stand-along component or integrated with a touchscreen, enables couplings or connections and thus the flow or integration of information between various components of the host premises and various types and/or combinations of IP devices, where the components of the host premises include a network (e.g., LAN) and/or a security system or subsystem to name a few. Consequently, the gateway controls the association between and the flow of information or data between the components of the host premises. For example, the gateway of an embodiment forms a sub-network coupled to another network (e.g., WAN, LAN, etc.), with the sub-network including IP devices. The gateway further enables the association of the IP devices of the sub-network with appropriate systems on the premises (e.g., security system, etc.). Therefore, for example, the gateway can form a sub-network of IP devices configured for security functions, and associate the sub-network only with the premises security system, thereby segregating the IP devices dedicated to security from other IP devices that may be coupled to another network on the premises. 
     The gateway of an embodiment, as described herein, enables couplings or connections and thus the flow of information between various components of the host premises and various types and/or combinations of IP devices, where the components of the host premises include a network, a security system or subsystem to name a few. Consequently, the gateway controls the association between and the flow of information or data between the components of the host premises. For example, the gateway of an embodiment forms a sub-network coupled to another network (e.g., WAN, LAN, etc.), with the sub-network including IP devices. The gateway further enables the association of the IP devices of the sub-network with appropriate systems on the premises (e.g., security system, etc.). Therefore, for example, the gateway can form a sub-network of IP devices configured for security functions, and associate the sub-network only with the premises security system, thereby segregating the IP devices dedicated to security from other IP devices that may be coupled to another network on the premises. 
     The system of an embodiment including the Cloud Hub and Virtual Gateway as described in detail herein includes one or more components of the “integrated cloud system (ICS)” described in detail herein. The system of an embodiment described herein incorporates one or more components of the “ICS”. The system of an embodiment described herein is coupled to one or more components of the “ICS”. The system of an embodiment described herein integrates with one or more components of the “ICS”. 
       FIG.  32    is a block diagram of the integrated cloud system or platform, under an embodiment. The integrated cloud system (ICS) of an embodiment comprises cloud-based components that include a Cloud Integration Service/Server (CIS) coupled to a system server (e.g., “Icontrol Server”, also referred to herein as the service provider server) via an internal event bus. The CIS, system server, and event bus are implemented by the service provider in data centers of the service provider&#39;s customers, but are not so limited. 
     The system server is coupled to customer-premises equipment (CPE) at corresponding subscriber premises of numerous subscribers. The CPE includes one or more of security panels, security systems, gateways, hubs, touchscreens, and Wi-Fi access points that operate as a gateway to the system servers and ICS. The CPE is described in detail in the Related Applications incorporated by reference herein. 
     The CIS is coupled to a partner&#39;s production server (“partner server”) via a Cloud Integration Adapter (CIA). The partner server interacts with their products/services that their users wish to integrate into their ICS platform. The Cloud Integration Adapter provides the system server and CIS with REST endpoints to call for checking the health of the adapter, associating with adapter cloud devices, and processing events coming from the CIS. Furthermore, the Cloud Integration Adapter is responsible for sending events to the CIS as acknowledgement of incoming system events, and as an endpoint for Adapter managed cloud device events to be reported into the system servers. 
     The ICS of an embodiment effects integration of cloud services and internet-connected devices with the user interface, Rules Engine and other components and functions of the service provider system. This integration enables third party and/or other connected devices (e.g., smart door bells (e.g, Doorbot, etc.), door locks, garage door operators (e.g., Chamberlain, etc.), cameras (e.g., Dropcam, etc.), thermostats (e.g., Nest, etc.), lighting systems (e.g., Philips Hue, etc.), lighting devices, lawn irrigation systems (e.g., Rachio, etc.), plant sensors, pet feeders, weather stations, rain sensors, pool controls, air quality sensors, music systems, remote controllers, internet user interfaces, connected systems, connected vehicles, etc.), and third party services (e.g weather forecasting services and applications (e.g., Accuweather, etc.), family networking services and applications, partner or third party services, Accuweather, MSO digital assets such as voicemail, etc.), to control or trigger automations in the service provider system using the user interface, Rules Engine and other components and functions of the service provider system. This enables end-users to integrate and use their previously-standalone internet-connected devices with each other as well as with their service provider-based service. 
     The ICS of an embodiment as described in detail herein includes one or more components of the “integrated security system” described in detail in the Related Applications, which are incorporated by reference herein. An example of the “integrated security system” is available as one or more of the numerous systems or platforms available from iControl Networks, Inc., Redwood City, Calif. The ICS of an embodiment incorporates one or more components of the “integrated security system”. The ICS of an embodiment is coupled to one or more components of the “integrated security system”. The ICS of an embodiment integrates with one or more components of the “integrated security system”. 
     The system server includes or hosts a partner proxy and an integration REST application programming interface (API). The integration REST API is coupled to the CIS. The partner proxy is coupled to a corresponding partner server, and is also coupled to a Card UI (“REST Client”). The partner proxy is configured to proxy API calls from the Partner&#39;s Card UI (REST client) to the Partner Server and appends the appropriate OAuth Token for a given user. This enables all client UIs to be enabled after a single OAuth pairing is completed (i.e., if one user authorizes Partner&#39;s product, all users and clients on the same account will have it auto-enabled and populated). This also improves security by not storing the user&#39;s credentials on the Partner&#39;s server in the client UI. The Card UI of an example embodiment is an HTML5-based user interface card developed by the Partner, or service provider, that is embedded into the service provider user interface (e.g., mobile app, web portal). 
     The ICS of an embodiment includes Cloud Actions and Triggers (CAT), which enable third party connected devices and services to trigger automations in the service provider system, thereby enabling end-users to integrate and use their previously-standalone internet connected devices with their service provider-based service. 
     Devices and services that are hosted outside of the automation platform or network are referred to as ‘cloud objects’ and provide numerous use cases when integrated with the system of an embodiment. The description that follows includes details of aspects of the system including but not limited to server infrastructure required to support external cloud objects, data format definitions for actions and triggers across the event bus, the process of onboarding external cloud objects, integration of cloud objects with the CPE rules engine, common OAuth2 Support for Cloud Services, and card UI/SDK Support for Cloud Objects. 
     The CAT of an embodiment integrates partner services into the ICS platform including support for rules on the CPE and partner-specific user interfaces based on the Card UI. The system of an embodiment includes a web API for the CIS for which partners develop Integration Adapters (also referred to as “adapters”) responsible for the translation of service provider events and operations into partner proprietary calls. Partners also develop Cards with the Card SDK in order to get branded partner specific user interfaces. The partners of an embodiment host their Integration Adapters in their environments, however in an alternative embodiment the adapters are hosed by the ICS described herein. 
     While the rules engine of an embodiment is included and running on CPE, the embodiments herein are not so limited. In an alternative embodiment the rules engine is included and running on a system server or other component of the ICS platform. 
     In another alternative embodiment the rules engine is distributed between the CPE and ICS platform so that a set of rules is included and running on the CPE while another set of rules is included and running on the ICS platform. For example, rules controlling actions and triggers limited to local devices in the premises, and not using any data or information from a device or service outside the premises, are included and running on the CPE. Likewise, rules controlling actions and triggers involving device(s) in the premises, and also involving device(s) or service(s) outside the premises, are included and running on the CPE. 
     The CAT includes but is not limited to use cases comprising Service Association, Cloud Object Creation, Service Disassociation, Cloud Object Synchronization, Card UI Interactions, Rule Authoring, and Rule Execution. Each of the use cases is described in detail herein. 
     Upon startup, the Partner&#39;s Cloud Integration Adapter uses username, password and partnerKey to authenticate with the CIS. The username, password and partnerKey are provided by the service provider. The Partner&#39;s Event Callback URL and Health Check URL are defined initially as part of the partner onboarding process. The CIS provides two URLs for the partner to optionally update the two URLs at runtime. 
     The Register Event callback URI allows partner to update the Event Callback URL at runtime.
         /cloudIntegration/[partnerName]/eventCallback/registerEventCallback?partner
 
Endpoint
   Url=[partnerUrl]
 
Descripti
   Update the eventCallback URL for a partner   on   Method POST
           x-login—username of the integration user   
           Header x-password—password of the integration user
           x-partnerKey—unique key issued by Service provider to the partner   
           URL partnerName: The unique name of the partner provided by Service provider paramete   rs partnerUrl: The updated Event Callback URL   Result HTTP response 200 if successful       

     An example payload includes but is not limited to the following: 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 curl -k -L -v -H “X-login: &lt;username&gt;” -H “X-password: test” -H “x-partnerKey: key” - 
               
               
                   
                 X POST 
               
               
                   
                 “https://&lt;server&gt;/cloudIntegration/icontrol/cloudIntegrations/rachio/eventCallback/regist 
               
               
                   
                 erEventCallback?partnerUrl=https://rachioAdapter/updatedEventCallbackUrl” 
               
               
                   
               
            
           
         
       
     
     The Register Health Check Callback URI allows partner to update the Health Check URL at runtime. 
     Endpo/cloudIntegration/[partnerName]/healthCheckCallback/registerHealthCheckCallb 
     
         
         
           
             int ack?partnerHealthCheckUrl=[partnerHealthCheckUrl]
 
Descri
 
             Update healthCheckCallback URL for partner
 
ption
 
Metho
 
             POST 
             d
           x-login—username of the integration userx-password—password of the   
         
             Heade
           integration userx-partnerKey—A unique key issued by Service provider to the   
         
             r
           partner   
         
             URL
           partnerName: The unique name of the partnerpartner   
         
             param
           HealthCheckUrl: The updated health check URL   
         
             eters 
             Result HTTP response 200 if successful 
           
         
       
    
     An example payload includes but is not limited to the following: 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 curl -k -L -v -H “Content-Type: text/xml ” -H “X-login: 
               
               
                   
                 &lt;username&gt;” -H “X-password: test” -H “x-partnerKey: key” -X POST 
               
               
                   
                 https://&lt;server&gt;/cloudIntegration/icontrol/cloudIntegrations/rachio/healthCheckCallback/ 
               
               
                   
                 registerHealthCheckCallback?partnerHealthCheckUrl=https://rachioAdapter/updatedHeal 
               
               
                   
                 thcheckcallback. 
               
               
                   
               
            
           
         
       
     
     For both the Event Callback Registration and Health Check Callback Registration, the CIS responds with a HTTP 200 if the POST is accepted. Appropriate HTTP error code will be returned for error conditions. 
     The Health Check Callback service implemented by the Partner supports HTTP GET operations, and responds with HTTP 200 to indicate all systems are functioning properly. Any other response will be considered an indication that the adapter is not available. The CIS of an embodiment periodically checks availability of the Integration Adapter, and the periodicity is configurable. 
     The cloud integration user lifecycle of an embodiment embodies the core user experiences from a technical viewpoint (i.e., technical use cases). The following user lifecycle use cases are described in detail herein: Service Association (User Onboarding); Updating new user product(s)/service(s) on the Partner&#39;s server; Product/Service status updates; Controlling user&#39;s product(s)/service(s) from the service provider platform; User Offboarding of one or more product(s)/service(s). 
     Service Association (User Onboarding) is initiated by the user via a service provider user interface when the user selects a Partner device type from the list of devices available to pair to the user&#39;s Service provider system.  FIG.  33    is a flow diagram for Service Association, under an embodiment. Service Association (Partner Onboarding) is initiated by a Card UI of an embodiment when the user selects a partner from a partner list. The list of all possible partners and their custom (partner specific) cards are built into each release of the Card UI (they are not dynamically downloaded from a server). However the list of enabled partners (and related metadata) is dynamically retrieved from Service provider server via an API. 
     Once the user selects a partner service for association, three-legged OAuth2 begins. A browser control is created, has its context populated with information identifying the user, and calls Service provider OAUTH Redirect servlet, which in turn opens the OAuth2 landing page URL with the required parameters (response_type, client_id and token). This page, served by the partner&#39;s web server, collects the user&#39;s ID and password and successfully authenticates. 
     After the user is authenticated, the partner server issues an HTTP 302 redirect to the Service provider OAuth Callback servlet located in the portal server and includes an authorization code as well as the rest of the original browser context. The OAuth Callback servlet contacts the partner&#39;s service to exchange the authorization code for an access token which it stores in the database. 
     Then, the OAuth Callback servlet will call the ‘Associate Account URL’ provided by the partner. The access token for the user account is attached to the request as the Authorization header to identify the user. The response to the call will include the user&#39;s account id in the partner system and a list of cloud devices owned by the user. After successful account association, HTTP 200 is returned to the browser indicating the completion of the service association process. 
     The service provider OAUTH callback URL has the following format, but is not so limited: https://&lt;servername&gt;/oauth/oauthPartner/&lt;partnerName&gt;. It is recommended that a service provider deployment registers this URL in the partner&#39;s system. As an alternate (less secure) option, this URL can be passed to the partner system as a parameter in the first leg of the OAUTH process. 
     The system of an embodiment includes Cloud Object Synchronization as described herein. After a service has been associated for a user/account, the system server has the list of cloud devices owned by the user. If the user adds/removes a device in the partner&#39;s system, partner server calls the Service provider Cloud Integration Service API to inform Service provider regarding the change. Conversely, if user removes a cloud device association in Service provider Card UI, an event will be sent to the partner&#39;s system via the ‘Event Callback URL’. 
     After completing user authentication, the OAuth token for the user account is attached to a request to associate the account (Associate Account in  FIG.  2   ). The Partner Server&#39;s response to the call will include the user&#39;s Account ID in the Partner&#39;s system and a list of cloud-enabled devices owned by the user in that account. After successful account association, HTTP 200 is returned to the browser indicating the completion of the service association process. After a service has been associated for a user/account, the Service provider server will have the list of cloud devices owned by the user. 
     Account association with the CIS is the process by which the system server creates the relationship between the Service provider user and partner cloud devices. The Cloud Integration Service sends, via HTTP POST, a JSON Object containing the OAuth Access Token. 
     An example Associate Account Request follows but the embodiment is not so limited: 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                 URL 
                 The ‘Associate Account URL’ provided  
               
               
                   
                 by the partner in the Cloud 
               
               
                   
                 Integration Submission Form. 
               
               
                 Description 
                 Get the user&#39;s account/device info from the partner. 
               
               
                 Method 
                 POST 
               
               
                 Header 
                 Authorization - ‘Bearer xxxxx’ where xxxxx  
               
               
                   
                 is the user&#39;s access token. 
               
               
                 URL 
                 customerName: The name of the Service provider server. 
               
               
                 parameters 
               
               
                   
               
            
           
         
       
     
     When an account association request is received by the Cloud Integration Adapter, it responds with a JSON message in the following format: 
                                                    Associate Account Response               {                “virtualDevice.siteId”:“acc_1234”,                “virtualDevice.instanceIds”:[                 {                  “id”:“device-inst001”,                  “name”:“Front Sprinkler”                 },                 {                  “id”:“device-inst002”,                  “name”:“Backyard Sprinkler”                 }                ]               }                        
Where:
 
     
       
         
           
               
               
               
             
               
                   
                   
               
               
                   
                 Field Name 
                 Description 
               
               
                   
                   
               
             
            
               
                   
                 virtualDevice.siteId  
                 The user ID in the Partner&#39;s  
               
               
                   
                   
                 system. This will be the global 
               
               
                   
                   
                 identifier used by Service provider  
               
               
                   
                   
                 to refer to the Partner&#39;s 
               
               
                   
                   
                 primary user. 
               
               
                   
                 virtualDevice.instanceIds 
                 A list (JSON Array) of devices  
               
               
                   
                   
                 the Partner or user wishes 
               
               
                   
                   
                 Service provider to interact with. 
               
               
                   
                 id 
                 The Device ID in the Partner&#39;s system. 
               
               
                   
                 name 
                 A friendly display name for this device. 
               
               
                   
                   
               
            
           
         
       
     
     A HTTP 200 is expected along with this data. Error codes should include an HTTP 500 for errors, and an HTTP 401 for improper OAuth token. 
     Updating status of partner product (events) involves user&#39;s interacting with the Partner&#39;s product/service through a Partner client (e.g., Partner mobile app) or the user may interact with the device locally and change its state, mode, or otherwise affect the product/service&#39;s status. Events received from the Partner&#39;s Cloud Integration Adapter can be treated as a trigger for a rule in the Service provider system (e.g., when the backyard sprinkler system is running, lock the pet door). 
     An example payload description follows but the embodiment is not so limited:
         Endp
           /cloudIntegration/[partnerName]/events/submitCloudEvent   
           oint   Descr
           Submit partner events to Service provider server.   
           iption   Meth
           POST   
           od
           x-login—username of the integration user.x-password—password of the   
           Heade
           integration user.x-partnerKey—A unique key issued by Service provider to the   
           r
           partner   
           URL
           partnerName: The unique name of the partner.externalAccountId: The user&#39;s   
           param
           account ID in the partner system.   
           eters   Events originated from the partner system in IcEvent(s) JSON format.Example:{“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”: “acc_1234”},{“name”:“virtualDevice.instanceId”,“value”:“rachio-inst001 “},{” name”:“virtualDevice.providerId”,“value”:“rachio”}],“mediaType”:“s prinkler/on”,“ts”:1409675025053,“value”:“true”}]}   Fields:
           mediaType: The event mediaTypes defined as part of the cloud object   
           Body definition and approved by Service provider.
           ts: The time when the event happened (in milliseconds).   
           Event metadata:
           virtualDevice.providerId: The name of the partner. Also referred to as Integration ID in the Card SDK.   virtualDevice.siteId: The user&#39;s account ID in the partner system.   virtualDevice.instanceId: The device ID in the partner system.
 
Result HTTP response 200 if successful.
   
               

     In controlling a partner product via the rules engine (actions) of an embodiment, the CIS uses the partner&#39;s Event Callback URL to submit action events to partner&#39;s system. Typically, an action event asks to the partner&#39;s system to perform a specific function. The partner submits the result of the action back to Service provider in the form of an event. 
     Payload Description 
     UR 
     
         
         
           
             The Event Callback URL for the partner
 
L
 
Des
 
crip Submit action events to partner server.
 
tion
 
Met
 
             POST
 
hod
 
             Authorization—The value is ‘Bearer xxxxxx’ with xxxxxx being the user&#39;s OAUTH
 
Hea
 
             access token.externalAccountId: The user&#39;s account ID in the partner system (to be
 
der
 
             added on Padre release).
 
UR
 
             L
 
par
 
             None.
 
am
 
eter
 
             s 
             Action events originated from the Service provider system in IcEvent JSON format. 
             Example event sent to Rachio: 
             {“icEvent”:[{“ts”:1409675025053,“instanceId”:“181964.0”,“mediaType”:“virtualDe vice/pending”,“id”:“1430834677258”,“instanceName”:“Bedroom”,“value”: null,“cont ext”:[ ],“metaData”:“name”:“virtualDevice.instanceId”,“value”:“rachio-inst001”},{“name”:“virtualDevice.siteId”,“value”:“acc_1234”},{“name”:“virtualDev ice.providerId”,“value”:“rachio”},{“name”:“functionMediaType”,“value”:“sprinkler/schedulePause”},{“requestMessageId”},{“value”:“1430489036”}]}]} 
             Fields:
           id: The event ID generated by Service provider server.   mediaType: All action events have ‘virtualDevice/pending’ as the event media type. The actual action is represented as ‘sprinkler/schedulePause’ in   
         
             Bo
           metadata.   
         
             dy
           ts: The time when the event happened (in milliseconds).   instanceId: The ID of the device in Service provider system.   
         
             Event metadata:
           virtualDevice.providerId: The name of the partner. Also referred to as Integration ID in the Card SDK.   virtualDevice.siteId: The user&#39;s account ID in the partner system.   virtualDevice.instanceId: The device ID in the partner system.   functionMediaType: Identifies the action called by Service provider. The list of all possible function media types are defined at the time of partner onboarding.   requestMessageId: The ID of the action request. Partner should used the this ID when sending success/failure response.   
         
             Upon receiving the action event, partner should send success/failure response as event to Service provider server. 
             Successful response:
           {“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”:“acc_1234” },{“na   
         
             Act
           me”:“virtualDevice.instanceId”,“value”:“rachio-   
         
             ion
           inst001”},{“name”:“virtualDevice.providerId”,“value”:“rachio”},{“name”:“request   
         
             Eve
           MessageId”,“value”:“1430489036”}],“mediaType”:“virtualDevice/success”,“ts”:140   
         
             nt
           9675025053,“value”:“true”}]}   
         
             Res 
             pon
           Failure Response:   
         
             se
           {“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”:“acc_1234”},{“na me”:“virtualDevice.instanceId”,“value”:“rachio-inst001”},{“name”:“virtualDevice.providerId”,“value”:“rachio”},{“name”:“request MessageId”,“value”:“1430489036”}],“mediaType”:“virtualDevice/failed”,“ts”:14096 75025053,“errorCode”:“500”,“value”:“true”}]}   
         
           
         
       
    
     Event disposition is determined by the functionMediaType in the metaData array. In the above example, the functionMediaType has the value of device/schedulePause, but depending on the function, there may be a parameter or value in order to effect the desired control. 
       FIG.  34    is a flow diagram for Service Disassociation, under an embodiment. If the user adds/removes a device in the Partner&#39;s system, the Partner Server calls the CIS API to inform Service provider about the change. A Cloud Service can be disassociated from an Service provider user through an API invocation on the Service provider server. This removes the cloud account and its associated Cloud devices from the Service provider server. A SMAP message is sent to the CPE to update its Cloud Object inventory, and the CIS calls the partner&#39;s ‘Event Callback URL’ to inform the Partner that the user has disassociated. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 Payload Description 
               
               
                   
                  URL   The Event Callback URL for the partner 
               
               
                   
                       Notify Partner Server that a user has “deleted” or removed one of their 
               
               
                   
                 Description 
               
               
                   
                       partner products from being controlled by the Service provider system. 
               
               
                   
                  Method  POST 
               
               
                   
                   URL 
               
               
                   
                       None 
               
               
                   
                 Parameters 
               
               
                   
                       { 
               
               
                   
                        “icEvent”:[ 
               
               
                   
                         { 
               
               
                   
                          “metaData”:[ 
               
               
                   
                           { 
               
               
                   
                            “name”:“virtualDevice.siteId”, 
               
               
                   
                            “value”:“rachio-account-id-0001”, 
               
               
                   
                           }, 
               
               
                   
                           { 
               
               
                   
                            “name”:“virtualDevice.instanceId”, 
               
               
                   
                            “value”:“rachio-userinst-0001”, 
               
               
                   
                           }, 
               
               
                   
                           { 
               
               
                   
                 Body         “name”:“virtualDevice.providerId”, 
               
               
                   
                            “value”:“rachio”, 
               
               
                   
                           }, 
               
               
                   
                          ], 
               
               
                   
                          “id”:“1409865500000”, 
               
               
                   
                          “mediaType”:“virtualDevice/remove”, 
               
               
                   
                          “ts”:1409865500000, 
               
               
                   
                          “href”:“sites/1/network/instances/181002.0”, 
               
               
                   
                          “siteId”:“1”, 
               
               
                   
                          “deviceId”:“1002”, 
               
               
                   
                          “instanceId”:“181002.0”, 
               
               
                   
                         } 
               
               
                   
                        ] 
               
               
                   
                       } 
               
               
                   
               
            
           
         
       
     
     Event metadata includes but is not limited to: virtualDevice.providerId (e.g., name of the partner, also referred to as Integration ID in the Card SDK); virtualDevice.siteId (e.g., user&#39;s account ID in the partner system); virtualDevice.instanceId (e.g., device ID in the partner system). Fields include but are not limited to: mediaType (e.g., all remove events will have a mediaType of ‘virtualDevice/remove’); is (e.g., time when the event happened (in milliseconds)); instanceId (e.g., ID of the device in Service provider system); id (e.g., event ID generated by Service provider server). 
       FIG.  35    is a flow diagram for Card UI Interactions, under an embodiment. The Card UIs that interact with the Cloud Objects will not depend on data stored in Service provider servers. Instead the cards will interact through the Partner Proxy Service, which handles authentication and logging, to make calls to the partner server. For example, a Nest card that needs to show a list of thermostats will get the list of thermostats and their metadata indirectly from Nest (through the Partner Proxy Service) instead of leveraging the Cloud Object data stored in our database. This is done primarily due to the desire to have the Card UI authors, which are expected to be the partners themselves, use their own APIs for easier development. Note that it does provide the possibility for the two data sets (the Cloud Objects in our database and the list of devices provided by the partner&#39;s server) to get out of sync if bugs exist in the integrations. Normally changes should be synchronized as described above in Cloud Object Synchronization and the two data sets should be equivalent. 
     Cards will be oblivious to authentication with the Partner Server (except for service association where the authentication data is stored in our server). Invocations to the Partner Proxy Service cause it to attempt a ‘pass-through’ invocation on the Partner Server using the authentication credentials stored in the database. If the Partner Server responds with a  401  authentication failure, the Partner Proxy Service will attempt to refresh the token and re-attempt the invocation to the Partner Server with the updated token as shown in the diagram above. Authentication credentials are not made available to the Cards, so they perform authenticated requests through the Partner Proxy Service. 
     The system of an embodiment includes files that form the Cloud Integration Metadata. As an example, an embodiment includes Cloud Integration Descriptor (CID) and Rules Template files that make up the Cloud Integration Metadata that defines a cloud integration. 
     The CID describes the capabilities of the devices and/or services provided by the Partner Provider Plugin including attributes, actions, events, and their associated parameters. This descriptor is used by the server to provide REST API access to the capabilities provided by the cloud service, but is not so limited. 
     An example CID XSD of an embodiment is as follows, but the embodiment is not so limited. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 CID XSD 
               
               
                   
                  &lt;xs:complexType name=“cloudObject”&gt; 
               
               
                   
                   &lt;xs:complexContent&gt; 
               
               
                   
                    &lt;xs:sequence&gt; 
               
               
                   
                     &lt;xs:element name=“name” type=“xs:token”/&gt; 
               
               
                   
                     &lt;xs:element name=“metaData” type=“metaData” minOccurs=“0” 
               
               
                   
                 maxOccurs=“64”/&gt; 
               
               
                   
                     &lt;xs:element name=“point” type=“point” minOccurs=“0” maxOccurs=“64”/&gt; 
               
               
                   
                     &lt;xs:element name=“function” type=“function” minOccurs=“0” 
               
               
                   
                 maxOccurs=“64”/&gt; 
               
               
                   
                    &lt;/xs:sequence&gt; 
               
               
                   
                    &lt;xs:attribute name=“id” type=“xs:string” use=“required”/&gt; 
               
               
                   
                    &lt;xs:attribute name=“mediaType” type=“xs:token” use=“optional”/&gt; 
               
               
                   
                    &lt;xs:attribute name=“href” type=“xs:anyURI”/&gt; 
               
               
                   
                    &lt;xs:attribute name=“tags” type=“xs:token”/&gt; 
               
               
                   
                    &lt;xs:attribute name=“status” type=“cloudObjectStatus”/&gt; 
               
               
                   
                   &lt;/xs:complexContent&gt; 
               
               
                   
                  &lt;/xs:complexType&gt; 
               
               
                   
                  &lt;xs:complexType name=“metaData”&gt; 
               
               
                   
                   &lt;xs:attribute name=“name” type=“xs:string”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“value” type=“xs:string”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“mediaType” type=“xs:token”/&gt; 
               
               
                   
                  &lt;/xs:complexType&gt; 
               
               
                   
                  &lt;xs:complexType name=“point”&gt; 
               
               
                   
                   &lt;xs:attribute name=“mediaType” type=“xs:token” use=“required”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“name” type=“xs:string”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“href” type=“xs:anyURI”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“value” type=“xs:string”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“ts” type=“xsiong”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“readOnly” type=“xs:boolean” use=“required”/&gt; 
               
               
                   
                  &lt;/xs:complexType&gt; 
               
               
                   
                  &lt;xs:complexType name=“function”&gt; 
               
               
                   
                   &lt;xs:sequence&gt; 
               
               
                   
                    &lt;xs:element name=“input” type=“input” minOccurs=“0” 
               
               
                   
                 maxOccurs=“unbounded”/&gt; 
               
               
                   
                   &lt;/xs:sequence&gt; 
               
               
                   
                   &lt;xs:attribute name=“mediaType” type=“xs:token” use=“required”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“name” type=“xs:token”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“href” type=“xs:anyURI”/&gt; 
               
               
                   
                   &lt;xs:attribute name=“description” type=“xs:string”/&gt; 
               
               
                   
                  &lt;/xs:complexType&gt; 
               
               
                   
                  &lt;xs:simpleType name=“cloudObjectStatus”&gt; 
               
               
                   
                   &lt;xs:restriction base=“xs:token”&gt; 
               
               
                   
                    &lt;xs:enumeration value=“ok”/&gt; 
               
               
                   
                    &lt;xs:enumeration value=“offline”/&gt; 
               
               
                   
                    &lt;xs:enumeration value=“unknown”/&gt; 
               
               
                   
                    &lt;xs:enumeration value=“missing”/&gt; 
               
               
                   
                    &lt;xs:enumeration value=“searching”/&gt; 
               
               
                   
                    &lt;xs:enumeration value=“configuration_failure”/&gt; 
               
               
                   
                    &lt;xs:enumeration value=“upgrading”/&gt; 
               
               
                   
                    &lt;xs:enumeration value=“configuring”/&gt; 
               
               
                   
                   &lt;/xs:restriction&gt; 
               
               
                   
                  &lt;/xs:simpleType&gt; 
               
               
                   
               
            
           
         
       
     
     An example CID of an embodiment is as follows, but the embodiment is not so limited. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 Example CID 
               
               
                   
                 &lt;Nest id=“Nest343234345” mediaType=“cloud/nest” tags=“thermostat” status=“ok”&gt; 
               
               
                   
                  &lt;name&gt;My Nest&lt;/name&gt; 
               
               
                   
                  &lt;metadata name=“manufacturer” mediaType=“cloud/nest/manufacturer” 
               
               
                   
                 value=“Nest”/&gt; 
               
               
                   
                  &lt;metadata name=“model” mediaType=“cloud/nest/model” value=“M1”/&gt; 
               
               
                   
                  &lt;point name=“temperature” mediaType=“cloud/nest/temperature” value=“2800” 
               
               
                   
                 ts=“23434535464557” readOnly=“false”/&gt; 
               
               
                   
                  &lt;point name=“coolSetpoint” mediaType=“cloud/nest/coolSetpoint” value=“2400” 
               
               
                   
                 ts=“23434535464557” readOnly=“false”/&gt; 
               
               
                   
                  &lt;point name=“heatSetpoint” mediaType=“cloud/nest/heatSetpoint” value=“2000” 
               
               
                   
                 ts=“23434535464557” readOnly=“false”/&gt; 
               
               
                   
                  &lt;function name=“resetSetpoints” mediaType=“cloud/nest/reset” description=“reset 
               
               
                   
                 heat/cool setpoint to factory default”/&gt; 
               
               
                   
                 &lt;/Nest&gt; 
               
               
                   
               
            
           
         
       
     
     An example Rules XSD Changes of an embodiment is as follows, but the embodiment is not so limited. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 Rules XSD Changes 
               
               
                   
                  &lt;!-- 
               
               
                   
                   - Subclass of trigger for Cloud commands. 
               
               
                   
                   --&gt; 
               
               
                   
                  &lt;xsd:complexType name=“cloudTrigger”&gt; 
               
               
                   
                   &lt;xsd:complexContent&gt; 
               
               
                   
                    &lt;xsd:extension base=“trigger”&gt; 
               
               
                   
                     &lt;xsd:sequence&gt; 
               
               
                   
                      &lt;!-- - The specific cloud object ID. --&gt; 
               
               
                   
                      &lt;xsd:element name=“cloudObjectID” type=“xsd:string” minOccurs=“1” 
               
               
                   
                 maxOccurs=“1”/&gt; 
               
               
                   
                      &lt;!-- the evaluation mechanism to apply to this trigger --&gt; 
               
               
                   
                      &lt;xsd:choice&gt; 
               
               
                   
                       &lt;xsd:element name=“simpleEval” 
               
               
                   
                 type=“cloudSimpleTriggerEvaluation”/&gt; 
               
               
                   
                       &lt;xsd:element name=“comparisonEval” 
               
               
                   
                 type=“cloudComparisonTriggerEvaluation”/&gt; 
               
               
                   
                      &lt;/xsd:choice&gt; 
               
               
                   
                     &lt;/xsd:sequence&gt; 
               
               
                   
                    &lt;/xsd:extension&gt; 
               
               
                   
                   &lt;/xsd:complexContent&gt; 
               
               
                   
                  &lt;/xsd:complexType&gt; 
               
               
                   
                  &lt;xsd:element name=“cloudTrigger” type=“cloudTrigger” 
               
               
                   
                 substitutionGroup=“trigger”/&gt; 
               
               
                   
                  &lt;!-- simple cloud trigger evaluation (just an event, no args) --&gt; 
               
               
                   
                  &lt;xsd:complexType name=“cloudSimpleTriggerEvaluation”&gt; 
               
               
                   
                   &lt;xsd:sequence&gt; 
               
               
                   
                    &lt;xsd:element name=“eventName” type=“xsd:string”/&gt; 
               
               
                   
                   &lt;/xsd:sequence&gt; 
               
               
                   
                  &lt;/xsd:complexType&gt; 
               
               
                   
                  &lt;!-- cloud trigger evaluation that compares a value --&gt; 
               
               
                   
                  &lt;xsd:complexType name=“cloudComparisonTriggerEvaluation”&gt; 
               
               
                   
                   &lt;xsd:sequence&gt; 
               
               
                   
                    &lt;xsd:element name=“attributeName” type=“xsd:string”/&gt; 
               
               
                   
                    &lt;xsd:element name=“comparisonMethod” type=“comparisonMethodEnum”/&gt; 
               
               
                   
                    &lt;xsd:element name=“comparisonValue” type=“xsd:double”/&gt; 
               
               
                   
                   &lt;/xsd:sequence&gt; 
               
               
                   
                  &lt;/xsd:complexType&gt; 
               
               
                   
                  &lt;!-- comparison methods --&gt; 
               
               
                   
                  &lt;xsd:simpleType name=“comparisonMethodEnum”&gt; 
               
               
                   
                   &lt;xsd:restriction base=“xsd:string”&gt; 
               
               
                   
                    &lt;!-- equality --&gt; 
               
               
                   
                    &lt;xsd:enumeration value=“eq”/&gt; 
               
               
                   
                    &lt;!-- less than --&gt; 
               
               
                   
                    &lt;xsd:enumeration value=“lt”/&gt; 
               
               
                   
                    &lt;!-- less than or equal --&gt; 
               
               
                   
                    &lt;xsd:enumeration value=“le”/&gt; 
               
               
                   
                    &lt;!-- greater than--&gt; 
               
               
                   
                    &lt;xsd:enumeration value=“gt”/&gt; 
               
               
                   
                    &lt;!-- greater than or equal --&gt; 
               
               
                   
                    &lt;xsd:enumeration value=“ge”/&gt; 
               
               
                   
                   &lt;/xsd:restriction&gt; 
               
               
                   
                  &lt;/xsd:simpleType&gt; 
               
               
                   
               
            
           
         
       
     
     An example Master Action List Changes of an embodiment is as follows, but the embodiment is not so limited. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 Master Action List Changes 
               
               
                   
                  &lt;a:action actionID=“137”&gt; 
               
               
                   
                   &lt;a:description&gt;Invoke a Cloud Action&lt;/a:description&gt; 
               
               
                   
                   &lt;a:parameterDef&gt; 
               
               
                   
                    &lt;a:key&gt;cloudObjectID&lt;/a:key&gt; 
               
               
                   
                    &lt;a:type&gt;string&lt;/a:type&gt; 
               
               
                   
                   &lt;/a:parameterDef&gt; 
               
               
                   
                   &lt;a:parameterDef&gt; 
               
               
                   
                    &lt;a:key&gt;cloudActionID&lt;/a:key&gt; 
               
               
                   
                    &lt;a:type&gt;string&lt;/a:type&gt; 
               
               
                   
                   &lt;/a:parameterDef&gt; 
               
               
                   
                   &lt;a:parameterDef&gt; 
               
               
                   
                    &lt;a:key&gt;parameters&lt;/a:key&gt; 
               
               
                   
                    &lt;a:type&gt;string&lt;/a:type&gt; &lt;!-- a JSONArray of  
               
               
                   
                    JSONObjects that contain 
               
               
                   
                 name/value/type triplets (type is optional) --&gt; 
               
               
                   
                   &lt;/a:parameterDef&gt; 
               
               
                   
                   &lt;!-- does this type make sense? --&gt; 
               
               
                   
                   &lt;a:type&gt;workflow&lt;/a:type&gt; 
               
               
                   
                   &lt;a:target&gt;ruleAction_invokeCloud&lt;/a:target&gt; 
               
               
                   
                  &lt;/a:action&gt; 
               
               
                   
               
            
           
         
       
     
     An example Rule XML Examples of an embodiment is as follows, but the embodiment is not so limited. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 Rule XML Examples 
               
               
                   
                 &lt;rule ruleID=“1002351”&gt; 
               
               
                   
                  &lt;triggerList&gt; 
               
               
                   
                   &lt;cloudTrigger&gt; 
               
               
                   
                    &lt;description&gt;Cloud Trigger&lt;/description&gt; 
               
               
                   
                    &lt;category&gt;cloud&lt;/category&gt; 
               
               
                   
                    &lt;!-- just points to the global service, not to any particular instance --&gt; 
               
               
                   
                    &lt;cloudObjectID&gt;AccuWeather&lt;/cloudObjectID&gt; 
               
               
                   
                    &lt;!-- it is assumed here that when the AccuWeather account is connected 
               
               
                   
                     that it is already filtering based on the user&#39;s location / zipcode --&gt; 
               
               
                   
                    &lt;simpleEval&gt; 
               
               
                   
                     &lt;eventName&gt;tornadoWarning&lt;/eventName&gt; 
               
               
                   
                    &lt;/simpleEval&gt; 
               
               
                   
                   &lt;/cloudTrigger&gt; 
               
               
                   
                  &lt;/triggerList&gt; 
               
               
                   
                  &lt;action&gt; 
               
               
                   
                   &lt;actionID&gt;70&lt;/actionID&gt; 
               
               
                   
                   &lt;parameter&gt; 
               
               
                   
                    &lt;key&gt;lightID&lt;/key&gt; 
               
               
                   
                    &lt;value&gt;3781220513309696&lt;/value&gt; 
               
               
                   
                   &lt;/parameter&gt; 
               
               
                   
                   &lt;parameter&gt; 
               
               
                   
                    &lt;key&gt;level&lt;/key&gt; 
               
               
                   
                    &lt;value&gt;100&lt;/value&gt; 
               
               
                   
                   &lt;/parameter&gt; 
               
               
                   
                  &lt;/action&gt; 
               
               
                   
                  &lt;description&gt;Turn on kitchen light when Tornado Warning&lt;/description&gt; 
               
               
                   
                 &lt;/rule&gt; 
               
               
                   
                 &lt;rule ruleID=“1008603”&gt; 
               
               
                   
                  &lt;triggerList&gt; 
               
               
                   
                   &lt;zoneTrigger&gt; 
               
               
                   
                    &lt;description&gt;Zone Trigger&lt;/description&gt; 
               
               
                   
                    &lt;category&gt;sensor&lt;/category&gt; 
               
               
                   
                    &lt;zoneState&gt;open&lt;/zoneState&gt; 
               
               
                   
                    &lt;zoneID&gt;18&lt;/zoneID&gt; 
               
               
                   
                   &lt;/zoneTrigger&gt; 
               
               
                   
                  &lt;/triggerList&gt; 
               
               
                   
                  &lt;action&gt; 
               
               
                   
                   &lt;actionID&gt;137&lt;/actionID&gt; 
               
               
                   
                   &lt;parameter&gt; 
               
               
                   
                    &lt;key&gt;cloudObjectID&lt;/key&gt; 
               
               
                   
                    &lt;value&gt;nest.1&lt;/value&gt; &lt;!-- device 1 under the nest service associated with this 
               
               
                   
                 account --&gt; 
               
               
                   
                   &lt;/parameter&gt; 
               
               
                   
                   &lt;parameter&gt; 
               
               
                   
                    &lt;key&gt;cloudActionID&lt;/key&gt; 
               
               
                   
                    &lt;value&gt;configureThermostat&lt;/value&gt; 
               
               
                   
                   &lt;/parameter&gt; 
               
               
                   
                   &lt;parameter&gt; 
               
               
                   
                    &lt;key&gt;parameters&lt;/key&gt; 
               
               
                   
                    &lt;value&gt;[ { “name”: “heatSetPoint”, “value”: “2200”, “type”: “nest/temperature” 
               
               
                   
                 }, { “name”: “coolSetPoint”, “value”: “2700” } ] &lt;/value&gt; 
               
               
                   
                   &lt;/parameter&gt; 
               
               
                   
                  &lt;/action&gt; 
               
               
                   
                  &lt;description&gt;Zone 1 Open Configure Nest Thermostat&lt;/description&gt; 
               
               
                   
                 &lt;/rule&gt; 
               
               
                   
               
            
           
         
       
     
     In order to provide a dynamic list of available actions and triggers during rule authoring, templates describing the available functionality must be provided with the Cloud Integration Metadata. Some examples of trigger and action templates (e.g., Rachio Smart Sprinkler Controller trigger and action template, AccuWeather weather service trigger template, etc.) of an embodiment are as follows, but the embodiment is not so limited. 
                                        Example Rule Templates           &lt;rules-core:triggerTemplates               xmlns:rules-core=“rules-core”           xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”               xsi:schemaLocation=“rules-core ../../../../rules-core/src/main/resources/rules-           core.xsd”&gt;               &lt;rules-core:triggerTemplate id=“203”               description=“{STR.RULES.TEMPLATES.TRIGGER.DESC.INSTANCE.RAC           HIO}”                   cvTriggerType=“cloudTrigger” cvCategory=“cloud”               excludeActionIds=“10:11:15:16:17:18:100:101:103:120:121:122:135:136:137:           138:139”&gt;                   &lt;rules-core:inputs&gt;                       &lt;rules-core:input hidden=“false”               description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.DES           C.RACHIO}”                           name=“targetValues” pattern=“eq”&gt;                           &lt;option               description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPT           ION.DESC.RACHIO.ON}”                               value=“1” /&gt;                           &lt;option               description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPT           ION.DESC.RACHIO.OFF}”                               value=“0” /&gt;                       &lt;/rules-core:input&gt;                       &lt;rules-core:input hidden=“true” name=“type” value=“event”           /&gt;                       &lt;rules-core:input hidden=“false” name=“instanceIds” /&gt;                       &lt;rules-core:input hidden=“true” name=“tags” value=“rachio”           /&gt;                       &lt;rules-core:input hidden=“true” name=“mediaTypes”                           value=“sprinkler/on” /&gt;                   &lt;/rules-core:inputs&gt;               &lt;/rules-core:triggerTemplate&gt;           &lt;/rules-core:triggerTemplates&gt;           &lt;rules-core:triggerTemplates               xmlns:rules-core=“rules-core”           xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”               xsi:schemaLocation=“rules-core ../../../../rules-core/src/main/resources/rules-           core.xsd”&gt;               &lt;rules-core:triggerTemplate id=“200”               description=“{STR.RULES.TEMPLATES.TRIGGER.DESC.INSTANCE.ACC           UWEATHER}”                   cvTriggerType=“cloudTrigger” cvCategory=“cloud”           excludeActionIds=“10:11:15:16:17:18:135:136”&gt;                   &lt;rules-core:inputs&gt;                       &lt;rules-core:input hidden=“false”               description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.DES           C.ACCUWEATHER}”                           name=“targetValues” pattern=“gt”&gt;                           &lt;option               description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPT           ION.DESC.ACCUWEATHER.TEMPERATURE.GT}”                               value=“temperatureGt” /&gt;                       &lt;/rules-core:input&gt;                       &lt;rules-core:input hidden=“true” name=“type“value=“event”           /&gt;                       &lt;rules-core:input hidden=“false” name=“instanceIds” /&gt;                       &lt;rules-core:input hidden=“true” name=“tags”           value=“accuWeather” /&gt;                       &lt;rules-core:input hidden=“true” name=“mediaTypes”                           value=“weather/temperature” /&gt;                   &lt;/rules-core:inputs&gt;               &lt;/rules-core:triggerTemplate&gt;           &lt;/rules-core:triggerTemplates&gt;           &lt;rules-core:actionTemplates xmlns:rules-core=“rules-core”               xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”               xsi:schemaLocation=“rules-core ../../../../rules-core/src/main/resources/rules-           core.xsd”&gt;               &lt;rules-core:actionTemplate id=“137”               description=“{STR.RULES.TEMPLATES.ACTION.DESC.RACHIO.OFF}”           cvActionId=“137”                   cvType=“workflow”&gt;                   &lt;rules-core:inputs&gt;                       &lt;rules-core:input hidden=“false” description=“Which Rachio           Object”                           name=“instanceIds” cvKey=“cloudObjectID”           cvType=“cloudObjectID”                           cvRequired=“true“/&gt;                       &lt;rules-core:input name=“mediaType”           value=“sprinkler/scheduleStop” /&gt;                   &lt;/rules-core:inputs&gt;               &lt;/rules-core:actionTemplate&gt;           &lt;/rules-core:actionTemplates&gt;                    
Sample curl commands of Rachio cloud rule follows.
 
curl -k -v -L -H “Content-Type:application/json”-H “X-login:insight”-H “X-password:test”-H “X-AppKey: defaultKey”-X PUT
 
“https://10.0.12.102/rest/icontrol/sites/420/rules”-d ‘{“description”:“Rachio turns ON,
 
Turn on
 
Light”,“executionSource”:“client”,“enabled”:true,“valid”:true,“default”:false,“conditional s”:{“conditional”:[{“triggers”:{“trigger”:[{“description”:“Rachio is
 
ON”,“id”:“0”,“templateId”:“203”,“targetValues”:“1”,“type”:“event”,“mediaTypes”:“sprin kler/systemOn”,“instances”:“181002.0”,“targetComparisonTypes”:“eq”}]},“actions”:{“ac tion”:[{“id”:“0”,“templateId”:“70”,“inputs”:“level=0&amp;”,“instanceIds”:“13000d6f00020a5 d9a.1.0”}]}}]}}’
 
User should pass targetComparisonTypes whenever there is a pattern present in cloudTrigger. In above case targetComparisonTypes is “eq” and targetValues is “1”.
 
Both these values should be fetched from the triggerTemplate.
 
Sample curl commands of AccuWeather cloud rule follows.
 
curl-k -v -L -H “Content-Type:application/json”-H “X-login:insight”-H “X-password:test”-H “X-AppKey: defaultKey”-X PUT
 
“https://10.0.12.102/rest/icontrol/sites/420/rules”-d ‘{“description”:“Outside temperature is less than 100, Turn on
 
light”,“executionSource”:“client”,“enabled”:true,“valid”:true,“default”:false,“conditionals”:{“conditional”:[{“triggers”:{“trigger”:[{“description”:“Outside temperature is greater than 60 degrees, turn on
 
light”,“id”:“0”,“templateId”:“200”,“targetValues”:“70”,“type”:“event”,“mediaTypes”:“we ather/temperature”,“instances”:“181001.0”,“targetComparisonTypes”:“gt”}]},“actions”:{“action”:[{“id”:“0”,“templateId”:“70”,“inputs”:“level=0&amp;”,“instanceIds”:“13000d6f00020a 5d9a.1.0”}]}}]}}’
 
In above case targetComparisonTypes is “gt” and targetValues is “70”. Here targetComparisonTypes should be fetched from triggerTemplate and user should pass user defined value in targetValues.
 
SMAP Protocol Changes
 
     SMAP is updated to allow server to send external events to CPE and CPE send external action event to server. 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 &lt;xsd:complexType name=“cloudEvent”&gt; 
               
               
                   
                   &lt;xsd:complexContent&gt; 
               
               
                   
                    &lt;xsd:extension base=“smap:baseMessage”&gt; 
               
               
                   
                     &lt;xsd:sequence&gt; 
               
               
                   
                      &lt;xsd:element name=“metaData” type=“smap:eventMetaData” 
               
               
                   
                 maxOccurs=“32” minOccurs=“0”&gt; 
               
               
                   
                       &lt;xsd:annotation&gt; 
               
               
                   
                        &lt;xsd:documentation&gt;Additional information about the event 
               
               
                   
                 itself&lt;/xsd:documentation&gt; 
               
               
                   
                       &lt;/xsd:annotation&gt; 
               
               
                   
                      &lt;/xsd:element&gt; 
               
               
                   
                      &lt;xsd:element name=“context” type=“smap:eventContext” maxOccurs=“32” 
               
               
                   
                 minOccurs=“0”&gt; 
               
               
                   
                       &lt;xsd:annotation&gt; 
               
               
                   
                        &lt;xsd:documentation&gt;Information about other aspects of the system at 
               
               
                   
                 the time of the event&lt;/xsd:documentation&gt; 
               
               
                   
                        &lt;/xsd:annotation&gt; 
               
               
                   
                      &lt;/xsd:element&gt; 
               
               
                   
                     &lt;/xsd:sequence&gt; 
               
               
                   
                     &lt;xsd:attribute name=“id” type=“xsd:token”/&gt; 
               
               
                   
                     &lt;xsd:attribute name=“cloudObjectId” type=“xsd:token”/&gt; 
               
               
                   
                     &lt;xsd:attribute name=“mediaType” type=“xsd:token” use=“required”/&gt; 
               
               
                   
                     &lt;xsd:attribute name=“ts” type=“xsd:long” use=“required”/&gt; 
               
               
                   
                     &lt;xsd:attribute name=“href” type=“xsd:anyURI”/&gt; 
               
               
                   
                     &lt;xsd:attribute name=“errorCode” type=“xsd:token”/&gt; 
               
               
                   
                     &lt;xsd:attribute name=“value” type=“xsd:string”/&gt; 
               
               
                   
                    &lt;/xsd:extension&gt; 
               
               
                   
                   &lt;/xsd:complexContent&gt; 
               
               
                   
                  &lt;/xsd:complexType&gt; 
               
               
                   
                  &lt;xsd:complexType name=“eventContext”&gt; 
               
               
                   
                   &lt;xsd:attribute name=“mediaType” type=“xsd:token” use=“required”/&gt; 
               
               
                   
                   &lt;xsd:attribute name=“value” type=“xsd:string” use=“required”/&gt; 
               
               
                   
                   &lt;xsd:attribute name=“href” type=“xsd:anyURI”/&gt; 
               
               
                   
                  &lt;/xsd:complexType&gt; 
               
               
                   
                  &lt;xsd:complexType name=“eventMetaData”&gt; 
               
               
                   
                   &lt;xsd:attribute name=” name” type=“xsd:token” use=“required”/&gt; 
               
               
                   
                   &lt;xsd:attribute name=“value” type=“xsd:string” use=“required”/&gt; 
               
               
                   
                  &lt;/xsd:complexType&gt; 
               
               
                   
                  &lt;xsd:complexType name=“cloudActionEvent”&gt; 
               
               
                   
                   &lt;xsd:complexContent&gt; 
               
               
                   
                    &lt;xsd:extension base=“smap:baseMessage”&gt; 
               
               
                   
                     &lt;xsd:sequence&gt; 
               
               
                   
                      &lt;xsd:element name=“ruleId” type=“xsd:long” minOccurs=“0” 
               
               
                   
                 maxOccurs=“1”&gt; 
               
               
                   
                       &lt;xsd:annotation&gt; 
               
               
                   
                        &lt;xsd:documentation&gt;Id of the rule that triggered this action, if 
               
               
                   
                 applicable.&lt;/xsd:documentation&gt; 
               
               
                   
                       &lt;/xsd:annotation&gt; 
               
               
                   
                      &lt;/xsd:element&gt; 
               
               
                   
                      &lt;xsd:element name=“eventId” type=“xsd:string” minOccurs=“0” 
               
               
                   
                 maxOccurs=“1”&gt; 
               
               
                   
                       &lt;xsd:annotation&gt; 
               
               
                   
                        &lt;xsd:documentation&gt;The id of the event that triggered the 
               
               
                   
                 rule.&lt;/xsd:documentation&gt; 
               
               
                   
                       &lt;/xsd:annotation&gt; 
               
               
                   
                      &lt;/xsd:element&gt; 
               
               
                   
                      &lt;xsd:element name=“cloudObjectId” type=“xsd:token” minOccurs=“1” 
               
               
                   
                 maxOccurs=“1”/&gt; 
               
               
                   
                      &lt;xsd:element name=“actionMediaType” type=“xsd:token” minOccurs=“1” 
               
               
                   
                 maxOccurs=“1”/&gt; 
               
               
                   
                      &lt;xsd:element name=“actionHrer type=“xsd:anyURI” minOccurs=“0” 
               
               
                   
                 maxOccurs=“1”/&gt; 
               
               
                   
                      &lt;xsd:element name=“actionInput” type=“smapinput” minOccurs=“0” 
               
               
                   
                 maxOccurs=“32”/&gt; 
               
               
                   
                     &lt;/xsd:sequence&gt; 
               
               
                   
                    &lt;/xsd:extension&gt; 
               
               
                   
                   &lt;/xsd:complexContent&gt; 
               
               
                   
                  &lt;/xsd:complexType&gt; 
               
               
                   
                  &lt;xsd:complexType name=“input”&gt; 
               
               
                   
                   &lt;xsd:attribute name=“name” type=“xsd:token” use=“required”/&gt; 
               
               
                   
                   &lt;xsd:attribute name=“mediaType” type=“xsd:token” use=“optional”/&gt; 
               
               
                   
                   &lt;xsd:attribute name=“value” type=“xsd:string” use=“required”/&gt; 
               
               
                   
                  &lt;/xsd:complexType&gt; 
               
               
                   
               
            
           
         
       
     
     The ICS of an embodiment effects ICS platform integration with third party system and device functionality (e.g., Philips Hue lights, Chamberlain garage door openers, Nest thermostats, Dropcam cameras, Doorbot doorbell cameras, etc.), as described in detail herein. Using the same processes, other server-to-server (cloud) services (e.g., Accuweather, MSO digital assets such as voicemail, etc.) are also integrated into the ICS platform. 
     Cloud Actions and Triggers of an embodiment enable cloud services and internet-connected devices to leverage the user interface, Rules Engine and other functions of the service provider system. This allows third party devices (e.g., smart door bells, door locks, garage door operators, cameras, thermostats, lighting systems, lighting devices, lawn irrigation systems, plant sensors, pet feeders, weather stations, rain sensors, pool controls, air quality sensors, music systems, remote controllers, internet user interfaces, connected systems, connected vehicles, etc.), third party services (e.g., weather forecasting services and applications, family networking services and applications, etc.), and others to trigger automations in the service provider system using the Rules Engine. This enables end-users to integrate and use their previously-standalone internet connected devices with their service provider-based service. 
       FIG.  36    is an example rules interface for controlling triggers and actions involving third party devices integrated in the CAT, under an embodiment.  FIG.  37    is an example of a triggers portion of a rules interface for third party services integrated with the CAT, under an embodiment.  FIG.  38    is another example of an actions portion of a rules interface for integrated third party devices, under an embodiment. The rules automation actions and triggers of an embodiment include monitor/control functionality enabled via proprietary UIs, and with cards in the Card UI as described herein. 
     Embodiments include a system comprising a cloud hub located in a premises. The cloud hub comprises a plurality of adapters coupled to a plurality of premises devices. The cloud hub is configured as a gateway for the premises devices. The system includes a virtual gateway located in a cloud server environment and coupled to the cloud hub. The virtual gateway is configured as a server-side abstraction of the cloud hub. The cloud hub and the virtual gateway are configured as an automation platform that maintains state data of the plurality of premises devices, controls interaction among the plurality of premises devices, and monitors and manages the plurality of premises devices. 
     Embodiments include a system comprising: a cloud hub located in a premises, wherein the cloud hub comprises a plurality of adapters coupled to a plurality of premises devices, wherein the cloud hub is configured as a gateway for the premises devices; a virtual gateway located in a cloud server environment and coupled to the cloud hub, wherein the virtual gateway is configured as a server-side abstraction of the cloud hub, wherein the cloud hub and the virtual gateway are configured as an automation platform that maintains state data of the plurality of premises devices, controls interaction among the plurality of premises devices, and monitors and manages the plurality of premises devices. 
     The plurality of adapters includes an internet protocol (IP) adapter. 
     The IP adapter is coupled to a premises device including at least one IP device. 
     The plurality of adapters includes a radio adapter. 
     The radio adapter is configured to use a communication protocol of a premises device coupled to the radio adapter. 
     The radio adapter includes a wireless radio adapter. 
     The radio adapter is coupled to a premises device including at least one Zigbee device. 
     The plurality of adapters includes a camera adapter. 
     The camera adapter is coupled to a premises device including at least one camera device. 
     The at least one camera device includes a tunnel camera. 
     The plurality of adapters include a Wi-Fi adapter. 
     The cloud hub is coupled to a radio frequency (RF) bridge in the premises. 
     The RF bridge is coupled to at least one additional premises device. 
     The at least one additional premises device includes at least one Z-Wave device. 
     The cloud server environment includes a session server, wherein the virtual gateway is an instance of a plurality of virtual gateways running on the session server. 
     The cloud server environment includes at least one of a registry gateway and a session gateway, wherein the at least one the registry gateway and a session gateway are coupled to the session server. 
     The registry gateway is configured to identify the virtual gateway from the plurality of virtual gateways and route incoming data from the cloud hub to the virtual gateway. 
     The routing of incoming data includes a mapping of premises device identification (ID) and device type to site ID corresponding to the premises. 
     The premises device ID corresponds to at least one of the plurality of premises devices. 
     The site ID is assigned to the cloud hub. 
     The cloud hub is configured to communicate with the registry gateway and receive the site ID. 
     The cloud hub is configured to communicate with the registry gateway and receive a network address of the credential gateway. 
     The cloud server environment includes a credential gateway, wherein the cloud hub is configured to communicate with the credential gateway and, using the site ID, receive a key. 
     The cloud hub is configured to receive session server data from the credential gateway, wherein the session server data includes a session server address. 
     The virtual gateway comprises a first gateway state machine running on the session server. 
     The cloud hub comprises a processor running a second gateway state machine. 
     At least one of the first gateway state machine and the second gateway state machine maintains track of a state of the plurality of premises devices. 
     At least one of the first gateway state machine and the second gateway state machine monitors and manages the plurality of premises devices. 
     The first gateway state machine and the second gateway state machine maintain track of a state of the plurality of premises devices. 
     The first gateway state machine and the second gateway state machine monitor and manage the plurality of premises devices. 
     The system includes at least one premises device of the plurality of premises devices configured to communicate with the virtual gateway over a cellular coupling. 
     Inbound communications to the virtual gateway comprise packet communications. 
     Outbound communications from the virtual gateway comprise short message service (SMS) messages. 
     The cloud hub is configured to maintain a persistent connection with the cloud server environment. 
     The cloud hub is coupled to the cloud server environment using a broadband coupling. 
     The cloud hub is coupled to the cloud server environment using a cellular coupling. 
     The system includes a remote device coupled to the cloud server environment, wherein the remote device receives state data of the plurality of premises devices and provides control data to the plurality of premises devices. 
     The remote device is coupled to the cloud server via at least one of a mobile portal and a web portal. 
     The plurality of premises devices includes at least one of a sensor, a detector, a camera, an input/output (I/O) device, a touchscreen controller, a video camera, an input/output (I/O) device, an actuator, and a device controller that controls an attached device. 
     Embodiments include a method comprising configuring a cloud hub to include a plurality of adapters. The plurality of adapters is coupled to a plurality of premises devices. The cloud hub is located in a premises and configured as a gateway for the premises devices. The method includes configuring a cloud server environment to include a virtual gateway. The virtual gateway is coupled to the cloud hub and configured as a server-side abstraction of the cloud hub. The method includes configuring the cloud hub and the virtual gateway as an automation platform that maintains state data of the plurality of premises devices, controls interaction among the plurality of premises devices, and monitors and manages the plurality of premises devices. 
     Embodiments include a method comprising: configuring a cloud hub to include a plurality of adapters, wherein the plurality of adapters is coupled to a plurality of premises devices, wherein the cloud hub is located in a premises and configured as a gateway for the premises devices; configuring a cloud server environment to include a virtual gateway, wherein the virtual gateway is coupled to the cloud hub and configured as a server-side abstraction of the cloud hub; configuring the cloud hub and the virtual gateway as an automation platform that maintains state data of the plurality of premises devices, controls interaction among the plurality of premises devices, and monitors and manages the plurality of premises devices. 
     The plurality of adapters includes an internet protocol (IP) adapter. 
     The IP adapter is coupled to a premises device including at least one IP device. 
     The plurality of adapters includes a radio adapter. 
     The method includes configuring the radio adapter to use a communication protocol of a premises device coupled to the radio adapter. 
     The radio adapter includes a wireless radio adapter. 
     The radio adapter is coupled to a premises device including at least one Zigbee device. 
     The plurality of adapters includes a camera adapter. 
     The camera adapter is coupled to a premises device including at least one camera device. 
     The at least one camera device includes a tunnel camera. 
     The plurality of adapters include a Wi-Fi adapter. 
     The cloud hub is coupled to a radio frequency (RF) bridge in the premises. 
     The RF bridge is coupled to at least one additional premises device. 
     The at least one additional premises device includes at least one Z-Wave device. 
     The method includes configuring the cloud server environment to include a session server, wherein the virtual gateway is an instance of a plurality of virtual gateways running on the session server. 
     The method includes configuring the cloud server environment to include at least one of a registry gateway and a session gateway, wherein the at least one of the registry gateway and the session gateway are coupled to the session server. 
     The method includes configuring the registry gateway to identify the virtual gateway from the plurality of virtual gateways and route incoming data from the cloud hub to the virtual gateway. 
     The method includes configuring the routing of incoming data to include a mapping of premises device identification (ID) and device type to site ID corresponding to the premises. 
     The premises device ID corresponds to at least one of the plurality of premises devices. 
     The site ID is assigned to the cloud hub. 
     The method includes configuring the cloud hub to communicate with the registry gateway and receive the site ID. 
     The method includes configuring the cloud hub to communicate with the registry gateway and receive a network address of the credential gateway. 
     The method includes configuring the cloud server environment to include a credential gateway, and configuring the cloud hub to communicate with the credential gateway and, using the site ID, receive a key. 
     The method includes configuring the cloud hub to receive session server data from the credential gateway, wherein the session server data includes a session server address. 
     The method includes configuring the virtual gateway to include a first gateway state machine running on the session server. 
     The method includes configuring the cloud hub to include a processor running a second gateway state machine. 
     The method includes configuring at least one of the first gateway state machine and the second gateway state machine to maintain track of a state of the plurality of premises devices. 
     The method includes configuring at least one of the first gateway state machine and the second gateway state machine to monitor and manage the plurality of premises devices. 
     The method includes configuring the first gateway state machine and the second gateway state machine to maintain track of a state of the plurality of premises devices. 
     The method includes configuring the first gateway state machine and the second gateway state machine to monitor and manage the plurality of premises devices. 
     The method includes configuring at least one premises device of the plurality of premises devices to communicate with the virtual gateway over a cellular coupling. 
     The method includes configuring inbound communications to the virtual gateway to include packet communications. 
     The method includes configuring outbound communications from the virtual gateway to include short message service (SMS) messages. 
     The method includes configuring the cloud hub to maintain a persistent connection with the cloud server environment. 
     The cloud hub is coupled to the cloud server environment using a broadband coupling. 
     The cloud hub is coupled to the cloud server environment using a cellular coupling. 
     The method includes a remote device coupled to the cloud server environment, wherein the remote device receives state data of the plurality of premises devices and provides control data to the plurality of premises devices. 
     The remote device is coupled to the cloud server via at least one of a mobile portal and a web portal. 
     The plurality of premises devices includes at least one of a sensor, a detector, a camera, an input/output (I/O) device, a touchscreen controller, a video camera, an input/output (I/O) device, an actuator, and a device controller that controls an attached device. 
     Embodiments include a system comprising a cloud hub located in a premises. The cloud hub comprises a plurality of adapters coupled to a plurality of premises devices. The cloud hub is configured as a gateway for the premises devices. The system includes a virtual gateway located in a cloud server environment and coupled to the cloud hub. The virtual gateway is configured as a server-side abstraction of the cloud hub. The cloud hub and the virtual gateway are configured as an automation platform that maintains state data of the plurality of premises devices, controls interaction among the plurality of premises devices, and monitors and manages the plurality of premises devices. The system includes a security system coupled to the virtual gateway. The security system includes a plurality of security system components. 
     Embodiments include a system comprising: a cloud hub located in a premises, wherein the cloud hub comprises a plurality of adapters coupled to a plurality of premises devices, wherein the cloud hub is configured as a gateway for the premises devices; a virtual gateway located in a cloud server environment and coupled to the cloud hub, wherein the virtual gateway is configured as a server-side abstraction of the cloud hub, wherein the cloud hub and the virtual gateway are configured as an automation platform that maintains state data of the plurality of premises devices, controls interaction among the plurality of premises devices, and monitors and manages the plurality of premises devices; a security system coupled to the virtual gateway, wherein the security system includes a plurality of security system components. 
     The plurality of adapters includes an internet protocol (IP) adapter. 
     The IP adapter is coupled to a premises device including at least one IP device. 
     The plurality of adapters includes a radio adapter. 
     The radio adapter is configured to use a communication protocol of a premises device coupled to the radio adapter. 
     The radio adapter includes a wireless radio adapter. 
     The radio adapter is coupled to a premises device including at least one Zigbee device. 
     The plurality of adapters includes a camera adapter. 
     The camera adapter is coupled to a premises device including at least one camera device. 
     The at least one camera device includes a tunnel camera. 
     The plurality of adapters include a Wi-Fi adapter. 
     The cloud hub is coupled to a radio frequency (RF) bridge in the premises. 
     The RF bridge is coupled to at least one additional premises device. 
     The at least one additional premises device includes at least one Z-Wave device. 
     The cloud server environment includes a session server, wherein the virtual gateway is an instance of a plurality of virtual gateways running on the session server. 
     The cloud server environment includes at least one of a registry gateway and a session gateway, wherein the at least one the registry gateway and a session gateway are coupled to the session server. 
     The registry gateway is configured to identify the virtual gateway from the plurality of virtual gateways and route incoming data from the cloud hub to the virtual gateway. 
     The routing of incoming data includes a mapping of premises device identification (ID) and device type to site ID corresponding to the premises. 
     The premises device ID corresponds to at least one of the plurality of premises devices. 
     The site ID is assigned to the cloud hub. 
     The cloud hub is configured to communicate with the registry gateway and receive the site ID. 
     The cloud hub is configured to communicate with the registry gateway and receive a network address of the credential gateway. 
     The cloud server environment includes a credential gateway, wherein the cloud hub is configured to communicate with the credential gateway and, using the site ID, receive a key. 
     The cloud hub is configured to receive session server data from the credential gateway, wherein the session server data includes a session server address. 
     The virtual gateway comprises a first gateway state machine running on the session server. 
     The cloud hub comprises a processor running a second gateway state machine. 
     At least one of the first gateway state machine and the second gateway state machine maintains track of a state of the plurality of premises devices. 
     A least one of the first gateway state machine and the second gateway state machine monitors and manages the plurality of premises devices. 
     The first gateway state machine and the second gateway state machine maintain track of a state of the plurality of premises devices. 
     The first gateway state machine and the second gateway state machine monitor and manage the plurality of premises devices. 
     The system includes at least one premises device of the plurality of premises devices configured to communicate with the virtual gateway over a cellular coupling. 
     Inbound communications to the virtual gateway comprise packet communications. 
     Outbound communications from the virtual gateway comprise short message service (SMS) messages. 
     The cloud hub is configured to maintain a persistent connection with the cloud server environment. 
     The cloud hub is coupled to the cloud server environment using a broadband coupling. 
     The cloud hub is coupled to the cloud server environment using a cellular coupling. 
     The system includes a remote device coupled to the cloud server environment, wherein the remote device receives state data of the plurality of premises devices and provides control data to the plurality of premises devices. 
     The remote device is coupled to the cloud server via at least one of a mobile portal and a web portal. 
     The plurality of premises devices includes at least one of a sensor, a detector, a camera, an input/output (I/O) device, a touchscreen controller, a video camera, an input/output (I/O) device, an actuator, and a device controller that controls an attached device. 
     At least one of the cloud hub and the virtual gateway is configured to maintain state data of the security system, and control interaction among the plurality of premises devices and the security system. 
     The security system is coupled to the virtual gateway using at least one of a broadband coupling and a cellular coupling. 
     The security system is coupled to the virtual gateway using a broadband coupling. 
     The cloud hub is coupled to the gateway using a cellular coupling. 
     The cloud server environment includes a security server. 
     The plurality of security system components includes at least one of a sensor, a detector, a camera, an input/output (I/O) device, and a touchscreen. 
     The plurality of security system components includes at least one of an Internet Protocol (IP) device, a video camera, an input/output (I/O) device, an actuator, and a device controller that controls an attached device. 
     Embodiments include a method comprising configuring a cloud hub to include a plurality of adapters. The plurality of adapters is coupled to a plurality of premises devices. The cloud hub is located in a premises and configured as a gateway for the premises devices. The method includes configuring a cloud server environment to include a virtual gateway. The virtual gateway is coupled to the cloud hub and configured as a server-side abstraction of the cloud hub. The method includes configuring the cloud hub and the virtual gateway as an automation platform that maintains state data of the plurality of premises devices, controls interaction among the plurality of premises devices, and monitors and manages the plurality of premises devices. The method includes configuring a coupling between the virtual gateway and a security system in the premises, wherein the security system includes a plurality of security system components. 
     Embodiments include a method comprising: configuring a cloud hub to include a plurality of adapters, wherein the plurality of adapters is coupled to a plurality of premises devices, wherein the cloud hub is located in a premises and configured as a gateway for the premises devices; configuring a cloud server environment to include a virtual gateway, wherein the virtual gateway is coupled to the cloud hub and configured as a server-side abstraction of the cloud hub; configuring the cloud hub and the virtual gateway as an automation platform that maintains state data of the plurality of premises devices, controls interaction among the plurality of premises devices, and monitors and manages the plurality of premises devices; configuring a coupling between the virtual gateway and a security system in the premises, wherein the security system includes a plurality of security system components. 
     The plurality of adapters includes an internet protocol (IP) adapter. 
     The IP adapter is coupled to a premises device including at least one IP device. 
     The plurality of adapters includes a radio adapter. 
     The method includes configuring the radio adapter to use a communication protocol of a premises device coupled to the radio adapter. 
     The radio adapter includes a wireless radio adapter. 
     The radio adapter is coupled to a premises device including at least one Zigbee device. 
     The plurality of adapters includes a camera adapter. 
     The camera adapter is coupled to a premises device including at least one camera device. 
     The at least one camera device includes a tunnel camera. 
     The plurality of adapters include a Wi-Fi adapter. 
     The cloud hub is coupled to a radio frequency (RF) bridge in the premises. 
     The RF bridge is coupled to at least one additional premises device. 
     The at least one additional premises device includes at least one Z-Wave device. 
     The method includes configuring the cloud server environment to include a session server, wherein the virtual gateway is an instance of a plurality of virtual gateways running on the session server. 
     The method includes configuring the cloud server environment to include at least one of a registry gateway and a session gateway, wherein the at least one the registry gateway and a session gateway are coupled to the session server. 
     The method includes configuring the registry gateway to identify the virtual gateway from the plurality of virtual gateways and route incoming data from the cloud hub to the virtual gateway. 
     The method includes configuring the routing of incoming data to include a mapping of premises device identification (ID) and device type to site ID corresponding to the premises. 
     The premises device ID corresponds to at least one of the plurality of premises devices. 
     The site ID is assigned to the cloud hub. 
     The method includes configuring the cloud hub to communicate with the registry gateway and receive the site ID. 
     The method includes configuring the cloud hub to communicate with the registry gateway and receive a network address of the credential gateway. 
     The method includes configuring the cloud server environment to include a credential gateway, and configuring the cloud hub to communicate with the credential gateway and, using the site ID, receive a key. 
     The method includes configuring the cloud hub to receive session server data from the credential gateway, wherein the session server data includes a session server address. 
     The method includes configuring the virtual gateway to comprise a first gateway state machine running on the session server. 
     The method includes configuring the cloud hub to include a processor running a second gateway state machine. 
     The method includes configuring at least one of the first gateway state machine and the second gateway state machine to maintain track of a state of the plurality of premises devices. 
     The method includes configuring at least one of the first gateway state machine and the second gateway state machine to monitor and manage the plurality of premises devices. 
     The method includes configuring the first gateway state machine and the second gateway state machine to maintain track of a state of the plurality of premises devices. 
     The method includes configuring the first gateway state machine and the second gateway state machine to monitor and manage the plurality of premises devices. 
     The method includes configuring at least one premises device of the plurality of premises devices to communicate with the virtual gateway over a cellular coupling. 
     The method includes configuring inbound communications to the virtual gateway to include packet communications. 
     The method includes configuring outbound communications from the virtual gateway to include short message service (SMS) messages. 
     The method includes configuring the cloud hub to maintain a persistent connection with the cloud server environment. 
     The method includes configuring the cloud hub to couple to the cloud server environment using a broadband coupling. 
     The method includes configuring the cloud hub to couple to the cloud server environment using a cellular coupling. 
     The method includes configuring the cloud server environment to couple to a remote device, wherein the remote device receives state data of the plurality of premises devices and provides control data to the plurality of premises devices. 
     The remote device is coupled to the cloud server via at least one of a mobile portal and a web portal. 
     The plurality of premises devices includes at least one of a sensor, a detector, a camera, an input/output (I/O) device, a touchscreen controller, a video camera, an input/output (I/O) device, an actuator, and a device controller that controls an attached device. 
     The method includes configuring at least one of the cloud hub and the virtual gateway to maintain state data of the security system, and control interaction among the plurality of premises devices and the security system. 
     The security system is coupled to the virtual gateway using at least one of a broadband coupling and a cellular coupling. 
     The security system is coupled to the virtual gateway using a broadband coupling. 
     The method includes configuring the cloud hub to couple to the gateway using a cellular coupling. 
     The method includes configuring the cloud server environment to include a security server. 
     The plurality of security system components includes at least one of a sensor, a detector, a camera, an input/output (I/O) device, and a touchscreen. 
     The plurality of security system components includes at least one of an Internet Protocol (IP) device, a video camera, an input/output (I/O) device, an actuator, and a device controller that controls an attached device. 
     As described above, computer networks suitable for use with the embodiments described herein include local area networks (LAN), wide area networks (WAN), Internet, or other connection services and network variations such as the world wide web, the public internet, a private internet, a private computer network, a public network, a mobile network, a cellular network, a value-added network, and the like. Computing devices coupled or connected to the network may be any microprocessor controlled device that permits access to the network, including terminal devices, such as personal computers, workstations, servers, mini computers, main-frame computers, laptop computers, mobile computers, palm top computers, hand held computers, mobile phones, TV set-top boxes, or combinations thereof. The computer network may include one of more LANs, WANs, Internets, and computers. The computers may serve as servers, clients, or a combination thereof. 
     The system can be a component of a single system, multiple systems, and/or geographically separate systems. The system can also be a subcomponent or subsystem of a single system, multiple systems, and/or geographically separate systems. The system can be coupled to one or more other components (not shown) of a host system or a system coupled to the host system. 
     One or more components of the system and/or a corresponding system or application to which the system is coupled or connected includes and/or runs under and/or in association with a processing system. The processing system includes any collection of processor-based devices or computing devices operating together, or components of processing systems or devices, as is known in the art. For example, the processing system can include one or more of a portable computer, portable communication device operating in a communication network, and/or a network server. The portable computer can be any of a number and/or combination of devices selected from among personal computers, personal digital assistants, portable computing devices, and portable communication devices, but is not so limited. The processing system can include components within a larger computer system. 
     The processing system of an embodiment includes at least one processor and at least one memory device or subsystem. The processing system can also include or be coupled to at least one database. The term “processor” as generally used herein refers to any logic processing unit, such as one or more central processing units (CPUs), digital signal processors (DSPs), application-specific integrated circuits (ASIC), etc. The processor and memory can be monolithically integrated onto a single chip, distributed among a number of chips or components, and/or provided by some combination of algorithms. The methods described herein can be implemented in one or more of software algorithm(s), programs, firmware, hardware, components, circuitry, in any combination. 
     The components of any system that includes the system herein can be located together or in separate locations. Communication paths couple the components and include any medium for communicating or transferring files among the components. The communication paths include wireless connections, wired connections, and hybrid wireless/wired connections. The communication paths also include couplings or connections to networks including local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), proprietary networks, interoffice or backend networks, and the Internet. Furthermore, the communication paths include removable fixed mediums like floppy disks, hard disk drives, and CD-ROM disks, as well as flash RAM, Universal Serial Bus (USB) connections, RS-232 connections, telephone lines, buses, and electronic mail messages. 
     Aspects of the systems and methods described herein may be implemented as functionality programmed into any of a variety of circuitry, including programmable logic devices (PLDs), such as field programmable gate arrays (FPGAs), programmable array logic (PAL) devices, electrically programmable logic and memory devices and standard cell-based devices, as well as application specific integrated circuits (ASICs). Some other possibilities for implementing aspects of the systems and methods include: microcontrollers with memory (such as electronically erasable programmable read only memory (EEPROM)), embedded microprocessors, firmware, software, etc. Furthermore, aspects of the systems and methods may be embodied in microprocessors having software-based circuit emulation, discrete logic (sequential and combinatorial), custom devices, fuzzy (neural) logic, quantum devices, and hybrids of any of the above device types. Of course the underlying device technologies may be provided in a variety of component types, e.g., metal-oxide semiconductor field-effect transistor (MOSFET) technologies like complementary metal-oxide semiconductor (CMOS), bipolar technologies like emitter-coupled logic (ECL), polymer technologies (e.g., silicon-conjugated polymer and metal-conjugated polymer-metal structures), mixed analog and digital, etc. 
     It should be noted that any system, method, and/or other components disclosed herein may be described using computer aided design tools and expressed (or represented), as data and/or instructions embodied in various computer-readable media, in terms of their behavioral, register transfer, logic component, transistor, layout geometries, and/or other characteristics. Computer-readable media in which such formatted data and/or instructions may be embodied include, but are not limited to, non-volatile storage media in various forms (e.g., optical, magnetic or semiconductor storage media) and carrier waves that may be used to transfer such formatted data and/or instructions through wireless, optical, or wired signaling media or any combination thereof. Examples of transfers of such formatted data and/or instructions by carrier waves include, but are not limited to, transfers (uploads, downloads, e-mail, etc.) over the Internet and/or other computer networks via one or more data transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When received within a computer system via one or more computer-readable media, such data and/or instruction-based expressions of the above described components may be processed by a processing entity (e.g., one or more processors) within the computer system in conjunction with execution of one or more other computer programs. 
     Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in a sense of “including, but not limited to.” Words using the singular or plural number also include the plural or singular number respectively. Additionally, the words “herein,” “hereunder,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. When the word “or” is used in reference to a list of two or more items, that word covers all of the following interpretations of the word: any of the items in the list, all of the items in the list and any combination of the items in the list. 
     The above description of embodiments of the systems and methods is not intended to be exhaustive or to limit the systems and methods to the precise forms disclosed. While specific embodiments of, and examples for, the systems and methods are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the systems and methods, as those skilled in the relevant art will recognize. The teachings of the systems and methods provided herein can be applied to other systems and methods, not only for the systems and methods described above. 
     The elements and acts of the various embodiments described above can be combined to provide further embodiments. These and other changes can be made to the systems and methods in light of the above detailed description.