WO2017185303A1 - 一种nfv mano策略描述符的管理方法及装置 - Google Patents

一种nfv mano策略描述符的管理方法及装置 Download PDF

Info

Publication number
WO2017185303A1
WO2017185303A1 PCT/CN2016/080516 CN2016080516W WO2017185303A1 WO 2017185303 A1 WO2017185303 A1 WO 2017185303A1 CN 2016080516 W CN2016080516 W CN 2016080516W WO 2017185303 A1 WO2017185303 A1 WO 2017185303A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
nfv mano
policy rule
descriptor file
rule
Prior art date
Application number
PCT/CN2016/080516
Other languages
English (en)
French (fr)
Inventor
夏海涛
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201680071472.3A priority Critical patent/CN108370328B/zh
Priority to PCT/CN2016/080516 priority patent/WO2017185303A1/zh
Priority to EP16899816.9A priority patent/EP3419216A4/en
Publication of WO2017185303A1 publication Critical patent/WO2017185303A1/zh
Priority to US16/168,512 priority patent/US10601666B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for managing an NFV MANO policy descriptor.
  • Network Function Virtualization is a telecommunications network operator that implements some telecommunications network functions in general-purpose cloud servers, switches, and storage by drawing on virtualization technologies in the IT field. This technology requires telecom network functions to be implemented in software and run on general-purpose server hardware, which can be migrated, instantiated, deployed in different locations on the network as needed, and does not require new equipment to be installed.
  • NFV MANO NFV MANagement and Orchestration
  • the network service is carried in a Network Service Descriptor (NSD) or a Virtualised Network Function Descriptor (VNFD).
  • NS Network Service
  • VNF Virtualized Network Function
  • the application of the NFV MANO strategy is based on the assumption that the policies are separated from each other and there is no policy association.
  • the invention provides a method and a device for managing an NFV MANO policy descriptor, which are proposed by the present invention.
  • the method and the device are provided to solve the problem that the MANO system in the prior art needs to create and maintain a large number of policy rules when facing a large number of NS instances or VNF instances for NFV MANO operations, thereby causing high cost of NFV MANO policy management.
  • a method for managing an NFV MANO policy descriptor including:
  • the policy rule execution entity receives the network function virtualization management and the orchestration NFV MANO operation request sent by the policy rule decision entity, where the NFV MANO operation request includes a policy parameter;
  • the policy rule execution entity acquires a policy descriptor file corresponding to the NFV MANO operation request, where the policy descriptor file includes at least one policy information corresponding to the NFV MANO operation request;
  • the policy rule execution entity configures the policy parameter into the policy information to form a policy rule.
  • the policy rule execution entity obtains a policy descriptor file corresponding to the NFV MANO operation request, and performs a signaling interaction between the policy rule execution entity and the policy rule decision entity, and the policy rule execution entity configures the policy parameter in the operation request. Forming policy rules into the policy information, avoiding maintenance of a large number of NFV MANO policies, and improving the efficiency of NFV MANO policy management.
  • the policy information includes at least one of an event monitored by a policy rule, a condition for executing a policy rule, and an action performed by the policy rule.
  • the NFV MANO operation class is normalized by the event monitored by the policy rule, the condition of the policy rule execution, or the action performed by the policy rule, thereby implementing the classification management of the policy rule, and further improving the NFV MANO.
  • obtaining a policy descriptor file corresponding to the NFV MANO operation request includes:
  • the policy rule execution entity determines an operation attribute of the NFV MANO operation request
  • the policy rule execution entity obtains the policy descriptor file corresponding to the operation attribute from a catalog library or from a set of policy descriptor files stored by the policy rule execution entity.
  • obtaining a policy descriptor file corresponding to the NFV MANO operation request includes:
  • the policy rule execution entity obtains an identifier of the policy descriptor file from the NFV MANO operation request;
  • the policy rule execution entity obtains the policy descriptor file corresponding to the identifier of the policy descriptor file from a catalog library.
  • the second and third possible implementations of the first aspect provide two ways of obtaining a policy descriptor file, and the policy descriptor file template processing normalized according to the category of the NFV MANO operation can be implemented in two ways, thereby Implement classification management of policy rules to further improve the efficiency of NFV MANO policy management.
  • the policy rule execution entity configures the policy parameter into the policy information to form a policy
  • the rules further include:
  • the policy rule execution entity receives request information for updating the policy rule, where the request information includes an identifier of a policy descriptor file used by the policy rule and an updated policy parameter;
  • the policy rule execution entity acquires a policy descriptor file used by the policy rule according to the identifier of the policy descriptor file;
  • the policy rule enforcement entity configures the updated policy parameters into the policy descriptor file to form updated policy rules.
  • one or several policy rules in the policy descriptor file may be moved. Status updates, which simplifies the update management process for policy rules.
  • the NFV MANO operation request includes a network service NS lifecycle management, a virtualized network function VNF life Cycle management and virtual resource management, NS instantiation, NS update, NS elastic scaling, NS healing, NS termination, VNF instantiation, VNF update, VNF elastic scaling, VNF healing, VNF termination, virtual resource reservation, virtual resource allocation At least one of them.
  • the policy rule decision entity is an operation/service support system OSS/BSS;
  • the policy rule execution entity is a network function virtualization orchestrator NFVO or a network function virtualization manager VNFM or a virtualized infrastructure manager VIM.
  • a policy rule execution entity including: a communication interface and a processor,
  • the communication interface is configured to receive a network function virtualization management and an NFV MANO operation request sent by a policy rule decision entity, where the NFV MANO operation request includes a policy parameter;
  • the processor is configured to acquire a policy descriptor file corresponding to the NFV MANO operation request, where the policy descriptor file includes at least one policy information corresponding to the NFV MANO operation request, and the policy parameter is configured to A policy rule is formed in the policy information.
  • the policy information includes at least one of an event monitored by a policy rule, a condition executed by a policy rule, and an action performed by a policy rule.
  • the processor is specifically configured to determine an operation attribute of the NFV MANO operation request; and from a catalog in the catalog Or obtaining the policy descriptor file corresponding to the operation attribute from a set of policy descriptor files stored by the policy rule execution entity.
  • the processor is specifically configured to obtain an identifier of a policy descriptor file from the NFV MANO operation request, and obtain the policy descriptor corresponding to the identifier of the policy descriptor file from a catalog database file.
  • the processor is further configured to receive request information for updating the policy rule, where And the request information includes an identifier of the policy descriptor file used by the policy rule and an updated policy parameter; and acquiring a policy descriptor file used by the policy rule according to the identifier of the policy descriptor file; The updated policy parameters are configured into the policy descriptor file to form updated policy rules.
  • the NFV MANO operation request includes a network service NS lifecycle management, a virtualized network function VNF life Cycle management and virtual resource management, NS instantiation, NS update, NS elastic scaling, NS healing, NS termination, VNF instantiation, VNF update, VNF elastic scaling, VNF healing, VNF termination, virtual resource reservation, virtual resource allocation At least one of them.
  • the policy rule decision entity is an operation/service support system OSS/BSS.
  • a management system for an NFV MANO policy descriptor comprising a policy rule execution entity and a policy rule decision entity provided by any one of the possible implementations of the second aspect.
  • the policy rule execution entity is a network function virtualization orchestrator NFVO or a network function virtualization manager VNFM or a virtualization infrastructure manager VIM.
  • the policy rule decision entity is a policy management function entity PMF; wherein, the PMF is used Create, delete, and modify policy rules.
  • the PMF is located at an NFVO level or an OSS/BSS level.
  • the PMF is a separate manager or a manager having the same IP address as the NFVO.
  • system further includes a catalog catalog, the catalog saves the policy descriptor file.
  • a fourth aspect a computer readable storage medium storing program code for implementing the management method for an NFV MANO policy descriptor described in the first aspect, the program code including running first Aspects of the execution instructions for the management method of the NFV MANO policy descriptor.
  • the method and apparatus provided by the embodiments of the present invention process the policy descriptor file template normalized by the NFV MANO policy rule according to the category of the NFV MANO operation (that is, the policy corresponding to each class operation) Descriptor file), and in the network service or VNF lifecycle management process, the policy information in the policy descriptor file is filled by the specific parameter values carried by the interactive commands between the MANO management entities, forming a lifecycle management process.
  • the practical application of the policy rules to improve the efficiency of NFV MANO policy management.
  • FIG. 1 is a schematic structural diagram of a management system of an NFV MANO policy descriptor according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a policy rule execution entity according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for managing an NFV MANO policy descriptor according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of an on-board process of a policy descriptor file according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of a policy rule update process according to an embodiment of the present invention.
  • Embodiments of the present invention provide a management system for an NFV MANO policy descriptor.
  • the management system of the NFV MANO policy descriptor includes: an operation support system/business support system (OSS/BSS), and an element management system (EMS). ), Virtual Network Function (VNF), Network Function Virtualization Infrastructure (NFVI), and NFV-MIMO.
  • NFV MANO includes NFV Orchestrator (NFVO), Virtualized Network Function Manager (VNFM), Virtualized Infrastructure Manager (VIM), and policy management. Policy Management Function (PMF).
  • OSS/BSS is mainly for telecom service operators, providing comprehensive network management and service operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • network management such as fault monitoring, network information collection, etc.
  • billing management billing management
  • customer service management customer service management
  • EMS can be used to manage one or more VNFs, mainly performing traditional fault management, configuration management, billing management, performance management, and security management (Fault Management, Configuration) for VNF. Management, Accounting Management, Performance Management, Security Management, referred to as FCAPS).
  • FCAPS fault Management, Configuration
  • the VNF corresponds to a Physical Network Function (PNF) in a traditional non-virtualized network, such as a virtualized Evolved Packet Core (EPC) node.
  • the virtualized EPC nodes include: a Mobile Management Entity (MME), a Serving GateWay (SGW), and a Packet Data Network GateWay (PGW).
  • MME Mobile Management Entity
  • SGW Serving GateWay
  • PGW Packet Data Network GateWay
  • the functional behavior and state of the network are independent of whether the network is virtualized.
  • the VNF and PNF in the NFV system have the same functional behavior and external interfaces.
  • the virtualization layer in NFVI is used to abstract the hardware resources of the hardware resource layer, decouple the VNF from the physical layer to which the hardware resources belong, and provide virtual resources to the VNF.
  • the virtual resource layer can include virtual computing, virtual storage, and virtual networking.
  • Virtual computing, virtual storage can be provided to the VNF in the form of a virtual machine or other virtual container, such as one or more virtual machines forming a VNF.
  • the virtualization layer forms a virtual network by abstracting network hardware.
  • a virtual network is used to implement communication between multiple virtual machines, or between other types of virtual containers that host VNFs.
  • the virtual network can be created by virtual LAN (Vritual LAN, VLAN for short), Virtual Private LAN Service (VPLS), Virtual eXtensible Local Area Network (VxLAN), or general routing.
  • Technology implementation such as Nerwork Virtualization using Generic Routing Encapsulation (NVGRE).
  • NFVO Implements NSD, Virtualised Network Function Forwarding Graph (VNFFG) management and processing, network service lifecycle management, and cooperates with VNFM to implement VNF lifecycle management and resource global view functions.
  • VNFFG Virtualised Network Function Forwarding Graph
  • VNFM Realize lifecycle management of virtualized network element VNF, including management and office of VNFD The initialization of the VNF instance, the expansion/reduction of the VNF, and the termination of the VNF instance. Supports receiving the elastic scaling policy delivered by NFVO to realize the elastic scaling of VNF.
  • VIM responsible for infrastructure layer hardware resources, virtualization resource management, monitoring and fault reporting, and providing virtualized resource pools for upper-layer applications.
  • the PMF is a new logical functional entity defined in the MANO architecture for centralized management of the NFV MANO policy.
  • the PMF reuses policy management functions for creating, deleting, and modifying policy rules in the prior art (for example, the PMF can reuse the ZOOM of the Telecom Management Forum (TMF) (Zero-touch Orchestration, Operations and Management) strategy model).
  • TMF Telecom Management Forum
  • the NFV MANO architecture deploys the PMF function
  • the MANO Management Entity Network Functions Virtualization Orchestrator (NFVO)/Virtualized Network Function Manager (VNFM)/Virtual Infrastructure Management Virtualised Infrastructure Manager (VIM) only maintains policy enforcement capabilities.
  • the location of PMF in the MANO architecture is shown in Figure 2:
  • the PMF function is located at the NFVO level or can be further upgraded to the OSS/BSS level.
  • the physical implementation can be a separate manager or a manager co-located with the NFVO (ie, having the same IP address).
  • the PMF has domain characteristics, the policy management domain of the PMF is the same as the NFVO domain, or the policy management domain of the PMF covers several NFVO domains.
  • a policy management reference point is defined between the PMF and the OSS/BSS, VNFM, and VIM. If the PMF is physically a separate manager, a policy management reference point is also defined between the PMF and the NFVO.
  • the Provider is created, deleted, and modified by the Provider for the Consumer. The function of the rules.
  • the memory implementing the data storage may include the following four repositories:
  • NS catalog Includes all NSDs that have been loaded.
  • VNF Catalog Includes all VNF Packages that have been loaded.
  • NFV instance Includes all running network service instances and VNF instances.
  • NFVI resources Includes all NFVI resource status, available/reserved/allocated NFVI resources.
  • the embodiment of the present invention provides a policy rule execution entity.
  • the system rule framework provided by the first embodiment may be the NFVO, VNFM or VIM in the first embodiment.
  • Any one of the policy rule execution entities may include at least one processor 201 (eg, a CPU), a communication interface 202 (which may be at least one network interface or other type of interface), a memory 203, and at least one communication bus 204, Used to implement connection communication between these devices.
  • the processor 201 is configured to execute an executable module, such as a computer program, stored in the memory 203.
  • the memory 203 may include a high speed random access memory (RAM: Random Access Memory), and may also include a non-volatile memory such as at least one disk memory.
  • the communication connection between the system gateway and at least one other network element is implemented by at least one communication interface 202 (which may be wired or wireless), and may use an Internet, a wide area network, a local network, a metropolitan area network, or the like.
  • the memory stores the program 2031, and the program can be executed by the processor to implement various functions of the processor.
  • the communication interface 202 is configured to receive a network function virtualization management and an NFV MANO operation request sent by a policy rule decision entity, where the NFV MANO operation request includes a policy parameter;
  • the NFV MANO operation request includes network service NS lifecycle management, virtualized network function VNF lifecycle management and virtual resource management, NS instantiation, NS update, NS elastic scaling, NS healing, NS termination, VNF instantiation, VNF Update, VNF elastic scaling, VNF At least one of a cure, a VNF termination, a virtual resource reservation, and a virtual resource allocation.
  • the processor 201 is configured to acquire a policy descriptor file corresponding to the NFV MANO operation requested by the NFV MANO operation request, where the policy descriptor file includes at least one policy information corresponding to the NFV MANO operation,
  • the policy parameter configuration is configured into the policy information to form a policy rule.
  • the policy information includes at least one of an event monitored by the policy rule, a condition for executing the policy rule, and an action performed by the policy rule.
  • the specific implementation manner of the processor 201 acquiring the policy descriptor file corresponding to the NFV MANO operation request includes multiple types.
  • the following two optimization methods are provided:
  • the processor 201 is specifically configured to determine an operation attribute of the NFV MANO operation request, and obtain, from a catalog in the catalog, or from a set of policy descriptor files stored by the policy rule execution entity, corresponding to the operation attribute.
  • the policy descriptor file is specifically configured to determine an operation attribute of the NFV MANO operation request, and obtain, from a catalog in the catalog, or from a set of policy descriptor files stored by the policy rule execution entity, corresponding to the operation attribute.
  • the policy descriptor file is specifically configured to determine an operation attribute of the NFV MANO operation request, and obtain, from a catalog in the catalog, or from a set of policy descriptor files stored by the policy rule execution entity, corresponding to the operation attribute.
  • the processor 201 is specifically configured to obtain an identifier of the policy descriptor file from the NFV MANO operation request, and obtain the policy descriptor file corresponding to the identifier of the policy descriptor file from the catalog database.
  • the processor 201 is further configured to receive request information for updating the policy rule, where the request information includes a policy descriptor file used by the policy rule. And the updated policy parameter; obtaining a policy descriptor file used by the policy rule according to the identifier of the policy descriptor file; configuring the updated policy parameter into the policy descriptor file to form an updated policy rule.
  • the policy rule decision entity is an operation/service support system OSS/BSS or a policy management function entity PMF.
  • the device provided by the embodiment of the present invention performs a normalized management of a plurality of NFV MANO policy rules by using a templated policy descriptor file to determine policy information of the policy rule. Further, in the network service or VNF lifecycle management process, the policy information in the policy descriptor file is filled by the specific parameters carried in the interaction command between the MANO management entities, and is formed in the NS or VNF lifecycle management process. The practical application of policy rules to improve the efficiency of NFV MANO policy management.
  • the apparatus provided by the foregoing embodiment may be used to specifically update certain specific policy rules without regenerating corresponding to the entire descriptor file. All policy rules, so it can simplify the process of forming policy rules; and can meet the real-time adjustment needs of policy rules.
  • Step 301 The policy rule execution entity receives the network function virtualization management and the scheduling NFV MANO operation request sent by the policy rule decision entity, where the NFV MANO operation request includes a policy parameter.
  • the system rule structure provided by Embodiment 1 may be any one of NFVO, VNFM or VIM in Embodiment 1; the policy rule decision entity may be OSS/BSS or PMF.
  • the NFV MANO operation includes network service NS lifecycle management, virtualized network function VNF lifecycle management and virtual resource management, NS instantiation, NS update, NS elastic scaling, NS healing, NS termination, VNF instance. , VNF update, VNF elastic scaling, VNF healing, VNF termination, virtual resource reservation or virtual resource allocation.
  • Step 302 The policy rule execution entity acquires a policy descriptor file corresponding to the NFV MANO operation request, where the policy descriptor file includes an operation with the NFV MANO Requesting at least one policy information corresponding to the requested NFV MANO operation;
  • the policy descriptor file includes at least one policy information corresponding to an NFV MANO operation.
  • the policy information may be policy rule metadata (PolicyRuleMetaData), and at least one policy information in the same policy descriptor file includes an event monitored by a policy rule to be determined by the same NFV MANO operation, a condition or policy executed by the policy rule.
  • PolicyRuleMetaData policy rule metadata
  • the event monitored by the policy rule, the condition for executing the policy rule, or the action performed by the policy rule may be:
  • the policy descriptor file 1 corresponds to the network service elastic scaling operation (NS scaling)
  • the policy descriptor file includes at least one policy information corresponding to the NS scaling; for example:
  • the event monitored by the policy rule the VNF indicator of the NS, the performance parameter of the virtual resource used by the VNF constituting the NS, for example, CPU usage.
  • the condition for the execution of the policy rule the threshold for the condition comparison corresponding to the event monitored by the policy, for example, the threshold corresponding to the CPU usage.
  • Actions performed by policy rules NFV MANO operations performed when the threshold is greater or less than the threshold. For example, when the CPU usage is greater than or equal to the threshold, the scale out operation is performed. If the threshold is less than a certain threshold, the operation is not performed or the scale in operation is performed.
  • the policy descriptor file 2 corresponds to a VNF healing operation
  • the policy descriptor file 3 is bound to a virtual resource allocation operation, and the like.
  • the NFV MANO operation initiated by the policy rule decision entity is to implement the network service elastic scaling operation
  • the corresponding acquisition policy descriptor file 1 is obtained.
  • Step 303 The policy rule execution entity configures the policy parameter into the policy information to form a policy rule.
  • the policy descriptor file only includes the framework structure that forms the policy rule, that is, the policy information, and does not form a specific policy rule, from the input parameters of the NFV MANO operation request. Get the parameter values and combine the parameter values with the policy information to form a complete policy rule.
  • the specific implementation can be:
  • the policy information is a conditional expression, and the corresponding parameter value is a threshold value used for condition comparison when the conditional expression is judged.
  • the implementation of the on-board process of the policy descriptor file in the embodiment of the present invention may be (the implementation process is as shown in FIG. 4):
  • Step 401 The OSS/BSS locally creates a generated policy descriptor file for a certain type of NFV MANO operation, and then sends an On-Board Policy Descriptor management command to the PMF, instructing the PMF to complete the loading process of the policy descriptor file.
  • Step 402 After receiving the On-Board Policy Descriptor command, the PMF performs authentication, authentication, and the like on the policy descriptor file.
  • Step 403 The PMF determines that the policy descriptor file can be put on the shelf by verification, and sends a Notify Catalog management command to the catalog library, and the policy descriptor is put into the library.
  • the Catalog is a database for storing policy descriptor files at the PMF level.
  • step 404 the PMF also returns an On-Board Policy Descriptor confirmation command to the OSS/BSS to notify the OSS/BSS that the policy descriptor file is completed.
  • the policy rule execution entity can obtain the policy descriptor file corresponding to the NFV MANO operation in various ways. The following two optimization implementations are provided:
  • Manner 1 The corresponding policy descriptor file is obtained through the operation attribute of the NFV MANO operation.
  • the specific implementation may be:
  • the policy rule execution entity determines an operation attribute of the NFV MANO operation request
  • the policy rule execution entity executes from the catalog catalog or from the policy rule
  • the policy descriptor file corresponding to the operation attribute is obtained from a set of the body stored policy descriptor files.
  • the policy descriptor file 1 corresponds to the network service elastic scaling operation (NS scaling)
  • the policy descriptor file 2 corresponds to the VNF healing operation (VNF healing)
  • the policy descriptor file 3 corresponds to the virtual resource allocation operation
  • the policy rule execution entity determines that the operation attribute of the received NFV MANO operation is to implement the network service elastic scaling operation, the corresponding acquisition policy descriptor file 1 is used as the first policy descriptor file.
  • Manner 2 The mapping between the policy descriptor file and the policy descriptor file identifier is established, and the corresponding policy descriptor file is obtained through the corresponding relationship.
  • the specific implementation may be:
  • the policy rule execution entity obtains an identifier of the policy descriptor file from the NFV MANO operation request;
  • the policy rule execution entity obtains the policy descriptor file corresponding to the identifier of the policy descriptor file from a catalog library.
  • the specific implementation of the embodiment may be:
  • the OSS/BSS In the process of initiating the NS Life Cycle Management (NS LCM) operation to the NFVO, the OSS/BSS carries the identifier of the policy descriptor file corresponding to the NS LCM operation in the operation request message.
  • NS LCM NS Life Cycle Management
  • the default is NFVO. According to the NS LCM operation command, the corresponding policy descriptor file can be directly selected from the Catalog.
  • the policy descriptor file identifier corresponding to the policy descriptor file 1 is 001; the policy descriptor file identifier corresponding to the policy descriptor file 2 is 002; and the policy descriptor file 3 corresponds to the policy description.
  • the file identifier is 003;
  • the policy descriptor file 2 can be obtained as the first policy descriptor file by using the policy descriptor file identifier.
  • the foregoing manner is a specific implementation process when the policy rule is generated for the first time, but in a specific implementation environment, it is not necessary to regenerate all the policy rules in the policy descriptor file once, so The method for updating the policy rule is simplified.
  • a certain policy rule that needs to be adjusted may be specifically updated.
  • the policy rule is formed by combining the policy information (that is, the architecture of the policy rule) and the parameter value (the specific parameter of the policy rule), so the specific implementation of updating the policy rule may be, first, determining that the policy is to be updated.
  • the policy descriptor file in which the policy rule is located and then obtain the policy information corresponding to the policy rule to be updated from the policy descriptor file, and finally combine the policy information with the parameter value to be updated to form a new policy rule.
  • the specific implementation steps can be (as shown in Figure 5):
  • Step 501 The policy rule execution entity receives request information for updating the policy rule, where the request information includes an identifier of a policy descriptor file used by the policy rule and an updated policy parameter.
  • Step 502 The policy rule execution entity acquires a policy descriptor file used by the policy rule according to the identifier of the policy descriptor file.
  • Step 503 The policy rule execution entity configures the updated policy parameter into the policy descriptor file to form an updated policy rule.
  • the implementation can be:
  • the updated policy rule is generated by charging the policy information.
  • the method provided by the embodiment of the present invention performs a normalized management of a plurality of NFV MANO policy rules by using a templated policy descriptor file to determine policy information of the policy rule, and further can be in a network service or a VNF life cycle.
  • the policy information in the policy descriptor file is filled by the specific parameters carried in the interaction command between the MANO management entities to form a policy rule actually applied in the NS or VNF lifecycle management process, thereby improving NFV MANO.
  • the efficiency of policy management is a normalized management of a plurality of NFV MANO policy rules by using a templated policy descriptor file to determine policy information of the policy rule, and further can be in a network service or a VNF life cycle.
  • the method provided in the foregoing embodiment may be used to specifically update certain specific policy rules without regenerating corresponding to the entire descriptor file. All policy rules, so it can simplify the process of forming policy rules; and can meet the real-time adjustment needs of policy rules.
  • the method and apparatus provided by the embodiments of the present invention process thousands or tens of thousands of NFV MANO policy rules according to the NFV MANO operation category normalized policy descriptor file template, and in the network service or VNF life cycle management process
  • the policy information in the policy descriptor file is filled in by the specific parameter values carried in the interaction command between the MANO management entities, and the policy rules actually applied in the lifecycle management process are formed, thereby improving the efficiency of the NFV MANO policy management. .
  • an implementation method of dynamically updating one or several policy rules according to a policy descriptor file is provided, thereby simplifying the update management process of the policy rules.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种NFV MANO策略描述符的管理方法及装置，该方法包括：策略规则执行实体接收策略规则决策实体发送的网络功能虚拟化管理和编排NFV MANO操作请求，所述NFV MANO操作请求包括策略参数；获取对应于所述NFV MANO操作请求的策略描述符文件，其中，所述策略描述符文件包括与所述NFV MANO操作请求所请求的NFV MANO操作对应的至少一个策略信息；将所述策略参数配置到所述策略信息中形成策略规则。提升了现有技术中NFV MANO策略管理的操作效率。

