IP Library Granted Patent US 12,518,621
Granted Patent B2
US 12,518,621 · App. 18/905,599 · Granted Jan 6, 2026

Roadside assistance system and method

Inventor: Carlos David Licona (Austin, TX)
Assignee: Carlos David Licona
G08G1/0133G06Q10/047G06Q10/063112G06Q10/20G06Q30/0282G06Q30/08G06Q40/08G06Q50/40G07C5/008G07C5/0808G07C5/0816G07C5/085G08B25/00G08G1/0967
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,518,621
App. No.
18/905,599
Granted
Jan 6, 2026
Kind
B2
Abstract

A method, computer program product, and computing system for storing instance information regarding a transportation instance of a vehicle; monitoring operation of the vehicle during the transportation instance to detect operation disruptions; detecting an operation disruption incident for the vehicle during the transportation instance; and providing one or more assistance providers with at least a portion of the instance information regarding a transportation instance.

Claims (72)

1 . A computer-implemented method, wherein the method comprises:

storing transportation instance information regarding a transportation instance of a vehicle, wherein the transportation instance information comprises: (i) duration information associated with the transportation instance, (ii) destination location information associated with the transportation instance, and (iii) starting location information associated with the transportation instance;

while the vehicle is engaged in the transportation instance, monitoring sensor data associated with the transportation instance and the vehicle, wherein the sensor data comprises (i) global positioning system (GPS) data associated with positions of the vehicle during the transportation instance, (ii) traffic data associated with one or more roadways between the starting location and the destination location of the transportation instance, (iii) acceleration data associated with acceleration of the vehicle, and (iv) velocity data associated with velocity of the vehicle;

determining whether the vehicle has experienced an operation disruption based at least in part on the sensor data, wherein determining whether the vehicle has experienced an operation disruption comprises distinguishing between whether the operation disruption is a mechanical failure or a traffic accident; and

presenting, via a graphical user interface, one or more roadside assistance providers for responding to the operation disruption based at least in part on (i) geographic proximities of the one or more roadside assistance providers to a position of the operation disruption and (ii) a determination that one or more assistance capabilities of the one or more roadside assistance providers are sufficient for the operation disruption.

2 . The computer-implemented method of claim 1 wherein the transportation instance information regarding the transportation instance of the vehicle further includes one or more of:

type information concerning the vehicle;

size information concerning the vehicle; and

weight information concerning the vehicle.

3 . The computer-implemented method of claim 1 wherein the transportation instance is all or a portion of a transportation route for the vehicle.

4 . The computer-implemented method of claim 1 wherein the vehicle is one of a passenger car, a tractor-trailer, a delivery van, a box truck, a tanker truck, or a flatbed truck.

5 . The computer-implemented method of claim 1 , further comprising:

receiving data associated with the one or more roadside assistance providers from a remote server system before presenting, via the graphical user interface, the one or more roadside assistance providers for responding to the operation disruption.

6 . The computer-implemented method of claim 1 wherein distinguishing between whether the operation disruption is a mechanical failure or a traffic accident comprises:

determining that the vehicle has experienced a mechanical failure when the velocity data indicates that the velocity of the vehicle is substantially zero while the vehicle is in a position along a roadway that is not experiencing traffic congestion; and

determining that the vehicle has experienced a traffic accident when the acceleration data indicates that the vehicle has experienced a rate of deceleration above a deceleration threshold and the velocity data indicates that the velocity of the vehicle is substantially zero.

7 . The computer-implemented method of claim 1 wherein the method further comprises:

providing information associated with the operation disruption to the one or more roadside assistance providers;

after providing the information associated with the operation disruption to the one or more roadside assistance providers, receiving data associated with one or more offers to respond to the operation disruption from the one or more roadside assistance providers; and

after receiving the data associated with the one or more offers to respond to the operation disruption from the one or more roadside assistance providers, presenting via the graphical user interface, the one or more offers.

8 . The computer-implemented method of claim 1 wherein the method further comprises:

providing information associated with the operation disruption to a liability processor.

9 . The computer-implemented method of claim 1 wherein the one or more roadside assistance providers includes one or more towing service providers.

10 . The computer-implemented method of claim 1 wherein the one or more roadside assistance providers includes one or more emergency assistance providers.

