N/A
The invention relates to refuse and waste removing and hauling. More particularly, the present invention relates to a method and apparatus for controlling, tracking, and monitoring movement of waste or refuse receptacles.
The collection and transportation of trash and recyclables from residential, commercial, industrial and large residential facilities is a major industry in the United States and throughout the civilized world. Typically, trash and recyclables are accumulated and temporarily stored in waste material receptacles such as trash cans and dumpsters. When filled, or at regularly scheduled intervals, trash and recyclables from the containers are transported for the eventual recycling. incineration and/or disposal into landfills.
Customers typically pay for trash and recyclables removal services based on the amount of trash and recyclables removed and the number of trash and recyclables pickups over a period of time. The compacting of trash and recyclables at a customer's location typically reduces the number of pickups. A successful trash and recyclables compactor is disclosed in U.S. Pat. No. 6,412,406, titled Trash Compactor and owned by Advanced Custom Engineered Systems & Equipment, Inc., Carol Stream, Ill.
These industrial, commercial and large residential bins and compactors are collected from different locations and hauled to a central location. Normally, those hauling the trash and recyclables are sent from a central location and dispatched to the different locations. In practice, paper logs or schedules document the hauler's runs (e.g., trash and recyclables to pick-up, trash and recyclables being picked-up, and trash and recyclables picked-up). The haulers are given their routes in person or over the phone. The haulers, in turn, keep in touch with the central location generally by cell phone or radio.
For large organizations this can be a very complicated task as there are many haulers and many customers needing their trash and recyclables collected, picked-up and hauled away. In addition, commercial, industrial and large residential (e.g., condos and apartment buildings) trash and recyclables compactors and balers must be monitored for maintenance and repair. This too requires time and energy for the haulers and/or representatives (of the service provider) to monitor and inspect.
It should also be recognized that these industrial, commercial and large residential bins, balers and compactors require both period maintenance and emergency demand repair services. Normally, those repairing the equipment are sent from a central location and dispatched to the different locations. In practice, paper logs or work orders document the repairperson's time (e.g., drive time, time spent performing the repairs, parts and materials used, etc.). The repair companies use a variety of management tools. For example, some are given their routes in person or over the phone. The service providers, in turn, keep in touch with the central location generally by cell phone or radio.
For large organizations this can be a very complicated to coordinate and to verify that the charges for these services are fair and accurate as there are many service providers and many customers needing their compactors, bins and balers repaired. In addition, commercial, industrial and large residential (e.g., condos and apartment buildings).
In addition, it must be recognized that trash and recyclables compactors, balers and bins must further be monitored for maintenance and repair.
Methods of improving the refuse collection are disclosed in commonly assigned and U.S. Patent Application Publication No. 2008-0197194 A1, published on Aug. 21, 2008; U.S. Patent Application Publication No. 2008-0198021 A1, published on Aug. 21, 2008; and U.S. Patent Application Publication No. 2008-0202357 A1, published on Aug. 28, 2008. These publications are hereby incorporated by reference as if fully set forth herein, and generally disclose systems for communicating with receptacles, etc.
One opportunity that exists with refuse removal is to improve communication between the vehicles making refuse pick-ups (emptying receptacles) and the central station or dispatcher. Currently, the dispatcher may be in contact with the vehicle via radio or telephone transmission. However, it is not cost-effective of feasible for the dispatcher to be in constant contact with every vehicle out in the field. Thus, it is impossible for the dispatcher to relay account information associated with each receptacle to a vehicle. In would be advantageous to provide such information to the vehicle to prevent pick-up and emptying of receptacles owned or managed by entities delinquent in their payment of invoices. Also, a given account may have special instructions, such as an additional oversized pick-up, for a discreet single day or event. The dispatcher currently has no way of assuring that the special instructions are provided to the vehicle in a timely manner.
Furthermore, there is on-going and growing concern in major municipalities with controlling several aspects refuse collection. For instance, citizens or users will often engage in activity with respect to refuse receptacles that violates municipal codes. Some of this is caused by simply overloading receptacles. Other times, a user may fall behind in payment of bills for removing refuse and waste, and the receptacles and surrounding areas will become over loaded with refuse. This provides a haven for vermin such as rats. It may also cause damage to the lane on which the receptacles are located.
Absent constant patrol of back lanes, municipalities often have no idea that these conditions exist until it is too late. Even when patrolling the back lanes, it is difficult to impossible to determine which receptacles belong to which owners/addresses. Finally, when a positive identification of the offending receptacle is able to be determined the process consumes so much time that the municipal employee is only able to investigate but a handful of the many violations that occur at any one time. Thus, city officials need a method that will facilitate receptacle identification while at the same time providing a simplified method of issuing citations to the proper entity responsible for the code violation.
The present invention is provided to solve the problems discussed above and other problems, and to provide advantages and aspects not provided by prior waste and refuse collection systems and apparatuses of this type. A full discussion of the features and advantages of the present invention is deferred to the following detailed description, which proceeds with reference to the accompanying drawings.
One aspect of the present invention is directed to a method for controlling a municipal permit system. The method comprises the steps of: (1) providing an RFID tag having a unique identifier; (2) issuing a permit for a subject of the permit; (3) and associating the unique identifier with the permit.
This aspect of the present invention may further comprise one or more of the following steps: (1) establishing a database having information associated with a permit holder and the unique identifier; (2) providing instructions for affixing the RFID tag onto the subject of the permit; (3) providing a portable reader for receiving a signal carrying the unique identifier from the RFID tag; (4) using the portable reader to receive the signal carrying the unique identifier from the RFID tag; (5) storing the unique identifier in a memory module; (6) issuing a citation for a violation of a municipal ordinance associated with a subject of the permit; and (7) providing a printer with the portable reader for printing the citation.
Another aspect of the present invention is directed to a permitting method for use by a municipality. This method comprises the step of issuing a permit to a permit holder. The permit comprises a unique identifier stored on a means for transmitting the unique identifier via a wireless signal.
This aspect of the invention may further one or more of the following steps: (1) providing instructions for affixing the means for transmitting on a subject of the permit; (2) providing a database on which identifying information for the permit holder is associated with the unique identifier; (3) providing a portable reader for receiving the wireless signal carrying the unique identifier from the means for transmitting; (4) transmitting a signal carrying the unique identifier from the portable reader to a central station at a separate location from the portable reader; (5) providing a computer at the central station; (6) inputting the unique identifier transmitted from the portable reader into the computer; (7) using a software on the computer to associate the unique identifier transmitted from the portable reader with the identifying information of the permit holder; and (8) transmitting at least some of the identifying information of the permit holder associated with the unique identifier transmitted from the portable reader from the central station to the portable reader.
Another aspect of the present invention is directed to a method for a municipality to control, track, and monitor waste or refuse receptacles. This method comprises the steps of: (1) requiring a permit for use of a waste receptacle; (2) issuing the permit associated with a discreet receptacle identifier; (3) providing a transmitter means attached to a discreet receptacle; and (4) transmitting a signal carrying data associated with the discreet receptacle identifier from the transmitter means. This aspect of the invention may further include the steps of: (1) providing a handheld receiver for receiving the signal from the transmitter means; (2) identifying a municipal code violation associated with a use of the waste receptacle; and/or (3) using the handheld receiver to automatically generate citations based on the municipal code violation.
Other features and advantages of the invention will be apparent from the following specification taken in conjunction with the following drawings.
To understand the present invention, it will now be described by way of example, with reference to the accompanying drawings in which:
While this invention is susceptible of embodiments in many different forms, there is shown in the drawings and will herein be described in detail preferred embodiments of the invention with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention and is not intended to limit the broad aspect of the invention to the embodiments illustrated.
Referring to
Each receptacle 100 is outfitted with a means of communicating or transmitting a signal carrying an identifier associated with the receptacle 102, such as a radio frequency identification (RFID) tag. RFID tags are well-known in the retail industry for identifying products. In particular, an RFID tag or transponder is an object applied to or incorporated into a product for the purpose of identification using radio waves. Most RFID tags contain at least two parts, namely an integrated circuit for storing and processing information, modulating and demodulating a (RF) signal and an antenna for receiving and transmitting the signal. RFID tags come in three general varieties: passive, active, or semi-passive (also known as battery-assisted). Passive tags require no internal power source, thus being pure passive devices (they are only activated when a reader is nearby to power them), whereas semi-passive and active tags require a power source, usually a small battery. While the present discussion focuses on passive RFID tags, it is recognized that a similar system can be used for active and semi-active RFID tags.
The RFID tags may transmit high frequency (HF) signals, low frequency signals (LF), or ultra high frequency (UHF) signals. The characteristics of these signals differ, and one particular frequency may be more advantageous than another based on the particular application of the system. For instance, low frequency signals have a short read range (distance) which would prevent errors or false reads. UHF signals can have a read range that is very short to very wide (any yards or meter).
While RFID, and in particular passive RFID tags are discussed herein, it is recognized that other identifying or alerting tags can be used. Many are known and perhaps others in the future. For example, electrical article surveillance (EAS) tags can be used. EAS tags are commonly used to prevent shoplifting from retail stores. The EAS tags are attached to merchandise and are removed or deactivated by the clerks when the item is properly bought or checked out. At the exits of stores, a detection system sounds an alarm or otherwise alerts the staff when it senses active tags. These tags are typically made of a strip of amorphous metal (metglas) having a low magnetic saturation value. This strip is also lined with a strip of ferromagnetic material with a coercive field (magnetic “hardness”). Detection is achieved by sensing harmonics and sum or difference signals generated by the non-linear magnetic response of the material under a mixture of low-frequency (in the 10 Hz to 1000 Hz range) magnetic fields.
When the ferromagnetic material is magnetized, it biases the amorphous metal strip into saturation, where it no longer produces harmonics. The tags are activated by demagnetization and deactivated with magnetization.
The identifier associated with the receptacle is preferably a discreet identifier which is assigned to the receptacle 100. The identifier information is stored on a database typically located at the external site 300, and electronically joined with an account to which the receptacle 100 belongs. In other words, account information is housed on a database located at the external site 300. Each account has one or more receptacle identifiers associated with it, and the database carries with it information typical to the management of any business account, for example, special instructions, accounts receivable, last receipt, last invoice, amount in arrears, days since last payment, historical account information, contact information, owner, etc.
Referring to
Each of the vehicles 200a-d includes a waste bin 202 located above a baseline upon which the vehicle 200a-d is supported, generally the ground. The waste bin 202 includes a chamber 204 and an emptying site 206. The refuse within the receptacles 100 is loaded into the chamber 204 via the emptying site 206. One of ordinary skill in the art of waste hauling would readily understand this method of refuse handling without further description as it is the standard procedure employed in the art.
The vehicles 200a-d are further outfitted with at least one receiver 208a, in most cases a plurality of receivers 208a,b and preferably two. The receivers 208a,b may be sensors, transducers, or antennae, or any combination thereof. As illustrated in
The locations chosen for the receivers 208a,b are extremely important because the receivers 208a,b are used for several different purposes, including for possible tracking of the receptacle 100 as it is transferred from position-to-position relative to the vehicle 200a-d by a means for transferring the receptacle 212, which may be automated systems known in the art, as shown in
The preferred location of the first receiver 208a on a front loading vehicle 200a, illustrated in
The preferred location for the first receiver 208a on a side loading vehicle 200b, illustrated in
The preferred location of the first receiver 208a on a rear loading vehicle 200c, illustrated in
The preferred location of the first receiver 208a on a roll-off vehicle 200d, illustrate in
The vehicles 200a-d also include a second receiver 208b located at a position where reception of the signal from the transmitter means 102 can be promoted either at the instant of receptacle unloading or just prior or just subsequent to receptacle unloading. Accordingly, this second location is typically adjacent the emptying site 206 to the chamber 204 and in alignment with the first receiver. The phrases “in alignment with the first receiver 208a,” “aligned with the first receiver 208a,” and the like are intended to include a position wherein a path of the receptacle and the means for transmitting 102 taken from the first position at the first receiver 208a to a second position at the second receiver 208b, as determined by the means for transferring the receptacle 212 included on the vehicles 200a-c, naturally brings the means for transmitting 102 to a location where the second receiver 208b can receive the signal from the means for transmitting 102, i.e. into a range of the second receiver 208b where reception is achieved.
The preferred location of the second receiver 208b on a front loading vehicle 200a, illustrated in
The preferred location for the second receiver 208b on a side loading vehicle 200b, illustrated in
The preferred location of the second receiver 208b on a rear loading vehicle 200c, illustrated in
The preferred location of the second receiver 208b on a roll-off vehicle 200d, illustrate in
As shown in the block diagram of
The external site 300 may include a server 302 in communication with computer 304 and a database 306, typically on the computer 304. Of course, the server 300 is not required to be at the same physical site as the computer 304, nor is it required for the database 306 to be stored on a computer separate from the server 302. The block diagram is merely an example of a possible layout. The only requirement for the external site 300 is the database 306 and a means for communication between the vehicles and database 306.
Now, as illustrated in flowcharts of
Referring to
Next, the communication link sends a signal, either pass though or new, to the external site which receives the signal. The identity of the receptacle 100 is checked against an account database 306 to verify that the receptacle 100 should be emptied into the vehicle 200. A signal is generated indicating the account status associated with the receptacle identifier.
If the account is in good standing (pass condition), the controller 214 for the means for transferring the receptacle 212 is automatically activated either by a module or routine on the on-board computer or on the external computer 304. The means for transferring the receptacle 212 transports the receptacle 100 to the emptying site 20 where the transmitter means 102 is within reception range of the second receiver 208b. The transmitter means 102 sends a signal carrying discreet receptacle identifier information to the receiver 208b. The receiver 208b either passes the signal directly to the on-board communication link, preferably a module of the on-board computer 216, or generates a new signal based on the signal received from the means for transmitting, but still including some type of receptacle identifier. The triggered or pass through signal from the second receiver 208b represents an event. The event is preferably the emptying of the receptacle 100 into the vehicle bin 202. This event is recorded on the database 306 at the external site 300 and associated with the receptacle account.
If the account is not in good standing (fail condition), the controller 214 is not activated, a signal carrying an alarm or warning is transmitted to the vehicle 200. The account status can also be displayed on the on-board graphic interface 218. As a result, the transfer means 212 is not activated, and the receptacle 100 is not emptied into the vehicle bin 202. However, if for some reason, such as immediate, on-the-spot payment of an invoice by a customer, the vehicle personnel are inclined to empty the receptacle 100, vehicle personnel may override the alert and manually engage/energize the transfer means 212. In this case, as illustrated on the right hand side of
Referring specifically to
Referring specifically to
Referring to
For example, the external site 300 receives a first signal carrying a receptacle identifier from the vehicle 200. This first signal is associated with the receptacle 100 being located at the first position. The first signal originates with, though is not necessarily identical to, the signal received from the transmitter means 102 at the first receiver 208a. A module at the external site 300, preferably on the computer 304, compares the data carried by the signal against account information on the database 306 to determine an account status associated with the receptacle identifier. The result of the comparison, i.e., the account status, is transmitted from the external site 300 back to the vehicle.
Further, the external site 300 receives a second signal from the vehicle 200. This second signal is associated with the receptacle 100 being located at the second position. The second signal originates with, though is not necessarily identical to, the signal received from the transmitter means 102 at second receiver 208b. A module at the external site 300, preferably on the computer 304, compares the data carried by the signal against account information on the database 306 and records an event, the emptying of the receptacle 100, in connection with the receptacle 100.
Referring generally to
As set forth above, this aspect of the invention directly results in cleaner streets and alleys. The invention will eliminate or reduce trash overages, under size containers, poor container maintenance condition, e.g., no lid. Permits and citations will force compliance. Users can specify correct container size, schedule additional pick-ups. Service may be halted due to lack of payment or by schedule.
Information regarding each permit/receptacle identifier, the account associated therewith, and the entity responsible for the account/permit/receptacle is stored on a managed database. The database may include other information such as hauler name, permit number and container asset number (human readable sticker and RFID tag). Use and access of the database is explained in more detail below.
The RFID tags 102 can be read by inspectors having mobile and/or handheld computers 400. Citations may be issued immediately via printer on the handheld 400 and/or mailed with back-up violation data. Inspectors and other municipal employees use mobile handheld RFID readers with cameras to read tags and report violations. Citations can be issued and wireless transmission of data achieved through the handhelds 400.
This aspect of the invention requires haulers or receptacle owners to purchase annual container permits. The issued permit includes a means for transmitting 102, such as an RFID container tag. Revenue to the municipality is generated by an enforcement program.
Further, a container registration fee includes RFID tagging. The RFID tag information is linked to customer and hauler information in the database.
More specifically, a tag 102 (such as a passive RFID tag) acts as a permit. While the description below discusses passive RFID tags as permits, it is recognized that other information storing devices can also be used, such as active RFID tags, hybrid RFID tags, smartcards, and other hereto unknown items.
Typically, one goes to the governing body or agency and fills out the necessary registration forms, pays the necessary fees, and receives the RFID tag 102 acting as a permit. This initial registration and payment can also be done on-line through the internet or over the telephone. The tag includes certain necessary information dependent on its purpose. Encoding, entering, and keeping such information on the tag is well-known to those skilled in the art. Such information can include: the permit's issuing body (e.g., Secretary of State, Village of Anywhere, City of Nowhere), the date of issuance of the permit, the term of the permit (e.g., Jun. 1, 2010-May 31, 2011), the type of permit (e.g., “Permit for Trash,” “Vehicle Permit,” Elevator Permit), the location for the permit's use (e.g., “123 Main St. Anytown, USA,” “1999 Ford Austere,” “Elevator No. 6 SE for The Towers”), the responsible party's name and contact information (e.g., “Joe Smith at 111 S. Main, Anytown,” “Office of Management, The Towers, 432 E. Main, Anytown,” “Joe's Construction Co., 999 W. Main, Anytown”), and any other information necessary under the circumstances for the inspector to make a determination as to whether the permit is in compliance or out of compliance resulting in a violation. In the preferred application, the tag 102 includes all the information necessary for a government or independent inspector to make a determination in the field at a remote location as to whether a violation is present and has occurred relating to the item being inspected.
For visual inspection and to ensure proper location (e.g., the tag is in the correct vehicle or at the correct address), the RFID tag 102 typically has identifying indicia thereon such as time period involved, address, municipality's identity, and possibly the owner's identity. This ensures the tag 102 is placed at the proper location and gives the inspector visual verification of the tag's location.
The tag 102 is given or sent to the person responsible for the permit along with specific instructions as to placement, use, and purpose.
The 102 tag can also include a mounting component 104, such as a protective pocket or pouch having an adhesive on one side so the pouch can hold the tag and protect it and be adhered to the location where the permit is to be displayed, e.g., the outside wall of a recycling container, the inside of a trash can lid (outside the trash can itself) or on the outside can wall, the inside of a windshield, the inside of a business window, etc.
The handheld device 400 is preferably a small computer carried by an authorized remote user. It is the method used to gather information in the field by the inspector, such as a policeman, village employee, etc. The device 400 includes several components, that being a power source 401, such as a battery, a means to enter data (a reader and keyboard) 402, an internal clock 404, a memory 406, a GPS locator 408, a camera 410, a monitor or screen 412, and a printer 414 or preferably a wireless connection 416 to a printer 414 having a wireless communication means 418.
One or more methods can be employed to enter the necessary data into the remote handheld device 400. The preferred means is an RFID reader 420. The reader 420 is capable of reading passive RFID tags 102 in the field. A keyboard 412 may also be provided for entering additional data as may be necessary.
In particular, three items are inputted into the remote handheld device 400, that being an authorization code, the permit information, and the time and date. The user's authorization code and the date and time can be entered on a keyboard provided on the handheld device 400. However, the preferred method of entering such data is by a reader 420 associated with the handheld device 400. The reader 420 can read the tags 102, such as passive RFID tags. The user/inspector can thus have an identification RFID card with the necessary authorization codes thereon to activate the device 400 and to operate and use the device 400 once the reader 420 reads the authorization information. Similarly, the reader 420 can read the information provided on the permit, such as a license plate number, a home address, a business address, etc. The date and time can be entered automatically by an internal clock 404 in the device 400.
A internal clock 404 is provided to document the time certain events occur, such as the reading, gathering and/or entering of information associated with reading the permit, the date/time of a photograph, and the date/time a citation is entered or printed, etc. The clock 404 is an internal mechanism stamping the memory of the event (permit reading, photograph, GPS locating, citation issuance) with the date and time of the event.
The device 400 includes a screen or monitor 412 for displaying information read and received. The device 40 also includes a wireless connection or link (Bluetooth) 416 to a mobile printer 414. The device 400 can then display or print information obtained by the reader 420 in the device 400 relating to the tag 102 or generated by the device 400 and relating to a citation. In the alternative, the printer 414 need not be mobile, but can be used at a central location 500 so that when the device 400 is downloaded at a central location 500 (such as the police station or city hall) through conventional means, information read by it or citations generated by it can be printed out.
An optional camera 410 and/or GPS locator 408 may also be provided in the handheld device 400 to document both what is seen visually by the remote user and to identify the location of the remote user.
Once the data has been entered or citation processed, the entry or issuance can be confirmed by digital or physical signature. The device 400 can have a touch screen for recording a signature by the inspector. In the alternative, the inspector's authorization card can be read once more or drawn from the device's memory 406 to confirm the inspector's identity and authorization relating to the entry of information or issuance of a citation.
As noted, biographically and permit information is obtained from an applicant for the permit and stored in the tag 102. For trash, refuse and recyclables this information will also include time period of permit (e.g., 6 months, 1 year, etc.), number of containers, location of containers (address), type of containers (e.g., size), and hauler information (identity, contact information, pick-up schedule, etc.). A permit, in this case—an RFID tag 102—is issued by the authorized body. The RFID tag 102 will typically have identifying indicia thereon such as address of containers, and possibly types and/or size of containers. The RFID tag 102 has an adhesive thereon or is placed into a protective pouch (having a transparent cover, with an adhesive on an outwardly facing surface). The RFID tag 102 is then adhered to the outer container wall in a designated location.
A remote, authorized user, typically a government or third party inspector enters an authorization code by typing it in or reading it (or it is automatically drawn from memory 406 and the initial sign-on/authorization), on her handheld device 400. When at the remote location, the inspector then reads the RFID tag 102 (the permit information contained thereon) with the handheld device 400. The display 412 (or print-out) will then display the necessary information for the inspector to make a determination as to whether the permit is in compliance or whether there is a violation. Such violations can include, among others, the permit is outdated and expired, the containers 100 of the permit are not the same as those being used, the containers 100 are constantly and consistently overflowed meaning they are undersized, the containers 100 are damaged and have not been properly maintained, the containers 100 are missing lids/covers, the containers 100 are in an improper location, the containers 100 do not have a permit, and/or the hauler has not made the necessary and scheduled pick-ups of recyclables and/or refuse. Of course, one of the primary purposes of issuing citations is to force compliance with rules, regulations and ordinances to maintain properly sized, safe equipment.
If desired, to document or corroborate the violation, the inspector can take a photograph of the scene with a camera 410 built-into or associated with the handheld device 400 and obtain the GPS location of the scene with a GPS locate 408 built-into or associated with the handheld device 400. This documentation stored in memory 406 can accompany the citation or merely be kept in memory 406 (on the handheld device or at a central database 502 at the central station 500) as back-up. It is preferred to have such documentation accompany and be part of the citation.
Once a violation has been determined, the inspector can issue or process a citation. This can be accomplished many ways. One way is to use the information read from the tag 102 and in the memory 406 of the handheld device 400 and entering the necessary information associated with the violation. The citation can then be stored in the memory 406 of the device 400 and formally issued later via mail or similar once the inspector's tour is completed. In the alternative, the device 400 can include a wireless link 416 to a mobile printer 414 for printing the citation and giving it or leaving it with the responsible party (business owner, individual, etc.). The violation and citation records can further be stored in the device's memory 406 for downloading later for documenting the citation, record keeping, tracking and follow-up. If the device 400 was used to take a picture and/or obtain location information, that information can also be attached or used with the issued citation as confirmatory information and supporting documentation.
It should be recognized that while the handheld device 400 is discussed as being carried by an inspector, it can also be mounted on a vehicle. As a result, the tag-permit can also be read by an RFID or similar reader mounted to a mobile vehicle. In some instances, this may prove to be more efficient.
The above describes a system wherein the tag-permit 102 and handheld device 400 are the primary components and virtually the sole components of the system. In an alternative device, the device 400 includes a communications module 416 to communicate with a central station 500 having a central database 502 and the tag-permit 102 has encoded information thereon for directing the central station 500 to make a determination of whether there is a violation and a citation should be issued.
Briefly, while the tag 102 acts as the permit, it merely includes identifying information encoded therein. As before, it may also have identifying indicia thereon such as time period involved, address and municipality's identity and possibly the owner's identity. Again, a mounting component 104, such as a pouch, can be used also.
The registration information, instead of being stored on the permit, is stored in a memory 504 associated with the central station 500. The central database 502 is housed and maintained at the central location 500 such as a police station, village hall, county office or state agency, or third party service provider. Some, if not all of the information is obtainable by and from an authorized remote user. The central database 502 is maintained on a system, such as on a computer 506, that can receive queries and transmit select information automatically or by pointed requests. As a result and by way of example, a policeman may access the database 502 and request certain vehicle and owner information by entering a license plate number or by specific inquiry prompted by reading the RFID-permit.
A communication module 508 is associated with the central station 500 allowing data or information to be received from one or more remote handheld devices 400 and information to be transmitted to one or more remote handheld devices 400.
Housed with the central station 500 is look-up and/or comparison software 510 capable of receiving information from the handheld device 400, polling/querying the memory 504 associated with the central station 500, and if necessary, making a comparison and generating a report or result of the comparison made. The information polled/looked up or generated by a comparison is then sent to the remote handheld device 400.
Specifically, the information obtained from the handheld device 400, such as a license plate entered into the remote handheld device 400 or by reading the tag 102 with an RFID reader 420, and received by the central station 500 will be looked-up or compared with the information accessed from the central database 502. The individual operating the remote device 400 can then determine whether a violation has occurred (such as when the looked-up data shows the permit has expired). Or, the database 502 comparison will then determine if the information obtained is the same as the information stored and/or determine whether a violation has occurred, such as the permit period paid for has lapsed.
The handheld device 400 is described above and is similar, except it further includes a communications module 416 for transmitting and receiving communications from the central station 500.
As noted, biographically and permit information is obtained from an applicant and stored in memory in a central database 502. A remote, authorized user, typically a policeman, government employee, or third party or government inspector, once authorized, reads the RFID-permit by the handheld device 400. This information is transmitted to the central database 502 where, in turn, the database queries its memory for information necessary to determine if a violation occurred, such as the permits expiration or improper container size. A citation can then be issued. And printed a the handheld devise 400 or on a printer 512 at the central station 500
By way of example, with respect to vehicle stickers, a traffic control manager can read an RFID attached to a windshield and transmit the information to a central database 502. The central database 502 then polls its memory 506 for information associated with that permit. The database or the manager in the field can then determine if the permit is expired or if the permit is associated with the correct vehicle. If a violation has occurred, the manager can issue a citation by printing a citation and attaching it to the car or transmitting the necessary information to the central database for printing and issuing (by mail) the citation.
While the specific embodiments have been illustrated and described, numerous modifications come to mind without significantly departing from the spirit of the invention, and the scope of protection is only limited by the scope of the accompanying Claims.
This application is a continuation of application Ser. No. 14/269,771, now U.S. Pat. No. 9,546,040, filed on May 5, 2014, which is a continuation of Ser. No. 13/353,900, now U.S. Pat. No. 8,714,440, filed on Jan. 19, 2012, which was a continuation of application Ser. No. 12/274,273, now U.S. Pat. No. 8,146,798, filed on Nov. 19, 2008, which was a continuation-in-part of application Ser. No. 12/267,367, filed on Nov. 7, 2008 and application Ser. No. 12/267,340, now U.S. Pat. No. 8,815,277, also filed on Nov. 7, 2008. Each application is hereby incorporated by reference as if fully set forth herein.
Number | Name | Date | Kind |
---|---|---|---|
3636863 | Woyden | Jan 1972 | A |
3765147 | Ippolito et al. | Oct 1973 | A |
4854406 | Appleton et al. | Aug 1989 | A |
4953109 | Burgis | Aug 1990 | A |
4955495 | Ruebesam | Sep 1990 | A |
5004392 | Naab | Apr 1991 | A |
5014206 | Scribner et al. | May 1991 | A |
5119894 | Crawford et al. | Jun 1992 | A |
5209312 | Jensen | May 1993 | A |
5222853 | Carson | Jun 1993 | A |
5230393 | Mezey | Jul 1993 | A |
5303642 | Durbin et al. | Apr 1994 | A |
5304744 | Jensen | Apr 1994 | A |
5326939 | Schafer | Jul 1994 | A |
5389346 | Copeland, Jr. | Feb 1995 | A |
5401915 | Schafer | Mar 1995 | A |
5416706 | Hagenbuch | May 1995 | A |
5464489 | De Graaf | Nov 1995 | A |
5565846 | Geiszler et al. | Oct 1996 | A |
5631835 | Hagenbuch | May 1997 | A |
5644489 | Hagenbuch | Jul 1997 | A |
5726884 | Sturgeon et al. | Mar 1998 | A |
5740050 | Ward, II | Apr 1998 | A |
5837945 | Cornwell et al. | Nov 1998 | A |
5861805 | Reeves | Jan 1999 | A |
5909480 | Reynaud et al. | Jun 1999 | A |
5947256 | Patterson | Sep 1999 | A |
5967028 | Schomisch et al. | Oct 1999 | A |
6021712 | Harrop | Feb 2000 | A |
6055902 | Harrop et al. | May 2000 | A |
6170318 | Lewis | Jan 2001 | B1 |
6191691 | Serrault | Feb 2001 | B1 |
6206282 | Hayes, Sr. et al. | Mar 2001 | B1 |
6302461 | Debras et al. | Oct 2001 | B1 |
6318636 | Reynolds et al. | Nov 2001 | B1 |
6412406 | Flood et al. | Jul 2002 | B1 |
6421080 | Lambert | Jul 2002 | B1 |
6429776 | Alicot et al. | Aug 2002 | B1 |
6448898 | Kasik | Sep 2002 | B1 |
6510376 | Burnstein | Jan 2003 | B2 |
6600418 | Francis et al. | Jul 2003 | B2 |
6601015 | Milvert et al. | Jul 2003 | B1 |
6647200 | Tanaka | Nov 2003 | B1 |
6759959 | Wildman | Jul 2004 | B2 |
7225980 | Ku et al. | Jun 2007 | B2 |
7256682 | Sweeney, II | Aug 2007 | B2 |
7275645 | Mallett et al. | Oct 2007 | B2 |
7318529 | Mallett et al. | Jan 2008 | B2 |
7328842 | Wagner et al. | Feb 2008 | B2 |
7385510 | Childress et al. | Jun 2008 | B2 |
7436303 | Tourrilhes et al. | Oct 2008 | B2 |
7454358 | Mallett et al. | Nov 2008 | B2 |
7456418 | Stevens et al. | Nov 2008 | B1 |
7487100 | Mallett et al. | Feb 2009 | B2 |
7501951 | Maruca et al. | Mar 2009 | B2 |
7511611 | Sabino et al. | Mar 2009 | B2 |
7518506 | Lee et al. | Apr 2009 | B2 |
7525443 | Littrell | Apr 2009 | B2 |
7591421 | Linton et al. | Sep 2009 | B2 |
7609406 | Roth et al. | Oct 2009 | B2 |
7639136 | Wass et al. | Dec 2009 | B1 |
7660724 | Mallett et al. | Feb 2010 | B2 |
7728730 | Langlois et al. | Jun 2010 | B2 |
7870042 | Maruca et al. | Jan 2011 | B2 |
8014863 | Zhang et al. | Sep 2011 | B2 |
8015029 | Flood | Sep 2011 | B2 |
8020767 | Reeves et al. | Sep 2011 | B2 |
8056817 | Flood | Nov 2011 | B2 |
8109759 | Robertson et al. | Feb 2012 | B2 |
8146798 | Flood et al. | Apr 2012 | B2 |
8165277 | Chen et al. | Apr 2012 | B2 |
8185277 | Flood et al. | May 2012 | B2 |
8210428 | Flood | Jul 2012 | B2 |
8714440 | Flood et al. | May 2014 | B2 |
9251388 | Flood | Feb 2016 | B2 |
9396453 | Hynes et al. | Jul 2016 | B2 |
20010028032 | Church et al. | Oct 2001 | A1 |
20020077875 | Nadir | Jun 2002 | A1 |
20020105424 | Alicot et al. | Aug 2002 | A1 |
20020163577 | Myers | Nov 2002 | A1 |
20020180588 | Erickson et al. | Dec 2002 | A1 |
20020196150 | Wildman | Dec 2002 | A1 |
20030025599 | Monroe | Feb 2003 | A1 |
20030031543 | Elbrink | Feb 2003 | A1 |
20030069716 | Martinez | Apr 2003 | A1 |
20030071736 | Brazier et al. | Apr 2003 | A1 |
20040123812 | Condon | Jul 2004 | A1 |
20040133484 | Kreiner | Jul 2004 | A1 |
20040145472 | Schmidtberg et al. | Jul 2004 | A1 |
20040199401 | Wagner et al. | Oct 2004 | A1 |
20040215351 | Kiire et al. | Oct 2004 | A1 |
20040233284 | Lesesky et al. | Nov 2004 | A1 |
20040257203 | Maltsev et al. | Dec 2004 | A1 |
20050018049 | Falk | Jan 2005 | A1 |
20050080520 | Kline | Apr 2005 | A1 |
20050088299 | Bandy et al. | Apr 2005 | A1 |
20050126405 | Imperato | Jun 2005 | A1 |
20060012481 | Rajapakse et al. | Jan 2006 | A1 |
20060032917 | Ritter | Feb 2006 | A1 |
20060080819 | McAllister | Apr 2006 | A1 |
20060157206 | Weik et al. | Jul 2006 | A1 |
20060177119 | McPheely et al. | Aug 2006 | A1 |
20060208072 | Ku et al. | Sep 2006 | A1 |
20060208859 | Hougen et al. | Sep 2006 | A1 |
20060220922 | Brinton et al. | Oct 2006 | A1 |
20060221363 | Roth | Oct 2006 | A1 |
20060253297 | Mallett et al. | Nov 2006 | A1 |
20060273180 | Ammond | Dec 2006 | A1 |
20070014693 | Kantrowitz et al. | Jan 2007 | A1 |
20070025600 | Ghebreyesus | Feb 2007 | A1 |
20070033108 | Luhr | Feb 2007 | A1 |
20070085676 | Lee et al. | Apr 2007 | A1 |
20070109103 | Jedrey et al. | May 2007 | A1 |
20070112620 | Johnson | May 2007 | A1 |
20070126592 | Littrell | Jun 2007 | A1 |
20070143079 | Duxbury et al. | Jun 2007 | A1 |
20070217761 | Chen et al. | Sep 2007 | A1 |
20070227125 | Robertson et al. | Oct 2007 | A1 |
20070236352 | Allen et al. | Oct 2007 | A1 |
20070250339 | Mallett et al. | Oct 2007 | A1 |
20070257857 | Marino et al. | Nov 2007 | A1 |
20070260466 | Casella et al. | Nov 2007 | A1 |
20070262878 | Maruca | Nov 2007 | A1 |
20070268759 | Sabino | Nov 2007 | A1 |
20080001746 | Childress et al. | Jan 2008 | A1 |
20080010197 | Scherer | Jan 2008 | A1 |
20080061125 | Langlois et al. | Mar 2008 | A1 |
20080061977 | Maruca et al. | Mar 2008 | A1 |
20080077541 | Scherer et al. | Mar 2008 | A1 |
20080169342 | Gonen | Jul 2008 | A1 |
20080185540 | Turner et al. | Aug 2008 | A1 |
20080197059 | Mallett et al. | Aug 2008 | A1 |
20080197194 | Flood | Aug 2008 | A1 |
20080198021 | Flood | Aug 2008 | A1 |
20080202357 | Flood | Aug 2008 | A1 |
20080211637 | Smith | Sep 2008 | A1 |
20080237251 | Barber | Oct 2008 | A1 |
20080275287 | Stevens et al. | Nov 2008 | A1 |
20080297314 | Kuwako et al. | Dec 2008 | A1 |
20080308631 | Mitschele | Dec 2008 | A1 |
20090276299 | Gonen | Nov 2009 | A1 |
20100088203 | Hynes et al. | Apr 2010 | A1 |
20100116881 | Flood et al. | May 2010 | A1 |
20100119340 | Flood et al. | May 2010 | A1 |
20100119341 | Flood et al. | May 2010 | A1 |
20100167704 | Villemaire | Jul 2010 | A1 |
20110279245 | Hynes et al. | Nov 2011 | A1 |
20120120449 | Flood et al. | May 2012 | A1 |
20140182951 | Curotto | Jul 2014 | A1 |
20140239059 | Flood et al. | Aug 2014 | A1 |
Number | Date | Country |
---|---|---|
2006225303 | Oct 2006 | AU |
2005211634 | Apr 2007 | AU |
2678933 | Oct 2016 | CA |
3933795 | Apr 1991 | DE |
19708204 | Sep 1998 | DE |
0500213 | Aug 1992 | EP |
0557238 | Aug 1993 | EP |
0899215 | Mar 1999 | EP |
2464272 | Apr 2010 | GB |
2464272 | Apr 2010 | GB |
6-44483 | Feb 1994 | JP |
7-33455 | Feb 1995 | JP |
7033455 | Mar 1995 | JP |
09245168 | Sep 1997 | JP |
3-241180 | Dec 2001 | JP |
2003-246409 | Sep 2003 | JP |
2004137042 | May 2004 | JP |
2005 008339 | Jan 2005 | JP |
2005 063217 | Mar 2005 | JP |
2005 067850 | Mar 2005 | JP |
2006163324 | Jun 2006 | JP |
2006 215857 | Aug 2006 | JP |
2007063014 | Mar 2007 | JP |
6-044483 | Dec 2016 | JP |
10-2006-0005812 | Jan 2006 | KR |
10-2006-0026226 | Mar 2006 | KR |
2006-0109306 | Oct 2006 | KR |
10-2007-0032381 | Mar 2007 | KR |
10-0732381 | Jun 2007 | KR |
2230015 | Oct 2004 | RU |
113395 | Oct 2012 | RU |
WO 9703768 | Oct 1997 | WO |
WO 9838593 | Sep 1998 | WO |
WO 9939899 | Aug 1999 | WO |
2008103820 | Oct 2008 | WO |
2010054232 | May 2010 | WO |
Entry |
---|
Local Patent Rule 2.3 Disclosures from Sonrai Systems, LLC, et al. v. AMCS Group, Inc., No. 1:16-cv-9404. |
Exhibits to Petition for Inter Parties Review of U.S. Pat. No. 8,146,798 Pursuant to 35 U.S.C. Secs. 311-319, 37 C.F.R. Section 42. |
PCT International Search Report and Written Opinion of the International Searching Authority dated Aug. 14, 2017. |
International Search Report for PCT/US2008/054571 dated Aug. 14, 2008. |
International Preliminary Report on Patentability for PCT/US2008/054571 dated Aug. 26, 2009. |
Written Opinion of ISA for PCT/US2008/054571 dated Aug. 14, 2008. |
International Search Report for PCT/US2009/063601 dated Mar. 12, 2010. |
International Preliminary Report on Patentability for PCT/US2009/063601 dated May 10, 2011. |
Nritten Opinion of ISA for PCT/US2009/063601 dated Mar. 12, 2010. |
Supplementary European Search Report for EP 08730384 dated Oct. 17, 2011. |
First Examination Report for EP 08730384.8 dated Nov. 22, 2012. |
Petition for Inter Partes Review of U.S. Pat. No. 8,146,798 Pursuant to 35 U.S.C. Secs. 311-319, 37 C.F.R. Section 42 (80 pages). |
Petitioner's Reply to Patent Owner's Response to Petition, Case No. IPR2018-00139 dated Jan. 25, 2019 (30 pages). |
Petitioner's Demonstrative Exhibits, Case No. IPR2018-00139, U.S. Pat. No. 8,146,798 (50 pages). |
Exhibit 1032 of Petitioner's Reply to Patent Owner's Response to Petition served Jan. 25, 2019 entitled Morgan D. Rosenberg—Essentials of Patent Claim Drafting (2019 Edition) Section 3.02 (12 pages). |
Final Written Decision, Case IPR2018-00139, U.S. Pat. No. 8,146,798, Paper No. 35 dated May 20, 2019 (36 pages). |
Aug. 14, 2017—(WO) International Search Report and Written Opinion—APP PCT/US2017/025569. |
Nov. 8, 2018—(US) Non-Final Office Action—U.S. Appl. No. 14/593,764. |
May 17, 2019—(US) Non-Final Office Action—U.S. Appl. No. 15/011,940. |
Number | Date | Country | |
---|---|---|---|
20170121107 A1 | May 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14269771 | May 2014 | US |
Child | 15406970 | US | |
Parent | 13353900 | Jan 2012 | US |
Child | 14269771 | US | |
Parent | 12274273 | Nov 2008 | US |
Child | 13353900 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12267340 | Nov 2008 | US |
Child | 12274273 | US | |
Parent | 12267367 | Nov 2008 | US |
Child | 12267340 | US |