WO2018017102A1 - Chariots de véhicule à déploiement automatique - Google Patents

Chariots de véhicule à déploiement automatique Download PDF

Info

Publication number
WO2018017102A1
WO2018017102A1 PCT/US2016/043362 US2016043362W WO2018017102A1 WO 2018017102 A1 WO2018017102 A1 WO 2018017102A1 US 2016043362 W US2016043362 W US 2016043362W WO 2018017102 A1 WO2018017102 A1 WO 2018017102A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
actuator
processor
cart
control signal
Prior art date
Application number
PCT/US2016/043362
Other languages
English (en)
Inventor
Edgar Ulises JIMENEZ LOPEZ
Ramiro Chable Hernandez
Gustavo Aar VAZQUEZ PEREZ
Original Assignee
Ford Global Technologies, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ford Global Technologies, Llc filed Critical Ford Global Technologies, Llc
Priority to PCT/US2016/043362 priority Critical patent/WO2018017102A1/fr
Publication of WO2018017102A1 publication Critical patent/WO2018017102A1/fr

Links

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
    • B62B—HAND-PROPELLED VEHICLES, e.g. HAND CARTS OR PERAMBULATORS; SLEDGES
    • B62B3/00—Hand carts having more than one axis carrying transport wheels; Steering devices therefor; Equipment therefor
    • B62B3/02—Hand carts having more than one axis carrying transport wheels; Steering devices therefor; Equipment therefor involving parts being adjustable, collapsible, attachable, detachable or convertible
    • B62B3/027—Hand carts having more than one axis carrying transport wheels; Steering devices therefor; Equipment therefor involving parts being adjustable, collapsible, attachable, detachable or convertible collapsible shopping trolleys
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
    • B62B—HAND-PROPELLED VEHICLES, e.g. HAND CARTS OR PERAMBULATORS; SLEDGES
    • B62B5/00—Accessories or details specially adapted for hand carts
    • B62B5/0003—Adaptations for loading in or on a vehicle
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
    • B62B—HAND-PROPELLED VEHICLES, e.g. HAND CARTS OR PERAMBULATORS; SLEDGES
    • B62B5/00—Accessories or details specially adapted for hand carts
    • B62B5/02—Accessories or details specially adapted for hand carts providing for travelling up or down a flight of stairs
    • B62B5/026—Accessories or details specially adapted for hand carts providing for travelling up or down a flight of stairs with spiders or adapted wheels
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
    • B62D—MOTOR VEHICLES; TRAILERS
    • B62D57/00—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track
    • B62D57/02—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track with ground-engaging propulsion means, e.g. walking members
    • B62D57/024—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track with ground-engaging propulsion means, e.g. walking members specially adapted for moving on inclined or vertical surfaces
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
    • B62D—MOTOR VEHICLES; TRAILERS
    • B62D57/00—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track
    • B62D57/02—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track with ground-engaging propulsion means, e.g. walking members
    • B62D57/028—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track with ground-engaging propulsion means, e.g. walking members having wheels and mechanical legs
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
    • B62D—MOTOR VEHICLES; TRAILERS
    • B62D57/00—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track
    • B62D57/02—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track with ground-engaging propulsion means, e.g. walking members
    • B62D57/032—Vehicles characterised by having other propulsion or other ground- engaging means than wheels or endless track, alone or in addition to wheels or endless track with ground-engaging propulsion means, e.g. walking members with alternately or sequentially lifted supporting base and legs; with alternately or sequentially lifted feet or skid
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • This disclosure relates generally to vehicle carts and, more particularly, to automatically deployable vehicle carts.
  • Vehicle carts assist individuals in transporting cargo (e.g., packages, bags, boxes, groceries, etc.) from a first location (e.g., a grocery store) to a vehicle, and/or from the vehicle to a second location (e.g., a residence).
  • cargo e.g., packages, bags, boxes, groceries, etc.
  • a first location e.g., a grocery store
  • a second location e.g., a residence
  • Vehicle carts are commonly configured to be stowable in a cargo compartment (e.g., a trunk) of a vehicle. Such vehicle carts require manual intervention to deploy the vehicle cart from the cargo compartment of the vehicle.
  • FIG. 1 illustrates an example vehicle cart constructed in accordance with the teachings of this disclosure shown in an example environment of use.
  • FIG. 2 is a block diagram of the example vehicle cart of FIG. 1.
  • FIG. 3 is a perspective view of the example vehicle cart of FIGS. 1 and 2 in a deployed configuration.
  • FIG. 4 is a perspective view of another example vehicle cart in a deployed configuration.
  • FIG. 5 a block diagram of the example vehicle of FIG. 1.
  • FIG. 6 is a perspective view of the example cargo compartment of the example vehicle of FIGS. 1 and 5.
  • FIG. 7 is a block diagram of the example remote control device of FIG. 1.
  • FIG. 8 is a block diagram of the example mobile device of FIG. 1.
  • FIG. 9 is a side view of the example vehicle cart of FIGS. 1-3 in an example stowed configuration relative to the example cargo compartment of the example vehicle of FIGS. 1, 5 and 6.
  • FIG. 10 is a side view of the example vehicle cart of FIGS. 1-3 in a first example partially-deployed configuration relative to the example cargo compartment of the example vehicle of FIGS. 1, 5 and 6.
  • FIG. 11 is a side view of the example vehicle cart of FIGS. 1-3 in a second example partially-deployed configuration relative to the example cargo compartment of the example vehicle of FIGS. 1, 5 and 6.
  • FIG. 12 is a side view of the example vehicle cart of FIGS. 1-3 in a third example partially-deployed configuration relative to the example cargo compartment of the example vehicle of FIGS. 1, 5 and 6.
  • FIG. 13 is a side view of the example vehicle cart of FIGS. 1-3 in an example deployed configuration relative to the example cargo compartment of the example vehicle of FIGS. 1, 5 and 6.
  • FIG. 14 is a flowchart representative of an example method that may be executed at the example vehicle cart of FIGS. 1-3 to automatically deploy the example vehicle cart from the example cargo compartment of the example vehicle of FIGS. 1, 5 and 6.
  • FIG. 15 is a flowchart representative of an example method that may be executed at the example vehicle cart of FIGS. 1-3 to automatically maneuver the vehicle cart toward the example vehicle of FIGS. 1, 5 and 6, the example remote control device of FIGS. 1 and 7, and/or the example mobile device of FIGS. 1 and 8.
  • FIG. 16 is a flowchart representative of an example method that may be executed at the example vehicle cart of FIGS. 1-3 to provide a shopping itinerary.
  • FIG. 17 is a flowchart representative of an example method that may be executed at the example vehicle of FIGS. 1, 5 and 6 to automatically deploy the example vehicle cart of FIGS. 1-3 from the example cargo compartment of the example vehicle.
  • FIG. 18 is an example processor platform capable of executing instructions to implement the methods of FIGS. 14-16 and the example vehicle cart of FIGS. 1-3.
  • FIG. 19 is an example processor platform capable of executing instructions to implement the methods of FIG. 17 and the example vehicle of FIGS. 1, 5 and 6.
  • FIG. 1 illustrates an example vehicle cart 102 constructed in accordance with the teachings of this disclosure shown in an example environment 100 of use.
  • the vehicle cart 102 is stowable in an example vehicle 104 and, more specifically, is stowable in an example cargo compartment 106 of the vehicle 104.
  • the vehicle cart 102 is automatically deployable from the cargo compartment 106 of the vehicle 104.
  • the vehicle cart 102 is automatically deployed from the cargo compartment 106 of the vehicle 104 in response to receiving a control signal transmitted by an example remote control device 108 and/or an example mobile device 110.
  • the vehicle cart 102 is automatically deployed from the cargo compartment 106 of the vehicle 104 in response to receiving a control signal generated via a user interface (not shown) of the vehicle cart 102.
  • the vehicle cart 102 is maneuverable to and/or from various locations.
  • the vehicle cart 102 is maneuverable between the vehicle 104 and an example residence 1 12, an example first store 114, an example second store 116, and an example third store 118.
  • the residence 1 12 includes example stairs 120 that the vehicle cart 102 may encounter in connection with entering, exiting and/or maneuvering within the residence 1 12.
  • movement of the vehicle cart 102 to and/or from the residence 1 12, the first store 114, the second store 1 16 and/or the third store 1 18 may occur automatically (e.g., in response to one or more control signal(s) and/or location signal(s) received by the vehicle cart 102) or manually (e.g., in response to a user pushing, pulling and/or steering the vehicle cart 102).
  • the vehicle cart 102 communicates with the example mobile device 110 to exchange information regarding one or more item(s) placed within, or to be placed within, the vehicle cart 102.
  • the vehicle cart 102 may obtain and/or access data corresponding to a shopping list from the mobile device 1 10, and may enable the shopping list to be updated as items identified on the list are added to the vehicle cart 102.
  • the vehicle cart 102 also communicates with one or more of the vehicle 104, the remote control device 108 and/or the mobile device 110 to exchange information regarding one or more of the respective locations of the vehicle cart 102, the vehicle 104, the remote control device 108 and/or the mobile device 110.
  • the vehicle cart 102 may determine its own location based on one or more signal(s) collected, acquired and/or received by the vehicle cart 102 from one or more example Global
  • GPS Positioning System
  • the vehicle 104, the remote control device 108 and/or the mobile device 110 is/are able to identify its/their respective location(s) in a similar manner.
  • the vehicle 104, the remote control device 108 and/or the mobile device 110 may share its/their respective location(s) with the vehicle cart 102 and vice-versa, such that a distance and/or a route between the vehicle cart 102 and one or more of the vehicle 104, the remote control device 108 and/or the mobile device 110 may be determined by and/or communicated to the vehicle cart 102.
  • Such information enables the vehicle cart 102 to automatically maneuver itself to a destination location corresponding to the current location of the vehicle 104, the remote control device 108 or the mobile device 110.
  • FIG. 2 is a block diagram of the example vehicle cart 102 of FIG. 1.
  • the vehicle cart 102 includes an example radio receiver 202, an example radio transmitter 204, an example GPS receiver 206, an example user interface 208, example front legs 210, 212, example front leg actuators 214, 216, example front wheels 218, 220, example front wheel actuators 222, 224, example front wheel contact sensors 226, 228, example rear legs 230, 232, example rear leg actuators 234, 236, example rear wheels 238, 240, example rear wheel actuators 242, 244, example rear wheel contact sensors 246, 248, an example obstacle sensor 250, an example level sensor 252, an example processor 254, an example memory 256, and an example battery 258.
  • other example radio receiver 202 includes an example radio receiver 202, an example radio transmitter 204, an example GPS receiver 206, an example user interface 208, example front legs 210, 212, example front leg actuators 214, 216, example front wheels 218, 220, example front wheel actuators 222, 224, example
  • implementations of the vehicle cart 102 may include fewer or additional structures in accordance with the teachings of this disclosure.
  • 1 and 2 may be of any size(s), shape(s) and or configuration(s) that enable(s) the vehicle cart 102 to be stowed within and automatically deployed from a cargo compartment of a vehicle (e.g., the cargo compartment 106 of the vehicle 104 of FIG. 1).
  • the example radio receiver 202 of FIG. 2 collects, acquires and/or receives one or more signal(s) from the vehicle 104, the remote control device 108, and/or the mobile device 110 of FIG. 1.
  • the signal(s) received by the radio receiver 202 are communicated via the cellular base station(s) 124 and/or the wireless access point(s) 126 of FIG. 1.
  • the radio receiver 202 may receive a control signal from the remote control device 108 and/or the mobile device 110 in association with the vehicle cart 102 being automatically deployed from the vehicle 104 of FIG. 1.
  • the radio receiver 202 may receive data from the mobile device 110 corresponding to a shopping list.
  • the radio receiver 202 may receive data corresponding to a current location of one or more of the vehicle 104, the remote control device 108, and/or the mobile device 110. Data identified and/or derived from the signal(s) collected and/or received by the radio receiver 202 may be stored in a computer-readable storage medium such as the example memory 256 described below.
  • the example radio transmitter 204 of FIG. 2 transmits one or more signal(s) to one or more of the vehicle 104, the remote control device 108, and/or the mobile device 1 10 of FIG. 1.
  • the signal(s) transmitted by the radio transmitter 204 are communicated via the cellular base station(s) 124 and/or the wireless access point(s) 126 of FIG. 1.
  • the radio transmitter 204 may transmit data corresponding to a current location of the vehicle cart 102. Data corresponding to the signal (s) to be transmitted by the radio transmitter 204 may be stored in a computer-readable storage medium such as the example memory 256 described below.
  • the GPS receiver 2 collects, acquires and/or receives one or more signal(s) from the GPS satellite(s) 122 of FIG. 1.
  • the signal(s) received by the GPS receiver may include information from which the current location of the vehicle cart 102 may be identified and/or derived, including for example, the current latitude and longitude of the vehicle cart 102.
  • Data identified and/or derived from the signal(s) collected and/or received by the GPS receiver 206 may be stored in a computer-readable storage medium such as the example memory 256 described below.
  • the example user interface 208 of FIG. 2 facilitates interactions and/or
  • the user interface 208 includes one or more input device(s) 260 via which the user may input information and/or data to the vehicle cart 102.
  • the user interface 208 may include a button, a microphone, and/or a touchscreen that enable(s) the user to convey data and/or commands to the vehicle cart 102.
  • the user interface 208 also includes one or more output device(s) 262 via which the processor 254 of the vehicle cart 102 presents information and/or data in visual and/or audible form to the user.
  • the user interface 208 may include a light emitting diode, a touchscreen, and/or a liquid crystal display for presenting visual information, and/or a speaker for presenting audible information.
  • Data and/or information that is presented and/or received via the user interface 208 may be of any type, form and/or format, and may be stored in a computer-readable storage medium such as the example memory 256 described below.
  • the example front legs 210, 212 of FIG. 2 are coupled (either directly or indirectly) to the vehicle cart 102.
  • the front legs 210, 212 extend downward from and/or retract upward toward the vehicle cart 102, as further described below in connection with FIGS. 3, 12 and 13.
  • the front legs 210, 212 may be implemented as one or more articulated and/or jointed member(s) that pivot relative to one another and/or relative to the vehicle cart 102.
  • the front legs 210, 212 may be implemented as one or more telescoping member(s) that extend and/or retract relative to one another and/or relative to the vehicle cart 102.
  • the vehicle cart 102 may include any number of front legs 210, 212, including a single front leg.
  • respective ones of the front legs 210, 212 may be coupled together such that movement of any one of the front legs 210, 212 results in corresponding movement to the other ones of the front legs 210, 212.
  • respective ones of the front legs 210, 212 may be independently movable and/or actuatable such that movement of any one of the front legs 210, 212 has no bearing and/or impact on movement of any of the other ones of the front legs 210, 212.
  • the example front leg actuators 214, 216 of FIG. 2 are operatively coupled to corresponding ones of the front legs 210, 212 of FIG. 2 to control the movement and/or actuation thereof. More specifically, in response to one or more control signal(s) and/or instruction(s) received by one or more of the front leg actuator(s) 214, 216 from the processor 254 of FIG. 2, respective ones of the front leg actuators 214, 216 move and/or actuate members of corresponding ones of the front legs 210, 212.
  • Movement and/or actuation of a front leg (e.g., front leg 210) by a corresponding front leg actuator (e.g., front leg actuator 214) causes the member(s) of the front leg to extend and/or retract relative to one another and/or relative to the vehicle cart 102.
  • the front leg actuators 214, 216 of FIG. 2 may be implemented as one or more pneumatic or hydraulic actuator(s) to control the movement and/or actuation of the front legs 210, 212 based on pressurized air and/or pressurized fluid supplied to the actuator(s) in response to one or more control signal(s) provided by the processor 254 of FIG. 2.
  • the front leg actuators 214, 216 may additionally and/or alternatively be implemented as one or more electric motor(s) to control the movement and/or actuation of the front legs 210, 212 based on one or more control signal(s) provided to the front leg actuators 214, 216 by the processor 254.
  • the vehicle cart 102 may include any number of front leg actuators 214, 216, including a single front leg actuator.
  • respective ones of the front legs 210, 212 may be coupled together such that movement of all of the front legs 210, 212 may be controlled by a single front leg actuator.
  • the number of front leg actuators 214, 216 corresponds to the number of front legs 210, 212, such that each front leg (e.g. front leg 210) is independently controlled by a corresponding front leg actuator (e.g., front leg actuator 214).
  • the example front wheels 218, 220 of FIG. 2 are respectively coupled (either directly or indirectly) to corresponding ones of the front legs 210, 212 of FIG. 2.
  • the front wheels 218, 220 respectively move upward and/or downward relative to the vehicle cart 102 as corresponding ones of the front legs 210, 212 extend downward from and/or retract upward toward the vehicle cart 102, as further described below in connection with FIGS. 3, 12 and 13.
  • the front wheels 218, 220 of the vehicle cart 102 may be of any size, shape and/or configuration.
  • the front wheels 218, 220 of the vehicle cart 102 may be coupled together (e.g., by a wheel axle) such that movement of any one of the front wheels 218, 220 results in corresponding movement of the other ones of the front wheels 218, 220.
  • the front wheels 218, 220 of the vehicle cart 102 may be independently movable and/or actuatable such that movement of any one of the front wheels 218, 220 has no bearing and/or impact on movement of any of the other ones of the front wheels 218, 220.
  • the vehicle cart 102 may include any number of front wheels 218, 220, including a single front wheel.
  • the number of front wheels 218, 220 of the vehicle cart 102 may differ from the number of front legs 210, 212 of the vehicle cart 102.
  • each front leg of the vehicle cart 102 may be coupled to two front wheels of the vehicle cart 102.
  • the number of front wheels 218, 220 of the vehicle cart 102 corresponds to the number of front legs 210, 212 of the vehicle cart, such that each front leg (e.g. front leg 210) is coupled to a single front wheel (e.g., front wheel 218).
  • the example front wheel actuators 222, 224 of FIG. 2 are operatively coupled to corresponding ones of the front wheels 218, 220 of FIG. 2 to control the movement and/or actuation thereof. More specifically, in response to one or more control signal(s) and/or instruction(s) received by one or more of the front wheel actuator(s) 222, 224 from the processor 254 of FIG. 2, respective ones of the front wheel actuators 222, 224 move and/or actuate corresponding ones of the front wheels 218, 220.
  • Movement and/or actuation of a front wheel (e.g., front wheel 218) by a corresponding front wheel actuator (e.g., front wheel actuator 222) causes the front wheel to rotate in a first direction (e.g., clockwise) or a second direction (e.g., counter-clockwise) opposite of the first direction.
  • the front wheel actuators 222, 224 may be implemented as one or more electric motor(s) to control the movement and/or actuation of the front wheels 218, 220 based on one or more control signal(s) provided to the front wheel actuators 222, 224 by the processor 254.
  • the vehicle cart 102 may include any number of front wheel actuators 222, 224, including a single front wheel actuator.
  • respective ones of the front wheels 218, 220 may be coupled together such that movement of all of the front wheels 218, 220 may be controlled by a single front wheel actuator.
  • the number of front wheel actuators 222, 224 corresponds to the number of front wheels 218, 220, such that each front wheel (e.g. front wheel 218) is independently controlled by a corresponding front wheel actuator (e.g., front wheel actuator 222).
  • the example front wheel contact sensors 226, 228 of FIG. 2 may respectively be implemented as one or more strain gauge(s) mounted on and/or operatively coupled to corresponding ones of the front wheel(s) 218, 220 and/or front leg(s) 210, 212 of the vehicle cart 102.
  • each front wheel contact sensor 226, 228 senses, measures and/or detects a force applied to the corresponding front wheel 218, 220 and/or front leg 210, 212 of the vehicle cart 102.
  • Different force values sensed, measured and/or detected by the front wheel contact sensors 226, 228 correspond to different forces being applied to the corresponding front wheels 218, 220 and/or front legs 210, 212 of the vehicle cart 102.
  • the front wheel contact sensor 226, 228 detects whether the corresponding front wheel 218, 220 is in contact with an underlying surface (e.g., the ground, a cargo compartment of a vehicle within which the vehicle cart is stored, etc.). For example, if the force value sensed, measured and/or detected by the front wheel contact sensor 226, 228 is increasing as the corresponding front leg 210, 212 is extending (a more recent measurement is of a larger force value than a prior measurement), the corresponding front wheel 218, 220 of the vehicle cart 102 is in contact with the underlying surface.
  • an underlying surface e.g., the ground, a cargo compartment of a vehicle within which the vehicle cart is stored, etc.
  • the corresponding front wheel 218, 220 of the vehicle cart 102 is not in contact with the underlying surface.
  • the vehicle cart 102 may include any number of front wheel contact sensors 226, 228, including a single front wheel contact sensor.
  • respective ones of the front wheels 218, 220 may be coupled together such that contact of all of the front wheels 218, 220 with an underlying surface may be sensed, measured and/or detected by a single front wheel contact sensor.
  • the number of front wheel contact sensors 226, 228 corresponds to the number of front wheels 218, 220, such that contact of each front wheel (e.g., front wheel 218) with an underlying surface is independently detectable by a corresponding front wheel contact sensor (e.g., front wheel contact sensor 226).
  • the example rear legs 230, 232 of FIG. 2 are coupled (either directly or indirectly) to the vehicle cart 102.
  • the rear legs 230, 232 extend downward from and/or retract upward toward the vehicle cart 102, as further described below in connection with FIGS. 3, 10 and 11.
  • the rear legs 230, 232 may be implemented as one or more articulated and/or jointed member(s) that pivot relative to one another and/or relative to the vehicle cart 102.
  • the rear legs 230, 232 may be implemented as one or more telescoping member(s) that extend and/or retract relative to one another and/or relative to the vehicle cart 102.
  • the vehicle cart 102 may include any number of rear legs 230, 232, including a single rear leg.
  • respective ones of the rear legs 230, 232 may be coupled together such that movement of any one of the rear legs 230, 232 results in corresponding movement to the other ones of the rear legs 230, 232.
  • respective ones of the rear legs 230, 232 may be independently movable and/or actuatable such that movement of any one of the rear legs 230, 232 has no bearing and/or impact on movement of any of the other ones of the rear legs 230, 232.
  • the example rear leg actuators 234, 236 of FIG. 2 are operatively coupled to corresponding ones of the rear legs 230, 232 of FIG. 2 to control the movement and/or actuation thereof. More specifically, in response to one or more control signal(s) and/or instruction(s) received by one or more of the rear leg actuator(s) 234, 236 from the processor 254 of FIG. 2, respective ones of the rear leg actuators 234, 236 move and/or actuate members of corresponding ones of the rear legs 230, 232.
  • Movement and/or actuation of a rear leg (e.g., rear leg 230) by a corresponding rear leg actuator (e.g., rear leg actuator 234) causes the member(s) of the rear leg to extend and/or retract relative to one another and/or relative to the vehicle cart 102.
  • the rear leg actuators 234, 236 of FIG. 2 may be
  • the rear leg actuators 234, 236 may additionally and/or alternatively be implemented as one or more electric motor(s) to control the movement and/or actuation of the rear legs 230, 232 based on one or more control signal(s) provided to the rear leg actuators 234, 236 by the processor 254.
  • the vehicle cart 102 may include any number of rear leg actuators 234, 236, including a single rear leg actuator.
  • the vehicle cart 102 includes two or more rear legs 230, 232, respective ones of the rear legs 230, 232 may be coupled together such that movement of all of the rear legs 230, 232 may be controlled by a single rear leg actuator.
  • the number of rear leg actuators 234, 236 corresponds to the number of rear legs 230, 232, such that each rear leg (e.g. rear leg 230) is independently controlled by a corresponding rear leg actuator (e.g., rear leg actuator 234).
  • the example rear wheels 238, 240 of FIG. 2 are respectively coupled (either directly or indirectly) to corresponding ones of the rear legs 230, 232 of FIG. 2.
  • the rear wheels 238, 240 respectively move upward and/or downward relative to the vehicle cart 102 as corresponding ones of the rear legs 230, 232 extend downward from and/or retract upward toward the vehicle cart 102, as further described below in connection with FIGS. 3, 10 and 11.
  • the rear wheels 238, 240 of the vehicle cart 102 may be of any size, shape and/or configuration.
  • the rear wheels 238, 240 of the vehicle cart 102 may be coupled together (e.g., by a wheel axle) such that movement of any one of the rear wheels 238, 240 results in corresponding movement of the other ones of the rear wheels 238, 240.
  • the rear wheels 238, 240 of the vehicle cart 102 may be independently movable and/or actuatable such that movement of any one of the rear wheels 238, 240 has no bearing and/or impact on movement of any of the other ones of the rear wheels 238, 240.
  • the vehicle cart 102 may include any number of rear wheels 238, 240, including a single rear wheel.
  • the number of rear wheels 238, 240 of the vehicle cart 102 may differ from the number of rear legs 230, 232 of the vehicle cart 102.
  • each rear leg of the vehicle cart 102 may be coupled to two rear wheels of the vehicle cart 102.
  • the number of rear wheels 238, 240 of the vehicle cart 102 corresponds to the number of rear legs 230, 232 of the vehicle cart, such that each rear leg (e.g. rear leg 230) is coupled to a single rear wheel (e.g., rear wheel 238).
  • the example rear wheel actuators 242, 244 of FIG. 2 are operatively coupled to corresponding ones of the rear wheels 238, 240 of FIG. 2 to control the movement and/or actuation thereof. More specifically, in response to one or more control signal(s) and/or instruction(s) received by one or more of the rear wheel actuator(s) 242, 244 from the processor 254 of FIG. 2, respective ones of the rear wheel actuators 242, 244 move and/or actuate corresponding ones of the rear wheels 238, 240.
  • Movement and/or actuation of a rear wheel (e.g., rear wheel 238) by a corresponding rear wheel actuator (e.g., rear wheel actuator 242) causes the rear wheel to rotate in a first direction (e.g., clockwise) or a second direction (e.g., counter-clockwise) opposite of the first direction.
  • the rear wheel actuators 242, 244 may be implemented as one or more electric motor(s) to control the movement and/or actuation of the rear wheels 238, 240 based on one or more control signal(s) provided to the rear wheel actuators 242, 244 by the processor 254.
  • the vehicle cart 102 may include any number of rear wheel actuators 242, 244, including a single rear wheel actuator.
  • respective ones of the rear wheels 238, 240 may be coupled together such that movement of all of the rear wheels 238, 240 may be controlled by a single rear wheel actuator.
  • the number of rear wheel actuators 242, 244 corresponds to the number of rear wheels 238, 240, such that each rear wheel (e.g. rear wheel 238) is independently controlled by a
  • rear wheel actuator e.g., rear wheel actuator 242.
  • the example rear wheel contact sensors 246, 248 of FIG. 2 may respectively be implemented as one or more strain gauge(s) mounted on and/or operatively coupled to corresponding ones of the rear wheel(s) 238, 240 and/or rear leg(s) 230, 232 of the vehicle cart 102.
  • each rear wheel contact sensor 246, 248 senses, measures and/or detects a force applied to the corresponding rear wheel 238, 240 and/or rear leg 230, 232 of the vehicle cart 102.
  • Different force values sensed, measured and/or detected by the rear wheel contact sensors 246, 248 correspond to different forces being applied to the corresponding rear wheels 238, 240 and/or rear legs 230, 232 of the vehicle cart 102.
  • the rear wheel contact sensor 246, 248 detects whether the corresponding rear wheel 238, 240 is in contact with an underlying surface (e.g., the ground, a cargo compartment of a vehicle within which the vehicle cart is stored, etc.). For example, if the force value sensed, measured and/or detected by the rear wheel contact sensor 246, 248 is increasing as the corresponding rear leg 230, 232 is extending (a more recent measurement is of a larger force value than a prior measurement), the corresponding rear wheel 238, 240 of the vehicle cart 102 is in contact with the underlying surface. If the force value sensed, measured and/or detected by the rear wheel contact sensor 246, 248 is not changing as the corresponding rear leg 230, 232 is extending (a more recent measurement is of the same force value as a prior measurement), the
  • the vehicle cart 102 may include any number of rear wheel contact sensors 246, 248, including a single rear wheel contact sensor.
  • respective ones of the rear wheels 238, 240 may be coupled together such that contact of all of the rear wheels 238, 240 with an underlying surface may be sensed, measured and/or detected by a single rear wheel contact sensor.
  • the number of rear wheel contact sensors 246, 248 corresponds to the number of rear wheels 238, 240, such that contact of each rear wheel (e.g., rear wheel 238) with an underlying surface is independently detectable by a corresponding rear wheel contact sensor (e.g., rear wheel contact sensor 246).
  • the example obstacle sensor 250 of FIG. 2 may be implemented as an infrared proximity sensor.
  • the obstacle sensor 250 emits an infrared beam of electromagnetic radiation in a direction away from the vehicle cart 102 and senses, measures and/or detects a reflected signal associated with the emitted beam being returned to the obstacle sensor 250.
  • the reflected signal may, for example, have reflected from an obstacle (e.g., a curb, a step, a flight of stairs, a wall, etc.) to be encountered by the vehicle cart 102.
  • the obstacle sensor 250 correlates and/or translates a value derived from the reflected signal (e.g., a travel time associated with the signal) to a distance between the vehicle cart 102 and the obstacle.
  • Different values derived from the reflected signal sensed, measured and/or detected by the obstacle sensor 250 correspond to different distances between the vehicle cart 102 and the obstacle.
  • the obstacle sensor 250 determines the distance between the vehicle cart 102 and the obstacle. For example, if the travel time associated with the reflected signal is decreasing (a more recent measurement is of a shorter duration than a prior measurement), the vehicle cart 102 is moving closer to the obstacle.
  • the vehicle cart 102 may include any number of obstacle sensors 250.
  • an array or two or more obstacle sensors 250 may be positioned about a perimeter of the vehicle cart 102 to enable the vehicle cart 102 to detect obstacles being approached by the vehicle cart 102 from multiple directions.
  • the example level sensor 252 of FIG. 2 may be implemented as a gyroscope.
  • the level sensor 252 senses, measures and/or detects a rotational orientation of the vehicle cart 102.
  • Different rotational orientation values sensed, measured and/or detected by the level sensor 252 correspond to different rotational orientations and/or degrees of levelness of the vehicle cart 102.
  • the level sensor 252 detects whether the vehicle cart 102 is level.
  • the example processor 254 of FIG. 2 is implemented by a semiconductor device such as a microprocessor, controller or microcontroller.
  • the processor 254 may be a silicon based hardware device.
  • the processor 254 manages and/or controls the operation of the vehicle cart 102 based on data, information and/or one or more control signal(s) obtained and/or accessed by the processor 254 from one or more of the radio receiver 202, the GPS receiver 206, the user interface 208, the front wheel contact sensor(s) 226, 228, the rear wheel contact sensor(s) 246, 248, the obstacle sensor 250, the level sensor 252 and/or the memory 256, and/or based on data, information and/or one or more control signal(s) provided by the processor 254 to one or more of the radio transmitter 204, the user interface 208, the front leg actuator(s) 214, 216, the front wheel actuator(s) 222, 224, the rear leg actuator(s) 234, 236 and/or the rear wheel actuator(s) 242, 244.
  • the processor 254 of FIG. 2 Based on one or more deployment control signal(s) and/or deployment command(s) received via the radio receiver 202 and/or via the user interface 208 of the vehicle cart 102, the processor 254 of FIG. 2 provides one or more control signal(s) to one or more of the front leg actuator(s) 214, 216, the front wheel actuator(s) 222, 224, the rear leg actuator(s) 234, 236 and/or the rear wheel actuator(s) 242, 244 to automatically deploy the vehicle cart 102 from a cargo compartment of a vehicle (e.g., the cargo compartment 106 of the vehicle 104 of FIG. 1).
  • a cargo compartment of a vehicle e.g., the cargo compartment 106 of the vehicle 104 of FIG. 1).
  • processor 254 provides one or more control signal(s) to one or more of the front leg actuator(s) 214, 216, the front wheel actuator(s) 222, 224, the rear leg actuator(s) 234, 236 and/or the rear wheel actuator(s) 242, 244 to automatically deploy the vehicle cart 102 is described below in connection with FIGS. 9-13.
  • the processor 254 of FIG. 2 compares data and/or information sensed, measured and/or detected by one or more of the front wheel contact sensor(s) 226, 228 and/or rear wheel contact sensor(s) 246, 248 to one or more threshold(s) to determine whether a wheel corresponding to the contact sensor (e.g., front wheel 218 corresponding to front wheel contact sensor 226) is in contact with an underlying surface (e.g., the ground, a cargo compartment of a vehicle within which the vehicle cart is stored, etc.).
  • a wheel corresponding to the contact sensor e.g., front wheel 218 corresponding to front wheel contact sensor 2266
  • an underlying surface e.g., the ground, a cargo compartment of a vehicle within which the vehicle cart is stored, etc.
  • the processor 254 determines that a force value sensed, measured and/or detected by a contact sensor (e.g., front wheel contact sensor 226) satisfies (e.g., exceeds) a force threshold, the processor 254 determines that the corresponding wheel (e.g., front wheel 218) of the vehicle cart 102 is in contact with an underlying surface. If the processor 254 instead determines that a force value sensed, measured and/or detected by the contact sensor (e.g., front wheel contact sensor 226) does not satisfy (e.g., does not exceed) the force threshold, the processor 254 determines that the corresponding wheel (e.g., front wheel 218) is not in contact with an underlying surface.
  • a contact sensor e.g., front wheel contact sensor 226) satisfies (e.g., exceeds) a force threshold
  • the processor 254 determines that the corresponding wheel (e.g., front wheel 218) of the vehicle cart 102 is in contact with an underlying surface.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to one or more of the front leg actuator(s) 214, 216, the front wheel actuator(s) 222, 224, the rear leg actuator(s) 234, 236 and/or the rear wheel actuator(s) 242, 244 based on one or more determination(s) made by the processor 254 as to whether one or more of the front wheel(s) 218, 220 and/or the rear wheel(s) 238, 240 are in contact with an underlying ground surface.
  • the processor 254 may provide one or more control signal(s) to an actuator of a leg corresponding to the wheel (e.g., front leg actuator 214) to cause a corresponding leg (e.g., front leg 210) to extend.
  • the control signal(s) provided by the processor 254 to the actuator of the leg corresponding to the wheel (e.g., front leg actuator 214) cause the corresponding leg (e.g., front leg 210) to extend until the processor 254 determines that the wheel (e.g., front wheel 218) is in contact with an underlying surface.
  • the processor 254 of FIG. 2 compares data and/or information sensed, measured and/or detected by the obstacle sensor 250 to one or more threshold(s) to determine whether the vehicle cart 102 is approaching and/or nearing an obstacle (e.g., a curb, a step, a flight of stairs, a wall, etc.) that may require the vehicle cart 102 to alter its path of travel. For example, if the processor 254 determines that a distance value sensed, measured and/or detected by the obstacle sensor 250 does not satisfy (e.g., does not exceed) a distance threshold, the processor 254 determines that the vehicle cart 102 is near an obstacle.
  • an obstacle e.g., a curb, a step, a flight of stairs, a wall, etc.
  • the processor 254 determines that the vehicle cart 102 is not near an obstacle.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to one or more of the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 based on one or more determination(s) made by the processor 254 as to whether the vehicle cart 102 is approaching and/or nearing an obstacle.
  • the processor 254 may provide one or more control signal(s) to one or more of the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 to cause the vehicle cart to turn away from and/or otherwise deviate from a path of travel along which the vehicle cart 102 would encounter the obstacle.
  • the control signal(s) provided by the processor 254 to the one or more of the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 cause the vehicle cart 102 to follow a path of travel by which the processor 254 determines that no obstacle is near and/or blocking the path of travel of the vehicle cart 102.
  • the processor 254 of FIG. 2 compares data and/or information sensed, measured and/or detected by the level sensor 252 to one or more threshold(s) to determine whether the vehicle cart 102 is level. For example, if the processor 254 determines that a rotational orientation value sensed, measured and/or detected by the level sensor 252 satisfies (e.g., exceeds) a balance threshold, the processor 254 determines that the vehicle cart 102 is not level. If the processor 254 instead determines that a rotational orientation value sensed, measured and/or detected by the level sensor 252 does not satisfy (e.g., does not exceed) the balance threshold, the processor 254 determines that the vehicle cart 102 is level.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to one or more of the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) 234, 236 based on one or more determination(s) made by the processor 254 as to whether the vehicle cart 102 is level. For example, in response to determining that the vehicle cart 102 is not level, the processor 254 may provide one or more control signal(s) to an actuator of a leg (e.g., front leg actuator 214) to cause a corresponding leg (e.g., front leg 210) to extend and/or retract.
  • a leg e.g., front leg actuator 214
  • control signal(s) provided by the processor 254 to the actuator of the leg cause the corresponding leg (e.g., front leg 210) to extend and/or retract until the processor 254 determines that the vehicle cart 102 is level.
  • the processor 254 of FIG. 2 compares location data (e.g., GPS data) associated with the vehicle cart 102 to location data associated with one or more of the vehicle 104, the remote control device 108 and/or the mobile device 110 to determine a path of travel of the vehicle cart 102. For example, in response to determining a location of the vehicle cart 102 relative to a location of the vehicle 104, the processor 254 determines, based on the respective locations of the vehicle cart 102 and the vehicle 104, a path of travel along which the vehicle cart 102 may be maneuvered, steered and/or otherwise navigated from its location (e.g., a current location) to reach the location (e.g., a destination location) of the vehicle 104.
  • location data e.g., GPS data
  • the processor 254 determines, based on the respective locations of the vehicle cart 102 and the remote control device 108, a path of travel along which the vehicle cart 102 may be maneuvered, steered and/or otherwise navigated from its location (e.g., a current location) to reach the location (e.g., a destination location) of the remote control device 108.
  • the processor 254 determines, based on the respective locations of the vehicle cart 102 and the mobile device 110, a path of travel along which the vehicle cart 102 may be maneuvered, steered and/or otherwise navigated from its location (e.g., a current location) to reach the location (e.g., a destination location) of the mobile device 1 10.
  • the processor 254 of FIG. 2 Based on one or more determined path(s) of travel of the vehicle cart 102, the processor 254 of FIG. 2 provides one or more control signal(s) to one or more of the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 to cause the vehicle cart 102 to track, follow and/or otherwise move toward one or more of the vehicle 104, the remote control device 108 and/or the mobile device 110.
  • the processor 254 may provide one or more control signal(s) to one or more of the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 to cause the vehicle cart 102 to track, follow and/or move toward the vehicle 104 along a corresponding path of travel (e.g., from a current location associated with the vehicle cart 102 toward a destination location associated with the vehicle 104).
  • the control signal(s) provided by the processor 254 may enable and/or cause the vehicle cart 102 to automatically return to the vehicle 104 from which the vehicle cart 102 was automatically deployed.
  • the processor 254 may provide one or more control signal(s) to one or more of the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 to cause the vehicle cart 102 to track, follow and/or move toward the remote control device 108 along a corresponding path of travel (e.g., from a current location associated with the vehicle cart 102 toward a destination location associated with the remote control device 108).
  • the processor 254 may provide one or more control signal (s) to one or more of the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 to cause the vehicle cart 102 to track, follow and/or move toward the mobile device 110 along a corresponding path of travel (e.g., from a current location associated with the vehicle cart 102 toward a destination location associated with the mobile device 110).
  • the control signal(s) provided by the processor 254 may enable and/or cause the vehicle cart 102 to automatically track, follow and/or move toward the remote control device 108 and/or the mobile device 110.
  • the remote control device 108 and/or the mobile device 110 may itself be changing locations, such as, for example, when being carried by a user who is moving about an environment.
  • the processor 254 of FIG. 2 may present a shopping list for display via the user interface 208 of FIG. 2 based on data received, retrieved and/or accessed from a mobile device. For example, the processor 254 may generate a shopping list based on corresponding shopping list data received by the radio receiver 202 of FIG. 2 from the mobile device 110 of FIG. 1. In some examples, the shopping list generated by the processor 254 includes a list of items to be purchased by a user of the vehicle cart 102.
  • the processor 254 of FIG. 2 based on the shopping list data received, retrieved and/or accessed by the vehicle cart 102 from the mobile device 110, the processor 254 of FIG. 2 identifies locations of corresponding stores from which an item on the shopping list may be purchased. For example, the processor 254 may identify the locations of one or more of the example first, second and/or third store(s) 1 14, 116, 118 of FIG. 1 as a store location from which a particular item on the shopping list may be purchased. The processor 254 may additionally identify prices at which the particular item may respectively be purchased from
  • the processor 254 may identify a first price at which the particular item is available for purchase from the first store 1 14, and a second price at which the particular item is available for purchase from a second store 1 16. In some examples, the processor 254 identifies the locations of corresponding stores from which an item on the shopping list may be purchased and/or the prices at which the item is available for purchase from such stores based on communications between the vehicle cart 102 and one or more external device(s) (e.g., a web server). Such communications may occur at the direction of the processor 254 via the example cellular base station(s) 124 and/or the example wireless access point(s) 126 of FIG. 1 in conjunction with the example radio receiver 202 and/or the example radio transmitter 204 of the vehicle cart of FIGS. 1 and 2.
  • a web server e.g., a web server
  • the processor 254 of FIG. 2 may present a shopping itinerary for display via the user interface 208 of FIG. 2.
  • the processor 254 may generate a shopping itinerary based on the identified locations and the identified prices of the items included on the shopping list described above.
  • the processor 254 may generate the shopping itinerary based on the identified store location(s) from which each item on the shopping list is available for purchase at its lowest price.
  • the processor 254 may generate the shopping itinerary based on the proximity of the identified store location(s) from which each item on the shopping list is available for purchase, with or without consideration of the identified price(s) at which the items are available for purchase from such store location(s).
  • the shopping itinerary may include routing and/or directions to be followed by the vehicle cart 102 and/or the vehicle 104 of FIG. 1 in the course of a user purchasing the items on the shopping itinerary.
  • the example memory 256 of FIG. 2 may be implemented by any type(s) and/or any number(s) of storage device(s) such as a storage drive, a flash memory, a read-only memory (ROM), a random-access memory (RAM), a cache and/or any other storage medium in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information).
  • the information stored in the memory 256 may be stored in any file and/or data structure format, organization scheme, and/or arrangement.
  • the memory 256 is accessible to the radio transmitter 204, the user interface 208, and the processor 254 of FIG. 2, and/or, more generally, to the vehicle cart 102 of FIGS. 1 and 2.
  • the example battery 258 of FIG. 2 provides power to one or more of the radio receiver 202, the radio transmitter 204, the GPS receiver 206, the user interface 208, the front leg actuators 214, 216, the front wheel actuators 222, 224, the front wheel contact sensors 226, 228, the rear leg actuators 234, 236, the rear wheel actuators 242, 244, the rear wheel contact sensors 246, 248, the obstacle sensor 250, the level sensor 252, the processor 254 and/or the memory 256 of FIG. 2, and/or, more generally, to the vehicle cart 102 of FIGS. 1 and 2.
  • the battery 258 is implemented as a rechargeable battery configured to be charged via a power supply and/or battery of a vehicle (e.g., the vehicle 104 of FIG. 1) in which the vehicle cart 102 is stowed, as further described in connection with FIGS. 5 and 6 below.
  • FIG. 2 While an example manner of implementing the example vehicle cart 102 of FIG. 1 is illustrated in FIG. 2, one or more of the elements, processes and/or devices illustrated in FIG. 2 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way.
  • the example radio receiver 202, the example radio transmitter 204, the example GPS receiver 206, the example user interface 208, the example front wheel contact sensors 226, 228, the example rear wheel contact sensors 246, 248, the example obstacle sensor 250, the example level sensor 252, the example processor 254 and/or the example memory 256 of FIG. 2 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware.
  • any of the example radio receiver 202, the example radio transmitter 204, the example GPS receiver 206, the example user interface 208, the example front wheel contact sensors 226, 228, the example rear wheel contact sensors 246, 248, the example obstacle sensor 250, the example level sensor 252, the example processor 254 and/or the example memory 256 could be any of the example radio receiver 202, the example radio transmitter 204, the example GPS receiver 206, the example user interface 208, the example front wheel contact sensors 226, 228, the example rear wheel contact sensors 246, 248, the example obstacle sensor 250, the example level sensor 252, the example processor 254 and/or the example memory 256 .
  • At least one of the example radio receiver 202, the example radio transmitter 204, the example GPS receiver 206, the example user interface 208, the example front wheel contact sensors 226, 228, the example rear wheel contact sensors 246, 248, the example obstacle sensor 250, the example level sensor 252, the example processor 254 and/or the example memory 256 is/are hereby expressly defined to include a tangible computer readable storage device or storage disk such as a memory, a digital versatile disk (DVD), a compact disk (CD), a Blu-ray disk, etc. storing the software and/or firmware.
  • the example vehicle cart 102 of FIG. 2 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in FIG. 2, and/or may include more than one of any or all of the illustrated elements, processes and devices.
  • FIG. 3 is a perspective view of the example vehicle cart 102 of FIGS. 1 and 2 in a deployed configuration.
  • the vehicle cart 102 includes the structures and/or components described above in connection with FIGS. 1 and 2, and further includes an example base 302, example sidewalls 304, 306, 308, 310, an example storage area 312, and an example handle 314.
  • other example implementations of the vehicle cart 102 may include fewer or additional structures in accordance with the teachings of this disclosure.
  • the base 302, sidewalls 304, 306, 308, 310, storage area 312 and/or handle 314 of the vehicle cart 102 may be of any size(s), shape(s) and or configuration(s) that enable(s) the vehicle cart 102 to be stowed within and automatically deployed from a cargo compartment of a vehicle (e.g., the cargo compartment 106 of the vehicle 104 of FIG. 1).
  • the example base 302 of FIG. 3 includes an example front end 316, an example rear end 318 opposite the front end 316, an example first surface 320 (e.g., an upper surface) to support one or more cargo item(s) (e.g., packages, bags, boxes, groceries, etc.) to be transported by the vehicle cart 102, and an example second surface 322 (e.g., a lower surface) opposite the first surface 320 to which the front legs 210, 212 and rear legs 230, 232 of the vehicle cart 102 are respectively coupled (either directly or indirectly).
  • the base 302 and the sidewalls 304, 306, 308, 310 of the vehicle cart 102 collectively define a storage area 312 to receive and store cargo items for transportation via the vehicle cart 102.
  • the sidewalls 304, 306, 308, 310 are of a height suitable to prevent cargo items positioned within the storage area 312 from falling off of and/or out of the storage area 312 and/or the vehicle cart 102 during transportation of such items via the vehicle cart 102.
  • the vehicle cart 102 may include any number of sidewalls 304, 306, 308, 310 having any combination of size(s), shape(s) and/or configuration(s).
  • the vehicle cart 102 may include a first sidewall (e.g., sidewall 304) adjacent the rear end 318 of the base 302 of the vehicle cart 102 and a second sidewall (e.g., sidewall 308) adjacent the front end 316 of the base 302 of the vehicle cart 102.
  • the sidewalls 304, 306, 308, 310 may all be of a uniform height. In other examples, a height of one or more of the sidewalls may differ from a height of other ones of the sidewalls.
  • the base 302 and/or one or more of the sidewalls 304, 306, 308, 310 of the vehicle cart 102 include one or more channel(s) 324.
  • the channels 324 may be of any number, size, shape and/or configuration. As further described below in connection with FIGS. 5, 6 and 9-12, the channels 324 assist in properly positioning the vehicle cart 102 for storage within and/or for deployment from a cargo compartment of a vehicle (e.g., the cargo compartment 106 of the vehicle 104 of FIG. 1).
  • the example handle 314 of FIG. 3 enables a user to grip and/or manually maneuver (e.g., push, pull, steer, etc.) the vehicle cart 102 in instances where manual control and/or operation of the vehicle cart 102 is desired by the user.
  • the handle 314 is coupled (either directly or indirectly) to the sidewall (e.g., sidewall 304) of the vehicle cart 102 that is most proximate the rear end 318 of the base 302 of the vehicle cart 102.
  • the handle 314 of the vehicle cart 102 may alternatively be coupled to one of the other sidewalls (e.g., sidewalls, 306, 308, 310) of the vehicle cart 102, including for example the sidewall (e.g., sidewall 308) that is most proximate the front end 316 of the base 302 of the vehicle cart 102.
  • the handle 314 of the vehicle cart 102 may be coupled to the base 302 of the vehicle cart 102.
  • the vehicle cart 102 may include multiple handles such that, for example, a first handle is coupled to the sidewall (e.g., sidewall 304) that is most proximate to the rear end 318 of the base 302 of the vehicle cart 102, and a second handle is coupled to the sidewall (e.g., sidewall 308) that is most proximate to the front end 316 of the base 302 of the vehicle cart 102.
  • a first handle is coupled to the sidewall (e.g., sidewall 304) that is most proximate to the rear end 318 of the base 302 of the vehicle cart 102
  • a second handle is coupled to the sidewall (e.g., sidewall 308) that is most proximate to the front end 316 of the base 302 of the vehicle cart 102.
  • the structures and/or components of the vehicle cart 102 described above in connection with FIG. 2 are housed by, embedded within, carried by, and/or otherwise coupled (either directly or indirectly) to the base 302, one or more of the sidewalls 304, 306, 308, 310, and/or the handle 314 of the vehicle cart 102 of FIG. 3.
  • the level sensor 252 is housed by, embedded within, carried by, and/or otherwise coupled to the base 302 of the vehicle cart 102
  • the obstacle sensor 250 is housed by, embedded within, carried by, and/or otherwise coupled to one of the sidewalls 304, 306, 308, 310 of the vehicle cart 102
  • the user interface is housed by, carried by and/or otherwise coupled to the handle 314 of the vehicle cart 102.
  • the front legs 210, 212 of the vehicle cart 102 are coupled (either directly or indirectly) to the second surface 322 of the base 302 of the vehicle cart 102 proximate the front end 316 of the base 302, and are extendable relative thereto.
  • the rear legs 230, 232 of the vehicle cart 102 are coupled (either directly or indirectly) to the second surface 322 of the base 302 of the vehicle cart 102 proximate the rear end 318 of the base 302, and are extendable relative thereto.
  • the front leg actuators 214, 216, front wheels 218, 220, front wheel actuators 222, 224 and front wheel contact sensors 226, 228 of the vehicle cart 102 are respectively coupled (either directly or indirectly) to the front legs 210, 212 of the vehicle cart 102, and the rear leg actuators 234, 236, rear wheels 238, 240, rear wheel actuators 242, 244 and rear wheel contact sensors 246, 248 of the vehicle cart 102 are respectively coupled (either directly or indirectly) to the rear legs 230, 232 of the vehicle cart 102.
  • FIG. 4 is a perspective view of another example vehicle cart 400 in a deployed configuration.
  • the vehicle cart 400 of FIG. 4 includes the radio receiver 202, radio transmitter 204, GPS receiver 206, user interface 208, front legs 210, 212, front leg actuators 214, 216, front wheels 218, 220, front wheel actuators 222, 224, front wheel contact sensors 226, 228, rear legs 230, 232, rear leg actuators 234, 236, rear wheel actuators 242, 244, rear wheel contact sensors 246, 248, obstacle sensor 250, level sensor 252, processor 254, memory 256, battery 258, base 302, sidewalls 304, 306, 308, 310 and handle 314 of the example vehicle cart 102 of FIGS. 1-3 described above.
  • each stair- climbing rear wheel 438, 440 is implemented as a rotatable triple wheel set that assists and/or enables the vehicle cart 400 to ascend, descend and/or traverse obstacles such as, for example, a curb, a step, or a flight of stairs.
  • the stair-climbing rear wheels 438, 440 of FIG. 4 may enable the vehicle cart 400 to ascend and/or descend the stairs 120 of the residence 112 of FIG. 1.
  • the vehicle cart 400 of FIG. 4 is illustrated as including stair-climbing rear wheels 438, 440, the vehicle cart 400 may additionally and/or altematively include stair-climbing front wheels (not shown) implemented in place of the front wheels 218, 220 of FIG. 4.
  • FIG. 5 a block diagram of the example vehicle 104 of FIG. 1.
  • the vehicle 104 includes an example radio receiver 502, an example radio transmitter 504, an example GPS receiver 506, an example user interface 508, the example cargo compartment 106, an example liftgate 510, an example liftgate actuator 512, example rails 514, 516, example rail actuators 518, 520, an example processor 522, an example memory 524, and an example battery 526.
  • the vehicle 104 may include fewer or additional structures in accordance with the teachings of this disclosure.
  • the example radio receiver 502 of FIG. 5 collects, acquires and/or receives one or more signal(s) from the vehicle cart 102, the remote control device 108, and/or the mobile device 110 of FIG. 1.
  • the signal(s) received by the radio receiver 502 from the vehicle cart 102, the remote control device 108, and/or the mobile device 110 are communicated via the cellular base station(s) 124 and/or the wireless access point(s) 126 of FIG. 1.
  • the radio receiver 502 may receive a control signal from the remote control device 108 and/or the mobile device 110 in association with the vehicle cart 102 being automatically deployed from the vehicle 104.
  • the radio receiver 502 may receive data corresponding to a current location of the vehicle cart 102. Data identified and/or derived from the signal(s) collected and/or received by the radio receiver 502 may be stored in a computer-readable storage medium such as the example memory 524 described below.
  • the example radio transmitter 504 of FIG. 5 transmits one or more signal(s) to the vehicle cart 102 of FIG. 1.
  • the signal(s) transmitted by the radio transmitter 504 to the vehicle cart 102 are communicated via the cellular base station(s) 124 and/or the wireless access point(s) 126 of FIG. 1.
  • the radio transmitter 504 may transmit data corresponding to a current location of the vehicle 104. Data corresponding to the signal(s) to be transmitted by the radio transmitter 504 may be stored in a computer-readable storage medium such as the example memory 524 described below.
  • the example GPS receiver 506 of FIG. 5 collects, acquires and/or receives one or more signal(s) from the GPS satellite(s) 122 of FIG. 1.
  • the signal(s) received by the GPS receiver 506 may include information from which the current location of the vehicle 104 may be identified and/or derived, including for example, the current latitude and longitude of the vehicle 104.
  • Data identified and/or derived from the signal(s) collected and/or received by the GPS receiver 506 may be stored in a computer-readable storage medium such as the example memory 524 described below.
  • the example user interface 508 of FIG. 5 facilitates interactions and/or
  • the user interface 508 includes one or more input device(s) 528 via which the user may input information and/or data to the vehicle 104.
  • the user interface 508 may be a button, a microphone, and/or a touchscreen that enable(s) the user to convey data and/or commands to the vehicle 104.
  • the user interface 508 also includes one or more output device(s) 530 via which the processor 522 of the vehicle 104 presents information and/or data in visual and/or audible form to the user.
  • the user interface 508 may include a light emitting diode, a touchscreen, and/or a liquid crystal display for presenting visual information, and/or a speaker for presenting audible information.
  • Data and/or information that is presented and/or received via the user interface 508 may be of any type, form and/or format, and may be stored in a computer-readable storage medium such as the example memory 524 described below.
  • the example cargo compartment 106 of FIGS. 1 and 5 provides an area in which the vehicle cart 102 of FIG. 1 may be stowed.
  • the example liftgate 510 of FIG. 5 is coupled (either directly or indirectly) to the cargo compartment 106 and/or the vehicle 104.
  • the liftgate 510 defines a rear boundary of the cargo compartment 106 and/or the vehicle 104.
  • the liftgate 510 is moveable between an open position that enables the vehicle cart 102 to be loaded into and/or deployed from the cargo compartment 106 of the vehicle 104, and a closed position that prevents the vehicle cart 102 from being loaded into and/or deployed from the cargo compartment 106 of the vehicle 104.
  • the liftgate 510 may be implemented as a single gate structure that pivots and/or rotates relative to the cargo compartment 106 and/or the vehicle 104.
  • the liftgate 510 may be implemented as a single gate structure that pivots from a closed position upwardly to an open position.
  • the liftgate may be implemented as multiple gate structures that respectively pivot and/or rotate relative to the cargo compartment 106 and/or the vehicle 104.
  • the liftgate 510 may be implemented as a first gate structure that pivots from a closed position upwardly to an open position, and a second gate structure that rotates from a closed position downwardly to an open position.
  • the example liftgate actuator 512 of FIG. 2 is operatively coupled to the liftgate 510 of FIG. 2 to control the movement and/or actuation thereof. More specifically, in response to one or more control signal(s) and/or instruction(s) received by the liftgate actuator 512 from the processor 522 of FIG. 5, the liftgate actuator 512 moves and/or actuates the liftgate 510. Movement and/or actuation of the liftgate 510 by the liftgate actuator 512 causes the liftgate 510 to open and/or close relative to the cargo compartment 106 of the vehicle 104.
  • the liftgate actuator 512 may additionally and/or alternatively be implemented as one or more electric motor(s) to control the movement and/or actuation of the liftgate 510 based on one or more control signal(s) provided to the liftgate actuator 512 by the processor 522.
  • the vehicle 104 may include any number of liftgate actuators 512.
  • the number of liftgate actuators 512 may correspond to the number of gate structures such that each gate structure is independently operable by a corresponding liftgate actuator 512.
  • the example rails 514, 516 of FIG. 5 are coupled (either directly or indirectly) to the cargo compartment 106 of the vehicle 104.
  • the rails 514, 516 are movable between a stowed position in which the rails 514, 516 are located within the cargo compartment 106 of the vehicle 104 when the liftgate 510 is in either an open or a closed position, and a deployed position in which the rails 514, 516 are located at least partially outside of the cargo compartment 106 of the vehicle 104 when the liftgate 510 of the vehicle 104 is in an open position.
  • the rails 514, 516 of the vehicle 104 are configured to mate with and/or engage the channels 324 of the vehicle cart 102 of FIG. 1 to support and/or guide the vehicle cart 102 when the vehicle cart 102 is stowed in the vehicle 104, and/or in connection with the vehicle cart 102 being automatically deployed from the vehicle 104.
  • the vehicle 104 may include any number of rails 514, 516, including a single rail.
  • respective ones of the rails 514, 516 may be coupled together such that movement of any one of the rails 514, 516 results in corresponding movement to the other ones of the rails 514, 516.
  • respective ones of the rails 514, 516 may be independently movable and/or actuatable such that movement of any one of the rails 514, 516 has no bearing and/or impact on movement of any of the other ones of the rails 514, 516.
  • the example rail actuators 518, 520 of FIG. 5 are operatively coupled to
  • corresponding ones of the rails 514, 516 of FIG. 5 to control the movement and/or actuation thereof. More specifically, in response to one or more control signal(s) and/or instruction(s) received by one or more of the rail actuators 518, 520 from the processor 522 of FIG. 5, respective ones of the rail actuators 518, 520 move and/or actuate corresponding ones of the rails 514, 516. Movement and/or actuation of a rail (e.g., rail 514) by a corresponding rail actuator (e.g., rail actuator 518) causes the rail to deploy and/or retract relative to the cargo compartment 106 of the vehicle 104.
  • the rail actuators 518, 520 may additionally and/or alternatively be implemented as one or more electric motor(s) to control the movement and/or actuation of the rails 514, 516 based on one or more control signal(s) provided to the rail actuators 518, 520 by the processor 522.
  • the vehicle 104 may include any number of rail actuators 518, 520, including a single rail actuator.
  • a single rail actuator In some examples in which the vehicle 104 includes two or more rails 514, 516, respective ones of the rails 514, 516 may be coupled together such that movement of all of the rails 514, 516 may be controlled by a single rail actuator.
  • the number of rail actuators 518, 520 corresponds to the number of rails 514, 516, such that each rail (e.g. rail 514) is independently controlled by a corresponding rail actuator (e.g., rail actuator 518).
  • the example processor 522 of FIG. 5 may be implemented by a semiconductor device such as a microprocessor, controller or microcontroller.
  • the processor 522 manages and/or controls the operation of the vehicle 104 based on data, information and/or one or more control signal(s) obtained and/or accessed by the processor 522 from one or more of the radio receiver 502, the GPS receiver 506, the user interface 508 and/or the memory 524, and/or based on data, information and/or one or more control signal(s) provided by the processor 522 to one or more of the radio transmitter 504, the user interface 508, the liftgate actuator 512 and/or the rail actuators 518, 520.
  • the processor 522 of FIG. 5 may provide one or more control signal(s) to the liftgate actuator 512 to actuate the liftgate 510 in conjunction with automatically deploying a vehicle cart (e.g., vehicle cart 102 of FIGS. 1-3) from the cargo compartment 106 of the vehicle 104.
  • a vehicle cart e.g., vehicle cart 102 of FIGS. 1-3
  • the processor 522 of FIG. 2 may provide one or more control signal(s) to the rail actuators 518, 520 to actuate the rails 514, 516 in conjunction with automatically deploying a vehicle cart (e.g., vehicle cart 102 of FIGS. 1-3) from the cargo compartment 106 of the vehicle 104.
  • a vehicle cart e.g., vehicle cart 102 of FIGS. 1-3
  • the processor 522 may provide one or more control signal(s) to the radio transmitter 504 to cause the radio transmitter 504 to transmit location data (e.g., GPS data), corresponding to a location of the vehicle 104, from the vehicle 104 to the vehicle cart 102 of FIG. 1.
  • location data e.g., GPS data
  • the example memory 524 of FIG. 5 may be implemented by any type(s) and/or any number(s) of storage device(s) such as a storage drive, a flash memory, a read-only memory (ROM), a random-access memory (RAM), a cache and/or any other storage medium in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information).
  • the information stored in the memory 524 may be stored in any file and/or data structure format, organization scheme, and/or arrangement.
  • the memory 524 is accessible to the example radio transmitter 504, the example user interface 508, and the example processor 522 of FIG. 5, and/or, more generally, to the example vehicle 104 of FIGS. 1 and 5.
  • the example battery 526 of FIG. 5 provides power to one or more of the radio receiver 502, the radio transmitter 504, the GPS receiver 506, the user interface 508, the liftgate actuator 512, the rail actuators 518, 520, the processor 522 and/or the memory 524 of the vehicle 104.
  • the battery 526 is configured to supply power to a vehicle cart (e.g., the example vehicle cart 102 of FIGS. 1-3) stowed in the cargo
  • a battery e.g., battery 258 of FIG. 2 of the vehicle cart.
  • FIG. 5 While an example manner of implementing the example vehicle 104 of FIG. 1 is illustrated in FIG. 5, one or more of the elements, processes and/or devices illustrated in FIG. 5 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example radio receiver 502, the example radio transmitter 504, the example GPS receiver 506, the example user interface 508, the example processor 522 and/or the example memory 524 of FIG. 5 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware.
  • any of the example radio receiver 502, the example radio transmitter 504, the example GPS receiver 506, the example user interface 508, the example processor 522 and/or the example memory 524 could be implemented by one or more analog or digital circuit(s), logic circuits, programmable processor(s), application specific integrated circuit(s) (ASIC(s)),
  • PLD programmable logic device
  • field programmable logic device PLD(s)
  • At least one of the example radio receiver 502, the example radio transmitter 504, the example GPS receiver 506, the example user interface 508, the example processor 522 and/or the example memory 524 is/are hereby expressly defined to include a tangible computer readable storage device or storage disk such as a memory, a digital versatile disk (DVD), a compact disk (CD), a Blu-ray disk, etc. storing the software and/or firmware.
  • the example vehicle 104 of FIG. 5 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in FIG. 5, and/or may include more than one of any or all of the illustrated elements, processes and devices.
  • FIG. 6 is a perspective view of the example cargo compartment 106 of the example vehicle 104 of FIGS. 1 and 5.
  • the cargo compartment 106 includes an example floor or base 602 and example sidewalls 604, 606.
  • the base 602 provides an underlying surface for a vehicle cart (e.g., the example vehicle cart 102 of FIGS. 1-3) when the vehicle cart is stowed in the cargo compartment 106 of the vehicle 104.
  • the rails 514, 516 are respectively coupled (either directly or indirectly) to the sidewalls 604, 606 of the cargo compartment 106.
  • FIG. 1 the cargo compartment 106 includes an example floor or base 602 and example sidewalls 604, 606.
  • the base 602 provides an underlying surface for a vehicle cart (e.g., the example vehicle cart 102 of FIGS. 1-3) when the vehicle cart is stowed in the cargo compartment 106 of the vehicle 104.
  • the rails 514, 516 are respectively coupled (either directly or indirectly) to the sidewalls 604,
  • the rails 514, 516 are shown in a stowed position in which the rails 514, 516 are located within the cargo compartment 106 of the vehicle 104.
  • the rails 514, 516 are movable from the stowed position to a deployed position in which the rails 514, 516 are located at least partially outside of the cargo compartment 106 of the vehicle 104.
  • the rails 514, 516 are configured to mate with and/or engage the channels 324 of the vehicle cart 102 of FIG. 1 to support and/or guide the vehicle cart 102 when the vehicle cart 102 is stowed in the cargo compartment 106 of the vehicle 104, and/or in connection with the vehicle cart 102 being automatically deployed from the cargo compartment 106 of the vehicle 104.
  • FIG. 7 is a block diagram of the example remote control device 108 of FIG. 1.
  • the remote control device 108 includes an example radio receiver 702, an example radio transmitter 704, an example GPS receiver 706, an example user interface 708, an example processor 710, an example memory 712, and an example battery 714.
  • the remote control device 108 may include fewer or additional structures in accordance with the teachings of this disclosure.
  • the example radio receiver 702 of FIG. 7 collects, acquires and/or receives one or more signal(s) from the vehicle cart 102 of FIG. 1.
  • the signal (s) received by the radio receiver 702 from the vehicle cart 102 are communicated via the cellular base station(s) 124 and/or the wireless access point(s) 126 of FIG. 1.
  • the radio receiver 702 may receive data corresponding to a current location of the vehicle cart 102. Data identified and/or derived from the signal(s) collected and/or received by the radio receiver 702 may be stored in a computer-readable storage medium such as the example memory 712 described below.
  • the example radio transmitter 704 of FIG. 7 transmits one or more signal(s) to the vehicle cart 102 and/or the vehicle 104 of FIG. 1.
  • the signal(s) transmitted by the radio transmitter 704 to the vehicle cart 102 and/or the vehicle 104 are communicated via the cellular base station(s) 124 and/or the wireless access point(s) 126 of FIG. 1.
  • the radio transmitter 704 may transmit a control signal to the vehicle cart 102 and/or the vehicle 104 in association with the vehicle cart 102 being automatically deployed from the vehicle 104.
  • the radio transmitter 704 may transmit data to the vehicle cart 102 corresponding to a current location of the remote control device 108. Data corresponding to the signal(s) to be transmitted by the radio transmitter 704 may be stored in a computer-readable storage medium such as the example memory 712 described below.
  • the example GPS receiver 706 of FIG. 7 collects, acquires and/or receives one or more signal(s) from the GPS satellite(s) 122 of FIG. 1.
  • the signal(s) received by the GPS receiver 706 may include information from which the current location of the remote control device 108 may be identified and/or derived, including for example, the current latitude and longitude of the remote control device 108.
  • Data identified and/or derived from the signal(s) collected and/or received by the GPS receiver 706 may be stored in a computer-readable storage medium such as the example memory 712 described below.
  • the example user interface 708 of FIG. 7 facilitates interactions and/or
  • the user interface 708 includes one or more input device(s) 716 via which the user may input information and/or data to the remote control device 108.
  • the user interface 708 may be a button, a microphone, and/or a touchscreen that enable(s) the user to convey data and/or commands to the remote control device 108.
  • the user interface 708 also includes one or more output device(s) 718 via which the processor 710 of the remote control device 108 presents information and/or data in visual and/or audible form to the user.
  • the user interface 708 may include a light emitting diode, a touchscreen, and/or a liquid crystal display for presenting visual information, and/or a speaker for presenting audible information.
  • Data and/or information that is presented and/or received via the user interface 708 may be of any type, form and/or format, and may be stored in a computer-readable storage medium such as the example memory 712 described below.
  • the example processor 710 of FIG. 7 may be implemented by a semiconductor device such as a microprocessor, controller or microcontroller.
  • the processor 710 manages and/or controls the operation of the remote control device 108 based on data, information and/or one or more control signal(s) obtained and/or accessed by the processor 710 from one or more of the radio receiver 702, the GPS receiver 706, the user interface 708 and/or the memory 712, and/or based on data, information and/or one or more control signal(s) provided by the processor 710 to one or more of the radio transmitter 704 and/or the user interface 708.
  • the processor 710 may provide one or more control signal(s) to the radio transmitter 704 to cause the radio transmitter 704 to transmit one or more deployment control signal(s) from the remote control device 108 to the vehicle cart 102 and/or to the vehicle 104 of FIG. 1.
  • the processor 710 may provide one or more control signal(s) to the radio transmitter 704 to cause the radio transmitter 704 to transmit location data (e.g., GPS data), corresponding to a location of the remote control device 108, from the remote control device 108 to the vehicle cart 102 of FIG. 1.
  • location data e.g., GPS data
  • the example memory 712 of FIG. 7 may be implemented by any type(s) and/or any number(s) of storage device(s) such as a storage drive, a flash memory, a read-only memory (ROM), a random-access memory (RAM), a cache and/or any other storage medium in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information).
  • the information stored in the memory 712 may be stored in any file and/or data structure format, organization scheme, and/or arrangement.
  • the memory 712 is accessible to the example radio transmitter 704, the example user interface 708, and the example processor 710 of FIG. 7, and/or, more generally, to the example remote control device 108 of FIGS. 1 and 7.
  • the example battery 714 of FIG. 7 provides power to one or more of the radio receiver 702, the radio transmitter 704, the GPS receiver 706, the user interface 708, the processor 710 and/or the memory 712 of the remote control device 108.
  • FIG. 7 While an example manner of implementing the example remote control device 108 of FIG. 1 is illustrated in FIG. 7, one or more of the elements, processes and/or devices illustrated in FIG. 7 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example radio receiver 702, the example radio transmitter 704, the example GPS receiver 706, the example user interface 708, the example processor 710 and/or the example memory 712 of FIG. 7 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware.
  • any of the example radio receiver 702, the example radio transmitter 704, the example GPS receiver 706, the example user interface 708, the example processor 710 and/or the example memory 712 could be implemented by one or more analog or digital circuit(s), logic circuits, programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s)
  • At least one of the example radio receiver 702, the example radio transmitter 704, the example GPS receiver 706, the example user interface 708, the example processor 710 and/or the example memory 712 is/are hereby expressly defined to include a tangible computer readable storage device or storage disk such as a memory, a digital versatile disk (DVD), a compact disk (CD), a Blu-ray disk, etc. storing the software and/or firmware.
  • the example remote control device 108 of FIG. 7 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in FIG. 7, and/or may include more than one of any or all of the illustrated elements, processes and devices.
  • FIG. 8 is a block diagram of the example mobile device 110 of FIG. 1.
  • the mobile device 110 includes an example radio receiver 802, an example radio transmitter 804, an example GPS receiver 806, an example user interface 808, an example processor 810, an example memory 812, and an example battery 814.
  • mobile device 110 may include fewer or additional structures in accordance with the teachings of this disclosure.
  • the example radio receiver 802 of FIG. 8 collects, acquires and/or receives one or more signal(s) from the vehicle cart 102 of FIG. 1.
  • the signal (s) received by the radio receiver 802 from the vehicle cart 102 are communicated via the cellular base station(s) 124 and/or the wireless access point(s) 126 of FIG. 1.
  • the radio receiver 802 may receive data corresponding to a current location of the vehicle cart 102. Data identified and/or derived from the signal(s) collected and/or received by the radio receiver 802 may be stored in a computer-readable storage medium such as the example memory 812 described below.
  • the example radio transmitter 804 of FIG. 8 transmits one or more signal(s) to the vehicle cart 102 and/or the vehicle 104 of FIG. 1.
  • the signal(s) transmitted by the radio transmitter 804 to the vehicle cart 102 and/or the vehicle 104 are communicated via the cellular base station(s) 124 and/or the wireless access point(s) 126 of FIG. 1.
  • the radio transmitter 804 may transmit a control signal to the vehicle cart 102 and/or the vehicle 104 in association with the vehicle cart 102 being automatically deployed from the vehicle 104.
  • the radio transmitter 804 may transmit data to the vehicle cart 102 corresponding to a current location of the mobile device 110. Data corresponding to the signal(s) to be transmitted by the radio transmitter 804 may be stored in a computer-readable storage medium such as the example memory 812 described below.
  • the example GPS receiver 806 of FIG. 8 collects, acquires and/or receives one or more signal(s) from the GPS satellite(s) 122 of FIG. 1.
  • the signal(s) received by the GPS receiver 806 may include information from which the current location of the mobile device 110 may be identified and/or derived, including for example, the current latitude and longitude of the mobile device 110.
  • Data identified and/or derived from the signal(s) collected and/or received by the GPS receiver 806 may be stored in a computer-readable storage medium such as the example memory 812 described below.
  • the example user interface 808 of FIG. 8 facilitates interactions and/or
  • the user interface 808 includes one or more input device(s) 816 via which the user may input information and/or data to the mobile device 110.
  • the user interface 808 may be a button, a microphone, and/or a touchscreen that enable(s) the user to convey data and/or commands to the mobile device 110.
  • the user interface 808 also includes one or more output device(s) 818 via which the processor 810 of the mobile device 110 presents information and/or data in visual and/or audible form to the user.
  • the user interface 808 may include a light emitting diode, a touchscreen, and/or a liquid crystal display for presenting visual information, and/or a speaker for presenting audible information.
  • Data and/or information that is presented and/or received via the user interface 808 may be of any type, form and/or format, and may be stored in a computer-readable storage medium such as the example memory 812 described below.
  • the example processor 810 of FIG. 8 may be implemented by a semiconductor device such as a microprocessor, controller or microcontroller.
  • the processor 810 manages and/or controls the operation of the mobile device 110 based on data, information and/or one or more control signal(s) obtained and/or accessed by the processor 810 from one or more of the radio receiver 802, the GPS receiver 806, the user interface 808 and/or the memory 812, and/or based on data, information and/or one or more control signal(s) provided by the processor 810 to one or more of the radio transmitter 804 and/or the user interface 808.
  • the processor 810 may provide one or more control signal(s) to the radio transmitter 804 to cause the radio transmitter 804 to transmit one or more deployment control signal(s) from the mobile device 110 to the vehicle cart 102 and/or to the vehicle 104 of FIG. 1.
  • the processor 810 may provide one or more control signal(s) to the radio transmitter 804 to cause the radio transmitter 804 to transmit location data (e.g., GPS data), corresponding to a location of the mobile device 110, from the mobile device 110 to the vehicle cart 102 of FIG. 1.
  • the processor 810 may provide one or more control signal(s) to the radio transmitter 804 to cause the radio transmitter 804 to transmit data corresponding to a shopping list stored on the mobile device 110, from the mobile device 110 to the vehicle cart 102 of FIG. 1.
  • the example memory 812 of FIG. 8 may be implemented by any type(s) and/or any number(s) of storage device(s) such as a storage drive, a flash memory, a read-only memory (ROM), a random-access memory (RAM), a cache and/or any other storage medium in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information).
  • the information stored in the memory 812 may be stored in any file and/or data structure format, organization scheme, and/or arrangement.
  • the memory 812 is accessible to the example radio transmitter 804, the example user interface 808, and the example processor 810 of FIG. 8, and/or, more generally, to the example mobile device 110 of FIGS. 1 and 8.
  • the example battery 814 of FIG. 8 provides power to one or more of the radio receiver 802, the radio transmitter 804, the GPS receiver 806, the user interface 808, the processor 810 and/or the memory 812 of the mobile device 110.
  • FIG. 8 While an example manner of implementing the example mobile device 110 of FIG. 1 is illustrated in FIG. 8, one or more of the elements, processes and/or devices illustrated in FIG. 8 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example radio receiver 802, the example radio transmitter 804, the example GPS receiver 806, the example user interface 808, the example processor 810 and/or the example memory 812 of FIG. 8 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware.
  • any of the example radio receiver 802, the example radio transmitter 804, the example GPS receiver 806, the example user interface 808, the example processor 810 and/or the example memory 812 could be implemented by one or more analog or digital circuit(s), logic circuits, programmable processor(s), application specific integrated circuit(s) (ASIC(s)),
  • PLD programmable logic device
  • field programmable logic device PLD(s)
  • At least one of the example radio receiver 802, the example radio transmitter 804, the example GPS receiver 806, the example user interface 808, the example processor 810 and/or the example memory 812 is/are hereby expressly defined to include a tangible computer readable storage device or storage disk such as a memory, a digital versatile disk (DVD), a compact disk (CD), a Blu-ray disk, etc. storing the software and/or firmware.
  • the example mobile device 110 of FIG. 8 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in FIG.
  • FIG. 9 is a side view of the example vehicle cart 102 of FIGS. 1-3 in an example stowed configuration relative to the example cargo compartment 106 of the example vehicle 104 of FIGS. 1, 5 and 6.
  • the vehicle cart 102 is positioned entirely within the cargo compartment 106 of the vehicle 104.
  • the liftgate 510 of the vehicle 104 includes a first gate 902 and a second gate 904.
  • the first and second gates 902, 904 of the liftgate 510 are both in a closed position to secure the vehicle cart 102 within the cargo compartment 106 of the vehicle 104.
  • FIG. 10 is a side view of the example vehicle cart 102 of FIGS. 1-3 in a first example partially-deployed configuration relative to the example cargo compartment 106 of the example vehicle 104 of FIGS. 1, 5 and 6.
  • the processor 522 of the vehicle 104 based on one or more deployment control signal (s) and/or deployment command(s) received via the radio receiver 502 and/or via the user interface 508 of the vehicle 104, the processor 522 of the vehicle 104 has provided one or more control signal(s) to the liftgate actuator(s) 512 of the vehicle 104 to actuate the first and second gates 902, 904 of the liftgate 510 into their respective open positions.
  • the first gate 902 has been pivoted from the closed position of FIG. 9 upwardly to an open position
  • the second gate 904 has been pivoted from the closed position of FIG. 9 downwardly to an open position.
  • the processor 254 of the vehicle cart 102 has provided one or more control signal(s) to the front wheel actuators 222, 224 and/or the rear wheel actuators 242, 244 to actuate the corresponding ones of the front wheels 218, 220 and/or the rear wheels 238, 240.
  • the vehicle cart 102 is moved, driven and/or maneuvered to the first example partially-deployed position shown in FIG. 10.
  • the rear wheels 238, 240 of the vehicle cart 102 are not in contact with an underlying surface (e.g., the rear wheels 238, 240 have cleared the underlying surface provided by the cargo compartment 106 and/or the second gate 904 of the vehicle 104).
  • the vehicle cart 102 may additionally and/or alternatively be moved into the first example partially-deployed position of FIG. 10 via actuation of the rails 514, 516 of the vehicle 104 of FIGS. 1, 5 and 6.
  • the processor 522 of the vehicle 104 may provide one or more control signal (s) to the rail actuators 518, 520 to actuate the rails 514, 516 to a deployed position corresponding to the first example partially- deployed position of the vehicle cart 102 of FIG. 10.
  • the vehicle cart 102 moves along with the rails 514, 516 as a result of the rails 514, 516 mating, engaging and/or supporting the channels 324 of the vehicle cart 102.
  • FIG. 11 is a side view of the example vehicle cart 102 of FIGS. 1-3 in a second example partially-deployed configuration relative to the example cargo compartment 106 of the example vehicle 104 of FIGS. 1, 5 and 6.
  • the processor 254 of the vehicle cart 102 has determined that the rear wheels 238, 240 of the vehicle cart 102 are not in contact with an underlying surface.
  • the processor 254 has provide one or more control signal(s) to the rear leg actuators 234, 236 to cause the rear legs 230, 232 of the vehicle cart to extend to place the vehicle cart 102 into the second example partially-deployed position shown in FIG. 11.
  • the rear wheels 238, 240 of the vehicle cart 102 are in contact with an underlying surface (e.g., the rear wheels 238, 240 are in contact with the ground).
  • FIG. 12 is a side view of the example vehicle cart 102 of FIGS. 1-3 in a third example partially-deployed configuration relative to the example cargo compartment 106 of the example vehicle 104 of FIGS. 1, 5 and 6.
  • the processor 254 of the vehicle cart 102 based on one or more deployment control signal (s) and/or deployment command(s) received via the radio receiver 202 and/or via the user interface 208 of the vehicle cart 102, the processor 254 of the vehicle cart 102 has provided one or more control signal(s) to the front wheel actuators 222, 224 and/or the rear wheel actuators 242, 244 to actuate the corresponding ones of the front wheels 218, 220 and/or the rear wheels 238, 240.
  • the vehicle cart 102 is moved, driven and/or maneuvered to the third example partially-deployed position shown in FIG. 12.
  • the front wheels 218, 220 of the vehicle cart 102 are not in contact with an underlying surface (e.g., the front wheels 218, 220 have cleared the underlying surface provided by the cargo compartment 106 and/or the second gate 904 of the vehicle 104).
  • the third example partially-deployed position of FIG. 12 In the third example partially-deployed position of FIG. 12, the front wheels 218, 220 of the vehicle cart 102 are not in contact with an underlying surface (e.g., the front wheels 218, 220 have cleared the underlying surface provided by the cargo compartment 106 and/or the second gate 904 of the vehicle 104).
  • a portion of the second surface 322 of the vehicle cart 102 proximate the front end 316 of the vehicle cart 102 (e.g., the portion of the second surface 322 located between the front wheel 218 and the front end 316 of the vehicle cart 102) supports the vehicle cart 102 on the second gate 904 of the vehicle 104.
  • the vehicle cart 102 may additionally and/or alternatively be moved into the third example partially-deployed position of FIG. 12 via actuation of the rails 514, 516 of the vehicle 104 of FIGS. 1, 5 and 6.
  • the processor 522 of the vehicle 104 may provide one or more control signal (s) to the rail actuators 518, 520 to actuate the rails 514, 516 to a deployed position corresponding to the third example partially- deployed position of the vehicle cart 102 of FIG. 12.
  • the vehicle cart 102 moves along with the rails 514, 516 as a result of the rails 514, 516 mating, engaging and/or supporting the channels 324 of the vehicle cart 102.
  • FIG. 13 is a side view of the example vehicle cart 102 of FIGS. 1-3 in an example deployed configuration relative to the example cargo compartment 106 of the example vehicle 104 of FIGS. 1, 5 and 6.
  • the processor 254 of the vehicle cart 102 has determined that the front wheels 218, 220 of the vehicle cart 102 are not in contact with an underlying surface.
  • the processor 254 has provide one or more control signal(s) to the front leg actuators 214, 216 to cause the front legs 210, 212 of the vehicle cart to extend to place the vehicle cart 102 into the deployed position shown in FIG. 13.
  • the front wheels 218, 220 of the vehicle cart 102 are in contact with an underlying surface (e.g., the front wheels 218, 220 are in contact with the ground).
  • FIGS. 14-17 Flowcharts representative of example methods for automatically deploying the example vehicle cart 102 of FIGS. 1-3 from the example cargo compartment 106 of the example vehicle 104 of FIGS. 1, 5 and 6, for automatically maneuvering the example vehicle cart 102 of FIGS. 1-3 toward the example vehicle 104 of FIGS. 1, 5 and 6, the example remote control device 108 of FIGS. 1 and 7, and/or the example mobile device 110 of FIGS. 1 and 8, and for providing the example vehicle cart 102 of FIGS. 1-3 with a shopping itinerary are shown in FIGS. 14-17.
  • the methods may be implemented using machine-readable instructions that comprise one or more program(s) for execution by a processor such as the example processor 254 of FIG.
  • the one or more program(s) may be embodied in software stored on a tangible computer readable storage medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), a Blu-ray disk, or a memory associated with the processor 254 or the processor 522, but the entire program(s) and/or parts thereof could alternatively be executed by a device other than the processor 254 or the processor 522 and/or embodied in firmware or dedicated hardware.
  • a tangible computer readable storage medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), a Blu-ray disk, or a memory associated with the processor 254 or the processor 522, but the entire program(s) and/or parts thereof could alternatively be executed by a device other than the processor 254 or the processor 522 and/or embodied in firmware or dedicated hardware.
  • example program(s) is/are described with reference to the flowcharts illustrated in FIGS. 14-17, many other methods for automatically deploying the example vehicle cart 102 from the example cargo compartment 106 of the example vehicle 104, for automatically maneuvering the example vehicle cart 102 toward the example vehicle 104, the example remote control device 108, and/or the example mobile device 110, and for providing the example vehicle cart 102 with a shopping itinerary may alternatively be used.
  • the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, or combined.
  • FIGS. 14-17 may be implemented using coded instructions (e.g., computer and/or machine-readable instructions) stored on a tangible computer readable storage medium such as a hard disk drive, a flash memory, a read-only memory (ROM), a compact disk (CD), a digital versatile disk (DVD), a cache, a random- access memory (RAM) and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/or for caching of the information).
  • coded instructions e.g., computer and/or machine-readable instructions
  • a tangible computer readable storage medium such as a hard disk drive, a flash memory, a read-only memory (ROM), a compact disk (CD), a digital versatile disk (DVD), a cache, a random- access memory (RAM) and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for
  • tangible computer readable storage medium is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals and to exclude transmission media.
  • tangible computer readable storage medium and “tangible machine readable storage medium” are used interchangeably.
  • FIGS. 14-17 may be implemented using coded instructions (e.g., computer and/or machine-readable instructions) stored on a non-transitory computer and/or machine-readable medium such as a hard disk drive, a flash memory, a read-only memory, a compact disk, a digital versatile disk, a cache, a random- access memory and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/or for caching of the information).
  • coded instructions e.g., computer and/or machine-readable instructions
  • a non-transitory computer and/or machine-readable medium such as a hard disk drive, a flash memory, a read-only memory, a compact disk, a digital versatile disk, a cache, a random- access memory and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/
  • non- transitory computer readable medium is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals and to exclude transmission media.
  • phrase “at least” is used as the transition term in a preamble of a claim, it is open-ended in the same manner as the term “comprising” is open ended.
  • FIG. 14 is a flowchart representative of an example method 1400 that may be executed at the example vehicle cart 102 of FIGS. 1-3 to automatically deploy the example vehicle cart 102 from the example cargo compartment 106 of the example vehicle 104 of FIGS. 1, 5 and 6.
  • the example method 1400 of FIG. 14 begins when the processor 254 of FIG. 2 determines whether one or more deployment control signal(s) have been received by the vehicle cart 102 of FIGS. 1-3 (block 1402). For example, the processor 254 may determine that the radio receiver 202 of the vehicle cart 102 of FIGS. 1-3 has received a deployment control signal from the remote control device 108 or the mobile device 110 of FIG. 1.
  • control of the example method 1400 proceeds to block 1404.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 of FIG. 2 to cause the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 to actuate and/or move corresponding ones of the front wheel(s) 218, 220 and/or the rear wheel(s) 238, 240 of FIG.
  • the control signal(s) provided by the processor 254 to the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 at block 1404 cause(s) corresponding ones of the front wheel(s) 218, 220 and/or the rear wheel (s) 238, 240 to rotate.
  • the rotation of the front wheel(s) 218, 220 and/or the rear wheel(s) 238, 240 causes the vehicle cart 102 of FIGS. 1-3 to move outward from a cargo compartment of a vehicle (e.g., the cargo compartment 106 of the vehicle 104 of FIGS. 1, 5 and 6) along an underlying surface thereof (e.g., along the base 602 of the cargo compartment 106 of FIGS. 1, 5 and 6).
  • the processor 254 of FIG. 2 determines whether one or more of the rear wheel(s) 238, 240 of the vehicle cart 102 of FIGS. 1-3 is/are in contact with an underlying surface (block 1406).
  • the processor 254 may compare data and/or information sensed, measured and/or detected by one or more of the rear wheel contact sensor(s) 246, 248 of FIG. 2 to one or more threshold(s) to determine whether the rear wheel(s) 238, 240 corresponding to the rear wheel contact sensor(s) 246, 248 is/are is in contact with an underlying surface.
  • the processor 254 determines that a force value sensed, measured and/or detected by a contact sensor (e.g., rear wheel contact sensor 246) satisfies (e.g., exceeds) a force threshold, the processor 254 determines that the corresponding wheel (e.g., rear wheel 238) of the vehicle cart 102 is in contact with an underlying surface. If the processor 254 instead determines in such an example that a force value sensed, measured and/or detected by the contact sensor (e.g., rear wheel contact sensor 246) does not satisfy (e.g., does not exceed) the force threshold, the processor 254 determines that the corresponding wheel (e.g., rear wheel 238) is not in contact with an underlying surface.
  • a contact sensor e.g., rear wheel contact sensor 246
  • control of the example method 1400 proceeds to block 1408. If the processor 254 instead determines at block 1406 that the rear wheels 238, 240 of the vehicle cart 102 are in contact with an underlying surface, control of the example method 1400 proceeds to block 1410.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to the rear leg actuator(s) 234, 236 of FIG. 2 to cause the rear leg actuator(s) 234, 236 to actuate and/or move corresponding ones of the rear leg(s) 230, 232 of FIG. 2 (block 1408).
  • the control signal(s) provided by the processor 254 to the rear leg actuator(s) 234, 236 at block 1408 cause(s) corresponding ones of the rear leg(s) 230, 232 to extend.
  • control of the example method 1400 returns to block 1406.
  • the control signal(s) provided by the processor 254 to the rear leg actuator(s) 234, 236 at block 1408 cause(s) corresponding ones of the rear leg(s) 230, 232 to extend until the processor 254 determines at block 1406 that corresponding ones of the rear wheel(s) 238, 240 is/are in contact with an underlying surface.
  • the processor 254 of FIG. 2 determines whether one or more of the front wheel(s) 218, 220 of the vehicle cart 102 of FIGS. 1 -3 is/are in contact with an underlying surface (block 1410). For example, the processor 254 may compare data and/or information sensed, measured and/or detected by one or more of the front wheel contact sensor(s) 226, 228 of FIG. 2 to one or more threshold(s) to determine whether the front wheel(s) 218, 220 corresponding to the front wheel contact sensor(s) 226, 228 is/are is in contact with an underlying surface.
  • the processor 254 determines that a force value sensed, measured and/or detected by a contact sensor (e.g., front wheel contact sensor 226) satisfies (e.g., exceeds) a force threshold, the processor 254 determines that the corresponding wheel (e.g., front wheel 218) of the vehicle cart 102 is in contact with an underlying surface. If the processor 254 instead determines in such an example that a force value sensed, measured and/or detected by the contact sensor (e.g., front wheel contact sensor 226) does not satisfy (e.g., does not exceed) the force threshold, the processor 254 determines that the corresponding wheel (e.g., front wheel 218) is not in contact with an underlying surface.
  • control of the example method 1400 proceeds to block 1412. If the processor 254 instead determines at block 1410 that the front wheels 218, 220 of the vehicle cart 102 are in contact with an underlying surface, control of the example method 1400 proceeds to block 1414.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to the front leg actuator(s) 214, 216 of FIG. 2 to cause the front leg actuator(s) 214, 216 to actuate and/or move corresponding ones of the front leg(s) 210, 212 of FIG. 2 (block 1412).
  • the control signal(s) provided by the processor 254 to the front leg actuator(s) 214, 216 at block 1412 cause(s) corresponding ones of the front leg(s) 210, 212 to extend.
  • control of the example method 1400 returns to block 1410.
  • control signal(s) provided by the processor 254 to the front leg actuator(s) 214, 216 at block 1412 cause(s) corresponding ones of the front leg(s) 210, 212 to extend until the processor 254 determines at block 1410 that corresponding ones of the front wheel(s) 218, 220 is/are in contact with an underlying surface.
  • the processor 254 of FIG. 2 determines whether the vehicle cart 102 of FIGS. 1 -3 is level (block 1414). For example, the processor 254 may compare data and/or information sensed, measured and/or detected by the level sensor 252 of FIG. 2 to one or more threshold(s) to determine whether the vehicle cart 102 is level. In such an example, if the processor 254 determines that a rotational orientation value sensed, measured and/or detected by the level sensor 252 satisfies (e.g., exceeds) a balance threshold, the processor 254 determines that the vehicle cart 102 is not level.
  • a rotational orientation value sensed, measured and/or detected by the level sensor 252 satisfies (e.g., exceeds) a balance threshold
  • the processor 254 determines that the vehicle cart 102 is level. If the processor 254 determines at block 1414 that the vehicle cart 102 is not level, control of the example method 1400 proceeds to block 1416. If the processor 254 instead determines at block 1414 that the vehicle cart 102 is level, the example method 1400 ends.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) 234, 236 of FIG. 2 to cause the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) to actuate and/or move corresponding ones of the front leg(s) 210, 212 and/or the rear leg(s) 230, 232 of FIG. 2 (block 1416).
  • control signal(s) provided by the processor 254 to the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) 234, 236 at block 1416 cause(s) corresponding ones of the front leg(s) 210, 212 and/or the rear leg(s) 230, 232 to extend and/or retract.
  • control of the example method 1400 returns to block 1414.
  • control signal(s) provided by the processor 254 to the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) 234, 236 at block 1416 cause(s) corresponding ones of the front leg(s) 210, 212 and/or the rear leg(s) 230, 232 to extend and/or retract until the processor 254 determines at block 1414 that the vehicle cart 102 is level.
  • FIG. 15 is a flowchart representative of an example method 1500 that may be executed at the example vehicle cart 102 of FIGS. 1-3 to automatically maneuver the vehicle cart 102 toward the example vehicle 104 of FIGS. 1, 5 and 6, the example remote control device 108 of FIGS. 1 and 7, and/or the example mobile device 110 of FIGS. 1 and 8.
  • the example method 1500 of FIG. 15 begins when the processor 254 of FIG. 2 determines whether data corresponding to a location of a target object (e.g., the vehicle 104, the remote control device 108 or the mobile device 110 of FIG. 1) has been received by the vehicle cart 102 of FIGS. 1-3 (block 1502). For example, the processor 254 may determine that the radio receiver 202 of the vehicle cart 102 of FIGS.
  • a target object e.g., the vehicle 104, the remote control device 108 or the mobile device 110 of FIG.
  • control of the example method 1500 proceeds to block 1504.
  • the processor 254 of FIG. 2 identifies a location of the vehicle cart 102 of FIGS. 1-3 (block 1504).
  • the processor 254 may identify a location of the vehicle cart 102 based on one or more signal(s) received by the GPS receiver 206 of the vehicle cart 102 of FIGS. 1-4.
  • the processor 254 of FIG. 2 compares the location of the vehicle cart 102 identified at block 1504 to the location of the target object identified at block 1502 (block 1506).
  • the processor 254 may compare the location of the vehicle cart 102 to the location of the mobile device 110.
  • the processor 254 of FIG. 2 determines a pathway between the vehicle cart 102 and the target object along which the vehicle cart 102 may be maneuvered, steered and/or otherwise navigated from its identified location (e.g., a current location) to reach the identified location (e.g., a destination location) of the target object (block 1508).
  • the processor 254 may determine a pathway between the vehicle cart 102 and the mobile device 110.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 of FIG.
  • the control signal(s) provided by the processor 254 to the front wheel actuator(s) 222, 224 and/or the rear wheel actuator(s) 242, 244 at block 1404 cause(s) corresponding ones of the front wheel(s) 218, 220 and/or the rear wheel (s) 238, 240 to rotate.
  • the rotation of the front wheel(s) 218, 220 and/or the rear wheel(s) 238, 240 causes the vehicle cart 102 of FIGS. 1-3 to move along the pathway determined by the processor 254 at block 1508.
  • the processor 254 of FIG. 2 determines whether the vehicle cart 102 of FIGS. 1-3 is level (block 1512). For example, the processor 254 may compare data and/or information sensed, measured and/or detected by the level sensor 252 of FIG. 2 to one or more threshold(s) to determine whether the vehicle cart 102 is level. In such an example, if the processor 254 determines that a rotational orientation value sensed, measured and/or detected by the level sensor 252 satisfies (e.g., exceeds) a balance threshold, the processor 254 determines that the vehicle cart 102 is not level.
  • a rotational orientation value sensed, measured and/or detected by the level sensor 252 satisfies (e.g., exceeds) a balance threshold
  • the processor 254 determines that the vehicle cart 102 is level. If the processor 254 determines at block 1512 that the vehicle cart 102 is not level, control of the example method 1500 proceeds to block 1514. If the processor 254 instead determines at block 1512 that the vehicle cart 102 is level, control of the example method 1500 proceeds to block 1516.
  • the processor 254 of FIG. 2 provides one or more control signal(s) to the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) 234, 236 of FIG. 2 to cause the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) to actuate and/or move corresponding ones of the front leg(s) 210, 212 and/or the rear leg(s) 230, 232 of FIG. 2 (block 1514).
  • control signal(s) provided by the processor 254 to the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) 234, 236 at block 1514 cause(s) corresponding ones of the front leg(s) 210, 212 and/or the rear leg(s) 230, 232 to extend and/or retract.
  • control of the example method 1500 returns to block 1512.
  • control signal(s) provided by the processor 254 to the front leg actuator(s) 214, 216 and/or the rear leg actuator(s) 234, 236 at block 1514 cause(s) corresponding ones of the front leg(s) 210, 212 and/or the rear leg(s) 230, 232 to extend and/or retract until the processor 254 determines at block 1512 that the vehicle cart 102 is level.
  • the processor 254 of FIG. 2 determines whether the vehicle cart 102 of FIGS. 1-3 is approaching an obstacle (block 1516). For example, the processor 254 may compare data and/or information sensed, measured and/or detected by the obstacle sensor 250 of FIG. 2 to one or more threshold(s) to determine whether the vehicle cart 102 is approaching an obstacle sensor. In such an example, if the processor 254 determines that a distance value sensed, measured and/or detected by the obstacle sensor 250 does not satisfy (e.g., does not exceed) the distance threshold, the processor 254 determines that the vehicle cart 102 is approaching an obstacle.
  • a distance value sensed, measured and/or detected by the obstacle sensor 250 does not satisfy (e.g., does not exceed) the distance threshold
  • the processor 254 determines that the vehicle cart 102 is not approaching an obstacle. If the processor 254 determines at block 1516 that the vehicle cart 102 is approaching an obstacle, control of the example method 1500 proceeds to block 1518. If the processor 254 instead determines at block 1516 that the vehicle cart 102 is not approaching an obstacle, control of the example method 1500 proceeds to block 1520. [0149] At block 1518, the processor 254 of FIG. 2 determines whether an alternate pathway between the vehicle cart 102 of FIGS. 1-3 and the target object is necessary (block 1518).
  • the processor 254 may determine at block 1518 that an alternate pathway between the vehicle cart 102 and the mobile device 110 is necessary. If the processor 254 determines at block 1518 that an alternate pathway between the vehicle cart 102 and the target object is necessary, control of the example method 1500 returns to block 1504. If the processor 254 instead determines at block 1518 that that an alternate pathway between the vehicle cart 102 and the target object is not necessary, control of the example method 1500 proceeds to block 1520.
  • the processor 254 of FIG. 2 determines whether data corresponding to an updated location of the target object has been received by the vehicle cart 102 of FIGS. 1- 3 (block 1502). For example, the processor 254 may determine that the radio receiver 202 of the vehicle cart 102 of FIGS. 1-3 has received data corresponding to an updated location (e.g., updated relative to the location determined at block 1502) of the mobile device 110 of FIG. 1. If the processor 254 determines at block 1520 that data corresponding to an updated location of the target object has been received, control of the example method 1500 retums to block 1504. If the processor 254 instead determines at block 1520 that data corresponding to an updated location of the target object has not been received, control of the example method 1500 proceeds to block 1522.
  • the processor 254 instead determines at block 1520 that data corresponding to an updated location of the target object has not been received.
  • the processor 254 of FIG. 2 determines whether the vehicle cart 102 of FIGS. 1-3 has reached the location of the target object (block 1522). For example, the processor 254 may determine that the vehicle cart 102 has reached the location of the mobile device 110 based on a comparison of an updated location of the vehicle cart 102 to location and/or updated location of the mobile device 110. If the processor 254 determines at block 1522 that the vehicle cart 102 has not reached the location of the target object, control of the example method 1500 returns to block 1510. If the processor 254 instead determines at block 1522 that the vehicle cart 102 has reached the location of the target object, the example method 1500 ends.
  • FIG. 16 is a flowchart representative of an example method 1600 that may be executed at the example vehicle cart 102 of FIGS. 1-3 to provide a shopping itinerary.
  • the example method 1600 of FIG. 16 begins when the processor 254 of FIG. 2 determines whether shopping list data has been received by the vehicle cart 102 of FIGS. 1-3 (block 1402). For example, the processor 254 may determine that the radio receiver 202 of the vehicle cart 102 of FIGS. 1-3 has received shopping list data from the mobile device 110 of FIG. 1. If the processor 254 determines at block 1602 that shopping list data has not yet been received, control of the example method 1600 remains at block 1602. If the processor 254 instead determines at block 1602 that a shopping list data has been received, control of the example method 1600 proceeds to block 1604.
  • the processor 254 of FIG. 2 identifies one or more store location(s) at which one or more item(s) on the shopping list are available for purchase (block 1604). For example, based on the shopping list data received by the vehicle cart 102, the processor 254 may identify the locations of one or more of the example first, second and/or third store(s) 114, 116, 118 of FIG. 1 as a store location at which a particular item on the shopping list may be purchased.
  • the processor 254 of FIG. 2 identifies one or more price(s) at which one or more items(s) on the shopping list are available for purchase at the identified store location(s) (block 1606). For example, based on the shopping list data received by the vehicle cart 102 and the store location(s) identified by the processor 254 at block 1604, the processor 254 may identify a first price at which a particular item is available for purchase from the first store 114 of FIG. 1, and a second price at which the particular item is available for purchase from the second store 116 of FIG. 1.
  • the processor 254 of FIG. 2 generates a shopping itinerary for display via the user interface 208 of the vehicle cart 102 of FIGS. 1-3 (block 1608).
  • the processor 254 may generate a shopping itinerary based on the shopping list data, the store location(s) identified by the processor 254 at block 1604, and/or the price(s) identified by the processor 254 at block 1606.
  • the processor 254 may generate the shopping itinerary based on the identified store location(s) from which each item on the shopping list is available for purchase at its lowest price.
  • the processor 254 may generate the shopping itinerary based on the proximity of the identified store location(s) from which each item on the shopping list is available for purchase, with or without consideration of the identified price(s) at which the items are available for purchase from such store location(s).
  • the shopping itinerary generated by the processor 254 may include routing and/or directions to be followed by the vehicle cart 102 of FIGS. 1-3 and/or the vehicle 104 of FIGS. 1, 5 and 6 in the course of a user purchasing the items on the shopping itinerary.
  • the processor 254 of FIG. 2 determines whether an indication has been received by the vehicle cart 102 of FIGS. 1-3 corresponding to a purchase of one or more of the item(s) on the shopping itinerary (block 1610). For example, the processor 254 may determine that the user interface 208 of the vehicle cart 102 of FIGS. 1-3 has received an input corresponding to a purchase of one or more of the item(s) on the shopping itinerary. If the processor 254 determines at block 1610 that an indication corresponding to the purchase of one or more item(s) on the shopping itinerary has not yet been received, control of the example method 1600 remains at block 1610. If the processor 254 instead determines at block 1610 that an indication corresponding to the purchase of one or more item(s) on the shopping itinerary has been received, control of the example method 1600 proceeds to block 1612.
  • the processor 254 of FIG. 2 updates the shopping itinerary (block 1612). For example, based on the received indication corresponding to the purchase of one or more item(s) on the shopping itinerary, the processor 254 may update the shopping itinerary to indicate that the corresponding item(s) have been purchased. In some examples, the processor 254 may update the shopping itinerary by removing the corresponding item(s), corresponding store location(s) and/or corresponding price(s) from the shopping itinerary.
  • the processor 254 of FIG. 2 determines whether an indication has been received by the vehicle cart 102 of FIGS. 1-3 corresponding to completion of the shopping itinerary (block 1614). For example, the processor 254 may determine that the user interface 208 of the vehicle cart 102 of FIGS. 1-3 has received an input corresponding to completion of the shopping itinerary. If the processor 254 determines at block 1614 that an indication corresponding to completion of the shopping itinerary has not yet been received, control of the example method 1600 returns to block 1610. If the processor 254 instead determines at block 1614 that an indication corresponding to completion of the shopping itinerary has been received, the example method 1600 ends.
  • FIG. 17 is a flowchart representative of an example method 1700 that may be executed at the example vehicle 104 of FIGS. 1, 5 and 6 to automatically deploy the example vehicle cart 102 of FIGS. 1-3 from the example cargo compartment 106 of the example vehicle 104.
  • the example method 1700 of FIG. 17 begins when the processor 522 of FIG. 5 determines whether one or more deployment control signal(s) have been received by the vehicle 104 of FIGS. 1, 5 and 6 (block 1702). For example, the processor 522 may determine that the radio receiver 502 of the vehicle 104 of FIGS. 1, 5 and 6 has received a deployment control signal from the remote control device 108 or the mobile device 110 of FIG. 1.
  • control of the example method 1700 proceeds to block 1704.
  • the processor 522 of FIG. 5 provides one or more control signal(s) to the liftgate actuator 512 of FIG. 5 to cause the liftgate actuator 512 to actuate and/or move the liftgate 510 of FIG. 5 from a closed position to an open position (block 1704).
  • the control signal(s) provided by the processor 522 to the liftgate actuator 512 at block 1704 cause(s) the liftgate 510 to open to enable a vehicle cart (e.g., the vehicle cart 102 of FIGS. 1-3) stowed within the cargo compartment 106 of the vehicle 104 to be
  • a vehicle cart e.g., the vehicle cart 102 of FIGS. 1-3
  • the processor 522 of FIG. 5 provides one or more control signal(s) to the rail actuator(s) 518, 520 of FIG. 5 to cause the rail actuator(s) 518, 520 to actuate and/or move corresponding ones of the rail(s) 514, 516 of FIG. 5 from a stowed position to a deployed position (block 1706).
  • the control signal(s) provided by the processor 522 to the rail actuator(s) 518, 520 at block 1706 cause(s) corresponding ones of the rail(s) 514, 516 to deploy to enable a vehicle cart (e.g., the vehicle cart 102 of FIGS. 1-3) engaged and or supported by the rail(s) 514, 516 to be automatically deployed from the cargo compartment 106 of the vehicle 104.
  • the example method 1700 ends.
  • FIG. 18 is an example processor platform 1800 capable of executing instructions to implement the methods of FIGS. 14-16 and the example vehicle cart 102 of FIGS. 1-3.
  • the processor platform 1800 of the illustrated example includes a processor 254.
  • the processor 254 of the illustrated example is hardware.
  • the processor 254 can be implemented by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired family or manufacturer.
  • the processor 254 of the illustrated example includes a local memory 1802 (e.g., a cache).
  • the processor 254 of the illustrated example is in communication with one or more example sensors 1804 via a bus 1806.
  • the example sensors 1804 include the example front wheel contact sensors 226, 228, the example rear wheel contact sensors 246, 248, the example obstacle sensor 250 and the example level sensor 252 of FIG. 2.
  • the processor 254 of the illustrated example is also in communication with one or more example actuators 1808 via the bus 1806.
  • the example actuators 1808 include the example front leg actuators 214, 216, the example front wheel actuators 222, 224, the example rear leg actuators 234, 236 and the example rear wheel actuators 242, 244 of FIG. 2.
  • the processor 254 of the illustrated example is also in communication with a main memory including a volatile memory 1810 and a non-volatile memory 1812 via the bus 1806.
  • the volatile memory 1810 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of random access memory device.
  • the non-volatile memory 1812 may be implemented by flash memory and/or any other desired type of memory device. Access to the volatile memory 1810 and the non-volatile memory 1812 is controlled by a memory controller.
  • the processor 254 of the illustrated example is also in communication with one or more mass storage devices 1814 for storing software and/or data.
  • mass storage devices 1814 include floppy disk drives, hard drive disks, compact disk drives, Blu- ray disk drives, RAID systems, and digital versatile disk (DVD) drives.
  • the mass storage device 1814 includes the example memory 256 of FIG. 2.
  • the processor platform 1800 of the illustrated example also includes an interface circuit 1816.
  • the interface circuit 1816 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.
  • one or more input device(s) 260 are connected to the interface circuit 1816.
  • the input device(s) 260 permit(s) a user to enter data and commands into the processor 254.
  • the input device(s) 260 can be implemented by, for example, an audio sensor, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a trackpad, a trackball, isopoint, a voice recognition system, a button, a microphone, and/or a liquid crystal display.
  • One or more output device(s) 262 are also connected to the interface circuit 1816 of the illustrated example.
  • the output device(s) 262 can be implemented, for example, by a light emitting diode, an organic light emitting diode, a liquid crystal display, a touchscreen and/or a speaker.
  • the interface circuit 1816 of the illustrated example may, thus, include a graphics driver such as a graphics driver chip and/or processor.
  • the input device(s) 260, the output device(s) 262 and the interface circuit 1816 collectively form the example user interface 208 of FIG. 2.
  • the processor platform 1800 of the illustrated example also includes a network communication interface circuit 1818.
  • the network communication interface circuit 1818 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.
  • the network communication interface circuit 1818 includes the example radio receiver 202, the example radio transmitter 204 and the example GPS receiver 206 of FIG. 2 to facilitate the exchange of data and/or signals with external machines (e.g., the vehicle 104 of FIGS. 1, 5 and 6, the remote control device 108 of FIGS. 1 and 7, and/or the mobile device 110 of FIGS. 1 and 8) via a network 1820 (e.g., a cellular network, a wireless local area network (WLAN), a GPS network, etc.).
  • WLAN wireless local area network
  • Coded instructions 1822 for implementing the methods of FIGS. 14-16 may be stored in the local memory 1802, in the volatile memory 1810, in the non-volatile memory 1812, in the mass storage device 1814, and/or on a removable tangible computer readable storage medium such as a CD or DVD.
  • FIG. 19 is an example processor platform 1900 capable of executing instructions to implement the method of FIG. 17 and the example vehicle 104 of FIGS. 1, 5 and 6.
  • the processor platform 1900 of the illustrated example includes a processor 522.
  • the processor 522 of the illustrated example is hardware.
  • the processor 522 can be implemented by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired family or manufacturer.
  • the processor 522 of the illustrated example includes a local memory 1902 (e.g., a cache).
  • the processor 522 of the illustrated example is in communication with one or more example actuators 1908 via a bus 1906.
  • the example actuators 1908 include the example liftgate actuator 512 and the example rail actuators 518, 520 of FIG. 5.
  • the processor 522 of the illustrated example is also in communication with a main memory including a volatile memory 1910 and a non-volatile memory 1912 via the bus 1906.
  • the volatile memory 1910 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of random access memory device.
  • the non-volatile memory 1912 may be implemented by flash memory and/or any other desired type of memory device. Access to the volatile memory 1910 and the non-volatile memory 1912 is controlled by a memory controller.
  • the processor 522 of the illustrated example is also in communication with one or more mass storage devices 1914 for storing software and/or data.
  • mass storage devices 1914 include floppy disk drives, hard drive disks, compact disk drives, Blu- ray disk drives, RAID systems, and digital versatile disk (DVD) drives.
  • the mass storage device 1914 includes the example memory 524 of FIG. 5.
  • the processor platform 1900 of the illustrated example also includes an interface circuit 1916.
  • the interface circuit 1916 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.
  • one or more input device(s) 528 are connected to the interface circuit 1916.
  • the input device(s) 528 permit(s) a user to enter data and commands into the processor 522.
  • the input device(s) 528 can be implemented by, for example, an audio sensor, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a trackpad, a trackball, isopoint, a voice recognition system, a button, a microphone, and/or a liquid crystal display.
  • One or more output device(s) 530 are also connected to the interface circuit 1916 of the illustrated example.
  • the output device(s) 530 can be implemented, for example, by a light emitting diode, an organic light emitting diode, a liquid crystal display, a touchscreen and/or a speaker.
  • the interface circuit 1916 of the illustrated example may, thus, include a graphics driver such as a graphics driver chip and/or processor.
  • a graphics driver such as a graphics driver chip and/or processor.
  • the input device(s) 528, the output device(s) 530 and the interface circuit 1916 collectively form the example user interface 508 of FIG. 5.
  • the processor platform 1900 of the illustrated example also includes a network communication interface circuit 1918.
  • the network communication interface circuit 1918 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.
  • the network communication interface circuit 1918 includes the example radio receiver 502, the example radio transmitter 504 and the example GPS receiver 506 of FIG. 5 to facilitate the exchange of data and/or signals with external machines (e.g., the vehicle cart 102 of FIGS. 1- 3, the remote control device 108 of FIGS. 1 and 7, and/or the mobile device 110 of FIGS. 1 and 8) via a network 1920 (e.g., a cellular network, a wireless local area network (WLAN), a GPS network, etc.).
  • WLAN wireless local area network
  • Coded instructions 1922 for implementing the method of FIG. 17 may be stored in the local memory 1902, in the volatile memory 1910, in the non-volatile memory 1912, in the mass storage device 1914, and/or on a removable tangible computer readable storage medium such as a CD or DVD.
  • the disclosed vehicle carts are automatically deployable from a cargo compartment of a vehicle. It will further be appreciated that the disclosed vehicle carts are automatically maneuverable toward one or more target object(s) such as a remote control device, a mobile device, or a vehicle from which the vehicle cart has been deployed. It will also be appreciated that the disclosed vehicle carts provide a shopping itinerary based on data corresponding to a shopping list obtained from a remotely located device such as a mobile device.
  • the vehicle carts disclosed herein advantageously provide a user with the ability to forego involvement with deploying the vehicle cart from a cargo compartment of a vehicle, navigating the vehicle cart once deployed, and/or obtaining a shopping itinerary.
  • an automatically deployable vehicle cart comprises a base, a front leg coupled to the base, the front leg being extendable relative to the base by a front leg actuator operatively coupled to the front leg, a rear leg coupled to the base, the rear leg being extendable relative to the base by a rear leg actuator operatively coupled to the rear leg, a front wheel coupled to the front leg, the front wheel being rotatable by a front wheel actuator operatively coupled to the front wheel, a rear wheel coupled to the rear leg, the rear wheel being rotatable by a rear wheel actuator operatively coupled to the rear wheel, a processor, and a memory.
  • the memory of the vehicle cart includes computer readable instructions which, when executed, cause the processor to provide a first control signal to at least one of the front wheel actuator or the rear wheel actuator, the first control signal to cause the at least one of the front wheel actuator or the rear wheel actuator to respectively actuate the front wheel or the rear wheel to automatically deploy the vehicle cart from a cargo compartment of a vehicle.
  • the first control signal is in response to a receiver of the vehicle cart receiving a deployment control signal from a remote control device.
  • the first control signal is in response to a user interface of the vehicle cart receiving an input corresponding to a deployment command.
  • the memory of the vehicle cart includes computer readable instructions which, when executed, cause the processor, in response to determining that a first value obtained from a rear wheel contact sensor operatively coupled to the rear wheel does not satisfy a first threshold, to provide a second control signal to the rear leg actuator, the second control signal to cause the rear leg actuator to extend the rear leg.
  • the second control signal causes the rear leg actuator to extend the rear leg until the processor determines that a second value obtained from the rear wheel contact sensor subsequent to the first value satisfies the first threshold.
  • the memory of the vehicle cart includes computer readable instructions which, when executed, are to cause the processor, in response to determining that a third value obtained from a front wheel contact sensor operatively coupled to the front wheel does not satisfy a second threshold, to provide a third control signal to the front leg actuator, the third control signal to cause the front leg actuator to extend the front leg.
  • the third control signal causes the front leg actuator to extend the front leg until the processor determines that a fourth value obtained from the front wheel contact sensor subsequent to the third value satisfies the second threshold.
  • the vehicle cart further comprises an obstacle sensor to detect a distance between an obstacle and the vehicle cart. In some disclosed examples, the vehicle cart further comprises a level sensor to detect a rotational orientation of the vehicle cart. In some disclosed examples, the rear wheel of the vehicle cart is a first wheel of a set of stair-climbing wheels.
  • the vehicle cart further comprises a user interface to display a shopping list based on shopping list data received from a mobile device.
  • the memory of the vehicle cart includes instructions which, when executed, cause the processor to identify locations of stores from which an item on the shopping list may be purchased, identify prices at which the item may respectively be purchased from corresponding ones of the locations, and present data corresponding to the locations and the prices for display by the user interface.
  • the memory of the vehicle cart includes instructions which, when executed, cause the processor to provide a tracking control signal to at least one of the front wheel actuator or the rear wheel actuator.
  • the tracking control signal causes the at least one of the front wheel actuator or the rear wheel actuator to respectively actuate the front wheel or the rear wheel to automatically maneuver the vehicle cart to a destination location corresponding to a current location of one of a remote control device, a mobile device, or the vehicle.
  • the respective identification and/or ordering of the "first,” “second” and “third” control signals and/or the "first,” “second,” “third” and “fourth” values referenced above may differ.
  • the memory of the vehicle cart includes computer readable instructions which, when executed, cause the processor to provide a first control signal to the rear leg actuator in response to determining that a first value obtained from a rear wheel contact sensor operatively coupled to the rear wheel does not satisfy a first threshold, the first control signal to cause the rear leg actuator to extend the rear leg, and to provide a second control signal to the front leg actuator in response to determining that a second value obtained from a front wheel contact sensor operatively coupled to the front wheel does not satisfy a second threshold, the second control signal to cause the front leg actuator to extend the front leg.
  • the first control signal causes the rear leg actuator to extend the rear leg until the processor determines that a third value obtained from the rear wheel contact sensor subsequent to the first value satisfies the first threshold.
  • the second control signal causes the front leg actuator to extend the front leg until the processor determines that a fourth value obtained from the front wheel contact sensor subsequent to the second value satisfies the second threshold.
  • the first control signal is further in response to a third control signal provided by the processor to at least one of the front wheel actuator or the rear wheel actuator, the third control signal to cause the at least one of the front wheel actuator or the rear wheel actuator to respectively actuate the front wheel or the rear wheel to automatically deploy the vehicle cart from a cargo compartment of a vehicle.
  • the first control signal is further in response to a rail actuator of a vehicle moving a rail of the vehicle to a first position, the vehicle cart being movably engaged with the rail of the vehicle, the rear wheel of the vehicle cart not being in contact with an underlying surface when the rail is moved to the first position.
  • the second control signal is further in response to the rail actuator of the vehicle moving the rail of the vehicle to a second position, the front wheel of the vehicle cart not being in contact with the underlying surface when the rail is moved to the second position.
  • a method for automatically deploying a vehicle cart from a cargo compartment of a vehicle comprises providing, via a processor of the vehicle cart, a first control signal to a rear leg actuator operatively coupled to a rear leg of the vehicle cart to cause the rear leg actuator to extend the rear leg, the rear leg being coupled to a base of the vehicle cart, the rear leg being extendable relative to the base by the rear leg actuator, the first control signal being in response to determining that a first value obtained from a rear wheel contact sensor operatively coupled to a rear wheel of the vehicle cart does not satisfy a first threshold.
  • the first control signal causes the rear leg actuator to extend the rear leg until the processor determines that a third value obtained from the rear wheel contact sensor subsequent to the first value satisfies the first threshold.
  • the method comprises providing, via the processor of the vehicle cart, a second control signal to a front leg actuator operatively coupled to a front leg of the vehicle cart to cause the front leg actuator to extend the front leg, the front leg being coupled to the base of the vehicle cart, the front leg being extendable relative to the base by the front leg actuator, the second control signal being in response to determining that a second value obtained from a front wheel contact sensor operatively coupled to a front wheel of the vehicle cart does not satisfy a second threshold.
  • the second control signal causes the front leg actuator to extend the front leg until the processor determines that a fourth value obtained from the front wheel contact sensor subsequent to the second value satisfies the second threshold.
  • the first control signal of the method is further in response to a third control signal provided by the processor to at least one of a front wheel actuator operatively coupled to the front wheel of the vehicle or a rear wheel actuator operatively coupled to the rear wheel of the vehicle, the third control signal to cause the at least one of the front wheel actuator or the rear wheel actuator to respectively actuate the front wheel or the rear wheel to automatically deploy the vehicle cart from the cargo compartment of the vehicle.
  • the first control signal of the method is further in response to a rail actuator of the vehicle moving a rail of the vehicle to a first position, the vehicle cart being movably engaged with the rail of the vehicle, the rear wheel of the vehicle cart not being in contact with an underlying surface when the rail is moved to the first position.
  • the second control signal of the method is further in response to the rail actuator of the vehicle moving the rail of the vehicle to a second position, the front wheel of the vehicle cart not being in contact with the underlying surface when the rail is moved to the second position.

