MXPA06004256A - Home automation system including plurality of wireless sensors and a portable fob with a display - Google Patents

Abstract

A home wellness system includes a headless base station having a first wireless communication port, a portable fob having a second wireless communication port, a user input device and a display, and plurality of sensors. Each of the sensors senses information and includes a third wireless communication port, which sends the sensed information to the first wireless communication port of the headless base station. The headless base station sends the sensed information for one, some or all of the sensors from its first wireless communication port to the second wireless communication port of the portable fob. The portable fob displays the sensed information for one, more or all of the sensors at its display.

Description

RESIDENTIAL SYSTEM INCLUDING A PORTABLE FALTRIQUERA HAVING A SCREEN Cross Reference to Related Requests This application relates to the patent applications assigned to the same assignee as follows: United States Patent Application Serial No. 10 / 686,179, filed October 15, 2001, - entitled "Home System Including A Portable Fob Having A Rotary Menu And A Display "(Residential System that includes a Faltriquera Portable that has a rotary menu and a screen); And U.S. Patent Application Serial No. 10 / 686,016, filed October 15, 2003, entitled "Home System Including a Portable Fob Mating With System Components" (Residential System Including a Portable Pouch Combining with Components of the System) . Background of the Invention Field of the Invention This invention relates generally to residential systems and, more particularly, to residential systems employing sensors and wireless communications, such as, for example, a wireless local area network (WLAN), or a wireless, low-rate personal area network (LR-WPAN). Background Information Wireless communication networks are a new emerging technology that allows users to access information and services electronically, regardless of their geographical position. All nodes in ad-hoc networks are potentially mobile and can be dynamically connected in an arbitrary manner. All the nodes of these networks behave as routers and take part in the discovery and maintenance of routes to other nodes in the network. For example, ad-hoc networks are very useful in emergency search and rescue operations, meetings or conventions in which people want to quickly share information, and in data acquisition operations in inhospitable terrain. An ad-hoc mobile communications network comprises a plurality of mobile hosts, each of which is capable of communicating with its neighboring mobile hosts, which are only one step away. In such a network, each mobile host acts as a router to redirect information packets from one mobile host to another. These mobile hosts communicate with each other over a wireless medium, typically without any unstructured network component support (or cabling). One type of ad-hoc routing protocol on demand is Dynamic Source Routing (DSR). A conventional DSR network allows communications between any device in such a network by discovering communication routes to other devices in the network. See, for example, Johnson et al., "Dynamic Source Routing in Ad Hoc Wireless Networks," Mobile Computing, 1996. Dynamic Source Routing for mobile communications networks allows periodic route announcements because route caches are used for store source routes that a mobile host has learned over time. A combination of point-to-point routing and transmission using the connection-oriented packet re-address approach is used. Routes are started at source and discovered through a route discovery protocol. With source routing, the sender explicitly lists the route in the header of each packet, so that the nodes in the next step are identified as the packet moves to the destination. Cached route information is used and precise updates of these route caches are essential, otherwise closed circles may occur. Since the sender has to be notified each time a route is truncated, the route maintenance phase does not support rapid route reconstruction. See, also, patents US 6,167,025; 6,034,961; and 5,987,011. The DSR protocol attaches a complete list of addresses from the source to the destination for both upstream and downstream communications (ie, bi-directional). That is, each device in a DSR network knows the entire path to another device, although this stored path can change dynamically. In addition to DSR, examples of routing protocol algorithms include Ad-hoc Demand Distance Vector (AODV) and pro-active source routing (PSR). In a PSR routing technique, the Network Coordinator (NC) attaches a complete list of addresses from that source to the destination Network Device (ND) for downstream communications (from NC to ND). For multipath downstream communications, the receiving and repeated ND removes its address from this address list from that ND to the next or destination ND. For upstream communications (to the NC from the ND), the originating ND appends its address in the original message to an upstream node. For multi-step upstream communications, the receiving and repeated ND append its address to the address list from that DN to the next upstream DN or NC. In contrast to wired networks, wireless personal area network wireless networks - low rate (LR-WPAN), mesh type networks, are intended to be relatively low energy, self-configured, and do not require no communications infrastructure (eg, cables) other than energy sources. Residential systems (eg, residences, houses, apartments) for monitoring, security, and automation (control) are well known.

A common type of individual home sensor is the conventional smoke detector, which typically uses an audible signal to alarm and a blinking light (eg, an LED) as a normal condition monitor. There is a family of such individual sensors including, for example, door audible alarms. The relatively low energy radio frequency (RF) lighting control systems employ battery-operated, RF-mounted "wall switch" sensors. Such a sensor sends a signal to a remote power control device, such as a relay, in order to turn on and off one or more lights in the house. Unlike individual devices, an RF sensor device allows your sensor to be connected to a remote controller or monitor. A simple example of this is the automatic garage door opener. In this example, the "sensor" is a button on a car. When the button is pressed, this causes the garage door to open or close. A known mechanism for associating a particular sensor with a given controller may involve pushing a button on the sensor while also pushing a button on the controller. This process usually requires two people. It is known to provide a sensor system in which a plurality of sensors are connected, either directly with cables or indirectly with RF communications, to a central control and a monitoring device. An example of such a sensor system is a security system, which may include a telephone line for dialing outward / inward communications. A known residential security system combines wired and RF sensors with a central base station having a keyboard and a screen. The RF sensors transmit to the base station. A bit like the manual or keychain RF remote controls used to close / open a car's doors, a RF key fob is used to arm / disarm the system. The key flap only transmits and sends a one-way command to the base station. The key pouch does not receive any feedback / confirmation, and does not receive or display any information from the system. The base station does not employ a third-party remote monitoring service provider, but it can be programmed to dial one or more telephone numbers which are selected by the residential owner. There is room for improvement in residential systems. SUMMARY OF THE INVENTION These and other needs are met by means of the present invention, which provides a residential system in which a server, such as a headless base station, wirelessly sends detected information to one or more sensors to a portable pouch. . The portable pouch includes a screen to display information detected for one, more or all the sensors of the system. As an aspect of the invention, a residential system comprises: a server including a wireless communications port first; a portable pouch including a second wireless communications port, a user input device and a screen; and a plurality of sensors, each of the sensors sending information and including a third wireless communications port, which sends the detected information to the wireless communications port first of the server, the server sending the detected information to at least one of the sensors from the first wireless communication port of the served to the second wireless communication port of the portable pouch, the portable pouch displaying the detected information for at least one of the sensors on the screen of the portable pouch. The screen of the portable pouch can include a graphic capacity. The screen of the portable pouch can include a plurality of graphic objects, and the user input device of the portable pouch can be a single rotary switch, which is used to select one of the graphic objects on the screen. The selection can be provided by pushing the rotary switch. The screen of the portable pouch can include a plurality of representations of at least some of the sensors. The user input device of the portable pouch can select one of the representations. The screen of the portable pouch can display in response the information detected for a corresponding one of the sensors. The server can be a base station without a head. The server can be a network coordinator for the sensors and the portable pouch. Brief Description of the Drawings A full understanding of the invention can be obtained from the following description of the preferred embodiments when read in conjunction with the accompanying drawings, in which: Figure 1 is a block diagram of a system of residential welfare according to the present invention; Figure 2A is a block diagram of the base station of Figure 1; Figure 2B is a block diagram of a base station according to another embodiment of the invention; Figure 3 is a block diagram of the pouch of Figure 1, Figures 4A and 4B are block diagrams of two of the sensors of Figure 1, Figures 5A-5E are examples of screens used by the pouch for monitor the sensors of figure 1; Figure 5F is a simplified plan view of the pouch of Figure 1; Figure 5G is a block diagram of the screen of the pouch of Figure 5F; Figures 6A and 6B are examples of deployment sequences used by the pouch to configure the base station and the sensors, respectively, of Figure 1; Figures 7A-7C are message flow diagrams showing the interaction between the pouch, the base station and the sensors for monitoring the sensors and sending data to the base station of Figure 1; Figures 8A-8B are message flow diagrams showing the interaction between one of the sensors and the base station of Figure 1 to monitor that sensor; Figures 9A and 9B are message flow diagrams showing the interaction between the pouch, one of the sensors and the base station of Figure 1 for configuring the pouch and the sensor, respectively; Fig. 10 is a block diagram of a PDA associated with the base station of Fig. 1 and its corresponding display screen; Figures 11 and 12 are plan views of a headless base station and a portable pouch according to another embodiment of the invention; Figures 13 and 14 are plan views of a sensor and a portable pouch according to another embodiment of the invention; Fig. 15 is an isometric view of the portable pouch being mated with the sensor of Fig. 12; Figure 16 is a plan view of a sensor and a portable pouch according to another embodiment of the invention; Figures 17A-17C are plan views of a system component and a portable pouch according to another embodiment of the invention. Description of Preferred Forms of Realization As used herein, a residential welfare system shall expressly include, but is not limited to, a system for monitoring and / or configuring aspects of a residence, such as, for example, residential sensors. As used herein, the term "wireless" will expressly include, but not be limited to, radio frequency (RF) wireless communications, infrared, wireless area networks, IEEE 802.11 (e.g., 802.11a; 802.11b; 802. llg), IEEE 802.15 (e.g., 802.15.1; 802.15.3, 8802.15.4), other wireless communication standards, DECT, PWT, pager, PCS, Wi-Fi, Bluetooth, and cellular. As used herein, the term "portable wireless communication device" will expressly include, but not be limited to, any portable communications device having a wireless communications port (e.g., a portable wireless device; a personal computer (PC) portable, a personal digital assistant (PDA)). As used herein, the term "pouch" will expressly include, but not be limited to, a portable wireless handheld communication device; a wireless network device; an object that is carried directly or indirectly by a person; an object that is placed in or attached to a domestic object (eg, a refrigerator, a table); an object that is coupled to or carried by a personal object (eg, a purse, a wallet, a credit card holder); a portable object; and / or a hand object. As used herein, the term "user input device" will expressly include, but not be limited to, any suitable transducer (e.g., a rotary encoder, a joystick, a micro-lever). of control; a touch-sensitive pad, which emulates a rotary encoder; a commercial OEM VersaPad entry pad! - by Interlink Electronics, Inc., of Camarillo, California, United States), which collects an entry from the user by direct physical manipulation, with or without employing any moving part (s), and which converts such input, either directly or indirectly, through a processor and / or an associated converter, into a corresponding digital form.

