Systems and methods for handling failover in a distributed routing environment

A computing device configured to implement a method for binding negotiation is disclosed. The computing device includes a processor and memory in electronic communication with the processor. A first binding has a first binding ID. Instructions are stored in the memory to implement a method for binding negotiation. The first binding is advertised on a network. A second provider is discovered to also provide the first binding with a second binding ID on the network. The computing device then determines whether it is to provide the first binding by evaluating a collision function (F). Based on the result of the collision function, either the addition of the first binding with the second binding ID is halted, or the first binding with the first binding ID is canceled.

TECHNICAL FIELD

The present invention relates generally to computers and computer-related technology. More specifically, the present invention relates to systems and methods for handling failover in a distributed routing environment.

BACKGROUND

Computer and communication technologies continue to advance at a rapid pace. Indeed, computer and communication technologies are involved in many aspects of a person's day. For example, many devices being used today by consumers have a small computer inside of the device. These small computers come in varying sizes and degrees of sophistication. These small computers include everything from one microcontroller to a fully-functional complete computer system. For example, these small computers may be a one-chip computer, such as a microcontroller, a one-board type of computer, such as a controller, a typical desktop computer, such as an IBM-PC compatible, etc.

Computers typically have one or more processors at the heart of the computer. The processor(s) usually are interconnected to different external inputs and outputs and function to manage the particular computer or device. For example, a processor in a thermostat may be connected to buttons used to select the temperature setting, to the furnace or air conditioner to change the temperature, and to temperature sensors to read and display the current temperature on a display.

Many appliances, devices, etc., include one or more small computers. For example, thermostats, furnaces, air conditioning systems, refrigerators, telephones, typewriters, automobiles, vending machines, and many different types of industrial equipment now typically have small computers, or processors, inside of them. Computer software runs the processors of these computers and instructs the processors how to carry out certain tasks. For example, the computer software running on a thermostat may cause an air conditioner to stop running when a particular temperature is reached or may cause a heater to turn on when needed.

These types of small computers that are a part of a device, appliance, tool, etc., are often referred to as embedded systems. The term “embedded system” usually refers to computer hardware and software that is part of a larger system. Embedded systems may not have typical input and output devices such as a keyboard, mouse, and/or monitor. Usually, at the heart of each embedded system is one or more processor(s).

A lighting system may incorporate an embedded system. The embedded system may be used to monitor and control the effects of the lighting system. For example, the embedded system may provide controls to dim the brightness of the lights within the lighting system. Alternatively, the embedded system may provide controls to increase the brightness of the lights. The embedded system may provide controls to initiate a specific lighting pattern among the individual lights within the lighting system. Embedded systems may be coupled to individual switches within the lighting system. These embedded systems may instruct the switches to power up or power down individual lights or the entire lighting system. Similarly, embedded systems may be coupled to individual lights within the lighting system. The brightness or power state of each individual light may be controlled by the embedded system.

A security system may also incorporate an embedded system. The embedded system may be used to control the individual security sensors that comprise the security system. For example, the embedded system may provide controls to power up each of the security sensors automatically. Embedded systems may be coupled to each of the individual security sensors. For example, an embedded system may be coupled to a motion sensor. The embedded system may power up the individual motion sensor automatically and provide controls to activate the motion sensor if motion is detected. Activating a motion sensor may include providing instructions to power up an LED located within the motion sensor, output an alarm from the output ports of the motion sensor, and the like. Embedded systems may also be coupled to sensors monitoring a door. The embedded system may provide instructions to the sensor monitoring the door to activate when the door is opened or closed. Similarly, embedded systems may be coupled to sensors monitoring a window. The embedded system may provide instructions to activate the sensor monitoring the window if the window is opened or closed.

Some embedded systems may also be used to control wireless products such as cell phones. The embedded system may provide instructions to power up the LED display of the cell phone. The embedded system may also activate the audio speakers within the cell phone to provide the user with an audio notification relating to the cell phone.

Home appliances may also incorporate an embedded system. Home appliances may include appliances typically used in a conventional kitchen, e.g., stove, refrigerator, microwave, etc. Home appliances may also include appliances that relate to the health and well-being of the user. For example, a massage recliner may incorporate an embedded system. The embedded system may provide instructions to automatically recline the back portion of the chair according to the preferences of the user. The embedded system may also provide instructions to initiate the oscillating components within the chair that cause vibrations within the recliner according to the preferences of the user.

Additional products typically found in homes may also incorporate embedded systems. For example, an embedded system may be used within a toilet to control the level of water used to refill the container tank. Embedded systems may be used within a jetted bathtub to control the outflow of air.

As stated, embedded systems may be used to monitor or control many different systems, resources, products, etc. With the growth of the Internet and the World Wide Web, embedded systems are increasingly connected to the Internet so that they can be remotely monitored and/or controlled. Other embedded systems may be connected to computer networks including local area networks, wide area networks, etc.

Some embedded systems may provide data and/or services to other computing devices using a computer network. Alternatively there may be typical computers or computing devices that provide data and/or services to other computing devices using a computer network. There may be a number of providers on the network. Sometimes providers may fail, which in turn means that the data and/or services being provided by the provider might also fail. Benefits may be realized if systems and methods were provided to handle failover in computer networks.

DETAILED DESCRIPTION

A computing device configured to implement a method for binding negotiation is disclosed. The computing device includes a processor and memory in electronic communication with the processor. A first binding has a first binding ID. Instructions are stored in the memory to implement a method for binding negotiation. The first binding is advertised on a network. A second provider is discovered to also provide the first binding with a second binding ID on the network. The computing device then determines whether it is to provide the first binding by evaluating a collision function (F). Based on the result of the collision function, either the addition of the first binding with the second binding ID is halted, or the first binding with the first binding ID is canceled.

The first binding may include an object and an interface. A service may be accessed through use of the object and the interface.

In some embodiments the collision function uses the first binding ID and the second binding ID as inputs and provides a Boolean result. Furthermore, the collision function (F) may satisfy the condition that F(A, B) is not the same as F(B, A), such that (F) satisfies the condition that if F(A, B)=True, then F(B, A)=False. In certain embodiments the collision function (F) comprises a less than function.

The instructions may implement a second method. A removal attempt is received from the network. The removal attempt is attempting to remove a second binding on a network. It is determined whether the computing device has the ability to provide the second binding. The removal attempt is allowed to continue if the computing device is not capable of providing the second binding. The removal attempt is halted, and the second binding is added to the network if the computing device is capable of providing the second binding but is not currently providing the second binding. In some embodiments the computing device is configured to implement a three-phase commit method.

The computing device may be embodied in various systems. For example, the computing device may be an embedded device that is part of a lighting control system. The computing device may be an embedded device that is part of a security system. Furthermore, the computing device may be an embedded device that is part of a home control system.

A method for binding negotiation between two or more providers is also disclosed. A first binding has a first binding ID. The first binding is advertised on a network by a first provider. A second provider is discovered to also provide the first binding with a second binding ID on the network. The first provider then determines whether it is to provide the first binding by evaluating a collision function (F). Based on the result of the collision function, either the addition of the first binding with the second binding ID is halted, or the first binding with the first binding ID is canceled.

A computer-readable medium comprising executable instructions for implementing a method for binding negotiation between two or more providers is also disclosed. A first binding has a first binding ID. The first binding is advertised on a network by a first provider. A second provider is discovered to also provide the first binding with a second binding ID on the network. The first provider then determines whether it is to provide the first binding by evaluating a collision function (F). Based on the result of the collision function, either the addition of the first binding with the second binding ID is halted, or the first binding with the first binding ID is canceled.