Landscapes

  • Engineering & Computer Science (AREA)
  • Chemical & Material Sciences (AREA)
  • Combustion & Propulsion (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Handcart (AREA)

Abstract

Les chariots de véhicule à déploiement automatique de l'invention comprennent une base, des pieds avant et arrière accouplés à la base et pouvant s'étendre par rapport à celle-ci grâce à des actionneurs de pied avant et arrière correspondants accouplés fonctionnellement aux pieds avant et arrière correspondants, des roues avant et arrière accouplées aux pieds avant et arrière correspondants et pouvant être mises en rotation par des actionneurs de roue avant et arrière correspondants accouplés fonctionnellement aux roues avant et arrières correspondantes, un processeur et une mémoire. La mémoire comprend des instructions lisibles par ordinateur qui, lorsqu'elles sont exécutées, amènent le processeur à fournir un premier signal de commande à au moins un des actionneurs de roue avant ou de roue arrière pour faire actionner respectivement par ledit actionneur de roue avant ou de roue arrière la roue avant ou arrière correspondante pour déployer automatiquement le chariot de véhicule à partir d'un coffre d'un véhicule.
PCT/US2016/043362 2016-07-21 2016-07-21 Chariots de véhicule à déploiement automatique WO2018017102A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2016/043362 WO2018017102A1 (fr) 2016-07-21 2016-07-21 Chariots de véhicule à déploiement automatique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2016/043362 WO2018017102A1 (fr) 2016-07-21 2016-07-21 Chariots de véhicule à déploiement automatique

Publications (1)

Publication Number Publication Date
WO2018017102A1 true WO2018017102A1 (fr) 2018-01-25

Family

ID=60992406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/043362 WO2018017102A1 (fr) 2016-07-21 2016-07-21 Chariots de véhicule à déploiement automatique

Country Status (1)

Country Link
WO (1) WO2018017102A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019191383A1 (fr) * 2018-03-29 2019-10-03 Toyota Research Institute, Inc. Systèmes et procédés pour un robot de chariot autonome
CN112996709A (zh) * 2018-11-26 2021-06-18 购物车私人有限公司 购物车
KR20220087642A (ko) * 2020-12-17 2022-06-27 (주)우신특장 차량용 충전식 적재카트
US11590997B1 (en) * 2018-08-07 2023-02-28 Staples, Inc. Autonomous shopping cart
US11630447B1 (en) 2018-08-10 2023-04-18 Staples, Inc. Automated guided vehicle for transporting objects

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5649718A (en) * 1996-08-01 1997-07-22 Groglio; Valerie Defede Utility cart
US20010052680A1 (en) * 1997-12-30 2001-12-20 Eugene Kevin Bennington Mobile cart
US20020149176A1 (en) * 2001-04-11 2002-10-17 Miller Timothy J. Versatile cart for transporting packages to a vehicle
US7509187B2 (en) * 2005-02-28 2009-03-24 The Braun Corporation Wheelchair lift with a rotary sensor used to determine lift position
US20100032911A1 (en) * 2006-03-06 2010-02-11 Sterraclimb Llc Stair-Climbing Wheeled Vehicle
US7865398B2 (en) * 2003-09-30 2011-01-04 Microsoft Corporation Radio frequency identification tag on picking container and display of picklist to order filler
US20120123673A1 (en) * 2010-11-15 2012-05-17 Microsoft Corporation Generating a map that includes location and price of products in a shopping list
US20130006807A1 (en) * 2011-06-01 2013-01-03 International Business Machines Corporation Guideline-Based Food Purchase Management
US20160025114A1 (en) * 2014-07-24 2016-01-28 Google Inc. Actuator Limit Controller
US9393981B1 (en) * 2015-02-17 2016-07-19 Ftr Systems, Inc Foldable cart with rear guidance arrangement

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5649718A (en) * 1996-08-01 1997-07-22 Groglio; Valerie Defede Utility cart
US20010052680A1 (en) * 1997-12-30 2001-12-20 Eugene Kevin Bennington Mobile cart
US20020149176A1 (en) * 2001-04-11 2002-10-17 Miller Timothy J. Versatile cart for transporting packages to a vehicle
US7865398B2 (en) * 2003-09-30 2011-01-04 Microsoft Corporation Radio frequency identification tag on picking container and display of picklist to order filler
US7509187B2 (en) * 2005-02-28 2009-03-24 The Braun Corporation Wheelchair lift with a rotary sensor used to determine lift position
US20100032911A1 (en) * 2006-03-06 2010-02-11 Sterraclimb Llc Stair-Climbing Wheeled Vehicle
US20120123673A1 (en) * 2010-11-15 2012-05-17 Microsoft Corporation Generating a map that includes location and price of products in a shopping list
US20130006807A1 (en) * 2011-06-01 2013-01-03 International Business Machines Corporation Guideline-Based Food Purchase Management
US20160025114A1 (en) * 2014-07-24 2016-01-28 Google Inc. Actuator Limit Controller
US9393981B1 (en) * 2015-02-17 2016-07-19 Ftr Systems, Inc Foldable cart with rear guidance arrangement

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022082550A (ja) * 2018-03-29 2022-06-02 トヨタ リサーチ インスティテュート，インコーポレイティド 自律カートロボット用システム及び方法
US20190302775A1 (en) * 2018-03-29 2019-10-03 Toyota Research Institute, Inc. Systems and methods for an autonomous cart robot
CN111936369A (zh) * 2018-03-29 2020-11-13 丰田研究所股份有限公司 用于自主式推车机器人的系统和方法
US10908612B2 (en) 2018-03-29 2021-02-02 Toyota Research Institute, Inc. Systems and methods for an autonomous cart robot
JP2021511974A (ja) * 2018-03-29 2021-05-13 トヨタ リサーチ インスティテュート，インコーポレイティド 自律カートロボット用システム及び方法
WO2019191383A1 (fr) * 2018-03-29 2019-10-03 Toyota Research Institute, Inc. Systèmes et procédés pour un robot de chariot autonome
JP7128903B2 (ja) 2018-03-29 2022-08-31 トヨタ リサーチ インスティテュート，インコーポレイティド 自律カートロボット用システム及び方法
JP7443408B2 (ja) 2018-03-29 2024-03-05 トヨタ リサーチ インスティテュート，インコーポレイティド 自律カートロボット用システム及び方法
US11590997B1 (en) * 2018-08-07 2023-02-28 Staples, Inc. Autonomous shopping cart
US11630447B1 (en) 2018-08-10 2023-04-18 Staples, Inc. Automated guided vehicle for transporting objects
CN112996709A (zh) * 2018-11-26 2021-06-18 购物车私人有限公司 购物车
KR20220087642A (ko) * 2020-12-17 2022-06-27 (주)우신특장 차량용 충전식 적재카트
KR102474233B1 (ko) 2020-12-17 2022-12-07 (주)우신특장 차량용 충전식 적재카트

Similar Documents

Publication Publication Date Title
WO2018017102A1 (fr) Chariots de véhicule à déploiement automatique
US11008033B2 (en) Hitch-mounted robot systems
JP6980637B2 (ja) 無人搬送車、無人搬送車の制御方法、及びプログラム
JP7055836B2 (ja) 電動荷物
US10452077B2 (en) Autonomous personal mobility systems
US10625934B2 (en) Container transporter and methods
KR102144781B1 (ko) 물류 취급 차량용 물체 트래킹 및 조향 조작
CN105467991B (zh) 运输车辆的停止位置计算装置及具有该装置的运输车辆
US7066291B2 (en) Robot system
US20170293294A1 (en) Systems and methods for delivering containers using an autonomous dolly
EP2595025B1 (fr) Corps mobile autonome
US7344037B1 (en) Inventory storage and retrieval system and method with guidance for load-handling vehicle
US20130098700A1 (en) Foldable cart with tracking arrangement
JP7510942B2 (ja) 自動運転車用自律放送システム
CN109655053B (zh) 用于自主运输物体的车辆
KR20140074390A (ko) 물류 취급 차량용 조향 제어 조작들
US20190199110A1 (en) Transportation device storage and charging
WO2020010047A1 (fr) Systèmes et procédés de commande de robots de manutention autonomes
US20200207167A1 (en) Devices including deployable hitch assemblies and autonomous engagement systems incorporating the same
KR101840700B1 (ko) 스마트 골프 카트
KR101877488B1 (ko) 스마트 골프 카트
WO2017164911A1 (fr) Dispositif de transport
KR20220094748A (ko) 실내 위치 추적이 가능한 운반대차 및 운반대차 관리 시스템
US20230192168A1 (en) Self-Propelled Cart
US20240010431A1 (en) Automated mobile robots for automated delivery and assisted delivery

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16909694

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16909694

Country of ref document: EP

Kind code of ref document: A1