US 7,756,086 B2Grant
Method for communicating in dual-modes
Issue Date:2010-07-13
•35 Claims
•9 Drawing Sheets
Abstract
The present invention is generally directed to methods for communicating in a dual-mode communication protocol. A representative embodiment of the present invention comprises: enabling communication in a spread-spectrum communication protocol, comprising: receiving 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 for receiving a second portion of the communication frame; switching to the second frequency channel; and receiving the second portion of the communication frame at the second frequency channel.
Metadata
Assignee
- Sipco, LLC
Inventors
- Thomas D. Petite
- Richard Huff
- David P. Aldoretta
Application Information
Application Number:US 10/792,464
Filing Date:2004-03-03
Priority Date:2004-03-03
Art Unit:2617
Classifications
IPC:
H04B7/216H04B1/00H04B1/18H04W72/00
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 infrastructure 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 method of communicating with a dual-mode communication protocol in a given frequency band composed of a plurality of channels. A first set of the plurality of channels is designated fixed-frequency channels and a second set of the plurality of channels is designated spread-spectrum channels. The spread-spectrum channels comprise a first subset of acquisition channels and a second subset of data channels. One such method comprises: enabling communication in a spread-spectrum communication mode; attempting to receive a communication packet by traversing through the subset of acquisition channels; upon receiving a communication packet, switching to a data channel designated by the communication packet; and receiving and verifying a data portion of the communication packet by communicating in the designated data channel. Upon not receiving a communication packet after traversing through the subset of acquisition channels, the method continues with: enabling communication in a fixed-frequency communication mode; attempting to receive a communication packet by traversing through the designated fixed-frequency channels; and, upon receiving a communication packet, receiving and verifying a data portion of the communication packet by maintaining communication in the current fixed-frequency channel.
[0006] Another embodiment is a method for communicating in a dual-mode communication protocol. The method comprises: enabling communication in a spread-spectrum communication protocol, comprising: receiving a first portion of a communication frame at a first frequency channel, the first portion of the communication frame comprising a data channel index that indicates a second frequency channel for receiving a second portion of the communication frame; switching to the second frequency channel; and receiving the second portion of the communication frame at the second frequency channel.
[0007] Yet another embodiment is a method for communicating data. The method comprises: enabling communication in a spread-spectrum communication protocol, the spread spectrum communication protocol, comprising: transmitting a first portion of a communication frame at a first frequency channel, the first portion of the communication frame comprising a data channel index that indicates a second frequency channel for communicating a second portion of the communication frame; switching to the second frequency channel; and transmitting the second portion of the communication frame at the second frequency channel.
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 method of communicating with a multi-mode communication protocol in a given frequency band composed of a plurality of channels, wherein a first set of the plurality of channels are designated fixed-frequency channels and a second set of the plurality of channels are designated spread-spectrum channels, the spread-spectrum channels being composed of a first subset of acquisition channels and a second subset of data channels, the acquisition channels separated by data channels, the method comprising:
enabling communication in a spread-spectrum communication mode;
attempting to receive a communication packet by traversing through the subset of acquisition channels;
upon receiving a communication packet,
switching to a data channel designated by the communication packet; and
receiving and verifying a data portion of the communication packet by communicating in the designated data channel;
upon not receiving a communication packet after traversing through the subset of acquisition channels,
enabling communication in a fixed-frequency communication mode;
attempting to receive a communication packet by traversing through the designated fixed-frequency channels and searching for a training sequence in the preamble of the communication packet; and
upon receiving a communication packet, receiving and verifying a data portion of the communication packet by maintaining communication in the current fixed-frequency channel.
2. The method of claim 1, wherein enabling communication in a spread-spectrum communication mode comprises:
setting a current modulation protocol to a frequency shift keying (FSK) protocol.
3. The method of claim 1, wherein enabling communication in a fixed-frequency communication mode comprises:
setting a current modulation protocol to an on-off keying (OOK) protocol.
4. A method for communicating in a dual-mode communication protocol, the method comprising:
enabling communication in a spread-spectrum communication protocol, comprising:
receiving 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 for receiving a second portion of the communication frame;
wherein the first frequency channel is one of a subset of acquisition channels, and the second frequency channel is one of a subset of data channels, wherein the acquisition and data channels are subsets of channels designated for spread-spectrum communication, and wherein the spread-spectrum communication protocol further comprises:
cycling through the subset of acquisition channels until synchronizing with a transmitter, whereupon the channel at which synchronization occurs is the first frequency channel;
receiving a predefined synchronization pattern, wherein the predefined synchronization pattern is found within a training sequence field of the first portion of the communication frame;
switching to the second frequency channel;
receiving the second portion of the communication frame at the second frequency channel;
upon not synchronizing with a transmitter, enabling communication in a fixed-frequency communication protocol, wherein the fixed-frequency communication protocol comprises:
receiving the entire communication frame at a third frequency channel, wherein the third frequency channel is one of a subset of fixed-frequency channels.
5. The method of claim 4, wherein enabling communication in a fixed-frequency communication protocol comprises enabling communication in a first modulation scheme, and wherein enabling communication in a spread-spectrum communication protocol comprises enabling communication in a second modulation scheme.
6. The method of claim 5, wherein the first modulation scheme is the same as the second modulation scheme.
7. The method of claim 5, wherein the first modulation scheme is an amplitude modulation scheme.
8. The method of claim 7, wherein the amplitude modulation scheme is an on-off keying (OOK) modulation scheme.
9. The method of claim 5, wherein the second modulation scheme is a frequency modulation scheme.
10. The method of claim 9, wherein the frequency modulation scheme is a frequency shift keying (FSK) modulation scheme.
11. A method for communicating data, the method comprising:
enabling communication in a spread-spectrum communication protocol, the spread spectrum communication protocol comprising:
transmitting a first portion of a communication frame at a first frequency channel, wherein the preamble of the first portion of the communication frame comprises a data channel index that indicates a second frequency channel for communicating a second portion of the communication frame;
determining whether to communicate in the spread-spectrum communication protocol or a fixed-frequency communication protocol;
examining a receiver address field of the communication frame to determine whether an intended receiver communicates in the spread-spectrum communication protocol or the fixed-frequency communication protocol;
upon communicating the communication frame, receiving an acknowledgement response from the intended receiver;
updating the receiver address field of the intended receiver;
switching to the second frequency channel;
transmitting the second portion of the communication frame at the second frequency channel;
upon determining to communicate in the fixed-frequency communication protocol, enabling communication in the fixed-frequency communication protocol, wherein the fixed-frequency communication protocol comprises transmitting the first and second portions of the communication frame in a third frequency channel.
12. The method of claim 11, wherein the first frequency channel is one of a subset of acquisition channels, and the second frequency channel is one of a subset of data channels, wherein the acquisition and data channels are subsets of a first set of channels designated for spread-spectrum communication, and wherein the third frequency channel is one of a second set of channels designated for fixed-frequency communication.
13. The method of claim 11, wherein enabling communication in a fixed-frequency communication protocol comprises enabling communication in a first modulation scheme, and wherein enabling communication in a spread-spectrum communication protocol comprises enabling communication in a second modulation scheme.
14. The method of claim 13, wherein the first modulation scheme is the same as the second modulation scheme.
15. The method of claim 13, wherein the first modulation scheme is an amplitude modulation scheme.
16. The method of claim 15, wherein the amplitude modulation scheme is an on-off keying (OOK) modulation scheme.
17. The method of claim 13, wherein the second modulation scheme is a frequency modulation scheme.
18. The method of claim 17, wherein the frequency modulation scheme is a frequency shift keying (FSK) modulation scheme.
19. The method of claim 13, wherein enabling communication in the fixed-frequency communication protocol further comprises:
enabling communication in a relatively low-power transmission mode.
20. The method of claim 13, wherein enabling communication in the spread-spectrum communication protocol further comprises:
enabling communication in a relatively high-power transmission mode.
21. A dual-mode transceiver, comprising: means for communicating in a spread-spectrum communication protocol, said means comprising:
means for receiving in the spread-spectrum communication protocol, comprising:
means for receiving at a first frequency channel a first portion of a communication frame that comprises a data channel index that indicates a second frequency channel for receiving a second portion of the communication frame;
wherein the first frequency channel is one of a subset of acquisition channels, and the second frequency channel is one of a subset of data channels, wherein the acquisition and data channels are subsets of channels designated for spread-spectrum communication, and wherein said means for receiving in the spread-spectrum communication protocol further comprises:
means for cycling through the subset of acquisition channels;
means for synchronizing with a transmitter, whereupon the acquisition channel at which synchronization occurs is the first frequency channel;
means for receiving a predefined synchronization pattern, wherein the predefined synchronization pattern is found within a training sequence field of the first portion of the communication frame;
means for switching to the second frequency channel designated by the data channel index;
means for receiving the second portion of the communication frame at the second frequency channel;
means for switching from receiving in the spread-spectrum communication protocol to receiving in the fixed-frequency communication protocol upon not synchronizing with a transmitter in the spread-spectrum communication protocol;
means for communicating in a fixed-frequency communication protocol, comprising:
means for receiving in the fixed-frequency communication protocol, comprising:
means for receiving the entire communication frame at a third frequency channel, wherein the third frequency channel is one of a subset of fixed-frequency channels.
22. The transceiver of claim 21, wherein said means for communicating in the spread-spectrum communication protocol further comprises:
means for transmitting in the spread-spectrum communication protocol, comprising:
means for transmitting 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 for communicating a second portion of the communication frame;
means for switching to the second frequency channel; and
means for transmitting the second portion of the communication frame at the second frequency channel.
23. The transceiver of claim 22, further comprising:
means for communicating in a fixed-frequency communication protocol, comprising:
means for transmitting in the fixed-frequency communication protocol, comprising:
means for transmitting the first and second portions of the communication frame in a third frequency channel.
24. The transceiver of claim 23, wherein said means for transmitting in the spread-spectrum communication protocol further comprises means for transmitting at a first radiating-power level, and wherein said means for transmitting in the fixed-frequency communication protocol further comprises means for communicating at a second radiating-power level.
25. The transceiver of claim 24, wherein the first radiating-power level is higher then the second radiating-power level.
26. The transceiver of claim 24, wherein the second radiating-power level is a substantially low power level.
27. The transceiver of claim 23, further comprising:
means for determining whether to transmit in the spread-spectrum communication protocol or the fixed-frequency communication protocol.
28. The transceiver of claim 24, wherein said means for determining comprises:
means for examining a receiver address field of the communication frame to determine whether an intended receiver communicates in the spread-spectrum communication protocol or the fixed-frequency communication protocol.
29. The transceiver of claim 25, further comprising:
means for receiving an acknowledgement response from the intended receiver; and
means for updating the receiver address field of the intended receiver.
30. The transceiver of claim 21, wherein said means for communicating in the fixed-frequency communication protocol further comprises means for communicating in a first modulation scheme, and wherein said means for communicating in the spread-spectrum communication protocol comprises means for communicating in a second modulation scheme.
31. The transceiver of claim 30, wherein the first modulation scheme is the same as the second modulation scheme.
32. The transceiver of claim 30, wherein the first modulation scheme is an amplitude modulation scheme.
33. The transceiver of claim 32, wherein the amplitude modulation scheme is an on-off keying (OOK) modulation scheme.
34. The transceiver of claim 30, wherein the second modulation scheme is a frequency modulation scheme.
35. The transceiver of claim 34, wherein the frequency modulation scheme is a frequency shift keying (FSK) modulation scheme.
Patent Citations (636)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3665475(A) | 1972-05-01 | Gram | Applicant |
| US3705385(A) | 1972-12-01 | Batz | Applicant |
| US3723876(A) | 1973-03-01 | Seaborn, Jr. | Applicant |
| US3742142(A) | 1973-06-01 | Martin | Applicant |
| US3848231(A) | 1974-11-01 | Wooten | Applicant |
| US3892948(A) | 1975-07-01 | Constable | Applicant |
| US3906460(A) | 1975-09-01 | Halpern | Applicant |
| US3914692(A) | 1975-10-01 | Seaborn, Jr. | Applicant |
| US3922492(A) | 1975-11-01 | Lumsden | Applicant |
| US3925763(A) | 1975-12-01 | Wadwhani et al. | Applicant |
| US4025315(A) | 1977-05-01 | Mazelli | Applicant |
| US4056684(A) | 1977-11-01 | Lindstrom | Applicant |
| US4058672(A) | 1977-11-01 | Crager et al. | Applicant |
| US4083003(A) | 1978-04-01 | Haemmig | Applicant |
| US4120452(A) | 1978-10-01 | Kimura et al. | Applicant |
| US4124839(A) | 1978-11-01 | Cohen | Applicant |
| US4135181(A) | 1979-01-01 | Bogacki et al. | Applicant |
| US4204195(A) | 1980-05-01 | Bogacki | Applicant |
| US4213119(A) | 1980-07-01 | Ward et al. | Applicant |
| US4277837(A) | 1981-07-01 | Stuckert | Applicant |
| US4278975(A) | 1981-07-01 | Kimura et al. | Applicant |
| US4354181(A) | 1982-10-01 | Spletzer | Applicant |
| US4396910(A) | 1983-08-01 | Enemark et al. | Applicant |
| US4396915(A) | 1983-08-01 | Farnsworth et al. | Applicant |
| US4417450(A) | 1983-11-01 | Morgan, Jr. et al. | Applicant |
| US4436957(A) | 1984-03-01 | Mazza | Applicant |
| US4446454(A) | 1984-05-01 | Pyle | Applicant |
| US4446458(A) | 1984-05-01 | Cook | Applicant |
| US4454414(A) | 1984-06-01 | Benton | Applicant |
| US4468656(A) | 1984-08-01 | Clifford et al. | Applicant |
| US4488152(A) | 1984-12-01 | Arnason et al. | Applicant |
| US4495496(A) | 1985-01-01 | Miller, III | Applicant |
| US4551719(A) | 1985-11-01 | Carlin et al. | Applicant |
| US4611198(A) | 1986-09-01 | Levinson et al. | Applicant |
| US4621263(A) | 1986-11-01 | Takenaka et al. | Applicant |
| US4630035(A) | 1986-12-01 | Stahl et al. | Applicant |
| US4631357(A) | 1986-12-01 | Grunig | Applicant |
| US4670739(A) | 1987-06-01 | Kelly, Jr. | Applicant |
| US4692761(A) | 1987-09-01 | Robinton | Applicant |
| US4707852(A) | 1987-11-01 | Jahr et al. | Applicant |
| US4731810(A) | 1988-03-01 | Watkins | Applicant |
| US4742296(A) | 1988-05-01 | Petr et al. | Applicant |
| US4788721(A) | 1988-11-01 | Krishnan et al. | Applicant |
| US4800543(A) | 1989-01-01 | Lyndon-James et al. | Applicant |
| US4825457(A) | 1989-04-01 | Lebowitz | Applicant |
| US4829561(A) | 1989-05-01 | Matheny | Applicant |
| US4849815(A) | 1989-07-01 | Streck | Applicant |
| US4851654(A) | 1989-07-01 | Nitta | Applicant |
| US4856046(A) | 1989-08-01 | Streck et al. | Applicant |
| US4857912(A) | 1989-08-01 | Everett, Jr. et al. | Applicant |
| US4875231(A) | 1989-10-01 | Hara et al. | Applicant |
| 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 |
| US4918690(A) | 1990-04-01 | Markkula, Jr. et al. | Applicant |
| US4918995(A) | 1990-04-01 | Pearman et al. | Applicant |
| US4928299(A) | 1990-05-01 | Tansky et al. | Applicant |
| US4939726(A) | 1990-07-01 | Flammer et al. | Applicant |
| US4940976(A) | 1990-07-01 | Gastouniotis et al. | Applicant |
| US4949077(A) | 1990-08-01 | Mbuthia | Applicant |
| US4952928(A) | 1990-08-01 | Carroll et al. | Applicant |
| US4962496(A) | 1990-10-01 | Vercellotti et al. | Applicant |
| US4967366(A) | 1990-10-01 | Kaehler | Applicant |
| US4968970(A) | 1990-11-01 | LaPorte | Applicant |
| US4968978(A) | 1990-11-01 | Stolarczyk | Applicant |
| US4972504(A) | 1990-11-01 | Daniel, Jr. et al. | Applicant |
| US4973957(A) | 1990-11-01 | Shimizu et al. | Applicant |
| US4973970(A) | 1990-11-01 | Reeser | Applicant |
| US4977612(A) | 1990-12-01 | Wilson | Applicant |
| US4980907(A) | 1990-12-01 | Raith et al. | Applicant |
| US4989230(A) | 1991-01-01 | Gillig et al. | Applicant |
| US4991008(A) | 1991-02-01 | Nama | Applicant |
| US4998095(A) | 1991-03-01 | Shields | Applicant |
| US4999607(A) | 1991-03-01 | Evans | Applicant |
| US5007052(A) | 1991-04-01 | Flammer | Applicant |
| US5032833(A) | 1991-07-01 | Laporte | Applicant |
| US5038372(A) | 1991-08-01 | Elms et al. | Applicant |
| US5055851(A) | 1991-10-01 | Sheffer | Applicant |
| US5057814(A) | 1991-10-01 | Onan et al. | Applicant |
| US5061997(A) | 1991-10-01 | Rea et al. | Applicant |
| US5079768(A) | 1992-01-01 | Flammer | Applicant |
| US5086391(A) | 1992-02-01 | Chambers | Applicant |
| US5091713(A) | 1992-02-01 | Horne et al. | Applicant |
| US5111199(A) | 1992-05-01 | Tomoda et al. | Applicant |
| US5113183(A) | 1992-05-01 | Mizuno et al. | Applicant |
| US5113184(A) | 1992-05-01 | Katayama | Applicant |
| US5115224(A) | 1992-05-01 | Kostusiak et al. | Applicant |
| US5115433(A) | 1992-05-01 | Baran et al. | Applicant |
| US5124624(A) | 1992-06-01 | de Vries et al. | Applicant |
| US5128855(A) | 1992-07-01 | Hilber et al. | Applicant |
| US5130519(A) | 1992-07-01 | Bush et al. | Applicant |
| US5130987(A) | 1992-07-01 | Flammer | Applicant |
| US5131038(A) | 1992-07-01 | Puhl et al. | Applicant |
| US5134650(A) | 1992-07-01 | Blackmon | Applicant |
| US5136285(A) | 1992-08-01 | Okuyama | Applicant |
| US5155481(A) | 1992-10-01 | Brennan, Jr. et al. | Applicant |
| US5159317(A) | 1992-10-01 | Brav | Applicant |
| US5162776(A) | 1992-11-01 | Bushnell et al. | Applicant |
| US5177342(A) | 1993-01-01 | Adams | Applicant |
| US5189287(A) | 1993-02-01 | Parienti | Applicant |
| US5191192(A) | 1993-03-01 | Takahira et al. | Applicant |
| US5191326(A) | 1993-03-01 | Montgomery | Applicant |
| US5193111(A) | 1993-03-01 | Matty et al. | Applicant |
| US5195018(A) | 1993-03-01 | Kwon et al. | Applicant |
| US5197095(A) | 1993-03-01 | Bonnet et al. | Applicant |
| US5200735(A) | 1993-04-01 | Hines | Applicant |
| US5204670(A) | 1993-04-01 | Stinton | Applicant |
| US5212645(A) | 1993-05-01 | Wildes et al. | Applicant |
| US5216502(A) | 1993-06-01 | Katz | Applicant |
| US5221838(A) | 1993-06-01 | Gutman et al. | Applicant |
| US5223844(A) | 1993-06-01 | Mansell et al. | Applicant |
| US5231658(A) | 1993-07-01 | Eftechiou | Applicant |
| US5235630(A) | 1993-08-01 | Moody et al. | Applicant |
| US5239294(A) | 1993-08-01 | Flanders et al. | Applicant |
| US5239575(A) | 1993-08-01 | White et al. | Applicant |
| US5241410(A) | 1993-08-01 | Streck et al. | Applicant |
| US5243338(A) | 1993-09-01 | Brennan, Jr. et al. | Applicant |
| US5245633(A) | 1993-09-01 | Schwartz et al. | Applicant |
| US5251205(A) | 1993-10-01 | Callon et al. | Applicant |
| US5252967(A) | 1993-10-01 | Brennan et al. | Applicant |
| US5253167(A) | 1993-10-01 | Yoshida et al. | Applicant |
| US5265150(A) | 1993-11-01 | Helmkamp et al. | Applicant |
| US5265162(A) | 1993-11-01 | Bush et al. | Applicant |
| US5266782(A) | 1993-11-01 | Alanara et al. | Applicant |
| US5272747(A) | 1993-12-01 | Meads | Applicant |
| US5282204(A) | 1994-01-01 | Shpancer et al. | Applicant |
| US5282250(A) | 1994-01-01 | Dent et al. | Applicant |
| US5289165(A) | 1994-02-01 | Belin | Applicant |
| US5291516(A) | 1994-03-01 | Dixon et al. | 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 |
| US5345231(A) | 1994-09-01 | Koo et al. | Applicant |
| US5345595(A) | 1994-09-01 | Johnson et al. | Applicant |
| US5347263(A) | 1994-09-01 | Carroll et al. | Applicant |
| US5354974(A) | 1994-10-01 | Eisenberg | Applicant |
| US5355278(A) | 1994-10-01 | Hosoi et al. | Applicant |
| US5355513(A) | 1994-10-01 | Clarke et al. | Applicant |
| US5365217(A) | 1994-11-01 | Toner | Applicant |
| US5371736(A) | 1994-12-01 | Evan | Applicant |
| US5382778(A) | 1995-01-01 | Takahira et al. | Applicant |
| US5383134(A) | 1995-01-01 | Wrzesinski | Applicant |
| US5390206(A) | 1995-02-01 | Rein | Applicant |
| US5406619(A) | 1995-04-01 | Akhteruzzman et al. | Applicant |
| US5412192(A) | 1995-05-01 | Hoss | Applicant |
| US5412760(A) | 1995-05-01 | Peitz | Applicant |
| US5416475(A) | 1995-05-01 | Tolbert et al. | Applicant |
| US5416725(A) | 1995-05-01 | Pacheco et al. | Applicant |
| US5418812(A) | 1995-05-01 | Reyes et al. | Applicant |
| US5420910(A) | 1995-05-01 | Rudokas et al. | Applicant |
| US5424708(A) | 1995-06-01 | Ballestry et al. | Applicant |
| US5432507(A) | 1995-07-01 | Mussino et al. | Applicant |
| US5438329(A) | 1995-08-01 | Gastouniotis et al. | Applicant |
| US5439414(A) | 1995-08-01 | Jacob | Applicant |
| US5440545(A) | 1995-08-01 | Buchholz et al. | Applicant |
| US5442553(A) | 1995-08-01 | Parrillo | Applicant |
| US5445287(A) | 1995-08-01 | Center et al. | Applicant |
| US5445347(A) | 1995-08-01 | Ng | Applicant |
| US5451929(A) | 1995-09-01 | Adelman et al. | Applicant |
| US5451938(A) | 1995-09-01 | Brennan, Jr. | Applicant |
| US5452344(A) | 1995-09-01 | Larson | Applicant |
| US5454024(A) | 1995-09-01 | Lebowitz | Applicant |
| US5465401(A) | 1995-11-01 | Thompson | Applicant |
| US5467074(A) | 1995-11-01 | Pedtke | Applicant |
| US5467082(A) | 1995-11-01 | Sanderson | Applicant |
| US5467345(A) | 1995-11-01 | Cutler, Jr. et al. | Applicant |
| US5468948(A) | 1995-11-01 | Koenck et al. | Applicant |
| US5471201(A) | 1995-11-01 | Cerami et al. | Applicant |
| US5473322(A) | 1995-12-01 | Carney | Applicant |
| US5475689(A) | 1995-12-01 | Kay et al. | Applicant |
| US5481259(A) | 1996-01-01 | Bane | Applicant |
| US5481532(A) | 1996-01-01 | Hassan et al. | Applicant |
| US5484997(A) | 1996-01-01 | Haynes | Applicant |
| US5488608(A) | 1996-01-01 | Flammer, III | Applicant |
| US5493273(A) | 1996-02-01 | Smurlo et al. | Applicant |
| US5493287(A) | 1996-02-01 | Bane | Applicant |
| US5502726(A) | 1996-03-01 | Fischer | Applicant |
| US5506837(A) | 1996-04-01 | Sollner et al. | Applicant |
| US5509073(A) | 1996-04-01 | Monnin | Applicant |
| US5513244(A) | 1996-04-01 | Joao et al. | Applicant |
| US5515419(A) | 1996-05-01 | Sheffer | Applicant |
| US5517188(A) | 1996-05-01 | Caroll et al. | Applicant |
| US5522089(A) | 1996-05-01 | Kikinis et al. | Applicant |
| US5528215(A) | 1996-06-01 | Siu et al. | Applicant |
| US5539825(A) | 1996-07-01 | Akiyama et al. | Applicant |
| US5541938(A) | 1996-07-01 | Di Zenzo et al. | Applicant |
| US5542100(A) | 1996-07-01 | Hatakeyama | Applicant |
| US5544036(A) | 1996-08-01 | Brown, Jr. et al. | Applicant |
| US5544784(A) | 1996-08-01 | Malaspina | Applicant |
| US5548632(A) | 1996-08-01 | Walsh et al. | Applicant |
| US5550358(A) | 1996-08-01 | Tait et al. | Applicant |
| US5550359(A) | 1996-08-01 | Bennett | Applicant |
| US5550535(A) | 1996-08-01 | Park | Applicant |
| US5553094(A) | 1996-09-01 | Johnson et al. | Applicant |
| US5555258(A) | 1996-09-01 | Snelling et al. | Applicant |
| US5555286(A) | 1996-09-01 | Tendler | Applicant |
| US5562537(A) | 1996-10-01 | Zver et al. | Applicant |
| US5565857(A) | 1996-10-01 | Lee | Applicant |
| US5568535(A) | 1996-10-01 | Sheffer et al. | Applicant |
| US5570084(A) | 1996-10-01 | Ritter et al. | Applicant |
| US5572438(A) | 1996-11-01 | Ehlers et al. | Applicant |
| US5573181(A) | 1996-11-01 | Ahmed | Applicant |
| US5574111(A) | 1996-11-01 | Brichta et al. | Applicant |
| US5583850(A) | 1996-12-01 | Snodgrass et al. | Applicant |
| US5587705(A) | 1996-12-01 | Morris | Applicant |
| US5589878(A) | 1996-12-01 | Cortjens et al. | Applicant |
| US5590038(A) | 1996-12-01 | Pitroda | Applicant |
| US5590179(A) | 1996-12-01 | Shincovich et al. | Applicant |
| US5592491(A) | 1997-01-01 | Dinks | Applicant |
| US5594431(A) | 1997-01-01 | Sheppard et al. | Applicant |
| US5596719(A) | 1997-01-01 | Ramakrishnan et al. | Applicant |
| US5602843(A) | 1997-02-01 | Gray | Applicant |
| US5604414(A) | 1997-02-01 | Milligan et al. | Applicant |
| US5604869(A) | 1997-02-01 | Mincher et al. | Applicant |
| US5606361(A) | 1997-02-01 | Davidsohn et al. | Applicant |
| US5608786(A) | 1997-03-01 | Gordon | Applicant |
| US5613620(A) | 1997-03-01 | Center et al. | Applicant |
| US5615277(A) | 1997-03-01 | Hoffman | Applicant |
| US5619192(A) | 1997-04-01 | Ayala | Applicant |
| US5625410(A) | 1997-04-01 | Washino et al. | Applicant |
| US5628050(A) | 1997-05-01 | McGraw et al. | Applicant |
| US5629687(A) | 1997-05-01 | Sutton et al. | Applicant |
| US5629875(A) | 1997-05-01 | Adair, Jr. | Applicant |
| US5630209(A) | 1997-05-01 | Wizgall et al. | Applicant |
| US5631554(A) | 1997-05-01 | Briese et al. | Applicant |
| US5636216(A) | 1997-06-01 | Fox et al. | Applicant |
| US5640002(A) | 1997-06-01 | Ruppert et al. | Applicant |
| US5644294(A) | 1997-07-01 | Ness | Applicant |
| US5655219(A) | 1997-08-01 | Jusa et al. | Applicant |
| US5657389(A) | 1997-08-01 | Houvener | Applicant |
| US5659300(A) | 1997-08-01 | Dresselhuys et al. | Applicant |
| US5659303(A) | 1997-08-01 | Adair, Jr. | Applicant |
| US5668876(A) | 1997-09-01 | Falk et al. | Applicant |
| US5673252(A) | 1997-09-01 | Johnson et al. | Applicant |
| US5673304(A) | 1997-09-01 | Connor et al. | Applicant |
| US5673305(A) | 1997-09-01 | Ross | Applicant |
| US5682139(A) | 1997-10-01 | Pradeep et al. | Applicant |
| US5682476(A) | 1997-10-01 | Tapperson et al. | Applicant |
| US5689229(A) | 1997-11-01 | Chaco et al. | Applicant |
| US5699328(A) | 1997-12-01 | Ishizaki et al. | Applicant |
| US5701002(A) | 1997-12-01 | Oishi et al. | Applicant |
| US5702059(A) | 1997-12-01 | Chu et al. | Applicant |
| US5704046(A) | 1997-12-01 | Hogan | Applicant |
| US5704517(A) | 1998-01-01 | Lancaster, Jr. | Applicant |
| US5706191(A) | 1998-01-01 | Bassett et al. | Applicant |
| US5706976(A) | 1998-01-01 | Purkey | Applicant |
| US5708223(A) | 1998-01-01 | Wyss | Applicant |
| US5708655(A) | 1998-01-01 | Toth et al. | Applicant |
| US5712619(A) | 1998-01-01 | Simkin | Applicant |
| US5712980(A) | 1998-01-01 | Beeler et al. | Applicant |
| US5714931(A) | 1998-02-01 | Petite et al. | Applicant |
| US5717718(A) | 1998-02-01 | Roswell et al. | Applicant |
| US5726634(A) | 1998-03-01 | Hess et al. | Applicant |
| US5726984(A) | 1998-03-01 | Kubler et al. | Applicant |
| US5732074(A) | 1998-03-01 | Spaur et al. | Applicant |
| US5732078(A) | 1998-03-01 | Arango | Applicant |
| US5736965(A) | 1998-04-01 | Mosebrook et al. | Applicant |
| US5740232(A) | 1998-04-01 | Pailles et al. | Applicant |
| US5742509(A) | 1998-04-01 | Goldberg et al. | Applicant |
| US5745849(A) | 1998-04-01 | Britton | Applicant |
| US5748104(A) | 1998-05-01 | Argyroudis et al. | Applicant |
| US5748619(A) | 1998-05-01 | Meier | Applicant |
| US5754111(A) | 1998-05-01 | Garcia | Applicant |
| US5754227(A) | 1998-05-01 | Fukuoka | Applicant |
| US5754542(A) | 1998-05-01 | Ault et al. | Examiner |
| US5757783(A) | 1998-05-01 | Eng et al. | Applicant |
| US5757788(A) | 1998-05-01 | Tatsumi et al. | Applicant |
| US5761083(A) | 1998-06-01 | Brown, Jr. et al. | Applicant |
| US5764742(A) | 1998-06-01 | Howard et al. | Applicant |
| US5767791(A) | 1998-06-01 | Stoop et al. | Examiner |
| US5771274(A) | 1998-06-01 | Harris | Applicant |
| US5774052(A) | 1998-06-01 | Hamm et al. | Applicant |
| US4757185(A) | 1998-07-01 | Onishi | Applicant |
| US5781143(A) | 1998-07-01 | Rossin | Applicant |
| US5790644(A) | 1998-08-01 | Kikinis | Applicant |
| US5790662(A) | 1998-08-01 | Valerij et al. | Applicant |
| US5790938(A) | 1998-08-01 | Talarmo | Applicant |
| US5796727(A) | 1998-08-01 | Harrison et al. | Applicant |
| US5798964(A) | 1998-08-01 | Shimizu et al. | Applicant |
| US5801643(A) | 1998-09-01 | Williams et al. | Applicant |
| US5815505(A) | 1998-09-01 | Mills | Applicant |
| US5818822(A) | 1998-10-01 | Thomas et al. | Applicant |
| US5822273(A) | 1998-10-01 | Bary et al. | Applicant |
| US5822544(A) | 1998-10-01 | Chaco et al. | Applicant |
| US5825772(A) | 1998-10-01 | Dobbins et al. | Applicant |
| US5826195(A) | 1998-10-01 | Westerlage et al. | Applicant |
| US5828044(A) | 1998-10-01 | Jun et al. | Applicant |
| US5832057(A) | 1998-11-01 | Furman | Applicant |
| US5838223(A) | 1998-11-01 | Gallant et al. | Applicant |
| US5838237(A) | 1998-11-01 | Revell et al. | Applicant |
| US5838812(A) | 1998-11-01 | Pare, Jr. et al. | Applicant |
| US5841118(A) | 1998-11-01 | East et al. | Applicant |
| US5841764(A) | 1998-11-01 | Roderique et al. | Applicant |
| US5842976(A) | 1998-12-01 | Williamson | Applicant |
| US5844808(A) | 1998-12-01 | Konsmo et al. | Applicant |
| US5845230(A) | 1998-12-01 | Lamberson | Applicant |
| US5852658(A) | 1998-12-01 | Knight et al. | Applicant |
| US5854994(A) | 1998-12-01 | Canada et al. | Applicant |
| US5862201(A) | 1999-01-01 | Sands | Applicant |
| US5864772(A) | 1999-01-01 | Alvarado et al. | Applicant |
| US5873043(A) | 1999-02-01 | Comer | Applicant |
| US5874903(A) | 1999-02-01 | Shuey et al. | Applicant |
| US5880677(A) | 1999-03-01 | Lestician | Applicant |
| US5884184(A) | 1999-03-01 | Sheffer | Applicant |
| US5884271(A) | 1999-03-01 | Pitroda | Applicant |
| US5886333(A) | 1999-03-01 | Miyake | Applicant |
| US5889468(A) | 1999-03-01 | Banga | Applicant |
| US5892690(A) | 1999-04-01 | Boatman et al. | Applicant |
| US5892758(A) | 1999-04-01 | Argyroudis | Applicant |
| US5892924(A) | 1999-04-01 | Lyon et al. | Applicant |
| US5896097(A) | 1999-04-01 | Cardozo | Applicant |
| US5897607(A) | 1999-04-01 | Jenney et al. | Applicant |
| US5898369(A) | 1999-04-01 | Godwin | Applicant |
| US5905438(A) | 1999-05-01 | Weiss et al. | Applicant |
| US5907291(A) | 1999-05-01 | Chen et al. | Applicant |
| US5907491(A) | 1999-05-01 | Canada et al. | Applicant |
| US5907540(A) | 1999-05-01 | Hayashi | Applicant |
| US5907807(A) | 1999-05-01 | Chavez, Jr. et al. | Applicant |
| US5914672(A) | 1999-06-01 | Glorioso et al. | Applicant |
| US5914673(A) | 1999-06-01 | Jennings et al. | Applicant |
| US5917405(A) | 1999-06-01 | Joao | Applicant |
| US5917629(A) | 1999-06-01 | Hortensius et al. | Applicant |
| US5923269(A) | 1999-07-01 | Shuey et al. | Applicant |
| US5926103(A) | 1999-07-01 | Petite | Applicant |
| US5926529(A) | 1999-07-01 | Hache et al. | Applicant |
| US5926531(A) | 1999-07-01 | Petite | Applicant |
| US5933073(A) | 1999-08-01 | Shuey | Applicant |
| US5941363(A) | 1999-08-01 | Partyka et al. | Applicant |
| US5941955(A) | 1999-08-01 | Wilby et al. | Applicant |
| US5948040(A) | 1999-09-01 | DeLorme et al. | Applicant |
| US5949779(A) | 1999-09-01 | Mostafa et al. | Applicant |
| US5949799(A) | 1999-09-01 | Grivna et al. | Applicant |
| US5953319(A) | 1999-09-01 | Dutta et al. | Applicant |
| US5953371(A) | 1999-09-01 | Roswell et al. | Applicant |
| US5955718(A) | 1999-09-01 | Levasseur et al. | Applicant |
| US5960074(A) | 1999-09-01 | Clark | Applicant |
| US5963146(A) | 1999-10-01 | Johnson et al. | Applicant |
| US5963452(A) | 1999-10-01 | Etoh et al. | Applicant |
| US5963650(A) | 1999-10-01 | Simionescu et al. | Applicant |
| US5966658(A) | 1999-10-01 | Kennedy, III et al. | Applicant |
| US5969608(A) | 1999-10-01 | Sojdehei et al. | Applicant |
| US5973756(A) | 1999-10-01 | Erlin | Applicant |
| US5974236(A) | 1999-10-01 | Sherman | Applicant |
| US5978364(A) | 1999-11-01 | Melnik | Applicant |
| US5978371(A) | 1999-11-01 | Mason, Jr. et al. | Applicant |
| US5986574(A) | 1999-11-01 | Colton | Applicant |
| US5987421(A) | 1999-11-01 | Chuang | Applicant |
| US5991625(A) | 1999-11-01 | Vanderpool | Applicant |
| US5991639(A) | 1999-11-01 | Rautiola et al. | Applicant |
| US5994892(A) | 1999-11-01 | Turino et al. | Applicant |
| US5995592(A) | 1999-11-01 | Shirai et al. | Applicant |
| US5995593(A) | 1999-11-01 | Cho | Applicant |
| US5997170(A) | 1999-12-01 | Brodbeck | Applicant |
| US5999094(A) | 1999-12-01 | Nilssen | Applicant |
| US6005759(A) | 1999-12-01 | Hart et al. | Applicant |
| US6005963(A) | 1999-12-01 | Bolle et al. | Applicant |
| US6021664(A) | 2000-02-01 | Granato et al. | Applicant |
| US6023223(A) | 2000-02-01 | Baxter, Jr. | Applicant |
| US6026095(A) | 2000-02-01 | Sherer et al. | Applicant |
| US6028522(A) | 2000-02-01 | Petite | Applicant |
| US6028857(A) | 2000-02-01 | Poor | Applicant |
| US6031455(A) | 2000-02-01 | Grube et al. | Applicant |
| US6032197(A) | 2000-02-01 | Birdwell et al. | Applicant |
| US6035213(A) | 2000-03-01 | Tokuda et al. | Examiner |
| US6035266(A) | 2000-03-01 | Williams et al. | Applicant |
| US6036086(A) | 2000-03-01 | Sizer, II et al. | Applicant |
| US6038491(A) | 2000-03-01 | McGarry et al. | Applicant |
| US6044062(A) | 2000-03-01 | Brownrigg et al. | Applicant |
| US6054920(A) | 2000-04-01 | Smith et al. | Applicant |
| US6060994(A) | 2000-05-01 | Chen | Applicant |
| US6061604(A) | 2000-05-01 | Russ et al. | Applicant |
| US6064318(A) | 2000-05-01 | Kirchner, III et al. | Applicant |
| US6067017(A) | 2000-05-01 | Stewart et al. | Applicant |
| US6067030(A) | 2000-05-01 | Burnett et al. | Applicant |
| US6069886(A) | 2000-05-01 | Ayerst et al. | Applicant |
| US6073169(A) | 2000-06-01 | Shuey et al. | Applicant |
| US6073266(A) | 2000-06-01 | Ahmed et al. | Applicant |
| US6073840(A) | 2000-06-01 | Marion | Applicant |
| US6075451(A) | 2000-06-01 | Lebowitz et al. | Applicant |
| US6078251(A) | 2000-06-01 | Landt et al. | Applicant |
| US6087957(A) | 2000-07-01 | Gray | Applicant |
| US6088659(A) | 2000-07-01 | Kelley et al. | Applicant |
| US6094622(A) | 2000-07-01 | Hubbard et al. | Applicant |
| US6100817(A) | 2000-08-01 | Mason, Jr. et al. | Applicant |
| US6101427(A) | 2000-08-01 | Yang | Applicant |
| US6101445(A) | 2000-08-01 | Alvarado et al. | Applicant |
| US6112983(A) | 2000-09-01 | D'Anniballe et al. | Applicant |
| US6115580(A) | 2000-09-01 | Chuprun et al. | Applicant |
| US6119076(A) | 2000-09-01 | Williams et al. | Applicant |
| US6121593(A) | 2000-09-01 | Mansbery et al. | Applicant |
| US6121885(A) | 2000-09-01 | Masone et al. | Applicant |
| US6124806(A) | 2000-09-01 | Cunningham et al. | 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. | Applicant |
| US6172616(B1) | 2001-01-01 | Johnson et al. | Applicant |
| US6174205(B1) | 2001-01-01 | Madsen et al. | Applicant |
| US6175922(B1) | 2001-01-01 | Wang | Applicant |
| US6177883(B1) | 2001-01-01 | Jennetti et al. | Applicant |
| US6181255(B1) | 2001-01-01 | Crimmins et al. | Applicant |
| US6181284(B1) | 2001-01-01 | Madsen et al. | Applicant |
| US6181981(B1) | 2001-01-01 | Varga et al. | Applicant |
| US6188354(B1) | 2001-02-01 | Soliman et al. | Applicant |
| US6192390(B1) | 2001-02-01 | Berger et al. | Applicant |
| US6198390(B1) | 2001-03-01 | Schlager et al. | Applicant |
| US6199068(B1) | 2001-03-01 | Carpenter | Applicant |
| US6208266(B1) | 2001-03-01 | Lyons et al. | Applicant |
| US6215404(B1) | 2001-04-01 | Morales | Applicant |
| US6218953(B1) | 2001-04-01 | Petite | Applicant |
| US6218958(B1) | 2001-04-01 | Eichstaedt | Applicant |
| US6218983(B1) | 2001-04-01 | Kerry et al. | Applicant |
| US6219409(B1) | 2001-04-01 | Smith et al. | Applicant |
| US6229439(B1) | 2001-05-01 | Tice | Applicant |
| US6233327(B1) | 2001-05-01 | Petite | Applicant |
| US6234111(B1) | 2001-05-01 | Ulman et al. | Applicant |
| US6236332(B1) | 2001-05-01 | Conkright et al. | Applicant |
| US6243010(B1) | 2001-06-01 | Addy et al. | Applicant |
| US6246677(B1) | 2001-06-01 | Nap et al. | Applicant |
| US6246886(B1) | 2001-06-01 | Oliva | Examiner |
| US6249516(B1) | 2001-06-01 | Brownrigg et al. | Applicant |
| US6259369(B1) | 2001-07-01 | Monico | Applicant |
| US6275707(B1) | 2001-08-01 | Reed et al. | Applicant |
| US6286756(B1) | 2001-09-01 | Stinson et al. | Applicant |
| US6288634(B1) | 2001-09-01 | Weiss et al. | Applicant |
| US6288641(B1) | 2001-09-01 | Casais | Applicant |
| US6295291(B1) | 2001-09-01 | Larkins | Applicant |
| US6301514(B1) | 2001-10-01 | Canada et al. | Applicant |
| US6304556(B1) | 2001-10-01 | Haas | Applicant |
| US6305602(B1) | 2001-10-01 | Grabowski et al. | Applicant |
| US6308111(B1) | 2001-10-01 | Koga | Applicant |
| US6311167(B1) | 2001-10-01 | Davis et al. | Applicant |
| US6314169(B1) | 2001-11-01 | Schelberg, Jr. et al. | Applicant |
| US6317029(B1) | 2001-11-01 | Fleeter | Applicant |
| US6334117(B1) | 2001-12-01 | Covert et al. | Applicant |
| US6351223(B1) | 2002-02-01 | DeWeerd et al. | Applicant |
| US6356205(B1) | 2002-03-01 | Salvo et al. | Applicant |
| US6357034(B1) | 2002-03-01 | Muller et al. | Applicant |
| US6362745(B1) | 2002-03-01 | Davis | Applicant |
| US6363057(B1) | 2002-03-01 | Ardalan et al. | Applicant |
| US6366217(B1) | 2002-04-01 | Cunningham et al. | Applicant |
| US6366622(B1) | 2002-04-01 | Brown et al. | Applicant |
| US6369769(B1) | 2002-04-01 | Nap et al. | Applicant |
| US6370489(B1) | 2002-04-01 | Williams et al. | Applicant |
| US6373399(B1) | 2002-04-01 | Johnson et al. | Applicant |
| US6380851(B1) | 2002-04-01 | Gilbert et al. | Applicant |
| US6384722(B1) | 2002-05-01 | Williams | Applicant |
| US6389059(B1) | 2002-05-01 | Smith et al. | Examiner |
| US6393341(B1) | 2002-05-01 | Lawrence et al. | Applicant |
| US6393381(B1) | 2002-05-01 | Williams et al. | Applicant |
| US6393382(B1) | 2002-05-01 | Williams et al. | Applicant |
| US6396839(B1) | 2002-05-01 | Ardalan et al. | Applicant |
| US6400819(B1) | 2002-06-01 | Nakano et al. | Applicant |
| US6401081(B1) | 2002-06-01 | Montgomery et al. | Applicant |
| US6405018(B1) | 2002-06-01 | Reudink et al. | Applicant |
| US6411889(B1) | 2002-06-01 | Mizunuma et al. | Applicant |
| US6415245(B2) | 2002-07-01 | Williams et al. | Applicant |
| US6421354(B1) | 2002-07-01 | Godlewski | Applicant |
| US6421731(B1) | 2002-07-01 | Ciotti, Jr. et al. | Applicant |
| US6422464(B1) | 2002-07-01 | Terranova | Applicant |
| US6424270(B1) | 2002-07-01 | Ali | Applicant |
| US6424931(B1) | 2002-07-01 | Sigmar et al. | Applicant |
| US6430268(B1) | 2002-08-01 | Petite | Applicant |
| US6431439(B1) | 2002-08-01 | Suer et al. | Applicant |
| US6437692(B1) | 2002-08-01 | Petite et al. | Applicant |
| US6438575(B1) | 2002-08-01 | Khan et al. | Applicant |
| US6445291(B2) | 2002-09-01 | Addy et al. | Applicant |
| US6456960(B1) | 2002-09-01 | Williams et al. | Applicant |
| US6457038(B1) | 2002-09-01 | Defosse | Applicant |
| US6462644(B1) | 2002-10-01 | Howell et al. | Applicant |
| US6462672(B1) | 2002-10-01 | Besson | Applicant |
| US6477558(B1) | 2002-11-01 | Irving et al. | Applicant |
| US6483290(B1) | 2002-11-01 | Hemminger et al. | Applicant |
| US6484939(B1) | 2002-11-01 | Blaeuer | Applicant |
| US6489884(B1) | 2002-12-01 | Lamberson et al. | Applicant |
| US6491828(B1) | 2002-12-01 | Sivavec et al. | Applicant |
| US6492910(B1) | 2002-12-01 | Ragle et al. | Applicant |
| US6504357(B1) | 2003-01-01 | Hemminger et al. | Applicant |
| US6507794(B1) | 2003-01-01 | Hubbard et al. | Applicant |
| US6509722(B2) | 2003-01-01 | Lopata | Applicant |
| US6519568(B1) | 2003-02-01 | Harvey et al. | Applicant |
| US6538577(B1) | 2003-03-01 | Ehrke et al. | Applicant |
| US6542076(B1) | 2003-04-01 | Joao | Applicant |
| US6542077(B2) | 2003-04-01 | Joao | Applicant |
| US6543690(B2) | 2003-04-01 | Leydier et al. | Applicant |
| US6560223(B1) | 2003-05-01 | Egan et al. | Applicant |
| US6574603(B1) | 2003-06-01 | Dickson et al. | Applicant |
| US6584080(B1) | 2003-06-01 | Ganz et al. | Applicant |
| US6600726(B1) | 2003-07-01 | Nevo et al. | Applicant |
| US6608551(B1) | 2003-08-01 | Anderson et al. | Applicant |
| US6618578(B1) | 2003-09-01 | Petite | Applicant |
| US6618709(B1) | 2003-09-01 | Sneeringer | Applicant |
| US6628764(B1) | 2003-09-01 | Petite | Applicant |
| US6628965(B1) | 2003-09-01 | LaRosa et al. | Applicant |
| US6653945(B2) | 2003-11-01 | Johnson et al. | Applicant |
| US6654357(B1) | 2003-11-01 | Wiedeman | Applicant |
| US6671586(B2) | 2003-12-01 | Davis et al. | Applicant |
| US6674403(B2) | 2004-01-01 | Gray et al. | Applicant |
| US6678255(B1) | 2004-01-01 | Kuriyan | Applicant |
| US6678285(B1) | 2004-01-01 | Garg | Applicant |
| US6731201(B1) | 2004-05-01 | Bailey et al. | Applicant |
| US6735630(B1) | 2004-05-01 | Gelvin et al. | Applicant |
| US6747557(B1) | 2004-06-01 | Petite et al. | Applicant |
| US6771981(B1) | 2004-08-01 | Zalewski et al. | Applicant |
| US6804532(B1) | 2004-10-01 | Moon et al. | Applicant |
| US6816088(B1) | 2004-11-01 | Knoska et al. | Applicant |
| US6888876(B1) | 2005-05-01 | Mason et al. | Examiner |
| US6891838(B1) | 2005-05-01 | Petite | Applicant |
| US6914533(B2) | 2005-07-01 | Petite | Applicant |
| US6914893(B2) | 2005-07-01 | Petite | Applicant |
| US6959550(B2) | 2005-11-01 | Freeman et al. | Applicant |
| US7027416(B1) | 2006-04-01 | Kriz | Applicant |
| US7054271(B2) | 2006-05-01 | Brownrigg et al. | Applicant |
| US2001/0002210(A1) | 2001-05-01 | Petite | Applicant |
| US2001/0003479(A1) | 2001-06-01 | Fujiwara | Applicant |
| US2001/0021646(A1) | 2001-09-01 | Antonucci et al. | Applicant |
| US2001/0024163(A1) | 2001-09-01 | Petite | Applicant |
| US2001/0034223(A1) | 2001-10-01 | Rieser et al. | Applicant |
| US2001/0038343(A1) | 2001-11-01 | Meyer et al. | Applicant |
| US2002/0002444(A1) | 2002-01-01 | Williams et al. | Applicant |
| US2002/0012323(A1) | 2002-01-01 | Petite et al. | Applicant |
| US2002/0013679(A1) | 2002-01-01 | Petite | Applicant |
| US2002/0019725(A1) | 2002-02-01 | Petite | Applicant |
| US2002/0027504(A1) | 2002-03-01 | Davis et al. | Applicant |
| US2002/0031101(A1) | 2002-03-01 | Petite | Applicant |
| US2002/0032746(A1) | 2002-03-01 | Lazaridis | Applicant |
| US2002/0061031(A1) | 2002-05-01 | Sugar et al. | Examiner |
| US2002/0072348(A1) | 2002-06-01 | Wheeler et al. | Applicant |
| US2002/0089428(A1) | 2002-07-01 | Walden et al. | Applicant |
| US2002/0095399(A1) | 2002-07-01 | Devine et al. | Applicant |
| US2002/0098858(A1) | 2002-07-01 | Struhsaker | Applicant |
| US2002/0109607(A1) | 2002-08-01 | Cumeralto et al. | Applicant |
| US2002/0136233(A1) | 2002-09-01 | Chen et al. | Examiner |
| 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, D.O. | 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 | Examiner |
| US2004/0053639(A1) | 2004-03-01 | Petite | Applicant |
| US2004/0131125(A1) | 2004-07-01 | Sanderford, Jr. et al. | Applicant |
| US2004/0133917(A1) | 2004-07-01 | Schilling | Examiner |
| US2004/0183687(A1) | 2004-09-01 | Petite | Applicant |
| US2004/0228330(A1) | 2004-11-01 | Kubler et al. | Examiner |
| US2005/0190055(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0195768(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0195775(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0201397(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0243867(A1) | 2005-11-01 | Petite | Applicant |
| US2006/0098576(A1) | 2006-05-01 | Brownrigg et al. | Applicant |
| US2008/0186898(A1) | 2008-08-01 | Petite | Applicant |
| US2009/0006617(A1) | 2009-01-01 | Petite | Applicant |
| US2009/0068947(A1) | 2009-03-01 | Petite | Applicant |
| EP718954 | 1996-06-01 | Applicant | |
| EP7144 | 1998-02-01 | Applicant | |
| EP1096454 | 2001-05-01 | Applicant | |
| FR2817110 | 2002-05-01 | Applicant | |
| GB2229302 | 1990-09-01 | Applicant | |
| GB2247761 | 1992-03-01 | Applicant | |
| GB2262683 | 1993-06-01 | Applicant | |
| GB2297663 | 1996-08-01 | Applicant | |
| GB2310779 | 1997-09-01 | Applicant | |
| GB2326002 | 1998-12-01 | Applicant | |
| GB2336272 | 1999-10-01 | Applicant | |
| GB2352004 | 2001-01-01 | Applicant | |
| GB2352590 | 2001-01-01 | Applicant | |
| JP60261288 | 1985-12-01 | Applicant | |
| JP1255100 | 1989-10-01 | Applicant | |
| JP11353573 | 1999-12-01 | Applicant | |
| JP200113590 | 2000-04-01 | Applicant | |
| JP2001063425 | 2001-03-01 | Applicant | |
| JP2001088401 | 2001-04-01 | Applicant | |
| JP2001309069 | 2001-11-01 | Applicant | |
| JP2001319284 | 2001-11-01 | Applicant | |
| JP2001357483 | 2001-12-01 | Applicant | |
| JP2002007672 | 2002-01-01 | Applicant | |
| JP2002007826 | 2002-01-01 | Applicant | |
| JP2002085354 | 2002-03-01 | Applicant | |
| JP2002171354 | 2002-06-01 | Applicant | |
| KR2001025431 | 2001-04-01 | Applicant | |
| WO90/13197 | 1990-11-01 | Applicant | |
| WO9534177 | 1995-09-01 | Applicant | |
| WO98/00056 | 1998-01-01 | Applicant | |
| WO98/10393(A1) | 1998-03-01 | Applicant | |
| WO98/37528 | 1998-08-01 | Applicant | |
| WO99/13426 | 1999-03-01 | Applicant | |
| WO23956 | 2000-04-01 | Applicant | |
| WO/36812(A1) | 2000-06-01 | Applicant | |
| WO1/15114 | 2000-08-01 | Applicant | |
| WO1/24109 | 2001-04-01 | Applicant | |
| WO2/08725 | 2002-01-01 | Applicant | |
| WO2/08866 | 2002-01-01 | Applicant | |
| WO2/052521 | 2002-07-01 | Applicant | |
| WO2/052521 | 2002-07-01 | Applicant | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/021877 | 2003-03-01 | Applicant | |
| WO3/021877 | 2003-03-01 | Applicant | |
| WO4002014 | 2003-12-01 | Applicant |
Non-Patent Literature (50)
- Printout of 47 C.F.R. 15 (131 pages).Applicant
- 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
- 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
- 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
- Brownrigg, E.B. et al.; A Packet Radio Network for Library Automation; IEEE (1987); pp. 456-462.Applicant
- Brownrigg, E.B. et al.; A Packet Radio Networks; Architectures, Protocols, Technologies and Applications (1987), (introduction pp. ix-xviii); pp. 3-274.Applicant
- Brownrigg, E.B. et al.; Distributions, Networks, and Networking: Options for Dissemination; Workshop on Electronic Texts Session III (http://palimpsest.standford.edu/byorg/lc/etextw/sess3.html 1992): pp. 1-10.Applicant
- Brownrigg, E.B. et al.; User Provided Access to the Internet; (http://web.simmons.edu/˜chen/nit/NIT'92/033-bro.htm 2005) pp. 1-6.Applicant
- Wey, Jyhi-Kong et al.; Clone Terminator: An Authentication Service for Advanced Mobile Phone System; IEEE (1995); pp. 175-179.Applicant
- Davis, A.B. et al.; Knowledge-Based Management of Cellular Clone Fraud; IEEE (1992); pp. 230-234.Applicant
- Johnson, David B.; Routing in Ad Hoc Networks of Mobile Hosts; IEEE (1995); pp. 158-163.Applicant
- Jubin, John and Tornow, Janet D., “The Darpa Packet Radio Network Protocols,”Proceedings of the IEEE, vol. 75, No. 1, Jan. 1987, pp. 21-32.Applicant
- Kleinrock, Leonard and Kamoun, Farouk, “Hierarchical Routing for Large Networks,” North-Holland Publishing Company, Computer Networks 1, 1997, pp. 155-174.Applicant
- Perkins, C.E. et al.; Highly Dynamic Destination-Sequenced Distance-Vector Routing (DSDV) for Mobile Computers; SIGCOMM 94-9/94 London England UK (1994); pp. 234-244.Applicant
- Wu, J.; Distributed System Design; CRC Press (1999); pp. 177-180 and 204.Applicant
- Khan, Robert E., Gronemeyer, Steven A. Burchfiel, Jerry, and Kunzelman, Ronald C., “Advances in Packet Radio Technology” IEEE Nov. 1978, vol. 66, No. 11, pp. 1468-149.Applicant
- Babak Daneshrad, et al.; 1997 Project Summary “Mobile Versatile Radios (MoVeR); ”University of California, Los Angeles; pp. 1-4.Applicant
- Rajeev Jain, et al.; 1997 Project Summary “Held Untethered Nodes;” University of California, Los Angeles; pp. 1-5.Applicant
- Randy H. Katz and Eric A. Brewer; 1997 Project Summary “Towards a Wireless Overlay Internetworking Architecture;” University of California, Berkeley; pp. 1-8, including slide show presentation at http://daedalus.cs.berkeley,edu/talks/retreat.6.96/Overview.pdf.Applicant
- J.J. Garcia-Luna-Aceves, et al.; “Wireless Internet Gateways (Wings);” IEEE, 1997; pp. 1271-1276.Applicant
- Randy H. Katz, et al.; “The Bay Area Research Wireless Access Network (BARWAN);” Electrical Engeneering and Computer Science Department, University of California, Berkeley, CA; IEEE, 1996; pp. 15-20, including slide show presentation at http://daedalus.cs.berkeley.eduitalks/retreat.6.97/BARWAN.S97.ppt.Applicant
- USPTO's Decision dated Nov. 28, 2008 Denying Ex Pane 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.Nov. 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