Module-based device interaction system

Abstract

A system that enables a person to monitor and/or control a device via a network, such as the Internet, via an interactive hardware module that interfaces with the device and communicates with a module server located locally or remotely from the placement of the module. The hardware module allows for the transmission and receipt of data between the device interfaced to the hardware module and the module server, thereby enabling the user manually or automatically to control or monitor the device via an access medium, such as an API.

Description

TECHNICAL FIELD

This application relates generally to the control of remote mechanisms via a network. More particularly, the present invention relates to a system and method for a Web-based medium for controlling or monitoring devices using a wireless or wired network and/or Internet connections.

BACKGROUND

Controlling devices over the Internet requires considerable knowledge across several fields. For example, to manipulate a device via the Internet, such as via an interactive Web site, a person may need to understand Web site design, networking, server management, communication protocols, multiple programming languages, embedded systems, and mechatronics. As such, the vast majority of people do not possess the necessary skills to configure a system allowing for the control a device via the World Wide Web.

In addition to the knowledge required, the hardware requirements of such an undertaking are prohibitive small entities, such as individuals or small organizations. Current Web-based device monitoring and control interface systems are meant for industrial applications. The expense and power requirements of industrial equipment are too great to make this a realistic solution. In addition, the equipment is rather large, consuming large cabinets and racks impractical for home or small business use. This solution may also require familiarity with the equipment's programming interface and custom cabling and hardware.

Other current solutions for Web-based device control require a person to establish a server which accepts requests from the Internet. These servers are typically embedded Web servers that host their own Web pages for device interaction. The Internet connections employed by small entities are typically based on dynamic internet protocol (IP) address assignment. Hosting a server on a dynamic IP address is problematic because the IP address may change, causing a disruption in the server's connection to the Internet and preventing a remote user from contacting the server. Additionally, hosting a server requires the user to configure the local network. An average person may have difficulty with the intricacies of remapping router ports and other such matters. Furthermore, some individuals may not have access to their Internet connection networking equipment, such as people living in apartment complexes or dormitories. Internet Service Providers (ISPs) may cause additional problems for server-based architectures. Many ISPs frown upon users hosting servers and may block ports used for this.

Both the aforementioned industrial and server solutions lack convenient mechanisms for Web site and Web service integration. Considerable knowledge of Hypertext Markup Language (HTML), JavaScript, and Application Programming Interfaces (APIs) is required to place any controls on a Web site or to establish access via a Web service (such as a social network), web application, desktop program, mobile application, or the like. As a result, such a solution requires customized Web site integration which, again, is beyond the skills of the average user.

What is needed is a convenient system and method that enables an average person to configure an architecture to control or monitor a device via a Web-based medium.

SUMMARY

The present invention addresses the aforementioned needs by providing a system that enables a person to monitor and/or control a device via a network, such as the Internet, via an interactive hardware module that interfaces with the device and communicates with a module server located locally or remotely from the placement of the module. The hardware module allows for the transmission and receipt of data between the device interfaced to the hardware module and the module server, thereby enabling the user manually or automatically to control or monitor the device via an access medium, such as an API.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and other advantages and features of the invention can be obtained, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments thereof that are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 illustrates a general architecture overview of an embodiment of a module-based device interaction system.

FIG. 2 illustrates an example of an embodiment of a hardware module enabled for Web-based device control or monitoring.

FIG. 3 illustrates an example of an embodiment of a module server enabled to interact with the hardware module of the present invention.

FIG. 4 illustrates a flowchart process of an embodiment of initializing the hardware module of the present invention.

FIG. 5 illustrates a flowchart process of an embodiment of a module server communicating with the hardware module of the present invention.

DETAILED DESCRIPTION

Various embodiments of the invention are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person with ordinary skill in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the invention.

FIG. 1 illustrates a general architecture overview of an embodiment of a module-based device interaction system (MBDIS) [100]. Although only a single instance of each component is depicted, this is for illustrative purposes only and is not to be construed as limiting. The components of the MBDIS [100] can interact with one another via a network [104], which may be any applicable electronic and/or wireless network. The network [104] can be a wide-area network (WAN), such as the Internet or a mobile network. The MBDIS [100] can include a hardware module [102] configured to be an input/output (I/O) mechanism and enabled to allow for connections to one or more devices [106]. The hardware module [102] can be connected via the network [104] to a module server [108], thereby serving as a link between the device [106] and the module server [108]. The hardware module [102] can connect to the network [104] via a local network [112], such as a local area network (LAN) or wireless local area network (WLAN).

The module server [108] can receive data messages sent by the hardware module [102], such as those relayed from an interfaced device [106]. The module server [108] can relay such communication to an access medium [110] and/or another hardware module [102] connected to the network [104]. The module server [108] can interface with an access medium [110] to transmit communications to or from the hardware module [102] and to configure the hardware module [102].

