Internet-Draft Network Working Group March 2023
Chen, et al. Expires 14 September 2023 [Page]
Workgroup:
Internet Research Task Force
Internet-Draft:
draft-chen-nmrg-ibn-management-00
Published:
Intended Status:
Informational
Expires:
Authors:
D. Chen
China Mobile
K. Yao
China Mobile
C. Yang
Xidian University
X. Mi
Xidian University
Y. Ouyang
Xidian University

Network Management Intent -One of IBN Use Cases

Abstract

Full life cycle network management will be a key feature of the future communication networks. Meanwhile, the complexity of the network management should be reduced and the network expects to be managed in a fully automated manner with humans out of the loop. In this document, we propose an use case of intent based network management to achieve more flexible , convenient, and efficient network management. In this use case, we propose an architecture and attempt to illustrate the five levels of achieving full autonomous network management.

Requirements Language

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 RFC 2119 [RFC2119].

Status of This Memo

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 14 September 2023.

Table of Contents

1. Introduction

With the rapid evolution of networks, such as the emergence of the sixth generation (6G), we have entered a new digital era that is ubiquitously connected by highly heterogeneous and dynamic network infrastructure. And various network applications are predicted to appear more in future communication networks. With these complex network scenarios, services, and uncountable degrees of freedom in future communication networks, the complexity of network management will increase drastically. Traditional network management methods are insufficient to keep up with the growing requirements. Firstly, there exists high complexity and difficulty to manage a large amount of infrastructures due to high labor cost, high error probability, low management efficiency. Secondly, traditional network management lacks closed-loop control, which can not find and repair faults in time. To overcome these challenges, some novel network models have been proposed, such as NFV and SDN. However, it still faces many novel challenges:

At the same time, with the exponential growth of network devices, network administrators need to put in tremendous effort to manage the policies that affect the services of these devices. While in recent years the network management methods have been gradually automated, there are still many procedures that must be accomplished under the strict supervision of administrators, resulting in high error probability. Moreover, current network management is at a level too low to entirely eliminate the requirements to customize each solution for a specific device or protocol in use. The emergence of the IBN, as defined in RFC 9315 [RFC9315], has the potential to compensate for the limitations of the current network management methods. The intent is a high-level abstraction of policy, and the IBN is a way to manage the network through intent-driven rather than a low-level configuration. When the user specifies a high-level goal (intent), the network automatically converts that goal into policies and automatically deploys these policies throughout the network.

2. Definitions and Acronyms

IBN: Intent based network

IBNM: Intent based network management

DQN: Deep Q network

3. Overview

Driven by the above requirements and challenges, the intent based network management (IBNM) is proposed. IBNM aims to transition from a fully static manual network management to a fully dynamic autonomous intent based network management. In IBNM, users express their service requirements or goals in a declarative manner without paying attention to how the network achieves them.

The architecture is shown as Fig 1, which includes the application layer, the intent-enabled layer and the infrastructure layer. The application layer collects intents from various users and applications, and provides a number of programmable network management services. The intent-enabled layer consists of the intent translation module, intelligent policy mapping module, and intent guarantee module, whose functions are to build a bridge between the application layer and the infrastructure layer. Heterogeneous physical devices are deployed in the infrastructure layer. This layer can execute management instructions from the intent-enabled layer and upload underlying network situation information to the intent-enabled layer. Information interaction between different layers is done through different interfaces, such as the northbound and southbound interfaces.

  +----------------------------------------+
  |          Application   Layer           |
  +-------------+---------^----------------+
Intent Ingestion|         | Northbound Interface
  +-------------+---------v----------------+
  |             |      Intent-enabled Layer|
  | +-----------+-------+  +-------------+ |
  | |           |       |  |             | |
  | |  +--------v----+  |  |             | |
  | |  | Translation |  |  |             | |
  | |  +-------------+  |  |             | |
  | |                   |  | Intelligent | |
  | |  +-------------+  |  |             | |
  | |  | Verification|  |  |  Guarantee  | |
  | |  +-------------+  |  |             | |
  | |Intent Translation |  |    Module   | |
  | |      Module       |  |             | |
  | +-------------------+  |             | |
  |                        |             | |
  | +-------------------+  |             | |
  | |Intelligent Policy |  |             | |
  | |  Mapping Module   |  |             | |
  | +-------------------+  +-------------+ |
  |                                        |
  +--------------------^-------------------+
                       |  Southbound Interface
  +--------------------v-------------------+
  |         Infrastructure Layer           |
  +----------------------------------------+
Figure 1: The Architecture of IBNM

Among these layers, the intent-enabled layer is the core of this network management architecture. First, the intent translation module translates declarative intent (expressed in the form of natural language) into the network intent that can be recognized by the system (specific ). There may be an intent conflict problem when multiple intents are input simultaneously. Thus, the intent translation module executes intent verification and intent conflict resolution before the intent is issued (measurable). Second, the intelligent policy mapping module provides customized policies (achievable) for specific intents according to various requirements and evaluates the current policy by rewarding values. After that, in order to complete the policy configuration within the time-bound, the intent guarantee module is needed to execute feature extraction and location on the collected alarm information. Then the fault information is fed back to the intelligent policy mapping module.

Based on the above design, on one hand, this architecture can achieve full lifecycle automated network management with humans out of the loop. On the other hand, it converts service requirements (intent) into network policies and provides self-adapted customized service with a full lifecycle verification. The functions of each module in intent-enabled layer are described below.

4. Advantages

The advantages of the intent based network management include:

5. Concrete Example

TBD

6. Automated Network Management Tiers

TBD

7. Security Considerations

TBD

8. IANA Considerations

This document has no requests to IANA.

9. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC9315]
Clemm, A., Ciavaglia, L., Granville, L. Z., and J. Tantsura, "Intent-Based Networking - Concepts and Definitions", RFC 9315, DOI 10.17487/RFC9315, , <https://www.rfc-editor.org/info/rfc9315>.

Authors' Addresses

Danyang Chen
China Mobile
Beijing
100053
China
Kehan Yao
China Mobile
Beijing
100053
China
Chungang Yang
Xidian University
Xi'an
710071
China
Xinru Mi
Xidian University
Xi'an
710071
China
Ying Ouyang
Xidian University
Xi'an
710071
China