Various embodiments of the invention are now described with reference to the Figures, where like reference numbers indicate identical or functionally similar elements. The embodiments of the present invention, as generally described and illustrated in the Figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of several exemplary embodiments of the present invention, as represented in the Figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of the embodiments of the invention.

Many features of the embodiments disclosed herein may be implemented as computer software, electronic hardware, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various components will be described generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

Where the described functionality is implemented as computer software, such software may include any type of computer instruction or computer executable code located within a memory device and/or transmitted as electronic signals over a system bus or network. Software that implements the functionality associated with components described herein may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices.

In distributed networks there are often failures in the underlying networks that connect the system together. Typical networks solve this problem by identifying alternate routes, and switching to those routes when a failure is encountered. In addition to the failure of network components, the ultimate providers of information can also fail. In typical networks this problem is solved by having multiple “redundant” providers and using failover to switch requests between them. These two solutions usually operate on different scales—network link failures occur in the WAN environment, and failover happens in a LAN, with a dedicated piece of hardware monitoring the different systems and switching.

The present systems and methods provide the ability of have a plurality of providers of the same binding, where only one of them is actually routable at a time. The others are not active, but can become active and visible if the currently routable provider fails for any reason.

This allows for high-availability of services (providers) in a distributed system. It is also not a requirement that all potential providers be closely coupled, as is the case in many systems today.

The system includes a set of nodes that are connected in an arbitrary fashion. This set of connections can contain loops, but there is at least one route from each node to each other node. Connected to this network are requesters and providers. These may exist on separate nodes that are connected to a single node in the network, or they may run on the network node itself.

Providers add binding information into the network. Each binding is assigned a unique identifier, and may also include an object identifier and an interface identifier. Partial duplicates (meaning the object identifier and interface identifier) are allowed, but the unique identifier for the binding cannot be duplicated by another binding.

This information is propagated through the network using a distributed three-phase commit (described below). This gives any node in the network the ability to “halt” the propagation indefinitely. This same procedure is used when a link is broken and the network needs to determine a new route and also when a binding is removed from the system.

FIG. 1is a network block diagram illustrating two intervening access nodes in the network100. A provider102is in electronic communication with the network100. The network embodiment100ofFIG. 1includes two requesters104in electronic communication with the network100. The intervening access nodes106are also on the network100. There may be more nodes on the network100.

An intervening access node106is a network node that provides features and services to the network100. An intervening access node106may be used in a variety of ways. For example, an intervening access node106may be present on a network to provide services to computers, applications and/or objects on the network100. An intervening access node106may also be used to provide a protocol converter. An intervening access node106may be embedded or it106may be large enough to handle enterprise traffic.

One feature that an intervening access node106may include relates to object refinement. Object refinement refers to the situation where an intervening access node106places itself in place of an object and provides different implementations of the same interfaces. This allows, among other things, for problems in the implementation of an interface to be fixed without changing the actual end provider of the interface.

An additional feature of an intervening access node106is that of object augmentation. Object augmentation is where the intervening access node106adds new interfaces to an object that the end provider does not support.

In current design, the intervening access node106does not differentiate between clients and devices, so any service added is available to any (authorized) connected entity or node.

The network100as shown inFIG. 1may inherit many features of web services. Web services are accessed using web protocols, usually HTTP and SOAP. The architecture is based on the peer-to-peer paradigm of networking.

Multiple intervening access nodes106in communication with one another form an intervening access node network110. To requesters104and/or providers102, the one or more intervening access nodes106of the intervening access node network110appear as a single intervening access node106. The size or number included in the intervening access node network110is transparent to providers102and/or requestors104.

A provider102is a node on the network100that is the source of a service108. A requester104is a node on the network100that is the user of the service108. A requestor104is a software entity implemented on a node that may directly discover a service108to control or interact with it.

