<?xml version="1.0" encoding="US-ASCII"?>
<!-- <?xml version="1.0" encoding="UTF-8"?> -->
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com)
     by Daniel M Kohn (private)
-->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">


<?rfc toc="yes"?>
<?rfc rfcedstyle="yes"?>
<?rfc subcompact="no"?>
<?rfc symrefs="yes"?>

<rfc ipr="trust200902" category="info" docName="draft-jeong-cats-its-use-cases-00">

<front>
    <title abbrev="Computing-Aware ITS Use Cases">
    Use Cases for Computing-Aware Intelligent Transportation Systems
    </title>

    <author role="editor" initials="J." surname="Jeong" fullname="Jaehoon Paul Jeong">
        <organization abbrev="Sungkyunkwan University">
        Department of Computer Science and Engineering
        </organization>

        <address>
            <postal>
                <street>Sungkyunkwan University</street>
                <street>2066 Seobu-Ro, Jangan-Gu</street>
                <city>Suwon</city> <region>Gyeonggi-Do</region>
                <code>16419</code>
                <country>Republic of Korea</country>
            </postal>
            <phone>+82 31 299 4957</phone>
            <facsimile>+82 31 290 7996</facsimile>
            <email>pauljeong@skku.edu</email>
            <uri>http://iotlab.skku.edu/people-jaehoon-jeong.php
         </uri>
        </address>
    </author>

    <date month="July" day="8" year="2024" />

    <area>Routing Area</area>
    
    <workgroup>Computing-Aware Traffic Steering Working Group</workgroup>

<!-- [rfced] Please insert any keywords (beyond those that appear in
the title) for use on http://www.rfc-editor.org/rfcsearch.html. -->

<keyword>Internet-Draft</keyword>

    <abstract>
        <t>
        This document proposes use cases for Computing-Aware 
        Intelligent Transportation Systems (ITS).
        Computing-Aware Traffic Steering (CATS) provides the steering
        of packets of a traffic flow for a specific service request
        toward the corresponging service instance at an edge computing
        server at a service site.
        The use cases for Computing-Aware ITS include Context-Aware 
        Navigation for Terrestrial Vehicles and Unmanned Aerial Vehicles (UVA)
        and Edge-Assisted Cluster-Based MAC Protocol for Software-Defined
        Vehicles.
        </t>
    </abstract>
</front>

<middle>

<section anchor="section:Introduction" title="Introduction">
    <t>
    Nowadays, various networked services are provided by leveraging
    edge computing infrastructure. Either a closest or a lightest edge
    computing server (simply called an edge server) can be selected to
    serve a request service.
    In this trend, Computing-Aware Traffic Steering (CATS) is 
    standardized to provide the steering of packets of a traffic flow
    for a specific service request toward the corresponging service
    instance at an edge server at a service site.
    </t>
    
    <t>
    This document proposes two use cases for Computing-Aware 
    Intelligent Transportation Systems (ITS).
    They are (i) Context-Aware Navigation Protocol for Terrestrial Vehicles
    and  Unmanned Aerial Vehicles (UVA) <xref target="CNP-Vehicle" />
    <xref target="CNP-UAV" /> and (ii) Edge-Assisted Cluster-Based MAC
    Protocol for Software-Defined Vehicles (SDV) <xref target="ECMAC" />.
    </t>
        
</section>

<section anchor="section:Terminology" title="Terminology">
    <t>
      This document uses the terminology described in <xref target="RFC9315" />
      <xref target="I-D.ietf-cats-usecases-requirements" />, and 
      <xref target="I-D.ietf-cats-framework" />.
      In addition, the following terms are defined below:
    </t>

    <t>
    <list style="symbols">
      <t>
        Context-Aware Navigation Protocol (CNP): It is a protocol that
        enables either terrestrial vehicles (i.e., ground vehicles) or
        Unmanned Aerial Vehicles (UAV) to move in road networks or
        fly in the sky to maneuver safely without collisions, respectively 
        <xref target="CNP-Vehicle" /><xref target="CNP-UAV" />.
      </t>

      <t>
        Edge-Assisted Cluster-Based MAC Protocol (ECMAC): It is a protocol
        that enables Software-Defined Vehicles (SDV) to communicate with
        each other using Software-Defined Vehicular Networks with edge
        computing servers <xref target="ECMAC" />.
      </t>

    </list>
    </t>

</section>

