Systems and methods for monitoring vehicle parking

Information

  • Patent Grant
  • 8223010
  • Patent Number
    8,223,010
  • Date Filed
    Tuesday, August 30, 2011
    13 years ago
  • Date Issued
    Tuesday, July 17, 2012
    12 years ago
Abstract
Embodiments of the present invention are generally directed to systems and methods of monitoring vehicle parking. An exemplary embodiment of the present invention provides a vehicle parking monitoring system that includes a parking space sensor enabled to detect the presence of at least one vehicle in a first parking space of a first parking area and a parking area transceiver in communication with the parking space sensor, the parking area transceiver configured to receive information from the parking space sensor and transmit the information to a gateway. The parking area transceiver is also configured to receive information from the gateway. The gateway is connected to a wide area network and configured to receive information from the parking area transceiver and transmit the information to the wide area network, the gateway is also configured to receive information from the wide area network and transmit the information to the parking area transceiver. Other aspects, features, and embodiments are also claimed and described.
Description
TECHNICAL FIELD

Embodiments of the present invention generally relate to remotely operated systems, and more particularly to a computerized system for monitoring, reporting on, and controlling remote systems by transferring information signals through a wide area network (WAN) and using software applications hosted on a connected server to appropriately process the information.


BACKGROUND

As is known, there are a variety of systems for monitoring and controlling manufacturing processes, inventory systems, emergency control systems, and the like. Most automatic systems use remote sensors and controllers to monitor and automatically respond to system parameters to reach desired results. A number of control systems utilize computers to process system inputs, model system responses, and control actuators to implement process corrections within the system. Both the electric power generation and metallurgical processing industries have had success controlling production processes by implementing computer controlled control systems in individual plants.


One way to classify control systems is by the timing involved between subsequent monitoring occurrences. Monitoring processes can be classified as aperiodic or random, periodic, and real-time. A number of remotely distributed service industries implement the monitoring and controlling process steps through manual inspection and intervention.


A periodic monitoring systems (those that do not operate on a predetermined cycle) are inherently inefficient as they require a service technician to physically traverse an area to record data, repair out of order equipment, add inventory to a vending machine, and the like. Such service trips are carried out in a number of industries with the associated costs being transferred to the consumers of the service.


Conversely, utility meter monitoring, recording, and client billing are representative of a periodic monitoring system. In the past, utility providers sent a technician from meter to meter on a periodic basis to verify meter operation and to record utility use. One method of cutting operating expenses in the utility industry involved increasing the period at which manual monitoring and meter data recording was performed. While this method decreased the monitoring and recording expense associated with more frequent meter observation and was convenient for consumers who favor the consistent billed amounts associated with “budget billing,” the utility provider retained the costs associated with less frequent meter readings and the processing costs associated with reconciling consumer accounts.


Lastly, a number of environmental and safety systems require constant or real-time monitoring. Heating, ventilation, and air-conditioning systems, fire reporting and damage control systems, alarm systems, and access control systems are representative systems that utilize real-time monitoring and often require immediate feedback and control. These real-time systems have been the target of control systems theory and application thereof for some time.


A problem with expanding the use of control systems technology to distributed systems are the costs associated with the sensor-actuator infrastructure required to monitor and control functions within such systems. The typical approach to implementing control system technology is to install a local network of hard-wired sensors and actuators along with a local controller. Not only is there expense associated with developing and installing appropriate sensors and actuators but the added expense of connecting functional sensors and controllers with the local controller. Another prohibitive cost associated with applying control systems technology to distributed systems is the installation and operational expense associated with the local controller.


Accordingly, an alternative solution to applying monitoring and control system solutions to distributed systems that overcomes the shortcomings of the prior art is desired.


SUMMARY OF EXEMPLARY EMBODIMENTS

Certain objects, advantages and novel features of the invention will be set forth in part in the description that follows and in part will become apparent to those skilled in the art upon examination of the following or may be learned with the practice of the invention. The objects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out in the appended claims.


To achieve the advantages and novel features, the present invention is generally directed to a cost effective method of monitoring and controlling remote devices. More specifically, the present invention is directed to a computerized system for monitoring, reporting, and controlling remote systems and system information transfer by transmitting information signals to a WAN gateway interface and using applications on a connected server to process the information. Because the applications server is integrated on a WAN, Web browsers can be used by anyone with Internet access (and the appropriate access permissions) to view and download the recorded data.


In accordance with a broad aspect of the invention, a system is provided having one or more sensors to be read and/or actuators to be controlled remotely, ultimately through a computer on the Internet. The sensors and/or actuators are interfaced with wireless transceivers that transmit and/or receive data to and from the Internet. In this regard, additional wireless transceivers may relay information between the transceivers disposed in connection with the sensors and actuators and a gateway to the Internet. It should be appreciated that, a portion of the information communicated includes data that uniquely identifies the sensors and/or actuators.


In accordance with one aspect of the invention, a system is configured to monitor and report system parameters. The system is implemented by using a plurality of wireless transceivers. At least one wireless transceiver is interfaced with a sensor, transducer, actuator or some other device associated with the application parameter of interest. In this regard, the term “parameter” is broadly construed and may include, but is not limited to, a system alarm condition, a system process variable, an operational condition, etc. The system also includes a plurality of transceivers that act as signal repeaters that are dispersed throughout the nearby geographic region at defined locations. By defined locations, it is meant only that the location of each transceiver is known to a central computer. The central computer may be informed of transceiver physical locations after permanent installation, as the installation location of the transceivers is not limited. Each transceiver that serves to repeat a previously generated data signal may be further integrated with its own unique sensor or a sensor actuator combination as required. Additional transceivers may be configured as stand-alone devices that serve to simply receive, format, and further transmit system data signals. Further, the system includes a local data formatter that is configured to receive information communicated from the transceivers, format the data, and forward the data via the gateway to one or more servers interconnected with the WAN. The server further includes means for evaluating the received information and identifying the system parameter and the originating location of the parameter. The server also includes means for updating a database or further processing the reported parameters.


Consistent with the broader concepts of the invention, the “means” for evaluating the received information and the “means” for reporting system parameters are not limited to a particular embodiment or configuration. Preferably, these “means” will be implemented in software that is executed by a processor within a server integrated with the Internet. However, dedicated WANs or Intranets are suitable backbones for implementing defined system data transfer functions consistent with the invention.


In one embodiment, a client retrieves configured system data by accessing an Internet Web site. In such an embodiment, a system consistent with the present invention acts as a data collector and formatter with data being delivered upon client request, with availability twenty-four hours a day, seven days a week.


In more robust embodiments, a system can be configured to collect, format, and deliver client application specific information on a periodic basis to predetermined client nodes on the WAN. In these embodiments, client intervention would serve to close the feedback loop in the control system.


In yet another embodiment, a system can be configured to collect, format, and control client application specific processes by replacing a local control computer with a WAN interfaced server and integrating system specific actuators with the aforementioned system transceivers.


It should be further appreciated that the information transmitted and received by the wireless transceivers 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 networked wireless transceivers, the local gateways, and the central server.


In yet a further embodiment, a system can be configured using the present invention to translate and transmit control signals from an existing local controller via the networked wireless transceivers. In this regard, the system of the present invention would require a data translator to tap into the data stream of an existing control system. Distinct control system signals may be mapped to function codes used by the present invention in order to provide customer access to control system data. In this way, the system of the present invention can be integrated with present data collection and system controllers inexpensively, as customers will only have to add a data translator and a wireless transmitter or transceiver as the application demands. By integrating the present invention with the data stream generated by present monitoring and control systems, potential customers enjoy the benefits of the present invention without the difficulties associated with integrating sensors and actuators to monitor individual system parameters.





BRIEF DESCRIPTION OF FIGURES

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. In the drawings:



FIG. 1 is a block diagram of a prior art control system;



FIG. 2 is a block diagram illustrating a monitoring/control system of the present invention;



FIG. 3A is a functional block diagram that illustrates a transmitter in accordance with the present invention integrated in a portable device with user operable buttons that trigger data transmissions as desired;



FIG. 3B is a functional block diagram that illustrates the integration of a sensor with a transmitter in accordance with the invention;



FIG. 3C is a block diagram illustrating a transceiver in accordance with the present invention integrated with a sensor and an actuator;



FIG. 3D is a functional block diagram further illustrating the transceiver of FIG. 3C as applied to a heating, ventilation, and air conditioning system controller;



FIG. 3E is a functional block diagram illustrating the combination of the transceiver of FIG. 3D with a global positioning system (GPS) receiver;



FIG. 4 is a functional block diagram that illustrates the functional components of a local WAN gateway constructed in accordance with the invention;



FIG. 5 is a diagram illustrating WAN connectivity in a system constructed in accordance with the invention;



FIG. 6 is a block diagram illustrating a client specific application in accordance with the invention (simple data collection or monitoring);



FIG. 7 is a block diagram illustrating another data monitoring and reporting application consistent with the present invention;



FIG. 8 is a block diagram illustrating a third client specific application in accordance with the invention (monitoring and controlling a process);



FIG. 9 is a block diagram illustrating the present invention as deployed in a particular business application;



FIG. 10 is a block diagram further illustrating the present invention as deployed in a plurality of business applications;



FIG. 11 is a table illustrating the message protocol of the present invention;



FIG. 12 illustrates three sample messages using the message protocol of the present invention;



FIG. 13 is a block diagram illustrating the system of the present invention integrated with the local controller of FIG. 1; and



FIG. 14 is a block diagram illustrating the system of the present invention integrated with a mobile inventory unit.





DETAILED DESCRIPTION OF PREFERRED & ALTERNATIVE EMBODIMENTS

Having summarized the invention above, reference is now made in detail to the description of the invention as illustrated in the drawings. While the invention will be described in connection with these drawings, there is no intent to limit it to the embodiment or embodiments disclosed therein. On the contrary, the intent is to cover all alternatives, modifications and equivalents included within the spirit and scope of the invention as defined by the appended claims.


Referring now to the drawings, reference is made to FIG. 1, which is a block diagram illustrating certain fundamental components of a prior art control system 100. More particularly, a prior art control system 100 includes a plurality of sensor actuators 111, 112, 113, 114, 115, 116, and 117 electrically coupled to a local controller 110. In a manner well known in the art of control systems, local controller 110 provides power, formats and applies data signals from each of the sensors to predetermined process control functions, and returns control signals as appropriate to the system actuators. Often, prior art control systems are further integrated via the public switched telephone network (PSTN) 120 to a central controller 130. Central controller 130 can be further configured to serve as a technician monitoring station or to forward alarm conditions via PSTN 120 to appropriate public safety officers.


Prior art control systems consistent with the design of FIG. 1 require the development and installation of an application-specific local system controller, as well as, the routing of electrical conductors to each sensor and actuator as the application requires. Such prior art control systems are typically augmented with a central controller 130 that may be networked to the local controller 110 via PSTN 120. As a result, prior art control systems often consist of a relatively heavy design and are subject to a single point of failure should local controller 110 go out of service. In addition, these systems require electrical coupling between the local controller and system sensors and actuators. As a result, appropriately wiring an existing industrial plant can be a dangerous and expensive proposition.


Having described a prior art control system and delineated some of its shortcomings, reference is now made to FIG. 2, which is a block diagram that illustrates a control system in accordance with the present invention. Control system 200 consists of one or more sensor/actuators 212, 214, 216, 222, and 224 each integrated with a transceiver. The transceivers are preferably RF (Radio Frequency) transceivers, that are relatively small in size and transmit a relatively low power RF signal. As a result, in some applications, the transmission range of a given transceiver may be relatively limited. As will be appreciated from the description that follows, this relatively limited transmission range of the transceivers is an advantageous and desirable characteristic of control system 200. Although the transceivers are depicted without a user interface such as a keypad, in certain embodiments of the invention the transceivers may be configured with user selectable buttons or an alphanumeric keypad. Often, the transceivers will be electrically interfaced with a sensor or actuator, such as a smoke detector, a thermostat, a security system, etc., where external buttons are not needed.


