Patent Application
20220138821
The invention generally relates to a system and method for collecting data from a vehicle as part of an Hours of Service or HOS compliance protocol. The invention more particularly relates to a system and method for collecting data from a vehicle via both an electronic logging device and a mobile communications device in close proximity therewith for enabling remote diagnosis and bidding for vehicle repair issues that arise during vehicle operation.
The present invention may be said to essentially provide an electronic logging system and method for collecting data from a vehicle-based electronic logging device and mapping the data to a mobile communications device in close proximity with the electronic logging device. The electronic logging system and method according to the present invention may be said to essentially comprise, in combination, an electronic logging device, at least one remote service provider, and at least one mobile communications device. The electronic logging device is outfitted upon a vehicle and configured to collect/record data exemplified by GPS location, engine error logs, and/or a log of vehicle drive time hours. The at least one remote service provider may preferably include at least an ELD service provider or Remote Service/ELD Provider service. The at least one service provider may also preferably provide Log Mapping Services. The essential function of the ELD service provider is to compile/aggregate data collected from the ELD or electronic logging device. The ELD service provider may also provide log mapping services or these services may be provided by a separate service provider.
The at least one remote service provider is preferably in communication with the electronic logging device for aggregating data therefrom. The at least one mobile communications device is preferably outfitted with a non-transitory, computer-implementable mobile software application. The non-transitory, computer-implementable mobile software application is configured for enabling the at least one mobile communications device to communicate with the at least one remote service provider for collecting and correlating data from both the electronic logging device and the at least one mobile communications device in a manner that allows the user to more easily arrange for repair services as required during vehicle operation.
Either the ELD service provider or a separate log mapping services provider preferably provides ELD-mapping services. The ELD-mapping services or processes provided by either the ELD service provider or the separate log mapping service provide may preferably utilize a best fit GPS mapping process with GPS data retrieved from the electronic logging device and the non-transitory, computer-implementable mobile software application. The ELD-mapping services or processes may alternatively utilize unique identifier-mapping whereby a unique identifier is retrieved from the electronic logging device via a wireless communication protocol provided by the non-transitory, computer-implementable mobile software application.
The electronic logging device or ELD is preferably in communication with the at least one remote service provider by way of a network-based communication channel and the at least one mobile communications device is in communication with the at least one remote service provider by way of a short-range wireless communication protocol. The electronic logging system according to the present invention contemplates the inclusion of a vehicle repair bidding system.
The vehicle repair bidding system extends the electronic logging system by way of or through the non-transitory, computer-implementable software application outfitted upon both the user's mobile device and a mechanic-side software application whereby a user may submit a vehicle repair request based on aggregated ELD data, user-provided imagery, video data, or audio data. The vehicle repair bidding system may be made more fully robust when used in combination with a remote vehicle diagnostic system.
The remote diagnostic system extends the electronic logging system through the non-transitory, computer-implementable software application whereby access is granted to electronic log data as mapped to a responding application for enabling diagnostics to be performed on the electronic log data. The user or vehicle driver is enabled to communicate with the diagnostic system via optional video, audio or text-based communication channels simultaneously when (temporary) access is granted to the electronic log data.
An alternative system according to the present invention provides a vehicular service request system. The vehicular service request system is operable to place localized vehicle service providers in communication with vehicle service requesters requiring vehicular service. The vehicular service request system preferably comprises at least one service provider client device; a remote service provider; and at least one service requester client device. Each service provider client device is preferably outfitted with a non-transitory, computer implementable software application for governing functionality of the system at the service provider side.
The remote service provider is outfitted with a server-side version of the a non-transitory, computer implementable software application for maintaining a service provider database and allowing registration of service provider client devices via the non-transitory, computer implementable software application. The remote service provider provides a unique user identification and logs geographic location associated with the service provider client device during a service provider registration.
The service requester client device is also outfitted with the non-transitory, computer implementable software application for enabling a vehicle service requester to initiate a vehicle service request. The system records the vehicle service request, preferably by way of a voicemail or telephone message recording, and associates the vehicle service request with a requester geographic location based on geographic location coordinates.
The remote service provider is configured to then search the service provider database for local service providers (i.e. those service providers within a predetermined radius of the service requester's geographic location as based on geographic coordinates), and sends the vehicle service request to those local service providers. The local service providers are thereby enabled to provide competitive cost estimates for the vehicle service request and the service requester is similarly enabled to accept an offer from a select local service provider by way of the non-transitory, computer implementable software application.
The vehicular service request system may further provide certain means for providing an Estimated Time of Arrival or ETA by select service providers based on reported geographic locations of the select service providers and the service requester. The remote service provider is further able to receive and correlate electronic log data as provided by an electronic logging device as outfitted upon a service request vehicle in close proximity to the service requester client device. The electronic log data may enable the local service providers to provide more comprehensive competitive cost estimates for the vehicle service request by providing the service providers with additional information taken directly from the Electronic Logging Device or ELD.
In this last regard, it will also be recalled the service requester is further enabled to provide a Vehicle Identification Number (VIN) identifier during the vehicle service request, which VIN identifier enables the local service provider(s) to provide more comprehensive competitive cost estimates for the vehicle service request. The non-transitory, computer implementable software application may be further preferably configured to provide status updates to a selected service provider (i.e. a local service provider whose bid or cost estimate and/or ETA has/have been accepted by the servicer requester) and/or the service requester on the status of the vehicle service request. This information may include financial transaction status in connection with the service request and the payment(s) therefor.
Other features and objectives of the invention will become more evident from a consideration of the following brief descriptions of patent drawings.
Referencing
The first component is the Electronic Logging Device or ELD device as referenced at 1. Put simply, an ELI) is an electronic solution that enables professional truck drivers and commercial motor carriers to easily track Hours of Service (HOS) for HOS compliance. All Commercial Driver's License or CDL drivers required to keep a Record of Duty Status (RODS) must use an ELD to document their compliance with HOS rules. Such an ELD device is typically installed in commercial freight vehicles to record GPS location, engine error logs, and log hours.
The ELD device 1 according to the present invention may be a state-of-the-art ELD device 1 and is connected to the engine of a commercial motor vehicle (CMV) and automatically records driving time and thereby ensures integrity of the driver's record of duty status (RODS) and compliance with hours-of-service (HOS) rules. ELD's use a variety of technologies, such as Global Positioning System (GPS), wireless and satellite communications and cloud-based data storage services to track HOS compliance. They have also become integral to overall fleet management, providing motor carriers with a vast amount of data useful for coaching drivers as well as tax and fuel management.
The second component of the present invention is an ELD service provider or Remote Service/ELD Provider service as referenced at 2. ELD service providers primarily function to aggregate data from ELD devices, and report the aggregated data to regulatory agencies on behalf of freight companies. An ELD data provider is a 3rd party service provider that allows some form of 3rd party API access to their end user ELD data. A third component of the system would be a Log Mapping Service Provider as at 4. Log mapping service providers 4 are dedicated to providing log mapping services and bidding services to mobile client devices as at 3. The fourth component of the system is such a mobile device as at 3. A driver may use the mobile device 3 to interact with the Log Mapping Service Provider 4.
It is also possible that the system be devised in such a way that the Log Mapping Service Provider and the Remote Service/ELD Service Provider are unified in a single system, providing ELD reporting and aggregation along with log-to-mobile device mapping, and a bidding system. All communication between components of the
Referencing
The mapping process begins with 2 data sources, the first of which is the ELD device 1 that reports GPS data, along with engine log and other critical data to the ELD service provider as a t 2. This process is depicted and referenced at box 100. The second data source is the mobile device 3 which also sends GPS data to the Log Mapping Service Provider 4 as depicted and referenced at box 101. The Log Mapping Service Provider or Service 4 then uses the GPS data from both the ELD 1 and the mobile device 3 to map the mobile device 3 to the ELD device 1 as depicted and referenced at box 102. The reader will note this mapping is constrained by device registration, meaning that the mapping only occurs against ELD devices 1 that have been registered under the same account or company as the mobile device 3 as depicted and referenced at box 103.
If the system is able to utilize GPS (as referenced at query 104), the mapping system may preferably use standard coordinate comparison formulae (e.g. Vincenty's formulae). The system first performs a search finding the closest ELD device 1 to the mobile device 3. Ater doing bad data checks (e.g. verifying that the mobile device 3 is within a threshold distance from the ELD device 1), the mapping service checks to see if it has more than one ELD-to-mobile device mapping that passes the bad data check. If so, it compares previous GPS coordinates, until a best fit is found. This process is generally depicted at box 105.
As an alternative to the GPS mapping system, the mobile device 3 may retrieve unique identifying data from the ELD device 1 via a Bluetooth, RFID, or similar signal as depicted at box 106. In this case, mapping is a simple query or request to either the ELD data store, or the ELD data service provider 2. An ELD data store is an internal implementation of all ELD storage requirements in compliance with federal and state regulations, which provides the same level of data as a 3rd party ELD Data provider. The datastore utilizes a database along with remote services to provide the same level of service. Once a mobile device 3 is mapped to log data, the system includes the log data in a repair request. The logging process may be an demand process (mapping occurs once a request for log data is sent from a mobile device 3), or a continuous process.
Referencing
The application then sends off the request to the Log Mapping Service Provider 4. The repair request may include mobile device GPS data, or the Log Mapping Service Provider may have this historical data continuously sent by the application and stored for log mapping purposes. The bidding process (running within the Log Mapping Service Provider 4) starts the mapping process as described in point 1 above, mapping the requesting mobile device 3 to log data. If mapping is run continuously then the bidding process queries a cache or index with device-to-ELD mappings (e.g. ELD device VIN-to-user UUID mapping, which can bring any number of unique identifiers). Once logs are mapped, a reference thereto or the logs themselves are attached to the repair request as summarized in box 109.
The remote service then locates local mechanics (mechanics are located using user device coordinates from both mechanics utilizing a mobile application and the requesting user's mobile device 3, or mechanic address and requesting user's device 3 coordinates) as at box 110. After locating local mechanics, a request is sent out over an established network base communication channel (exemplified by push notification, socket, HTTP polling, etc. . . . ) as at box 111. Local mechanics may then review the logs and repair details. If sufficient data is present to make a reasonable offer, mechanics may make an offer or put forth a bid as at box 112. If additional data is required the mechanic may request a phone call, send a text message, or establish a real time video call to request additional information. It is also possible that the mechanic could request temporary access to live ELD data, during a call to get data from the engine as a truck driver operates the truck or fulfills diagnostic requests from the mechanic as generally depicted in
Referencing
If the user approves the services, temporary access may be granted at the application interface of the mechanic as at box 116. The authorization grant may be in the form of a JWT token with a 30-minute expiration, or a grant of temporary access to the mechanics user session with the remote services. The truck driver/requesting user is then given the option of approving temporary access to ELD data. If the truck driver/user approves the request the mechanic application is authorized to request the log data from the remote services 4. The remote services 4 provide access to the log data mapped to the truck driver's mobile device/application 3 as at box 118. Once sufficient data has been collected the mechanic sends off a bid as at box 112. Preferably the requesting user/truck driver receives multiple bids. The user then uses the mobile application user interface to accept the bid as at box 114.
Referencing
After registering, the service provider user's mobile device updates as at 31 the remote or backend services 22 with the service provider's location by the service provider's geographic coordinates 25. The service provider thus registers with the remote backend system after which registration process, the system updates with information regarding the service provider's location as compiled via the geographic coordinates of the mobile communications device outfitted with the software application.
The audio recording 24 and coordinates 25 are sent as at 34 to the remote or backend system or service 22 which remote or backend system or service 22 maintains a register of service providers and their respective geographic locations. The remote or backend system or service 22 receives the service requesting user's geographic coordinates 25, and implements a database look up to locate nearby registered service providers, and retrieves phone numbers associated with registered service providers as provided during the during the registration process 30.
Using the phone number of a local service provider, the remote or backend system or service 22 sends out as at 35 a phone call through a programmatically enabled phone system or API as exemplified by service offerings of Twilio Inc., with corporate headquarters at 375 Beale Street, Suite 300, San Francisco, Calif., 94105. The phone call sent (as at 35) carries with it audio recording 24 and is played as at 36 to select service provider(s) as at 21.a, 21.b, and/or 21.c, who may then respond as at 37 to the remote or backend system or service 22 through the phone, SMS, or software application, providing the service-requesting user with an estimated price or bid on the repair work. The remote service 22 or mobile application may further generate an associated Estimated Time of Arrival or ETA using standard navigation SDK's or algorithms that are included as a part of the response. The service request user 23 may then then review all received offers from local service providers and respond via the software application by selecting one of the offers.
Referencing
With the associated phone numbers and ELD data, the system is prepared to properly route service requests from account-associated mobile phones as exemplified by mobile device 41. When an account associated mobile phone 41 calls into the system as at 43 via a registered phone number operating through a programmatic phone system or API, the user is preferably prompted to input VIN information. This could be either the full VIN code 45 or enough to uniquely identify the vehicle within the fleet. In this regard, it is contemplated that the last 6 alphanumeric characters of the VIN will usually suffice. The user is also prompted to record an audio message or audio recording 44 describing the type of service required.
The audio recording 44 and Vin data 45 are both delivered as at 43 to the remote or backend system or services 22 via programmatic phone or programmatic phone service provider exemplified by the service offerings of Twilio Inc. The Vin data 45 is then used to look up and return as at 46 vehicle data and geographic coordinates 47 from the ELD data 39. The coordinates 47 are used to locate nearby registered service providers 21 as more fully described in connection with the registration process generally illustrated in
The remote service then generates as at 48 a programmatic phone call to all nearby registered service providers (as at 21.a and 21.b) playing the recorded audio 44 during the call to every service provider 21 that answers the call. The service provider(s) 21 may then respond as at 49 to the system providing price estimates or bids on the service request(s), and an ETA that can be generated on either service providers device 21 or the remote or backend system or service 22. Using the location 47 of the service requester or user, this location 47 is delivered to the client by certain delivery means if the ETA is generated on the client side (SMS, push, socket etc.). The mobile client would then respond via phone input, SMS, or via the software application. The system may further provide status updates and financial transaction processing to service providers 21 and/or service consumers 23.
While the invention has been illustrated and described in detail in the drawings and foregoing description, the same is to be considered as illustrative and not restrictive in character, it being understood that only preferred embodiments have been shown and/or described and that all changes and modifications that come within the spirit of the invention are desired to be protected. The present invention may be said to essentially provide an electronic logging system for collecting data from a vehicle-based electronic logging device and mapping the data to a mobile communications device in close proximity with the electronic logging device.
The electronic logging system and method according to the present invention may be said to essentially comprise, in combination, an electronic logging device, at least one remote service provider, and at least one mobile communications device. The electronic logging device is outfitted upon a vehicle and configured to collect/record data exemplified by GPS location, engine error logs, and/or a log of vehicle drive time hours. The at least one remote service provider may preferably include at least an ELD service provider or Remote Service/ELD Provider service. The at least one service provider may also preferably provide Log Mapping Services. The essential function of the ELD service provider is to compile/aggregate data collected from the ELD or electronic logging device. The ELD service provider may also provide log mapping services or these services may be provided by a separate service provider.
The at least one remote service provider is preferably in communication with the electronic logging device for aggregating data therefrom. The at least one mobile communications device is preferably outfitted with a non-transitory, computer-implementable mobile software application. The non-transitory, computer-implementable mobile software application is configured for enabling the at least one mobile communications device to communicate with the at least one remote service provider for collecting and correlating data from both the electronic logging device and the at least one mobile communications device in a manner that allows the user to more easily arrange for repair services as required during vehicle operation.
Either the ELD service provider or a separate log mapping services provider preferably provides ELD-mapping services. The ELD-mapping services or processes provided by either the ELD service provider or the separate log mapping service provide may preferably utilize a best fit GPS mapping process with GPS data retrieved from the electronic logging device and the non-transitory, computer-implementable mobile software application. The ELD-mapping services or processes may alternatively utilize unique identifier-mapping whereby a unique identifier is retrieved from the electronic logging device via a wireless communication protocol provided by the non-transitory, computer-implementable mobile software application.
The electronic logging device or ELD is preferably in communication with the at least one remote service provider by way of a network-based communication channel and the at least one mobile communications device is in communication with the at least one remote service provider by way of a short-range wireless communication protocol. Referencing
The electronic logging system according to the present invention contemplates the inclusion of a vehicle repair bidding system. The vehicle repair bidding system extends the electronic logging system by way of or through the non-transitory, computer-implementable software application outfitted upon both the user's mobile device and a mechanic-side software application whereby a user may submit a vehicle repair request based on aggregated ELD data, user-provided imagery, video data, or audio data. The vehicle repair bidding system may be made more fully robust when used in combination with a remote vehicle diagnostic system.
The remote diagnostic system extends the electronic logging system through the non-transitory, computer-implementable software application whereby access is granted to electronic log data as mapped to a responding application for enabling diagnostics to be performed on the electronic log data. The user or vehicle driver is enabled to communicate with the diagnostic system via optional video, audio or text-based communication channels simultaneously when (temporary) access is granted to the electronic log data.
An alternative system according to the present invention provides a vehicular service request system. The vehicular service request system is operable to place localized vehicle service providers in communication with vehicle service requesters requiring vehicular service. The vehicular service request system preferably comprises at least one service provider client device as at 21, a remote service provider as at remote services 22, and at least one service requester client device as at 23. Each service provider client device 21 is preferably outfitted with a non-transitory, computer implementable software application for governing functionality of the system at the service provider side.
The remote service provider 22 is outfitted with a server-side version of the a non-transitory, computer implementable software application for maintaining a service provider database and allowing registration of service provider client devices via the non-transitory, computer implementable software application. The remote service provider provides a unique user identification and logs geographic location associated with the service provider client device during a service provider registration.
The service requester client device 23 is also outfitted with the non-transitory, computer implementable software application for enabling a vehicle service requester to initiate a vehicle service request. The system records the vehicle service request, preferably by way of a voicemail or telephone message recording, and associates the vehicle service request with a requester geographic location based on geographic location coordinates as at 25.
The remote service provider 22 is configured to then search the service provider database for local service providers (i.e. those service providers within a predetermined radius of the service requester's geographic location as based on geographic coordinates 25), and sends the vehicle service request to those local service providers. The local service providers are thereby enabled to provide competitive cost estimates for the vehicle service request and the service requester is similarly enabled to accept an offer from a select local service provider by way of the non-transitory, computer implementable software application.
The vehicular service request system may further provide certain means for providing an Estimated Time of Arrival or ETA by select service providers based on reported geographic locations of the select service providers and the service requester. The remote service provider 22 is further able to receive and correlate electronic log data as provided by an electronic logging device as outfitted upon a service request vehicle in close proximity to the service requester client device. The electronic log data may enable the local service providers to provide more comprehensive competitive cost estimates for the vehicle service request by providing the service providers with additional information taken directly from the Electronic Logging Device or ELD.
In this last regard, it will also be recalled the service requester is further enabled to provide a Vehicle Identification Number (VIN) identifier during the vehicle service request, which VIN identifier enables the local service provider(s) to provide more comprehensive competitive cost estimates for the vehicle service request. The non-transitory, computer implementable software application may be further preferably configured to provide status updates to a selected service provider (i.e. a local service provider whose bid or cost estimate and/or ETA has/have been accepted by the servicer requester) and/or the service requester on the status of the vehicle service request. This information may include financial transaction status in connection with the service request and the payment(s) therefor.
Accordingly, although the invention has been described by reference to certain preferred embodiments, and certain associated methodologies, it is not intended that the novel arrangement and methods be limited thereby, but that modifications thereof are intended to be included as falling within the broad scope and spirit of the foregoing disclosures and the appended drawings. Insofar as the description above and the accompanying drawings disclose any additional subject matter that is not within the scope of the claims below, the embodiments are not dedicated to the public and the right to file one or more applications to claim such additional embodiments is reserved.
This application claims the benefit of pending U.S. Provisional Patent Application No. 63/107,288 filed in the United States Patent and Trademark Office (USPTO) on 29 Oct. 2020, the specifications and drawings of which application are hereby incorporated by reference thereto.
| Number | Date | Country | |
|---|---|---|---|
| 63107288 | Oct 2020 | US |