<section anchor="section:Computing-Aware-ITS-Use-Cases" 
title="Use Cases for Computing-Aware Intelligent Transportation Systems">
    <t>
    This section explains a vehicular network architecture for vehicles and    
    three use cases for for Computing-Aware ITS.
    </t>

    <section anchor="section:Vehicular-Network-Architecture" 
    title="Vehicular Network Architecture">
        <t>
        Software-Defined Vehicles (SDV) include terrestrial vehicles and 
        Unmanned Aerial Vehicles (UAV). The standardization and implementation
        of SDVs are performed by AUTOSAR <xref target = "AUTOSAR" />, 
        Eclipes SDV <xref target = "Eclipse-SDV" />, and COVESA
        <xref target = "COVESA" />. 
        These SDVs need to communicate with each other to avoid collisions
        or accidents.
        </t>

        <t>
        <xref target = "figure:Vehicular-Network-Architecture" /> shows
        a Vehicular Network Architecture for Software-Defined Vehicles (SDV)
        such as terrestrial vehicles and Unmanned Aerial Vehicles (UAV).
        </t>

        <figure anchor="figure:Vehicular-Network-Architecture">
        <name>A Vehicular Network Architecture for Software-Defined Vehicles</name>
        <artwork name="" type="" align="left" alt=""><![CDATA[
                              Vehicular Cloud
               *******************************************
             *                                             *
            *              +------------------+             *
           *               | Cloud Controller |              *
           *               +------------------+              *
           *                         ^                       *
            *                        |                      *
             *                       v                     *
               *******************************************
                 ^ +------------+   ^ +------------+   ^ +------------+
                 | |Edge-Server1|   | |Edge-Server2|   | |Edge-Server3|
                 | +------------+   | +------------+   | +------------+
                 |   ^              |   ^              |   ^
                 |   |              |   |              |   |
                 v   V              v   V              v   V
               +---------+         +---------+        +---------+
               | IP-RSU1 |<------->| IP-RSU2 |<------>| IP-RSU3 |
               +---------+         +---------+        +---------+
                    ^                   ^                    ^
                    :                   :                    :
           +-----------------+ +-----------------+   +-----------------+
           |        : V2I    | |        : V2I    |   |       : V2I     |
           |        v        | |        v        |   |       v         |
+--------+ |   +--------+    | |   +--------+    |   |   +--------+    |
|  SDV1  |===> |  SDV2  |===>| |   |  SDV3  |===>|   |   |  SDV4  |===>|
+--------+<...>+--------+<........>+--------+    |   |   +--------+    |
           V2V     ^         V2V        ^        |   |        ^        |
           |       : V2V     | |        : V2V    |   |        : V2V    |
           |       v         | |        v        |   |        v        |
           |  +--------+     | |   +--------+    |   |    +--------+   |
           |  |  SDV5  |===> | |   |  SDV6  |===>|   |    |  SDV7  |==>|
           |  +--------+     | |   +--------+    |   |    +--------+   |
           +-----------------+ +-----------------+   +-----------------+
                 Subnet1              Subnet2              Subnet3
                (Prefix1)            (Prefix2)            (Prefix3)

        <----> Wired Link   <....> Wireless Link   ===> Moving Direction
]]></artwork>
        </figure>
    </section>

    <section anchor="section:Context-Aware-Navigation-Protocol" 
    title="Context-Aware Navigation Protocol">
    <t>
    Context-Aware Navigation Protocol is developed to provide
    the safe navigation (e.g., maneuver on the ground or in the
    sky) with Software-Defined Vehicles (SDV) such as electrical
    vehicles, autonomous vehicles, Unmanned Aerial Vehicle (UAV), 
    and urban Air Mobility (UAM) <xref target="CNP-Vehicle" />
    <xref target="CNP-UAV" />.
    </t>

    <t>
    A connected network of such SDVs (e.g., autonomous vehicles and
    drones) on road networks can facilitate the safe driving on the 
    ground or the safe flying in the sky.
    while driving on the roadways or skyways, many dangerous situations
    for SDVs may occur by the speed, orientation, and traffic density of
    the SDVs involved. Thus, there is a necessity for an automatic 
    maneuvering mechanism for SDVs that handles both the current driving
    SDV and the oncoming SDVs heading toward an emergency spot (e.g., 
    road hazard and road accident place).
    </t>

    <t>
    CNP is a realization of such an automatic maneuvering mechanism that
    SDVs collaborate with each other with the help of edge computing 
    infrastructure through wireless communications such as 5G 
    Vehicle-to-Everything Communication (i.e., 5G V2X).
    SDVs observe their road environments and other SDVs' behaviors
    with their on-board sensors like cameras and LiDAR.
    SDVs share these sensing data with an edge server in the edge
    computing infrastructure.
    </t>

    <t>
    The sensing data of SDVs need to be forwarded to an appropriate 
    edge server in terms of network status and computing resource status.
    Such an edge server needs to be selected in order to provide SDVs
    with timely guidance for safe driving.
    The edge server conducts a maneuver control with the mobility 
    information of SDVs and road environments, interacting with
    the SDVs and road infrastructure entities (e.g., traffic lights 
    and raod ramps) in real time.
    </t>

    <t>
    CNP also provides a collision mitigation scheme with the SDVs
    so that the SDVs may experience minimum collision damages 
    in hazardous roadways (or skyways) during non-maneuverable scenarios.
    CNP uses cluster formation where a cluster head is selected among 
    adjacent SDVs to give guidance to its cluster members for safe 
    maneuvering. The selection of such a cluster head is performed by
    the edge server that has the mobility information
    (e.g., speed, current position, and direction) of the SDVs.
    </t>
    
    <t>
    For SDVs, CNP based on IPv6 Neighbor Discovery is proposed in 
    <xref target="CNP-Vehicle" />. It can work on top of either
    Dedidated Short-Range Communications (DSRC) like Wireless Access
    in Vehicular Environments (WAVE) or 5G V2X.
    Refer to <xref target="CNP-Vehicle" /> and <xref target="CNP-UAV" />
    for the detailed mechanism of CNP for SDVs moving in either 
    roadways or flying in skyways.
    </t>
    </section>

    <section anchor="section:Edge-Assisted-Cluster-Based-MAC-Protocol" 
    title="Edge-Assisted Cluster-Based MAC Protocol">
    <t>
    Edge-Assisted Cluster-Based MAC Protocol (ECMAC) is a protocol
    to facilitate the real-time communications among SDVs for 
    safe maneuvering (e.g., driving or flying).
    ECMAC works on the SDVs with the help of an edge server
    in Software-Defined Vehicular Networks (SDVN).
    </t>

    <t>
    The edge server collects the mobility information from the SDVs
    in Vehicular Ad Hoc Networks (VANET) or Flying Ad Hoc Networks (FANET).
    The SDVs are formed in clusters that have a cluster head and the 
    corresponging cluster members by the edge server in the SDVN.
    The edge server allocates a wireless channel and time slot scheduling 
    to each cluster. Cluster members in each cluster report their 
    mobility information (e.g., speed, current position, and direction)
    to its cluster head according to the time slot scheduling for a given
    wireless channel. The cluster head reports the aggregated mobility 
    information to the edge server. 
    </t>

    <t>
    An appropriate edge server needs to be dynamically selected and relaced 
    according to the navigation path of the SDVs. 
    This selection of an edge server should be performed by considering 
    the network status and computing resource status between the edge server
    and SDVs.
    </t>

    <t>
    Refer to <xref target="ECMAC" /> for the detailed mechanism of ECMAC 
    for SDVs moving in roadways.
    </t>
    </section>