Control system 200 also includes a plurality of stand-alone transceivers 211, 213, 215, and 221. Each stand-alone transceiver 211, 213, 215, and 221 and each of the integrated transceivers 212, 214, 216, 222, and 224 may be configured to receive an incoming RF transmission (transmitted by a remote transceiver) and to transmit an outgoing signal. This outgoing signal may be another low power RF transmission signal, a higher power RF transmission signal, or alternatively may be transmitted over a conductive wire, fiber optic cable, or other transmission media. The internal architecture of a transceiver integrated with a sensor/actuator 212 and a stand-alone transceiver 211 will be discussed in more detail in connection with FIGS. 3A through 3C. It will be appreciated by those skilled in the art that integrated transceivers 212, 214, 216, 222, and 224 can be replaced by RF transmitters (not shown) for client specific applications that require data collection only.


Local gateways 210 and 220 are configured and disposed to receive remote data transmissions from the various stand-alone transceivers 211, 213, 215, and 221 or integrated transceivers 212, 214, 216, 222, and 224 having an RF signal output level sufficient to adequately transmit a formatted data signal to the gateways. Local gateways 210 and 220 analyze the transmissions received, convert the transmissions into TCP/IP format and further communicate the remote data signal transmissions via WAN 230. In this regard, and as will be further described below, local gateways 210 and 220 may communicate information, service requests, control signals, etc. to remote sensor/actuator transceiver combinations 212, 214, 216, 222, and 224 from server 260, laptop computer 240, and workstation 250 across WAN 230. Server 260 can be further networked with database server 270 to record client specific data.


It will be appreciated by those skilled in the art that if an integrated transceiver (either of 212, 214, 216, 222, and 224) is located sufficiently close to local gateways 210 or 220 such that its RF output signal can be received by a gateway, the RF data signal need not be processed and repeated through stand-alone transceivers 211, 213, 215, or 221.


It will be further appreciated that a monitoring system constructed in accordance with the teachings of the present invention may be used in a variety of environments. In accordance with a preferred embodiment, a monitoring system such as that illustrated in FIG. 2 may be employed to monitor and record utility usage by residential and industrial customers as illustrated in FIG. 6. Another preferred monitoring system is illustrated in FIG. 7. FIG. 7 depicts the transfer of vehicle diagnostics from an automobile via a RF transceiver integrated with the vehicle diagnostics bus to a local transceiver that further transmits the vehicle information through a local gateway onto a WAN.


It will be further appreciated that a monitoring and control system consistent with the present invention may be used in a variety of environments. In accordance with a preferred embodiment, a control system such as that illustrated in FIG. 2 may be employed to monitor and control an irrigation system as illustrated in FIG. 8. Another preferred control system is illustrated in FIG. 9. FIG. 9 depicts a business application of a control system wherein the operation of a parking facility may be automated.


As will be further appreciated from the discussion herein, transceivers 212, 214, 216, 222, and 224 may have substantially identical construction (particularly with regard to their internal electronics), which provides a cost effective implementation at the system level. Furthermore, a plurality of stand-alone transceivers 211, 213, 215, and 221, which may be identical, are disposed in such a way that adequate coverage in an industrial plant or community is provided. Preferably, stand-alone transceivers 211, 213, 215, and 221 may be dispersed sufficient that only one stand-alone transceiver will pick up a transmission from a given integrated transceiver 212, 214, 216, 222, and 224 (due in part to the low power transmission nature of each transmitter). However, in certain instances two, or even more, stand-alone transceivers may pick up a single transmission. Thus, the local gateways 210 and 220 may receive multiple versions of the same data transmission signal from an integrated transceiver, but from different stand-alone transceivers. The local gateways 210 and 220 may utilize this information to triangulate, or otherwise more particularly assess 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.


In accordance with the preferred embodiment shown in FIG. 2, integrated transceivers 212, 214, 216, 222, and 224 may be disposed within automobiles (see FIG. 7), a rainfall gauge (see FIG. 8), or a parking lot access gate (see FIG. 9) to monitor vehicle diagnostics, total rainfall and sprinkler supplied water, and access gate position, respectively. 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 210 and 220 may communicate with all system transceivers. Since local gateways 210 and 220 are permanently integrated with WAN 230, server 260 can host application specific software which was typically hosted in an application specific local controller as shown in FIG. 1. Of further significance, the data monitoring and control devices of the present invention need not be disposed in a permanent location as long as they remain within signal range of a system compatible transceiver that subsequently is within signal range of a local gateway interconnected through one or more networks to server 260. In this regard, small application specific transmitters compatible with control system 200 can be worn or carried about one's person as will be further described below.


In one embodiment, server 260 collects, formats, and stores client specific data from each of the integrated transceivers 212, 214, 216, 222, and 224 for later retrieval or access from workstation 250 or laptop 240. In this regard, workstation 250 or laptop 240 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 260 may perform the additional functions of hosting application specific control system functions and replacing the local controller by generating required control signals for appropriate distribution via WAN 230 and local gateways 210 and 211 to the system 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 270 and server 260 may act solely as a data collection and reporting device with client workstation 250 generating control signals for the system.


It will be appreciated by those skilled in the art that the information transmitted and received by the wireless transceivers of the present invention may be further integrated with other data transmission protocols for transmission across telecommunications and computer networks 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 networked wireless transceivers, the local gateways, and the central server.


Reference is now made to FIG. 3A, which is a block diagram that illustrates the functional components of a RF transmitter 320, of a type worn or carried by a person, in more detail. Blocks 327 and 329 represent physical buttons, which a user may actuate to cause the RF transmitter 320 to initiate different signal transmissions. In the illustrated embodiment, these include a “transmit” button 327 and a panic or “emergency” button 329. Of course, additional, fewer, or different buttons may be provided on a given transmitter, depending upon the system or implementation desired. Each of these buttons may be electrically wired to a data interface 321 which is configured to receive electrical signals from buttons 327 and 329, and ultimately convey that information to a data formatter 324. In one embodiment, data interface 321 may simply comprise an addressable port that may be read by the data formatter 324.


For example, each of the signal lines extending between the buttons and the data interface 321 may be pulled up by individual pull up resistors (not shown). Depressing any of the individual buttons may ground the electrical signal line interconnecting the respective button and the data interface 321. Data formatter 324 may constantly read from the port defined by data interface 321, and all bit positions should remain high at any given time, if no buttons are depressed. If, however, the data formatter 324 reads a zero in one or more of the bit positions, it then recognizes that one or more of the buttons 327 and 329 have been depressed.


Each transmitter unit may be configured to have a unique identification code (e.g., transmitter identification number) 326, that uniquely identifies the transmitter to the functional blocks of control system 200 (see FIG. 2). This transmitter identification number may be electrically programmable, and implemented in the form of, for example, an EPROM. Alternatively, the transmitter identification number may be set/configured through a series of DIP switches. Additional implementations of the transmitter identification number, whereby the number may be set/configured, may be implemented consistent with the broad concepts of the present invention.


Finally, an additional functional block of the transmitter 320 is a RF transmitter 328. This circuit is used to convert information from digital electronic form into a format, frequency, and voltage level suitable for transmission from antenna 323 via an RF transmission medium.


The data formatter 324 operates to format concise data packets 330 that may be transmitted via RF to a nearby transceiver. From a substantive basis, the information conveyed includes a function code, as well as, a transmitter identification number. As previously mentioned, the transmitter identification number is set for a given transmitter 320. When received by server 260 (see FIG. 2), the transmitter identification number may be used to access a look up table that identifies, for example, the person assigned to carry that particular transmitter. Additional information about the person may also be provided within the lookup table, such as, a physical description, and/or any other information that may be deemed appropriate or useful under the circumstances or implementation of the particular system.


In addition, a function code is communicated from RF transmitter 320 to the nearby transceiver. FIG. 3A illustrates a lookup table 325 that may be provided in connection with data formatter 324. Lookup table 325 may be provided to assign a given and unique function code for each button pressed. For example, transmit button 327 may be assigned a first code to identify the party depressing the button. The emergency button 329 may be assigned a second code. Furthermore, additional codes may be provided as necessary to accommodate additional functions or features of a given transmitter 320. Thus, in operation, a user may depress the emergency button 329, which is detected by the data formatter 324. The data formatter 324 may then use the information pertaining to the emergency button 329 to access a look up table 325 to retrieve a code that is uniquely assigned to emergency button 329. The data formatter 324 may also retrieve the pre-configured transmitter identification number 326 in configuring a data packet 330 for communication via RF signals to a nearby transceiver.


Reference is now made briefly to FIG. 3B, which is a block diagram illustrating certain functional blocks of a similar transmitter 340 that may be integrated with sensor 310. For example, sensor 310 in its simplest form could be a two-state device such as a smoke alarm. Alternatively, the sensor 310 may output a continuous range of values to the data interface 321. If the signal output from the sensor 310 is an analog signal, the data interface 321 may include an analog-to-digital converter (not shown) to convert signals output to the actuator 340. Alternatively, a digital interface (communicating digital signals) may exist between the data interface 321 and each sensor 310.


As illustrated, many of the components of RF transmitter 340 are similar to that of RF transmitter 320 and need not be repeated herein. The principal difference between the configurations of RF transmitter 320 of FIG. 3A and the RF transmitter 340 of FIG. 3B lies at the input of the data interface 321. Specifically, RF transmitter 320 included user interface buttons 327 and 329. RF transmitter 340, illustrates electrical integration with sensor 310. Unique transmitter identification code 326 coupled with a function code for a smoke alarm on condition is formatted by data controller 324 for transformation into a RF signal by RF transmitter 328 and transmission via antenna 323. In this way, data packet 330 communicated from transmitter 340 will readily distinguish from similar signals generated by other RF transmitters in the system. Of course, additional and/or alternative configurations may also be provided by a similarly configured RF transmitter. For example, a similar configuration may be provided for a transmitter that is integrated into, for example, a carbon monoxide detector, a door position sensor and the like. Alternatively, system parameters that vary across a range of values may be transmitted by RF transmitter 340 as long as data interface 321 and data controller 324 are configured to apply a specific code, consistent with the input from sensor 310. As long as the code was understood by server 260 or workstation 250 (see FIG. 2) the target parameter could be monitored with the present invention.


Reference is now made to FIG. 3C, which is a block diagram similar to that illustrated in FIGS. 3A and 3B, but illustrating a transceiver 360 that is integrated with a sensor 310 and an actuator 380. In this illustration, data interface 321 is shown with a single input from sensor 310. 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 thermister to report an ambient temperature. The condition of related parameters can be input to data interface 321 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 321 as well.


The addition of actuator 380 to the assembly permits data interface 321 to apply control signals to the manual temperature control for the temperature set point, the climate control mode switch, and the system on/off switch. In this way, a remote workstation 250 or laptop 240 with WAN access (see FIG. 2) could control a home heating system from a remote location.