11 . A computer program product residing on a computer readable medium having a plurality of instructions stored thereon, wherein the instructions, when executed by one or more processors, cause a mobile computing device to perform operations comprising:

storing transportation instance information regarding a transportation instance of a vehicle, wherein the transportation instance information comprises: (i) duration information associated with the transportation instance, (ii) destination location information associated with the transportation instance, and (iii) starting location information associated with the transportation instance;

while the vehicle is engaged in the transportation instance, monitoring sensor data associated with the transportation instance and the vehicle, wherein the sensor data comprises (i) global positioning system (GPS) data associated with positions of the vehicle during the transportation instance, (ii) traffic data associated with one or more roadways between the starting location and the destination location of the transportation instance, (iii) acceleration data associated with acceleration of the vehicle, and (iv) velocity data associated with velocity of the vehicle;

determining whether the vehicle has experienced an operation disruption based at least in part on the sensor data, wherein determining whether the vehicle has experienced an operation disruption comprises distinguishing between whether the operation disruption is a mechanical failure or a traffic accident; and

presenting, via a graphical user interface, one or more roadside assistance providers for responding to the operation disruption based at least in part on (i) geographic proximities of the one or more roadside assistance providers to a position of the operation disruption and (ii) a determination that one or more assistance capabilities of the one or more roadside assistance providers are sufficient for the operation disruption.

12 . The computer program product of claim 11 wherein the transportation instance information regarding the transportation instance of the vehicle further includes one or more of:

type information concerning the vehicle;

size information concerning the vehicle; and

weight information concerning the vehicle.

13 . The computer program product of claim 11 wherein the transportation instance is all or a portion of a transportation route for the vehicle.

14 . The computer program product of claim 11 wherein the vehicle is one of a passenger car, a tractor-trailer, a delivery van, a box truck, a tanker truck, or a flatbed truck.

15 . The computer program product of claim 11 , further comprising:

receiving data associated with the one or more roadside assistance providers from a remote server system before presenting, via the graphical user interface, the one or more roadside assistance providers for responding to the operation disruption.

16 . The computer program product of claim 11 wherein distinguishing between whether the operation disruption is a mechanical failure or a traffic accident comprises:

determining that the vehicle has experienced a mechanical failure when the velocity data indicates that the velocity of the vehicle is substantially zero while the vehicle is in a position along a roadway that is not experiencing traffic congestion; and

determining that the vehicle has experienced a traffic accident when the acceleration data indicates that the vehicle has experienced a rate of deceleration above a deceleration threshold and the velocity data indicates that the velocity of the vehicle is substantially zero.

17 . The computer program product of claim 11 wherein the operations further comprise:

providing information associated with the operation disruption to the one or more roadside assistance providers;

after providing the information associated with the operation disruption to the one or more roadside assistance providers, receiving one or more offers to respond to the operation disruption from the one or more roadside assistance providers; and

after receiving the one or more offers to respond to the operation disruption from the one or more roadside assistance providers, presenting via the graphical user interface, the one or more offers.

18 . The computer program product of claim 11 wherein the operations further comprise:

providing information associated with the operation disruption to a liability processor.

19 . The computer program product of claim 11 wherein the one or more roadside assistance providers includes one or more towing service providers.

20 . The computer program product of claim 11 wherein the one or more roadside assistance providers includes one or more emergency assistance providers.

21 . A computing system including a processor and memory configured to perform operations comprising:

storing transportation instance information regarding a transportation instance of a vehicle, wherein the transportation instance information comprises: (i) duration information associated with the transportation instance, (ii) destination location information associated with the transportation instance, and (iii) starting location information associated with the transportation instance;

while the vehicle is engaged in the transportation instance, monitoring sensor data associated with the transportation instance and the vehicle, wherein the sensor data comprises (i) global positioning system (GPS) data associated with positions of the vehicle during the transportation instance, (ii) traffic data associated with one or more roadways between the starting location and the destination location of the transportation instance, (iii) acceleration data associated with acceleration of the vehicle, and (iv) velocity data associated with velocity of the vehicle;

determining whether the vehicle has experienced an operation disruption based at least in part on the sensor data, wherein determining whether the vehicle has experienced an operation disruption comprises distinguishing between whether the operation disruption is a mechanical failure or a traffic accident; and

