Patent Description:
There are many different home automation communication protocols, wireless, wired, or combinations of wired and wireless in use today. Examples of home automation communication protocols include Bluetooth® including Bluetooth low energy (BLE), X10, xPL, ZigBee®, Z-wave, C-Bus, EnOcean, KNX, Thread, Universal Powerline bus or the like. Many of these protocols do not allow communication between devices that operate according to the different protocols.

For example, BLE devices cannot communicate with ZigBee devices directly and vice versa. When BLE and ZigBee devices are both located in a premises, this inability to communicate with one another in effect creates an island of BLE devices and another island of ZigBee devices. Moreover, mobile devices which include a Bluetooth transceiver but lack a ZigBee transmitter, are only able to communicate directly with BLE devices.

Since the ZigBee and BLE protocols are used to control a number of complimenting devices, it would be advantageous to exploit the home Internet of Things (IoT) ecosystem as a whole rather than limiting it based on protocol and dealing with BLE and ZigBee islands independently. However, currently available IoT web applications and/or native applications can only list IoT devices according to the hardware capability of a mobile device. Hence, computer applications presently available for mobile devices only display BLE devices since mobile devices lack ZigBee transceivers.

Presently ZigBee device gateway applications only provide access to ZigBee devices discovered by the application. In some cases, the limiting factor is that the hardware executing the application does not have access to a compatible transmitter, receiver, transceiver or the like. In addition, there is presently no way to easily connect a BLE device with a ZigBee device on a mobile device. Even if it is connected, the mobile device or the application on the mobile device has to be ZigBee aware to know the actions possible on ZigBee devices.

Hence, there is a need in not only home automation, but premises automation (e.g., home, residence, office environment, industrial environments, and the like) to provide a capability for mobile devices to be given access to devices controllable via different protocols, so that a user can seamlessly associate actions to one type of device based on events received by another type of device.

<CIT> provides a prior art example of a method and system for master slave protocol communication in an intelligent electronic device. <CIT> provides a prior art example of an illumination control system, illuminating device and secondary controller. <CIT> provides a prior art example of an adaptable wireless power, light and automation system.

Further detailed embodiments are defined in the dependent claims.

The drawing figures depict one or more implementations in accord with the present concepts, by way of example only, not by way of limitations.

In the following detailed description, numerous specific details are set forth by way of examples in order to provide a thorough understanding of the relevant teachings. However, it should be apparent to those skilled in the art that the present teachings may be practiced without such details. In other instances, well known methods, procedures, components, and/or circuitry have been described at a relatively high-level, without detail, in order to avoid unnecessarily obscuring aspects of the present teachings.

BLE and ZigBee are the predominant standards used in the home automation IoT environment. Mobile devices, however, do not typically include a transceiver compatible with the ZigBee communication frequencies. To allow the ZigBee IoT devices to be controlled by mobile devices, it is desirable to provide the mobile devices access to ZigBee devices in a premises networking environment, such as the home automation IoT network. It would be beneficial for the ZigBee devices to be monitored and controlled by the mobile device in a manner similar to a Bluetooth-compatible device, even if only limited monitoring and control of the ZigBee device were possible. It would also be beneficial if a user could associate Bluetooth actions with ZigBee devices based on events received by Bluetooth devices in a premises networking environment.

Typically a ZigBee device is configured to communicate with a dedicated ZigBee device gateway to facilitate control and monitoring of the ZigBee device through communication uses a WiFi compatible application executing on a mobile device or computer terminal, or via a web application executing through a website.

In some instances, the dedicated ZigBee device gateway may provide an application that only presents ZigBee devices discovered by the dedicated ZigBee device gateway on the mobile device display. Prior to the disclosed examples, there was no way to easily combine control of a BLE device and a ZigBee device on a mobile device or a gateway. While BLE and ZigBee are primarily discussed, the following examples provide systems, devices and methods that address the foregoing problems and provide the advantage of enabling one device to control and monitor premises automation devices which communicate using disparate networking protocols.

<FIG> is a high level diagram of an example of customer premises networked system. In the examples of <FIG>, the customer premises networked system <NUM> includes a first network <NUM>, a second network <NUM>, a premises gateway <NUM>, a mobile device <NUM> and cloud server <NUM>.

The cloud server <NUM> may be provided by a multi-system operator, such as Comcast™, Verizon™, Time Warner™ or the like. In addition, the cloud server may include third-party applications (executing on Android™ or IOS™ operating systems) that facilitate the provision of different services by the devices within the first network <NUM> and the second network <NUM>, respectively. The first and second wireless networks <NUM>, <NUM> may provide communication and data exchange capabilities amongst devices within a premises system <NUM>. A premises may be a home, a business office area, a business, such as a retail establishment or industrial setting, a school or the like.

It is envisioned that the one or more networks <NUM>, <NUM> include devices dedicated to a particular networking protocol, and that the devices within the particular networks communicate according to the networking protocol of the particular network. The network protocol or wireless connectivity protocol may be a mesh network protocol that enables the devices with the particular network <NUM> or <NUM> to communicate amongst one another within their respective networks. Currently major low power IoT standards such as ZigBee and BLE (BT Smart) offer mesh networking. ZigBee and BLE can thus support several devices by forming a mesh network (self organizing and healing) of like devices. BLE devices, however, communicate only with BLE devices and ZigBee devices communicate only with ZigBee devices. BLE may be referred to as a wireless connectivity protocol or standard and ZigBee may referred to as a mesh networking protocol or standard. Further, applications are available on the cloud server <NUM> to connect devices together, thus offering meshing capability across devices of the same networking protocol. Unlike prior systems, the present examples provide the Devices <NUM>-<NUM> and Devices <NUM>-<NUM> in two disparate networks <NUM> and <NUM> that are controllable by a single device, such as mobile device <NUM>, configured to control devices of different types of mesh networking and/or wireless connectivity protocols, such as BLE and ZigBee, by execution of an application by the device processor.

To overcome this deficiency of prior systems, the premises gateway <NUM> of <FIG> may be configured to communicate using a number of different communication and/or network protocols. The premises gateway <NUM> may be configured to translate communications (as described below) between multiple different protocols, such as the first networking protocol, the second networking protocol and a third protocol. For example, the premises gateway <NUM> may be configured to communicate with devices <NUM> to <NUM> within the second network <NUM> according to the second networking protocol, which in this example is the ZigBee protocol.