</section>

<section anchor="section:IANA-Considerations" title="IANA Considerations">
  <t>
    This document does not require any IANA actions.
  </t>
</section>

<section anchor="section:Security-Considerations" title="Security Considerations">
  <t>
    The same security considerations for Computing-Aware Traffic Steering (CATS)
    are applicable to the use cases for the 
    Computing-Aware ITS <xref target="I-D.ietf-cats-usecases-requirements" />
    <xref target="I-D.ietf-cats-framework" />.
  </t>

</section>

</middle>

<back>

<!-- START: Normative References -->
<references title="Normative References">

    <?rfc include="reference.RFC.9315"?>
    
</references>
<!-- END: Normative References -->

<!-- START: Informative References -->
<references title="Informative References">

    <?rfc include='reference.I-D.ietf-cats-usecases-requirements'?>
    <?rfc include='reference.I-D.ietf-cats-framework'?>

    <reference anchor="AUTOSAR">
        <front>
            <title>AUTOSAR Adaptive Platform</title>
            <author surname="AUTOSAR" />
            <date month="March" year="2024" />
        </front>
        <seriesInfo name="Available:" value="https://www.autosar.org/standards/adaptive-platform" />    
    </reference>

    <reference anchor="Eclipse-SDV">
        <front>
            <title>Eclipse Software Defined Vehicle Working Group Charter</title>
            <author surname="Eclipse" />
            <date month="March" year="2024" />
        </front>
        <seriesInfo name="Available:" value="https://www.eclipse.org/org/workinggroups/sdv-charter.php" />    
    </reference>

    <reference anchor="COVESA">
        <front>
            <title>Connected Vehicle Systems Alliance </title>
            <author surname="COVESA" />
            <date month="March" year="2024" />
        </front>
        <seriesInfo name="Available:" value="https://covesa.global/" />    
    </reference>

    <reference anchor="CNP-Vehicle">
        <front>
            <title>Context-Aware Navigation Protocol for Safe Driving in Vehicular Cyber-Physical Systems</title>
            <author initials="B." surname="Mugabarigira" />            
            <author initials="Y." surname="Shen" />
            <author initials="J." surname="Jeong" />
            <author initials="T." surname="Oh" />
            <author initials="H." surname="Jeong" />            
            <date month="January" year="2023" />
        </front>
        <seriesInfo name="IEEE" value="Transactions on Intelligent Transportation Systems" />
        <seriesInfo name="Available:" value="https://ieeexplore.ieee.org/document/9921182" />    
    </reference>

    <reference anchor="CNP-UAV">
        <front>
            <title>Context-Aware Navigation Protocol for Safe Flying of Unmanned Aerial Vehicles</title>
            <author initials="B." surname="Mugabarigira" />            
            <author initials="J." surname="Jeong" />
            <date month="January" year="2024" />
        </front>
        <seriesInfo name="KICS" value="Winter Conference" />
        <seriesInfo name="Available:" value="http://iotlab.skku.edu/publications/international-journal/CNP-TITS-2023.pdf" />    
    </reference>

    <reference anchor="ECMAC">
       <front>
            <title>ECMAC: Edge-Assisted Cluster-Based MAC Protocol in Software-Defined Vehicular Networks</title>
            <author initials="Y." surname="Shen" />
            <author initials="J." surname="Jeong" />
            <author initials="J." surname="Jun" />
            <author initials="T." surname="Oh" />
            <author initials="Y." surname="Baek" />            
            <date month="April" year="2024" />
        </front>
        <seriesInfo name="IEEE" value="Transactions on Vehicular Technology" />
        <seriesInfo name="Available:" value="https://ieeexplore.ieee.org/document/10505005" />    
     </reference>


