Method for controlling conveyance of events by driver administrator of vehicles equipped with ELDs

• US 10,277,689 B1
• Filed: 11/21/2018
• Issued: 04/30/2019
• Est. Priority Date: 12/23/2005
• Status: Active Grant

• Current Assignee: PerdiemCo LLC
• Original Assignee: PerdiemCo LLC
• Inventors: Diem, Darrell
• Primary Examiner(s): Tran, Congvan
• Application Number:
  US16/198,330
• Publication Number:
  US 20190109912A1
• Time in Patent Office: 160 Days
• Field of Search: 455461, 4554042, 4554561, 34054911, 340988, 340991, 340992, 340994
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06K 7/10366 the interrogation device being adapted for miscellaneous applications
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G08B 5/22 using electric transmission; using electromagnetic transmission
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04M 1/72412 using two-way short-range wireless interfaces
• CPC Class Codes: H04M 1/72457 according to geographic location
• CPC Class Codes: H04M 2250/10 including a GPS signal receiver
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/084 using delegated authorisation, e.g. open authorisation [OAuth] protocol
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/30 : Services specially adapted for particular environments, situations or purposes
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]

Abstract

An improved system and method for defining an event based upon an object location and a user-defined zone and managing the conveyance of object location event information among computing devices where object location events are defined in terms of a condition based upon a relationship between user-defined zone information and object location information. One or more location information sources are associated with an object to provide the object location information. One or more user-defined zones are defined on a map and one or more object location events are defined. The occurrence of an object location event produces object location event information that is conveyed to users based on user identification codes. Accessibility to object location information, zone information, and object location event information is based upon an object location information access code, a zone information access code, and an object location event information access code, respectively.

Claims

1. A method for controlling conveyance of event information in a tracking service provided to authorized users who track vehicles that use a plurality of electronic logging devices (ELDs), wherein an ELD administrator of the tracking service provides access to user accounts in a first database management system application (DBMSA) executed by one or more central or distributed servers that provide user interfaces to the authorized users to log into to their respective user accounts, said DBMSA having access to a first database (DB) that identifies the ELDs by corresponding ELD IDs, the vehicles by corresponding Vehicles IDs (VIDs), the authorized users including drivers of a group of vehicles by corresponding User IDs (UIDs), and the group by a group ID (GID), wherein a Driver administrator of the group is given a privilege to access an administrator account in the first DBSMA by the ELD administrator, the method comprising the steps of:

a. interfacing over one or more wireless networks with the plurality of ELDs including a first ELD and a second ELD that are respectively identified by a first ELD ID and a second ELD ID, wherein each ELD comprises one or more processors that execute a location tracking application (LTA), said each ELD being configured to;

i. receive a power up sensor information from one or more sensors that indicate a vehicle in the group that uses the ELD is powered up by a driver of the vehicle, said power up sensor information being received in order to record one or more driving events after the driver logs into a driver user account via the ELD;

ii. periodically receive location information from a location information source (LIS) used by the ELD;

iii. log location information received from the LIS, said location information indicating where driving event conditions for occurrence of driving events are met;

iv. record a driving event information related to a first driving event that occurs based on a first driving event condition, wherein the recorded driving event information comprises a logged location information that indicates where the first driving event occurs;

v. provide a log-in interface via the LTA that allows the driver to log into the driver user account in the first DBMSA with a driver user ID and a driver password to access the recorded driving event, and

vi. provide an ELD interface via the LTA that allows the driver to edit the recorded driving event information after the driver logs into the driver user account; and

b. interfacing over one or more wired or wireless networks with a computing device that is configured to enable the Driver administrator to log into the administrator account by providing an administrator ID and an administrator password in order to;

i. identify a first vehicle by a first VID and a second vehicle by a second VID, said first VID and second VID being associated with the GID,

ii. specify a first authorized user identified by a first UID as a first driver of the first vehicle which uses the first ELD,

iii. specify a second authorized user identified by a second UID as a second driver of the second vehicle which uses the second ELD, and

iv. specify one or more recipients who are authorized to receive recorded driving event information;

c. receiving a first recorded driving event information from the first ELD containing the first UID;

d. receiving a second recorded driving event information from the second ELD containing the second UID driver; and

e. sending notifications to one or more recipients who are authorized by the Driver administrator to receive the first recorded driving event information or the second recorded driving event information.

2. The method of claim 1, wherein the first driving event condition is a condition applied to the group of the first vehicle and the second vehicle.

3. The method of claim 1, wherein the first driving event condition is met based on a sensed vehicle movement.