In the example of <FIG>, the first network <NUM> may be configured to enable communications according to a first wireless networking protocol, such as a Bluetooth standard communication protocol. Devices <NUM> to <NUM> in the first network <NUM>, for example, may be configured to communicate according to the Bluetooth standard. As such, the first network <NUM> including mobile device <NUM> may be a mesh network that communicates according to the Bluetooth standard. The second network <NUM> may be configured to enable communications according to a second wireless networking protocol, such as the ZigBee mesh networking standard. For example, Devices <NUM> to <NUM> in the second network <NUM> may be configured to communicate according to the ZigBee standard. In this example, the second wireless networking protocol is incompatible with the first networking protocol.

In addition, the premises gateway <NUM> may communicate with the mobile device <NUM> via the first networking standard as well as via Bluetooth. In addition, the premises gateway <NUM> may be configured to communicate via a third wireless networking protocol, such as WiFi provided according to one or more of the <NUM> communication specifications. The third wireless networking protocol is not compatible with the first and second protocols.

Within the home network system <NUM>, the mesh network <NUM> may be a Bluetooth mesh that controls devices <NUM> to <NUM> that are within communication range of a primary device, such as mobile device <NUM>. The devices <NUM> to <NUM> send communications to and/or receive communications from the mobile device <NUM>. As the mobile device <NUM> moves about a premises, different controllable devices may drop in or out of the mesh network <NUM> as the mobile device <NUM> moves in or out of wireless communication range with the respective controllable devices in the mesh network <NUM>.

In the example, controllable Devices <NUM> to <NUM> of the first mesh network <NUM> may be BLE controllable personal and health devices, such as audio/visual entertainment systems, such as speakers or audio routing systems, wearable devices, such as health monitoring bands that may include one or more of a thermometer, a blood pressure monitor, a heart rate monitor, a pedometer, a wristwatch, small appliances, or the like. Alternatively or in addition, the BLE controllable device may be a printer or other computer peripheral device. For some BLE controllable devices, there are one or more Bluetooth standard Generic Attribute profiles (GATT) that facilitate different services to be provided by some of the BLE controllable devices.

Meanwhile, the controllable Devices <NUM> to <NUM> operating according to the ZigBee protocol in the second network <NUM> may be devices that are used for metering, monitoring and controlling large and/or small appliance-type devices within the home or premises environment. For example, a controllable, ZigBee device, such as Devices <NUM> to <NUM>, may be a smart energy meter, an electricity usage monitoring device, a water usage monitoring device, a home flooding detection device, a heating/ventilation system, an air conditioning system, a security system, a refrigerator and other appliances, a printer, a power outlet, a light, a door/window actuator, or the like.

A user of the controllable BLE devices <NUM> to <NUM> may use the mobile device <NUM> or the premises gateway (GW) <NUM> as an aggregator of BLE devices and use applications stored in either the premises GW <NUM> or a cloud server <NUM> to monitor and control the respective controllable BLE devices <NUM> to <NUM>. Similarly, ZigBee devices at home can use premises GW <NUM> as the aggregator (since mobile devices lack a ZigBee transceiver) and can use applications stored in the premises GW or a cloud server to monitor or control and monitor the ZigBee devices.

A benefit of using Bluetooth standards, in particular, the Bluetooth low energy (BLE) instead of WiFi is that BLE reduces the battery consumption of mobile device <NUM> or devices <NUM> to <NUM> in first network <NUM>, and operates on a frequency that is more robust than WiFi. In contrast, WiFi consumes more battery resources of a device, such a mobile device <NUM>, due to frequent status checking with connected devices.

The premises GW <NUM> is configured to execute customer premises equipment (CPE) software that is compatible with the ZigBee protocol. The premises GW <NUM> is configured to offer and list the controllable ZigBee Devices <NUM> to <NUM> as native BLE devices, such as controllable Devices <NUM> to <NUM> on the mobile device <NUM>. As an alternative to the mobile device <NUM>, the GW <NUM> may have a web application that causes a display of the premises GW <NUM> to present the list of controllable ZigBee Devices <NUM> to <NUM>.

The mobile device <NUM> also need not be configured to communicate via the ZigBee protocol since the GW <NUM> can translate BLE events/actions to appropriate ZigBee actions. Thus, the GW <NUM> offers ZigBee Devices <NUM> to <NUM> to the mobile device <NUM>, such that each of the ZigBee Devices <NUM> to <NUM> may be viewed as another BLE device. The mobile device <NUM> may present a limited menu of available ZigBee actions as compared to accessing the ZigBee device through a dedicated ZigBee control hub. However, the mobile device <NUM> application enables a user to associate actions with ZigBee devices based on events detected by BLE devices.

In the presented example, the GW <NUM> offers and lists the ZigBee devices in the same manner as native BLE devices on the display of the mobile device or on the display of the GW as web application, the user can control BLE devices and ZigBee devices without switching between communication/network protocol specific applications. Hence, existing web applications and/ or applications native to the mobile device <NUM> for controlling BLE devices <NUM> to <NUM> available for the mobile device <NUM> may now be used to control the controllable ZigBee devices <NUM> to <NUM>.

While the ZigBee functionality was described as being configured within the premises gateway <NUM>, the ZigBee transmitter and/or the application functionality may be configured in a dongle, such as dongle <NUM> that is connected to a port, such as a universal serial bus (USB) port, of the premises gateway <NUM>. Alternatively, the dongle <NUM> may be coupled to a mobile device <NUM> or the like and may aggregate the presence of ZigBee devices that are published to the mobile device using an application as described in the following examples.

It may be beneficial to describe the above mentioned general system capabilities in more detail with reference to several examples. As will be described with reference to <FIG>, the application user, via a mobile device <NUM> and/or the premises GW <NUM>, may communicate between the different networks without switching between communication/network protocol specific applications. The premises GW <NUM> may execute software also translates commands requesting BLE specific actions to appropriate ZigBee specific actions that are then delivered to and executed by the ZigBee device.

An example of the operation and functions of the system example of <FIG> may be described with reference to <FIG> is a flowchart of an example process for communicating within a customer premises network environment, such as that shown in <FIG>.

The process <NUM> includes launching (at <NUM>) a mesh networking protocol conversion application by a mobile device processor. The mesh networking protocol conversion application may be a web-based application or a native application executed by the mobile device processor. For example, in response to user selection of the application in a menu of applications, the mobile device processor may cause the selected application to begin execution on the mobile device. Alternatively, the mobile device as will be explained in more detail with reference to a later example may detect the occurrence of an event, such as a determination by a global positioning system (GPS) that the mobile device <NUM> is located at a premises, or that a signal was received from another device or system, such as a premises security system. Detection of these events causes the mobile device <NUM> processor (not shown in this example) to launch the application.

