... | ... | @@ -5,6 +5,9 @@ The figure shows the SEADA choreography. The application is triggered when drive |
|
|
Considering the given route, **ND** continuously updates traffic information with the purposes to give driving advisory to the drivers for eco-friendly driving. This is done through the Get Eco Speed Route Information task where **ND** interacts with **SEADA-SEATSA** for eco-speed information. In order to collect traffic information, **SEADA-SEATSA** interacts with **DTS- AREA-TRAFFIC** through the Get Traffic Route Information task and gets cached information directly. **SEADA-SEATSA** then evaluates the eco factors and interacts with **ND** and presents eco-speed information through the Set Eco Speed Route Information task.
|
|
|
![EcoFriendlyRoutesInformation](/uploads/b75c616b475107ca912d015487698df1/EcoFriendlyRoutesInformation.png)
|
|
|
The figure shows the Eco Friendly Routes Information sub-choreography. It consists of a set of tasks involving interactions between different provider services for collecting traffic information and calculating eco-related information. Firstly, **SEADA-SEARP** interacts with **SEADA-SEATSA** through the Get Eco Friendly Routes Information task to request eco information for the available routes. Afterwards, **SEADA-SEATSA** interacts with **DTS-AREA-TRAFFIC** through the Get Traffic Route Information task to get information for a given route. Notice that this task is a loop task where it collects information for each of the available route. Thanks to the newly designed traffic information collection choreography to be discussed in the next section, the loop task can be executed efficiently. After all information is available, **SEADA-SEATSA** interacts with **SEADA-SEARP** through the Set Eco Friendly Routes Information task to return routes with eco information.
|
|
|
|
|
|
![trafficAreaInformationCollection](/uploads/af271ea53811182101486a2f222a1a76/trafficAreaInformationCollection.png)
|
|
|
As shown in the figure, Traffic information collection choreography is a long- running choreography. It is designed to continuously collect traffic related information and using it for fast response upon requesting. Leveraging the city area related information managed by Traffic Information Collector, **SEADA-TRAFFIC** firstly requests segment information for a given area by interacting with **DTS-AREA-TRAFFIC** through the Get Area Segments task. This starts the timely executed flow for continuous traffic information collection. A Traffic Segment Information Collection sub-choreography is executed to collect all types of traffic information and make it available to **SEADA-TRAFFIC**. Afterwards, **SEADA-TRAFFIC** feeds the information through the Set Traffic Area task to **DTS-AREA-TRAFFIC** for fast response such as in the previous choreography.
|
|
|
![trafficSegmentInformationCollection](/uploads/b137eb57f6ad0e6fb7e984460d4aad55/trafficSegmentInformationCollection.png)
|
|
|
The figure illustrates the Traffic Segment Information Collection sub-choreography. After **SEADA-TRAFFIC** receives all segment information, it interacts with **DTS-SEGMENT-TRAFFIC** for traffic information for each of the given segment through the Get Segment Traffic Information task. Afterwards, for a given road segment, **DTS-SEGMENT-TRAFFIC** requests related traffic information concurrently to **DTS-ACCIDENT** through the Segment Accident Information task; to **DTS-BRIGE** through the Bridge Status Information task; to **DTS-CONGESTION** through the Segment Congestion Information task; and to the **DTS-WEATHER** through the Segment Weather Information task. Once all information is available, **DTS-SEGMENT-TRAFFIC** interacts with **SEADA-TRAFFIC** for feeding the traffic information through the Set Segment Traffic Information task.
|
|
|
|
|
|
|