US 7,697,492 B2Grant
Systems and methods for monitoring and controlling remote devices
Issue Date:2010-04-13
•25 Claims
•10 Drawing Sheets
Abstract
Systems and methods for monitoring and controlling remote devices are provided. In an embodiment, a system can comprise one or more remotely controlled sensors and actuators. The remote sensors/actuators can interface with uniquely identified remote transceivers that transmit and/or receive data. The embodiment can also comprise a plurality of transceivers each having a unique address, and a controller adapted to communicate with at least one of the transceivers in a preformatted message. A sensor can be associated with at least one transceiver to detect a condition and output a data signal to the transceiver, and an actuator can be associated with a transceiver to receive a control signal and activate a device. Other embodiments are also claimed and described.
Metadata
Assignee
- Sipco, LLC
Inventor
- Thomas David Petite
Application Information
Application Number:US 11/159,768
Filing Date:2005-06-23
Priority Date:1998-06-22
Art Unit:2419
Classifications
IPC:
H04W4/00
Patent Drawings (10 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 09/812,044, filed Mar. 19, 2001, and entitled “System and Method for Monitoring and Controlling Remote Devices”, now U.S. Pat. No. 6,914,893. U.S. patent application Ser. No. 09/812,044 is a continuation-in-part of: U.S. patent application Ser. No. 09/704,150, filed Nov. 1, 2000, and entitled “System and Method for Monitoring and Controlling Residential Devices”, now U.S. Pat. No. 6,891,838; 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; U.S. patent application Ser. No. 09/102,178, filed Jun. 22, 1998, and entitled, “Multi-Function General Purpose Transceiver”, now U.S. Pat. No. 6,430,268; U.S. patent application Ser. No. 09/172,554, filed Oct. 14, 1998, and entitled, “System for Monitoring the Light Level Around an ATM”, now U.S. Pat. No. 6,028,522; and U.S. patent application Ser. No. 09/412,895, filed Oct. 5, 1999, and entitled, “System and Method for Monitoring the Light Level Around an ATM”, now 6,218,953. U.S. patent application Ser. No. 09/812,044 also claims the benefit of U.S. Provisional Application Ser. No. 60/224,043, filed Aug. 9, 2000, and entitled “SOS OEA Packet Message Protocol (RF)”. Each of the above-identified applications are hereby incorporated by reference in their entireties as if fully set forth below.
Technical Field
[0002] The present invention generally relates to remotely operated systems, and more particularly to a system for monitoring, controlling and, reporting on remote systems utilizing radio frequency (RF) transmissions.
Background
[0003] There are a variety of systems for monitoring and controlling manufacturing processes, inventory systems, and emergency control systems. Most automatic systems use remote sensors and controllers to monitor and automatically respond to system parameters to reach desired results. A number of control systems utilize computers to process sensor outputs, model system responses, and control actuators that implement process corrections within the system. For example, the electric power generation and metallurgical processing industries successfully control production processes by utilizing computer control systems.
[0004] Many environmental and safety systems require real-time monitoring. Heating, ventilation, and air-conditioning systems (HVAC), fire reporting and suppression systems, alarm systems, and access control systems utilize real-time monitoring, and often require immediate feedback and control.
[0005] A problem with expanding the use of control system technology is the cost of the sensor/actuator infrastructure required to monitor and control such systems. The typical approach to implementing control system technology includes installing a local network of hard sensor(s)/actuator(s) and a local controller. There are expenses associated with developing and installing the appropriate sensor(s)/actuator(s) and connecting functional sensor(s)/actuator(s) with the local controller. Another prohibitive cost of control systems is the installation and operational expenses associated with the local controller.
[0006] FIG. 1 sets forth a block diagram illustrating certain fundamental components of a prior art control system 100. The prior art control system 100 includes a plurality of sensor/actuators 111, 112, 113, 114, 115, 116, and 117 electrically and physically coupled to a local controller 110. Local controller 110 provides power, formats and applies data signals from each of the sensors to predetermined process control functions, and returns control signals as appropriate to the actuators. Often, prior art control systems are further integrated via the public switched telephone network (PSTN) 120 to a central controller 130. Central controller 130 can also serve as a technician monitoring station and/or forward alarm conditions via PSTN 120 to appropriate officials.
[0007] Prior art control systems similar to that of FIG. 1 require the development and installation of an application-specific local system controller. In addition, each local system requires the direct coupling of electrical conductors to each sensor and actuator to the local system controller. Such prior art control systems are typically augmented with a central controller 130 that may be networked to the local controller 110 via PSTN 120. As a result, prior art control systems often are susceptible to a single point of failure if the local controller 110 goes out of service. Also, appropriately wiring an existing industrial plant can be dangerous and expensive.
Brief Summary of the Invention
[0008] The embodiments of present invention are directed to a system and method of monitoring and controlling remote devices. More specifically, the present system is directed to a system for monitoring and controlling remote devices by transmitting data between the remote systems and a gateway interface via a packet message protocol system.
[0009] A preferred embodiment can comprise one or more remote sensors to be read and one or more actuators to be remotely controlled. The remote sensor(s)/actuator(s) can interface with unique remote transceivers that transmit and/or receive data. If necessary in individual applications, signal repeaters may relay information between the transceiver(s) and the gateway interface. Communication links between the remote transceivers and the gateway interface are preferably wireless, but may also be implemented with a mixture of wireless and wired communication links.
[0010] To successfully communicate between the transceiver(s) and the gateway interface, a preferred embodiment of the present invention can receive a plurality of RF signal transmissions containing a packet protocol via a preferred embodiment of data structures that include sender and receiver identifiers, a description of the packet itself, a message number, commands, data, and an error detector. The data structure can be integrated with alternate data communication protocols for use with many other communication systems and networks. Also, a preferred embodiment of the present invention can be integrated into an existing control system using networked wireless transceivers. Distinct control signals from the pre-existing system can be mapped into the packet protocol enabling integration into a pre-existing control system easily and inexpensively.
Brief Description of the Drawings
[0011] FIG. 1 is a block diagram of a prior art control system.
[0012] FIG. 2 is a block diagram illustrating a monitoring/control system in accordance with a preferred embodiment of the present invention.
[0013] FIG. 3 is a block diagram illustrating a transceiver in accordance with a preferred embodiment of the present invention.
[0014] FIG. 4 is a block diagram illustrating a transmitter in accordance with a preferred embodiment of the present invention.
[0015] FIG. 5 is a block diagram illustrating a transceiver in accordance with a preferred embodiment of the present invention integrated with a sensor and an actuator.
[0016] FIG. 6 is a block diagram illustrating a local gateway in accordance with a preferred embodiment the present invention.
[0017] FIG. 7 is a table illustrating the message protocol in accordance with a preferred embodiment of the present invention.
[0018] FIG. 8 is a table illustrating various “to” addresses in accordance with a preferred embodiment of the present invention.
[0019] FIG. 9 illustrates three sample messages using a message protocol system in accordance with an embodiment of the present invention.
Detailed Description of Preferred Embodiments
[0020] FIG. 2 sets forth a block diagram illustrating a preferred embodiment of a control system 200 in accordance with the present invention. The control system 200 can consist of one or more transceivers. An exemplary transceiver 205 can be integrated with a sensor 224 to form a first combination. A second transceiver 207 can be integrated with an actuator 222 to form a second combination. The transceivers 205, 207 are preferably wireless RF transceivers that are small and transmit a low-power-RF signal. As a result, in some applications, the transmission range of a given transceiver 205, 207 may be limited. As will be appreciated from the description that follows, this limited transmission range of the transceivers 205, 207 can be a desirable characteristic of the control system 200. Although the transceivers 205, 207 are depicted without user interfaces such as a keypad (not shown), the transceivers 205, 207 may be configured with user selectable buttons or an alphanumeric keypad (not shown). Often, the transceivers 205, 207 can be electrically interfaced with a sensor/actuator 222 such as a smoke detector, a thermostat, or a security system, where external buttons are not needed.
[0021] One or more specific types of RF transceivers can be used with the various embodiments of the present invention. For example, one RF transceiver that may be used is the TR1000, manufactured by RF Monolithics, Inc. The TR1000 hybrid transceiver is well suited for short range, wireless data applications where robust operation, small size, low power consumption, and low-cost are desired. All critical RF functions may be performed within a single hybrid semi-conductor chip, simplifying circuit design and accelerating the design-in process. The receiver section of the TR1000 is sensitive and stable. A wide dynamic range log detector, in combination with digital automatic gain control (AGC) provides robust performance in the presence of channel noise or interference. Two stages of surface acoustic wave (SAW) filtering provide excellent receiver out-of-band rejection. The TR100 includes provisions for both on-off keyed (OOK) and amplitude-shift key (ASK) modulation. The TR100 employs SAW filtering to suppress output harmonies, for compliance with FCC and other regulations.
[0022] Additional details of the TR1000 transceiver need not be described herein, because the present invention is not limited by the particular choice of transceiver. Indeed, numerous RF transceivers may be implemented in accordance with the teachings of the present invention. Such other transceivers may include other 900 MHz transceivers, as well as transceivers at other frequencies. In addition, infrared, ultrasonic, and other types of wireless transceivers may be employed. Further details of the TR1000 transceiver may be obtained through data sheets, application notes, design guides (e.g., the “ASH Transceiver Designers Guide”), and other publications.
[0023] The control system 200 can also include a plurality of stand-alone transceivers 211, 213, 215, and 221. Each of the stand-alone transceivers 211, 213, 215, and 221, and each of the integrated transceivers 212, 214, 216, 222, and 224 can receive an incoming RF transmission and transmit an outgoing signal. This outgoing signal may be a low-power-RF transmission signal, a high-power-RF transmission signal, or may be electric signals transmitted over a conductive wire, a fiber optic cable, or other transmission media. It will be appreciated by those skilled in the art that the integrated transceivers 212, 214, 216, 222, and 224 can be replaced by RF transmitters for applications that require continuous data collection only.
[0024] The local gateways 210 and 220 can receive remote data transmissions from one or more of the stand-alone transceivers 211, 213, 215, and 221, or one or more of the integrated transceivers 212, 214, 216, 222, and 224. The local gateways 210 and 220 can analyze the transmissions received, convert the transmissions into TCP/IP format, and further communicate the remote data signal transmissions via the WAN 230. The local gateways 210 and 220 may communicate information, service requests, and/or control signals to the remote integrated transceivers 212, 214, 216, 222, and 224, from the server 260, the laptop computer 240, and/or the workstation 250 across the WAN 230. The server 260 can be further networked with the database server 270 to record client specific data. Further information regarding the integration of embodiments of the present invention into the WAN 230 can be found in U.S. Pat. No. 6,891,838 application entitled, “System and Method for Monitoring and Controlling Residential Devices.”
[0025] It will be appreciated by those skilled in the art that if an integrated transceiver (either of 212, 214, 216, 222, and 224) is located sufficiently close to one of the local gateways 210 or 220 such that the integrated transceiver's outgoing signal can be received by a gateway, the outgoing signal need not be processed and repeated through one of the stand-alone transceivers 211, 213, 215, or 221.
[0026] A monitoring system constructed in accordance with the teachings of the present invention may be used in a variety of environments. In accordance with a preferred embodiment, a monitoring system 200 such as that illustrated in FIG. 2 may be employed to monitor and record utility usage by residential and industrial customers, to transfer vehicle diagnostics from an automobile via a RF 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 an irrigation system, or to automate a parking facility. Further information regarding these individual applications can be found in U.S. Pat. No. 6,891,838 entitled, “System and Method for Monitoring and Controlling Residential Devices.”
[0027] The integrated transceivers 212, 214, 215, 222, and 224 can have substantially identical construction (particularly with regard to their internal electronics), which provides a cost-effective implementation at the system level. Alternatively, the transceivers (integrated or stand-alone) can differ as known to one of ordinary skill in the art as necessitated by individual design constraints. Furthermore, a plurality of stand alone transceivers 211, 213, 215, and 221, which may be identical, can be disposed in such a way that adequate RF coverage is provided. Preferably, the stand-alone transceivers 211, 213, 215, and 221 may be dispersed sufficient that only one stand-alone transceiver will pick up a transmission from a given integrated transceiver 212, 214, 216, 222, and 224 (due in part to the low power transmission typically emitted by each transmitter).
[0028] In certain instances, however, two or more, stand-alone transceivers may pick up a single transmission. Thus, the local gateways 210 and 220 may receive multiple versions of the same data transmission from an integrated transceiver, but from different stand-alone transceivers. The local gateways 210 and 220 may utilize this information to triangulate or otherwise more particularly assess a location from which the common data transmission is originating. Due to the transmitting device identifier incorporated within the preferred protocol in the transmitted signal, duplicative transmissions (e.g., transmissions duplicated to more than one gateway or to the same gateway) may be ignored or otherwise appropriately handled.
[0029] The advantage of integrating a transceiver, as opposed to a one-way transmitter, with the sensor is the transceiver's ability to receive incoming control signals and to transmit data signals upon demand. The local gateways 210 and 220 may communicate with all system transceivers. Since the local gateways 210 and 220 can be permanently integrated with the WAN 230, the server 260 coupled to the WAN 230 can host application specific software. Further, the data monitoring and control devices of the present invention can be movable as necessary given that they remain within signal range of a stand-alone transceiver 211, 213, 215, or 221 that subsequently is within signal range of a local gateway 210, 220 interconnected through one or more networks to server 260. As such, small application specific transmitters compatible with control system 200 can be worn or carried. It will be appreciated that a person so equipped may be in communication with any device communicatively coupled with the WAN 230.
[0030] In one embodiment, the server 260 collects, formats, and stores client specific data from each of the integrated transceivers 212, 214, 216, 222, and 224 for later retrieval or access from the workstation 250 or the laptop 240. The workstation 250 or the laptop 240 can be used to access the stored information through a Web browser. In another embodiment, the server 260 may perform the additional functions of hosting application specific control system functions and replacing the local controller by generating required control signals for appropriate distribution via the WAN 230 and the local gateways 210, 220 to the system actuators. In another embodiment, clients may elect for proprietary reasons to host any control applications on their own WAN connected workstation. The database 270 and the server 260 may act solely as a data collection and reporting device with the client workstation 250 generating control signals for the system.
[0031] Reference is now made to FIG. 3 , which is a block diagram illustrating certain functional blocks of a transceiver 340 that may be integrated with sensor 310 in accordance with a preferred embodiment of the present invention. For example, sensor 310 in its simplest form can be a two-state device, such as a smoke alarm. Alternatively, the sensor 310 may output a continuous range of values to the data interface 321 such as a thermometer. If the signal output from the sensor 310 is an analog signal, the data interface 321 may include an analog-to-digital converter (not shown) to convert signals output to the transceiver 340. Alternatively, a digital interface (communicating digital signals) may exist between the data interface 321 and each sensor 310.
[0032] The sensor 310 can be communicatively coupled with the RF transceiver 340. The RF transceiver 340 may comprise a RF transceiver controller 328, a data interface 321, a data controller 324, a transceiver identifier 326, and an antenna 328. As shown in FIG. 3 , a data signal forwarded from the sensor 310 may be received at an input port of the data interface 321. The data interface 321 may be configured to receive the data signal. In those situations where the data interface has received an analog data signal, the data interface 321 may be configured to convert the analog signal into a digital signal before forwarding a digital representation of the data signal to the data controller 324.
[0033] In accordance with a preferred embodiment, each transceiver 340 may be configured with a unique transceiver identification 326 that uniquely identifies the RF transceiver 340. The transceiver identification 326 may be programmable, and implemented an EPROM. Alternatively, the transceiver identification 326 may be set and/or configured through a series of dual inline package (DIP) switches. Additional implementations of the transceiver identification 326, whereby the number may also be set and/or configured as desired, may be implemented.
[0034] The unique transceiver identification 326 coupled with a function code for a sensor “on” condition can be formatted by data controller 324 for transformation into the RF signal 330 by RF transmitter 328 and transmission via antenna 323.
[0035] While the unique transceiver address can be varied, it is preferably a six-byte address. The length of the address can be varied as necessary given individual design constraints. This data packet 330 communicated from transceiver 340 will readily distinguish from similar signals generated by other transceivers in the system.
[0036] Of course, additional and/or alternative configurations may also be provided by a similarly configured transceiver. For example, a similar configuration may be provided for a transceiver that is integrated into, for example, a carbon monoxide detector, or a door position sensor. Alternatively, system parameters that vary across a range of values may be transmitted by transceiver 340 as long as data interface 321 and data controller 324 are configured to apply a specific code that is consistent with the input from sensor 310. As long as the code was understood by the server 260 or workstation 250, the target parameter can be monitored by the embodiments of the present invention.
[0037] Reference is now made to FIG. 4 . FIG. 4 is a block diagram illustrating a transmitter in accordance with a preferred embodiment of the present invention. The sensor 400 may be coupled to the RF transmitter 410. The RF transmitter 410 may comprise a transmitter controller 405, a data interface 420, a data controller 425, a transmitter identification 430, and an antenna 440. The data signal forwarded from the sensor 400 may be received at an input port of the data interface 420. The data interface 420 may be configured to receive the data signal. In those situations where the data interface 420 has received an analog data signal, the data interface 420 may be configured to convert the analog signal into a digital signal before forwarding a digital representation of the data signal to the data controller 425.
[0038] Each transmitter/transceiver 410 may be configured with a unique transmitter identification 430 that uniquely identifies the RF transmitter 410. The transmitter identification number 430 may be programmable, and implemented with an EPROM. Alternatively, the transmitter identification 430 may be set and/or configured through a series of dual inline package (DIP) switches. Additional implementations of the transmitter identification 430, whereby the identification may be set and/or configured as desired, may also be implemented.
[0039] The data controller 425 may be configured to receive both a data signal from the data interface 420 and the transmitter identification 430. The data controller 425 may be configured to format (e.g., concatenate) both data portions into a composite information signal. The composite information signal may be forwarded to the transmitter controller 415 which can then transmit the encoded RF signal from the sensor 400 via a packet message protocol system. The transmitter controller 415 may convert information from digital electronic form into a format, frequency, and voltage level suitable for transmission from antenna 440. The transmitter identification 430 can be set for a given transmitter 410. When received by the application server 260 (FIG. 2 ), the transmitter identification 430 may be used to access a look-up table that identifies, for example, the location, the system, and the particular parameter assigned to that particular transmitter. Additional information about the related system may also be provided within the lookup table, with particular functional codes associated with a corresponding condition or parameter, such as but not limited to, an appliance operating cycle, a power status, a temperature, a position, and other information.
[0040] FIG. 5 sets forth a block diagram of the transceiver 500 integrated with a sensor 510 and an actuator 520 in accordance with a preferred embodiment of the present invention. Here, the data interface 525 is shown with a single input from the sensor 510. It is easy to envision a system that may include multiple sensor inputs. The RF transceiver 500 may comprise a transceiver controller 530, a data interface 525, a data controller 535, a transceiver identification 540, and an antenna 550. The data signal forwarded from the sensor 510 may be received at an input/output port of the data interface 525. The data interface 525 may be configured to receive the data signal and transmit a command signal. In those situations where the data interface 525 has received an analog data signal, the data interface 525 may be configured to convert the analog signal into a digital signal before forwarding a digital representation of the data signal to the data controller 525. Similarly, when the data controller 535 forwards a digital representation of a command signal, the data interface 525 may be configured to translate the digital command signal into an analog voltage suitable to drive the actuator 520.
[0041] In accordance with a preferred embodiment, each RF transceiver 500 may be configured with a unique transceiver identification 540 that uniquely identifies the RF transceiver 500. The transceiver identification 540 may be set or configured as described above.
[0042] The data controller 535 may be configured to receive both a data signal from the data interface 525 and the transceiver identification number 540. The data controller 535 may also receive one or more data signals from other RF communication devices. As previously described, the data controller 535 may be configured to format (e.g., concatenate) both data signal portions originating at the RF transceiver 500 into a composite information signal which may also include data information from other closely located RF communication devices. The composite information signal may be forwarded to a transceiver controller 530, which may be configured to transmit the encoded RF data signals via the packet messaging system. It will be appreciated that the transceiver controller 530 may convert information from digital electronic form into a format, frequency, and voltage level suitable for transmission from the antenna 550.
[0043] For example, a common home heating and cooling system might be integrated with an embodiment of the present invention. The home heating system may include multiple data interface inputs from multiple sensors. A home thermostat control connected with the home heating system could be integrated with a sensor that reports the position of a manually adjusted temperature control (i.e., temperature set value) and a sensor integrated with a thermister to report an ambient temperature. The condition of related parameters can be sent to the data interface 525 as well as including the condition of the system on/off switch, the climate control mode selected (i.e., heat, fan, or AC). In addition, depending upon the specific implementation, other system parameters may be provided to data interface 525 as well.
[0044] The addition of the actuator 520 to the integrated transceiver 500 permits the data interface 525 to apply signals to the manual temperature control for the temperature set point, the climate control mode switch, and the system on/off switch. This, a remote workstation 250 or a laptop 240 with WAN access (see FIG. 2 ) could control a home heating system from a remote location.
[0045] Again, each of these various input sources can be routed to the data interface 525, which provides the information to the data controller 535. The data controller 535 may utilize a look up table to access unique function codes that are communicated in the data packet 560, along with a transceiver identification code 540, to the local gateway and further onto the WAN. In general, the operation of RF transceiver 500 will be similar to that described above.
[0046] The various RF communication devices illustrated and described may be configured with a number of optional power supply configurations. For example, a personal mobile transceiver may be powered by a replaceable battery. Similarly, a stand-alone RF transceiver repeater may be powered by a replaceable battery that may be supplemented and/or periodically charged via a solar panel. These power supply circuits, therefore, may differ from RF communication device to RF communication device depending upon the remote system monitored, the related actuators to be controlled, the environment, and the quality of service level required. Those skilled in the art will appreciate and understand how to meet the power requirements of the various RF communication devices. As a result, it is not necessary to further describe a power supply suitable for each RF communication device and each application in order to appreciate the concepts and teachings of the present invention.
[0047] Having illustrated and described the operation of the various combinations of RF communication devices with the various sensors 114 and sensor actuators 112 consistent with the present invention, reference is now made to FIG. 6 . FIG. 6 is a block diagram further illustrating a local gateway 600 in accordance with a preferred embodiment of the present invention. A local gateway 600 may comprise an antenna 610, an RF transceiver 615, a central processing unit (CPU) 620, a memory 625, a network card 630, a digital subscriber line (DSL) modem 635, and an integrated services digital network (ISDN) interface card 640. The local gateway 600 can also include many other components not illustrated in FIG. 6 , capable of enabling a terminal control protocol Internet protocol (TCP/IP) connection to the WAN 130.
[0048] The RF transceiver 615 may be configured to receive incoming RF signal transmissions via an antenna 610. Each of the incoming RF signal transmissions can be consistently formatted in the convention previously described. The local gateway 600 may also be configured such that the memory 625 includes a look-up table 650 that may assist in identifying the various remote and intermediate RF communication devices used in generating and transmitting the received data transmission as illustrated in memory sectors 650 and 660 herein labeled, “Identify Remote Transceiver” and “Identify Intermediate Transceiver,” respectively. Programmed or recognized codes within the memory 625 may also be provided and configured for controlling the operation of a CPU 620 to carry out the various functions that are orchestrated and/or controlled by the local gateway 600. For example, the memory 625 may include program code for controlling the operation of the CPU 625 to evaluate an incoming data packet to determine what action needs to be taken. One or more look-up tables 650 may also be stored within the memory 625 to assist in this process. Furthermore, the memory 625 may be configured with program code to identify a remote RF transceiver 655 or identify an intermediate RF transceiver 660. Function codes, RF transmitter and/or RF transceiver identification numbers may all be stored with associated information in the look-up tables 650.
[0049] Thus, one look-up table 650 may be provided to associate transceiver identifications with a particular user. Another look-up table 650 may be used to associate function codes with the interpretation thereof. For example, a unique code may be associated by a look-up table 650 to identify functions such as test, temperature, smoke alarm active, or security system breach. In connection with the lookup table(s) 650, the memory 625 may also include a plurality of code segments that are executed by the CPU 620, which may control operation of the gateway 600. For example, a first data packet segment 665 may be provided to access a first lookup table to determine the identity of the RF transceiver 625, which transmitted the received message. A second code segment may be provided to access a second lookup table to determine the proximate location of the message generating RF transceiver 600, by identifying the RF transceiver 600 that relayed the message. A third code segment may be provided to identify the content of the message transmitted. Namely, is it a fire alarm, a security alarm, an emergency request by a person, or a temperature control setting. Additional, fewer, or different code segments may be provided to carry out different functional operations and data signal transfers.
[0050] The local gateway 600 may also include one or more mechanisms to facilitate network based communication with remote computing devices. For example, the gateway 600 may include a network card 630, which may allow the gateway 600 to communicate across a local area network to a network server, which in turn may contain a backup gateway 110 to the WAN 645. Alternatively, the local gateway 600 may contain a DSL modem 635, which may be configured to provide a link to a remote computing system, by way of the PSTN. In yet another alternative, the local gateway 600 may include an ISDN card 640 configured to communicate via an ISDN connection with a remote system. Other communication interfaces may be provided as well to serve as primary and or backup links to the WAN 645 or to local area networks that might serve to permit local monitoring of local gateway 600 health and data packet control.
[0051] For each of the remote devices to communicate, there needs to be a standard enabling each device to understand a message. FIG. 7 sets forth a format of a data packet protocol in accordance with a preferred embodiment of the present invention. All messages transmitted within the system consist of a “to” address 700, a “from” address 710, a packet number 720, a number of packets in a transmission 730, a packet length 740, a message number 750, a command number 760, any data 770, and a check sum error detector (CKH 780 and CKL 790).
[0052] The “to” address 700 can indicate 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 700 can indicate a general message to all transceivers, to only the stand-alone transceivers, or to an individual integrated transceiver. In a six byte “to” address, the first byte indicates the transceiver type to all transceivers, to some transceivers, or a specific transceiver. The second byte can be the identification base, and bytes three through six can be used for the unique transceiver address (either stand-alone or integrated). The “to” address 700 can be scalable from one byte to six bytes depending upon the intended recipient(s).
[0053] The “from” address 710 can be a the six-byte unique transceiver address of the transceiver originating the transmission. The “from” address 710 can be the address of the controller when the controller requests data, or this can be the address of the integrated transceiver when the integrated transceiver sends a response to a request for information to the controller.
[0054] The packet number 720, the packet maximum 730, and the packet length 740 can be used to concatenate messages that are greater than 128 bytes. The packet maximum 730 can indicate the number of packets in the message. The packet number 720 may be used to indicate a packet sequence number for a multiple-packet message.
[0055] The message number 750 can be originally assigned by the controller. Messages originating from the controller can be assigned an even number. Responses to the controller can be the original message number plus one, rendering the responding message number odd. The controller can then increment the message number 750 by two for each new originating message. This enables the controller to coordinate the incoming responses to the appropriate command message.
[0056] The next section is the command byte 760 that requests data from the receiving device as necessary. There can be two types of commands: device specific and not device specific. Device specific commands can control a specific device such as a data request or a change in current actuator settings. A number of commands are not device specific. Such commands are for example, but not limited to, a ping, an acknowledge, a non-acknowledgement, downstream repeat, upstream repeat, read status, emergency message, and a request for general data, among others. General data may include a software version number, the number of power failures, and/or the number of resets.
[0057] The data 770 section may contain data as requested by a specific command. The requested data can be many values. By way of example, test data can be encoded in ASCII (American Standard Code for Information Interchange) or many other encoding systems. The data section of a single packet can be scalable up to 109 bytes. When the requested data exceeds 109 bytes, the integrated transceiver can divide the data into appropriate number of sections and concatenates the series of packets for one message using the packet identifiers as discussed above.
[0058] The checksum sections 780, 790 can be used to detect errors in the 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, many other error detection systems can be used.
[0059] In one embodiment of this invention, this system can be implemented via an RF link at a basic rate of 4,800 bits per second (bps) with a data rate of 2,400 bps. All the data can 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. Other RF formats can be used depending upon individual design constraints. For example, a quadrature phase shift encoding method could be used, enabling the control system to communicate via hexadecimal instead of binary.
[0060] While the message indicates 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 can vary because of the scalability of the “to” address, the command byte, and the scalability of the data.
[0061] The message can further include a preface and a postscript (not shown). The preface and postscripts are not part of the message body, but rather serve to synchronize the control system and to frame each packet of the message. The packet begins with the preface and ends with a postscript. The preface can be a series of twenty-four logic ones followed by two bit times of high voltage with no transition. The first byte of the packet can then follow immediately. The postscript will be a transition of the transmit data line from a high voltage to a low voltage, if necessary. It is less desirable to not leave the transmit data line high after the message is sent.
[0062] FIG. 8 sets forth a preferred embodiment of the “to” address byte assignment in accordance with an embodiment of the present invention. As shown in FIG. 8 , the “to” address consists of six bytes. The first byte (Byte 1) can indicate the device type. The second byte (Byte 2) can indicate the manufacturer or the owner. The third byte (Byte 3) can be a further indication of the manufacturer or owner. The fourth byte (Byte 4) can either indicate 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 byte can be a particular code. If the message is for a particular device, the fourth, fifth, and sixth bytes (Byte 5 and Byte 6) can be a unique identifier for the particular devices.
[0063] Having described a general message structure in accordance with an embodiment of the present invention, reference is made to FIG. 9 . FIG. 9 illustrates three sample messages. The first message 910 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.”
[0064] The second message 920 illustrates how the first message might be sent to a stand-alone transceiver. Emergency message “FF” from a central server with address “00123456578” can be first sent to stand-alone transceiver “FO.” The second message contains additional command data “A000123456” that may be used by the system to identify further transceivers to send the signal through on the way to the destination device.
[0065] The third message 930 illustrated in FIG. 9 illustrates how the message protocol of the present invention may be used to “ping” a remote transceiver to determine transceiver health. For example, source unit “E112345678” may originate a ping request by sending command “08” to a transceiver identified as “A012345678.” The response to the ping request can be as simple as reversing the “to address” and the “from address” of the command such that a healthy receiver will send a ping message back to the originating device. A system in accordance with a preferred embodiment of the present invention may be configured to expect a return ping within a specific time period. Operators of the present invention could 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 of the system.
[0066] Returning to FIG. 2 , the local gateway 210 can act as a local communications master in a system, such as system 200. With the exception of emergency messages, the local gateway 210 usually initiates communications with any remote transceivers (either stand-alone 211, 213, 215, 221 or integrated 212, 214, 216, 224). The remote transceivers then respond based upon the command received in the message. In general, the local gateway 210 expects a response to all messages sent to any of the remote transceivers 211, 212, 213, 214, 215, 216, 221, and 225.
[0067] To acknowledge a message, any of the remote transceivers 211, 212, 213, 214, 215, 216, 221, 224 can send one of two messages: a positive acknowledgement or a negative acknowledgement. The positive acknowledgement may have two forms. When the message is between the local gateway 210 or a stand-alone transceiver 211, 213, 215, 221 and another stand-alone transceiver 211, 213, 215, 221, the acknowledgement can be a re-send the original message with no changes. The second form is for a message sent from the local gateway 210 stand-alone transceiver 211, 213, 215, 221 to a integrated transceiver 212, 214, 216, 224. In this case, the positive acknowledgement can be a message containing the requested data.
[0068] Emergency messages are preferably the only messages initiated by the integrated transceivers 212, 214, 216, 224. To accommodate receiving any emergency messages, the local gateway 210 may dedicate one-half of every ten-second period to receive emergency messages. During these time periods, the local gateway 210 may not transmit messages other than acknowledgements to any emergency messages. The integrated transceivers 212, 214, 216, 224 may detect the period of silence, and in response, may then transmit the emergency message.
[0069] There are typically two forms of emergency messages: from personal safety/security transceiver(s) and from permanently installed safety/security transceiver(s). In the first case of the personal transceiver, the emergency message can consist of a predetermined “to” address and an odd, random number. In response to this emergency message, the local gateway 210 can acknowledge during a silent period. The personal transceiver can then repeat the same emergency message. The local gateway 210 can then forward the emergency message on to the WAN 230 in the normal manner.
[0070] Upon receipt of the local gateway 210 acknowledgement, the personal transceiver can reset itself. If no acknowledgement is received within a predetermined time period, the personal transceiver may continue to re-transmit the original emergency message until acknowledged by the local gateway 210 for a predetermined number of re-transmissions.
[0071] In the second case, the permanently installed safety/security transceiver (212) may send one message to the local gateway 210 during a time out period. The emergency message can be transmitted to a predetermined address other than the emergency address for personal transceivers.
[0072] The foregoing description has illustrated certain fundamental concepts of the invention, and other additions and/or modifications may be made consistent with the inventive concepts. For example, the one-way transmitters may be adapted to continuously monitor the current status of water, gas, and other utility meters. One-way transmitters might further be used to monitor and report actual operational hours on rental equipment or any other apparatus that must be serviced or monitored on an actual run-time schedule.
[0073] The transceivers of the current invention may be adapted to monitor and apply control signals in an unlimited number of applications. For example, two-way transceivers of the current invention can be adapted for use with pay-type-publicly-located telephones, cable television set converter boxes, and a host of residential appliances and devices enabling a remote controllable home automation and security system. For example, building automation systems, fire control systems, alarm systems, industrial trash compactors, and building elevators can be monitored and controlled with devices consistent with the present invention. In addition, courier drop boxes, time clock systems, automated teller machines, self-service copy machines, and other self-service devices can be monitored and controlled as appropriate. By way of further example, a number of environment variables that require monitoring can be integrated with the system of the present invention 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 can be remotely monitored.
[0074] In a geographic area appropriately networked with permanently located stand-alone transceivers consistent with the embodiments of the invention, personal transceivers can be used to monitor and control personnel access and egress from specific rooms or portions within a controlled facility. Personal transceivers can also 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.
[0075] The transceivers using the packet message protocol of the present invention may be further integrated with a voice-band transceiver. As a result, when a person presses, for example, the emergency button on a transmitter, medical personnel, staff members, or others may respond by communicating via two-way radio with the person. Each transceiver may be equipped with a microphone and a speaker enabling a person to communication information such as their present emergency situation or their specific location.
[0076] The foregoing description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the inventions to the precise embodiments disclosed. Obvious modifications or variations are possible in light of the above teachings. For example, the transceiver can be permanently integrated into an alarm sensor or other stationary device within a system, and the control system server and/or local gateway could be configured to identify the transceiver location by the transceiver identification number alone. It will be appreciated that, in embodiments that do not utilize stand-alone transceivers, the transceivers will be configured to transmit at a high RF power level to effectively communicate with the control system local gateway.
[0077] It will be appreciated by those skilled in the art that the information transmitted and received by the wireless transceivers of the present invention may be further integrated with other data transmission protocols for transmission across telecommunications and computer networks. In addition, it should be further appreciated that telecommunications and computer networks can function as a transmission path between the networked wireless transceivers, the local gateways, and the central server.
[0078] While the various embodiments of this invention have been described in detail with particular reference to exemplary embodiments, those skilled in the art will understand that variations and modifications can be effected within the scope of the invention as defined in the appended claims. Accordingly, the scope of the various embodiments of the present invention should not be limited to the above discussed embodiments, and should only be defined by the following claims and all applicable equivalents.
Claims
Post-issuance certificates present
The text shown below may not reflect later post-issuance changes.
I claim:
1. In a communication system to communicate command and sensed data between remote devices, the system comprising:
a receiver address comprising a scalable address of at least one remote device;
a command indicator comprising a command code;
a data value comprising a scalable message; and
a controller associated with a remote wireless device comprising a transceiver configured to send and receive wireless signals, the remote device configured to send a preformatted message comprising the receiver address, a command indicator, and the data value via the transceiver to at least one other remote device.
2. The system of claim 1, further comprising:
a plurality of transceivers each having a unique address, the transceiver being one of the plurality of transceivers;
a plurality of controllers associated with each the controller associated with at least one of the transceivers, the controller being in communication with at least one other transceiver with a preformatted message, the preformatted message having at least one scalable field;
at least one sensor associated with at least one of the transceivers to detect a condition and output a data signal to the transceiver; and
at least one actuator associated with at least one of the transceivers to activate a device.
3. The system of claim 1, wherein the controller sends the preformatted message via an associated transceiver, and at least one transceiver sends the preformatted response message.
4. The system of claim 1, wherein at least one transceiver receives the preformatted message requesting sensed data, confirms the receiver address as its own unique address, receives a sensed data signal, formats the sensed data signal into scalable byte segments, determines the number of segments required to contain the sensed data signal, and generates and transmits the preformatted response message comprising at least one packet.
5. The system of claim 4, wherein the packet further comprises:
a preface having a predetermined sequence including a first logic level and a subsequent sequence comprising at least two bytes of a second logic level; and
a postscript having a low voltage output.
6. The system of claim 1, wherein each remote device is adapted to transmit and receive radio frequency transmissions to and from at least one other transceiver.
7. The system of claim 1, wherein the preformatted message comprises Manchester encoding.
8. A method of communicating command and sensed data between remote wireless devices, the method comprising:
providing a receiver to receive at least one message;
wherein the message has a packet that comprises a command indicator comprising a command code, a scalable data value comprising a scalable message, and an error detector that is a redundancy check error detector; and
providing a controller to determine if at least one received message is a duplicate message and determining a location from which the duplicate message originated.
9. The method of claim 8, further comprising providing at least one remote wireless communication device, wherein at least one of the devices comprise geographically remote transceivers adapted to transmit and receive the at least one message using radio frequency transmissions.
10. The method of claim 8, further comprising providing at least one remote wireless communication device, wherein at least one of the devices has a unique address and the packet further comprises at least one scalable address field to contain the unique address for at least one device.
11. The method of claim 8, further comprising providing an actuator associated with at least one of the remote devices, the actuator configured to actuate in response to the command code.
12. The method of claim 8, further comprising sending at least one message via Manchester type encoding.
13. The method of claim 8, further comprising determining if an error exists in a packet of the at least one message.
14. A wireless communication device for use in a communication system to communicate command and sensed data between remote wireless communication devices, the wireless communication device comprising:
a transceiver configured to send and receive wireless communications; and
a controller configured to communicate with at least one other remote wireless device via the transceiver with a preformatted message, the controller further configured to format a message comprising a receiver address comprising a scalable address of at least one remote wireless device; a command indicator comprising a command code; a data value comprising a scalable message.
15. The wireless communication device of claim 14, further comprising at least one sensor configured to detect a condition and output a signal to the controller.
16. The wireless communication device of claim 14, wherein the controller is further configured to determine if at least one received message is a duplicate message and determine a location from which the duplicate message originated.
17. The wireless communication device of claim 14, further comprising at least one actuator configured to implement an action corresponding to the command code.
18. The device of claim 14, wherein the transceiver comprises a unique transceiver address to distinguish the transceiver from other transceivers.
19. In a system for communicating commands and sensed data between remote devices comprising a communications device for communicating commands and sensed data, the communications device comprising:
a transceiver operatively configured to be in communication with at least one other of a plurality of transceivers, wherein the transceiver has a unique address, wherein the unique address identities the individual transceiver, wherein the transceiver is geographically remote from the other of the plurality of transceivers, wherein each transceiver communicates with each of the other transceivers via preformatted messages;
a controller configured to be in communication with the transceiver, the controller configured to provide preformatted messages for communication; wherein the preformatted messages comprises at least one packet, wherein the packet comprises: a receiver address comprising a scalable address of the at least one of the intended receiving transceivers; sender address comprising the unique address of the sending transceiver; a command indicator comprising a command code; at least one data value comprising a scalable message; and an error detector comprising a redundancy check error detector; and wherein the controller is configured to interact with the transceiver to send preformatted command messages.
20. The communications device of claim 19, further comprising a sensor operatively configured to detect a condition and output a sensed data signal that corresponds to the condition to the transceiver.
21. The communications device of claim 20, wherein the transceiver is configured to receive a preformatted command message requesting sensed data, confirms the receiver address as its own unique address, receives the sensed data signal, formats the sensed data signal into scalable byte segments, determines a number of segments required to contain the sensed data signal, and generates and transmits the preformatted response message comprising at least one packet.
22. In a system for controlling geographically diverse devices from a central location, a communications device comprising:
means for dynamically sending and receiving messages, wherein the sent messages comprise commands and the received messages comprise responses to the commands, wherein the message comprises at least one means for packeting a message;
a means for communicating information, the communicating means comprising: means for receiving messages; means for preparing responses to the received message; and means for sending the response message; wherein each communicating means has a unique identifying address;
and wherein the packeting means comprises: means for identifying intended recipients; means for identifying a sender; means for indicating a command; means for data transfer; means for indicating potential error; means for indicating a byte length of a packet; means for indicating a total number of packets in a message; means for identifying a message; means for alerting a recipient to an incoming packet; and means for indicating an end of a packet.
23. The communications device of claim 21, wherein the means for communicating information is further configured to encode messages via Manchester encoding.
24. The communication device of claim 23, wherein the means for indicating potential error is configured to detect if an error exists in a packet or a number of packets of at least one message.
25. A wireless communication device for use in a communication system to communicate a number of commands and sensed data between remote wireless communication devices, the wireless communication device comprising:
a transceiver configured to send and receive wireless communications; and
a controller configured to communicate with at least one other remote wireless device via the transceiver with a preformatted message, the controller further configured to reformat a message comprising a receiver address comprising a scalable address of at least one remote wireless device; a command indicator comprising a command code; a data value comprising a scalable message.
Patent Citations (636)
| 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 |
| US3892948(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 |
| US4322842(A) | 1982-03-01 | Martinez | Examiner |
| 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 | Steck 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 | Applicant |
| 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. | Applicant |
| US5252967(A) | 1993-10-01 | Brennan et al. | Applicant |
| US5253167(A) | 1993-10-01 | Yoshida et al. | Applicant |
| US5265150(A) | 1993-11-01 | Helmkamp 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 | Glidwell et al. | Applicant |
| 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 | Akhteruzzman 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 | Ballestry et al. | Applicant |
| US5432507(A) | 1995-07-01 | Mussino et al. | Applicant |
| US5438329(A) | 1995-08-01 | Gastouniotis et al. | Applicant |
| 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, Jr. 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 | Caroll 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 | Dinkins | 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. | Applicant |
| 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. | Applicant |
| 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. | Applicant |
| 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 et al. | 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 | Roswell et al. | Applicant |
| US5719564(A) | 1998-02-01 | Sears | Examiner |
| 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. | Applicant |
| 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. | Examiner |
| US5880677(A) | 1999-03-01 | Lestician | Applicant |
| US5883886(A) | 1999-03-01 | Eaton et al. | Examiner |
| 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. | Applicant |
| 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. | Applicant |
| US5907540(A) | 1999-05-01 | Hayashi | Applicant |
| US5907807(A) | 1999-05-01 | Chavez, Jr. et al. | Applicant |
| 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. | Examiner |
| 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 | Roswell 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. | Applicant |
| 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. | Applicant |
| US6060994(A) | 2000-05-01 | Chen | Applicant |
| US6061604(A) | 2000-05-01 | Russ et al. | Applicant |
| US6064318(A) | 2000-05-01 | Kirchner, III et al. | Applicant |
| 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 |
| US6108614(A) | 2000-08-01 | Lincoln et al. | Examiner |
| 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. | Applicant |
| 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. | Applicant |
| 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. | Applicant |
| US6215404(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. | Applicant |
| 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 | Olivia | 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 | Carsais | Applicant |
| US6295291(B1) | 2001-09-01 | Larkins | Applicant |
| US6301514(B1) | 2001-10-01 | Canada et al. | Applicant |
| 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 | Applicant |
| 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 |
| US7227927(B1) | 2007-06-01 | Benedyk et al. | Examiner |
| 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 et al. | 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 | 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 |
| US2006/0098576(A1) | 2006-05-01 | Brownrigg et al. | Applicant |
| US2008/0186898(A1) | 2008-07-01 | Petite | Applicant |
| US2009/0006617(A1) | 2009-01-01 | Petite | Applicant |
| US2009/0068947(A1) | 2009-12-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 | |
| WO90/13197 | 1990-11-01 | Applicant | |
| WO9524177 | 1995-09-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 | |
| WO23956 | 2000-04-01 | Applicant | |
| WO/36812(A1) | 2000-06-01 | Applicant | |
| WO1/15114 | 2001-03-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 | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/021877 | 2003-03-01 | Applicant | |
| WO4/002014 | 2003-12-01 | Applicant |
Non-Patent Literature (45)
- 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/Ic/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
- 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.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,”, 1987.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
- 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. Johnson 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
- 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 Engineering 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
- USPTO'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