As used herein, the term "rotary menu" will expressly include, but not be limited to, a menu or list of names, icons, graphic identifiers, values and / or other displayed objects, which forms a circular menu having no beginning or end, a circular list having no beginning or end, a menu having a beginning and an end in which the beginning and / or end of the menu do not need to be displayed at any time, or a list having a beginning and an end in which the beginning and / or end of the menu do not need to be displayed at any time. As used herein, the term "network coordinator" (NC) will expressly include, but not be limited to, any communications device, which operates as the coordinator for devices that wish to join a communications network and / or as a central controller in a wireless communications network. As used, the term "network device" (ND) will expressly include, but not be limited to, any communications device (e.g., a portable wireless communication device; a pouch; a fixed communications device; wireless, such as, for example, switch sensors, motion sensors or temperature sensors as used in a wirelessly enabled sensor network), participating in a wireless communications network, and not being a network coordinator .

As used herein, the term "node" includes NDs and NCs. As used herein, the term "headless" means without any user input device and without any display device. As used herein, the term "server" will expressly include, but not be limited to, a "headless" base station; and / or a network coordinator. Figure 1 is a block diagram of a residential, wireless comfort system 2. System 2 includes a "headless" RF base station 4, a portable RF pouch or "house key" 6, a plurality of RF sensors , such as 8, 10, 12. The base station RF 4 can include a suitable link 14 (eg, telephone, DSL; Ethernet) to the Internet 16 and, thus, to a web server 18. The sensors 8, 10, 12, may include, for example, the analog sensor 8, the digital on / off detector 10, and the sensor 12. The sensors 8, 10, 12, the base station 4 and the pouch 6 all use RF communications of relatively short distance, relatively very low energy. These components 4, 6, 8, 10, 12 form a wireless network 20 in which the ID node for each of such components is unique and is preferably stored in a suitable non-volatile memory, such as an EEPROM (single memory). programmable reading, capable of erasing), in each of such components.

The base station 4 (e.g., a wireless web server, a network coordinator) can collect data from sensors 8, 10, 12 and "voce", or otherwise send an RF alert message, to the pouch 6 in the event that a critical state changes in one or more of such sensors. The pouch 6 can be used both as a portable monitor at home for the various sensors 8, 10, 12 and, also, as a portable configuration tool for the base station 4 and such sensors. The example base station 4 is headless and does not include a user interface. Sensors 8, 12 preferably do not include a user interface, although some sensors may have a status indicator (e.g., an LED (light emitting diode) 116 of Figure 4A). The functions of the user interface are provided by the pouch 6, as will be discussed in more detail below. As shown with the device 12, the network 20 preferably employs a multi-hop capability, ad hoc, in which the sensors 8, 10, 12 and the pouch 6 do not have to be within the range of the base station 4 , in order to communicate. Figure 2A shows the base station 4 of the figure 1. The base station 4 includes a suitable first processor 22 (e.g., PIC model 18F2320, commercialized by Microchip Technology Inc., of Chandler, Arizona, United States), having the RAM 24 and a second radio processor or RF 26, suitable, having RAM (random access memory) 28 and PROM (programmable read only memory) 30 The first and second processors 22, 26 communicate through a suitable serial interface (eg, SCI, SPI) 32. The second processor 26, in turn, employs an RF (RX / TX) transceiver 34. having an external antenna 36. As shown with the processor 22, the various components of the base station receive power from a suitable AC / DC power source 38. The first processor 22 receives inputs from a timer 25 and a program switch 42 (e.g., which detects pairing or linkage with the pouch 6 of Figure 1). The EEPROM memory 40 is used to store the unique ID of the base station 4 as well as other non-volatile information such as, for example, the unique IDs of other components, which are part of the wireless network 20, and other information related to the configuration. The second processor 26 may be, for example, a CC1010 RF transceiver, marketed by Chipcon AS of Oslo, Norway. The processor 26 incorporates a suitable microcontroller core 44, the very low energy RF transceiver 34, and hardware DES encryption / decryption (not shown). Figure 2B is a block diagram of another base station 46. The base station 46 of Figure 2A is similar to the base station 46 of Figure 2B, except that it also includes one or more interfaces 48, 50, 52 with a personal computer (PC) (not shown), a telephone line (not shown) and a network, such as an Ethernet local area network (LAN) (not shown). In this example, the PIC processor 22 communicates with a local PC through a suitable RS-232 48 interface and the Jl connector, with a telephone line through a suitable modem 50 and the J2 connector, and with an Ethernet LAN through an Ethernet port 52 and connector J3. Thus, the modem 50 can facilitate communications with a remote cellular phone, another portable electronic device (e.g., a PDA (not shown)) or remote service provider (not shown), and the Ethernet port 52 can provide communications with Internet 16 of Figure 1 and, thus, with a remote PC or other client device (not shown). Figure 3 is a block diagram of the pouch 6 of Figure 1. The pouch 6 includes a first suitable processor 54 (e.g., PIC) having RAM 56 and a second radio or RF processor 58 having RAM memory 60 and PROM memory 62. The first and second processors 54, 58 communicate through a suitable serial interface (eg, SCI, SPI) 64. The EEPROM memory 72 is used to store the unique ID of the pouch 6. as well as other non-volatile information. For example, there may be a non-volatile storage for icons, character sets / typography and sensor labels (eg, base station 4 sends a message indicating that a sensor or on / off device is ready to be configured, and the pouch 6 consults the sensor or device on / off and finds a pre-defined list of names to choose from). This speeds a relatively fast interaction. The pouch 6 can also employ a short-term memory cache (not shown) that is used when the pouch 6 is outside the range of the base station 4. This stores the list of known sensors and devices and their last two states. This allows the user, even if far away, to check, for example, which door was open, when the pouch 6 was last in range. The second processor 58, in turn, employs an RF (RX / TX) transceiver 66 having an external antenna 68. As shown with the processor 54, the various components of the pouch 6 receive energy from a battery 70. The first processor 54 receives inputs from a timer 55, a suitable proximity sensor, such as the sensor / base program switch 74 (e.g., that detects pairing or pairing with one of the sensors 8, 10, 12 or with the base station 4 of Figure 1), and a user input device, such as, for example, the exemplary encoder 76 or the switch / selector rotating, such as a thumb wheel encoder. The first processor 54 also outputs to a suitable screen 78 (e.g., a 120 x 32 liquid crystal display), one or more visual alerts, such as a red retro-light 80 (e.g., an alert is present) and a green retro-light 82 ( e.g., an alert is not present) for screen 78, and an alert device 84 (e.g., an appropriate audible, visual or vibrating device that provides, for example, a sound, a tone, a squeak , a vibration or a twinkling light). The program switch 74 can be, for example, a Panasonic ESE-24MH1T two-pole detector switch or a Panasonic EVQ-11U04M pole micro switch. This program switch 74 includes an externally pivotable or linear actuator (not shown), which can be leveraged in one of two directions (eg, pivoted clockwise and counterclockwise; inside and outside), in order to close one of one or two normally open contacts (not shown). Such a two-pole detector is advantageous in applications in which the pouch 6 is slid to link to the sensor 12 or the base station 4, as discussed below with reference to figures 11 and 12. Therefore, monitoring one of these contacts, when the pouch 6 is slid in a linear direction (eg, without limitation, from right to left in figure 12), the corresponding contact is closed momentarily, without concern for the over-displacement of the surface corresponding linkage (not shown). Similarly, by monitoring the other of those contacts, when the phantom 6 is slid in the other linear direction (e.g., without limitation, from left to right in Figure 12), the corresponding contact is closed momentarily and another suitable action can be taken (eg, a diagnostic function, an appropriate action in response to removal of the pouch 6, a removal of a component from the network 20, an indication to enter a different configuration or mode of march). Although a physical switch 74 is disclosed, an "optical" switch (not shown) may be employed, which is activated when the pouch 6, or portion thereof, "breaks" an optical beam when paired with another system component. Alternatively, any suitable device or sensor can be used to detect that the pouch 6 has properly linked or is next to another component of the system, such as the base station 4 or the sensors 8, 10, 12 of Figure 1 The encoder 76 may be, for example, a serial encoder AEC11BR sold by CUI Inc., of Beaverton, Oregon, United States. Although the encoder 76 is shown, any suitable user input device (e.g., rotary switch and push button combined, touch sensitive pad, joystick button) may be employed. Although the warning device 84 is displayed, any suitable annunciator (e.g., an audible generator to generate one or more audible tones to alert the user of one or more corresponding state changes; a vibration generator to alert the user by the sense of touch; a visual indicator such as, for example, an LED indicator to alert the user of a corresponding state change). Screen 78 preferably provides both continuous alerts to the user and optional information messages. Figures 4A and 4B are block diagrams of the digital (discrete) on / off sensor 10 and the analog sensor 8, respectively, of Figure 1. Each of the sensors 8, 10 includes an RF transceiver (RX / TX RF) 86 having an external antenna 88, a battery 90 for driving the various sensor components, a suitable processor, such as a microcontroller (μC) 92 or 93 having RAM 94, ROM 96, a stopwatch 98 (e.g., in order to provide, for example, a periodic activation of the corresponding μC 92 or 93, in order to periodically send status information of the device or sensor back to the base station 4 of Figure 1) and another memory (e.g., EEPROM 100 including the unique ID 102 of the component that is stored there during manufacturing), and a sensor program switch 104 for pairing with the pouch program switch 74 of Figure 3. The digital (discrete) on / off sensor 10 includes a discrete physical input interface 106 (e.g., an on / off detector, an open / closed detector, a water detector, a motion detector) with the μC 92 employing a discrete input 108, while the analog sensor 8 includes an interface of physical analog input 110 (eg, temperature sensor having an analog output, a light sensor or photo-sensor having an analog output) with μC 93 using an analog input 112 and an analog-to-digital converter (ADC) corresponding 114. The sensor 10 of Figure 4A includes a suitable indicator, such as an LED 116, for outputting the status of the physical discrete input interface 106 (e.g., illuminated LED for on; LED not illuminated for off) . Sensor 8 of Figure 4B does not include an indicator. It will be appreciated, however, that the sensor 10 does not need to employ an indicator and that the sensor 8 can employ an indicator (e.g., to show that the battery 90 is good, to show that the analog value of the ADC 114 is within of an acceptable range of values). Figures 5A-5E are example screens 120, 122, 124, 126, 128 employed by the pouch 6 to monitor various sensors, such as 8, 10, 12 of Figure 1. According to an important aspect of this form of In the embodiment, the pouch screen 78 of FIG. 3 provides a rotary menu 130 of information 131, which monitors the base station 4 from the various sensors. As shown in Figure 5A, such sensors may be associated with various sensor names such as, for example, basement, garage door, kitchen window, kitchen [Kitchen Win (dow)], room [ Living Room], main bedroom [Master Bed (room)], stereo system [Stereo Sys (tem)] and television [Television], where the portion in parentheses of those names is truncated to display in this example. Also, in this example, the system message region 132 of the phantom screen 78 shows a global system / connectivity status of the stringer 6 being updated 5 minutes ago ("Updated: 5 minutes ago") by the base station 4 If, for example, the information is too long to fit in region 132, then this region of the screen is cycled through messages or auto-spirals from right to left (e.g., in teleprinter tape style). . The content region 134 of the pouch screen 78 shows three of the sensor names (e.g., Basement, Garage Door, Kitchen Win (dow)), while the remaining four names 136 (e.g., Living Room, Master Bed (room), Stereo Sys (tem) and Television), in this example, are available for display from the rotary menu 130 in the RAM 56 of the pouch PIC processor (figure 3) by using the rotary knob 138 as it will be described. Thus, the information 131 includes both information for the content region 134 and information for the other names 136. The display content region 134 includes sensor information from the most recent update of the base station 4. For example, the system message region 132 of Figure 5B shows that the pouch 6 is now getting updated ("Getting Update ..."), Figure 5C shows all the systems: well ... newly updated ("All Systems: Ok. .. Just Up (dated) ") and figure 5D shows that the pouch 6 was updated: 5 seconds ago (" Updated: 5 seconds ago ") as measured from the current time. It will be appreciated that the names in the rotary menu 130 and in the information 131 can be displayed in a wide range of commands. For example, the names may be presented in alphabetical order, in the order that the corresponding sensors 8, 10, 12 were configured as part of the residential system 2 of Figure 1, in an order reflecting the sensor location in such residential system, or in an order that gives priority by severity. For example, alerts take precedence over status information. As an additional example, the nature of a sensor (eg, smoke; fire) and its status (eg, smoke detected, fire detected) may have a greater severity than those of another sensor (eg, bedroom lights) and its status (eg, off). The various icons 140 of Figure 5A reflect the current state of the corresponding sensors. For example, the contour of the water drop icon 142 shows that the corresponding Basement sensor (not shown) has not detected water, the open door icon 144 of the corresponding Garage Door sensor (not shown) shows that the corresponding door ( not shown) is open, the focus on icon (Figure 5B) of the Master Bed (room) sensor (not shown) shows that the corresponding light (not shown) is on, and the non-lit focus icon 148 of the Stereo Sys sensor (tem) (not shown) shows that the corresponding system (not shown) is off.

