Subject: [its] comments on the draft on ITS scenarios and requirements

From: <[email-masked]>
Date: Sun, 29 Jul 2012 23:34:08 +0000

Hi Alex,

I think that draft-petrescu-its-scenarios-reqs-01.txt  is introducing some vehicular networking scenarios, but for the sake of completeness it will be probably beneficiary to mention all possible types of scenarios and use cases. 

The vehicular networking applications can be classified in Traffic (or Active) road safety, traffic efficiency & management and Infotainment applications.  Many documents are describing these applications, see references at the bottom of this email!

Traffic (or Active) road safety applications are those that are primarily employed to decrease the probability of traffic accidents and the loss of life of the occupants of vehicles.  The active road safety applications can be grouped in Driving assistance-Co-operative awareness and Driving assistance Road Hazard Warning applications.

Traffic efficiency and management applications: focus on improving the vehicle traffic flow, traffic coordination and traffic assistance and provide updated local information, maps and in general, messages of relevance bounded in space and/or time. Speed management and Co-operative navigation are two typical groups of this type of applications.

Infotainment applications: All other type of applications are Infotainment applications. These applications can be divided in two main classes: Co-operative local services and Global Internet services
According to several standardization bodies, like ETSI ITS and CALM, only the Infotainment applications and some of the Traffic efficiency applications make use of the IP based protocol stack.

Therefore, below, I will briefly describe the main Traffic efficiency and Infotainment applications mentioned in the ETSI ITS specification (ETSI TR 102 638), see the reference at the bottom of this email, that could make use of the IP based protocol stack. 

In addition to that I would like to mention that a division of the requirements might be useful. This division could be, see also e.g., ETSI TR 102 638:

=> Radio communication capabilities, such as (1) single hop radio communication range, (2) used radio frequency channels, (3) available bandwidth and bit transfer rate, (4) robustness of the radio communication channel, (5) level of compensation for radio signal propagation difficulties by e.g., using road side units.

=> Network communication capabilities, such as (1) mode of dissemination: unicasting, broadcasting, multicasting, geocasting (broadcasting capability that is valid only within a specified area), (2) data aggregation, (3) congestion control, (4) message priority, (5) management means for channel and connectivity realization, (6) support of IPv6 or IPv4 addressing, (7) mobility management associated with changes of point of attachment to the Internet.

=> Vehicle absolute positioning capabilities, such as (1) Global Navigation Satellite System (GNSS), e.g., Global Positioning System (GPS), (2) Combined positioning capabilities, e.g., combined GNSS with information provided by a local geographical map.

=> Other vehicle capabilities, such as (1) vehicle interfaces for sensor and radar, (2) vehicle navigation capabilities. Vehicle communication security capabilities, such as (1) respect of privacy and anonymity, (2) integrity and confidentiality, (3) resistance to external security attacks, (4) authenticity of received data, (5) data and system integrity.

Below, I am briefly describing the main Traffic efficiency and Infotainment applications mentioned in the ETSI ITS specification (ETSI TR 102 638), see the reference at the bottom of this email, that could make use of the IP based protocol stack. 

Traffic efficiency & management
--------------------------------------------
Traffic efficiency & management applications are focusing on improving the vehicle traffic flow, traffic coordination and traffic assistance. Furthermore, traffic efficiency & management applications are focusing on providing updated local information, maps and in general messages of relevance limited in space and/or time. The traffic efficiency & management applications can be grouped in Speed management and Co-operative navigation.

a) Speed management
This type of applications is used to assist the driver to manage the speed of his/her vehicle in order to make the driving smoother and avoid unnecessary stopping. This application type can be applied in the following use cases:

=> Regulatory/contextual speed limit notification: in this use case, a road side units broadcasts at a given frequency the current traffic speed limits, e.g., regulatory and contextual.

 => Green light optimal speed advisory: in this use case a road side unit broadcasts information regarding the traffic lights timing data associated to the traffic light state. A vehicle that receives this information it can use the traffic lights data and its own current speed to estimate an optimal speed advise such that the vehicle could reach the intersection under green light.
 
b) Co-operative navigation
This type of applications is used to increase the traffic efficiency by managing the navigation of vehicles through the cooperation between vehicles and through the cooperation between vehicles and road side units. This application type can be applied in the following use cases:

=> Traffic information and recommended itinerary: in this use case, a road side unit broadcasts periodically to inform approaching vehicles about traffic abnormal conditions and provides advices to avoid a traffic jam. These advices may include map and route information.
 
=> Enhanced route guidance and navigation: in this use case, a road side unit can communicate with vehicles that would want to use Internet connectivity in order to download optimized itinerary according to personalized requirements. This interaction may also include route guidance and navigation information.
 
=> Limited access warning and detour notification: in this use case, a road side unit informs approaching vehicles about some road limited access. The approaching vehicles may be queried about security access control related information. The vehicles that are not being authorized to access the restricted area are being guided to follow another way. 
 
=> In-vehicle signing: in this use case, road side units are broadcasting information associated with traffic signs to the drivers of the approaching vehicles.
 
=> Electronic toll collect: in this use case, a road side unit queries approaching vehicles about security access control related information. Vehicles that have the necessary access rights are allowed to access the road network part, after electronic toll collect. 
 
=> Co-operative adaptive cruise control (it is recommended that this use case should not use the Internet based protocol stack): in this use case, vehicles are cooperating with each other and, if possible with road side units, to obtain the necessary lead vehicle dynamics information and general traffic ahead, such as acceleration and head distance, in order to enhance the performance of the current Adaptive Cruise Control (ACC) systems.
 
=> Co-operative vehicle-highway automatic system (platoon) (it is recommended that this use case should not use the Internet based protocol stack): in this use case, vehicles are cooperating with each other and, if possible with road side units, to obtain the necessary lead vehicle dynamics information and general traffic ahead in order to enhance the C-ACC (Co-operative ACC) features, such that a series of vehicles could drive and operate safely and smoothly as a platoon on a highway or a specific lane.
 
Infotainment Applications
-----------------------------------
a) Co-operative local services
This type of applications is focusing on infotainment that can be obtained from locally based services. This application type can be applied in the following use cases:

=> Point of interest notification: in this use case, a road side unit informs on a periodical way the approaching vehicles about the presence of locally based services, such as restaurants, and points of interest.
 
=> ITS (Intelligent Transport System) local electronic commerce: in this use case, a road side unit informs vehicles that they might have the capability to process a local payment for service (e.g., parking) reservation or some other local purchasing.
 
=> Media downloading: in this use case, a road side unit can provide multimedia to approaching vehicles using either the internet network or locally. The downloading can be conditioned by a commercial transaction, when digital rights are required for the downloading action.
 
b) Global Internet services
This type of applications is focusing on infotainment that can be obtained from global internet services. This application type is grouped in Communities services and ITS station life cycle:

b.1) Communities services
This global internet service application group is including insurance and financial services, fleet management and parking zone management. This application type can be applied in the following use cases:

=> Insurance and financial services: in this use case, a road side unit provides the capability to approaching vehicles the pay as you drive services, where an on-demand and real time interaction can be supported using financial and insurance coverage service provider. This can be enabled using, in addition to the vehicle to vehicle network, also the Internet network.
 
=> Fleet management: in this use case, a road side unit can use Internet access and provide and collect fleet management data from approaching vehicles, through the exchanges between vehicles and road side units. 
 
b.2) ITS station life cycle
This type of applications is focusing on infotainment, where vehicles can download software and data provisioning and updates. This application type can be applied in the following use case:

=> Vehicle software/data provisioning and update: in this use case, a road side unit is able to insure the software and data exchange between vehicles and a relevant software provisioning center. The exchanged information can be used for provisioning or for updating installed software and/or data.
 
Below a list with documents that provide more detail on vehicular networking scenarios and use cases and possible issues that need to be solved!

ETSI TR 102 638, “Intelligent Transport System (ITS); Vehicular Communications; Basic Set of Applications; Definition, ETSI specification TR 102 638, v.1.1.1, June 2009.

Car to Car Communication Consortium, “Car to Car Communication Consortium Manifesto: Overview of the C2C-CC System”, C2C-CC, version 1.1, 2007.
 
Intellidrive project, “Vehicle safety applications”, ITS Joint program Office, USDOT, 2008, pp. 1-15.