Again, each of these various input sources are routed to data interface 321 which provides the information to a data controller 324. The data controller may utilize a look up table to access unique function codes that are communicated in data packet 330, along with a transceiver identification code 326 via RF, to a local gateway and further onto a WAN. In general, the operation of transceiver 360 will be similar to that described for a transmitter as previously illustrated in FIGS. 3A and 3B. It is significant to note that data packet 330 will include a concatenation of the individual function codes selected for each of the aforementioned input parameters. As by way of example, server 260 may provide client workstation 250 with a Web page display that models a common home thermostat. As previously described, either server 260 or workstation 250 may include application software that would permit a user with access to remotely adjust the controls on a home heating system by adjusting related functional controls on a graphical user interface updated with feedback from the aforementioned control system.


Reference is now made to FIG. 3D, which is a block diagram further illustrating the transceiver of FIG. 3C in light of the home heating system described above. Specifically, transceiver 360 is shown with four specific parameters related to four specific function codes as illustrated in look up table 325. In this regard, sensor(s) 310 (one sensor shown for simplicity) inputs a data signal to data interface 321. Data controller receives an input from data interface 321 that it associates with a specific function code as shown in look up table 325. Data controller 324 assembles data packet 332 by concatenating received data packet 330 with its own transceiver identification code 326 and its own specific function codes. Data packet 332 is configured by RF transceiver 350 for transmission via antenna 323 to either a stand-alone transceiver as shown in FIG. 2, or alternatively, to local gateway 210. It will be appreciated by persons skilled in the art that data interface 321 may be uniquely configured to interface with specialized sensor(s) 310. This circuit, therefore, may differ from transceiver to transceiver, depending upon the remote system parameter that is monitored and the related actuator to be controlled. Implementation of data interface 321 will be understood by persons skilled in the art, and need not be described herein.


Reference is now made to FIG. 3E, which is a block diagram further illustrating the transceiver of FIG. 3C in combination with a GPS receiver. Specifically, GPS receiver 327 replaces data interface 321, sensor 310, and actuator 380 as illustrated in FIG. 3C. In this regard, GPS receiver 327 inputs a data signal containing latitude and longitude coordinates to data controller 324. Data controller 324 assembles data packet 332 by concatenating received data packet 330 with its own transceiver identification code 326 and the coordinates received from GPS receiver 327. Data packet 332 is configured by RF transceiver 350 for transmission via antenna 323 to either a stand-alone transceiver as shown in FIG. 2, or alternatively, to local gateway 210 as previously described.


Having illustrated and described the operation of the various combinations of RF transmitters and transceivers consistent with the present invention, reference is now made to FIG. 4, which is a block diagram illustrating certain principal components and the operation of a local gateway 210 of a control system 100 (see FIG. 2) constructed in accordance with the present invention. The primary physical components that may be provided within local gateway 210 are a transceiver 420, a CPU 422, a memory 424, a network card 426, a DSL modem 428, an ISDN card 430, as well as other components not illustrated in the FIG. 4 that would enable a TCP/IP connection to WAN 230. The transceiver 420 is configured to receive incoming signals consistently formatted in the convention previously described. Local gateway 210 may be configured such that memory 424 includes look up table 425 to assist in identifying the remote and intermediate transceivers used in generating and transmitting the received data transmission. Program code within the memory 424 may also be provided and configured for controlling the operation of a CPU 422 to carry out the various functions that are orchestrated and/or controlled by local gateway 210. For example, memory 424 may include program code for controlling the operation of the CPU 422 to evaluate an incoming data packet to determine what action needs to be taken. In this regard, look up tables 425 may also be stored within memory 424 to assist in this process. Furthermore, memory 424 may be configured with program code configured to identify a remote transceiver 427 or identify an intermediate transceiver 429. Function codes, transmitter and or transceiver identification numbers, may all be stored with associated information within look up tables 425.


Thus, one look up table may be provided to associate transceiver identification numbers with a particular user. Another look up table may be used to associate function codes with the interpretation thereof. For example, a unique code may be associated by a look up table to identify functions such as test, temperature, smoke alarm active, security system breach, etc. In connection with the lookup tables 425, memory 424 may also include a plurality of code segments that are executed by CPU 422, and which largely control the operation of the computer. For example, a first data packet segment 330 may be provided to access a first lookup table to determine the identity of the transceiver which transmitted the received message. A second code segment may be provided to access a second lookup table to determine the proximate location of the message generating transceiver, by identifying the transceiver that relayed the message. A third code segment may be provided to identify the content of the message transmitted. Namely, is it a fire alarm, a security alarm, an emergency request by a person, a temperature control setting, etc. Consistent with the invention, additional, fewer, or different code segments may be provided to carryout different functional operations and data signal transfers throughout the transceiver network.


The local gateway 210 may also include one or more mechanisms through which to communicate with remote systems. For example, the gateway may include a network card 426, which would allow the gateway 210 to communicate across a local area network to a network server, which in turn may contain a backup gateway to WAN 230. Alternatively, local gateway 210 may contain a DSL modem 428, which may be configured to provide a direct dial link to a remote system, by way of the PSTN. Alternatively, local gateway 210 may include an ISDN card 430 configured to communicate via an ISDN connection with a remote system. Other communication gateways may be provided as well to serve as primary and or backup links to WAN 230 or to local area networks that might serve to permit local monitoring of gateway health and data packet control.


Reference is now made to FIG. 5, which is a diagram illustrating WAN connectivity in a system constructed in accordance with the invention. In this regard, local gateway 210 is configured to transmit control signals and receive data signals using the open data packet protocol as previously described. Local gateway 210 is preferably interconnected permanently on WAN 230 and configured to translate received data signals for WAN transfer via TCP/IP. A server 530 configured with web applications and client specific applications as required is connected to WAN 230 via router 510 and further protected and buffered by firewall 520. Consistent with the present invention, server 530 is assisted in its task of storing and making available client specific data by database server 540. A workstation 560 configured with a Web browser is connected to WAN 230 at client premises by any suitable means known by those of skill in the art. Alternatively, clients may access WAN 230 via remote laptop 550 or other devices configured with a compatible Web browser. In this way, server 530 may provide client specific data upon demand.


Having described the control system of FIG. 2, reference is now made to FIG. 6 which illustrates a specific monitoring embodiment consistent with application of the invention. More specifically, FIG. 6 illustrates a remote utility meter monitoring system 600. Remote utility meter subsystem 610 consists of utility meter 613 and an appropriately integrated sensor 612 wherein the current utility meter operational status and current utility meter usage total is transmitted via functional codes along with a transceiver identification code in a manner previously described by transmitter 614 to stand-alone transceiver 221. Stand-alone transceiver 221 further processes and transmits the encoded data to local gateway 210 which translates the data packet information into TCP/IP format for transfer across WAN 230 to server 260. Server 260 collects and formats the utility meter information for viewing and or retrieval upon client demand in a manner previously described.


Having described a specific client application consistent with the present invention wherein the remote transmitter is permanently integrated with a stationary data input point (a utility meter), reference is now made to FIG. 7 which more fully illustrates the flexibility of the invention. More specifically, FIG. 7 illustrates a remote automotive diagnostics monitoring system 700. Remote automotive diagnostics interface unit 710 consists of sensor 712 integrated with the vehicle diagnostics data bus 711, and transmitter 714 wherein contents of the vehicle diagnostics can be downloaded upon a control signal to sensor 712 from a remote location serviced by local gateway 210. In this manner, a vehicle in need of service but still capable of accessing the vehicle diagnostics codes can be remotely diagnosed by uploading the information through remote automotive diagnostics monitoring system 700 and accessing a custom report created by server 260 in a manner previously described. In this regard, server 260 could be configured to perform any of a number of levels of diagnostics and provide service manual instructions, figures, and local authorized service contact information via WAN 230 on a fee basis or per a predetermined level of service plan.


Having described a monitoring system consistent with the present invention wherein the control signal initiates the monitoring process, reference is now made to FIG. 8. FIG. 8 illustrates a client specific control system consistent with both monitoring and control functions of the invention. More specifically, FIG. 8 illustrates a remote irrigation control system 800. For simplicity, controlled area 810 is represented by a single rain gauge 813 and a single related spray head 817. It is easy to see that such a system could be modified and expanded to monitor and control any of a number of irrigation systems integrated with the present invention.


Controlled area 810 is configured with a rain gauge 813 integrated with sensor 811 wherein rainfall and applied water to the adjacent area is transmitted via functional codes by transmitter 812 along with a related transceiver identification code in a manner previously described to stand-alone transceiver 221. Stand-alone transceiver 221 further processes and transmits the encoded data to local gateway 210 which translates the data packet information into TCP/IP format for transfer across WAN 230 to server 260. Server 260 collects and formats the rain gauge data for viewing or retrieval upon client demand in a manner previously described. Additionally, server 260 may be configured to communicate data to operate spray head 817 by opening water supply valve 816 integrated with actuator 814 by sending a control signal to transceiver 815, per a client directed water application control schedule. Alternatively, a customer workstation 250 could periodically download and review the rain gauge data and could initiate an automatic control signal appropriate with the customer's watering requirements. In yet another embodiment, a customer technician could initiate a control signal upon review of the rain gauge information and making the determination that more water is required.


Reference is now made to FIG. 9 which illustrates the operation of an automated parking control system 900 consistent with the present invention. Automated parking facility 910 consists of a controlled access area with ingress gate 920 and egress gate 930. Both gates 920 and 930 are further configured with a position sensor, an actuator, and transceiver illustrated as ingress assembly 922 and egress assembly 932, respectively. Parking spaces 940 may be configured with vehicle sensors. Sensor-transceiver assembly 932 may be configured to transmit a function code associated with the condition of parking spaces 1, 2, 3, and 4. It will be appreciated by those skilled in the art that the single row of four appropriately configured parking spaces illustrated can be expanded by adding parking spaces configured with vehicle sensors integrated with control system 900 via multiple sensor-transceiver assemblies. Automated parking control system 900 collects data signals from each sensor-transceiver assembly 932, integrated in the system, and compiles a master schedule consisting of scheduled use for each parking space in the automated parking facility. In this manner, a customer with access to WAN 230 and server 530 may make a reservation and or check the availability of parking spaces at the automated parking facility from her home or office (or through any Internet portal). For example, a customer that will be out of town on business for 2 days next week, may access the automated parking control system server 530 by using a Web browser to view parking availability for the target travel dates. The customer may reserve the parking slot by providing a personal transmitter identification code (or other identification code) that the customer intends to use to access and exit the facility the following week. When the customer arrives at the ingress gate 920, the customer may enter the automated parking facility 910 by depressing a button on her personal portable transmitter (see FIG. 3A). Ingress assembly 922 receives and forwards the customer's transmitted identification code to server 530 via gateway 210 and WAN 230 in a manner previously described. Server 530 confirms the customer's reservation, alternatively checks space availability to determine if access should be granted. In addition, server 530 may be further programmed to determine if the particular customer has an established account with the facility owner or whether a credit card payment transaction is in order. Automatic parking facility control system 900 would record the actual use of the reserved parking space for storage on database server 540. Server 530 could retrieve the stored usage information on a periodic basis from database server 540 and generate appropriate bills for each customer.


Alternatively, the customer could reserve the slot by providing billing information via WAN 230 and ingress gate 920 could be further configured with a credit card reader and an alphanumeric keypad interface. Both the credit card reader and the alphanumeric keypad interface could be interconnected to the automated parking facility control system 900 by their own appropriately configured transceiver. Either or both the credit card reader and the alphanumeric keypad interface could be used to identify customers with reservations.


The operator of parking facility control system 900, can expand both the level of security of the parking facility and the services provided by adding networked peripherals in a manner previously described and upgrading the software applications on server 530. For example, by adding automated ingress and egress gates configured to allow the entry and exit of parking facility customers and authorized personnel and configuring the egress gate 930 for vehicles such that only identified customers may exit with a vehicle, both customers and their vehicles are protected from thieves.


