|Publication number||US7509116 B2|
|Application number||US 11/095,878|
|Publication date||Mar 24, 2009|
|Filing date||Mar 30, 2005|
|Priority date||Mar 30, 2005|
|Also published as||US20060223516|
|Publication number||095878, 11095878, US 7509116 B2, US 7509116B2, US-B2-7509116, US7509116 B2, US7509116B2|
|Inventors||Rodric C. Fan, Edward David Mleczko, Sean Dominic Taylor|
|Original Assignee||Genx Mobile Incorporated|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (19), Referenced by (23), Classifications (40), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The invention relates generally to a system and method for mobile communication and particularly to a system and method for tracking statuses of mobile units.
Increasingly, industries rely on a fleet of dispatched mobile units to provide services or deliver products. For example, general contractors, utility providers, cable companies, appliance service providers, truck rental companies, taxi companies, airlines, police/fire departments, and various delivery services all utilize mobile units (e.g., vans, trucks, automobiles, airplanes) as part of their respective operations. When an operation involves numerous mobile units, it is often desirable, yet difficult, to obtain information about the dispatched mobile units. For example, it is desirable to know where the mobile units are at a given time. Also, the dispatching company may want to know if a mobile unit has been involved in an accident or if an employee driver is using the mobile unit in an inappropriate manner.
Locating a mobile unit is especially useful if it can be done from a remote management station, such as where the scheduling is done. This remote locating process usually entails two steps: determination of the position of the mobile unit, and transmission of the position data to the remote management station. One of the methods for determining the location of a mobile unit utilizes the Global Positioning System (GPS). The GPS involves a plurality of satellites orbiting the earth and sending out, at synchronized times, a code sequence that identifies the satellite. Along with this identification information is sent some positioning information that can be processed to determine a position. A GPS receiver receives the code sequence and the positioning information and passes it on to a processor. The processor determines the position of the GPS receiver by using well-known methods such as triangulation.
The position information as determined by the processor is then transmitted to a server that stores the information. Typically, this transmission from the GPS receiver to the server is achieved via a combination of wireless communication networks such as CDMA and the Internet. Further details of this system are provided in U.S. Pat. No. 5,959,577 (“the '577 patent).
While the system of the '577 patent accomplishes the goal of allowing remote management stations to obtain information about mobile units, it has several drawbacks that make the system unappealing to clients. One of the drawbacks is the lack of flexibility in changing the reporting patterns of the mobile units. The system of the '577 patent provides four modes in which the mobile units can operate, and the mode selection affects how often the mobile unit updates its position information. There is no mention in the '577 patent as to whether a single mobile unit always operates in the same mode or the mode is changeable. Thus, if the fleet management operator decides that he wants to see more frequent updates after the mobile units are dispatched, there is no way for the operator to change the update frequency.
Another drawback is the lack of scalability. Since the central server receives all the information collected by the mobile units and maintains a record of them, the amount of data that is stored becomes very large very fast. Given that each additional mobile unit takes up a lot of space in the database, it is difficult to add many mobile units to the system at once. If a company with a large fleet signs up for the system, the additional burden could cause the system to crash.
A system and method of providing mobile unit information (e.g., position information) in a more flexible and user-friendly manner is desired.
In one aspect, the invention is a system for collecting data from a remote mobile unit. The system includes a configuration database containing a plurality of configuration files, each configuration file containing a configuration parameter that dictates a data reporting pattern. The mobile unit collects data and wirelessly accesses the configuration database to determine how to report the collected data before transmitting the data according to the configuration parameter.
In another aspect, the invention is a method of locating a mobile unit. The method includes determining an identification number of the mobile unit upon being contacted by the mobile unit through a data network, and locating a configuration file that is assigned to the identification number. The configuration file contains parameters that dictate how the mobile unit transmits its position data over the data network.
In yet another aspect, the invention is a mobile device that includes a global positioning system (GPS) receiver for receiving position data and a wireless transmitter for connecting to a data network. The wireless transmitter obtains a configuration parameter via the data network upon being powered up, and transmits position data to the data network according to the configuration parameter.
Embodiments of the invention are described herein in the context of vehicle-installed devices and more specifically in the context of fleet management. However, it is to be understood that the embodiments provided herein are just preferred embodiments, and the scope of the invention is not limited to the applications or the embodiments disclosed herein.
As used herein, “position data” are data indicating a mobile unit's position, and may be in the form that needs some processing to be meaningful to computer 16 or a form that is already meaningful to the computer 16. A “computer,” as used herein, is a commercially available device that has a processor, a memory, and a user interface, including a server. In the embodiments disclosed herein, the computer also has a means for communicating with the data network. A “configuration parameter” tells the mobile unit how often to transmit a certain type of data.
In the system of the invention, the distributed mobile units are initially all the same. These “generic” mobile units, which initially contain the same information, are configured to collect certain data (e.g., position data) and, upon first being powered-on, to contact the service provider's computer. The service provider's computer checks the identification number of the mobile unit that contacted it, and identifies the location of a configuration file that is specifically created for the contacting mobile unit. The service provider then directs the contacting mobile unit to the location of the configuration file. Each mobile unit is assigned to at least one configuration file. There is, however, no limit to the number of mobile units a configuration file applies to, and sometimes, a configuration file may not apply to any mobile unit. For example, in one instance involving 200 mobile units and three configuration files, the first configuration file may apply to 100 mobile units, the second configuration file may apply to 70 mobile units, and the third one may apply to 30 mobile units.
The configuration parameters in the configuration files are changeable, for example by the service provider. The system of the invention makes the change process easy to implement because the service provider only needs to change one configuration file to affect the reporting patterns of multiple mobile units. For example, by changing just the first configuration file in the above example, 100 mobile units will be affected.
The mobile units can be regrouped fairly easily as well. The service provider's computer may maintain a table of configuration file assignments indexed by mobile unit identification number. By changing the configuration file that is assigned to a specific mobile unit in the table, the mobile unit is effectively moved to a different group covered by a different configuration file. In the above example involving 200 mobile units, for example, changing the configuration file assignments for 10 mobile units could make the first configuration file apply to 90 mobile units, the second configuration file apply to 75 mobile units, and the third file apply to 35 mobile units. Thus, the reporting patterns of the mobile units can be altered efficiently at the service provider's computer.
In some embodiments, the configuration files are arranged in layers to provide more flexibility in regrouping the mobile units. Where there are, for example, three layers of files, a mobile unit may pull its configuration parameters from a file in each of the three layers. Another mobile unit may pull its configuration parameters from only two of the three layers because the operator did not want the third configuration file to apply to this mobile unit. Yet another mobile unit may pull its configuration parameters from all three layers, but use a different file than the other mobile unit in one of the layers. The number of possible permutations with parameter combinations is large, and can be controlled by the number of layers and the numbers of files per layer. The layers can contain different numbers of files. Configuration files may be deleted and created.
The service provider usually controls the configuration files. However, in some cases, the client (e.g., delivery service company) who has an account with the service provider may be able to directly control the configuration files with the service provider's permission.
Details of the invention will now be described in reference to the Figures.
When a client first opens an account with the service provider, the service provider creates a configuration file assignment table that contains all the mobile units that the client wants to monitor. The configuration table is indexed by mobile unit identification number, so that the service provider can match up a mobile unit 12 with the proper configuration that the client intended for that particular mobile unit 12. The client may decide that they want certain reporting patterns from different mobile units depending on the nature of the delivery, geographic location, weather conditions, driver reputation, etc.
As shown in
Preferably, the mobile unit 12 processes the collected data so that the data is already in a format that is meaningful to the computer 16 when the data is transmitted. However, in some cases, the mobile unit 12 sends “raw” data that needs processing and the computer 16 processes the received data. The mobile unit 12 time-stamps the data it transmits to the computer 16. Thus, for example, the computer 16 may determine the speed of a mobile unit by using the time stamp (speed=distance traveled divided by the time it took to travel the distance).
The configuration files may be arranged in multiple layers, as illustrated in the example of
Layer 2 contains a plurality of configuration files that are classified according to county lines. Layer 2, thus, would have many more configuration files than Layer 1 in this example. Each county-specific configuration file may contain, for example, landmarks and planned routes. Landmarks are physical locations that the client company considers as denoting a significant geographical location, and maybe something as large as Golden Gate Park or something as specific as San Francisco City Hall. “Planned routes” are routes that are planned either by the service provider or the client when the delivery is scheduled, based on the starting point and the destination. The configuration file may include a command to send an alert to the computer 16 and/or the monitoring station 22 if there is a significant deviation from the planned route. The county-specific configuration files may also include a command to send an alert if a mobile unit approaches a county line, so that the mobile unit can be regrouped and a different configuration file (either must in Layer 2 or in both Layer 1 and Layer 2) can be assigned.
Layer 3 may contain a plurality of configuration files classified according to vehicle type. For example, there may be Class A trucks that travel interstate, Class B trucks that stay within a state's boundaries, and Class C trucks that carry perishable goods. The configuration file for Class C mobile units may include an instruction to send an alert if 5 hours have passed since the mobile unit was initialized and the truck is not yet at the destination. On the other hand, the configuration file for Class A mobile units might include an instruction to send an alert to the client if it has been more than 48 hours since initialization and the truck has not reached the destination. In this case, the driver of the delivery trucks would be instructed to initialize the mobile unit when the cargo is unloaded. Upon seeing an alert, an operator monitoring the mobile units at the monitoring station 22 may attempt to contact the driver to see what is happening.
Suppose there is an exemplary Class A delivery truck that is being dispatched from Nevada to make a delivery in Santa Clara County, California. The driver of the truck would turn on the mobile unit when he loads up the truck and is ready to begin driving. The mobile unit then automatically communicates with the computer 16 to continually exchange data that will be turned into a report for the delivery company (i.e., the client at the monitoring station 22). The mobile unit 12 collects data according to the preprogrammed instructions. However, the mobile unit does not transmit all the collected data to the computer 16. Rather, the mobile unit selectively transmits the type of data that is requested by the configuration files according to the configuration parameters, which reflect the information that the client is interested in tracking. Applying the configuration file layers of
The multi-layer structure of the configuration files imparts flexibility to the client control of mobile units. For example, if there is a storm in three counties in California, the client can go into Layer 2 of the configuration files and include a command to issue an alert if the speed exceeds 55 mph. This command will override the generic 75 mph alert limit set in the Layer 1 configuration file, but only for the three affected counties. Thus, the 75 mph limit would still apply to trucks in all the other counties. When the storm clears up, the client can go into Layer 2 and delete this restriction. The same configuration can be applied to multiple mobile units with one entry, instead of reconfiguring each mobile unit separately.
There is no limit to the number of layers that can be incorporated into a configuration file, or to how many classes there can be in a layer. Layers may be added or removed. A person of ordinary skill in the art will appreciate that this layered structure of the configuration files can be exploited to cluster the mobile units as broadly or as specifically as is suitable to a client's needs. At the most specific level, there could be a configuration layer that is specific to a mobile unit identification number.
After the very first power-on, which is programmed to trigger an initialization process whereby the mobile unit 12 contacts the computer 16, the configuration files may be used to control the manner in which the initialization process is triggered. When a mobile unit 12 is powered on for the very first time, it is preprogrammed to contact the computer 16 to obtain the configuration parameters that are specifically intended for it. If the configuration file includes a command to re-initialize at 7 a.m. daily, the mobile unit will re-read its configuration file(s) at 7 a.m. everyday after the very first initialization. If the mobile unit is not turned on at 7 a.m., it may automatically turn on and re-initialize. The initialization may also be performed in response to a manual command from the client or the truck driver. This manual initialization option is handy for unexpected situations, for example if the truck battery died and the mobile unit could not operate for a while. When the battery is replaced, the driver can manually initialize the mobile unit 12. In some cases, the mobile unit 12 is programmed to automatically initialize after a hardware repair.
The initialization parameter in the configuration files may be set with a timer. The timer function is useful if a client wants its mobile units all across the country to download their configurations at the same time so that there won't be different groups of trucks acting according to different configurations. The mobile units 12 could download the new configuration parameters with the timer data (which would be part of the configuration file). In this case, the mobile units will download the configuration files but not activate or use them until the time indicated by the timer. This timer function helps synchronize the mobile units 12 so that they act consistently according to the same configuration files regardless of what time they were last initialized. The timer function can also be used to activate different groups of mobile units 12 sequentially according to a predetermined order.
Some embodiments of system 10 allow there to be multiple versions of one configuration file. Different versions may have different fields or different parameter values. For example, there may be a version for rainy days, a version for foggy/snowy days, and a version for sunny days. This way, the client can designate the version that applies depending on the weather conditions of the relevant region.
The memory at the computer 16 may store geographical parameters, communication parameters, and device operations, among other data. Geographical parameters include maps, landmarks (e.g., the Civic Center) and boundaries (zip code, state/county/city lines). In some cases, there is an electronic map stored at the computer 16 on which x-vertice polygons are used to divide the country into sub-areas according to a suitable parameter (e.g., crime rate). Planned routes, mentioned above, may also be part of geographical parameters. These geographical parameters may be combined with reported data to produce reports in the client-requested format.
Typically, the service provider controls and maintains the configuration database 20, and sends reports to its client for some type of fee arrangement. However, in some cases, the client may directly control the service provider. Where the client directly changes the configuration database, the configurations are preferably in a human-readable form so that no special training is needed for changing the configuration parameters. For example, someone may be able to reset the frequency at which a mobile unit reports its location by typing “position report period=2 minutes.”
Where the client is allowed to directly change the configuration parameters, a licensing key may be issued by the server station 16 to the client to maintain control over the client's usage of the system.
The detection components 32 include various probes, sensors, and thermometers connected to different parts of the vehicle, such as the speedometer, the rods, the latch at the door, etc. A person of ordinary skill in the art will know which probes/sensors to use and how to connect the probes/sensors to the processor 34 to implement the detection components 32. The detection components 32 take measurements periodically, in response to a signal from the processor 34. The mobile unit 12 also includes a GPS receiver 38 for receiving position data from a GPS satellite system (not shown). The wireless modem 30 is then used to forward the received position data to the computer 16.
The embodiment of the mobile unit 12 that is depicted in
If desired, encryption may be used for data transmission.
Although preferred embodiments of the present invention have been described in detail hereinabove, it should be clearly understood that many variations and/or modifications of the basic inventive concepts herein taught which may appear to those skilled in the present art will still fall within the spirit and scope of the present invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5295261 *||Jul 27, 1990||Mar 15, 1994||Pacific Bell Corporation||Hybrid database structure linking navigational fields having a hierarchial database structure to informational fields having a relational database structure|
|US5748104 *||Jul 11, 1996||May 5, 1998||Qualcomm Incorporated||Wireless remote telemetry system|
|US5917911 *||Jan 23, 1997||Jun 29, 1999||Motorola, Inc.||Method and system for hierarchical key access and recovery|
|US5953722 *||Sep 5, 1997||Sep 14, 1999||Navigation Technologies Corporation||Method and system for forming and using geographic data|
|US5959577 *||Aug 28, 1997||Sep 28, 1999||Vectorlink, Inc.||Method and structure for distribution of travel information using network|
|US6292657 *||Jul 13, 1998||Sep 18, 2001||Openwave Systems Inc.||Method and architecture for managing a fleet of mobile stations over wireless data networks|
|US6522876 *||Oct 4, 1999||Feb 18, 2003||Sprint Spectrum L.P.||System for managing telecommunications services through use of customized profile management codes|
|US6611739 *||Nov 28, 2000||Aug 26, 2003||New Flyer Industries||System and method for remote bus diagnosis and control|
|US6658562 *||Aug 25, 2000||Dec 2, 2003||International Business Machines Corporation||Method, system, and program for customizing a basic input/output system (“BIOS”) configuration according to the type of user|
|US6662014 *||Feb 4, 2000||Dec 9, 2003||Sbc Properties, L.P.||Location privacy manager for a wireless communication device and method therefor|
|US6757719 *||Apr 28, 2000||Jun 29, 2004||Charmed.Com, Inc.||Method and system for data transmission between wearable devices or from wearable devices to portal|
|US6895240 *||Jul 16, 2001||May 17, 2005||Openwave Systems Inc.||Method and architecture for managing a fleet of mobile stations over wireless data networks|
|US7027808 *||May 21, 2003||Apr 11, 2006||Philip Bernard Wesby||System and method for monitoring and control of wireless modules linked to assets|
|US20010025280 *||Feb 28, 2001||Sep 27, 2001||Davide Mandato||Management of user profile data|
|US20020061754 *||Nov 14, 2001||May 23, 2002||Nec Corporation||Mobile communication terminal and operation control system thereof|
|US20020112052 *||Feb 13, 2001||Aug 15, 2002||Peter Brittingham||Remote computer capabilities querying and certification|
|US20040162063 *||Feb 18, 2003||Aug 19, 2004||Quinones Luis F.||Method and apparatus for conditioning access for a remotely-accessible device|
|US20060007870 *||Jul 5, 2005||Jan 12, 2006||Steve Roskowski||Collection of data at target wireless devices using data collection profiles|
|US20060223495 *||Mar 13, 2006||Oct 5, 2006||Cassett Tia M||Method and apparatus for monitoring usage patterns of a wireless device|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7817994 *||Sep 20, 2004||Oct 19, 2010||Robert Bosch Gmbh||Secure control of wireless sensor network via the internet|
|US7925249||Oct 6, 2010||Apr 12, 2011||Robert Bosch Gmbh||Secure control of a wireless sensor network via the internet|
|US8149113||Apr 22, 2009||Apr 3, 2012||Darrell Diem||Apparatus and method for conveying location event information based on access codes|
|US8223012||Apr 2, 2012||Jul 17, 2012||Geofence Data Access Controls Llc||System and method for conveying object location information|
|US8370054 *||Mar 24, 2005||Feb 5, 2013||Google Inc.||User location driven identification of service vehicles|
|US8493207||Jul 17, 2012||Jul 23, 2013||Geofence Data Access Controls Llc||Location information sharing system and method for conveying location information based on user authorization|
|US8717166||Jul 23, 2013||May 6, 2014||Geofence Data Access Controls Llc||System and method for conveying location information via a plurality of information-sharing environments|
|US9003499||May 6, 2014||Apr 7, 2015||Geofence Data Access Controls Llc||System and method for conveying event information based on varying levels of administrative privilege under multiple levels of access controls|
|US9047359 *||Feb 1, 2007||Jun 2, 2015||Hand Held Products, Inc.||Apparatus and methods for monitoring one or more portable data terminals|
|US9071931||Feb 12, 2015||Jun 30, 2015||Perdiemco Llc||Location tracking system with interfaces for setting group zones, events and alerts based on multiple levels of administrative privileges|
|US9119033||Feb 23, 2015||Aug 25, 2015||Perdiemco Llc||System for sharing information about groups of individuals, drivers, vehicles or objects|
|US9319471||Feb 23, 2015||Apr 19, 2016||Perdiemco Llc||Object location tracking system based on relative coordinate systems using proximity location information sources|
|US9485314||Feb 23, 2015||Nov 1, 2016||Perdiemco Llc||Multi-level privilege notification system operated based on indoor location information received from a location information sources|
|US20060062201 *||Sep 20, 2004||Mar 23, 2006||Karsten Funk||Secure control of wireless sensor network via the internet|
|US20060217885 *||Mar 24, 2005||Sep 28, 2006||Mark Crady||User location driven identification of service vehicles|
|US20070234427 *||Mar 20, 2007||Oct 4, 2007||Absolute Software Corporation||Method for determining identification of an electronic device|
|US20080132223 *||Aug 30, 2007||Jun 5, 2008||Chun-Fu Lin||Systems and methods for providing traffic information|
|US20080185432 *||Feb 1, 2007||Aug 7, 2008||Caballero Aldo M||Apparatus and methods for monitoring one or more portable data terminals|
|US20080235806 *||Jun 2, 2008||Sep 25, 2008||International Business Machines Corporation||Methods and Apparatus for Implementing Context-Dependent File Security|
|US20090207015 *||Apr 22, 2009||Aug 20, 2009||Robert S. Babayi||System and method for defining an event based on a relationship between an object location and a user-defined zone|
|US20100073187 *||Sep 22, 2008||Mar 25, 2010||Symbol Technologies, Inc.||Methods and apparatus for no-touch initial product deployment|
|US20150261643 *||May 29, 2015||Sep 17, 2015||Hand Held Products, Inc.||Apparatus and methods for monitoring one or more portable data terminals|
|WO2011098661A1 *||Dec 30, 2010||Aug 18, 2011||Nokia Corporation||Method and apparatus for providing utilization of data profiling for radio resource management|
|U.S. Classification||455/405, 370/252, 709/219, 455/456.2, 380/286, 455/411, 455/420, 455/456.1, 455/419, 340/870.11, 707/999.002, 707/999.1, 342/357.57, 701/31.4, 701/32.7|
|International Classification||H04W24/00, H04M1/66, H04W8/20, H04M3/00, H04M1/68, H04M11/00, H04M3/16, G01S19/19|
|Cooperative Classification||Y10S707/99932, Y02B90/246, Y04S20/42, H04Q9/00, Y04S20/325, H04M2242/30, H04W8/20, Y02B90/243, G01D4/006, H04L67/34, H04L67/04, H04L67/303|
|European Classification||H04Q9/00, H04L29/08N29T, G01D4/00R2, H04L29/08N3, H04L29/08N33|
|Mar 30, 2005||AS||Assignment|
Owner name: GENX MOBILE INCORPORATED, A DELAWARE CORPORATION,
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FAN, RODRIC C.;MIECZKO, EDWARD D.;TAYLOR, SEAN D.;REEL/FRAME:016449/0958;SIGNING DATES FROM 20050324 TO 20050330
|Sep 10, 2012||FPAY||Fee payment|
Year of fee payment: 4
|Sep 23, 2016||FPAY||Fee payment|
Year of fee payment: 8