The service108may be any kind of service that may be provided by a computing device. Some possible examples of services108include providing temperature data from a location, providing surveillance data, providing weather information, providing an audio stream, providing a video stream, etc. Many different kinds of services and/or data may be provided over a computer network100from a provider102.

The service108is accessed through one or more bindings112. A binding112includes an object identifier114and an interface identifier116. Typically the object114and the interface116are in pairs. A provider102can provide a plurality of bindings112. It is possible that multiple providers102can be providing the same service108, binding112, object114or interface116. Each binding112can be represented with a unique binding ID118. The binding ID118must be unique to the intervening access node network110.

The provider102may be an embedded provider. An embedded provider is a provider102being implemented on an embedded device. An embedded device is a type of computing device that does not include all the same components associated with a typical desktop computer. For example, some embedded devices do not include monitors, others do not include a keyboard or a mouse, and some embedded devices do not include either a monitor or a keyboard/mouse. Many embedded devices are microcontroller-based devices, i.e., the central processor for the embedded device is a microcontroller.

The term “network” as used herein refers to a system in which a series of nodes are interconnected by a communications path. A node is a physical computing device that communicates with other nodes. The specific behavior of a node is determined by the applications or software it executes. Applications running on nodes of a network communicate with each other through software modules that implement protocols, formalized rules for how data is sent over a network. Some protocols deal with the timing, sequencing, and error checking of data transmission. Others deal more with how the data is formatted and the commands and responses that the nodes exchange. A set of protocols that work together is called a protocol stack, with each protocol acting as a layer in the stack that is built on top of another layer. The top layer of a protocol stack is used by an application, the middle layers deal with transferring groups (packets and frames) of data between nodes, and the bottom layer deals directly with the networking hardware that transfers data.

Physical networks consist of nodes that are connected by some sort of physical medium (e.g., electrical wire, optical fiber, air). This physical connection may sometimes be referred to as a link. A physical network limited to two nodes may be referred to as point-to-point, while a physical network that may support more than two nodes may be referred to as multiple-access. Each node on a multiple-access network has a physical address that is used to distinguish it from the other nodes on the network.

Logical networks may be superimposed onto physical networks to specify a unique group of nodes. Each node in a logical network has a logical address that is mapped by a protocol to the node's physical address. A sub-network, or subnet, is a physically or logically independent portion of a network, distinguished by a subnet number.

Most protocols deal with logical networks because most physical network issues already have many well-defined implementations and defining new physical layers is not required. Logical networks also have the benefit of being insulated from the physical network, and are therefore more generally useful. For example, TCP/IP is defined on top of a logical network (IP). IP can run on many physical networks (Ethernet, serial, wireless, etc.). This makes TCP/IP a more generic solution than had it been defined only in terms of some specific physical network.

Any number of intervening access nodes106may be used in a network100.FIG. 2illustrates a network200that includes a number of intervening access nodes206as shown. Two requesters204are in electronic communication with the intervening access nodes206. In addition, a requestor/provider205is in electronic communication with the intervening access nodes206. In the network embodiment200shown inFIG. 2, the two requesters204all request the services208being provided by the provider202. The data from the services208is sent through the intervening access node network210.

The intervening access node network210ofFIG. 2operates similarly to the intervening access node network110ofFIG. 1. In typical operation, the requesters104,204and the providers102,202, including the requestor/provider205, would not distinguish between the intervening access node network110ofFIG. 1and the intervening access node network210ofFIG. 2.FIG. 2also illustrates that a node may serve as both a requestor and a provider, as shown by the illustrated requestor/provider205. This requestor/provider205provides a service228and binding232.FIG. 2also illustrates that a service/binding may be provided by an intervening access node206e.

The intervening access nodes106,206may be connected in an arbitrary way, which includes loops. InFIGS. 1 and 2requesters104,204,205and providers102,202,205,206ewere illustrated. Requestors and providers may be separate nodes or may coexist on an intervening access node.