The sensor names in the rotary menu 130 are rotated by the rotary knob 138. A sufficient clockwise rotation rotates the names upwards (or the displayed menu 130 downwards), eg, two positions, of the Figure 5A to Figure 5B, such that the names and icons for Kitchen Win (dow), Living Room and Master Bed (room) are displayed. Similarly, another rotation clockwise enough rotates the names up, for example, two positions, from Figure 5B to Figure 5C, such that the names and icons for Master Bed (room), Stereo Sys (tem) and Television are deployed. Of course, different rotational amounts of the rotary knob 138 rotate the names to zero, one, two, three, or more positions, and a sufficient counterclockwise rotation (not shown) rotates the names down one or more positions. Figures 5F and 5G illustrate the user interface of the pouch of Figure 1. This user interface is preferably intuitive, consistent, and predictable, in which several "screens" (e.g., Figures 5A-5E and 6A-6B) in the interface follow a predictable "physics" of interaction. The rotary knob 138 in the pouch 6 is used, for example, to select and follow links, which allows the user to navigate from screen to screen. In particular, the rotary knob 138 is used to pass between information, and to highlight and follow links displayed on the screen 78.

By turning the knob 138 clockwise, this rotates to the rotary menu 130 (e.g., as discussed above in connection with FIGS. 5A-5C). Alternatively, the knob 138 may move the pointer or cursor 150 down in a counterclockwise rotation under certain user interface conditions as determined by the PIC pouch processor 54. Alternatively, the knob 138 may highlight any link displayed in the screen, in sequence. Similarly, by rotating the knob 138 in the opposite direction, this rotates the rotary menu 130 downwards and / or highlights the links in opposite order. Pushing the knob 138 in the center position 152 functions as pressing the mouse button on a desktop computer. Then, the selected link is typically followed by a new screen. Alternatively, some selected links change only a section of the current screen and / or "unfold" more of the larger virtual loop. As another alternative, the selected link can carry out an operation, such as, for example, resetting a maximum value. Preferably, the navigation is never deeper than a level beyond a home screen (e.g., of Figure 5C to or Figure 5D). When the user takes steps to configure a sensor (e.g., by pairing the pouch 6 with the sensor 12 of Figure 1), the pouch 6 automatically displays the screen 154 of Figure 6B. Similarly, when the user completes the sensor configuration (e.g., by selecting finish / exit training ("Done / Exit Training?") 156 from screen 158 of Figure 6B), the screen of the figure 5A, for example, is automatically re-deployed by the pouch 6. Holding the rotary knob 138 for a predetermined time (e.g., about one second) at any point or any time during the interaction flow automatically returns to the user to the home screen. Figure 5G shows that the pouch screen 78 includes two parts: the system message region 132, and the content region 134. The system message region 132 displays global system / connectivity state as well as context-specific tracks. For example, the system message region 132 may display that the pouch 6 was last updated 20 minutes ago ("Last Updated: 20 minutes ago") by the base station 4, it was last updated 5 minutes ago (" Last Updated: 5 minutes ago ") by the base station 4, is currently getting update (" Getting Update ") from the base station 4, is out of range (" Out of Range ") of the base station 4, or that the user must press a button for details ("<; press button for details > ") As another example, the content region 134 is the largest section of the pouch screen 78 and is devoted to the display of detailed information (eg, in the form of relatively large animated icons and text) about the system and the elements therein.Frequently, this screen acts as a "window" to a larger virtual spiral.The rotary menu 130 of figure 5A can be implemented in several ways.Two examples follow.Example 1 In this example , Basement is at the top of the list of information 131 and Television is at the bottom of the list, without wrapping Television back to Basement being allowed, Also, in this example, the down arrow 160 of Figure 5A indicates that Basement is at the top of the list, the up and down arrows 162 of Figure 5B indicate that the three names are neither at the top nor at the bottom of the list, and the line and arrow toward arrib to 164 of Figure 5C indicates that Television is at the bottom of the list. Example 2 Alternatively, as shown in Figure 5E, Television is followed by Basement in the content region 134 if there is additional clockwise rotation of the rotary knob 138, thereby providing a list or menu that wraps up. Similarly, if the rotary knob 138 is then rotated slightly in the opposite direction, the names displayed will include: Stereo Sys (tem), Television and Basement.

