<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<rfc
      xmlns:xi="http://www.w3.org/2001/XInclude"
      category="std"
      docName="draft-zhao-detnet-enhanced-use-cases-01"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IETF"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3">

 <!-- ***** FRONT MATTER ***** -->

 <front>

   <title abbrev="Enhanced Use Cases for Scaling Deterministic Networks">Enhanced Use Cases for Scaling Deterministic Networks</title>
    <seriesInfo name="Internet-Draft" value="draft-zhao-detnet-enhanced-use-cases-01"/>

    <author fullname="Junfeng Zhao" initials="J" surname="Zhao">
      <organization>CAICT</organization>

      <address>
        <postal>
          <street></street>
          
          <city></city>
          
          <region></region>
  
          <code></code>

          <country>China</country>
        </postal>

        <phone></phone>

        <email>zhaojunfeng@caict.ac.cn</email>
      </address>
    </author>	
   
   <author fullname="Quan Xiong" initials="Q" surname="Xiong">
      <organization>ZTE Corporation</organization>
      <address>
        <postal>
          <street/>
         <city></city>
          <region/>
          <code/>
          <country>China</country>
        </postal>
        <phone></phone>
        <email>xiong.quan@zte.com.cn</email>
     </address>
    </author>
	
 <author fullname="Zongpeng Du" initials="Z" surname="Du">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street></street>
          
          <city></city>
          
          <region></region>
  
          <code></code>

          <country>China</country>
        </postal>

        <phone></phone>

        <email>duzongpeng@chinamobile.com</email>
      </address>
    </author>

	

   <area>Routing</area>
    <workgroup>DETNET</workgroup>
   <keyword></keyword>
   
   <abstract>

    <t>This document describes use cases and network requirements for 
	scaling deterministic networks which is not covered in RFC8578,
	such as industrial internet, high experience video and intelligent 
	computing, and outlines the common properties implied by these
	use cases.</t>
	  
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default"> <name>Introduction</name>
	
    <t>According to <xref target="RFC8655" pageno="false" format="default"/>, Deterministic Networking (DetNet) operates 
	at the IP layer and delivers service which provides extremely low data
    loss rates and bounded latency within a network domain. The bounded 
	latency indicates the minimum and maximum end-to-end latency from source 
	to destination and bounded jitter (packet delay variation). 
	<xref target="RFC8578" format="default"/> has presented use cases for 
	diverse industries and these use cases differ in their network 
	topologies and requirements. It should provide specific desired 
	behaviors in DetNet. </t>
	
	<t><xref target="I-D.ietf-detnet-scaling-requirements"></xref> focus
	on the scaling deterministic networks and describes the enhanced 
	requirements for DetNet enhanced data plane including the 
	deterministic latency guarantees and it also mentioned the 
	enhanced DetNet should support different levels of application
	requirements which is important for the DetNet deployment.
	There are a variety of use cases in scaling deterministic 
	networks which is not covered in <xref target="RFC8578" format="default"/>. 
	It is required to provide the typical use cases for scaling
	deterministic networks and analyze the SLAs requirements and
	desired behaviors in enhanced DetNet.</t>
	
	<t>The industries covered by the use cases in this document are:</t>
	
   <ul spacing="normal">
   <li>Industrial Internet (section 3.1)</li>
   <li>High Experience Video (section 3.2)</li>
   <li>Intelligent Computing (section 3.3)</li>
   </ul>
	
	 
	<t>This document describes use cases and network requirements for 
	scaling deterministic networks including industrial internet, 
	high experience video and intelligent computing and outlines
	the common properties implied by these use cases.</t>
	    
      <section numbered="true" toc="default"><name>Requirements Language</name>
	  
        <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" format="default">RFC 2119</xref>.</t>
	   
      </section>
    </section>
	
    <section anchor="Terminology" numbered="true" toc="default"> <name>Terminology</name>
	<t>The terminology is defined as <xref target="RFC8655" pageno="false" format="default"/> and
	<xref target="RFC8578" pageno="false" format="default"/>.</t>
     
    </section>
	
    <section numbered="true" toc="default"><name>Enhanced Use Cases and Network Requirements</name>

	 
    <section numbered="true" toc="default"> <name>Industrial Internet</name>
	
    <section numbered="true" toc="default"> <name>Use Case Description</name>
	
	<t>In the industrial internet, the entire industrial process can be 
	roughly divided into research and development design, production
	manufacturing, operation and maintenance services. The typical 
	application prospects of deterministic networks mainly include 
	ultra-high definition video, cloud-based robots, remote control, 
	machine vision, and cloud-based AGV. The scenarios such  as machine
	vision, AGV intelligent control, remote control, and AR assisted
	robotic arm control demand deterministic requirements.</t>
	
    <section numbered="true" toc="default"> <name>Machine Vision</name>	

    <t>The machine vision system needs to achieve real-time remote
	monitoring function, which requires high-speed and large 
	connectivity characteristics. It can monitor the production 
	process execution management system (MES) of manufacturing 
	enterprises through mobile and portable terminals without 
	entering the workshop, and obtain the operating status of 
	the visual inspection system, such as normal operating time, 
	effective operating time, fault cause etc. It is bandwidth 
	sensitive and demand cloud-based deployment and wide area  
	networks requirements.</t>
	
	<t>The following table shows the main network requirements 
	of machine vision.(These metrics are based on 3GPP Standard
	3GPP TS 22.104, 3GPP TR 22.261, and 3GPP TR 22.829.)</t>
 
 
  <figure title="Requirements of Machine Vision" align="center" suppress-title="false" alt="" width="" height="">
   <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	
   
   +---------------------------------+---------------------------------+
   |    Machine Vision Requirement   |            Attribute            |
   +---------------------------------+---------------------------------+
   |      Bandwidth                  |   Real time upload of image     |
   |                                 |   information:>50M              |
   |                                 |                                 |
   |     One-way maximum delay       |              10 ms              |
   |                                 |                                 |
   |           Availability          |             99.99%              |
   +---------------------------------+---------------------------------+
   
   	   </artwork>
 </figure>
 