In addition or alternatively, when executing the application, the mobile device <NUM> may be configured to obtain access to records stored at a premises gateway, such as gateway <NUM>. The records, such as device identifiers, device profiles, device capabilities, device user preferences or the like, may relate to one or more controllable devices, such as Devices <NUM>-<NUM>, that communicate with the premises gateway <NUM> according to a mesh networking protocol. In some examples, the devices that communicate with the premises gateway are proximate to the gateway. For example, the device may be within the same room, same cabinet, same piece of furniture (e.g., an entertainment center or bookshelf) or the like. In other examples, the devices that communicate with the premises <NUM> may be located in different rooms and/or different floors of a premises some distance away from the gateway <NUM>. In addition, the controlled devices may be on the exterior of the premises.

The launched mesh networking protocol conversion application may include a user interface presented on a touchscreen display device of the mobile device (<NUM>). In a specific example with reference to <FIG>, Device <NUM> in the second network <NUM> may be a ZigBee-based power outlet that supplies electrical power to a device such as an air conditioning unit or a lighting device. The application, upon being provided with a list of devices in the second network, such as network <NUM>, may cause the display of Device <NUM> to appear as an BLE-compatible device instead of ZigBee-compatible device. In addition, the display of Device <NUM> may be enabled with a Bluetooth low energy (BLE) Generic Attribute Profile (GATT) service to thereby enable Device <NUM> to present profile information related to Device <NUM> on the mobile device display.

A list of devices, such as Devices <NUM>-<NUM>, in the second network is received by the mobile device via a wireless connection with a premises gateway, such as gateway <NUM>. The wireless connection may be a connection that is formed using infrared light, near field communication (NFC), ultrasound, WiFi, Bluetooth including BLE, or the like. The mesh network devices operate according to a mesh networking protocol and are hosted by the premises gateway device (<NUM>).

The list of mesh networking protocol controllable devices is presented on the touchscreen display with controllable devices that operate according to a wireless connectivity standard (<NUM>). For example, the presented list includes devices from a first network, such as network <NUM>, and devices from a second network, such as network <NUM>. The mobile device <NUM> may list the Device <NUM> (e.g., a Power Outlet device) from <FIG> as a BLE GATT Automation IO service capable device. In another example, the Device <NUM> may instead be listed as a BLE GATT with a vendor service. Accordingly, the mobile device may now be configured to independently list BLE devices as well as ZigBee devices and control them as supported by the application. For example, the mobile device processor considers the ZigBee device as a GATT based service device controllable via Bluetooth-compatible commands.

The mobile device processor is configured to generate commands based on user inputs. For example, in response to an input to the touchscreen display of the mobile device, the mobile device generates a wireless connectivity standard-compatible command to control at least one of the mesh networking protocol devices in the presented list of wireless connectivity standard devices (<NUM>). The mobile device outputs the command via a wireless connection with the premises gateway to cause the premises gateway device to control the at least one mesh networking protocol device (<NUM>). For example, the application user interface presented on the touchscreen display of the mobile device allows a user to input an instruction. The instruction may be in the form of an event-action structure (e.g., in response to some event, some action is performed either by the device that experienced the event or some other device assigned to respond to the event).

In response to the input to the touchscreen display the example mobile device processor assigns an event to Device <NUM>, which may be a BLE-protocol thermometer in first network <NUM>. The event may be, for example, when a specific temperature is reached such as <NUM>°F, an action may be taken by a device, such as Device <NUM>, assigned to respond to the event. In a specific example, the device assigned to take action in response to an indication of the occurrence of the event may be a ZigBee-protocol power outlet, that is connected to a thermostat or an air conditioner. In the example, the user can assign an "On" command of Device <NUM> (i.e., the ZigBee device) when Device <NUM> (i.e., the BLE device) outputs a temperature reading, for example, of more than <NUM>°F (i.e., a "temperature event"). Based on these settings made via the application user interface presented on the mobile device display, the mobile device <NUM> issues a command, addressed to Device <NUM>, to the premises gateway <NUM> in response to Device <NUM> reading a temperature exceeding <NUM>°F.

After the mobile device issues the command at step <NUM>, the premises gateway <NUM> may perform a process in response to the issued command. An example process performed by the premises gateway <NUM> is described with reference to <FIG> is a flow chart of an example process performed by a premises gateway. In <FIG>, the example process <NUM> may include a step (<NUM>) of receiving by the premises gateway <NUM> the wireless connectivity standard-compatible command. This command may be transmitted from the mobile device to the premises gateway via a wireless connection. The command may be intended for delivery to at least one of the mesh networking protocol-compatible devices presented in the list on the mobile device touchscreen.

Returning to the Device <NUM> and Device <NUM> example discussed above, the premises gateway <NUM> receives the wireless connectivity standard-compatible command issued in response to the temperature event detected by Device <NUM> from the mobile device <NUM>. Information included with the command may, for example, include an indication of Device <NUM> as the addressee of the command, an indication of the temperature reading, the source of the temperature reading, a time and/or date of the temperature reading, or the like. Based on a correspondence between the received wireless connectivity standard-compatible command and a mesh networking protocol-compatible command, at <NUM>, the example premises gateway <NUM> translates the command to output a mesh networking protocol-compatible command to the at least one mesh networking protocol device, in the case of the our example, Device <NUM>.

In an example, the received command may be a wireless connectivity standard-compatible command, such as a Bluetooth command. The premises gateway processor may translate the received command by determining a correspondence between the received wireless connectivity standard-compatible command and a mesh networking protocol-compatible command. Upon determining the correspondence, the premises gateway <NUM> outputs (at <NUM>) the corresponding mesh networking protocol command to the at least one mesh networking protocol-compatible device. Other examples and/or additional features are explained in more detail below.