As shown in Figure 5C, the name Master Bed (room) is highlighted by the cursor icon 166 and, when the knob 138 (Figure 5A) is pushed, the last status information from the corresponding sensor (not shown) it unfolds below that name. In this example, the sensor has two attributes, lights (Lights) 168 and battery (Battery) 170, and the states of those attributes, On (On) 172 and Ok (Ok) 174, respectively, are also displayed. Generally, the sensors include at least the corresponding analog or digital state being monitored, and may also include health information (eg, battery level, not responding, intermittent). Figures 6A and 6B show sequences of screens used by the pouch 6 to configure the base station 4, and the sensors 8, 10, 12, respectively, of Figure 1. Figure 6A shows a set of display screens that the user used to configure the pouch 6 and the base station. First, the screen 180 thanks the user for choosing the system 2. This is followed by the screen 182, which points to the user, at 183, to press the knob 138 of Figure 5A to begin. The next two screens 184, 186 respectively instruct the user to turn on (e.g., connect to an AC power cord (not shown)) the base station 4 and point to the user, at 187, to press the knob 138 to continue. The next two screens 188, 190 graphically inform the user to insert the pouch 6 within the base station 4. Those screens 188, 190 are preferably repeated until the PIC pouch processor 54 detects that the sensor / base program switch 74 of Figure 3 is active or closed. When switch 74 closes in response to pouch 6 being suitably matched with base station 4, screen 190 makes transition, at 191, to screen 192, which informs the user, at 193, that pouch 6 is collecting ( or exchanging) information with the base station 4 (e.g., the ID of the pouch 6 is sent to the base station 4 by the RF transceivers on the wireless network 20, the ID of the base station 4 is sent to the pouch 6, or other pertinent data are provided from the base station 4 to the pouch 6) by exchanging a series of messages (not shown). Next, the user is informed by the screen 194 that the base station 4 has been identified, by the screen 196 that the system 2 is being activated, and by the screen 198 that the base station 4 is ready. Then, screen 200 points to the user, at 201, to press knob 138 to continue. In response to that action, the screen 202 informs the user that the phantom 6 is ready and, thus, that the phantom RAM memory 60 (Figure 3) includes, for example, the particular node ID of the base station 4 and both the pouch 6 and the base station 4 are part of the system 2. Finally, the screen 204 points to the user, at 205, to press the knob 138 to continue. When that action occurs, execution continues with screen 206 of Figure 6B. On the screen 206 of Figure 6B, the user is instructed to insert the pouch 6 into a sensor (e.g., a sensor does not configure 207) to add it to the system 2 of Figure 1. In summary, when one of the sensors 8, 10, 12 is adapted in this way, the pouch 6 starts to collect corresponding information and, then, reports the success to the user. As discussed below, the pouch 6 provides the ability to customize the sensor 207, with the status bar 132 cycling through two messages: mark to highlight ("<dial to highlight ...>") and press to select ("< press to select >"). Following screen 206, screen 154 reports that pouch 6 is collecting information. This is possible, because there are two, and only two, components in the system 2 (e.g., the pouch 6 and the particular sensor 207 (or the base station 4), which turn off and have their corresponding switches 74, 104 closed at any one time). As discussed below in connection with Figure 9B, when the sensor switch 104 is activated by pairing with the pouch 6, the sensor 207 sends a request to the base station 4 to join the network 20 (attempt_network_discovery). The phantom program switch 74 is also actuated (eg, simultaneously) by pairing with the sensor 207, and the pouch also sends a "program sensor" message to the base station 4. By receiving this message from "confirmation" of the pouch 6, the base station 4 recognizes to accept this sensor 207 to the network 20, and sends a message nwk_connect_confirm. Next, screen 208 reports the type of sensor (e.g., an Open-Closed Sensor 209 in this example). Then, the screen 210 reports that the sensor 207 is identified and the screen 212 removes the message of collecting information ("<.; gathering info ... > ") 213 of the status bar 132. Next, screens 214 and 216 point to the user to mark to highlight (" <dial to highlight ...> ") and press to select (" <press to select ") >) one of the three actions displayed: customize sensor ("Customize sensor?"), end / exit training ("Done / Exit Training?") and remove sensor ("Remove Sensor?"). If the user highlights and press (e.g., using the rotary knob 138 of FIG. 5A) "Customize sensor?" on screen 218, then screen 220 is displayed, which confirms that sensor 207 is a "Sensor Open-Closed "221 and list the possible names of that sensor in the lower rotary (configuration) menu 222. In this example, there are two possible names shown, which are based on the possible locations for such a sensor: window of stay [Living R (oo) m Window) and main door [Front Door], where the portion in parentheses of those names is truncated to display in this example Also, in this example, there may be one, three, or more names and the menu display operation Rotary (configuration) 222 can mimic the display operation of the rotary (monitor) menu 223 of FIG. 5E.

