<?xml version="1.0" encoding="US-ASCII"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
]>

<rfc category="info" docName="draft-kim-nmrg-nnmb5g-00" ipr="trust200902">

  <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
  <!-- used by XSLT processors -->
  <!-- For a complete list and description of processing instructions (PIs),
   please see http://xml.resource.org/authoring/README.html. -->
  <!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
   (Here they are set differently than their defaults in xml2rfc v1.32) -->
  <?rfc strict="yes" ?>
  <!-- give errors regarding ID-nits and DTD validation -->
  <!-- control the table of contents (ToC) -->
  <?rfc toc="yes"?>
  <!-- generate a ToC -->
  <?rfc tocdepth="4"?>
  <!-- the number of levels of subsections in ToC. default: 3 -->
  <!-- control references -->
  <?rfc symrefs="yes"?>
  <!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
  <?rfc sortrefs="no" ?>
  <!-- sort the reference entries alphabetically -->
  <!-- control vertical white space
   (using these PIs as follows is recommended by the RFC Editor) -->
  <?rfc compact="no" ?>
  <!-- do not start each main section on a new page -->
  <?rfc subcompact="no" ?>
  <!-- keep one blank line between list items -->
  <!-- end of list of popular I-D processing instructions -->

  <!-- ***** FRONT MATTER ***** -->
  <front>
      <!-- The abbreviated title is used in the page header - it is only necessary if the
       full title is longer than 39 characters -->

    <title abbrev="draft-kim-nmrg-nnmb5g-00">SOAR(Security Orchestration
      Automation and Response)-based Native Network Management to Optimize an
      Adaptive B5G Network</title>

    <!-- add 'role="editor"' below for the editors if appropriate -->
    <!-- Another author who claims to be an editor -->
    <author fullname="Hwan-kuk Kim" initials="M-S" surname="Kim">
        <organization abbrev="SANGMYUNG UNIVERSITY">SANGMYUNG UNIVERSITY</organization>
        <address>
            <postal>
                <street>31, Sangmyeongdae-gil, Dongnam-gu</street>
                <!-- Reorder these if your country does things differently -->
                <city>Cheonan</city>
                <region></region>
                <code>31066</code>
                <country>Korea</country>
            </postal>
            <phone>+82 41 550 5101</phone>
            <email>rinyfeel@smu.ac.kr</email>
            <!-- uri and facsimile elements may also be added -->
        </address>
    </author>

    <author fullname="Min-Suk Kim" initials="M-S" surname="Kim">
        <organization abbrev="SANGMYUNG UNIVERSITY">SANGMYUNG UNIVERSITY</organization>
        <address>
            <postal>
                <street>31, Sangmyeongdae-gil, Dongnam-gu</street>
                <!-- Reorder these if your country does things differently -->
                <city>Cheonan</city>
                <region></region>
                <code>31066</code>
                <country>Korea</country>
            </postal>
            <phone>+82 41 550 5113</phone>
            <email>minsuk.kim@smu.ac.kr</email>
            <!-- uri and facsimile elements may also be added -->
        </address>
    </author>

    <date month="Oct" year="2021" />
    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill
     in the current day for you. If only the current year is specified, xml2rfc will fill
	 in the current day and month for you. If the year is not the current one, it is
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to
	 specify just the year. -->

    <!-- Meta-data Declarations -->
    <area>Internet</area>

    <workgroup>Network Management Research Group</workgroup>

    <!-- WG name at the upperleft corner of the doc,
     IETF is fine for individual submissions.
	 If this element is not present, the default is "Network Working Group",
     which is used by the RFC Editor as a nod to the history of the IETF. -->

    <keyword>Internet Draft</keyword>

    <!-- Keywords will be incorporated into HTML output
     files in a meta tag but they have no effect on text or nroff
     output. If you submit your draft to the RFC Editor, the
     keywords will be used for the search engine. -->

    <abstract>
      <t>This document is derived from the intelligent artificial intelligent (AI)
        network and autonomous security, network management intend-based
        technology to ensure constant security quality in B5G. SOAR
        (Security Orchestration Automation and Response) is needed by autonomous
        security and network management to optimize an adaptive B5G network.
        The purpose of this document is to confirm whether the requirements are
         reflected to future users and to develop and identify user provided
         by useful decision how to develop the system. This document also covers
         the user requirements for autonomous security and intend-based network
         management to ensure constant security quality on B5G.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
		<t>In order to respond to large-scale attacks on B5G communication
      infrastructure based on hyper-performance, hyperspace, the advanced
      security threats targeting new convergence services and intended
      super-trust-based security technology. It can both ensure constant
      security throughout on B5G infrastructure and relate the foundations aim
      to acquire skills. For native network management to optimize an adaptive
      B5G network based on SOAR, there are a lot of research fields to secure
      intend-based super-trust security skills and the related technology such
       as vulnerability analysis and security threat modeling to provide
        super-reliable infrastructure for B5G network, AI-based autonomous
        security and control framework to provide safe new convergence services
        in B5G, B5G-based station security to ensure availability of 3D mobile
        communication and quantum security technologies (PQC, QKD) of conversion
        methodology for B5G encryption system application.
		</t>
    </section>

    <section title="Background">
      <section title="Autonomous Network">
  	    	<t>The autonomous network concept is defined differently depending on
             the standardization organization, and these contents are as follows.
  	      </t>
          <t>3GPP: SON (Self Organizing Networks)</t>
          <t>ETS/ITU-T/GSMA: Autonomous Network</t>
          <t>ETSI: ZSM (Zero touch network and Service Management)</t>
          <t>Hauwei: AND (Autonomous Driving Network)</t>
          <t>Juniper: SDN (Self Driving Network)</t>
          <t>Cisco: DNA (Digital(Data) Network Architecture)</t>
          <t>Ericson: ZTN (Zero Touch Network)</t>
          <t>Autonomous networks levels can also be divided into six different
            levels.</t>
          <t>Level 0 - Manual Network: The system is supported by monitoring
            function to manually execute dynamic tasks (SNMP, CLI)</t>
          <t>Level 1 - Assisted Network: The system executes specific and
            repetitive subtasks that are preconfigured to increase execution
            efficiency (Tack-Centric)</t>
          <t>Level 2 - Partial Autonomous Network: The system enables
            closed-loop O and M for specific devices based on AI models in specific external environments (Node-Centric)</t>
          <t>Level 3 - Conditional Autonomous network: L2-based system has
            functions to detect real-time environment change, specific network
            domain and intention device. Semi-closed loop management is possible
            to optimize and adjust to the external environment (Service-Centric)</t>
          <t>Level 4 - Highly autonomous Network: L3-based system has
            capabilities of service- and customer-experience-centric in a more
            complex cross-domain environment. It can analyze and make decisions
            based on predictive or active closed-loop management of the network
            (User-Centric)</t>
          <t>Level 5 - Fully autonomous network: The system is a fully
            autonomous network with multi-services, multi-domains and full
            lifecycle (Value-Centric)</t>


      </section>

      <section title="NWDAF (Network Data Analytics Function)">
        <t>NWDAF is one of the network functions located on the control plane in the SBA structure of 5GC.
          It is based on 5G Core, MEC (Cloud) and user equipment (UE) in edge networks.
          It is also used with data collection and data analysis depending on
          application function (AF) and Operations and Administration Maintenance
          (OAM). The purpose of NWDAF is to simplify the complexity of interfacing
          with 5GC and 3rd analytic solution providers. 5GC-related data in NWDAF
          is collected with 5G network data and the data can be analyzed by
           machine learning and statistical analysis. The analyzed result data is
           provided to other 5G core network functions to optimize each network
           function and to improve performance as its main function.
        </t>

        <figure anchor="nnmb5g-fig1" title="NWDAF Architecture Overview"> <artwork align="center">

     +----+
     +NF-1+----------------+--------------------+             +----+
     +----+                + NWDAF              +-------------+NF-1+