presenting, via a graphical user interface, one or more roadside assistance providers for responding to the operation disruption based at least in part on (i) geographic proximities of the one or more roadside assistance providers to a position of the operation disruption and (ii) a determination that one or more assistance capabilities of the one or more roadside assistance providers are sufficient for the operation disruption.

22 . The computing system of claim 21 wherein the transportation instance information regarding the transportation instance of the vehicle further includes one or more of:

type information concerning the vehicle;

size information concerning the vehicle; and

weight information concerning the vehicle.

23 . The computing system of claim 21 wherein the transportation instance is all or a portion of a transportation route for the vehicle.

24 . The computing system of claim 21 wherein the vehicle is one of a passenger car, a tractor-trailer, a delivery van, a box truck, a tanker truck, or a flatbed truck.

25 . The computing system of claim 21 wherein the operations further comprise:

receiving data associated with the one or more roadside assistance providers from a remote server system before presenting, via the graphical user interface, the one or more roadside assistance providers for responding to the operation disruption.

26 . The computing system of claim 21 wherein distinguishing between whether the operation disruption is a mechanical failure or a traffic accident comprises:

determining that the vehicle has experienced a mechanical failure when the velocity data indicates that the velocity of the vehicle is substantially zero while the vehicle is in a position along a roadway that is not experiencing traffic congestion; and

determining that the vehicle has experienced a traffic accident when the acceleration data indicates that the vehicle has experienced a rate of deceleration above a deceleration threshold and the velocity data indicates that the velocity of the vehicle is substantially zero.

27 . The computing system of claim 21 wherein the operations further comprise:

providing information associated with the operation disruption to the one or more roadside assistance providers;

after providing the information associated with the operation disruption to the one or more roadside assistance providers, receiving one or more offers to respond to the operation disruption from the one or more roadside assistance providers; and

after receiving the one or more offers to respond to the operation disruption from the one or more roadside assistance providers, presenting via the graphical user interface, the one or more offers.

28 . The computing system of claim 21 wherein the operations further comprise:

providing information associated with the operation disruption to a liability processor.

29 . The computing system of claim 21 wherein the one or more roadside assistance providers includes one or more towing service providers.

30 . The computing system of claim 21 wherein the one or more roadside assistance providers includes one or more emergency assistance providers.