A further example of expanding the services offered by automated parking facility control system 900 might consist of offering a schedule of vehicle services that could be scheduled and performed on the vehicles of long-term parking customers. By adding the appropriate interface to server 530, parking facility customers could be prompted when making their reservation with a list of potential vehicle services that could be scheduled and performed by vehicle service technicians during the duration of the customer's business trip. A customer interested in having her automobile's oil changed and tires rotated would authorize and schedule the desired services when arranging her parking reservation. Upon leaving the parking facility at the start of her business trip, the customer could leave her vehicle valet key in an appropriately identified lock box. After her trip is complete, the customer returns to the lot. She gains access to the lot by any of the aforementioned methods and retrieves her valet key by similarly identifying herself as the vehicle owner.


Having illustrated specific applications using the present invention in FIGS. 6 through 9, reference is now made to FIG. 10 which illustrates a system 1000 that monitors and controls remote data points associated with a plurality of systems. In this embodiment, server 530 may be configured with monitor/control remote services 1010 application-specific software. For example, the controlled area 810 of the irrigation control system shown in FIG. 8, the remote utility meter subsystem 610 of FIG. 6, and the automated parking facility 910 of FIG. 9 may be monitored and remotely controlled (where required) by server 530. In a manner previously described herein, server 530 collects and processes data information transferred and sent over WAN 230 by local gateways coupled via RF links to transceivers and transmitters associated with systems 1020, 1030, and 1040. Alternatively, server 530 initiates control signals that may be sent via the gateways to the appropriate transceivers and transmitters as required. For ease of illustration and description, FIG. 10 shows each of the systems serviced by server 530 requiring its own dedicated local gateway. It will be appreciated by those skilled in the art that small-scale systems jointly located within a geographic area served by an array of transceivers and a gateway may be configured to share the transceiver and gateway infrastructure of a previously installed local system.


Having described the physical layer of a system consistent with the present invention, reference is now made to FIG. 11 which describes the data structure of messages sent and received using the invention. In this regard, the standard message consists of: to address; from address; packet number; maximum packet number, packet length; command; data; packet check sum (high byte); and packet check sum (low byte). The “to address” or message destination consists from 1 to 6 bytes. The “from address” or message source device is coded in a full 6 byte designator. Bytes 11 through 13 are used by the system to concatenate messages of packet lengths greater than 256 bytes. Byte 14 is a command byte. Byte 14 works in conjunction with bytes 15 through 30 to communicate information as required by system specific commands. Bytes 31 and 32 are packet check sum bytes. The packet check sum bytes are used by the system to indicate when system messages are received with errors. It is significant to note that bytes 31 and 32 may be shifted in the message to replace bytes 15 and 16 for commands that require only one byte. The order of appearance of specific information within the message protocol of FIG. 11 remains fixed although the byte position number in individual message transmissions may vary due to scalability of the “to address,” the command byte, and scalability of the data frame.


Having described the general message structure of a message of the present invention, reference is directed to FIG. 12 which illustrates three sample messages. The first message illustrates the broadcast of an emergency message “FF” from a central server with an address “0012345678” to a personal transceiver with an address of “FF.”


The second message illustrated reveals how the first message might be sent to a transceiver that functions as a repeater. In this manner, emergency message “FF” from a central server with address “0012345678” is first sent to transceiver “F0.” The second message, further contains additional command data “A000123456” that may be used by the system to identify further transceivers to send the signal through on the way to the destination device.


The third message illustrated on FIG. 12 reveals how the message protocol of the present invention may be used to “ping” a remote transceiver in order to determine transceiver health. In this manner, source unit “E112345678” originates a ping request by sending command “08” to a transceiver identified as “A012345678.” The response to the ping request can be as simple as reversing the “to address” and the “from address” of the command, such that, a healthy transceiver will send a ping message back to the originating device. The system of the present invention may be configured to expect a return ping within a specific time period. Operators of the present invention could use the delay between the ping request and the ping response to model system loads and to determine if specific system parameters might be adequately monitored and controlled with the expected feedback transmission delay of the system.


Having described the message structure of a message of the present invention, reference is directed to FIG. 13 which illustrates the integration of the system of the present invention with the control system of FIG. 1. Having previously illustrated several variations consistent with the principles of the present invention, it will be appreciated by those skilled in the art that multiple variations of the present invention may be integrated with existing control systems. In this regard, an existing control system with local controller 110 and a plurality of sensor actuators 115 (one shown for simplicity of illustration) are in communication with central controller 130 via PSTN 120 as previously described. In a manner well known in the art of control systems, local controller 110 transmits appropriate status information via PSTN 120 to central controller 130.


Control systems consistent with the design of FIG. 1, as further illustrated in FIG. 13, require the routing of electrical conductors to each sensor and actuator as the application requires. It will be appreciated by those skilled in the art that the system of the present invention can take advantage of the infrastructure of an existing system by inserting data translator 140 such that system data is sent to both the central controller 130 in the old configuration, as well as, the data translator 140. Data translator 140 serves to convert system data to function codes as previously described. Once data translator 140 successfully converts the system data stream to the message protocol of the present invention, transceiver 815 further converts the system data stream to a RF signal.


As previously described in connection with FIG. 2, stand-alone transceiver 221 receives and repeats the RF data transmission received from transceiver 815. Local gateway 210 receives the RF data transmission repeated by stand-alone transceiver 221 and converts the RF data transmission into TCP/IP for further transmission across WAN 230 to server 260. In this regard, server 260 may further manage the data for internal storage or alternatively storage in database 270. Customers with WAN 230 access may access the system data from workstation 250 or laptop computer 240.


Having described integration of the system of the present invention with the control system of FIG. 1 in FIG. 13, reference is now directed to FIG. 14 which illustrates integration of the system of the present invention with mobile inventory units. In this regard, system 1060 consists of the system of the present invention as previously illustrated and described in FIGS. 1 and 13. Having previously illustrated several variations consistent with the principles of the present invention, it will be appreciated by those skilled in the art that multiple variations of the present invention may be integrated with mobile inventory units 1070. In this regard, sensor/actuator 115 integrated with transceiver 815 in sensor-transceiver assembly 1065 is further integrated with any of a number of mobile inventory units 1070 (one sensor-transceiver unit 1065 shown for simplicity of illustration). It will be appreciated by those skilled in the art that as long as a mobile inventory unit 1070, herein represented by a package, ship, airplane, train, and a taxi are within the radio-frequency transmission and receiving range of stand-alone transceiver 221, the system of the present invention may be used to monitor, store and report information of and relating to mobile inventory unit 1070.


It will be further appreciated by those skilled in the art that the system of the present invention may be used to transfer information to adequately equipped mobile inventory units 1070. In this regard, shipping companies may use the present invention to update a database containing location and status information for each mobile inventory unit 1070 in the company fleet. Shipping companies may also transfer informative messages or other information using the system of the present invention.


In one embodiment, the present invention may be used to store, retrieve, and update maintenance information related to individual mobile inventory units. For example, federally registered airplanes must keep a maintenance log with the craft detailing all inspections, maintenance, and repairs. The system of the present invention could be used by fixed base operators (FBOs) who perform inspections and maintenance on aircraft to retrieve and update the aircraft maintenance log. In this way, FBOs located throughout the world will be able to retrieve and update an electronic version of the maintenance history of an aircraft. In addition, a properly configured system could also contain maintenance directives and other service bulletins related to the particular aircraft.


In yet another embodiment, a properly integrated sensor/actuator 115 with transceiver 815 may be used to monitor mobile inventory unit system parameters. For example, an airplane could be configured to monitor and report engine run time, time elapsed since the last recorded inspection of a particular type, and related system information. It will be appreciated by those skilled in the art that the system of the present invention may be integrated with remote units other than those shown. The ship, package, airplane, train, and taxi shown in FIG. 14 are for example only and not meant to limit the scope of the present invention.


It will be appreciated that the foregoing description has illustrated certain fundamental concepts of the invention, but that other additions and/or modifications may be made consistent with the inventive concepts. For example, the one-way transmitters illustrated in FIG. 3A and implemented in a control system as illustrated in FIG. 6 may be adapted to monitor the current status of water, gas, and other utility meters. One-way transmitters might further be used to monitor and report actual operational hours on rental equipment or any other apparatus that must be serviced or monitored on an actual run-time schedule.


The two-way transceivers of the current invention, may be adapted to monitor and apply control signals in an unlimited number of applications. By way of example only, two-way transceivers of the current invention can be adapted for use with pay type publicly located telephones, cable television set converter boxes, as well as, for use with a host of residential appliances and devices to enable a remote controllable home automation and security system.


In a geographic area appropriately networked with permanently located transceivers consistent with the invention, personal transmitters consistent with the invention can be used to monitor and control personnel access and egress from specific rooms or portions thereof within a controlled facility. Personal transmitters can further be configured to transfer personal information to public emergency response personnel, personal billing information to vending machines, or to monitor individuals within an assisted living community.


Two-way transceivers consistent with the present invention can be integrated to monitor and control a host of industrial and business applications as well. By way of example only, building automation systems, fire control systems, alarm systems, industrial trash compactors, and building elevators can be monitored and controlled with devices consistent with the present invention. In addition, courier drop boxes, time clock systems, automated teller machines, self-service copy machines, and other self-service devices can be monitored and controlled as appropriate. By way of further example, a number of environment variables that require monitoring can be integrated with the system of the present invention to permit remote monitoring and control. For instance, light levels in the area adjacent to automated teller machines must meet minimum federal standards, the water volume transferred by water treatment plant pumps, smokestack emissions from a coal burning power plant or a coke fueled steel plant oven may also be remotely monitored.


The two-way transceivers of the present invention may be further integrated with a voice-band transmitter and receiver. As a result, when a person presses, for example, the emergency button on his/her transmitter, medical personnel, staff members, or others may respond by communicating via two-way radio with the party in distress. In this regard, each transmitter may be equipped with a microphone and a speaker that would allow the person to communication information such as their present emergency situation, their specific location, etc.


The foregoing description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obvious modifications or variations are possible in light of the above teachings. For example, it should be appreciated that, in some implementations, the transceiver identification number is not necessary to identify the location of the transmitter. Indeed, in implementations where the transmitter is permanently integrated into an alarm sensor other stationary device within a system, then the control system server and or local gateway could be configured to identify the transmitter location by the transmitter identification number alone. In will be appreciated that, in embodiments that do not utilize repeating transceivers, the transmitters will be configured to transmit at a higher RF power level, in order to effectively communicate with the control system local gateway.


