Abstract:
A network based product enables browser based computers, smart phones or tablets to connect to and access the product. A local router can be automatically configured by the product. The product can be automatically registered with a DDNS server and a user account opened. Authentication can be carried out between the product and the server.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
       [0001]    This application claims the benefit of the filing date of U.S. Provisional Application Ser. No. 61/568,271 filed Dec. 8, 2011, entitled, “Connected Home Control System With Auto Router Port Configuration and DDNS Registration”. The &#39;271 application is hereby incorporated herein by reference. 
     
    
     FIELD 
       [0002]    This application pertains to systems and methods of providing web based access to displaced monitoring control systems. More particularly, the application pertains to such systems and methods which substantially automatically adjusts the setting of a local router and registers with a DDNS server to provide remote connectivity to homes and buildings, which include such monitoring systems. 
       BACKGROUND 
       [0003]    Regional monitoring systems are known which can provide information to a user via one or more computer networks as to a variety of conditions in a home, commercial or industrial building. Such systems are commercially available from representatives of the assignee hereof, Honeywell International Inc., under the brand name of TUXEDO home automation systems. A plurality of lights, thermostats, door locks, cameras, sensors, or detectors can be monitored by a system control unit with a touch screen keyboard. Such systems can be Internet enabled so that users can access their system remotely. 
         [0004]    There is a significant and growing consumer demand for remote connectivity into homes and buildings via smartphones and tablets to remotely control such systems. These can include intrusion, automation control, access, video, HVAC, energy management, home healthcare systems without limitation. Existing remote service concepts are primarily centralized cloud based services, virtual private networks (VPN) or dynamic domain name service (DDNS). 
         [0005]    DDNS type of services have received less interest in past due to requirements for complex router configurations and DDNS registration.  FIG. 4A  illustrates a known manual process where a user configures the router. 
         [0006]    DDNS however is a very low cost and low maintenance solution. It would be desirable to provide versions of DDNS types of services that are easier to use than are known configurations. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0007]      FIG. 1  illustrates an overall view of a system in accordance herewith; 
           [0008]      FIG. 2  illustrates aspects of a DDNS registration process; 
           [0009]      FIG. 3  illustrates aspects of multi-port router assignments; 
           [0010]      FIG. 4A  illustrates a prior art process of manual, router port assignment; 
           [0011]      FIG. 4B  illustrates aspects of a process of automatic router port assignment in accordance herewith; 
           [0012]      FIG. 5A  illustrates a block diagram of a system in accordance herewith; 
           [0013]      FIG. 5B  illustrates another view of the system of  FIG. 5A ; 
           [0014]      FIG. 6A  illustrates another system in accordance herewith; and 
           [0015]      FIG. 6B  illustrates another view of the system of  FIG. 6A . 
       
    
    
     DETAILED DESCRIPTION 
       [0016]    While disclosed embodiments can take many different forms, specific embodiments thereof are shown in the drawings and will be described herein in detail with the understanding that the present disclosure is to be considered as an exemplification of the principles thereof as well as the best mode of practicing same, and is not intended to limit the application or claims to the specific embodiment illustrated. 
         [0017]    Embodiments hereof are based on products with built-in web servers to provide low cost and low maintenance remote connectivity via DDNS services. Unlike conventional IP camera remote DDNS solutions, embodiments hereof solve the two most difficult setup areas for an installer or home owner, to open an unused port in a local router and registering with a DDNS service. Two problematic configuration requirements are addressed in a user friendly “auto remote access account creation” process implemented between a web enabled product and a server. This process advantageously requires little or no user intervention. 
         [0018]    Intelligent IP network based products, such as Honeywell&#39;s TUXEDO brand home controllers with built-in web servers can communicate with browser based PC&#39;s, smartphones and tablets to connect and access such products via html or app based user interfaces. In one aspect, controller products, such as TUXEDO brand products, can incorporate universal plug and play (UPNP) auto router configuration technology to easily connect to a router and determine the router&#39;s firewall and port settings. It will then set the proper settings in the router and the product can be remotely accessed. 
         [0019]    In another aspect, a self-contained DDNS server can be provided that automatically accepts trusted controller products, such as TUXEDO brand products, and creates user accounts for the customers who have purchased the products. The TUXEDO brand products and the self-contained DDNS server both can incorporate matching authentication techniques to connect to each other and exchange data to automatically create remote access accounts. 
         [0020]    With respect to the figures,  FIG. 1  illustrates a configuration  10  wherein a plurality of buildings, such as residences R 1 , R 2  . . Rn include web enabled monitoring systems,  12 - 1 , implemented as Honeywell 6280-type TUXEDO brand products each with an interactive operator interface, such as indicated at  12   a . Associated with each of the products,  12 - 1  is a local router,  14 - 1 ,  14 - 2  . . .  14 -n to implement bidirectional communications via a plurality of networks, N- 1 , N- 2  . . . N-n via the internet I with a DDNS server  16  and an interrogating device such as a PC, smart phone or tablet  20  all without limitation. It will be understood that reference to the Honeywell 6280-type Tuxedo server based products, noted herein is exemplary only. Other types of network, Internet enabled or server based products come within the spirit and scope hereof. 
         [0021]    The product  12 - 1 , in accordance herewith, has reported its Public IP address to server  16 , along with an associated domain name, as at “1”. The server  16  stores the domain name and the IP address for later use. 
         [0022]    Subsequently, a user wishing to transmit a request, to interrogate or forward commands to the server based products, such as  12 - 1 , can transmit a domain name via a browser. The server  16  can look up the IP address, and forward it for execution to the appropriate addressee via a network, such as N- 1 . The device  20  can then communicate with the product  12 - 1 . Server  16  can thus maintain a current record of domain names and corresponding IP addresses, as new products are added, or moved to different locations, having different IP addresses. 
         [0023]      FIG. 2  illustrates a process  100  of automatically registering a server based product, such as  12 -i with DDNS server  16 . As at  102   a , on first powerup the product  12 -i initiates the registration sequence by communicating via local router  14 -I (not shown) and the internet I (not shown), with the server  16 . The product  12 -i and the server  16  automatically engage in an authentication process, as at  102   b.    
         [0024]    If the authentication process is successful, the product  12 -i forwards its IP address, and hardware address, MAC ID, to server  16 . In response, subsequently, as at  102   d , the server  16  creates a new user account, logs the product  12 -i into its database along with the IP address and account information. Then server  16  returns to the product  12 -i a default domain name, associated with the IP address and login information. 
         [0025]    With reference to  104   a , the product  12 -i forwards to the server  16  a domain name, login and user password, selected by the user via a keyboard or touchscreen capability in the product  12 -i. The server  16  creates the account for the user, as at  104   b  and as at  104   c  forwards the account information to the product  12 -i as at  104   c.    
         [0026]    Upon successful account creation the product  12 -i displays the account information on its screen  12   a  (not shown), as at  106   a . The user can then accept the terms and conditions to activate the account as at  106   b . Subsequently, as at  108  the user can long into the server  16  and update the account information. 
         [0027]    As a further advantage of the present embodiment, as illustrated in  FIG. 3  a second product,  12 -i 2  can be supported via a variation of the dynamic IP address with a common domain name. Unique port assignments can be implemented via the router  14   i.    
         [0028]      FIG. 4B  illustrates a process  200  of automatic adjustment of the local router  14 -i by the product  12 -i. The product  12 -i communicates with the local router  14 -i, as at  202  to establish an unused port number which can be set in both the product  12 -i and the router  14 -i. The product  12 -i reports the new port number to the server  16 , as at  206 . Multiple products can be supported via multiple different ports, as in  FIG. 3 . In the event that the product  12 -i encounters problems with the router  14 -i, it can communicate with the server  16 , as at  204 . A successful port setting can be communicated to user U via the display  12   a  (not shown) of the product  12 -i as  208 . 
         [0029]      FIG. 5A  illustrates a system  40  in accordance herewith. System  40  can implement a method which incorporates an IP intelligent device, such as  42 , capable of using UPNP technology, implemented at least in part with executable instructions  42   a , to automatically find and configure a network router  44  to open a port and automatically connect to a remote DDNS server, such as server  16 , to create a user DDNS acct with an assigned URL. This account will enable the user to instantly access the device  42  and other devices associate with the account from anywhere in the world over the Internet or a cellular network. 
         [0030]    System  40  includes, at least one IP intelligent device, such as  42 , with UPNP or Bonjour plug-n-play software  42   a , an optional built-in web server function  42   b , plus IP network router port forwarding auto configuration software  42   c , DDNS client software  42   d  capable of communicating with the DDNS server  16  to automatically create the user account. 
         [0031]    System  40  also includes, at least one UPNP capable IP network router  44  with or without built-in modem and/or access point, and, at least one DDNS server, such as server  16  located at a remote location providing DDNS service. The server  16  could be provided with or without auto DDNS account creation capabilities. 
         [0032]    System  40  can implement a method of establishing a user account and activating a URL for an associated external IP address. This method enables the device  42  to automatically detect, configure the router  44  and create a user DDNS account at the server  16  as follows: the IP intelligent device  42  uses UPNP functionality and software  42   a  to find the router  42  to which it is connected. The IP intelligent device  42  automatically negotiates with the router  44  for an unused port or gets a pre-assigned port from the administrator. The device  42  automatically requests that the router  44  open a port associated with the IP address of the device  42 . 
         [0033]    The device  42  subsequently receives confirmation from the router  44 . The device  42  acquires the router&#39;s external IP address from the router  44  or from the Internet I. 
         [0034]    The device  42  prepares a user account data packet (example: URL, user name, password, mac id, ip address port number, device number, acct number . . ). The packet can then be sent to a predetermined DDNS sever, such as server  16 , to request creation of a user account. The packet can, optionally, be encrypted and sent over a secure network. 
         [0035]    The device  42  receives a reply from the DDNS server  16  indicating that the request for an account was or was not accepted. If accepted, the DDNS server  16  establishes the user account and activates a URL for the associated external IP address. Port number association and activation are optional. The IP intelligent device  42  then requests that the DDNS server  16  validate the newly created URL so that users can access the device  42  externally. 
         [0036]      FIG. 5B  illustrates a system such as device  42  and router  44  installed in a region R 1  being monitored. As implemented, server based product  42 - 1  corresponds to the above discussed device  42 . Router  44 - 1  corresponds to the above discussed router  44 . As discussed above, per a user&#39;s request, router  44 - 1  can be set by the product  42 - 1 , and communications with the server  16  can take place to establish a user&#39;s account and activate the associated URL. 
         [0037]      FIG. 6A  illustrates a system  50  which includes IP intelligent device  42  capable of using UPNP technology, including software  42   a , to automatically find other IP network devices, find and configure the network router  44  to open a port and automatically connect to the remote DDNS server  16  to add a new IP device to a new or existing DDNS user account. Elements of system  50  which correspond to previously discussed elements of system  40  have been assigned the same identification numerals as in  FIG. 5A . 
         [0038]    The system  50  in implementing the above noted method can include at least one IP intelligent device  42  with an optional built-in web server function, UPNP or Bonjour plug-n-play software  42   a , IP network router port forwarding auto configuration software  42   c  plus DDNS client software  42   d  capable of communicating with the DDNS server  16  to create or update the user account automatically. 
         [0039]    System  50  also includes, at least one standard IP device with optional built-in web server function  52 , and, other functions such as IP camera, IP NAS drive, IP thermostat, IP energy meter, computers . . . and the like all without limitation. At least one UPNP capable IP network router  44  with or without built-in modem and/or access point can communicate at least with device  42 . At least one DDNS server  16  at a remote location provides DDNS service with or without auto DDNS account creation capabilities. 
         [0040]      FIG. 6B  illustrates the system  50  in connection with monitoring events in a region R 2 . Device  42  has been implemented as device  42 - 1 , for example the previously noted TUXEDO brand product, in conjunction with a local alarm monitoring system, indicated at  56   a , and associated sensors, as at  56   b.    
         [0041]    Systems such as  50  can implement various useful methods, including using UPNP technology to automatically find all associated devices in system  50  and supervising the devices periodically to resolve port conflict within the network plus within the router and updating the associated user accounts of the DDNS server  16  with new port changes of system  50 . Alternately, system  50  can automatically find and configure the network router to close a port and automatically connect to a remote DDNS server, such as server  16 , to remove IP devices from an existing DDNS user account. 
         [0042]    Additionally, a remote administrator or machine can remotely connect to an IP intelligent device capable of using UPNP technology to automatically find and configure a network router to open a port and automatically connect to a remote DDNS server, such as server  16 , to add an IP device to an existing DDNS user account. Alternately, the administrator or machine can remote connect to an IP intelligent device capable of using UPNP technology to automatically find and configure the network router to close a port and automatically connect to a remote DDNS server to remove the IP device from an existing DDNS user account. 
         [0043]    From the foregoing, it will be observed that numerous variations and modifications may be effected without departing from the spirit and scope hereof. It is to be understood that no limitation with respect to the specific apparatus illustrated herein is intended or should be inferred. It is, of course, intended to cover by the appended claims all such modifications as fall within the scope of the claims. 
         [0044]    Further, logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. Other steps may be provided, or steps may be eliminated, from the described flows, and other components may be add to, or removed from the described embodiments.