</section>	
 

    <section numbered="true" toc="default"> <name>Remote Control</name> 
	
	<t>Remote control can ensure personnel safety, improve production
	efficiency, and achieve assistance from multiple production units. 
	In order to achieve the effect of remote control, the controller 
	needs to send status information to the controller through a 
	communication network based on remote perception. The controller
	analyzes and makes decisions based on the received status information, 
	and then sends corresponding action instructions to the controller 
	through the communication network. The controller executes the 
	corresponding actions based on the received action instructions, 
	completing the remote control process. In order to guarantee control 
	effectiveness, communication network latency, jitter, and reliability
	are even more important. The typical application is cloud-based PLC 
	(Programmable Logic Controller). It is jitter sensitive and  
    cloud-based PLC demand wide area networks requirements.</t>
	
	<t>The following table describes requirements of Cloud-based PLC.
	(These metrics are based on 3GPP Standard 3GPP TS 22.104, 3GPP TR 
	22.261, and 3GPP TR 22.829.)</t>

	 <figure title="Requirements of Cloud-based PLC" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	
		 
   +-------------------------------+-----------------------------------+
   |  Cloud-based PLC Requirement  |            Attribute              |
   +-------------------------------+-----------------------------------+
   |     Bandwidth                 | Image/video stream upload,        |      
   |                               |  upstream>50Mbps;                 |      
   |                               | PLC control command issued,       |      
   |                               |  downstream>50kbps;               |      
   |                               |                                   |      
   |      One-way maximum delay    |Within workshop level equipment:1ms| 
   |                               |Workshop level equipment room:10ms | 
   |                               |Remote operation in the park/city/ |
   |                               |wide area: image upstream:20ms;    |
   |                               |Command issuance:10ms;             |
   |                               |                                   |
   |          Maximum jitter       |      Less than 100 us             |
   |                               |                                   |
   |           Availability        |             99.999%               |
   +-------------------------------+-----------------------------------+
 
   	   </artwork>
    </figure>
	
	</section>
	
	<section numbered="true" toc="default"> <name>AGV Intelligent Control</name> 
	
	<t>Automated Guided Vehicle (AGV) is an intelligent device widely 
	used in highly automated places such as factory workshops, airports, 
	ports, freight warehouses, etc. It generally consists of three parts: 
	walking, navigation, and control systems. The automated AGV is equipped
	with a camera to capture the scene in front of the vehicle and upload 
	it to the MEC and navigation system in real-time through a 5G module 
	for image analysis and route planning, achieving fully automated logistics
	transportation. AGV has a certain driving speed and is often used in 
	cluster operation scenarios. Therefore, a network connection with 
	high deterministic delay and jitter is required to transmit control 
	signals. </t>
	
	<t>The following table describes requirements of AGV intelligent
	control.(These metrics are based on 3GPP Standard 3GPP TS 22.104, 
	3GPP TR 22.261, and 3GPP TR 22.829.)</t>
 
 	 <figure title="Requirements of AGV Intelligent Control" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">

   +-----------------------------+--------------------------------------+
   | AGV Intelligent Control     |                                      |
   |              Requirement    |            Attribute                 |
   +-----------------------------+--------------------------------------+
   |     Bandwidth               |Schedule communication:>1Mbps,        |
   |                             |Real time communication:1Mbps~200Mbps |      
   |                             |Visual: 10Mbps~1Gbps                  |          
   |                             |                                      |      
   |    One-way maximum delay    |Schedule communication:100ms          | 
   |                             |Dispatching communication:100ms       | 
   |                             |Real time communication:20ms~40ms     |
   |                             |Visual: 10ms~100ms                    |
   |     Availability            |             99.9999%                 |
   +-----------------------------+--------------------------------------+		 
   
   	   </artwork>
     </figure>
 
	 
    </section>

	
    <section numbered="true" toc="default"> <name>AR Assistance</name>
   <t>With the intelligent and networked transformation and upgrading 
   of industrial manufacturing equipment, more and more AR assisted 
   intelligent robots will be used in advanced manufacturing. At the 
   same time, there are scenarios where multiple robot systems work 
   together, such as welding, stamping, etc. The robotic arm is the 
   most widely used automated mechanical device in the field of robotics
   technology, in areas such as industrial manufacturing, medical 
   treatment, entertainment services, military, semiconductor manufacturing, 
   and space exploration. The more axis joints of the AR assisted 
   robotic arm, the higher the degree of freedom, and the larger the 
   angle of the operating range. </t>
   
   <t>The following table describes requirements of AR Assistance.
   (These metrics are based on 3GPP Standard 3GPP TS 22.104, 
	3GPP TR 22.261, and 3GPP TR 22.829.)</t>
   
     <figure title="Requirements of AR Assistance" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">

   +---------------------------+----------------------------+
   |  AR Assistance Requirement|            Attribute       |
   +---------------------------+----------------------------+
   |     Bandwidth             | Maintenance guidance:      |      
   |                           |  downstream>50Mbps         |      
   |                           |  upstream > 20Mbps         |      
   |                           |  downstream>50kbps         |      
   |                           | Auxiliary assembly: >50Mbps|
   |                           |  downstream: 1Mbps~30Mbps  | 
   |                           |                            |   
   |  One-way maximum delay    |Maintenance guidance:20ms   | 
   |                           |Auxiliary assembly:10ms     | 
   |                           |                            |
   |    Maximum jitter         |      Less than 500 us      |
   |                           |                            |
   |    Availability           |        99.999%             |
   +---------------------------+----------------------------+		 

   	   </artwork>
     </figure>
   
   </section>
	
	</section>
	
	<section numbered="true" toc="default"> <name>Requests to the IETF</name>
	
   <ul spacing="normal">
   
   <li>Real-time remote monitoring, which requires high-speed connectivity </li>
   <li>Cloud-based deployment, which requires transmission through 
   heterogeneous networks </li>
   <li>Cloud-based centralized management</li> 
   <li>Remote control is jitter sensitive, e.g. less than 100us</li> 
   <li>Industrial camera images with high definition, with little or
   no compression, which requires high bandwidth</li>
   <li>Low end-to-end delay requirements differ from applications
   and services, such as 10ms and 20ms</li>
   </ul>
	</section>
	
	</section>
	
	<section numbered="true" toc="default"> <name>High Experience Video</name>
	
	<section numbered="true" toc="default"> <name>Use Case Description</name>
	
	<t>High Experience Video refers to video content that delivers an 
	exceptional viewing experience through advanced technologies and 
	production techniques. It demands high-quality transmission to 
	ensure that the content is delivered without compromising its 
	integrity and impact. High Experience Video relies on deterministic
	networks to deliver the best possible viewing experience, which
	requires a combination of low latency, low jitter, high bandwidth,
	and high reliability. The typical scenarios of High Experience Video 
	involve applications that have high requirements for video quality, 
	transmission speed, and user experience such as cloud VR and AR,
	cloud games and cloud live streaming.</t>
	
    <section numbered="true" toc="default"> <name>Cloud VR and AR</name>
	
	<t>The key feature of Cloud Virtual Reality/Augmented Reality (Cloud VR/AR)
	is that content is on the cloud and rendering is on the cloud. 
	By utilizing powerful cloud capabilities, VR/AR user experience is
	improved and terminal costs are reduced. VR/AR will quickly enter 
	Cloud VR/AR to promote the rapid popularization of VR/AR services.
	Cloud AR/VR services exhibit strong latency sensitivity, and 
	different levels of experience require differentiated certainty. 
	Cloud VR/AR rendering and streaming latency are divided into three
	parts: cloud processing, network transmission, and terminal processing.
	Cloud VR/AR operation latency is divided into cloud rendering latency 
	and terminal secondary rendering and refresh rendering processes.</t>
	
	<t>The following table describes requirements of Cloud VR/AR. (These 
	metrics are based on 3GPP TR 22.261).</t>
	
	<figure title="The Requirements of Cloud VR/AR" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">
		 