Next, after the user highlights one of the names, such as Front Door 225, the screen 224 points to the user to press the knob 138 of Figure 5A to select that name. Next, after the user selects the name, the display 226 displays the name, Front Door 227, in the system message region 132, and prompts the user to select one of the sensor alert levels, eg, alert Silent awareness ("Silent awareness?"), alert me if it opens ("Alert me if opened?") And alert me if it closes ("Alert me if closed?"). Although zero, one, two, three or more warning levels can be used for a particular sensor, in this example, "Silent awareness?" means that an audible vibrator 84 (figure 3) of the pouch 6 is inactive regardless of the state of that sensor. Otherwise, the user may select an audible alert as determined by the base station 4 to sound if that configured sensor is opened or if such a sensor is closed. Next, on screen 228, in this example, select "Silent awareness?", Which causes screen 216 to be re-deployed. At that point, if the user highlights and selects the option "Done / Exit Training?" 156, then the newly entered information for the sensor 207 is transferred to the base station 4. Alternatively, if the user highlights and selects the option "Remove sensor?" 230, and independently of i the sensor 207 was previously added, that information for such a sensor is transferred to the base station 4, to remove the sensor 207 from the system 2. Finally, if the user highlights and selects the option "Customize sensor?" 231, the screen 218 is re-deployed, no information is sent to the base station 4, and the user is pointed to re-enter the information to customize the sensor 207. Figures 7A, 7B and 7C are message flow diagrams 252, 254 and 256, respectively, showing several messages between the base station 4 and the pouch 6 to monitor the sensors 8, 10, 12 of Figure 1 and to send pouch data to such a base station. Figure 7A shows that the pouch 6 requests and receives information from the base station 4. Preferably, those requests (only one request is shown) are initiated at regular intervals (eg, periodic). Figure 7B shows that the base station 4 can also send a message to the pouch 6 in response to a change in state of one of the sensors 8, 10, 12. In this example, the pouch 6 is out of range of the station base 4. Figure 7C shows that the pouch 6 sends pouch data 258 to the base station. As shown in Figures 2A-2B, 3 and 7A-7C, the base station 4 includes both a PIC processor 22 and an RF processor 26, and the pouch 6 includes both a PIC processor 54 and an RF processor 58. It will be appreciated , however, that such components may alternatively employ one or more suitable processors. As shown in Figure 7A, the pouch 6 periodically requests and receives information from the base station 4. The message sequence 260 is also discussed below in connection with Figure 9B. At the end of that sequence 260, the PICT processor 54 of the pouch sends a hibernation request [SLEEP_request ()] 262 to the RF 58 processor of the pouch. Then, after a suitable hibernation interval to conserve battery power (eg, one minute), the PIC 54 pouch processor is awakened by the pouch timer 55 of FIG. 3, and the PIC 54 pouch processor. sends a wake-up request message [WAKEUP_-request ())] 264 to the RF 58 phantom processor. In turn, the message sequence 260 is executed to reload the local pouch data table 266 with the latest available information from the base station 4 relative to the sensors 8, 10, 12. As part of the sequence 260, the The PIC 54 pouch processor sends a PICDATA_request (rqst_updates) message 268 to the phantom RF processor 58, which receives that message 268 and in response sends an RF Data (reqst_updates) message 270 to the base RF 26 processor. Upon receipt of the RF 270 message, the base RF processor 26 sends an Acknowledge-ment RF message (SUCCESS) 272 back to the RF phantom processor 58 and sends a PICDATA_indication (rqst_updates) message 274 to the base PIC processor 22. The data requested by this message 274 may include, for example, profile and status information of one or more components, such as the sensors 8, 10, 12. Here, the pouch 6 is requesting an update of the base PIC processor 22 for data from all sensors 8, 10, 12, including any newly added sensors (eg, sensor 207 of Figure 6B), in view of that state change (i.e., there is new data from the newly sensor added 207). In response to receiving the RF Acknowledgement (SUCCESS) message 272, the RF 58 processor of the pouch sends a PICDATA_confirm (SENT) message 276 to the PIC 54 pouch processor. In response to receiving the PICDATA_indication (rqst_updates) message 274, the base processor PIC 22 sends a PICDATA_re-quest (updates) message 279 to the base RF processor 26, which receives that message 278 and in response sends an RF Data message ( updates) 280 to the RF 58 phantom processor. After receiving the RF Data (updates) message 280, the RF 58 chip processor sends an RF Acknowledge (SUCCESS) message 282 back to the base RF processor 26 and sends a PICDATA_indication (updates) message 286, including the data of requested sensor updates, to the PIC 54 pouch processor, which updates its local data table 266. Then, if there is no activity of the thumb circle 138 of FIG. 5F, or if no alert is received from the base station 4 , then the PIC 54 pouch processor sends a SLEEP_request () message 262 to the phantom RF processor 58 and both the pouch processors 54, 58 enter the low power mode [low_power_mo-de ()] 288, 290, respectively. After receiving the RF Acknowledge (SUCCESS) message 282, the base RF processor 26 sends a PIC_DATA_confirm (SENT) message 284 back to the base processor PIC 22. Following the message sequence 260, the pouch timer 55 awakens the pouch processor PIC 54, at 291, which sends the message 264 to the phantom RF processor 58, to periodically repeat the message sequence 260. Figure 7B shows a sequence of alert messages from the base station 4 to the pouch 6, in which the pouch 6 is out of range of the base station 4. First, at 293, the base station PIC 22 sends a PIC_DATA_request (alert) message 292 to the base station RF processor 26. In response, that processor 26 sends an RF Data (alert) message 294 to the phantom RF processor 58. In this example, any RF message sent by the base station 4 while the phantom 6 is out of range (or in low power mode) will be lost. After a suitable waiting period, the base station RF processor 26 detects non-response by the pouch 6 and in response sends the PIC_DATA_confirm (OUT_OF_RANGE) message 296 back to the base station processor PIC 22. A satisfactory version of this message sequence 254 is discussed below in connection with Figure 9B. In figure 7C, at 297, the PICT processor 54 of the pouch sends a PICDATA_request (data) message 298 to the RF processor 58 of the pouch. Next, the RF 58 processor of the pouch sends an RF Data (data) message 299 including the phantom data 258 to the base station RF processor 26. In response, the base station RF processor 26 sends an RF Acknowledgement (SUCCESS) 300 message to the RF phantom processor 58. Finally, the phantom RF processor 58 sends a PICDATA__confirm (SENT) message 302 to the PIC 54 pouch processor. Figures 8A and 8B are message flow diagrams 310, 312 showing various messages between one of the sensors 8, 10, 12 and the base station 4 of Figure 1 to monitor that sensor. Figure 8A shows that the sensor sends status information to the base station 4 at regular (eg, periodic) intervals. Figure 8B shows that the sensor also sends status information to the base station 4 in response to changes in sensor status. The sensor chronometer 98 of FIGS. 4A and 4B preferably establishes the regular interval, sensor_heart-beat_interval, 314 of FIGS. 8A-8B (e.g., without limitation, once per minute).; once per hour; once a day; any suitable period of time), for that particular sensor, such as 8, 10, 12. It will be appreciated that the regular intervals for the various sensors 8, 10, 12 may be the same or may be different depending on the desired update interval. for each particular sensor. In Figure 8A, after the expiration of sensor_-heartbeat_interval 314, the sensor, such as 10, wakes up [wake_upO] at 316. Next, the sensor 10 sends an RF message Data (state_information) 318 to the base station RF processor 26, and that RF processor 26 sends in response an RF Acknowledgment (SUCCESS) message 320 back to the sensor 10. In response to receiving that message 320, the sensor 10 enters a low energy mode [low_power_mode ()] 324 (e.g., to conserve energy from the sensor battery 90 of Figure 4B). Also, in response to sending that message 320, the base station RF processor 26 sends a PICDATA_indication (state) message 322 to the base station processor PIC 22. Both the RF Data (state_information) 318 message and the PICDATA_indication (state) message 322 convey the status of the sensor 10 (eg sensor on / off, sensor battery good / low). The low energy mode [low_power_mode ()] 324 is maintained until one of two events occurs. As discussed previously, after the expiration of sensor_heartbeat_inter-val 314, sensor 10 wakes at 316. Alternatively, as shown in Figure 8B, sensor 10 wakes up [wake_up () 326] in response to a state change ( e.g., the sensor 10 detects a transition from on to off or a transition from off to on of the discrete input of the sensor 106 of FIG. 4A). Next, the sensor 10 sends an RF Data message (state_information) 328 to the base station RF processor 26, and the RF processor 26 sends in response an RF Acknowledgment message (SUCCESS) 330 back to the sensor 10. In response to receiving that message 330, the sensor 10 enters low_power__mode () 332. After the expiration of sensor_heartbeat_interval 314, the sensor 10 wakes up at 316 of Figure 8A. Next, at 333, the base station RF processor 26 in response sends a PICDATA_indication (state) message 334 to the base station processor PIC 22. Both the RF Data (state_information) 328 message and the PICDATA_indication (state) 334 message carry the status of the sensor 10. In response to receiving that message 334, the base station PIC 22 sends a PICDATA__re-quest (alert) 336 message to the RF 26 base station processor. Such an alert is sent when there is any change of sensor status. Finally, the base station RF processor 26 sends an RF Data (alert) message 338 to the RF processor 58 of the pouch. The response by that processor 58 and the subsequent activity by the pouch 6 are discussed, below, in connection with a sensor joining the network 20 of Figure 1 and Figure 9B, which shows the procedure and messages for status update . Figures 9A and 9B are message flow diagrams 350, 352 showing the interaction between the pouch 6, a sensor, such as 10, and the base station 4 of Figure 1 for configuring that pouch and that sensor. In Figure 9A, after the four processors 54, 58, 26, 22 complete their respective power_on () initialization 354, 356, 358, 360, the pouch 6 can be joined to the network 20 of the base station 4. The sensor 10 the initialization power__on () 362 also starts. Initially, in response to screens 188, 190 of FIG. 6A, the user undertakes a sweep [FOB_swipe ()] 354 of the pouch 6 with the base station 4. In view of the screens 188, 190, the PIC 54 pouch processor knows, at this point, that the paired component is the base station 4. The PIC 54 pouch processor detects the closure of the sensor / base program switch 74 of FIG. 3 and in FIG. The response sends a JOIN_request (NetworkDevice) 366 message to the phantom RF processor 58, which in response executes an initialize_comm_stack () routine 368. This routine 368 initializes the communication stack of that processor, which provides appropriate software services. two for communications of one RF component (e.g., the pouch 6) to another RF component (e.g., the base station 4). Then, the RF 58 processor of the phantom sends an RF discovery attempt message [attempt_nwk_disco ery ()] 370 to the RF base processor 26, which may or may not be ready for that message. Only after the base station 4 has been successfully started, these attempts to discover the pouch 6 will be satisfactory. At that point, the pouch 6 can transmit its profile 363 to the base station 4. When the base processor PIC 22 is notified, as a result of FOB_swipe () 364 of the pouch 6 with the base station 4, of the switch closure of the switch. program 42 of FIG. 2A, sends in response a JOIN_request (NetworkCoordinator) message 371 to the base RF processor 26, which in response executes an initialize_comm_stack () routine 372. As a result, the stacking of base communications is started and the base RF processor 26 is ready to accept requests from other components to join the network 20 of Figure 1. When the routine 372 concludes, the base RF processor 26 sends a JOIN_confirm (SUCCESS) message 374 back to the PIC processor 22 of base. Therefore, the base RF 26 processor is now ready to accept requests from other components (e.g., the sensor 10).; the pouch 6) to join the network 20. Although the first RF attempt_nwk_discovery 370 message to the base RF 26 processor was ignored, since the routine 372 has not yet concluded, a second or subsequent RF attempt_nwk_discovery message, such as 376 , it is sent to and received by the base RF 26 processor. That processor 26 receives the message 376 and responds with an RF message of nwk_connetct_confirm () 378 back to the RF processor 58 of the pouch. When the message 378 is received, the RF processor 58 of the pouch sends a JOIN_confirm (SUCCESS) message 380 back to the base processor PIC 22. The profile 363, for a component such as the pouch 6, includes suitable component identification information, which, for example, identifies the component as a pouch and provides the node ID and any of the attributes thereof. The profile 363 is transmitted to the base RF processor 26 after the RF chip processor 58 has joined the network 20 of FIG. 1. In this regard, the RF 58 chip processor can periodically attempt that action as shown. by the example sequence of two RF messages from attempt_nwk_discovery () 370, 376 to the RF processor 26 of base. It will be appreciated that one or more such attempts are employed. Also, such discovery attempts can be employed after the power is turned on and independent of the linking of the pouch 6 with the base station 4. At 381, the pouch 6 can transmit its profile 363 to the base station 4. The PIC processor 54 of the pouch sends a PICDATA_request (profile) 382 message to the phallic RF processor 58, which in response sends an RF message DA-TA (profile_information) 384. That message 384 is received by the base RF processor 26. In response, that processor 26 sends an RF Acknowledgement (SUCCESS) 386 message back to the RF processor 58 of the pouch. Upon receipt of that message 386 by the phantom RF processor 58, sends a PICDATA_confirm (SENT) 388 message back to the PIC 54 pouch processor. After sending the RF Acknowledge (SUCCESS) message 386, the base RF processor 26 sends a PICDATA_indication (profile) message 390 to the base processor PIC 22. Upon receipt of the message 390, the base PIC processor 22 sends a PICDATA_request (profile_confirm) message 392 to the base processor RF 26 and also stores the profile 363 for the pouch 6 in an internal table 393 of components, which has been added to the network 20. Upon receipt of the message 392, the base RF processor 26 sends an RF DATA message (profile_confirm) 394 to the RF processor 58 of the pouch. Upon receipt of that message 394 by the RF chip processor 58, it sends an Acknowledgement (SUCCESS) RF message 396 back to the base RF processor 26 and sends a PICDATA-_indication (profile_confirm) message 400 back to the PIC processor 54 of pouch. In response to the reception of that message 400, the pouch processor PIC 54 displays the pouch acceptance screen 202 ("Key is ready.") Of Figure 6A to the user. Upon receipt of the RF message 396, the base RF processor 26 sends a PICDATA_confirm (SENT) message 398 to the base processor PIC 22. Finally, at 401, the PIC 54 processor of pouch sends a SLEEP_request () message 402 to the RF processor 58 of the pouch and both the pouch processors 54, 58 enter low_power_mode () 404, 406, respectively.