Description

一种NFV MANO策略描述符的管理方法及装置 技术领域
本发明涉及通信技术领域，尤其涉及一种NFV MANO策略描述符的管理方法及装置。
背景技术
网络功能虚拟化(Network Function Virtualization，NFV)是电信网络运营商通过借鉴IT领域的虚拟化技术，在通用的云服务器、交换机和存储中实现部分电信网络功能。这种技术需要电信网络功能以软件方式实现，并能在通用的服务器硬件上运行，可以根据需要进行迁移、实例化、部署在网络的不同位置，并且不需要安装新设备。
在NFV管理和编排(NFV MANagement and Orchestration，NFV MANO)架构中，在网络服务描述符(Network Service Descriptor，NSD)或虚拟化网络功能描述符(Virtualised Network Function Descriptor，VNFD)中携带关于网络服务(Network Service，NS)或虚拟化网络功能(Virtualised Network Function，VNF)预配置的策略，例如:自动伸缩(Auto-Scaling)，亲和性(Affinity)/反亲和性(Anti-Affinity)规则。NFV MANO策略的应用基于一种假设：各策略之间彼此分立，不存在策略关联。
按照MANO现有的策略管理功能框架，当MANO系统面对数以千计或数以万计的VNF/NS实例的生命周期管理和相应的虚拟资源管理，需要创建和维护大量的策略规则，无法提升NFV MANO策略管理的效率。
发明内容
本发明提供一种NFV MANO策略描述符的管理方法及装置，本发明所提 供的方法和装置解决现有技术中MANO系统在面对大量的NS实例或VNF实例进行NFV MANO操作时，需要创建和维护大量的策略规则，从而导致NFV MANO策略管理的成本较高的问题。
第一方面，提供一种NFV MANO策略描述符的管理方法，包括：
策略规则执行实体接收策略规则决策实体发送的网络功能虚拟化管理和编排NFV MANO操作请求，所述NFV MANO操作请求包括策略参数；
所述策略规则执行实体获取对应于所述NFV MANO操作请求的策略描述符文件，其中，所述策略描述符文件包括与所述NFV MANO操作请求对应的至少一个策略信息；
所述策略规则执行实体将所述策略参数配置到所述策略信息中形成策略规则。
本该实现方式中，策略规则执行实体获取对应NFV MANO操作请求的策略描述符文件，通过策略规则执行实体和策略规则决策实体间的信令交互，策略规则执行实体将操作请求中的策略参数配置到所述策略信息中形成策略规则，避免了大量NFV MANO策略的维护，提升了NFV MANO策略管理的效率。
结合第一方面，在第一种可能的实现方式中，所述策略信息包括策略规则监视的事件、策略规则执行的条件和策略规则执行的动作中的至少一个。
在该实现方式中，通过策略规则监视的事件、策略规则执行的条件或策略规则执行的动作对NFV MANO操作的类别进行归一化的处理，从而实现策略规则的分类管理，进一步的提升NFV MANO策略管理的效率。
结合第一方面的第一种可能的实现方式，在第二种可能的实现方式中，获取对应于所述NFV MANO操作请求的策略描述符文件包括：
所述策略规则执行实体确定所述NFV MANO操作请求的操作属性；
所述策略规则执行实体从目录库Catalog中，或者从所述策略规则执行实体存储的策略描述符文件的集合中获取与所述操作属性对应的所述策略描述符文件。
结合第一方面的第一种可能的实现方式，在第三种可能的实现方式中，获取对应于所述NFV MANO操作请求的策略描述符文件包括：
所述策略规则执行实体从所述NFV MANO操作请求中获取策略描述符文件的标识；
所述策略规则执行实体从从目录库Catalog中获取与所述策略描述符文件的标识对应的所述策略描述符文件。
第一方面第二种和第三种可能的实现方式提供两种获取策略描述符文件的方式，通过两种方式可以实现根据NFV MANO操作的类别进行归一化的策略描述符文件模板处理，从而实现策略规则的分类管理，进一步的提升NFV MANO策略管理的效率。
结合第一方面，或者第一方面的第一至三种可能的实现方式，在第四种可能的实现方式中，所述策略规则执行实体将所述策略参数配置到所述策略信息中形成策略规则，进一步包括：
所述策略规则执行实体接收对所述策略规则进行更新的请求信息，其中，所述请求信息中包括所述策略规则所使用的策略描述符文件的标识和更新的策略参数；
所述策略规则执行实体根据所述策略描述符文件的标识获取所述策略规则所使用的策略描述符文件；
所述策略规则执行实体将所述更新的策略参数配置到所述策略描述符文件中形成更新的策略规则。
在该实现方式中，可以对策略描述符文件中的某一个或几个策略规则动 态更新，从而简化了策略规则的更新管理流程。
结合第一方面，或者第一方面的第一至四种可能的实现方式，在第五种可能的实现方式中，所述NFV MANO操作请求包括网络服务NS生命周期管理、虚拟化网络功能VNF生命周期管理和虚拟资源管理、NS实例化、NS更新、NS弹性伸缩、NS治愈、NS终结、VNF实例化、VNF更新、VNF弹性伸缩、VNF治愈、VNF终结、虚拟资源预留、虚拟资源分配中的至少一种。
结合第一方面，或者第一方面的第一至五种可能的实现方式，在第六种可能的实现方式中，所述策略规则决策实体为运营/业务支撑系统OSS/BSS；
所述策略规则执行实体为网络功能虚拟化编排器NFVO或网络功能虚拟化管理器VNFM或虚拟化基础设施管理器VIM。
第二方面，提供一种策略规则执行实体，包括：通信接口和处理器，
所述通信接口用于接收策略规则决策实体发送的网络功能虚拟化管理和编排NFV MANO操作请求，所述NFV MANO操作请求包括策略参数；
所述处理器用于获取对应于所述NFV MANO操作请求的策略描述符文件，其中，所述策略描述符文件包括与所述NFV MANO操作请求对应的至少一个策略信息，将所述策略参数配置到所述策略信息中形成策略规则。
结合第二方面，在第一种可能的实现方式中，其特征在于，所述策略信息包括策略规则监视的事件、策略规则执行的条件和策略规则执行的动作中的至少一个。
结合第二方面或第二方面第一种可能的实现方式，在第二种可能的实现方式中，所述处理器具体用于确定所述NFV MANO操作请求的操作属性；并从目录库Catalog中，或者从所述策略规则执行实体存储的策略描述符文件的集合中获取与所述操作属性对应的所述策略描述符文件。
结合第二方面或第二方面第一种可能的实现方式，在第三种可能的实现 方式中，所述处理器具体用于从所述NFV MANO操作请求中获取策略描述符文件的标识；并从从目录库Catalog中获取与所述策略描述符文件的标识对应的所述策略描述符文件。
结合第二方面，或者第二方面的第一至三种可能的实现方式，在第四种可能的实现方式中，所述处理器还用于接收对所述策略规则进行更新的请求信息；其中，所述请求信息中包括所述策略规则所使用的策略描述符文件的标识和更新的策略参数；根据所述策略描述符文件的标识获取所述策略规则所使用的策略描述符文件；将所述更新的策略参数配置到所述策略描述符文件中形成更新的策略规则。
结合第二方面，或者第二方面的第一至四种可能的实现方式，在第五种可能的实现方式中，所述NFV MANO操作请求包括网络服务NS生命周期管理、虚拟化网络功能VNF生命周期管理和虚拟资源管理、NS实例化、NS更新、NS弹性伸缩、NS治愈、NS终结、VNF实例化、VNF更新、VNF弹性伸缩、VNF治愈、VNF终结、虚拟资源预留、虚拟资源分配中的至少一种。
结合第二方面，或者第二方面的第一至五种可能的实现方式，在第六种可能的实现方式中，所述策略规则决策实体为运营/业务支撑系统OSS/BSS。
第三方面，提供一种NFV MANO策略描述符的管理系统，该系统包括第二方面任意一种可能的实现方式所提供的策略规则执行实体和策略规则决策实体。
结合第三方面，在第一种可能的实现方式中，所述策略规则执行实体为网络功能虚拟化编排器NFVO或网络功能虚拟化管理器VNFM或虚拟化基础设施管理器VIM。
结合第三方面或第三方面第一种可能的实现方式，在第二种可能的实现方式中，所述策略规则决策实体为策略管理功能实体PMF；其中，该PMF用 于进行策略规则创建、删除和修改。
结合第二方面第二种可能的实现方式，在第三种可能的实现方式中，所述PMF位于NFVO层面或者OSS/BSS层面。
结合第三方面第二种或第三种可能的实现方式，在第四种可能的实现方式中，所述PMF为单独的管理器或者是与NFVO具有相同的IP地址的管理器。
结合第三方面，或第三方面第一种至第四种可能的实现方式中任一，在第五种可能的实现方式中，该系统还包括目录库Catalog，该Catalog保存所述策略描述符文件。
第四方面，提供了一种计算机可读存储介质，所述可读存储介质上存储有实现第一方面描述的用于NFV MANO策略描述符的管理方法的程序代码，该程序代码包含运行第一方面描述的用于NFV MANO策略描述符的管理方法的执行指令。
本发明实施例提供的方法和装置将数以千计或万计的NFV MANO策略规则根据NFV MANO操作的类别进行归一化的策略描述符文件模板处理(即对应每个类别的操作对应一个策略描述符文件)，并在网络服务或VNF生命周期管理过程中，通过MANO管理实体之间的交互命令所携带的具体参数值来填充该策略描述符文件中的策略信息，形成在生命周期管理过程中实际应用的策略规则，从而提升NFV MANO策略管理的效率。
附图说明
图1为本发明实施例提供的一种NFV MANO策略描述符的管理系统的结构示意图；
图2为本发明实施例提供的一种策略规则执行实体的结构示意图；
图3为本发明实施例提供的一种NFV MANO策略描述符的管理方法的流程示意图；
图4为本发明实施例策略描述符文件的上架(on-board)过程的流程示意图；
图5为本发明实施例策略规则更新过程的流程示意图。
具体实施方式
实施例一
本发明实施例的方法和装置应用在NFV系统。本发明实施例提供一种NFV MANO策略描述符的管理系统。如图1所示，该NFV MANO策略描述符的管理系统包括：运营支撑系统/业务支撑系统(Operation Support System/Business Support System，简称OSS/BSS)、网元管理系统(Element Management System，简称EMS)、虚拟网络功能(Virtualized Network Function，简称VNF)、网络功能虚拟化基础设施(Network Function Virtualization Infrastructure，简称NFVI)以及NFV-MIMO。其中，NFV MANO包括网络功能虚拟化编排器(NFV Orchestrator，简称NFVO)、虚拟网络功能管理器(Virtualized Network Function Manager，简称VNFM)、虚拟化基础设施管理器(Virtualized Infrastructure Manager,VIM)以及策略管理功能实体(Policy Management Function，PMF)。
OSS/BSS主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。
EMS可以用于管理一个或多个VNF，主要针对VNF执行传统的故障管理、配置管理、计费管理、性能管理、安全管理(Fault Management，Configuration  Management，Accounting Management，Performance Management，Security Management，简称FCAPS)功能。
VNF对应于传统非虚拟化网络中的物理网络功能(Physical Network Function，简称PNF)，如虚拟化的演进分组核心网(Evolved Packet Core，简称EPC)节点。虚拟化的EPC节点包括：移动管理实体(Mobile Management Entity，简称MME)、服务网关(Serving GateWay，简称SGW)和分组数据网关(Packet Data Network GateWay，简称PGW)等。其中，网络的功能性行为和状态与网络是否虚拟化无关，NFV系统中VNF和PNF拥有相同的功能性行为和外部接口。
NFVI中的虚拟化层用于抽象硬件资源层的硬件资源，将VNF和硬件资源所属的物理层解耦，向VNF提供虚拟资源。
虚拟资源层可以包括虚拟计算、虚拟存储和虚拟网络。虚拟计算、虚拟存储可以以虚拟机或其他虚拟容器的形式向VNF提供，例如一个或多个虚拟机组成一个VNF。虚拟化层通过抽象网络硬件形成虚拟网络。虚拟网络，用于实现多个虚拟机之间，或多个承载VNF的其他类型的虚拟容器之间的通信。虚拟网络的创建可以通过虚拟LAN(Vritual LAN,简称VLAN)、虚拟专用局域网业务(Virtual Private LAN Service,简称VPLS)、虚拟可扩展局域网(Virtual eXtensible Local Area Network,简称VxLAN)或通用路由封装网络虚拟化(Nerwork Virtualization using Generic Routing Encapsulation，简称NVGRE)等技术实现。
NFVO：实现NSD、虚拟网络功能转发图(Virtualised Network Function Forwarding Graph，VNFFG)的管理及处理，网络服务生命周期的管理，并与VNFM配合实现VNF的生命周期管理和资源的全局视图功能。
VNFM：实现虚拟化网元VNF的生命周期管理，包括VNFD的管理及处 理，VNF实例的初始化，VNF的扩容/缩容，VNF实例的终止。支持接收NFVO下发的弹性伸缩(scaling)策略，实现VNF的弹性伸缩。
VIM：主要负责基础设施层硬件资源，虚拟化资源的管理，监控和故障上报，面向上层应用提供虚拟化资源池。
在本发明实施例中，PMF是在MANO架构中定义的新的用于对NFV MANO策略进行集中式管理的逻辑功能实体。可选的，PMF复用现有技术中的策略规则创建、删除和修改的策略管理功能(例如：PMF可以复用电信管理论坛(Telecom Management Forum,TMF)的ZOOM(Zero-touch Orchestration,Operations and Management)策略模型)。在NFV MANO架构部署了PMF功能的场景下，MANO管理实体(网络功能虚拟化编排器(Network Functions Virtualization Orchestrator，NFVO)/虚拟网络功能管理器(Virtualised Network Function Manager，VNFM)/虚拟化基础设施管理器(Virtualised Infrastructure Manager，VIM))仅保持策略执行功能。PMF在MANO架构中的位置如图2所示：
其中，PMF功能位于NFVO层面或者可以进一步提升到OSS/BSS层面，物理实现上可以是单独的管理器或者与NFVO共址(即具有相同的IP地址)的管理器。PMF具有域的特性，PMF的策略管理域与NFVO域相同，或者PMF的策略管理域覆盖若干个NFVO域。
PMF和OSS/BSS、VNFM、VIM之间定义策略管理参考点，如果PMF物理上是单独的管理器，则PMF和NFVO之间也定义策略管理参考点。在PMF相关的各参考点上(例如：Os-Ma-Pmf，Pmf-Vnfm，Pmf-Vi，Pmf-Nfvo)，实现服务者方(Provider)为消费者方(Consumer)创建、删除、修改策略规则的功能。
在该实施例中，实现数据存储的存储器可以包括下面四个储存库:
NS目录册(catalog):包括所有已经加载的NSD。
VNF目录册:包括所有已经加载的VNF Packages。
NFV实例:包括所有正在运行的网络服务实例和VNF实例。
NFVI资源:包括所有NFVI资源状态，可用的/已预留的/已分配的NFVI资源。
实施例二
如图2所示，结合实施例一本发明实施例提供一种策略规则执行实体；基于实施例一所提供的系统框架，该策略规则执行实体可以是实施例一中的NFVO、VNFM或VIM中的任意一个；该策略规则执行实体可以包括至少一个处理器201(例如CPU)，通信接口202(该通信接口可以是至少一个网络接口或者其他类型接口)，存储器203，和至少一个通信总线204，用于实现这些装置之间的连接通信。处理器201用于执行存储器203中存储的可执行模块，例如计算机程序。存储器203可能包含高速随机存取存储器(RAM：Random Access Memory)，也可能还包括非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。通过至少一个通信接口202(可以是有线或者无线)实现该系统网关与至少一个其他网元之间的通信连接，可以使用互联网，广域网，本地网，城域网等。
在一些实施方式中，存储器存储了程序2031，程序可以被处理器执行，实现处理器的各项功能，具体实现包括：
所述通信接口202，用于接收策略规则决策实体发送的网络功能虚拟化管理和编排NFV MANO操作请求，所述NFV MANO操作请求包括策略参数；
其中，该NFV MANO操作请求包括网络服务NS生命周期管理、虚拟化网络功能VNF生命周期管理和虚拟资源管理、NS实例化、NS更新、NS弹性伸缩、NS治愈、NS终结、VNF实例化、VNF更新、VNF弹性伸缩、VNF 治愈、VNF终结、虚拟资源预留、虚拟资源分配中的至少一种。
处理器201，用于获取所述NFV MANO操作请求所请求的NFV MANO操作对应的策略描述符文件，其中，所述策略描述符文件包括与所述NFV MANO操作对应的至少一个策略信息，将所述策略参数配置到所述策略信息中形成策略规则。
其中，该策略信息包括策略规则监视的事件、策略规则执行的条件和策略规则执行的动作中的至少一个。
可选的，该处理器201获取对应于所述NFV MANO操作请求的策略描述符文件的具体实现方式包括多种，以下提供两种最优化的方式：
处理器201，具体用于确定所述NFV MANO操作请求的操作属性；并从目录库Catalog中，或者从所述策略规则执行实体存储的策略描述符文件的集合中获取与所述操作属性对应的所述策略描述符文件。
处理器201，具体用于从所述NFV MANO操作请求中获取策略描述符文件的标识；并从从目录库Catalog中获取与所述策略描述符文件的标识对应的所述策略描述符文件。
可选的，为了简化策略规则的更新流程，该处理器201还用于接收对所述策略规则进行更新的请求信息；其中，所述请求信息中包括所述策略规则所使用的策略描述符文件的标识和更新的策略参数；根据所述策略描述符文件的标识获取所述策略规则所使用的策略描述符文件；将所述更新的策略参数配置到所述策略描述符文件中形成更新的策略规则。
可选的，在具体使用本发明实施例所提供的方案时，该所述策略规则决策实体为运营/业务支撑系统OSS/BSS或策略管理功能实体PMF。
本发明实施例提供的装置通过模板化的策略描述符文件来对数量众多的NFV MANO策略规则进行分类别的归一化管理，确定策略规则的策略信息， 进一步的可以在网络服务或VNF生命周期管理过程中，通过MANO管理实体之间的交互命令所携带的具体参数来填充该策略描述符文件中的策略信息，形成在NS或VNF生命周期管理过程中实际应用的策略规则，从而提升NFV MANO策略管理的效率。
另外，当实际的应用中需要更新的特定几个策略规则时，利用上述实施例所提供的装置可以有针对性的更新特定的几个策略规则并不需要重新生成与整个描述符文件所对应的所有策略规则，所以能够简化策略规则的形成流程；并能够满足策略规则的实时调整需求。
实施例三
如图3所示，基于实施例一所提供的系统构架，下面结合说明书附图对本发明实施例提供的一种NFV MANO策略描述符的管理方法作进一步详细描述，具体包括：
步骤301，策略规则执行实体接收策略规则决策实体发送的网络功能虚拟化管理和编排NFV MANO操作请求，所述NFV MANO操作请求包括策略参数；
其中，集合实施例一所提供的系统构架，该策略规则执行实体可以是实施例一中的NFVO、VNFM或VIM中的任意一个；该策略规则决策实体可以是OSS/BSS或PMF。
在该实施例中，该NFV MANO操作包括网络服务NS生命周期管理、虚拟化网络功能VNF生命周期管理和虚拟资源管理、NS实例化、NS更新、NS弹性伸缩、NS治愈、NS终结、VNF实例化、VNF更新、VNF弹性伸缩、VNF治愈、VNF终结、虚拟资源预留或虚拟资源分配。
步骤302，所述策略规则执行实体获取对应于所述NFV MANO操作请求的策略描述符文件，其中，所述策略描述符文件包括与所述NFV MANO操作 请求所请求的NFV MANO操作对应的至少一个策略信息；
另外，策略描述符文件包括与一个NFV MANO操作对应的至少一个策略信息。其中，该策略信息可以是策略规则元数据(PolicyRuleMetaData)，同一个策略描述符文件中的至少一个策略信息包括面对同一NFV MANO操作要确定的策略规则监视的事件、策略规则执行的条件或策略规则执行的动作中的一种或多种的组合。其中，策略规则监视的事件、策略规则执行的条件或策略规则执行的动作分别可以是：
若策略描述符文件1与网络服务弹性伸缩操作(NS scaling)对应，则该策略描述符文件中包括至少一个与NS scaling对应的策略信息；例如：
策略规则监视的事件：组成该NS的VNF指示器(VNF indicator)、组成该NS的VNF所使用的虚拟资源的性能参数，例如：CPU占用率。
策略规则执行的条件：策略监视的事件对应的用于条件比较的门限，例如：CPU占用率对应的门限值。
策略规则执行的动作：大于或者小于条件中的门限值时所执行的NFV MANO操作。例如：CPU占用率大于等于门限值时执行scale out操作，小于某个门限值时不操作或执行scale in操作。
策略描述符文件2与VNF自愈操作(VNF healing)对应，策略描述符文件3绑定虚拟资源分配操作等。对应的，如果策略规则决策实体发起的NFV MANO操作是实现网络服务弹性伸缩操作的，则对应的获取策略描述符文件1。
步骤303，所述策略规则执行实体将所述策略参数配置到所述策略信息中形成策略规则。
在该实施例中，策略描述符文件只包括了形成策略规则的框架结构即策略信息，并没有形成具体的策略规则，从NFV MANO操作请求的输入参数中 获取参数值，将参数值与策略信息组合才能形成完整的策略规则。例如要形成一个条件判断的策略规则，具体实现可以是：
策略信息为条件表达式，对应的参数值则为条件表达式判断时所使用的用于条件比较的门限值。
基于实施例一的系统结构，在获取所述的策略描述符文件之前，本发明实施例中策略描述符文件的上架(on-board)过程具体实现可以是(实现流程如图4所示)：
步骤401，OSS/BSS针对某类NFV MANO操作在本地创建生成策略描述符文件，然后向PMF发送On-Board Policy Descriptor管理命令，指示PMF完成该策略描述符文件的上架过程。
步骤402，PMF接收到On-Board Policy Descriptor命令后，对策略描述符文件进行鉴权、认证等方面的验证；
步骤403，PMF确定该策略描述符文件通过验证可以上架，则发送Notify Catalog管理命令给目录库Catalog，将该策略描述符上架入库。其中，Catalog是位于PMF层面的用于存储策略描述符文件的数据库。
步骤404，PMF还向OSS/BSS返回On-Board Policy Descriptor确认命令，通知OSS/BSS完成了策略描述符文件的上架。
在策略描述符文件上架存储到Catalog后，策略规则执行实体可以通过多种方式获取对应于所述NFV MANO操作的策略描述符文件，以下提供两种最优化的实现方式：
方式一：通过NFV MANO操作的操作属性获取对应的策略描述符文件，具体实现可以是：
所述策略规则执行实体确定所述NFV MANO操作请求的操作属性；
所述策略规则执行实体从目录库Catalog中，或者从所述策略规则执行实 体存储的策略描述符文件的集合中获取与所述操作属性对应的所述策略描述符文件。
例如：策略描述符文件1与网络服务弹性伸缩操作(NS scaling)对应、策略描述符文件2与VNF自愈操作(VNF healing)对应、策略描述符文件3与虚拟资源分配操作对应；
对应的如果策略规则执行实体确定接收到的NFV MANO操作的操作属性是实现网络服务弹性伸缩操作，则对应的获取策略描述符文件1作为第一策略描述符文件。
方式二：建立策略描述符文件与策略描述符文件标识的对应关系，通过该对应关系获取对应的策略描述符文件，具体实现可以是：
所述策略规则执行实体从所述NFV MANO操作请求中获取策略描述符文件的标识；
所述策略规则执行实体从从目录库Catalog中获取与所述策略描述符文件的标识对应的所述策略描述符文件。
当利用OSS/BSS和NFVO交互实现本发明实施例的方案时，该实施例的具体实现可以是：
OSS/BSS在向NFVO发起NS生命周期管理(NS Life Cycle Management，NS LCM)操作的过程中，在操作请求消息中携带对应该NS LCM操作的策略描述符文件的标识。
如果在NS LCM操作中没有携带策略描述符文件的标识，那么默认为NFVO根据该NS LCM操作命令可以直接从Catalog选择相应的策略描述符文件。
例如：策略描述符文件1对应的策略描述符文件标识为001；策略描述符文件2对应的策略描述符文件标识为002；策略描述符文件3对应的策略描述 符文件标识为003；
对应的，如果策略规则执行实体从接收到的NFV MANO操作中获取标识为002，则可以通过该策略描述符文件标识获取到策略描述符文件2作为第一策略描述符文件。
可选的，上述方式是策略规则第一次生成时的具体实现过程，但是在具体的实现环境中，并不需要每次都将策略描述符文件中的所有策略规则都重新生成一次，所以为了简化策略规则的更新流程，本发明实施例提供的方法中，还可以对某一个需要调整的策略规则进行具体的更新。因为在本发明实施例中，策略规则是由策略信息(即策略规则的架构)和参数值(策略规则的具体参数)组合形成，所以要更新某一个策略规则具体实现可以是，首先确定待更新的策略规则所在的策略描述符文件，然后再从该策略描述符文件中获取待更新的策略规则对应的策略信息，最后将策略信息与要更新的参数值进行组合就可以形成新的策略规则，具体实现步骤可以是(如图5所示)：
步骤501，所述策略规则执行实体接收对所述策略规则进行更新的请求信息，其中，所述请求信息中包括所述策略规则所使用的策略描述符文件的标识和更新的策略参数；
步骤502，所述策略规则执行实体根据所述策略描述符文件的标识获取所述策略规则所使用的策略描述符文件；
步骤503，所述策略规则执行实体将所述更新的策略参数配置到所述策略描述符文件中形成更新的策略规则。
其中，为了达到有针对性的对特定策略规则进行更新，而不是更新整个策略描述符文件，则在将所述更新的策略参数配置到所述策略描述符文件中形成更新的策略规则时，具体实现可以是：
在策略描述符文件中获取策略规则对应的策略信息，利用更新参数值填 充到所述策略信息中生成更新后的策略规则。
本发明实施例提供的方法通过模板化的策略描述符文件来对数量众多的NFV MANO策略规则进行分类别的归一化管理，确定策略规则的策略信息，进一步的可以在网络服务或VNF生命周期管理过程中，通过MANO管理实体之间的交互命令所携带的具体参数来填充该策略描述符文件中的策略信息，形成在NS或VNF生命周期管理过程中实际应用的策略规则，从而提升NFV MANO策略管理的效率。
另外，当实际的应用中需要更新的特定几个策略规则时，利用上述实施例所提供的方法可有针对性的更新特定的几个策略规则并不需要重新生成与整个描述符文件所对应的所有策略规则，所以能够简化策略规则的形成流程；并能够满足策略规则的实时调整需求。
本申请实施例中的上述一个或多个技术方案，至少具有如下的技术效果：
本发明实施例提供的方法和装置将数以千计或万计的NFV MANO策略规则根据NFV MANO操作的类别进行归一化的策略描述符文件模板处理，并在网络服务或VNF生命周期管理过程中，通过MANO管理实体之间的交互命令所携带的具体参数值来填充该策略描述符文件中的策略信息，形成在生命周期管理过程中实际应用的策略规则，从而提升NFV MANO策略管理的效率。
另外，还提供根据策略描述符文件动态更新某一个或几个策略规则的实现方式，从而简化了策略规则的更新管理流程。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (20)

  1. 一种NFV MANO策略描述符的管理方法，其特征在于，包括：
    策略规则执行实体接收策略规则决策实体发送的网络功能虚拟化管理和编排NFV MANO操作请求，所述NFV MANO操作请求包括策略参数；
    所述策略规则执行实体获取对应于所述NFV MANO操作请求的策略描述符文件，其中，所述策略描述符文件包括与所述NFV MANO操作请求所请求的NFV MANO操作对应的至少一个策略信息；
    所述策略规则执行实体将所述策略参数配置到所述策略信息中形成策略规则。
  2. 如权利要求1所述的方法，其特征在于，所述策略信息包括策略规则监视的事件、策略规则执行的条件和策略规则执行的动作中的至少一个。
  3. 如权利要求1或2所述的方法，其特征在于，获取对应于所述NFV MANO操作的策略描述符文件包括：
    所述策略规则执行实体确定所述NFV MANO操作的操作属性；
    所述策略规则执行实体从目录库Catalog中，或者从所述策略规则执行实体存储的策略描述符文件的集合中获取与所述操作属性对应的所述策略描述符文件。
  4. 如权利要求1或2所述的方法，其特征在于，获取对应于所述NFV MANO操作的策略描述符文件包括：
    所述策略规则执行实体从所述NFV MANO操作请求中获取策略描述符文件的标识；
    所述策略规则执行实体从从目录库Catalog中获取与所述策略描述符文件的标识对应的所述策略描述符文件。
  5. 如权利要求1～4任一所述的方法，其特征在于，所述策略规则执行实体将所述策略参数配置到所述策略信息中形成策略规则，进一步包括：
    所述策略规则执行实体接收对所述策略规则进行更新的请求信息，其中，所述请求信息中包括所述策略规则所使用的策略描述符文件的标识和更新的策略参数；
    所述策略规则执行实体根据所述策略描述符文件的标识获取所述策略规则所使用的策略描述符文件；
    所述策略规则执行实体将所述更新的策略参数配置到所述策略描述符文件中形成更新的策略规则。
  6. 如权利要求1～5任一所述的方法，其特征在于，所述NFV MANO操作包括网络服务NS生命周期管理、虚拟化网络功能VNF生命周期管理和虚拟资源管理、NS实例化、NS更新、NS弹性伸缩、NS治愈、NS终结、VNF实例化、VNF更新、VNF弹性伸缩、VNF治愈、VNF终结、虚拟资源预留、虚拟资源分配中的至少一种。
  7. 如权利要求1～6任一所述的方法，其特征在于，所述策略规则决策实体为运营/业务支撑系统OSS/BSS；
    所述策略规则执行实体为网络功能虚拟化编排器NFVO或网络功能虚拟化管理器VNFM或虚拟化基础设施管理器VIM。
  8. 一种策略规则执行实体，其特征在于，包括：通信接口和处理器，
    所述通信接口用于接收策略规则决策实体发送的网络功能虚拟化管理和编排NFV MANO操作请求，所述NFV MANO操作请求包括策略参数；
    所述处理器用于获取所述NFV MANO操作请求所请求的NFV MANO操作对应的策略描述符文件，其中，所述策略描述符文件包括与所述NFV MANO操作对应的至少一个策略信息，将所述策略参数配置到所述策略信息 中形成策略规则。
  9. 如权利要求8所述策略规则执行实体，其特征在于，所述策略信息包括策略规则监视的事件、策略规则执行的条件和策略规则执行的动作中的至少一个。
  10. 如权利要求8或9所述策略规则执行实体，其特征在于，所述处理器具体用于确定所述NFV MANO操作的操作属性；并从目录库Catalog中，或者从所述策略规则执行实体存储的策略描述符文件的集合中获取与所述操作属性对应的所述策略描述符文件。
  11. 如权利要求8或9所述策略规则执行实体，其特征在于，所述处理器具体用于从所述NFV MANO操作请求中获取策略描述符文件的标识；并从从目录库Catalog中获取与所述策略描述符文件的标识对应的所述策略描述符文件。
  12. 如权利要求8～11任一所述策略规则执行实体，其特征在于，所述处理器还用于接收对所述策略规则进行更新的请求信息；其中，所述请求信息中包括所述策略规则所使用的策略描述符文件的标识和更新的策略参数；根据所述策略描述符文件的标识获取所述策略规则所使用的策略描述符文件；将所述更新的策略参数配置到所述策略描述符文件中形成更新的策略规则。
  13. 如权利要求8～12任一所述策略规则执行实体，其特征在于，所述NFV MANO操作请求包括网络服务NS生命周期管理、虚拟化网络功能VNF生命周期管理和虚拟资源管理、NS实例化、NS更新、NS弹性伸缩、NS治愈、NS终结、VNF实例化、VNF更新、VNF弹性伸缩、VNF治愈、VNF终结、虚拟资源预留、虚拟资源分配中的至少一种。
  14. 如权利要求8～13任一所述策略规则执行实体，其特征在于，所述策略规则决策实体为运营/业务支撑系统OSS/BSS。
  15. 一种NFV MANO策略描述符的管理系统，其特征在于，包括权利要求8～14任一项所述的策略规则执行实体和策略规则决策实体。
  16. 如权利要求15所述的NFV MANO策略描述符的管理系统，其特征在于，所述策略规则执行实体为网络功能虚拟化编排器NFVO或网络功能虚拟化管理器VNFM或虚拟化基础设施管理器VIM。
  17. 如权利要求15或16所述的NFV MANO策略描述符的管理系统，其特征在于，所述策略规则决策实体为策略管理功能实体PMF；其中，该PMF用于进行策略规则创建、删除和修改。
  18. 如权利要求17所述的NFV MANO策略描述符的管理系统，其特征在于，所述PMF位于NFVO层面或者OSS/BSS层面。
  19. 如权利要求17或18所述的NFV MANO策略描述符的管理系统，其特征在于，所述PMF为单独的管理器或者是与NFVO具有相同的IP地址的管理器。
  20. 如权利要求15～19任一所述的NFV MANO策略描述符的管理系统，其特征在于，该系统还包括目录库Catalog，该Catalog保存所述策略描述符文件。