Continuity (2)
Provisional Application 63587594 · Oct 3, 2023
Related Publication 20250111708A1 · Apr 3, 2025
References Cited (77)
US 9053588B1 · Briggs et al. · 2015 [cited by applicant]
US 9282430B1 · Brandmaier et al. · 2016 [cited by applicant]
US 9520006B1 · Sankovsky et al. · 2016 [cited by applicant]
US 9672719B1 · Hollenstain et al. · 2017 [cited by applicant]
US 10124757B1 · Kerr et al. · 2018 [cited by applicant]
US 10317240B1 · Di et al. · 2019 [cited by applicant]
US 10943463B1 · Clark · 2021 [cited by applicant]
US 11012667B1 · Nodder · 2021 [cited by applicant]
US 12174027B2 · Konrardy et al. · 2024 [cited by applicant]
US 12175433B2 · Lin et al. · 2024 [cited by applicant]
US 12202504B2 · Tong et al. · 2025 [cited by applicant]
US 20100256859A1 · Leyerle et al. · 2010 [cited by applicant]
US 20110224898A1 · Scofield et al. · 2011 [cited by applicant]
US 20140206308A1 · Hatton · 2014 [cited by applicant]
US 20140277888A1 · Dastoor et al. · 2014 [cited by applicant]
US 20140309853A1 · Ricci · 2014 [cited by applicant]
US 20140357295A1 · Skomra et al. · 2014 [cited by applicant]
US 20150324720A1 · Briggs et al. · 2015 [cited by applicant]
US 20160092962A1 · Wasserman et al. · 2016 [cited by applicant]
US 20160198306A1 · Miles et al. · 2016 [cited by applicant]
US 20160269883A1 · Eswaran · 2016 [cited by examiner]
US 20170046216A1 · Stenneth · 2017 [cited by applicant]
US 20170210323A1 · Cordova et al. · 2017 [cited by applicant]
US 20180053401A1 · Martin et al. · 2018 [cited by applicant]
US 20180268305A1 · Dhondse et al. · 2018 [cited by applicant]
US 20180309592A1 · Stolfus · 2018 [cited by applicant]
US 20190243026A1 · Houchens et al. · 2019 [cited by applicant]
US 20190392367A1 · Gara et al. · 2019 [cited by applicant]
US 20200037141A1 · Hirata · 2020 [cited by examiner]
US 20200118444A1 · Wen et al. · 2020 [cited by applicant]
US 20200184591A1 · Balu et al. · 2020 [cited by applicant]
US 20200234515A1 · Gronsbell et al. · 2020 [cited by applicant]
US 20200334928A1 · Bourke · 2020 [cited by examiner]
US 20200365034A1 · Barth et al. · 2020 [cited by applicant]
US 20210026918A1 · Axelrod · 2021 [cited by applicant]
US 20210133906A1 · Lota · 2021 [cited by applicant]
US 20210197702A1 · Krishnamurthi · 2021 [cited by applicant]
US 20210272183A1 · Turnbull et al. · 2021 [cited by applicant]
US 20220051156A1 · Kumar et al. · 2022 [cited by applicant]
US 20220065643A1 · Madineni et al. · 2022 [cited by applicant]
US 20220169287A1 · Beaurepaire et al. · 2022 [cited by applicant]
US 20220170752A1 · Beaurepaire et al. · 2022 [cited by applicant]
US 20220207446A1 · Fu et al. · 2022 [cited by applicant]
US 20220215755A1 · Broaddus et al. · 2022 [cited by applicant]
US 20220374908A1 · Faga et al. · 2022 [cited by applicant]
US 20220391564A1 · Zhang et al. · 2022 [cited by applicant]
US 20230022638A1 · Avrashi et al. · 2023 [cited by applicant]
US 20230053196A1 · Brandmaier et al. · 2023 [cited by applicant]
US 20230290188A1 · Neely et al. · 2023 [cited by applicant]
US 20240025294A1 · Treharne · 2024 [cited by applicant]
US 20240253651A1 · Mcnew et al. · 2024 [cited by applicant]
US 20240257146A1 · Valas et al. · 2024 [cited by applicant]
US 20240257166A1 · Valas et al. · 2024 [cited by applicant]
US 20250029026A1 · Telpaz et al. · 2025 [cited by applicant]
US 20250076881A1 · Nguyen et al. · 2025 [cited by applicant]
US 20250078587A1 · Desai et al. · 2025 [cited by applicant]
US 20250087095A1 · Wen et al. · 2025 [cited by applicant]
WO 2015095235A1 · 2015 [cited by applicant]
WO 2020060912A1 · 2020 [cited by applicant]
Cheryl Jensen. Special to the Tribune. (Feb. 26, 1998). At Your Service GM Expands Onstar Emergency System Beyond Cadillac: [North Sports Final edition]. Chicago Tribune (Year: 1998). [cited by applicant]
Lang, B. (Oct. 28, 2000). Smart Cars; GM's OnStar system growing in popularity: [SA edition]. The Post and Courier (Year: 2000). [cited by applicant]
Mzila, P., A Service Supplier Database for Location-Based Mobile Commerce, Jun. 1, 2007, 27th International Conference on Distributed Computing Systems Workshops (ICDCSW'07) (Year: 2007). [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 18/905,659 on Dec. 13, 2024. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 18/905,676 on Dec. 20, 2024. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 18/905,693 on Dec. 2, 2024. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 18/905,723 on Dec. 5, 2024. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 18/905,743 on Dec. 13, 2024. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 18/905,785 on Dec. 3, 2024. [cited by applicant]
Owram, K. (Dec. 10, 2014). Towing startups take aim at CAA with GPS apps; ‘ripe for revolution’. National Post (Year: 2014). [cited by applicant]
S. K. Datta and C. Bonnet, “An IoT framework for intelligent roadside assistance system,” 2017 IEEE International Conference on Consumer Electronics—Taiwan (ICCE-TW), Taipei, Taiwan, 2017, pp. 353-354, doi: 10.1109/ICCE… [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 18/905,659 on Apr. 1, 2025. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 18/905,676 on Jun. 4, 2025. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 18/905,693 on Jun. 10, 2025. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 18/905,723 on Jul. 2, 2025. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 18/905,743 on Mar. 28, 2025. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 18/905,785 on Apr. 14, 2025. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 18/905,723 on Mar. 20, 2025. [cited by applicant]