With reference to Figure 9B, in order to join one of the sensors, such as 10, to the network 20 of Figure 1, the user suitably pairs the pouch 6 with that sensor. In response, the PIC 54 pouch processor detects the sensor program / base station switch 74 of Figure 3 being closed. In view of the screen 206 of Figure 6B, the pouch 6 knows, at this point, that the paired component is a sensor. Following the routine FOB_switch_pressed () 412, the pill processor PIC 54 sends a WAKEUP_re-quest () message 414 to the RF processor 58 of the pouch. Similar to the RF messages 370, 376 of the phantom RF processor, the sensor 10 periodically sends RF messages, such as the RF attempt_nwk_discovery 420 message, to the base RF processor 26. Otherwise, the sensor 10 goes into a low energy mode, such as 427, if the network discovery attempts are unsuccessful. The sensor 10 then re-attempts (not shown) such network discovery attempts after an adequate time in low energy mode. At 415, after sending the wake-up message 414, the PIC 54 pouch processor sends a PICDATA_re-quest (SensorJoining) 416 message to the RF 58 phantom processor, which, in turn, sends an RF message from DATA (SensorJoining ) 418 to the base processor RF 26. The physical action of FOB_swipe 410 also causes the sensor 10 to detect the closure of the sensor program switch 104 of FIG. 4A. Preferably, that action triggers the first RF message 420. In view of the two RF messages 418, 420 to the base RF processor 26, in response it sends an RF message nwk__connect_confirm () 422 back to the sensor 10. Upon receipt of that RF message 422, the sensor sends an RF DATA message (profile_information) 424 back to the base RF processor 26. That RF message 424 includes the sensor profile 425, which includes suitable component identification information, such as component type (e.g., sensor), sensor type (e.g., on / off); an entry; battery-powered), the node ID and any suitable attribute of the sensor 10. Upon receipt of that RF message 424, the RF base processor 24 sends the sensor 10 an RF Acknowledgment (SUCCESS) message 426. Next, the RF processor 26 sends a PICDATA_indication (profile) 428 message to base processor PIC 22, including sensor profile 425. Base processor PIC 22 receives that message 428 and stores profile 425 in table 430. PIC processor 22 The base also sends a PICDATA_request (alert) 432 message to the RF base processor 26, which indicates that a new sensor 10 has been added to the network 20. As will be seen, this message 432 is finally communicated to the pouch 6, which , then, it needs in response to request data associated with the newly added sensor 10. After receiving the RF Acknowledge (SUCCESS) message 426, the sensor 10 enters low_power mode () 427. In turn, after a suitable sensor_heartbeat_interval 429, the sensor 10 awakens as discussed above in connection with Figure 8A. Upon receipt of the PICDATA_request (alert) message 432, the base RF 26 processor sends an RF Data (alert) 434 message to the RF 58 processor of the phantom, which receives that RF 434 message and in response sends an RF message of Acknowledge- ment (SUCCESS) 436 back to the base RF 26 processor. Upon reception of the RF message 436, the base RF processor 26 sends a PICDATA_confirm (SENT) message 438 to the base processor PIC 22. Then, after the phantom RF processor 58 sends the RF message 436, it sends a message PICDATA_indicatión (alert) 440 to the PIC 54 pouch processor. Then, the message sequence 260 of FIG. 7A is executed to provide sensor information for the sensor 10 newly added to the pouch 6. As part of the sensor profile 425, the sensor 10 provides, for example, a node ID, a network address and / or a unique sensor serial number. As part of the messages 416, 418, the pouch 6 provides a graphic identifier (e.g., a label; sensor name; sensor attribute) associated with the sensor configuration (e.g., display 224 of FIG. 6B provides the name "Front Door" 225 for the sensor being configured). Fig. 10 shows a PDA 450 associated with the base station 4 of Fig. 1 and its corresponding display 452. The base station 4 communicates with the PDA 450 via RF, cellular or other wireless communications 454 from the network server 18 of Figure 1. Although a PDA 450 is shown, the base station 4 can communicate, for example, with the pouch 6, a PC (e.g., a palmtop, a laptop) (not shown), Internet 16 of Figure 1, or a web-enabled telep (not shown). Display screen 452 preferably provides a suitable menu 456 (eg, including status, calendar, configuration and sensor information). The "in view" screen also communicates critical information about the "well-being" (eg, "health") of the residence. That information may include information obtained from sensors 8, 10, 12 (e.g., mail, temperature, alarm, lights, fire, electrical, security, heat, air conditioning (AC), water, and residential computer system or wall of fire (firewall) of wireless LAN). Example 3 The base station 4 can provide status and remote alerts directly to the owner or user via, for example, telep, cell p, pager, e-mail or AOL Instant Messenger messages, remote pouch, facsimile, any messaging mechanism suitable, or Internet 16 of Figure 1 regarding various household conditions, functions and / or applications.

Example 4 Examples of the types of sensors 12 of Figure 1 include water leaks; power cuts; abnormal temperatures (eg, home; refrigerator; oven; air conditioning; heat pump); movement (eg, infant, pet, elderly person, wild animal); alarm (eg, open or matched; door; window; cabinet); electro-domestic appliance turned on (eg, iron, television, coffee maker); sound (eg, smoke alarm, intruder alert); separate garage status; tremor (e.g., earthquake); aroma (e.g., natural gas); Pressure (e.g., packaging delivered in the main entrance mat); manual request (eg, a button is pressed on a sensor "able to name", such as, for example "bring food to take" or "lack of milk"). Sensor 12 may include, for example, conventional safety devices (eg, movement, door state, window condition, smoke, fire, heat, gas (e.g., carbon monoxide, natural gas); alarm) and monitors of residence condition (eg, humidity, temperature, electrical energy, energy (eg, natural gas, water, electricity, electric power)). Example 5 Wireless communications of relatively short range (eg, without limitation, RF) can be used between sensors 8, 10, 12 (and pouch 6) and base station 4. Example 6 Base station 4 can use relatively long-range communications (eg, an existing landline telephone from the owner; DSL modem) to reach the owner remotely (eg, cell phone, pager, Internet). Example 7 Locations without a landline may employ a suitable cellular control channel (e.g., as an asset management system) to transport sensor information remotely. Example 8 Residential wireless communications can be self-configured such that a typical owner can easily install and easily use system 2 and sensors 8, 10, 12 of Figure 1 with relatively minimal configuration.