The premises gateway <NUM>, for example, translates the received wireless connectivity standard-compatible formatted command into a mesh networking protocol-compatible formatted command, or determines a correspondence between the received wireless connectivity standard-compatible command and a mesh networking protocol-compatible command. The correspondence may be determined in a variety of different ways. Examples of ways to make the determination include: identifying a mesh networking protocol command by accessing a memory that corresponds to the received wireless connectivity standard-compatible command, such as by using a look-up table of various wireless connectivity standard-compatible commands that are assigned to or are linked to a corresponding mesh networking protocol-compatible command; identifying a specific field(s) in the command, reading a data value in the identified field(s), and translating the value using function to produce a value that corresponds to a value assigned to a mesh networking protocol. Other processes may be used to determine the correspondence between the wireless connectivity standard-compatible commands and the corresponding mesh networking protocol-compatible command.

The translating step in process <NUM> may further include identifying the received command as being formatted according to an Automation IO service of the Bluetooth Low Energy protocol. The received command from the Bluetooth Low Energy protocol may be converted to a ZigBee mesh networking protocol for transmission to the one or more of the ZigBee mesh networking devices, such as Device <NUM>.

In another example, the execution of the application by the mobile device <NUM> may configure the mobile device <NUM> to control both the wireless connectivity standard controllable devices, such as Devices <NUM>-<NUM> and devices <NUM> of <FIG>, via the mobile device.

In another example, the premises gateway <NUM> may also have BLE communication capability. As a result, the premises gateway <NUM> may offer ZigBee device(s), such as Devices <NUM>-<NUM> as BLE device(s) with a generic attribute (GATT) service profile. The Bluetooth-capable mobile device <NUM> may detect a BLE device proximate to the mobile device, such as Devices <NUM>-<NUM>, as well as Devices <NUM>-<NUM> (provided via the premises gateway <NUM>) seamlessly since the mobile device <NUM> is equipped with a BLE transceiver. For example, the premises gateway <NUM> offers to the mobile device <NUM> a list of device including Devices <NUM>-<NUM> and Devices <NUM>-<NUM>. Devices <NUM>-<NUM> may adhere to the second networking standard, such as ZigBee, and Devices <NUM>-<NUM> may adhere to the first networking standard, such as BLE. In this way, the Devices <NUM>-<NUM> may be discovered and controlled by the mobile device <NUM>, or any other similarly configured mobile device, that adheres to, or is BLE-compatible (i.e., the first networking standard). An application executing on the mobile device <NUM> may enable the mobile device to control both BLE devices, such as Devices <NUM>-<NUM>, and the ZigBee devices, such as Devices <NUM>-<NUM>. For example and as referenced above, the BLE GATT commands (i.e., wireless connectivity standard commands) sent by the mobile device <NUM> are received by the premises gateway <NUM>, and are routed by the premises gateway <NUM> to one or more of the ZigBee devices (e.g., Devices <NUM>-<NUM>) to affect an action (e.g., close the blinds, turn ON/OFF a light, change a thermostat setting or the like).

In another example, the premises gateway <NUM> includes a Bluetooth transceiver as well as ZigBee transmitter and/or ZigBee receiver. On a BLE interface, the premises gateway <NUM> advertises (i.e., spoofs) a ZigBee device as a BLE device with BLE GATT service. Now, a mobile device, such as device <NUM>, with BLE capability and/or stock firmware, may discover the ZigBee device advertised as a BLE device by the premises gateway <NUM> seamlessly. The mobile device <NUM> may generate commands to control some functions of the ZigBee device using any off the shelf or native application running on the mobile device <NUM>.

In another example, the premises gateway <NUM> provides the list of devices operating according to a mesh networking protocol to the mobile device <NUM>. The premises gateway <NUM> receives via a WiFi wireless (shown in another example) connection with a mobile device <NUM> a command intended for delivery to at least one mesh networking protocol-compatible device, such as Devices <NUM>' and <NUM>', presented in the list of devices. The command is formatted according to a communication protocol of a wireless network standard different from the mesh networking protocol. The received command may be translated to a command formatted according to the mesh networking protocol based on a correspondence between the received command and a mesh networking protocol command stored in a memory, such as <NUM>, <NUM> or <NUM>. The premises gateway <NUM> outputs the corresponding mesh networking protocol command to the at least one mesh networking protocol-compatible device, such as Devices <NUM>' and <NUM>'.

In some examples, the mobile device application may be agnostic to the ZigBee protocol. In addition, the premises gateway <NUM> may maintain in a memory settings, such as in the event example of Device <NUM> and Device <NUM> above, or user preference setting, premise-specific settings (e.g., after <NUM> pm or at sunrise all blinds are closed), or the like, made via the mobile device web application. The application user interface mentioned above may take various forms. It may be helpful to describe an example of a form of the application user interface with reference to the following example.

<FIG> is an example of a graphical user interface useful for controlling devices within a customer premises network. Examples of a customer premises network include networks <NUM> and <NUM> within system <NUM> as described with reference to <FIG>. The application graphical user interface (GUI) <NUM> may be a dedicated user interface of the application or it may be presented by a browser program executing on a device, such as a mobile phone, a tablet, a desktop computer, a laptop computer, notebook computer, a display screen on the premises gateway device, a monitor or television to which the premises gateway is coupled, or the like. The application may present, on the GUI <NUM>, a number of different input fields and information fields. For example, a menu <NUM> may be provided that allows a user to select a Home screen as shown in <FIG>, a tab to "Edit Devices", a tab to "Block" devices, and/or a tab for "Help. " Each of these different tabs may provide a different function that permits a user to customize the user experience.

In the home screen shown in <FIG>, the mobile device may receive an input selecting the control input "Discover Devices" <NUM> and using a premises gateway <NUM>, such as <NUM>, an aggregate listing of BLE and ZB devices may be provided. In the example, the application may be able to provide the aggregated list based on a Bluetooth GATT profile as discussed above. Once presented with the aggregate list the user is able to control and communicate with a number of devices that operate according to different communication protocols. As described above, the application enables a user to control both a Bluetooth-compatible device and a ZigBee compatible device.

The described examples enable a single device through a single application to control a number of different devices that communicate according to different and incompatible communication protocols. The application may be provided in various forms. For example, the application may be provided via the premises gateway <NUM> to the mobile device <NUM>, as a plugin from the premises gateway to an application executing on or, in the case of a web application, interacting with the mobile device, or as a stand-alone application executing on the mobile device or interacting with the mobile device, if it is a web application.

