<?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-00"
      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-00"/>

    <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 computing-aware
	applications, and analyzes the classification for the three typical
	use cases and applications.</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>Computing-Aware Applications (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 computing-aware applications and analyzes
	the classification for the three typical use cases and applications.</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>
	
	<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, AR/VR, 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 deployment and wide area hosting 
	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 type and  
    cloud based PLC demand wide area hosting.</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 u
	sed 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 fields 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>High Experience Video</name>
	
    <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 business.
	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>Computing-aware Applications</name>
	
	<t>HPC and big data applications demand high bandwidth and high 
	reliability in carrying capacity. In the field of scientific 
	research, a large amount of computing power resources such as 
	CPU, GPU, memory, and other P-level or higher are usually 
	required. The bearer network needs to provide access data 
	channels of 10G to 100G or above, and propose high reliability
	and high isolation bearer requirements. </t>
	
	
	<t>In nuclear fusion experiments, the carrier network is 
	required to have 99.999% availability. DC remote disaster 
	recovery proposes deterministic load-bearing requirements 
	for large bandwidth, low latency, and secure isolation. 
	DC remote disaster recovery applications are mainly 
	concentrated in industries such as finance and bonds. 
	The data consistency requirement for remote disaster 
	recovery multi activity systems should not exceed 10ms,
	and the data consistency requirement for local disaster 
	recovery multi activity systems should be between 1.5ms 
	and 2ms. </t>
	
	</section>
   </section>


   <section numbered="true" toc="default"> <name>Classification of the Differentiated Applications</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 production control, production monitoring, production 
   collection, video AI, AR/VR high experience video and key control. 
   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 new computing force 
   applications, ect.</t>
   	
	<figure title="Classification and Characteristics of Typical Applications" align="center" suppress-title="false" alt="" width="" height="">
         <artwork align="center" xml:space="preserve" name="" type="" alt="" width="" height="">	
   

+---+--------------------+---------------------+-----------------+-------------+
|   |   Classification   | Typical Applications|Characteristics  |Networks     |
+---+--------------------+---------------------+-----------------+-------------+
| 1 | Production control | Industrial          | low jitter      |Local area   |
|   | in the park        | internet            | low latency     |             |
|   |                    | PLC,etc             | low bandwidth   |             |
+---+--------------------+---------------------+-----------------+-------------+  
| 2 | Remote control     | Industrial          | low jitter      |Local/       |
|   |                    | internet            | low latency     |metropolitan/|
|   |                    | cloud PLC,etc       | low bandwidth   |wide area    |  
+---+--------------------+---------------------+-----------------+-------------+
| 3 | Production  data   | Industry IoT data   |low latency      |Local/       |
|   | collection         | collection, etc     |large connection |metropolitan/|
|   |                    |                     |low speeds       |wide area    | 
+---+--------------------+---------------------+-----------------+-------------+
| 4 | Production         | Industry production |medium bandwidth |Local/       |
|   | Monitoring         | and safety video    |bounded latency  |metropolitan/|
|   |                    | monitoring, etc     |                 |wide area    | 
+---+--------------------+---------------------+-----------------+-------------+
| 5 | AR/VR high         |Industry AR/VR       |high bandwidth   |Local/       |
|   | experience video   |assistance,          |low latency      |metropolitan/|
|   |                    |consumer AR/VR, high |                 |wide area    | 
|   |                    |experience cloud game|                 |             |
|   |                    |cloud live streaming |                 |             |
+---+--------------------+---------------------+-----------------+-------------+   
| 6 | AI for video       |Machine vision and   |high bandwidth   |Local/       |
|   |                    |high-definition      |low latency      |metropolitan/|
|   |                    |quality inspection   |high Availability|wide area    | 
+---+--------------------+---------------------+-----------------+-------------+
| 7 | Key control        |Physical isolation   |ultra high       |Local/       |
|   |                    |class of power grid: |Availability     |metropolitan/|
|   |                    |differential         |and isolation    |wide area    | 
|   |                    |protection, etc.     |                 |             |
|   |                    |critical control     |                 |             |
|   |                    |class related to life|                 |             |
|   |                    |safety in industry   |                 |             |
+---+--------------------+---------------------+-----------------+-------------+    
   	   </artwork>
    </figure>    
   </section>
   
   
   <section  numbered="true" toc="default"> <name>Security Considerations</name>
   <t>TBA</t>
   </section>
   <section numbered="true" toc="default"> <name>IANA Considerations</name>
   <t>TBA</t>
   </section>
	
   <section numbered="true" toc="default"> <name>Acknowledgements</name>
   <t>TBA</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://datatracker.ietf.org/doc/bibxml3/draft-ietf-detnet-scaling-requirements.xml"/>
		
      </references>
    </references>
 
 </back>
</rfc>
