Internet-Draft | IBN Network Management Automation | November 2023 |
Jeong, et al. | Expires 9 May 2024 | [Page] |
This document describes Network Management Automation (NMA) of cellular network services in 5G networks. For NMA, it proposes a framework empowered with Intent-Based Networking (IBN). The NMA in this document deals with a closed-loop network control, network intent translator, and network management audit. To support these three features in NMA, it specifies an architectural framework with system components and interfaces. Also, this framework can support the use cases of NMA in 5G networks such as the data aggregation of Internet of Things (IoT) devices, network slicing, and the Quality of Service (QoS) in Vehicle-to-Everything (V2X).¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 9 May 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
5G networks are evolutionary mobile networks over 4G networks in terms of high speed, wide bandwidth, high frequency bands, massive device connectivity, low energy consumption, and intelligence. Especially, the intelligence will be a key feature to understand the intents of users and automate network management fully. 5G networks are designed and implemented on the experience from 4G networks and new technologies which include Software-Defined Networking (SDN) [RFC7149] and Network Functions Virtualization (NFV) [ETSI-NFV][ETSI-NFV-Release-2] along with mmWave for low delivery delay, high data speed, and large network capacity [TS-23.501].¶
The support of network intelligence is one of the main goals of 5G networks. The network intelligence can provide the 5G networks with Network Management Automation (NMA) for a self-driving network that optimizes and adjusts itself by minimizing the interaction with humans (e.g., network administrators and users).¶
Intent-Based Networking (IBN) is a feasible approach that can provide the 5G networks with the NMA services [RFC9315] [TS-28.312][TR-28.812]. The concept of IBN enables a closed-loop network control architecture [RFC9315] that can adapt to the current status of a target network by collecting and analyzing monitoring data from Network Service Functions (NSFs). NSFs can be either Virtual Network Functions (VNFs), Cloud-Native Network Functions (CNFs) or Physical Network Functions (PNFs) in cloud and edge computing environments. In the 3rd Generation Partnership Project (3GPP), Network Data Analytics Function (NWDAF) is defined to collect and analyze monitoring data from multiple VNFs and PNFs in cellular networks [TS-23.288][TS-29.520].¶
For the intelligent NMA services, this document proposes an architectural framework that combines the IBN and NWDAF to the 5G networks with Artificial Intelligence (AI) and Machine Learning (ML). The framework allows a network intent from either a network operator or user, which is expressed in the form in [TS-28.312], to be translated into a network policy by a Network Intent Translator (NIT) [I-D.yang-i2nsf-security-policy-translation]. A Natural Language Processing (NLP) technique can be used to design and implementation of such an NIT [USENIX-ATC-Lumi]. For the intent translation, the data model mapping between a network indent data model and a network policy needs to be performed by a data model mapper in advance [I-D.yang-i2nsf-security-policy-translation]. The translated network policy can be used to remotely configure NSFs running on top of VNFs, CNFs or PNFs in order to enforce the commanded intent in a target network (e.g., 5G Networks). Also, it also collects and analyzes the monitoring data from VNFs, CNFs and PNFs such that the network policy can be verified and optimized to satisfy the requests for the network intent.¶
Therefore, the NMA in this document deals with closed-loop network control, network intent translator, and network management audit. To support these three features in NMA, it specifies an architectural framework with system components and interfaces. In addition, this framework can support the use cases of NMA in 5G networks such as the data aggregation of Internet of Things (IoT) devices, network slicing, and the Quality of Service (QoS) in Vehicle-to-Everything (V2X). Especially, this document shows a use case of IoT in 5G networks such as the data collection and analysis of IoT devices.¶
This document uses the terminology described in [RFC8329], [I-D.ietf-i2nsf-applicability], and [I-D.jeong-i2nsf-security-management-automation]. In addition, the following terms are defined below:¶
Intent: A set of operational goals (that a network should meet) and outcomes (that a network is supposed to deliver) defined in a declarative manner without specifying how to achieve or implement them [RFC9315].¶
Network Management Automation (NMA): It enforces a network intent from a user (or administrator) into a target network system. The network intent can be translated into the corresponding network policy by a network intent translator (NIT) and dispatched to appropriate NSFs. Through the monitoring of the NSFs, the activity and performace of the NSFs is monitored and analyzed. If needed, the network rules of the network policy are augmented or new network rules are generated and configured to appropriate NSFs.¶
Network Intent Translator (NIT): It translates a network intent to a network policy that can be understood and configured by an NSF for a specific network service, such as the data aggregation of Internet of Things (IoT) devices, network slicing, and the Quality of Service (QoS) provisioning in Vehicle-to-Everything (V2X) communications.¶
Feedback-Based Network Management (FNM): It means that a network service is evolved by updating a network policy (having network rules) and adding new network rules for detected network problems by processing and analzing the monitoring data of NSFs.¶
This section describes an IBN framework for 5G networks. Note that this IBN Framework is based on the Framework for Interface to Network Security Functions (I2NSF) [RFC8329][I-D.jeong-i2nsf-security-management-automation]. As shown in Figure 1, an IBN User can use network functions by delivering network intents, which specify network requirements and goals that the IBN User wants to enforce, to the IBN Controller via the Consumer-Facing Interface (CFI).¶
The following are the system components for the IBN framework for network management automation in 5G networks.¶
IBN User: An entity that delivers a network intent to IBN Controller. It is assumed that a network intent is constructed by the intent data model in the 3GPP intent document [TS-28.312].¶
IBN Controller: An entity that controls and manages other system components in the IBN framework. It translates a network intent into the corresponding network policy and selects appropriate NSFs to execute the network rules of the network policy.¶
Vendor's Management System (VMS): An entity that provides an image of of a virtualized NSF for a network service to the IBN framework, and registers the capability and access information of an NSF with IBN Controller.¶
Network Service Function (NSF): An entity that is a Virtual Network Function (called VNF), Cloud-Native Network Function (CNF), and Physical Network Function (called PNF) which is also called Cloud-native Network Function, for a specific network service such as the data aggregation of IoT devices, network slicing, and the QoS provisioning in V2X communications.¶
IBN Analyzer: An entity that collects monitoring data from NSFs and analyzes such data for checking the activity and performance of the NSFs using machine learning techniques (e.g., Deep Learning [Deep-Learning]). IBN Analyzer can be a Network Data Analytics Function (NWDAF) in 5G networks [TS-23.288][TS-29.520]. If there is a suspicious network problem (e.g., traffic congestion and QoS degradation) for the target network or NSF, IBN Analyzer delivers a report of the augmentation or generation of network rules to IBN Controller.¶
For IBN-based network services with Feedback-Based Network Management (FNM), IBN Analyzer is a key IBN component for the IBN framework [RFC9315] to collect monitoring data from NSFs and analyzing the monitoring data. The actual implementation of the analysis of monitoring data is out of the scope of this document.¶
The following are the interfaces for the IBN framework. Note that the interfaces can be modeled with YANG [RFC6020] or YAML [YAML] and network policies are delivered through either RESTCONF [RFC8040] or NETCONF [RFC6241]. In addition, according to 3GPP specifications, REST API [REST] can be supported for those interfaces.¶
Consumer-Facing Interface: An interface between IBN User and IBN Controller for the delivery of a network intent [I-D.ietf-i2nsf-consumer-facing-interface-dm].¶
NSF-Facing Interface: An interface between IBN Controller and an NSF (e.g., Network Exposure Function (NEF) in 5G Core Network) for the delivery of a network policy [I-D.ietf-i2nsf-nsf-facing-interface-dm].¶
Registration Interface: An interface between a VMS and IBN Controller for the registration of an NSF's capability and access information with the IBN Controller or the query of an NSF for a required low-level network policy [I-D.ietf-i2nsf-registration-interface-dm].¶
Monitoring Interface: An interface between an NSF and IBN Analyzer for collecting monitoring data from an NSF to check the activity and performance of an NSF for a possible network problem [I-D.ietf-i2nsf-nsf-monitoring-data-model].¶
Analytics Interface: An interface between IBN Analyzer and IBN Controller for the delivery of an analytics report of the augmentation or generation of network rules to IBN Controller, which lets IBN Controller apply the report for network rules to its network policy management.¶
For IBN-based network services with FSM, Analytics Interface is a key interface in the IBN framework to deliver an analytics report of the augmentation or generation of network rules to IBN Controller through the analysis of the monitoring data from NSFs.¶
To facilitate Network Intent Translation, IBN Controller needs to have a Network Intent Translator (NIT) that performs the translation of a network intent (called intent) into the corresponding network policy (called policy). For the automatic NIT services, the IBN framework needs to bridge an intent data model and a policy data model in an automatic manner [I-D.yang-i2nsf-security-policy-translation]. Note that an intent data model is for the IBN Consumer-Facing Interface, and a policy data model is for the IBN NSF-Facing Interface.¶
Figure 2 shows automatic mapping of intent and policy data models for network policies. Automatic Data Model Mapper takes an intent data module for the Consumer-Facing Inteface and a policy data module for the NSF-Facing Interface. It then constructs a mapping table associating the data attributes (or variables) of the intent data module with the corresponding data attributes (or variables) of the policy data module. Also, it generates a set of production rules of the grammar for the construction of an XML (or JSON) file of network policy rules.¶
Figure 3 shows the procedure of network intent translation. A network policy translator is a component of IBN Controller. The translator consists of three components such as Data Model Mapper, Policy Data Extractor, Policy Data Converter, and Policy Generator.¶
Data Model Mapper maps the attributes and their values of a network intent to the corresponding attributes and their values of a network policy. Note that the values of a network intent may involve a human language and must be converted to an appropriate value for a network policy (e.g., employees -> 192.0.1.0/24).¶
Data Extractor extracts the values of the attributes related to the network intent that was delivered by an IBN User to an IBN Controller through the Consumer-Facing Interface [I-D.ietf-i2nsf-consumer-facing-interface-dm].¶
Data Converter converts the values of the network intent's attributes into the values of the corresponding network policy's attributes to generate the network policy [I-D.ietf-i2nsf-nsf-facing-interface-dm].¶
Policy Generator generates the corresponding network policy that is delivered by the IBN Controller to an appropriate NSF through NSF-Facing Interface [I-D.ietf-i2nsf-nsf-facing-interface-dm].¶
The IBN framework is weak to both an insider attack and a supply chain attack since it trusts in NSFs provided by VMS and assumes that NSFs work for their network services appropriately [I-D.ietf-i2nsf-applicability].¶
To detect the malicious activity of either an insider attack by a malicious VMS or a supply chain attack by a compromised VMS, a network audit system is required by the IBN framework. This network audit system can facilitate the non-repudiation of configuration commands and monitoring data generated in the IBN framework.¶
A network audit system has the following four main objectives:¶
To check the existence of a network policy, a management system, and its procedures;¶
To identify and understand the existing vulnerabilities and risks of either an insider attack or a supply chain attack;¶
To review existing network controls on operational and administrative issues;¶
To provide recommendations and corrective actions to IBN Controller for further network and security improvement.¶
Figure 4 shows activity auditing with a network audit system in the IBN framework. All the components in the IBN framwork report its activities (such as configuration commands and monitoring data) to Network Audit System as transactions through Remote Attestation Interface [I-D.yang-i2nsf-remote-attestation-interface-dm]. The network audit system can analyze the reported activities from the IBN components to detect malicious activities such as an insider attack and a supply chain attack. Note that such a network audit system can be implemented by remote attestation [I-D.ietf-rats-architecture][I-D.yang-i2nsf-remote-attestation-interface-dm] or Blockchain [Bitcoin]. The details of the implementation of the network audit system are out of the scope of this document.¶
In order to determine a minimum set of controls required to reduce the risks from either an insider attack or a supply chain attack, the network audit system should analyze the activities of all the components in the IBN framework periodically, evaluate possible risks, and take an action to such risks since vulnerabilities and threats may change in different environments over time.¶
This section describes a use case where a policy of IoT device data aggregation is set up in the IBN framework for 5G networks.¶
Figure 5 shows the procedure of the enforcement for an IoT device data aggregation intent in the IBN Framework as follows:¶
IBN User sends a Network Intent Request to IBN Controller.¶
IBN Controller translates the request with its Network Intent Translator (called NIT). The NIT identifies NSFs (i.e., IoT Devices) for the request after the steps of Data Extraction and Data Conversion.¶
If the NSFs are available for the requested network policy, go to the step of Policy Generation in NIT. If the NSFs are unavailable for the requested network policy, go to the next step.¶
IBN Controller sends an NSF Query Request to Vendor's Management System (called VMS) to find an appropriate NSF for the request network policy.¶
If there is such an NSF registered with VMS, VMS sends an NSF Initializtion Request to Cloud (or Edge Server) to initialize the NSF.¶
Cloud (or Edge Server) forwards the NSF Initializtion Request to the appropriate NSF to let it initialize itself.¶
The NSF performs an initialization to perform a task for a network policy in 5G networks.¶
The NSF sends an NSF Initialization Response to Cloud (or Edge Server) to tell Cloud (or Edge Server) its readiness to perform a task.¶
Cloud (or Edge Server) forwards the NSF Initialization Response to VMS to tell an NSF's readiness to perform a task.¶
VMS sends an NSF Query Response to IBN Controller to tell an NSF's readiness to perform a task along with the network access information for the NSF.¶
IBN Controller performs the step of Policy Generation in its NIT along with the network access information of an appropriate NSF(s).¶
IBN Controller sends a Network Policy Request to the appropriate NSF.¶
The NSF performs the configration in the given Network Policy Request to perform the requested task (e.g., sensing and reporting).¶
The NSF sends a Network Policy Response to IBN Controller to tell its readiness to perform the requested task.¶
Figure 6 shows the procedure of the reporting for IoT device data aggregation in the IBN Framework as follows:¶
NSF1 (as an IoT Device) sends its Sensing Data to IBN Analyzer (as an NWDAF).¶
NSF2 (as an IoT Device) sends its Sensing Data to IBN Analyzer (as an NWDAF).¶
IBN Analyzer performs Sensing Data Aggregation and analyzes the aggregated sensing data through Machine Learning (ML) techniques. It then generates a Sensing Report for IBN Controller.¶
IBN Analyzer sends a Sensing Report to IBN Controller.¶
IBN Controller analyzes the Sensing Report for a further action. If a further action is needed, it updates the existing network policy or generates a new network policy.¶
IBN Controller sends the report for the further action to IBN User optionally if the reporting is needed.¶
For the further action, IBN Controller sends an Updated NSF Policy Request or a New NSF Policy Request to the appropriate NSF(s).¶
The appropriate NSF(s) reconfigures the Updated NSF Policy or configures the new NSF Policy in its own system.¶
The appropriate NSF(s) sends an Updated NSF Policy Response or a NEW NSF Policy Response to IBN Controller.¶
This document does not require any IANA actions.¶
The same security considerations for the IBN framework [RFC8329] are applicable to this document.¶
The development and introduction of IBN Analyzer and Network Audit System in the IBN Framework may create new security concerns that have to be anticipated at the design and specification time. The usage of machine learning to analyze monitoring data of malicious NSFs may add a risk to its model to be attacked (e.g., adversarial attack) and can result in a bad security policy that is deployed into the IBN system.¶
This work was supported in part by Institute of Information & Communications Technology Planning & Evaluation (IITP) grant funded by the Korea Ministry of Science and ICT (MSIT)(No. 2022-0-01015, Development of Candidate Element Technology for Intelligent 6G Mobile Core Network).¶
This work was supported in part by Institute of Information & Communications Technology Planning & Evaluation (IITP) grant funded by the Korea Ministry of Science and ICT (MSIT) (No. 2022-0-01199, Regional strategic industry convergence security core talent training business).¶
This document is made by the group effort of NMRG, greatly benefiting from inputs and texts by Linda Dunbar (Futurewei) and Susan Hares (Huawei). The authors sincerely appreciate their contributions.¶
The following are coauthors of this document:¶
The following changes are made from draft-jeong-nmrg-ibn-network-management-automation-02:¶