An access medium [110] can be a mechanism by which a user can control or monitor a device [106]. For example, an access medium [110] can enable a user to operate a device [106], monitor the status of a device [106], receive and/or review data generated by a device [106], or the like. In one embodiment, an access medium [110] can be accessible by various agents, such as a personal computer, a mobile device, or the like. For example, an access medium [110] can be a Web service, such as, for example, a streaming server, a push-driven server, an email server, a social network, a database, an event notification service, a scripting server, a Web page, or the like. Additionally, an access medium [110] can comprise an API, such as a Web widget or gadget, another convenient programming interface, or the like. Alternatively, an access medium can be a Web interface, such as a dynamic scripting, a Flash interface, or the like.

Data transmitted between one or more of the device [106], the hardware module [102], the module server [108], and the access medium [110] can be encrypted, such as via a compressible encryption technique encapsulated and translated over common internetworking protocols and networking technologies.

Hardware Module

The hardware module [102] can act as a client to the module server [108]. This configuration enables the MBDIS [100] to overcome problems inherent in hosting a server. A dynamic IP address is no longer problematic. The hardware module [102] can initiate the connection to the module server [108] and, as such, there is no need to keep track of the user's IP address. Additionally, an ISP does not block outbound traffic from a user's location (as opposed to in-bound traffic, as would be the case if the user employed a local server), as this would be the equivalent to preventing the user from accessing the Internet entirely. Furthermore, as the hardware module [102] itself establishes the connection as a client to the module server [108], there is no need for any network configuration on the part of the user. All traffic generated by the use of the hardware module [102] is viewed as normal traffic by the network [104]. This enables the hardware module [102] to work through firewalls and proxy servers.

The design of the hardware module [102] can vary per implementation. In one example, the hardware module [102] may be constructed of a two-sided, 0.060 inch-thick printed circuit board (PCB). A top and bottom plate of 0.125 inch clear acrylic, fixed in place by spacers and screws, may provide a simple, exterior structure for the hardware module [102]. A label on the top surface of the hardware module [102] may indicate the model number, serial number, connection assignments, media access control (MAC) address, and I/O channel pin out, and the like. In totality, the hardware module [102] may be 3.8 inches×2.5 inches×1.24 and weighs approximately 90 grams. In other scenarios, the hardware module [102] may be smaller or larger and may be constructed of different materials.

As illustrated by FIG. 2, in one embodiment, the hardware module [102] can include a network connection mechanism [202], a controller mechanism [204], a memory mechanism [206], a power mechanism [208], an initialization mechanism [210], an initialization status display [212], a connectivity status display [214], an I/O channel port [216], and an event processor [218].

The hardware module [102] can be located at a location convenient to the entity employing it. For example, an individual may employ a hardware module [102] at his residence or a small business owner may employ a hardware module [102] at his work location. The hardware module [102] can be located anywhere, so long as the device [106] to be controlled or monitored can connect with the network connection mechanism [202].

The controller mechanism [204] can communicate with the components of the hardware module [102] to direct the flow of data, monitor and/or direct the activity of components, and the like. For example, the controller mechanism [204] can communicate with the network connection mechanism [202] to enable the communication of data to and from the hardware module [102]. In one embodiment, the controller mechanism [204] is a microcontroller. In addition to enabling the transmission of messages from an interfaced device [106] to the module server [108], the controller mechanism [204] can relay messages from a device [106] interfaced with one I/O channel port [216] (e.g., I/O channel port [216A]) to another device [106] interfaced with a different I/O channel port [216] (e.g., I/O channel port [216B]).

The network connection mechanism [202] can enable the hardware module [102] to connect to the network [104], and thereby transmit and receive data from the module server [108]. In one embodiment, the network connection mechanism [202] can connect with the network [104] via a local network [112]. For example, the hardware module [102] may function on any 10/100/1000 Base-T auto-negotiated network. In one embodiment, the network connection mechanism [202] can enable a wired connection. For example, the network connection mechanism [202] may be an Ethernet controller. Alternatively, the network connection mechanism [202] can enable a wireless connection. The hardware module [102] can function via a Dynamic Host Configuration Protocol (DHCP) or static addressing. If the local network [112] is configured for MAC filtering, the MAC address of the hardware module [102] can be added to the local network router's list of allowable addresses. Alternatively, the hardware module [102] can be connected to a non-MAC filtered network first and management tools can be used to change the MAC address of the hardware module [102]. Alternatively, the hardware module [102] can connect to the network [104] directly.

When the hardware module [102] connects to the network [104], it can establish a communication link with the module server [108]. The communication link may be established through any known protocol, such as via Transmission Control Protocol/Internet Protocol (TCP/IP). The hardware module [102] can accept communications from and transmit messages to the module server [108].

The hardware module [102] can include a memory mechanism [206] to store settings. For example, the memory mechanism [206] may be non-volatile random access memory (RAM).

The power mechanism [208] can enable the distribution of power to the hardware module [102]. For example, the power mechanism [208] may enable and monitor the receipt of electricity to power the hardware module [102] from an electrical cord or battery.