PCT/CN2016/080516 2016-04-28 2016-04-28 一种nfv mano策略描述符的管理方法及装置 WO2017185303A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201680071472.3A CN108370328B (zh) 2016-04-28 2016-04-28 一种nfv mano策略描述符的管理方法及装置
PCT/CN2016/080516 WO2017185303A1 (zh) 2016-04-28 2016-04-28 一种nfv mano策略描述符的管理方法及装置
EP16899816.9A EP3419216A4 (en) 2016-04-28 2016-04-28 MANUFACTURING POLICY DESCRIPTOR MANUFACTURING METHOD AND DEVICE
US16/168,512 US10601666B2 (en) 2016-04-28 2018-10-23 Network functions virtualization management and orchestration policy descriptor management method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/080516 WO2017185303A1 (zh) 2016-04-28 2016-04-28 一种nfv mano策略描述符的管理方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/168,512 Continuation US10601666B2 (en) 2016-04-28 2018-10-23 Network functions virtualization management and orchestration policy descriptor management method and apparatus

Publications (1)

Publication Number Publication Date
WO2017185303A1 true WO2017185303A1 (zh) 2017-11-02

Family

ID=60160543

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/080516 WO2017185303A1 (zh) 2016-04-28 2016-04-28 一种nfv mano策略描述符的管理方法及装置

