A Back-end System for an Autonomous Parking and Charging System for Electric Vehicles

Transcription

1 A Back-end System for an Autonomous Parking and Charging System for Electric Vehicles Julian Timpner, Lars Wolf IEVC 2012

2 V-Charge Project Goals Motivation Software Architecture Conclusion A system combining autonomous valet parking with e-mobility Increasing customer acceptance of electric vehicles By compensating for longer charging cycles Challenges Efficiently using scarce charging resources Multiple communication channels (V2I, Web, mobile) Autonomous driving and parking (not in this talk) IEVC 2012 Julian Timpner Page 2

3 V-Charge Partners

4 Motivation Software Architecture Conclusion Motivation Scenario: EV driver at airport Roam for a free spot Use shuttle services Transport luggage What about charging? Disadvantages Cumbersome Only few charging stations Makes it even harder to find parking IEVC 2012 Julian Timpner Page 4

5 Solution: V-Charge Motivation Software Architecture Conclusion Autonomous Parking and Charging Charging Station Charging Station Drop-off Zone Drop-off and Pick-up Zone (a) Drop-off (b) Reparking IEVC 2012 Julian Timpner Page 5

6 Motivation Software Architecture Conclusion Required Back-end Functionality Communication with vehicles and mobile user devices Management of the overall system Scheduling concepts and assignment of free parking spots and charging stations to connected vehicles Distribution of mission information to connected vehicles IEVC 2012 Julian Timpner Page 6

7 Motivation Software Architecture Conclusion Supporting Back-end Functionality Storage and online distribution of a parking lot map to connected vehicles Sensor data aggregation (e.g., parking spot occupation) and fusion with central map System monitoring, with status information being available via a user interface Security and trust concepts IEVC 2012 Julian Timpner Page 7

8 Outline Motivation Software Architecture Conclusion Motivation Software Architecture Conclusion IEVC 2012 Julian Timpner Page 8

9 Motivation Software Architecture Conclusion Use Cases V-Charge System reserve parking spot drop off vehicle pick up vehicle User view status information «extends» manage parking situation Administration assign charging station «extends» «extends» «extends» assign parking spot manage overall vehicle movement update vehicle's mission goal IEVC 2012 Julian Timpner Page 9

10 - Server activates car w/next heartbeat response. - Server updates map & goal. - Vehicle pulls out. - Vehicle notifies server when it has left the parking spot. - Server updates parking situation. Use Case: Pick-up - Vehicle follows global path to pick-up zone. - Vehicle has reached final destination, and notifies server. - User can get into the vehicle and takes over control. - Server deactivates vehicle. Motivation Software Architecture Conclusion :User :HMI :V-Server :Vehicle heartbeat pick-up request pick-up request heartbeat activate send map & mission goal confirmation confirmation confirmation plan path path start mission send status update schedule wait for takeover takeover takeover check out IEVC 2012 Julian Timpner Page 10

11 Domain Model Motivation Software Architecture Conclusion Groups -groupname * Requirement -arrival -departure -energy 1 1 Customer - -firstname -lastname -password -owner 1 Vehicle -vehicles -licenceplate -battery -position -schedules * -status 1 * Schedule -arrival -departure -status -delay 1 ParkingLot -name -capacity 1 1..* * 1 Site -name -position -status -type -destination 1 * 1 * Reservation -starttime -endtime IEVC 2012 Julian Timpner Page 11

12 Component Specification Motivation Software Architecture Conclusion Visual Paradigm for UML Community Edition [not for commercial use] Management <<component>> MapManager Map Update Parking Situation <<component>> VehicleManager Vehicle Command <<component>> LotManager Vehicle Status Parking Requirements <<component>> CustomerManager Registration Vehicle Check-in Vehicle Handover Vehicle Pick-up Vehicle Status IEVC 2012 Julian Timpner Page 12

13 Software Technology and Deployment Motivation Software Architecture Conclusion V-Charge Server <<https>> EJB Container WebContainer CustomerManager DBServer V-Charge Website * -End6 -End5 RESTful Web Services LotManager VehicleManager MapManager SQL Server Map Storage <<https>> IEVC 2012 Julian Timpner Page 13