The initialization mechanism [201] can be used to establish a connective link between the hardware module [102] and a user account at the module server [108]. Additionally, the initialization mechanism [210] can enable a user to reset the hardware module [102] to a previous condition, such as its factory condition. The initialization mechanism [210] can be a manual implement. For example, the initialization mechanism [210] may be a button that the user pushes or holds down. Alternatively, the initialization mechanism [210] can be accessible electronically. For example, the user may operate the initialization mechanism [210] via his computer, such as via an access medium [110].

The hardware module [102] can include one or more display mechanisms, such as an initialization status display [212]. The initialization status display [212] can relate information associated with the hardware module's [102] connection to the module server [108]. For example, the initialization status display [212] may indicate one or more of the following:

• • the hardware module [102] has booted successfully and is attempting to connect to the local network [112];
  • the hardware module [102] has established a connection with the local network [112];
  • the hardware module [102] has successful accomplished a DHCP transaction and now has an IP address;
  • the hardware module [102] is attempting to resolve remote server's hostname to an IP address;
  • the hardware module [102] successful DNS hostname resolution; the hardware module [102] is looking for the Internet gateway MAC address; the hardware module [102] has found the Internet gateway and is searching for a free a local TCP socket;
  • the hardware module [102] has located a free local TCP socket and is attempting to connect to the module server [108];
  • the hardware module [102] has established a successful connection to the module server and authentication has commenced; or
  • the hardware module [102] has successfully undergone authentication and normal operation has commenced.In one embodiment, the initialization status display [212] is a seven segment LED numeric display.

The hardware module [102] can also include a connectivity status display [214]. The connectivity status display [214] can indicate the state of connectivity between the hardware module [102] and the module server [108]. For example, the connectivity status display [214] may indicate one or more of the following:

• • the hardware module [102] is not connected to the module server [108];
  • the hardware module [102] is connected to the module server [108];
  • the hardware module [102] is powering up; or
  • the hardware module [102] has disconnected from the module server [108] and is resetting.

The hardware module [102] can also include one or more I/O channel ports [216] that can interface with a device [106]. Although four I/O channel ports [216] have been depicted in FIG. 2 (i.e., 216A, 216B, 216C, 216D), this is not to be construed as limiting and amount can vary depending upon implementation. The device [106] can be any appropriate apparatus, such as a conventional device [106A] or a smart device [106B] (described in detail below). The hardware module [102] can interface with a device [106] via a wired or wireless connection. For example, an I/O channel port [216] can include an outlet to receive a wired plug. Alternatively, an I/O channel port [216] can be configured to receive a wireless signal. In one embodiment, the user can employ a medium adapter to interface a device [106] with the hardware module [102] wirelessly. The medium adapter can enable various wireless communication methods and can enable the conversion of various communication methods. For example, the medium adapter may enable the conversion of an electronic signal to a fiber optic or radio frequency signal.

The hardware module [102] can discover an interfaced device [106] manually or automatically. To manually discover a device [106], the user can access his user account and indicate the type of device [106] he had interfaced. For example, a user may access a MBDIS Web site, log into his user account and indicate the type of device [106], such as via a dropdown menu or from a checkbox list. Alternatively, the controller mechanism [204] can include a discovery protocol which can enable plug and play functionality. For example, the discovery protocol may interrogate the controller mechanism [204] to determine whether an interfaced device [106] is a conventional device [106A] or a smart device [106B].

In one embodiment, each I/O channel port [216] has a separate digital input, analog input, and digital output. Each I/O channel port [216] can be configured to employ digital input/output, analog input/output, serial data input/output, pulse and frequency counting/generation, audio input/output, video input/output, or the like. The hardware module [102] can be configured to set the state (i.e., the digital voltage level) of output on a particular I/O channel port [216] and can also read a voltage input level. As described below in regard to smart mode, an I/O channel port [216] can serve as a data channel for communication with interfaced smart devices [106B].

The I/O channel ports [216] can be independent from one another and may be the input and output means for the MBDIS [100]. Communication from the module server [108] to the hardware module [102] can instruct the hardware module [102] to change output lines on the I/O channel ports [216] while communication from the hardware module [102] to the module server can relay information about device [106] values and other inputs.

An I/O channel port [216] can include multiple lines, or “pins.” The functionality of each pin may vary dependent upon the operating mode of the particular I/O channel port [216]. An I/O channel port [216] can be capable of operating in one of two modes: normal mode and smart mode.

Normal Mode

When an I/O channel port [216] is set to normal mode, the hardware module [102] can use digital I/O and analog input capabilities native to the controller mechanism [204] to interact with an interfaced device [106]. For example, an I/O channel port [216] set to normal mode may be enabled for discreet digital input and/or output, pulse counting, frequency counting, serial input and/or output, and analog input and/or output, or the like. In normal mode, the hardware module [102] can interface with conventional devices, such as analog sensors, switches, lights, liquid crystal displays (LCDs), microcontroller units (MCUs), relays, or the like. A device [106] connected to an I/O channel port [216] set to normal mode can be considered a conventional device [106A].

Smart Mode