For example as mentioned above, the premises gateway <NUM> may be equipped with both a BLE transceiver and a ZigBee transceiver. On the BLE interface, the premises gateway advertises (or spoofs) a ZigBee device as a BLE device using a BLE GATT service. Most mobile devices, such as <NUM>, are equipped with BLE transceivers and the standard firmware, or a web application, an off-the-shelf or native application running on the mobile device, that enable discovery of BLE device advertisement. In some cases, the needed function may be provided via a software plugin that may be hosted on web application or native application. For example, the plugin may be one or more standard plugins, such as third-party plugins, that work with BLE devices. These plugins are executed by a browser application currently displaying the GUI <NUM> as shown in <FIG>.

In an example of a Bluetooth-equipped premises gateway <NUM>, the mobile device <NUM> detects the BLE advertisements output by the premises gateway <NUM> indicating the presence of a number of ZigBee devices, such as Devices <NUM>-<NUM>, wirelessly coupled to the premises gateway <NUM>. As a result, the mobile device <NUM> via the mesh networking protocol conversion application is able to interact with the ZigBee devices based on the advertisements from the premises gateway <NUM> by translating the BLE commands into ZigBee commands and sending them to the ZigBee devices.

The premises gateway provides a web page/application, which the user of a mobile device can access for discovering/aggregating devices that are part of a mesh network coupled to the premises gateway as well as wireless connectivity devices proximate to the mobile device within the premises. If premises gateway has a display capability, the webpage <NUM> may also be accessed via the premises gateway.

For example, when the application is executing and the GUI <NUM> is being presented, a user may select the input "Discover Devices" <NUM>. In response to the selection of the "Discover Devices" <NUM>, the application, or an application plugin, broadcasts a query that polls devices within the mesh network proximate to the premises gateway <NUM>. Compatible devices within wireless range or connected via a wired connection to the premises gateway <NUM> respond to the query. The responses may include information identifying the type of device, a device identifier, capability of device, or other information related to the respective devices both the BLE devices proximate to the premises gateway and/or the mobile device and ZigBee devices coupled to the premises gateway. As a result, information about the responding devices may be returned to the application. Using the information returned to the application, the application may generate a list of connected BLE devices and ZigBee devices. For example, the application may return information related to the ZigBee devices, such as Devices <NUM>-<NUM> as well as information related to the BLE devices, such as Devices <NUM>-<NUM>, with a BLE GATT profile.

The application GUI <NUM> may present command options such as "Switch ON" <NUM>, "Switch Off' <NUM>, or setting options such as "Set Rules" <NUM>. Of course, other options may also be presented and any of the options, such as command or settings, may have sub-options, such as user preferences, parental controls, or the like. When the devices are shown in the list on the display device, a user may select (via a touchscreen input, keystrokes or by selection with a cursor) inputs such as "Switch ON" <NUM>, "Switch Off' <NUM>, or "Set Rules" <NUM>.

In the illustrated example, only the "Switch ON" <NUM>, "Switch Off' <NUM>, or "Set Rules" <NUM> controls are shown. The following discussion describes the functions of those options in more detail. The function of the "Switch On" <NUM> control is to turn a selected device ON.

For example, Device <NUM> may be a ZigBee-compatible power outlet as mentioned in the event example above. A graphical, textual or other representation of Device <NUM> may be presented on the display device in a list of devices using the GUI <NUM>. The list includes both BLE-compatible and ZigBee-compatible devices. In this example, a user may select the representation of Device <NUM> and select the "Switch On" <NUM> control. In response, the application executing on the mobile device <NUM> delivers a BLE-formatted command to the premises gateway <NUM>. The premises gateway receives and parses the BLE-formatted command. Using information in the command, the premises gateway determines that the command is directed to a ZigBee device, in this case, Device <NUM>, wirelessly coupled to the premises gateway and is not intended for another BLE device. Using information from the parsed command, the premises gateway generates a command instructing Device <NUM> to turn ON. The command is forwarded to Device <NUM> via ZigBee for execution.

Similar to the manner for turning a device ON, a user may turn a device OFF. In one example, a user may select the representation of Device <NUM> and select the "Switch OFF" <NUM> control. In response, the application executing on the mobile device delivers a BLE-formatted command to the premises gateway <NUM>. The gateway receives and parses the BLE-formatted command. From the parsed command, the premises gateway determines that the command is directed to ZigBee Device <NUM>, The premises gateway then generates a command instructing Device <NUM> to turn OFF. The command is forwarded to Device <NUM> for execution.

In another example, a user may set rules that dictate the operation of the device. For example, a user may wish to turn ON and OFF a lamp coupled to the Device <NUM> power outlet at particular times of day. For example, the light turns ON at <NUM> pm and turn OFF at 12am. A user may select the representation of Device <NUM> and select the "Set Rule" <NUM> control. In response, the application executing on the mobile device may present the user with a preselected set of functions like Time ON, Time OFF, Group Devices and the like from which a user may make a selection. Returning to the example, the processor based on the selections generates a rule for turning Device <NUM> ON and OFF at the desired times by selecting the Time ON function input and inputting "<NUM> pm" and selecting the Time OFF function input and inputting "<NUM> am. " The application may then present an option to confirm the generated rule.

The rule may be stored in a memory of the premises gateway <NUM> or in a memory of the mobile device <NUM>. Depending upon where the rules are stored, the rules may be handled differently than the commands to perform a function. For example, if the rule is stored in a memory of the premises gateway, the command may be executed by an instance of the application executing on a premises gateway processor. For example, the application executing on the premises gateway may access the memory of the premises gateway to retrieve the stored rules. The stored rules may be formatted as BLE commands or as ZigBee commands. Based on the format of the stored rules, the application may or may not translate the stored rules. Based on the rule, the example application causes the processor to generate a command to execute the rule.

Continuing with above rule example, the application may cause the processor to generate a command instructing the Device <NUM> power outlet to turn ON, and to send the command to Device <NUM> in time for Device <NUM> to execute the command at <NUM> pm according to the rule. Using information in the rule, the premises gateway generates a command instructing Device <NUM> to turn OFF at <NUM>:<NUM> am. The command is forwarded to Device <NUM> for execution at the appropriate time.

In an example claimed in the present invention the mobile device maintains the rules. In such an example, when executing the rule, the mobile device at a time (e.g., <NUM>:<NUM> pm) delivers a BLE-formatted command to the premises gateway based on the indicated time (i.e., <NUM>:<NUM> pm) that the device is to take some action, such as turn ON. As discussed above, the premises gateway receives the BLE-formatted command and translates it into a ZigBee-formatted command for transmission to Device <NUM>. The ZigBee-formatted command is forwarded at the assigned time (i.e., <NUM> pm) to ZigBee-compatible Device <NUM> instructing Device <NUM> to Turn ON.