IST Safespot project, “Use cases, functional specifications and safety margin applications for the SAFESPOT Project”, Safespot IST-4-026963-IP deliverable D8.4.4, 2008, pp 1 – 54.

IST PreDrive C2X project, “Detailed description of selected use cases and corresponding technical requirements”, PreDrive C2X deliverable 4.1.

IST CVIS project, “Use cases and system requirements”, CVIS IST-4-027293-IP deliverable 2.2, v. 1.0, 2006, pp 1- 256.

R. Bishop, “A Survey of Intelligent Vehicle Applications Worldwide”, in Proc. of IEEE Intelligent Vehicles Symposium, pp. 25-30, 2000.

A. R. Girard, J. Borges de Sousa, J. K. Hedrick, “An Overview of Emerging Results in Networked Multi-Vehicle Systems”, in Proc. of 40th IEEE Conference on Decision and Control, USA, pp. 1485-1490, 2001.

S. Tsugawa, “Inter-Vehicle Communications and their Applications to Intelligent Vehicles: an Overview”, in Proc. of IEEE Intelligent Vehicles Symposium, pp. 564-569, 2002. 

J. Luo, J.-P. Hubaux, “A survey of research in inter-vehicle communications, in Embedded Security in Cars”, in Journal of Computer Science, Embedded Security in Cars Securing Current and Future Automotive IT Applications, Springer-Verlag, pp. 111-122, 2006.

J.Chennikara-Varghese, W. Chen, O. Altintas and S. Cai, “Survey of Routing Protocols for Inter-Vehicle Communications,” in Proc. of Vehicle-to-Vehicle Communications (V2VCOM) Workshop 2006, in conjunction with MobiQuitous 2006, pp. 1-5, July 2006.

Fan Li, Yu Wang, “Routing in Vehicular Ad Hoc Networks: A Survey”, in IEEE Vehicular Technology Magazine, pp. 12-22, June 2007.

M. L. Sichitiu, M. Kihl, “Inter-Vehicle Communication Systems: A Survey”, in IEEE Communications Surveys & Tutorials, Vol. 10, Issue 2, 2nd Quarter, pp. 88 – 105, 2008.

Y. Toor, P. Mühlethaler, A. Laouiti, A. de la Fortelle, “Vehicle Ad Hoc Networks: Applications and Related Technical Issues”, in IEEE Communications Surveys & Tutorials, Vol. 10, Issue 3, 3rd Quarter 2008.

H. Hartenstein, K. P. Laberteaux, “A Tutorial Survey on Vehicular Ad Hoc Networks”, in IEEE Communications Magazine, Vol. 46, Issue 6, pp. 164-171, June 2008.

T. L. Willke, P. Tientrakool, N. F. Maxemchuk, “A Survey of inter-Vehicle Communication Protocols and Their Applications”, IEEE Communications Surveys & Tutorials, Vol 11, Issue 2, 2nd Quarter, pp. 3-20, 2009. 

P. Papadimitratos, A. de La Fortelle, K. Evenssen, R. Brignolo and S. Cosenza, “Vehicular Communication Systems: Enabling Technologies, Applications, and Future Outlook on Intelligent Transportation,” in IEEE Communications Magazine, Vol. 47, Issue 11, pp. 84-95, November 2009.

G. Karagiannis, O. Altintas, E. Ekici, G.J., Heijenk, B. Jarupan, K. Lin, T. Weil, (2011) “Vehicular networking: A survey and tutorial on requirements, architectures, challenges, standards and solutions”,  IEEE Communications Surveys & Tutorials, 13 (4). pp. 584-616. ISSN 1553-877X, 2011 

Best regards,
Georgios

________________________________________
Van: [email-masked] [[email-masked]] namens Alexandru Petrescu [[email-masked]]
Verzonden: vrijdag 13 juli 2012 19:04
Aan: [email-masked]
Onderwerp: [its] New draft on scenarios and requirements for IP in ITS

Participants to ITS informal effort at IETF,

Per our recent discussions, we submitted a new draft about scenarios and
requirements for IP in ITS:

          draft-petrescu-its-scenarios-reqs-01.txt

I would like to request feedback about the scenarios and requirements
described in this draft.

Thanks in advance,

Alex and on behalf of co-authors.