When an I/O channel port [216] is set to smart mode, the hardware module [102] can interface with more sophisticated devices [106]. Smart mode can convert the I/O channel port [216] into a digital communication port allowing other equipment to interface with the hardware module [102] and an I/O channel port [216] set for this mode may be capable of serial communication via standard and proprietary protocols. For example, smart mode may be employed if a particular function is beyond the scope of a simple analog sensor or digital I/O device. A device [106] interfaced to a smart mode-enabled I/O port channel [216] can be considered a smart device [106B]. A smart device [106B] can include its own controller mechanism, such as a microcontroller, to manage communication via its particular I/O port channel [216]. For example, smart devices [106B] may be serial or servo controllers, Infrared receivers and transmitters, video devices, audio devices, USB hardware, wireless transceiver, medium adapters, other peripheral hardware, or the like. Smart devices [106B] provide data to the hardware module [102], which can relay it to the module server [108], which can in turn transmit it to an access medium or another hardware module [102]. For example, the data can be sent to a networked database for logging. Likewise, messages intended for a smart device [106B] can be received by the module server [108], relayed to the hardware module [102] and then transmitted to the smart device [106B]. The hardware module [102] need not directly manage a smart device [106B]. In one embodiment, the hardware module [102] merely registers the existence of the smart device [106B] on startup and directs messages to and from it.

The hardware module [102] can act as a client while the interfaced smart device [106B] may function as a server. Despite these roles, this configuration allows for the smart device [106B] to generate and transmit a message unsolicited to the hardware module [102] and, in turn, the module server [108].

The hardware module [102] can also include an event processor [218]. The event processor [218] can monitor behavior of an interfaced device [106] and, when, a particular event occurs, the event processor [218] can push a message to another device [106] interfaced with the hardware module [102] or to the module server [108] and, in turn, an access medium [110] or one or more additional hardware modules [102]. For example, if the device [106] interfaced with the hardware module [102] is a thermometer, the event processor [218] can send a message to a second interfaced device [106] or to the module server [108] when a particular temperature is reached. As another example, the event processor [216] may receive video or audio data and, in turn, initiate a message transmission. In addition to, or instead of, initiating the pushing of data based upon a particular device event, the event processor [218] can push messages via an established schedule. For example, the interfaced device [106] may be a lamp and a user may configure the hardware module to turn on the lamp at a certain time on a certain day. Furthermore, the event processor [218] can communicate data when requested by an access medium [110]. For instance, continuing with the thermometer example, the user can employ an access medium [110] to request the thermometer's current temperature reading.

As is detailed below, the module server [108] can also include an event processor [316]. The event processor [316] located at the module server [108] can be functionally equivalent to the event processor [218] of the hardware module [102]. In one embodiment, the hardware module event processor [218] can be synchronized with the configuration maintained by the module server event processor [316]. Once configured, the hardware module event processor can enable the hardware module [102] to function autonomously, regardless of whether it has an active connection to the module server [108].

Either, or both, the hardware module event processor [218] and the module server event processor [316] can cause the transmission of a message based on an event associated with one device [106] to a second device [106]. In one embodiment, both the first and second devices can be interfaced with the same hardware module [102], either via separate I/O channel ports [216] or the same I/O channel port [216]. As such, the event processor [218/316] can cause the relaying of data between two or more devices [106] interfaced with the same hardware module [102].

Module Server

The module server [108] can relay data and instructions between a hardware module [102] and an access medium [110] or a second hardware module [102]. The module server [108] can be located remotely from the hardware module [102], but need not be. The module server [108] can include a server controller [310], one or more module connections [302], one or more access medium connections [304], an authentication database [306], a user account database [312], a transaction identifying mechanism [314], a transaction logging mechanism [308], and an event processor [316].

The server controller [310] can enable the flow of data amongst the various components of the module server [108].

A module connection [302] can be a socket waiting and listening for incoming communication from a hardware module [102]. A module connection [302] can enable the pulling and pushing of data between the module server [108] and a hardware module [102] (and, in turn, a device [106]). An access medium connection [304] is a socket used by the module server [108] to communicate with an access medium [110]. An access medium connection [304] can wait and listen for incoming communication from an access medium [110] and can receive conventional requests from Web services, such as Hypertext Transfer Protocol (HTTP) requests. For example, an access medium connection [302] can receive communication originating from a web browser or an automated Common Gateway Interface (CGI) script, desktop application, Web service API, or mobile application. In one embodiment, the module connections [302] and the access medium connections [304] wait and listen on different ports to ensure proper communication.

The authentication database [306] can maintain information pertinent to module identifiers (e.g., serial numbers). The authentication database [306] can maintain a record of all module identifiers for all hardware modules [102] distributed by the MBDIS service provider. The authentication database [306] can also maintain data pertaining to encryption. For example, when a hardware module [102] initiates a connection with the module server [108], the server controller [310] may access the authentication database [306] to locate a module identifier and its corresponding encryption key to authenticate the connection. If the module identifier is located and the encryption is successful, the hardware module [102] can interface with the module server [108] and, in turn, an access medium [110]. Alternatively, if a corresponding module identifier is not found or encryption fails, the server controller [310] can close the connection.