Similarly, when time approaches the designated turn OFF time, the mobile device <NUM> may command the gateway <NUM> to send the turn OFF ZigBee command to the device <NUM> at <NUM>:<NUM> am.

A consumer premises set top box may be viewed as an IoT premises gateway to aggregate and manage IoT use cases. Currently major low power IoT standards such as ZigBee and Bluetooth®, offer mesh networking. As mentioned above, ZigBee and Bluetooth can thus support several devices by forming a mesh network (self organizing and healing). Further, cloud applications may be used to connect devices together, thus offering meshing capability across devices. The reference to Bluetooth® includes the multiple versions under the Bluetooth standard such as Bluetooth low energy (BLE or BT Smart). While the foregoing examples primarily refer to Bluetooth and ZigBee devices, other devices that utilize different communication protocols, such as X10, KNX, and the like may also utilize the described mesh networking protocol conversion application executing on the mobile device processor, a premises gateway processor, and/or an external server (as a web application) as described above with respect to the examples of <FIG>.

It may be helpful to describe an example of a premises gateway device that is suitable for use in the above referenced examples. <FIG> is a block diagram useful for describing a premises gateway device that may be useable in a customer premises network environment, such as that shown in <FIG>. There are many possible implementations of the premises gateway <NUM> of <FIG>. In the example illustrated, Devices <NUM>' and <NUM>' may be ZigBee devices coupled in a mesh network, such as network <NUM> of <FIG>. Devices <NUM> and <NUM> may, for example, communicate according to a wireless connectivity protocol, such as Bluetooth, and may be discoverable by portable devices, such as mobile device <NUM>. According to the described examples, Devices <NUM>' and <NUM>' may also be discoverable by portable devices, such as mobile device <NUM>. The devices <NUM> and <NUM> may be a wirelessly coupled thermostat, a computer terminal, an audio/video output system or the like. In an example, a network attached storage (NAS) device <NUM>, Digital Television (DTV) receiver <NUM>, and a radio receiver <NUM> may be coupled to the premises gateway <NUM> via physical connections. The mobile device <NUM> may be coupled to the gateway <NUM> via a short-range radio frequency (RF), magnetic or optical connection (e.g. <NUM> WiFi, Bluetooth, near field communication (NFC) or infra-red (IR)), and Digital Versatile Disc (DVD) player <NUM>, may be coupled to the premises gateway <NUM> via a wired connection such as a universal serial bus (USB) cable, a FireWire cable, an Ethernet connection and/or via a short-range RF, magnetic or optical wireless connection. Each of these connections may be considered to be a separate communications channel.

The premises gateway <NUM> includes a central processing unit (CPU) <NUM>, a communication interface, <NUM>, a local network adaptor <NUM>, a television interface, <NUM>, a cable interface <NUM>, a user input/output (I/O) <NUM>, and a memory <NUM> for storing programming instructions including program instructions executable by the CPU <NUM> for converting the commands received from the portable device to the second networking standard device commands. Alternatively, the converting and other functions' program instructions may be stored as the mesh networking protocol conversion application in Apps <NUM>.

The premises gateway <NUM> communication interface <NUM> may be an interface to one or more data communication transmitters and/or transceivers for communicating within the one or more wireless networks. For example, the interface <NUM> may couple to an <NUM> or WiFi transmitter and/or receiver <NUM>, a Bluetooth transmitter and/or transceiver <NUM>, a near field communication (NFC) transmitter and/or receiver <NUM>, ZigBee transmitter and/or receiver <NUM>. The premises gateway <NUM> may be configured to operate in a third wireless network that operates according to another wireless networking standard. For example, in addition to the first and second wireless networking standards, such as Bluetooth and ZigBee network standards, described above, the premises gateway <NUM> may be configured to operate according to a third wireless networking standard, such as <NUM>.

The example Bluetooth transceiver <NUM> of the premises gateway <NUM> may be coupled to an antenna <NUM> that is configured to send and receive Bluetooth signals; the WiFi channel <NUM> may be coupled to an antenna <NUM> that is configured to send and receive WiFi signals; and the NFC transceiver <NUM> may be coupled to an antenna <NUM> that is configured to send and receive NFC signals. The premises gateway <NUM> also includes a local network adaptor <NUM> interface for local communication with consumer premises equipment (CPE) devices, such as mobile device <NUM> and Devices <NUM>' and <NUM>'. In this example, the local network adapter <NUM> is coupled to a wired/optical communication port as well as a USB port(s) <NUM> and to the WiFi channel <NUM>, the Bluetooth transceiver <NUM>, the NFC transceiver <NUM> and the ZigBee transmitter/transceiver <NUM>. In some examples, WiFi channel <NUM> may be coupled to a WiFi access point (not shown).

In addition, the ZigBee transmitter/transceiver <NUM> may be coupled to an antenna <NUM> that is configured to transmit and/or receive ZigBee signals. For example, the ZigBee transmitter <NUM> may transmit signals to ZigBee-compatible Device <NUM>' and Device <NUM>' that are configured in a home automation network or the like in the premises in which the premises gateway <NUM> is located. Devices <NUM>' and <NUM>' may communicate according to a particular communication protocol or standard, such as the ZigBee communication protocol. For example, Devices <NUM>' and <NUM>' may be ZigBee-compatible power outlets, appliances, or the like, such as Devices <NUM>-<NUM> of <FIG>. As such, the premises gateway <NUM> may act as a gateway for controlling communications within a mesh network configured with the ZigBee devices.

A user may wish to control one or more devices in a premises in which the user is located. In an example of the operation of the premises gateway <NUM>, the user of mobile device <NUM> may select an application from a menu of applications presented on a display device of the mobile device <NUM>. One of the applications in the menu may be useful to control devices in a wireless connectivity protocol network as well as devices in a mesh network as described above with reference to <FIG>. In response to the selection of the application, the processor of the example mobile device either accesses a memory of the mobile device or sends a request to the premises gateway <NUM>, to obtain the selected application. For example, the application (or an application plug-in) may be stored in the memory of the mobile device <NUM> in which case, the mobile device processor (not shown in this example) obtains the application from memory.

Upon launching of the application, the mobile device <NUM> may begin a control process as described above with reference to <FIG> and <FIG>. The control process may be substantially the same as that described above with reference to <FIG> and <FIG>. Therefore, a detailed explanation of the process steps <NUM>-<NUM> will not be repeated.