Example 9 Bi-directional wireless communications can be used between the sensors 8, 10, 12 (and the pouch 6) and the base station 4, to ensure reception / recognition of messages. Example 10 The base station 4 can allow remote control by the pouch 6 of the selected residence functions (e.g., change the temperature in a thermostat (not shown)). Example 11 The pouch 6 can provide a personal dashboard (e.g., status indicators) of the residence to provide a state of view and awareness of various residential conditions. Example 12 The system 2 can provide only relatively short range, wireless communications between the sensors 8, 10, 12 (and the pouch 6) and the base station 4. Example 13 The system 2 can provide relatively short range, wireless communications between the sensors 8, 10, 12 (and the pouch 6) and the base station 4, and communications of relatively long range to the owner through a remote pouch (e.g., the PDA 450 of Figure 10). For example, the base station 4 may communicate with a cellular phone (data) (not shown) or a pager (not shown) as a remote user interface. Example 14 The system of example 12 may also provide relatively long-range communications to the owner through a remote pouch (e.g., PDA 450 of Figure 10). Example 15 System 2 can provide a mechanism to allow the owner through a local or remote pouch or send an alert to a service contractor (not shown) or another third party. Example 16 System 2 may partner with a service provider, which takes calls from the owner or the base station 4 and contacts "certified" (eg, trusted) contractors. Example 17 System 2 can be associated with a service provider, which takes calls from the owner or the base station 4 and responds accordingly. Example 18 The system of examples 12-15 may not require a service contract (eg, quotas) with a security company. Example 19 The system of examples 12-18 can address the level of programmability and personalization available (eg, to create unique sensor names); simple logic of code). The communication interfaces 48, 50, 52 in the base station 4 can be used to allow the user to create custom names for sensors by entering them into a PC or through an Internet browser. Example 20 The pouch 6 is preferably portable and relatively small. The pouch 6, which supports wireless communications, allows the base station 4 to be "headless". In this manner, the user can employ the pouch 6 as a user interface to system 2 when the user wishes to use it (eg, front cover; dressed; attached to a refrigerator; placed on a table; placed on a base); that is wireless. The pouch 6 provides the user or owner with conscience by exception, and provides peace of mind (that is, everything is fine at home). The pouch configuration procedure differs from that of known residential products and systems in that it provides a single button 152 and a rotary dial or selector 138 (FIG. 5F), to select from a predetermined list of sensor names and attributes based on, for example, the location and type of component being configured (e.g., context aware). The pouch 6 combines the low memory cost, short range wireless communications, and a plurality of definitions or configuration names (see, for example, examples 21-27, following). This preference configuration procedure employs an interaction protocol in successive layers (eg, first-time users will only see the upper "layer" of interaction choices, such as adding a sensor or naming a sensor, but once the user has experienced and learned the interaction physics, then will discover deeper configuration avenues, such as clicking on a sensor name expands the list to show more details) to allow both first-time and experienced users to access tasks of typical or more probable systems. Example 21 Non-limiting examples of types of sensors 8, 10, 12 of Figure 1 include opening / closing devices, on / off devices, water detection devices, water absence detection devices, water detection devices, movement, and event detection devices. Example 22 Non-limiting examples of sensor identity names for opening / closing devices include: Door (door), Window (window), Back Door (back door), Basement Door (basement door), Basement Window (basement window) ), Bathroom Window, Bedroom Door, Bedroom Window, Deck Door, Front Door, Kitchen Door, Kitchen Window (kitchen window), Garage Door (garage door), Living Rm Window (or Living Room Window) (stay window), Pantry (pantry), Pet Door (pet door), Storage Area (storage area), Supply Room (supply room), Cabinet (cabinet), Closet (closet), Drawer (drawer), Gun Cabinet, Jewelry Box, Mail Box, Refrigerator, Safe, Trunk, and TV Stereo Cabinet ). Example 23 Non-limiting examples of sensor identity names for on / off devices include: Appliance (electro-domestic appliance), Clothes Iron (clothes iron, Coffee Maker (coffee maker), Curling Iron (hair iron), Game System (game system), Light (light), Refrigerator (refrigerator), Stereo (stereo), Stove (stove), Toaster Oven (toaster oven), and TV (television) Example 24 Non-limiting examples of sensor identity names for water detector devices (eg, an alarm is generated if water is detected) include: Basement Floor, Bathroom Floor, Bed Room, Dining Room, Garage (garage), Laundry Room (laundry room), Living Room (stay), Storage Area (storage area), Sump Pump (sump pump), Under Sink (under the sink), and Utility Sink (service sink Example 25 Non-limiting examples of sensor identity names for devices for detecting the absence of water (v.gr. , an alarm is generated if no water is detected) include: Cat Bowl (cat bowl), Dog Bowl (dog bowl), Fish Tank (fish tank), Garden Pool (pool), and Water Bowl (bowl) for water) . Example 26 Non-limiting examples of sensor identity names for motion detection devices include: Attic (attic), Baby Room (baby room), Back Door (back door), Basement (basement), Driveway (access path for cars), Front (front), Garage (carport), Hallway (corridor), Kitchen (kitchen), and Pantry (pantry). Example 27 Non-limiting examples of sensor identity names for event detectors (e.g., which may respond, for example, to a push button or other user input) include: Help! (Help!), Get Milk! (Bring milk!), Come Down Here (come down here!), Come Up Here (come up here!), I'm Home (I came home), Doorbell (doorbell), Keyfinder (key finder), and Community Watch (community watch) . As discussed above in connection with Figure 9B, during the configuration of the sensor, the pouch 6 and the sensor 10 communicate (e.g., via RF) with the base station 4 for storing configuration details. This starts, for example, as a result of the physical pairing of the pouch 6 and the particular sensor, such as 10. Although the configuration appears, from the user's perspective, as if it were taking place locally (directly), it is in fact being mediated by the base station 4. This allows the base station 4 to store / record critical information in non-volatile memory and / or report it remotely. The pouch user interface (e.g., Figure 5F) represents a single "detachment" personal deployment and configuration device (e.g., the pouch 6 is either removable from the base station 4 or from one of the sensors 8, 10, 12 and, also, it is portable) for each aspect of the system 2. Preferably, the user learns the procedure once (e.g., for the base station 4 (Figure 6A) or for an initial sensor , such as sensor 207 of FIG. 6B) and employs that method for the other sensors 8, 10, 12 of system 2. In this manner, base station 4 and sensors, such as 8 of FIG. 4B, are " without a head "and simply" make a port "with," pair "with or are close to the pouch 6 when and where they are needed. This procedure acts as a logical constraint on the proliferation of non-standard user interface elements within the system environment. Therefore, instead of solving a particularly troublesome user interface problem in a given component by, for example, adding buttons to the component and adding instructions to the user's guide, the "detachment" pouch user interface allows a Consistent, flexible, potentially deep graphical interface for both relatively low cost and relatively high cost / complexity components.

The pairing of the pouch 6 to the system component (e.g., base station 4, sensor 10) provides for an associative / semantic "training" of new components to customize the system 2 and to provide a start / structure and unique dice location. This mechanical pairing allows for system 2 to provide context and location specific deployment and configuration interaction using, for example, sensor physical location as a filtering mechanism, which significantly reduces the overall perceived complexity of the interface. This, in addition, allows for a "one button / dial" interaction physics in the pouch 6. Examples 28-37 and 39, below, furthermore disclose examples of the pouching mating procedure. Example 28 Current known systems require that the user: (1) memorize a sensor number; (2) Mount the sensor in its place in the residence (eg, possibly out of range of its main control board); (3) establish any specific sensor configuration switch; (4) Go back to the main control board and test the sensor; (5) associate the memorized sensor number with, typically, a written name / number map; and (6) repeat steps (1) - (5) for each of the sensors, while setting different and different configuration switches on each sensor. Alternatively, each sensor requires a unique (and usually different) display and input mechanism to learn and program (eg, different switches, knobs, screens and / or buttons) on a remote control. In contrast, the present system 2 employs a single "physical" interface in which the rotary knob 138 of FIG. 5F is rotated to search through (and / or highlight) various links or information, and the button of FIG. pouch 152 is pressed to select the highlighted league or information. As part of the configuration, the personal interface pouch 6 is physically matched or otherwise properly matched to the component (eg, sensor 10; base station 4) to be configured. Then, the user reads and answers questions that pop up on this screen of the component, now active, in the pouch 6 using the simple interface "physics" previously described. Then, the user places the component in the desired location in the residence. For example, if the user walks out of range of the base station 4, the paired pouch 6 and the component, such as the sensor 10, preferably informs the user of the condition "out of range". Finally, based on the desired location (e.g., door) and type (e.g., open / closed detector) of the component, the user can easily customize it accordingly (e.g., a door sensor). automatically displays a list of common names, for example "Front Door" (main door) and "Deck Door" (terrace door)).

In this example, the physical pairing of the pouch 6 and the sensor 10 allows for the filtering of the various interface items (e.g., if it is paired with a door sensor, then a menu of the sensors is not displayed). water detector). Also, the physical location in the paired time in the desired environment allows filtering the functionality (eg, if the sensor 10 is "out of range" of the base station 4, then the pouch 6 will show "out"). of range ", which indicates to the user that they have exceeded the functional range of the sensor 10). Example 29 Figure 13 shows a sensor 460 having a female connector 462 and a nearby pouch 464 having a male connector 466 (e.g., a USB style bayonet connector). Figure 14 shows the matched pair of sensor 460 and pouch 464 in which male connector 466 is inserted into female connector 462, to provide the signature (eg, address, serial number) of sensor 460 directly to the pouch 464. This physical "key" pouch 464 provides the user with a sense of security in system 2 of figure 1 by "activating" each system component, such as sensor 460, through the process of "opening" or pairing with it. Alternatively, the sensor 460 can wirelessly communicate its signature to the base station 4, instead of to the pouch 464. Example 30 Figures 11 and 12 show another pouch 470 which employs a recessed "key" slot 472 to link to a base station 474 and sensor 476, respectively. In contrast to example 29, this cuts the overall length of the pouch 470 by making the electrical connection part of a slider (e.g., including two longitudinally located electrical contacts 478, 480) in the recessed "key" slot 472 , instead of the USB style bayonet connector 466 of FIG. 13. These contacts 478, 480, in this example, electrically and mechanically link a conductor 481 in the base station 474. Example 31 Figure 15 shows the resulting pair of the pouch 470 with the RF sensor 476 having an antenna 477. In this example, the pouch 470 can still generally look like a key, although when paired, or otherwise "closed" with the sensor 476, it resembles a deployment interface "sudden onset" 482. This effectively creates a "customizable" sensor screen linked to location, ad-hoc, for adjustment of a "headless" component, such as sensor 476. Example 32 Figure 16 shows an example of the sensor / base program switch 74 of a pouch 6 ', and the sensor program switch 104 of a sensor 10'. The pouch 6 'includes a box or cover 490 having an opening 492, a protrusion 494 and a printed circuit board 496 therein. The sensor / base program switch 74 is close to the opening 492, and the sensor program switch 104 is on a printed circuit board 497 and close to the opening 498 of the sensor case or cover 500. When the pourer is 6 'is suitably matched with the sensor 10', the pouch protrusion 494 passes through the sensor opening 498 and links to the sensor program switch 104. At the same time, when the sensor 10 'is properly matched with the 6 ', the sensor protrusion 502 passes through the pouch opening 492 and links to the sensor / base program switch 74. Example 33 The configuration mechanism (or linked) allows the base station 4 without a head to associate a particular sensor, such as 10, with a corresponding name (Open-Close) and location (Front Door). First, the portable pouch 6 is brought to the particular sensor 10 to be configured as part of the system 2. Next, the pouch 6 and the particular sensor 10 are properly connected, such that the pouch 6 can associate the sensor identification signature ( v. address; serial number) with a corresponding graphic identifier (eg, label, symbol, icon) on screen 78 of the pouch of figure 3. In turn, this information is communicated wirelessly of the pouch 6 and / or sensor 10 to the base station 4 without a head.