The module server [108] can include a transaction logging mechanism [308] to record transactions with one or more hardware modules [102]. The transaction logging mechanism [308] can be configured to record all transactions that are handled by the module server [108] and/or those indicated by the configurations established via the module server event processor [316] or the hardware module event processor [218]. The recorded data can be employed to analyze system data, such as to create charts, plots, or calculate values for record-keeping or event triggering.

The module server [108] can also include a transaction identifying mechanism [314]. As described in detail below, the transaction identifying mechanism [314] can associate a transaction identifier with each transmission sent to the hardware module [102] to ensure successful interaction between the module server [108] and the hardware module [102].

A user account database [312] can maintain user accounts for individuals who have registered their hardware modules [102] with the MBDIS [100]. A user account can include various information associated with the user, such as contact information (name, mailing address, email address, phone numbers, latitude/longitude, etc.), information particular to the user's hardware module(s) [102] (model data, make data, a module identifier, etc.), authentication information (e.g., username and password), financial account information (e.g., credit card numbers, etc.), or the like. An individual can create a user account prior to initializing his hardware module [102]. To create a user account, the user can provide the MBDIS service provider with the necessary information via a Web site, email, mail, verbally (e.g., via a customer service representative), fax, or the like.

As aforementioned, the module server [108] can include an event processor [316]. The event processor [316] can push a message to an access medium [110] or second hardware module [102] per an event that has occurred at a device [106] that is interfaced with a first hardware module [102]. This configuration can enable a user to monitor the performance of a device [106] in real time. In one scenario, the access medium [110] may be an email service, a text messaging service (e.g., Short Message Service (SMS), etc.), a social network service, or the like. For example, if the device [106] is a thermometer, the event processor [316] can push a message to a social networking service, such as Facebook, when the thermometer reaches a certain temperature, and the temperature data can be displayed as a status update. As another example, the temperature data can be sent to an email service and the user can receive the data in an email message. As with the hardware module event processor [218], the module server event processor [316] can also transmit messages on a scheduled, periodic basis. In addition to pushing messages, the event processor [316] can provide such data when requested by an access medium [110] or another hardware module [102].

A user can access his user account via, for example, the MBDIS Web site and configure one or more triggers and corresponding action for his registered hardware module(s) [102]. As mentioned above, the user can also initiate a synchronization process whereby the module server event processor [316] settings are synchronized with those of a hardware module event processor [218].

Regarding communication between a first hardware module [102] and a second hardware module [102], the event processor [316] can provide instructions to the second hardware module [102] based on an event that occurred at the first hardware module [102]. For example, the event processor [316] may receive temperature data from a thermometer device [106] interfaced with the first hardware module [102] and, if the temperature data indicates a temperature higher than a certain threshold, the event processor [316] may send a message to the second hardware module [102] instructing it to activate an interfaced cooling device [106]. The event processor [316] can act in a similar fashion to relay messages between two or more devices [106] interfaced with the same hardware module [102]. For instance, the event processor [316] may receive temperature data from a thermometer device [106] interfaced with one I/O channel port [216] and send a message to a cooling device [106] interfaced with a second I/O channel port [216] on the same hardware module [102]. In another example, the device [106] interfaced with the hardware module [102] may be a data storage medium and the user can employ the data storage medium to record data regarding a second device [106] interfaced with a different I/O channel port [216] or another hardware module [102].

In addition, or instead of, sending a message to an access medium [110] or a hardware module [102], the event processor [316] can send data to the transaction logging mechanism [308]. The user can employ this configuration when he wishes to, for example, record data from a device [106], but does not desire real-time monitoring. Additionally, the transaction logging mechanism [308] can enable various visualization processes so that data recorded via the event processor [316] can be analyzed. For example, data recorded by the transaction logging mechanism [308] can be accessible via an access medium [110], such as a Web widget that can display the recorded data as a chart or graph.

The event processor [316] can also be enabled to transmit data to an external database for recordation, analysis, or the like.

Access Medium

The access medium [110] can be a mechanism by which a user can interact, via the module server [108], with a device [106] interfaced with a hardware module [102]. For example, an access medium [110] may be an API, a Web service, a Web interface, or the like. As aforementioned, via an access medium [110], a user can control or monitor a device [106]. For example, an access medium [110] can request data from a device [106], translate data generated by a device [106] into a useful syntax and display it, push a command to a device [106], or the like. The access medium [110] can be provided by portable, client-side scripting that allows for embedding control and monitoring resources into Web sites, mobile device applications and widgets, Web service feeds, social networks, Web service APIs, or the like. The access medium [110] interpret data received from a device [106] and present the data to users and Web services in current and appropriate scales, formats, and syntaxes. For example, an access medium [110] can receive data from a thermometer device [106] and present that data in degrees Fahrenheit or Centigrade. The access medium [110] can receive data based upon push data transmission initiated by an event processor [218/316], can request data itself, or it can access data recorded in the transaction logging mechanism [308] (e.g., to display such logged data a chart, graph, or the like).

