SYSTEM AND METHODS FOR EFFICIENT PARKING AND CHARGING OF ELECTRIFIED VEHICLES

Abstract

A system can include: a detector configured to provide input information; an electric vehicle; an electric vehicle charger; and a cloud server configured to execute a Simultaneous Parking and Charging Management (SPCM) method based on the input information, and communicate with the electric vehicle to assign a time for a certain electric vehicle charger based on a result of the executed SPCM method.

Claims

1. A system, comprising: at least one detector configured to provide input information; at least one electric vehicle; at least one electric vehicle charger; and a cloud server configured to: execute a Simultaneous Parking and Charging Management (SPCM) method based at least in part on the input information; and communicate with the at least one electric vehicle to assign a time for a certain one of the at least one electric vehicle charger based at least in part on a result of the executed SPCM method.

2. A method, comprising: using at least one sensor to collect information pertaining to current traffic conditions and parking/charging spot availability for a parking area; each of the at least one electric vehicle reporting a plurality of parameters upon entering the parking area; using a cloud server, solving an optimization problem based at least in part on the collected information and the plurality of parameters; and communicating to each of the at least one electric vehicle an assigned time and a location of a certain parking spot based on a result of the solved optimization problem.

3. The method of claim 2, further comprising using at least one sensor to monitor the price of electricity in real-time.

4. The method of claim 2, wherein the plurality of parameters includes at least one selected from the group consisting of: electric vehicle type, expected departure time, and user preference.

5. The method of claim 2, further comprising communicating to at least one of the at least one electric vehicle a path for the at least one vehicle to use to reach the certain parking spot.

6. The method of claim 5, further comprising optimizing the path the minimize energy consumption by the at least one electric vehicle.

7. The method of claim 2, wherein the at least one electric vehicle includes a Plug-in Hybrid Electric Vehicle (PHEV) and further wherein the PHEV is assigned immediately to a parking spot with a vehicle charger.

8. The method of claim 2, wherein the at least one electric vehicle includes a Plug-in Hybrid Electric Vehicle (PHEV) and further wherein the PHEV is tentatively assigned to at least one parking-only spot on a waitlist.

9. The method of claim 8, further comprising communicating to one of the at least one electric vehicle an instruction to leave the certain parking spot responsive to completion of a charge cycle.

10. The method of claim 9, further comprising communicating to the PHEV an instruction to proceed to the certain parking spot.

11. The method of claim 2, wherein the at least one electric vehicle includes an electric vehicle (EV) and further wherein the EV is assigned immediately to a parking spot with a vehicle charger.

12. The method of claim 2, wherein the at least one electric vehicle includes an electric vehicle (EV) and further wherein the EV is tentatively assigned to at least one parking-only spot on a waitlist.

13. The method of claim 12, further comprising communicating to one of the at least one electric vehicle an instruction to leave the certain parking spot responsive to completion of a charge cycle.

14. The method of claim 13, further comprising communicating to the EV an instruction to proceed to the certain parking spot.

15. The method of claim 2, wherein the at least one electric vehicle includes a Plug-in Hybrid Electric Vehicle (PHEV) and an electric vehicle (EV) and further wherein the PHEV and EV are each assigned immediately to a parking spot with a vehicle charger.

16. The method of claim 2, wherein the at least one electric vehicle includes a Plug-in Hybrid Electric Vehicle (PHEV) and an electric vehicle (EV) and further wherein the PHEV and EV are each tentatively assigned to at least one parking-only spot on a waitlist.

17. The method of claim 16, further comprising communicating to one of the at least one electric vehicle an instruction to leave the certain parking spot responsive to completion of a charge cycle.

18. The method of claim 17, further comprising communicating to the PHEV and EV an instruction to proceed to the certain parking spot.

19. The method of claim 2, wherein the plurality of parameters includes at least one selected from the group consisting of: electric vehicle type, expected departure time, and desired SoC at the end of the charge.

20. The method of claim 19, wherein at least one of the plurality of parameters is provided by the user or another software based on a future driving schedule.