FIG. 3is a block diagram of a provider402with two bindings412a,412b. When the provider402connects to an intervening access node network110, it advertises its bindings412a,412bby sending out a first binding advertisement430aand a second binding advertisement430b. The first binding advertisement430anotifies whoever receives this signal that the first binding412ais available and its specific binding ID418a. The second binding advertisement430bnotifies whoever receives this signal that the second binding412bis available and its specific binding ID418b. With this information requestors can request the binding412a,412bfrom the provider402. It is also possible that the first intervening access node106,206assigns and keeps track of the binding ID418. This is possible because the provider402only needs the object114and interface116, while the intervening access node requires the unique binding ID418.

FIG. 4is a timing diagram500illustrating a three-phase commit process. The time axis501is shown. The intervening access node A502has a binding to add into the network100. At some point after connecting to the network100, at time t1, the intervening access node A502advertises530the binding. This advertisement530reaches another intervening access node, intervening access node B504. The intervening access node B504may then acknowledge505the binding at time t2. At this point the intervening access node A502is still not a potential provider for the intervening access node B504. In order to lock the intervening access node A502into providing the other intervening access node B504with the service or binding, the intervening access node A502needs to confirm532the binding with the intervening access node B504, shown at time t3. At this point, after the confirmation532, the three-phase commit process has been gone through and the intervening access node A502has committed to provide the service to the intervening access node B504. Once confirmed, the intervening access node B504may advertise the binding to any connected requestors104. Note that this final advertise does not need to use the three-phase commit process.

FIG. 5is a flow diagram illustrating a method600for signal or message propagation by an intervening access node106. Messages or signals such as the advertisement430amay be processed according to the method600shown. A message or signal is received602. Then it is determined604whether the message/signal is a duplicate by checking the unique binding ID418of the signal or message. If the signal is a duplicate, then the node acknowledges606the signal immediately.

If the signal/message is not a duplicate, then the signal/message is propagated608to all intervening access nodes106that are connected to the present node except for the node that sent the present node the signal. Then the node waits610for acknowledgement from the connected nodes that it sent the signal to. When the acknowledgements are received and/or when a timeout is reached, a confirmation is sent612to all connected intervening access nodes106. Note that this confirmation is initiated only by the original sender of the signal. It is, however, forwarded by all intervening access nodes106.

The method600as outlined inFIG. 5results in optimal behavior for intervening nodes106that may contain loops. Providers that are directly connected (coexist) on an intermediate node can use the same logic with very low overhead.

A problem may exist when multiple providers connect to the network and are providing the same binding. It is assumed in the present embodiments that it is desirable to only have one of the providers actually provide the binding, while additional providers with the same binding are held in reserve by the network and will be able to provide the binding in the future should the need arise. The three-phase commit is used in order to negotiate which of the providers will actually provide the binding. It is assumed that each provider has equal right and ability to provide the binding, and so any means of determining which should actually provide it is acceptable.

FIG. 6is a block diagram700of a network710that includes one or more intervening access nodes and two providers702a,702b. Provider A702aincludes a first binding712awith a binding ID A718a. Provider B702bincludes a first binding712bwith a binding ID B718b. Thus both providers can provide the same binding, the first binding, although they have different binding identifications718a,718b. The network710and the providers702a,702bneed to negotiate and determine which provider702will provide the binding and which one will be held in reserve to provide the binding at a later time, if necessary. This situation typically occurs when two or more providers702connect to a network710at approximately the same time such that each of the providers does not become aware of the other provider until after they have already advertised their bindings.

FIG. 7is a flow diagram illustrating one embodiment of a method800for determining which provider702will provide the binding712in the situation as illustrated inFIG. 6. The flow diagram800will be explained with respect to provider A702afor the sake of explanation. However, it will be appreciated that this same method is followed in the present embodiment by provider B702bas well. Provider A702aconnects802to the network710. Then provider A702aadvertises804its first binding712awith its unique binding ID718a. At approximately the same time provider B702bconnects to the network710and advertises its first binding712bwith its unique binding ID718b. Both providers have begun the distributed three-phase commit process.