Additionally, an access medium [110] can also allow a user to configure the hardware module [102] and/or its interfaced devices [106] via the module server [108]. For example, the user may set an I/O channel port [216] to normal mode or smart mode.

An access medium [110] can be accessible via Web-enabled devices, such as personal computers and mobile devices (e.g., mobile phones, smart phones, personal digital assistant, etc.).

To enhance user convenience, the MBDIS service provider can offer one or more access mediums [110] to users. For example, a user may visit an MBDIS Web site and access ready-made Web widget coding that can be input into the coding of a Web page in order to control or monitor a device [106] from the Web page. The MBDIS service provider can provide access mediums [110] for common functionalities, such as light levels, temperature display, weather information, and the like. The MBDIS sever provider can also provide a convenient interface by which a user can create a customized access medium [110]. For example, an MBDIS Web site may include a point and click interface, a wizard interface, or another form of customized programming interface by which a user may generate a customized access medium [110] suitable to the user's needs and/or the particular functionality of a device [106].

Hardware Module Initialization

In order for a user to employ to a hardware module [102], he may be required to authenticate it with the module server [108], thereby linking his hardware module [102] to his user account. The MBDIS service provider can employ an authentication process in order to confirm that an actual individual wishing to employ a particular hardware module [102] is initializing the hardware module [102], rather than an automated process. This can ensure the hardware module [102] is being employed with the user's permission.

To begin initialization, the user can connect his hardware module [102] to the network [104] [step 402]. As aforementioned, the user may connect his hardware module [102] to the network [104] via a local network [112]. The hardware module [102] can then transmit a connection request to the module server [108] [step 404]. The module server [108] can be configured to listen to the network [104] and enabled to await such requests. Once a connection has been established between the module server [108] and the hardware module [102] [step 406], the connectivity status display [214] can indicate this (e.g., by displaying a green light).

The user can then register a module identifier associated with the hardware module [102] with the module server [108] [step 408]. In one embodiment, the user can register a module identifier by associating it with a user account maintained by the module server [108]. The module identifier can be, for example, a serial number included on the hardware module [102] and/or documentation provided to the user when the hardware module [102] was acquired. The module identifier can also be included in firmware maintained by the hardware module [102]. In addition to registering the module identifier, the user can register contact information, authentication information (e.g., username and password), financial account information, or the like.

The registration process can involve the user establishing a user account with the MBDIS service provider. The user can establish the user account prior to the initialization. Additionally, the user can be allowed to register multiple hardware modules [102] with the same user account and, therefore, can employ the initialization process to add an additional hardware module [102] to an existing user account. In one embodiment, the user can establish a user account by employing a computing device (e.g., personal computer, mobile device, etc.) to access a Web site linked to the module server [108]. Once at the Web site, the user can register the module identifier and other information. In alternate embodiments, the user can establish and/or augment a user account via other methods. For example, a user may verbally establish an account by calling the MBDIS service provider and providing the necessary information to a customer service representative. As another example, a user may complete a registration form and mail, email, or email it to the MBDIS service provider.

Once the user has registered the module identifier with his user account, he can activate the initialization mechanism [210] [step 410]. For example, if the initialization mechanism [210] is an external button, the user may hold the button for particular amount of time (e.g., five seconds). The initialization status display [212] can indicate to the user that initialization has commenced.

The hardware module [102] can receive authentication data transmitted from the module server [108] [step 412]. The hardware module [108] can display this authentication data to the user via the initialization status display mechanism [212]. For example, the module server [108] may transmit a series of digits to the hardware module [108] and the initialization status display mechanism [212] may display the digits to the user.

The user can provide the transmitted authentication data to the MBDIS service provider [step 414]. In one embodiment, the user can enter the displayed authentication data at a Web site linked to the module server [108]. The user may do so during the same session with which he registered the module identifier. In alternate embodiments, the user can provide the authentication data by verbally relating it to a customer service representative (e.g. via telephone), or by mailing, emailing, or faxing the authentication data to the MBDIS service provider.

The provided authentication data is relayed to the module server [108], which analyzes it to determine if it is valid. If the provided authentication data is incorrect, the user may be requested to provide it again. If the user cannot successfully do so, the hardware module [102] can receive a termination signal from the module server [108] [step 416] and the hardware module [102] may not be activated. If the authentication data is deemed valid, the hardware module [102] can receive a signal from the module server [108] indicating that the initialization is complete [step 418]. The hardware module [102] can now have an active connection with the module server [108] and the initialization display mechanism [212] can signal the end of initialization.

Communication between the Hardware Module and the Module Server

As aforementioned, the configuration of the MBDIS [100] can enable the hardware module [102] to serve as a client rather than a server. The hardware module [102] can issue transmissions via the network [104] to the module server [108] without the module server [108] replying immediately. In one embodiment, Internet Protocol (IP), such as HTTP protocol, can be used for communication between the hardware module [102] and the module server [108]. The hardware module [102] can act as a client and issue requests to the module server [108]. The module server [108] need not reply immediately, thereby allowing the hardware module [102] to send another request to push data to the module server [108]. Although it may, the hardware module [102] need not request anything from the module server [108]. Once the hardware module [102] makes its initial connection, requests can be generated by the module server [108]. The hardware module [102] can push data to the module server [108] and can do so without being solicited. In one embodiment, the hardware module [102] can transmit HTTP POST requests, which are not cached by web proxy servers. Furthermore, the use of HTTP POST transmissions with no immediate reply from the module server [108] enables web proxy servers to manage the communication between the hardware module [102] and module server [108] as standard HTTP traffic, thereby alleviating unnecessary burden upon the MBDIS [100].