21. The method of claim 2, further comprising: sending to the grid, electricity retailer, utility, or facility operator the current and predicted energy profile for charging the vehicles in the lot; the grid, electricity retailer, utility, or facility operator software accepting the request or deciding to reach a consensus on a different profile with the SPCM; and the SPCM re-computing the charging strategies for each vehicle.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The present disclosure will be better understood from reading the following description of non-limiting embodiments, with reference to the attached drawings, wherein below:

[0010] FIG. 1 illustrates an example of a control process for parking and charging management in accordance with certain implementations of the disclosed technology; and

[0011] FIG. 2 illustrates an example of system data flow in accordance with certain implementations of the disclosed technology.

DETAILED DESCRIPTION

[0012] Embodiments of the present disclosure may leverage Infrastructure. With sensors to detect parking/charging spot availability and real-time traffic congestion in the parking lot, the system can allocate the vehicles to optimal parking spots and assign driving trajectories to follow. With the control of chargers, the charging time and power of each vehicle can be optimized jointly with the parking management.

[0013] Embodiments of the present disclosure may leverage V2X communication. With vehicle-to-cloud (V2C) communication, the information can be gathered by the vehicles, such as the traffic condition and charger status, and sent to a central coordinator in the cloud server. After the parking allocation, trajectory generation, and charging plan are optimized, the cloud server can transmit the optimal results to the vehicles for compliance therewith.

[0014] Embodiments of the present disclosure may leverage Automated vehicles. If vehicles are deployed with self-driving controllers, vehicles can be automated to self-drive the assigned trajectories in the most energy-efficient manner. It is also possible to relocate the vehicles after charging completion so that the charger becomes available to other EVs. This may require a wireless charging mechanism or an automated plug-in and plug-out mechanism.

[0015] FIG. 1 illustrates an example of a control process 100 for parking and charging management in accordance with certain implementations of the disclosed technology. In the example, the control process 100 includes a cloud server 102, vehicles 104, a charging facility 106, and human drivers or automatic controllers 108.

[0016] FIG. 2 illustrates an example of system data flow 200 in accordance with certain implementations of the disclosed technology. In the example, the data flow 200 includes inputs 202 such as detectors/sensors, vehicles/drivers, and grid signal. The inputs 202 may include direct measurement or indirect measurement. In certain embodiments, the detectors may be physical sensors on the infrastructure side; alternatively or in addition thereto, the detectors may be inferred by using hardware on the vehicles. For example, a vehicle entrance and/or exit may be inferred by high-precision GPS (e.g., rather than having a counter at the entrance). Also, an empty or occupied spot may be inferred by sensors on other cars (e.g., radar, lidar or ultrasound) which can detect an empty spot and communicate with the cloud system.

[0017] In the example, the data flow 200 further includes process 204 that includes operations from the cloud server 102. The data flow 200 further includes outputs 204 to vehicles/drivers and chargers.

[0018] In the example, sensors in the parking lot can collect the data on current traffic and parking/charging spot availability. The price of electricity can also be monitored in real-time.

[0019] When one of the vehicles 104 enters the parking lot, it can report to the system the necessary parameters, such as the vehicle type (e.g., ICE, EV, or Plug-in Hybrid Electric Vehicle (PHEV)), the expected departure time, and the user preference. If PH/EV, the vehicle can also report the current state of charge (SOC), desired SOC by departure, the battery capacity, and the rated charging power.

[0020] Based on observing and predicting the parking and charging demand, the cloud server 102 can solve an optimization problem and notify the vehicle(s) 104 via a mobile phone app or on the dashboard of the vehicle, for example. All vehicles 104 can be informed of their assigned time and location of the parking spot, as well as the path to reach the spot. PH/EVs can be informed on their planned charging schedule.

[0021] PH/EVs can be either assigned immediately to spots with chargers (e.g., vehicles A, B, and D at the left bottom of the figure) or tentatively assigned into parking-only spots on a waitlist (e.g., vehicle C in the figure at the left bottom of the figure). For the latter case, the system 100 can coordinate the interchange of vehicles on a charger. When one of the vehicles 104 finishes charging (e.g., vehicle B at the right bottom of the figure), it can be notified to leave the charging spot as soon as possible. When it leaves, the vehicle on a waitlist (e.g., vehicle C on the right bottom of the figure) can be notified to move in and use the now open charger.