+----------------------+-----------+---------------------+----------------+
|    Requirement       | Bandwidth |One-way maximum delay|Packet loss rate|
+----------------------+-----------+---------------------+----------------+
| Cloud VR/AR Video    |downstream |  50ms               |no more than    |
|  comfortable         | >75Mbps   |                     |0.001%          |
|  experience          |           |                     |                |
+----------------------+-----------+---------------------+----------------+
| Cloud VR/AR Video    |downstream |  50ms               |no more than    |
|comfortable experience|>140Mbps   |                     |0.001%          |
|full perspective      |           |                     |                |
+----------------------+-----------+---------------------+----------------+ 
| Cloud VR/AR strong   |downstream |  15ms               |no more than    |
|interaction           |>260Mbps   |                     |0.001%          |
|comfortable experience|           |                     |                |
|I frame and P frame   |           |                     |                |
+----------------------+-----------+---------------------+----------------+ 
| Cloud VR/AR strong   |downstream |  8ms                |no more than    |  
|interaction           |1Gbps      |                     |0.0001%         |   
|8K ideal experience   |           |                     |                |
|I frame and P frame   |           |                     |                |
+----------------------+-----------+---------------------+----------------+  
   	   </artwork>
    </figure> 
	
	</section>
	
	<section numbered="true" toc="default"> <name>Cloud Games</name>
	
	<t>Cloud Game is an online gaming technology based on cloud computing
	technology. Cloud gaming technology enables lightweight devices with 
	relatively limited graphics processing and data computing capabilities
	to run high-quality games. In cloud game scenarios, game related computing
	is not run on the user terminal, but on a cloud server, which renders the
	game scene as a video and audio stream and transmits it to the user 
	terminal through the network. The user's cloud gaming experience relies
	on a high-quality, low latency network environment. </t>
	
	<t>The following table describes requirements of Cloud Games:</t>
	
	<figure title="Requirements of Cloud Games" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">
		 