The module server [108] can manage numerous connections simultaneously. Since the module server [108] can request data from the hardware module [102] in addition to the hardware module [102] being able to send data to the module server [108], there is the possibility that data messages may cross in transit. As illustrated by FIG. 5, the transaction identifying mechanism [314] can prevent any problem that may occur due to such a situation. The server controller [310] can receive a transmission to be sent to the hardware module [102] [step 502]. For example, a user may employ an access medium [110] to send control instructions to the hardware module [102] or the event processor [316] may wish to send data to a hardware module [102] per an event triggered by a device [106]. The transaction identifying mechanism [314] of the module server [108] can associate a transaction identifier with each transmission to be sent to the hardware module [102] [step 504]. The transaction identifying mechanism [314] can record this transaction identifier [step 506]. For example, the module server [108] may issue a unique, six digit transaction identification code with each request sent to the hardware module [102]. The module server [108] can send the transmission with its associated transaction identifier to the hardware module [102] [step 508]. The module server [108] can receive a response transmission from the hardware module [102] and the response can include a transaction identifier, such as in a Uniform Resource Identifier [step 510]. The transaction identifying mechanism [314] can compare the received transaction identifier with those it has recorded to determine if the response is a valid transmission [step 512]. If the received transaction identifier does not match one recorded, the response can be rejected [step 514]. If the received transaction identifier matches on record, the response is deemed a valid transmission and accepted [step 516]. As aforementioned, the hardware module [102] can transmit data unsolicited. For such transmissions, the controller mechanism [204] of the hardware module [102] can associate a particular transaction identifier with all unsolicited transmissions and the transaction identifying mechanism [314] can be configured to treat all such transmissions as valid. For example, the hardware module [102] may use the transaction identifier “000000” for all unsolicited transmissions.

For example, in one scenario, a message from the hardware module [102] may be formatted as follows:

• • POST/001234 HTTP/1.1
  • Host: www.hardwareserver.com
  • Content-Encoding: application/octet-stream
  • Cache-Control: no-transform, no-store, private
  • Content-Length: 15
  • Message: Hh8S1ykd08Mp82g

In the example above, the transaction identifier is 001234.

As another example, a request from the module server [108] to the hardware module [102] may be formatted as the following:

• • HTTP/1.1 200 OK

Date: Mon, 14 Jul. 2008 04:28:18 GMT

• • Cache-Control: no-transform, no-store, private
  • Content-Encoding: application/octet-stream
  • Content-Length: 23
  • Message: uN05aJdnaSneH96hu6dsll

In this example, the transaction identifier is included, and encrypted, in the message body (e.g., 059611).

Messages Pushed by the Hardware Module to the Module Server

As mentioned, the hardware module [102] can generate and transmit messages on its own volition. For example, rather than the module server [108] periodically polling the hardware module [102] for the status of a digital input, the event processor [218] of the hardware module [102] can push a message at the instant it receives an indication from an I/O channel port [216] that an event has occurred at an interfaced device [106]. The hardware module [102] can push data to the module server [108] or a device 106 on a separate I/O channel port [216] via auto-messaging, triggered messaging, or a smart device push. Auto-messaging and triggered messaging can be accomplished via an I/O channel port [216] set to normal mode, while a smart device push can be handled via smart mode.

To push data via auto-messaging, the event processor [218] of the hardware module [102] can be configured to send the state of the I/O channel port [216] (and therefore the interfaced conventional device [106A]) automatically at a set schedule. For example, an analog input value can be sent every fifteen seconds. Each I/O channel port [216] can be set to send either its analog input or digital input at a user determined schedule. Each I/O channel port [216] auto-message interval can be set independently.

Data can be pushed via triggered messaging when the state of a digital or analog input from the interfaced conventional device [106A] changes. Each I/O channel port [216] can have a configurable trigger and reset value. The hardware module [102] can send a message when an input reaches a certain level.

If the I/O channel port [216] is set to smart mode, the hardware module [102] can transmit an unsolicited message from the smart device [106B]. The message can be sent on behalf of the configuration of the smart device [106B] itself. For example, particular events, activities, actions, or the like that occur via the smart device [106B] may initiate the transmission of data to the hardware module [102] and in turn the module server [108] or another device 106 interfaced with a separate I/O channel port [216].

These and other aspects of the present invention will become apparent to those skilled in the art by a review of the preceding detailed description. Although a number of salient features of the present invention have been described above, the invention is capable of other embodiments and of being practiced and carried out in various ways that would be apparent to one of ordinary skill in the art after reading the disclosed invention. Therefore, the description should not be considered to be exclusive of these other embodiments. Also, it is to be understood that the phraseology and terminology employed herein are for the purposes of description and should not be regarded as limiting.

