PATENT CLAIM ANALYSIS

Application Number: 15956175
Application Type: Utility
Filing Date: 2018-04
Publication Date: 2018-10
Patent Classification: ["705", "305000"]

Abstract:
A method and system of a vehicle service. Such a method and system are related to computer-assisted software for summoning servicing of a vehicle. With the software, a customer and mechanics may communicate each other to offer and accept proper vehicle services.

Claim (Index 1):
A method of providing maintenance and services for mobile or stationary robots comprising:\n creating and maintaining at least one schedule database structure in which schedule data and other associated data is stored, partitioned, and secured via tools comprising zero or more of: Passwords, PINs, biometrics, tokens, or combinations thereof; establishing a recommended maintenance and servicing schedule based on input data comprising one or more of: Manufacturer's recommended schedule, manufacturer's recalls, and other preferred maintenance and servicing schedules; storing the recommended maintenance and servicing schedule in the schedule database structure; establishing communication with the robot self-diagnostics to automatically or manually discover conditions that require maintenance; establishing communication with the user, through a user interface and communications path to provide interface capabilities that permit the user to manage the scheduling data using management tasks comprising one or more of: Manually or automatically upload, update, and store the manufacturer's suggested maintenance tasks, manually or automatically upload, update, and store product recalls, manually or automatically upload, update, and store problems from the robot's self-diagnostics, manually or automatically upload, update, and store problems discovered by the user or maintainer, manually or automatically upload, update, and store problems discovered in any other way, and to manually or automatically upload, update, and store dates, times, and locations in the schedule database structure for the maintenance to actually occur; presenting, through the user interface, suggestions for maintenance event locations produced from a user profile, which comprises one or more of: Lists of user preferences of maintainers for each task and a candidate list of local maintainers, where both lists additionally comprise zero, one, or more of: Advertisements of those businesses, their discounts, their ratings, and their presence on an automatic decline list that is maintained by the user; upon selection or entry of one or a plurality of maintainers by the user, the invention sends to the maintainers service inquiries about service topics which comprise one or more of: Available locations, available services, available times, pricing, or other important issues and policies; if there are responses from one or more maintainers, the responses are presented to the user so that zero, one, or a plurality of maintainers and actual appointment times are selected by the user; if one or a plurality of maintainers is selected, the selected one or plurality of maintainers is notified that their response is accepted; if there are maintainers that provided responses but the user declined the responses by selecting one or more responses from the list comprising: Assigning the particular service to another maintainer, actively declining the particular service, not accepting the particular service, or cancelling the particular service, the declined maintainers are automatically notified by the invention that their responses are not accepted; if there are maintainers who did not provide responses before the user finally selected the maintainers that will perform the maintenance, the outstanding inquiries to the non-responsive providers are rescinded by the invention; if there is a plurality of maintainer locations to be visited, thereby forming a schedule chain, the invention provides the user the option to optimize routes to each maintainer via travelling salesman or other route planning algorithm, while accounting for available appointment times, before finalizing selections of appointment times in the schedule chain; appointment data comprising one or more of: Actual dates and times of the accepted appointments, locations of the one or plurality of maintainers, is manually or automatically recorded or updated in the schedule data structure; the invention checks the robot's fuel, charge, or energy level to see if there is enough to complete a trip to the first maintainer; if there isn't enough fuel, the invention notifies the user and schedules a refueling or recharging stop as the first maintenance in the schedule chain; after each stop on the schedule chain, the invention further, checks the robot's fuel, charge, or energy level to see if there is enough complete a trip to the rest of the schedule chain, including the return trip; if there isn't enough fuel, the invention schedules a refueling or recharging stop as the next maintenance in the schedule chain; if a robot is not capable of automatically departing on its own or being tele-robotically, or manually driven for any reason, the invention, upon approval of the user, either notifies a robot retrieval service to schedule transport of the robot to the maintenance appointment or notifies a mobile servicing unit to schedule delivery of service to the immobile robot; the invention further comprises a communication path for further communication between the user and the robot retrieval service or mobile servicing unit, so that additional information is available for service, retrieval, or further assistance from police, fire, or ambulance services; upon arrival of the robot at an appointment location, the invention notifies user and maintainer of the arrival; upon reception of the robot by the maintainer using temporary authorizations, the maintainer is given authority to activate, repair, test, and drive the robot; a receipt documenting the reception event is produced and recorded for the user to keep in a file provided by the invention; the invention provides to the maintainer a user interface where an estimate of the work to be done further comprising estimates regarding more maintenance work which is discovered, suggested, or upsold by the maintainer is made available to the user; the user decides whether individual work tasks should be performed according to estimates; If no work is to be performed, the schedule is set to release car to either go to the next appointment, if one is scheduled in an appointment chain, or to go to the return location assigned by the user; If the user decides that any work tasks are to be performed according to the estimates, the user provides an affirmative response to some or all itemized maintenance tasks to be performed by the maintainer; for undesired tasks that are to be declined, the invention also asks the user to indicate that the undesired tasks are to be declined; the user interface and communication path provided to the maintainer enables maintainer to set schedule data, partition the data, and secure the data in the schedule data structure, wherein the schedule data further comprises: The completion status of maintenance tasks, the time and date for releasing the robot to leave the maintainer (if maintainer decides to put lien on vehicle for payment, the time is set to an indefinite time); if there is no lien on the vehicle and the vehicle is not in the process of repair, the user has the options to cancel or reschedule any or all appointments in the schedule data and to call for the vehicle to immediately return; the invention notifies user of robot status data comprising one or more of: The current completion status of the maintenance tasks, the currently scheduled time for release of the robot and departure from the maintainer, the calculated time for arrival at the next destination; at user's option, the robot's return location is set or updated to return to a place selected by the user, whether it is the user's home, workplace, phone's current GPS location, or any other user-selected location; at one or more predetermined times before departure, robot notifies the user of Departure Data comprising one or more of: Notice that the robot is about to depart its current location, the next location, estimated time of arrival at the next location; at scheduled departure time, the robot automatically departs to go to the one or more maintainers identified in its schedule chain and its progress is logged by the invention so that the robot status is tracked by the user by regularly updated GPS mapping or other interface; if the robot is a stationary robot that needs to be transported back to its location, a robot transfer service is dispatched to replace the robot; if the robot is a mobile robot, upon arrival at the next destination, the robot looks for available parking, notifies the user that it has arrived, and displays its location on map via GPS or other location service; if vehicle has returned to the user and parking is not available, the invention notifies user of the fact and requests assistance or schedules a time and place to meet the user or to wait for the user.

Metadata:
- Claim Count in Document: 41.0
- Percentile: 91.0
- Lexical Diversity: 1.48387
- Patent Class: 705.0
- Transitional Phrase Type: open
- Component Type: 1
- Foreign Priority: False
- Related Applications: ['13767469', '15445648', '13299740', '14081692', '14081783']

Analysis Scores:
- 35 USC 101 Eligibility (BERT): 0.0985571315578088
- 35 USC 102 Novelty (BERT): 0.4732159708077056
- Combined Prediction Score: 0.1360230154827985
- Mean Citation Score: 138.221758
- Max Citation Score: 145.16177
- Similarity Product: 99.70399132232428

Labels:
- Claim Label 101: 0
- Claim Label 102: 1
- Claim Label 103: 1
- Claim Label 112: 0
- Combined Label: 0
- Label 101 Adjusted: 0

Dataset: test