WO1999045519A2 - Systeme et procede de gestion de parc automobile - Google Patents

Systeme et procede de gestion de parc automobile Download PDF

Info

Publication number
WO1999045519A2
WO1999045519A2 PCT/US1999/004931 US9904931W WO9945519A2 WO 1999045519 A2 WO1999045519 A2 WO 1999045519A2 US 9904931 W US9904931 W US 9904931W WO 9945519 A2 WO9945519 A2 WO 9945519A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
user
mobile
mdt
information
Prior art date
Application number
PCT/US1999/004931
Other languages
English (en)
Other versions
WO1999045519A3 (fr
Inventor
Sanjiv Prabhakaran
Original Assignee
Mobile Information System, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mobile Information System, Inc. filed Critical Mobile Information System, Inc.
Priority to AU28987/99A priority Critical patent/AU2898799A/en
Publication of WO1999045519A2 publication Critical patent/WO1999045519A2/fr
Publication of WO1999045519A3 publication Critical patent/WO1999045519A3/fr

Links

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/123—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams
    • G08G1/127—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams to a central station ; Indicators in a central station

Definitions

  • the present invention relates to an apparatus and system for data processing and, more specifically, data processing as it relates to transportation management.
  • the present invention is illustrated by way of an example with regard to a system for fleet management using an apparatus and method capable of remotely transmitting and receiving information from a base station. But it will be recognized transmitting and receiving information from a base station. But it will be recognized that the invention has a wider range of applicability.
  • the invention can be applied to other types of transportation, mapping, information management, and the like. As the world becomes more industrialized and populated, transportation requirements also increase rapidly.
  • Mobile Information Systems are systems that pioneered a technique for implementing easy-to-read maps for tracking vehicle location on a display or workstation at the central office terminal or any other terminal.
  • Mobile Information Systems implemented one of the first techniques for using a raster-type map and vector data for referencing vehicle location.
  • the raster-type map used on a display had features that were easy-to-read for a dispatcher or user. These features were generally geographical in nature and were easier to reference than the maps predominantly made using stick-type representations of geographical features.
  • the techniques used by Mobile Information Systems have partly overcome some of the daily problems faced by a fleet manager or the like. It would, however, be desirable to develop other techniques for integrating further aspects of fleet management.
  • the invention provides a technique for fleet management in a flexible way to process data at a remote location such that a user may conveniently enter and transfer data and also have ready access to powerful data processing.
  • the present technique can be used in a variety of applications such as transportation and the like.
  • the present invention provides a system for fleet management having an improved interface unit at a user location.
  • the system also has, among many features, a graphical interface user apparatus having a display and user interface such as a keyboard.
  • the fleet management system further has an information center, which provides vehicle position data and the like. This vehicle position data are received and transmitted to a fleet of vehicles (e.g. , couriers) through the mobile information center.
  • the vehicle position data are received and transmitted from a novel interface unit (e.g., hand-held unit, mobile data terminal, personal information manager, commonly known as PLM or the like).
  • the interface unit includes, among a variety of features, a processor, e.g., microprocessor, digital signal processor, microcomputer.
  • a positioning system e.g., GPS
  • a remote data terminal electrically couples to the interface unit during at least a first time period.
  • the remote data terminal is capable of data transfers with the interface unit during the first time period and with a user in the vehicle. This system allows a user to take the remote data terminal on errands away from the interface unit, and transfer data to and from the interface unit.
  • the information center is operably coupled to the interface unit.
  • the remote data terminal is adapted to be hand-held. This allows the user to carry the remote data terminal on errands. Thus, the user can enter data conveniently in real-time when the user receives data. This, for example, allows the user to avoid writing the data onto paper only to be entered electronically later.
  • the present invention provides a method of data processing including receiving user data in a control unit, receiving positioning data from a first antenna of the control unit, and transmitting the user data and the positioning data, using a second antenna of the control unit, to a base station.
  • This embodiment provides a method by which user data may be combined with positioning data thereby providing an indication of not only the substance but also the origin of the user data.
  • the present invention provides a microprocessor based system using a novel set of instructions or computer codes.
  • the computer codes form a computer program (e.g., software) to carry out the functionality and methods described herein.
  • the functionality and methods are described throughout the present specification and more particularly below.
  • This invention provides myriad advantages. For example, quick access could be gained to valuable information such as the user's current location, speed, direction, destination, schedule, estimated time to destination, and required time to destination in some embodiments.
  • the present invention can also store and transmit precise tracking information regarding the user's past, present, and future positions and locations at noteworthy times such as when the user reaches certain destinations including pickup and delivery points in other embodiments.
  • the present invention can, for example, improve user efficiency b reducing the time and cost of travel between destinations while providing improved tracking of the user, packages, or the like.
  • the present invention can provide accurate location and tracking information automatically, without requiring the user to enter this information which may require additional time or introduce human error. Also, the present invention may provide these and other advantages in a convenient and portable package.
  • At least one, of not all, of these advantages are integrated into an easy to use fleet management system for controlling and/or tracking a fleet of movable items, e.g., vehicles, planes, trucks, people, boats, golf carts, trains.
  • movable items e.g., vehicles, planes, trucks, people, boats, golf carts, trains.
  • the present invention provides other advantages.
  • the description provided here is only exemplary and not an exhaustive list.
  • FIG. 1 is a simplified diagram of a display according to the present invention.
  • Figs. 2-5 are simplified diagrams of fleet management systems according to embodiments of the present invention
  • Figs. 6-15 are simplified diagrams of one or more data processing systems according to embodiments of the present invention.
  • Fig. 1 illustrates an integrated raster map display according to an embodiment of the present invention.
  • the raster map 510 includes natural features such as marshlands 512, creeks 514, and the like.
  • the raster map 510 also includes manmade features such as the Auto Assembly Plant 516, Agnews Hospital 518, and others.
  • the raster map is, for example, a digitally scanned road map, a digitally scanned automobile road map, a raster image in digital form, a preexisting digital map without intelligent information, a digital map in TIFF format, a digitized video image, a digitized satellite image, or the like.
  • the raster map can also generally be almost any type of digital map with substantially clear features without intelligent street information or the like.
  • Icons 520 show the position of the vehicles identified in the vector information table 528.
  • the icons can also represent any mobile entities such as automobiles, vans, trucks, ambulances, animals, people, boats, ships, motorcycles, bicycles, tractors, moving equipment, trains, courier services, container ships, shipping containers, airplanes, public utility vehicles, telephone company vehicles, taxi cabs, buses, milk delivery vehicles, golf carts, beverage delivery vehicles, fire trucks and vehicles, hazardous waste transportation vehicles, chemical transportation vehicles, long haul trucks, local haul trucks, emergency vehicles, and the like.
  • the icons can represent any mobile or potentially mobile entity or the like.
  • the vector information table 528 indicates selected geographic and cartographic information retrieved from, for example, the vector database.
  • the vector information table 528 provides intelligent street information such as block number, address information, nearest cross-section of major streets, and the like with reference to the vehicle position.
  • the vector table can also provide information about vehicle speed, vehicle heading, an activity status, a time status, and the like.
  • the display shown in Fig. 1 can be divided into at least two regions or segments such as a raster display segment 530, a vector information display segment 532, and others.
  • the raster display segment 530 includes a first and second axis 534, 536 representing the latitudinal and longitudinal position of the vehicle position, respectively.
  • the raster display segment may be in cylindrical or polar coordinates, and may not be limited to two dimensions.
  • a digitized map of the region through which the vehicle travels is displayed in the first segment of the display 530, adjacent to the first and second axis 534, 536.
  • each vehicle is represented as an icon.
  • the icons may be color coded relative to a status chart and the like. Of course, the shape and color of each icon depend upon the particular application.
  • the display segments can be in the form of one or more "windows" that are commonly used in graphical user interfaces.
  • the window can have either vector or graphical information, or a combination of vector and graphical information.
  • the windows can be disposed along an edge of the display or in the center of the display. Furthermore, the windows can be moved from any location on the display for easier reading and referencing.
  • the present display can include addition features such as those discussed in U.S. Serial
  • Fig. 2 illustrates a block diagram of the fleet tracking system 600 for automatic vehicle location according to the present invention.
  • Each vehicle 610a-610n includes a navigational tracking device hereafter called a fleet mobile data suite (MDS) 611a-611n.
  • the fleet MDS 611 includes a microprocessor-controlled circuit 700 coupled to a GPS navigational sensor 702. a mobile radio modem 704, and a specialized mobile radio (SMR) 706 operational in the 800-900 Mhz frequency range, as illustrated by Fig. 3.
  • the fleet MDS 611 continuously compiles latitude and longitude position data from the GPS sensor. Latitude and longitude position data is periodically transmitted to the data acquisition system 612.
  • the mobile position block 616 processes vehicle location information typically on a UNIX based computer.
  • Other computer such as Windows NT, DOS, MacOs, etc. based computer, for example, are also contemplated for alternative embodiments of the present invention.
  • the mobile position block 616 includes a data acquisition system 612, a mobile position database 614, a UNIX process
  • the data acquisition system 612 includes a personal computer coupled to both a base data link controller, and a specialized mobile radio (SMR) operational in the 800-900 Mhz frequency range, but is not limited to this radio. Cellular telephones, wireless "totem pole" communication, pagers, and other wireless communication techniques can also be used.
  • SMR specialized mobile radio
  • the data acquisition system 612 receives latitude and longitude position data from the fleet MDS 611 , attaches a vehicle identifier to the navigational position data, and transmits the data block 613 (e.g., vehicle identification, latitude, longitude) to the mobile position database 614.
  • Vehicle position is defined in terms of a latitude and longitude value during a predetermined time period.
  • the UNIX process DBFUPDATE 618 scans the mobile position database 614, preferably every 5 seconds, for any new information from the fleet MDS.
  • the new data 620 is permanently stored in the disk database 622 for subsequent retrieval of historical information.
  • Another UNIX process DBREQSRV 624 processes requests by the user from the mobile tracking station 626 for navigational position information.
  • the mobile tracking station 626 can be a high resolution color UNIX workstation.
  • User requests 628 are originated by mobile information data process 630, a UNIX process running on the mobile tracking station 626.
  • the mobile information data process 630 receives latitude and longitude position data for a ⁇ articular vehicle.
  • the mobile information data process 630 accesses the vector database 631 using the vector utilities 632.
  • the vector utilities 632 match the latitude and longitude position information 634 to the latitude and longitude of street segment information 636 from the vector database 631.
  • the vector utilities 632 match the latitude and longitude position information 634 to the latitude and longitude information of the cross-section of major streets 636 in the cross-section vector database 638.
  • the cross-section vector database 638 can be a subsection of the vector database 631.
  • the nearest matching street segment, its street name and block number range, and the nearest cross-section of major streets, and its street name 640 are transmitted to the mobile information data process 630.
  • the mobile information data process 630 attaches the street text information to the mobile position information and sends this data packet 642 to the fleet process 644.
  • the fleet process 644, a UNIX based process or the like, is the user interface display process.
  • the fleet process 644 receives mobile position information and street text information from the mobile information data process 630.
  • the fleet process 644 accesses the raster database 645 through the raster map utilities 646.
  • the raster map utilities 646 match the latitude and longitude mobile position 648 from the fleet MDS 611 to the various digitized raster maps data 650 in the raster map database 645.
  • the zoom level option using as an example, the Xll/Motif graphical user interface on the mobile tracking station 626, the digitized raster map is displayed in one display window segment 530 and the corresponding street text information on another display window segment 532.
  • a user locatable mark 520 represents the fleet MDS position for a particular vehicle. The icon 520 is positioned at the corresponding latitude and longitude location on the raster map display 530.
  • Historical data requests may be made by specifying a particular time period and a particular fleet MDS 611.
  • the data request is sent by the fleet process 644 to the mobile information data process 630.
  • the mobile information data (MID) process 630 in turn sends a request 628 to the DBRQSRV 624 process.
  • the DBRQSRV 624 process accesses the disk database 622 and retrieves reports for the specific time period and fleet MDS 611. For every historical report sent back to the MID process 630, the above described process flow for accessing and displaying the raster map, vector street information, and displaying the user locatable mark representing the position of the navigational system is followed.
  • the vehicle display system includes at least three databases (a mobile position database 614, a raster database 645 and a vector database 631).
  • the database information is interrelated by common latitude and longitude position data.
  • a mobile tracking station 626 displays the position, raster and vector information in a format easily understood by the dispatcher or fleet manager.
  • the first database, the mobile position database 614 is a positional information database for storing vehicle position information received from the navigation systems .
  • Navigational data transmitted from systems such as LORAN and GPS (Global Positioning System) is stored into data records indicating the latitude and longitude of a particular vehicle during a predetermined time interval.
  • the DAQ process 612 is used to format position data received from the navigational system into the mobile position database 614.
  • the vehicle identification is used as locator field to access the database for a particular vehicle.
  • Vehicle position data is stored related to the vehicle identifier.
  • the second database, the raster database 645 is generated by digitally scanning a standard road map or paper map.
  • the raster database 645 contains a digitized version of the visual features of the land for a specified region. Digitized raster information is stored in the raster database 645 in data records. Each data record corresponds to a digitized region having a particular latitude and longitude value. The latitude and longitude values are used as a locator field for accessing the raster database 645.
  • Data from both the raster database 645 and the mobile position database 614 are used in displaying the raster map and icon 520 in the first segment 530 of the display shown in Fig. 5.
  • the fleet process 644 in combination with the raster map utilities 646, MID process 630, and vector map utilities 632 contains routines to access the mobile position database 614 and the raster map database 612.
  • Both the mobile position database 614 and the raster map database 645 include a latitude and longitude field identifier.
  • the raster map utility 646 in combination with the fleet process 644 and MID 630 matches the longitude and latitude values from the mobile position database 614 and the raster map database 645 and displays an icon 520 (representative of a particular vehicle) moving along the raster map as it changes its latitude and longitude position.
  • the icon 520 moves according to the navigational data extracted from the mobile position database 614 for a particular vehicle.
  • the icon 520 is also displayed in the first display segment 530. Since the latitude and longitudinal position of the icon 520 corresponds to a street location, the icon 520 moves along a particular street on the raster map display 530.
  • a third database, the vector database 631, is needed to provide intelligent street information.
  • Vector address data and street information is publicly available from the US Census Bureau.
  • the US Census provides GBF/DIME (Geographic Base Files/Dual Independent Map Encoding) files which are a common source of address data for dispatching applications. These files contain information describing the street network and other features. Each field record contains the segment name, address range and ZIP code. Node numbers for intersections are referenced to the vehicle latitude and longitude coordinate position.
  • a third database the vector database 631 contains vector information provided from GBF/DIME files.
  • Vector information is displayed in the second display segment 532.
  • the vector information displayed in segment 532 is typically displayed as text and relates intelligent street information corresponding to the latitude and longitude of a particular vehicle.
  • Display segment 532 of Fig. 5 represents the vector text information.
  • the MID process 630 contains routines to access the mobile position database 614. Both the mobile position database 614 and the vector map database include a latitude and longitude field identifier.
  • the vector utility 632 in combination with the MID process 630 contains routines to extract block number, street name, cross-section of major streets and other address related information and to match the longitude and latitude values from the mobile position database 614 to the vector map database 632.
  • the mobile tracking station 626 displays the vehicle position on a raster map and corresponding address information simultaneously .
  • the steps for display of the integrated system include defining a coordinate system having a first axis representing the latitude of the vehicle position and a second axis representing the longitude of the vehicle position. Digitized information representative of a raster map is extracted from the raster database 645 and displayed adjacent to the first and second axes to form a raster map of a first predefined area. Mobile position data from the GPS navigation system corresponding to vehicle latitude and longitude position during a predetermined time interval is extracted from the mobile position database 614. A user locatable mark 520 in the first display segment 530 corresponding to the latitude and longitude of the vehicle position is displayed. Intelligent street information is extracted from a third database, the vector database 631. Vector text information is displayed in a second segment 532 of the display. The vector text information corresponds to the latitude and longitude of the user locatable mark 520.
  • Fig. 4 illustrates a simplified block diagram 800 of an integrated raster map display and information display according to an alternative embodiment of the present invention.
  • the block diagram is merely a simplified illustration and should not limit the scope of the claims as defined herein.
  • the block diagram provides functions for accessing mobile information center (MIC) databases and servers to handle sub-systems such as an automatic vehicle location (AVL) system, a two-way messaging (TWM) system, a computer aided dispatch (CAD) system, and others.
  • the simplified block diagram includes fleet mobile units 610, a mobile information center (MIC) 802, a mobile tracking system-mobile information center link (MTS- MIC LINK) 804, a mobile tracking system 806, among other features.
  • MIC mobile information center
  • TWM two-way messaging
  • CAD computer aided dispatch
  • the mobile tracking system 806 includes system elements such as a mobile tracking station 626. a fleet process 644, a computer aided dispatch system 811, a mobile information data menu (MIDMENU) 821, a mobile information data main process (MIDMAIN) 823, and other elements.
  • the mobile tracking system provides functions similar to the previous embodiment, but also has the computer aided dispatch system 811 and other elements.
  • Selected system elements from the previous embodiment such as the mobile information data process 630, raster utility library 646, raster database 645, vector database 631, vector utility library 632 are combined within the MIDMENU & MIDMAIN 821, 823 process (hereinafter collectively "MIDMAIN").
  • a UNIX process such as the DBREQSRV 624 processes requests by a user from the mobile tracking station 626 for navigational position information.
  • the mobile tracking station 626 can be any suitable high resolution color UNIX workstation or the like.
  • User requests 628 originate at the MIDMAIN 821, 823 process which is a UNIX process running on the mobile tracking station 626.
  • the MIDMAIN 821, 823 process receives latitude and longitude position data for a selected mobile unit MDS-1 to MDS-n via line represented as 629.
  • the MIDMAIN 821. 823 process accesses the vector database (or memory) 631 using the vector utilities.
  • the vector utilities match the latitude and longitude position information to the latitude and longitude of street segment information from the vector database.
  • the vector utilities also match the latitude and longitude position information to the latitude and longitude information of the cross-section of major streets in the cross-section vector database.
  • the cross-section vector database is a subsection of the vector database, all within the MIDMAIN 821, 823 process or the like.
  • the MIDMAIN 821, 823 process via vector utility library retrieves the nearest matching street segment, its street name and block number range, and the nearest cross-section of major streets, and its street name and other information.
  • the MIDMAIN 821, 823 process via mobile information data process attaches the street text information to the mobile position information and defines such information as a data packet or the like.
  • the MIDMAIN 821, 823 process sends the data packet over a line represented as 642 to the fleet process 644.
  • the fleet process 644 is a user interface display process.
  • the fleet process can be any suitable user interface display process such as a UNIX process or the like.
  • the fleet process 644 receives mobile position information and street text information from the MIDMAIN 821, 823 process.
  • the fleet process 644 accesses via line represented as 642 the raster database (or memory) through the raster map utilities, all in the MIDMAIN 821. 823.
  • the raster map utilities match the latitude and longitude mobile position from the fleet mobile units to the various digitized raster maps data in the raster map database.
  • the zoom level option using for example the X22/Motif graphical user interface on the mobile tracking station 626, the digitized raster map is displayed in one display window segment 530 and the corresponding street text information on another display window segment 532.
  • a user locatable mark 520 represents the fleet mobile units position for a particular vehicle. The icon 520 is positioned at the corresponding latitude and longitude location on the raster map display 530.
  • the display system includes at least three databases or memory locations and the like (a mobile position database 614, a raster database 645, and a vector database 631).
  • the database information is interrelated by common latitude and longitude position data.
  • the mobile tracking station 626 displays the position, raster and vector information in a format easily understood by the dispatcher or fleet manager.
  • the raster information includes a graphical representation of the raster map and icons graphically depict locations of the fleet mobile units on such raster map.
  • Vector information is superimposed onto the raster map to provide intelligence.
  • Other functions of the vehicle display system are similar to the previous embodiment.
  • each vehicle 610a-610n includes a navigational tracking device, hereinafter called a fleet mobile data suite (MDS-1 to MDS-n) 611a-611n.
  • MDS-1 to MDS-n a navigational tracking device
  • Each fleet MDS 611a-611n includes elements such as a microprocessor-controlled circuit coupled to a GPS navigational sensor and the like, a mobile radio modem, and a specialized mobile radio (SMR) operational in, for example, the 800-900 Mhz frequency range.
  • SMR specialized mobile radio
  • the specialized mobile radio may be any type of wireless commumcation means such as cellular telephone, frequency modulated (FM) carrier means, cellular digital packet data means (CDPD), satellite communication, wide area wireless communication network (WAN) such a product called RicochetTM sold by Metricom of Los Gatos, California, and others.
  • the mobile radio modem can also be a data modem, PCMCIA card modem, or the like for transporting data signals, voice signals, video signals, and the like.
  • the fleet MDS 611a-611n compiles latitude and longitude position data from GPS sensors in a continuous manner and the like. Latitude and longitude position data are periodically transmitted at for example 5 minute increments or less to the mobile information center 802 block.
  • the automatic vehicle location system provides for vehicle tracking by way of selected elements from the fleet mobile units, the mobile information center, and other elements.
  • the automatic vehicle system includes elements such as a UNIX DBFUPDATE server 618, a UNIX DBREQSRV server 624, a data acquisition and messaging interchange module (MIP or messaging interchange module) 801, a data acquisition and messaging interchange module and receive module (MIP_RCV) 808, a monitoring process (MONDBF) 813, and others. Also shown are a shared memory 815, a mobile information center (MIC) disk buffer 807, and other elements.
  • MIP or messaging interchange module data acquisition and messaging interchange module 801
  • MIP_RCV data acquisition and messaging interchange module and receive module
  • MONDBF monitoring process
  • shared memory 815 a shared memory 815
  • MIC mobile information center
  • the UNIX DBFUPDATE server 618 momtors the shared memory 815 via line represented as 827 for any new reports or updated reports.
  • the UNIX DBFUPDATE server 618 transfers the reports from the shared memory 815 to the mobile information center disk buffer 807 in a periodic manner via line represented as 825.
  • the reports include information such as a time, a vehicle location, a driver name, a vehicle number, a vehicle speed, a vehicle status, and others.
  • the UNIX DBFUPDATE server 618 uses memory and file locking protocols to access data from the shared memory 614.
  • the UNIX DBFUPDATE server 618 process runs continuously, transferring reports in data form from the shared memory 815 to the mobile information center disk buffer 807.
  • the shared memorv 815 can be a dynamic random access memory which can store up to about 50 or less reports per vehicle. Accordingly, it is important that the data in shared memory 815 be transferred to the mobile information center disk buffer 807 before the shared memory fills up with data. For example, vehicles reporting every minute fill up the shared memory 815 in about 50 minutes or less, and the new data coming into the shared memory can be overwritten. Of course, as dynamic random access memory capacity increases, more reports can be stored in the shared memory 815.
  • the UNIX DBRQSRV 624 server processes requests from login to logoff from the automatic vehicle location subsystem, and in particular a workstation.
  • the workstation can be any suitable workstation of sufficient memory and processing means to handle data as described herein.
  • the UNIX DBRQSRV 624 server also forks out a copy of its process upon connection on a socket. The fork out process verifies login information and processes requests from each workstation.
  • the UNIX DBRQSRV 624 server also provides for a different (or second) commumcation channel w ith the use of a computer aided dispatch (CAD-type) messages as will be described in more detail below. Other functions of the UNIX DBRQSRV were described in the previous embodiment.
  • CAD-type computer aided dispatch
  • An interface between fleet mobile units 610 and mobile information center disk buffer 807 is provided by the messaging interchange process (MIP) 801.
  • MIP messaging interchange process
  • vehicle position reports from the mobile units 610 are transferred to the snared memory 614 via line represented as 829.
  • the UNIX DBFUPDATE server transfers the vehicle position reports into the mobile information center disk buffer 807 via line represented as 827.
  • the vehicle position reports include at least latitude and longitude information at a selected time and the like.
  • the MIP.RCV process 808 assistants (or is an assistant) the messaging interchange process 801.
  • the MIP.RCV process 808 receives data from the messaging interchange process 801 and processes the data to determine a forwarding path. For example, some data are sent back to the messaging interchange module 801 for forwarding to the fleet mobile unit(s) 610, and other data go into the shared memory 815 and/or the two way messaging disk buffer 805, among other elements.
  • the MIP.RCV may also forward data to other elements of the mobile information center, mobile tracking station, and the like.
  • the automatic vehicle location system also includes the monitoring process such as the MONDBF 813 and the like.
  • the MONDBF 813 is often dormant but periodically wakes up and checks the DBFUPDATE process 618 via line represented as 831. If the DBFUPDATE process 618 is not nning, the MONDBF 813 outputs a warning message to an output device such as a screen or a printer, typically in standard UNIX shell script language or the like. The warning message alerts a user and appropriate action such as maintenance of the system or the like occurs.
  • the two-way messaging system provides for two-way messaging between the fleet mobile units 610 and, for example, a dispatcher or the like.
  • the two-way messaging system is a "dumb" messaging system for communicating voice, data, video, and the like information between the fleet mobile umts and the dispatcher and the like.
  • the two-way messaging system includes elements such as a mobile information center two-way messaging module (MIC.TWM) 803, a UNIX server 809, a CANPEND process 817, a CLRTWMDB process 819, and others.
  • MIC.TWM mobile information center two-way messaging module
  • a message such as a two-way message and the like from one of the fleet mobile units goes to the MIC_TWM process from the message interchange module 801 via line represented as 833.
  • a message from a dispatcher goes to the fleet mobile units through the MIC.TWM module (or process) 803 through the messaging interchange module 801 via lines represented as 841 and 833.
  • the MIC TWM module provides an interface between the dispatcher and the fleet mobile units 610 for two-way messaging.
  • the MIC.TWM module also has write access to a two- way messaging (TWM) database 805 and other memory devices via line represented as 835.
  • the MIC . TWM module has read access to the two-way messaging database 805 and other memory devices via line represented as 835.
  • the MIC.TWM module also records in-coming (fleet mobile units to mobile information center) and outgoing (mobile information center to fleet mobile units) messages in the two-way messaging disk buffer or the like.
  • the MIC.TWM module creates queues for communication between the messaging interchange 801 module, the UNIX DBTWMSRV server 809, and any other two-way messaging module, and is often started first in the two-way messaging system.
  • the CANPEND module 817 cancels pending messages via line represented as 839.
  • Pending messages may be defined as messages sent to vehicles that are turned “off” or messages that need “acknowledgment” which are queued up as “pending” until they are delivered or acknowledged.
  • the CANPEND module 817 reduces the likelihood of messages being piled up or the like.
  • the CANPEND module 817 is preferably activated periodically to automatically cancel pending messages and the like.
  • the cancelled messages are stored in the TWM disk buffer 805, and can be viewed via a HISTORY.DATA option, but the status is preferably displayed as "cancelled” in a selected display device.
  • the CLRTWMDB module (or process) 819 clears the two-way messaging disk buffer of incomplete message transactions in the event that the messaging interchange process 810 or the MIP.RCV 808 process is restarted.
  • the CLRTWMDB module 819 clears status prompts such as message sent or message fail and other types of status prompts from the two-way messaging disk buffer, and leaves the messages as pending.
  • the CLRTWMDB process 819 is often executed before the messaging interchange module process, but can also be executed at other times.
  • the computer aided (CAD) dispatch process provides dispatching for the fleet mobile units from the dispatch office.
  • the computer aided dispatch process includes servers 809 such as a MICDSP server, a UNIX SF.DSPSRV server, a SFDSP server, and others.
  • the computer aided dispatch also includes a system 811 (or module).
  • the system or module can be any suitable computer aided dispatch software and hardware combination or the like.
  • the MICDSP server defines an interface to the CAD process 811 and other system elements such as the mobile tracking station 626, the fleet mobile units 610, and the like.
  • the MICDSP server translates data coming from the CAD system 811 via line represented as 843 and formats the data into the mobile information center system specifications or the like.
  • the MICDSP server passes data to the SF DSPSRV process, a UNIX socket level interface process or the like.
  • the SF.DSPSRV server provides an interface between the MICDSP server and the SFDSP server.
  • the SF . DSPSRV server deciphers different types of CAD messages and routes them to either the SFDSP or DBREQSRV servers.
  • Messages from the fleet mobile units are sent to SFDSP server, while display and driver status type of messages are sent to the MTS station via the DBRQSRV process.
  • the SFDSP module provides a connection to the two-way messaging disk buffer for a store-n-forward mechanism.
  • the SFDSP provides socket connection to the DBTWMSRV process and sends CAD messages via the two-way messaging disk buffer to the fleet mobile units. Statuses are returned to the CAD system by the fleet mobile data units via the SFDSP process.
  • the SFDSP process also reads the SUPERUSR account information of the fleet mobile units at start-up time via a login packet transaction.
  • the present fleet management system can also be any of those described in U.S. Serial No. 08/706,211 (15517-000111), commonly assigned, and also incorporated by reference. Additionally, the present fleet management system can also be a variety of others. Furthermore, the various functions of a fleet management system can be implemented in hardware or software or a combination of hardware and software. Accordingly, the descriptions above can be further combined in the form of software, as well as combined in hardware. These descriptions should not be limited with respect to the claims defined herein.
  • Fig. 5 shows a simplified overall system 110 in an information management system, such as a fleet management system, according to an embodiment of the present invention.
  • System 110 includes a mobile information center (MIC), or base station, 112 that interacts with a mobile data suite (MDS) 114.
  • MDS mobile data suite
  • the MIC may include a system, such as a software system, to manage several MDS users to efficiently control fleet use.
  • U.S. Serial No.08/706,211 commonly assigned, describes a MIC according to the present invention.
  • This application is incorporated by reference herein for all purposes. Of course, other types of systems which have similar functionality as the MIC described herein can also be used.
  • the MDS is an integrated module including a mobile control unit (MCU) 116 and a mobile data terminal (MDT) 118.
  • the MDS is an on-board module, adapted to fit conveniently in a fleet vehicle such as a car, van, or truck.
  • the MDS is easily portable, fitting in a carrying case no bigger than approximately 18 " x 12 " x 10 " and weighing approximately 10 pounds or less. This portability allows a user to remove the MDS from the vehicle for safe storage or for convenient maintenance away from the confines of the vehicle.
  • the MDT may act as an interface between the MCU and the user for receiving and displaying information.
  • the MCU includes a global positioning system (GPS) 120, a microprocessor unit 122 (e.g., a microprocessor board, a microcomputer, a micro-controller, a programmable controller), and a transmitter/receiver (T/R) unit 124.
  • GPS global positioning system
  • the GPS allows monitoring of positioning-related information, e.g., latitude and longitude.
  • Positioning data enters the GPS via a GPS antenna 126.
  • the GPS antenna may be mounted on the exterior of the vehicle, but is not limited to this location. This may improve reception of the antenna while reducing space consumed by the system inside the vehicle.
  • a magnetic base may be used to mount the antenna that will allow a user to quickly and easily remove the antenna for storage, to improve reception, or for other purposes.
  • the GPS can determine the current or past location of the MCU based on information received from global positioning satellites.
  • the GPS, the microprocessor unit, or the MDT (including MDT software) either alone or in combination, may use the information received by the GPS to determine information related to system management such as the vehicle's speed and heading.
  • equipment at the MIC or elsewhere in the MCU, such as in the microprocessor unit may determine this system management information.
  • the GPS is a Trimble OEM GPS receiver card made by Trimble Navigation, although other GPS systems can be used.
  • Any form of positioning system capable of determining the location of the MCU could replace the GPS.
  • a system using information from local position detectors instead of global positioning satellites could be used.
  • the GPS is generally not required and may be omitted from the MCU.
  • the MCU T/R receives data from, and transfers data to, the MIC via an MCU T/R antenna 128a.
  • the MIC receives data from, and transmits data to, the MCU via a MIC antenna 128b (the data transfer represented by a double-ended arrow).
  • Data from the microprocessor or GPS may be sent to the MIC or data from the MIC may be received and transferred to the GPS or microprocessor as needed by the MCU T/R.
  • the MCU T/R may process received data as necessary to be in a form compatible with its destination.
  • the MCU T/R is preferably a radio T/R, such as a radio frequency radio modem, due to cost and maintenance advantages.
  • the MCU T/R may be a RAM compatible Mobitek Modem made by Mobitek.
  • Other forms of T/R units, however, may be used depending upon the application.
  • the MCU T/R antenna similar to the GPS antenna, may have a magnetic base, or be otherwise adapted, to assist mounting the antenna on the exterior of the fleet vehicle.
  • the GPS antenna and the MCU T/R antenna may be mounted at least about 12 inches apart.
  • the microprocessor unit may act as an interface unit in the MDS.
  • the microprocessor may provide an interface between the MCU T/R and the MDT, the MCU T/R and the GPS, or the GPS and the MDT.
  • Included in the microprocessor unit are a memory 130 and a microprocessor 132.
  • the memory may, for example, store messages for the user of the MDS. These messages may come from, for example, the MIC, the GPS, or the user. Messages may be categorized into groups for convenience such as received but not yet read, received and previously read, and sent.
  • the microprocessor can access desired portions of the memory for data insertion or retrieval.
  • the microprocessor may also process data from the memory, the MIC, the GPS, or the MDT before transferring the data to the memory, the MIC, the GPS, or the MDT. Examples of such processing may include determining speed and heading information based upon positioning data.
  • the MDS architecture includes the MDT, MCU, GPS, microprocessor unit, and MCU T/R.
  • the microprocessor unit may act as the central controller of the MDS, directing information flow between the components and storing information as necessary.
  • the GPS receives information through its antenna and the microprocessor unit may store this data and/or direct it to the MCU T/R for transmission to the MIC or to the MDT for user viewing.
  • Information from the MDT may also pass to the MCU T/R and/or be stored in memory under the direction of the microprocessor unit.
  • the MCU T/R may then transmit the data to the MIC.
  • the MCU T/R may also receive information from the MIC which the microprocessor unit may then direct into memory and/or to the MDT.
  • a power cable 134 may connect the MCU to an external power supply.
  • the external power supply may be the same power supply used by the vehicle.
  • the power cable may have a connector (not shown) that fits into a cigarette lighter socket of the vehicle.
  • the MCU would then use the electrical energy from the vehicle such as a 12-volt battery.
  • Using an external power supply could help reduce the size, weight, and cost of the MDS.
  • the MCU may have an internal power supply 136 in addition to, or in lieu of, the external power supply. Having an internal power supply would allow the MDS to operate independently of an external power supply. The user could, for example, use the MDS in places which would be inaccessible if the MCU was dependent upon a vehicle power supply.
  • having an internal power supply would allow the user to use the MDS as needed in case of a failure of the vehicle's power supply. For example, the user could relay information to the MIC if the user is in an accident that causes the battery to stop functioning, or during a malfunction which prevents energy from reaching the power cable.
  • the MDS may also include a printer 140. Having a printer would, for example, allow the user to make a hard copy of data received from the MIC, transmitted to the MIC, or entered into the MDT even if not transmitted to the MIC.
  • the printer may also be utilized to provide a hard copy of other information such as the configuration of the MDS, GPS, MDT, or the MCU.
  • Fig. 6 illustrates an exemplary front view diagram of an MDT 200 according to an embodiment of the present invention.
  • Data from the GPS and MIC may be illustrated on a display 202 of the MDT.
  • the display permits the user to visually inspect the displayed data and act accordingly.
  • the display can be any suitable output device such as a liquid crystal display or an active matrix liquid crystal display, as well as other types of displays, e.g., laser, diodes.
  • the display should have a sufficient region for providing information (e.g., text, numbers) in an easy to read manner to a user. Additionally, the display can work under limited or low power conditions in some embodiments.
  • the display also can be employed as an input device such as a touch sensitive screen used in, for example, a product called PalmPilotTM made by 3ComTM Corporation of California.
  • the display is also resistant to extreme environmental temperature ranges (e.g., freezing) and is shock resistant.
  • the display is sealed or isolated from moisture and particulates such as "dust" or contamination.
  • information from the MIC such as changes in delivery or pick-up schedules, lunch break approvals, emergencies, traffic conditions, vehicle location, and personal messages may be displayed.
  • the MDT is a pager
  • the user can receive business, personal, and other messages such as reminders, phone numbers, and emergencies.
  • the received data may include general information that may be broadcast to many users simultaneously, such as sports scores or other news.
  • the display can also be coupled to another output device such as a beeper, a pager, electric shocker, or a vibrator to alert the user in a specific or selected situation such as an emergency.
  • the MDT may also receive data from the user.
  • the MDT may have a data entry portion 204.
  • the data entry area may be a keypad.
  • Other types of data entry tools may be utilized including a flat-panel keypad, a recorder that receives and stores sounds such as speech, a voice recognition unit which could recognize speech and convert the speech into data indicative of the speech such as text data, a touch-sensitive display, a display area allowing the user to write or draw characters or symbols such as a signature (e.g., pen computing), a bar-code reader, or a scanner (e.g., an optical character recognition device).
  • the data entry area is one of the last two examples, the data entry portion may coincide with the display 202.
  • the MDT or MCU may include circuitry to recognize hand-writings or signatures. This ability, for example, could assist the user in determining whether the person signing for a package has the authority to do so.
  • the MDT may include a housing 206 adapted to fit in the user's hand, for example. Such a hand-held design permits the user to hold the MDT with one hand and enter data with the other hand.
  • the data entry portion receives audio input, the user may conveniently hold the MDT with one hand, enter data, and still have one hand free. Such an arrangement also permits a user with physical handicap to use the MDT more conveniently.
  • the housing is preferably made of a suitable material to withstand environmental variations such as temperature and weather. Accordingly, it is desirable to have a housing that is resistant to moisture and particulate contamination. This feature can be achieved by way of seals such as o-type rings and rubber gaskets, which seal one member of the housing with another member of the housing.
  • the housing can be sufficiently rigid to withstand mechanical shock, although other embodiments may require a flexible or "soft" housing for ergonomic purposes.
  • the housing can have a coating made of a soft or flexible synthetic material, which tends to be easier to handle with "hot” and “sweaty” palms, for example.
  • the housing is also made of an isolating or shielding material which can electrically isolate the internal electronics from external transmission lines that can lead to "noise” or multi-path influences.
  • the housing is also chemically resistant and inert to isolate the internal components from chemical influences.
  • the MDT is detachable from the MCU in some embodiments.
  • a detachable design allows the user to use the MDT away from the MCU. Thus, the user may not need to carry the whole MCU in order to use the system.
  • an internal MDT power supply 208 would permit the user to use the MDT away from the MCU.
  • the MDT power supply may also be mounted externally, for example, on a belt clip. Such a configuration may provide a lighter MDT which may be carried by hand for a longer period to distance.
  • the MDT is generally less than 5 pounds, less than 2.5 pounds, or less than 1 pound to merely ounces in preferred embodiments.
  • the MDT can be able to transfer data to, and receive data from, the MCU when connected to the MCU.
  • the user enters data while away from the MCU and later connects the MDT to the MCU.
  • the MDT and MCU can transfer data to each other.
  • This configuration obviates driving or even having an antenna, and associated circuitry, in the MDT for receiving and transferring data while detached from the MCU.
  • the MDT may receive, transmit, or transmit and receive data while detached from the MCU.
  • the MDT may have an MDT antenna 210 and associated circuitry, which is shown in reference to Fig. 2 A.
  • the MDT antenna may be internal, as shown, or external.
  • the MDT can transfer data back and forth with the MCU, MDS, and MIC via the MDT antenna.
  • the MDT may be restricted to receiving data only (such as if the MDT is a pager), or transmitting data only.
  • the MCU may require an additional MCU/MDT antenna 138.
  • the MDT may take several forms.
  • the MDT can be similar to a portable data terminal (PDT) 3100 made by Symbol Technologies, Inc.
  • the MDT may be an electronic personal organizer such as the PalmPilotTM.
  • the MDT may also include, or simply be, a printer.
  • Fig. 6 A is a simplified block diagram of the MDT shown above.
  • the simplified diagram includes, among other elements, a GPS 251, a transmitter/receiver unit 253, a microprocessor unit 254, a power supply 263, a printer driver 261, a display driver 259, which are coupled to each other by way of a common bus(es) 257.
  • the GPS determines positioning information, which can be displayed by way of the display through the display driver or which can be sent to the MIC through the transmitter/receiver unit. Additional output of information can be directed to an optional printer by way of the printer driver.
  • the power supply provides energy in the form of electrical voltage and current to elements of the MDT.
  • the power supply is a rechargeable battery such as "NiCad” or the like.
  • low voltage applications can be driven by a solar power supply unit, which can also be used to recharge the battery in some embodiments.
  • Antenna 210 is coupled to the transmitter/ receiver.
  • the antenna is capable of communicating through radio frequency radio signals.
  • the location and type of the antenna is merely exemplary and one of ordinary skill in the art would recognize other variations, alternatives, and modifications.
  • the antenna may be internal or external to the device, or may utilize other types of signals to communicate, such as infra red. Overall functionality of the MDT is often overseen using the microprocessor based unit in the present embodiment.
  • Fig. 7 shows an example of a simplified method 300 according to an embodiment of the present invention using a system such as that shown in Figs. 1 and 2. This method is exemplary only and does not limit the claims to this embodiment. The order in which the steps appear in the figure are largely arbitrary and may appear in many orders different from the specific order shown in Fig. 7.
  • the method starts at step 302 and proceeds to step 304, when user data is entered into the MDT.
  • This data entry may take any of numerous forms depending on the particular MDT used. For example, the user may enter data by pressing keys on a keypad, touching portions of a touch screen, scanning a document, or reading a bar code.
  • the user data is transferred from the MDT to the MCU.
  • this data transfer may take any of numerous forms.
  • the data transfer may be accomplished via the MDT antenna, or by coupling the MDT and MCU using a cable, or by positioning the MDT into a cradle in the MCU having MCU contacts adapted to couple to corresponding MDT contacts.
  • the MDS receives positioning data via the GPS antenna and MIC data via the T/R antenna.
  • the positioning data could also come from local position detectors or other positioning systems.
  • the GPS and T/R antennas may be specifically designed or selected to reduce the power needed to provide adequate data transfer between the MCU and the positioning system or the MIC.
  • the MCU processes MCU data (including, for example, the user data, positioning data, and MIC data) as needed. Such processing may include manipulating the user data, positioning data, and MIC data and converting them into formats compatible with the MIC or the MDT. For example, the positioning data may require manipulation in order to display this information on the MDT. Also, this step may include the processing needed to determine information such as vehicle speed and heading.
  • the MCU data is transferred to the MIC. All, selected part, or none of the information available for transfer may be transferred. This data transfer may typically involve sending the data via the T/R antenna to a corresponding antenna at the MIC.
  • the MCU transfers data to the MDT. All, selected part, or none of the information available for transfer may be transferred. This data transfer may occur in the same manner as described above with respect to transferring data from the MDT to the MCU.
  • the MCU may be configured to transfer data when a communication link between the MCU and the MDT exists, or periodically. For example, the MCU may accumulate data for transfer to the MDT for a predetermined time period, then transfer some part of the accumulated data at the end of the time period. Alternatively, the MCU may transfer data to the MDT in real-time, as soon as data is ready for transfer.
  • the MCU data is displayed on the MDT display.
  • the displayed data may include the MCU data transferred from the MCU, the user data entered into the MDT, and/or predetermined data not entered by the user or received from the MCU.
  • An example of the predetermined data would be prompts provided to the user to request data input, text or symbols displayed near the user data, or MCU data that may provide an indication of the significance, or meaning, of the displayed user or MCU data.
  • the process terminates at step 320. While the above method has been described using a specific order, many combinations and permutations of the order presented are possible. The steps may appear in almost any order within a few logical guidelines. These guidelines may merely ask that data exists before an attempt to transfer or process it.
  • step 306 of transferring user data from the MDT to the MCU may follow step 304 at a later time.
  • step 312 of processing MCU data may follow any combination of the steps that provide data to the MCU, such as steps 306 through 310.
  • steps 314 and 316 of transferring MCU data to the MIC and the MDT may follow any combination of the steps that provide data to the MCU.
  • step 318 of displaying MCU data on the MDT display may follow the step of transferring MCU data to the MDT at a later time. Additions and omissions to the steps of Fig. 7 are also acceptable.
  • the MCU need not receive MIC data from the MIC.
  • the MCU may not even have GPS (or other positioning system) capabilities and, hence, the method need not include receiving positioning data. Other deletions are also possible.
  • the method may include more steps or sub-steps including transferring data to a RAM network that may provide coverage nationwide, globally, and beyond.
  • the present invention includes software to control the user interface and data processing operations.
  • the software may partly or completely reside in the MCU or MIC, but preferably resides in the MDT.
  • the MDT software this label refers to an, but not the only, possible embodiment of the present invention.
  • the MDT may encased in a product manufactured by Symbol commonly known as a Symbol terminal, such as Series 3100, that has its own software.
  • the software described below may be an addition, a modification, or a replacement of the software supplied with the Symbol terminal.
  • the software of the present invention may control receipt, processing, and transmission of data between the MCU, MDT, MIC, user, etc.
  • an external modem configuration may support a Symbol Series 3100 terminal, an external RAM-compatible Mobitek Modem (sometimes referred to as a Mobidem), and a Motorola 505sd modem. This configuration may, for example, not support GPS functionality.
  • a black box configuration may support a Symbol Series 3100 terminal and a black box including a RAM-compatible Mobitek Modem module, and a Trimble OEM GPS receiver card.
  • This configuration could support, among others, modem communications and GPS information receipt, processing, and transmission.
  • the software preferably runs on the MDT, interfaces with the external Mobitek modem or a black box including the GPS and the MCU T/R. Also, the MDT software preferably includes a traffic manager and a report scheduler.
  • the MDT software is organized in a modular fashion. This arrangement may provide compartmentalized functionality to assist with creation and modification of the software code and debugging of problems.
  • an engine module may communicate with the GPS. This module could prepare data for transmission to the GPS and process data received from the GPS. The data transmitted and received may or may not pass through or be stored in the microprocessor unit.
  • the engine module supports Magnavox 4200 and engine receivers used in the GPS.
  • a hardware initialization module may provide initialization and hardware interface functions for the MDS. In this respect, the MDT may initialize the entire MDS by transmitting initialization parameters to the MCU to initialize the MCU T/R, the GPS, and the microprocessor unit.
  • this module can provide interface functions among the various MDS components.
  • this module may also provide support for an event timer facility of the MDS.
  • the event timer facility could, for example, allow users to have a number of timers based on the Symbol terminal system timer.
  • an MDT module may provide MDT-specific functions.
  • the MDT module may support data entry forms (e.g., a package delivery form or a hospital admittance form) that are larger than the physical size of the screen by allowing scrolling of the forms.
  • a number of routines could support automatic list building by selecting and inserting an identification number in appropriate form field.
  • the MDT module may provide a recall of information that is the same from job to job, such as customer-related information, by having the user provide the identification number. This would save the user time and effort in entering such information. For example, the customer's address, phone number, billing, and special instruction information may be recalled based upon entry of the customer's name or other identification tools such as the identification number.
  • Menus module to support scrolling menus, time and distance position reporting, data compression, and blinking overlaid indicators for canceled, re-transmitted, and changed jobs.
  • the user may select items in each menu by scrolling or entering an associated number. To exit from any menu, the user may press a clear key, etc.
  • an MDT utility module may provide utilities for an MDT interface.
  • the MDT interface may include a display screen upon which data may be displayed prompting the user for information or providing the user with information.
  • the MDT utility module may provide processes for, among other things, creating menus, positioning a cursor in the menus, and checking for input from the user.
  • Fig. 8 shows a sample startup activation screen. This screen displays general information and, for example, prompts the user to press the acknowledge key to activate the system.
  • a timer requires the user to press the enter key within a predetermined time (e.g., five seconds) or the MDT would shut down, requiring reactivation by the user before use.
  • the startup screen may ask for the user to enter a security code. This will, for example, only provide authorized personnel access to the MDT.
  • Other methods of startup activation may include finger-print recognition, retina recognition, etc.
  • Fig. 9 shows a sample warning screen displayed by the MDT at least for safety purposes. This or other warning screens may be displayed for different purposes. For example, the screen may display contact information in case the MDT is lost by the rightful owner.
  • Fig. 10 shows a welcome screen that the MDT may display. Information regarding matters including company name, version of the software, copyright, patent, trademark, or other intellectual property protection may be displayed on this screen. This screen may also display contact information in case the MDT is lost by the rightful owner.
  • Fig. 11 shows an primary menu 7000 of the MDT with an upper portion 7020 including status indicators, and the current date and time, and a lower portion 7040 providing information about user selectable functions and the corresponding keys.
  • the MDT status indicators shown in Fig. 11 provide information about the current operating status of the MDT.
  • a NEW indicator 7060 flashes when new messages are received.
  • An indicator 7070 displays the number of new messages.
  • a LINK indicator 7080 informs the user as to whether the network link is UP or DOWN.
  • the MDS communicates with the MIC only if the link is UP.
  • a BATT indicator (not shown) may replace the LINK indicator when the MDT is disconnected from the MCU.
  • the BATT indicator may provide general energy status of a battery in the MDT by, for example, indicating that the battery is either GOOD, LOW, or DEAD. Any of the MDT indicators may flash to indicate an abnormal status.
  • a number 7090 next to a pending indicator 7100 displays the number of messages currently awaiting transmission.
  • a number 7110 next to a saved indicator 7120 displays how many messages have been saved.
  • a GPS indicator 7140 provides information as to the age of GPS data and current GPS navigation capabilities.
  • An "UNK” status may designate an unknown GPS status.
  • "N/A” may indicate that GPS information is unavailable or "OLD” may indicate that the most recent GPS data is older than 10 seconds.
  • “NV2" may indicate that only 2-D navigation is available (i.e., only 3 satellites are visible) while “NV3” may indicate that 3-D navigation is available (i.e., more than 4 satellites are visible).
  • a signal-strength indicator 7160 may indicate the signal strength of the modem.
  • the signal-strength indicator may display up to six bars (e.g., right-facing arrowheads in Fig. 1 1). Three or more bars may indicate very strong communication signal, providing a very good coverage area.
  • the lower portion of the primary menu displays several options available to the user by pressing various keys. For example, pressing the FI key may display a help description. Pressing the PREV or NEXT keys may then step through various help pages. To return to the primary menu, the user can press the MENU key. Pressing F2 from the primary menu may allow the user to view sent messages. In an embodiment, the MDT retains the four most recently sent messages.
  • Pressing F2 from the primary menu may cause the MDT to display a list of sent messages with corresponding current statuses such as delivered or pending and the time each was sent.
  • Using the PREV/up-arrow and NEXT/down-arrow keys may step through these messages.
  • An extended beep sounds may warn the user when no further scrolling is possible.
  • the user may press F3 from the menu 7000.
  • the MDT then displays the latest saved message which could be scrollable as discussed above.
  • the user may delete sent and saved messages by navigating through the appropriate screens. Before deleting any messages, the MDT may confirm the deletion action.
  • Pressing F4 from the menu 7000 may provide access to new messages. For example, if the NEW indicator in the primary menu is blinking, the MDT may have one or more new messages. Pressing F4 may cause the MDT to display the new messages, for example, with the newest message displayed first. Once the user reaches the new messages, the user may scroll through the various new messages.
  • Figs. 12A and 12B illustrate a simplified FORMS MENU 8000. As shown, various options may be displayed on the FORMS MENU. This menu may also be scrollable to ensure all related information are displayed in the same menu. For example, Figs. 12A and 12B may be 2 of may available screens within the same menu 8000. An area 8050 may show an order of the present screen amongst the available screens within the same menu 8000. The user may select a desired form by either highlighting the form's title using an up-arrow or a down-arrow key and pressing an enter key. Alternatively, numbers associated with each item may be entered. Preferably, each form displayed in the FORMS MENU may be designed to ensure the user spends less time in preparing reoccurring information. For example, O 99/45519
  • 34 form 810 may enable the user to enter orders by utilizing previously saved information in order to minimize data entry time and possible errors. Once a form is filled, the user may send the currently-selected form to, for example, the MIC.
  • Figs. 13 A and 13B illustrates an exemplary STATUS MENU 9000.
  • the user may select a desired form by using the up-arrow and down-arrow keys and the enter key, or by entering the appropriate code.
  • the selected status screen is then displayed. If a different status is desired, the user may repeat the process, or may use the PREV and NEXT keys to cycle ttirough the various status codes. Once the desired status is displayed, the user may send the status to, for example, the MIC. The user may also exit the status menu.
  • the MDT keypad performs several generic operations according to the keys pressed.
  • Table 1 lists some generic operations according to key stroke or combination of strokes that initiate corresponding functions.
  • Fig . 14 shows a secondary menu of the MDT indicating various options for the user .
  • pressing a next key from the primary menu causes the MDT to display this screen.
  • the user may press any key (except FI - F4) to go back to the primary menu.
  • pressing FI from the secondary menu may provide the user with time, speed, and direction information. This may be accomplished by displaying GPS information, if available .
  • a time-speed-direction screen may show the current time, the speed of the vehicle, and the direction it is heading such as north, east, etc. It also may display how long the system has been turned on. In this embodiment, pressing any key returns the user to the secondary menu.
  • shutting down the MDT may also shut down the MCU a ter the MCU sends a message to the MIC (which could take as long as five minutes or more if communication coverage is poor). It may take a few seconds to a minute before the MDT actually powers down.
  • Fig. 15 is an exemplary illustration of a shutdown screen according to an embodiment of the present invention.
  • This screen may inform the user that the user will not receive messages while the MDT is shut down and prompts the user to proceed with shut down (ACK) or cancel the shut down request (CLR).
  • ACK shut down
  • CLR shut down request
  • pressing the F3 key may permit the user to enter a field-service screen. Access to this screen, however, may require a password and, preferably, only field service personnel have access to valid passwords or security codes.
  • the user may also view the MDT system application version number by pressing F4. From the system version screen, pressing any key may return the user to the secondary menu.
  • the MDS may be configured to save the last 40 job ID's (tag or identification numbers) to make it easier to enter them into an outgoing form rather than re-entering them using the alpha/numeric keys or other means such as a voice recognition, character recognition, etc.
  • the cursor When the cursor is placed in the job ID field, the user may press the up-arrow or down-arrow keys to scroll through the list of the latest JOB IDs. Once the desired job ID is displayed in this field, the user can proceed to the next field using the ENTER key. Some IDs may be displayed in reverse order indicating that a "pickup form" was sent to the host.
  • Jobs in the MDT may be canceled by the dispatcher, retransmitted, or changed.
  • the MDT may display these conditions in a unique way. If a job is canceled, the MDT displays the job to be canceled with a big flashing "X" overlaying the job. The MDT automatically removes the job once the user acknowledges the message. If the job is retransmitted as is, the MDT displays the job with a big flashing "R.” Finally, if the job is retransmitted with some changes in it, the MDT may detect that the job has changed and display the job with a big flashing "C.” The MDT may display these screens from either the primary or secondary menus. The retransmitted and changed jobs may replace the previous copies of the job. At any given time, the MDT may have only one copy of a job.
  • the MDT may also display various error messages to assist the user.
  • error messages may include: invalid form number; invalid status; invalid queued message; could not translate incoming message; error saving data ... press any key to continue; error retrieving data ... press any key to continue; error setting default lat/long; RCV queue full ... incoming message was lost ... please delete SAVED/SENT messages or process NEW messages; out of memory ... incoming message was lost... please delete SAVED/SENT messages or process NEW messages; out of memory ... message was not sent ... please delete SAVED/SENT messages or process NEW messages; delete a message from the save queue before saving this message; etc.
  • the MDT may display various warning messages to assist the user.
  • warning messages may include: Communications Out-Of-Range
  • the MDT may be restarted by a warm boot. For example, if the MDT application appears to be frozen (e.g., text on the display does not change even after trying to go to a different menu) for any reason and nothing revives it, then the user may want to warm boot the MDT. To warm boot the MDT, the user may press the PWR key for about 30 seconds to shut off the MDT. Then the user may press the 4 and 5 keys simultaneously followed by pressing the PWR key twice. turn off in 15 seconds of no activitv.
  • a warm boot For example, if the MDT application appears to be frozen (e.g., text on the display does not change even after trying to go to a different menu) for any reason and nothing revives it, then the user may want to warm boot the MDT. To warm boot the MDT, the user may press the PWR key for about 30 seconds to shut off the MDT. Then the user may press the 4 and 5 keys simultaneously followed by pressing the PWR key twice. turn off in 15 seconds of no activitv.
  • Table 2 indicates various possible trouble conditions and possible solutions to recover from them according to an embodiment of the present invention. TABLE 2
  • the present invention is not limited to the specific hardware and software described.
  • the functionality described herein can be further combined in terms of hardware or further combined in terms of software.
  • the hardware can also be separated or combined with other software.
  • the software can also be separated from the hardware.
  • the functionality can all be stored in the form of electronic data on an integrated circuit, for example.
  • the integrated circuit can include, among others, DRAM, SRAM, FRAM, and Flash Memory Cells, as well as other integrated circuit devices in the form of "chips" or "cards. " Accordingly, the present specification should not be construed as limiting the scope of the language of the claims herein.
  • embodiments of the present invention are fully described above, various modifications, alternate constructions, and equivalents will be obvious to those with skill in the art. Thus, the scope of the present invention is limited solely by the appended claims and their full scope of equivalents.

Landscapes

  • Engineering & Computer Science (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)
  • Navigation (AREA)

Abstract

L'invention concerne une technique de traitement de données ainsi qu'un système de gestion de parc automobile doté d'un module d'interfaçage nouveau (116) comprenant un processeur (122). Un système de positionnement (120) est couplé à une première antenne (126) et au processeur. Une terminal éloigné (118) est couplé électriquement au module d'interfaçage pendant au moins une première période. Il est capable de transférer des données au module d'interfaçage pendant la première période et un utilisateur.
PCT/US1999/004931 1998-03-06 1999-03-05 Systeme et procede de gestion de parc automobile WO1999045519A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU28987/99A AU2898799A (en) 1998-03-06 1999-03-05 Fleet management system and method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US3609498A 1998-03-06 1998-03-06
US09/036,094 1998-03-06

Publications (2)

Publication Number Publication Date
WO1999045519A2 true WO1999045519A2 (fr) 1999-09-10
WO1999045519A3 WO1999045519A3 (fr) 1999-11-25

Family

ID=21886588

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/004931 WO1999045519A2 (fr) 1998-03-06 1999-03-05 Systeme et procede de gestion de parc automobile

Country Status (2)

Country Link
AU (1) AU2898799A (fr)
WO (1) WO1999045519A2 (fr)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7065433B2 (en) 2003-02-07 2006-06-20 The Boeing Company Vehicle monitoring and reporting system and method
US7230527B2 (en) 2004-11-10 2007-06-12 The Boeing Company System, method, and computer program product for fault prediction in vehicle monitoring and reporting system
US7667647B2 (en) 1999-03-05 2010-02-23 Era Systems Corporation Extension of aircraft tracking and positive identification from movement areas into non-movement areas
US7739167B2 (en) 1999-03-05 2010-06-15 Era Systems Corporation Automated management of airport revenues
US7777675B2 (en) 1999-03-05 2010-08-17 Era Systems Corporation Deployable passive broadband aircraft tracking
US7782256B2 (en) 1999-03-05 2010-08-24 Era Systems Corporation Enhanced passive coherent location techniques to track and identify UAVs, UCAVs, MAVs, and other objects
US7889133B2 (en) 1999-03-05 2011-02-15 Itt Manufacturing Enterprises, Inc. Multilateration enhancements for noise and operations management
US7908077B2 (en) 2003-06-10 2011-03-15 Itt Manufacturing Enterprises, Inc. Land use compatibility planning software
US7965227B2 (en) 2006-05-08 2011-06-21 Era Systems, Inc. Aircraft tracking using low cost tagging as a discriminator
US8072382B2 (en) 1999-03-05 2011-12-06 Sra International, Inc. Method and apparatus for ADS-B validation, active and passive multilateration, and elliptical surveillance
US8203486B1 (en) 1999-03-05 2012-06-19 Omnipol A.S. Transmitter independent techniques to extend the performance of passive coherent location
US8446321B2 (en) 1999-03-05 2013-05-21 Omnipol A.S. Deployable intelligence and tracking system for homeland security and search and rescue
FR3025914A1 (fr) * 2014-09-16 2016-03-18 42Pix Dispositif de gestion d'une flotte de vehicules de depannage

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5122959A (en) * 1988-10-28 1992-06-16 Automated Dispatch Services, Inc. Transportation dispatch and delivery tracking system
US5408695A (en) * 1992-12-31 1995-04-18 Coded Communications Corporation Intelligent automatic deviation compensation for wireless modems
US5457629A (en) * 1989-01-31 1995-10-10 Norand Corporation Vehicle data system with common supply of data and power to vehicle devices
US5859628A (en) * 1994-01-05 1999-01-12 Pois, Inc. Apparatus and method for a personal onboard information system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5122959A (en) * 1988-10-28 1992-06-16 Automated Dispatch Services, Inc. Transportation dispatch and delivery tracking system
US5457629A (en) * 1989-01-31 1995-10-10 Norand Corporation Vehicle data system with common supply of data and power to vehicle devices
US5408695A (en) * 1992-12-31 1995-04-18 Coded Communications Corporation Intelligent automatic deviation compensation for wireless modems
US5859628A (en) * 1994-01-05 1999-01-12 Pois, Inc. Apparatus and method for a personal onboard information system

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7889133B2 (en) 1999-03-05 2011-02-15 Itt Manufacturing Enterprises, Inc. Multilateration enhancements for noise and operations management
US7667647B2 (en) 1999-03-05 2010-02-23 Era Systems Corporation Extension of aircraft tracking and positive identification from movement areas into non-movement areas
US7739167B2 (en) 1999-03-05 2010-06-15 Era Systems Corporation Automated management of airport revenues
US7777675B2 (en) 1999-03-05 2010-08-17 Era Systems Corporation Deployable passive broadband aircraft tracking
US7782256B2 (en) 1999-03-05 2010-08-24 Era Systems Corporation Enhanced passive coherent location techniques to track and identify UAVs, UCAVs, MAVs, and other objects
US8072382B2 (en) 1999-03-05 2011-12-06 Sra International, Inc. Method and apparatus for ADS-B validation, active and passive multilateration, and elliptical surveillance
US8203486B1 (en) 1999-03-05 2012-06-19 Omnipol A.S. Transmitter independent techniques to extend the performance of passive coherent location
US8446321B2 (en) 1999-03-05 2013-05-21 Omnipol A.S. Deployable intelligence and tracking system for homeland security and search and rescue
US7065433B2 (en) 2003-02-07 2006-06-20 The Boeing Company Vehicle monitoring and reporting system and method
US7908077B2 (en) 2003-06-10 2011-03-15 Itt Manufacturing Enterprises, Inc. Land use compatibility planning software
US7230527B2 (en) 2004-11-10 2007-06-12 The Boeing Company System, method, and computer program product for fault prediction in vehicle monitoring and reporting system
US7965227B2 (en) 2006-05-08 2011-06-21 Era Systems, Inc. Aircraft tracking using low cost tagging as a discriminator
FR3025914A1 (fr) * 2014-09-16 2016-03-18 42Pix Dispositif de gestion d'une flotte de vehicules de depannage

Also Published As

Publication number Publication date
WO1999045519A3 (fr) 1999-11-25
AU2898799A (en) 1999-09-20

Similar Documents

Publication Publication Date Title
US6889139B2 (en) System and method for mobile data processing and transmission
US6087952A (en) Remote mobile data suite and method
US5922040A (en) Method and apparatus for fleet management
US5758313A (en) Method and apparatus for tracking vehicle location
US5636122A (en) Method and apparatus for tracking vehicle location and computer aided dispatch
US7085775B2 (en) Database method and system for conducting integrated dispatching
EP1864084B1 (fr) Systeme de localisation et de navigation pour vehicule
US8018332B2 (en) Global emergency alert notification system
WO1989012835A1 (fr) Systeme de localisation de vehicules routiers
WO1999045519A2 (fr) Systeme et procede de gestion de parc automobile
WO2000048058A2 (fr) Suivi, commande, et systeme et procede de logistique
JP2004013801A (ja) 目的地及び通過地点到着時の自動通報管理システム
KR20010015007A (ko) 이동위치 추적장치 및 추적방법
JPH1131294A (ja) 集配管理システムおよび集配管理端末装置
JPH10188194A (ja) 行動補助システム及び記憶媒体
EP1240565A2 (fr) Systeme et procede de logistique
KR19980033511A (ko) 글로벌 위치설정 시스템과 페이저망을 이용한 택시 운행 장치및 방법
JPH1042072A (ja) 緊急通報システム
JP2002334395A (ja) タクシー顧客ガイドシステム
WO1999045471A9 (fr) Suite de donnees mobile et procede
KR19990035271A (ko) 위치 전송 및 관리 기능이 부여된 이동전화장치
AU774453B2 (en) Method and apparatus for tracking vehicle location
AU696284B2 (en) Method and apparatus for tracking vehicle location
JP3382755B2 (ja) 移動体誘導システム
KR200282481Y1 (ko) 이동차량의 위치추적 단말장치

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: A3

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase