Not Applicable.
1. Field of the Invention
This invention relates to a method, apparatus, and system for interfacing between electronic devices and more particularly relates to a method, apparatus, and system for communication between electronic devices using different protocols and different modulation schemes.
2. Background Art
Advances in technology have enabled manufacturers of many consumer products to automate their products and make customer use of the product more convenient. Many products today provide remote access of a product to a customer through radio waves. For example, people can open their garages without leaving their car and can determine whether security sensors in their house have been tripped. The problem, however, is that these devices often operate on different radio frequencies or use different communication protocols so that each product must have a unique corresponding device to interpret the radio frequency transmissions. As more and more products allow for remote access, the number of corresponding radio frequency devices increases. This creates clutter and makes operation of the devices cumbersome, which often negates the desired convenience to the customer.
For example, Manufacturer A may make a motion detector and Manufacturer B may make automatic window blinds. Both may use some type of radio frequency protocol to enable remote access, but each operates at a different radio frequency, and they may each use different communication protocols to interact with a corresponding remote device. Neither remote device can work with the other product however.
From the foregoing discussion, it will be appreciated that it would be an advancement in art to have a multiple protocol apparatus that is compact and cost-effective. It would be an additional advancement to have such an apparatus that could interface with devices having different radio frequencies that span large band gaps. It would be a further advancement to provide such an apparatus that could interface with devices having different types of modulation, be it amplitude modulation or frequency modulation. It would be a further advancement to have such an apparatus that is dynamically upgradeable such that new devices can be added. Such an apparatus is disclosed and claimed herein.
The features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by the practice of the invention without undue experimentation. The features and advantages of the invention may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims.
The invention disclosed herein has been developed in response to the present state of the art, and in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available radio frequency interface devices. Accordingly, the present invention has been developed to provide an apparatus, system, and method for interfacing between electronic devices that overcome many or all of the above-discussed shortcomings present in the art.
The illustrative apparatus which interfaces between electrical devices is provided with a plurality of modules configured to functionally execute one or more of the following steps: implementing the communication protocol(s) of one or more electronic devices, scanning for a first signal containing information transmitted in a learned communication protocol from one or more of the electrical devices, receiving and recognizing the first signal, decoding the first signal using the appropriate communication protocol to extract the desired information, translating the information extracted from the signal into a predetermined language, creating a second signal containing the translated information using a second communication protocol, sending the second signal to another electrical device, and receiving an acknowledgment that the second signal was received by the other electrical device.
These modules in the described illustrative embodiments include a scanning module, a decoding module, a translation module, a send/receive module, and a handshake module. The apparatus, in one illustrative embodiment, is configured to scan known frequencies on which multiple third-party and/or proprietary radio frequency devices operate. If the apparatus recognizes a signal in a known communication protocol on any of the frequencies, the apparatus may then demodulate and/or decode the signal to extract the desired information and then translate the information into a common predetermined communication language for sending to another electrical device.
An illustrative system of the present invention is also disclosed to interface between radio frequency devices. The system may be embodied in wireless network having programmable software, firmware, and hardware. In particular, the system, in one illustrative embodiment, includes a processor and a power supply. The system may also contain one or more radio frequency sensors or antenna. The system may also contain an AM/FM interface, a radio frequency sensor/antenna, and transceiver. A bus may operably connect the processor, sensors, transceiver, and third party radio frequency (AM/FM) interface.
In one illustrative embodiment, the system includes a memory containing the modules that make up the system discussed above. The system may also include a controller that acts as a backend central control system. In one illustrative embodiment, the controller may communicate with the apparatus wirelessly. In another illustrative embodiment, the controller may communicate with the apparatus through any number of electronic connections, including low-voltage wiring, fiber optic, infra red, power line carrier and other media as can be devised by those skilled in the art.
An illustrative method of the present invention is also presented for interfacing between radio frequency devices. The method in the illustrative embodiments substantially includes the steps necessary to carry out the functions presented above with respect to the operation of the described apparatus and system. In one illustrative embodiment, the method includes determining the frequency of one or more radio devices, scanning known frequencies for a signal using a known communication protocol and decoding the communication protocol. The method may also include the steps of converting the decoded information in the signal into a predetermined interface language and creating a communication packet containing the converted communication protocol for sending to controller. In another illustrative embodiment, the method includes the step of receiving an acknowledgment that the communication packet was received by the radio frequency device controller. The method steps disclosed herein may also be embodied as operations carried out by the computer-readable code of a computer program product.
Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present invention should be or are in any single embodiment of the invention. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present invention. Thus, discussion of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same illustrative embodiment.
Furthermore, the described features, advantages, and characteristics of the invention may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the invention may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the invention.
Another illustrative aspect of the present invention includes minimizing the total scanning time on any particular frequency by an apparatus such that the possibility of a missed signal on another frequency is reduced. In one illustrative embodiment, the apparatus may only analyze a small fraction of a signal to determine if the signal is a valid signal using a known protocol. When a valid signal is detected, the apparatus will proceed to analyze the whole signal, otherwise the signal is discarded and the apparatus continues scanning.
Another illustrative aspect of the present invention includes limiting the total scanning time for all of the frequencies scanned by an apparatus. In one embodiment, each communication protocol for which an apparatus is designed to scan is weighted to determine the resources used by that communication protocol. If the available resources are overextended such that the apparatus would likely miss a signal while scanning, the apparatus may dynamically optimize its scanning procedure to reduce the likelihood of a missed signal while scanning, prohibit additional communication protocols, or require the elimination of one of the communication protocols.
The features and advantages of the present invention will become more fully apparent from the following description and appended claims, or may be learned by the practice of the invention as set forth hereinafter.
In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
For the purposes of promoting an understanding of the principles in accordance with the disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Any alterations and further modifications of the inventive features illustrated herein, and any additional applications of the principles of the disclosure as illustrated herein, which would normally occur to one skilled in the relevant art and having possession of this disclosure, are to be considered within the scope of the disclosure claimed.
Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions that may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
Reference throughout this specification to “one embodiment,” “an embodiment” or “illustrative embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
Reference to computer program product may take any form capable of generating a signal, causing a signal to be generated, or causing execution of a program of machine-readable instructions on a digital processing apparatus. A computer program product may be embodied by a transmission line, a compact disk, digital-video disk, a magnetic tape, a Bernoulli drive, a magnetic disk, a punch card, flash memory, integrated circuits, or other digital processing apparatus or memory device which can be arrived at by those skilled in the art.
Furthermore, the described features, structures, or characteristics of the invention may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
It must be noted that, as used in this specification and the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Further, as used herein, the terms “comprising,” “including,” “containing,” “characterized by,” and grammatical equivalents thereof are inclusive or open-ended terms that do not exclude additional, unrecited elements or method steps.
The radio devices 102A-102D may communicate with an interface 108 by means of radio waves 104. In one embodiment, the interface 108 includes a radio frequency antenna 106A to pick up the radio waves 104. The interface 108 may have a range from the devices 102A-102D of up to about 50 feet. In another embodiment, the radio devices 102A-102D communicate with the interface 108 through a wired connection. The interface 108 can send and receive signals to and from the devices 102A-102D via the antenna 106A. It will be appreciated that each device 102A-102D may use its own distinct communication protocol. Thus, in one embodiment, the interface 108 can recognize multiple communication protocols to thereby communicate with all of devices 102A-102D. The devices 102E and 102F may communicate with interface 108 via a wired connection. In one embodiment, the wired connection is a low voltage wired connection.
The interface 108 may also include a processor 110 for executing control commands. The processor may be an Atmel MEGA Processor. In another embodiment, the processor 110 may be an ARM processor. The interface 108 may also include a power supply 112. In one embodiment, the power supply may be an AC to DC power supply. The power source may also be an AC power source, such as from a power grid, or a battery.
The interface 108 may include a third party radio frequency interface, which in the illustrative embodiment is represented as a secondary radio interface 114. The secondary radio interface 114 can be programmed to communicate with any radio frequency device within predetermined frequency ranges. In one embodiment, the frequency range is between about 100 MHZ and about 600 MHZ. In another embodiment, the frequency range is between about 600 MHZ and about 1000 MHZ. In still another embodiment, the frequency range is between about 300 MHZ and 1000 MHZ.
It will be appreciated by those of skill in the art that the secondary radio interface 114 can be programmed to read and decode radio frequency devices in other frequencies ranges and many different communication protocols. In one illustrative embodiment, the secondary radio interface 114 may use half duplex bi-directional radio frequency communication.
In one embodiment, the interface 108 includes a common language interface module, which in the illustrative embodiment is represented as a primary radio interface 116. The primary radio interface 116 may send and receive signals 107 through antenna 106B. The primary radio interface 116 may be a universal asynchronous radio transceiver of a kind known in the industry. In one embodiment, the primary radio interface 116 includes a transceiver which is configured to operate as part of the common language interface module. The primary radio interface 116 is generally configured to handle a single protocol, both incoming and outgoing and in this manner operates as a common language interface module. In another embodiment, the primary radio interface 116 operates in the frequency range of about 902 MHZ to 928 MHZ.
It will be appreciated by those of skill in the art that the interface 108 may therefore include two separate co-located radio transceivers, namely the primary radio interface 116 and the secondary radio interface 114.
A memory 118 may store executable code for operating the system 100. It will be appreciated by those of skill in the art that the code may also be embodied as hardware or firmware. The memory 118 may include one or more translation modules for bridging communication between the secondary radio interface 114 and the primary radio interface 116. The translation modules are executed by processor 110.
The memory 118 could include separate translation modules for communicating with each device 102A-102D. This is due to the fact that each of the devices 102A-102D may be manufactured by different manufacturers. Traditionally, each manufacturer uses its own proprietary communications protocol with its devices. For this reason, a separate translation module may be required for each device 102A-102D.
The secondary radio interface 114 and the primary radio interface 116 may cause the execution of the translation modules to accomplish the functionality associated with each one. For example, an incoming signal from any of the devices 102A-102D is received by secondary radio interface 114. Once received, the interface 108 calls upon the appropriate translation module to recognize the protocol of the signal, decode the signal using the appropriate communication protocol to extract the desired information, and translate the information extracted from the signal into the common language. The primary radio interface 116 then transmits the information in the common language.
Likewise, a signal may be received at the primary radio interface 116. The interface 108 may then call upon the appropriate translation module to translate information in the signal into the specified third party's communication protocol. The interface 108 can then send the signal to the appropriate device 102A-102D through the secondary radio interface 114.
In one illustrative embodiment, the translation modules may format the information, such as control commands, into the appropriate communications protocol required by the intended recipient device. This may include the appropriate headers, preambles, commands, etc. required to communicate with the devices 102A-102D. This may also include the correct encoding scheme, how to start or end a message, handshaking, and error correction schemes. This may further include the correct frequency and modulation schemes. Likewise, the translation modules are able to decode the message into the common interface language. In one embodiment, the translation modules are dynamically upgradeable such that new devices may be added to the system 100 at any time.
In order to create a translation module for a communication protocol, the communication protocol must be identified and analyzed. In the case of a third party manufacturer, it is preferable to secure the cooperation of the manufacturer to provide the information on its proprietary protocol. The third party protocol may also utilize a proprietary communication language. For example, the language may include commands and status information. For example, in the case of automated blinds, the commands may include “up,” “down,” “open,” and “close.” These commands must be correlated to the generic commands of the common interface language which may include commands having the same meaning. Thus, the translation module can translate the “up” command in the common interface language to the “up” command of the third party protocol and vice versa. In this sense, the interface 108 is able to mimic a third party control device. That is, the controlled devices 102A-102D do not know that the command originated from the interface 108 instead of its own remote control device.
In one illustrative embodiment, the interface 108 includes a relay 122, which is a low-voltage relay of a kind known in the art. The relay may be a 1 amp 40 VDC relay. Interface 108 also includes the appropriate circuitry to drive relay 122. Interface 108 may send a signal to device 102F using the relay 122. In actual use, a detected signal 104 or 107 could cause the relay 122 to be activated to emulate a contact switch closure to device 102F. In another embodiment, the interface 108 may include a contact input 120 to detect a momentary switch closure. When a momentary switch closure is detected through contact input 120, the interface 108 then translates this information into the common interface language and sends a message to a controller 126. Device 102E may provide the contact input signal. The controller 126 executes programming in response to that contact input 120, which may include sending a signal back to the interface 108 instructing it to close the relay 122 as well as carrying out any number of pre-programmed instructions, such as sending a signal to any of devices 102A-102D.
The inclusion of the contact inputs 120 allows the interface 108 to receive input from wired third-party devices, such as most passive infrared motion detectors, door contacts, stress sensors, light sensors, humidity and temperature sensors, smoke and carbon monoxide detectors, garage door openers and more. The inclusion of the relay 122 allows the interface 108 to control devices as well as emulate devices that are responsive to switch closures.
The interface 108 may also include a display 128 to facilitate use of the system 100 by a user. In one embodiment, the display 128 is an LED display.
The system 100 also includes a controller, such as the controller 126 shown in
The range between the controller 126 and the interface 108 may be up to about 150 feet. In one embodiment, the radio frequency enabler 124 is built into the controller 126. In another embodiment, the interface 108 is wired to the controller 126 and uses an RS-232 protocol. In another embodiment, the interface 108 is wired to the controller 126 using low voltage communications bus.
In one embodiment, the interface 108 acts as a radio frequency bridge. On one end of the interface 108 is a network, such as a home automation network or computer network, that may include the controller 126. Through CPU negotiation and transfer, the interface 108 forms a bridge between the network and third-party devices 102A-102F. On the third-party devices 102A-102F side of the interface 108 there will be an in and/or out communication protocol.
For example, one of the devices 102A-102F in the system 100 communicates with the controller 126 and receives commands from it to control a set of blinds 102B that are controlled through a radio protocol. The interface 108 would receive a command from the controller 126, emulate the SOMFY® blind protocol and control the device 102B. Likewise, the interface 108 could bridge to a motion sensor 102C that sends out a radio signal when it detects motion. The interface 108 would receive that signal, convert it to a message to the controller 126, which would alert a user or carry-out some other preprogrammed operation. The system 100 is capable of having multiple third-party protocols running simultaneously. Thus, one advantage of the present invention is that a single interface 108 can communicate with multiple different manufacturers' products, as represented at 102A-102F, instead of requiring multiple devices to communicate with the products 102A-102F. The interface 102 integrates and bridges the devices 102A-102F and allows outside interface capability.
From the foregoing, it will be appreciated that the system 100 recognizes different types of third-party devices 102 and can recognize all of their communication protocols and all of their different ways of passing communication packets back and forth. The interface 108 is configured to integrate this down to one common interface language and makes that available to an outside network. In one illustrative embodiment, that outside network is a network containing the controller 126. In another illustrative embodiment, the outside network could be a wired proprietary network. In another illustrative embodiment, the outside network could be an RS-232 outside interface that could then be utilized by anything with that particular communication protocol capability. In a wired embodiment, the connection may include without limitation, category 5 wire, Ethernet, and or use any other media format which can be selected by those skilled in the art. It will be appreciated that the interface 108 advantageously acts as a universal translator.
With some devices, for example some key fob devices 102A, they are multi-frequency units and must be aligned with devices on their network. This requires significant power from these battery-operated devices. If they were powered up all the time, their battery would drain very quickly. Accordingly, some key fob devices 102A go into a power saving or “hibernation” mode. The system 100 of the present invention allows a user to hit a button on the key fob device 102A which wakes up, transmits, goes back to sleep and it never has to wake up again if the user doesn't ever hit a button again. The battery-operated key fob typically has a much simpler radio frequency protocol to save power.
The system also allows a user to lower the window blinds 102B because the motion sensor 102C was tripped, even though they are made by different manufacturers using different protocols. In this scenario, when the motion sensor 102C is tripped, it sends a signal to the interface 108. The interface decodes and translates the signal into the common interface language. The interface 108 then sends a signal 107 to the controller 126 indicating that the motion sensor 102C has been tripped. Associated with this, is programming on the controller 126 which instructs the controller 126 to cause the blinds 102B to lower if the motion sensor 102C has been tripped. The controller 126 would send the interface 108 a common interface packet using the common interface language. The interface 108 would receive the signal and determine what action to take. For example, the command from the controller 126 may be to “Interface with the blinds 102B and send the user's particular command to it to lower the blinds.” The interface 108, knowing the particular communication protocol for the blind 102B, would form a communication packet to go out over that communication protocol and then indicate to the internal logic that a command is ready to go. When the interface 108 finds a time slot it will transmit on the particular frequency used by the blinds 102B and using the modulation protocol associated with the blinds 102B and with appropriate timing with the third-party device 102B, lower the blinds. Thus, two previously unrelated devices are able to interact one with another.
It will be appreciated that it is within the scope of the present invention to provide embodiments of the present invention which can transmit to one or more radio frequency devices using multiple protocols. Using the disclosure provided herein, those skilled in the art will readily be able to arrive at embodiments of the invention providing such features.
Referring to
The apparatus may also include a decoding module 304 configured to decode and/or demodulate a communication protocol utilized by a third-party or proprietary device recognized by the scanning module 302 on a particular frequency used by that third-party of proprietary device. A communication protocol may include without limitation, a signal, communication, or other recognizable information on a particular frequency. The types of communication protocols may include without limitation, FM, AM, OOK, FSK, and the like. The apparatus also includes a conversion module 306 configured to convert the decoded communication protocol into a predetermined communication language that can be interpreted by a controller type device or that can convert a predetermined communication language into a communication protocol. The decoding module 304, in connection with the conversion module 306, is capable of converting the commands and communications of multiple third party and proprietary devices into a single language or communication protocol for sending to a controller.
The apparatus 300 may include a send/receive module 308 configured to send and receive communication packets containing data in the common communication language to and from a controller, respectively. The send/receive module 308 may also be configured to send and receive communication packets to devices in their own proprietary communication protocol.
The apparatus 300 also includes a handshake module 310. The handshake module 310 establishes a communication path or link between the apparatus 300 and a radio frequency controller such that communication packets can be sent and the receipt of the communication packets can be acknowledged.
The apparatus 300 also includes a weighting module 312. The weighting module 312 employs a weighting factor to determine the allowable combination of radio frequencies to be scanned by the scanning module 302. For each scanned frequency, i.e., each communication protocol being scanned for, the weighting module 312 may determine the amount of time required to “lock” onto a signal using a particular protocol. If the time required to recognize a signal is excessive, a signal on another frequency may be missed. Ideally, the scanning module 302 never misses any signals. However, if the scanning module 302 spends too much time away from any one particular frequency while scanning for signals on other frequencies, then a signal on that particular frequency is likely to be missed.
Another factor taken into consideration, is that any particular communications protocol may require that a signal using that protocol be repeated any number of times. In the case where a signal is repeated numerous times, the scanning module 302 may spend more time away from that particular frequency on which the signal is being transmitted. This is because, if a signal is missed while scanning another frequency, the signal is still likely to be received by the apparatus 300 when it returns to the signal's frequency due to the fact that the signal is repeated. Thus, the more times a signal is repeated, the more time the scanning module 302 can spend scanning other frequencies.
Finally, the speed, or transmission rate, of the signal being receiving is taken into consideration by the weighting module 312. If the signal is slow, and each bit time is very long, it will take more time to lock onto a signal. Alternatively, if the signal is very fast, the lock time will be reduced, but the minimum allowed time away from that signal's frequency will also be greatly reduced hindering the allowed time on other channels.
The weighting module 312 may therefore take into account the time required to lock onto and validate a preamble or a first portion of a signal, whether the communication protocols call for repeating a signal, and the transmission rate of the signal being received in order to limit the number of scanned frequencies. In regards to the time required to validate a signal, in the event that the time required to validate is relatively excessive, then the apparatus 300 may be limited to scanning only one or two frequencies. If a communication protocol calls for repeating a signal multiple times, then it is more likely that the scanning module 312 will detect the signal even if the actual time scanning the frequency of the signal is relatively short. If the speed of the signal is slow, and each bit time is very long, it will take more time to validate a signal. Alternatively, if the signal's transmission rate is very fast, the lock time will be reduced, but the minimum time away from the frequency of the signal will be also be reduced hindering the allowed time on other frequencies.
In the illustrative embodiments of the present invention, each communication protocol will be weighted according to the factors discussed above to determine or limit the amount of frequencies scanned by the scanning module 302. This weight will determine the allowable combination of user protocols per apparatus 300. For example, in the case of a protocol that calls for a very fast signal that is not repeated, this protocol could be weighted at 100% meaning that only it would be allowed to operate on apparatus 300. In another example, a protocol that calls for a very fast signal that is repeated ten (10) times could be weighted at 10%. In this case, the apparatus 300 could comfortably scan for this protocol as well as another, assuming that this other protocol does not impair the ability to detect the first protocol.
The illustrations of
The schematic flow chart diagrams that follow are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of one illustrative embodiment of the presented method. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the format and symbols employed are provided to explain the logical steps of the method and are understood not to limit the scope of the method. Although various arrow types and line types may be employed in the flow chart diagrams, they are understood not to limit the scope of the corresponding method. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the method. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.
If a communication protocol is not detected 516 on this frequency, a next frequency is scanned 518. Previously known or currently determined frequencies are scanned randomly or in order until a signal, communication, or other communication protocol is found. In one exemplary embodiment, known frequencies are scanned in order from a first known frequency until a last known frequency and then the scanning repeats in the same order.
Once a communication protocol is found, it is decoded 508 and converted 510 into a predetermined communication language. The converted communication protocol is then packaged in a communication packet and sent to a controller or other device. In one embodiment, the device is a controller that interacts with a user in order to operate one or more different radio frequency devices, even if those different devices operate at different radio frequencies or different modulations. The process may then repeat or end 520.
The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application claims the benefit of U.S. Provisional Application No. 60/715,115, filed Sep. 7, 2005, which is hereby incorporated by reference herein in its entirety, including but not limited to those portions that specifically appear hereinafter, the incorporation by reference being made with the following exception: In the event that any portion of the above-referenced provisional application is inconsistent with this application, this application supercedes said above-referenced provisional application.
Number | Name | Date | Kind |
---|---|---|---|
2482773 | Hieronymus | Sep 1949 | A |
D163736 | Bangert, Jr. | Jun 1951 | S |
2828413 | Bowers | Mar 1958 | A |
2853585 | Danziger et al. | Sep 1958 | A |
3284667 | Harris et al. | Nov 1966 | A |
3491249 | Rabinow | Jan 1970 | A |
3579030 | Bentham et al. | May 1971 | A |
3689886 | Durkee | Sep 1972 | A |
3697821 | Johnson | Oct 1972 | A |
3706914 | Van Buren | Dec 1972 | A |
3707682 | Harris | Dec 1972 | A |
3736591 | Rennels et al. | May 1973 | A |
3746923 | Spira et al. | Jul 1973 | A |
3763394 | Blanchard | Oct 1973 | A |
3784875 | Baker et al. | Jan 1974 | A |
3867596 | Schadow | Feb 1975 | A |
3868546 | Gilbreath et al. | Feb 1975 | A |
3868547 | Kappenhagen et al. | Feb 1975 | A |
3885116 | Kodaira | May 1975 | A |
3918062 | Haruki et al. | Nov 1975 | A |
3940660 | Edwards | Feb 1976 | A |
3980954 | Whyte | Sep 1976 | A |
3986423 | Rossum | Oct 1976 | A |
3996441 | Ohashi | Dec 1976 | A |
4016561 | Parker et al. | Apr 1977 | A |
4057751 | Bonsignore et al. | Nov 1977 | A |
4060735 | Pascucci et al. | Nov 1977 | A |
4095139 | Symonds et al. | Jun 1978 | A |
D249141 | Mayo | Aug 1978 | S |
4123756 | Nagata et al. | Oct 1978 | A |
4131777 | Bailey et al. | Dec 1978 | A |
4156866 | Miller | May 1979 | A |
4163218 | Wu | Jul 1979 | A |
4169972 | Black et al. | Oct 1979 | A |
4185531 | Oberheim et al. | Jan 1980 | A |
4187528 | Morriss | Feb 1980 | A |
4194099 | Mickelson | Mar 1980 | A |
4196388 | Weller et al. | Apr 1980 | A |
4200862 | Campbell et al. | Apr 1980 | A |
4203096 | Farley et al. | May 1980 | A |
4206443 | Britton | Jun 1980 | A |
4225808 | Saraceni | Sep 1980 | A |
4246494 | Foreman et al. | Jan 1981 | A |
4253048 | Osako | Feb 1981 | A |
4259619 | Wall | Mar 1981 | A |
4262180 | Walter | Apr 1981 | A |
4274045 | Goldstein | Jun 1981 | A |
4277727 | LeVert | Jul 1981 | A |
4300090 | Weber | Nov 1981 | A |
4303811 | Parkinson | Dec 1981 | A |
4334171 | Parman et al. | Jun 1982 | A |
4336464 | Weber | Jun 1982 | A |
4338595 | Newman | Jul 1982 | A |
4339632 | Early et al. | Jul 1982 | A |
4359670 | Hosaka et al. | Nov 1982 | A |
4381456 | Saito et al. | Apr 1983 | A |
4388567 | Yamazaki et al. | Jun 1983 | A |
4390814 | Peek | Jun 1983 | A |
4392187 | Bornhorst | Jul 1983 | A |
4395660 | Waszkiewicz | Jul 1983 | A |
4418333 | Schwarzbach et al. | Nov 1983 | A |
4421966 | Pounds | Dec 1983 | A |
4436972 | Scanlon | Mar 1984 | A |
4437169 | Bertenshaw et al. | Mar 1984 | A |
4455546 | Roszel | Jun 1984 | A |
4463287 | Pitel | Jul 1984 | A |
4468542 | Pounds | Aug 1984 | A |
4471493 | Schober | Sep 1984 | A |
4484190 | Bedard | Nov 1984 | A |
4485374 | Meserow et al. | Nov 1984 | A |
4489385 | Miller et al. | Dec 1984 | A |
4491843 | Boubouleix | Jan 1985 | A |
4504778 | Evans | Mar 1985 | A |
4521843 | Pezzolo et al. | Jun 1985 | A |
4523132 | Christiansen et al. | Jun 1985 | A |
4524288 | Schimmelpennink et al. | Jun 1985 | A |
4527198 | Callahan | Jul 1985 | A |
4532395 | Zukowski | Jul 1985 | A |
4540917 | Luchaco et al. | Sep 1985 | A |
4550276 | Callahan et al. | Oct 1985 | A |
4560909 | Peil | Dec 1985 | A |
4563592 | Yuhasz et al. | Jan 1986 | A |
4575660 | Zaharchuk et al. | Mar 1986 | A |
4582967 | Brumit et al. | Apr 1986 | A |
4590614 | Erat | May 1986 | A |
D285066 | Liss et al. | Aug 1986 | S |
4611198 | Levinson et al. | Sep 1986 | A |
4628440 | Thompson | Dec 1986 | A |
4631377 | Imazeki et al. | Dec 1986 | A |
4635040 | Masot | Jan 1987 | A |
4638299 | Campbell | Jan 1987 | A |
4644320 | Carr et al. | Feb 1987 | A |
4680536 | Roszel et al. | Jul 1987 | A |
4684822 | Angott | Aug 1987 | A |
4689547 | Rowen et al. | Aug 1987 | A |
4691341 | Knoble et al. | Sep 1987 | A |
4695820 | D'Aleo et al. | Sep 1987 | A |
4697227 | Callahan | Sep 1987 | A |
4703306 | Barritt | Oct 1987 | A |
4714983 | Lang | Dec 1987 | A |
4716409 | Hart et al. | Dec 1987 | A |
4719446 | Hart | Jan 1988 | A |
4727296 | Zaharchuk et al. | Feb 1988 | A |
4728949 | Platte et al. | Mar 1988 | A |
4737769 | Masot | Apr 1988 | A |
4745351 | Rowen et al. | May 1988 | A |
4749917 | Angott et al. | Jun 1988 | A |
4751385 | Van Benthusysen et al. | Jun 1988 | A |
4755792 | Pezzolo et al. | Jul 1988 | A |
4764981 | Miyahara et al. | Aug 1988 | A |
4772824 | Gulledge | Sep 1988 | A |
4772825 | Tabor et al. | Sep 1988 | A |
4783581 | Flowers et al. | Nov 1988 | A |
4792731 | Pearlman et al. | Dec 1988 | A |
4797599 | Ference et al. | Jan 1989 | A |
4814776 | Caci et al. | Mar 1989 | A |
4823069 | Callahan et al. | Apr 1989 | A |
4825209 | Sasaki et al. | Apr 1989 | A |
4843386 | Wolf | Jun 1989 | A |
4864588 | Simpson et al. | Sep 1989 | A |
4876552 | Zakman | Oct 1989 | A |
4878010 | Weber | Oct 1989 | A |
4880950 | Carson et al. | Nov 1989 | A |
4889999 | Rowen | Dec 1989 | A |
4893062 | D'Aleo et al. | Jan 1990 | A |
4908806 | Nickolaus | Mar 1990 | A |
4918432 | Pauley et al. | Apr 1990 | A |
4918717 | Bissonnette et al. | Apr 1990 | A |
4924109 | Weber | May 1990 | A |
4924151 | D'Aleo et al. | May 1990 | A |
4940903 | Brown, Jr. et al. | Jul 1990 | A |
4948987 | Weber | Aug 1990 | A |
D310349 | Rowen | Sep 1990 | S |
4955084 | Umetsu et al. | Sep 1990 | A |
D311382 | Mayo et al. | Oct 1990 | S |
D311485 | Jacoby et al. | Oct 1990 | S |
D311678 | Graef et al. | Oct 1990 | S |
4980806 | Taylor et al. | Dec 1990 | A |
D313738 | Mayo et al. | Jan 1991 | S |
4995053 | Simpson et al. | Feb 1991 | A |
5003318 | Berneking et al. | Mar 1991 | A |
5012225 | Gill | Apr 1991 | A |
5017837 | Hanna et al. | May 1991 | A |
5027106 | Lizzi et al. | Jun 1991 | A |
5028853 | Brown, Jr. et al. | Jul 1991 | A |
5030893 | Spira et al. | Jul 1991 | A |
5034602 | Garcia, Jr. et al. | Jul 1991 | A |
D319429 | D'Aleo et al. | Aug 1991 | S |
5041825 | Hart et al. | Aug 1991 | A |
5051720 | Kittirutsunetorn | Sep 1991 | A |
5059871 | Pearlman et al. | Oct 1991 | A |
5079559 | Umetsu et al. | Jan 1992 | A |
5086385 | Launey et al. | Feb 1992 | A |
5099193 | Moseley et al. | Mar 1992 | A |
5103209 | Lizzi et al. | Apr 1992 | A |
5109222 | Welty | Apr 1992 | A |
5113498 | Evan et al. | May 1992 | A |
D327255 | D'Aleo et al. | Jun 1992 | S |
5128855 | Hilber et al. | Jul 1992 | A |
5146153 | Luchaco et al. | Sep 1992 | A |
5170487 | Peek | Dec 1992 | A |
5175477 | Grissom | Dec 1992 | A |
5187655 | Post et al. | Feb 1993 | A |
5189412 | Mehta et al. | Feb 1993 | A |
5191265 | D'Aleo et al. | Mar 1993 | A |
5209560 | Taylor et al. | May 1993 | A |
5225765 | Callahan et al. | Jul 1993 | A |
5237264 | Moseley et al. | Aug 1993 | A |
5239205 | Hoffman et al. | Aug 1993 | A |
5247293 | Nakagawa | Sep 1993 | A |
5248919 | Hanna et al. | Sep 1993 | A |
5280296 | Tan et al. | Jan 1994 | A |
D344264 | D'Aleo et al. | Feb 1994 | S |
5311656 | Eldershaw | May 1994 | A |
5321736 | Beasley | Jun 1994 | A |
5327426 | Dolin, Jr. et al. | Jul 1994 | A |
5340954 | Hoffman et al. | Aug 1994 | A |
5349362 | Forbes et al. | Sep 1994 | A |
5357170 | Luchaco et al. | Oct 1994 | A |
5361184 | El-Sharkawi et al. | Nov 1994 | A |
5361985 | Rein et al. | Nov 1994 | A |
5367133 | Schmidt et al. | Nov 1994 | A |
5373411 | Grass et al. | Dec 1994 | A |
5382947 | Thaler et al. | Jan 1995 | A |
5399940 | Hanna et al. | Mar 1995 | A |
5400041 | Strickland | Mar 1995 | A |
5400246 | Wilson et al. | Mar 1995 | A |
5401927 | Lundell et al. | Mar 1995 | A |
5430356 | Ference et al. | Jul 1995 | A |
5436510 | Gilbert | Jul 1995 | A |
5452291 | Eisenhandler et al. | Sep 1995 | A |
5455464 | Gosling | Oct 1995 | A |
5455761 | Kushiro et al. | Oct 1995 | A |
5463286 | D'Aleo et al. | Oct 1995 | A |
5467264 | Rauch et al. | Nov 1995 | A |
5473202 | Mudge et al. | Dec 1995 | A |
5481750 | Parise et al. | Jan 1996 | A |
5490144 | Tran et al. | Feb 1996 | A |
5495406 | Kushiro et al. | Feb 1996 | A |
5523631 | Fishman et al. | Jun 1996 | A |
5555150 | Newman, Jr. | Sep 1996 | A |
5563459 | Kurosawa et al. | Oct 1996 | A |
5565855 | Knibbe | Oct 1996 | A |
5565865 | So | Oct 1996 | A |
5574431 | McKeown et al. | Nov 1996 | A |
5588760 | So | Dec 1996 | A |
5598322 | Von Arx et al. | Jan 1997 | A |
5637930 | Rowen et al. | Jun 1997 | A |
5638296 | Johnson et al. | Jun 1997 | A |
5640141 | Myllymäki | Jun 1997 | A |
4095139 | Symonds et al. | Jul 1997 | A |
5657005 | Seebeck et al. | Aug 1997 | A |
5668358 | Wolf et al. | Sep 1997 | A |
5711588 | Rudisill | Jan 1998 | A |
5726644 | Jednacz et al. | Mar 1998 | A |
5736965 | Mosebrook et al. | Apr 1998 | A |
5748828 | Steiner et al. | May 1998 | A |
5796382 | Beeteson | Aug 1998 | A |
5801345 | Mikula-Curtis et al. | Sep 1998 | A |
5861809 | Eckstein et al. | Jan 1999 | A |
5905442 | Mosebrook et al. | May 1999 | A |
5912443 | Hasunuma | Jun 1999 | A |
5960942 | Thornton | Oct 1999 | A |
5962109 | Schwietz | Oct 1999 | A |
5975711 | Parker et al. | Nov 1999 | A |
5977901 | Fenner | Nov 1999 | A |
5982103 | Mosebrook et al. | Nov 1999 | A |
6032202 | Lea et al. | Feb 2000 | A |
6080940 | Rice | Jun 2000 | A |
6091205 | Newman, Jr. et al. | Jul 2000 | A |
6092903 | Higgins, Jr. | Jul 2000 | A |
6100659 | Will et al. | Aug 2000 | A |
6140987 | Stein et al. | Oct 2000 | A |
6169256 | Hanahara et al. | Jan 2001 | B1 |
6180895 | Hutchinson et al. | Jan 2001 | B1 |
6184481 | Chen | Feb 2001 | B1 |
6192282 | Smith et al. | Feb 2001 | B1 |
6199136 | Shteyn | Mar 2001 | B1 |
6201364 | Will et al. | Mar 2001 | B1 |
6207913 | Nakajima et al. | Mar 2001 | B1 |
6233132 | Jenski | May 2001 | B1 |
6310609 | Morgenthaler | Oct 2001 | B1 |
6331687 | Dunk et al. | Dec 2001 | B1 |
6355890 | Kuroda | Mar 2002 | B1 |
6359562 | Rubin | Mar 2002 | B2 |
6369524 | Sid | Apr 2002 | B1 |
6369800 | Nading et al. | Apr 2002 | B1 |
6400271 | Davies, Jr. et al. | Jun 2002 | B1 |
D461782 | Butler et al. | Aug 2002 | S |
6453687 | Sharood et al. | Sep 2002 | B2 |
6467924 | Shipman | Oct 2002 | B2 |
6493874 | Humpleman | Dec 2002 | B2 |
6510995 | Muthu et al. | Jan 2003 | B2 |
6523696 | Saito et al. | Feb 2003 | B1 |
6549190 | Windrem | Apr 2003 | B1 |
6555774 | Nielsen | Apr 2003 | B1 |
6575607 | Klemish et al. | Jun 2003 | B1 |
6593530 | Hunt | Jul 2003 | B2 |
6608271 | Duarte | Aug 2003 | B2 |
6618764 | Shteyn | Sep 2003 | B1 |
6640141 | Bennett | Oct 2003 | B2 |
6646843 | Newman, Jr. et al. | Nov 2003 | B1 |
6674248 | Newman, Jr. et al. | Jan 2004 | B2 |
6680730 | Shields et al. | Jan 2004 | B1 |
6753661 | Muthu et al. | Jun 2004 | B2 |
6774328 | Adams et al. | Aug 2004 | B2 |
6797902 | Farage et al. | Sep 2004 | B2 |
6882111 | Kan et al. | Apr 2005 | B2 |
6909424 | Liebenow et al. | Jun 2005 | B2 |
6931364 | Anturna | Aug 2005 | B1 |
6950087 | Knox et al. | Sep 2005 | B2 |
6952715 | Kronz | Oct 2005 | B1 |
6965848 | Ballus | Nov 2005 | B2 |
6967448 | Morgan et al. | Nov 2005 | B2 |
6967565 | Lingemann | Nov 2005 | B2 |
7130774 | Thomas et al. | Oct 2006 | B2 |
20010000422 | Sid | Apr 2001 | A1 |
20010047250 | Schuller et al. | Nov 2001 | A1 |
20010047251 | Kemp | Nov 2001 | A1 |
20010055003 | Chi et al. | Dec 2001 | A1 |
20020016639 | Smith et al. | Feb 2002 | A1 |
20020026533 | Dutta et al. | Feb 2002 | A1 |
20020037004 | Bossemeyer et al. | Mar 2002 | A1 |
20020137479 | Tsui | Sep 2002 | A1 |
20020196771 | Vij et al. | Dec 2002 | A1 |
20030009315 | Thomas et al. | Jan 2003 | A1 |
20030012035 | Bernard | Jan 2003 | A1 |
20030052770 | Mansfield, Jr. et al. | Mar 2003 | A1 |
20030056012 | Modeste et al. | Mar 2003 | A1 |
20030129969 | Rucinski | Jul 2003 | A1 |
20030158954 | Williams | Aug 2003 | A1 |
20030227894 | Wang et al. | Dec 2003 | A1 |
20030233429 | Matte et al. | Dec 2003 | A1 |
20040024624 | Ciscon et al. | Feb 2004 | A1 |
20040037288 | Bourgart et al. | Feb 2004 | A1 |
20040038683 | Rappaport et al. | Feb 2004 | A1 |
20040054747 | Breh et al. | Mar 2004 | A1 |
20040088082 | Ahmed | May 2004 | A1 |
20040113945 | Park et al. | Jun 2004 | A1 |
20040143428 | Rappaport et al. | Jul 2004 | A1 |
20040225811 | Fosier | Nov 2004 | A1 |
20040267385 | Lingemann | Dec 2004 | A1 |
20070019682 | Krzyzanowski | Jan 2007 | A1 |
20070019683 | Kryzyanowski | Jan 2007 | A1 |
Number | Date | Country |
---|---|---|
2 245 671 | Sep 2003 | CA |
30 08 339 | Sep 1981 | DE |
30 12 840 | Oct 1981 | DE |
32 21 873 | Jan 1984 | DE |
32 24 997 | Jan 1984 | DE |
219 637 | Mar 1985 | DE |
43 08 161 | Sep 1994 | DE |
103 06 080 | Aug 2004 | DE |
0 022 516 | Jan 1981 | EP |
0 040 339 | Nov 1981 | EP |
0 054 582 | Jun 1982 | EP |
0 196 347 | Oct 1986 | EP |
0 293 569 | Dec 1988 | EP |
0 327 128 | Aug 1989 | EP |
0 346 614 | Dec 1989 | EP |
0 357 136 | Mar 1990 | EP |
0 361 734 | Apr 1990 | EP |
0 435 224 | Jul 1991 | EP |
0 466 152 | Jan 1992 | EP |
0 513 443 | Nov 1992 | EP |
0 552 769 | Jul 1993 | EP |
0 555 869 | Aug 1993 | EP |
0 558 349 | Sep 1993 | EP |
0 616 451 | Sep 1994 | EP |
0 626 635 | Nov 1994 | EP |
0 687 078 | Dec 1995 | EP |
2 702 115 | Sep 1994 | FR |
1 090 891 | Nov 1967 | GB |
1 215 009 | Dec 1970 | GB |
2 076 180 | Nov 1981 | GB |
2 097 918 | Nov 1982 | GB |
2 099 222 | Dec 1982 | GB |
2 166 328 | Apr 1986 | GB |
WO-8606890 | Nov 1986 | WO |
WO-9008418 | Jul 1990 | WO |
WO-9313507 | Jul 1993 | WO |
WO-9532595 | Nov 1995 | WO |
WO-9729560 | Aug 1997 | WO |
Number | Date | Country | |
---|---|---|---|
20070183449 A1 | Aug 2007 | US |
Number | Date | Country | |
---|---|---|---|
60715115 | Sep 2005 | US |