<?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-suk-nmrg-sdaf5g-ibn-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-suk-nmrg-sdaf5g-ibn-00">Security Data Analytics Function Based on 5G Service-Based Architecture for Intent-Based Network Management</title>

    <!-- add 'role="editor"' below for the editors if appropriate -->
    <!-- Another author who claims to be an editor -->
    <author fullname="Hwankuk Kim" initials="H-K" surname="Kim">
        <organization abbrev="Kookmin University">Kookmin University</organization>
        <address>
            <postal>
                <street>77, Jeongneung-ro, Seongbuk-gu</street>
                <!-- Reorder these if your country does things differently -->
                <city>Seoul</city>
                <region></region>
                <code>02707</code>
                <country>Korea</country>
            </postal>
            <phone>+82 2 910 4745</phone>
            <email>rinyfeel@kookmin.ac.kr</email>
            <!-- uri and facsimile elements may also be added -->
        </address>
    </author>

    <author fullname="Min-Gyu Kim" initials="M-G" surname="Kim">
        <organization abbrev="Kookmin University">Kookmin University</organization>
        <address>
            <postal>
                <street>77, Jeongneung-ro, Seongbuk-gu</street>
                <!-- Reorder these if your country does things differently -->
                <city>Seoul</city>
                <region></region>
                <code>02707</code>
                <country>Korea</country>
            </postal>
            <phone>+82 2 910 4114</phone>
            <email>skystarloid@kookmin.ac.kr</email>
            <!-- uri and facsimile elements may also be added -->
        </address>
    </author>

    <author fullname="Jaehyeok Jeong" initials="J-H" surname="Jeong">
        <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 5114</phone>
            <email>2023D1013@sangmyung.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>mskim1997@gmail.com</email>
            <!-- uri and facsimile elements may also be added -->
        </address>
    </author>
    <date month="Jul" year="2024" />
    <!-- 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 architecture and detailed functions of SDAF. It is a network function to perform a security analysis and provide analysis results in a 5G system with a service-based architecture (SBA). To this end, the concept of SDAF, the structure of internalizing the 5G system, and the communication interface used by SDAF are defined. It also defines the use cases that can utilize SDAF. This standard is based on the service and operation requirements for a 5G system with SBA.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
     <t>To respond to large-scale attacks on 5G communication infrastructure based on hyper-performance, hyperspace, and advanced security threats targeting new convergence services and intended super-trust-based security technology. It can ensure constant security throughout B5G infrastructure and relate to the foundation aim to acquire skills. For ibn management to optimize an adaptive 5G network, there are a lot of research fields to secure intent-based super-trust security skills and related technology. AI-based autonomous security and control framework to provide safe new convergence services, 5G-based station security to ensure availability of 3D mobile communication, and quantum security technologies (PQC, QKD) of conversion methodology for B5G encryption system application. This document outlines the architecture and specific functions of SDAF, a network function designed to conduct security analysis and deliver analysis results within 5G systems utilizing a Service-Based Architecture (SBA). To this end, we define the concept of SDAF, the structure for internalizing the 5G system, the communication interface SDAF uses, and a use case that can utilize it. This is also based on the service and operation requirements for a 5G system with SBA (3GPP).</t></section>

    <section title="Convention and Terminology">
     <t>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119.
     </t></section>

    <section title="Background"> 
      <section title="Terminology">
        <t>NWDAF (Network Data Analytics Function): As one of the components of the 5G service-based architecture, SDAF analyzes past events for NFs in the 5G core network (statistics or predictions) and provides the results. Consequently, this enables overall management and performance improvement of the 5G network. (Technical Specification (TS) 23.288)</t>        
        <t>SBA (Service Based Architecture): A structure of a 5G system defined in Release 15 by 3GPP allows control plane NFs to interact with each other based on services. The NFs of the SBA interact using a service-based interface (SBI). (TS 23.501)</t>
        <t>SBI (Service Based Interface): A structure of a 5G system defined in Release 15 by 3GPP enables control plane NFs to interact with each other based on services. The NFs within the SBA interact using a service-based interface (SBI). (TS 23.501)</t>
      </section>

      <section title="Abbreviations Theorem">
        <t>3GPP: The 3rd Generation Partnership Project</t>
        <t>AF: Application Function</t>
        <t>AMF: Access and Mobility Management Function</t>
        <t>AUSF: Authentication Server Function</t>
        <t>DN: Data Network</t>
        <t>gNB: Next Generation Node B</t>
        <t>NF: Network Function</t>
        <t>NRF: Network Repository Function</t>
        <t>PCF: Policy Control Function</t>
        <t>(R)AN: Radio Access Network</t>
        <t>UDM: Unified Data Management</t>
        <t>UDR: Unified Data Repository</t>
        <t>UE: User Equipment</t>
        <t>UPF: User Plane Function</t>
      </section>

      <section title="Purpose of Research">
        <section title="Definition of 5G/6G Security Internalization Element Technology Analysis and Detail Function">
          <t>1. 5G/6G Wireless Access/D2D/Infrastructure Virtualization Element Technical Analysis and Definition of Security Requirements</t>
          <t>2. 5G/6G Global Network Security Intelligence Internalization Element Technology Analysis and Detail Functional Definition</t>
          <t>3. Analysis of Flying Base Station Security Vulnerabilities and Security Requirements</t>
          <t>4. Analysis of Quantum Security Element Technology for Application of 5G/6G Cryptosystem</t>
        </section>

       <section title="Conceptual Design of 5G/6G Security Internalization Element Technology ">
          <t>1. 5G/6G Wireless Access/D2D/Infrastructure Virtualization Element Technical Analysis and Definition of Security Requirements</t>
          <t>2. 5G/6G Global Network Security Intelligence Internalization Element Technology Analysis and Detail Functional Definition</t>
          <t>3. Analysis of Flying Base Station Security Vulnerabilities and Security Requirements</t>
          <t>4. Analysis of Quantum Security Element Technology for Application of 5G/6G Cryptosystem</t>
        </section>
       </section>
     </section>

    <section title="Design of SDAF Features and SBI Interface">
        <section title="SDAF Definition and Key Features">
          <t>The 5G system architecture is based on the software and virtualization of network functions (NF). An NF that performs a specific network function is defined, and the interworking between NFs is carried out using a service-based interface (SBI). The SBA structure aims for a service-oriented architecture that provides independent micro-services by modularizing network functions such as Session Management Functions (SMF), Access and Mobility Management Functions (AMF), and User Plane Data Processing (UPF). In addition, each NF adopted a standardized communication interface through the RESTful API based on HTTP/2 and JSON, enabling them to operate as a 'Provider and Consumer' structure for interconnection and communication between the two NFs. SDAF is an application function for internalizing real-time security analysis functions according to 5G service-based architecture standards. The purpose of SDAF is to collect network information, security event information, and log information from the 5G system structure, create a response security policy through various security analyses, and apply it to the 5G system structure in real-time.</t>

    <figure anchor="nnmsdaf-fig1" title="5G Service Based Architecture "> <artwork align="center">

 +-----+     +---+    +---+   +---+   +---+   +---+
   NSSF       NEF      NRF     PCF     UDM      AF
 +-----+     +---+    +---+   +---+   +---+   +---+
    |Nnssf     |Nnef   |Nnrf    |Npef    |Nudm   |Naf