[0022] If any of the vehicles 104 is autonomous with level 4, it can self-drive the path and velocity trajectory, which can be solved and provided by the system, and maneuver to the assigned spot. If a single vehicle in the lot is autonomous, the path can be optimized to minimize its own energy consumption based on the current traffic situation. If multiple vehicles are autonomous, their paths can be jointly optimized to minimize the aggregate energy consumption.

[0023] If a PH/EV is autonomous and needs to leave a charging spot for another PH/EV to use, it can be controlled to self-drive out of the charging spot and park at an available parking-only spot. If the incoming PH/EV is autonomous and has occupied a parking-only spot before, it can also be controlled to self-drive out of the parking spot and into the now-open charging spot.

[0024] In the example, multiple sources can send input data to the cloud server 102; the sensors in the parking lot can detect the current traffic condition and parking/charging spot availability, the vehicles 104 can transmit the information on the vehicle status and the details of parking/charging demands, and the energy grid can report the electricity price, for example.

[0025] Further in the example, the cloud server 102 can process the input data and execute the SPCM to solve for the optimal spot allocation, driving trajectory, and the charging plan, for example.

[0026] Also in the example, the cloud server 102 can send the solution to the vehicles 104 and chargers to follow. The vehicles 104 can reach the parking/charging spots per assigned schedule by human drivers or automated controllers 108 and the chargers can supply the scheduled power to the vehicles, for example.

[0027] It will be appreciated that, in certain embodiments, the disclosed SPCM may work for a set of individually-operated vehicles as well as for vehicles belonging to a fleet operator. In the latter case, a single “fleet-level” cost function is optimized (e.g., the SPCM instead of truing to make all drivers/autonomous vehicles happy, needs simply to optimize for the fleet operator).

Examples

[0028] In a first example, a system can include at least one detector configured to provide input information, at least one electric vehicle, at least one electric vehicle charger, and a cloud server configured to execute a Simultaneous Parking and Charging Management (SPCM) method based at least in part on the input information and communicate with the at least one electric vehicle to assign a time for a certain one of the at least one electric vehicle charger based at least in part on a result of the executed SPCM method.

[0029] In a second example, a method can include using at least one sensor to collect information pertaining to current traffic conditions and parking/charging spot availability for a parking area, each of the at least one electric vehicle reporting a plurality of parameters upon entering the parking area, using a cloud server, solving an optimization problem based at least in part on the collected information and the plurality of parameters, and communicating to each of the at least one electric vehicle an assigned time and a location of a certain parking spot based on a result of the solved optimization problem.

[0030] The second example can further include using at least one sensor to monitor the price of electricity in real-time.

[0031] The plurality of parameters in the second example can include at least one selected from the group consisting of: electric vehicle type, expected departure time, and user preference.

[0032] The second example can further include communicating to at least one of the at least one electric vehicle a path for the at least one vehicle to use to reach the certain parking spot. Such example can further include optimizing the path the minimize energy consumption by the at least one electric vehicle.

[0033] The at least one electric vehicle of the second example can include a Plug-in Hybrid Electric Vehicle (PHEV) and the PHEV can be assigned immediately to a parking spot with a vehicle charger. Alternatively, the at least one electric vehicle of the second example can include a Plug-in Hybrid Electric Vehicle (PHEV) and the PHEV can be tentatively assigned to at least one parking-only spot on a waitlist. Such examples can further include communicating to one of the at least one electric vehicle an instruction to leave the certain parking spot responsive to completion of a charge cycle. Such examples can further include communicating to the PHEV an instruction to proceed to the certain parking spot.

[0034] The at least one electric vehicle of the second example can include an electric vehicle (EV) and the EV can be assigned immediately to a parking spot with a vehicle charger. Alternatively, the EV can be tentatively assigned to at least one parking-only spot on a waitlist. Such examples can further include communicating to one of the at least one electric vehicle an instruction to leave the certain parking spot responsive to completion of a charge cycle and/or communicating to the EV an instruction to proceed to the certain parking spot.