The embodiment or embodiments discussed were chosen and described 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
  • 1. A vehicle parking monitoring system, comprising: a parking space sensor enabled to detect the presence of at least one vehicle in a first parking space of a first parking area; anda parking area transceiver in communication with the parking space sensor, the parking area transceiver configured to receive information from the parking space sensor and transmit the information to a gateway, the parking area transceiver also configured to receive information from the gateway,wherein the gateway is connected to a wide area network and configured to receive information from the parking area transceiver and transmit the information to the wide area network, the gateway also configured to receive information from the wide area network and transmit the information to the parking area transceiver.
  • 2. The vehicle parking monitoring system in claim 1, further comprising a server enabled to receive the information from the gateway via the wide area network and send information to the gateway via the wide area network.
  • 3. The vehicle parking monitoring system in claim 2, wherein the server is configured to monitor and control the parking of a plurality of vehicles in the first parking area.
  • 4. The vehicle parking monitoring system in claim 3, wherein the server is configured to remotely authorize a payment for the parking of the at least one vehicle in the first parking area.
  • 5. The vehicle parking monitoring system in claim 3, wherein the parking space sensor can monitor a total time period that the at least one vehicle occupies the first parking space and the parking space sensor can communicate that total time period to the server via the parking area transceiver.
  • 6. The vehicle parking monitoring system in claim 3, wherein the server is configured to send an invoice for parking services to a customer with the at least one vehicle in the in the first parking area.
  • 7. The vehicle parking monitoring system in claim 6, wherein the customer is enabled to access the server via the internet to make parking reservations, pre-pay for parking services, or pay for previous parking services.
  • 8. The vehicle parking monitoring system in claim 1, further comprising an ingress sensor in communication with the parking area transceiver, the ingress sensor is enabled to provide a data message to the parking area transceiver when the vehicle enters the first parking area.
  • 9. The vehicle parking monitoring system in claim 8, wherein the ingress sensor is further configured with a credit card reader configured to read a credit card of a customer to enable the vehicle of the customer to access to the first parking area.
  • 10. The vehicle parking monitoring system in claim 8, wherein the ingress sensor is further configured with an alphanumeric keypad interface, and wherein a customer can enter a confirmation number into the alphanumeric keypad interface to enable the vehicle of the customer to access the first parking area.
  • 11. The vehicle parking monitoring system in claim 1, further comprising an egress sensor in communication with the parking area transceiver, the egress sensor is enabled to provide a data message to the parking area transceiver when the vehicle exits the first parking area.
  • 12. The vehicle parking monitoring system in claim 1, further comprising a personal portable transmitter enabled to communicate with the parking area transceiver, wherein the a customer can press a button on the personal portable transmitter to identify the arrival of the vehicle at the first parking area.
  • 13. The vehicle parking monitoring system in claim 12, wherein the parking area transceiver can receive a communication from the personal portable transmitter, and thereby send a data message to identify the arrival of the vehicle at the first parking area.
  • 14. The vehicle parking monitoring system in claim 12, wherein the parking area transceiver can receive a communication from the personal portable transmitter, and thereby send a data message to identify the exit of the vehicle from the first parking area.
  • 15. A vehicle parking monitoring system, comprising: a parking space sensor enabled to detect the presence of at least one vehicle in a first parking space of a first parking area;a parking area transceiver in communication with the parking space sensor, the parking area transceiver configured to receive information from the parking space sensor and transmit the information to a gateway, the parking area transceiver also configured to receive information from the gateway;an ingress sensor in communication with a second parking area transceiver, the ingress sensor is enabled to provide a first data message to the second parking area transceiver when the vehicle enters the first parking area;an egress sensor in communication with a third parking area transceiver, the egress sensor is enabled to provide a second data message to the parking area transceiver when the vehicle exits the first parking area; andwherein the gateway is connected to a wide area network and configured to receive information from the first, second, and third parking area transceivers and transmit the information to the wide area network, the gateway also configured to receive information from the wide area network and transmit the information to the first, second, and third parking area transceivers.
  • 16. The vehicle parking monitoring system in claim 15, further comprising a server enabled to receive the information from the gateway via the wide area network and send information to the gateway via the wide area network.
  • 17. The vehicle parking monitoring system in claim 16, wherein the server is configured to monitor and control the parking of a plurality of vehicles in the first parking area.
  • 18. The vehicle parking monitoring system in claim 15, wherein the ingress sensor is further configured with a credit card reader configured to read a credit card of a customer to enable the vehicle of the customer to access to the first parking area.
  • 19. The vehicle parking monitoring system in claim 15, wherein the ingress sensor is further configured with an alphanumeric keypad interface, and wherein a customer can enter a confirmation number into the alphanumeric keypad interface to enable the vehicle of the customer to access the first parking area.
  • 20. The vehicle parking monitoring system in claim 15, further comprising a personal portable transmitter enabled to communicate with the second parking area transceiver, wherein the a customer can press a button on the personal portable transmitter to identify the arrival of the vehicle at the first parking area.
CROSS REFERENCE TO RELATED APPLICATIONS & PRIORITY CLAIMS

This application is a continuation of copending U.S. patent application Ser. No. 12/477,329, entitled, “Systems and Methods for Monitoring and Controlling Remote Devices,” filed on Jun. 3, 2009; which is a continuation of U.S. patent application Ser. No. 12/337,739, entitled System and Method for Monitoring and Controlling Remote Devices and filed on 18 Dec. 2008; which is a continuation of U.S. patent application Ser. No. 11/395,685, entitled, “System and Method for Monitoring and Controlling Remote Devices,” filed on Mar. 31, 2006, issued as U.S. Pat. No. 7,468,661; which is a continuation of U.S. patent application Ser. No. 10/139,492, entitled, “System and Method for Monitoring and Controlling Remote Devices,” filed on May 6, 2002 and now U.S. Pat. No. 7,053,767; which is a continuation of U.S. patent application Ser. No. 09/439,059, filed on Nov. 12, 1999 and entitled “System and Method for Monitoring and Controlling Remote Devices,” now U.S. Pat. No. 6,437,692. U.S. Pat. No. 6,437,692 is a continuation-in-part of U.S. patent application Ser. No. 09/271,517, filed Mar. 18, 1999 and entitled, “System for Monitoring Conditions in a Residential Living Community”, which is a continuation-in-part of U.S. patent application Ser. No. 09/102,178 filed Jun. 22, 1998 and entitled, “Multi-Function General Purpose Transceiver,” now U.S. Pat. No. 6,430,268, which is a continuation-in-part of U.S. patent application Ser. No. 09/412,895, filed Oct. 5, 1999 and entitled, “System and Method for Monitoring the Light Level Around an ATM,” now U.S. Pat. No. 6,218,953; which is a continuation-in-part of U.S. patent application Ser. No. 09/172,554, filed Oct. 14, 1998 and entitled, “System for Monitoring the Light Level Around an ATM,” now U.S. Pat. No. 6,028,522; and further claims the benefit of U.S. Provisional Application Ser. No. 60/146,817, filed Aug. 2, 1999 and entitled, “System and Method for Monitoring and Controlling Residential Devices.” Each of the above identified applications and patents are incorporated herein by reference in their entireties.