Country Status (4)

Country Link
US (1) US10601666B2 (zh)
EP (1) EP3419216A4 (zh)
CN (1) CN108370328B (zh)
WO (1) WO2017185303A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887121A (zh) * 2019-11-29 2021-06-01 北京华为数字技术有限公司 一种管理网络服务的方法、设备及系统
WO2021238718A1 (zh) * 2020-05-25 2021-12-02 中兴通讯股份有限公司 一种响应方法、确定方法、装置、设备及介质
EP3796162A4 (en) * 2018-06-05 2022-03-16 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR CONTAINER SERVICE MANAGEMENT

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10476839B2 (en) * 2016-08-15 2019-11-12 Cisco Technology, Inc. Datapath triggered on-demand NFV service activation
EP3698246A1 (en) * 2017-10-17 2020-08-26 Telefonaktiebolaget LM Ericsson (PUBL) Management of a virtual network function
CN110971439A (zh) * 2018-09-30 2020-04-07 中兴通讯股份有限公司 策略决策方法及装置、系统、存储介质、策略决策单元及集群
CN111399839B (zh) * 2019-01-02 2023-03-28 中国移动通信有限公司研究院 一种vnf注册方法、装置、介质和设备
CN111404709B (zh) * 2019-01-02 2023-05-09 中国移动通信有限公司研究院 网络功能虚拟化下策略规则的运行方法及装置
CN111953503B (zh) * 2019-05-14 2023-04-07 中国电信股份有限公司 Nfv资源部署编排方法和网络功能虚拟化编排器
TWI707561B (zh) * 2019-11-20 2020-10-11 中華電信股份有限公司 虛擬網路功能的管理系統和管理方法
EP4113911A4 (en) * 2020-02-26 2024-04-10 Rakuten Symphony Singapore Pte Ltd NETWORK SERVICE CONSTRUCTION SYSTEM AND NETWORK SERVICE CONSTRUCTION METHODS

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104580293A (zh) * 2013-10-17 2015-04-29 中国电信股份有限公司 用于远程控制管控策略的方法、装置和系统
US20150381423A1 (en) * 2014-06-26 2015-12-31 Futurewei Technologies, Inc. System and Method for Virtual Network Function Policy Management
CN105282195A (zh) * 2014-06-27 2016-01-27 中兴通讯股份有限公司 网络服务提供、策略规则评估、服务组件选择方法及装置
WO2016045082A1 (zh) * 2014-09-26 2016-03-31 华为技术有限公司 一种策略实现方法和装置以及系统

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103607305B (zh) * 2013-11-26 2017-03-15 北京华胜天成科技股份有限公司 一种分布式网络策略实现方法和装置
CN105210337B (zh) * 2014-03-24 2019-06-11 华为技术有限公司 一种nfv系统的业务实现方法及通信单元
US9806975B2 (en) * 2014-06-12 2017-10-31 Futurewei Technologies, Inc. Methods and systems for managing capacity in a virtualized network
CN104134122B (zh) * 2014-07-30 2018-01-23 华为技术有限公司 一种许可证申请方法及装置
CN105577499B (zh) * 2014-10-10 2019-05-28 华为技术有限公司 决策协调方法、执行装置和决策协调器
EP3249860A4 (en) * 2015-01-23 2018-01-24 Nec Corporation Method, device, and program for management and orchestration of network functions virtualization
US9769694B2 (en) * 2015-03-13 2017-09-19 Intel IP Corporation MME overload or underload mitigation by MME VNF apparatus and method
CN105099789B (zh) * 2015-09-02 2018-03-16 华为技术有限公司 一种网元升级方法及设备
KR101994118B1 (ko) * 2015-09-09 2019-09-30 한국전자통신연구원 범용 vnfm 및 vnf 관리 방법
EP3366016A1 (en) * 2015-10-22 2018-08-29 Nokia Solutions and Networks Oy Security mechanism for communication network including virtual network functions
KR20170056350A (ko) * 2015-11-13 2017-05-23 한국전자통신연구원 Nfv 자원 할당 검증 장치
US11070442B2 (en) * 2015-11-24 2021-07-20 NEC Laboratories Europe GmbH Method and network for managing and orchestrating virtual network functions and network applications
WO2017170470A1 (ja) * 2016-03-28 2017-10-05 日本電気株式会社 ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104580293A (zh) * 2013-10-17 2015-04-29 中国电信股份有限公司 用于远程控制管控策略的方法、装置和系统
US20150381423A1 (en) * 2014-06-26 2015-12-31 Futurewei Technologies, Inc. System and Method for Virtual Network Function Policy Management
CN105282195A (zh) * 2014-06-27 2016-01-27 中兴通讯股份有限公司 网络服务提供、策略规则评估、服务组件选择方法及装置
WO2016045082A1 (zh) * 2014-09-26 2016-03-31 华为技术有限公司 一种策略实现方法和装置以及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3419216A4 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3796162A4 (en) * 2018-06-05 2022-03-16 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR CONTAINER SERVICE MANAGEMENT
US11354167B2 (en) 2018-06-05 2022-06-07 Huawei Technologies Co., Ltd. Container service management method and apparatus
CN112887121A (zh) * 2019-11-29 2021-06-01 北京华为数字技术有限公司 一种管理网络服务的方法、设备及系统
CN112887121B (zh) * 2019-11-29 2022-08-19 北京华为数字技术有限公司 一种管理网络服务的方法、设备及系统
US20220294708A1 (en) * 2019-11-29 2022-09-15 Huawei Technologies Co., Ltd. Method, device, and system for managing network service
US11848831B2 (en) 2019-11-29 2023-12-19 Huawei Technologies Co., Ltd. Method, device, and system for managing network service
WO2021238718A1 (zh) * 2020-05-25 2021-12-02 中兴通讯股份有限公司 一种响应方法、确定方法、装置、设备及介质

