End-to-end intent definition of network functions for network slice management
Described are examples for providing end-to-end intent definition of network functions for network slice management. Intents are defined for each level of network constituent including slices, slice subnets, and management functions. A system of intent based network slice management includes a network slice management function (NSMF) configured to receive a service profile from a communication service management function (CSMF) and derive an intent for each desired network slice subnet for a network slice subnet management function (NSSMF). The NSSMF is configured to derive requirements for a plurality of network functions (NFs) and provide an intent defining the requirements of a respective NF to a network function management function (NFMF). The NFMF is configured to receive the intent for the respective NF via an intent-based interface for management of NFs and derive a network resource model (NRM) for the respective NF based on the intent.
1 . A method of intent based network slice management, comprising:
receiving an intent for a respective network function (NF) via an intent-based interface for management of NFs, the intent for the network function including limited information defining requirements of the NF;
deriving a network resource model (NRM) for the respective NF based on the intent for the respective NF, wherein the NRM defines information object classes (IOCs) for expected performance of the respective NF and IOCs for a configuration of the respective NF; and
translating the NRM for the respective NF to a NF vendor-specific interface by a convergence agent for one of a plurality of NF vendors, wherein the convergence agent is configured to:
convert the NRM to one or more vendor-specific configuration messages; and
provide the one or more vendor-specific configuration messages to the respective NF via the NF vendor-specific interface.
2 . The method of claim 1 , wherein the limited information is a partial list of attributes of the NRM that define information object classes (IOC) for expected performance of the respective NF.
3 . The method of claim 2 , wherein deriving the NRM comprises deriving an NF profile specifying configuration of the respective NF based on the partial list of attributes of the NRM.
4 . The method of claim 3 , wherein deriving the NRM comprises refining the partial list of attributes of the NRM using one or more of: local policy, metadata, pluggable logic, or hard coded logic.
5 . The method of claim 1 , wherein the requirements for the plurality of NFs include a number and a type of each of the plurality of NFs.
6 . The method of claim 1 , wherein the NF vendor-specific interface is a cloud infrastructure service management system interface or a container infrastructure service management system interface.
7 . A system of intent based network slice management, comprising:
one or more memories, individually or in combination, having computer-executable instructions stored thereon; and
one or more processors, individually or in combination, configured to execute the computer-executable instructions to instantiate:
a network function management function (NFMF) configured to:
receive an intent for a respective network function (NF) via an intent-based interface for management of NFs, the intent for the network function including limited information defining requirements of the NF; and
derive a network resource model (NRM) for the respective NF based on the intent, wherein the NRM defines information object classes (IOCs) for expected performance of the respective NF and IOCs for a configuration of the respective NF; and
define a convergence agent for each of a plurality of NF vendors, each convergence agent configured to translate the NRM for the NF to a NF vendor-specific interface, wherein the convergence agent is configured to:
convert the NRM to one or more vendor-specific configuration messages; and
provide the one or more vendor-specific configuration messages to the respective NF via the NF vendor-specific interface.
8 . The system of claim 7 , wherein the limited information is a partial list of attributes of the NRM that define information object classes (IOCs) for expected performance of the respective NF.
9 . The system of claim 8 , wherein the NFMF is configured to derive an NF profile specifying configuration of the respective NF based on the partial list of attributes of the NRM.
10 . The system of claim 8 , wherein the NFMF is configured to refine the partial list of attributes of the NRM using one or more of: local policy, metadata, pluggable logic, or hard coded logic.
11 . The system of claim 7 , wherein the requirements for the plurality of NFs include a number and a type of each of the plurality of NFs.
12 . The system of claim 7 , wherein the NF vendor-specific interface is a cloud infrastructure service management system interface or a container infrastructure service management system interface.
13 . A non-transitory computer-readable medium storing computer-executable code, comprising code to:
receive an intent for a network function (NF) via an intent-based interface for management of NFs, the intent for the network function including limited information defining requirements of the NF;
derive a network resource model (NRM) for the NF based on the intent, wherein the NRM defines information object classes (IOCs) for expected performance of the respective NF and IOCs for a configuration of the respective NF; and
define a convergence agent for each of a plurality of NF vendors, each convergence agent configured to translate the NRM for the NF to a NF vendor-specific interface, wherein the convergence agent is configured to:
convert the NRM to one or more vendor-specific configuration messages; and
provide the one or more vendor-specific configuration messages to the NF via the NF vendor-specific interface.
14 . The non-transitory computer-readable medium of claim 13 , wherein the limited information is a partial list of attributes of the NRM that define information object classes (IOC) for expected performance of the NF.
15 . The non-transitory computer-readable medium of claim 14 , wherein the code to derive the NRM comprises code to derive a network function profile specifying configuration of the network function based on the partial list of attributes of the NRM.
16 . The non-transitory computer-readable medium of claim 14 , wherein the code to derive the NRM comprises code to refine the partial list of attributes of the NRM using one or more of: local policy, metadata, pluggable logic, or hard coded logic.
17 . The non-transitory computer-readable medium of claim 13 , wherein the NF vendor-specific interface is a cloud infrastructure service management system interface or a container infrastructure service management system interface.