+----------------------+-----------+---------------------+----------------+
|    Requirement       | Bandwidth |One-way maximum delay|Video resolution|
+----------------------+-----------+---------------------+----------------+
| Junior level         | >8Mbps    |  150ms              |720P            |
+----------------------+-----------+---------------------+----------------+
| 3A professional level| >12Mbps   |  60ms               |1080P           |
+----------------------+-----------+---------------------+----------------+ 
| Level of esports     | >40Mbps   |  60ms               |4K              | 
+----------------------+-----------+---------------------+----------------+   
   	   </artwork>
    </figure> 
	
	</section>
	
    <section numbered="true" toc="default"> <name>Cloud Live Streaming</name>
	
	<t>For scenarios such as concerts, press conferences, sports events, 
	and live events, cloud live streaming uses 5G uplink high bandwidth 
	to transmit 8K/VR videos. Combined with various applications such as
	video analysis based on live streaming services, character and scene
	recognition, real-time presentation of athlete and event data, and VR
	live streaming interaction, it provides a brand new and rich event 
	viewing experience. </t>
	
	<t>The following table describes requirements of Cloud live streaming:</t>
	
	<figure title="Requirements of Cloud Live Streaming" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	
   +------------------------+---------------------+
   | 8K live streaming      |  Attribute          |
   | 8K video feedback      |                     |    
   +------------------------+---------------------+
   |     Bandwidth          |  upstream>100Mbps   |       
   |                        |                     |   
   |  One-way maximum delay |  200ms              | 
   |                        |                     |
   |    Availability        |  99.9%              |
   |                        |                     |
   |   Frame rate           |  60                 |
   +------------------------+---------------------+	
   	   </artwork>
    </figure> 
	
	</section>

     </section>
	<section numbered="true" toc="default"> <name>Requests to the IETF</name>
	
	 <ul spacing="normal">
	 
   <li>High requirements for video quality and transmission speed</li>
   <li>Cloud processing with real-time interaction </li>
   <li>Cloud-based deployment, which requires transmission through 
   heterogeneous networks </li>
   <li>No jitter requirements</li>
   <li>Packet loss requirement is less than 0.001%</li>
   <li>End-to-end delay requirements differ from applications
   and services, such as 8ms, 15ms, 50ms, 150ms, 200ms and so on</li>
   </ul>
	</section>
	
   </section>

    <section numbered="true" toc="default"> <name>Intelligent Computing</name>
	
    <section numbered="true" toc="default"> <name>Use Case Description</name>
	<t>Intelligent computing refers to the integration of artificial 
	intelligence (AI) techniques with computational methods to enhance
	the performance, efficiency, and capabilities of computing systems. 
	It involves the use of algorithms, machine learning models, and 
	other AI approaches to solve complex problems, analyze large datasets,
	and improve decision-making processes. Intelligent Computing has 
	specific requirements for deterministic networks to ensure reliable 
	and predictable performance such as predictable latency, low packet 
	loss rate, high throughput and reliability. The typical scenarios 
	involve applications such as AI-based scientific research and
	autonomous vehicles and so on.</t>
	
    <section numbered="true" toc="default"> <name>Scientific Research</name>

	<t>Intelligent computing is used to provide computing and data 
	analysis capabilities, which are crucial for handling large-scale
	scientific simulations and datasets such as astronomy, climate 
	science, and bioinformatics. In scientific research, a large amount 
	of computing power resources such as CPU, GPU, memory, and other
	P-level or higher are usually required. The network needs to 
	provide services for data volume of 10G to 100G or above, which
	requires high bandwidth, high reliability and high throughput with
	ultra-low packet loss. </t>
	
	<t>Many applications in scientific research, such as remote 
	observations, real-time data analysis, and distributed 
	computing, require networks to provide stable low latency and
	high reliability. It must provide millisecond or even microsecond
	level latency and jitter guarantees. For example, in nuclear 
	fusion experiments, the carrier network is required to have
	99.999% availability. </t>
	</section>
	
   <section numbered="true" toc="default"> <name>Autonomous Vehicles</name>
   <t>Intelligent computing is used in the development of self-driving 
   cars, which rely on AI algorithms for perception, decision-making, 
   and control. Autonomous vehicles refers to the technology of vehicles
   that are capable of navigating without the need for human input such 
   as identifying other vehicles, pedestrians, and traffic signals. 
   It relies heavily on deterministic forwarding to ensure safe, efficient,
   and reliable operation. It is also challenging for big data management
   of autonomous driving. Vehicles record data from 4K HD cameras, laser
   scanners, and radars on the road. Each vehicle can generate 80TB of 
   data per day, which requires data-intensive transmission.  </t>
   
   <t>V2X (Vehicle-to-Everything) is a fundamental component of the 
   autonomous driving ecosystem, providing the necessary communication
   backbone that enables vehicles to interact with their environment 
   in a safe and efficient manner. V2X provides the communication 
   infrastructure that enables vehicles to exchange information with 
   each other (V2V), with roadside infrastructure (V2I), with 
   pedestrians (V2P), and with the network (V2N). This exchange of 
   information is crucial for autonomous vehicles to make informed 
   decisions, improve navigation accuracy, and enhance overall road safety.
   The following table describes requirements of 5G V2X which is divided 
   into four scenarios. (These metrics are based on 3GPP TR 22.886)</t>
	
	<figure title="The Requirements of Autonomous Vehicles" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">
		 