-------------------------------------------------------
                 |Nausf         |Namf         |Nsmf   
               +------+      +-----+       +-----+
                 AUSF          AMF           SMF
               +------+      +-----+       +-----+
                               |              |
                      ------------          ------
                   N1|         N2|           N4|
                     +---+     +------+      +----+      +---+
                      UE  ----  (R)AN  -N3-   UPF  -N6-   DN
                     +---+     +------+      +----+      +---+  

         </artwork>
         <postamble></postamble>
        </figure>

        <t>SDAF interacts with other NFs through the SBI interface as shown in (Fig1). At this time, SDAF collects security-related data in response to the consumer NF's security analysis service request, uses it to perform security analysis, and derives the results. SDAF's core functions include security data collection, security analysis, and security policy creation and enforcement.</t>

     <figure anchor="nnmsdaf-fig2" title="SDAF Application Position in the 5G SBA Structure"> <artwork align="center">

 +-----+     +---+    +---+   +---+   +------+ 
   NDAF       NRF      UDM      AF      NWDAF
 +-----+     +---+    +---+   +---+   +------+ 
    |Nsdaf     |Nnrf   |Nudm    |Naf     |Nnwdaf   
----------------------------------------------------
        |Npcf       |Namf      |Nsmf    |Nudr   
      +-----+    +----+     +----+   +----+
        PCF       AMF        SMF       UDR
      +-----+    +----+     +----+   +----+
                   |            |
        ------------          
     N1|         N2|          N4|
     +---+     +-----+      +----+      +---+
       UE  ---   gNB   -N3-   UPF  -N6-   DN
     +---+     +-----+      +----+      +---+  


         </artwork>
         <postamble></postamble>
        </figure>

        <t>Security data collection is a function of collecting security data information from NFs connected to SBA structures such as AMF, SMF, PCF, UPF, etc. The security analysis function analyzes correlations based on collected security data (logs, security events, etc.) to detect specific patterns or anomalies and identify potential security threats. The security policy creation and enforcement function generate policies through the security analysis function by defining response methods for specific security events or behaviors. For example, it can automatically block or send warnings when a specific type of attack is detected and enforce these policies accordingly.</t>
        </section>
          
      <section title="SBI Interface Standard">
      <t>SDAF follows the SBI API Design Guide TS 29.501 (5G System; Principles and Guidelines for Services Definition) standard and defines Nsdaf as a communication interface name for interworking with other NFs.</t>

        <section title="Service Consumer and Service Producer Structure">
        <t>The SBI communication service uses a service producer and service consumer model. A service producer plays a role in providing a specific service among NFs within the SBA structure. A service consumer, on the other hand, can be any NF that utilizes or requests a specific service provided by the service producer. As depicted in Fig 3, SDAF can function as a service producer that provides security analysis services or as a service consumer that utilizes services from other NFs.</t>

     <figure anchor="nnmsdaf-fig3" title="Service Procedure for SDAF and NFs "> <artwork align="center">

 SDAF                any NF           SDAF                any NF     
