Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

Urban Traffic Coordination work package 4 by Cristofer Englund, Viktoria Swedish ICT
First Year Project Review in Brussels
11 February 2016

Published in: Software
  • Be the first to comment


  1. 1. WP 4 Urban traffic coordination – Situation and eco-aware driving assist Cristofer Englund Viktoria Swedish ICT
  2. 2. WP4 Overview Duration: M1 – M36 (all tasks) Effort: 53 PMs Task 4.1: Urban Traffic Coordination Scenario Investigation and Requirements Analysis •  Viktoria, Cefriel, Thales, Tirasa, UDA Task 4.2: Urban Traffic Coordination Services Implementation and Choreography Development •  Viktoria, Cefriel, Inria, Thales, Tirasa, UDA Task 4.3: Urban Traffic Coordination Choreography Deployment and Assessment •  Viktoria, Cefriel, Inria, Thales, Tirasa, UDA Task 4.4: Urban Traffic Coordination Business Model •  Viktoria 211 Feb 2016
  3. 3. WP4 Deliverables ü  D4.1: Urban Traffic Coordination Scenario Definition and Requirements (Viktoria) – M6 •  D4.2: Urban Traffic Coordination Initial application prototyping (Viktoria) – M24 •  D4.3: Urban Traffic Coordination Deployment and Demonstration (Viktoria) – M36 •  D4.4: Urban Traffic Coordination Business models (Viktoria) – M36 311 Feb 2016
  4. 4. 11 Feb 2016 4 Transport challenges l  Growing mobility and congestion l  Increasing emission from transport sector l  Traffic safety l  Urbanization l  High expectations on information availability, timing, accuracy Source: Source: WHO Over 1.2 million people die each year on the world’s roads, and between 20 and 50 million suffer non-fatal injuries + 40% CO2 emissions since 1992 from transport, while decreasing from other areas Sweden aim for fossil free transport system in 2030 in Sweden. Today 95%.
  5. 5. 5 Opportunities •  Cooperative intelligent transport systems (C-ITS) •  Connected vehicles •  Ubiquitous connectivity – Networked society •  Cloud computing •  Open data 11 Feb 2016
  6. 6. 6 Services and Things in the FI domain •  Multiple services •  Real time traffic information •  Map information •  Routing/Navigation information •  Road infrastructure information •  … •  Multiple domains •  Public authorities •  Commercial data providers •  Open data •  Crowd data •  … 11 Feb 2016
  7. 7. Challenges with services and things 11 Feb 2016 Middleware protocolsSOAP REST CoAP MQTT MQTT-S XMPP Issues Security: We want to have secure communication between services Heterogeneity: No single choice on middleware protocols, depending on stakeholders Interoperability: Different protocols need to be able to communicate with each other, critical in IoT Strong competition between protocols Solutions Security filters Binding components Adaptors 7
  8. 8. Scenario description – Situation and eco-aware driving assist (SEADA) Situa&on)and) Eco-Aware) Travel)Speed) Advisory)SEATSA) ! CWARP) Conges&on) Warning)&) Route)re- Planning) Accident) Warning)&) Route)re- Planning) AWARP) Extreme)Road) Situa&on) Warning)&) Route)re- Planning) ! ERWARP) Traffic-based)events) Green)Light) Op&mized) Speed)) Advisory))GLOSA) BOWARP) Bridge)Open) Warning)&) Route)re- Planning) ! Loca&on-based)events) Origin) Upon)traffic)events) Approaching)loca&ons) Situa&on)and) Eco-Aware) Route) Planning)SEARP) Dest) New)route)) needed?) Y) N) To develop highly responsive situation and eco-aware information to improve driving experiences and reduce CO2 emission. 11 Feb 2016 8
  9. 9. Scenario description – Situation and eco-aware driving assist (SEADA) l  WP 4: Use Case Urban Traffic Coordination (UTC) -  Design with respect to security and requirements -  Situation-aware and eco-friendly driving guidance -  improved driving comfort, -  traffic efficiency, -  emission reduction -  Define eco-driving -  Develop situation- and eco-aware driving application -  Business models for eco-driving -  How can eco-driving be integrated C-ITS 11 Feb 2016 9
  10. 10. ORCHESTRATION vs CHOREOGRAPHY •  Centralized - Orchestration •  Services interact only with the central service •  Difficult to coordinate multiple domain services •  Less flexible •  Less scalable •  Distributed- Choreography •  Peer-to-peer service interaction •  Straighforward to coordinate multiple domain services •  Flexible to change coordination logic •  Scalable service coordination •  Facing future C-ITS system Central service ! applica5on boundary 11 Feb 2016 10
  11. 11. 11 CHOReVOLUTION features •  Easy choreography specification based on BPMN2 •  Reusability of existing services and things •  Automatic choreography synthesis and enactment •  Interoperability between different service protocols •  Deals with services and things •  Cloud deployment for straightforward application execution An all-in-one platform for service-choreography-based application development is very promising in future connected and automated transport system. 11 Feb 2016
  12. 12. Traffic related services •  Eco-driving -  Mathematical model for evaluating eco-friendliness of routes based on geo-information and real-time traffic information •  BOWARP – Bridge Opening Warning & Route re-planning -  Building web-service based on API from City of Gothenburg •  GLOSA – Green Light Optimal Speed -  Mathematical model of the traffic light status -  Building web-service based on Public Transport API of the bus status -  Time-To-Red modelling 11 Feb 2016 12
  13. 13. Estimate Time-To-Red – based on bus position Regnbågsgatan Stop t1 Pumpgatan Stop t2 Frihamnen Stop t3 11 Feb 2016 Traffic light Time-To-Red = f(t1,t2,t3) 13
  14. 14. 14 Route planning: Choreography diagram Figure 4.3: WP4 Choreography Specification Figure 4.4: WP4 Traffic Estimation Sub-Choreography Specification BS-MAP represents a service that supports ND while accessing digital maps. Map information can be both local and on-demand through Internet access. BS-MAP is used for accessing the Figure 4.3: WP4 Choreography Specification Figure 4.4: WP4 Traffic Estimation Sub-Choreography Specification11 Feb 2016
  15. 15. Route planning: Alternative routes 11 Feb 2016 15
  16. 16. Route planning: Traffic information 11 Feb 2016 16
  17. 17. Route planning: Traffic-based events 11 Feb 2016 17
  18. 18. Conclusion and next step •  WP4 main achievments in the period: -  D4.1 delivered on time -  Created choreographies for the use-case -  Re-used a number of services for route generation and traffic- related information •  Continue experimenting with the Chorevolution studio -  Evaluate and give feedback, for continous development, of the Chorevolution studio -  Incremental development to add funcitonallity of the use-case 11 Feb 2016 18
  19. 19. THANK YOU