US 8,031,650 B2Grant
System and method for monitoring remote devices with a dual-mode wireless communication protocol
Issue Date:2011-10-04
•16 Claims
•9 Drawing Sheets
Abstract
The present invention is generally directed to systems and device for monitoring remote device with a wireless, dual-mode communication protocol. As such, a representative embodiment is a system for monitoring and controlling remote devices. The system includes a first- and a second remote device; and a first and a second wireless transceiver integrated with the respective remote devices. The wireless transceivers are configured to communicate with at least one of a spread-spectrum communication protocol and a fixed-frequency communication protocol.
Metadata
Assignee
- Sipco, LLC
Inventors
- Thomas D. Petite
- Richard Huff
- David P. Aldoretta
- Candida Stevens
Application Information
Application Number:US 10/792,608
Filing Date:2004-03-03
Priority Date:2004-03-03
Art Unit:2617
Classifications
IPC:
H04B7/216H04B7/204H04W4/00G08B23/00G08C15/06
Patent Drawings (9 sheets)
Description
Background Section
[0001] Prior art monitoring and controlling systems for various applications, such as automated meter reading, prognostics, vending machines, and fire alarm and sprinkler systems utilize various communication protocols. Generally, these protocols utilize wireless RF communications either between transceivers or between a plurality of transceivers and a remote interrogator. The remote interrogator may then be coupled to a wide area network (WAN) which enables access to the transceivers by backend servers, workstations, etc.
[0002] In some instances, the RF transceivers may utilize a single-channel, substantially low-power communications protocol and, thus, have a limited range. The low-power applications are advantageous in certain remote applications, where a constant power supply is not available. For example, a transceiver coupled to a water meter cannot tap into any local power at the water meter, because typically there is no power. In this case, a battery is typically used. In order to maximize the life span of the battery, low-power transmissions are used. Low-power transmissions may also be advantageous because at certain frequency bands, a license from the Federal Communication Commission (FCC) is not required. The FCC requires certain devices to be licensed and/or comply with certain provisions if the devices radiate enough power within a given frequency spectrum over a given period.
[0003] Unfortunately, there are drawbacks to a low-power, single-channel communication protocol. In particular, the range of communication is directly proportional to the level of radiated power. Therefore, low power implies shorter communication range. Shorter communication range generally requires more infra-structure in a wireless system. Furthermore, single-channel communications (e.g., communications within one frequency channel, or on one carrier frequency) can be a problem if there is other electromagnetic radiation in a given area. Interference from other devices may cause noise at or near the specific single channel in which the RF transceivers are attempting to communicate, thus making communication unreliable, if not unfeasible.
[0004] Considering these drawbacks, it would be desirable to have a communication protocol that overcomes the disadvantages illustrated above. Furthermore, it would be advantageous for a systems provider for the communication devices (i.e., the RF transceivers and gateways) to be compatible with both communications protocols so that a communication upgrade would not require existing devices to be replaced. Instead the existing devices could be upgraded remotely through the system.
Summary
[0005] Various embodiments of a dual-mode communication protocol, and corresponding systems, devices, methods, and computer programs, are provided. One embodiment is a system for monitoring and controlling remote devices. The system includes a first and a second remote device; and a first and a second wireless transceiver integrated with said respective remote devices. The wireless transceivers are configured to communicate with at least one of a spread-spectrum communication protocol and a fixed-frequency communication protocol.
[0006] Another embodiment is a system for monitoring the utility consumption measured by a plurality of utility meters. The system includes a plurality of utility meters and a network of wireless RF transceivers for communicating utility consumption data. The network of wireless RF transceivers is comprised of at least a first dual-mode transceiver, at least a first fixed-frequency transceiver, and at least a first spread-spectrum transceiver. The system further includes at least a first gateway in communication with each wireless RF transceiver either directly or via other wireless RF transceivers. The at least first gateway relays data from the network of wireless RF transceivers to a back-end system.
[0007] Yet another embodiment is a wireless transceiver used within a system for monitoring remote devices. The wireless transceiver includes an RF transceiver for communicating in at least one of a spread-spectrum communication protocol and a fixed-frequency communication protocol and a data controller coupled to the RF transceiver for processing data to be either transmitted by or received from the RF transceiver. The wireless transceiver also includes memory for storing various logic to be performed by the data controller and the RF transceiver for communicating in at least one of the communication protocols.
Brief Description of the Drawings
[0008] The accompanying drawings incorporated in and forming a part of the specification, illustrate several aspects of the present invention, and together with the description serve to explain the principles of the invention.
[0009] FIG. 1 is a block diagram illustrating an embodiment of a dual-mode monitoring/control system.
[0010] FIG. 2 is a block diagram illustrating the functional components of an embodiment of a dual-mode transceiver of the system of FIG. 1 .
[0011] FIG. 3 is an illustration of an exemplary frequency band implemented in the system of FIG. 1 .
[0012] FIG. 4A is a data structure illustrating an embodiment of a fixed-frequency communication packet for the system of FIG. 1 .
[0013] FIG. 4B is a data structure illustrating an embodiment of a spread-spectrum communication packet for the system of FIG. 1 .
[0014] FIG. 5 is a flow chart illustrating an embodiment of a method for transmitting in a dual-mode communication protocol.
[0015] FIG. 6 is a flow chart illustrating an embodiment of a method for transmitting in a spread-spectrum communication protocol.
[0016] FIG. 7 is a flow chart illustrating an embodiment of a method for receiving in the dual-mode communication protocol.
[0017] FIG. 8 is a flow chart illustrating an embodiment of a method for receiving in the spread-spectrum communication protocol.
Detailed Description
[0018] Embodiments illustrated in further detail below illustrate various systems, methods, devices, and programs for communicating in a dual-mode communication protocol. A first communication protocol may generally be considered a fixed-frequency communication protocol and a second communication protocol may generally be considered a spread-spectrum communication protocol.
[0019] An embodiment of a transceiver communicating in a fixed-frequency communication protocol is generally configured to communicate a communication packet at a single frequency channel, with a first modulation scheme, at a given radiating power level.
[0020] An embodiment of a transceiver communicating in a spread-spectrum communication protocol is generally configured to communicate a first portion of a communication packet at a first frequency channel, and then communicate a second portion of the communication packet at a second frequency channel. The spread-spectrum communication protocol may employ a second modulation scheme, at a given radiating power level.
[0021] An embodiment of a transceiver communicating in the dual-mode communication protocol can generally communicate in both communication protocols. By providing for both communication protocols, the disadvantages of utilizing one singular protocol may be avoided. The accompanied figures and description illustrate embodiments of the dual-mode communication protocol in further detail.
[0022] Turning now to FIG. 1 , illustrated is a block diagram of an embodiment of a dual-mode monitoring/control system 1. Dual-mode system 1 comprises one or more external devices to be monitored and/or controlled (e.g., sensor/actuators 10) as illustrated in FIG. 1 . Each sensor/actuator may be integrated with a transceiver 30, 31, or 32. The transceivers 30-32 are preferably RF (radio frequency) transceivers that are relatively small in size. Depending on the communication mode utilized, the transceivers 30-32 transmit either a relatively low-power RF signal, or a higher-power RF signal. As a result, in some applications, the transmission range of a given transceiver may be relatively limited. Although the transceivers 30-32 are depicted without a user interface such as a keypad, in certain embodiments, the transceivers 30-32 may be configured with user selectable buttons or an alphanumeric keypad. The transceivers 30-32 may be electrically interfaced with the device to be monitored and/or controlled, such as a smoke detector, a thermostat, a security system, etc., where external buttons are not needed.
[0023] Dual-mode system 1 also includes a plurality of stand-alone transceivers 33-35, which may be fixed or mobile. Each stand-alone transceiver 33-35 and each of the integrated transceivers 30-32 may be configured to receive an incoming RF transmission (transmitted by a remote transceiver) and to transmit an outgoing signal. The transceivers depicted in FIG. 1 may include different functionality depending on whether the transceiver communicates in a fixed-frequency communication mode, a spread-spectrum communication mode, or both. These communication modes, or protocols, will be discussed in further detail in subsequent figures. All transceivers may include the hardware and/or software to communicate in either of the protocols, but may be programmed or configured to communicate in only one or the other, or both,
[0024] Fixed-frequency transceiver 30 is an integrated transceiver that is configured to communicate only with the fixed-frequency communication protocol. In general, the fixed-frequency communication protocol is any protocol in which a packet or frame of data is communicated within a single frequency channel. Transceiver 35 is the stand-alone counterpart to transceiver 30. A fixed-frequency communication link is illustrated in FIG. 1 with a thin communication bolt designated with numeral 40.
[0025] Spread-spectrum transceiver 31 is an integrated transceiver that is configured to communicate only with the spread-spectrum communication protocol. The spread-spectrum communication protocol will be discussed in further detail, but in short, is a protocol that facilitates frequency-channel hopping within a given frequency band. Transceiver 34 is the stand-alone counterpart to transceiver 31. A spread-spectrum communication link is denoted in FIG. 1 with a wide communication bolt and given numeral 45.
[0026] Dual-mode transceiver 32 is an integrated transceiver that is configured to communicate with either of the two aforementioned protocols. Transceiver 33 is the stand-alone counterpart to the dual-mode transceiver 32.
[0027] Notably, each transceiver can communicate only with another transceiver configured for similar protocols. In other words, a fixed-frequency transceiver 30, 35 cannot communicate with a spread-spectrum transceiver 31, 34. This, however, can be reasonably obviated by deploying dual-mode transceivers 32, 33 into the wireless infrastructure.
[0028] The specifics of a fixed-frequency communication 40 will be discussed in further detail in FIG. 4A and the specifics of a spread-spectrum communication 45 will be discussed in further detail in FIG. 4B . Both communications, however, are preferably wireless, RF transmissions, and more preferably, in the 902-928 MHz frequency range. Although this is preferable, in other embodiments, alternative frequency ranges may be employed. Furthermore, each communication may be transmitted over a conductive wire, fiber optic cable, or other transmission media.
[0029] The internal architecture of a transceiver 30-32 integrated with a sensor/actuator 10 and a stand-alone transceiver 33-35 will be discussed in more detail in connection with FIG. 2 . It will be appreciated by those skilled in the art that integrated transceivers 30-32 can be replaced by RF transmitters (not shown) for client specific applications that only require data collection only.
[0030] Local gateways 15 are configured and disposed to receive remote data transmissions from the various stand-alone transceivers 33-35 or integrated transceivers 30-32 having an RF signal output level sufficient to adequately transmit a formatted data signal to the gateways. Local gateways 15 can communicate in either of the two aforementioned communication protocols. Thus, for the purpose of this document, they will be considered dual-mode gateways 15. In other embodiments, local gateways 15 may be capable of communicating in only one of the aforementioned protocols.
[0031] Local gateways 15 analyze the transmissions received, convert the transmissions into TCP/IP format (or other protocol), and further communicate the remote data signal transmissions to back-end system 21 via WAN 20. In this regard, and as will be further described below, local gateways 15 may communicate information, service requests, control signals, etc., to integrated transceivers 30-32 from server 25, laptop computer 28, and workstation 27 across WAN 20. Server 25 can be further networked with database server 26 to record client specific data. Server 25, laptop computer 28, and workstation 27 are capable of remotely controlling and/or configuring various functions of the transceivers. For instance, server 26 is capable of remotely controlling the communication protocol in which each transceiver can communicate. This can be accomplished by sending a downstream control signal and/or by sending a software/firmware upgrade downstream.
[0032] It will be appreciated by those skilled in the art that if an integrated transceiver (either of 30-32) is located sufficiently close to dual-mode local gateways 15 to receive RF data signals, the RF data signal need not be processed and repeated through stand-alone transceivers 33-35. It will be further appreciated that the system 1 may be used in a variety of environments. In one embodiment, system 1 may be employed to monitor and record utility usage of residential and industrial customers. In another embodiment, system 1 may be configured for the transfer of vehicle diagnostics from an automobile via an 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.
[0033] Generally, transceivers 30-32 may have similar construction (particularly with regard to their internal electronics) where appropriate, which provides a cost-effective implementation at the system level. Alternatively, fixed-frequency transceiver 30 may include some different internal electronics then spread-spectrum transceiver 31. Furthermore, dual-mode transceiver 32 may include different internal electronics as transceivers 30 and 31. Stand-alone transceivers 33-35 may include similar communication components as their integrated counterparts. The necessary hardware and software to integrate with a sensor/actuator 10 may, however, be excluded.
[0034] As illustrated in FIG. 1 , stand-alone transceivers 33-35 are disposed to provide adequate coverage in a desired geographic area (e.g., an industrial plant or community), which is based on the particular system application. Preferably, stand-alone transceivers 33-35 may be dispersed so that at least one stand-alone transceiver will pick up a transmission from a given integrated transceiver 30-32. However, in certain instances, two or more stand-alone transceivers may pick up a single transmission. Thus, local gateways 15 may receive multiple versions of the same data transmission signal from an integrated transceiver, but from different stand-alone transceivers. Local gateways 15 may utilize this information to triangulate, or otherwise more particularly assess the location from which the transmission is originating. Due to the transmitting device identification that is incorporated into the transmitted signal, duplicative transmissions (e.g., transmissions duplicated to more than one gateway, or to the same gateway, more than once) may be ignored or otherwise appropriately handled.
[0035] Integrated transceivers 30-32 may be implemented in a variety of devices. For example, integrated transceivers 30-32 may be disposed within automobiles, a rainfall gauge, a parking lot access gate, and utility meters to monitor vehicle diagnostics, total rainfall and sprinkler supplied water, access gate position, and utility consumption, to name a few. The advantage of integrating a transceiver, as opposed to a one-way transmitter, into a monitoring device relates to the ability of the transceiver to receive incoming control signals, as opposed to merely transmitting data signals. Significantly, local gateways 15 may communicate with all system transceivers. Since local gateways 15 are integrated with WAN 20, server 25 can host application specific software that is typically hosted in an application specific local controller. Of further significance, the data monitoring and control devices need not be disposed in a permanent location. Provided the monitoring and control devices remain within signal range of a system compatible transceiver, which is within signal range of local gateway 15 interconnected through one or more transceiver networks to server 25. In this regard, small application specific transmitters compatible with system 1 can be worn or carried about one's person or coupled to an asset to be tracked and monitored.
[0036] In one embodiment, server 25 collects, formats, and stores client specific data from each of the integrated transceivers 30-32 for later retrieval or access from workstation 27 or laptop 28. In this regard, workstation 27 or laptop 28 can be used to access the stored information through a Web browser in a manner that is well known in the art. In another embodiment, server 25 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 WAN 20 and local gateways 15 to the system sensors/actuators. In a third embodiment, clients may elect for proprietary reasons to host control applications on their own WAN connected workstation. In this regard, database 26 and server 25 may act solely as a data collection and reporting device with client workstation 27 generating control signals for the system 1.
[0037] It will be appreciated by those skilled in the art that the information communicated by the transceivers 30-35 may be further integrated with other data transmission protocols for transmission across telecommunications and computer networks other than the Internet. In addition, it should be further appreciated that telecommunications and computer networks other than the Internet can function as a transmission path between the transceivers, the local gateways, and the central server. For example, an integrated transceiver may communicate with a stand-alone transceiver in a RF communication scheme. The stand-alone transceiver may communicate with the gateway 15 in a cellular communication scheme, such as GSM or PCS. The gateway 15 may communicate with the back-end system 21 via satellite, POTS, or the Internet.
[0038] Reference is now made to FIG. 2 , which is a block diagram that illustrates functional components of an embodiment of a dual-mode transceiver 32, 33. Dual-mode transceiver 32, 33 may communicate with another transceiver 30, 32, 33, and 35 or gateway 15 with the fixed-frequency communication protocol, or may communicate with another transceiver 31-34 or gateway 15 with the spread-spectrum communication protocol.
[0039] The integrated dual-mode transceiver 32 is coupled to external devices 10, for example, sensor 11 and actuator 12, by way of data interface 70. Data interface 70 is configured to receive electrical signals from sensor 11 and provide electrical signals to actuator 12, and ultimately convey such information to and from a data controller 50. In one embodiment, data interface 70 may simply comprise an addressable port that may be read by the data controller 50. Dual-mode transceiver 33 is a stand-alone transceiver, thus may not include the data interface 70 for coupling to external components 10, such as sensor 11 and actuator 12.
[0040] Data controller 50 is coupled to memory 100 which stores various software, firmware, and other logic. Further coupled with data controller 50 is an RF transceiver 80 which is used to convert information received from data controller 50 in digital electronic form into a format, frequency, and voltage level suitable for transmission from antenna 60 via an RF transmission medium. RF transceiver 80 also converts a received electromagnetic signal from antenna 60 into digital electronic form for data controller 50 to process.
[0041] Data controller 50 may be considered a micro-controller or micro-processor and, as such, is configured for performing the data processing for the transceiver 32, 33. Data controller 50 is configured to perform operations as directed by firmware 102 stored in memory 100. These operations include data formatting for communication in both modes of communication, as well as data formatting for communication with sensor 11 and actuator 12 (if so equipped).
[0042] RF transceiver 80 of dual-mode transceiver 32, 33 may include distinct chipsets for each communication protocol: a fixed-frequency communication protocol chipset (FF chipset) 81 and a spread-spectrum communication protocol chipset (SS chipset 82). Chipsets 81 and 82 include the necessary components for transmitting and receiving in the particular communication protocols. For example, FF chipset 81 includes the components for communicating in a first modulation scheme, at a given power level, and in a particular frequency band in accordance with the fixed-frequency communication protocol. SS chipset 82 includes the components for communicating in a second modulation scheme, at a given power level, and in another particular frequency band in accordance with the spread-spectrum communication protocol. In other embodiments, the chipsets may be fully integrated.
[0043] Fixed-frequency transceivers 30 and 35 may differ from dual-mode transceivers 32 and 33 because they may not include SS chipset 82. Alternatively, data controller 50 for fixed-frequency transceivers 30 and 35 may not be programmed, by firmware 102, for communicating in the spread-spectrum communication protocol. As will be discussed shortly, certain modules of memory 100 which are included in dual-mode transceivers 32 and 35 may not be included in fixed-frequency transceivers 30 and 35.
[0044] Likewise, spread-spectrum transceivers 31 and 34 may differ from dual-mode transceivers 32 and 33 because they may not include FF chipset 81. Alternatively, data controller 50 for the spread-spectrum transceivers 31 and 34 may not be programmed, by firmware 102, to communicate in the fixed-frequency communication protocol.
[0045] Memory 100 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory 100 may incorporate electronic, magnetic, optical, and/or other types of storage media. Memory 100 can have a distributed architecture, where various components are situated remote from one another, but can be accessed by the data controller 50. Modules included in the memory 100 of a dual-mode transceiver 32 and 33 are a data channel index table 103, an acquisition channels table 105, a fixed-frequency channels table 106, a receiver (Rx) address table 104, firmware 102, RAM 101, and a transceiver identification (Tx ID) 107.
[0046] The data channel index table 103 is utilized for communication in the spread-spectrum communication protocol. The contents of the data channel index table 103 will become clearer as the spread-spectrum communication protocol is laid out in subsequent figures. In short, the data channel index table 103 includes a list of data channel frequencies in which a data portion of a communication packet may be communicated. Each data channel is given an index that RF transceiver 80 will recognize, and furthermore can be communicated in a preamble of a communication packet. A receiving transceiver 31-34 or gateway 15 will need to recover the data channel index from the preamble to properly receive the remainder of a communication packet. In the preferred embodiment, there are 40 frequency channels dedicated for data communication each channel designated by a unique data channel index. One will appreciate that the number of channels is not relevant. Accordingly, in other embodiments, the number of channels may vary.
[0047] The acquisition channels table 105 is utilized for communication in the spread-spectrum communication protocol. The acquisition channels table 105 includes a list of frequency channels designated for synchronizing communication with another transceiver and for communicating a preamble of a communication packet. In the preferred embodiment there are ten designated acquisition channels, although this number can vary. An understanding of the acquisition channels table 105 will become clearer upon further explanation of the spread-spectrum communication protocol.
[0048] The fixed-frequency channels table 106 is utilized for communication in the fixed-frequency communication protocol. The fixed-frequency channels table 106 includes a list of frequency channels designated for synchronizing communication and subsequently communicating the data portion of a communication packet. In the preferred embodiment, there are eight fixed-frequency channels. An understanding of the fixed-frequency channels table 106 and its associated fixed-frequency channels will become clearer upon further explanation of the dual-mode communication protocol.
[0049] Each transceiver is configured to have a unique identification code 107 (e.g., transceiver identification number—Tx ID), that uniquely identifies the transceiver to the functional blocks of control system 1 (see FIG. 1 ). This transceiver identification number 107 may be electrically programmable, and implemented in the form of, for example, an EPROM. Alternatively, the transceiver identification number 107 may be set/configured through a series of DIP switches, or stored in RAM. Alternative methods of setting and configuring the transceiver identification number 107 may be implemented.
[0050] Rx address table 104 is generally a look-up table of transceiver identification numbers (Tx IDs), or addresses, of other transceivers in a given network in the system 1 and is called upon when preparing a communication packet to be transmitted. Each communication packet transmitted by any transceiver 30-35, or gateway 15, is destined for a particular transceiver as designated by the transceiver identification number 107 embedded within the communication packet for either communication protocol (to be illustrated in FIG. 4 ). As a transceiver receives various packets, it can distinguish, by the transceiver identification number embedded in the communication packet, whether that packet is destined for that transceiver. Otherwise, the transceiver may disregard the packet and/or relay the packet along to another transceiver. The specifics of how a communication packet is processed upon reception, including relaying the packet, is generally beyond the scope of the present invention.
[0051] The Rx address table 104 may also include more information about other transceivers, such as the communication protocol with which the other transceivers communicate. Furthermore, the desired modulation scheme(s) with which the other transceivers communicate as well as a necessary radiating-power level. Importantly some or all of the contents of the Rx address table 104 can be updated remotely, for instance, by server 26.
[0052] Firmware 102 includes the logic for operating data controller 50 in accordance with embodiments of the present invention. Logic configured to perform operations as laid out in flow charts illustrated in subsequent figures is found in firmware 102, along with programming logic for communicating with data interface 70 and its coupled components 10. Other programming logic may be incorporated in the firmware 102 as known by those of ordinary skill in the art, such as power conservation sequences, power-up and power-down sequences, and operating system upgrade sequences.
[0053] Sensor 11, in its simplest form, could be a two-state device such as a smoke alarm. Alternatively, the sensor 11 may output a continuous range of values to the data interface 70. If the signal output from the sensor 11 is an analog signal, the data interface 70 may include an analog-to-digital converter (not shown) to convert signals output to the actuator 12. Alternatively, a digital interface (communicating digital signals) may exist between the data interface 70 and each sensor 11. In FIG. 2 , data interface 70 is shown with a single input from sensor 11. It is easy to envision a system that may include multiple sensor inputs. By way of example, a common home heating and cooling system might be integrated with 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), as well as, a sensor integrated with a thermostat to report an ambient temperature. The condition of related parameters can be input to data interface 70 as well, including the condition of the system on/off switch, and 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 70 as well.
[0054] The integration with an actuator 12 permits data interface 70 to apply control signals to a manual temperature control for the temperature set point, a climate control mode switch, and a system on/off switch. In this way, a remote workstation 27 or laptop 28 with WAN access (see FIG. 1 ) could control a home heating system from a remote location.
[0055] The operation of an embodiment of transceiver 32, 33 is best illustrated in the flow charts of FIGS. 5-8 . However, a brief explanation of the operation should be made with reference to the particular components illustrated in the block diagram of FIG. 2 . The dual-mode transceiver 32, 33, as its name implies, can communicate in any one of two modes or protocols: the fixed-frequency communication protocol and the spread-spectrum communication protocol.
[0056] When transmitting in the fixed-frequency communication protocol, data controller 50 will build a fixed-frequency communication packet (described in FIG. 4A ) and pass that along to the RF transceiver 80 for communication. A communication packet is transmitted in the fixed-frequency communication protocol by transmitting at a dedicated channel, where the dedicated channel is one of the fixed-frequency channels (as illustrated in FIG. 3 ). Preferably, the dedicated channel for transmission is the center channel of the fixed-frequency band, which, in the case of FIG. 3 , is the 916.5 MHz channel. Alternatively, building the fixed-frequency communication packet may involve querying the fixed-frequency channels table 106 to find the next fixed-frequency channel in which to communicate. The selected frequency channel is communicated to the FF chipset 81 along with the communication packet. In another alternative, the FF chipset 81 may be configured to cycle through the designated fixed-frequency channels without having to receive an index or pointer to a channel from the memory 100. In this alternative embodiment, the fixed-frequency channel table 106 may be excluded from the memory 100 and stored in memory integrated in with the FF chipset 81. The payload portion of the communication packet is populated with the relevant information to be communicated, which may include information received from the data interface 70. The data controller 50 may query the Rx address table 104 to make sure the destined transceiver can communicate in the fixed-frequency communication mode. After the packet is assembled it is passed along to the transceiver 80 for transmission.
[0057] FF chipset may receive in the fixed-frequency communication mode by cycling through the fixed-frequency channels to look for a carrier signal. Once found and synchronized, the packet communicated at that carrier channel is received and passed along to the data controller 50 for processing. Processing of the data may include preparing a reply signal, updating information in memory 100, and/or controlling actuator 12 or other external component 10.
[0058] When transmitting in the spread-spectrum communication protocol, the data controller 50 will build a spread-spectrum communication packet (as illustrated in FIG. 4B ). The spread-spectrum communication protocol is built by querying the acquisition channels table 105 to find the next acquisition channel in which to send a preamble of the communication packet. Alternatively, the SS chipset 82 may be configured to cycle through the designated acquisition channels without having to receive an index or pointer to a channel from the memory 100. In this alternative embodiment, the acquisition channel table 105 may be excluded from the memory 100 and stored instead in memory integrated with the SS chipset 82. The preamble of the communication packet may also be prepared by querying the data channel index table 103 to find which data channel to communicate the payload portion of the packet. The index to the designated data channel is populated within the preamble. The payload portion of the communication packet is populated and formatted in a similar manner as the fixed-frequency communication protocol calls for. The communication packet is then passed along to RF transceiver 80 for transmission.
[0059] SS chipset 82 prepares the preamble of the communication packet for transmission at the designated acquisition channel frequency. Upon completing transmission of the preamble, SS chipset 82 then transmits the remainder of the communication packet at the frequency designated by the data channel index. Typically, this requires SS chipset 82 to change frequency channels mid-communication packet. In some special cases, however, the designated data-channel may be the same as the acquisition channel, which is essentially equivalent to the fixed-frequency communication protocol.
[0060] Importantly, communicating with the two communication protocols also provides the opportunity to communicate in two different modulation schemes. This is beneficial because the drawbacks of each can be countered with the advantages of the other. In one embodiment, the fixed-frequency communication protocol uses an amplitude modulation scheme, such as on-off keying (OOK). The spread-spread communication protocol uses a frequency modulation scheme, such as frequency shift-keying (FSK). These are merely exemplary modulation schemes that can be utilized. Those of skill in the art will appreciate that various modulation schemes may be utilized. Furthermore, in some embodiments, the two communication protocols may utilize the same modulation scheme. The particular modulation scheme used for each communication protocol by each transceiver can be remotely controlled by devices in the back-end system 21. Control commands can be received downstream to change the particular modulation scheme to be utilized.
[0061] FIG. 3 is an illustration of an embodiment of a preferred frequency band 200 at which the dual-mode transceivers communicate. The illustrated frequency band 200 is the 902-928 MHz band, which falls in the ultra high-frequency (UHF) radio band. Other frequency bands may be utilized. The 902-928 MHz band may be advantageous in certain situations because communication ion this band may not require licensing by the FCC, provided signal radiations remain below a given power threshold.
[0062] In the embodiment illustrated in FIG. 3 , the 902-928 MHz frequency band is divided into a first set of channels designated as spread-spectrum communication channels and a second set of channels designated as fixed-frequency communication channels. The spread-spectrum communication channels are further divided into subsets of acquisition channels 220 and data channels 210. In the embodiment illustrated in FIG. 3 , there are fifty spread-spectrum communication channels, of which ten are designated as acquisition channels 220 and forty are designated as data channels 210. Each channel comprises 500 kHz, with the carrier frequency being centered within the 500 kHz.
[0063] In other embodiments, the number of spread-spectrum communication channels, as well as the number of acquisition channels 220 and data channels 210 may be different. Furthermore, in some embodiments, the acquisition channels 220 and data channels 210 may overlap. In order to comply with certain provisions of Part 15 of the FCC's Guidelines for Operation (which is hereby incorporated by reference in its entirety), fifty channels are necessary for spread-spectrum communication. Embodiments of the present invention comply with the FCC's guidelines for communicating at a higher power level. By communicating at a higher power level, longer range communications and/or greater signal penetrations are possible, which is very advantageous for many applications in which system 1 may be utilized.
[0064] In one embodiment, the acquisition channels 220 are separated from each other by four data channels 210, thus providing 2 MHz of bandwidth between acquisition channels 220. The acquisition channels 220 are spread evenly across the entire frequency band 200 to spread the power spectral density across the entire frequency band. Again, this pattern can vary greatly, and should not be limited the embodiments illustrated in FIG. 3 . For example, the acquisition channels 220 can be grouped together at various sections of the frequency band 200. One must consider, however, complying with the FCC's guidelines when designating the acquisition channels. The acquisition channels 220 may be evenly utilized because each transceiver is configured to cycle through the acquisition channels 220, upon transmission, in either a predetermined and/or pseudorandom pattern. The data channels 210 may also be evenly utilized because each transceiver is configured to cycle through the data channels 210 upon transmission in either a predetermined and/or pseudorandom pattern.
[0065] The current FCC guidelines require even usage of channels across an entire bandwidth. In one embodiment, it would appear that the acquisition channels 220 would get 4× more usage then the data channels 210. This may be accounted for, however, by limiting the data throughput at each acquisition channel 220. The total number of data bits communicated in the acquisition channels 220 is about equal to or less than the total number of data bits communicated across the many data channels 210.
[0066] Spread-spectrum communication may also be advantageous because it provides for communication from more devices using a given frequency band and greatly reduces the effects of interference. If one channel is currently in use or has some external interference, the transceivers can simply switch to another frequency channel. In one embodiment, the transmitter dictates what the next frequency channel will be by communicating the data channel index in the preamble of a communication packet. Frequency hopping is often used in spread-spectrum communication, which, as its name implies, is generally the process of changing frequency channels in which a transceiver communicates during operation.
[0067] As briefly discussed above with respect to FIG. 2 , several embodiments of the spread-spectrum communication protocol work by communicating a preamble portion of a communication packet in one of the designated acquisition channels 220. A receiver can cycle through the designated acquisition channels 220 and lock onto a carrier signal at the acquisition channel 220 in which a transmitter is communicating. The receiver then receives the remainder of the preamble, which includes a data channel index field. The receiver then switches to the data channel 210 as designated by the data channel index and prepares to receive the remainder (the data portion) of the communication packet. This will be discussed in further detail in subsequent figures.
[0068] The fixed-frequency communication protocol is designated to communicate within another frequency band. In the embodiment illustrated in FIG. 3 , the fixed-frequency channel band 230 is confined within one of the channels designated for the spread-spectrum communication protocol. For example, as FIG. 3 illustrates, the fixed-frequency channel band 230 is allotted the 916.3-916.7 MHz frequency band which is slightly smaller then one of the spread-spectrum communication channels of 500 kHz. It should be noted that the frequency band selected for the fixed-frequency communication protocol is merely a preferred frequency band and other frequency bands, including those outside the band dedicated for spread-spectrum communication, could be utilized. Importantly, other components of the dual-mode transceivers are a function of the selected frequency band. For example, antenna 60 may be a dual-frequency antenna for operating in two different frequency bands.
[0069] In one embodiment, eight channels 235 (each 50 kHz) are dedicated for fixed-frequency communication with the carrier frequency being centered in each channel 235. Of course, the number of fixed-frequency channels 235 and the allotted bandwidth for each channel 235 can vary.
[0070] Important to note is the relatively narrow bandwidth provided for the fixed-frequency channels 235. This is because the illustrated embodiment of the fixed-frequency communication protocol calls for lower power communication and also amplitude modulation. First, with lower power communications, the power spectral density at each carrier frequency is much more focussed at the carrier frequency than higher power communications. Thus, with higher-power communications, more bandwidth is required to allow sufficient separation between the also-wider frequency responses. Second, amplitude modulation, such as OOK, does not require deviation from the carrier frequency, as only the amplitude of the carrier frequency (or a nearby secondary frequency) is being modulated.
[0071] A receiving device operating within the fixed-frequency communication protocol, will search for a carrier frequency by cycling through the fixed-frequency channels 235 searching for a carrier frequency. Once locked on to a carrier frequency, the receiver will begin receiving the preamble and also the data portion of a communication packet. Unlike in the spread-spectrum communication protocol, the receiver will not be required to switch to another channel to receive the data portion of the communication packet.
[0072] FIG. 4A illustrates an embodiment of a fixed-frequency communication packet, or frame, 300 and FIG. 4B illustrates an embodiment of a spread-spectrum communication packet 400. Both embodiments preferably implement the Manchester encoding scheme. Nonetheless, one of ordinary skill in the art will appreciate that other embodiments may employ other encoding schemes. The Manchester encoding scheme is a bit-level encoding scheme well known in the art for its reliability and ease of timing synchronization. The Manchester encoding scheme translates a binary 1 data bit into a low-to-high transition, at the physical layer level. A binary 0 data bit is thus a high-to-low transition, at the physical layer level. Thus, for each data bit to be transmitted, a full data cycle is required with a 50% duty cycle. Although this cuts the data throughput in half, timing and synchronization is easily accomplished because synchronization can be done at each clock cycle.
[0073] Referring to FIG. 4A , the fixed-frequency communication packet 300 includes a preamble portion 301 and a data portion 302, both of which are communicated while at the same frequency channel. The preamble portion 301 includes a training sequence 310, which is composed of a predefined sequence of bits. In one embodiment, the sequence 310 is a series of binary 1s. The length of sequence 310 should be suitable for a receiver to cycle through the designated fixed-frequency channels 235 and look for the sequence. The receiver is configured to look for a subset, such as six or eight consecutive binary 1s. If the receiver receives this subset, the receiver remains at the current fixed-frequency channel 235. Otherwise, the receiver will move on to the next channel. In one embodiment, the training sequence 310 is 24 bits in length. Furthermore, the training sequence 310 could be another sequence besides consecutive binary 1s. Consecutive binary 0s or alternating binary 1s or 0s could be utilized.
[0074] As discussed earlier, the Manchester encoding scheme makes timing and synchronization relatively easy. A string of consecutive binary 1s appears to a receiver to be a square wave with a 50% duty cycle (as would a string of consecutive 0s, 180 degrees out of phase). If a receiver receives this square wave for a predefined period (equivalent to the prescribed period of time for the synchronization subset), the receiver will recognize that this data is the start of a communication packet, and timing and synchronization can then be performed with a standard phase lock loop.
[0075] As illustrated in FIG. 4A , a start marker 320 is composed of two bits and used to signify the end of the training sequence 310 and the start of the data portion 302 of the communication packet 300. The start marker 320 breaks away from the standard Manchester encoding scheme and is made up of two full clock cycles (thus two bits) of an all high (or on, for OOK) signal. Certainly, other configurations could be utilized.
[0076] The data portion 302 of the fixed-frequency communication packet 300 is composed of a variable length payload 330. In one embodiment, the variable length payload 330 is similar to the variable length payload 430 of the spread-spectrum communication packet 400 of FIG. 4B and will be discussed in further detail below.
[0077] Turning now to FIG. 4B , the spread-spectrum communication packet 400 is made up of a preamble portion 401 and a data portion 402. In one embodiment, the preamble portion 401 of the spread-spectrum communication packet 400 is communicated at one of the acquisition channels 220 (See FIG. 3 ). The preamble portion 401 includes a training sequence 410 similar to training sequence 310 and also a data channel index field 415. In the one embodiment, the training sequence 410 is composed of 48 bits, but this may greatly vary in other embodiments. The length of the training sequence 410 should be suitable for a receiver to cycle through all of the acquisition channels 220.
[0078] The preamble 401 also includes a data channel index field 415, which communicates to a receiver the data channel at which the data portion 402 of the communication packet 400 will be communicated. In one embodiment, the data channel index field 415 is composed of eight bits. The two most significant bits 415 are binary 0s and the remaining six bits are used to communicate the data channel. The data channel index field 415 also serves to notify a receiver that the communication packet is a spread-spectrum communication packet and not a fixed-frequency communication packet.
[0079] A start marker 420 similar to start marker 320 is then included in the communication packet 400. In the embodiment of FIG. 4B , the start marker 420 is composed of four bits and used to signify the end of the preamble 401.
[0080] The data portion 402 of the communication packet 400 is composed of a variable length payload 430. Briefly, the variable length payload 430 may include fields, such as a start-of-packet, or header, 431, receiver (Rx) address 432, and transmitter (Tx) address 433. A checksum, cyclic-redundancy check (CRC) 434 or other equivalent error detection scheme could be included in the variable length payload 430. Next, the actual data is transmitted in a variable length payload 435 followed by a footer 436. In one embodiment, the variable length payload 430 can vary from 112 to 1024 bits. The upper limit is defined by the data rate and a maximum dwell time at a particular channel. These parameters may be different in other embodiments, thus varying the length of the data portions of the communication packets. However, the length of the total communication packet should provide for continuous communication at a particular channel, at a given data rate, that is less then the maximum dwell time allotted by the FCC's guidelines. In one embodiment, 400 ms is the maximum dwell time allotted for communication on any frequency channel in the UHF band. The communication packet has a variable length (but not to exceed a given length) and the preferred data rate is 2400 bits per second (bps). This may vary in other embodiments.
[0081] The discussion that follows is directed toward the flow charts of FIGS. 5-8 . The flow charts of FIGS. 5-8 are intended to illustrate embodiments of methods for communicating in a dual-mode communication protocol. In general, the methods may be embodied in software, hardware, firmware, or any combination thereof, and may be executed by devices, such as those illustrated in the embodiments of FIGS. 1-2 .
[0082] FIG. 5 is a flow chart illustrating an embodiment of a method 500 for transmitting in the dual-mode communication mode. Initially, the method 500 begins by receiving a command to transmit a particular communication packet. The communication packet may be generated by the device preparing to transmit, or it may be from another device having just sent the communication packet. In the latter case, the current device serves as a relay or repeater.
[0083] The method 500 proceeds by first searching for the communication mode of the intended receiver (step 510). This may be accomplished by examining the Rx address of the intended receiver, where information conveying the communication mode may be found. For example, the two MSBs of the Rx address may be reserved for conveying whether the receiver can communicate in the fixed-frequency communication protocol, the spread-spectrum communication protocol, or both. This may require querying the Rx address table 104 found in memory 100 of a transceiver (see FIG. 2 ). Alternatively, this information may be found in another table, which is not fully integrated with the Rx address.
[0084] If it is determined that the receiver communicates in the fixed-frequency communication protocol (step 515), the transmitter then begins transmission of the communication packet in the fixed-frequency communication protocol (step 520). The fixed-frequency communication protocol operates by communicating the entire communication packet, including the preamble and data portion, while at one frequency channel. Furthermore, the fixed-frequency communication protocol may utilize a particular modulation scheme, such as a particular amplitude modulation scheme. Likewise, the fixed-frequency communication protocol may transmit at a given power level. In the preferred embodiment, the fixed-frequency communication protocol operates at a substantially low-power radiation level. Other modulation schemes and/or power radiation levels could be utilized without departing from the scope of the present invention.
[0085] The transmitter may determine whether the transmission was a success (step 525) by receiving a response from the intended receiver. In certain instances, a response may not be required, thus the transmitter may not expect such a response. In these instances, success verification is not necessary and this step may be omitted.
[0086] Upon a success, or upon completing transmission of the communication packet if success verification is not necessary, the communication mode of the intended receiver may be updated (step 550), if necessary, and the response communication packet can be processed (step 560). Upon a failure, the method 500 proceeds by attempting to communicate in the spread-spectrum communication protocol (step 530).
[0087] Returning back to step 515, if it is determined that the intended receiver does not communicate in the fixed-frequency communication protocol, the transmitter will then begin transmission in the spread-spectrum communication protocol (step 530). This step will be discussed in further detail with relation to FIG. 6 .
[0088] Upon transmitting the communication packet in the spread-spectrum communication protocol, the transmitting device may then verify whether the transmission was successful by receiving a response from the intended receiver (step 540). If successful, the method 500 proceeds to step 550 where the communication mode of the intended receiver may be updated. The transmitter can then process the response, if necessary (step 560). If not successful, the method 500 proceeds by attempting to transmit the communication packet in the fixed-frequency communication protocol (step 520).
[0089] A simple counter can be applied to count the number of failures or attempts at communicating in the two protocols (step 570). After a prescribed number of failures, a failure mode may be initialized, which may include a recalibration feature.
[0090] In some situations, the transmitting device may not have knowledge of the communication mode in which the intended receiver operates. In this case, the default procedure is to first attempt communication in the spread-spectrum communication protocol (step 530). If this is successful, the communication mode related to the intended receiver may be updated. If not successful, transmission can be attempted in the fixed-frequency communication protocol. If successful, the communication mode related to the intended receiver can be updated accordingly. Alternatively, the default may be to attempt communication first in the fixed-frequency communication protocol, and then the spread-spectrum communication protocol.
[0091] FIG. 6 is a flow chart illustrating an embodiment of a method 530 for transmitting in the spread-spectrum communication protocol. The method 530 begins by placing the transmitting device in the spread-spectrum modulation mode (step 531). In one embodiment, the spread-spectrum modulation mode utilizes a frequency modulation scheme, such as frequency shift keying (FSK) modulation. In other embodiments, other modulation schemes could be utilized, including those other then frequency modulation schemes. Furthermore, the spread-spectrum communication protocol calls for transmitting at a relatively higher-power radiation power then the fixed-frequency communication protocol. In this manner, the spread-spectrum communication protocol facilitates greater range and signal penetration.
[0092] The method 530 proceeds by setting the transmitting channel to the desired acquisition channel (step 532). The desired acquisition channel may be chosen in a predetermined pattern, or randomly.
[0093] Once the transmitting channel is set, the preamble of the communication packet can be sent (step 533). This step includes sending the training sequence (step 534) and the data channel index (step 535).
[0094] Upon sending the preamble, the transmitting device then switches the transmitting channel to the data channel as designated by the data channel index (step 536). The designated data channel may be selected in a predetermined pattern, or randomly. Subsequently, the data portion of the communication packet (step 537) is sent.
[0095] Once the entire communication packet is sent, the transmitting device may then switch to receive mode and await a response acknowledging reception of the communication packet by the intended receiver (step 538). This step may be omitted if no response is necessary. Receive mode is described in further detail in subsequent figures.
[0096] FIG. 7 is a flow chart illustrating one embodiment of a method 600 for receiving in the dual-mode communication protocol. The method 600 begins by placing the receiving device in one of the communication modes, in this case the spread-spectrum communication mode, which includes setting the demodulation mode to the chosen spread-spectrum modulation/demodulation scheme, as discussed in FIGS. 5 & 6 (step 605).
[0097] Next, the receiving channel is set for the next acquisition channel in the sequence or series of acquisition channels (step 610). The sequence or series of acquisition channels may be predetermined and preprogrammed into the firmware of the receiving devices, or may be done in a random or pseudorandom fashion. If it is determined that all of the acquisition channels have been used without detecting a carrier signal (step 615) the method 600 then proceeds with switching to fixed-frequency communication mode, which will be discussed shortly.
[0098] At each acquisition channel, a carrier signal is checked for using standard carrier detection techniques as known in the art (step 620). If one is not found at the current acquisition channel, the method 600 returns to step 610, where the receiving channel moves on to the next acquisition channel.
[0099] If a carrier signal is detected, the method 600 proceeds with receiving the communication packet in the spread-spectrum communication protocol (step 630), which is discussed in further detail in FIG. 8 .
[0100] Next, the receiving device transmits a response back to the originating transmitter verifying a successful communication (step 640). Transmitting a successful response may require communicating by way of the methods illustrated in FIGS. 5 & 6 . Upon transmitting a response, the receiving device can then return back to the start of the method 600 and prepare for the next communication packet.
[0101] As mentioned above, if all of the acquisition channels are cycled through and a carrier signal is not detected (at step 615), the method 600 proceeds to the fixed-frequency communication mode. In this case, the receiving device switches (if necessary) to the fixed-frequency demodulation scheme (step 645). In one embodiment, the fixed-frequency modulation/demodulation scheme is different from the spread-spectrum modulation scheme, thus requiring a switch. Alternatively, however, the two modulation/demodulation schemes may be the same.
[0102] Next, the receiving channel is set to the next fixed-frequency channel (step 650). The next fixed-frequency channel may be selected among the designated fixed-frequency channels at random or in a predetermined manner. If it is determined that all of the fixed-frequency channels have been traversed without detecting a carrier signal (step 655), a recalibration procedure may be initiated (step 685). The recalibration procedure may not, however, be initiated until after a significant number of traversals of the acquisition channels and fixed-frequency channels without a carrier signal detection.
[0103] If a carrier signal is detected at step 660, the receiving device locks on and synchronizes communication by receiving the training sequence in the preamble of the communication packet. The remainder of the communication packet, including the data portion is then received at the current receiving channel (step 670).
[0104] Included within the step of receiving the entire communication packet (step 670) are several points at which the integrity of the data is verified. First, the receiving device receives the preamble of the communication packet (step 671). Next, the preamble is verified to determine whether it is a valid preamble (step 672). If not, the method 600 may return to step 650 where a new fixed-frequency channel is selected. If a valid preamble is detected, the receiving device receives and verifies the remainder of the communication packet (step 673). If the communication packet is invalid, it may be ignored and the method resumes back to step 650. If the communication packet is valid, the receiving device may then switch to transmission mode and transmit a response (step 680).
[0105] The recalibration procedure (step 685) may greatly vary with other embodiments. In one embodiment, particular environment conditions can be verified to determine whether drastic changes have occurred which could result in device malfunctions (step 686). For example, drastic operating temperature changes or ambient temperature changes could be verified to determine whether they are the cause of a possible device malfunction. In practice, environmental conditions such as these take time to change, thus the recalibration procedure may be performed at certain intervals of time, perhaps every 1000 fixed-frequency channel cycles, as an example. If recalibration is necessary (step 687), a recalibration protocol could be enabled (step 688).
[0106] The method 600 may return back to the spread-spectrum communication mode at step 605. In other embodiments, it is entirely foreseeable that the fixed-frequency communication mode is the first mode chosen, as opposed to the spread-spectrum communication mode. In this case, a receiving device would first attempt to receive in the fixed-frequency communication mode and then switch to the spread-spectrum communication mode after cycling through all of the fixed-frequency channels.
[0107] FIG. 8 is a flow chart illustrating an embodiment of a method 630 for receiving in the spread-spectrum communication protocol. The method 630 begins once a carrier signal has been detected at a particular acquisition channel. A receiving device then receives a preamble portion of a communication packet, which includes a training sequence and data channel index (step 631). The training sequence, as discussed earlier, is used to synchronize the timing for the receiving device.
[0108] Once the preamble is received, the receiving device may verify whether the preamble is valid (step 632). If not, the receiving device may return back to step 610 and switch to the next acquisition channel.
[0109] If the preamble is valid, the method 630 proceeds with looking up the data channel corresponding to the received data channel index in the preamble (step 633). Once established, the receiving device switches to the designated data channel, if necessary (step 634). In certain instances, where the acquisition channels and data channels overlap, it may be possible for the data channel index to indicate to the receiving device to remain at the current channel for data reception. For example, the special case of six binary 1s may indicate to the receiving device to remain at the current acquisition channel for data reception.
[0110] The data portion of the communication packet is then received and verified for integrity (step 635). If the communication packet is found to be invalid, the receiving device may revert back to step 610 where the next acquisition channel is selected. If the communication packet is found to be valid, method 630 ends, and the receiving device prepares to transmit a response, if necessary.
[0111] The embodiment or embodiments discussed were chosen and described to illustrate the principles of the invention and its practical application to enable one of ordinary skill in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. All such modifications and variations are within the scope of the invention as determined by the appended claims when interpreted in accordance with the breadth to which they are fairly and legally entitled.
Claims
What is claimed is:
1. A system for monitoring and controlling remote devices, said system comprising:
a first, a second and a third remote devices;
a first, a second and a third wireless transceivers integrated with said respective remote devices, wherein said wireless transceivers are configured to communicate with at least one of a spread-spectrum communication protocol and a fixed-frequency communication protocol;
the first wireless transceiver and the third wireless transceivers each comprising a logic element configured to:
transmit or receive a first portion of a communication frame at a first frequency channel, wherein the first portion of the communication frame comprises a data channel index that indicates a second frequency channel;
switch to the second frequency channel;
transmit or receive a second portion of the communication frame at the second frequency channel;
the first wireless transceiver is configured to switch between communicating in said spread spectrum communication protocol and said fixed frequency communication protocol said communication protocols by determining if after traversing through a first set of designated channels for communicating in one of said communication protocols and not receiving a communication frame in one of said designated channels; and
the first wireless transceiver and the second wireless transceiver are configured to communicate in the fixed-frequency communication protocol by transmitting or receiving a preamble and data portion of a communication frame at a third frequency channel.
2. The system of claim 1, wherein said wireless transceivers are further configured to communicate with a first modulation scheme when communicating in said spread-spectrum communication protocol and to communicate with a second modulation scheme when communicating in said fixed-frequency communication protocol.
3. The system of claim 2, wherein said first modulation scheme is the same as the second modulation scheme.
4. The system of claim 2, wherein said first modulation scheme is a frequency modulation scheme.
5. The system of claim 2, wherein said second modulation scheme is an amplitude modulation scheme.
6. The system of claim 1, wherein said wireless transceivers are further configured to communicate at a first radiating-power level when communicating in said spread-spectrum communication protocol and to communicate at a second radiating-power level when communicating in said fixed-frequency communication protocol.
7. The system of claim 6, wherein said first radiating-power level is higher then said second radiating-power level.
8. The system of claim 1, wherein said first and second remote devices are utility meters, and wherein said wireless transceivers are configured to communicate at least data corresponding to the measurements made by said utility meters.
9. The system of claim 1, further comprising: a local area network (LAN) of wireless transceivers, wherein said first and second wireless transceivers are part of said LAN; and at least a first gateway in communication with said LAN.
10. The system of claim 9, further comprising: a back-end system in communication with said at least first gateway via a wide area network (WAN), such that data is passed from each wireless transceiver in said LAN to said back-end system via said at least first gateway and WAN.
11. The system of claim 10, wherein said back-end system comprises: a network server configured to remotely control communication functions of said wireless transceivers in said LAN.
12. The system of claim 11, wherein said network server is configured to remotely control a modulation scheme in which any of said wireless transceivers communicate in either communication protocol.
13. The system of claim 11, wherein said network server is configured to remotely control a radiating-power level at which any of said wireless transceivers communicate in either communication protocol.
14. A system for monitoring the utility consumption measured by a plurality of utility meters, said system comprising:
a plurality of utility meters;
a network of wireless RF transceivers for communicating utility consumption data, wherein said network of wireless RF transceivers comprises a first dual-mode transceiver, a first fixed-frequency transceiver, and a first spread-spectrum transceiver;
the first spread-spectrum transceiver and first dual-mode transceiver each having a data channel index table stored on a memory element, the data channel index table correlating a plurality of data channel indexes to a plurality of data channel frequencies;
the first spread-spectrum transceiver and the first dual-mode transceiver each having a logic element for communicating in a spread spectrum protocol over a plurality of acquisition channel frequencies and a plurality of data channel frequencies, the logic element configured to:
prepare a communication message having a preamble portion and a separate data portion;
determine an acquisition channel frequency to transmit the preamble portion and a data channel frequency to transmit the data portion;
insert into the preamble portion a data channel index corresponding to the data channel frequency;
transmit the preamble portion over the acquisition channel frequency and transmit the data portion over the data channel frequency;
receive the preamble portion over the acquisition channel frequency;
ascertain the data channel frequency by comparing the data channel index in the preamble portion to the data channel index table stored in memory; and
receive the data portion by switching reception to the data channel frequency ascertained from the data channel index;
the first dual-mode transceiver is configured to switch between communicating in a fixed-frequency communication protocol or said spread spectrum communication protocol by determining if after traversing through a first set of designated channels for communicating in said spread spectrum communication protocols and not receiving a communication frame in one of said designated channels;
the first fixed-frequency transceiver and the first dual-mode transceiver are configured to communicate in a fixed-frequency communication protocol by transmitting or receiving a preamble and data portion of a communication frame at a third frequency channel;
a first gateway in communication with each wireless RF transceiver either directly or via other wireless RF transceivers, the first gateway relaying data from said network of wireless RF transceivers to a back-end system;
the first gateway configured to recover the data channel index from the preamble of the first portion of the communication frame and switch to a data channel frequency designated by the data channel index to receive the data portion of the communication frame.
15. The system of claim 14, wherein a first portion of said network of wireless RF transceivers are integrated with individual ones of said plurality of utility meters and a second portion of said network of wireless RF transceivers are stand-alone RF transceivers.
16. The system of claim 14, wherein said at least first gateway is a dual-mode gateway and is configured to communicate in the fixed-frequency communication protocol or the spread-spectrum communication protocol, depending on the protocol in which an intended transceiver communicates.
Patent Citations (839)
| 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 | Wadhwani 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 |
| US4284852(A) | 1981-08-01 | Szybicki et al. | Applicant |
| US4322842(A) | 1982-03-01 | Martinez | Applicant |
| US4345116(A) | 1982-08-01 | Ash et al. | Applicant |
| US4354181(A) | 1982-10-01 | Spletzer | Applicant |
| US4395780(A) | 1983-07-01 | Gohm et al. | Applicant |
| US4396910(A) | 1983-08-01 | Enemark et al. | Applicant |
| US4396915(A) | 1983-08-01 | Farnsworth et al. | Applicant |
| US4399531(A) | 1983-08-01 | Grande et al. | Applicant |
| US4406016(A) | 1983-09-01 | Abrams 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 |
| US4665519(A) | 1987-05-01 | Kirchner et al. | Applicant |
| US4669113(A) | 1987-05-01 | Ash et al. | Applicant |
| US4670739(A) | 1987-06-01 | Kelly, Jr. | Applicant |
| US4692761(A) | 1987-09-01 | Robinton | Applicant |
| US4704724(A) | 1987-11-01 | Krishnan et al. | 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 |
| US4792946(A) | 1988-12-01 | Mayo | Applicant |
| US4799059(A) | 1989-01-01 | Grindahl et al. | Applicant |
| US4800543(A) | 1989-01-01 | Lyndon-James et al. | Applicant |
| US4814763(A) | 1989-03-01 | Nelson 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 |
| US4864559(A) | 1989-09-01 | Perlman | Applicant |
| US4875231(A) | 1989-10-01 | Hara et al. | Applicant |
| US4884123(A) | 1989-11-01 | Morris et al. | Applicant |
| US4884132(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 |
| US4912656(A) | 1990-03-01 | Cain et al. | Applicant |
| US4918432(A) | 1990-04-01 | Pauley | Applicant |
| US4918690(A) | 1990-04-01 | Markkula, Jr. et al. | Applicant |
| US4918995(A) | 1990-04-01 | Pearman et al. | Applicant |
| US4924462(A) | 1990-05-01 | Sojka | 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 |
| US4987536(A) | 1991-01-01 | Humblet | 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 |
| US5088032(A) | 1992-02-01 | Bosack | 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 |
| US5117422(A) | 1992-05-01 | Hauptschein 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 |
| US5138615(A) | 1992-08-01 | Lamport et al. | Applicant |
| US5155481(A) | 1992-10-01 | Brennan, Jr. et al. | Applicant |
| US5159317(A) | 1992-10-01 | Brav | Applicant |
| US5159592(A) | 1992-10-01 | Perkins | Applicant |
| US5162776(A) | 1992-11-01 | Bushnell et al. | Applicant |
| US5170393(A) | 1992-12-01 | Peterson 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 |
| US5224468(A) | 1993-07-01 | Simon 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 |
| US5276680(A) | 1994-01-01 | Messenger | 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 |
| US5289362(A) | 1994-02-01 | Liebl et al. | Applicant |
| US5291516(A) | 1994-03-01 | Dixon et al. | Examiner |
| US5295154(A) | 1994-03-01 | Meier et al. | Applicant |
| US5305370(A) | 1994-04-01 | Kearns et al. | Applicant |
| US5309501(A) | 1994-05-01 | Kozik et al. | Applicant |
| US5315645(A) | 1994-05-01 | Matheny | Applicant |
| US5317309(A) | 1994-05-01 | Vercellotti et al. | Applicant |
| US5319364(A) | 1994-06-01 | Waraksa et al. | Applicant |
| US5319698(A) | 1994-06-01 | Glidewell et al. | 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 |
| US5344068(A) | 1994-09-01 | Haessig | 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 |
| US5352278(A) | 1994-10-01 | Korver 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 |
| US5383187(A) | 1995-01-01 | Vardakas et al. | Applicant |
| US5390206(A) | 1995-02-01 | Rein | Applicant |
| US5406619(A) | 1995-04-01 | Akhteruzzaman et al. | Applicant |
| US5412192(A) | 1995-05-01 | Hoss | Applicant |
| US5412654(A) | 1995-05-01 | Perkins | Applicant |
| US5412760(A) | 1995-05-01 | Peitz | Applicant |
| US5416475(A) | 1995-05-01 | Tolbert et al. | Applicant |
| US5416725(A) | 1995-05-01 | Pacheco et al. | Applicant |
| US5418812(A) | 1995-05-01 | Reyes et al. | Applicant |
| US5420910(A) | 1995-05-01 | Rudokas et al. | Applicant |
| US5424708(A) | 1995-06-01 | Ballesty et al. | Applicant |
| US5430729(A) | 1995-07-01 | Rahnema | 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 |
| US5442633(A) | 1995-08-01 | Perkins et al. | 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 |
| US5455569(A) | 1995-10-01 | Sherman et al. | 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 |
| US5479400(A) | 1995-12-01 | Dilworth 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 |
| US5508412(A) | 1996-04-01 | Kast et al. | Applicant |
| US5509073(A) | 1996-04-01 | Monnin | Applicant |
| US5513244(A) | 1996-04-01 | Joao et al. | Applicant |
| US5515419(A) | 1996-05-01 | Sheffer | Applicant |
| US5517188(A) | 1996-05-01 | Carroll et al. | Applicant |
| US5522089(A) | 1996-05-01 | Kikinis et al. | Applicant |
| US5528215(A) | 1996-06-01 | Siu et al. | Applicant |
| US5528507(A) | 1996-06-01 | McNamara 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 |
| US5544322(A) | 1996-08-01 | Cheng 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 | Applicant |
| US5555258(A) | 1996-09-01 | Snelling et al. | Applicant |
| US5555286(A) | 1996-09-01 | Tendler | Applicant |
| US5557320(A) | 1996-09-01 | Krebs | Applicant |
| US5557748(A) | 1996-09-01 | Norris | 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 |
| US5572528(A) | 1996-11-01 | Shuen | 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 |
| US5583914(A) | 1996-12-01 | Chang et al. | Applicant |
| US5587705(A) | 1996-12-01 | Morris | Applicant |
| US5588005(A) | 1996-12-01 | Ali et al. | Applicant |
| US5589878(A) | 1996-12-01 | Cortjens et al. | Applicant |
| US5590038(A) | 1996-12-01 | Pitroda | Applicant |
| US5590179(A) | 1996-12-01 | Shincovich et al. | Applicant |
| US5592491(A) | 1997-01-01 | Dinks | Applicant |
| US5594431(A) | 1997-01-01 | Sheppard et al. | Applicant |
| US5596719(A) | 1997-01-01 | Ramakrishnan et al. | Applicant |
| US5596722(A) | 1997-01-01 | Rahnema | 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 |
| US5608721(A) | 1997-03-01 | Natarajan et al. | Applicant |
| US5608786(A) | 1997-03-01 | Gordon | Applicant |
| US5613620(A) | 1997-03-01 | Center et al. | Applicant |
| US5615227(A) | 1997-03-01 | Schumacher, Jr. et al. | Applicant |
| US5615277(A) | 1997-03-01 | Hoffman | Applicant |
| US5617084(A) | 1997-04-01 | Sears | Applicant |
| US5619192(A) | 1997-04-01 | Ayala | Applicant |
| US5623495(A) | 1997-04-01 | Eng et al. | 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 |
| US5691980(A) | 1997-11-01 | Welles, II et al. | Applicant |
| US5696695(A) | 1997-12-01 | Ehlers 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 | Rowsell et al. | Applicant |
| US5719564(A) | 1998-02-01 | Sears | Applicant |
| US5726534(A) | 1998-03-01 | Seo | Applicant |
| US5726544(A) | 1998-03-01 | Lee | Applicant |
| US5726634(A) | 1998-03-01 | Hess et al. | Applicant |
| US5726644(A) | 1998-03-01 | Jednacz 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 |
| US5737318(A) | 1998-04-01 | Melnik | Applicant |
| US5740232(A) | 1998-04-01 | Pailles et al. | Applicant |
| US5740366(A) | 1998-04-01 | Mahany 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 |
| US5760742(A) | 1998-06-01 | Branch 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. | Examiner |
| 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 |
| US5812531(A) | 1998-09-01 | Cheung 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 |
| US5822309(A) | 1998-10-01 | Ayanoglu 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 |
| US5848054(A) | 1998-12-01 | Mosebrook et al. | Applicant |
| US5852658(A) | 1998-12-01 | Knight et al. | Applicant |
| US5854994(A) | 1998-12-01 | Canada et al. | Applicant |
| US5856974(A) | 1999-01-01 | Gervais et al. | Applicant |
| US5862201(A) | 1999-01-01 | Sands | Applicant |
| US5864772(A) | 1999-01-01 | Alvarado et al. | Applicant |
| US5870686(A) | 1999-02-01 | Monson | Applicant |
| US5872773(A) | 1999-02-01 | Katzela et al. | Applicant |
| US5873043(A) | 1999-02-01 | Comer | Applicant |
| US5874903(A) | 1999-02-01 | Shuey et al. | Applicant |
| US5875185(A) | 1999-02-01 | Wang et al. | Applicant |
| US5880677(A) | 1999-03-01 | Lestician | Applicant |
| US5883884(A) | 1999-03-01 | Atkinson | Applicant |
| US5883886(A) | 1999-03-01 | Eaton et al. | Applicant |
| US5884184(A) | 1999-03-01 | Sheffer | Applicant |
| US5884271(A) | 1999-03-01 | Pitroda | Applicant |
| US5886333(A) | 1999-03-01 | Miyake | Applicant |
| US5889468(A) | 1999-03-01 | Banga | Applicant |
| US5892690(A) | 1999-04-01 | Boatman et al. | Applicant |
| US5892758(A) | 1999-04-01 | Argyroudis | Applicant |
| US5892924(A) | 1999-04-01 | Lyon et al. | Applicant |
| US5896097(A) | 1999-04-01 | Cardozo | Applicant |
| US5897421(A) | 1999-04-01 | Chuang | Applicant |
| US5897607(A) | 1999-04-01 | Jenney et al. | Applicant |
| US5898369(A) | 1999-04-01 | Godwin | Applicant |
| US5898733(A) | 1999-04-01 | Satyanarayana | Applicant |
| US5905438(A) | 1999-05-01 | Weiss et al. | Applicant |
| US5905442(A) | 1999-05-01 | Mosebrook et al. | Applicant |
| US5907291(A) | 1999-05-01 | Chen et al. | Applicant |
| US5907491(A) | 1999-05-01 | Canada | Applicant |
| US5907540(A) | 1999-05-01 | Hayashi | Applicant |
| US5907807(A) | 1999-05-01 | Chavez, Jr. et al. | Applicant |
| US5909429(A) | 1999-06-01 | Satyanarayana 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. | Applicant |
| US5926101(A) | 1999-07-01 | Dasgupta | Applicant |
| US5926103(A) | 1999-07-01 | Petite | Applicant |
| US5926529(A) | 1999-07-01 | Hache et al. | Applicant |
| US5926531(A) | 1999-07-01 | Petite | Applicant |
| US5933073(A) | 1999-08-01 | Shuey | Applicant |
| US5940771(A) | 1999-08-01 | Gollnick et al. | Applicant |
| US5941363(A) | 1999-08-01 | Partyka et al. | Applicant |
| US5941955(A) | 1999-08-01 | Wilby et al. | Applicant |
| US5946631(A) | 1999-08-01 | Melnik | Applicant |
| US5948040(A) | 1999-09-01 | DeLorme et al. | Applicant |
| US5949779(A) | 1999-09-01 | Mostafa et al. | Applicant |
| US5949799(A) | 1999-09-01 | Grivna et al. | Applicant |
| US5953319(A) | 1999-09-01 | Dutta et al. | Applicant |
| US5953371(A) | 1999-09-01 | Rowsell et al. | Applicant |
| US5953507(A) | 1999-09-01 | Cheung et al. | Applicant |
| US5955718(A) | 1999-09-01 | Levasseur et al. | Applicant |
| US5957718(A) | 1999-09-01 | Cheng 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 | 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 |
| US5978578(A) | 1999-11-01 | Azarya et al. | Applicant |
| US5986574(A) | 1999-11-01 | Colton | Applicant |
| US5987011(A) | 1999-11-01 | Toh | Applicant |
| US5987331(A) | 1999-11-01 | Grube et al. | 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 |
| US5995022(A) | 1999-11-01 | Plis 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 |
| US6005884(A) | 1999-12-01 | Cook et al. | Applicant |
| US6005963(A) | 1999-12-01 | Bolle et al. | Applicant |
| US6018659(A) | 2000-01-01 | Ayyagari 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 |
| US6046978(A) | 2000-04-01 | Melnik | Applicant |
| US6054920(A) | 2000-04-01 | Smith et al. | Applicant |
| US6055561(A) | 2000-04-01 | Feldman 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 | 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 | 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 |
| US6084867(A) | 2000-07-01 | Meier | 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 |
| US6097703(A) | 2000-08-01 | Larsen et al. | Applicant |
| US6100816(A) | 2000-08-01 | Moore | 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. | Applicant |
| US6112983(A) | 2000-09-01 | D'Anniballe et al. | Applicant |
| US6115393(A) | 2000-09-01 | Engel 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 |
| US6122759(A) | 2000-09-01 | Ayanoglu et al. | Applicant |
| US6124806(A) | 2000-09-01 | Cunningham et al. | Applicant |
| 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. | Examiner |
| US6167239(A) | 2000-12-01 | Wright et al. | Applicant |
| US6172616(B1) | 2001-01-01 | Johnson et al. | Applicant |
| US6173159(B1) | 2001-01-01 | Wright 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 |
| US6185307(B1) | 2001-02-01 | Johnson, Jr. | Applicant |
| US6188354(B1) | 2001-02-01 | Soliman et al. | Applicant |
| US6188675(B1) | 2001-02-01 | Casper et al. | Applicant |
| US6192282(B1) | 2001-02-01 | Smith et al. | Applicant |
| US6192390(B1) | 2001-02-01 | Berger et al. | Applicant |
| US6195018(B1) | 2001-02-01 | Ragle et al. | Applicant |
| US6198390(B1) | 2001-03-01 | Schlager et al. | Applicant |
| US6199068(B1) | 2001-03-01 | Carpenter | Applicant |
| US6201962(B1) | 2001-03-01 | Sturniolo et al. | Applicant |
| US6205143(B1) | 2001-03-01 | Lemieux | Applicant |
| US6208247(B1) | 2001-03-01 | Agre et al. | Applicant |
| US6208266(B1) | 2001-03-01 | Lyons et al. | Applicant |
| US6212175(B1) | 2001-04-01 | Harsch | Applicant |
| US6215404(B1) | 2001-04-01 | Morales | Applicant |
| US6215440(B1) | 2001-04-01 | Geldart et al. | 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 |
| US6246676(B1) | 2001-06-01 | Chen et al. | Applicant |
| US6246677(B1) | 2001-06-01 | Nap | Applicant |
| US6246886(B1) | 2001-06-01 | Oliva | Applicant |
| US6249516(B1) | 2001-06-01 | Brownrigg et al. | Applicant |
| US6259369(B1) | 2001-07-01 | Monico | Applicant |
| US6271752(B1) | 2001-08-01 | Vaios | Applicant |
| US6275166(B1) | 2001-08-01 | del Castillo et al. | Applicant |
| US6275707(B1) | 2001-08-01 | Reed et al. | Applicant |
| US6286050(B1) | 2001-09-01 | Pullen et al. | Applicant |
| US6286756(B1) | 2001-09-01 | Stinson et al. | Applicant |
| US6288634(B1) | 2001-09-01 | Weiss et al. | Applicant |
| US6288641(B1) | 2001-09-01 | Casais | Applicant |
| US6295291(B1) | 2001-09-01 | Larkins | Applicant |
| US6301514(B1) | 2001-10-01 | Canada et al. | Applicant |
| US6304556(B1) | 2001-10-01 | Haas | Applicant |
| US6305205(B1) | 2001-10-01 | Derks et al. | Applicant |
| US6305602(B1) | 2001-10-01 | Grabowski et al. | Applicant |
| US6307843(B1) | 2001-10-01 | Okanoue | 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 |
| US6327245(B1) | 2001-12-01 | Satyanarayana et al. | Applicant |
| US6329902(B1) | 2001-12-01 | Lee et al. | 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 |
| US6363422(B1) | 2002-03-01 | Hunter et al. | Applicant |
| US6366217(B1) | 2002-04-01 | Cunningham | 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 |
| US6392692(B1) | 2002-05-01 | Monroe | 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 | 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 |
| US6415155(B1) | 2002-07-01 | Koshima et al. | Applicant |
| US6415245(B2) | 2002-07-01 | Williams et al. | Applicant |
| US6416471(B1) | 2002-07-01 | Kumar 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 |
| US6441723(B1) | 2002-08-01 | Mansfield, Jr. 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 |
| US6496696(B1) | 2002-12-01 | Melnik | Applicant |
| US6504357(B1) | 2003-01-01 | Hemminger et al. | Applicant |
| US6504834(B1) | 2003-01-01 | Fifield | Applicant |
| US6507794(B1) | 2003-01-01 | Hubbard et al. | Applicant |
| US6509722(B2) | 2003-01-01 | Lopata | Applicant |
| US6513060(B1) | 2003-01-01 | Nixon et al. | Applicant |
| US6515586(B1) | 2003-02-01 | Wymore | 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 |
| US6543690(B2) | 2003-04-01 | Leydier et al. | Applicant |
| US6542077(B2) | 2003-05-01 | Joao | Applicant |
| US6560223(B1) | 2003-05-01 | Egan et al. | Applicant |
| US6574234(B1) | 2003-06-01 | Myer 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 |
| US6665278(B2) | 2003-12-01 | Grayson | 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 |
| US6691173(B2) | 2004-02-01 | Morris et al. | 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 |
| US6775258(B1) | 2004-08-01 | van Valkenburg et al. | Applicant |
| US6804532(B1) | 2004-10-01 | Moon et al. | Applicant |
| US6816088(B1) | 2004-11-01 | Knoska et al. | Applicant |
| US6826607(B1) | 2004-11-01 | Gelvin et al. | Applicant |
| US6832251(B1) | 2004-12-01 | Gelvin et al. | Applicant |
| US6842430(B1) | 2005-01-01 | Melnik | Applicant |
| US6858876(B2) | 2005-02-01 | Gordon et al. | Applicant |
| US6859831(B1) | 2005-02-01 | Gelvin et al. | Applicant |
| US6888876(B1) | 2005-05-01 | Mason et al. | Examiner |
| US6891838(B1) | 2005-05-01 | Petite et al. | Applicant |
| US6900737(B1) | 2005-05-01 | Ardalan et al. | Applicant |
| US6906636(B1) | 2005-06-01 | Kraml | Applicant |
| US6914533(B2) | 2005-07-01 | Petite | Applicant |
| US6914893(B2) | 2005-07-01 | Petite | Applicant |
| US6922558(B2) | 2005-07-01 | Delp et al. | Applicant |
| US6959550(B2) | 2005-11-01 | Freeman et al. | Applicant |
| US6970434(B1) | 2005-11-01 | Mahany et al. | Applicant |
| US7020701(B1) | 2006-03-01 | Gelvin et al. | Applicant |
| US7027416(B1) | 2006-04-01 | Kriz | Applicant |
| US7027773(B1) | 2006-04-01 | McMillin | Applicant |
| US7053767(B2) | 2006-05-01 | Petite et al. | Applicant |
| US7054271(B2) | 2006-05-01 | Brownrigg et al. | Applicant |
| US7064679(B2) | 2006-06-01 | Ehrke et al. | Applicant |
| US7117239(B1) | 2006-10-01 | Hansen | Applicant |
| US7181501(B2) | 2007-02-01 | Defosse | Applicant |
| US7254372(B2) | 2007-08-01 | Janusz et al. | Applicant |
| US7304587(B2) | 2007-12-01 | Boaz | Applicant |
| US7349682(B1) | 2008-03-01 | Bennett, III et al. | Applicant |
| US7424527(B2) | 2008-09-01 | Petite | Applicant |
| US7468661(B2) | 2008-12-01 | Petite et al. | Applicant |
| US7480501(B2) | 2009-01-01 | Petite | Applicant |
| US7484008(B1) | 2009-01-01 | Gelvin et al. | Applicant |
| US7573813(B2) | 2009-08-01 | Melnik | Applicant |
| US7653394(B2) | 2010-01-01 | McMillin | Applicant |
| US7739378(B2) | 2010-06-01 | Petite | Applicant |
| US2001/0002210(A1) | 2001-05-01 | Petite | Applicant |
| US2001/0003479(A1) | 2001-06-01 | Fujiwara | Applicant |
| US2001/0021646(A1) | 2001-09-01 | Antonucci et al. | Applicant |
| US2001/0024163(A1) | 2001-09-01 | Petite | Applicant |
| US2001/0034223(A1) | 2001-10-01 | Rieser et al. | Applicant |
| US2001/0038343(A1) | 2001-11-01 | Meyer et al. | Applicant |
| US2002/0002444(A1) | 2002-01-01 | Williams et al. | Applicant |
| US2002/0012323(A1) | 2002-01-01 | Petite | Applicant |
| US2002/0013679(A1) | 2002-01-01 | Petite | Applicant |
| US2002/0016829(A1) | 2002-02-01 | Defosse | Applicant |
| US2002/0019725(A1) | 2002-02-01 | Petite | Applicant |
| US2002/0027504(A1) | 2002-03-01 | Petite | Applicant |
| US2002/0031101(A1) | 2002-03-01 | Petite | Applicant |
| US2002/0032746(A1) | 2002-03-01 | Lazaridis | Applicant |
| US2002/0061031(A1) | 2002-05-01 | Sugar et al. | Applicant |
| US2002/0072348(A1) | 2002-06-01 | Wheeler et al. | Applicant |
| US2002/0089428(A1) | 2002-07-01 | Walden et al. | Applicant |
| US2002/0095399(A1) | 2002-07-01 | Devine et al. | Applicant |
| US2002/0098858(A1) | 2002-07-01 | Struhsaker | Applicant |
| US2002/0109607(A1) | 2002-08-01 | Cumeralto et al. | Examiner |
| US2002/0136233(A1) | 2002-09-01 | Chen et al. | Applicant |
| US2002/0158774(A1) | 2002-10-01 | Johnson et al. | Applicant |
| US2002/0163442(A1) | 2002-11-01 | Fischer | Applicant |
| US2002/0169643(A1) | 2002-11-01 | Petite | Applicant |
| US2002/0193144(A1) | 2002-12-01 | Belski et al. | Applicant |
| US2003/0001754(A1) | 2003-01-01 | Johnson et al. | Applicant |
| US2003/0023146(A1) | 2003-01-01 | Shusterman | Applicant |
| US2003/0028632(A1) | 2003-02-01 | Davis | Applicant |
| US2003/0030926(A1) | 2003-02-01 | Aguren et al. | Applicant |
| US2003/0034900(A1) | 2003-02-01 | Han | Applicant |
| US2003/0035438(A1) | 2003-02-01 | Larsson | Applicant |
| US2003/0036822(A1) | 2003-02-01 | Davis et al. | Applicant |
| US2003/0046377(A1) | 2003-03-01 | Daum et al. | Applicant |
| US2003/0058818(A1) | 2003-03-01 | Wilkes et al. | Applicant |
| US2003/0069002(A1) | 2003-04-01 | Hunter et al. | Applicant |
| US2003/0073406(A1) | 2003-04-01 | Benjamin et al. | Applicant |
| US2003/0078029(A1) | 2003-04-01 | Petite | Applicant |
| US2003/0093484(A1) | 2003-05-01 | Petite | Applicant |
| US2003/0133473(A1) | 2003-07-01 | Manis et al. | Applicant |
| US2003/0169710(A1) | 2003-09-01 | Fan et al. | Applicant |
| US2003/0185204(A1) | 2003-10-01 | Murdock | Applicant |
| US2003/0210638(A1) | 2003-11-01 | Yoo et al. | Applicant |
| US2004/0047324(A1) | 2004-03-01 | Diener | Applicant |
| US2004/0053639(A1) | 2004-03-01 | Petite | Applicant |
| US2004/0090950(A1) | 2004-05-01 | Lauber et al. | Applicant |
| US2004/0113810(A1) | 2004-06-01 | Mason, Jr. et al. | Applicant |
| US2004/0131125(A1) | 2004-07-01 | Sanderford et al. | Examiner |
| 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. | Examiner |
| US2005/0017068(A1) | 2005-01-01 | Zalewski et al. | Applicant |
| US2005/0190055(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0195768(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0195775(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0201397(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0243867(A1) | 2005-11-01 | Petite | Applicant |
| US2005/0270173(A1) | 2005-12-01 | Boaz | Applicant |
| US2006/0095876(A1) | 2006-05-01 | Brownrigg et al. | Applicant |
| US2007/0112907(A1) | 2007-05-01 | Defosse | Applicant |
| US2008/0186898(A1) | 2008-08-01 | Petite | Applicant |
| US2009/0006617(A1) | 2009-01-01 | Petite | Applicant |
| US2009/0068947(A1) | 2009-03-01 | Petite | Applicant |
| US2009/0096605(A1) | 2009-04-01 | Petite | Applicant |
| US2009/0215424(A1) | 2009-08-01 | Petite | Applicant |
| US2009/0243840(A1) | 2009-10-01 | Petite et al. | Applicant |
| US2010/0250054(A1) | 2010-09-01 | Petite | Applicant |
| EP483547(A1) | 1992-05-01 | Applicant | |
| EP578041(B1) | 1994-01-01 | Applicant | |
| EP663746(B1) | 1995-07-01 | Applicant | |
| EP718954 | 1996-06-01 | Applicant | |
| EP718954(A1) | 1996-06-01 | Applicant | |
| EP740873(B1) | 1996-11-01 | Applicant | |
| EP749259(A2) | 1996-12-01 | Applicant | |
| EP749260(A2) | 1996-12-01 | Applicant | |
| EP766489(A2) | 1997-04-01 | Applicant | |
| EP768777(A2) | 1997-04-01 | Applicant | |
| EP812502(B1) | 1997-12-01 | Applicant | |
| EP7144 | 1998-02-01 | Applicant | |
| EP825577(A1) | 1998-02-01 | Applicant | |
| EP999717(A2) | 2000-05-01 | Applicant | |
| EP1096454 | 2001-05-01 | Applicant | |
| EP1096454(A2) | 2001-05-01 | Applicant | |
| FR2817110 | 2002-05-01 | Applicant | |
| FR2817110(A1) | 2002-05-01 | Applicant | |
| GB2229302 | 1990-09-01 | Applicant | |
| GB2229302(A) | 1990-09-01 | Applicant | |
| GB2247761 | 1992-03-01 | Applicant | |
| GB2247761(A) | 1992-03-01 | Applicant | |
| GB2262683 | 1993-06-01 | Applicant | |
| GB2262683(A) | 1993-06-01 | Applicant | |
| GB2297663 | 1996-08-01 | Applicant | |
| GB2297663(A) | 1996-08-01 | Applicant | |
| GB2310779 | 1997-09-01 | Applicant | |
| GB2310779(A) | 1997-09-01 | Applicant | |
| GB2326002 | 1998-12-01 | Applicant | |
| GB2326002(A) | 1998-12-01 | Applicant | |
| GB2336272 | 1999-10-01 | Applicant | |
| GB2336272(A) | 1999-10-01 | Applicant | |
| GB2352004 | 2001-01-01 | Applicant | |
| GB2352004(A) | 2001-01-01 | Applicant | |
| GB2352590 | 2001-01-01 | Applicant | |
| GB2352590(A) | 2001-01-01 | Applicant | |
| JP60261288 | 1985-12-01 | Applicant | |
| JP60261288(A) | 1985-12-01 | Applicant | |
| JP1255100 | 1989-10-01 | Applicant | |
| JP1255100(A) | 1989-10-01 | Applicant | |
| JP11353573 | 1999-12-01 | Applicant | |
| JP11353573(A) | 1999-12-01 | Applicant | |
| JP200113590 | 2000-04-01 | Applicant | |
| JP2000113590(A) | 2000-04-01 | Applicant | |
| JP2001063425 | 2001-03-01 | Applicant | |
| JP2001063425(A) | 2001-03-01 | Applicant | |
| JP2001088401 | 2001-04-01 | Applicant | |
| JP2001088401(A) | 2001-04-01 | Applicant | |
| JP2001309069 | 2001-11-01 | Applicant | |
| JP2001309069(A) | 2001-11-01 | Applicant | |
| JP2001319284 | 2001-11-01 | Applicant | |
| JP2001319284(A) | 2001-11-01 | Applicant | |
| JP2001357483 | 2001-12-01 | Applicant | |
| JP2001357483(A) | 2001-12-01 | Applicant | |
| JP2002007672 | 2002-01-01 | Applicant | |
| JP2002007672(A) | 2002-01-01 | Applicant | |
| JP2002007826 | 2002-01-01 | Applicant | |
| JP2002007826(A) | 2002-01-01 | Applicant | |
| JP2002085354 | 2002-03-01 | Applicant | |
| JP2002085354(A) | 2002-03-01 | Applicant | |
| JP2002171354 | 2002-06-01 | Applicant | |
| JP2002171354(A) | 2002-06-01 | Applicant | |
| KR2001025431 | 2001-04-01 | Applicant | |
| KR2001025431(A) | 2001-04-01 | Applicant | |
| NO3/021877 | 2003-03-01 | Applicant | |
| WO90/13197 | 1990-11-01 | Applicant | |
| WO95/12942 | 1995-05-01 | Applicant | |
| WO9524177 | 1995-09-01 | Applicant | |
| WO95/24177 | 1995-09-01 | Applicant | |
| WO95/34177 | 1995-12-01 | Applicant | |
| WO96/10307 | 1996-04-01 | Applicant | |
| WO98/00056 | 1998-01-01 | Applicant | |
| WO98/10393 | 1998-03-01 | Applicant | |
| WO98/10393(A1) | 1998-03-01 | Applicant | |
| WO98/37528 | 1998-08-01 | Applicant | |
| WO98/45717 | 1998-10-01 | Applicant | |
| WO99/13426 | 1999-03-01 | Applicant | |
| WO23956 | 2000-04-01 | Applicant | |
| WO/23956 | 2000-04-01 | Applicant | |
| WO/36812 | 2000-06-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 | |
| WO2/052521 | 2002-07-01 | Applicant | |
| WO2/52521 | 2002-07-01 | Applicant | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/07264 | 2003-01-01 | Applicant | |
| WO3/021877 | 2003-03-01 | Applicant | |
| WO3/21877 | 2003-03-01 | Applicant | |
| WO4002014 | 2003-12-01 | Applicant | |
| WO2004/002014 | 2003-12-01 | Applicant |
Non-Patent Literature (820)
- Federal Communications Commission, “Notice of Proposed Rule Making and Order,” Adopted Dec. 17, 2003, Released Dec. 30, 2003 (53 pages).Applicant
- Xecom Incorporated, “XE900S Smart Spread Spectrum Transceiver,” Nov. 2003 (13 pages).Applicant
- Harrington, Tim, “More Visible Vehicles,” ActionLINE, Jul. 2003 (4 pages).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,”.Applicant
- Brownrigg, Edwin, “User Provided Access to the Internet,”, Open Access Solutions, http://web.simmons.edu/chen/nit/NIT'92/033-bro.htm, Jun. 8, 2005-Jun. 9, 2005.Applicant
- Khan, Robert E., “The Organization of Computer Resources into a Packet Radio Network,” IEEE, Jan. 1977, vol. Com-25 No. 1, pp. 169-178.Applicant
- Westcott, Jill A., “Issues in Distributed Routing for Mobile Packet Radio Network,” IEEE 1982, pp. 233-238.Applicant
- Khan, Robert E., “The Organization of Computer Resources into a Packet Radio Network,” IEEE Transactions on Communications, Jan. 1977, vol. Com-25 No. 1, pp. 169-178.Applicant
- Westcott, Jill A., “Issues in Distributed Routing for Mobile Packet Radio Network,” IEEE 1982, pp. 233-238.Applicant
- Brownrigg, E.B. et al.; A Packet Radio Network for Library Automation; IEEE (1987); pp. 456-462.Applicant
- Brownrigg, E.B. et al.; A Packet Radio Networks; Architectures, Protocols, Technologies and Applications (1987), (introduction pp. ix-xviii); pp. 3-274.Applicant
- Brownrigg, E.B. et al.; Distributions, Networks, and Networking: Options for Dissemination; Workshop on Electronic Texts Session III (http://palimpsest.standford.edu/byorg/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-Sep. 1994 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-1469.Applicant
- Babak Daneshrad, et al.; 1997 Project Summary “Mobile Versatile Radios (MoVeR); ”University of California, Los Angeles; pp. 1-4.Applicant
- Rajeev Jain, et al.; 1997 Project Summary “Held Untethered Nodes;” University of California, Los Angeles; pp. 1-5.Applicant
- Randy H. Katz and Eric A. Brewer; 1997 Project Summary “Towards a Wireless Overlay Internetworking Architecture;” University of California, Berkeley; pp. 1-8, including slide show presentation at http://daedalus.cs.berkeley,edu/talks/retreat.6.96/Overview.pdf.Applicant
- J.J. Garcia-Luna-Aceves, et al.; “Wireless Internet Gateways (Wings);” IEEE, 1997; pp. 1271-1276.Applicant
- Randy H. Katz, et al.; “The Bay Area Research Wireless Access Network (BARWAN);” Electrical Engeneering and Computer Science Department, University of California, Berkeley, CA; IEEE, 1996; pp. 15-20, including slide show presentation at http://daedalus.cs.berkeley.edu/talks/retreat.6.97/BARWAN.S97.ppt.Applicant
- USPO's Decision dated Nov. 28, 2008 Denying Ex Parte Reexamination of USPN 7,103,511 in Reexamination Control No. 90/010,315.Applicant
- USPTO's Decision dated Jun. 22, 2009 Granting Ex Parte Reexamination of USPN 7,103,511 in Reexamination Control No. 90/010,509.Applicant
- USPTO's Decision dated Jun. 22, 2009 Granting Ex Parte Reexamination of USPN 7,103,511 in Reexamination Control No. 90/010,505.Applicant
- USPTO's Decision dated Jun. 22, 2009 Granting Ex Parte Reexamination of USPN 7,103,511 in Reexamination Control No. 90/010/507.Applicant
- USPTO's Decision dated Jun. 22, 2009 Granting Ex Parte Reexamination of USPN 7,103,511 in Reexamination Control No. 90/010,508.Applicant
- USPTO's Decision dated Jul. 21, 2009 Granting Ex Parte Reexamination of USPN 6,891,838 in Reexamination Control No. 90/010,512.Applicant
- USPTO's Decision dated Jul. 21, 2009 Granting Ex Parte Reexamination of USPN 6,891,838 in Reexamination Control No. 90/010,510.Applicant
- USPTO's Decision dated Jul. 21, 2009 Granting Ex Parte Reexamination of USPN 6,891,838 in Reexamination Control No. 90/010,511.Applicant
- USPTO's Decision dated Nov. 13, 2008 Granting Ex Parte Reexamination of USPN 6,891,838 in Reexamination Control No. 90/010,301.Applicant
- K. Bult, et al.; “Low Power Systems for Wireless Microsensors;” UCLA Electrical Engineering Department, Los Angeles, CA and Rockwell Science Center, Thousand Oaks, CA; pp. 25-29.Applicant
- David B. Johnnson and David A. Maltz, Dynamic Source Routing in Ad Hoc Wireless Networks; Computer Science Department, Carnegie Mellon University; a Chapter in Mobile Computing; Feb. 29, 1996; pp. 1-18.Applicant
- David A. Maltz et al.; Experiences Designing and Building a Multi-Hop Wireless Ad Hoc Network Testbed; School of Computer Science, Carnegie Mellon University; Mar. 5, 1999; pp. 1-20.Applicant
- “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications;” IEEE Std 802.11-1997; published Jun. 26, 1997 by the IEEE; pp. 1-459.Applicant
- John Jubin and Janet D. Tornow; “The DARPA Packet Radio Network Protocols;” Proceedings of the IEEE; vol. 75, No. 1, Jan. 1987; pp. 64-79.Applicant
- Chane Lee Fullmer; “Collision Avoidance Techniques for Packet-Radio Networks” thesis; University of California at Santa Cruz, CA; Jun. 1998; pp. 1-172.Applicant
- “3Com Invests in Coactive Networks,” Coactive (press release), Author: unknown, Dec. 14, 1999, pp. 1-4.Applicant
- “5808 Photoelectric Smoke/Heat Detector with BuiltOin Wireless Transmitter Installation Instructions,” Ademco, 1998.Applicant
- “ABB Kent-Taylor Interfacing,” Author: unknown, Engineering Report, No. 93-011, Jun. 18, 1996, pp. 1-9.Applicant
- “AES Central Station Installation & Operation Manual, Document No. 40-0551e,” AES Intellinet, Nov. 1996.Applicant
- “AlarmNet-C Service Shutdown,” Honeywell, Inc., Author: unknown, Date: unknown, pp. 1.Applicant
- “Allen-Bradley Interfacing,” Author: unknown, Engineering Report, No. 90-023, Jul. 21, 1999, pp. 1-11.Applicant
- AN/TSQ-129 Position Location Reporting System (PLRS), Author: unknown, available at http://www.fas.org/man/dod-101/sys/land/plrs.htm on Feb. 22, 2010, pp. 1-3.Applicant
- “AWAIRS Adaptive Wireless Arrays Interactive Recconaissance, Surveillance, and Target Acquisition in Small Unit Operations”.Applicant
- “Barrington Interface,” Author: unknown, Engineering Report, No. 90-013, Revised: Oct. 1994, p. 1.Applicant
- Bell Canada launches public wireless Internet hotspot pilot, Dec. 10, 2002, http://www.bell.ca/3n/about/press/release/2002/pr—20021210.asp (3 pages).Applicant
- “Bristol Babcock Interfacing,” Author: unknown, Engineering Report, No. 95-001, Revised: Apr. 17, 1996, pp. 1-4.Applicant
- “Caddx Installation Instructions Package, document No. 466-1486,” Caddx Controls, Aug. 1998.Applicant
- “Caddx Installation Instructions Package, document No. 466-1786,” CADDX Installation Controls, Inc., Caddx Controls; Author: unknown; Aug. 1998, pp. 1-58.Applicant
- “Caddx Installation Instructions Package,” document No. 466-1786, CADDX Installation Controls, Inc., Caddx Controls; Author: unknown; Jul. 15, 1999, pp. 1-116.Applicant
- “CADDX NetworX NX-8 Control/Communicator Installation Manual,” Caddx Controls, 1996.Applicant
- “Case Study: Genentech Uses Coactive's Technology to Centralize Monitor and Control Functions in a Mixed Legacy and New Equipment Environment,” Coactive, Author: unknown, 1998, pp. 1-4.Applicant
- “Case Study: Ingham Regional Medical Center Uses Coactive Technology to Monitor and Control Critical Power Generations in a Multi-Campus Environment,” Coactive, 1998, pp. 1-4.Applicant
- “Central Station Manual Section 1 System Overview, document No. 40-0551,” AES Intellinet, Dec. 1996.Applicant
- “Circon Systems Partners with Coactive Networks to Deliver Circon WebControl™, ” Coactive (press release), Author: unknown; Feb. 7, 2000, pp. 1-4.Applicant
- “CIRCON Technology Connects Building Management Systems to Internet Using Coactive Routers,” Coactive (press release), May 20, 1997.Applicant
- “CISCO's John Chambers Discusses the Internet Consumer Revolution at CES Using Demo Based on Echelon's LonWorks Technology,” Home Toys (press release), Jan. 8, 1999.Applicant
- Coactive Bridges Gap between Control Systems and Corporate Data Networks with New Off-the-Shelf Router Family, Coactive (press release), Jun. 8, 1998.Applicant
- “Coactive Enhances Residential Gateway to Enable Multiple Home Networks,” Coactive (press release), Author: unknown; Jan. 6, 2000, pp. 1-4.Applicant
- “Coactive Joins 3Com to Demonstrate Convergence of Control and Enterprise Networks at Retail Systems '98,” Coactive (press release), Author: unknown, Jun. 16, 1998, pp. 1-4.Applicant
- “Coactive Launches First Architecture to Support the Convergence Between Contol and IP Networks,” Coactive (press release), Author: unknown, May 20, 1998, pp. 1-4.Applicant
- “Coactive Leads Standardization Effort for LonTalk/IP Routers,” Coactive (press release), Author: unknown, May 20, 1997, p. 3.Applicant
- “Coactive Networks and Diverse Networks Team to Deliver End-to-End Infrastructure for Enabling the Digital Home,” Coactive (press release), Author: unknown, Aug. 28, 2000, p. 1-4.Applicant
- “Coactive Networks and Innovex Technologies Deliver Internet Access to Home Security, Lighting and Climate Control,” Coactive (press release), Author: unknown, Feb. 29, 2000, pp. 1-4.Applicant
- “Coactive Networks and Silicon Energy Partner to Deliever an End-to-End Solution for Internet-Based Energy Monitoring and Analysis,” Coactive (press release), Author: unknown, Sep. 19, 2000, pp. 1-4.Applicant
- “Coactive Networks and Vicinium Systems team to Deliver a Complete Television-Based Interface to Digital Homes and Neighborhoods,” Coactive (press release), Author: unknown, Jun. 19, 2000, pp. 1-4.Applicant
- “Coactive Networks Announces First Shipments of Internet Gateway to Home Control Systems,” Coactive (press release), Author: unknown, May 3, 1999, pp. 1- 4.Applicant
- “Coactive Networks Announces Formation of Technical Advisory Board,” Coactive (press release), Author: unknown, Oct. 5, 1998, pp. 1-4.Applicant
- “Coactive Networks Announces System Provider Partner Program,” Coactive (press release), Author: unknown, Jan. 25, 1999, pp. 1-4.Applicant
- “Coactive Networks Expands Support for Management and HMI Applications,” Coactive (press release), Author: unknown, Nov. 2, 1998, pp. 1-4.Applicant
- “Coactive Networks Names Gus Ezcurra Vice President of Sales,” Coactive (press release), Author: unknown, Jul. 20, 1998, p. 2.Applicant
- “Coactive Networks Names Janice Roberts, 3Com Senior VP, to Board of Directors,” Coactive (press release), Author: unknown, Jun. 2, 1998, p. 2.Applicant
- “Coactive Networks Powers Innovative Energy Management Solution,” Coactive (press release), Author: unknown, Jan. 5, 2001, pp. 1-4.Applicant
- “Coactive Networks President Named to LonMark Board of Directors,” Coactive (press release), Jun. 14, 1998.Applicant
- “Coactive Networks Shatters Price Barriers with New IP Gateway to Home Control Systems,” Coactive (press release), Author: unknown, Oct. 26, 1998, pp. 1-4.Applicant
- “Coactive Networks to Supply Internet-Based Home Gateways for up to 400,000 customers; First Phase of Deliveries Valued at US$2 Million,” Coactive (press release), Author: unknown, Oct. 25, 1999.Applicant
- “Coactive Networks Unveils the First Full-Service Residential Gateway,” Coactive (press release), Author: unknown, May 3, 2000, pp. 1-4.Applicant
- “Coactive Receives $2 Million in Funding,” Coactive (press release), Oct. 15, 1997.Applicant
- “Coactive Receives First Round of Venture Funding Investors Embrace Control Network Connectivity Technology,” Coactive (press release), Author: unknown, Dec. 1, 1997, p. 2.Applicant
- “DSC-3500 Meeting the Control and Conservation Challenge,” Johnson Controls, 1984, pp. 1-6.Applicant
- “DTE Energy Technologies Selects Coactive Networks Internet Gateways to Roll Out New Class of E-Services to Businesses,” Coactive (press release), Author: unknown, May 3, 2000, pp. 1-4.Applicant
- “DTE Energy Technologies Selects Coactive Networks to Power Distributed Generation Solutions Worldwide,” Coactive (press release), Author: unknown, Aug. 1, 2001, pp. 1-4.Applicant
- “Echelon Corporation Demonstrates Internet Connectivity in Digital Home Applications at 1999 International Consumer Electronics Show,” Home Toys (press release) , Dec. 15, 1998.Applicant
- “Eight Leading Controls Companies Join Coactive Partner Program,” Coactive (press release), Author: unknown, Aug. 21, 2000, pp. 1-4.Applicant
- “Enhanced Position Location Reporting System (EPLRS),” Author: unknown, available at http://www.globalsecurity.org/military/systems/ground/eplrs.htm on Feb. 22, 2010, pp. 1-3.Applicant
- “ESTeem Engineering Report, Johnson Controls Interface No. 91-102,” Author: unknown, Publisher: unknown, Nov. 1994, pp. 1-14.Applicant
- “ESTeem Model 96F,” Author: unknown, ESTeem Radios; Sep. 6, 1996, pp. 1-2.Applicant
- “Foxboro Interfacing,” Author: unknown, Engineering Report, No. 91-023, Revised: Jun. 19, 1996, pp. 1-5.Applicant
- “GE Fanuc Interfacing,” Author: unknown, Engineering Report, No. 91-010, Revised: Apr. 11, 1996, pp. 1-8.Applicant
- “General PLC/RTU Interfacing,” Author: unknown, Engineering Report, No. 92-010, Revised: Jun. 18, 1996, pp. 1-5.Applicant
- ADEMCO Group, 7720P Programming Tool, User Guide, Mar. 1992, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net; pp. 1-8.Applicant
- ADEMCO Group, 7720Plus Subscriber Radio Installation Instructions, Oct. 1996, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net; pp. 1-30.Applicant
- ADEMCO Group, 7720ULF Combination Fire Control and Long Range Radio Transmitter, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990501210612/www.ademco.com/ademco on Mar. 5, 2009, pp. 1-3.Applicant
- ADEMCO Group, 7720ULF Subscriber Radio, Installation Instructions, Mar. 1995, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-20.Applicant
- ADEMCO Group, 7720V2 Self-Contained Long Range Radio Transmitter, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990501212349/www.ademco.com/ademco on Mar. 5, 2009 pp. 1-4.Applicant
- ADEMCO Group, 7720V2 Subscriber Radio, Installation Instructions, Jun. 1996, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-24.Applicant
- ADEMCO Group, 7810iR Internet Receiver, Installation and Setup Guide, May 2002, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-58.Applicant
- ADEMCO Group, 7820 Appendicies, Mar. 1995, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-2.Applicant
- ADEMCO Group, 7820 Integrated Radio Transmitter, Installation Instructions, Aug. 1995, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-52.Applicant
- ADEMCO Group, 7825 Outdoor Antenna with Bracket, Installation Instructions, Feb. 1995, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-2.Applicant
- ADEMCO Group, 7830R SafetyNet Subscriber Radio, Installation Instructions, Jun. 1996, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-32.Applicant
- ADEMCO Group, 7830R Subscriber Transmitter, 1997, available at http://web.archive.org/web/19990501215427/www.ademco.com.ademco on Mar. 5, 2009, pp. 1-3.Applicant
- ADEMCO Group, 7835C Cellular Control Channel Transceiver, Installation and Setup Guide, Sep. 1998, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-32.Applicant
- ADEMCO Group, 7835C Cellular SafetyNet Subscriber Radio Transceiver, 1997ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990801221202/www.ademco.com/on Mar. 5, 2009, pp. 1-3.Applicant
- ADEMCO Group, 7845C Cellular Control Channel Transceiver, Installation and Setup Guide, Sep. 1990, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-104.Applicant
- ADEMCO Group, 7845CZ Seven Zone Cellular Control Channel Transceiver, Installation and Setup Guide, Sep. 2001, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-64.Applicant
- ADEMCO Group, 7845i Internet Communications Module, Installation and Setup Guide, Mar. 2002, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-42.Applicant
- ADEMCO Group, 7920SE 900MHz Fully Synthesized Transceiver, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990501222639/www.ademco.com/ on Mar. 5, 2009, pp. 1-3.Applicant
- ADEMCO Group, 7920SE Transceiver, Installation Instructions, Apr. 1995, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-80.Applicant
- ADEMCO Group, ADEMCO World Leader in Home Security Products, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990428164624/www.ademco.com/ademco on Mar. 5, 2009, pp. 1-2.Applicant
- ADEMCO Group, AlarmNet Introduces Control Channel Cellular for Commercial Fire/Burglary Applications, Ademco Group (press release), Aug. 31, 1999, available at http://web.archive.org/web/19990420234120/www.ademco.com/pr0831 on Mar. 31, 2009.Applicant
- ADEMCO Group, AlarmNet, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/199904240234130/www.ademco.com/ademco on Mar. 5, 2009, pp. 1-3.Applicant
- ADEMCO Group, Alpha Vista No. 5130XT Security System, Installation Instructions, Mar. 1989, ADEMCO Group, Author: unknown, p. 96.Applicant
- ADEMCO Group, Compass Network Downloader, ADEMCO Group, Author: unknown, Date: unknown, available at http://www.guardianalarms.net pp. 1-109.Applicant
- ADEMCO Group, Compass, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990209094401/www.ademco.com/ademco on Mar. 5, 2009.Applicant
- ADEMCO Group, Control/Communicator 5110XM User's Manual, Apr. 1996, Ademco Group, Author: unknown, pp. 1-30.Applicant
- ADEMCO Group, Fire and Burglary System Model 5120XM User's Manual, Apr. 1996, ADEMCO Group, Author: unknown, pp. 1-40.Applicant
- ADEMCO Group, Home Page, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19961023204954/http://ademco.com/ on Mar. 5, 2009, p. 1.Applicant
- ADEMCO Group, LYNX- Quick Install Security System, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990116225005 pp. 1-3.Applicant
- ADEMCO Group, Lynx Quick Start Guide, Oct. 1998, Ademco Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Lynx Security System Installation and Setup Guide, Oct. 1998, Ademco Group, Author: unknown, pp. 1-48.Applicant
- ADEMCO Group, Lynx Security System Programming Form & Summary of Connections, Oct. 1998, Ademco Group, Author: unknown, pp. 1-16.Applicant
- ADEMCO Group, Lynx Security System User Guide, Oct. 1998, Ademco Group, Author: unknown, pp. 1-40.Applicant
- ADEMCO Group, Powerline Carrier Device Modules, 1997 ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990218035115/www.ademco.com/ademco on Mar. 5, 2009, pp. 1-2.Applicant
- ADEMCO Group, Remote Keypads 6128, 6137, 6137R, 6138, 6139 & 6139R, Installation Guide, Aug. 1998, Ademco Group, Author: unknown, pp. 1-2.Applicant
- ADEMCO Group, Security System Model 4110DL Programming Form, Oct. 1996, ADEMCO Group, Author: unknown, pp. 1-8.Applicant
- ADEMCO Group, Security System Model 4110XM Programming Form, Jul. 1996, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Security System Model 4120EC Programming Form, Sep. 1993, ADEMCO Group, Author: unknown, pp. 1-2.Applicant
- ADEMCO Group, Security System Model 4120XM Programming Form, Sep. 1992, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Security System Model 4130XM, 4140XM, 5130XM Programming Form, Date: unknown, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Security System Model 4130XT/4140/5130XT Programming Form, Jul. 1989, ADEMCO Group, Author: unknown, pp. 1-2.Applicant
- ADEMCO Group, Security System Model 4140XMP Programming Form, Jan. 1992, ADEMCO Group, Author: unknown, pp. 1-2.Applicant
- ADEMCO Group, Security System Model 4140XMPT Programming Form, ADEMCO Group, Author: unknown, Date: unknown, pp. 1-2.Applicant
- ADEMCO Group, Security System Model 4140XMPT2 Programming Form, Apr. 1996, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Security System Model 5110XM Programming Form, Apr. 1996, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Security System Model 5120XM Programming Form, Jun. 1996, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Security System Model 5140XM Programming Form, Jun. 1993, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Security System Model Vista-10 Programming Form, Sep. 1994, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, Security System Model Vista-10SE Programming Form, Apr. 1997, ADEMCO Group, Author: unknown, pp. 1-24.Applicant
- ADEMCO Group, Security System Model Vista-128B Commercial Burglary Partitioned Security System with Scheduling, Quick Start Guide, Jun. 1998, ADEMCO Group, Author: unknown, pp. 1-39.Applicant
- ADEMCO Group, Security System User's Manual, Sep. 1996, ADEMCO Group, Author: unknown, pp. 1-88.Applicant
- ADEMCO Group, The Vista-100 Series, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web19970620010543/www.ademco.com/ademco on Mar. 5, 2009.Applicant
- ADEMCO Group, The Vista-10SE, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990502214402/www.ademco/com/ademco on Mar. 5, 2009, pp. 1-4.Applicant
- ADEMCO Group, via16 Programming Form, Jul. 1993, ADEMCO Group, Author: unknown, pp. 1-2.Applicant
- ADEMCO Group, vial 6 Security System, Installation Instructions, Jan. 1992, ADEMCO Group, Author: unknown, pp. 1-24.Applicant
- ADEMCO Group, via-30+, Vista 10, 4111XM Security System User's Manual, Jul. 1994, ADEMCO Group, Author: unknown, pp. 1-44.Applicant
- ADEMCO Group, via-30Pse Security System Programming Guide, Apr. 1997, ADEMCO Group, Author: unknown, pp. 1-24.Applicant
- ADEMCO Group, via-30PSE, VISTA-1SE Security System User's Manual, Jan. 1997, ADEMCO Group, Author: unknown, pp. 1-88.Applicant
- ADEMCO Group, Vista 4120XM and 4140XMP Security System User's Manual, Jan. 1994, ADEMCO Group, Author: unknown, pp. 1-60.Applicant
- CUSTOM SOLUTIONS, INC., HomeVision-PC Version 2.62, Owner's Manual (1997), pp. 1-234.Applicant
- CUSTOM SOLUTIONS, INC., Media Information, Feb. 16, 1999, available at http://web.archive.org/web/19990502073249/www.csi3.com/hv—media.htm on Feb. 27, 2009, pp. 1-2.Applicant
- CUSTOM SOLUTIONS, INC., Using Enerzone StatNet Thermostats with HomeVision (1998) pp. 1-16.Applicant
- Davies et al., “Internetworking in the Military Environment,” Proceedings of IEEE Infocom '82 (1982) pp. 19-29.Applicant
- Davies et al., “The Application of Packet Switching Techniques to Combat Net Radio,” Proceedings of the IEEE, vol. 75, No. 1, Jan. 1987, pp. 43-55.Applicant
- Davis et al., “Knowledge-Based Management of Cellular Clone Fraud,” IEEE (1992), pp. 230-234.Applicant
- Deering et al., “Internet Protocol, Version 6 (IPv6),” RFC1883, Publisher: unknown, Dec. 1995, pp. 1-37.Applicant
- Deering et al., “Internet Protocol, Version 6 (IPv6),” RFC2460, The Internet Society, Dec. 1998, pp. 1-39.Applicant
- Diaz, “Intervehicular Information System (IVIS): the Basis for a Tactical Information System,” SAE International, Mar. 1994, pp. 1-14.Applicant
- Dixon et al., “Addressing, Bridging and Source Routing,” IEEE Network, Jan. 1988, vol. 2, No. 1, pp. 25-32.Applicant
- Dong et al., “Low Power Signal Processing Architectures for Network Microsensors,” ACM, 1997, pp. 173-177.Applicant
- Echelon Corp., “LonTalk® Protocol Specification,” Doc. No. 19550, available at http://www.enerlon.com/JobAids/Lontalk% /020Protocol%20Spec.pdf (1994).Applicant
- Echelon Corp., “Series 90™-30 PLC LonWorks® Bus Interface Module User's Manual,” Doc. No. GFK-1322A, available at http://www.pdfsupply.com/pdfs/gfk1322a.pdf (1997).Applicant
- Elson et al., “Fine-Grained Network Time Synchronization Using Reference Broadcasts,” UCLA Computer Science Department, May 17, 2002, pp. 1-14.Applicant
- Eng et al., “Bahama: A Broadband Ad-Hoc Wireless ATM Local-Area Network,” 1995 IEEE International Conference on Communications, Jun. 18-22, 1995, pp. 1216-1223.Applicant
- Ephremides et al., “A Design Concept for Reliable Mobile Radio Networks with a Frequency Hopping Signaling,” IEEE 1987, pp. 1-18.Applicant
- ESTeem Application Paper—AgriNorthwest Employee's Provide Wireless Control System (describinga system that was in use prior to Mar. 1999).Applicant
- ESTeem Application Paper—Allen-Bradley Goes Wireless on Alaska's North Slope (describing a system that was in use prior to Mar. 1999).Applicant
- ESTeem Application Paper—Build Your Own Wireless Power Distribution System (describing a system that was in use prior to Mar. 1999).Applicant
- ESTeem Application Paper—Lost Cabin Gas Plant Uses Wireless Control to Enhance Production & Safety (describing a system that was in use prior to Mar. 1999).Applicant
- ESTeem Application Paper—Northwest Farm Applies Wireless Solution (describing a system that was in use prior to Mar. 1999).Applicant
- ESTeem Application Paper—Wireless Control of Polluted Water (describing a system that was in use prior to Mar. 1999).Applicant
- ESTeem Application Paper—Wireless Mobile Mapping System (describing a system that was in use prior to Mar. 1999).Applicant
- ESTeem Application Paper—Wireless Networking for Kodiak's Coast Guard Station (describing a system that was in use prior to Mar. 1999).Applicant
- ESTeem Application Paper—Wireless Networking for Natural Gas Extraction (describing a system that was in use prior to Mar. 1999).Applicant
- ESTeem Models 85, 95, 96, & 98 User's Manual (describing the ESTeem 96C and 96F radios used prior to 1999).Applicant
- Estrin et al., “Next Century Challenges: Scallable Coordination in Sensor Networks,” ACM, 1999, pp. 263-270.Applicant
- Estrin et al., “RFC1940-Source Demand Routing: Packet Format and Forwarding Specification (Version 1),” Network Working Group, May 1996, available at http://www.faqs.org/rfcs/rfc1940.html, Sep. 14, 2009, pp. 1-20.Applicant
- Estrin et al., “Source Demand Routing: Packet Format and Forwarding Specification (Version 1)”, Network Working Group, Internet Draft, Jan. 19, 1995, pp. 1-28.Applicant
- Federal Communications Commission, “Notice of Proposed Rule Making and Order,” Adopted Dec. 17, 2003, Released Dec. 30, 2003 (54 pages).Applicant
- Frank, “Transmission of IP Datagrams Over NET/ROM Networks, ARRL Amateur Radio 7th Computer Networking Conference,” Oct. 1988, pp. 65-70.Applicant
- Frank, “Understanding Smart Sensors,” Artech House (1996).Applicant
- Frankel, “Packet Radios Provide Link for Distributed Survivable Command Control Communications in Post-Attack Scenarios,” Microwave System News, Jun. 1983, Circle Reader Service No. 77, pp. 80-108.Applicant
- Franz, “HiperLAN—Der ETSI-Standard fur locale Funknetze,” NTZ, Sep. 1995, 10 pages.Applicant
- Gale et al., “The Impact of Optical Media on Information Publishing,” Bulletin of the American Society For Information Science, vol. 12, No. 6, Aug./Sep. 1986, pp. 12-14.Applicant
- Garbee, “Thoughts on the Issues of Address Resolution and Routing in Amateur Packet Radio TCP/IP Networks,” ARRL Amateur Radio 6th Computer Networking Conference, Aug. 1987, p. 56-58.Applicant
- Garcia-Luna-Aceves, “A Fail-Safe Routing Algorithm for Multishop Packet-Radio Networks,” IEEE Infocom '86, Technical Sessions: Apr. 8-10, 1986, pp. 434-442.Applicant
- Garcia-Luna-Aceves, “A Minimum-hop Routing Algorithm Based on Distributed Information,” Elsevier Science Publishers, B.V. (North Holland), 1989, pp. 367-382.Applicant
- Garcia-Luna-Aceves, “Routing Management in Very Large Scale Networks,” Elsevier Science Publishers, B.V. (North Holland), 1988, pp. 81-93.Applicant
- GE Security, “NetworkX NX-4,” 2004, pp. 1-2.Applicant
- GE Security, “NetworkX NX-548E,” 2006, pp. 1-2.Applicant
- Geier et al., “Networking Routing Techniques and their Relevance to Packet Radio Networks,” ARRL/CRRL Amateur Radio 6th Computer Networking Conference, London, Ontario, Canada, Sep. 1990, pp. 105-117.Applicant
- Gerla et al., “Multicluster, Mobile, Multimedia Radio Network,” UCLA Computer Science Department; Baltzer Journals; Wireless Networks; Jul. 12, 1995, pp. 255-265.Applicant
- Golden Power Manufacturing, “6030 PCT Programmable Communicating Thermostat,” Author: unknown, 2007, pp. 1-3.Applicant
- Golden Power Manufacturing, “Ritetemp Universal Wireless Thermostat,” Author: unknown, 2007, pp. 1-2.Applicant
- Goldman et al., “Impact of Information and Communications Technologies on Residential Customer Energy Services,” Paper, Berkeley: UCLA, Oct. 1996, pp. 1-89.Applicant
- Gower et al., “Congestion Control Using Pacing in a Packet Radio Network”, Rockwell International, Collins Communications Systems Division, Richardson, TX, IEEE 1982, pp. 23.1-1-23.1-6, 1982.Applicant
- Grady et al., “Telemetry Options for Small Water Systems,” Special Report SR14-1999, Publisher: unknown, Sep. 1999, pp. 1-23.Applicant
- Guardian Alarms, Inc., “Home Security System—Model 7068 Digital Dialer Interface,” Author: unknown, available at www.guardianalarms.net, 2007, p. 1.Applicant
- Guardian Alarms, Inc., “Security Company—Home Alarm System Monitoring—AES 7067 IntelliTap-II Digital Dialer Interface,” Author: unknown, available at www.guardianalarms.net, 2007, p. 1.Applicant
- Guardian Alarms, Inc., “Security System—Alarm System Monitoring—7160 EZ Router,” Author: unknown, available at www.guardianalarms.net, 2007, p. 1.Applicant
- Guardian Alarms, Inc., “Security System—Alarm System Monitoring—NET 7000,” Author: unknown, available at www.guardianalarms.net, 2007, p. 1.Applicant
- Guardian Alarms, Inc., “Security System—Alarm System Monitoring—Radionics FDX,” Author: unknown, available at www.guardianalarms.net, 2007, p. 1.Applicant
- U.S. Appl. No. 12/477,329 Non-Final Office Action dated Aug. 19, 2010.Applicant
- U.S. Appl. No. 12/477,329 Non-Final Office Action dated Dec. 28, 2009.Applicant
- U.S. Appl. No. 12/356,358 Final Office Action dated Sep. 15, 2010.Applicant
- U.S. Appl. No. 12/356,358 Non-Final Office Action dated Jan. 21, 2010.Applicant
- U.S. Appl. No. 10/792,608 Non-Final Office Action dated Jan. 22, 2010.Applicant
- U.S. Appl. No. 10/792,608 Final Office Action dated Sep. 2, 2009.Applicant
- U.S. Appl. No. 10/792,608 Non-Final Office Action dated Feb. 3, 2009.Applicant
- U.S. Appl. No. 10/792,608 Final Office Action dated Aug. 19, 2008.Applicant
- U.S. Appl. No. 12/792,608 Restriction Requirement dated Dec. 21, 2007.Applicant
- U.S. Appl. No. 10/792,608 Non-Final Office Action dated Mar. 21, 2007.Applicant
- U.S. Appl. No. 12/816,266 Non-Final Office Action dated Oct. 12, 2010.Applicant
- U.S. Appl. No. 11/814,632 Final Office Action dated Dec.7, 2010.Applicant
- U.S. Appl. No. 11/814,632 Non-Final Office Action dated Jul. 13, 2010.Applicant
- U.S. Appl. No. 11/125,009 Non-Final Office Action dated Dec. 9, 2010.Applicant
- U.S. Appl. No. 11/125,009 Non-Final Office Action dated Mar. 1, 2010.Applicant
- U.S. Appl. No. 11/125,009 Non-Final Office Action dated Apr.6, 2009.Applicant
- U.S. Appl. No. 11/125,009 Non-Final Office Action dated Oct. 1, 2008.Applicant
- U.S. Appl. No. 11/125,009 Notice of Allowance dated Sep. 21, 2009.Applicant
- U.S. Appl. No. 12/169,536 Non-Final Office Action dated Oct. 20, 2010.Applicant
- U.S. Appl. No. 12/689,220 Non-Final Office Action dated Dec. 15, 2010.Applicant
- U.S. Appl. No. 11/300,902 Non-Final Office Action dated Aug. 6, 2010.Applicant
- U.S. Appl. No. 11/300,902 Non-Final Office Action dated Nov. 17, 2009.Applicant
- U.S. Appl. No. 11/300,902 Non-Final Office Action dated Oct. 7, 2008.Applicant
- U.S. Appl. No. 11/300,902 Final Office Action dated Jun. 4, 2008.Applicant
- U.S. Appl. No. 11/300,902 Non-Final Office Action dated Oct. 11, 2007.Applicant
- U.S. Appl. No. 11/300,902 Advisory Action dated Aug. 11, 2008.Applicant
- U.S. Appl. No. 12/482,892 Non-Final Office Action dated Dec. 13, 2010.Applicant
- MacGregor et al., “Multiple Control Stations in Packet Radio Networks”, Bolt, Beranek and Newman, Inc., Cambridge, MA, IEEE 1982, pp. 10.3-1-10.3-5, 1982.Applicant
- Mak et al., “Design Considerations for Implementation of Large Scale Automatic Meter Reading Systems,” IEEE Transactions on Power Delivery, vol. 10, No. 1, Jan. 1995, pp. 97-103.Applicant
- Malkin, “RFC 2453, RIP Version 2 (Nov. 1998),” available at http://tools.ietf.org/html/rfc2453, Jun. 24, 2009, pp. 1-40.Applicant
- Maltz, “On-Demand Routing in Multi-Hop Wireless Mobile Ad Hoc Networks,” Thesis, May 2001, pp. 1-192.Applicant
- Marcy et al., “Wireless Sensor Networks for Area Monitoring and lintegrated Vehicle Health Management Applications,” Rockwell Science Center, Thousand Oaks, CA, AIAA-99/4557; Date: unknown, pp. 1-11.Applicant
- Markie et al., “LonWorks and PC/104: A winning combination,” PC/104 Embedded Solutions, Summer 1998, pp. 1-8.Applicant
- Martel et al., “Home Automation Report: A Modular Minimum Complexity, High-Resolution and Low CostField Device Implementation for Home Automation and Healthcare,” MIT; Publisher: unknown; Mar. 31, 1998; pp. 1-29.Applicant
- McQuillan et al., “The ARPA Network Design Decisions,” Computer Networks, vol. 1, No. 5, Aug. 1977 pp. 243-289.Applicant
- McQuillan et al., “The New Routing Algorithm for the ARPANET,” IEEE Transactions on Communications, vol. COM-28, No. 5, May 1980, pp. 711-719.Applicant
- Mills, “Exterior Gateway Protocol Formal Specification” (Apr. 1984), RFC 904, available at http://tools.ietf.org/html/rfc904, Jun. 24, 2009, pp. 1-32.Applicant
- Moorman, “Packet Radio Used in a Cost-Effective Automated Weather Meso-Net,” available at http://www.wrh.noaa.gov/wrh/96TAs/TA9631/ta96-31.html, Dec. 3, 1996 (5 pages).Applicant
- Moy, “RFC 2328, OSPF Version 2 (Apr. 1998),” available at http://tools.ietf.org/html/rfc2328, Jun. 24, 2009, pp. 1-245.Applicant
- Mozer et al., “The Neural Network House: An Overview,” in L. Niklasson & Boden (eds.), Current trends in connectionism (pp. 371-380); Hillsdale: Erlbaun, 1995; pp. 1-9.Applicant
- Murthy et al., “An Efficient Routing Protocol for Wireless Networks, Mobile Networks and Applications 1,” (1996), pp. 183-197.Applicant
- Natkunanathan et al. “WINS: Signal Search Engine for Signal Classification,” EED, UCLA; Date: unknown; pp. 1-6.Applicant
- Natkunanathan et al., “A Signal Search Engine for Wireless Integrated Network Sensors,” EED, UCLA Electrical Engineering Department;; Date: unkown; pp. 1-4.Applicant
- Negus et al., “HomeRF™ and SWAP: Wireless Networking for the Connected Home,” ACM SIGMOBILE Mobile Computing and Communications Review, vol. 2, Issue 4, Oct. 1998, available at http://portal.acm.org/citation.cfm?id=1321400.1321401 on Mar. 29, 2009, pp. 1-2.Applicant
- Negus et al., “HomeRF™ and SWAP: Wireless Networking for the Connected Home,” Mobile Computing and Communications Review, vol. 2, No. 4, Date: unknown, pp. 28-37.Applicant
- NEXTGEN Searches, “IPCO v. The Wireless Sensor Network Industry? Special Report on IPCO v. ONCOR et al.,” Corporate Manager's Edition, 2009, pp. 1-16.Applicant
- Nilsen et al., “Storage Monitoring Systems For The Year 2000,” Dept. of Energy, Office of Scientific and Technical Information, Report No. SAND—97-8532C, available at http://www.osti.gov/bridge/product.biblio.jsp?query—id=&page=0&osti—id=303988 (1997).Applicant
- Ondo, “PLRS/JTDS Hybrid,” Filled Artillery Journal, Jan.-Feb. 1981, pp. 20-25.Applicant
- Oran (ed.), “OSI IS-IS Intra-Domain Routing Protocol,” RFC 1142 (Feb. 1990), available at http://tools.ietf.org/html/rfc1142, Jun. 24, 2009, pp. 1-665.Applicant
- Park et al., “SensorSim: A Simulation Framework for Sensor Networks,” ACM, 2000, pp. 104-111.Applicant
- Perkins et al., “A Mobile Networking System Based on Internet Protocol,” Publisher: unknown, Date: unknown, pp. 1-17.Applicant
- Perkins et al., “Ad-Hoc On-Demand Distance Vector Routing ”AODV, http://moment.cs.ucsb.edu/AODV/aodv.html, Aug. 25, 2009, pp. 1-5.Applicant
- Perkins et al., “Continuous, transparent network access for portable users, A Mobile Networking System Based on Internet Protocol,” IEEE Personal Communications, First Quarter 1994, pp. 32-41.Applicant
- Perkins et al., “Highly Dynamic Destination-Sequenced Distance-Vector Routing (DSDV) for Mobile Computers,” SIGCOM Conference on Communications Architectures, Protocols ans Applications, London England UK (Aug. 1994); pp. 234-244.Applicant
- Perkins et al., “Mobility Support in IPv6,” Internet Draft (Sep. 22, 1994), available at http://www.monarch.cs.rice.edu/internet-draft/draft-perkins-ipv6-mobility-sup-oo.txt., Sep. 26, 2009, pp. 1-13.Applicant
- Perkins et al., “RFC3561—Ad Hoc On-Demand Distance Vector (AODV) Routing (Jul. 2003),” available at http://tools.ietf.org/html?rfc 3561, Aug. 25, 2009, pp. 1-38.Applicant
- Pittway Corporation, “Company History,” available at http://www.fundinguniverse.com/company-histories/Pittway-Corporation Mar. 6, 2009, pp. 1-5.Applicant
- Plaintiffs' Opening Markman Brief in Support of Their Proposed Claim Constructions, filed by the patent owner and its co-plaintiff in SIPCO LLC et al. v. The Toro Co. et al., Case No. 2:08-cv-00505-TJS (E.D. Pa.) filed on Sep. 26, 2008.Applicant
- Pleading—Defendant Digi International Inc.'S First Amended Answer and Defenses of SIPCO, LLC v. CONTROL4 Corporation et al., Civil Action No. 6:10-cv-249, currently pending in the U.S. District Court for the Eastern District of Texas, Tyler Division, filed Nov. 22, 2010, pp. 1-27.Applicant
- Pleading—Defendant Siemens Industry, Inc.'S First Amended Answer and Defenses of SIPCO, LLC v. CONTROL4 Corporation et al., Civil Action No. 6:10-cv-249, currently pending in the U.S. District Court for the Eastern District of Texas, Tyler Division, filed Nov. 22, 2010, pp. 1-27.Applicant
- Pleading—Defendant The Toro Company, The Toro Company's Second Supplemented Objections and Answers to Plaintiffs SIPCO LLC and Advanced Sensor Technology, Inc.'S Interrogatory No. 4 to Defendant The Toro Company of SIPCO LLC, et al. v. The Toro Company et al., Civil Action No. 08- Cv-00505-TJS (pp. 1-9).Applicant
- Pleading—Defendant The Toro Company, Third Supplemented Objections and Answers to Plaintiffs SIPCO LLC and Advanced Sensor Technology, Inc.'S Interrogatory No. 4 to Defendant The Toro Company of SIPCO LLC, et al. v. The Toro Company et al., Civil Action No. 08-Cv-00505-TJS (pp. 1-9).Applicant
- Pleading—Expert Report of Randy H. Katz, Ph. D, of SIPCO, LLC et al. v. The Toro Company et al., Case No. 2:08-cv-00505.Applicant
- Poor, Robert D., “Hyphos: A Self-Organizing, Wireless Network,” Massachusetts Institute of Technology (Jun. 1997).Applicant
- Postel (ed.), “Transmission Control Protocol, Version 4,” RFC793, available at http://www.faqs.org/rfcs/rfc793.html, Sep. 1981, pp. 1-85.Applicant
- Postel (Editor), “Internet Protocol, DARPA Internet Program Protocol Specification,” RFC 791 (Sep. 1981), Information Sciences Institute, University of So. Cal., pp. 1-45.Applicant
- Pottie et al., “Adaptive Wireless Arrays for Interactive RSTA in SUO (AWAIRS),” UCLA, Electrical Engineering Department; Date: unknown, pp. 1-20.Applicant
- Pottie et al., “Adaptive Wireless Arrays Interactive Recconaissance, Surveillance, and Target Acquisition in Small Unit Operations (AWAIRS); Lower Power Wireless Integrated Microsensors (LWIM),” Presented to Dr. E. Carapezza, Dr. D. Lao and Lt. Col. J. Hernandez, UCLA, Rockwell Science Center; Mar. 21, 1997, pp. 1-110.Applicant
- Pottie et al., “WINS: Principles and Practice,” EDD, UCLA; Date: unknown, pp. 1-10.Applicant
- Pottie et al., “Wireless Integrated Network Sensors,” Communications of the ACM, vol. 43, No. 5, May 2000, pp. 51-58.Applicant
- Pottie et al., “Wireless Integrated Network Sensors: Towards Low Cost and Robust Self-Organizing Security Networks;” EED, UCLA; Rockwell Science Center; SPIE vol. 3577, Nov. 1, 1998, pp. 86-95.Applicant
- Pottie, “AWAIRS: Mini-Site Review, Project Status,” UCLA: Rockwell Science Center, Feb. 23, 1998, pp. 1-58.Applicant
- Pottie, “Hierarchical Information Processing in Distributed Sensor Networks,” ISIT, Aug. 16-21, 1998, IEEE, 1998, pp. 163;.Applicant
- Pottie, “R&D Quarterly and Annual Status Report,” SPAWAR (contractor), Apr. 31, 1999.Applicant
- Pottie, “Wireless Sensor Networks,” ITW 1998, Jun. 22-26, 1998, available at http://dantzig.ee.ucla.edu/oclab/Pottie.html, 2 pages.Applicant
- Printout of 47 C.F.R. 15 (131 pages).Applicant
- Rabaey et al., “PicoRadio Support Ad Hoc Ultra-Low Power Wireless Networking,” Computer, IEEE, Jul. 2000, pp. 42-48.Applicant
- Radlherr, “Datentransfer Ohne Draht and Telefon,” Funkschau, Nov. 1991, pp. 49-52.Applicant
- Raji, “Control Networks and the Internet, Rev. 2.0,” Echelon Corp., 1998, pp. 1-39.Applicant
- Raji, “End-to-End Solutions with LonWorks® Control Technology: Any Point, Any Time, Any Where,” Echelon Corp.; 1998, pp. 1-30.Applicant
- Raji, “Control Networks and the Internet,” Echelon Corp., Rev. 2.0, available at http://www.echelon.com/solutions/opensystems/papers/Control—Internet.pdf (1998).Applicant
- Rants and Ramblings, “Go Wireless . . . At a Payphone,” May 10, 2003, http://www.morethanthis.net/blog/archives/2003/05/10/000301.html (2 pages).Applicant
- Rehkter et al., “A Border Gateway Protocol 4 (BGP-4),” RFC 1771, (Mar. 1995), available at http://tools.ietf.org/html.rfc1771, Jun. 24, 2009, pp. 1-58.Applicant
- Reuters, “Verizon Launches Wi-Fi Hot Spots,” May 18, 2003, http://www.wired.com/news/wireless/0,1382,58830,00.html (2 pages).Applicant
- Ritter et al., The Architecture of Metricom's Microcellular Data Network™ (MCDN) and Details of its Implementation as the Second and Third Generation Ricochet™ Wide-Area Mobile Data Service, IEEE, 2001, pp. 143-152.Applicant
- Ross et al., “PNC/DOE Remote Monitoring Project at Japan's Joyo Facility,” Office of Scientific and Technical Information, Report No. SAND—96-1937C, available at http://www.osti.gov/bridge/product.biblio.jsp?query—id=0&page=0&osti—id=270680 (1996).Applicant
- Saffo, Paul, “Sensors: The Next Wave of Infotech Innovation,” Institute for the Future (1997).Applicant
- Salkintzisa et al., “Design and implementation of a low-cost wireless network for remote control and monitoring applications,” Elservier, Microprocessors and Microsystems, 1997, pp. 79-88.Applicant
- Saltzer et al., “Source Routing for Campus-wide Internet Transport (Sep. 15, 1980),” available at http://groups.csail.mit.edu/ana/publications/pubPDFs/Sourcerouting.html, Sep. 21, 2009, pp. 1-14.Applicant
- Schneider et al., “International Remote Monitoring Project Argentina Nuclear Power Station Spent Fuel Transfer Remote Monitoring System,” Dept. of Energy, Office of Scientific and Technical Information, Report No. SAND—97-1784C, available at http://www.osti.gov/bridge/product.biblio.jsp?query—id=1&page=0&osti—id=505674 (1997).Applicant
- Schulman et al., “SINCGARS Internet Controller-Heart of the Digitized Battlefield,” Proceedings of the 1996 Tactical Communications Conference, Apr. 30-May 2, 1996, pp. 417-421.Applicant
- Shacham et al., “A Packet Radio Network for Library Automation,” 1987 IEEE Military Communications Conference, vol. 2, at 21.3.1 (Oct. 1987); pp. 456-462.Applicant
- Shacham et al., “Dynamic Routing for Real-Time Data Transport in Packet Radio Networks,” IEEE Proceedings of INFOCOM '82, pp. 152-159.Applicant
- Shacham et al., “Future Directions In Packet Radio Architectures And Protocols,” Proceedings of the IEEE, vol. 75, No. 1, Jan. 1987, pp. 83-99.Applicant
- Shacham et al., “Future Directions In Packet Radio Technology,” Proceedings of IEEE Infocom 85, Mar. 26-28, 1985, pp, 93-98.Applicant
- Shacham et al., “Packet Radio Networking,” Telecommunications vol. 20, No. 9, Sep. 1986, pp. 42,43,46,48,64 and 82.Applicant
- Shoch, “Inter-Network Naming, Addressing and Routing, Internet Experiment Note # 19, Notebook section 2.3.3.5,” Xerox Palo Alto Research Center, Jan. 29, 1978, Publisher: unknown, pp. 1-9.Applicant
- Sohrabi et al., Protocols for Self-Organization of a Wireless Sensor Network, IEEE Personal Communications, Oct. 2000, pp. 16-27.Applicant
- Stern, “Verizon to Offer Wireless Web Link Via Pay Phones,” May 10, 2003, http://www.washingtonpopst.com/ac2/wp-dyn?pagename=article&node=&contentID=A367 . . . (3 pages).Applicant
- Subramanian et al., An Architectural for Building Self-Configurable Systems, IEEE, 2000, pp. 63-73.Applicant
- Sunshine, “Addressing Problems in Multi-Network Systems,” (Apr. 1981), available at ftp://ftp.isi.edu/in-notes/ien/ien178.txt, Sep. 14, 2009, pp. 1-26.Applicant
- Sunshine, “Addressing Problems in Multi-Network Systems,” Proceedings INFOCOM '82, 1982 IEEE, pp. 12-19.Applicant
- Sunshine, “Network Interconnection and Gateways,” IEEE Journal on Selected Areas in Communications, vol. 8, No. 1, Jan. 1990, pp. 4-11.Applicant
- Sunshine, “Source Routing in Computer Networks,” Information Sciences Department of The Rand Corporation (1977), Publisher: unknown, pp. 29-33.Applicant
- Sutherland, Ed, “Payphones: The Next Hotspot Wave?,” Jan. 28, 2003, http://www.isp-planet.com/fixed— wireless/news/2003/bellcanada—030128.html (3 pages).Applicant
- Tanenbaum, “Computer Networks,” 4th Int'l CAN Conf., Berlin, Germany, 1997.Applicant
- Thodorides, “Wireless Integrated Network Sensors,” Power Point Presentation, Publisher: unknown, Apr. 15, 2003, pp. 1-19.Applicant
- Thomas, “Extending CAN Networks by Incorporating Remote Bridging,” ESTeem Radios, Nov. 1994.Applicant
- Thomas, “Extending CAN Networks By Incorporating Remote Bridging,” 4th Int'l CAN Conf., Berlin, Germany, available at http://www.can-cia.org/fileadmin/cia/files/icc/4/thom as.pdf (1997).Applicant
- Tobagi et al, “Packet Radio and Satellite Networks,” IEEE Communications Magazine, vol. 22, No. 11, Nov. 1984, pp. 24-40.Applicant
- Toh, “A Novel Distributed Routing Protocol to Support Ad-Hoc Mobile Computing,” Conference Proceedings of the 1996 IEEE Fifteenth Annual International Phoenix Conference on Computers and Communications, Mar. 27-29, 1996, pp. 480-486.Applicant
- Totolo, Home RF, A New Protocol on the Horizon, Feb. 1999, available at www.hometoys.com/htinews/feb99/articles/totolo/totolo.htm on Mar. 2, 2009.Applicant
- Transmission Control Protocol; “DARPA Internet Program Protocol Specification,” John Postel Editor; Information Sciences Institute, University of Southern California, California; Sep. 1981; pp. 1-85.Applicant
- Varadhan et al., “SDRP Route Construction,” Internet Draft, available at draft-ietf-sdr-route-construction-01.{ps,txt}, Feb. 27, 2005, pp. 1-12.Applicant
- Vardhan, “Wireless Integrated Network Sensors (WINS): Distributed In Situ Sensing for Mission and Flight Systems,” 2000 IEEE Aerospace Conference Proceedings, (2000).Applicant
- Verizon, “Verizon Broadband Anytime,” Copyright 2003, https://www33.verizon.com/wifi/login/loacations/locations-remote.jsp (2 pages).Applicant
- Wang et al., “Energy-Scalable Protocols for Battery Operated MicroSensor Networks,” Department of Electrical Engineering Massachusetts Institute of Technology, 1999.Applicant
- Warrock, “School Give Report on Radio-Based FMS,” Energy User News, Nov. 7, 1983, p. 1.Applicant
- Weiser, “Some Computer Science Issues in Ubiquitous Computing,” Communications of the ACM, Jul. 1993.Applicant
- Weiser, “The Computer for the 21st Century,” Scientific American, Sep. 1991.Applicant
- Westcott et al., “A Distributed Routing Design for a Broadcast Environment,” 1982 IEEE Military Communications Conference on Progress in Spread Spectrum Communications, vol. 3, Oct. 17-20, 1982, pp. 10.4.1 - 10.4.5.Applicant
- Westcott et al., “Hierarchical Routing for Very Large Networks,” IEEE Military Communications Conference, Oct. 21-24, 1984, Conference Record vol. 2, pp. 214-218.Applicant
- Westcott, “Issues in Distributed Routing for Mobile Packet Radio Networks,” Proceedings of Computer Networks Compcon '82, Sep. 20-23, 1982, pp. 233-238.Applicant
- Wikipedia, “Ad Hoc On-Demand Distance Vector Routing,” available at http://en.wikipedia.org/wiki/Ad—Hoc—On-Demand—Distance—Vector— Routing on Aug. 25, 2009, pp. 1-3.Applicant
- Wikipedia, “Bellman-Ford Algorithm,” available at http://en.wikipedia.org/wiki/Bellman-Ford.Applicant
- Wikipedia, “Border Gateway Protocol,” available at http://en.wikipedia.org/wiki/Border—Gateway—Protocol, Jun. 24, 2009, pp. 1-13.Applicant
- Wikipedia, “Distance-Vector Routing Protocol,” available at http://en.wikipedia.org/wiki/Distance-Vector— Routing—protocol, Jun. 24, 2009, pp. 1-4.Applicant
- Wikipedia, “Enhanced Interior Gateway Routing Protocol,” available at http://en.wikipedia.org/wiki/EIGRP, Jun. 24, 2009, pp. 1-7.Applicant
- Wikipedia, “Exterior Gateway Protocol,” available at http://en.wikipedia.org/wiki/Exterior—Gateway—Protocol, Jun. 24, 2009, p. 1.Applicant
- Wikipedia, “Interior Gateway Routing Protocol,” available at http://en.wikipedia.org/wiki/Interior—Gateway—Routing—Protocol, Jun. 24, 2009, pp.1-2.Applicant
- Wikipedia, “IS-IS,” available at http://en.wikipedia.org/wiki/IS-IS, Jun. 24, 2009, pp. 1-3.Applicant
- Wikipedia, “L. R. Ford, Jr.,” available at http://en.wikipedia.org/wiki/L.—R.—Ford,—Jr, Jun. 24, 2009, p. 1.Applicant
- Wikipedia, “Open Shortest Path First,” available at http://en.wikipedia,org.wiki/Richard—Bellman, Jun. 24, 2009, pp. 1-3.Applicant
- Wikipedia, “Richard E. Bellman,” available at http://en.wikipedia.org/wiki/Richard—Bellman, Jun. 24, 2009, pp. 1-3.Applicant
- Wikipedia, “Routing Information Protocol,” available at http://en.wikipedia.org/wiki/Routing—Information—Protocol, Jun. 24, 2009, pp. 1-4.Applicant
- Will et al., “Wireless Networking for Control and Automation of Off-road Equipment,” ASAE, Jul. 18-21, 1999, pp. 1-10.Applicant
- Wilson, Lexicon 700t Touchscreen Remote, Jan. 1, 1999, available at http://avrev.com/home-theater-remotes-system-control/remotes-system on Mar. 2, 2009, pp. 1-3.Applicant
- Wright (ed.), Home-automation networks mature with the PC industry chases a new home LAN, EDN Design Feature, Date: unknown, pp.1-9.Applicant
- Wu, Jie, “Distributed System Design”, Department of Computer Science and Engineering, Florida Atlantic University, CRC Press, pp. 177- 180, 204+ Cover Pages, 1999.Applicant
- Nunavut et al., Web Based Remote Security System (WRSS) Model Development, IEEE, Apr. 7-9, 2000, pp. 379-382.Applicant
- X10, “CK11A ActiveHome, Home Automation System, Owner's Manual,” Oct. 23, 1997, pp. 1-56.Applicant
- X10.com: The Supersite for Home Automation, “What's in the Kit,” available at http://web.archive.org/web/19991111133453/www.com/products/x, on Mar. 2, 2009, pp. 1-2.Applicant
- X10.com: The Supersite for Home Automation, “Wireless Remote Control System (RC5000),” available at http://web.archive.org/web/1999111453227/www.x10.com/products/x1 on Mar. 2, 2009, p. 1.Applicant
- X10: The Supersite for Home Automation, “Transceiver Module,” available at http://web.archive.org/web/20000229141517/www.x10.com/products/x on Mar. 2, 2009, p. 1.Applicant
- Xecom Incorporated, “EX900S Smart Spread Spectrum Transceiver,” Nov. 2003 (13 pages).Applicant
- Yadav, “Border Security Using Wireless Integrated Network Sensors (WINS)”; ECE 7th SEM, UE6551.Applicant
- Young, “USAP: A Unifying Dynamic Distributed Mulitchannel TDMA Slot Assignment Protocol,” Rockwell International Communication Systems Division, IEEE (1996).Applicant
- Yu, “Target Identification Processor for Wireless Sensor Network,” Dissertation, Los Angeles: University of California, 1999, pp. 1-110.Applicant
- Zander et al., “The SOFTNET Project: A Retrospect,” 1988 IEEE, pp. 343-345.Applicant
- Zich et al., “Distribution, Networks, and Networking: Options for Dissemination”, Workshop on Electronic Texts Session III, http://palimpsets.stanford.edu/byorg/lc/etextw/sess3.html, pp. 1-10, Accessed Jul. 17, 2007.Applicant
- Zimmermann et al., “Daten Funken, Modacom-Telekom-Datenfunkdienst;” Bates SENSUS15305-15309, Publisher: unknown; Date: unknown, pp. 1-6.Applicant
- Kahn et al., Advances in Packet Radio Technology, Proceedings of the IEEE, vol. 66, No. 11, pp. 1468-1496 (Nov. 1978).Applicant
- Agre et al., “Development Platform for Self-Organizing Wireless Sensor Networks,” Rockwell Science Center and UCLA, Date:Apr. 1999, pp. 257-268.Applicant
- Kahn, “The Organization of Computer Resources into a Packet Radio Network,” IEEE, Jan. 1977, vol. Com-25 No. 1, pp. 169-178.Applicant
- Rosen, “Exterior Gateway Protocol (EGP),” Bolt Beranek and Newman Inc., Oct. 1982, pp. 1-48.Applicant
- ADEMCO Group, Control/Communicator 5110XM Installation Instructions, Apr. 1996, Ademco Group, Author: unknown, pp. 1-76.Applicant
- ADEMCO Group, Vista-128FB Commercial Fire and Burglary Partitioned Security System Quick Start Guide, Oct. 1998, ADEMCO Group, Author: unknown, pp. 1-68.Applicant
- Brain, “How Motes Work: A Typical Mote,” available at http://computer.howstuffworks.com/mote4.htm, on Feb. 25, 2010, pp. 1-2.Applicant
- Cook et al., Water Distribution and Control by Wireless Networking, Electronic Systems Technology; Date: unknown, pp. 1-3.Applicant
- Haartsen et al., “Bluetooth: Vision, Goals, and Architecture;” Mobile Computing and Communications Review; vol. 1, No. 2; pp. 1-8.Applicant
- Haartsen, “BLUETOOTH-The Universal Radio Interface for Ad Hoc, Wireless Connectivity;” Ericsson Review No. 3, 1998; pp. 110-117.Applicant
- Hahn et al., “Packet Radio Network Routing Algorithms: A Survey,” IEEE Communications Magazine, vol. 22, No. 11, Nov. 1984, pp. 41-47.Applicant
- Hai Omni, Features & Specifications, Home Automation, Inc., available at http://web.archive.org/web/19970216055832/www.homeauto.com/omni on Feb. 17, 2009, pp. 1-6.Applicant
- Hall, “Tactical Internet System Architecture for Task Force XXI,” 1996 IEEE, pp. 219-230.Applicant
- Hamilton et al., “Optimal Routing in Multihop Packet Radio Networks,” 1990 IEEE, pp. 389-396.Applicant
- Harrington, “More Visible Vehicles,” ActionLINE, Jul. 2003 (4 pages).Applicant
- Harrison, “Microwave Radio In The British Telecom Access Network,” Second IEE National Conference on Telecommunications, Conference Publication No. 300, Date: unknown, pp. 208-213.Applicant
- Hedrick, “An Introduction to IGRP,” Rutgers, The State University of New Jersey, Center for Computers and Information Services, Laboratory for Computer Science Research, Aug. 22, 1991 (Updated Aug. 10, 2005), pp. 1-21.Applicant
- Hedrick, “Routing Information Protocol” (Jun. 1988), RFC 1058, available at Http://Tools.letf.Org/Html/Rfc1058, Jun. 24, 2009, pp. 1-34.Applicant
- Hinden et al., “The DARPA Internet Gateway,” RFC 823, Publisher: unknown, Sep. 1982, pp. 1-43.Applicant
- Hogan, “Call of the Wi-Fi,” Entrepeneur Magazine, Sep. 2003, pp. 39-42.Applicant
- Holtsville et al., “Symbol Technologies, Telxon and Aironet Commit to Future Interoperability of Their Wireless Local Area Networks Based on the IEEE 802.11 Specification,” Business Wire, Jun. 24, 1996, available at http://www.thefreelibrary.com/—/print/PrintArticle.aspx?id=18414624, pp. 1-3.Applicant
- Home Automation Inc., “HAI Company Background;” Publisher: Unknown, Date: unknown, pp. 1-2.Applicant
- Home Toys, Inc., “HTINews Review,” available at http://www.hometoys.com/htinews/aug97/reviews/homevis/homevis1.htm on Mar. 2, 2009, pp. 1-26.Applicant
- Honeywell, Inc., “Honeywell Home Control Version 2.0 Demonstratin,” available at http://web.archive.org/web/19980630195929/www.hbc.honeywell.com/ on Mar. 5, 2009 (7 pages).Applicant
- Hong et al., “U.S. Lightning Market Characterization, vol. II.: Energy Efficient Lighting Technology Options,” Sep. 30, 2005, Reportprepared for Building Technologies Program, Office of Energy Efficiency and Renewable Energy, pp. 1-36.Applicant
- Hotel Technology Next Generation, “A Guide for Understanding Wireless in Hospitality,” an Htng White Paper, Jun. 2006 (Jayne O'Neill, ed.), pp. 1-77.Applicant
- Hruschka et al., “Packet Radio, Drahtlose Datenubertragung im Amateurfunk,” Elektor, Jun. 1991, pp. 54-57 and 84.Applicant
- Hsu et al., “Wireless Communications for Smart Dust,” Berkeley: UCLA, Jan. 30, 1998, pp. 1-20.Applicant
- Hubner et al., “A Distributed Multihop Protocol for Mobile Stations to Contact a Stationary Infrastructure,” The Third IEE Conference on Telecommunications, Conference Publication No. 331, Date: unknown, pp. 204-207.Applicant
- Internet Protocol, Version 4 (IPv4), RFC791 (Sep. 1981).Applicant
- Internet Protocol, Version 6 (IPv6) Specification, RFC 2460 (Dec. 1998).Applicant
- Internet Protocol; DARPA Internet Program Protocol Specification, John Postel Editor; Information Sciences Institute, University of Southern California, California; Sep. 1981; pp. 1-45.Applicant
- Iwata et al., “Scalable Routing Strategies for Ad Hoc Wireless Networks,” IEEE Journal on Selected Areas in Communications, vol. 17, No. 8, Aug. 1999, pp. 1369-1379.Applicant
- Jacobsen, “The Building Blocks of a Smart Sensor for Distributed Control Networks,” IEEE Technical Applications Conference Northcon, Nov. 4-6, 1998, pp. 285-290.Applicant
- JDS Technologies, “Infrafred Xpander, IR-XP2, User Manual,” Date: unknown, pp. 1-15.Applicant
- JDS Technologies, “Model: 8R5PR, 8 Channel RS485 Relay Xpander, Installation Manual,” pp. 1-5.Applicant
- JDSTechnologies, “Stargate 8 Channel RS-485 HUB,” Publisher: unknown, Date: unknown, p. 1.Applicant
- JDS Technologies, “Stargate Interactive Automation System,” 1998, pp. 1-2.Applicant
- JDS Technologies, “Stargate, Operation Manual,” Mar. 2000, pp. 1-114.Applicant
- JDS Technologies, “Stargate-IP System Layout,” Publisher: unknown; Date: unknown, p. 1.Applicant
- JDS Technologies, “Support: Protocol Specifications,” available at http://jdstechnologies.com/protocol.htm, on Feb. 16, 2009, pp. 1-32.Applicant
- JDS Technologies, “TimeCommander, TimeCommander Plus, User Guide,” Jun. 1998, pp. 1-95.Applicant
- JDS Technologies, “Web Xpander, Installation and Operation Manual,” Feb. 2004, pp. 1-34.Applicant
- Jimenez-Cedeno et al., “Centralized Packet Radio Network: A Communication Approach Suited for Data Collection in a Real-Time Flash Flood Prediction System,” ACM-SAC 1993, pp. 709-713.Applicant
- Johnson Controls, Inc., LonWorks® Digital Controller, 1998, pp. 1-12.Applicant
- Johnson et al., “Protocols for Adaptive Wireless and Mobile Networking,” IEEE Personal Communications, 3(1), Feb. 1996, pp. 1-18.Applicant
- Johnson et al., “Route Optimization in Mobile IP,” Internet Draft (Nov. 28, 1994), available at http://www.monarch.cs.rice.edu/internet-drafts/draft-ietf-mobileip-optim-00.txt., Sep. 26, 2009, pp. 1-29.Applicant
- Johnson, “Mobile Host Internetworking Using IP Loose Source Routing,” Carnegie Mellon University CMU-CS-93-128, DARPA Order No. 7330, Feb. 1993, pp. 1-18.Applicant
- Johnson, “Scalable and Robust Internetwork Routing for Mobile Hosts,” 1994 IEEE, pp. 1-11.Applicant
- Jubin, “Current Packet Radio Network Protocols,” Proc. of the IEEE Infocom (Mar. 26-28, 1985), pp. 86-92.Applicant
- Kaashoek et al., “FLIP: An Internetwork Protocol for Supporting Distributed Systems,” ACM Transactions on Computer Systems, vol. 11, No. 1, Feb. 1993, pp. 73-106.Applicant
- Kaiser et al., “Detailed Progress Report—LWIM Applications, Systems Verification and Field Trust Test,” UCLA..Applicant
- Kaiser et al., “Low Power Wireless Integrated Microsensors (LWIM), BAA 94-15 Proposal Abstract,” UCLA Electrical Engineering Department, Rockwell Science Center, Date: unknown, 15 pages.Applicant
- Kaiser et al., “Low Power Wireless Integrated Microsensors (LWIM), Request for Support to Project”, UCLA Electrical Engineering Department, Rockwell Science Center, Sep. 13, 1994, 71 pages.Applicant
- Kaiser et al., “Low Power Wireless Integrated Microsensors (LWIM),” UCLA; Rockwell Science Center; LWIM Kickoff Meeting, Aug. 8, 1995, Presented to Dr. Ken Gabriel (ARPA, Dr. Elissa Sobolewski (ARPA), and Dr. Joseph Kielman (FBI), 62 pages.Applicant
- Kaiser et al., “Program Mission: Low Power Wireless Integrated Microsensor (LWIM),” UCLA, Date: unknown.Applicant
- Kaiser, “Circuits and Systems for Embedded Wireless Devices: Low Power Sensor, Interface, Signal Processing, Communication, and Network Systems,” École Polytechnique Fédérale de Lausanne, pp. 1-40.Applicant
- Brownrigg et al., “Technical Services in the Age of Electronic Publishing,” Library Resource & Technical Services, Jan./Mar. 1984, pp. 59-67.Applicant
- Brownrigg, “Continuing Development of California State Radio Packet Project,” Proceedings of the ASIS 1992 Mid-Year Meeting (Silver Spring, MD: American Society for Information Science, 1992), pp. 97-100.Applicant
- Brunninga, “A Worldwide Packet Radio Network,” Signal, vol. 42, No. 10, Jun. 1988, pp. 221-230.Applicant
- Bryan et al., “Man-Portable Networked Sensor System,” Publisher: unknown, Date: unknown, pp. 1-10.Applicant
- Bult et al., “A Distributed, Wireless MEMS Technology for Condition Based Maintenance,” EED, Defense Technical Information Center, UCLA, Electrical Engineering Department, Rockwell Science Center; Apr. 22-26, 1996.Applicant
- Bult et al., “A Distributed, Wireless MEMS Technology for Condition Based Maintenance,” Publisher: unknown; Nov. 1997, pp. 1-8.Applicant
- Bult et al., “Low Power Systems for Wireless Microsensors,” EED, UCLA; ILSPED; 1996, pp. 1-15.Applicant
- Bult et al., “Low Power Wireless Integrated Microsensors (LWIN),” EED, UCLA; ARPA—LPE PI Meeting, Apr. 27-28, 1995, pp. 1-30.Applicant
- Bult et al., “Wireless Integrated Microsensors,” EED, UCLA Electrical Engineering Department, Rockwell Science Center, TRF; Jun. 6, 1996, pp. 205-210.Applicant
- CADDX-CADDI Controls, Inc., Ranger 9000E, User's Manual, downloaded from http://www.guardianalarms.net, May 17, 1996, pp. 1-9.Applicant
- Carlisle, “Edison's NetComm Project,” Proceedings of the 33rd Annual Rural Electric Power Conference, IEEE, Apr. 1989, pp. B5/1-B5/4.Applicant
- Custom Solutions, Inc., HomeVision-PC Description, available at http://web.archive.org/web/19981205094024/http://www.csi3.com/hv—pc.htm on Mar. 2, 2009, pp. 1-6.Applicant
- Custom Solutions, Inc., HomeVision-PC Software, available at http://web.archive.org/web/19990224053817/http://www.csi3.com/hvp3pc.htm on Feb. 27, 2009, pp. 1-2.Applicant
- Chen et al., “Route Optimization and Location Updates for Mobile Hosts,” 1996 IEEE, Proceedings of the 16th ICDS, pp. 319-326.Applicant
- Chen, Emerging Home Digital Networking Needs, Paper, DSP Solutions R & D Center, Texas Instruments, Inc., pp. 1-6.Applicant
- Cisco Systems, Inc., Enhanced Interior Gateway Routing Protocol, Cisco Systems, Inc., Updated Sep. 9, 2005, pp. 1-44.Applicant
- Cisco Systems, RFC1812-Requirements for IP Version 4 Routers, Fred Baker ed. (Jun. 1995), available at http://www.faqs.org/rfcs/rfc1812.html, Sep. 14, 2009, pp. 1-129.Applicant
- Clement, “SCADA System Using Packet Radios Helps to Lower Cincinnati's Telemetry Costs,” WATER/ Engineering & Management, Aug. 1996, pp. 18-20.Applicant
- Cleveland, “Performance and Design Considerations for Mobile Mesh Networks,” Milcom '96 Conference Proceedings, vol. 1 of 3, Oct. 22-24, 1996, pp. 245-249.Applicant
- Clever Solutions—Metricom offers wireless data networks—includes related articles on Metricom's technology and the SONeTech-company—Company Profile, available at http://findarticles.com/p/articles/mi—m0REL/is—n 11—v93/ai—147—70465/?tag=content;co11, on Nov. 22, 1993, (3 pages).Applicant
- Coactive Networks, Inc., A New Solution for Offering Multive Telemetry Services to the Home, Coactive, 1999, pp. 1-8.Applicant
- Coactive Networks, Inc., Coactive Connector@ 1000 Series, Coactive, 2000, pp. 1-4.Applicant
- Coactive Networks, Inc., Coactive Connector@ 2000 Series, Coactive, Date: unknown, pp. 1-8.Applicant
- Coactive Networks, Inc., Connecting Networks to the Real WorldTM' Coactive, Date: unknown, pp. 1-4.Applicant
- Coactive Networks, Inc., Corporate Backgrounder, Coactive, 2001, pp. 1-6.Applicant
- Coactive Networks, Inc., Corporate Fact Sheet, Coactive, 2001, p. 2.Applicant
- Coactive Networks, Inc., Router-LE: Remote Access to LonWorks Over Ethernet, Coactive, 1998, pp. 1-4.Applicant
- Coactive Networks, Inc., Router-LL: Connect LonWorks Networks Across Internet Protocol, Coactive, 1998, pp. 1-4.Applicant
- Cohen et al., “IP Addressing and Routing in a Local Wireless Network,” 1992 IEEE, 1992, pp. 626-632.Applicant
- Cook et al., “Water Distribution and Control by Wireless Networking,” Electronic Systems Technology, Date: unknown, pp. 1-3.Applicant
- Corbell et al., “Technical Implementation in Support Of The IAEA's Remote Monitoring Field Trial At The Oak Ridge Y-12 Plant,” Dept. of Energy, Office of Scientific and Technical Information, Report No. SAND—096-1934C, available at http://www.osti.gov/bridge/product.biblio.jsp?query—id=1&page=0&osti—id=270678 (1996).Applicant
- Corbell et al., “Technical Results Of Y-12/IAEA Field Trial Of Remote Monitoring System,” Dept. of Energy, Office of Scientific and Technical Information, Report No. SAND—97-1781C, available at http://www.osti.go v/bridge/product.biblio.jsp?query—id=0&page=0&osti—id=505711 (1997).Applicant
- Corcoran et al., “Browser-Style Interfaces to a Home Automation Network,” IEEE Transactions on Consumer Electronics, vol. 43, No. 4, Nov. 1997, pp. 1063-1069.Applicant
- Corcoran et al., “CEBus Network Access via the World-Wide-Web,” available at http://ieeexplore.ieee.org/xpl/freeabs—all.jsp?arnumber=517285, on Mar. 29, 2009, Paper published on Consumer Electronics, 1996, Digest of Technical Papers, pp. 236-237.Applicant
- Corcoran et al., “CEBus Network Access via the World-Wide-Web,” IEEE, 1996.Applicant
- Corson et al., “Architectural Considerations for Mobile Mesh Networking,” Milcom '96 Conference Proceedings vol. 1 of 3, Oct. 22-24, 1996, pp. 225-229.Applicant
- Corson et al., “Internet-Based Mobile Ad Hoc Networking,” IEEE Internet Computing, Jul.-Aug. 1999, pp. 63-70.Applicant
- Court's claim construction Order dated Feb. 10, 2009, in SIPCO LLC et al. v. The Toro Co. et al., Case No. 2:08-cv-00505-TJS (E.D. Pa.).Applicant
- Custom Solutions, Inc. Acessories, available at http://web.archive.org/web/19981206221844/www.csi3.com/hv— pv4.htm on Feb. 27, 2009, pp. 1-3.Applicant
- Custom Solutions, Inc., HomAtion 2000 for HomeVision, Press Release, available at http://web.archive.org/web/19981207075734/www.csi3.com/HV—PR—0 on Feb. 27, 2009, pp. 1-2.Applicant
- Custom Solutions, Inc., HomeVision 2.7 “How To” Information, Date: unknown; pp. 1-146.Applicant
- Custom Solutions, Inc., HomeVision 2.7 Auto Report Feature, Date: unknown, pp. 1-10.Applicant
- Custom Solutions, Inc., HomeVision 2.7 Interface Command Protocol, Date: unknown, pp. 1-40.Applicant
- Custom Solutions, Inc., HomeVision 2.7 Interface Command Protocol, Date: unknown, pp. 1-80.Applicant
- Custom Solutions, Inc., HomeVision 2.7, Date: unknown, pp. 1-42.Applicant
- Custom Solutions, Inc., HomeVision 2.7, Document Purpose, Date: unknown, pp. 1-28.Applicant
- Custom Solutions, Inc., HomeVision 2.7, Summary of Changes—2.7, Date: unknown, pp. 1-26.Applicant
- Custom Solutions, Inc., HomeVision 2.7, Welcome to HomeVision, Date: unknown, pp. 1-18.Applicant
- Custom Solutions, Inc., HomeVision 2.7e, Owner's Manual (1999); pp. 1-596.Applicant
- Custom Solutions, Inc., HomeVision 2.7e, Version History Overview, Date: unknown, pp. 1-38.Applicant
- Custom Solutions, Inc., HomeVision Description, available at http://web.archive.org/web/19981206004955/http://www.csi3.com/HV.htm on Mar. 2, 2009, pp. 1-14.Applicant
- Custom Solutions, Inc., HomeVision PC 2.62 Interface Command Protocol, date: unknown, pp. 1-36.Applicant
- Custom Solutions, Inc., HomeVision PC 2.62, Welcome to HomeVision PC, Date: unknown; pp. 1-16.Applicant
- Custom Solutions, Inc., HomeVision PC 2.62, Document Purpose, Date: unknown, pp. 1-24.Applicant
- Custom Solutions, Inc., HomeVision PC 2.62, Summary of Changes—2.62, date: unknown, pp. 1-8.Applicant
- Custom Solutions, Inc., HomeVision PC 2.62, Version History Overview, Date:unknown, pp. 1-6.Applicant
- AES IntelliNet Model 7050-E & 7750-E, RF Subscriber Unit, Version 1.71, Installation & Operation Manual, AES IntelliNet, Author: unknown, Feb. 24, 1997, available at www.guardianalarms.net, pp. 1-54.Applicant
- AES IntelliNet Model 7050-E Radio Subscriber Unit Installation Manual, AES IntelliNet, Author: unknown, Jul. 17, 2000, available at www.guardianalarms.net, pp. 1-4.Applicant
- AES IntelliNet Model 7440 & 7440-XL RF Subscriber Unit, Addendum, AES IntelliNet, Author: unknown, Aug. 29, 2002.Applicant
- AES IntelliNet Net 77 Version 1.48.30, Installation & Operation Manual, Document 40-0551u, AES Corporation, Author: unknown, Jun. 1999, pp. 1-30.Applicant
- AES IntelliNet Net 77 Version 1.48.4, Installation & Operation Manual, Document 40-0551u, AES Corporation, Author: unknown, Nov. 2000, pp. 1-36.Applicant
- AES IntelliNet Net 7K Version 1.48.4, Installation & Operation Manual, Document 40-0551, AES Corporation, Nov. 2000, pp. 1-36.Applicant
- AES IntelliNet Net7K Version 3, Installation & Operation Manual, Document 40-0551, AES Corporation, Jun. 1999, pp. 1-30.Applicant
- AES IntelliNet Radio Communication Subscriber Unit 7050, Sep. 16, 1997, available at http://web.archive.org/web/19990203061203/www.aes-intellinet.com/sp on Mar. 5, 2009, pp. 1-2.Applicant
- AES IntelliNet Theory of Operation, AES IntelliNet; Author: unknown, Dec. 1996, downloaded from http://www.guardianalarms.net, pp. 1-18.Applicant
- AES IntelliNet Wireless Network Glossary of Terms, document 40-0551 u, AES IntelliNet, Author: unknown, Dec. 96, pp. 1-15.Applicant
- AES IntelliNotes Universal Serial data Interface/USDI, Bulletin No. 55, AES Corporation, Author: unknown, Apr. 5, 2001, pp. 1-12.Applicant
- AES IntelliTAP Model 7068, Version 1.08, Installation Guide, AES IntelliNet, Author: unknown, Jun. 15, 2000, pp. 1-11.Applicant
- Aes IntelliTRAK 7555-RT GPS Based Vehicle Tracking Unit, Version 2.0a, AES IntelliNet, Author: unknown, Feb. 20, 2001, pp. 1-16.Applicant
- AES IntelliTRAK 7555-RT GPS Based Vehicle Tracking Unit, Version 2.12, AES IntelliNet, Author: unknown, Nov. 6, 2002, pp. 1-16.Applicant
- AES Net7000, Installation & Operation Manual, AES Intellinet, Author: unknown, Nov. 24, 1996, pp. 1-76.Applicant
- AES Net77 Wireless Network Management Software Installation & Operation ManuCentral Station Manual, Section 3, AES IntelliNet, Author: unknown, Dec. 1996, pp. 1-87.Applicant
- AES UL/ULC System Configuration, AES Corporation, Author: unknown, May 1, 2003, p. 1.Applicant
- Agre et al., “Autoconfigurable Distributed Control Systems,” ISADS, Apr. 27, 1995.Applicant
- Agre et al., “Development Platform for Self-Organizing Wireless Sensor Networks,” Rockwell Science Center and UCLA, Date:unknown, pp. 1-25.Applicant
- Agre et al., “Technical and Management Proposal for Adaptive Wireless Arrays for Interactive Reconnaissance, Surveillance and Target Acquisition in Small Unit Operations (AWAIRS),” Defense Advanced Research Projects Agency Broad Agency Announcement 96-26, UCLA, Date: unknown, pp. 1-50.Applicant
- Airpath Wireless, Inc., “Hot Spot Hardware,” Copyright 2003, http://www.airpath.com/programs/hardward/hardware.htm (vistited Jul. 29, 2003) (2 pages).Applicant
- AlarmLink, Inc. A Brief History available at http://www.alarmlink.com/Default.aspx?tabid=28, on Mar. 23, 2009, p. 1.Applicant
- AlarmLink, Inc. Alarm Over IP Products, available at http://www.alarmlink.com/Default.aspx?tabid=38 on Mar. 24, 2009, p. 1.Applicant
- AlarmLink, Inc. Central Stations, availabe at http://www.alarmlink.com/Default.aspx?tabid=35, on Mar. 24, 2009.Applicant
- AlarmLink, Inc. Home Page, avaliable at http://www.alarmlink.com/ on Mar. 24, 2009, p. 1.Applicant
- AlarmLink, Inc., “MeshWorks of Los Angeles,” available at http://www.alarmlink.com/Default.aspx?tabid=39 on Mar. 24, 2009, p. 1.Applicant
- Alwan et al., “Adaptive Mobile Multimedia Networks,” IEEE Personal Communications, Apr. 1996, pp. 34-51.Applicant
- Amir et al., “An Evaluation of the Metricom Ricochet Wireless Network,” CS 294-7 Class Project, Department of Electrical Engineering and Computer Science of the University of California at Berkeley, Publisher: unknown, May 7, 1996, pp. 1-20.Applicant
- Amir, “The Ricochet System Architecture,” available at http://www.lariat.org/Berkeley/node2.html, on May 1996, pp. 1-5.Applicant
- Asada et al., “Low Power Wireless Communication and Signal Processing Circuits for Distributed Microsensors;” Proceedings of the International Circuits and Systems Symposium, ISCAS '97; UCLA, Rockwell Science Center; Jun. 1997, pp. 1-5.Applicant
- Asada et al., “Wireless Integrated Network Sensors: Low Power Systems on a Chip,” UCLA, Rockwell Science Center; Date: unknown, pp. 1-24.Applicant
- Asada et al., “Wireless Integrated Sensors Networks: Low Power Systems on a Chip,” Publisher: unknown, Date: unknown, pp. 1-8.Applicant
- Asada, “Wireless Integrated Network Sensors (WINS),” UCLA, SPIE vol. 3673, Mar. 1999, pp. 11-18.Applicant
- Baba et al., “Wireless Medium Access Control Protocol for CAN,” 4th Int'l CAN Conf., Berlin, Germany, available at http://www.can-cia.org/fileadmin/cia/files/icc/4/babal.pdf (1997).Applicant
- Bagby, “Calypso Ventures Inc.—WLAN background,” 2 pages.Applicant
- Baker et al. “The Architectual Organization of a Mobile Radio Network via a Distributed Algorithm,” IEEE, Nov. 1981.Applicant
- Ball et al., “Reliability of Packet Switching Broadcast Radio Networks,” IEEE Transactions on Circuits and Systems, vol. CAS-23, No. 12, Dec. 1976, pp. 806-813.Applicant
- Bapna, et al., “Antenna Pointing for High Bandwidth Communications from Mobile Robots,” Paper, Field Robotics Center, The Robotics Institute, Carnegie Mellon University, date: unknown, pp. 1-6.Applicant
- Beech et al., “AX.25 Link Access Protocol for Amateur Packet Radio, Version 2.2,” American Relay & Tucson Amateur Packet Radio Corporation, Jul. 1993, Revised Jul. 1998, pp. 1-143.Applicant
- Bergstein, “US telco plans WiFi payphone,” May 12, 2003, http://www.news.com.au/common/story—page/0,4057,6420676%5E1 5306,00.html (2 pages).Applicant
- BGE, 5743 Wireless Dual Switch™ Glass Break Detector, Installation and Operating Instructions, BGE, Author: unknown; Date: unknown, pp. 1-2.Applicant
- Bge, 5742 Wirelss Audio Switch™Glass Break Detector, Installation and Operating Instructions, Bge, Author: unknown, Date: unknown, pp. 1-10.Applicant
- Bhatnagar et al., “Layer Net: A New Self-Organizing Network Protocol,” Department of Electrical Engineering, SUNY, IEEE, 1990.Applicant
- Black, “Lutron RF Technology, Reliable, First, Forward Thinking,” Lutron Electronics Co. Inc., Aug. 2006, pp. 1-16.Applicant
- Blaney, “HomeRF™ Working Group, 4th Liason Report,” IEEE, 802.11-98/360, Nov. 1998, Slides 1-12.Applicant
- Brain, “How Motes Work,” available at http://computer.howstuffworks.com/mote.htm, on Feb. 25, 2010, pp. 1-2.Applicant
- Brain, “How Motes Work: Ad hoc Networks,” available at http://computer.howstuffworks.com/mote3.htm on Feb. 25, 2010, pp. 1-3.Applicant
- Brain, “How Motes Work: The Basic Idea,” available at http://computer.howstuffworks.com/mote1.htm, on Feb. 26, 2010, pp. 1-2.Applicant
- Brain, “How Motes Work: Typical Applications,” available at http://computer.howstuffworks.com/mote2.htm, on Feb. 25, 2010, pp. 1-2.Applicant
- Brayer, “Implementation and Performance of Survivable Computer Communication with Autonomous Decentralized Control,” IEEE Communications Magazine, Jul. 1983, pp. 34-41.Applicant
- Brownrigg et al., “Development of a Packet-Switching Network for Library Automation,” Proceedings of The National Online Meeting Apr. 12-14, 1983, pp. 67-74.Applicant
- Brownrigg et al., “Electrons, Electronic Publishing, and Electronic Display,” Information Technology and Libraries (Sep. 1985), pp. 201-207.Applicant
- Brownrigg et al., “Implementing Library Automation Plans in a University Computing Environment, Planning for Computing in Higher Education 5,” EDUCOM Series in Computing and Telecommunications in Higher Education, 1980, pp. 215-225.Applicant
- Brownrigg et al., “Online Catalogues: Through a Glass Darkly,” Information Technology and Libraries, Mar. 1983, pp. 104-115.Applicant
- Brownrigg et al., “Packet Radio for Library Automation,” Information Technology and Libraries 3 (Sep. 1984), pp. 229-244.Applicant
- Brownrigg et al., “Packet Switching and Library Automation: A Management Perspective,” Proceedings of the 45th ASIS Annual Meeting Oct. 17-21, 1982, vol. 19, pp. 54-57.Applicant
- “Hai Omni: Features & Specifications,” Home Automation, Inc. (archived web page), 1997.Applicant
- “Home Telemetry Gateway Specifications Sheet: Connector 2000 Series,” Coactive 1998.Applicant
- “How Does the New Power Company Deliver on the Promise of Energy Reconstructing?” NewPower (press release), Author: unknown, May 31, 2001, pp. 1-6.Applicant
- “IEEE Standards Board: Project Authorization Request (PAR) Form;” http://grouper.ieee.org/groups/802/11/PARs/par80211bapp.html, Mar. 24, 1998.Applicant
- “Important Dealer Notification—Honeywell AlarmNet-M Network Alert,” Source: unknown, Author: unknown, Apr. 2007, p. 1.Applicant
- “inCode Telecom Transforming Payphones into Wi-Fi Hot Spots,” Jan. 14, 2003, http://www.pocketpcmag.com/news/incode.asp (2 pages).Applicant
- “Industrial Communications,” Author: unknown, available at http://web.archive.org/web/19990222162354/www.metricom.com/industrial/ on May 10, 2010, pp. 1-3.Applicant
- “Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications,” Author: unknown, IEEE, Std. 802.11-1997, 1997, pp. 1-445.Applicant
- “Integrated Communication Services” of Industrial Communications; pp. 1-3; available at web.archive.org/web/19990222162354/www.metricom.com/industrial, 1999.Applicant
- “International Search Report and Written Opinion for International Application No. PCT/US2006/002342,” Search Authority European Patent Office, mailed May 31, 2006.Applicant
- “IOConnect Architecture™, ” Coactive, 2001, pp. 1-4.Applicant
- “JC/83RF System: Cost-effective Multiple Facility Management by Radio Network,” Johnson Controls, Date: unknown, pp. 1-6.Applicant
- “JC/83RF System: Multiple Facility Management by Radio Network,” Johnson Controls, Publication No. 2161, 1983, pp. 1-4.Applicant
- “Keltron's Home Page with Frames, Index,” available at http://web.archive.org/web/19990831161957/http://www.keltroncorp.com, on Mar. 24, 2009, p. 1.Applicant
- “Local and Metropolitan Area Networks: Wireless Medium Access Control (MAC) and Physical (PHY) Specifications, Annex A: Protocol Implementation Conformance Statement (PICS) Proforma,” Author: unknown; IEEE, Nov. 1997, pp. 1-75.Applicant
- “LonTalk Protocol, LonWorks™ Engineering Bulletin,” Echelon Corp.; Author: unknown; Apr. 1993, pp. 1-27.Applicant
- “LonWorks® Products, 1998, Version A,” Echelon Corp.; Author: unknown; 1997, pp. 1-21.Applicant
- “LonWorks® Router User's Guide,” Echelon Corp., Author: unknown; 1995, pp. 1-136.Applicant
- “LonWorks® SMX™ Transceiver,” datasheet, Echelon Corp.; Author: unknown; 1997, pp. 1-18.Applicant
- “M100 Series Motor Actuator,” Author: unknown, Johnson Controls, Inc., Apr. 1993, pp. 1-20.Applicant
- “M100C Series Actuator with Digital Control Signal Input and R81CAA-2 Interface Board,” Installation Bulletin, Johnson Controls, 2000, pp. 1-12.Applicant
- “Man-Portable Networked Sensor System (1997—),” Author: unknown, available at http://www.spawar.navy.mil/depts/d30/d37/d371/mpnss/mpnss.html on May 20, 2010, pp. 1-4.Applicant
- “March of the Motes,” Author: unknown, New Scientist, vol. 179, issue 2409, Aug. 23, 2003, pp. 1-8.Applicant
- “Metasys Compatible Products,” Author: unknown; Johnson Controls, Inc., 1997 (9 pages).Applicant
- “Metasys Extended System Architecture, vol. II,” Author: unknown, Publisher: unknown, Sep. 1999.Applicant
- “Metasys N2 System Protocol Specification for Vendors,” Author: unknown, Publisher: unknown, Jun. 1996.Applicant
- “Modicon Interfacing,” Author: unknown, Engineering Report, No. 90-022, Revised: Apr. 12, 1996, pp. 1-9.Applicant
- “Moore Products—Hart Protocol Interfacing,” Author: unknown, Engineering Report, No. 94-007, Revised: Mar. 1, 1996, pp. 1-3.Applicant
- “MTC Teams with Coactive Networks to Deliver an Advanced Energy Communications and Management Solution,” Coactive (press release), Author: unknown, Feb. 5, 2001, pp. 1-4.Applicant
- “Net77 Central Station Manual Section 3,” AES Intellinet, Dec. 1996.Applicant
- “NewPower and Coactive Networks Announce Strategic Alliance to Deliver the Connected Home,” Coactive (press release), Author: unknown, Mar. 14, 2001, pp. 1-4.Applicant
- “NX-480 Wireless Motion Sensor, document No. 466-1479 Rev. D,” Caddx Controls, May 1, 1998.Applicant
- “Omni Automation System,” Author: unknown, Home Automation, Inc., Date: unknown, pp. 1-266.Applicant
- “Omni Installation Manual,” Author: unknown; Home Automation, Inc., Oct. 1997, pp. 1-88.Applicant
- “Omni Owner's Manual,” Author: unknown; Home Automation, Inc., Date: unknown, pp. 1-136.Applicant
- “Omron Interfacing,” Author: unknown, Engineering Report, No. 95-003, Revised: Apr. 17, 1996, pp. 1-4.Applicant
- “Opto-22 Protocol,” Author: unknown, Engineering Report, No. 93-010, Revised: May 31, 1996, pp. 1-8.Applicant
- “Part 15.1: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Wireless Personal Area Networds (WPANS),” www.ieee802.org/15/Bluetooth/802-15-1—Clause—05.pdf, Jun. 14, 2002.Applicant
- “Phoenix Contact Interfacing, Author: unknown,” Engineering Report, No. 94-001, Revised: Jun. 20, 1996, pp. 1-7.Applicant
- “Phonelin / HPNA / HomePNA Networks,” http://www.homenethelp.com/web/howto/HomeNet-HPNA.asp (visited Jul. 29, 2003) (3 pages).Applicant
- “PLC Direct (Koyo) Interfacing, Author: unknown,” Engineering Report, No. 96-001, Revised: Apr. 10, 1996, pp. 1-8.Applicant
- “Power/Perfect Energy Management Systems,” Author: unknown, Johnson Controls, 1983, pp. 1-4.Applicant
- “Selected Vendor Telecommunications Products,” available at http://eetd.lbl.gov/ea/ems/reports/39015a.pdf (describing public uses in 1995), pp. 1-83.Applicant
- “Smart Home Technology Leader Intelli Selects Coactive Networks Internet Gateways,” Coactive (press release), Author: unknown, Sep. 11, 2000, pp. 1-4.Applicant
- “Special Poll Feature,” Author: unknown, Engineering Report, No. 93-008, Sep. 1993, pp. 1-5.Applicant
- “Square D Interfacing,” Author: unknown, Engineering Report, No. 88-010, Revised: Apr. 18, 1996, pp. 1-9.Applicant
- “Technology Review, Metricom's Ricochet Packet Radio Network,” Ham Radio Online, 1996, Author: unknown, pp. 1-3.Applicant
- “Texas Instruments Interface,” Author: unknown, Engineering Report, No. 91-021, Revised: Nov. 1994, pp. 1-3.Applicant
- “The New Power Company Announces Revolutionary Energy-Saving Program the Gives Consumers Remote Control of the Their Thermostats via the Internet,” NewPower (press release), Author: unknown, Apr. 24, 2001.Applicant
- “The SNVT Master List and Programmer's Guide,” Echelon Corp., Author: unknown, Mar. 1996, pp. 1-23.Applicant
- to Starbucks and beyond: 802.11 wireless Internet access takes off, CommunicationsSolutions.com, vol. 4, Issue 1, Q1 2003, pp. 8-9.Applicant
- “Toshiba Interfacing,” Author: unknown, Engineering Report, No. 91-011, Revised: Jun. 19, 1996, pp. 1-4.Applicant
- “TranstexT® Advanced Energy Management System,” Article, Author: unknown, Publisher: unknown, Date: unknown, pp. 1-2.Applicant
- “TranstexT® Advanced Energy Management System,” Brochure, Author: unknown, Integrated Communication Systems, Inc., 1990, pp. 1-8.Applicant
- 90-008011 Request for Ex Parte Reexamination of 6,044,062.Applicant
- 90-008011 Grant of Reexamination Request.Applicant
- 90-008011 Non-Final Office Action dated Nov. 19, 2007.Applicant
- 90-008011 Final Office Action dated Aug. 13, 2008.Applicant
- 90-010301 Request for Ex Parte Reexamination of 6,891,838.Applicant
- 90-010315 Request for Ex Parte Reexamination of 7,103,511.Applicant
- 90-010315 Petition to Review Denial of Request for Reexamination.Applicant
- 90-010507 Request for Ex Parte Reexamination of 7,103,511.Applicant
- 90-010509 Request for Ex Parte Reexamination of 7,103,511.Applicant
- 90-010510 Request for Ex Parte Reexamination of 6,891,838.Applicant
- 90-010505 Substitute Request for Ex Parte Reexamination of 7,103,511.Applicant
- 90-010507 Substitute Request for Ex Parte Reexamination of 7,103,511.Applicant
- 90-010508 Substitute Request for Ex Parte Reexamination of 7,103,511.Applicant
- 90-010509 Substitute Request for Ex Parte Reexamination of 7,103,511.Applicant
- 90-010510 Substitute Request for Ex Parte Reexamination of 6,891,838.Applicant
- 90-010511 Substitute Request for Ex Parte Reexamination of 6,891,838.Applicant
- 90-010512 Substitute Request for Ex Parte Reexamination of 6,891,838.Applicant
- 90-010301 Non-Final Office Action dated Dec. 2, 2009.Applicant
- 90-010315 Denial of Petition to Review Denial of Request for Reexamination.Applicant
- 90-010505 Non-Final Office Action dated Mar. 3, 2010.Applicant
- 90-010507 Non-Final Office Action dated Mar. 3, 2010.Applicant
- 90-010508 Non-Final Office Action dated Mar. 3, 2010.Applicant
- 90-010509 Non-Final Office Action dated Mar. 3, 2010.Applicant
- 90-008011 Examiner Answer to Appeal Brief.Applicant
- 90-010505 Final Office Action dated Aug. 2, 2010.Applicant
- 90-010507 Final Office Action dated Aug. 2, 2010.Applicant
- 90-010508 Final Office Action dated Aug. 2, 2010.Applicant
- 90-010509 Final Office Action dated Aug. 2, 2010.Applicant
- 90-010510 Final Office Action dated Aug. 20, 2010.Applicant
- 90-010511 Final Office Action dated Aug. 20, 2010.Applicant
- 90-010512 Final Office Action dated Aug. 20, 2010.Applicant
- 90-010301 Final Office Action dated Nov. 5, 2010.Applicant
- 90-010510 Final Office Action dated Nov. 5, 2010.Applicant
- 90-010511 Final Office Action dated Nov. 5, 2010.Applicant
- 90-010512 Final Office Action dated Nov. 5, 2010.Applicant
- 90-008011 BPAI Decision.Applicant
- 90-010510 Non-Final Office Action dated Dec. 2, 2009.Applicant
- 90-010511 Non-Final Office Action dated Dec. 2, 2009.Applicant
- 90-010512 Non-Final Office Action dated Dec. 2, 2009.Applicant
- 90-010301 Notice of Intent to Issue Reexam Certificate dated Dec. 13, 2010.Applicant
- Lister's Initial Disclosure of Invalidity Contentions Pursuant to LPR 4.3; IPOC, LLC v. Elster Electricity, LLC, Northern District of Georgia Case No. 1:05-cv-1138 (183 pages).Applicant
- Lister's First Supplement to its Initial Disclosure of Invalidity Contentions Pursuant to LPR 4.3; IPCO, LLC v. Elster Electricity, LLC, Northern District of Georgia Case No. 1:05-cv-1138 (154 pages).Applicant
- Lister's Second Supplemental to its Initial Disclosure of Invalidity Contentions Pursuant to LPR 4.3; IPCO, LLC v. Elster Electricity, LLC Northern District of Georgia Case No. 1:05-cv-1138 (111 pages).Applicant
- Defendant's Joint Preliminary Invalidity Contentions filed by Defendants Crestron Electronics, Inc. and Wayne-Dalton Corporation in SIPCO, LLC v. AMAZON.COM, Inc. et al., District Court for the Eastern District of Texas Case No. 2:08-cv-359 (180 pages).Applicant
- Trilliant Network, Inc.'s Invalidity Contentions Pursuant to Patent Rule 3-3, IP Co. LLC v. Oncor Electric Delivery Company LLC et al., District Court for the Eastern District of Texas Case No. 2:09-cv-37 (112 pages).Applicant
- Sensus's Invalidity Contentions filed by Defendant Sensus USA Inc. In SIPCO, LLC v. SENSUS USA Inc., District Court for the Eastern District of Texas Case No. 2:09-cv-37 (21 pages).Applicant
- Defendant EKA Systems, Inc.'s Invalidity Contentions, IP Co. LLC v. Oncor Electric Delivery Company LLC et al., District Court for the Eastern District of Texas Case No. 2:09-cv-37 (110 pages).Applicant
- EKA Systems, Inc.'s Invalidity Contentions Pursuant to Patent Rule 3-3, IP CO. LLC v. Oncor Electric Delivery Company LLC et al., District Court for the Eastern District of Texas Case No. 2:09-cv-37 (110 pages).Applicant
- Sensus's Invalidity Contentions filed by Defendant Sensus USA Inc. In SIPCO, LLC v. SENSUS USA Inc., District Court for the Eastern District of Texas Case No. 6:09-cv-532 (22 pages).Applicant
- Defendant Datamatic, Ltd's Invalidity Contentions to Plaintiff, SIPCO, LLC v. DATAMATIC Ltd, et al., District Court for the Eastern District of Texas Case No. 6:09-cv-532 (2 pages with 7 claim chart exhibits).Applicant
- Johnson Controls, Inc.'s Invalidity Contentions and Disclosures Pursuant to P.R. 3-3 and 3-4, SIPCO, LLC v. DATAMATIC Ltd, et al., District Court for the Eastern District of Texas Case No. 6:09-cv-532 (59 pages).Applicant
- Trilliant Networks, Inc.'s Invalidity Contentions to Plaintiff, SIPCO, LLC v. DATAMATIC Ltd, et al., District Court for the Eastern District of Texas Case No. 6:09-cv-532 (418 pages).Applicant
- Defendant Datamatic, Ltd's Invalidity Contentions to Plaintiff Pursuant to P.R. 3-3(a), SIPCO LLC v. DATAMATIC Ltd, et al., District Court for the Eastern District of Texas Case No. 6:09-cv-532 (2 pages with 7 claim chart exhibits).Applicant
- Johnson Controls, Inc.'s Supplement Letter to the Invalidity Contentions, SIPCO, LLC v. DATAMATIC Ltd, et al., District Court for the Eastern District of Texas Case No. 6:09-cv-532 (5 pages and 99 page Addendum).Applicant
- Defendant's Invalidity Contentions Pursuant to P.R. 3-3 and 3-4 filed by Control4 Corporation et al., SIPCO, LLC v. Control4Corporation, Eastern District of Texas Case No. 6:10-cv-249 (85 pages).Applicant
- Johnson Controls, Inc.'s Supplemental Invalidity Contentions and Disclosures Pursuant to P.R. 3-3 and 3-4, SIPCO, LLC v. DATAMATIC Ltd, et al., District Court for the Eastern District of Texas Case No. 6:09-cv-532 (89 pages).Applicant
- Defendant Toro Company's Motion for Summary Judgment of Invalidity, Sipco, LLC v. The Toro Company, JLH LABS, LLC and Jason Hill, District Court for the Eastern District of Pensylvania Case No. 08-Cv-00505-TJS.Applicant
- Kaiser, “Embedded Wireless Devices: Sensors,” Outline, École Polytechnique Fédérale de Lausanne, pp. 1-53.Applicant
- Kaiser, “Embedded Wireless Devices: Signal Processing,” Outline, École Polytechnique Fédérale de Lausanne, pp. 1-19.Applicant
- Kaiser, “Embedded Wireless Devices: Wireless Networking,” Outline, École Polytechnique Fédérale de Lausanne, pp. 1-16.Applicant
- Kaiser, “Embedded Wireless Devices: Wireless Physical Layer,” Outline, École Polytechnique Fédérale de Lausanne, pp. 1-29.Applicant
- Karn et al., “Packet Radio in the Amateur Service,” IEEE Journal on Selected Areas in Communications, vol. SAC-3, No. 3, May 1985, pp. 431-439.Applicant
- Katz et al., “The Bay Area Research Wireless Access Network (BARWAN)” (Jun. 1996) (presentation paper), http://daedalus.cs.berkeley.edu/talks/retreat.6.97/BARWAN.597.ppt, pp. 1-66.Applicant
- Lynch et al., “The Telecommunications Landscape: 1986,” Library Journal, Oct. 1, 1986, pp. 40-46.Applicant
- Katz et al., “Towards a Wireless Overlay Internetworking Architecture”, DARPA ITO Sponsored Research, 1997 Project Summary, University of California, Berkeley, pp. 1-8, Including a Slide Show Presentation of 56 Pages at http://daedalus.cs.berkeley.edu/talks/retreat.6.96/overview.pdf.Applicant
- Kemp, “Home Automation Application Guide,” Applications for Home Automation in Any Home, vol. 1, 2000, pp. 1-106.Applicant
- Kleinrock et al., “Hierarchical Routing for Large Networks, Performance Evaluation, and Optimization,” Computer Networks 1 (1977), pp. 155-174.Applicant
- Kocom, “Digital Home Network, Kitchen TV Phone KTD-505, User's Manual,” pp. 1-7.Applicant
- Kohno et al., “An Adaptive Sensor Network System for Complex Environments in Intelligent Autonomous Systems (Kakazu et al., eds.),” IOS Press, 1998, pp. 21-28.Applicant
- Kooser et al., “Testing 1-2-3,” Entrepreneur Magazine, Sep. 2003, pp. 27-30.Applicant
- Krishnamachari, “Networking Wireless Sensors,” Cambridge University Press, Date: unknown, pp. 1-10.Applicant
- Krishnamachari, “Wireless Sensor Networks: the Vision;” Cambridge University Press; pp. 1-10.Applicant
- Lacoss, “Distributed Sensor Networks, Final Report,” Lincoln Laboratory at Massachusetts Institute of Technology, Sep. 30, 1986, pp. 1-225.Applicant
- Lauer et al., “Survivable Protocols for Large Scale Packet Radio Networks,” IEEE Global Telecommunications Conference, Nov. 26-29, 1984, vol. 1 of 3, pp. 468-471.Applicant
- Lauer, “Packet-Radio Routing, Routing in Communications Networks,” Ch. 11 (1995) pp. 351-396.Applicant
- Lee et al., “Distributed Measurement and Control Based on the IEEE 1451 Smart Transducer Interface Standards,” Proceedings of the 16th IEEE Instrumentation and Measurement Technology Conference, vol. 1, May 24-26, 1999, IEEE, pp. 608-613.Applicant
- Leiner et al., “Goals and Challenges of the DARPA GloMo Program ;” IEEE Personal Communications; Dec. 1996, vol. 3, No. 6; pp. 34-45.Applicant
- Leviton Manufacturing Co., Inc., “The DECORA® Collection of Designer Devices,” 2006, pp. 1-85.Applicant
- Lewis et al., “Packet-Switching Applique for Tactical VHF Radios,” 1987 IEEE Military Communications Conference, Oct. 19-22, 1987, Conference Record vol. 2 of 3, pp. 449-455.Applicant
- Lin et al., “Adaptive Clustering for Mobile Wireless Networks;” Publisher: unknown; Date: unknown; pp. 1-21.Applicant
- Lin et al., “CMOS Front End Components for Micropower RF Wireless Systems;” EED, UCLA Electrical Engineering Department; 1998, pp. 1-5.Applicant
- Lin et al., “Wireless Integrated Network Sensors (WINS) for Tactical Information Systems,” UCLA, Rockwell Science Center; Date: unknown; pp. 1-5.Applicant
- Linear Corporation, “Supervised Digital Security Transmitter t-90, Installation Instructions,” 2006, pp. 1-2.Applicant
- Linear Corporation, “Supervised Digital Security Transmitters TX-91, TX-92, TX-94, Operation Instructions,” 1993, p. 1.Applicant
- Linear Corporation, “Supervised Wireless Receiver and Zone Expander SRX-64A, Installation Instructions,” 2003, pp. 1-2.Applicant
- Local and Metropolitan Area Networks: Wireless Medium Access Control (MAC) and Physical (PHY) Specifications, Author: unknown; IEEE, Nov. 1997, pp. 1-98.Applicant
- Clare et al., “Self-Organizing Distributed Sensor Networks,” UCLA, Rockwell Science Center.Applicant
- Clare, “AWAIRS Progress Review: Planned Milestones,” UCLA Rockwell Science Center, Nov. 20, 1998.Applicant
- Lougheed et al., “A Border Gateway Protocol 3 (BGP-3),” RFC 1267, (Oct. 1991), available at http://tools.ietf.org/html/rfc1267, Jun. 24, 2009, pp. 1-36.Applicant
- Lowe et al., “Publishing Bibliographic Data on Optical Disks: A Prototypical Application and Its Implications,” Third International Conference on Optical Mass Data Storage, Proceedings of SPIE, vol. 529, pp. 227-236.Applicant
- Lutron Electronics Co. Inc., Connecting to a RadioRA System via a Local Area Network, Application Note #127, Date: unknown, pp. 1-16.Applicant
- Lutron Electronics Co. Inc., Homeowner's Guide for the RadioRA® Quick Start Package, 2004, pp. 1-8.Applicant
- Lutron Electronics Co. Inc., How to Retrofit RadioRA® Wall-Mounted Master Control into an existing home, Application #41, 2004, pp. 1-2.Applicant
- Lutron Electronics Co. Inc., Interfacing RadioRA ® to Security and Fire Alarm Systems, Application Note#59, pp. 1-4.Applicant
- Lutron Electronics Co. Inc., IR/RS232 Interface for Bang & Olufsen® Remote Control and RadioRA®, Application Note #119, 2004, pp. 1-3.Applicant
- Lutron Electronics Co. Inc., Level Capture with a RadioRA® Master Control, Application Note #73, 2003, pp. 1-3.Applicant
- Lutron Electronics Co. Inc., Modem Installation for HomeWorks®, Application Note #9, 1998, pp. 1-4.Applicant
- Lutron Electronics Co. Inc., RadioRA® RA-IR-KIT Installation Instructions, Application Note #61, 2000, pp. 1-4.Applicant
- Lutron Electronics Co. Inc., RadioRA® RF Signal Repeater, 1998, pp. 1-2.Applicant
- Lutron Electronics Co. Inc., RadioRA® Single-Location Switch, Controls for Permanently Installed Lighting Loads, 1998, pp. 1-2.Applicant
- Lutron Electronics Co. Inc., RadioRA® Table Lamp Controls, Dimming and Switching Controls for Table and Floor Lamps, 1999, pp. 1-2.Applicant
- Lutron Electronics Co. Inc., Using a Photocell with the RadioRA® System, Application Note #45, 1998, pp. 1-4.Applicant
- Lutron Electronics Co. Inc., Using an Astronomic Timeclock with the RadioRA® System, Application Note #42, 1998, pp. 1-2.Applicant
- Lutron Electronics Co. Inc., Using the RadioRA® System to Activate Scenes 5-16 on a GRAFIK Eye® Control Unit, Application Note #48, 1998, pp. 1-4.Applicant
- Lutron Electronics Co. Inc., Using the RadioRA® Telephone Interface, Application Note #46, 1998, pp. 1-2.Applicant
- Lynch et al., “Application of Data Compression Techniques to a Large Bibliographic Database,” Proceeding of the Seventh International Conference on Very Large Databases, Cannes, France, Sep. 9-11, 1981 (Washington, DC: IEEE Computer Society Press, 1981), pp. 435-447.Applicant
- Lynch et al., “Beyond the Integrated Library System Concept: Bibliographic Networking at the University of California,” Proceedings of the Second National Conference on Integrated Online Library Systems Proceedings, Sep. 1984, pp. 243-252.Applicant
- Lynch et al., “Conservation, Preservation and Digitization, Energies for Transition,” Proceedings of the Fourth National Conference of the Association of College and Research Libraries, Baltimore, MD, Apr. 9-12, 1986 (Chicago, IL: Association of College and Research Libraries, 1986), pp. 225-228.Applicant
- Lynch et al., “Document Delivery and Packet Facsimile,” Proceedings of the 48th ASIS Annual Meeting, vol. 22, Oct. 20-24, 1985, pp. 11-14.Applicant
- Lynch et al., “Electronic Publishing, Electronic Imaging, and Document Delivery, Electronic Imaging '86,” (Boston, MA: Institute for Graphic Communication, Inc., 1986), pp. 662-667.Applicant
- Lynch et al., “Library Applications of Electronic Imaging Technology,” Information Technology and Libraries, Jun. 1986, pp. 100-105.Applicant
- Lynch et al., “Packet Radio Networks: Architectures, Protocols, Technologies and Applications,” Pergamon Press, 1ed., 1987, pp. 1-275.Applicant
- Lynch et al., “Public Access Bibliographic Databases in a Multicampus University Environment, Databases in the Humanities and Social Sciences—4,” Proceedings of the International Conference on Databases in the Humanities and Social Sciences, Jul. 1987, Learned Information, Inc., 1989, pp. 411-419.Applicant
- ADEMCO Group, Vista 4130XT Security System Installation Instructions, Oct. 1998, ADEMCO Group, Author: unknown, pp. 1-84.Applicant
- ADEMCO Group, Vista 4140XMPT2 Partitioned Security System with Scheduling Installation Instructions, May 1993, ADEMCO Group, Author: unknown, pp. 1-68.Applicant
- ADEMCO Group, Vista AT 4140 Security System Installation Instructions, Sep. 1998, ADEMCO Group, Author: unknown, pp. 1-68.Applicant
- ADEMCO Group, Vista Series 4120EC Security System User's Manual, Sep. 1992, ADEMCO Group, Author: unknown, pp. 1-28.Applicant
- ADEMCO Group, Vista Series 4130XM, 5130XM, 4140XMP Security System User's Manual, Feb. 1992, ADEMCO Group, Author: unknown, pp. 1-32.Applicant
- ADEMCO Group, Vista Series 4140XMPT/4140XMPT-UL Partitioned Security System User's Manual, Jun. 1993, ADEMCO Group, Author: unknown, pp. 1-32.Applicant
- ADEMCO Group, Vista Series 4140XMP, Installation Instructions, Jan. 1992, ADEMCO Group, Author: unknown, pp. 1-52.Applicant
- ADEMCO Group, Vista Series 5140XM User's Manual, Aug. 1992, ADEMCO Group, Author: unknown, pp. 1-28.Applicant
- ADEMCO Group, Vista XM Series 4140XM, 5130XM, 4130XM, Installation Instructions, Jul. 1990, ADEMCO Group, Author: unknown, pp. 1-26.Applicant
- ADEMCO Group, Vista XM Series, Installation Instructions, ADEMCO Group, Author: unknown, Oct. 1991, pp. 1-16.Applicant
- ADEMCO Group, Vista-10 Security System, Installation Instructions, Sep. 1994, ADEMCO Group, Author: unknown, pp. 1-56.Applicant
- ADEMCO Group, Vista-100 Commercial Fire & Burglary Alarm Partitioned Security System with Scheduling, Installation Instructions and Programming Guide, Jan. 1998, ADEMCO Group, Author: unknown, pp. 1-233.Applicant
- ADEMCO Group, Vista-100 Commercial Fire & Burglary Alarm System User's Manual, Nov. 1995, ADEMCO Group, Author: unknown, pp. 1-66.Applicant
- ADEMCO Group, Vista-100 Commercial Fire & Burglary Alarm System with Scheduling Quick Start, Apr. 1996, ADEMCO Group, Author: unknown, pp. 1-24.Applicant
- ADEMCO Group, Vista-10SE Security System, Installation Instructions, May 1997, ADEMCO Group, Author: unknown, pp. 1-88.Applicant
- ADEMCO Group, Vista-128B Commercial Burglary Partitioned Security System with Scheduling, Installation and Setup Guide, Jul. 1998, ADEMCO Group, Author: unknown, pp. 1-252.Applicant
- ADEMCO Group, Vista-128FB Commercial Fire and Burglary Partioned Security System with Scheduling, Installation, and Setup Guide, Oct. 1998, ADEMCO Group, Author: unknown, pp. 1-220.Applicant
- ADEMCO Group, Vista-128FB Commercial Fire and Burglary Partitioned Security System User Guide, Oct. 1998, ADEMCO Group, Author: unknown, pp. 1-80.Applicant
- ADEMCO Group, Vista-20 2-Partitioned Security System, Installation Instructions, Nov. 1995, ADEMCO Group, Author: unknown, pp. 1-120.Applicant
- ADEMCO Group, Vista-20 2-Partitioned Security System, Programming Form, Apr. 1996, ADEMCO Group, Author: unknown, pp. 1-8.Applicant
- ADEMCO Group, Vista-20 Security System User's Manual, Apr. 1995, ADEMCO Group, Author: unknown, pp. 1-52.Applicant
- ADEMCO Group, Vista-20HW 2-Partitioned Security System, Installation Instructions, Apr. 1996, ADEMCO Group, Author: unknown, pp. 1-100.Applicant
- ADEMCO Group, Vista-20HW 2-Partitioned Security System, Programming Form, Apr. 1996, ADEMCO Group, Author: unknown, pp. 1-8.Applicant
- ADEMCO Group, Vista-20HWse 2-Partitioned Security System, Installation Instructions, Aug. 1997, ADEMCO Group, Author: unknown, pp. 1-84.Applicant
- ADEMCO Group, Vista-20HWse 2-Partitioned Security System, Programming Form, Aug. 1997, ADEMCO Group, Author: unknown, pp. 1-8.Applicant
- ADEMCO Group, Vista-20SE 2-Partitioned Security System, Installation Instructions, Aug. 1997, ADEMCO Group, Author: unknown, pp. 1-100.Applicant
- ADEMCO Group, Vista-20SE 2-Partitioned Security System, Programming Guide, Aug. 1997, ADEMCO Group, Author: unknown, pp. 1-8.Applicant
- ADEMCO Group, Vista-20SE/Vista-20HWse Security System User's Manual, Jun. 1997, ADEMCO Group, Author: unknown; pp. 1-52.Applicant
- ADEMCO Group, Vista-30Pse Security System, Installation Instructions, Apr. 1997, ADEMCO Group, Author: unknown; pp. 1-104.Applicant
- ADEMCO Group, Vista-40 2-Partition Security System, Installation and Setup Guide, Jul. 1998, ADEMCO Group, Author: unknown; pp. 1-380.Applicant
- ADEMCO Group, Vista-40 2-Partition Security System, Programming Guide, Jul. 1998, ADEMCO Group, Author: unknown; pp. 1-24.Applicant
- ADEMCO Group, Vista-40 Programming Guide, Jun. 1997, ADEMCO Group, Author: unknown; available at www.guardianalarms.net pp. 1-20.Applicant
- ADEMCO Group, Vista-40 Security System User's Guide, Jul. 1998, ADEMCO Group, Author: unknown; pp. 1-60.Applicant
- ADEMCO Group, Vista-50, Vista 50UL Security System, Nov. 1994, ADEMCO Group, Author: unknown; pp. 1-66.Applicant
- ADEMCO Group, Vista-50P, Vista-50PUL Partitioned Security System with Scheduling, Installation Instructions and Programming Guide, Oct. 1997, ADEMCO Group, Author: unknown; pp. 1-199.Applicant
- ADEMCO Group, Vista-50P, Vista-50PUL Security System User's Manual, Jul. 1995, ADEMCO Group, Author: unknown; pp. 1-66.Applicant
- ADEMCO Group, Vista-50P, Vista-50PUL, Partitioned Security System with Scheduling, Quick Start, Aug. 1995, ADEMCO Group, Author: unknown; pp. 1-28.Applicant
- ADEMCO Group, Vista5140XM Commercial Fire and Burglary Alarm System Installation Instructions, Jun. 1993, ADEMCO Group, Author: unknown, pp. 1-74.Applicant
- ADEMCO Group, Vista-At Security System User's Manual, Sep. 1998, ADEMCO Group, Author: unknown; pp. 1-56.Applicant
- ADEMCO Group, V-Link Downloading Software User's Guide, Jun. 1994, ADEMCO Group, Author: unknown; available at http://www.guardianalarms.net, pp. 1-126.Applicant
- ADEMCO Group, V-Plex Security Technology, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990421110527/www.ademco.com/ademco on Mar. 5, 2009, pp. 1-6.Applicant
- ADEMCO Group, Wireless Transmitters/Receivers: 5700 Wireless Transmitters, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990127120423/www.ademco.com/ademco on Mar. 5, 2009, pp. 1-2.Applicant
- ADEMCO Group, Wireless Transmitters/Receivers: 5800 Wireless Transmitters, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990218181254/www.ademco/com/ademco on Mar. 5, 2009, pp. 1-2.Applicant
- ADEMCO Group, Wirelss User Interface Devices, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990421190353/www.ademco.com/ademco on Mar. 5, 2009, pp. 1-4.Applicant
- ADEMCO Group,Vista Series Partitioned Security Systems Model 4140XMPT Installation Instructions, Feb. 1992, ADEMCO Group, Author: unknown, pp. 1-60.Applicant
- AES—7700 Central Station, Installation & Operation Manual, Document 40/0551u, AES Corporation, Author: unknown, Nov. 2003, pp. 1-40.Applicant
- AES— IntelliGuard 7470, AES IntelliNet, Author: unknown, Nov. 2003, pp. 1-15.Applicant
- AES 7000 Smart Central Station InstaCentral Station Installation & Operation Manual, Document No. 40-551, AES IntelliNet, Author: unknown; Nov. 20, 1996, pp. 1-48.Applicant
- AES 7067 IntelliTap-II Digital Dialer Interface: A Supplemental Alarm Supporting Device, AES IntelliNet, Author: unknown, Aug. 5, 2004, pp. 1-4.Applicant
- AES 7099 Central Station Installation & Operation Manual, Document No. 40-0050, AES IntelliNet, Author: unknown; 1998, pp. 1-20.Applicant
- AES 7450 RF Subscriber Unit Installation Manual, AES IntelliNet, Author: unknown, 1998, pp. 1-8.Applicant
- AES 7750-F RF SMART Subscriber Unit Version 2, Including 7750-F-4x4 and 7750-F-8, Installation & Operation Manual, AES IntelliNet, Author: unknown, Apr. 2001 (Updated Nov. 2003), pp. 1-60.Applicant
- AES 7750-F RF SMART Subscriber Unit Version 2, Installation & Operation Manual, AES IntelliNet, Author: unknown, Aug. 2000, pp. 1-30.Applicant
- AES Central Alarm Monitoring, Author: unknown, available at http://web.archive.org/web/19990225163745/www.aes-intellinet.com/ae, on Mar. 5, 2009, pp. 1-3.Applicant
- AES IntelliNet 7450 Addendum, AES Corporation, Author: unknown, Jul. 9, 2002, pp. 1-2.Applicant
- AES IntelliNet Dealer's List by State, Author: unknown, available at http://web.archive.org/web/200102162324026/www.aes-intellinet.com/list on Mar. 5, 2009, pp. 1-13.Applicant
- AES IntelliNet Model 7003 Central Station, Installation & Operation Manual, AES IntelliNet, Author: unknown, Jan. 9, 2001, available at http://www.guardianalarms.net, pp. 1-25.Applicant
- AES IntelliNet Model 7050, 7750, Subscriber Unit, Version 1.62, Installation & Operation Manual, AES IntelliNet, Author: unknown, Dec. 1996, available at www.guardianalarms.net, pp. 1-110.Applicant
- “Wayport's Value Proposition: To provide the industry's best high-speed Internet and business center experience for the airport passenger to stay productive,” http://www.wayport.net/airportsoverview (visited Jul. 29, 2003) (2 pages).Applicant
- “Welcome to UtiliNet: A Wireless Data Communications Solution from Metricom, Inc.,” Author: unknown, available at http://web.archive.org/web/199806028045812/www.metricom.com/industrial/utilinet.html on May 10, 2010, pp. 1-10.Applicant
- “Westinghouse Numa Logic Interface,” Author: unknown, Engineering Report, No. 91-013, Date: unknown, pp. 1-7.Applicant
- “What's Behind Ricochet: A Network Overview,” Author: unknown, available at http://web.archive.org/web/20000815090824/www.ricochet.com/ricochet—advantage/tech—overview.html, Aug. 15, 2000, pp. 1-4.Applicant
- “Wireless Access List—Atlanta Hartsfield International Airport,” http://www.ezgoal.com/hotsports/wireless/f.asp?fid=63643 (visited Jul. 29, 2003) (1 page).Applicant
- “Wireless Access List -0 ATL Admirals Club,” http://www.ezgoal.com/hotspots/wireless/f.asp?fid=60346 (visited Jul. 29, 2003) (1 page).Applicant
- “Wireless Accessories, catalog pages,” Home Automation, Inc (archived web page), 1997.Applicant
- “ESTeem Model 96C,” ESTeem Radios (describing a system that was for sale at least as early as 1994).Applicant
- “Site Survey Report,” ESTeem Radios, Sep. 24, 1993.Applicant
- “Technical Bulletin—Johnson Controls,” ESTeem Radios, Jan. 29, 1998.Applicant
- Abbott et al., “Wireless Product Applications for Utilities,” Electric Power Research Institute, Feb. 1996, pp. 1-137.Applicant
- About AES Corporation, AES IntelliNet, Author: unknown, available at http://web.archive.org/web/19990127093116/www/aes-intellinet.com/ae, on Mar. 5, 2009, pp. 1-2.Applicant
- ADEMCO Group, 7720NX Network Extender,ADEMCO Group, Author: unknown, 1998; pp. 1-2.Applicant
- ADEMCO Group, 4110DL Security System, Installation Instructions, Oct. 1996, ADEMCO Group, Author: unknown, pp. 1-15.Applicant
- ADEMCO Group, 4110XM Security System, Installation Instructions, Jul. 1996, ADEMCO Group, Author: unknown, pp. 1-20.Applicant
- ADEMCO Group, 4120EC Security System, Installation Instructions, Nov. 1990, ADEMCO Group, Author: unknown, pp. 1-17.Applicant
- ADEMCO Group, 4120XM Security System, Installation Instructions, Oct. 1993, ADEMCO Group, Author: Unknown, pp. 1-80.Applicant
- ADEMCO Group, 4140XMPT2 Partitioned Security System with Scheduling User's Manual, May 1993, ADEMCO Group, Author: unknown; pp. 1-54.Applicant
- ADEMCO Group, 4281, 5881, and 5882 Series RF Receivers Installation Instructions, Oct. 1996, ADEMCO Group, Author: unknown; pp. 1-6.Applicant
- ADEMCO Group, 5330 Alpha Console, Installation Instructions, May 1990, ADEMCO Group, Author: unknown, pp. 1-24.Applicant
- ADEMCO Group, 5706 Smoke Detector with Built-In Wireless Transmitter, Installation Instructions, Dec. 1991, ADEMCO Group, Author: unknown, pp. 1-8.Applicant
- ADEMCO Group, 5707 Smoke Detector with Built-in Wireless transmitter, Installation Instructions, Aug. 1992, ADEMCO Group, Author: unknown, pp. 1-12.Applicant
- ADEMCO Group, 5715 Universal Transmitter, Installation Instructions, Mar. 1989, ADEMCO Group; Author: unknown; pp. 1-4.Applicant
- ADEMCO Group, 5775 Passive Infrared Motion Detector/Transmitter, Installation Instructions, Jul. 1991, ADEMCO Group, Author: unknown; pp. 1-4.Applicant
- ADEMCO Group, 5808C Photoelectronic Smoke Detector with Built-In Wireless Transmitter Installation Instructions, 1998, ADEMCO Group, Author: unknown; pp. 1-4.Applicant
- ADEMCO Group, 5800TM Transmitter Module Installation Instructions, Apr. 1994, ADEMCO Group, Author: unknown; pp. 1.Applicant
- ADEMCO Group, 5801 Remote Wireless Panic Transmitter Installation Instructions, Apr. 1994, ADEMCO Group, Author: unknown; p. 2.Applicant
- ADEMCO Group, 5802CP Belt Clip Transmitter Installation Instructions, Nov. 1994, ADEMCO Group, Author: unknown; p. 1.Applicant
- ADEMCO Group, 5802MN, Supervised Miniature Transmitter Installation Instructions, Jan. 1995, ADEMCO Group, Author: unknown; p. 1.Applicant
- ADEMCO Group, 5802MN2 Supervised Miniature Transmitter Installation Instructions, Jun. 1997, ADEMCO Group, Author: unknown; p. 1.Applicant
- ADEMCO Group, 5803 Wireless Key Transmitter Installation Instructions, Nov. 1994, ADEMCO Group, Author: unknown, p. 2.Applicant
- ADEMCO Group, 5804 Wireless Key Transmitter Installation Instructions, Jul. 1995, ADEMCO Group, Author: unknown, p. 3.Applicant
- ADEMCO Group, 5804BD Bi-Directional Key Transmitter Installation Instructions, Apr. 1997, ADEMCO Group, Author: unknown, p. 4.Applicant
- ADEMCO Group, 5806 Smoke Detector with Built-In Wireless Transmitter Installation Instructions, May 1998, ADEMCO Group, Author: unknown, pp. 1-4.Applicant
- ADEMCO Group, 5807 Smoke Detector with Built-In Wireless Installation Instructions, May 1998, ADEMCO Group, Author: unknown, pp. 1-6.Applicant
- ADEMCO Group, 5808 Photoelectronic Smoke/Heat Detector with Built-In Wireless Transmitter Installation Instructions, 1998, ADEMCO Group, Author: unknown, pp. 1-8.Applicant
- ADEMCO Group, 5808 Wireless Smoke Detector, 1999, available at http://web.archive.org/web/20000118015507/www.ademco.com/ademco on Mar. 5, 2009 pp. 1-4.Applicant
- ADEMCO Group, 5809 Rate-of Rise Heat Detector/Transmitter Installation Instructions, Nov. 1994, ADEMCO Group, Author: unknown; pp. 1-2.Applicant
- ADEMCO Group, 5816 Door/Window Transmitter Installation Instructions, Nov. 1994, ADEMCO Group, Author: unknown; pp. 1-2.Applicant
- ADEMCO Group, 5816TEMP Low Temperature Transmitter Installation Instructions, May 1998, ADEMCO Group, Author: unknown; pp. 1-2.Applicant
- ADEMCO Group, 5818 Recessed Transmitter Installation Instructions, Jan. 1994, ADEMCO Group, Author: unknown; pp. 1-2.Applicant
- ADEMCO Group, 5819 Shock Processor Transmitter Installation Instructions, May 1998, ADEMCO Group, Author: unknown; pp. 1-2.Applicant
- ADEMCO Group, 5819WHS Wireless Shock Sensor and Processor, 1997, available at http://web.archive.org/web/19990428164624/www.ademco.com/ademco on Mar. 5, 2009, p. 1.Applicant
- ADEMCO Group, 5819WHS/5819BRS Shock Processor Transmitter Installation Instructions, May 1998, ADEMCO Group, Author: unknown; pp. 1-2.Applicant
- ADEMCO Group, 5827 Remote Wireless Keypad/Transmitter Installation Instructions, Apr. 1994, ADEMCO Group, Author: unknown; p. 1.Applicant
- ADEMCO Group, 5827BD and 5827BDE Wireless Bi-Directional Keypads Installation Instructions and Operating Guide, Mar. 1996, ADEMCO Group, Author: unknown; pp. 1-6.Applicant
- ADEMCO Group, 5849 Glass Break Detector/Transmitter Installation Instructions, Oct. 1997, ADEMCO Group, Author: unknown; pp. 1-4.Applicant
- ADEMCO Group, 5850 Glass Break Detector/Transmitter Installation Instructions, May 1998, ADEMCO Group, Author: unknown; pp. 1-4.Applicant
- ADEMCO Group, 5890 Passive Infrared Motion Detector/Transmitter Installation Instructions, May 1998, ADEMCO Group, Author: unknown; pp. 1-8.Applicant
- ADEMCO Group, 5890 Wireless PIR Motion Detector, 1997, available at http://web.archive.org/web/19990429054256/www.ademco.com/asc on Mar. 5, 2009, pp. 1-3.Applicant
- ADEMCO Group, 5890P1 Passive Infrared Motion Detector/Transmitter Installation Instructions, Mar. 1998, ADEMCO Group, Author: unknown; pp. 1-4.Applicant
- ADEMCO Group, 6128RF Keypad/Receiver-full wireless capability, 1997, ADEMCO Group, Author: unknown; pp. 1-2.Applicant
- ADEMCO Group, 6128RF Keypad/Transceiver Installation Instructions, Jul. 1998, ADEMCO Group, Author: unknown; pp. 1-8.Applicant
- ADEMCO Group, 6128RF Keypad/Transceiver, User Guide, May 1998, ADEMCO Group, Author: unknown; p. 1.Applicant
- ADEMCO Group, 6128WL Keypad/Receiver Installation Instructions, Oct. 1998, ADEMCO Group, Author: unknown; pp. 1-8.Applicant
- ADEMCO Group, 6128WL Keypad/Receiver User Guide, Oct. 1998, ADEMCOGroup, Author: unknown; p. 1.Applicant
- ADEMCO Group, 7715DF MicroFAST Installation Tool, User Manual, Feb. 1998, ADEMCO Group, Author: unknown; pp. 1-32.Applicant
- ADEMCO Group, 7720 Subscriber Radio, Installation Instructions, Jan. 1992, ADEMCO Group, Author: unknown, available at http://www.guardianalarms.net, pp. 1-18.Applicant
- ADEMCO Group, 7720NX Network Extender, 1997, ADEMCO Group, Author: unknown, available at http://web.archive.org/web/19990220035932/www.ademco.com/ademco on Mar. 5, 2009, pp. 1-3.Applicant