... | ... | @@ -10,4 +10,5 @@ As shown in the figure, Traffic information collection choreography is a long- r |
|
|
![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.
|
|
|
|
|
|
**Experiment** The experiment conducted for the UTC use case employed the following experimental units.
|
|
|
|