One document matched: draft-liu-its-scenario-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="exp" docName="draft-liu-its-scenario-00" ipr="trust200902">
  <front>
    <title abbrev="ITS Scenario">Scenario of Intelligent Transportation
    System</title>

    <author fullname="Dapeng Liu" initials="D." surname="Liu">
      <organization>Alibaba Group</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <code/>

          <region/>

          <country>Beijing</country>
        </postal>

        <phone>+86-1391788933</phone>

        <facsimile/>

        <email>maxpassion@gmail.com</email>
      </address>
    </author>

    <date day="9" month="March" year="2015"/>

    <area>Internet Area</area>

    <workgroup/>

    <abstract>
      <t>This document discuss the scenario of intelligent transportation
      system.</t>
    </abstract>

    <note title="Requirements Language">
      <t>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 <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>
  </front>

  <middle>
    <section title="Scenario of Intelligent Transportation System Mobile Applications">
      <t>This document introduces several intelligent transportation system
      mobile applications. From those applications, we analyze the scenario
      and requirement of intelligent transportation system.</t>

      <section title="Waze">
        <t>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.</t>

        <t>Waze architecture is shown in figure 1.</t>

        <figure align="center">
          <preamble>preamble to the figure.</preamble>

          <artwork><![CDATA[
          +---------------------------+
          |      Waze Platform        |
          |     +Navigation           |  
          |     +Road Info            |
          |     +Traffic Info         |
          |     +Group communication  |
          +---------------------------+
                |       |         |
    +-----------+       |         +----------+
    |                   |                    |
+----------+       +----------+        +----------+
| Waze App |<----> | Waze App |<------>| Waze App | ...
+----------+ share +----------+  share +----------+

 Driver               Driver              Driver ]]></artwork>

          <postamble>Figure 1: Waze architecture</postamble>
        </figure>

        <t>Summary of the Waze architecture<list style="symbols">
            <t>There is a centralized waze server that collect the road and
            traffic information.</t>

            <t>Waze application can communicate with each other through
            centralized waze server.</t>

            <t>Waze application's communication is based on TCP/IP.</t>
          </list></t>
      </section>

      <section title="iRezQ">
        <t>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.</t>

        <figure align="center">
          <artwork><![CDATA[          +--------------------+
          |   SOS Operator     |
          +--------------------+
                     ^
                     |
          +--------------------+
          |   iRezQ Platform   |
          +--------------------+
            |        |       |
     +------+        |       +--------+
     |               |                |
+---------+      +---------+     +----------+
|iRezQ App| -->  |iRezQ App|     |iRezQ App |
+---------+ Warn +---------+     +----------+
  Crash]]></artwork>

          <postamble>Figure 2: iRezQ architecture</postamble>
        </figure>

        <t>Summary of iRezQ architecture:<list style="symbols">
            <t>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.</t>

            <t>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.</t>

            <t>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.</t>
          </list></t>

        <t/>
      </section>

      <section title="Sentinel">
        <t>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.</t>

        <t/>

        <figure>
          <artwork align="center"><![CDATA[

             +----------+
             |  Vehicle |
             +----------+
                  |   200m    +----------+
                  +---------->| Vehicle  |
                      Warn    +----------+
              ]]></artwork>

          <postamble>Figure 3: Sentinel architecture</postamble>
        </figure>

        <t/>

        <t>Summary of sentinel architecture:</t>

        <t><list style="symbols">
            <t>There is a vehicle to vehicle distance detection/communication
            in sentinel architecture.</t>
          </list></t>
      </section>

      <section title="COYOTE">
        <t>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.</t>

        <figure align="center">
          <artwork><![CDATA[

                  +------------------+
                  |  coyote platform |
                  +------------------+
        +------------------|--------------------+
   +----------+       +----------+       +-----------+
   |coyote App|       |coyote App|       | coyote App|
   +----------+       +----------+       +-----------+       
           ]]></artwork>

          <postamble>Figure 4: Coyote architecture</postamble>
        </figure>

        <t>Summary of coyote architecture:</t>

        <t><list style="symbols">
            <t>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.</t>
          </list></t>

        <t/>
      </section>
    </section>

    <section title="Communication Requirement of ITS Application ">
      <t>This section discusses the communication requirement of ITS
      application. Section 1 introduces several ITS mobile applications. From
      the analysis, we can conclude that:</t>

      <t><list style="symbols">
          <t>All the communication between the ITS mobile application and its
          backend server is based on IP.</t>

          <t>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.</t>

          <t>For some ITS application, for example, Sentinel, there is a
          requirement of direct communication between vehicles.</t>
        </list>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.</t>

      <t/>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document makes no request of IANA.</t>

      <t/>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>TBD</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>TBD</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>
    </references>
  </back>
</rfc>