Patent Publication Number: US-2023138613-A1

Title: Automated Rental Systems and Methods

Description:
BACKGROUND 
     People often rent vehicles for a variety reasons. For example, the person&#39;s car may be in the shop getting repair work done. In such a scenario, the person needs a means of transportation until the person&#39;s car is finished being repaired. In another scenario, the person may be taking a long trip, and he does not desire to put the miles on his/her vehicle, so the person rents a car. 
     To rent a car, the person typically calls the rental company, e.g., Hertz, Avis, etc., ahead of time and makes a reservation. As individuals have experienced, this does not necessarily mean the rental company will have the vehicle you indicated to them on the phone call you wanted to rent. 
     When the person goes to pick up the rental vehicle, he/she must give the rental company personal information before renting the vehicle. For example, the person must give the rental company your name, your address, a copy of your driver&#39;s license, a copy of your insurance, and a credit card to have on file, even if you are not paying with a credit card. 
     After you have given all the information to the rental agent at the desk, it is time to take custody of the rental car. As indicated hereinabove, the person may or may not get the car you reserved. Further, it typically takes the rental agent time to get the person his/her rental vehicle. 
    
    
     
       DESCRIPTION OF THE DRAWINGS 
       The disclosure can be better understood referencing the following drawings. The elements of the drawings are not necessarily to scale relative to each other, emphasis instead being placed upon clearly illustrating the principles of the disclosure. Furthermore, like reference numerals designate corresponding parts throughout the views. 
         FIG.  1    is an exemplary automated rental system in accordance with an embodiment of the present disclosure. 
         FIG.  2    is an exemplary graphical user interface (GUI) that displays to a handheld device for providing personal information to a rental car server such as is shown in  FIG.  1   . 
         FIG.  3    is an exemplary login GUI for creating a password for the system such as is shown in  FIG.  1   . 
         FIG.  4    is an exemplary GUI of the system of  FIG.  1    that provides a user with the rentable vehicles in the rental company&#39;s fleet from which the user can select the vehicle he/she desires to rent. 
         FIG.  5    is an exemplary GUI of the system of  FIG.  1    that shows the vehicle the user desires to rent and comprises input boxes for indicating a date range that the user will have the car, and the GUI further shows the cost. 
         FIG.  6    is an exemplary GUI of the system of  FIG.  1    that shows the vehicle the user is renting and instructs the user to “Head to the car lot” and provides an address. 
         FIG.  7    is an exemplary GUI of the system of  FIG.  1    that comprises a “Open Gate” button that when selected opens a gate. 
         FIG.  8    is an exemplary gate for protecting a fleet of vehicles of a rental company. 
         FIG.  9    is an exemplary GUI of the system of  FIG.  1    for capturing the user&#39;s face. 
         FIG.  10    is an exemplary GUI of the system of  FIG.  1    that comprises a “Get Keys” button that when selected opens a key box. 
         FIG.  11    is an exemplary key box of the system of  FIG.  1    that protects the keys until a user is verified to obtain the keys from the key box. 
         FIG.  12    is an exemplary GUI of the system of  FIG.  1    for capturing the user&#39;s face. 
         FIG.  13    is an exemplary GUI of the system of  FIG.  1    that is displayed after the user&#39;s face is verified that comprises an “Open Exit Door” button. 
         FIG.  14    is a block diagram of an exemplary handheld used in the system such as is shown in  FIG.  1   . 
         FIG.  15    is a block diagram of an exemplary rent a car control server such as is shown in  FIG.  1   . 
         FIG.  16    is a flowchart of exemplary architecture and functionality of the system such as is shown in  FIG.  1   . 
     
    
    
     DETAILED DESCRIPTION 
     The present disclosure is a system for automating the rental of a vehicle. The system comprises a handheld device, e.g., a cellular phone or a tablet, which is used by a renter. Further, the system comprises an entrance gate and/or exit gate that protects a fleet of vehicles. Further, the system has a key box that houses the keys to a vehicle, and the box locks the keys in the key box until a verified person is granted access to the key box. 
     The handheld device performs a variety of functions. First, the renter downloads a specific application from an application store that allows the automated rental of the vehicle. Further, through the downloaded application, the handheld device communicates with a rental car server. Also, the handheld device provides a graphical user interface (GUI) that enables the renter to enter driver&#39;s license information, e.g., an image of the renter&#39;s driver&#39;s license, social security information, bank information and/or credit card information. In addition, the handheld device provides an upload of an image of the renter renting the vehicle. The renter also uploads a copy of the renter&#39;s insurance police and an image of the user&#39;s fingerprint. 
     In one embodiment, an Available Vehicle GUI is displayed to the renter, and the renter selects which car he/she desires to rent and hits a submit button. Another Confirm Price GUI provides text fields in which the renter can provide a from date to a to date, i.e., the duration the car shall be rented. Once this information is entered, the car rental server determines the cost, transmits the cost to the handheld device, and the handheld device displays a confirmation price to the renter. 
     The system additionally provides the renter directions to the rental car facility. At a gate to the rental car facility, a camera, which may be coupled to the gate, obtains a picture of the renter&#39;s face and the car rental server compares picture to the face image entered when the car was rented online. The system comprises a “Get Keys” GUI and when the renter selects the “Get Keys” pushbutton on the handheld device, the handheld device transmits a signal to a receiver on the key box, which houses the keys. Upon receiving the signal, the box opens giving the renter access to the keys so that the user may have access to the rental car. 
       FIG.  1    is an exemplary embodiment of an automated rental system  100  in accordance with the present disclosure. The automated rental system  100  comprises a handheld device  102 , a rental car server  105 , a third party verifier  105 , and an application store  107 . 
     The handheld device  102  communicates with the application store  107  over network  104 . In this regard, when a renter  108  desires to download the automated rental car application, the renter  108  downloads the automated rental car application over the network  102 , and the automated rental car application is stored on the handheld device  102 . 
     Through the automated rental car application, the handheld device  102  communicates with the rental car server  105  via a network  104 . In this regard, information entered in the automated rental car application is transmitted to the rental car server  104  over the network  104 . 
     The third party verifier  106  communicates directly with or over a network with the rental car server  105 . In this regard, the rental car server  105  transmits data indicative of the renter, e.g., date of birth, name, social security number, etc., and the third party verifier  106  verifies the renter  108 . 
       FIG.  2    shows the display  215  of the handheld device  102  displaying a Main GUI  200 . The handheld device  102  comprises a display  215  to which the GUIs of the present disclosure may be displayed. However, other types of input devices or computing devices may be used in other embodiments. The Main GUI  200  comprises text fields and upload buttons for obtaining information from the renter  108  ( FIG.  1   ). The display  215  of the handheld device  102  displays the Main GUI  200  to the renter  108  using the handheld device  102 . 
     In this regard, the Main GUI  200  comprises an upload button for the following: a) front of a driver&#39;s license upload button  201 ; back of a driver&#39;s license upload button  202 ; social security card upload button  203 ; bank information including, a routing number upload button  204  and an account number upload button  205 ; credit card information, including card number text field  206 , expiry date upload text field, security number upload text field  208 ; photograph upload button  210 ; insurance policy upload button  211 . In addition, the renter  108  may provide his/her fingerprint by selecting button  212  and a facial recognition button  213 . When the information has been entered in the system via the text fields and pushbuttons, the user selects the verify pushbutton  214 , which displays a GUI  300  described with reference to  FIG.  3    and the handheld device  102  saves the information entered in the GUI  200 . 
       FIG.  3    is a password GUI  300  displayed by the handheld device  102 . The password GUI  300  provides two text boxes. The renter  108  ( FIG.  1   ) enters his/her password in text box  300  and reenters the password again in text box  301 . When the password has been entered and reentered, the user selects the Logon pushbutton  302 . 
     Upon selection of the logon pushbutton  302 , the display  215  of the handheld device  102  displays a Cars Available GUI  400  of  FIG.  4   . The display  215  of the handheld device  102  displays a plurality of vehicles  401  that are available for rent. From the variety of vehicles displayed, the renter selects which vehicle he/she desires to rent. 
     In one embodiment, the display  215  displays all the cars available for rent. In another embodiment, the renter  108  ( FIG.  1   ) may scroll down or sideways to view additional cars for rent. 
     Once the renter  108  selects the vehicle  401  that he/she desires to rent, the renter hits the submit pushbutton  402 . Upon selecting the submit pushbutton  402 , the display  215  of the handheld device  102  displays the vehicle  504  the renter has selected in a rent GUI  500 . 
     The rent GUI  500  comprises days of rental text fields, including a from text field  501  and a to text field  502 . The renter enters in text field  501  when the renter desires to start renting the vehicle, and the renter enters in text field  502  when the renter will drop the vehicle off at the rental vehicle agency and stop renting the vehicle. 
     Once the renter enters data in the from text field  501  and the text field  502 , the application in conjunction with the rental car server  105  ( FIG.  1   ) determines a cost for the described rental and displays the cost in text field  503 . If the renter agrees with the cost, the renter selects the confirm price pushbutton  503 . Further, the rental car server  105  provides the handheld device  102  a key that indicates that the rental is verified. 
     In GUI  600 , the application directs the renter to the rental car location. Once the renter  108  arrives at the rental car location, the display  215  displays the GUI  700 , which comprises an open gate button  701 . When the renter  108  selects the open gate button  701 , the gate is ready to open. 
       FIG.  8    is a gate  800  in accordance with an embodiment of the present disclosure. The gate  800  comprises a housing  801  and an arm  802  that prevents vehicles from entering the rental car location. The gate  800  comprises a controller  803 . In one embodiment, the controller  803  comprises a camera for taking pictures of the renter  108 . 
     In another embodiment shown in  FIG.  9   , the display  215  of the handheld device  102  captures a picture of the renter  108 . Data indicative of this picture is transmitted to the controller  803 . The controller  803  comprises the image the renter  108  sent when he rented the car, so the controller  803  can compare the picture taken to the image to verify the renter  108 . 
     Once face recognition is a success as indicated by text message  901 , the display  215  of the handheld device  102  displays the GUI  1000  shown in  FIG.  10   . GUI  1000  indicates the number of the key box  1001 . The renter  108  goes to the correct key box and select the get keys pushbutton  1003 . 
       FIG.  11    is a key box  1100  in accordance with an embodiment of the present disclosure. The key box  1100  comprises a housing  1101  for housing keys to the vehicle the renter  108  rented. Coupled to the key box is a receiver  1102 . 
     When the renter  108  selects the get keys pushbutton  1003 , the application executing on the handheld device  102  transmits a signal to the receiver  1102 . The receiver  1102  recognizes the signal as valid and opens the key box  1100  so that the renter  108  can get the keys to the vehicle the renter  108  has renter. 
     Once the renter  108  is driving the vehicle he/she has rented, the renter  108  must exit the rental car location. In GUI  1200  shown in  FIG.  12   , the renter  108  again takes a picture of his face with the application running on the handheld  102 . The picture is transmitted to the controller  803  ( FIG.  8   ) of the gate  800  ( FIG.  8   ). The controller  803  compares the picture to the image captured when the renter  108  rented the car. If facial recognition is a success as indicated by text  1201 , the GUI  1300  of  FIG.  13    is displayed to the display  125  of the handheld device  102 . The renter  108  selects the open exit gate pushbutton  1301 , the gate  800  opens, and the renter  108  leaves with the rental car. 
       FIG.  14    is block diagram of an exemplary embodiment of the handheld device  102  depicted in  FIG.  1   . As shown by  FIG.  14   , the handheld device  102  comprises at least a processing unit  1401 , a network interface  1407 , an input device  1404 , an output device  1405 , and memory  1402 . Stored in memory  1402  is rent a car control logic  1403 . The rent a car control logic  1403  may be software, hardware, firmware, or a combination thereof. 
     The exemplary embodiment of the handheld device  102  depicted by  FIG.  14    comprises at least one conventional processing unit  1401 , such as a Digital Signal Processor (DSP) or a Central Processing Unit (CPU), that communicates to and drives the other elements within the handheld device  102  via a local interface  1406 , which can include at least one bus. Further, the processing unit  1401  is configured to execute instructions of software, such as the rent a car control logic  1403 . 
     The rent a car control logic  306  controls the functionality of the handheld device  102 , and the present disclosure will describe in more detail hereafter. As noted above, the rent a car control logic  1403  can be implemented in software, hardware, firmware, or any combination thereof. In an exemplary embodiment illustrated in  FIG.  14   , the rent a car control logic  1403  is implemented in software and stored in memory  1402 . 
     Note that the rent a car control logic  1403 , when implemented in software, can be stored, and transported on any computer-readable medium for use by or in connection with an instruction execution apparatus that can fetch and execute instructions. In the context of this document, a “computer-readable medium” can be any means that can contain or store a computer program for use by or in connection with an instruction execution apparatus. 
     The input device  1404  may be, for example, a touch screen, a keyboard, or a microphone. The renter  108  ( FIG.  1   ) uses one or more of the input devices  1404  to input data into the handheld device  102 . In this regard, the user may use the touch screen, the keyboard or microphone to enter data for renting a car. Also, the input device  1404  may be a camera (not shown) that receives images, e.g., a photograph of the user  108 . 
     The output device  1405 , for example, a display device (e.g., a Liquid Crystal Display (LCD)), outputs data to the user  108  ( FIG.  1   ) of the handheld device  102 . In this regard, the rent a car control logic  1406  may display to the user GUIs configured to receive information from the renter  108  and give directions to the user  108 . 
     In addition, the network interface  1407 , such as a Network Interface Card (MC), enables the handheld device  102  to communicate via the network  101  ( FIG.  1   ) with the server  105  ( FIG.  1   ). 
     In operation, the rent a car control logic  1403  displays a graphical user interface (GUI) to the output device  1405 . The GUI comprises input icons (not shown) that receive data from the renter  108  defining the renter  108 . Once the user enters this information, the rent a car control logic  1403  transmits data indicative of the user to the server  105  ( FIG.  1   ). 
     Upon receipt, the server  105  verifies the renter  108  with the third party verifier  106 . This verification ensures that the renter  108  meets the minimum criteria to rent a vehicle. 
       FIG.  15    is block diagram of an exemplary embodiment of the rental car server  105  depicted in  FIG.  1   . As shown by  FIG.  15   , the rental car server  105  comprises at least a processing unit  1501 , a network interface  1507 , an input device  1504 , an output device  1505 , and memory  1502 . Stored in memory  1502  is rent a car control server logic  1503 . The rent a car server control logic  1503  may be software, hardware, firmware, or a combination thereof. 
     The exemplary embodiment of the rental car server  105  depicted by  FIG.  15    comprises at least one conventional processing unit  1501 , such as a Digital Signal Processor (DSP) or a Central Processing Unit (CPU), that communicates to and drives the other elements within the rental car server  105  via a local interface  1506 , which can include at least one bus. Further, the processing unit  1501  is configured to execute instructions of software, such as the rent a car server control logic  1503 . 
     The rent a car server control logic  1503  controls the functionality of the rental car server  105 , and the present disclosure will describe in more detail hereafter. As noted above, the rent a car server control logic  1503  can be implemented in software, hardware, firmware, or any combination thereof. In an exemplary embodiment illustrated in  FIG.  15   , the rent a car server control logic  1503  is implemented in software and stored in memory  1502 . 
     Note that the rent a car server control logic  1503 , when implemented in software, can be stored, and transported on any computer-readable medium for use by or in connection with an instruction execution apparatus that can fetch and execute instructions. In the context of this document, a “computer-readable medium” can be any means that can contain or store a computer program for use by or in connection with an instruction execution apparatus. 
     The input device  1504  may be, for example, a touch screen, a keyboard, or a microphone. An administrator (not shown) uses one or more of the input devices  1504  to input data into the rental car server  105 . In this regard, the administrator may use the touch screen, the keyboard or microphone to enter data for setting up the system  100  or for modifying the system  100 . Also, the input device  1504  may be a camera (not shown) that receives images. 
     The output device  1505 , for example, a display device (e.g., a Liquid Crystal Display (LCD)), outputs data to the administrator of the rental car server  105 . In this regard, the rent a car server control logic  1506  may display to the administrator GUIs configured to receive information for administering the rental car server  105 . 
     In addition, the network interface  1507 , such as a Network Interface Card (MC), enables the rental car server  105  to communicate via the network  101  ( FIG.  1   ) with the handheld device  102  ( FIG.  1   ) and the third party verifier  106  ( FIG.  1   ). 
     In operation, the rent a car server control logic  1503  receives data indicative of a renter  108  ( FIG.  1   ). The rent a car server control logic  1503  transmits the data indicative of the renter  108  to the third party verifier  106 . The third party verifier  106  reviews and confirms the renter&#39;s information and intentions and thus ensures accuracy. The third party verifier  106  transmits data to the rental car server  105  indicating whether the renter  108  is a valid renter  108 . 
       FIG.  16    is a flowchart of exemplary architecture and functionality of the automated rental system  100 . 
     In step  1600 , the rent a car server control logic  1503  ( FIG.  15   ) receives a plurality of information about a potential renter  108  ( FIG.  1   ). This information may be provided by a handheld device  102  ( FIG.  1   ) over a network  104  ( FIG.  1   ). While a handheld device  102  is shown, it can be any type of computing device known in the art capable of transmitting data to the server  105 . 
     In response to receiving the data, the rent a car server control logic  1503  transmits the data to the third part verifier  106  ( FIG.  1   ). If the renter  108  is verified in step  1601 , the rent a car server control logic  1503  display a plurality of vehicles from which the renter can choose the vehicle the renter  108  desires to rent in step  1602 . 
     In step  1603 , the rent a car server control logic  1503  receives a vehicle choice from the renter  108  via the handheld device  102 . In addition, the rent a car server control logic  1503  receives data indicative of the duration of the rental time in step  1604 . 
     In step  1605 , the rent a car server control logic  1503  calculates a rental cost for the chosen vehicle for the duration of time and displays this value to the renter  108  via the handheld device  102 . 
     If the renter  108  does not confirm the price in step  1606 , the rent a car server control logic  1503  continues at step  1605 . If the renter  108  confirms the price, the rent a car server control logic  1503  directs the renter  108  to the car rental location in step  1607  where the vehicle the renter  108  is renting is located. 
     In step  1608 , the renter  108  selects the open gate button on his/her handheld device  102 . If the user has been verified, the rent a car server control logic  1503  opens the gate to the car rental location in step  1609 . 
     The rent a car server control logic  1503  directs the user to the key box (not shown) that houses the keys for the vehicle the renter  108  is renting. Using his/her handheld device  102 , the renter  108  captures his image, which is transmitting to a receiver (not shown) locking the key box in step. If the captured image matches the picture captured during the rental process in step  1610 , the rent a car server control logic  1503  displays a get keys pushbutton on the renter&#39;s handheld device  102  in step  1611 . 
     When the renter  108  selects the get keys pushbutton, the key box opens. Thus, the renter  108  can retrieve the keys to the vehicle that he/she is renting in step  1612 . 
     As the renter  108  is leaving the car rental location, at the gate, the renter  108  uses his/her handheld device  102  to capture his/her image. If the controller at the gate matches the image captured with the picture previously captured during rental of the vehicle, the rent a car server control logic  1503  displays an open exit gate button to the renter&#39;s handheld  102  in step  1613 . 
     In one embodiment, in step  1614 , the rent a car server control logic  1503  may also require additional data be entered by the renter  108  before exiting the rental car location. 
     In  1615 , the rent a car server control logic  1503  opens the exit gate.