+-------------+   +-----+  +                    +             +----+
+ Untrusted AF+---+NEF-1+--+                    +
+-------------+   +-----+  +  +--------------+  +             +-----+
+----------+               +  +analytic Model+  +-------------+NEF-1+
+Trusted AF+---------------+  +(Static,      +  +             +-----+
+----------+               +  + algorithm)-3 +  +
     +-----+               +  +--------------+  +-------------------+
     +UDR-1+---------------+                    +
     +-----+               +                    +             +-----+
     +-----+               +                    +-------------+OAM-2+
     +OAM-2+---------------+                    +             +-----+
     +-----+               +--------------------+
----------------------------------------------------------------------------
    .................................................
    .  1: Core NF             2: Network Management .
    .  3: Proprietary Function                      .
    .................................................


         </artwork>
         <postamble></postamble>
        </figure>
      </section>

      <section title="Management for other Standardization">
        <t>NFV (Network Functions Virtualization) Management and NFVO
          (NFV Orchestration): Identify network function (NF) lifecycle
          management procedures in virtualized environments
        </t>
        <t>OSM (Open Source MANO): E2E Network Service Orchestrator (NFV +
          Slice + Cross Domain)
        </t>
        <t>MEC (Multi access Edge Computing) Management, F5G
          (Fifth Generation Fixed Network)
        </t>
        <t>ENI (Experiential Networked Intelligence):</t>
        <t>(a)Cognitive Netwok Management architecture using AI and Context aware Polices</t>
        <t>(b)Method to add intelligence to legacy systems</t>
        <t>(c)Method between API Broker layer and Legacy System (OSS/BSS, NF, User, etc. and ENI system)
        </t>
        <t>ZSM (Zero Touch Network and Service Management):</t>
        <t>(a)Fully Autonomous Management and Operations Framework level</t>
        <t>(b)Management Services of Domain, Unified Fabric and Cross Domain</t>
        <t>(c)Closed Loop Control Acquisition, Analysis, Determination and Execution Method Actions</t>
        <t>(D)Domain level Management, Cross Domain Level Management, Business Service Level Management
        </t>
        <t>This document present to aim B5G-based autonomous security and
          intend framework based on the constant security quality guarantee to
          provide the super-trusted infrastructure of the new convergent network
          security service without cyber threats
        </t>
      </section>
    </section>


  <section title="B5G Native Network Management based on SOAR">

		<section title="Purpose of B5G Native Network Management Framework">
	    	<t>It is necessary to verify native security element skill to analyze
          the detailed functions such as B5G wireless access, D2D and infrastructure
          virtualization. It is also needed to analyze B5G global network
          security-based intelligence and internalization technology, security
          vulnerability in flying base station and quantum security for security
          application system. We also propose of design of B5G native network
          management and requirement for B5G wireless access/D2D/infrastructure
          virtualization attack model, AI-based B5G autonomous security control
          of security native intelligence, networking security and intrusion
          detection in flying base station and quantum security for application
          of B5G security system. In addition, security native modeling and
          verification are also necessary in B5G native network management framework.
          [TM-Forum][ITU-T:Y.3172][ITU-T:Y.3173][ITU-T:Y.3174][ITU-T:Y.3176][FG-ML5G:spec1]
          [FG-ML5G:spec2][FG-ML5G:spec3][FG-ML5G:spec4][Y.ML:IMT2020-RAFR][TS23.288]
          [TR23.791][TR28.809][TR28.810][TR28.100][TR28.812][TR28.312][TR28.805]
          [TR28.535][TR28.536][TR28.861][TR28.313]
	      </t>
    </section>

		<section title="Scope of B5G Native Network Management">
	    	<t>Above all, the first scope is to analyze of B5G wireless access/D2D/infrastructure
          virtualization elements and to define security requirements such as
          B5G wireless access, Ultra-high-density of B5G D2D and infrastructure
          virtualization. In next scope, there are B5G wireless access/D2D/infrastructure
          virtualization attack model development and threat analysis, design of
          AI-based B5G autonomous security control and security intelligence
          internalization concept. It is also necessary to design networking security,
          intrusion detection element technology in flying base station and
          design of quantum security technology for B5G security application.
          Verification of the contents in advance is also additionally required
          with the following scope.
	    	</t>
   	</section>


	</section>


  <section anchor="IANA" title="IANA Considerations">
  	<t>There are no IANA considerations related to this document.</t>
  </section>

  <section title="Security Considerations">
   	<t>[TBD]</t>
  </section>

