In a system such as the Gen II Meter System (Provisional Patent Application Ser. No. 61/202,201, Filed February 2009) built with multiple processors contained in a single node provides internal monitoring of the operability of all units. An alphanumeric identifying message ID for each message is transmitted from a component to identify intermittent and other communication errors such as consistently “lost” packets of information within a RAM system (patent application Ser. No. 11/802,244, filed 21 May 2007) for Parking Management. An alphanumeric identifying message ID for each message transmitted from a component to identify intermittent and other communication errors such as consistently “lost” packets of information within a RAM system for Parking Management. An alphanumeric message Id confirms message delivery between radio network components in the RAM system for parking. The alphanumeric message ID confirms message delivery between radio network components in the RAM system for parking. The above alphanumeric message ID confirms message delivery between radio network components in the RAM system for parking. The above alphanumeric message IF confirms message delivery between radio network components in the RAM system for parking. A switching mechanism is used as a method of time stamping Parking Meter collections and sending sets of commands either directly from handheld implements or through a radio network.
The provisional patent application Ser. No. 61/202,201 relates to multiple task specific processors such as an Application Processor, a Meter Controller and a Radio Processor all controlled via a shared SPI bus and using rechargeable batteries and solar power sources for controlling and monitoring a vehicle parking system.
The invention entitled: Parking System Employing RAM Techniques, Ser. No. 11/802,244, filed 21 May 2007 which relates to the management of vehicle parking systems and in particular to such systems using remote management techniques for enhancing management efficiency and to provide solutions to the parking system that could not otherwise be managed by (1) sensing, collecting, recording and displaying data regarding all aspects of the environment pertaining to the parking system, (2) analyzing the data collected to create actionable outputs responsive to the needs of the public and the management of the parking system; (3) communicating with the various parking system components, and (4) receiving feedback to perform requested operations for the parking system.
The system of the invention with the GEN II Meter System uses multiple processors contained in a single node to provide internal monitoring of the operability of all units in the system. The invention uses an embedded power control unit such as the one included in the GEN II Meter System to reset any non-responsive processor in the individual node when one of the processors is found to be non-responsive.
Within a complex system of microprocessors such as the Gen II Meter System, individual processors may become disabled by undiscovered programming bugs or unforeseen circumstances. A disabled microprocessor would render the system incapable of providing accurate data—if any data at all is able to be transmitted. In order to correct such a failure, a maintenance worker would have to be dispatched to correct the problem on-site. This results in a cost in terms of labor, fuel, and/or lost revenues at the meter. The problem could also mean that citations are contested by motorists resulting in lost revenues from citations as well as costs in terms of personnel and legal fees to adjudicate such citations.
Having multiple processors in the same piece of electronic equipment not only saves power, but also allows independent operation of each unit so that if anyone processor enters a disabled state, the remaining processors remain operable. Taking advantage of this redundancy, the operable processors can periodically check the operability of the other processors in its proximity. If it is found that one of the proximate processors is non-responsive, the operable processor can re-initialize the non-responsive one by using a command to the power control unit which switches power to the non-responsive processor off and then back-on. This re-initialization can often restore the non-responsive processor to normal operation.
Use of an alphanumeric identifying message ID for each message transmitted from a component to identify intermittent and other communication errors such as consistently “lost” packets of information within a RAM system for Parking Management.
Wireless communication systems, such as that envisioned in the RAM system for Parking are subject to lost message packets. This is an intermittent condition that may simply be a one-time issue. Similarly, “lost” packets may also indicate a more significant problem. The difference can be problematic to distinguish.
A daily examination of data received for each radio asset is performed to determine the percentage of packets lost over the last day. The test should keys off the embedded sequence number associated with each radio message generated by a radio. These sequence numbers exist within a predefined range and increment from zero to the upper range limit with each message sent. If a message sequence number is equal to the upper range limit for one message, the next message will have a sequence number of zero and restart the incremental process. This is considered when processing new messages. If an expected sequence number is not received within 10 messages, it is considered lost. If the resulting lost packet rate is more than a pre-defined percentage of total messages expected (“lost” packets+received packets), an alarm state can be triggered and the problem investigated.
Use of the above alphanumeric message ID to confirm message delivery between radio network components in the RAM system for Parking. In systems such as the RAM system for Parking Management, communications between radio network components can be interrupted. Additionally, these messages are often transmitted after a previous message is transmitted. If multiple messages are sent from one originating radio, but only a portion of them are received completely, it isn't possible for the originating radio to re-send the interrupted message without an indication as to which message was interrupted This results in either the need to transmit all the messages again—causing increased radio traffic, interference and power drain- or the need to drop the packet and create data inaccuracies.
The receiving radio sends an acknowledgement message back to the originating radio with each message received successfully including the alphanumeric message ID. Only upon receipt of the acknowledgement record or aging algorithm does the originating radio discard the message from the queue of messages to send. If the originating radio receives no acknowledgement message or instead receives a No-Acknowledgement message with a matching message ID, it re-sends the message. This ensures that all messages have the maximum chance to be received from the originating device to the Command and Control Interface in the RAM System for Parking Management.
Use of an additional battery to those described in the GEN II Meter System to supplement or replace traditional non-rechargeable batteries used in standard electronic parking meters,
While the Gen II Meter System can generate significantly more power than is needed by the radio detection and application processor systems, many electronic parking meters only have connections to allow regular, non-rechargeable batteries to connect to the meter for the purpose of powering them. Additionally, standard electronic parking meters burn through batteries within 18 months or even in as little as 6 months. This results in the need for maintenance personnel to be mobilized to visit each meter regularly to replace the batteries used to power the mechanisms. Each replacement costs those managing parking operations in terms of labor, fuel and battery costs. Additionally, replacement of batteries results in unusable discharged batteries that need to be disposed. This disposal is costly due to environmental effects of disposing batteries made of toxic chemicals. The GEN II Meter System can be paired with a rechargeable battery fitted with appropriate connection to allow the rechargeable battery to connect to the meter's electronics so as to either supplement or replace the currently used non-rechargeable batteries. Use of this power greatly reduces or even negates the number of battery replacements a manager of a parking operation would need to replace meter mechanism batteries as well as the incursion of the costs related to battery replacement.
Use of meters such as those described in the Gen II Meter System and the handheld or in-vehicle mounted mobile computers connected to a central Command and Control Interface as described in the RAM System for Parking to produce a ranking of both groups of spaces and individual spaces for display on mobile data terminals in ranked order for use by enforcement, maintenance and collections personnel.
Currently enforcement, maintenance and collections are performed either by following established routes and seeking out specific problems. Other methods of deployment include using historical records to determine area of high probability of violations, in-operable meters or meters nearing capacity. The current methods of managing these assets incur costs in terms of labor, fuel and lost revenues due to the inefficiencies inherent in routine inspection methods
GPS systems embedded in either the handheld or in-mounted mobile computers or vehicles used by enforcement, maintenance and collections personnel can provide the specific locations of the field level workers back to the command and control interface as described in the RAM System for Parking. The proximity of meter operation exceptions (violations, meter errors or low meter coin capacity) to those responsible for addressing the exceptions can be added to other operational elements (number of additional exceptions in that area, revenue potential, business goals or other criteria) to rank either individual spaces or even collections of meters for attention by field level personnel. By deploying personnel to problems by exception, great efficiency can be achieved. Not only are labor and fuel costs reduced, but equipment repairs are completed more quickly-increasing uptime. Additionally, the amount of time needed to identify and cite vibrations is greatly reduced resulting in greater numbers of citations that can be issued.
Use of data received from the handheld or in-vehicle mounted mobile computers described in the RAM system for Parking to show proximity of field level personnel to specific parking spaces with exceptions requiring attention of those workers.
Supervisor personnel currently do not have an easy way of determining where their field level personnel are at a given point of the day. Supervisors can contact personnel and ask for their location. This method is not only error prone, but also can't be confirmed. Errors in dispatching personnel to the nearest locations can result in inefficient routing. That, in turn, creates additional and unnecessary fuel and labor costs as well as lost revenue opportunities due to inoperable equipment or not cited violations.
GPS systems embedded in either the mobile computers or vehicles use by enforcement, maintenance and collections personnel can provide the specific location of the field level worker back to the command and control interface as described in the RAM system for Parking. This information can be displayed on the interfaces of the command and control interface portal. Various icons can track the handheld unit and any equipped vehicle separately. The history of location information can be displayed as a collection of points and the timestamps from each reading used to illustrate the route taken by the field level worker and/or his vehicle. Different icons can be used to distinguish between handheld tracking and vehicle tracking on the same map as the stationary parking meter assets. This gives the supervisors a confirmed history of each worker as well as a confirmed location of that worker to current issues in near real-time. By deploying personnel to problems by proximity, great efficiency can be achieved. Not only are labor and fuel costs reduced, but equipment repairs are completed more quickly-increasing uptime. Additionally, the amount of time needed to identify and cite violations is greatly reduced resulting in greater numbers of citations than can be issued.
Combining the data used in the two preceding paragraphs with known information regarding charged parking rates, parking demand, turnover, parking time limits, violation type, violation fine levels, historical violation durations and other metrics to rank tasks for field workers and the application of an artificial intelligence to permit a system to uniquely identify the highest assay opportunity—taking into account the worker's location as well as a ranked priority of the other factors known from current and historical data, where the historical data includes historical parking space management characteristics and historical various parking space conditions which together may define the dynamic priority of near real time exceptions from predetermined parking space management characteristics of the parking space and the exceptions may be actionable in near real time based on the historical geographical locations of the mobile computer and the field level workers.
Parking management activities are complex to prioritize. First, parking management goals can include revenue maximization, space availability maximization or many other types of goals. Second, the environment in which parking management equipment is used is one that is constantly changing. Current methods of identifying exceptions in compliance, operability or vault capacity cannot provide the necessary information to guide the workers in the field to the tasks most directed toward the accomplishments of those goals.
The command and control interface within the Ram system for parking management can be configured with flexible algorithms that score each exception on parameters that match the management goals of the parking manager. These inputs can include but are not limited to, the number of nearby exceptions, the rate of the space per hour, the number of occupants normally visiting that space per day, the average duration of violations in that space, the average duration of stay per motorist, the fines for each type of violation and the type of violation being observed. Each of these items can be weighted in a manner that reflects the goals of the parking manager to rank each exception so that each exception can be addressed in a way that most applies to the goal of the parking manager. This process is automated through algorithms so that the priority of tasks can be dynamic—based on the ever-changing environment being managed.
Reed relay as a method of time stamping Parking Meter collections and sending sets of commands either directly from handheld computers or through the network. A meter system like the GEN II Meter System requires an event-triggered form of communication in order to avoid overuse of a limited battery power. This prevents many on-demand functions from being initiated such as immediate posting of time by city personnel or initialization of transmission of meter audit records at the time collections are taken.
The use a Reed Relay or other form of switch to wake the meter node allows any number of instructions to be executed on demand. The waking of the meter node can be used to initiate a pre-established set of commands possibly including communication to a collector or gateway to receive data and commands awaiting it there and/or communicate to a proximate handheld to similarly receive data and commands awaiting it there. Another possible command set can be used to trigger the meter to transmit its audit information for later comparison to collection receipts. Additionally, the command set can be used to have the meter node await customized instructions from the handheld device carried by the field worker. These command sets would be customized to the activity being performed by the field worker present at that time.
Loop Puck
The use of inductance loops can often require the running of lead wires from many spaces to a common point where the monitoring of a plurality of spaces is performed. This consolidated point is often a long distance away from the individual spaces and the distance can cause higher installation costs and—the possibility of breakage. Additionally, the running of many wire leads from multiple spaces to a common location can in some situations cause cross-talk—the confusion of a signal on one line to interfere with the communications of the signal on another line.
A small detection unit and radio device of the GEN II design can be packaged in a small container. This unit can be connected to the loop leads and installed in a cored-out area near the loop itself. The unit would then transmit to a central collector as in the GEN II Meter System, thereby negating the need to cut long channels to consolidate the loop leads in a single location.
List of Internal Diagnostics and Messaging
The Gen II Meter System is a complex set of subsystems. A failure in any one of these systems may affect the operability of the entire system monitoring that space. Without proper monitoring data, timely trouble-shooting and repair is difficult.
The GEN II Meter System employs self-monitoring protocols that cover the following areas of its operation:
(1) Checksum error
(2) Link level protocol error
(3) Transport level protocol error
(4) Application level protocol error
(5) Invalid transport address
(6) Invalid request type
(7) Invalid data in request
(8) Invalid count was specified in a request
(9) Verify error (FUP only)
(10) No transfer buffer available
(11) No memory buffer available
(12) Invalid message length
(13) Error accessing real time clock
(14) Invalid chip Id
(15) Not active
(16) Device is busy
(17) Invalid sequence number
(18) No response to application level request
(19) Device cannot accept input—retry later
(20) Parking meter error: Protocol error
(21) Parking meter error: invalid acknowledgement character received from parking meter
(22) Parking meter error: Listen pulse error
(23) Parking meter error: Meter mode character error
(24) Parking meter error: Parking meter has been disabled
(25) Parking meter error: Invalid event pointer
(26) Parking meter error: Access denied
(27) File system error: Directory is full
(28) File system error: Storage is full
(29) File system error: Bad link in file
(30) File system error: No file is open (in for request operation)
(31) File system error: Invalid data count
(32) File system error: End of file seen
(33) File system error: File not found
(34) Invalid sequence number
(35) Invalid format in image file
(36) Invalid image data
(37) Invalid address for memory contents
(38) Invalid image format
(39) Invalid transaction protocol (reported by bootstrap)
(40) Verification error
(41) Loaded application code is not valid, cannot be started
These error codes are communicated to allow specific action to be taken to repair any problem occurring in the system in a timely manner.
In
In
In
In
This application is a continuation of U.S. patent application Ser. No. 12/801,987 filed on 7 Jul. 2010 and claims the benefit of U.S. provisional patent application No. 61/213,752, filed on 10 Jul. 2009, the disclosures of which are incorporated herein by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
4884059 | Shapiro | Nov 1989 | A |
5121390 | Farrell et al. | Jun 1992 | A |
5721737 | Radjabi et al. | Feb 1998 | A |
5774111 | Lecland et al. | Jun 1998 | A |
5845268 | Moore | Dec 1998 | A |
5852411 | Jacobs et al. | Dec 1998 | A |
5910782 | Schmitt et al. | Jun 1999 | A |
6037880 | Manion | Mar 2000 | A |
6055581 | Berglund et al. | Apr 2000 | A |
6111522 | Hiltz | Aug 2000 | A |
6144927 | Grill et al. | Nov 2000 | A |
6147624 | Clapper | Nov 2000 | A |
6323785 | Nickell et al. | Nov 2001 | B1 |
6340935 | Hall | Jan 2002 | B1 |
6344806 | Katz | Feb 2002 | B1 |
6426708 | Trajkovic et al. | Jul 2002 | B1 |
6477539 | Smith | Nov 2002 | B1 |
6559776 | Katz | May 2003 | B2 |
6885311 | Howard et al. | Apr 2005 | B2 |
6927700 | Quinn | Aug 2005 | B1 |
6970101 | Squire | Nov 2005 | B1 |
7104447 | Lopez et al. | Sep 2006 | B1 |
7230535 | Jackson et al. | Jun 2007 | B2 |
7768426 | Groft | Aug 2010 | B2 |
7899583 | Mendelson | Mar 2011 | B2 |
8199001 | Verbil | Jun 2012 | B2 |
8306734 | Mathews | Nov 2012 | B2 |
8385840 | King | Feb 2013 | B2 |
8624756 | Ganot | Jan 2014 | B2 |
8671014 | Stefik et al. | Mar 2014 | B2 |
20020007291 | Miller | Jan 2002 | A1 |
20020109609 | Potter, Sr. | Aug 2002 | A1 |
20020111768 | Ghorayeb | Aug 2002 | A1 |
20020120728 | Braatz | Aug 2002 | A1 |
20020186662 | Tomassetti et al. | Dec 2002 | A1 |
20030132840 | Bahar | Jul 2003 | A1 |
20030146852 | O'Dell | Aug 2003 | A1 |
20040068434 | Kanekon | Apr 2004 | A1 |
20040094619 | Silberberg | May 2004 | A1 |
20040146070 | Blackmore et al. | Jul 2004 | A1 |
20040221196 | Datta | Nov 2004 | A1 |
20040252034 | Slemmer | Dec 2004 | A1 |
20050066119 | Azimi | Mar 2005 | A1 |
20050099320 | Nath et al. | May 2005 | A1 |
20050104723 | Mandy | May 2005 | A1 |
20050168352 | Tomer | Aug 2005 | A1 |
20060020487 | Spittel | Jan 2006 | A1 |
20060116892 | Grimes | Jun 2006 | A1 |
20060152349 | Ratnaker | Jul 2006 | A1 |
20060203709 | Laroia et al. | Sep 2006 | A1 |
20070061065 | Krikelis | Mar 2007 | A2 |
20070096943 | Arnold et al. | May 2007 | A1 |
20070171069 | Allen | Jul 2007 | A1 |
20070210935 | Yost | Sep 2007 | A1 |
20070285281 | Welch | Dec 2007 | A1 |
20070293157 | Haartsen et al. | Dec 2007 | A1 |
20070293232 | Nonaka | Dec 2007 | A1 |
20080066119 | Azimi | Mar 2008 | A1 |
20080127325 | Ebrom et al. | May 2008 | A1 |
20080165003 | Graichen et al. | Jul 2008 | A1 |
20080165030 | Kuo et al. | Jul 2008 | A1 |
20080231470 | Loli | Sep 2008 | A1 |
20080235082 | Zanotti | Sep 2008 | A1 |
20080238715 | Cheng et al. | Oct 2008 | A1 |
20080277468 | Mitschele | Nov 2008 | A1 |
20080287070 | King | Nov 2008 | A1 |
20080291054 | Groft | Nov 2008 | A1 |
20090086762 | Kugler | Apr 2009 | A1 |
20090109062 | An | Apr 2009 | A1 |
20090132070 | Ebrom et al. | May 2009 | A1 |
20090182868 | McFate et al. | Jul 2009 | A1 |
20090207003 | Brekke et al. | Aug 2009 | A1 |
20090231129 | Edwards et al. | Sep 2009 | A1 |
20090267732 | Chauvin | Oct 2009 | A1 |
20090309761 | Nagase | Dec 2009 | A1 |
20100026521 | Noel | Feb 2010 | A1 |
20100030708 | Ward | Feb 2010 | A1 |
20100191584 | Fraser | Jul 2010 | A1 |
20100328104 | Groft | Dec 2010 | A1 |
20110062230 | Ward, II | Mar 2011 | A1 |
20110099126 | Belani | Apr 2011 | A1 |
20110102197 | Herwich | May 2011 | A1 |
20110131154 | Faber | Jun 2011 | A1 |
20110133958 | Carboon | Jun 2011 | A1 |
20110140656 | Starr | Jun 2011 | A1 |
20110205087 | Kell et al. | Aug 2011 | A1 |
20110288895 | Perez, Jr. | Nov 2011 | A1 |
Number | Date | Country |
---|---|---|
2221770 | Aug 2010 | EP |
2278565 | Jan 2011 | EP |
20070060373 | Jun 2007 | KR |
2007027818 | Mar 2007 | WO |
Entry |
---|
Wikipedia. “Node (networking)” Wikimedia Foundation, Inc. Feb. 16, 2014. http://en.wikipedia.org/wiki/node_ (networking). |
Partial European Search Report, EP Application No. 10250201, dated Jun. 16, 2013. |
Rebeling Plastics, “Thermoplastics—Polycarbonate (LEXAN)”, accessed Mar. 23, 2015, published on or before Sep. 13, 2007, all pages pertinent, <https://web.archive.org/web/20070913190802/http://www.reblingplastics.com/ polycarbonate-lexan.htm>. |
Number | Date | Country | |
---|---|---|---|
20150213717 A1 | Jul 2015 | US |
Number | Date | Country | |
---|---|---|---|
61213752 | Jul 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12801987 | Jul 2010 | US |
Child | 14679610 | US |