Alternatively, in response to selection of the application or the application plug-in, the mobile device <NUM> may forward a request to the premises gateway <NUM> requesting that the application or the application plug-in be delivered to the mobile device <NUM>. Upon receipt of the request, the premises gateway <NUM> may retrieve a copy or instance of the application or application plug-in from the application memory <NUM>, and deliver the application or application plug-in to the mobile device <NUM>. Alternatively, instead of application memory <NUM>, the application or application plug-in may be retrieved from the NAS device <NUM> or from storage on the cloud server (not shown in <FIG>).

In yet another alternative, the premises gateway <NUM> upon receipt of a request from the mobile device <NUM> may send a request to a web server or application server. The web server or application server may be configured to provide the services needed by the mobile device <NUM> to present a GUI, such as GUI <NUM> and a list of devices controllable by the mobile device.

The mobile device <NUM> and the premises gateway <NUM> may exchange communications via Bluetooth signals, WiFi signals or a combination of both. While the ZigBee functionality was described as being configured within the premises gateway <NUM>, the ZigBee transceiver and/or the application functionality may be configured in a dongle, such as dongle <NUM> (shown in <FIG>) that is connected to a port, such as a universal serial bus (USB) port, of the premises gateway <NUM>. Alternatively, the dongle may be coupled to a user device, such as <NUM> of <FIG>, or the like and may aggregate the presence of ZigBee devices that are published to the mobile device using an application as described above.

For example, the mobile device <NUM> may communicate directly with the dongle to request the mesh networking protocol conversion application as described with reference to <FIG> above.

The user devices may be CPE devices such as a NAS device <NUM>, a DTV receiver <NUM>, a radio receiver <NUM>, an external entertainment device <NUM> including a streaming video facility, a mobile device <NUM> or a computer <NUM>. These CPE devices can be located at or near a user's premises. In the example system, mobile device <NUM> may have wireless telecommunications capability. In <FIG>, only particular CPE devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are shown for illustrative purposes, but more or fewer can be coupled to the premises gateway <NUM>. For example, the ZigBee devices <NUM>' and <NUM>' may also be considered to be CPE devices. Each of the CPE devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>'and <NUM>' coupled to the premises gateway <NUM> uses a predetermined protocol. This protocol may be, for example, IEEE <NUM> WiFi, Universal Plug and Play Device Management (UPnP DM), IEEE <NUM> FireWire, IEEE <NUM> (e.g. WPAN), Bluetooth, Bluetooth Low Energy (BLE), ZigBee specifications, such as ZigBee RF4CE, ZigBee home automation <NUM>, and the like or other data exchange protocol. Device <NUM> may be a Bluetooth-compatible thermostat, and device <NUM> may be a Bluetooth-compatible keyboard and monitor.

The protocol may determine how information about the IoT device, such as codes indicating a particular manufacturer, model number and serial number, device capabilities (e.g., data download capabilities), device firmware versions, and/or the like may be obtained. For example, this device information may be provided <NUM>) automatically when the device is connected, or <NUM>) in response to a device discovery request provided by the premises gateway <NUM>, NAS device <NUM> or an external server (not shown). The CPU <NUM> may store the device information - either locally in the memory <NUM>, NAS device <NUM> or remotely - for use to provide user preferences or other control parameters with respect to rules established in the manner as explained above.

The processor <NUM>, for example, may be configured to communicate with one or more first networking standard-enabled premises devices, such as mobile device <NUM> of <FIG>, that is operating according to a first wireless networking standard, and respond to and send control signals from the mobile device, such as mobile device <NUM> of <FIG>. The first wireless networking standard may be a wireless connectivity standard such as a version of Bluetooth or the like. In addition, the processor <NUM> is configured to communicate with one or more second networking standard-enabled premises devices, such as Devices <NUM>' and <NUM>' operating according to the second networking standard, such as the ZigBee mesh networking protocol. The second networking standard, such as ZigBee mesh networking protocol, is incompatible for direct communication between the one or more second networking standard-enabled premises devices (e.g., Devices <NUM>' and <NUM>') and the mobile device <NUM> since the mobile device <NUM> is not configured with a ZigBee compatible transmitter.

The example premises gateway <NUM> also includes cable interface <NUM> for receiving programming and Internet protocol (IP) packets from an external content providers (not shown) and the like. The IP packets may include, for example, encapsulated MPEG transport streams. The TV interface circuitry <NUM> may include circuitry that reconstitutes selected MPEG transport streams from the IP packets and sends the MPEG transport streams to the DTV device <NUM>. The cable interface may also send and receive data over the network to/from a content server (not shown) to obtain the media content and possibly meta-data files or meta-data related instructions from the external content providers. The premises gateway <NUM> also includes circuits forming one or more processors to implement a CPU <NUM> and memory <NUM> for controlling operations of the premises gateway, including performing the processing of the IP packets, media content and mesh network/IoT commands. The memory <NUM> may include one or more memories and/or other program and data storage devices, for example, for storing instructions executable by the CPU <NUM>. For example, the memory <NUM> may include computer applications (Apps) <NUM>, such as a computer application that provides the mesh network protocol translation and/or conversion functions, command and control functions, and application GUI functions as described above.

The example premises gateway <NUM> also includes a user I/O interface <NUM>. The user I/O interface <NUM> may include an electroluminescent (EL), liquid crystal device (LCD), or light emitting diode (LED) display for displaying information to the user. The user I/O interface <NUM> may also include an infrared (IR) transceiver for transmitting and receiving instructions to and from the user's remote control or other IR capable device. Although not shown, this IR transceiver may provide a communication channel for sending and receiving short-range optical communications between the premises gateway and one or more of the CPE or mesh network devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>' and <NUM>'.

In this example, the premises gateway <NUM> includes the functionality of a set-top box (STB). It is contemplated, however, that the STB may be separate from the premises gateway. In this instance, the premises gateway provides the network connection and the STB provides the media functionality. When the STB is separate from the premises gateway <NUM>, the STB may be connected to the cable line in parallel with the premises gateway or may be connected to the premises gateway <NUM> to receive IPTV packets from the premises gateway.

<FIG> is a block diagram of an example mobile device <NUM>. The mobile device includes a touch-screen display <NUM> for displaying application screens, messages, menus or the like and for receiving input selections such as dialed numbers and web page navigation. A keypad <NUM> includes a limited number of keys that perform functions such as power-on/off, sound volume adjustments and other functions of the device.