During the process of the distributed three-phase commit, provider A702abecomes aware806of provider B702band specifically becomes aware that provider B702bis trying to provide the same first binding712. Provider A702amay become aware of this, by way of example, when it receives the advertisement from provider B702b. Provider A702athen determines808whether or not it will provide the first binding712a. This is achieved by evaluating a collision function (F) that takes as input (1) the binding ID718aof provider A702aand (2) the binding ID718bof provider B702b. If the result810is true, then provider A702ahalts812the addition of provider B702bby not sending the expected acknowledgement to provider B702b. If the result is false, then provider A702acancels814its own addition. Provider A702amay cancel its own addition in a number of ways including, but not limited to, sending out a cancellation message or by simply not confirming any bindings and thus not completing the three-phase commit with any other nodes.

Once this method800has been accomplished by the providers702a,702b, only a single binding will be active. The alternate provider (the provider with the binding being held in reserve) remains present. If the current provider removes the binding for any reason, these “alternate” providers “halt” the removal while they add the same binding (using the process described above), and then they allow the removal to continue. This allows for failover from one provider to another. This process is described below in relation toFIG. 8.

In the disclosed embodiments, the collision function (F) satisfies the following conditions: (1) F results in a Boolean (true/false) result, and (2) F(G1,G2) is the opposite of F(G2,G1). The first condition simply means that when F is evaluated it will provide either a true or false result. The second condition means that the collision function will not give the same result if the parameters are the same but in a different order. For example, F(G1,G2)=F(G1, G2), but F(G1,G2) gives the opposite result as F(G2,G1). With these conditions it is important that any provider consistently place its own binding ID (e.g., G1) first in the parameters for the collision function. Alternatively, any provider may consistently place its own binding ID (e.g., G1) second in the parameters for the collision function. Because the order of the parameters is important, the providers need to consistently apply the same rules when passing parameters to the collision function. One example of F would be a “less than” comparison. If the binding ID718awere 6,000, and the binding ID718bwere 10,000, and if F were a less than comparison, then F(6,000,10,000) would provide a true result because 6,000<10,000. In addition, F(10,000, 6,000) would yield a false result because 10,000 is not less than 6,000.

FIG. 8is an embodiment of a method900for allowing for failover from one provider to another. Assuming the context show inFIG. 6and that the method ofFIG. 7has been executed such that only one provider, provider A702ais actively providing the binding712a. Provider A702aattempts to remove902the binding712afrom the system. For example, perhaps provider A702ais going offline or is malfunctioning and unable to continue operation. When provider B702breceives904the removal, it checks to determine906whether it can provide the same binding. If it cannot provide the same binding, then the removal of the binding continues908. In this situation, provider B702bdoes have the first binding712band, as a result, it can provide the same binding (i.e., the first binding). Provider B702bthen halts910the removal of the first binding. Provider B702balso adds912the first binding712bto the system or network using the process described above. Provider B702bfinally allows914the removal of the first binding712ato continue. Provider B702bthen begins providing the first binding712bwith its binding ID B718b, while the first binding712awith a binding ID A718ais removed. This allows for failover from one provider to another.

FIG. 9is a flow diagram of an embodiment of a method1000of a requester104establishing a service communication link with a provider102. The requestor104connects1002to the network100. Then the requestor104may request1004a list of bindings from the intervening access node(s)106. Using the list of bindings, the requestor is able to determine what service it needs and it requests1006the service from a provider102. The intervening access node network110,210communicates1008the request from the requestor104to the provider102.

FIG. 10is a block diagram of hardware components that may be used in an embodiment of an embedded device which may be used as either an embedded provider or as an embedded requester.