</references>
<!-- END: Informative References -->

<section title="Acknowledgments">

    <t indent="0" pn="section-appendix.a-1">    
    This work was supported by Institute of Information &amp; Communications
    Technology Planning &amp; Evaluation (IITP) grant funded by the Korea
    Ministry of Science and ICT (MSIT) (No. RS-2024-00398199).
    </t>

    <t indent="0" pn="section-appendix.a-2">
    This work was supported in part by Institute of Information &amp; Communications
    Technology Planning &amp; Evaluation (IITP) grant funded by the Korea
    Ministry of Science and ICT (MSIT) (No. 2022-0-01015, Development of
    Candidate Element Technology for Intelligent 6G Mobile Core Network).
    </t>

    <t indent="0" pn="section-appendix.a-3">    
    This work was supported in part by the National Research Foundation of Korea
    (NRF) grant funded by the Korea government, Ministry of Science and ICT
    (MSIT) (No. 2023R1A2C2002990).
    </t>

</section>

<section anchor="section:Contributors" title="Contributors">
    <t indent="0" pn="section-appendix.b-1">
    This document is made by the group effort of CATS WG, greatly benefiting 
    from inputs and texts by <contact fullname="Peng Liu"/> (China Mobile),
    <contact fullname="Yong-Geun Hong"/> (Daejeon University), and
    <contact fullname="Joo-Sang Youn"/> (Dong-Eui University).
    The authors sincerely appreciate their contributions.
    </t>

    <t indent="0" pn="section-appendix.b-2">  
    The following are coauthors of this document:
    </t>   

      <contact fullname="Bien Aime Mugabarigira">
        <organization showOnFrontPage="true">Department of Electrial &amp; Computer Engineering</organization>
        <address>
          <postal>
            <extaddr>Sungkyunkwan University</extaddr>
            <street>2066 Seobu-Ro, Jangan-Gu</street>
            <city>Suwon</city>
            <region>Gyeonggi-Do</region>
            <code>16419</code>
            <country>Republic of Korea</country>
          </postal>
          <phone>+82 31 299 4106</phone>
          <email>bienaime@skku.edu</email>
          <uri>http://iotlab.skku.edu/people-Bien-Aime.php</uri>
        </address>
      </contact>

      <contact fullname="Yiwen Shen">
        <organization showOnFrontPage="true">Department of Computer Science &amp; Engineering</organization>
        <address>
          <postal>
            <extaddr>Sungkyunkwan University</extaddr>
            <street>2066 Seobu-Ro, Jangan-Gu</street>
            <city>Suwon</city>
            <region>Gyeonggi-Do</region>
            <code>16419</code>
            <country>Republic of Korea</country>
          </postal>
          <phone>+82 31 299 4106</phone>
          <email>chrisshen@skku.edu</email>
          <uri>http://iotlab.skku.edu/people-chris-shen.php</uri>
        </address>
      </contact>
</section>

</back>

<!-- <vspace blankLines="100"/> -->
<!-- page break to put addresses onto one page-->

</rfc>