US Referenced Citations (771)
Number Name Date Kind
3665475 Gram May 1972 A
3705385 Batz Dec 1972 A
3723876 Seaborn, Jr. Mar 1973 A
3742142 Martin Jun 1973 A
3768014 Smith Oct 1973 A
3769965 Raddi et al. Nov 1973 A
3848231 Wootton Nov 1974 A
3885552 Kennedy May 1975 A
3892948 Constable Jul 1975 A
3906460 Halpern Sep 1975 A
3914692 Seaborn, Jr. Oct 1975 A
3922492 Lumsden Nov 1975 A
3925763 Wadhwani et al. Dec 1975 A
4025315 Mazelli May 1977 A
4056684 Lindstrom Nov 1977 A
4058672 Crager et al. Nov 1977 A
4083003 Haemmig Apr 1978 A
4120452 Kimura et al. Oct 1978 A
4124839 Cohen Nov 1978 A
4135181 Bogacki et al. Jan 1979 A
4204195 Bogacki May 1980 A
4213119 Ward et al. Jul 1980 A
4277837 Stuckert Jul 1981 A
4278975 Kimura et al. Jul 1981 A
4284852 Szybicki et al. Aug 1981 A
4322842 Martinez Mar 1982 A
4345116 Ash et al. Aug 1982 A
4354181 Spletzer Oct 1982 A
4395780 Gohm et al. Jul 1983 A
4396910 Enemark et al. Aug 1983 A
4396915 Farnsworth et al. Aug 1983 A
4399531 Grande et al. Aug 1983 A
4406016 Abrams et al. Sep 1983 A
4417450 Morgan, Jr. et al. Nov 1983 A
4436957 Mazza et al. Mar 1984 A
4446454 Pyle May 1984 A
4446458 Cook May 1984 A
4454414 Benton Jun 1984 A
4468656 Clifford et al. Aug 1984 A
4488152 Arnason et al. Dec 1984 A
4495496 Miller, III Jan 1985 A
4551719 Carlin et al. Nov 1985 A
4611198 Levinson et al. Sep 1986 A
4621263 Takenaka et al. Nov 1986 A
4630035 Stahl et al. Dec 1986 A
4631357 Grunig Dec 1986 A
4665519 Kirchner et al. May 1987 A
4669113 Ash et al. May 1987 A
4670739 Kelly, Jr. Jun 1987 A
4692761 Robinton Sep 1987 A
4704724 Krishnan et al. Nov 1987 A
4707852 Jahr et al. Nov 1987 A
4731810 Watkins Mar 1988 A
4742296 Petr et al. May 1988 A
4757185 Onishi Jul 1988 A
4788721 Krishnan et al. Nov 1988 A
4792946 Mayo Dec 1988 A
4799059 Grindahl et al. Jan 1989 A
4800543 Lyndon-James et al. Jan 1989 A
4814763 Nelson et al. Mar 1989 A
4825457 Lebowitz Apr 1989 A
4829561 Matheny May 1989 A
4849815 Streck Jul 1989 A
4851654 Nitta Jul 1989 A
4856046 Streck et al. Aug 1989 A
4857912 Everett, Jr. et al. Aug 1989 A
4864559 Perlman Sep 1989 A
4875231 Hara et al. Oct 1989 A
4884123 Dixit et al. Nov 1989 A
4884132 Morris et al. Nov 1989 A
4897644 Hirano Jan 1990 A
4906828 Halpern Mar 1990 A
4908769 Vaughan et al. Mar 1990 A
4912656 Cain et al. Mar 1990 A
4918432 Pauley et al. Apr 1990 A
4918690 Markkula, Jr. et al. Apr 1990 A
4918995 Pearman et al. Apr 1990 A
4924462 Sojka May 1990 A
4928299 Tansky et al. May 1990 A
4939726 Flammer et al. Jul 1990 A
4940976 Gastouniotis et al. Jul 1990 A
4949077 Mbuthia Aug 1990 A
4952928 Carroll et al. Aug 1990 A
4962496 Vercellotti et al. Oct 1990 A
4967366 Kaehler Oct 1990 A
4968970 LaPorte Nov 1990 A
4968978 Stolarczyk Nov 1990 A
4972504 Daniel, Jr. et al. Nov 1990 A
4973957 Shimizu et al. Nov 1990 A
4973970 Reeser Nov 1990 A
4977612 Wilson Dec 1990 A
4980907 Raith et al. Dec 1990 A
4987536 Humblet Jan 1991 A
4989230 Gillig et al. Jan 1991 A
4991008 Nama Feb 1991 A
4993059 Smith et al. Feb 1991 A
4998095 Shields Mar 1991 A
4999607 Evans Mar 1991 A
5007052 Flammer Apr 1991 A
5032833 Laporte Jul 1991 A
5038372 Elms et al. Aug 1991 A
5055851 Sheffer Oct 1991 A
5057814 Onan et al. Oct 1991 A
5061997 Rea et al. Oct 1991 A
5079768 Flammer Jan 1992 A
5086391 Chambers Feb 1992 A
5088032 Bosack Feb 1992 A
5091713 Horne et al. Feb 1992 A
5111199 Tomoda et al. May 1992 A
5113183 Mizuno et al. May 1992 A
5113184 Katayama May 1992 A
5115224 Kostusiak et al. May 1992 A
5115433 Baran et al. May 1992 A
5117422 Hauptschein et al. May 1992 A
5124624 de Vries et al. Jun 1992 A
5128855 Hilber et al. Jul 1992 A
5130519 Bush et al. Jul 1992 A
5130987 Flammer Jul 1992 A
5131038 Puhl et al. Jul 1992 A
5134650 Blackmon Jul 1992 A
5136285 Okuyama Aug 1992 A
5138615 Lamport et al. Aug 1992 A
5155481 Brennan, Jr. et al. Oct 1992 A
5159317 Brav Oct 1992 A
5159592 Perkins Oct 1992 A
5162776 Bushnell et al. Nov 1992 A
5170393 Peterson et al. Dec 1992 A
5177342 Adams Jan 1993 A
5189287 Parienti Feb 1993 A
5191192 Takahira et al. Mar 1993 A
5191326 Montgomery Mar 1993 A
5193111 Matty et al. Mar 1993 A
5195018 Kwon et al. Mar 1993 A
5197095 Bonnet et al. Mar 1993 A
5200735 Hines Apr 1993 A
5204670 Stinton Apr 1993 A
5212645 Wildes et al. May 1993 A
5216502 Katz Jun 1993 A
5221838 Gutman et al. Jun 1993 A
5223844 Mansell et al. Jun 1993 A
5224468 Grunewald et al. Jul 1993 A
5231658 Eftechiou Jul 1993 A
5235630 Moody et al. Aug 1993 A
5239294 Flanders et al. Aug 1993 A
5239575 White et al. Aug 1993 A
5241410 Streck et al. Aug 1993 A
5243338 Brennan, Jr. et al. Sep 1993 A
5245633 Schwartz et al. Sep 1993 A
5251205 Callon et al. Oct 1993 A
5252967 Brennan et al. Oct 1993 A
5253167 Yoshida et al. Oct 1993 A
5265150 Helmkamp et al. Nov 1993 A
5265162 Bush et al. Nov 1993 A
5266782 Alanara et al. Nov 1993 A
5272747 Meads Dec 1993 A
5276680 Messenger Jan 1994 A
5282204 Shpancer et al. Jan 1994 A
5282250 Dent et al. Jan 1994 A
5289165 Belin Feb 1994 A
5289362 Liebl et al. Feb 1994 A
5291516 Dixon et al. Mar 1994 A
5295154 Meier et al. Mar 1994 A
5305370 Kearns et al. Apr 1994 A
5309501 Kozik et al. May 1994 A
5315645 Matheny May 1994 A
5317309 Vercellotti et al. May 1994 A
5319364 Waraksa et al. Jun 1994 A
5319698 Glidewell et al. Jun 1994 A
5319711 Servi Jun 1994 A
5321618 Gessman Jun 1994 A
5323384 Norwood et al. Jun 1994 A
5325429 Kurgan Jun 1994 A
5329394 Calvani et al. Jul 1994 A
5331318 Montgomery Jul 1994 A
5334974 Simms et al. Aug 1994 A
5335265 Cooper et al. Aug 1994 A
5343493 Karimullah Aug 1994 A
5344068 Haessig Sep 1994 A
5345231 Koo et al. Sep 1994 A
5345595 Johnson et al. Sep 1994 A
5347263 Carroll et al. Sep 1994 A
5352278 Korver et al. Oct 1994 A
5354974 Eisenberg Oct 1994 A
5355278 Hosoi et al. Oct 1994 A
5355513 Clarke et al. Oct 1994 A
5365217 Toner Nov 1994 A
5371736 Evan Dec 1994 A
5382778 Takahira et al. Jan 1995 A
5383134 Wrzesinski Jan 1995 A
5383187 Vardakas et al. Jan 1995 A
5390206 Rein et al. Feb 1995 A
5406619 Akhteruzzaman et al. Apr 1995 A
5412192 Hoss May 1995 A
5412654 Perkins May 1995 A
5412760 Peitz May 1995 A
5414624 Anthonyson May 1995 A
5416475 Tolbert et al. May 1995 A
5416725 Pacheco et al. May 1995 A
5418812 Reyes et al. May 1995 A
5420910 Rudokas et al. May 1995 A
5424708 Ballesty et al. Jun 1995 A
5430729 Rahnema Jul 1995 A
5432507 Mussino et al. Jul 1995 A
5432508 Jackson Jul 1995 A
5438329 Gastouniotis et al. Aug 1995 A
5439414 Jacob Aug 1995 A
5440545 Buchholz et al. Aug 1995 A
5442553 Parrillo Aug 1995 A
5442633 Perkins et al. Aug 1995 A
5445287 Center et al. Aug 1995 A
5445347 Ng Aug 1995 A
5448230 Schanker et al. Sep 1995 A
5451929 Adelman et al. Sep 1995 A
5451938 Brennan, Jr. Sep 1995 A
5452344 Larson Sep 1995 A
5454024 Lebowitz Sep 1995 A
5455569 Sherman et al. Oct 1995 A
5465401 Thompson Nov 1995 A
5467074 Pedtke Nov 1995 A
5467082 Sanderson Nov 1995 A
5467345 Cutler, Jr. et al. Nov 1995 A
5468948 Koenck et al. Nov 1995 A
5471201 Cerami et al. Nov 1995 A
5473322 Carney Dec 1995 A
5475689 Kay et al. Dec 1995 A
5479400 Dilworth et al. Dec 1995 A
5481259 Bane Jan 1996 A
5481532 Hassan et al. Jan 1996 A
5484997 Haynes Jan 1996 A
5488608 Flammer, III Jan 1996 A
5493273 Smurlo et al. Feb 1996 A
5493287 Bane Feb 1996 A
5502726 Fischer Mar 1996 A
5504746 Meier Apr 1996 A
5506837 Sollner et al. Apr 1996 A
5508412 Kast et al. Apr 1996 A
5509073 Monnin Apr 1996 A
5513244 Joao et al. Apr 1996 A
5515419 Sheffer May 1996 A
5517188 Carroll et al. May 1996 A
5522089 Kikinis et al. May 1996 A
5528215 Siu et al. Jun 1996 A
5528507 McNamara et al. Jun 1996 A
5539825 Akiyama et al. Jul 1996 A
5541938 Di Zenzo et al. Jul 1996 A
5542100 Hatakeyama Jul 1996 A
5544036 Brown, Jr. et al. Aug 1996 A
5544322 Cheng et al. Aug 1996 A
5544784 Malaspina Aug 1996 A
5548632 Walsh et al. Aug 1996 A
5550358 Tait et al. Aug 1996 A
5550359 Bennett Aug 1996 A
5550535 Park Aug 1996 A
5553094 Johnson et al. Sep 1996 A
5555258 Snelling et al. Sep 1996 A
5555286 Tendler Sep 1996 A
5557320 Krebs Sep 1996 A
5557748 Norris Sep 1996 A
5562537 Zver et al. Oct 1996 A
5565857 Lee Oct 1996 A
5568535 Sheffer et al. Oct 1996 A
5570084 Ritter et al. Oct 1996 A
5572438 Ehlers et al. Nov 1996 A
5572528 Shuen Nov 1996 A
5573181 Ahmed Nov 1996 A
5574111 Brichta et al. Nov 1996 A
5583850 Snodgrass et al. Dec 1996 A
5583914 Chang et al. Dec 1996 A
5587705 Morris Dec 1996 A
5588005 Ali et al. Dec 1996 A
5589878 Cortjens et al. Dec 1996 A
5590038 Pitroda Dec 1996 A
5590179 Shincovich et al. Dec 1996 A
5592491 Dinkins Jan 1997 A
5594431 Sheppard et al. Jan 1997 A
5596719 Ramakrishnan et al. Jan 1997 A
5596722 Rahnema Jan 1997 A
5602843 Gray Feb 1997 A
5604414 Milligan et al. Feb 1997 A
5604869 Mincher et al. Feb 1997 A
5606361 Davidsohn et al. Feb 1997 A
5608721 Natarajan et al. Mar 1997 A
5608786 Gordon Mar 1997 A
5613620 Center et al. Mar 1997 A
5615227 Schumacher, Jr. et al. Mar 1997 A
5615277 Hoffman Mar 1997 A
5617084 Sears Apr 1997 A
5619192 Ayala Apr 1997 A
5623495 Eng et al. Apr 1997 A
5625410 Washino et al. Apr 1997 A
5628050 McGraw et al. May 1997 A
5629687 Sutton et al. May 1997 A
5629875 Adair, Jr. May 1997 A
5630209 Wizgall et al. May 1997 A
5631554 Briese et al. May 1997 A
5636216 Fox et al. Jun 1997 A
5640002 Ruppert et al. Jun 1997 A
5644294 Ness Jul 1997 A
5655219 Jusa et al. Aug 1997 A
5657389 Houvener Aug 1997 A
5659300 Dresselhuys et al. Aug 1997 A
5659303 Adair, Jr. Aug 1997 A
5668876 Falk et al. Sep 1997 A
5673252 Johnson et al. Sep 1997 A
5673259 Quick, Jr. Sep 1997 A
5673304 Connor et al. Sep 1997 A
5673305 Ross Sep 1997 A
5682139 Pradeep et al. Oct 1997 A
5682476 Tapperson et al. Oct 1997 A
5689229 Chaco et al. Nov 1997 A
5691980 Welles, II et al. Nov 1997 A
5696695 Ehlers et al. Dec 1997 A
5699328 Ishizaki et al. Dec 1997 A
5701002 Oishi et al. Dec 1997 A
5702059 Chu et al. Dec 1997 A
5704046 Hogan Dec 1997 A
5704517 Lancaster, Jr. Jan 1998 A
5706191 Bassett et al. Jan 1998 A
5706976 Purkey Jan 1998 A
5708223 Wyss Jan 1998 A
5708655 Toth et al. Jan 1998 A
5712619 Simkin Jan 1998 A
5712980 Beeler et al. Jan 1998 A
5714931 Petite et al. Feb 1998 A
5717718 Rowsell et al. Feb 1998 A
5719564 Sears Feb 1998 A
5722076 Sakabe et al. Feb 1998 A
5726534 Seo Mar 1998 A
5726544 Lee Mar 1998 A
5726634 Hess et al. Mar 1998 A
5726644 Jednacz et al. Mar 1998 A
5726984 Kubler et al. Mar 1998 A
5732074 Spaur et al. Mar 1998 A
5732078 Arango Mar 1998 A
5736965 Mosebrook et al. Apr 1998 A
5737318 Melnik Apr 1998 A
5740232 Pailles et al. Apr 1998 A
5740366 Mahany et al. Apr 1998 A
5742509 Goldberg et al. Apr 1998 A
5745849 Britton Apr 1998 A
5748104 Argyroudis et al. May 1998 A
5748619 Meier May 1998 A
5754111 Garcia May 1998 A
5754227 Fukuoka May 1998 A
5757783 Eng et al. May 1998 A
5757788 Tatsumi et al. May 1998 A
5760742 Branch et al. Jun 1998 A
5761083 Brown, Jr. et al. Jun 1998 A
5764742 Howard et al. Jun 1998 A
5767791 Stoop et al. Jun 1998 A
5771274 Harris Jun 1998 A
5774052 Hamm et al. Jun 1998 A
5781143 Rossin Jul 1998 A
5790644 Kikinis Aug 1998 A
5790662 Valerij et al. Aug 1998 A
5790938 Talarmo Aug 1998 A
5796727 Harrison et al. Aug 1998 A
5798964 Shimizu et al. Aug 1998 A
5801643 Williams et al. Sep 1998 A
5812531 Cheung et al. Sep 1998 A
5815505 Mills Sep 1998 A
5818822 Thomas et al. Oct 1998 A
5822273 Bary et al. Oct 1998 A
5822309 Ayanoglu et al. Oct 1998 A
5822544 Chaco et al. Oct 1998 A
5825772 Dobbins et al. Oct 1998 A
5826195 Westerlage et al. Oct 1998 A
5828044 Jun et al. Oct 1998 A
5832057 Furman Nov 1998 A
5838223 Gallant et al. Nov 1998 A
5838237 Revell et al. Nov 1998 A
5838812 Pare, Jr. et al. Nov 1998 A
5841118 East et al. Nov 1998 A
5841764 Roderique et al. Nov 1998 A
5842976 Williamson Dec 1998 A
5844808 Konsmo et al. Dec 1998 A
5845230 Lamberson Dec 1998 A
5848054 Mosebrook et al. Dec 1998 A
5852658 Knight et al. Dec 1998 A
5854994 Canada et al. Dec 1998 A
5856974 Gervais et al. Jan 1999 A
5862201 Sands Jan 1999 A
5864772 Alvarado et al. Jan 1999 A
5867688 Donahue Feb 1999 A
5870686 Monson Feb 1999 A
5872773 Katzela et al. Feb 1999 A
5873043 Comer Feb 1999 A
5874903 Shuey et al. Feb 1999 A
5875185 Wang et al. Feb 1999 A
5880677 Lestician Mar 1999 A
5883884 Atkinson Mar 1999 A
5883886 Eaton et al. Mar 1999 A
5884184 Sheffer Mar 1999 A
5884271 Pitroda Mar 1999 A
5886333 Miyake Mar 1999 A
5889468 Banga Mar 1999 A
5892690 Boatman et al. Apr 1999 A
5892758 Argyroudis Apr 1999 A
5892924 Lyon et al. Apr 1999 A
5896097 Cardozo Apr 1999 A
5897607 Jenney et al. Apr 1999 A
5898369 Godwin Apr 1999 A
5898733 Satyanarayana Apr 1999 A
5905438 Weiss et al. May 1999 A
5905442 Mosebrook et al. May 1999 A
5907291 Chen et al. May 1999 A
5907491 Canada et al. May 1999 A
5907540 Hayashi May 1999 A
5907807 Chavez, Jr. et al. May 1999 A
5909429 Satyanarayana et al. Jun 1999 A
5914656 Ojala et al. Jun 1999 A
5914672 Glorioso et al. Jun 1999 A
5914673 Jennings et al. Jun 1999 A
5917405 Joao Jun 1999 A
5917629 Hortensius et al. Jun 1999 A
5923269 Shuey et al. Jul 1999 A
5926101 Dasgupta Jul 1999 A
5926103 Petite Jul 1999 A
5926529 Hache et al. Jul 1999 A
5926531 Petite Jul 1999 A
5933073 Shuey Aug 1999 A
5940481 Zeitman Aug 1999 A
5940771 Gollnick et al. Aug 1999 A
5941363 Partyka et al. Aug 1999 A
5941955 Wilby et al. Aug 1999 A
5946631 Melnik Aug 1999 A
5948040 DeLorme et al. Sep 1999 A
5949779 Mostafa et al. Sep 1999 A
5949799 Grivna et al. Sep 1999 A
5953319 Dutta et al. Sep 1999 A
5953371 Rowsell et al. Sep 1999 A
5953507 Cheung et al. Sep 1999 A
5955718 Levasseur et al. Sep 1999 A
5957718 Cheng et al. Sep 1999 A
5960074 Clark Sep 1999 A
5963146 Johnson et al. Oct 1999 A
5963452 Etoh et al. Oct 1999 A
5963650 Simionescu et al. Oct 1999 A
5966658 Kennedy, III et al. Oct 1999 A
5969608 Sojdehei et al. Oct 1999 A
5973756 Erlin Oct 1999 A
5974236 Sherman Oct 1999 A
5978364 Melnik Nov 1999 A
5978371 Mason, Jr. et al. Nov 1999 A
5978578 Azarya et al. Nov 1999 A
5986574 Colton Nov 1999 A
5987011 Toh Nov 1999 A
5987331 Grube et al. Nov 1999 A
5987421 Chuang Nov 1999 A
5991625 Vanderpool Nov 1999 A
5991639 Rautiola et al. Nov 1999 A
5994892 Turino et al. Nov 1999 A
5995022 Plis et al. Nov 1999 A
5995592 Shirai et al. Nov 1999 A
5995593 Cho Nov 1999 A
5997170 Brodbeck Dec 1999 A
5999094 Nilssen Dec 1999 A
6005759 Hart et al. Dec 1999 A
6005884 Cook et al. Dec 1999 A
6005963 Bolle et al. Dec 1999 A
6018659 Ayyagari et al. Jan 2000 A
6021664 Granato et al. Feb 2000 A
6023223 Baxter, Jr. Feb 2000 A
6026095 Sherer et al. Feb 2000 A
6028522 Petite Feb 2000 A
6028857 Poor Feb 2000 A
6031455 Grube et al. Feb 2000 A
6032197 Birdwell et al. Feb 2000 A
6035213 Tokuda et al. Mar 2000 A
6035266 Williams et al. Mar 2000 A
6036086 Sizer, II et al. Mar 2000 A
6037880 Manion Mar 2000 A
6038491 McGarry et al. Mar 2000 A
6044062 Brownrigg et al. Mar 2000 A
6046978 Melnik Apr 2000 A
6054920 Smith et al. Apr 2000 A
6055561 Feldman et al. Apr 2000 A
6060994 Chen May 2000 A
6061604 Russ et al. May 2000 A
6064318 Kirchner, III et al. May 2000 A
6067017 Stewart et al. May 2000 A
6067030 Burnett et al. May 2000 A
6069886 Ayerst et al. May 2000 A
6073169 Shuey et al. Jun 2000 A
6073266 Ahmed et al. Jun 2000 A
6073840 Marion Jun 2000 A
6075451 Lebowitz et al. Jun 2000 A
6078251 Landt et al. Jun 2000 A
6084867 Meier Jul 2000 A
6087957 Gray Jul 2000 A
6088659 Kelley et al. Jul 2000 A
6094622 Hubbard et al. Jul 2000 A
6097703 Larsen et al. Aug 2000 A
6100816 Moore Aug 2000 A
6100817 Mason, Jr. et al. Aug 2000 A
6101427 Yang Aug 2000 A
6101445 Alvarado et al. Aug 2000 A
6108614 Lincoln et al. Aug 2000 A
6112983 D'Anniballe et al. Sep 2000 A
6115393 Engel et al. Sep 2000 A
6115580 Chuprun et al. Sep 2000 A
6119076 Williams et al. Sep 2000 A
6121593 Mansbery et al. Sep 2000 A
6121885 Masone et al. Sep 2000 A
6122759 Ayanoglu et al. Sep 2000 A
6124806 Cunningham et al. Sep 2000 A
6127917 Tuttle Oct 2000 A
6128551 Davis et al. Oct 2000 A
6130622 Hussey et al. Oct 2000 A
6133850 Moore Oct 2000 A
6137423 Glorioso et al. Oct 2000 A
6140975 Cohen Oct 2000 A
6141347 Shaughnessy et al. Oct 2000 A
6150936 Addy Nov 2000 A
6150955 Tracy et al. Nov 2000 A
6157464 Bloomfield et al. Dec 2000 A
6157824 Bailey Dec 2000 A
6163276 Irving et al. Dec 2000 A
6167239 Wright et al. Dec 2000 A
6172616 Johnson et al. Jan 2001 B1
6173159 Wright et al. Jan 2001 B1
6174205 Madsen et al. Jan 2001 B1
6175922 Wang Jan 2001 B1
6177883 Jennetti et al. Jan 2001 B1
6178173 Mundwiler et al. Jan 2001 B1
6181255 Crimmins et al. Jan 2001 B1
6181284 Madsen et al. Jan 2001 B1
6181981 Varga et al. Jan 2001 B1
6185307 Johnson, Jr. Feb 2001 B1
6188354 Soliman et al. Feb 2001 B1
6188675 Casper et al. Feb 2001 B1
6192282 Smith et al. Feb 2001 B1
6192390 Berger et al. Feb 2001 B1
6195018 Ragle et al. Feb 2001 B1
6198390 Schlager et al. Mar 2001 B1
6199068 Carpenter Mar 2001 B1
6201962 Sturniolo et al. Mar 2001 B1
6205143 Lemieux Mar 2001 B1
6208247 Agre et al. Mar 2001 B1
6208266 Lyons et al. Mar 2001 B1
6212175 Harsch Apr 2001 B1
6215404 Morales Apr 2001 B1
6215440 Geldart et al. Apr 2001 B1
6218953 Petite Apr 2001 B1
6218958 Eichstaedt et al. Apr 2001 B1
6218983 Kerry et al. Apr 2001 B1
6219409 Smith et al. Apr 2001 B1
6229439 Tice May 2001 B1
6233327 Petite May 2001 B1
6234111 Ulman et al. May 2001 B1
6236332 Conkright et al. May 2001 B1
6243010 Addy et al. Jun 2001 B1
6246676 Chen et al. Jun 2001 B1
6246677 Nap et al. Jun 2001 B1
6246886 Oliva Jun 2001 B1
6249516 Brownrigg et al. Jun 2001 B1
6259369 Monico Jul 2001 B1
6271752 Vaios Aug 2001 B1
6275166 del Castillo et al. Aug 2001 B1
6275707 Reed et al. Aug 2001 B1
6286050 Pullen et al. Sep 2001 B1
6286756 Stinson et al. Sep 2001 B1
6288634 Weiss et al. Sep 2001 B1
6288641 Casais Sep 2001 B1
6295291 Larkins Sep 2001 B1
6301514 Canada et al. Oct 2001 B1
6304556 Haas Oct 2001 B1
6305205 Derks et al. Oct 2001 B1
6305602 Grabowski et al. Oct 2001 B1
6307843 Okanoue Oct 2001 B1
6308111 Koga Oct 2001 B1
6311167 Davis et al. Oct 2001 B1
6314169 Schelberg, Jr. et al. Nov 2001 B1
6317029 Fleeter Nov 2001 B1
6327245 Satyanarayana et al. Dec 2001 B1
6329902 Lee et al. Dec 2001 B1
6334117 Covert et al. Dec 2001 B1
6351223 DeWeerd et al. Feb 2002 B1
6356205 Salvo et al. Mar 2002 B1
6357034 Muller et al. Mar 2002 B1
6362745 Davis Mar 2002 B1
6363057 Ardalan et al. Mar 2002 B1
6363422 Hunter et al. Mar 2002 B1
6366217 Cunningham et al. Apr 2002 B1
6366622 Brown et al. Apr 2002 B1
6369769 Nap et al. Apr 2002 B1
6370489 Williams et al. Apr 2002 B1
6373399 Johnson et al. Apr 2002 B1
6380851 Gilbert et al. Apr 2002 B1
6384722 Williams May 2002 B1
6389477 Simmon et al. May 2002 B1
6392692 Monroe May 2002 B1
6393341 Lawrence et al. May 2002 B1
6393381 Williams et al. May 2002 B1
6393382 Williams et al. May 2002 B1
6396839 Ardalan et al. May 2002 B1
6400819 Nakano et al. Jun 2002 B1
6401081 Montgomery et al. Jun 2002 B1
6405018 Reudink et al. Jun 2002 B1
6411889 Mizunuma et al. Jun 2002 B1
6415155 Koshima et al. Jul 2002 B1
6415245 Williams et al. Jul 2002 B2
6416471 Kumar et al. Jul 2002 B1
6421354 Godlewski Jul 2002 B1
6421731 Ciotti, Jr. et al. Jul 2002 B1
6422464 Terranova Jul 2002 B1
6424270 Ali Jul 2002 B1
6424931 Sigmar et al. Jul 2002 B1
6430268 Petite Aug 2002 B1
6431439 Suer et al. Aug 2002 B1
6437692 Petite et al. Aug 2002 B1
6438575 Khan et al. Aug 2002 B1
6441723 Mansfield, Jr. et al. Aug 2002 B1
6445291 Addy et al. Sep 2002 B2
6456960 Williams et al. Sep 2002 B1
6457038 Defosse Sep 2002 B1
6462644 Howell et al. Oct 2002 B1
6462672 Besson Oct 2002 B1
6477558 Irving et al. Nov 2002 B1
6483290 Hemminger et al. Nov 2002 B1
6484939 Blaeuer Nov 2002 B1
6489884 Lamberson et al. Dec 2002 B1
6491828 Sivavec et al. Dec 2002 B1
6492910 Ragle et al. Dec 2002 B1
6496696 Melnik Dec 2002 B1
6504357 Hemminger et al. Jan 2003 B1
6504834 Fifield Jan 2003 B1
6507794 Hubbard et al. Jan 2003 B1
6509722 Lopata Jan 2003 B2
6513060 Nixon et al. Jan 2003 B1
6515586 Wymore Feb 2003 B1
6519568 Harvey et al. Feb 2003 B1
6532077 Arakawa Mar 2003 B1
6538577 Ehrke et al. Mar 2003 B1
6542076 Joao Apr 2003 B1
6542077 Joao Apr 2003 B2
6543690 Leydier et al. Apr 2003 B2
6560223 Egan et al. May 2003 B1
6574234 Myer et al. Jun 2003 B1
6574603 Dickson et al. Jun 2003 B1
6584080 Ganz et al. Jun 2003 B1
6600726 Nevo et al. Jul 2003 B1
6608551 Anderson et al. Aug 2003 B1
6618578 Petite Sep 2003 B1
6618709 Sneeringer Sep 2003 B1
6628764 Petite Sep 2003 B1
6628965 LaRosa et al. Sep 2003 B1
6653945 Johnson et al. Nov 2003 B2
6654357 Wiedeman Nov 2003 B1
6665278 Grayson Dec 2003 B2
6671586 Davis et al. Dec 2003 B2
6671819 Passman et al. Dec 2003 B1
6674403 Gray et al. Jan 2004 B2
6678255 Kuriyan Jan 2004 B1
6678285 Garg Jan 2004 B1
6691173 Morris et al. Feb 2004 B2
6731201 Sharood et al. May 2004 B1
6735630 Gelvin et al. May 2004 B1
6747557 Petite et al. Jun 2004 B1
6751196 Hulyalkar et al. Jun 2004 B1
6771981 Zalewski et al. Aug 2004 B1
6775258 van Valkenburg et al. Aug 2004 B1
6804532 Moon et al. Oct 2004 B1
6816088 Knoska et al. Nov 2004 B1
6826607 Gelvin et al. Nov 2004 B1
6832251 Gelvin et al. Dec 2004 B1
6842430 Melnik Jan 2005 B1
6858876 Gordon et al. Feb 2005 B2
6859831 Gelvin et al. Feb 2005 B1
6888876 Mason, Jr. et al. May 2005 B1
6891838 Petite et al. May 2005 B1
6900737 Ardalan et al. May 2005 B1
6906636 Kraml Jun 2005 B1
6914533 Petite Jul 2005 B2
6914893 Petite Jul 2005 B2
6922558 Delp et al. Jul 2005 B2
6959550 Freeman et al. Nov 2005 B2
6970434 Mahany et al. Nov 2005 B1
7020701 Gelvin et al. Mar 2006 B1
7027416 Kriz Apr 2006 B1
7027773 McMillin Apr 2006 B1
7053767 Petite et al. May 2006 B2
7054271 Brownrigg et al. May 2006 B2
7064679 Ehrke et al. Jun 2006 B2
7103511 Petite Sep 2006 B2
7117239 Hansen Oct 2006 B1
7181501 Defosse Feb 2007 B2
7254372 Janusz et al. Aug 2007 B2
7304587 Boaz Dec 2007 B2
7349682 Bennett, III et al. Mar 2008 B1
7424527 Petite Sep 2008 B2
7468661 Petite et al. Dec 2008 B2
7480501 Petite Jan 2009 B2
7484008 Gelvin et al. Jan 2009 B1
7573813 Melnik Aug 2009 B2
7653394 McMillin Jan 2010 B2
7739378 Petite Jun 2010 B2
20010002210 Petite May 2001 A1
20010003479 Fujiwara Jun 2001 A1
20010021646 Antonucci et al. Sep 2001 A1
20010024163 Petite Sep 2001 A1
20010034223 Rieser et al. Oct 2001 A1
20010038343 Meyer et al. Nov 2001 A1
20020002444 Williams et al. Jan 2002 A1
20020012323 Petite et al. Jan 2002 A1
20020013679 Petite Jan 2002 A1
20020016829 Defosse Feb 2002 A1
20020019725 Petite Feb 2002 A1
20020027504 Davis et al. Mar 2002 A1
20020031101 Petite et al. Mar 2002 A1
20020032560 Simmon et al. Mar 2002 A1
20020032746 Lazaridis Mar 2002 A1
20020035637 Simmon et al. Mar 2002 A1
20020036619 Simmon et al. Mar 2002 A1
20020038377 Simmon et al. Mar 2002 A1
20020038378 Simmon et al. Mar 2002 A1
20020040406 Simmon et al. Apr 2002 A1
20020061031 Sugar et al. May 2002 A1
20020072348 Wheeler et al. Jun 2002 A1
20020089428 Walden et al. Jul 2002 A1
20020095399 Devine et al. Jul 2002 A1
20020097273 Simmon et al. Jul 2002 A1
20020098858 Struhsaker Jul 2002 A1
20020109607 Cumeralto et al. Aug 2002 A1
20020136233 Chen et al. Sep 2002 A1
20020158774 Johnson et al. Oct 2002 A1
20020163442 Fischer Nov 2002 A1
20020169643 Petite et al. Nov 2002 A1
20020184384 Simmon et al. Dec 2002 A1
20020193144 Belski et al. Dec 2002 A1
20030001754 Johnson et al. Jan 2003 A1
20030023146 Shusterman Jan 2003 A1
20030028632 Davis Feb 2003 A1
20030030926 Aguren et al. Feb 2003 A1
20030034900 Han Feb 2003 A1
20030035438 Larsson Feb 2003 A1
20030036822 Davis et al. Feb 2003 A1
20030046377 Daum et al. Mar 2003 A1
20030058818 Wilkes et al. Mar 2003 A1
20030069002 Hunter et al. Apr 2003 A1
20030073406 Benjamin et al. Apr 2003 A1
20030078029 Petite Apr 2003 A1
20030093484 Petite May 2003 A1
20030133473 Manis et al. Jul 2003 A1
20030169710 Fan et al. Sep 2003 A1
20030185204 Murdock Oct 2003 A1
20030210638 Yoo et al. Nov 2003 A1
20040047324 Diener Mar 2004 A1
20040053639 Petite et al. Mar 2004 A1
20040090950 Lauber et al. May 2004 A1
20040113810 Mason, Jr. et al. Jun 2004 A1
20040131125 Sanderford, Jr. et al. Jul 2004 A1
20040133917 Schilling Jul 2004 A1
20040183687 Petite et al. Sep 2004 A1
20040228330 Kubler et al. Nov 2004 A1
20050017068 Zalewski et al. Jan 2005 A1
20050190055 Petite Sep 2005 A1
20050195768 Petite et al. Sep 2005 A1
20050195775 Petite et al. Sep 2005 A1
20050201397 Petite Sep 2005 A1
20050243867 Petite Nov 2005 A1
20050270173 Boaz Dec 2005 A1
20060095876 Chandra May 2006 A1
20070112907 Defosse May 2007 A1
20080186898 Petite Aug 2008 A1
20090006617 Petite Jan 2009 A1
20090068947 Petite Mar 2009 A1
20090096605 Petite Apr 2009 A1
20090215424 Petite Aug 2009 A1
20090243840 Petite et al. Oct 2009 A1
20100250054 Petite Sep 2010 A1
Foreign Referenced Citations (72)
Number Date Country
945277 Apr 1974 CA
2324563 Sep 1999 CA
2205336 Aug 1973 DE
4401443 Aug 1994 DE
0483547 May 1992 EP
0578041 Jan 1994 EP
0663746 Jul 1995 EP
0718954 Jun 1996 EP
0740873 Nov 1996 EP
0749259 Dec 1996 EP
0749260 Dec 1996 EP
0766489 Apr 1997 EP
0768777 Apr 1997 EP
0812502 Dec 1997 EP
0825577 Feb 1998 EP
0550517 Dec 1998 EP
0999717 May 2000 EP
1096454 May 2001 EP
2126301 Oct 1972 FR
2624749 Jun 1989 FR
2817110 May 2002 FR
1384573 Feb 1975 GB
2229302 Sep 1990 GB
2247761 Mar 1992 GB
2262683 Jun 1993 GB
2297663 Aug 1996 GB
2310779 Sep 1997 GB
2326002 Dec 1998 GB
2336272 Oct 1999 GB
2352004 Jan 2001 GB
2352590 Jan 2001 GB
60261288 Dec 1985 JP
1255100 Oct 1989 JP
11353573 Dec 1999 JP
2000113590 Apr 2000 JP
2001063425 Mar 2001 JP
2001088401 Apr 2001 JP
2001309069 Nov 2001 JP
2001319284 Nov 2001 JP
2001357483 Dec 2001 JP
2002007672 Jan 2002 JP
2002007826 Jan 2002 JP
2002085354 Mar 2002 JP
2002171354 Jun 2002 JP
2001025431 Apr 2001 KR
377048 Jun 1975 SE
WO 9013197 Nov 1990 WO
WO 9512942 May 1995 WO
WO 9524177 Sep 1995 WO
WO 9534177 Dec 1995 WO
WO 9610307 Apr 1996 WO
WO 9700708 Jan 1997 WO
WO 9800056 Jan 1998 WO
WO 9810393 Mar 1998 WO
WO 9837528 Aug 1998 WO
WO 9845717 Oct 1998 WO
WO 9913426 Mar 1999 WO
WO 9945510 Sep 1999 WO
WO 9948065 Sep 1999 WO
WO 0023956 Apr 2000 WO
WO 0036812 Jun 2000 WO
WO 0055825 Sep 2000 WO
WO 0058745 Oct 2000 WO
WO 0115114 Mar 2001 WO
WO 0124109 Apr 2001 WO
WO 0135190 May 2001 WO
WO 0208725 Jan 2002 WO
WO 0208866 Jan 2002 WO
WO 02052521 Jul 2002 WO
WO 03007264 Jan 2003 WO
WO 03021877 Mar 2003 WO
WO 2004002014 Dec 2003 WO
Related Publications (1)
Number Date Country
20110309953 A1 Dec 2011 US
Provisional Applications (1)
Number Date Country
60146817 Aug 1999 US
Continuations (5)
Number Date Country
Parent 12477329 Jun 2009 US
Child 13221689 US
Parent 12337739 Dec 2008 US
Child 12477329 US
Parent 11395685 Mar 2006 US
Child 12337739 US
Parent 10139492 May 2002 US
Child 11395685 US
Parent 09439059 Nov 1999 US
Child 10139492 US
Continuation in Parts (4)
Number Date Country
Parent 09271517 Mar 1999 US
Child 09439059 US
Parent 09412895 Oct 1999 US
Child 09271517 US
Parent 09172554 Oct 1998 US
Child 09412895 US
Parent 09102178 Jun 1998 US
Child 09172554 US