4. The method of claim 1, wherein the first driving event condition is met based on a sensed vehicle speed.

5. The method of claim 1, wherein the first event condition is a pre-defined event condition specified at the application level of DBMSA by the ELD administrator.

6. The method of claim 5, wherein the first driving event condition is based on a pre-defined zone.

7. The method of claim 6, wherein the pre-defined zone is based on State Plane Coordinates, wherein the logged location information indicates a movement of the first vehicle or the second vehicle within a State boundary, wherein the movement within the State boundary is recorded to be reviewed at a later time by a reviewer.

8. The method of claim 1, wherein a second driving event condition is defined at a user level by the Driver administrator, wherein a second event different from the first event occurs when the second driving event condition is met.

9. The method of claim 8, wherein the second driving event condition is met based on locations of the first vehicle or the second vehicle relative to a user-defined zone.

10. The method of claim 9, where in the user-defined zone is drawn on a map.

11. The method of claim 9, wherein the user-defined zone is created based on perimeter coordinates of a surveyed property stored in a DB.

12. The method of claim 8, wherein the second driving event condition is based on (1) information received from a sensor in the first ELD or in the second ELD or (2) location information received from a first LIS used by the first ELD or a second LIS used by the second ELD.

13. The method of claim 1, wherein the first driver uses an ELD interface of the first ELD to turn off a tracking mode.

14. The method of claim 13, wherein the first driver is tracked in the at least two different tracking modes while a first LIS used by the first ELD remains activated in both modes including when the tracking mode is turned off by the first driver.

15. The method of claim 1, wherein the Driver administrator is enabled to specify access privileges for a third authorized user having a third user account in the DBMSA, wherein the third authorized user controls access privileges of at least one of the first driver or the second driver.

16. The method of claim 1, further including the step

(d) receiving a file originated at the first ELD or at the second ELD that contains either (1) shipping information associated with one or more objects inside the first vehicle or inside the second vehicle or (2) shipping information associated with one or more trailers that are attached to the first vehicle or to the second vehicle;

and

(e) sending the file to a recipient authorized by the Driver administrator.

17. The method of claim 1, wherein the first event condition is based on a vehicle non-movement.

18. The method of claim 1, further including the steps:

(d) of receiving one or more information packages originated at the first ELD or at the second ELD when a second event different from the first event occurs based a second driving event condition different form the first event condition, wherein the second driving event condition is met based on a sensed measure of a physical characteristic at the first vehicle or the second vehicle, wherein the information package contains a video, an image or an audio file; and

(e) sending the one of more information packages to a recipient authorized by the Driver administrator.

19. The method of claim 1, wherein the first DBMSA interfaces with a second DB that is accessible by a second DBMSA maintained by the Driver administrator.

20. The method of claim 1, further including the step (b)(vi) of specifying a third authorized user identified by a third UID in the group based on a role in an organization, said role allowing the third authorized user to specify a sub-group within the group.

21. The method of claim 1, wherein logging of said location information starts from when the first vehicle or the second vehicle exits one boundary and ends when the first vehicle or the second vehicle enters another boundary, thereby allowing a movement of the first vehicle or the second vehicle between two boundaries to be reviewed at a later time by a reviewer.

22. The method of claim 1, further including the steps of:

(d) storing said location information in a log file; and

(e) sending the log file to a computing device for playing back the stored location information.

23. The method of claim 1, further including the step (d) of sending a message to the first ELD or the second ELD.

24. The method of claim 1, wherein icons indicate the location of the first vehicle or the second vehicle on a depicted map as the first vehicle or the second vehicle travels between a first boundary and a second boundary.

25. The method of claim 24, wherein an icon when selected is set to display a status in the first vehicle or the second vehicle.

26. The method of claim 25, wherein the status is related to a sensed measure at the first vehicle or the second vehicle.

27. The method of claim 26, wherein the sensed measure is related to location of the first vehicle or the second vehicle.

28. The method of claim 26, wherein a logged location information indicates where the sensed measure is made.

29. The method of claim 1, wherein each authorized user is given a user access privilege based on a role in an organization after logging into a corresponding user account, wherein the Driver administrator is given a privilege by the ELD administrator to specify user access privileges to classes of information, including a class of driver information that are accessible by the drivers of the group of vehicles.

30. The method of claim 1, wherein the first event condition is met based on a driver input at a user interface provided by the first ELD or the second ELD.

31. A The method of claim 1, wherein the recorded event information is edited by writing into a file stored in the ELD.

32. The method of claim 1, wherein a logged location information indicates where a sensor measurement is made at the first vehicle or a second vehicle.