--------           ---------         ---------           ---------
Service             Service           Service             Service
Producer  --Nsdaf-- Consumer          Consumer  --Nnf--  Producer
--------           ---------         ---------           ---------

          .......                              .......
          .  a  .                              .  b  .
          .......                              .......


         </artwork>
         <postamble></postamble>
        </figure>

        <t>SDAF message transmission and reception methods provide two methods (a. Request/Response method and b. Subscribe/Notify method) depending on the purpose of using the SDAF service (Fig 4). The request/response method is a synchronized communication method used for one-off service provision and utilization. In contrast, the subscription/notification method is an asynchronous communication method. When a service consumer subscribes to a specific service, the service producer sends notifications or updates asynchronously.</t>

     <figure anchor="nnmsdaf-fig4" title="Purpose of SDAF Service (a. Request/Response, b. Subscribe/Notify) "> <artwork align="center">

------------                            --------------
 NF Service   ---Request/Response--->      NF Service
  Consumer    ---Subscribe/Norify--->       Producer
------------                            --------------


         </artwork>
         <postamble></postamble>
        </figure>
    
        </section>
      </section>
    </section>

  <section title="SDAF Security Analysis Service and Communication Interface">
    <section title="SDAF Security Data Collection Function">
      <section title="Security Data Collection Service">
      <t>The security data collection function involves SDAF gathering data potentially utilized for security analysis from other NFs. SDAF may collect two types of data: general data and security data. General data collection involves gathering event data from NFs within the SBA, following the guidelines of 3GPP TS 23.502. In the data collection function, the producer NF is the NFs that provides data, and the SDAF operates as the consumer NF. The security data type is a function of collecting the security data of each NF. For example, network data (PCAP, flow information, etc.) of the NF, system logs, and security equipment detection logs may be collected.</t>
      </section>

      <section title="Request/Response Communication Interface">
      <t>In the request/response method, the service operation name of SDAF is defined as "Nsdaf_DataExposure". The service operations for collecting security data include IDS LogTransfer, NF log data transfer, and network packet data transfer.</t>
      </section>
    </section>

   <section title="SDAF Security Data Analysis Feature">
     <section title="Security Data Analysis Service">
     <t>The security analysis function provides various security analysis services requested by other NFs while SDAF acts as a service producer. SDAF's analysis-enabled services include SIEM analysis, AI analysis, and CTI analysis services. The SIEM analysis service is a service that monitors and analyzes security events and log data collected from NFs, manages logs, and determines whether there is a security threat. The AI analysis service performs security analysis using a machine learning model to identify and assess potential security threats. The CTI analysis function is a function of analyzing CTI such as malicious IP and malicious URLs and determining whether there is a security threat because it has a database that stores information on security threats (malicious IP, etc.). The three detailed functions of the security analysis function operate through the services provided by SDAF. SDAF acts as the producer NF, while the NF receiving the security analysis result serves as the consumer NF. The services utilized by SDAF are categorized according to their specific functions, and these functions operate via either request/response or subscription/notification methods. </t>
     </section>

    <section title="Subscription/Notify Communication Interface">
      <t>TBD</t>
      </section>
    </section>

    <section title="SDAF security policy creation and enforcement">
      <section title="Security Policy Creation and Implementation Service">
      <t>SDAF's security policy creation and enforcement function involve creating and implementing policies to respond to security threats. This function operates based on the security analysis results derived from the security analysis function. In the security policy creation and enforcement function, the producer NF is SDAF, which creates the security policy, while the consumer NF is the NF responsible for implementing the security policy. This function operates through request/response or subscription/notification methods.</t>
      </section>

    <section title="Subscribe/Notify Bunk Communication Interface">
      <t>TBD</t>
      </section>

    </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>

  <section title="Acknowledgements">
   	<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='TS 23.501'>
        <front>
            <title>System architecture for the 5G System (5GS)</title>
            <author></author>
            <date month='' year='2022' />
        </front>
        </reference>

	<reference anchor='TS 23.288'>
        <front>
            <title>Architecture enhancements for 5G System (5GS) to support network data analytics services</title>
            <author></author>
            <date month='' year='2022' />
        </front>
        </reference>

	<reference anchor='TS 29.508'>
        <front>
            <title>Access and Mobility Management Services</title>
            <author></author>
            <date month='' year='2022' />
        </front>
        </reference>

	<reference anchor='TS 29.510'>
        <front>
            <title>Network Function Repository Services</title>
            <author></author>
            <date month='' year='2022' />
        </front>
        </reference>

	<reference anchor='TS 29.518'>
        <front>
            <title>Access and Mobility Management Services</title>
            <author></author>
            <date month='' year='2022' />
        </front>
        </reference>

	<reference anchor='TS 29.520'>
        <front>
            <title>Network Data Analytics Services</title>
            <author></author>
            <date month='' year='2022' />
        </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='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='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>

 </references>

</back>
</rfc>