A CPU1110or processor may be provided to control the operation of the embedded device1102, including the other components thereof, which are coupled to the CPU1110via a bus1112. The CPU1110may be embodied as a microprocessor, microcontroller, digital signal processor or other device known in the art. The CPU1110performs logical and arithmetic operations based on program code stored within the memory1114. In certain embodiments, the memory1114may be on-board memory included with the CPU1110. For example, microcontrollers often include a certain amount of on-board memory.

The embedded device1102may also include a network interface1116. The network interface1116facilitates communication between the embedded device1102and other devices connected to the network100. The network100may be a pager network, a cellular network, a global communications network, the Internet, a computer network, a telephone network, etc. The network interface1116operates according to standard protocols for the applicable network100.

The embedded device1102may also include memory1114. The memory1114may include a random access memory (RAM) for storing temporary data. Alternatively, or in addition, the memory1114may include a read-only memory (ROM) for storing more permanent data, such as fixed code and configuration data. The memory1114may also be embodied as a magnetic storage device, such as a hard disk drive. The memory1114may be any type of electronic device capable of storing electronic information.

The embedded device1102may also include communication ports1118, which facilitate communication with other devices. The embedded device1102may also include input/output devices1120, such as a keyboard, a mouse, a joystick, a touchscreen, a monitor, speakers, a printer, etc.

The present systems and methods may be used in several contexts.FIG. 11illustrates one embodiment of a system wherein the present systems and methods may be implemented.FIG. 11is a block diagram that illustrates one embodiment of a lighting system1200that includes a lighting controller system1208. The lighting system1200ofFIG. 11may be incorporated in various rooms in a home. As illustrated, the system1200includes a room A1202, a room B1204, and a room C1206. Although three rooms are shown inFIG. 11, the system1200may be implemented in any number and variety of rooms within a home, dwelling, or other environment.

The lighting controller system1208may monitor and control additional embedded systems and components within the system1200. In one embodiment, the room A1202and the room B1204each include a switch component1214,1218. The switch components1214,1218may also include a secondary embedded system1216,1220. The secondary embedded systems1216,1220may receive instructions from the lighting controller system1208. The secondary embedded systems1216,1220may then execute these instructions. The instructions may include powering on or powering off various light components1210,1212,1222, and1224. The instructions may also include dimming the brightness or increasing the brightness of the various light components1210,1212,1222, and1224. The instructions may further include arranging the brightness of the light components1210,1212,1222, and1224in various patterns. The secondary embedded systems1216,1220facilitate the lighting controller system1208to monitor and control each light component1210,1212,1222, and1224located in the room A1202and the room B1204.

The lighting controller system1208might also provide instructions directly to a light component1226that includes a secondary embedded system1228in the depicted room C1206. The lighting controller system1208may instruct the secondary embedded system1228to power down or power up the individual light component1226. Similarly, the instructions received from the lighting controller system1208may include dimming the brightness or increasing the brightness of the individual light component1226.

The lighting controller system1208may also monitor and provide instructions directly to individual light components1230and1232within the system1200. These instructions may include similar instructions as described previously.

FIG. 12is an additional embodiment of a system wherein the present systems and methods of the present invention may be implemented.FIG. 12is a block diagram illustrating a security system1300. The security system1300in the depicted embodiment is implemented in a room A1302, a room B1304, and a room C1306. These rooms may be in the confines of a home or other enclosed environment. The system1300may also be implemented in an open environment where the rooms A, B and C,1302,1304, and1306respectively represent territories or boundaries.