</middle>

<!--  *****BACK MATTER ***** -->
<!--  *****BACK MATTER ***** -->
<back>
    <!-- References split into informative and normative -->

    <!-- There are 2 ways to insert reference entries from the citation libraries:
     1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
     2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
     (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

     Both are cited textually in the same manner: by using xref elements.
     If you use the PI option, xml2rfc will, by default, try to find included files in the same
     directory as the including file. You can also define the XML_LIBRARY environment variable
     with a value containing a set of directories to search.  These can be either in the local
     filing system or remote ones accessed by http (http://domain/dir/... ).-->

 <references title="Informative References">

	<reference anchor='TM-Forum'>
        <front>
            <title>Aaron Richard Earl Boasman-Patel, Autonomous Networks: Empowering Digital Transformation for The Telecoms Industry</title>
            <author></author>
            <date month='' year='2019' />
        </front>
    </reference>

	<reference anchor='ITU-T:Y.3172'>
        <front>
            <title>Architectural framework for machine learning in future networks including IMT-2020</title>
            <author></author>
            <date month='' year='2020' />
        </front>
    </reference>

	<reference anchor='ITU-T:Y.3173'>
        <front>
            <title>Framework for evaluating intelligence level of future networks including IMT-2020</title>
            <author></author>
            <date month='' year='2020' />
        </front>
    </reference>

	<reference anchor='ITU-T:Y.3174'>
        <front>
            <title>Framework for data handling to enable machine learning in future networks including IMT-2020</title>
            <author></author>
            <date month='' year='2020' />
        </front>
    </reference>

	<reference anchor='ITU-T:Y.3176'>
        <front>
            <title>Machine learning marketplace integration in future networks including IMT-2020</title>
            <author></author>
            <date month='' year='2020' />
        </front>
    </reference>

	<reference anchor='FG-ML5G:spec1'>
        <front>
            <title>Requirements, architecture and design for machine learning function orchestrator</title>
            <author></author>
            <date month='' year='2020' />
        </front>
    </reference>

	<reference anchor='FG-ML5G:spec2'>
        <front>
            <title>Machine Learning Sandbox for future networks including IMT-2020 requirements and architecture framework</title>
            <author></author>
            <date month='' year='2020' />
        </front>
    </reference>

	<reference anchor='FG-ML5G:spec3'>
        <front>
            <title>Machine learning based end to end network slice management and orchestration</title>
            <author></author>
            <date month='November' year='2020' />
        </front>
    </reference>

	<reference anchor='FG-ML5G:spec4'>
        <front>
            <title>Vertical assisted Network Slicing Based on a Cognitive Framework</title>
            <author></author>
            <date month='' year='2020' />
        </front>
    </reference>

	<reference anchor='Y.ML:IMT2020-RAFR'>
        <front>
            <title>Architecture framework for AI based network automation of resource adaptation and failure recovery for future networks including IMT 2020</title>
            <author></author>
            <date month='' year='2020' />
        </front>
    </reference>

	<reference anchor='TS23.288'>
        <front>
            <title>Architecture enhancements for 5G System to support network data analytics services</title>
            <author></author>
            <date month='' year='2021' />
        </front>
    </reference>

  <reference anchor='TR23.791'>
        <front>
            <title>Study of Enablers for Network Automation for 5G</title>
            <author></author>
            <date month='' year='2021' />
        </front>
    </reference>
 <reference anchor='TR28.809'>
        <front>
            <title>Study on enhancement of Management Data Analytics (MDA)</title>
            <author></author>
            <date month='' year='2021' />
        </front>
    </reference>
 <reference anchor='TR28.810'>
        <front>
            <title>Study on concept, requirements and solutions for levels of autonomous network</title>
            <author></author>
            <date month='' year='2021' />
        </front>
    </reference>
 <reference anchor='TR28.100'>
        <front>
            <title>Management and orchestration; Levels of autonomous network</title>
            <author></author>
            <date month='' year='2021' />
        </front>
    </reference>
 <reference anchor='TR28.812'>
        <front>
            <title>Telecommunication management; Study on scenarios for Intent driven management services for mobile networks</title>
            <author></author>
            <date month='' year='2021' />
        </front>
    </reference>
 <reference anchor='TR28.312'>
        <front>
            <title>Intent driven management services for mobile networks</title>
            <author></author>
            <date month='' year='2021' />
        </front>
    </reference>
 <reference anchor='TR28.805'>
        <front>
            <title>Telecommunication management; Study on management aspects of communication services</title>
            <author></author>
            <date month='' year='2021' />
        </front>
    </reference>
 <reference anchor='TR28.535'>
        <front>
             <title>Management and orchestration; Management services for communication service assurance; Requirements</title>
             <author></author>
             <date month='' year='2021' />
       </front>
  </reference>
  <reference anchor='TR28.536'>
         <front>
              <title>Management and orchestration; Management services for communication service assurance; Stage 2 and Stage 3</title>
              <author></author>
              <date month='' year='2021' />
        </front>
   </reference>
   <reference anchor='TR28.861'>
          <front>
               <title>Study on the Self Organizing Networks (SON) for 5G networks</title>
               <author></author>
               <date month='' year='2021' />
         </front>
    </reference>
    <reference anchor='TR28.313'>
           <front>
                <title>Self-Organizing Networks (SON) for 5G networks</title>
                <author></author>
                <date month='' year='2021' />
          </front>
     </reference>

 </references>

</back>
</rfc>