A microprocessor <NUM> serves as a programmable controller for the mobile device <NUM>, in that it controls all operations of the mobile device <NUM> in accord with programming that it executes, for all operations. In the example, the mobile device <NUM> includes flash type program memory <NUM>, for storage of various "software" or "firmware" such as an operating system and application programs. In addition the memory <NUM> may hold mobile configuration settings, such as mobile directory number (MDN) and/or mobile identification number (MIN), etc. The mobile device <NUM> may also include a non-volatile random access memory (RAM) <NUM> for a working data processing memory.

The mobile device <NUM> further includes a microphone device <NUM>, speaker <NUM> and vocoder <NUM> for audio input and output functions. The mobile station <NUM> also includes at least one digital transceiver (XCVR) <NUM>, for digital wireless communications, such as cellular communications, and at least one or two short-range radio frequency transceivers <NUM> and <NUM>, shown in the example as a WiFi transceiver <NUM> and a Bluetooth (BT) or BLE transceiver <NUM>, respectively, to communicate with the premises gateway <NUM> via a WiFi channel <NUM> and/or Bluetooth transceiver <NUM>. The Bluetooth transceiver may also communicate with proximate Bluetooth devices, such as devices <NUM>-<NUM> in <FIG>. The transceiver <NUM> provides two-way wireless communication of information, such as vocoded speech samples and/or digital information, in accordance with the technology of the telecommunications network. Each example transceiver <NUM>, <NUM> and <NUM> connects through RF send and receive amplifiers (not separately shown) to a respective antennas <NUM>, <NUM> and <NUM>. The transceiver <NUM> may also support various types of mobile messaging services, such as short message service (SMS), enhanced messaging service (EMS) and/or multimedia messaging service (MMS) and may include a web browser for interacting with websites either through the telecommunications transceiver <NUM> or the short-range transceiver <NUM>. The BT transceiver <NUM> may interact with other Bluetooth-equipped devices.

The user interface of the exemplary mobile device <NUM> includes a display <NUM>, which the microprocessor <NUM> controls via a display driver <NUM>, to present visible outputs to the device user. The user interface also includes a touch/position sensor <NUM> that overlies the display <NUM> and is relatively transparent, so that the user may view the information presented on the display <NUM>. A sense controller <NUM> senses signals from elements of the touch/position sensor <NUM> and detects occurrence and position of each touch of the screen formed by the display <NUM> and sensor <NUM>. The sense controller <NUM> provides touch position information to the microprocessor <NUM>, which can correlate that information to the information currently displayed via the display <NUM>, to determine the nature of user input via the sensor <NUM>.

Aspects of the methods of the exemplary apparatus and method outlined above may be embodied in programming, e.g. in the form of software, firmware, or microcode executable by a user computer system, a server computer or other programmable device. Program aspects of the technology may be thought of as "products" or "articles of manufacture" typically in the form of executable code and/or associated data that is carried on or embodied in a type of machine readable medium. "Storage" type media include any or all of the tangible memory of the computers, processors or the like, or associated modules thereof, such as various semiconductor memories, tape drives, disk drives and the like, which may provide non-transitory storage at any time for the software programming. All or portions of the software may at times be communicated through the Internet or various other telecommunication networks. Such communications, for example, may enable loading of the software from one computer or processor into another, for example, from a management server or host processor into the memory <NUM> of the premises gateway <NUM>. Thus, another type of media that may bear the software elements includes optical, electrical and electromagnetic waves, such as used across physical interfaces between local devices, through wired and optical landline networks and over various air-links. The physical elements that carry such waves, such as wired or wireless links, optical links or the like, also may be considered as media bearing the software. As used herein, unless restricted to one or more of "non-transitory," "tangible" or "storage" media, terms such as computer or machine "readable medium" refer to any medium that participates in providing instructions to a processor for execution.

Hence, a machine readable medium may take many forms, including but not limited to, a tangible storage medium, a carrier wave medium or physical transmission medium. Non-transitory storage media include, for example, optical or magnetic disks, such as any of the storage devices in any computer(s) or the like. It may also include storage media such as dynamic memory, for example, the main memory of a computer platform. Tangible transmission media include coaxial cables; copper wire and fiber optics, including the wires that comprise a bus within a computer system. Carrier-wave transmission media can take the form of electric or electromagnetic signals, or acoustic or light waves such as those generated during radio frequency (RF) and light-based data communications. Common forms of computer-readable media therefore include for example: a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any other optical medium, punch cards paper tape, any other physical storage medium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave transporting data or instructions, cables or links transporting such a carrier wave, or any other medium from which a computer can read programming code and/or data. Many of these forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to a processor for execution.

Program instructions may comprise a software or firmware implementation encoded in any desired language. Programming instructions, when embodied in machine readable medium accessible to a processor of a computer system or device, render computer system or device into a special-purpose machine that is customized to perform the operations specified in the program.

It will be understood that the terms and expressions used herein have the ordinary meaning as is accorded to such terms and expressions with respect to their corresponding respective areas of inquiry and study except where specific meanings have otherwise been set forth herein. Relational terms such as first and second and the like may be used solely to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," "includes," "including," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by "a" or "an" does not, without further constraints, preclude the existence of additional identical or similar elements in the process, method, article, or apparatus that comprises the element.

The term "coupled" as used herein refers to any logical, physical or electrical connection, link or the like by which signals produced by one system element are imparted to another "coupled" element. Unless described otherwise, coupled elements or devices are not necessarily directly connected to one another and may be separated by intermediate components, elements or communication media that may modify, manipulate or carry the signals. Each of the various couplings may be considered a separate communications channel.

Claim 1:
A premises system (<NUM>), comprising:
a mobile device (<NUM>) configured to:
communicate according to a first networking protocol;
generate one or more rules, each of the one or more rules including a least a condition, and a command for a device based on the condition;
determine a condition for the one or more rules is met;
transmit a command associated with the rule for which the condition is met to the premises gateway device (<NUM>), the command formatted according to a first networking protocol;
a premises gateway device (<NUM>) including:
a processor configured to:
advertise one or more devices adhering to a second networking protocol as devices adhering to the first networking protocol;
receive, from the mobile device, the command formatted according to the first networking protocol;
translate the command associated with the rule for which the condition is met to a format according to the second networking protocol; and
a transmitter configured to transmit the translated command to the at least one device associated with the rule for which the condition is met.