+----------------------+---------------------+--------------+
|    Requirement       | Communication Delay | Availability |
+----------------------+---------------------+--------------+
| Vehicles Platooning  |    10~25ms          | 99%~99.99%   | 
+----------------------+---------------------+--------------+
| Extended Sensors     |    3~100ms          | 99%~99.999%  |  
+----------------------+---------------------+--------------+ 
| Advanced Driving     |    3~100ms          | 99%~99.999%  |
+----------------------+---------------------+--------------+ 
| Remote Driving       |    5ms              |  99.999%     |  
+----------------------+---------------------+--------------+  

   	   </artwork>
    </figure> 
   
	</section>
    </section>
	
    <section numbered="true" toc="default"> <name>Requests to the IETF</name>
	
    <ul spacing="normal">
   <li>Real-time communication</li>
   <li>Data-intensive transmission with high throughput 
   and ultra-low packet loss</li>
   <li>Low bounded latency, such as us~ms</li>
   <li>High availability, such as 99.999%</li>
   </ul>
	
	</section>
   </section>
   </section>

   <section numbered="true" toc="default"> <name>Use Case Common Themes</name>
   
   
   <section numbered="true" toc="default"> <name>Differentiated Deterministic Requirements</name>
   
   <t>Classification and characteristics has been summarized  
   from the requirements of use cases as described in <xref target="RFC8578" pageno="false" format="default"/>
   and this documents. Seven levels of typical applications 
   have been defined including on-site production control,
   remote control, production monitoring, production 
   collection, video AI, AR/VR high experience video and  
   intelligent computing. Different levels of applications
   differ in the network ranges and SLAs requirements such 
   as bounded latency, jitter, bandwidth, availability and 
   isolation.</t>
   
   <t>The following table summarizes deterministic requirements
   of industrial internet, cloud video and intelligent computing 
   applications, etc.</t>
   	
	<figure title="Characteristics of Typical Applications" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	