Example 34 Preferably, the pouch 6 employs a relatively simple instruction manual and / or an intuitive sequence of operational steps, to provide an out-of-the-box experience for the user. The pouch 6 either temporarily or momentarily is paired or otherwise associated with the sensor 10 to "learn" the sensor identification signature (e.g., address, serial number) and "tag" that information with the identifier graphic (e.g., label; symbol; icon) corresponding to the pouch screen 78. In this manner, system 2 can "open" the new sensor 10 to residential system 2, instead of to a neighboring system (not shown). Also, system 2 can "open" only residential sensors 8, 10, 12 to residential system 2, instead of any of the neighboring sensors (not shown). In addition, this allows new sensors, such as 207 of Figure 6B, to be easily added to system 2 and train them or associate them with unique locations and environments in or around the residence. Example 35 The connection mechanism between the pouch 464 and the sensor 460 of Figure 13 can be physical (e.g., employing mechanically and electrically pairing connectors 466, 462 in both the pouch 464 and the sensor 460), communicating the presence of the sensor to the pouch 464, and for communicating the sensor identification signature (eg, address, serial number) to the pouch 464 and / or base station 4. Example 36 The connection mechanism between a phantom and a sensor can be wireless (eg, optical, RF in both the pouch and the sensor), to communicate the presence of the sensor to the pouch, and to communicate the sensor identification signature (e.g. address, serial number) to the base station. Example 37 In some cases, the location of the sensor in system 2 may be such that the sensor is difficult to access. An example is a sensor for fixing a ceiling light, which is difficult to access directly, for example, using a ladder or similar device. Therefore, the sensor and the pouch can employ a proximity sensor (not shown) and / or an optical gate (not shown), which detects when the pouch is within a suitable distance from the sensor. Example 38 Although a pouch 6, which simulates the figure of a "key", has been disclosed, a wide range of other suitable figures and sizes of pouches can be employed. For example, other embodiments of such pouches may be in the form of a pendant, a credit card or other item that is worn and / or seen directly or indirectly by a person. Such pouches, for example, may be attached to and / or cloned into another household item (e.g., a refrigerator, a table), and / or attached to or carried by a personal item (eg, a purse; a credit card cover). Example 39 Figures 17A-17C show an example of another pouch 510 and a wireless system component 512 (e.g., a sensor, a base station), which is suitably matched for configuration of the system component 512 and / or the pouch 510. The pouch 510 includes a training / mating switch 514, which operates in the manner of the sensor / base program switch 74 of FIG. 3. The component 512 includes a surface or protrusion 516, which is designed to link to switch 514. Component 512 also includes a training / mating switch 518 having an actuator 519, which operates in the manner of the base program switch 42 of FIG. 2A or the sensor program switch 104 of FIG. Figure 4A. The pouch includes a protrusion or surface 520, which is designed to be attached to the switch actuator 519. Initially, as shown in Figures 17A and 17B, the pouch 510 slides toward the component 512. For example, the pouch 510 includes a linking portion 522 having a tongue 524, while the component 512 has a corresponding matching mating recess 526 (shown in hidden line drawing) with a corresponding slit 528. As the component protrusion 516 approaches the pouch switch 514, it links and activates an actuator 530 therein, as shown in Fig. 17C. At the same time, as the pouch surface 520 approaches the switch disconnector actuator 519, it links and activates that actuator 519, as shown in Fig. 17C. In turn, when the phantom 510 and the component 512 are fully seated, with both switches 514, 518 being activated, the pouch 510 and the component 512 can establish RF communications with the base station 4 of figure 1 as discussed previously in connection with Figures 9A and 9B. In this example, the component switch 518 is activated only before the pouch switch 514. Alternatively, the switches 514, 518 can be activated at the same or at different times. Also, in the example, the component switch 518 may be a two-pole device, which is designed to detect both insertion and removal of the 510 pouch. The exemplary residential system 2 provides a conscientious owner seven days a week , 24 hours a day, both at home (referred to as "only at home") and outside the home (referred to as "outside and around") of the "well-being" of the residence. Although for clarity of disclosure reference has been made herein to the exemplary screen 78 for displaying information and values of residential welfare system, it will be appreciated that such information, such values, other information and / or other values can be stored, printed on paper , modified by computer, or combined with other data. All such processing should be considered falling within the terms "screen" or "unfold" as used herein. Although specific embodiments of the invention have been described in detail, it will be appreciated by those skilled in the art that various modifications and alternatives to those details could be developed in light of the overall teachings of the disclosure. Accordingly, particular disclosed arrangements are intended to be illustrative only and not limiting as to the scope of the invention which will be given the full scope of the appended claims and any and all equivalents thereof.

Claims (25)

1. CLAIMS 1. A system for a structure, said system for a structure comprising: a server that includes a wireless communications gateway first; a portable pouch that includes a second wireless communications gate, a user input device and a screen; and a plurality of sensors, each of said sensors detecting information and including a third wireless communications gate, to which said detected information is sent to the first wireless communications gate of said server, said server sending said detected information to at least one of said sensors of said wireless communication gateway first of said server to said second wireless communication gate of said portable pouch, said portable pouch displaying said detected information for at least one of said sensors on the screen of said portable pouch.
2. 2. The system for a claim structure 1, where the screen of said portable pouch includes graphic capacity.
3. 3. The system for a claim structure 1, wherein the screen of said portable pouch includes a plurality of graphic objects; and wherein the user input device of said portable pouch is a simple rotary switch, which is used to select one of the graphic objects of said screen.
4. 4. The system for a structure of claim 3, wherein said rotary switch is adapted to be pushed to select said one of the graphic objects.
5. The system for a structure of claim 1, wherein said screen of said portable pouch includes a plurality of representations of at least one of said sensors; wherein the user input device of said portable pouch selects one of said representations; and where the screen of said portable pouch in response displays said detected information for a corresponding one of said sensors.
6. 6. The system for a claim structure 1, wherein said sensors and said server employ bi-directional wireless communication links between said third wireless communications gates and said first wireless communication gate; and wherein said sensors include a routing function in some of said sensors to communicate with said server through other of said sensors.
7. The system for a structure of claim 6, wherein said server, said portable pouch and said sensors employ bi-directional wireless communications links between said first wireless communication gate, said second wireless communications gate and said wireless communications gate. third; and wherein said portable pouch and said sensors include a routing function in which said portable pouch and some of said sensors communicate with said server through other of said sensors.
8. The system for a structure of claim 1, wherein said server is adapted to communicate with one of a telephone line, a cellular telephone, a global communications network, a local area network, and a locator such as another user interface .
9. The system for a structure of claim 1, wherein said portable pouch is adapted to be worn by a wearer.
10. 10. The system for a structure of claim 1, wherein said portable pouch is adapted to be carried by a user.
11. 11. The system for a structure of claim 1, wherein said portable pouch is adapted to be placed in a home object.
12. The system for a structure of claim 1, wherein said portable pouch is adapted to be attached to a home object.
13. 13. The system for a structure of claim 1, wherein said portable pouch is adapted to configure said sensors for communication with said server.
14. The system for a structure of claim 1, wherein said portable pouch is adapted to configure said portable pouch for communication with said server.
15. 15. The system for a structure of claim 1, wherein said server is a base station without a head.
16. 16. The system for a structure of Claim 1, wherein said server is a network coordinator for said sensors and said portable pouch.
17. The system for a structure of claim 1, wherein said server, said portable pouch and said sensors form an IEEE 802.11 wireless local area network.
18. The system for a structure of claim 1, wherein said server, said portable pouch and said sensors form an IEEE 802.11 wireless personal area network.
19. The system for a structure of claim 1, wherein said server further includes a processor, which detects a state change in one of said sensors, and which sends said change of state of the wireless communications gate first to the second wireless communications gate of said portable pouch.
20. 20. The system for a structure of claim 19, wherein said portable pouch also includes a processor, which receives said change of state of the second wireless communications gate and which in response drives said screen.
21. 21. The system for a structure of claim 20, wherein said portable pouch also includes an alert device; and wherein the processor of said portable pouch in response drives said warning device in response to said state change.
22. 22. The system for a structure of claim 21, wherein said warning device is one of an audible device, a visual device and a vibrating device.
23. The system for a structure of claim 21, wherein said warning device includes a first back light for said screen and a second back light for said screen; and wherein the processor of said portable pouch in response drives one of said first and second taillights in response to said state change.
24. The system for a structure of claim 1, wherein said sensors periodically send said detected information to the first wireless communications gate of said server; and wherein said portable pouch periodically requests and receives said detected information for said sensors between the first and second wireless communication gates.
25. 25. The system for a structure of claim 24, wherein the screen of said portable pouch includes a plurality of graphic objects corresponding to the detected information received for said sensors.