US 7,650,425 B2Grant
System and method for controlling communication between a host computer and communication devices associated with remote devices in an automated monitoring system
Issue Date:2010-01-19
•12 Claims
•8 Drawing Sheets
Abstract
A site controller adapted to be used in an automated monitoring system for monitoring and controlling a plurality of remote devices via a host computer connected to a first communication network is provided. The site controller is configured for controlling communication with the host computer and a plurality of communication devices that define a second communication network associated with the plurality of remote devices. Briefly described, in one embodiment, the site controller comprises a transceiver configured to communicate with the plurality of communication devices via the second communication network; a network interface device configured to communicate with the host computer via the first communication network; and logic configured to: manage communication with each of the plurality of communication devices, via a first communication protocol, based on one or more communication paths for each of the plurality of communication devices, each communication path comprising one or more communication devices involved in the communication link between the transceiver and each of the plurality of communication devices; and manage communication with the host computer via a second communication protocol.
Metadata
Assignee
- Sipco, LLC
Inventors
- James Davis
- Thomas D. Petite
Application Information
Application Number:US 09/925,786
Filing Date:2001-08-09
Priority Date:1999-03-18
Art Unit:2452
Classifications
IPC:
G06F15/173
Patent Drawings (8 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation-in-part of the following U.S. utility patent applications: U.S. patent application Ser. No. 09/271,517, filed Mar. 18, 1999, and entitled, “System For Monitoring Conditions in a Residential Living Community,”, now abandoned; U.S. patent application Ser. No. 09/439,059, filed Nov. 12, 1999, and entitled, “System and Method for Monitoring and Controlling Remote Devices”, now U.S. Pat. No. 6,437,692, issued Aug. 20, 2002; U.S. patent application Ser. No. 09/812,809, filed Mar. 20, 2001, and entitled, “System and Method for Monitoring the Light Level in a Lighted Area”, now abandoned, which is a continuation-in-part of U.S. patent application Ser. No. 09/412,895, filed Oct. 5, 1999, and entitled, “System For Monitoring the Light Level Around and ATM,” now U.S. Pat. No. 6,218,953, issued Apr. 17, 2001. Each of the identified U.S. patent applications is incorporated herein by reference in its entirety. This application also claims the benefit of U.S. Provisional Application Ser. No. 60/223,943, filed Aug. 9, 2000, and entitled “Design Specifications for a Site Controller” which is hereby incorporated by reference in its entirety.
Field of the Invention
[0002] The present invention generally relates to systems for monitoring and/or controlling a plurality of remote devices via a host computer connected to a wide area network (WAN), and more particularly relates to systems and methods for managing communication between the host computer and the plurality of remote devices.
Background of the Invention
[0003] There are a variety of systems for monitoring and/or controlling any of a number of systems and/or processes, such as, for example, manufacturing processes, inventory systems, emergency control systems, personal security systems, residential systems, and electric utility meters to name a few. In many of these “automated monitoring systems,” a host computer in communication with a wide area network monitors and/or controls a plurality of remote devices arranged within a geographical region. The plurality of remote devices typically use remote sensors and controllers to monitor and respond to various system parameters to reach desired results. A number of automated monitoring systems use computers or dedicated microprocessors in association with appropriate software to process system inputs, model system responses, and control actuators to implement corrections within a system.
[0004] Various schemes have been proposed to facilitate communication between the host computer and the remote devices within the system, including RF transmission, light transmission (including infra-red), and control signal modulation over the local power distribution network. For example, U.S. Pat. No. 4,697,166 to Warnagiris et al. describes a power-line carrier backbone for inter-element communications. As recognized in U.S. Pat. No. 5,471,190 to Zimmerman, there is a growing interest in home automation systems and products that facilitate such systems. One system, critically described in the Zimmerman patent, is the X-10 system. Recognizing that consumers will soon demand interoperability between household systems, appliances, and computing devices, the Electronics Industry Association (EIA) has adopted an industry standard, known as the Consumer Electronics Bus (CEBus). The CEBus is designed to provide reliable communications between suitably configured residential devices through a multi-transmission media approach within a single residence.
[0005] One problem with expanding the use of control systems technology to distributed systems is the cost associated with developing the local sensor-actuator infrastructure necessary to interconnect the various devices. A typical approach to implementing control system technology is to install a local network of hard-wired sensors and actuators along with a local controller. Not only is there expense associated with developing and installing appropriate sensors and actuators, but the added expense of connecting functional sensors and actuators with the local controller is also problematic. Another prohibitive cost is the expense associated with the installation and operational expense associated with programming the local controller.
[0006] Accordingly, an alternative solution for implementing a distributed control system suitable for monitoring and controlling remote devices that overcomes the shortcomings of the prior art is desired.
Summary of the Invention
[0007] To achieve the advantages and novel features, an embodiment of the present invention is generally directed to a cost-effective automated monitoring system and method for monitoring and controlling a plurality of remote devices via a host computer connected to a communication network, such as a wide area network. The automated monitoring system may include one or more sensors to be read and/or actuators to be controlled, ultimately, through a remote applications server via a site controller. The remote applications server and the site controller may communicate via a communication network, such as a wide area network. The sensors and/or actuators are in communication with communication devices, which may be wireless, that transmit and/or receive encoded data and control signals to and from the site controller. Additional communication devices, such as wireless repeaters, may relay information between communication devices disposed in connection with the sensors and/or actuators and the site controller.
[0008] More specifically, the present invention is directed to a site controller adapted to be used in an automated monitoring system for monitoring and controlling a plurality of remote devices via a host computer connected to a first communication network. The site controller is configured for controlling communication with the host computer and a plurality of communication devices that define a second communication network associated with the plurality of remote devices. Briefly described, in one embodiment, the site controller comprises a transceiver configured to communicate with the plurality of communication devices via the second communication network; a network interface device configured to communicate with the host computer via the first communication network; and logic configured to: manage communication with each of the plurality of communication devices, via a first communication protocol, based on one or more communication paths for each of the plurality of communication devices, each communication path comprising one or more communication devices involved in the communication link between the transceiver and each of the plurality of communication devices; and manage communication with the host computer via a second communication protocol.
[0009] The present invention may also be viewed as providing a method for controlling communication with a host computer connected to a first communication network and a plurality of communication devices that define a second communication network associated with a plurality of remote devices that are to be monitored and controlled by the host computer. Briefly, one such method involves the steps of: determining a unique address for each of the plurality of communication devices by receiving an initialization message; determining with which of the plurality of communications devices that each of the plurality of communication devices has a communication link; based on the plurality of unique addresses and which of the plurality of communications devices each of the plurality of communication devices has a communication link with, determining one or more communication paths associated with each of the plurality of communication devices; managing communication with each of the plurality of communication devices, via a first communication protocol, based on one or more of the communication paths associated with each of the plurality of communication devices; and managing communication with the host computer via a second communication protocol.
[0010] Thus, the site controller according to the present invention minimizes cost and complexity by providing a site controller to maintain the bulk of the data needed by the user and by providing simplified and inexpensive communication devices to collect and communicate the data to the site controller. By simplifying the communication devices and maintaining data storage, data organization, etc., at the site controller, initial installation costs are reduced, and future expansions of the automated monitoring system are simple and inexpensive.
Brief Description of the Drawings
[0011] The accompanying drawings incorporated in and forming a part of the specification, illustrate several aspects of the present invention, and together with the description serve to explain the principles of the invention. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
[0012] FIG. 1 is a block diagram illustrating an embodiment of an automated monitoring system according to the present invention.
[0013] FIG. 2 is a block diagram illustrating an embodiment of the site controller of the automated monitoring system of FIG. 1 .
[0014] FIG. 3 is a more detailed schematic diagram illustrating the connectivity of the WAN of FIG. 1 .
[0015] FIG. 4 is a table illustrating an embodiment of a message structure for a communication protocol according to the present invention that may be used for communicating between the site controller and transceivers of FIG. 1 .
[0016] FIG. 5 is a table illustrating various values for the “to address” in the message structure of FIG. 4 .
[0017] FIG. 6 illustrates three sample messages for the message structure of FIG. 4 according to the present invention.
[0018] FIG. 7 illustrates another embodiment of the automated monitoring system according to the present invention.
Detailed Description of the Preferred Embodiments
[0019] Having summarized the invention above, reference is now made in detail to the description of the invention as illustrated in the drawings. While the invention will be described in connection with these drawings, there is no intent to limit it to the embodiment or embodiments disclosed therein. On the contrary, the intent is to cover all alternatives, modifications and equivalents included within the spirit and scope of the invention as defined by the appended claims.
[0020] FIG. 1 is a block diagram illustrating one of a number of possible embodiments of an automated monitoring system 100 according to the present invention. Automated monitoring system 100 may comprise one or more applications servers 110, a database 115, a wide area network (WAN) 120, transceivers/repeaters 125, sensor/actuators 130, transceivers 135, sensors 140, transmitters 145, and at least one site controller 150. Each of the sensor/actuators 130 and sensors 140 is integrated with a suitably configured wireless transceiver/repeater 125, a wireless transceiver 135, or wireless transmitter 145 Within the context of this document, a wireless transceiver/repeater 125, a wireless transceiver 135, and a wireless transmitter 145 will be referred to as “wireless communication devices.”
[0021] Each of the wireless communication devices in automated monitoring system 100 is preferably small in size and may be configured to transmit a relatively low-power signal, such as, for example a radio frequency (RF) signal. As a result, in some applications, the transmission range of a given RF communication device may be relatively limited. Of course, the transmitter power and range may be appropriately designed for the target operating environment. As will be appreciated from the description that follows, this relatively limited transmission range of the wireless communication devices is advantageous and a desirable characteristic of automated monitoring system 100. Although the wireless communication devices are depicted without a user interface such as a keypad, etc., in certain embodiments the wireless communication devices may be configured with user selectable pushbuttons, switches, an alphanumeric keypad, or any other type of user interface device suitably configured with software and/or firmware to accept operator input. Often the wireless communication device will be in communication with a sensor 140 or with a sensor/actuator 130, such as a smoke detector, a thermostat, a security system. etc., where user selectable inputs may not be needed.
[0022] As illustrated in FIG. 1 , the wireless communication devices in automated monitoring system 100 are geographically arranged such that the antenna patterns (not shown) associated with each wireless communication device overlap to create a coverage area 165. In this manner, automated monitoring system 100 may enable a site controller 150 associated with coverage area 165 to communicate with each sensor/actuator 130 and each sensor 140 via any of a plurality of possible communication paths. For instance, site controller 150 may communicate with a specific sensor/actuator 130 via a plurality of distinct communication paths, each of which are defined by one or more wireless communication devices involved in the communication between site controller 150 and the specific sensor/actuator 130. By way of example, one of the plurality of possible communication paths may consist of a wireless connection from site controller 150 to a wireless communication device associated with the specific sensor/actuator 130. Another possible communication path may consist of a wireless connection from site controller 150 to an intermediate wireless communication device and then to the wireless communication device associated with the specific sensor/actuator 130. Further communication paths may include multiple intermediate wireless communication devices in the wireless connection between site controller 150 and the wireless communication device associated with the specific sensor/actuator 130.
[0023] As illustrated in FIG. 1 , one or more sensors 140 may communicate with at least one site controller 150 via a wireless transmitter 145, a wireless transceiver 135, or a wireless transceiver/repeater 125. Furthermore, one or more sensors/actuators 130 may communicate with at least one site controller 150 via a wireless transceiver 135 or a wireless transceiver/repeater 125. One of ordinary skill in the art will appreciate that in order to send a command from the applications server 110 to a sensor/actuator 130, the wireless communication device associated with the sensors/actuators 130 should be a two-way communication device, such as a transceiver. It will also be appreciated that one or more sensors/actuators 130 may be in direct communication with one or more site controllers 150. It will be further appreciated that the communication medium between the one or more sensor/actuators 130 and the one or more site controller 150 may be wireless or, for relatively closely located configurations, a wired communication medium may be used.
[0024] As is further illustrated in FIG. 1 , automated monitoring system 100 may comprise a plurality of stand-alone wireless transceiver/repeaters 125. Each stand-alone wireless transceiver/repeater 125, as well as each wireless transceiver 135, may be configured to receive one or more incoming transmissions (transmitted by a remote transmitter 145 or transceiver 135) and to transmit an outgoing signal. This outgoing signal may be any wireless transmission signal, such as, for example, a low-power RF transmission signal, or a higher-power RF transmission signal. Alternatively, where a wired configuration is employed, the outgoing signal may be transmitted over a conductive wire, fiber optic cable, or other transmission media. One of ordinary skill in the art will appreciate that if an integrated wireless communication device (e.g., a wireless transmitter 145, a wireless transceiver 135, or a wireless transceiver/repeater 125) is located sufficiently close to site controller 150 such that its output signal can be received by at least one site controller 150, the data transmission signal need not be processed and repeated through either a wireless transceiver/repeater 125 or wireless transceivers 135.
[0025] One or more site controllers 150 are configured and disposed to receive remote data transmissions from the various stand-alone wireless transceiver/repeaters 125, integrated wireless transmitters 145, or the integrated wireless transceivers 135. The site controllers 150 may be configured to analyze the transmissions received, convert the transmissions into TCP/IP format, and further communicate the remote data signal transmissions via WAN 120 to one or more applications servers 110 or other devices in communication with WAN 120. One of ordinary skill in the art will appreciate that additional site controllers 150 may function as either a back-up site controller in the event of a site controller failure or can function as a primary site controller to expand the potential size of coverage area 165 of automated monitoring system 100. When implemented as a back-up site controller 150, the second site controller 150 may function when the applications server 110 detects a site controller failure. Alternatively, the second site controller 150 may function to expand the capacity of automated monitoring system 100. A single site controller 150 may accommodate a predetermined number of wireless communication devices. While the number of wireless communication devices may vary based upon individual requirements, in one of a number of embodiments there may be approximately 500 wireless communication devices.
[0026] By way of example, a second site controller 150 may double the capacity of a single system. Although not shown, additional site controllers 150 may be added depending on the specific implementation of automated monitoring system 100. The number of wireless communication devices managed by a site controller 150 is limited only by technical constraints such as memory, storage space, etc. In addition, the site controller 150 may manage more addresses than devices as some wireless communication devices may have multiple functions such as sensing, repeating, etc. As stated above, automated monitoring system 100 includes an applications server 110 in communication with site controller 150 via WAN 120. Applications server 110 may host any of a variety of application specific software depending on the precise environment in which automated monitoring system 100 is employed. As further described below, the site controller 150 may receive, via WAN 120, information in the form of data and/or control signals from applications server 110, laptop computer 155, workstation 160, and any other device in communication with WAN 120 Site controller 150 may then communicate the data and/or control signals to remote sensor/actuators 130 and/or remote sensors 140. Automated monitoring system 100 may also comprise a database 115 associated with applications server 110. Database 115 may be configured to communicate with applications server 110 and record client specific data or to assist the applications server 110 in deciphering a particular data transmission from a particular sensor 140.
[0027] FIG. 2 sets forth one of many possible embodiments of the site controller 150 of FIG. 1 . Site controller 150 may comprise a micro-controller 205, a power supply 210, an on-site input port 215, an antenna 220, and a transceiver 225. One of ordinary skill in the art will appreciate that various other elements may be included based on any of a variety of design needs. The micro-controller 205 may comprise a central processing unit (CPU) 230, memory 235, and one or more network interface devices 240. The CPU 230 may be any of a variety of known controllers, such as, for example, a microprocessor, hard-wired circuitry, firmware, etc. The memory 235 may store any necessary programming code for the CPU 230, as well as one or more look-up tables 270, databases (not shown), etc. Network interface devices 240 may be any of a variety of devices configured for communication with WAN 120. For example, site controller 150 may include a network card configured for communication across a local area network to a network server. The network server may contain a backup site controller (not shown) coupled to WAN 120 (FIG. 1 ). Alternatively, site controller 150 may include a digital subscriber line (DSL) modem 250 configured to provide a link to a remote computing system. In yet another alternative, site controller 150 may include an integrated services digital network (ISDN) card configured for communication via an ISDN connection with a remote system. Other network interfaces may be provided to serve as primary and/or backup links to WAN 120 (FIG. 1 ) or to local area networks (not shown) that might serve to permit local monitoring of the operating status of site controller 150 and for data packet control.
[0028] Depending upon the specific configuration of network interface device(s) 240, site controller 150 may communicate with any of a variety of types of wide area networks. For example, WAN 120 may be any type of communication network, or collection of communication networks, employing any network topology, transmission medium, or network protocol. WAN 120 may be any public or private packet-switched or other data network, including the Internet, circuit-switched networks, such as the public switched telephone network (PSTN), wireless networks, or any other desired communications infrastructure. One of ordinary skill in the art will appreciate that the information transmitted between the wireless communication and site controller 150 may be further integrated with various other data transmission protocols for transmission across telecommunications and computer networks other than the WAN 120 (FIG. 1 ). In addition, it should be further appreciated that communication networks other than WAN 120 (FIG. 1 ) may function as the transmission path between the wireless communication devices, site controller 150, and the applications server 110 (FIG. 1 ).
[0029] Referring again to FIG. 2 , wireless transceiver 225 may be configured to receive incoming transmissions via antenna 220. Each of the incoming transmissions may be consistently formatted in the message protocol as described below. Site controller 150 may be configured such that the memory 235 includes a look-up table 270 configured for identifying the various wireless communication devices (including intermediate wireless communication devices) used in generating and transmitting the received data transmission. As illustrated in FIG. 2 , site controller 150 may include an “Identify Remote Transceiver” memory sector 275 and an “Identify Intermediate Transceiver” memory sector 280. Programmed or recognized codes within the memory 235 may also be provided and configured for controlling the operation of a CPU 230 to carry out the various functions that are orchestrated and/or controlled by the site controller 150. For example, memory 235 may include program code for controlling the operation of the CPU 230 to evaluate an incoming data packet to determine what action needs to be taken. In this regard, one or more look-up tables 270 may also be stored within the memory 235 to assist in this process. Function codes and wireless communication device identifiers transmitter may all be stored with associated information within look-up tables 270.
[0030] Thus, one look-up table 270 may be provided to associate identification information for each wireless communication device with a particular user. Another look-up table 270 may be used to identify the various function codes associated with the message protocol. For example, a look-up table 270 may include a unique code designating various functions such as test, temperature, smoke alarm active, security system breach, etc. One of ordinary skill in the art will appreciate that various function codes may be implemented depending on the specific implementation of automated monitoring system 100. In connection with lookup table(s) 270, memory 235 may also include one or more code segments that are executed by the CPU 230 and configured to control operation of the site controller 150. For example, a first data packet segment may be configured for accessing a first lookup table to determine the identity of the wireless communication device that transmitted the received message to the site controller 150. A second code segment may be configured for accessing a second look-up table to determine the proximate location of the wireless communication device that generated the received message. A third code segment may be provided to identify the content of the message transmitted (not shown). Namely, is it a fire alarm, a security alarm, an emergency request by a person, a temperature control setting, etc. In accordance with the present invention, additional, fewer, or different code segments may be provided to carry out various functional operations and data signal transfers.
[0031] The power supply 210 may be one of the following: AC power supply, AC power supply with rechargeable battery as a back up solar cells, battery, etc. The power supply provides appropriate DC voltage levels to microcontroller 230. The AC power supply may operate from an external, commonly-provided outside AC power line. The battery may be a lead acid gel battery or other appropriate battery for the prevailing environmental and other conditions that could be considered by those of ordinary skill in the art. The battery may maintain the site controller 150 fully operational for a predetermined time period. This time period may be varied based upon the individual site and system criteria as would be obvious to one of ordinary skill in the art. The battery may also be supplied with a recharger that can recharge the battery to full capacity within a predetermined time period. The charging time may be varied based upon individual site and system criteria as would be obvious to one of ordinary skill in the art. The microcontroller 230 may monitor the battery on a periodic basis and report the battery condition to the applications server 110.
[0032] In addition, the power supply 210 may accommodate AC voltages between approximately 95–135 V. It would be obvious to one of ordinary skill in the art to modify this supplied voltage range depending upon individual designs. For example, the supplied voltage range may be varied to accommodate any of a variety of standard supply voltages. Furthermore, the power supply 210 may maintain the temperature of site controller 150 within an acceptable working range, such as approximately 5° C. above the ambient temperature. The operating temperature of the site controller 150 depends upon individual system and environmental conditions. Therefore, it would be obvious to one of ordinary skill in the art to maintain the system at an appropriate operating temperature. This can be accomplished by distributing and/or removing the heat from the power supply 210, adding a heater or various cooling devices, etc. as known by one of ordinary skill in the art.
[0033] The on-site input port 215 may be configured to enable an on-site technician to communicate with the microcontroller 230. By way of example, the on-site input port 215 may be a serial port, a USB port, etc. as would be known to one of ordinary skill in the art. The technician may communicate with the on-site input port 215 via any of a variety of computing devices, such as a laptop, personal digital assistant (PDA), or any other computing device. The on-site input port 215 may be used for initial programming updates and other functions as necessary. In addition to on-site programming via the on-site input port 215, the site controller 150 may be reprogrammed via the applications server 110 (FIG. 1 ).
[0034] The transceiver 225 may be a TR1000 hybrid transceiver, which is well-suited for short range, wireless data applications where robust operation, small size, low power consumption, and low-cost are desired. All of the critical wireless functions may be contained within the single hybrid chip to simplify circuit design and accelerate the design process. The receiver section of the TR1000 may preferably be sensitive and stable. A wide dynamic range log detector may be employed, in combination with digital automatic gain control (AGC) to provide robust performance in the presence of channel noise or interference. Two stages of surface acoustic wave (SAW) filtering may provide excellent receiver out-of-band rejection. The transmitter may be configured for both on-off keyed (OOK) and amplitude-shift key (ASK) modulation. The transmitter may be configured for employing SAW filtering to suppress output harmonics in compliance with FCC and other regulations. One of ordinary skill in the art will appreciate that transceiver 225 may be configured in a variety of ways. For example, transceiver 225 may include other 900 MHz transceivers, as well as transceivers at other frequencies. In addition, infrared, ultrasonic, and other types of transceivers may be employed, consistent with the scope of the present invention.
[0035] The antenna 220 radiates the signal transmitted by the transceiver 225 to the various wireless communication devices located within coverage area 165. A specific antenna type may be selected based on the frequency at which the signal is to be transmitted. In addition, the antenna 220 may be adjustably oriented as required to maximize both transmission and signal characteristics. Non-limiting examples of antenna types that may be used by the site controller 150 include dipoles, spiral, logarithmic, etc.
[0036] The site controller 150 may also be equipped to operate in a wide range of temperatures and humidity levels to provide a consistently operating system. In addition, the site controller 150 may be protected from static discharges and direct contact discharges, such as lightening strikes. To provide consistent operation, the site controller 150 may be shielded to avoid interference from a wide range of electric field and AC line noise.
[0037] Significantly, the site controller 150 may communicate with all of the wireless communication devices. Of further significance, the data monitoring and control devices need not be disposed in a permanent location as long as they remain within signal range of a repeating wireless communication device that is within signal range of a site controller 150 that is interconnected through one or more communication networks to the applications server 110. Of still further significance, the automated monitoring system 100, as illustrated in FIG. 1 , provides a flexible access and control solution through virtually any suitably configured computing device in communication with the WAN 120. By way of example, a laptop computer 155 and/or a computer workstation 160 appropriately configured with suitable software may provide remote operator access to data collected via automated monitoring system 100. In more robust embodiments, the laptop computer 155 and the computer workstation 160 may permit a user to enter remote operative commands.
[0038] In one embodiment of automated monitoring system 100, an applications server 110 (FIG. 1 ) collects, formats, and stores client specific data from each of the integrated wireless transmitters 145, wireless transceivers 135, and/or wireless transceiver/repeaters 125 for later retrieval and/or access from, for example, workstation 160 or laptop 155. Workstation 160 or laptop 155 may be used to access the stored information in a variety of ways, such as via a web browser. In another embodiment, the applications server 110 may host application specific functions associated with automated monitoring system 100, thereby replacing site controller 150 by generating required control signals for appropriate distribution via the WAN 120 and the site controller 150 to the sensor/actuators 130 and the sensors 140. In a further embodiment, clients may elect, for proprietary reasons, to host control applications on their own workstation 160 that is connected to WAN 120. In this manner, database 115 and applications server 110 may function solely as data collection and reporting devices with the client workstation 160 generating control signals for the system.
[0039] Reference is now made to FIG. 3 , which illustrates the external connectivity of WAN 120 of FIG. 1 in accordance with the present invention. Site controller 150 may be configured to transmit control signals and receive data signals using the open data packet protocol described in detail below. Site controller 150 is preferably interconnected permanently on WAN 120 and configured to receive data signals from the wireless communication devices and translate the data signals for transfer to applications servers 110 via WAN 120. Site controller 150 may translate the received data signals into any appropriate protocol for delivery via WAN 120. For example, in one embodiment site controller 150 translates the received data signals into transmission control protocol/Internet protocol (TCP/IP) for delivery via WAN 120. As stated above, applications server 110 may be configured for communication with WAN 120 via, for example, router 310 and further protected and buffered by firewall 320. Applications server 110 may also be configured with web applications and client specific applications as needed for operation of automated monitoring system 100. Consistent with the concepts and teachings of the present invention, applications server 110 may be assisted in its task of storing and making available client specific data by database 115.
[0040] As further illustrated in FIG. 3 , a client workstation 160 may include a Web browser for facilitating communication with applications server 110, database 115, and/or site controller 150. Alternatively, clients may access WAN 120 via a remote laptop 155 or other computing devices (not shown) configured with a compatible Web browser or other user interface. In this way, the applications server 110 may provide client specific data upon demand.
[0041] As stated above, communication between site controller 150 and sensors/actuators 130 and sensors 140 is accomplished using an open data packet protocol in accordance with the present invention. Because the wireless communication devices are geographically arranged such that their respective antenna patterns overlap to create a coverage area 165, site controller 150 may communicate with each sensor/actuator 130 and each sensor 140 via any of a plurality of possible communication paths. Each of the communication paths are defined by one or more wireless communication devices involved in the communication between site controller 150 and the target sensor/actuator 130 and/or sensor 140. For instance, site controller 150 may communicate with a specific sensor/actuator 130 via a plurality of distinct communication paths. By way of example, one of the plurality of possible communication paths may consist of a wireless connection from site controller 150 to a wireless communication device associated with the specific sensor/actuator 130. Another possible communication path may consist of a wireless connection from site controller 150 to an intermediate wireless communication device and then to the wireless communication device associated with the specific sensor/actuator 130. Further communication paths may include multiple intermediate wireless communication devices in the wireless connection between site controller 150 and the wireless communication device associated with the specific sensor/actuator 130. In this manner, site controller 150 may communicate with sensors/actuators 130 and/or sensors 140 that are located a greater distance from the site controller 150 by having messages repeated by successive wireless communication devices along one of the communication paths.
[0042] FIG. 4 sets forth a format for the open data packet protocol of the present invention. All messages transmitted within automated monitoring system 100 consist of a “to” address 400, a “from” address 410, a packet number 420, a number of packets in a transmission 430, a packet length 440, a message number 450, a command number 460, data field 470, and a check sum error detector (CkH 480 and CkL 490).
[0043] The “to” address 400 indicates the intended recipient of the packet. This address can be scalable from one to six bytes based upon the size and complexity of the system. By way of example, the “to” address 400 can indicate a general message to all wireless communication devices, to only the stand-alone wireless communication devices, or to an individual integrated wireless communication device. In a six byte “to” address, the first byte indicates the type of the wireless communication device—to all wireless communication devices, to some wireless communication devices, or to a specific wireless communication device. The second byte can be the identification base, and bytes three through six can be used for the unique address of the wireless communication device (either stand-alone or integrated). The “to” address 400 is scalable from one byte to six bytes depending upon the intended recipient(s).
[0044] The “from” address 410 may be the six-byte unique address associated with the device from which the transmission originated. The “from” address 410 may be the address of the site controller 150 when the site controller 150 requests data, or this can be the address of one of the wireless communication devices responding to a request for information from the site controller 150.
[0045] The packet number 420, the packet maximum 430, and the packet length 440 may be used to concatenate messages that are greater than a predetermined byte length. The packet maximum 430 indicates the number of packets in the message The packet number 420 may be used to indicate a packet sequence number for a multiple-packet message.
[0046] The message number 450 may originally be assigned by the site controller 150 Messages originating from the site controller 150 may be assigned an even number, while responses to the site controller 150 may be the original message number plus one, thereby rendering the responding message with an odd number. For example, the site controller 150 may increment the message number 450 by two for each new originating message. This enables the site controller to coordinate the incoming responses to the appropriate command message.
[0047] The command number 460 may designate a specific data request from the receiving device as necessary. One of ordinary skill in the art will appreciate that, depending on the specific implementation of automated monitoring system 100, the types of commands may differ. In one embodiment, there may be two types of commands: device specific and not device specific. Device specific commands may control a specific device, such as a data request or a change in current actuator settings. Commands that are not device specific may include, but are not limited to, a ping, an acknowledgement, a non-acknowledgement, downstream repeat, upstream repeat, read status, emergency message, and a request for general data to name a few. General data may include a software version number, the number of power failures, the number of resets, etc.
[0048] The data field 470 may contain data as requested by a specific command. The requested data may be any value. By way of example, test data may preferably be encoded in ASCII (American Standard Code for Information Interchange) or other known encoding systems as known in the art. The data field 470 of a single packet may be scalable up to a predetermined byte length. When the requested data exceeds the predetermined byte length, the integrated wireless communication device may divide the data into an appropriate number of sections and concatenate the series of packets for one message using the packet identifiers as discussed above.
[0049] The checksum fields 480 and 490 are used to detect errors in transmissions. In one embodiment, any error can be detected via cyclic redundancy check sum methodology. This methodology divides the message as a large binary number by the generating polynomial (in this case, CRC-16). The remainder of this division is then sent with the message as the checksum. The receiver then calculates a checksum using the same methodology and compares the two checksums. If the checksums do not match, the packet or message will be ignored. While this error detection methodology is preferred, one of ordinary skill in the art will appreciate that various other error detection methodologies may be implemented.
[0050] As stated above, automated monitoring system 100 may employ wireless and/or wired communication technologies for communication between site controller 150 and the wireless communication devices. In one embodiment, communication between site controller 150 and the wireless communication devices within coverage area 165 may be implemented using a wireless link having a basic rate of 4,800 bits per second (bps) and a data rate of 2400 bps. All the data may be encoded in the Manchester format such that a high to low transition at the bit center point represents a logic zero and a low to high transition represents a logic one. One of ordinary skill in the art will appreciate that other signal formats may be used as desired. By way of example, a quadature phase shift encoding method may be used, thereby enabling the site controller 150 to communicate via hexadecimal instead of binary. The site controller 150 may use any predetermined RF transmission method to transmit the messages. In one embodiment, a transmission frequency of approximately 916.5 MHz may be employed, although one of ordinary skill in the art will appreciate that any other frequency may be desirable. Alternatively, the transmission can be on a predetermined range of frequencies such as with spread spectrum technology. Furthermore, the message may be modulated using any technique, such as on-off keying, frequency modulation (FM), or any other modulation technique.
[0051] While the message indicates the specific byte length for each section, only the order of the specific information within the message is constant. The byte position number in individual transmissions may vary because of the scalability of “to” address 400, command number 460, and the scalability of data field 470.
[0052] The message may further include a preface and a postscript (not shown). The preface and postscripts need not be part of the message body, but rather provide synchronization and frame each packet of the message. The packet may begin with the preface and end with the postscript. The preface may be, for example, a series of twenty-four logic ones followed by two bit times of high voltage with no transition. The first byte of the packet may then follow immediately. The postscript may be, for example, a transition of the transmit data line from a high voltage to a low voltage. It may be less desirable to not leave the transmit data line high after the message is sent. Furthermore, one of ordinary skill in the art will appreciate that the preface and postscript may be modified in a number of ways.
[0053] FIG. 5 illustrates one embodiment of a byte assignment for the “to” address 400 of FIG. 4 . One of ordinary skill in the art will appreciate that various byte assignments may be used within “to” address field 400. For example, in one embodiment, “to” address 400 consists of six bytes. The first byte (Byte 1) may indicate the device type. The second byte (Byte 2) may indicate the manufacturer or the owner. The third byte (Byte 3) may be a further indication of the manufacturer or owner. The fourth byte (Byte 4) may indicate either that the message is for all devices or that the message is for a particular device. If the message is for all devices, the fourth by may be a particular code. If the message is for a particular device, the fourth, fifth, and sixth bytes (Byte 5 and Byte 6) may include the unique identifier for that particular device.
[0054] Having described the general message structure for the open data packet protocol of the present invention, reference is directed to FIG. 6 , which illustrates three sample messages. The first message 600 illustrates the broadcast of an emergency message “FF” from a central server with an address “0012345678” to a integrated transceiver with an address of “FF.”
[0055] The second message 602 illustrates how the first message 600 may be sent to a stand-alone wireless communication device. In this manner, emergency message “FF” from a central server with address “00123456578” is first sent to stand-alone wireless device “FO.” The second message 602, further contains additional command data “A000123456” that may be used by the wireless communication device to identify further wireless communication devices to send the signal through on the way to the destination device.
[0056] The third message 604 illustrates how the open data packet protocol of the present invention may be used to “ping” a remote wireless communication device in order to determine the status of the wireless communication device. In this manner, source unit “E112345678” originates a ping request by sending command “08” to a transceiver identified as “A012345678.” The response to the ping request may be as simple as reversing the “to address” and the “from address” of the command such that a healthy wireless communication device may send a ping message back to the originating device. Automated monitoring system 100 may be configured to expect a return ping within a specific time period. Operators of automated monitoring system 100 may use the delay between the ping request and the ping response to model system loads and to determine if specific system parameters might be adequately monitored and controlled with the expected feedback transmission delay.
[0057] Further information regarding the structure and operation of the data packet protocol implemented in automated monitoring system 100 may be found in commonly assigned U.S. Patent Application “System and Method for Interconnecting Remote Devices in an Automated Monitoring System,” (Ser. No. 09/925,445) which is hereby incorporated in its entirety by reference.
[0058] Referring again to FIG. 1 , during normal operations, the site controller 150 acts as the communications master. Thus, the site controller 150 may initiate all communications with the wireless communications devices, except emergency messages described below. In addition to initiating command messages, the site controller 150 also tracks response messages. This tracking allows the site controller 150 to monitor the operational status of the wireless communication devices.
[0059] In addition to orchestrating communications with the wireless communication devices, the site controller 150 maintains current databases of information regarding the automated monitoring system 100, such as, for example, the function of the wireless communication devices, the unique address for each of the wireless communication devices, and current data contained in response messages. One of ordinary skill in the art will appreciate that site controller 150 may contain information related to any of a variety of other aspects of automated monitoring system 100.
[0060] As stated above, the site controller 150 also controls communications with the applications server 110. When communicating with the applications server 110, the site controller 150 receives requests for information, commands, etc. and sends the appropriate response. The applications server 110 maintains the requested information and/or commands in such a way that a user can access the information via a remote desktop 155, remote laptop 160, or any other device configured for communication with WAN 120.
[0061] Furthermore, the site controller 150 may be configured to maintain a database of the wireless communication devices and their unique addresses. The unique addresses may be assigned such that the site controller 150 may easily send messages to one wireless communication device, a group of wireless communication devices, or all of the wireless communication devices.
[0062] Using the site controller 150 as a communications master and maintaining individual device information at the site controller 150 enables the wireless communication devices to be simplified. The simplification of the wireless communication devices has two main advantages: (1) simplifying the construction of the wireless communication device and (2) decreasing cost. The wireless communication device may be simplified because of a reduced need for large memory and/or storage devices. As well-known in the art, memory and storage devices increase in cost as they increase in size. Therefore, decreasing the size of the memory and/or storage reduces the construction and operating costs of the wireless communication devices.
[0063] The site controller 150 sends messages to the wireless communication devices using the open data packet protocol described above. Initially, the site controller 150 maps all of the wireless communication devices so as to “learn” all the unique addresses and the necessary communication paths. To do this mapping, the site controller 150 issues a command to document the down-stream addresses and the upstream addresses for each communication path associated with a wireless communication device. The site controller 150 logs the response data from the wireless communication devices into the appropriate databases. Messages from the site controller 150 travel downstream to the intended wireless communication device(s). Messages from the wireless communication devices(s) travel upstream to the site controller 150. When mapping the communication paths for each of the wireless communication devices, the site controller 150 “learns” the unique address of each wireless communication device, the addresses of each wireless communication device that can directly and reliably communicate with each transceiver/repeater(s) 125 in a downstream path, the unique address of each transceiver/repeater(s) 125 in a downstream path, the upstream addresses for the wireless communication device, and the downstream addresses for the wireless communication device.
[0064] When sending command messages, the site controller 150 expects an acknowledgement to each command. A command is considered to be not acknowledged when either the site controller 150 fails to receive a positive acknowledgement from the addressed wireless communication device within a first time period, fails to detect the re-transmission of the command message by a transceiver/repeater 125 within a second time period, or receives a negative acknowledgement from a transceiver/repeater 125 in the communication path of the wireless communication device. If the site controller 150 receives a negative acknowledgement, the site controller 150 can then log the failed message and retransmit the message. This re-transmission can occur a predetermined number of times. It should be noted the first time period may be longer than the second time period. In the above cases, the first time period is long enough to ensure receipt of the preamble of the response message when there are multiple transceiver/repeater(s) 125 in the communications path. The second time period is long enough to either receive the preamble of the response message (if no repeaters are in the communications path) or to hear the preamble of the command message being re-transmitted by the first transceiver/repeater 125 in the communication path of the wireless communication device.
[0065] After initializing and during normal operation, the site controller 150 may poll each of the remote sensor/actuators according to a predetermined schedule. During this process, the site controller 150 requests the current operating status of each of the sensors/actuators 135. The status of a sensor/actuator device 135 depends upon the type of device. For example, a smoke detector's status may be operational/non-operational. In contrast, a utility meter's status may be the utility usage that has occurred since the last polling. A thermostat's status response may be the actual temperature and the desired temperature. The information sent in response to a status poll may vary depending upon the particular configuration of the sensor/actuator 135. This information is maintained by the site controller 150 and may be sent to the applications server 110 upon request. The predetermined schedule has flexibility based upon the number of failed attempts and any emergency messages. To poll the device, the site controller 150 sends a “read status” message. The command message is considered complete upon receipt of the response message. The command message is considered failed upon receipt of a negative acknowledgement. After a negative acknowledgement, the site controller 150 retries the command six more times and logs all failed attempts.
[0066] To facilitate communications with the applications server 110, the site controller 150 may maintain database files of information. The site controller 150 may maintain communication databases that store the device failures, as discussed above, and that store the emergency messages. These database stored logs can contain the unique address of the wireless communication device, a code representing a present condition, and a date/time stamp. Any failures to communicate with the applications server 110 are also logged into the appropriate database. These databases may have a predetermined size and may be forwarded to the applications server 110 when the databases are a specific percentage full or upon request by the applications server 110. Once forwarded to and acknowledged by the applications server 110, the entries in the communications databases are deleted. One of ordinary skill in the art will appreciate that the contents, size, and scheduling of database entries may be varied in a variety of ways.
[0067] After mapping the wireless communication devices, the site controller 150 develops and maintains a database that includes the unique address for each wireless communication device, the number of transceiver/repeaters 125 in the downstream path, the address of each transceiver/repeater 125 in the downstream path, the upstream addresses, and the downstream addresses. The site controller 150 does not necessarily respond to the messages from wireless communication device s not listed in this database.
[0068] In addition to mapping the wireless communication devices, the site controller 150 may update the device database via the applications server 110. This update may add/delete wireless communication devices from the automated monitoring system 100, change the communications path of any or all of the wireless communication devices, or change the unique addresses of any or all of the wireless communication devices. Upon request of the applications server 110, the site controller 150 may transmit the device database to the applications server 110.
[0069] It should be noted that the databases enumerated above are merely exemplary, and other databases may be included as would be obvious to one of ordinary skill in the art.
[0070] The “normal” operating procedure described above is continued unless the site controller 150 receives an emergency message from a wireless communication device. The emergency message is transmitted unsolicited. The emergency message can be received by the site controller 150 either directly, via a repeater, or via a plurality of repeaters. Upon receipt of an emergency message, the site controller 150 immediately notifies the applications server 110 of the emergency message. In addition, the site controller 150 suspends the above polling for a predetermined time period. This suspension insures the receipt of any additional emergency messages. After the time period expires with no additional messages, the site controller 150 resumes polling.
[0071] To facilitate communications between the applications server 110 and the site controller 150, the site controller 110 maintains a database of contact information. By way of example, if the site controller 150 communicates via a network interface device 240, the site controller 150 can maintain a database of telephone numbers and IP addresses of the applications server 110.
[0072] During normal communications, the applications server 110 sends response messages. As stated above, one of ordinary skill in the art will appreciate that the applications server 110 and the site controller 150 may communicate via TCP/IP protocol or any other protocol. Exemplary requests include a “get file” request of the database and a “put file” request, which sends a file to the site controller 150.
[0073] Normal communications between the site controller 150 and the applications server 110 may also be interrupted by an emergency message. The emergency message originates at the site controller 150 and may include an emergency message from a remote device, a “file too large” message, and a site controller status change message to name a few. In the case of safety and security system devices such as smoke detectors, glass break alarms, etc., the site controller 150 may immediately generate an emergency message to the applications server 110 in the event a safety/security device fails to respond to a poll message.
[0074] One of ordinary skill in the art will appreciate that what has been described herein is a very top-level illustration of a system constructed in accordance with the automated monitoring system 100 of the present invention. In accordance with the invention, a variety of remote devices, such as utility meter devices, personal security devices, household devices and appliances, and other remote devices employing a sensor and/or an actuator, may be monitored and/or controlled from a remote location via a computing device connected to WAN 120. The data and command transmissions may be transmitted and received by the site controller 150 connected to WAN 120. Site controller 150 is further in communication with the wireless communication devices within coverage area 165. The data and command transmissions may be relayed via the various wireless communication devices defining the communication path until they reach a designated destination or the site controller 150.
[0075] It will be further appreciated that automated monitoring system 100 in accordance with the present invention may be used in a variety of environments. In one embodiment, automated monitoring system 100 may be employed to monitor and record utility usage by residential and industrial customers, to transfer vehicle diagnostics from an automobile via a wireless transceiver integrated with the vehicle diagnostics bus to a local transceiver that further transmits the vehicle information through a local gateway onto a WAN, to monitor and control all irrigation system, to automate a parking facility, to monitor and control a residential security system, etc, which are described in more detail in the commonly assigned U.S. patent application Ser. No. 09/704,150, and entitled, “System and Method for Monitoring and Controlling Residential Devices,”, now U.S. Pat. No. 6,891,838, issued May 10, 2005.
[0076] Automated monitoring system 100 may be adapted to monitor and apply control signals in an unlimited number of applications. By way of example only, the wireless communication devices may be adapted for use with any associated device, such as, for example, pay type publicly located telephones, cable television set top boxes, utility meters, and residential appliances and/or devices to enable a remote controllable home automation and security system.
[0077] In a geographic area appropriately networked with permanently located stand-alone transceivers 125, personal transceivers (not shown) may be used to monitor and control personnel access and egress from specific rooms or portions thereof within a controlled facility. Personal transceivers may further be configured to transfer personal information to public emergency response personnel, to transfer personal billing information to vending machines, or to monitor individuals within an assisted living community.
[0078] Wireless communication devices using the open data packet protocol of the present invention may be integrated to monitor and control a host of industrial and business applications as well. By way of example only, building automation systems, fire control systems, alarm systems, industrial trash compactors, and building elevators may be monitored and controlled. In addition, courier drop boxes, time clock systems, automated teller machines, self-service copy machines, and other self-service devices may be monitored and controlled as appropriate. By way of further example, a number of environment variables that require monitoring may be integrated with automated monitoring system 100 to permit remote monitoring and control. For instance, light levels in the area adjacent to automated teller machines must meet minimum federal standards. Also, the water volume transferred by water treatment plant pumps, smokestack emissions from a coal burning power plant, or a coke fueled steel plant oven may be remotely monitored.
[0079] The wireless communication devices using the open data packet protocol of the present invention may be further integrated with a voice-band transceiver having multiple function buttons. As a result, when a person presses, for example, the emergency button on his/her transmitter, medical personnel, staff members, or others may respond by communicating via two-way radio with the party in distress. In this regard, each transceiver may be equipped with a microphone and a speaker that would allow a person to communicate information such as their present emergency situation, their specific location, etc.
[0080] As an example, FIG. 7 sets forth an alternate embodiment of an automated monitoring system 100. Automated monitoring system 100 of FIG. 1 is shown with an additional sensor 180 and transceiver 185. The additional sensor 180 and transceiver 185 are shown to be communicating with, but outside of, the coverage area 165. In this example, the additional sensor 180 and transceiver 185 may be placed outside of the original control system. In order to communicate, the coverage area of transceiver 185 need only overlap the coverage area 165. By way of example only, the original installation may be an automated monitoring system 100 that monitors electricity usage via the utility meters in an apartment complex. Later a neighbor in a single family residence nearby the apartment complex may remotely monitor and control their thermostat by installing a sensor/actuator transceiver according to the present invention. The transceiver 185 then communicates with the site controller 150 of the apartment complex. If necessary, repeaters (not shown) can also be installed to communicate between the transceiver 185 and the apartment complex site controller 150. Without having the cost of the site controller 150, the neighbor may enjoy the benefits of the control system.
[0081] The foregoing description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obvious modifications or variations are possible in light of the above teachings. For example, it should be appreciated that, in some implementations, the transceiver unique address is not necessary to identify the location of the transceiver. Indeed, in implementations where the transceiver is permanently integrated into an alarm sensor other stationary device within a system, then the applications server 110 and/or the site controller 150 may be configured to identify the transmitter location by the transmitter unique address alone. It will be appreciated that, in embodiments that do not utilize wireless transceiver/repeaters 125, the wireless transmitters 145 and/or wireless transceivers 135 may be configured to transmit at a higher power level, in order to effectively communicate with the site controller 150.
[0082] The embodiment or embodiments discussed were chosen and described to illustrate the principles of the invention and its practical application to enable one of ordinary skill in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. All such modifications and variations are within the scope of the invention as determined by the appended claims when interpreted in accordance with the breadth to which they are fairly and legally entitled.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
The invention claimed is:
1. A method for controlling communication with a host computer connected to a first communication network and a plurality of communication devices that define a second communication network associated with a plurality of remote devices that are to be monitored and controlled by the host computer, the method comprising the steps of:
sending a path determination message to a target communication device from a site controller through the second communication network prompting the target communication device to retransmit the path determination message to the site controller through the second communication network,
generating a network map of all down-stream communication paths from the site controller to the target communication device and all up-stream communication paths from the target communication device to the site controller from the unique addresses of the communication devices that retransmitted the path determination message from the site controller to the target communication device or from the target communication device to the site controller,
based on the network map, determining one or more up-stream and down-stream communication paths associated with each of the plurality of communication devices;
managing communication with each of the plurality of communication devices and the identification of each of the plurality of communication devices in the one or more communication paths, via a first communication protocol, based on one or more of the communication paths associated with each of the plurality of communication devices;
managing communication with the host computer via a second communication protocol;
storing on the site controller a first look-up table for identifying each of the plurality of communication devices that define a second communication network; and
storing on the site controller a second look-up table for identifying a function to be performed by the site controller based upon an analysis of a message received from any one of the plurality of communication devices that define a second communication network.
2. The method of claim 1, wherein each of the plurality of communication devices are wireless communication devices, the plurality of wireless communication devices being disposed throughout a geographic area such that the antenna patterns associated with the plurality of wireless communication devices overlap to create a coverage area that defines the second communication network.
3. The method of claim 1, wherein the first communication network is a wide area network and the second communication protocol comprises TCP/IP.
4. The method of claim 1, further comprising the step of managing communication with each of the plurality of communication devices, via a first communication protocol, based on one or more of the communication paths associated with each of the plurality of communication devices wherein the first communication protocol comprises a data packet, the data packet comprising:
a to address;
a from address; and
a command number comprising as function code.
5. The method of claim 4, wherein the data packet further comprises:
a data field;
a checksum field;
a packet number field;
a packet length field;
a packet maximum field; and
a message number field.
6. The method of claim 1, further comprising the steps of:
receiving a request, via the first communication network, from the host computer for information related to one of the plurality of remote devices;
providing a command message to the second communication network for delivery to the one of the plurality of remote devices based on one of the communication paths associated with the communication device corresponding to the one of the plurality of remote devices.
7. The method of claim 6, further comprising the step of receiving a response message, via the second communication network, that is generated by the communication device corresponding to the one of the plurality of remote devices, the response message comprising a first communication device identifier associated with the communication device associated with the one of the plurality of remote devices and a predetermined function code corresponding to a data signal provided by the one of the plurality of remote devices associated with the communication device that generated the response message; and
determining, based on the first communication device identifier, the communication device that generated the first data signal.
8. The method of claim 7, comprising the step of providing the data signal to the first communication network for delivery to the host computer.
9. A method for controlling communication with a host computer connected to a first communication network and a plurality of communication devices that define a second communication network associated with a plurality of remote devices that are to be monitored and controlled by the host computer, the method comprising:
sending a path determination message to each communication device from a site controller through the second communication network prompting each communication device to retransmit the path determination message to the site controller through the second communication network;
generating a map of the entire network from the unique addresses of every communication device that retransmitted each path determination message from the site controller to each communication device or from each communication device to the site controller;
based on the network map, determining one or more up-stream and down-stream communication paths between the controller and each communication device;
managing communication between the controller and each of the communication devices based upon the network map and through a first communication protocol;
managing communication between the controller and the host computer through a second communication protocol;
the site controller translating a message from the host computer to a communication device in the second communication network from the second communication protocol into the first communication protocol; and
storing on the site controller a first look-up table for identifying each of the plurality of communication devices that define a second communication network; and
storing on the site controller a second look-up table for identifying a function to be performed by the site controller based upon an analysis of a message received from any one of the plurality of communication devices that define a second communication network.
10. The method of claim 9 further comprising, the site controller translating a message from a communication device in the second communication network to the host computer from the first communication protocol into the second communication protocol.
11. The method of claim 9, wherein a message from any one of the communication devices that define a second communication network to the host computer contains a preface and a postscript.
12. The method of claim 9, wherein the first communication protocol is an open data packet protocol.
Patent Citations (632)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3665475(A) | 1972-05-01 | Gram | Applicant |
| US3705385(A) | 1972-12-01 | Batz | Applicant |
| US3723876(A) | 1973-03-01 | Seaborn, Jr. | Applicant |
| US3742142(A) | 1973-06-01 | Martin | Applicant |
| US3848231(A) | 1974-11-01 | Wooten | Applicant |
| US3892848(A) | 1975-07-01 | Constable | Applicant |
| US3906460(A) | 1975-09-01 | Halpern | Applicant |
| US3914692(A) | 1975-10-01 | Seaborn, Jr. | Applicant |
| US3922492(A) | 1975-11-01 | Lumsden | Applicant |
| US3925763(A) | 1975-12-01 | Wadwhani et al. | Applicant |
| US4025315(A) | 1977-05-01 | Mazelli | Applicant |
| US4056684(A) | 1977-11-01 | Lindstrom | Applicant |
| US4058672(A) | 1977-11-01 | Crager et al. | Applicant |
| US4083003(A) | 1978-04-01 | Haemmig | Applicant |
| US4120452(A) | 1978-10-01 | Kimura et al. | Applicant |
| US4124839(A) | 1978-11-01 | Cohen | Applicant |
| US4135181(A) | 1979-01-01 | Bogacki et al. | Applicant |
| US4204195(A) | 1980-05-01 | Bogacki | Applicant |
| US4213119(A) | 1980-07-01 | Ward et al. | Applicant |
| US4277837(A) | 1981-07-01 | Stuckert | Applicant |
| US4278975(A) | 1981-07-01 | Kimura et al. | Applicant |
| US4354181(A) | 1982-10-01 | Spletzer | Applicant |
| US4396910(A) | 1983-08-01 | Enemark et al. | Applicant |
| US4396915(A) | 1983-08-01 | Farnsworth et al. | Applicant |
| US4417450(A) | 1983-11-01 | Morgan, Jr. et al. | Applicant |
| US4436957(A) | 1984-03-01 | Mazza | Applicant |
| US4446454(A) | 1984-05-01 | Pyle | Applicant |
| US4446458(A) | 1984-05-01 | Cook | Applicant |
| US4454414(A) | 1984-06-01 | Benton | Applicant |
| US4468656(A) | 1984-08-01 | Clifford et al. | Applicant |
| US4488152(A) | 1984-12-01 | Arnason et al. | Applicant |
| US4495496(A) | 1985-01-01 | Miller, III | Applicant |
| US4551719(A) | 1985-11-01 | Carlin et al. | Applicant |
| US4611198(A) | 1986-09-01 | Levinson et al. | Applicant |
| US4621263(A) | 1986-11-01 | Takenaka et al. | Applicant |
| US4630035(A) | 1986-12-01 | Stahl et al. | Applicant |
| US4631357(A) | 1986-12-01 | Grunig | Applicant |
| US4670739(A) | 1987-06-01 | Kelly, Jr. | Applicant |
| US4692761(A) | 1987-09-01 | Robinton | Applicant |
| US4707852(A) | 1987-11-01 | Jahr et al. | Applicant |
| US4731810(A) | 1988-03-01 | Watkins | Applicant |
| US4742296(A) | 1988-05-01 | Petr et al. | Applicant |
| US4757185(A) | 1988-07-01 | Onishi | Applicant |
| US4788721(A) | 1988-11-01 | Krishnan et al. | Applicant |
| US4800543(A) | 1989-01-01 | Lyndon-James et al. | Applicant |
| US4825457(A) | 1989-04-01 | Lebowitz | Applicant |
| US4829561(A) | 1989-05-01 | Matheny | Applicant |
| US4849815(A) | 1989-07-01 | Streck | Applicant |
| US4851654(A) | 1989-07-01 | Nitta | Applicant |
| US4856046(A) | 1989-08-01 | Streck et al. | Applicant |
| US4857912(A) | 1989-08-01 | Everett, Jr. et al. | Applicant |
| US4875231(A) | 1989-10-01 | Hara et al. | Applicant |
| US4884123(A) | 1989-11-01 | Morris et al. | Applicant |
| US4897644(A) | 1990-01-01 | Hirano | Applicant |
| US4906828(A) | 1990-03-01 | Halpern | Applicant |
| US4908769(A) | 1990-03-01 | Vaughan et al. | Applicant |
| US4918690(A) | 1990-04-01 | Markkula, Jr. et al. | Applicant |
| US4918995(A) | 1990-04-01 | Pearman et al. | Applicant |
| US4928299(A) | 1990-05-01 | Tansky et al. | Applicant |
| US4939726(A) | 1990-07-01 | Flammer et al. | Applicant |
| US4940976(A) | 1990-07-01 | Gastouniotis et al. | Applicant |
| US4949077(A) | 1990-08-01 | Mbuthia | Applicant |
| US4952928(A) | 1990-08-01 | Carroll et al. | Applicant |
| US4962496(A) | 1990-10-01 | Vercellotti et al. | Applicant |
| US4967366(A) | 1990-10-01 | Kaehler | Applicant |
| US4968970(A) | 1990-11-01 | LaPorte | Applicant |
| US4968978(A) | 1990-11-01 | Stolarczyk | Applicant |
| US4972504(A) | 1990-11-01 | Daniel, Jr. et al. | Applicant |
| US4973957(A) | 1990-11-01 | Shimizu et al. | Applicant |
| US4973970(A) | 1990-11-01 | Reeser | Applicant |
| US4977612(A) | 1990-12-01 | Wilson | Applicant |
| US4980907(A) | 1990-12-01 | Raith et al. | Applicant |
| US4989230(A) | 1991-01-01 | Gillig et al. | Applicant |
| US4991008(A) | 1991-02-01 | Nama | Applicant |
| US4993059(A) | 1991-02-01 | Smith et al. | Applicant |
| US4998095(A) | 1991-03-01 | Shields | Applicant |
| US4999607(A) | 1991-03-01 | Evans | Applicant |
| US5007052(A) | 1991-04-01 | Flammer | Applicant |
| US5032833(A) | 1991-07-01 | Laporte | Applicant |
| US5038372(A) | 1991-08-01 | Elms et al. | Applicant |
| US5055851(A) | 1991-10-01 | Sheffer | Applicant |
| US5057814(A) | 1991-10-01 | Onan et al. | Applicant |
| US5061997(A) | 1991-10-01 | Rea et al. | Applicant |
| US5079768(A) | 1992-01-01 | Flammer | Applicant |
| US5086391(A) | 1992-02-01 | Chambers | Applicant |
| US5091713(A) | 1992-02-01 | Horne et al. | Applicant |
| US5111199(A) | 1992-05-01 | Tomoda et al. | Applicant |
| US5113183(A) | 1992-05-01 | Mizuno et al. | Applicant |
| US5113184(A) | 1992-05-01 | Katayama | Applicant |
| US5115224(A) | 1992-05-01 | Kostusiak et al. | Applicant |
| US5115433(A) | 1992-05-01 | Baran et al. | Applicant |
| US5124624(A) | 1992-06-01 | de Vries et al. | Applicant |
| US5128855(A) | 1992-07-01 | Hilber et al. | Applicant |
| US5130519(A) | 1992-07-01 | Bush et al. | Applicant |
| US5130987(A) | 1992-07-01 | Flammer | Applicant |
| US5131038(A) | 1992-07-01 | Puhl et al. | Applicant |
| US5134650(A) | 1992-07-01 | Blackmon | Applicant |
| US5136285(A) | 1992-08-01 | Okuyama | Applicant |
| US5155481(A) | 1992-10-01 | Brennan, Jr. et al. | Applicant |
| US5159317(A) | 1992-10-01 | Brav | Applicant |
| US5162776(A) | 1992-11-01 | Bushnell et al. | Applicant |
| US5177342(A) | 1993-01-01 | Adams | Applicant |
| US5189287(A) | 1993-02-01 | Parienti | Applicant |
| US5191192(A) | 1993-03-01 | Takahira et al. | Applicant |
| US5191326(A) | 1993-03-01 | Montgomery | Applicant |
| US5193111(A) | 1993-03-01 | Matty et al. | Applicant |
| US5195018(A) | 1993-03-01 | Kwon et al. | Applicant |
| US5197095(A) | 1993-03-01 | Bonnet et al. | Applicant |
| US5200735(A) | 1993-04-01 | Hines | Examiner |
| US5204670(A) | 1993-04-01 | Stinton | Applicant |
| US5212645(A) | 1993-05-01 | Wildes et al. | Applicant |
| US5216502(A) | 1993-06-01 | Katz | Applicant |
| US5221838(A) | 1993-06-01 | Gutman et al. | Applicant |
| US5223844(A) | 1993-06-01 | Mansell et al. | Applicant |
| US5231658(A) | 1993-07-01 | Eftechiou | Applicant |
| US5235630(A) | 1993-08-01 | Moody et al. | Applicant |
| US5239294(A) | 1993-08-01 | Flanders et al. | Applicant |
| US5239575(A) | 1993-08-01 | White et al. | Applicant |
| US5241410(A) | 1993-08-01 | Streck et al. | Applicant |
| US5243338(A) | 1993-09-01 | Brennan, Jr. et al. | Applicant |
| US5245633(A) | 1993-09-01 | Schwartz et al. | Applicant |
| US5251205(A) | 1993-10-01 | Callon et al. | Examiner |
| US5252967(A) | 1993-10-01 | Brennan et al. | Applicant |
| US5253167(A) | 1993-10-01 | Yoshida et al. | Applicant |
| US5265150(A) | 1993-11-01 | Heimkamp et al. | Applicant |
| US5265162(A) | 1993-11-01 | Bush et al. | Applicant |
| US5266782(A) | 1993-11-01 | Alanara et al. | Applicant |
| US5272747(A) | 1993-12-01 | Meads | Applicant |
| US5282204(A) | 1994-01-01 | Shpancer et al. | Applicant |
| US5282250(A) | 1994-01-01 | Dent et al. | Applicant |
| US5289165(A) | 1994-02-01 | Belin | Applicant |
| US5291516(A) | 1994-03-01 | Dixon et al. | Applicant |
| US5295154(A) | 1994-03-01 | Meier et al. | Applicant |
| US5305370(A) | 1994-04-01 | Kearns et al. | Applicant |
| US5309501(A) | 1994-05-01 | Kozik et al. | Applicant |
| US5315645(A) | 1994-05-01 | Matheny | Applicant |
| US5317309(A) | 1994-05-01 | Vercellotti et al. | Applicant |
| US5319364(A) | 1994-06-01 | Waraksa et al. | Applicant |
| US5319698(A) | 1994-06-01 | Glidewell et al. | Examiner |
| US5319711(A) | 1994-06-01 | Servi | Applicant |
| US5323384(A) | 1994-06-01 | Norwood et al. | Applicant |
| US5325429(A) | 1994-06-01 | Kurgan | Applicant |
| US5329394(A) | 1994-07-01 | Calvani et al. | Applicant |
| US5331318(A) | 1994-07-01 | Montgomery | Applicant |
| US5334974(A) | 1994-08-01 | Simms et al. | Applicant |
| US5335265(A) | 1994-08-01 | Cooper et al. | Applicant |
| US5343493(A) | 1994-08-01 | Karimullah | Applicant |
| US5345231(A) | 1994-09-01 | Koo et al. | Applicant |
| US5345595(A) | 1994-09-01 | Johnson et al. | Applicant |
| US5347263(A) | 1994-09-01 | Carroll et al. | Applicant |
| US5354974(A) | 1994-10-01 | Eisenberg | Applicant |
| US5355278(A) | 1994-10-01 | Hosoi et al. | Applicant |
| US5355513(A) | 1994-10-01 | Clarke et al. | Applicant |
| US5365217(A) | 1994-11-01 | Toner | Applicant |
| US5371736(A) | 1994-12-01 | Evan | Applicant |
| US5382778(A) | 1995-01-01 | Takahira et al. | Applicant |
| US5383134(A) | 1995-01-01 | Wrzesinski | Applicant |
| US5390206(A) | 1995-02-01 | Rein | Applicant |
| US5406619(A) | 1995-04-01 | Akhteruzzaman et al. | Applicant |
| US5412192(A) | 1995-05-01 | Hoss | Applicant |
| US5412760(A) | 1995-05-01 | Peitz | Applicant |
| US5416475(A) | 1995-05-01 | Tolbert et al. | Applicant |
| US5416725(A) | 1995-05-01 | Pacheco et al. | Applicant |
| US5418812(A) | 1995-05-01 | Reyes et al. | Applicant |
| US5420910(A) | 1995-05-01 | Rudokas et al. | Applicant |
| US5424708(A) | 1995-06-01 | Ballesty et al. | Applicant |
| US5432507(A) | 1995-07-01 | Mussino et al. | Applicant |
| US5438329(A) | 1995-08-01 | Gastouniotis et al. | Examiner |
| US5439414(A) | 1995-08-01 | Jacob | Applicant |
| US5440545(A) | 1995-08-01 | Buchholz et al. | Applicant |
| US5442553(A) | 1995-08-01 | Parrillo | Applicant |
| US5445287(A) | 1995-08-01 | Center et al. | Applicant |
| US5445347(A) | 1995-08-01 | Ng | Applicant |
| US5451929(A) | 1995-09-01 | Adelman et al. | Applicant |
| US5451938(A) | 1995-09-01 | Brennan, Jr. | Applicant |
| US5452344(A) | 1995-09-01 | Larson | Applicant |
| US5454024(A) | 1995-09-01 | Lebowitz | Applicant |
| US5465401(A) | 1995-11-01 | Thompson | Applicant |
| US5467074(A) | 1995-11-01 | Pedtke | Applicant |
| US5467082(A) | 1995-11-01 | Sanderson | Applicant |
| US5467345(A) | 1995-11-01 | Cutler et al. | Applicant |
| US5468948(A) | 1995-11-01 | Koenck et al. | Applicant |
| US5471201(A) | 1995-11-01 | Cerami et al. | Applicant |
| US5473322(A) | 1995-12-01 | Carney | Applicant |
| US5475689(A) | 1995-12-01 | Kay et al. | Applicant |
| US5481259(A) | 1996-01-01 | Bane | Applicant |
| US5481532(A) | 1996-01-01 | Hassan et al. | Applicant |
| US5484997(A) | 1996-01-01 | Haynes | Applicant |
| US5488608(A) | 1996-01-01 | Flammer, III | Applicant |
| US5493273(A) | 1996-02-01 | Smurlo et al. | Applicant |
| US5493287(A) | 1996-02-01 | Bane | Applicant |
| US5502726(A) | 1996-03-01 | Fischer | Applicant |
| US5506837(A) | 1996-04-01 | Sollner et al. | Applicant |
| US5509073(A) | 1996-04-01 | Monnin | Applicant |
| US5513244(A) | 1996-04-01 | Joao et al. | Applicant |
| US5515419(A) | 1996-05-01 | Sheffer | Applicant |
| US5517188(A) | 1996-05-01 | Carroll et al. | Applicant |
| US5522089(A) | 1996-05-01 | Kikinis et al. | Applicant |
| US5528215(A) | 1996-06-01 | Siu et al. | Applicant |
| US5539825(A) | 1996-07-01 | Akiyama et al. | Applicant |
| US5541938(A) | 1996-07-01 | Di Zenzo et al. | Applicant |
| US5542100(A) | 1996-07-01 | Hatakeyama | Applicant |
| US5544036(A) | 1996-08-01 | Brown, Jr. et al. | Applicant |
| US5544784(A) | 1996-08-01 | Malaspina | Applicant |
| US5548632(A) | 1996-08-01 | Walsh et al. | Applicant |
| US5550358(A) | 1996-08-01 | Tait et al. | Applicant |
| US5550359(A) | 1996-08-01 | Bennett | Applicant |
| US5550535(A) | 1996-08-01 | Park | Applicant |
| US5553094(A) | 1996-09-01 | Johnson et al. | Applicant |
| US5555258(A) | 1996-09-01 | Snelling et al. | Applicant |
| US5555286(A) | 1996-09-01 | Tendler | Applicant |
| US5562537(A) | 1996-10-01 | Zver et al. | Applicant |
| US5565857(A) | 1996-10-01 | Lee | Applicant |
| US5568535(A) | 1996-10-01 | Sheffer et al. | Applicant |
| US5570084(A) | 1996-10-01 | Ritter et al. | Applicant |
| US5572438(A) | 1996-11-01 | Ehlers et al. | Applicant |
| US5573181(A) | 1996-11-01 | Ahmed | Applicant |
| US5574111(A) | 1996-11-01 | Brichta et al. | Applicant |
| US5583850(A) | 1996-12-01 | Snodgrass et al. | Applicant |
| US5587705(A) | 1996-12-01 | Morris | Applicant |
| US5589878(A) | 1996-12-01 | Cortjens et al. | Applicant |
| US5590038(A) | 1996-12-01 | Pitroda | Applicant |
| US5590179(A) | 1996-12-01 | Shincovich et al. | Applicant |
| US5592491(A) | 1997-01-01 | Dinks | Applicant |
| US5594431(A) | 1997-01-01 | Sheppard et al. | Applicant |
| US5596719(A) | 1997-01-01 | Ramakrishnan et al. | Applicant |
| US5602843(A) | 1997-02-01 | Gray | Applicant |
| US5604414(A) | 1997-02-01 | Milligan et al. | Applicant |
| US5604869(A) | 1997-02-01 | Mincher et al. | Applicant |
| US5606361(A) | 1997-02-01 | Davidsohn et al. | Applicant |
| US5608786(A) | 1997-03-01 | Gordon | Applicant |
| US5613620(A) | 1997-03-01 | Center et al. | Applicant |
| US5615277(A) | 1997-03-01 | Hoffman | Applicant |
| US5619192(A) | 1997-04-01 | Ayala | Applicant |
| US5625410(A) | 1997-04-01 | Washino et al. | Examiner |
| US5628050(A) | 1997-05-01 | McGraw et al. | Applicant |
| US5629687(A) | 1997-05-01 | Sutton et al. | Applicant |
| US5629875(A) | 1997-05-01 | Adair, Jr. | Applicant |
| US5630209(A) | 1997-05-01 | Wizgall et al. | Applicant |
| US5631554(A) | 1997-05-01 | Briese et al. | Applicant |
| US5636216(A) | 1997-06-01 | Fox et al. | Applicant |
| US5640002(A) | 1997-06-01 | Ruppert et al. | Applicant |
| US5644294(A) | 1997-07-01 | Ness | Applicant |
| US5655219(A) | 1997-08-01 | Jusa et al. | Applicant |
| US5657389(A) | 1997-08-01 | Houvener | Applicant |
| US5659300(A) | 1997-08-01 | Dresselhuys et al. | Applicant |
| US5659303(A) | 1997-08-01 | Adair, Jr. | Applicant |
| US5668876(A) | 1997-09-01 | Falk et al. | Applicant |
| US5673252(A) | 1997-09-01 | Johnson et al. | Examiner |
| US5673304(A) | 1997-09-01 | Connor et al. | Applicant |
| US5673305(A) | 1997-09-01 | Ross | Applicant |
| US5682139(A) | 1997-10-01 | Pradeep et al. | Applicant |
| US5682476(A) | 1997-10-01 | Tapperson et al. | Examiner |
| US5689229(A) | 1997-11-01 | Chaco et al. | Applicant |
| US5699328(A) | 1997-12-01 | Ishizaki et al. | Applicant |
| US5701002(A) | 1997-12-01 | Oishi et al. | Applicant |
| US5702059(A) | 1997-12-01 | Chu et al. | Applicant |
| US5704046(A) | 1997-12-01 | Hogan | Applicant |
| US5704517(A) | 1998-01-01 | Lancaster, Jr. | Applicant |
| US5706191(A) | 1998-01-01 | Bassett et al. | Applicant |
| US5706976(A) | 1998-01-01 | Purkey | Applicant |
| US5708223(A) | 1998-01-01 | Wyss | Applicant |
| US5708655(A) | 1998-01-01 | Toth | Applicant |
| US5712619(A) | 1998-01-01 | Simkin | Applicant |
| US5712980(A) | 1998-01-01 | Beeler et al. | Applicant |
| US5714931(A) | 1998-02-01 | Petite et al. | Applicant |
| US5717718(A) | 1998-02-01 | Rowsell et al. | Applicant |
| US5726634(A) | 1998-03-01 | Hess et al. | Applicant |
| US5726984(A) | 1998-03-01 | Kubler et al. | Applicant |
| US5732074(A) | 1998-03-01 | Spaur et al. | Examiner |
| US5732078(A) | 1998-03-01 | Arango | Applicant |
| US5736965(A) | 1998-04-01 | Mosebrook et al. | Applicant |
| US5740232(A) | 1998-04-01 | Pailles et al. | Applicant |
| US5742509(A) | 1998-04-01 | Goldberg et al. | Applicant |
| US5745849(A) | 1998-04-01 | Britton | Applicant |
| US5748104(A) | 1998-05-01 | Argyroudis et al. | Applicant |
| US5748619(A) | 1998-05-01 | Meier | Applicant |
| US5754111(A) | 1998-05-01 | Garcia | Applicant |
| US5754227(A) | 1998-05-01 | Fukuoka | Applicant |
| US5757783(A) | 1998-05-01 | Eng et al. | Applicant |
| US5757788(A) | 1998-05-01 | Tatsumi et al. | Applicant |
| US5761083(A) | 1998-06-01 | Brown, Jr. et al. | Applicant |
| US5764742(A) | 1998-06-01 | Howard et al. | Applicant |
| US5767791(A) | 1998-06-01 | Stoop et al. | Applicant |
| US5771274(A) | 1998-06-01 | Harris | Applicant |
| US5774052(A) | 1998-06-01 | Hamm et al. | Applicant |
| US5781143(A) | 1998-07-01 | Rossin | Applicant |
| US5790644(A) | 1998-08-01 | Kikinis | Applicant |
| US5790662(A) | 1998-08-01 | Valerij et al. | Applicant |
| US5790938(A) | 1998-08-01 | Talarmo | Applicant |
| US5796727(A) | 1998-08-01 | Harrison et al. | Applicant |
| US5798964(A) | 1998-08-01 | Shimizu et al. | Applicant |
| US5801643(A) | 1998-09-01 | Williams et al. | Applicant |
| US5815505(A) | 1998-09-01 | Mills | Applicant |
| US5818822(A) | 1998-10-01 | Thomas et al. | Applicant |
| US5822273(A) | 1998-10-01 | Bary et al. | Applicant |
| US5822544(A) | 1998-10-01 | Chaco et al. | Applicant |
| US5825772(A) | 1998-10-01 | Dobbins et al. | Applicant |
| US5826195(A) | 1998-10-01 | Westerlage et al. | Applicant |
| US5828044(A) | 1998-10-01 | Jun et al. | Applicant |
| US5832057(A) | 1998-11-01 | Furman | Applicant |
| US5838223(A) | 1998-11-01 | Gallant et al. | Applicant |
| US5838237(A) | 1998-11-01 | Revell et al. | Applicant |
| US5838812(A) | 1998-11-01 | Pare, Jr. et al. | Applicant |
| US5841118(A) | 1998-11-01 | East et al. | Applicant |
| US5841764(A) | 1998-11-01 | Roderique et al. | Applicant |
| US5842976(A) | 1998-12-01 | Williamson | Applicant |
| US5844808(A) | 1998-12-01 | Konsmo et al. | Applicant |
| US5845230(A) | 1998-12-01 | Lamberson | Applicant |
| US5852658(A) | 1998-12-01 | Knight et al. | Applicant |
| US5854994(A) | 1998-12-01 | Canada et al. | Applicant |
| US5862201(A) | 1999-01-01 | Sands | Applicant |
| US5864772(A) | 1999-01-01 | Alvarado et al. | Applicant |
| US5873043(A) | 1999-02-01 | Comer | Applicant |
| US5874903(A) | 1999-02-01 | Shuey et al. | Applicant |
| US5880677(A) | 1999-03-01 | Lestician | Applicant |
| US5884184(A) | 1999-03-01 | Sheffer | Applicant |
| US5884271(A) | 1999-03-01 | Pitroda | Applicant |
| US5886333(A) | 1999-03-01 | Miyake | Applicant |
| US5889468(A) | 1999-03-01 | Banga | Applicant |
| US5892690(A) | 1999-04-01 | Boatman et al. | Applicant |
| US5892758(A) | 1999-04-01 | Argyroudis | Applicant |
| US5892924(A) | 1999-04-01 | Lyon et al. | Examiner |
| US5896097(A) | 1999-04-01 | Cardozo | Applicant |
| US5897607(A) | 1999-04-01 | Jenney et al. | Applicant |
| US5898369(A) | 1999-04-01 | Godwin | Applicant |
| US5905438(A) | 1999-05-01 | Weiss et al. | Applicant |
| US5907291(A) | 1999-05-01 | Chen et al. | Applicant |
| US5907491(A) | 1999-05-01 | Canada et al. | Examiner |
| US5907540(A) | 1999-05-01 | Hayashi | Applicant |
| US5907807(A) | 1999-05-01 | Chavez et al. | Examiner |
| US5914672(A) | 1999-06-01 | Glorioso et al. | Applicant |
| US5914673(A) | 1999-06-01 | Jennings et al. | Applicant |
| US5917405(A) | 1999-06-01 | Joao | Applicant |
| US5917629(A) | 1999-06-01 | Hortensius et al. | Applicant |
| US5923269(A) | 1999-07-01 | Shuey et al. | Applicant |
| US5926103(A) | 1999-07-01 | Petite | Applicant |
| US5926529(A) | 1999-07-01 | Hache et al. | Applicant |
| US5926531(A) | 1999-07-01 | Petite | Applicant |
| US5933073(A) | 1999-08-01 | Shuey | Applicant |
| US5941363(A) | 1999-08-01 | Partyka et al. | Applicant |
| US5941955(A) | 1999-08-01 | Wilby et al. | Applicant |
| US5948040(A) | 1999-09-01 | DeLorme et al. | Applicant |
| US5949779(A) | 1999-09-01 | Mostafa et al. | Applicant |
| US5949799(A) | 1999-09-01 | Grivna et al. | Applicant |
| US5953319(A) | 1999-09-01 | Dutta et al. | Applicant |
| US5953371(A) | 1999-09-01 | Rowsell et al. | Applicant |
| US5955718(A) | 1999-09-01 | Levasseur et al. | Applicant |
| US5960074(A) | 1999-09-01 | Clark | Applicant |
| US5963146(A) | 1999-10-01 | Johnson et al. | Applicant |
| US5963452(A) | 1999-10-01 | Etoh et al. | Applicant |
| US5963650(A) | 1999-10-01 | Simionescu et al. | Applicant |
| US5966658(A) | 1999-10-01 | Kennedy, III et al. | Applicant |
| US5969608(A) | 1999-10-01 | Sojdehei et al. | Applicant |
| US5973756(A) | 1999-10-01 | Erlin | Applicant |
| US5974236(A) | 1999-10-01 | Sherman | Applicant |
| US5978364(A) | 1999-11-01 | Melnik | Applicant |
| US5978371(A) | 1999-11-01 | Mason, Jr. et al. | Applicant |
| US5986574(A) | 1999-11-01 | Colton | Applicant |
| US5987421(A) | 1999-11-01 | Chuang | Applicant |
| US5991625(A) | 1999-11-01 | Vanderpool | Applicant |
| US5991639(A) | 1999-11-01 | Rautiola et al. | Applicant |
| US5994892(A) | 1999-11-01 | Turino et al. | Applicant |
| US5995592(A) | 1999-11-01 | Shirai et al. | Applicant |
| US5995593(A) | 1999-11-01 | Cho | Applicant |
| US5997170(A) | 1999-12-01 | Brodbeck | Applicant |
| US5999094(A) | 1999-12-01 | Nilssen | Applicant |
| US6005759(A) | 1999-12-01 | Hart et al. | Applicant |
| US6005963(A) | 1999-12-01 | Bolle et al. | Applicant |
| US6021664(A) | 2000-02-01 | Granato et al. | Examiner |
| US6023223(A) | 2000-02-01 | Baxter, Jr. | Applicant |
| US6026095(A) | 2000-02-01 | Sherer et al. | Applicant |
| US6028522(A) | 2000-02-01 | Petite | Applicant |
| US6028857(A) | 2000-02-01 | Poor | Applicant |
| US6031455(A) | 2000-02-01 | Grube et al. | Applicant |
| US6032197(A) | 2000-02-01 | Birdwell et al. | Applicant |
| US6035213(A) | 2000-03-01 | Tokuda et al. | Applicant |
| US6035266(A) | 2000-03-01 | Williams et al. | Applicant |
| US6036086(A) | 2000-03-01 | Sizer, II et al. | Applicant |
| US6038491(A) | 2000-03-01 | McGarry et al. | Applicant |
| US6044062(A) | 2000-03-01 | Brownrigg et al. | Applicant |
| US6054920(A) | 2000-04-01 | Smith et al. | Examiner |
| US6060994(A) | 2000-05-01 | Chen | Examiner |
| US6061604(A) | 2000-05-01 | Russ et al. | Applicant |
| US6064318(A) | 2000-05-01 | Kirchner et al. | Examiner |
| US6067017(A) | 2000-05-01 | Stewart et al. | Applicant |
| US6067030(A) | 2000-05-01 | Burnett et al. | Applicant |
| US6069886(A) | 2000-05-01 | Ayerst et al. | Applicant |
| US6073169(A) | 2000-06-01 | Shuey et al. | Applicant |
| US6073266(A) | 2000-06-01 | Ahmed et al. | Applicant |
| US6073840(A) | 2000-06-01 | Marion | Applicant |
| US6075451(A) | 2000-06-01 | Lebowitz et al. | Applicant |
| US6078251(A) | 2000-06-01 | Landt et al. | Applicant |
| US6087957(A) | 2000-07-01 | Gray | Applicant |
| US6088659(A) | 2000-07-01 | Kelley et al. | Applicant |
| US6094622(A) | 2000-07-01 | Hubbard et al. | Applicant |
| US6100817(A) | 2000-08-01 | Mason, Jr. et al. | Applicant |
| US6101427(A) | 2000-08-01 | Yang | Applicant |
| US6101445(A) | 2000-08-01 | Alvarado et al. | Applicant |
| US6112983(A) | 2000-09-01 | D'Anniballe et al. | Applicant |
| US6115580(A) | 2000-09-01 | Chuprun et al. | Applicant |
| US6119076(A) | 2000-09-01 | Williams et al. | Applicant |
| US6121593(A) | 2000-09-01 | Mansbery et al. | Applicant |
| US6121885(A) | 2000-09-01 | Masone et al. | Applicant |
| US6124806(A) | 2000-09-01 | Cunningham et al. | Examiner |
| US6127917(A) | 2000-10-01 | Tuttle | Applicant |
| US6128551(A) | 2000-10-01 | Davis et al. | Examiner |
| US6130622(A) | 2000-10-01 | Hussey et al. | Applicant |
| US6133850(A) | 2000-10-01 | Moore | Applicant |
| US6137423(A) | 2000-10-01 | Glorioso et al. | Applicant |
| US6140975(A) | 2000-10-01 | Cohen | Applicant |
| US6141347(A) | 2000-10-01 | Shaughnessy et al. | Examiner |
| US6150936(A) | 2000-11-01 | Addy | Applicant |
| US6150955(A) | 2000-11-01 | Tracy et al. | Applicant |
| US6157464(A) | 2000-12-01 | Bloomfield et al. | Applicant |
| US6157824(A) | 2000-12-01 | Bailey | Applicant |
| US6163276(A) | 2000-12-01 | Irving et al. | Applicant |
| US6172616(B1) | 2001-01-01 | Johnson et al. | Applicant |
| US6174205(B1) | 2001-01-01 | Madsen et al. | Applicant |
| US6175922(B1) | 2001-01-01 | Wang | Applicant |
| US6177883(B1) | 2001-01-01 | Jennetti et al. | Applicant |
| US6181255(B1) | 2001-01-01 | Crimmins et al. | Applicant |
| US6181284(B1) | 2001-01-01 | Madsen et al. | Applicant |
| US6181981(B1) | 2001-01-01 | Varga et al. | Applicant |
| US6188354(B1) | 2001-02-01 | Soliman et al. | Applicant |
| US6192390(B1) | 2001-02-01 | Berger et al. | Applicant |
| US6198390(B1) | 2001-03-01 | Schlager et al. | Applicant |
| US6199068(B1) | 2001-03-01 | Carpenter | Applicant |
| US6208266(B1) | 2001-03-01 | Lyons et al. | Examiner |
| US6215440(B1) | 2001-04-01 | Morales | Applicant |
| US6218953(B1) | 2001-04-01 | Petite | Applicant |
| US6218958(B1) | 2001-04-01 | Eichstaedt | Applicant |
| US6218983(B1) | 2001-04-01 | Kerry et al. | Applicant |
| US6219409(B1) | 2001-04-01 | Smith et al. | Applicant |
| US6229439(B1) | 2001-05-01 | Tice | Applicant |
| US6233327(B1) | 2001-05-01 | Petite | Applicant |
| US6234111(B1) | 2001-05-01 | Ulman et al. | Examiner |
| US6236332(B1) | 2001-05-01 | Conkright et al. | Applicant |
| US6243010(B1) | 2001-06-01 | Addy et al. | Applicant |
| US6246677(B1) | 2001-06-01 | Nap et al. | Applicant |
| US6246886(B1) | 2001-06-01 | Oliva | Applicant |
| US6249516(B1) | 2001-06-01 | Brownrigg et al. | Applicant |
| US6259369(B1) | 2001-07-01 | Monico | Applicant |
| US6275707(B1) | 2001-08-01 | Reed et al. | Applicant |
| US6286756(B1) | 2001-09-01 | Stinson et al. | Applicant |
| US6288634(B1) | 2001-09-01 | Weiss et al. | Applicant |
| US6288641(B1) | 2001-09-01 | Casais | Examiner |
| US6295291(B1) | 2001-09-01 | Larkins | Applicant |
| US6301514(B1) | 2001-10-01 | Canada et al. | Examiner |
| US6304556(B1) | 2001-10-01 | Haas | Applicant |
| US6305602(B1) | 2001-10-01 | Grabowski et al. | Applicant |
| US6308111(B1) | 2001-10-01 | Koga | Applicant |
| US6311167(B1) | 2001-10-01 | Davis et al. | Applicant |
| US6314169(B1) | 2001-11-01 | Schelberg, Jr. et al. | Applicant |
| US6317029(B1) | 2001-11-01 | Fleeter | Applicant |
| US6334117(B1) | 2001-12-01 | Covert et al. | Applicant |
| US6351223(B1) | 2002-02-01 | DeWeerd et al. | Applicant |
| US6356205(B1) | 2002-03-01 | Salvo et al. | Applicant |
| US6357034(B1) | 2002-03-01 | Muller et al. | Applicant |
| US6362745(B1) | 2002-03-01 | Davis | Applicant |
| US6363057(B1) | 2002-03-01 | Ardalan et al. | Applicant |
| US6366217(B1) | 2002-04-01 | Cunningham et al. | Applicant |
| US6366622(B1) | 2002-04-01 | Brown et al. | Applicant |
| US6369769(B1) | 2002-04-01 | Nap et al. | Applicant |
| US6370489(B1) | 2002-04-01 | Williams et al. | Applicant |
| US6373399(B1) | 2002-04-01 | Johnson et al. | Applicant |
| US6380851(B1) | 2002-04-01 | Gilbert et al. | Applicant |
| US6384722(B1) | 2002-05-01 | Williams | Applicant |
| US6393341(B1) | 2002-05-01 | Lawrence et al. | Applicant |
| US6393381(B1) | 2002-05-01 | Williams et al. | Applicant |
| US6393382(B1) | 2002-05-01 | Williams et al. | Applicant |
| US6396839(B1) | 2002-05-01 | Ardalan et al. | Applicant |
| US6400819(B1) | 2002-06-01 | Nakano et al. | Applicant |
| US6401081(B1) | 2002-06-01 | Montgomery et al. | Applicant |
| US6405018(B1) | 2002-06-01 | Reudink et al. | Applicant |
| US6411889(B1) | 2002-06-01 | Mizunuma et al. | Applicant |
| US6415245(B2) | 2002-07-01 | Williams et al. | Applicant |
| US6421354(B1) | 2002-07-01 | Godlewski | Applicant |
| US6421731(B1) | 2002-07-01 | Ciotti, Jr. et al. | Applicant |
| US6422464(B1) | 2002-07-01 | Terranova | Applicant |
| US6424270(B1) | 2002-07-01 | Ali | Applicant |
| US6424931(B1) | 2002-07-01 | Sigmar et al. | Applicant |
| US6430268(B1) | 2002-08-01 | Petite | Applicant |
| US6431439(B1) | 2002-08-01 | Suer et al. | Applicant |
| US6437692(B1) | 2002-08-01 | Petite et al. | Applicant |
| US6438575(B1) | 2002-08-01 | Khan et al. | Applicant |
| US6445291(B2) | 2002-09-01 | Addy et al. | Applicant |
| US6456960(B1) | 2002-09-01 | Williams et al. | Applicant |
| US6457038(B1) | 2002-09-01 | Defosse | Examiner |
| US6462644(B1) | 2002-10-01 | Howell et al. | Applicant |
| US6462672(B1) | 2002-10-01 | Besson | Applicant |
| US6477558(B1) | 2002-11-01 | Irving et al. | Applicant |
| US6483290(B1) | 2002-11-01 | Hemminger et al. | Applicant |
| US6484939(B1) | 2002-11-01 | Blaeuer | Applicant |
| US6489884(B1) | 2002-12-01 | Lamberson et al. | Applicant |
| US6491828(B1) | 2002-12-01 | Sivavec et al. | Applicant |
| US6492910(B1) | 2002-12-01 | Ragle et al. | Applicant |
| US6504357(B1) | 2003-01-01 | Hemminger et al. | Applicant |
| US6507794(B1) | 2003-01-01 | Hubbard et al. | Applicant |
| US6509722(B2) | 2003-01-01 | Lopata | Applicant |
| US6519568(B1) | 2003-02-01 | Harvey et al. | Applicant |
| US6538577(B1) | 2003-03-01 | Ehrke et al. | Applicant |
| US6542076(B1) | 2003-04-01 | Joao | Applicant |
| US6542077(B2) | 2003-04-01 | Joao | Applicant |
| US6543690(B2) | 2003-04-01 | Leydier et al. | Applicant |
| US6560223(B1) | 2003-05-01 | Egan et al. | Applicant |
| US6574603(B1) | 2003-06-01 | Dickson et al. | Applicant |
| US6584080(B1) | 2003-06-01 | Ganz et al. | Applicant |
| US6600726(B1) | 2003-07-01 | Nevo et al. | Applicant |
| US6608551(B1) | 2003-08-01 | Anderson et al. | Applicant |
| US6618578(B1) | 2003-09-01 | Petite | Applicant |
| US6618709(B1) | 2003-09-01 | Sneeringer | Applicant |
| US6628764(B1) | 2003-09-01 | Petite | Applicant |
| US6628965(B1) | 2003-09-01 | LaRosa et al. | Applicant |
| US6653945(B2) | 2003-11-01 | Johnson et al. | Applicant |
| US6654357(B1) | 2003-11-01 | Wiedeman | Applicant |
| US6671586(B2) | 2003-12-01 | Davis et al. | Applicant |
| US6674403(B2) | 2004-01-01 | Gray et al. | Applicant |
| US6678255(B1) | 2004-01-01 | Kuriyan | Applicant |
| US6678285(B1) | 2004-01-01 | Garg | Applicant |
| US6731201(B1) | 2004-05-01 | Bailey et al. | Applicant |
| US6735630(B1) | 2004-05-01 | Gelvin et al. | Applicant |
| US6747557(B1) | 2004-06-01 | Petite et al. | Applicant |
| US6771981(B1) | 2004-08-01 | Zalewski et al. | Applicant |
| US6804532(B1) | 2004-10-01 | Moon et al. | Applicant |
| US6816088(B1) | 2004-11-01 | Knoska et al. | Applicant |
| US6888876(B1) | 2005-05-01 | Mason, Jr. et al. | Applicant |
| US6891838(B1) | 2005-05-01 | Petite | Applicant |
| US6914533(B2) | 2005-07-01 | Petite | Applicant |
| US6914893(B2) | 2005-07-01 | Petite | Applicant |
| US6959550(B2) | 2005-11-01 | Freeman et al. | Applicant |
| US7027416(B1) | 2006-04-01 | Kriz | Applicant |
| US7054271(B2) | 2006-05-01 | Brownrigg et al. | Applicant |
| US2001/0002210(A1) | 2001-05-01 | Petite | Applicant |
| US2001/0003479(A1) | 2001-06-01 | Fujiwara | Applicant |
| US2001/0021646(A1) | 2001-09-01 | Antonucci et al. | Applicant |
| US2001/0024163(A1) | 2001-09-01 | Petite | Applicant |
| US2001/0034223(A1) | 2001-10-01 | Rieser et al. | Applicant |
| US2001/0038343(A1) | 2001-11-01 | Meyer et al. | Applicant |
| US2002/0002444(A1) | 2002-01-01 | Williams et al. | Applicant |
| US2002/0013679(A1) | 2002-01-01 | Petite | Applicant |
| US2002/1112323 | 2002-01-01 | Petite | Applicant |
| US2002/0019725(A1) | 2002-02-01 | Petite | Applicant |
| US2002/0027504(A1) | 2002-03-01 | Petite | Applicant |
| US2002/0031101(A1) | 2002-03-01 | Petite | Applicant |
| US2002/0032746(A1) | 2002-03-01 | Lazaridis | Applicant |
| US2002/0061031(A1) | 2002-05-01 | Sugar et al. | Applicant |
| US2002/0072348(A1) | 2002-06-01 | Wheeler et al. | Applicant |
| US2002/0089428(A1) | 2002-07-01 | Walden et al. | Applicant |
| US2002/0095399(A1) | 2002-07-01 | Devine et al. | Applicant |
| US2002/0098858(A1) | 2002-07-01 | Struhsaker | Applicant |
| US2002/0109607(A1) | 2002-08-01 | Cumeralto et al. | Applicant |
| US2002/0136233(A1) | 2002-09-01 | Chen et al. | Applicant |
| US2002/0158774(A1) | 2002-10-01 | Johnson et al. | Applicant |
| US2002/0163442(A1) | 2002-11-01 | Fischer | Applicant |
| US2002/0169643(A1) | 2002-11-01 | Petite | Applicant |
| US2002/0193144(A1) | 2002-12-01 | Belski et al. | Applicant |
| US2003/0001754(A1) | 2003-01-01 | Johnson et al. | Applicant |
| US2003/0023146(A1) | 2003-01-01 | Shusterman | Applicant |
| US2003/0028632(A1) | 2003-02-01 | Davis | Applicant |
| US2003/0030926(A1) | 2003-02-01 | Aguren et al. | Applicant |
| US2003/0034900(A1) | 2003-02-01 | Han | Applicant |
| US2003/0035438(A1) | 2003-02-01 | Larsson | Applicant |
| US2003/0036822(A1) | 2003-02-01 | Davis et al. | Applicant |
| US2003/0046377(A1) | 2003-03-01 | Daum et al. | Applicant |
| US2003/0058818(A1) | 2003-03-01 | Wilkes et al. | Applicant |
| US2003/0069002(A1) | 2003-04-01 | Hunter et al. | Applicant |
| US2003/0073406(A1) | 2003-04-01 | Benjamin et al. | Applicant |
| US2003/0078029(A1) | 2003-04-01 | Petite | Applicant |
| US2003/0093484(A1) | 2003-05-01 | Petite | Applicant |
| US2003/0133473(A1) | 2003-07-01 | Manis et al. | Applicant |
| US2003/0169710(A1) | 2003-09-01 | Fan et al. | Applicant |
| US2003/0185204(A1) | 2003-10-01 | Murdock | Applicant |
| US2003/0210638(A1) | 2003-11-01 | Yoo et al. | Applicant |
| US2004/0047324(A1) | 2004-03-01 | Diener | Applicant |
| US2004/0053639(A1) | 2004-03-01 | Petite | Applicant |
| US2004/0131125(A1) | 2004-07-01 | Sanderford, Jr. et al. | Applicant |
| US2004/0133917(A1) | 2004-07-01 | Schilling | Applicant |
| US2004/0183687(A1) | 2004-09-01 | Petite | Applicant |
| US2004/0228330(A1) | 2004-11-01 | Kubler et al. | Applicant |
| US2005/0190055(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0195768(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0195775(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0201397(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0243867(A1) | 2005-11-01 | Petite | Applicant |
| US2006/0095876(A1) | 2006-05-01 | Brownrigg et al. | Applicant |
| US2008/0186898(A1) | 2008-08-01 | Petite | Applicant |
| US2009/0006617(A1) | 2009-01-01 | Petite | Applicant |
| US2009/0068947(A1) | 2009-03-01 | Petite | Applicant |
| EP718954 | 1996-06-01 | Applicant | |
| EP7144 | 1998-02-01 | Applicant | |
| EP1096454 | 2001-05-01 | Applicant | |
| FR2817110 | 2002-05-01 | Applicant | |
| GB2229302 | 1990-09-01 | Applicant | |
| GB2247761 | 1992-03-01 | Applicant | |
| GB2262683 | 1993-06-01 | Applicant | |
| GB2297663 | 1996-08-01 | Applicant | |
| GB2310779 | 1997-09-01 | Applicant | |
| GB2326002 | 1998-12-01 | Applicant | |
| GB2336272 | 1999-10-01 | Applicant | |
| GB2352004 | 2001-01-01 | Applicant | |
| GB2352590 | 2001-01-01 | Applicant | |
| JP60261288 | 1985-12-01 | Applicant | |
| JP1255100 | 1989-10-01 | Applicant | |
| JP11353573 | 1999-12-01 | Applicant | |
| JP200113590 | 2000-04-01 | Applicant | |
| JP2001063425 | 2001-03-01 | Applicant | |
| JP2001088401 | 2001-04-01 | Applicant | |
| JP2001309069 | 2001-11-01 | Applicant | |
| JP2001319284 | 2001-11-01 | Applicant | |
| JP2001357483 | 2001-12-01 | Applicant | |
| JP2002007672 | 2002-01-01 | Applicant | |
| JP2002007826 | 2002-01-01 | Applicant | |
| JP2002085354 | 2002-03-01 | Applicant | |
| JP2002171354 | 2002-06-01 | Applicant | |
| KR2001025431 | 2001-04-01 | Applicant | |
| NO3/021877 | 2003-03-01 | Applicant | |
| WO90/13197 | 1990-11-01 | Applicant | |
| WO98/00056 | 1998-01-01 | Applicant | |
| WO98/10393(A1) | 1998-03-01 | Applicant | |
| WO98/37528 | 1998-08-01 | Applicant | |
| WO99/13426 | 1999-03-01 | Applicant | |
| WO/36812(A1) | 2000-06-01 | Applicant | |
| WO1/15114 | 2000-08-01 | Applicant | |
| WO1/24109 | 2001-04-01 | Applicant | |
| WO2/08725 | 2002-01-01 | Applicant | |
| WO2/08866 | 2002-01-01 | Applicant | |
| WO2/052521 | 2002-07-01 | Applicant | |
| WO2/052521 | 2002-07-01 | Applicant | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/021877 | 2003-03-01 | Applicant |
Non-Patent Literature (48)
- Royer, et al “A Review of Current Routing Protocols for Ad Hoc Mobile Wireless Networks”, Apr. 1999, IEEE Personal Communications, vol. 6, Issue 2, pp. 46-55.Examiner
- Westcott, Jil et al., “A Distributed Routing Design For A Broadcoast Environment”, IEEE 1982, pp. 10.4.0-10.4.5.Applicant
- Khan, Robert E. et al., “Advances in Packet Radio Technology”, IEEE Nov. 1978, vol. 66, No. 11, pp. 1468-1496.Applicant
- Frankel, Michael S., “Packet Radios Provide Link for Distributed, Survivable C3 in Post-Attack Scenarios”, MSN Jun. 1983.Applicant
- Lauer, Greg et al., “Survivable Protocols for Large Scale Packet Radio Networks”, IEEE 1984, pp. 15.1-1 to 15.1-4.Applicant
- Gower, Neil et al., “Congestion Control Using Pacing in a Packet Radio Network”, IEEE 1982, pp. 23.1-1 to 23.1-6.Applicant
- MacGregor, William et al., “Multiple Control Stations in Packet Radio Networks”, IEEE 1982, pp. 10.3-1 to 10.3-5 1.Applicant
- Shacham, Nachum et al., “Future Directions in Packet Radio Technology”, IEEE 1985, pp. 93-98.Applicant
- Jubin, John, “Current Packet Radio Network Protocols”, IEEE 1985, pp. 86-92.Applicant
- Westcott, Jill A., Issues in Distributed Routing for Mobile Packet Radio Network, IEEE 1982, pp. 233-238.Applicant
- Lynch, Clifford A. et al., Packet Radio Networks, “Architectures, Protocols, Technologies and Applications,”.Applicant
- Brownrigg, Edwin, “User Provided Access to the Internet”, Open Access Solutions, http://web.simmons.edu/chen/nit/NIT'92/033-bro.htm, Jun. 8, 2005 - Jun. 9, 2005.Applicant
- Khan, Robert E., “The Organization of Computer Resources into a Packet Radio Network,” IEEE, Jan. 1977, vol. Com-25 No. 1, pp. 169-178.Applicant
- Westcott, Jill A., “Issues in Distributed Routing for Mobile Packet Radio Network,” IEEE 1982, pp. 233-238.Applicant
- Khan, Robert E., “The Organization of Computer Resources into a Packet Radio Network,” IEEE Transactions on Communications, Jan. 1977, vol. Com-25 No. 1, pp. 169-178.Applicant
- Westcott, Jill A., “Issues in Distributed Routing for Mobile Packet Radio Network,” IEEE 1982, pp. 233-238.Applicant
- Brownrigg, E.B. et al.; A Packet Radio Network for Library Automation; IEEE (1987); pp. 456-462.Applicant
- Brownrigg, E.B., et al.; A Packet Radio Networks; Architectures, Protocols, Technologies and Applications (1987), (introduction pp. ix-xviii); pp. 3-274.Applicant
- Brownrigg, E.B., et al.; Distributions, Networks, and Networking: Options for Dissemination; Workshop on Electronic Texts Session III (http://palimpsest.standford.edu/byorg/lc/etextw/sess3.html 1992): pp. 1-10.Applicant
- Brownrigg, E.B. et al.; User Provided Access to the Internet; (http://web.simmons.edu/˜chen/nit/NIT'92/033-bro.htm 2005) pp. 1-6.Applicant
- Wey, Jyhi-Kong et al.; Clone Terminator: An Authentication Service for Advanced Mobile Phone System; IEEE (1995); pp. 175-179.Applicant
- Davis, A.B. et al.; Knowledge-Based Management of Cellular Clone Fraud; IEEE (1992); pp. 230-234.Applicant
- Johnson, David B.; Routing in Ad Hoc Networks of Mobile Hosts; IEEE (1995); pp. 158-163.Applicant
- Jubin, John and Tornow, Janet D., “The Darpa Packet Radio Network Protocols,” Proceedings of the IEEE, vol. 75, No. 1, Jan. 1987, pp. 21-32.Applicant
- Kleinrock, Leonard and Kamoun, Farouk, “Hierarchical Routing for Large Networks,” North-Holland Publishing Company, Computer Networks 1, 1997, pp. 155-174.Applicant
- Perkins, C.E. et al.; Highly Dynamic Destination-Sequenced Distance-Vector Routing (DSDV) for Mobile Computers; SIGCOMM 94-9/94 London England UK (1994); pp. 234-244.Applicant
- Wu, J.; Distributed System Design; CRC Press (1999); pp. 177-180 and 204.Applicant
- Khan, Robert E., Gronemeyer, Steven A. Burchfiel, Jerry, and Kunzelman, Ronald C., “Advances in Packet Radio Technology” IEEE Nov. 1978, vol. 66, No. 11, pp. 1468-149.Applicant
- Babak Daneshrad, et al.; 1997 Project Summary “Mobile Versatile Radios (MoVeR);” University of California, Los Angeles; pp. 1-4.Applicant
- Rajeev Jain, et al.; 1997 Project Summary “Held Untethered Nodes;” University of California, Los Angeles; pp. 1-5.Applicant
- Randy H. Katz and Eric A. Brewer; 1997 Project Summary “Towards a Wireless Overlay Internetworking Architecture;” University of California, Berkeley; pp. 1-8, including slide show presentation at http://daedalus.cs.berkeley,edu/talks/retreat.6.96/Overview.pdf.Applicant
- J.J. Garcia-Luna-Aceves, et al.; “Wireless Internet Gateways (Wings),” IEEE, 1997; pp. 1271-1276.Applicant
- Randy H. Katz, et al.; “The Bay Area Research Wireless Access Network (BARWAN);” Electrical Engeneering and Computer Science Department, University of California, Berkeley, CA; IEEE, 1996; pp. 15-20, including slide show presentation at http://daedalus.cs.berkeley.edu/talks/retreat.6.97/BARWAN.S97.ppt.Applicant
- USPO's Decision dated Nov. 28, 2008 Denying Ex Parte Reexamination of USPN 7,103,511 in U.S. Appl. No. 90/010,315.Applicant
- USPTO's Decision dated Jun. 22, 2009 Granting Ex Parte Reexamination of USPN 7,103,511 in U.S. Appl. No. 90/010,509.Applicant
- USPTO's Decision dated Jun. 22, 2009 Granting Ex Parte Reexamination of USPN 7,103,511 in U.S. Appl. No. 90/010,505.Applicant
- USPTO's Decision dated Jun. 22, 2009 Granting Ex Parte Reexamination of USPN 7,103,511 in U.S. Appl. No. 90/010,507.Applicant
- USPTO's Decision dated Jun. 22, 2009 Granting Ex Parte Reexamination of USPN 7,103,511 in U.S. Appl. No. 90/010,508.Applicant
- USPTO's Decision dated Jul. 21, 2009 Granting Ex Parte Reexamination of USPN 6,891,838 in U.S. Appl. No. 90/010,512.Applicant
- USPTO's Decision dated Jul. 21, 2009 Granting Ex Parte Reexamination of USPN 6,891,838 in U.S. Appl. No. 90/010,510.Applicant
- USPTO's Decision dated Jul. 21, 2009 Granting Ex Parte Reexamination of USPN 6,891,838 in U.S. Appl. No. 90/010,511.Applicant
- USPTO's Decision dated Nov. 13, 2008 Granting Ex Parte Reexamination of USPN 6,891,838 in U.S. Appl. No. 90/010,301.Applicant
- K. Bult, et al.; “Low Power Systems for Wireless Microsensors;” UCLA Electrical Engineering Department, Los Angeles, CA and Rockwell Science Center, Thousand Oaks, CA; pp. 25-29.Applicant
- David B. Johnnson and David A. Maltz, Dynamic Source Routing in Ad Hoc Wireless Networks; Computer Science Department, Carnegie Mellon University; a chapter in Mobile Computing; Feb. 29, 1996; pp. 1-18.Applicant
- David A. Maltz et al.; Experiences Designing and Building a Multi-Hop Wireless Ad Hoc Network Testbed; School of Computer Science, Carnegie Mellon University; Mar. 5, 1999; pp. 1-20.Applicant
- “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications;” IEEE Std 802.11-1997; published Jun. 26, 1997 by the IEEE; pp. 1-459.Applicant
- John Jubin and Janet D. Tornow; “The DARPA Packet Radio Network Protocols;” Proceedings of the IEEE; vol. 75, No. 1, Jan. 1987; pp. 64-79.Applicant
- Chane Lee Fullmer; “Collision Avoidance Techniques for Packet-Radio Networks” thesis; University of California at Santa Cruz, CA; Jun. 1998; pp. 1-172.Applicant