+---+------------+--------------------+---------------------------------------------------------+
|   | Use Case   | Typical            |       Differentiated Deterministic Requirements         |
|   |            | Applications       +----------+----------+---------+-------------------------+
|   |            |                    |Bandwidth | Delay    |  Jitter |Packet Loss| Availability|
+---+------------+--------------------+----------+----------+---------+-----------+-------------+
| 1 |Industrial  |Machine Vision      |  Low     |  Low     |   N/A   |    N/A    |   Medium    |
|   |Internet    |                    |          |          |         |           |             |
|   |            +--------------------+----------+----------+---------+-----------+-------------+
|   |            |Remote Control      |  Low     |  Low     |Ultra-low|    N/A    |   High      |          
|   |            +--------------------+----------+----------+---------+-----------+-------------+
|   |            |AGV Control         |Low~High  |Low~Medium| N/A     |    N/A    | Ultra-high  |
|   |	         +--------------------+----------+----------+---------+-----------+-------------+
|   |            |AR Assistance       | Low      | Low      |Ultra-low|    N/A    |   High      |  
+---+------------+--------------------+----------+----------+---------+-----------+-------------+
| 2 |High        |Cloud VR and AR     |Medium    | Low      |  N/A    | Ultra-low |    N/A      |
|   |Experience  |                    | ~High    |          |         |           |             |
|   |Video       |                    |          |          |         |           |             |
|   |            +--------------------+----------+----------+---------+-----------+-------------+
|   |            |Cloud Games         | Low      | High     |   N/A   |    N/A    |   N/A       |
|   |            +--------------------+----------+----------+---------+-----------+-------------+
|   |            |Cloud Live Streaming| Medium   | High     |   N/A   |    N/A    |   Medium    |            
+---+------------+--------------------+----------+----------+---------+-----------+-------------+
| 3 |Intelligent |Scientific Research |Ultra-high|  Low     |   N/A   | Ultra-low |  Ultra-high |
|   |Computing   |                    |          |          |         |           |             |
|   |            +--------------------+----------+----------+---------+-----------+-------------+
|   |            |Autonomous Vehicles |Ultra-high|  Low     |  N/A    | Ultra-low |  Ultra-high |       
+---+------------+--------------------+----------+----------+---------+-----------+-------------+


   	   </artwork>
    </figure>  
	

   <t>Since the DetNet applications differ in their requirements, it demands
   specific desired behavior and different services requires differentiated 
   DetNet QoS. The classification of the deterministic flows within different
   levels should be taken into considerations. It is required to provide 
   Latency, bounded jitter and packet loss dynamically and flexibly in all
   scenarios for each characterized flow. For example, as the figure shows, 
   the services can be classified into 4 types and DetNet applications 
   and related deterministic behaviors are differentiated within each type.</t>
  	<figure title="Classification of Deterministic Behaviors" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	
		 
