Network Working Group D. Liu Internet-Draft Alibaba Group Intended status: Experimental March 9, 2015 Expires: September 10, 2015 Scenario of Intelligent Transportation System draft-liu-its-scenario-00 Abstract This document discuss the scenario of intelligent transportation system. Requirements Language 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]. 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 September 10, 2015. Copyright Notice Copyright (c) 2015 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 Liu Expires September 10, 2015 [Page 1] Internet-Draft ITS Scenario March 2015 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. Scenario of Intelligent Transportation System Mobile Applications . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Waze . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2. iRezQ . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Sentinel . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4. COYOTE . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Communication Requirement of ITS Application . . . . . . . . 5 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 6. Normative References . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Scenario of Intelligent Transportation System Mobile Applications This document introduces several intelligent transportation system mobile applications. From those applications, we analyze the scenario and requirement of intelligent transportation system. 1.1. Waze Waze (https://www.waze.com/) is a community-based traffic and navigation application. The drivers who use waze can share the traffic related event to other waze users. Traffic related event includes traffic jams, accidents, road hazards etc. It uses the idea of UGC (User Provided Content) to generate real-time traffic map. Waze users can also communicate with each other using the waze platform. For example, a group of friends that have the same destination can share their location to coordinate everyone's arrival times. Waze architecture is shown in figure 1. Liu Expires September 10, 2015 [Page 2] Internet-Draft ITS Scenario March 2015 preamble to the figure. +---------------------------+ | Waze Platform | | +Navigation | | +Road Info | | +Traffic Info | | +Group communication | +---------------------------+ | | | +-----------+ | +----------+ | | | +----------+ +----------+ +----------+ | Waze App |<----> | Waze App |<------>| Waze App | ... +----------+ share +----------+ share +----------+ Driver Driver Driver Figure 1: Waze architecture Summary of the Waze architecture o There is a centralized waze server that collect the road and traffic information. o Waze application can communicate with each other through centralized waze server. o Waze application's communication is based on TCP/IP. 1.2. iRezQ iRezQ is another mobile application in the ITS field. Its main use case is for driving safety. The iRezQ mobile application running on the driver's mobile phone can monitor the vehicle's speed to detect whether there is a collision. When collision is detected, iRezQ application can dial the emergency call automatically. The architecture of iRezQ architecture is shown in figure 2. Liu Expires September 10, 2015 [Page 3] Internet-Draft ITS Scenario March 2015 +--------------------+ | SOS Operator | +--------------------+ ^ | +--------------------+ | iRezQ Platform | +--------------------+ | | | +------+ | +--------+ | | | +---------+ +---------+ +----------+ |iRezQ App| --> |iRezQ App| |iRezQ App | +---------+ Warn +---------+ +----------+ Crash Figure 2: iRezQ architecture Summary of iRezQ architecture: o The iRezQ mobile application is used to detect whether there is a collision occurs. It uses the sensors in the mobile phone and certain algorithm to determine whether there is a crash happening. o If there is a crash detected by iRezQ mobile application, it will warn the driver and sent out iRezQ-Warning message to all the nearby drivers who are using iRezQ mobile application. The nearby iRezQ users will receive a "WARNING! ACCIDENT NEARBY" message. It will prevent the nearby drivers running into the collision again and result in a second crash. o For premium member, iRezQ mobile application will alert the iRezQ emergency rescue center where an operator can see the driver's position and breaking pattern presented i a graph. The iRezQ rescue center will try to reach the driver if they suspect a true accident. 1.3. Sentinel Sentinel is security system used in Dakar rally. It is a security system that alerts the drivers and riders about imminent overtakes or accidents. It beeps and glows to warn the rider that he is going to be overtaken. It alerts the participant who's being overtaken when there are 200m between two vehicles. The architecture of sentinel is shown in figure 3. Liu Expires September 10, 2015 [Page 4] Internet-Draft ITS Scenario March 2015 +----------+ | Vehicle | +----------+ | 200m +----------+ +---------->| Vehicle | Warn +----------+ Figure 3: Sentinel architecture Summary of sentinel architecture: o There is a vehicle to vehicle distance detection/communication in sentinel architecture. 1.4. COYOTE Coyote System is a provider of community-based driving assistants. Coyote provides real-time information on speed limits, road hazards and traffic conditions to the coyote users. The architecture of coyote is shown in figure 4. +------------------+ | coyote platform | +------------------+ +------------------|--------------------+ +----------+ +----------+ +-----------+ |coyote App| |coyote App| | coyote App| +----------+ +----------+ +-----------+ Figure 4: Coyote architecture Summary of coyote architecture: o Coyote has similar architecture as Waze. Coyote users can share traffic information to coyote platform and the coyote platform can share the traffic information to other coyote users. 2. Communication Requirement of ITS Application This section discusses the communication requirement of ITS application. Section 1 introduces several ITS mobile applications. From the analysis, we can conclude that: o All the communication between the ITS mobile application and its backend server is based on IP. Liu Expires September 10, 2015 [Page 5] Internet-Draft ITS Scenario March 2015 o For some of those ITS applications, there is no direct communication between the ITS mobile applications but there is communication between ITS applications through the backend server. o For some ITS application, for example, Sentinel, there is a requirement of direct communication between vehicles. IP provides the most flexibility from the developer's perspective. There are plenty of developers that are familiar with developing application based on TCP/IP. If there is a direct IP connection between vehicles, it will help the developers to develop more innovative and useful applications. 3. IANA Considerations This document makes no request of IANA. 4. Security Considerations TBD 5. Acknowledgements TBD 6. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Author's Address Dapeng Liu Alibaba Group Beijing Beijing Phone: +86-1391788933 Email: maxpassion@gmail.com Liu Expires September 10, 2015 [Page 6]