14 Vehicle Interaction Concept Motivation Software Architecture Conclusion [User checks in vehicle] CHECKED_IN [User activates communications system] WAITING_FOR_HANDOVER [User initiates handover] WAITING_FOR_COMMANDS [Vehicle receives mission goal] EN_ROUTE [Vehicle ends mission] WAITING_FOR_TAKEOVER [User gets into car] [User summons car] PARKED DEACTIVATED IEVC 2012 Julian Timpner Page 14

15 Outline Motivation Software Architecture Conclusion Motivation Software Architecture Conclusion IEVC 2012 Julian Timpner Page 15

16 Motivation Software Architecture Conclusion On-going Work Concepts for efficient charging station management (scheduling) Evaluating suitability of different scheduling strategies Real test cases with actual vehicles (April 2012) IEVC 2012 Julian Timpner Page 16

17 Motivation Software Architecture Conclusion Summary Back-end architecture for autonomous valet parking automatic recharging capabilities Standards-based, e.g., Java EE, RESTful Web services, SSL Portable Scalable Secure Supporting multiple communications channels (V2I, Web, mobile) IEVC 2012 Julian Timpner Page 17

18 Motivation Software Architecture Conclusion Summary Back-end architecture for autonomous valet parking automatic recharging capabilities Standards-based, e.g., Java EE, RESTful Web services, SSL Portable Scalable Secure Supporting multiple communications channels (V2I, Web, mobile) Thank you! IEVC 2012 Julian Timpner Page 17

19 Section 4 Appendix

20 Appendix Communications Support of several data channels Wi-Fi (802.11a) as standard 3G, C2X to be considered Mobile users will use a smartphone to interact with the system Server will distribute maps and updates via Wi-Fi to the vehicles Administration via Web interface IEVC 2012 Julian Timpner Page 19

21 Security Concept Appendix 1. CSR CA 2. Cuser 3. Mutual Authentication User 4. Cv1 V-Charge Server 6. Mutual Authentication 5. Cvcharge, Cv1 Vehicle V1 7. Mutual Authentication Vehicle V2 IEVC 2012 Julian Timpner Page 20

22 Appendix Charging Station Scheduling SchedulingStrategy +controladmission() +schedule() +removereservation() +retractreservation() GuaranteeBasedStrategy #cscache EDFStrategy ScanningOnlyStrategy ShiftingPerStationStrategy GreedyDistributionStrategy FlexibleGreedyDistributionStrategy IEVC 2012 Julian Timpner Page 21

23 Simulation Setup Appendix 08:15 Previous Check-in 09:00 Check-in 10:15 Handover (real) 10:00 Handover (planned) 11:35 Pick-up (planned) 11:20 Pick-up (real) 09:00 10:00 11:00 08:00 12:00 08:15-09:00 09:00-10:00 10:00-11:35 Interarrival time Release time (planned) Parking time (planned) 09:00-10:15 Release time (real) 10:15-11:20 Parking time (real) 08:15 Previous Check-in 09:00 Check-in 10:50 Handover (real) 10:30 Handover (planned) 13:00 Pick-up (planned) 12:45 Pick-up (real) IEVC 2012 Julian Timpner Page 22 08:15-09:00 09:00 09:00-10:30-10:50 Interarrival time Release Release time (planned) time (real)

24 Simulation Speed-up Appendix 08:00 08:01:58 08:02 08:03:58 08:04 08:05:16 08:05:18 T 0 T 1 Server event T 2 Server event T 3 Simulator event 08:01 08:02 08:03 08:04 08:05 08:00 08:06 08:01:58 08:02 T 1 Server event 08:01 08:01:59 08:02:01 08:02 Lock Unlock IEVC 2012 Julian Timpner Page 23

25 Metrics Appendix Facility use, such as Overall peak-period utilization (e.g. daily spaces occupied) Charging station utilization Number of charging station switches per vehicle Customer satisfaction, such as Percent satisfied customer parking requirements Energy demand vs. provided energy IEVC 2012 Julian Timpner Page 24