Scenarios and Requirements for IP in Intelligent Transportation Systems
draft-petrescu-its-scenarios-reqs-00.txt

Abstract

This draft describes scenarios of vehicular communications that are considered pertinent to Intelligent Transportation Systems. In these scenarios, the necessity of using IP networking technologies and protocols is exposed.

Status of this Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on January 08, 2013.

Copyright Notice

Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Terminology
• 3. Scenarios
• 3.1. Vehicle-to-Infrastructure (V2I)
• 3.2. Vehicle-to-Vehicle (V2V)
• 3.3. Vehicle-to-Vehicle-to-Infrastructure (V2V2I)
• 3.4. Infrastructure Support
• 4. Requirements
• 5. Acknowledgements
• 6. IANA Considerations
• 7. Security Considerations
• 8. References
• 8.1. Normative References
• 8.2. Informative References
• Appendix A. ChangeLog
• Authors' Addresses

1. Introduction

The field of vehicular communications is encompassing a large number of wired and wireless technologies. In particular, the breakthrough advancements in wide-area cellular telecommunications, the advent of inexpensive hardware, impressively high bandwidth and low-cost data subscription plans make possible new paradigms which put the vehicle at the center of a communications ecosystem. It can be observed that whereas only in the recent past linking vehicles in a robust manner to a fixed infrastructure represented endeavors available only to top categories, more and more middle category vehicles are announced to take advantage of data connectivity.

Communication protocols used in the fixed and mobile (terminal) Internet can be applied in the scenarios employing vehicles which communicate. A number of particular aspects make vehicular communications different, not least being the that mobility is the norm, rather than the exception. At the same time, several protocols developped at IETF are good candidates to form basis of further development of IP protocols for vehicular communications.

The use of Internet protocols in the vehicular scenarios may prove advantageous from several standpoints:

• immediate availability of a large number of applications with an established customer base.
• scalability: large numbers of inter-communicating vehicles can be accommodated across large distances.
• accessing heterogeneous, mixed and multiple-standard link layer technologies.

The context of vehicular communications considers the use of several classes of Internet protocols for vehicular applications. One particular family of protocols is Mobile IP. Its salient features characterize well several mobility aspects such as reachability at permanent addresses, seamless handovers and group mobility management. Earlier documents at IETF idenfitied a number of scenarios and potential requirements for further work towards improving the Mobile IP protocols for a better adaptation in vehicular environments (see for example the draft titled "Automotive Industry Requirements for NEMO Route Optimization" edited in 2009 [I-D.ietf-mext-nemo-ro-automotive-req].)

A Vehicle-to-Infrastructure scenario (V2I) is a typical setting in which a vehicle uses a long-range wireless interface (cellular, sattelite) to connect to a fixed infrastructure. As a separate matter, scenarios of Vehicle-to-Vehicle (V2V) communications consider direct communications between vehicles, without, or with minimal, assistance from the infrastructure. In areas where wireless coverage is absent, Vehicle-to-Vehicle-to-Infrastructure communications are scenarios where covered vehicles offer access to non covered vehicles, in a multi-hop manner.

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

3. Scenarios

3.1. Vehicle-to-Infrastructure (V2I)

This section describes the communication scenario in which one mobile vehicle connects to a fixed infrastructure.

Topology:

	    
         --------             /--------------+
        | Vehicle|---     ---/Fixed          |------>Internet
         --------  wireless  \Infrastructure |
                     link     \--------------+                
                 (long range)
           

3.2. Vehicle-to-Vehicle (V2V)

Topology:

	    
         --------             --------
        | Vehicle|--       --| Vehicle|
         --------  wireless   --------
                     link     
                   (short range)
	    

3.3. Vehicle-to-Vehicle-to-Infrastructure (V2V2I)

Topology:

	    
  --------             --------       /-------------+
 | Vehicle|--       --| Vehicle|-- --/Fixed         |----->Internet 
  --------  wireless   --------  w   \Infrastructure|
              link              link  \-------------+                
           (short range)     (long range)
             

3.4. Infrastructure Support

4. Requirements

• R0. IP addressing within each vehicle.
• R1. IP addressing on the interface between vehicles.
• Rn.

5. Acknowledgements

The authors would like to acknowledge colleagues who commented and thus helped improving this document.

6. IANA Considerations

No particular requirements to IANA.

7. Security Considerations

Currently no Security considerations.

8. References

8.1. Normative References

8.2. Informative References

Appendix A. ChangeLog

The changes are listed in reverse chronological order, most recent changes appearing at the top of the list.

From -- to draft-petrescu-its-scenarios-reqs-00.txt:

• First version of draft issued.

Authors' Addresses