Claims

1. A system for enabling a Web-based interface allowing for interaction between an individual and an interactive device, the system comprising: a hardware module, wherein the hardware module is an input/output client apparatus enabled to interface with an interactive device via one or more of a wired connection and a wireless connection and communicate a data transmission regarding the interactive device to a module server and to receive a data transmission from the module server via an electronic network; anda module server, wherein the module server is configured to communicate with one or more hardware modules and an access medium via the electronic network, to communicate a data transmission between the hardware module and the access medium, thereby enabling an individual to interact via the access medium, with the interactive device interfaced with the hardware module, and to communicate a data transmission between the hardware module and an additional hardware module, thereby enabling the hardware module to interact with the additional hardware module.

2. The system of claim 1, wherein one or more of the hardware module and the module server include an event processor, wherein the event processor is enabled to initiate communication of a data transmission between the hardware module and the module server based upon one or more of the following: an event occurring at the interactive device interfaced with the hardware module and an established schedule.

3. The system of claim 1, wherein the electronic network comprises one or more of the following: a wide-area network and a wired or wireless local network, wherein the wired or wireless local network enables the connection of the hardware module to the wide-area network.

4. The system of claim 1, wherein the access medium includes one or more of the following: an application programming interface, a Web interface, and a Web service.

5. The system of claim 1, wherein the hardware module is further configured to communicate a data transmission regarding the interactive device to an additional interactive device interfaced with the hardware module.

6. The system of claim 1, wherein the interactive device is one or more of the following: a conventional device and a smart device.

7. The system of claim 1, wherein the module server includes a transaction logging mechanism, wherein the transaction logging mechanism can record data pertaining to one or more data transmissions conducted via the module server.

8. A method for module server of a module-based device interaction system to interact with a hardware module, the method comprising: receiving, by a module server, a data transmission from an access medium or a second hardware module to be sent to a first hardware module, wherein a hardware module is an input/output client apparatus interfaced via one or more of a wired connection or a wireless connection with an interactive device, and wherein the module server is configured to communicate data transmissions to and from the access medium or the second hardware module to the first hardware module;associating, at the module server, a transaction identifier with the data transmission;recording, at the module server, the transaction identifier associated with the data transmission;sending, from the module server to the first hardware module, the data transmission and the recorded transaction identifier;receiving, by the module server, a response transmission from the first hardware module, wherein the response transmission includes a response transaction identifier; anddetermining, by the module server, whether the response transaction identifier matches a recorded transaction identifier;wherein if the response transaction identifier matches a recorded transaction identifier, the module server accepts the response transmission from the first hardware module; andwherein if the response transaction identifier does not match a recorded transaction identifier, the module server does not accept the response transmission from the first hardware module.

9. The method of claim 8, further comprising recording, at the module server, an unsolicited transmission identifier.

10. A hardware module apparatus for use in a module-based device interaction system, the apparatus comprising: a network connection mechanism, wherein the network connection mechanism enables interaction with a wide-area network and, thereby, enabling the apparatus to receive a data transmission from an access medium or an additional hardware module apparatus via a module server connected to the wide-area network and enabling the apparatus to transmit a data transmission to the access medium or the additional hardware module apparatus via the module server connected to the wide-area network;a power mechanism, wherein the power mechanism enables the receipt and distribution of power;a memory mechanism, wherein the memory mechanism is configured to store a setting pertaining to apparatus operation;an input/output channel port, wherein the input/output channel port enables the apparatus to interface with an interactive device via one or more of a wired connection and a wireless connection, thereby enabling the interactive device to respond according to the data transmission received from the access medium or the additional hardware module via the module server connected to the wide-area network;an event processor, wherein the event processor is enabled to initiate data transmission based upon data associated with the interactive device interfaced with the input/output channel port; anda controller mechanism, wherein the controller mechanism is configured to direct operation of the network connection mechanism, the power mechanism, the memory mechanism, the input/output channel port, and the event processor.

11. The apparatus of claim 10, wherein the network connection mechanism enables connection to a wide-area network via one or more of the following: a wired connection and a wireless connection.

12. The apparatus of claim 10, wherein the event processor is configured to initiate a data transmission based upon one or more of the following: an event triggered by the interactive device interfaced with the apparatus and an established schedule.

13. The apparatus of claim 10, wherein the event processor is configured to initiate a data transmission to a module server.

14. The apparatus of claim 10, wherein the apparatus further includes one or more additional input/output channel ports.

15. The apparatus of claim 14, wherein event processor is configured to initiate a data transmission from a first device interfaced with a first input/output channel port to a second device interfaced with a second input/output channel port.

16. The apparatus of claim 10, wherein the controller mechanism is a microcontroller.

17. The apparatus of claim 10, wherein the apparatus further comprises one or more of the following: an initialization mechanism, an initialization status display mechanism, and a connectivity status display mechanism.