The system1300includes a security controller system1308. The security controller system1308monitors and receives information from the various components within the system1300. For example, a motion sensor1314,1318may include a secondary embedded system1316,1320. The motion sensors1314,1318may monitor an immediate space for motion and alert the security controller system1308when motion is detected via the secondary embedded system1316,1320. The security controller system1308may also provide instructions to the various components within the system1300. For example, the security controller system1308may provide instructions to the secondary embedded systems1316,1320to power up or power down a window sensor1310,1322and a door sensor1312,1324. In one embodiment, the secondary embedded systems1316,1320notify the security controller system1308when the window sensors1310,1322detect movement of a window. Similarly, the secondary embedded systems1316,1320notify the security controller system1308when the door sensors1312,1324detect movement of a door. The secondary embedded systems1316,1320may instruct the motion sensors1314,1318to activate the LED (not shown) located within the motion sensors1314,1318.

The security controller system1308may also monitor and provide instructions directly to individual components within the system1300. For example, the security controller system1308may monitor and provide instructions to power up or power down to a motion sensor1330or a window sensor1332. The security controller system1308may also instruct the motion sensor1330and the window sensor1332to activate the LED (not shown) or audio alert notifications within the sensors1330and1332.

Each individual component comprising the system1300may also include a secondary embedded system. For example,FIG. 12illustrates a door sensor1326including a secondary embedded system1328. The security controller system1308may monitor and provide instructions to the secondary embedded system1328in a similar manner as previously described.

FIG. 13is a block diagram illustrating one embodiment of a home system1400. The home system1400includes a home controller1408that facilitates the monitoring of various systems such as the lighting system1200, the security system1300, and the like. The home system1400allows a user to control various components and systems through one or more embedded systems. In one embodiment, the home controller system1408monitors and provides information in the same manner as previously described in relation toFIGS. 11 and 12. In the depicted embodiment, the home controller1408provides instructions to a heating component1424via a secondary embedded system1420. The heating component1424may include a furnace or other heating device typically found in resident locations or offices. The home controller system1408may provide instructions to power up or power down the heating component1424via the secondary embedded system1420.

Similarly, the home controller1408may monitor and provide instructions directly to a component within the home system1400such as a cooling component1430. The cooling component1430may include an air conditioner or other cooling device typically found in resident locations or offices. The central home controller1408may instruct the cooling component1430to power up or power down depending on the temperature reading collected by the central embedded system1408. The home system1400functions in a similar manner as previously described in relation toFIGS. 11 and 12.

There are many types of embedded devices and many reasons for creating device networks. Several examples of device networking applications will be set forth. It will be appreciated by those skilled in the art that the examples discussed are not exhaustive.

One example of a device networking application is remote monitoring. Many useful device networks involve remote monitoring, the one-way transfer of information from one node to another. In these applications, providers typically act as small servers that report certain information in response to a requestor. Providers can also be set up to publish their state information to subscribers. A requestor may ask for periodic reports or for updates whenever the state changes, perhaps with some means of limiting how often updates are to be sent. Providers can be set up to notify requestors when some event or exceptional condition occurs.

Another example of a device network application is remote control, where requesters are able to send commands to providers to invoke some specific action. In most cases, remote control involves some sort of feedback.

A still further example of a device networking application is distributed control systems. The functions and data associated with individual providers can be combined and coordinated through a network to create a distributed system that provides additional value. Sometimes these distributed control systems can be established more or less automatically. In many cases, a more sophisticated device joins a peer-to-peer network to perform configuration, monitoring or diagnostic duties. Such systems may be created by objects that communicate as peers or through a master-slave configuration, in which each object in the system communicates with a single, central node that contains all of the control logic.

With each category of networking application, there are a variety of ways in which requestors may connect to providers. When a relatively small number of providers are involved, a requestor may use a web browser, pager or even a WAP-enabled cell phone to communicate with a provider in a more or less interactive manner. As the number of providers grows, however, these methods may become unworkable and requestors may employ more general data management techniques such as a spreadsheet or database application.

As a variety of networks are implemented over time and with different technologies, the situation can arise in which multiple networks might sit in the same home or facility, each using their own protocols and unable to communicate with the others. In this case the various networks and protocols can be bridged to create a single, larger network. This can allow a single application to access each provider, simplifying the interaction with all of the providers.