Also Published As

Publication number Publication date
CN108370328B (zh) 2020-09-11
CN108370328A (zh) 2018-08-03
EP3419216A1 (en) 2018-12-26
EP3419216A4 (en) 2019-01-23
US10601666B2 (en) 2020-03-24
US20190058636A1 (en) 2019-02-21

Similar Documents

Publication Publication Date Title
WO2017185303A1 (zh) 一种nfv mano策略描述符的管理方法及装置
US11924068B2 (en) Provisioning a service
US10701139B2 (en) Life cycle management method and apparatus
EP3455728B1 (en) Orchestrator for a virtual network platform as a service (vnpaas)
EP3501141B1 (en) A network service design and deployment process for nfv systems
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
KR101932872B1 (ko) 네트워크 기능들 가상화의 관리 및 오케스트레이션을 위한 방법, 디바이스, 및 프로그램
WO2019233273A1 (zh) 管理容器服务的方法和装置
US8769531B2 (en) Optimizing the configuration of virtual machine instances in a networked computing environment
EP3905588A1 (en) Cloud platform deployment method and apparatus, server and storage medium
CN104781783B (zh) 在现有计算环境中部署的集成计算平台
WO2017185251A1 (zh) Vnfm的确定方法和网络功能虚拟化编排器
CN108429768A (zh) 云数据分析服务管理系统、方法和云端服务器
WO2019174000A1 (zh) 用于业务管理的方法和装置
WO2018001091A1 (zh) 虚拟网络功能vnf更新方法、装置和vnf包
CN106134141A (zh) 一种更新网络服务描述器nsd的方法及装置
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
WO2021063130A1 (zh) 网络资源管理方法、系统、网络设备和可读存储介质
KR102168188B1 (ko) 인텐트 기반의 정책구성을 통한 가상 네트워크 인프라의 프로비저닝을 관리하는 방법 및 수행하는 프로그램이 기록된 컴퓨터 판독이 가능한 기록매체 및 그 관리자 및 시스템
CN112889247B (zh) Vnf服务实例化方法及装置
US20210105628A1 (en) Adaptive network slicing via overlaying decomposition and inheritance
WO2023155838A1 (zh) 一种虚拟网络功能vnf实例化的方法及装置
WO2018014351A1 (zh) 一种资源配置方法及装置
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统
WO2023066224A1 (zh) 一种部署容器服务的方法及装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2016899816

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016899816

Country of ref document: EP

Effective date: 20180919

NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16899816

Country of ref document: EP

Kind code of ref document: A1