+--------------+---------+--------------+---------------+----------+
|Classification|     1   |    2         |     3         |     4    |   
+--------------+---------+--------------+---------------+----------+
|Deterministic |Low      |Low delay and |Low delay and  | Ultra-low|
|Forwarding    |delay    |high bandwidth|Low packet loss| delay    |
|Behaviors     |         |              |               |and jitter| 
+--------------+---------+--------------+---------------+----------+
|Applications  |Machine  |Cloud         |Autonomous     |Remote    |
|Examples      |Vision   |AR/VR         |Vehicles       |Control   |
+--------------+---------+--------------+---------------+----------+

	   	   </artwork>
    </figure> 
   </section>
   
	
	</section> 
	
	
   
   <section  numbered="true" toc="default"> <name>Security Considerations</name>
   <t>Security considerations for DetNet are covered in the DetNet
   Architecture <xref target="RFC8655"></xref> and DetNet use cases
   <xref target="RFC8578"></xref> and DetNet security considerations
   <xref target="RFC9055"></xref>. </t>
   </section>
   <section numbered="true" toc="default"> <name>IANA Considerations</name>
   <t>This document makes no requests for IANA action.</t>
   </section>
	
   <section numbered="true" toc="default"> <name>Acknowledgements</name>
   <t>The authors would like to acknowledge Aihua Liu and Bin Tan for 
   their thorough review and very helpful comments.</t>
   </section> 
   
  </middle>
  
  <!--  *****BACK MATTER ***** -->

 <back>
 
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8664.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8655.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9320.xml"/>	
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8578.xml"/>
        <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9055.xml"/>	
        <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-detnet-scaling-requirements.xml"/>
		
      </references>
    </references>
 
 </back>
</rfc>