[0035] The at least one electric vehicle of the second example can include a Plug-in Hybrid Electric Vehicle (PHEV) and an electric vehicle (EV) and the PHEV and EV can each be assigned immediately to a parking spot with a vehicle charger. Alternatively, the PHEV and EV are each tentatively assigned to at least one parking-only spot on a waitlist. Such examples can further include communicating to one of the at least one electric vehicle an instruction to leave the certain parking spot responsive to completion of a charge cycle. Such examples can further include communicating to the PHEV and EV an instruction to proceed to the certain parking spot.

[0036] The plurality of parameters in the second example can include at least one selected from the group consisting of: electric vehicle type, expected departure time, and desired SoC at the end of the charge. In such example, at least one of the plurality of parameters can be provided by the user or another software based on a future driving schedule.

[0037] The second example can further include sending to the grid, electricity retailer, utility, or facility operator the current and predicted energy profile for charging the vehicles in the lot. Such example can further include the grid, electricity retailer, utility, or facility operator software accepting the request or deciding to reach a consensus on a different profile with the SPCM. Such example can further include the SPCM re-computing the charging strategies for each vehicle.

[0038] Aspects of the disclosure may operate on particularly created hardware, firmware, digital signal processors, or on a specially programmed computer including a processor operating according to programmed instructions. The terms controller or processor as used herein are intended to include microprocessors, microcomputers, Application Specific Integrated Circuits (ASICs), and dedicated hardware controllers.

[0039] One or more aspects of the disclosure may be embodied in computer-usable data and computer-executable instructions, such as in one or more program modules, executed by one or more computers (including monitoring modules), or other devices. Generally, program modules include routines, programs, objects, components, data structures, and so on, that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer executable instructions may be stored on a computer readable storage medium such as a hard disk, optical disk, removable storage media, solid state memory, Random Access Memory (RAM), etc. As will be appreciated by one of skill in the art, the functionality of the program modules may be combined or distributed as desired in various aspects. In addition, the functionality may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, FPGAs, and the like.

[0040] Particular data structures may be used to more effectively implement one or more aspects of the disclosure, and such data structures are contemplated within the scope of computer executable instructions and computer-usable data described herein.

[0041] The disclosed aspects may be implemented, in some cases, in hardware, firmware, software, or any combination thereof. The disclosed aspects may also be implemented as instructions carried by or stored on one or more or computer-readable storage media, which may be read and executed by one or more processors. Such instructions may be referred to as a computer program product. Computer-readable media, as discussed herein, means any media that can be accessed by a computing device. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media.

[0042] Computer storage media means any medium that can be used to store computer-readable information. By way of example, and not limitation, computer storage media may include RAM, ROM, Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory or other memory technology, Compact Disc Read Only Memory (CD-ROM), Digital Video Disc (DVD), or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, and any other volatile or nonvolatile, removable or non-removable media implemented in any technology. Computer storage media excludes signals per se and transitory forms of signal transmission.

[0043] Communication media means any media that can be used for the communication of computer-readable information. By way of example, and not limitation, communication media may include coaxial cables, fiber-optic cables, air, or any other media suitable for the communication of electrical, optical, Radio Frequency (RF), infrared, acoustic or other types of signals.

[0044] As used herein, an element or step recited in the singular and proceeded with the word “a” or “an” should be understood as not excluding plural of said elements or steps, unless such exclusion is explicitly stated. Furthermore, references to “one embodiment” of the present invention are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. Moreover, unless explicitly stated to the contrary, embodiments “comprising,” “including,” or “having” an element or a plurality of elements having a particular property may include additional such elements not having that property. The terms “including” and “in which” are used as the plain-language equivalents of the respective terms “comprising” and “wherein.” Moreover, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements or a particular positional order on their objects.

[0045] This written description uses examples to disclose the invention, including the best mode, and also to enable a person of ordinary skill in the relevant art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those of ordinary skill in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.