WO2020063550A1 - 策略决策方法及装置、系统、存储介质、策略决策单元及集群 - Google Patents

策略决策方法及装置、系统、存储介质、策略决策单元及集群 Download PDF

Info

Publication number
WO2020063550A1
WO2020063550A1 PCT/CN2019/107368 CN2019107368W WO2020063550A1 WO 2020063550 A1 WO2020063550 A1 WO 2020063550A1 CN 2019107368 W CN2019107368 W CN 2019107368W WO 2020063550 A1 WO2020063550 A1 WO 2020063550A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
policy decision
management
event
decision
Prior art date
Application number
PCT/CN2019/107368
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 中兴通讯股份有限公司
Publication of WO2020063550A1 publication Critical patent/WO2020063550A1/zh

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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • 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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Definitions

  • the present invention relates to, but is not limited to, the field of communications, and in particular, to but not limited to a method and device for policy decision, a computer-readable storage medium, a policy decision unit, a policy decision cluster, and a network management system.
  • the telecommunications industry has always adopted a vertically integrated architecture on the network architecture of the network management system.
  • the service and network construction is a chimney group method, so new business development and listing cycles are long.
  • O & M costs are high and automated O & M is difficult.
  • 5G 5th Generation
  • SDN Software Defined Network
  • embodiments of the present invention provide a method and device for policy decision, system, storage medium, policy decision unit, and cluster.
  • At least one embodiment of the present invention provides a policy decision unit, which includes a policy engine module and an event theme manager, wherein the policy engine module is used to create a policy engine and use the policy engine to implement at least the following operations: loading policy rules And, when an event sent by the event topic manager is received, a corresponding policy action is triggered according to a policy rule matched by the event; the event topic manager is configured to monitor the event according to the policy rule and receive all When an event is monitored, the event is sent to the policy engine corresponding to the event.
  • At least one embodiment of the present invention provides a policy decision cluster, including at least one policy decision unit according to any one of the embodiments.
  • At least one embodiment of the present invention provides a policy decision method, including: a policy decision unit creates a policy engine and uses the policy engine to load a policy rule; the policy decision unit listens to an event according to the policy rule, and receives the monitored event When the event is sent to the policy engine, the policy engine triggers a corresponding policy action according to the policy rule matched by the event.
  • At least one embodiment of the present invention provides a policy decision device, including a memory and a processor.
  • the memory stores a program.
  • the policy decision according to any one of the embodiments is implemented. method.
  • At least one embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement any The strategy decision method according to an embodiment.
  • At least one embodiment of the present invention provides a network management system, which includes a network function virtualization NFV orchestrator, a virtual network function manager, and a virtualized infrastructure management. It is also characterized in that it further includes the policy decision cluster described above, and the policy decision The cluster is managed independently of the NFV orchestrator, the virtualized network function manager, and the virtualized basic device management.
  • Figure 1 is a network architecture diagram
  • FIG. 2 is a diagram of a MANO (Management and Orchestration, management and orchestration) network architecture (including a policy component) according to an embodiment of the present invention
  • FIG. 3 is a general architecture diagram of a policy component according to an embodiment of the present invention.
  • FIG. 4 is a NFV (Network Function Virtualization) MANO network architecture diagram according to another embodiment of the present invention.
  • FIG. 4 is a NFV (Network Function Virtualization) MANO network architecture diagram according to another embodiment of the present invention.
  • FIG. 5 is a flowchart of loading a policy rule file according to an embodiment of the present invention.
  • 6a is a structural diagram of a policy decision unit according to an embodiment of the present invention.
  • 6b is a structural diagram of a policy decision unit according to another embodiment of the present invention.
  • FIG. 7 is a flowchart of a policy decision method according to an embodiment of the present invention.
  • FIG. 8 is a structural diagram of a policy decision cluster according to an embodiment of the present invention.
  • FIG. 9 is a timing diagram of a policy-based VNF (Virtualized Network Function) expansion provided by an embodiment of the present invention.
  • VNF Virtualized Network Function
  • FIG. 10 is a policy-based VNF shrinking sequence diagram according to an embodiment of the present invention.
  • FIG. 11 is a structural diagram of a VNF fault intelligent self-healing provided by an embodiment of the present invention.
  • FIG. 12 is a block diagram of a policy decision device according to an embodiment of the present invention.
  • FIG. 13 is a block diagram of a computer-readable storage medium according to an embodiment of the present invention.
  • FIG. 14 is a block diagram of a network management system according to an embodiment of the present invention.
  • NFVO NFV Orchestrator, NFV orchestrator
  • VNFM Virtualized Network Function Manager
  • VIM Virtualized Infrastructure Manager
  • NFVO101 is the orchestrator of the NFV system, responsible for the management of network services and the global resource management of NFV.
  • NFVO101 composes network services by orchestrating different VNF (Virtualized Network Function) 104 or VNF104 and PNF (Physical Network Function), and manages VNF104 and NFVI (Network Functions Virtualization Infrastructure) ) 105 resource association and mapping relationship.
  • NFVO101 deployment or operation and maintenance operations are performed based on NS (Network Service) network templates.
  • NFVO101 is generally neutral to the logical functions provided by the NSs it manages / orchestrates. NSs instantiated by NFVO usually do not involve the configuration of logical functions.
  • NFVO101 can monitor network KPIs (Key Performance Indicators), and manage and adjust network services based on KPIs.
  • KPIs Key Performance Indicators
  • One NFVO101 can manage multiple VNFM102 and multiple VIM103 at the same time.
  • VNFM102 management includes traditional fault management, configuration management, billing management, performance management, and security management (FCAPS).
  • VNFM102 focuses on VNF installation, initialization, operation, expansion and reduction, upgrade, and offline of decoupled virtual resources. End-to-end lifecycle management. In the process of VNF life management, VNFM102 can monitor VNF and KPI, and expand and reduce capacity based on KPI indicators.
  • VNFM102 is independent of the logical functions provided by the VNFs it manages / orchestrates. VNFM's management of instantiated VNFs usually does not include the configuration of logical functions. Most VNFM functions are public functions and can be applied to any type of VNF.
  • Each VNF instance has a VNFM102 associated with it; a VNFM102 can be responsible for managing a single VNF instance, or multiple VNF instances of the same or different types.
  • VIM103 is a virtual infrastructure manager, responsible for controlling and managing the computing, storage, and network resources contained in NFVI105, and providing it to VNFM102 and NFVO101 for scheduling and use.
  • a VIM 103 may be designated to manage a certain type of NFVI resources (for example, only compute resources / storage resources / network resources), or it may manage multiple NFVI resources.
  • FIG. 1 further includes OSS (Operation Support System) / BSS (Business Support System) 106 and EM (Element Management) 107.
  • OSS is a support system for telecommunication operator integration and information resource sharing, which is mainly used for network management, system management, billing, business, accounting, and customer service services.
  • BSS is also an integration and information service provider for telecommunications operators.
  • the resource sharing support system is mainly used for services such as customer relationship management, business supply chain management, and business decision support.
  • the EM107 can be used to perform traditional FCAPS functions against VNFs.
  • FIG. 2 is a schematic diagram of a MANO architecture according to an embodiment of the present invention.
  • NFVO / VNFM / VIM implements policy decisions and policy execution.
  • the policy decisions in the policy architecture are implemented.
  • the functions are separated from NFVO / VNFM / VIM, and a separate PDP (Policy, Decision Point, Policy Decision Unit) is set to implement policy decisions.
  • Policy 201 includes policy life cycle management (PLCM) 301, policy decision point (PDP) 302, and policy enforcement point (PEP).
  • PLCM301 is mainly used for the full life cycle management of policies, including the loading of policy templates and the addition, deletion, modification, query, start, stop and suspension of policy rules , Strategic task management, template management, policy query services, and conflict detection and resolution.
  • the policy parameters and template information are received, a policy rule file is generated, the policy rule file is stored in PR304, and description information of the policy rule file is sent to the PDP302.
  • the description information of the policy rule file includes at least one of the following: file name, file description information, event subject information, and resource storage coordinates.
  • the policy rule file contains one or more policy rules.
  • ECA Events-Condition-Condition, Action-Action
  • a policy rule includes a policy event, a policy condition, and a policy action.
  • Strategy action When a policy event occurs and the policy event meets the policy condition, the corresponding execution is performed.
  • the PDP302 is the decision center of the entire system. It is responsible for receiving policy operation requests, making decisions based on the policy information, and then allocating the corresponding execution actions to the PEP to meet the management requirements. Specifically, the PDP302 receives a policy operation request sent by the PLCM301, generates a policy engine, obtains a policy rule file from PR304 according to the description information of the policy rule file carried in the policy operation request, parses the policy rule file to obtain a policy rule, and loads the A policy rule, which listens to an event defined in the policy rule, receives the monitored event, and when the event matches a policy rule (that is, meets a policy condition), triggers a corresponding policy action according to the policy rule matched by the event .
  • the PDP302 is not limited to obtaining the policy rule file from the PR304, it can also directly obtain the policy rule file from the PLCM301, or obtain the policy rule file from other modules, or the PDP302 itself generates a policy rule file or a policy rule, and so on.
  • PEP303 is a network entity that accepts the policy action of PDP302, and is the execution entity of the policy, that is, the response subject of the action. It can also forward information to the PDP so that the PDP is aware of changes in network or device conditions.
  • PEP303 can be any one or more of NFVO, VNFM, and VIM.
  • PEP includes a variety of management resources. The types of resources can include Cloud, Network, and VNF, that is, software and hardware resources on all network nodes. However, each resource needs to provide external access capabilities and register this capability interface to facilitate the design of policy rule files. You can design policies for its interface to achieve the execution results required by users, and then generate and publish corresponding policy templates or specific policy execution packages.
  • PR304 is used to store policy rule files, and can also store resource classification business rule packages, as well as version control of business rules and process models.
  • the solution provided in this embodiment separates the PDP and PEP, provides an independent PDP, and the PDP uniformly processes the policy rules.
  • the Identifying target network elements selected in NFVO / VNFM / VIM to be issued by the policy rule, improving the efficiency of policy execution.
  • the system also includes OSS / BSS205, EM206, VNF207, and NFVI208.
  • the PDP 302 may be one or more, that is, a PDP cluster is formed. Multiple PDP302s are distributed. With the increase of management nodes or resources in the system, there are thousands of policy rules, which will cause performance bottlenecks and single-node failures. Therefore, deploy PDPs in a multi-node manner. The number of PDPs is determined based on the size of the service, such as the number of cells or the number of VNF nodes. Deployed in a cluster mode through PDP, compared to the implementation mode with only a single PDP, it can achieve fast response to concurrent and large-capacity external module requests, and improve the efficiency and stability of policy decision execution.
  • the strategy designer in Figure 3 is VNF, NFVO, etc.
  • PEP303 is performed by NFVO / VNFM / VIM.
  • the policy component 201 includes PLCM301, PDP302, and PR304.
  • a flowchart for loading a policy rule file includes: Step 501, a PLCM receives an operation request of OSS / BSS or NFVO, the operation request includes policy parameters and template information; step 502, the PLCM checks The policy parameter, generating a policy rule file according to the policy parameter and template information, and storing the policy rule file in a policy repository; step 503, the PLCM generates a policy operation request, and the policy operation request carries a policy rule file
  • the description information of the policy rule file includes at least one of the following: file name, file description information, event subject information, and resource storage coordinates.
  • PLCM can also modify, delete, and so on the policy rule file in the policy repository, and then generate a policy operation request.
  • step 504 the PLCM sends the policy operation request to the PDP.
  • step 505 the PDP receives the policy operation request, and according to the resource storage coordinates in the description information of the policy rule file in the policy operation request,
  • the policy repository obtains a policy rule file, parses the policy rule file to obtain a policy rule, forms a policy rule tree in memory, and registers and listens to events according to events in the policy rule.
  • the PDP is responsible for making policy decisions for the policy operation requests of external modules. Specifically, it receives policy operation requests from external modules and finds relevant policy rules that match the policy operation requests in the published policy rule base. File, and load the successfully matched policy rule file into the PEP, and pass the specific execution to the PEP according to the policy action in the policy rule, and let the PEP perform the relevant operation.
  • FIG. 6a is a PDP architecture diagram provided by an embodiment of the present invention.
  • the PDP includes a policy engine module 601 and an event theme manager 602, and an external interface.
  • the policy engine module 601 is configured to create a policy engine, and use the policy engine to implement the following operations: loading a policy rule and, upon receiving an event sent by the event topic manager, a policy matched according to the event The rule triggers the corresponding policy action; it is also used to manage the life cycle of the policy engine; the event topic manager 602 is used to listen to the event according to the policy rule, and when the event is received, send the event to the policy engine corresponding to the event .
  • Policy rules include events, conditions, and actions. Therefore, events have corresponding policy rules, and the policy engine corresponding to the event is the policy engine that loads the policy rules corresponding to the event.
  • Figure 6a also includes multiple interfaces: a PDP management interface 603 (a resource of a PDP node), a theme management interface 604, and an engine management interface 605 (a policy rule file).
  • the PDP management interface 603 is used to manage the resources of the PDP node
  • the theme management interface 604 is used to listen to events, receive events, etc.
  • the engine management interface 605 is used to transmit information related to the policy engine, for example, to receive policy operation requests,
  • the message middleware 606 in FIG. 6a refers to a message forwarding unit when a policy action is triggered to send a message to the PEP.
  • the basic mechanism of the policy engine is: to retrieve the currently submitted event, and match the loaded policy rule with the current attribute value of each data object in the event and the relationship between them, and find a matching (compliant with the policy conditions) policy rule , Trigger the corresponding action according to the Action declared in the policy.
  • the policy engine needs to update it in time according to the policy rule file.
  • the policy engine and policy rules are in a one-to-many relationship, that is, one policy engine can load multiple policy rules.
  • the PDP and the policy engine are in a one-to-many relationship, that is, multiple policy engines can be created in a PDP.
  • policy engines and policy rules, policy engines and PDPs can also be one-to-one.
  • the policy engine module 601 creating a policy engine includes: receiving a policy operation request sent by a policy lifecycle management, and creating a policy engine.
  • the loading of the policy rule includes: obtaining a policy rule file from a policy repository according to the description information of the policy rule file carried in the policy operation request, and parsing the policy rule file to obtain a policy rule.
  • the policy rules may not be obtained from the policy repository, for example, when the policy operation request carries the policy rules, the policy rules are directly loaded. Alternatively, the PDP itself generates and loads policy rules, and so on.
  • the PDP further includes a cluster management module 607 and a communication interface 608, and the cluster management module 607 is configured to determine a location when the PDP is a management node of a policy decision cluster. Whether the PDP in the policy decision cluster can be used as a backup PDP for other PDPs, and when the PDP in the policy decision cluster is unavailable, use the backup PDP to replace the unavailable PDP.
  • the communication interface 608 is used for interaction between PDPs.
  • the cluster management module 607 is further configured to periodically select a management node of a policy decision cluster.
  • the algorithm for selecting a management node may be determined according to requirements, which is not limited in this application. For example, select the lowest dictionary value (the dictionary value is the order in the dictionary, the dictionary order is a, b, c ..., and the corresponding dictionary values increase in order. In this embodiment, the dictionary value of the first letter of the PDP logo is used) PDP as the management node. This is just an example. You can use other election algorithms, inxS election.
  • a management node can be selected for PDPs for each policy language. That is, multiple management nodes can be selected, and each management node manages PDPs of the same policy language. It should be noted that this is only an example, and only one management node can be selected.
  • the election cycle can be set as required. In addition, it may not be a periodic election, but an election when triggered, or an election when a user instruction is received. Alternatively, you can specify the management node directly, and so on. It should be noted that the management node may not be elected in the policy decision cluster, and other cluster management methods are used for management, which is not limited in this application. For example, use highly reliable servers to manage policy decision clusters, and so on.
  • the management node of the periodic decision-making policy decision cluster includes: periodically selecting the management node of the policy decision cluster according to the information in the management entity table, wherein the management entity table includes at least one of the following: First: the identification, resource name, management status, availability status, active / standby status, and creation and modification time information of the policy decision unit.
  • a policy decision method includes: Step 701, a PDP creates a policy engine, and uses the policy engine to actually load policy rules; step 702, the PDP listens to events according to the policy rules When the monitored event is received, the event is sent to the policy engine, and the policy engine triggers a corresponding policy action according to a policy rule matched by the event.
  • the policy engine creation includes: receiving a policy operation request sent by a policy lifecycle management, and creating a policy engine. It should be noted that a policy engine can also be created after receiving policy operation requests from other modules. For example, a policy operation request is received from NFVO.
  • the loading of the policy rule includes: obtaining a policy rule file from a policy repository according to the description information of the policy rule file carried in the policy operation request, and parsing the policy rule file to obtain a policy rule.
  • the event includes a policy action triggered when other policy decision units match a policy rule.
  • the method further includes, when the PDP is a management node of a policy decision cluster, determining whether a PDP in the policy decision cluster can be used as a backup PDP for other PDPs, and when the policy decision is made When the PDP in the cluster is unavailable, the spare PDP is used to replace the unavailable PDP.
  • the method further includes that the PDP periodically elects a management node of a policy decision cluster based on information in the shared management entity table.
  • the management entity table includes at least one of the following: an identifier of the policy decision unit, a resource name, a management status, an available status, an active / standby status, and creation and modification time information.
  • an embodiment of the present invention provides a policy decision cluster 80 including at least one PDP 302 described in the foregoing embodiment.
  • There is a communication interface between PDPs in this policy decision cluster and communication is based on the PDP communication protocol.
  • the policy rules are distributed in multiple PDPs. The same events are monitored for the association of policies, and the policy actions are associated through the PDP communication interface.
  • the application of the NFV MANO strategy is based on the separation of each strategy, and there is no policy association.
  • a policy association trigger is implemented through a PDP communication interface, thereby improving decision-making efficiency.
  • policies can be written in multiple languages. Therefore, if cross-language policy execution is required, it is necessary to cooperate between policy execution bodies of cross-language language types through message methods. In addition, PDPs with the same policy language will be based on the actual situation. The CPU load rate, memory usage rate and other indicators perform scheduling through the message mode.
  • the PDP communication protocol is a protocol used to communicate with each other to manage state and deployment.
  • the purpose of the interface is mainly to coordinate processing between PDPs, complete the operation of policy association, and solve the association and cooperation process between different policies.
  • the communication interfaces between PDPs include at least one of the following: Intra-PDP Interface (Inter-PDP Interface) and Inter-PDP Interface (PDP Interface) two communication interfaces.
  • Inter-PDP Interface is a protocol that any instance of PDP type can use to communicate with each other to manage status and deployment.
  • Intra-PDP Interface is a protocol within PDP that is used to communicate with each other to manage status and deployment. protocol.
  • a state management entity table (StateManagementEntity) is provided, and the table stores at least one of the following: the identity of the PDP (such as the IP of the PDP), the name of the resource (that is, the name of the PDP, such as a name displayed to the user for viewing) ), Management status (that is, whether the PDP is a management node), availability status, active / standby status, and creation and modification time information.
  • the available status indicates whether the PDP is available, the PDP is available when it is connected, the unavailable status is unavailable, and the active / standby status indicates whether the PDP can be used as a standby PDP for other PDPs.
  • the meaning of the standby PDP is that when a PDP fails, the function performed by the standby PDP can be replaced by the standby PDP.
  • the backup PDP loads the data on the failed PDP (loaded from the database shared by each PDP) and executes it.
  • the creation modification time information is the creation modification time of the piece of information. All PDPs share the management entity table and periodically update the status information (management status, available status, active / standby status) in the management entity table.
  • All PDPs in the PDP cluster periodically run the election algorithm (of course, the election algorithm can also be run after being triggered). Because each PDP uses the same data (data in the shared state management entity table), all PDP elections Out the same management node. Among them, the management status of the selected PDP is updated to the active status (or the service status is provided, and the node in this status is the management node in the cluster). Therefore, the algorithm is distributed with no single point of failure, assuming the database is configured for high availability.
  • a shared PDP entity table (PdpEntity) is also provided.
  • the PdpEntity table records whether a node's election algorithm is currently running and the time when the node was last designated as a management node.
  • the status of all PDPs is collected regularly. Each node reads the standbystatus (that is, status information) of all other nodes from the StateManagementEntity table.
  • the standbystatus that is, status information
  • For a PDP running an election algorithm if the PDP is currently elected as the management node and was already the management node before the election, no action is required. If it is currently elected as the management node and was not the management node before the election, modify the status of the PDP to be active; if it is not elected as the management node, no operation is performed.
  • the PDP can be set to the hotstandby state (for example only, other states can also be set). If the selected PDP is itself, it will change from the hotstandby state to the active state. If the chosen PDP is not itself, it will do nothing.
  • a state change notification will occur and the state change handler will take appropriate action.
  • a shared policy module is constructed between OSS / BSS and MANO.
  • the policy decision unit is proposed separately, the policy decision unit is deployed in a cluster, and the policy decision is made.
  • Units provide communication protocols to better implement the current policy transition between 3 / 4G and 5G, and are well compatible with the management of original network equipment, improving the efficiency of NFVO's policy execution.
  • the network service auto-scaling policy is provided by VNF (that is, VNF as the designer) and implemented by VNFM (as PEP).
  • VNF that is, VNF as the designer
  • VNFM as PEP
  • a policy designer that is, VNF
  • designs an automatic expansion strategy binds a given type of VNF through PLCM, encapsulates it in policy information, and delivers it to a PDP.
  • An example of an automatic expansion strategy may include the following information: If a change in the first index value of a VNF is detected, the VNF instance is expanded according to a given action.
  • the first index value can be set according to requirements, which is not limited in this application.
  • the monitoring indicator information of the VNF instance is reported to the specified analyzer (for example, Performance Management (PM)).
  • PM Performance Management
  • the PDP obtains the first indicator information from the analyzer, matches the first indicator information with the current capacity expansion strategy, and VNFM serves as the PEP. To ultimately execute the decision. See Figure 9 for details, including: Step 901, the PDP creates a policy engine after receiving the policy operation request sent by PLCM; among them, after PLCM receives the policy parameters and template information sent by NFVO, it creates a policy rule file to save to PR and sends the policy operation The request is sent to the PDP.
  • the policy operation request carries the description information of the policy rule file.
  • the PDP After receiving the policy operation request, the PDP downloads the policy rule file from the PR according to the description information of the policy rule file carried in the policy operation request. What needs to be explained is in other embodiments, the PDP may also directly receive the policy parameters and template information sent by the NFVO to create a policy rule file.
  • the PDP uses the policy engine to load a policy rule file and parse the policy rule file to obtain a policy rule.
  • the PM collects the value of the virtual resource counter of the VIM to obtain a first indicator.
  • the PDP subscribes to the first An indicator change event; specifically, the PDP's event theme manager subscribes to the PM's first indicator change event and receives the first indicator change event; step 905, the event theme manager sends the first indicator change event to the policy engine module; steps 906.
  • the policy engine module receives the first indicator change event and matches the expansion rule, that is, the change of the first indicator triggers the expansion rule in the PDP.
  • Step 907 the policy engine module initiates a capacity expansion request to the NFVO according to the policy action in the capacity expansion rule.
  • Step 908 the NFVO checks the capacity expansion request after receiving the capacity expansion request; step 909, after the verification is passed, the NFVO initiates a VNF instantiation request to the VNFM; step 910, the VNFM receives the VNF instance After the request is parsed, the VNFD (Virtualization Network Functions Descriptor) is parsed to obtain Deploy the virtual resources required for VNF to generate a capacity expansion resource list; step 911, the VNFM returns a capacity expansion resource list to NFVO; step 912, the NFVO sends a VNF capacity expansion event to the PDP, and specifically, to the PDP's policy engine module; step 913 After receiving the VNF capacity expansion event, the PDP matches the resource rule; step 914, sends a capacity expansion request to the NFVO according to the policy action in the resource rule; step 915, after receiving the capacity expansion request, the
  • step 916 decides to accept the request for performing the expansion, and request resource allocation from the VIM, that is, send a resource allocation request to the VIM; step 916, the VIM creates a virtual machine after receiving the resource allocation request of the NFVO; step 917, VIM returns the resource allocation result to NFVO; step 918, NFVO sends a resource configuration completion notification to VNFM; step 919, VNFM configures VNF according to the template requirements for application deployment and parameter configuration; step 920, VNFM notifies NFVO to complete VNF instantiation; step 921 , NFVO sends a capacity expansion completion event to the PDP to complete the closed loop of VNF automatic capacity expansion.
  • Network service auto-scaling policy (NS, Auto-scaling policy) is provided by VNF (that is, VNF as the designer) and implemented by VNFM (that is, VNFM as the PEP).
  • VNF Network service auto-scaling policy
  • VNFM that is, VNFM as the PEP
  • the policy designer (that is, VNF) designs an automatic shrinking policy, binds a given type of VNF through PLCM, encapsulates it in policy information, and delivers it to a PDP.
  • An example of an automatic shrinking strategy may include the following information: If changes in some VNF index values are detected, then VNF instance shrinking is performed according to a given action. Specific index values can be set as required, which is not limited in this application.
  • the specified analyzer is reported to the monitoring indicator information of the VNF instance.
  • the PDP obtains the indicator information from the analyzer, matches the indicator information with the current capacity reduction strategy, and VNFM acts as the PEP to finally execute the decision result. See Figure 10 for details, including: Step 1001:
  • the PDP receives the policy operation request sent by PLCM and creates a policy. Among them, after PLCM receives the policy parameters and template information sent by NFVO, it creates a policy rule file to save to PR and sends a policy operation request. To the PDP, the policy operation request carries the description information of the policy rule file. After receiving the policy operation request, the PDP downloads the policy rule file from the PR according to the description information of the policy rule file carried in the policy operation request.
  • Step 1002 the PDP uses The policy engine loads a policy rule file, parses the policy rule file to obtain a policy rule; step 1003, the VNFM uses a notification of the performance management interface of the VNF / VIM or obtains a performance criterion operation to obtain a specific VNF measurement index; step 1004, a PDP
  • the event topic manager subscribes to the VNF measurement index event of VNFM and receives the VNF measurement index event; step 1005, the event topic manager of the PDP sends the VNF measurement index time to the policy engine; step 1006, the policy engine module receives the VNF measurement index time To match the shrinking rule and determine to execute the shrinking; step 1007 ,
  • the PDP initiates a reduction request to NFVO; step 1008, after receiving the reduction request, NFVO verifies the reduction request; step 1009, after the verification is passed, the NFVO sends a VNF reduction request to VNFM, so
  • the VNF scaling request carries VNFD; step 1010, after receiving the VNF scaling
  • the solution provided in this embodiment implements automatic shrinkage by interacting with the PDP.
  • VNF alarm automation is implemented based on policies. By setting policies, certain alarms are automatically analyzed and resolved, thereby achieving intelligent alarm self-healing and reducing operation and maintenance costs.
  • the system includes an alarm collection module 1101, an alarm root cause analysis module 1102, a machine rule learning module 1103, a policy center 1104, and an intelligent script library 1105.
  • the policy center 1104 includes PLCM, PDP, and PR, of which:
  • the collection module 1101 is configured to collect a virtual resource alarm of the VIM and report the alarm root cause analysis module 1102 based on the NFVO alarm subscription request and from the perspective of VNF.
  • the alarm root cause analysis module 1102 is used to correlate VNF alarms, virtual resource alarms, and physical resource alarms from the perspective of VNF; analyze the alarms, and send the alarms that can be automatically repaired to the Policy Center 1104; for those that cannot be automatically repaired Alarms, manual processing;
  • the machine rule learning module 1103 is configured to provide an analysis model and a policy rule by analyzing historical alarms through big data machine learning, and the policy rule includes a self-healing rule; for example, analyzing the proportion of flash alarms with a short life cycle by analyzing historical alarms Situation, by analyzing historical alarms to analyze the periodically occurring alarm conditions.
  • the policy center 1104 is responsible for triggering a policy.
  • the action in the policy rule is triggered.
  • the actions include calling a script library of the intelligent script platform 1105.
  • the policy rules include self-healing rules, which are derived from field customization, expert experience import, and machine rule learning modules.
  • the self-healing rules of the policy center and the script library of the intelligent script platform are used to heal. After the self-healing is successful, the alarm is reported on the network element to recover, so Realize intelligent self-healing of alarms and reduce operation and maintenance costs.
  • an embodiment of the present invention provides a policy decision device 120, which includes a memory 121 and a processor 122.
  • the memory 121 stores a program.
  • the program is read and executed by the processor 122, Implement the policy decision method described in any of the embodiments.
  • an embodiment of the present invention provides a computer-readable storage medium 130.
  • the computer-readable storage medium 130 stores one or more programs 131.
  • the one or more programs 131 may be stored in one or more programs 131.
  • Multiple processors execute to implement the policy decision method described in any embodiment.
  • An embodiment of the present invention provides a network management system.
  • the network management system includes NFVO201, VNFM202, and VIM203, and further includes a policy decision cluster 80 according to any one of the foregoing embodiments.
  • the policy decision cluster is independent of the NFVO201, VNFM202, VIM203.
  • the method further includes: PLCM301 and PR304, wherein the PLCM301 is configured to generate a policy rule file after receiving the policy parameters and template information, store the policy rule file in a policy repository, and send a carry policy
  • the policy operation request of the description information of the rule file is requested to a policy decision unit in the policy decision cluster; the PR304 is configured to store the policy rule file.
  • computer storage medium includes volatile and non-volatile implemented in any method or technology used to store information such as computer-readable instructions, data structures, program modules or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer.
  • a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

Abstract

一种策略决策方法及装置、系统、存储介质、策略决策单元及集群。所述策略决策单元包括策略引擎模块和时间主题管理器，其中，所述策略引擎模块用于创建策略引擎，使用所述策略引擎至少实现如下操作：加载策略规则，以及，接收到所述事件主题管理器发送的事件时，根据所述事件匹配到的策略规则触发对应的策略动作；所述事件主题管理器根据所述策略规则监听事件，接收到所监听的事件时，将该事件发送给该事件对应的所述策略引擎。

Description

策略决策方法及装置、系统、存储介质、策略决策单元及集群
交叉引用
本发明要求在2018年9月30日提交中国专利局、申请号为201811162422.3、发明名称为“策略决策方法及装置、系统、存储介质、策略决策单元及集群”的中国专利申请的优先权，该申请的全部内容通过引用结合在本发明中。
技术领域
本发明涉及但不限于通信领域，尤其涉及但不限于一种策略决策方法及装置、计算机可读存储介质、策略决策单元及策略决策集群、网管系统。
背景技术
电信业在网管系统的网络架构上一直沿用垂直一体化的架构，业务和网络构建是烟囱群方式，因此新业务开发和上市周期长。与IT厂商相比，运维成本高，自动化运维困难。随着5G(5th Generation，第五代)的基于SDN(Software Defined Network，软件定义网络)理念重新定义网络架构，通过网络功能和节点虚拟化，然后在其基础上实现网络按需快速部署、按需编排组织物理资源，从而灵活的实现各个层次的网络功能。
发明内容
有鉴于此，本发明实施例提供了一种策略决策方法及装置、系统、存储介质、策略决策单元及集群。
本发明至少一实施例提供一种策略决策单元，包括策略引擎模块和事件主题管理器，其中：所述策略引擎模块用于，创建策略引擎，使用所述策略引擎至少实现如下操作：加载策略规则，以及，接收到所述事件主题管理器 发送的事件时，根据所述事件匹配到的策略规则触发对应的策略动作；所述事件主题管理器用于，根据所述策略规则监听事件，接收到所监听的事件时，将该事件发送给该事件对应的所述策略引擎。
本发明至少一实施例提供一种策略决策集群，包括至少一个任一实施例所述的策略决策单元。
本发明至少一实施例提供一种策略决策方法，包括：策略决策单元创建策略引擎，使用所述策略引擎加载策略规则；所述策略决策单元根据所述策略规则监听事件，接收到所监听的事件时，将所述事件发送到所述策略引擎，由所述策略引擎根据所述事件匹配到的策略规则触发对应的策略动作。
本发明至少一实施例提供一种策略决策装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现任一实施例所述的策略决策方法。
本发明至少一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现任一实施例所述的策略决策方法。
本发明至少一实施例提供一种网管系统，包括网络功能虚拟化NFV编排器、虚拟化网络功能管理器、虚拟化基础设施管理，其特征在于，还包括：上述策略决策集群，所述策略决策集群独立于所述NFV编排器、所述虚拟化网络功能管理器和所述虚拟化基础设备管理。
附图说明
附图用来提供对本发明技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本发明的技术方案，并不构成对本发明技术方案的限制。
图1为一种网络架构图；
图2为本发明一实施例提供的MANO(Management and Orchestration， 管理与编排)网络架构图(包括策略组件)；
图3为本发明一实施例提供的策略组件通用架构图；
图4为本发明另一实施例提供的NFV(Network Function Virtualization，网络功能虚拟化)MANO网络架构图；
图5为本发明一实施例提供的策略规则文件加载流程图；
图6a为本发明一实施例提供的策略决策单元架构图；
图6b为本发明另一实施例提供的策略决策单元架构图；
图7为本发明一实施例提供的策略决策方法流程图；
图8为本发明一实施例提供的策略决策集群架构图；
图9为本发明一实施例提供的一种基于策略的VNF(Virtualized Network Function，虚拟网络功能)扩容时序图；
图10为本发明一实施例提供的一种基于策略的VNF缩容时序图；
图11为本发明一实施例提供的一种VNF故障智能自愈的结构图；
图12为本发明一实施例提供的一种策略决策装置框图；
图13为本发明一实施例提供的计算机可读存储介质框图；
图14为本发明一实施例提供的网管系统框图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚明白，下文中将结合附图对本发明的实施例进行详细说明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
先对一种标准架构(如MANO架构)进行说明。如图1所示，MANO架构包含了NFVO(NFV Orchestrator，NFV编排器)101、VNFM(Virtualized Network Function Manager，虚拟化网络功能管理器)102、VIM(Virtualized  Infrastructure Manager，虚拟化基础设施管理)103，功能说明如下：NFVO101是NFV系统的编排器，负责网络服务的管理和NFV的全局资源管理。NFVO101通过编排不同的VNF(Virtualized Network Function，虚拟网络功能)104或VNF104与PNF(Physical Network Function，物理网络功能)组成网络服务，并管理VNF104与NFVI(Network Functions Virtualization Infrastructure，网络功能虚拟化基础设施)105资源的关联和映射关系。NFVO101的部署或运维操作都基于NS(Network Service，网络服务)模板进行。NFVO101通常中立于其所管理/编排的NS所提供的逻辑功能，NFVO实例化的NS通常不涉及逻辑功能的配置。网络服务生命周期管理过程中，NFVO101可以对网络KPI(Key Performance Indicator，关键性能指标)进行监控，并依据KPI指标进行网络服务的管理和调整。一个NFVO101可以同时管理多个VNFM102和多个VIM103。
VNFM102管理包括传统的故障管理、配置管理、计费管理、性能管理和安全管理(FCAPS)，VNFM102聚焦在将VNF在解耦的虚拟资源上安装、初始化、运行、扩缩容、升级、下线的端到端生命周期管理。VNF生命管理过程中，VNFM102可以对VNF KPI进行监控，并依据KPI指标进行扩缩容。VNFM102独立于其所管理/编排的VNF所提供的逻辑功能，VNFM针对实例化VNF的管理通常不包含逻辑功能的配置。大多数VNFM功能是公共功能，可应用于任何类型VNF。然而，NFV MANO架构也需要支持VNF实例生命周期管理需要的定制功能，定制可作为VNF服务包的一部分进行发布。每个VNF实例都有一个与之相关的VNFM102；一个VNFM102可以负责管理一个单独的VNF实例，或者多个相同或不同类型的VNF实例。
VIM103是虚拟基础设施管理器，负责控制和管理NFVI105所包含的计算、存储和网络资源，并提供给VNFM102和NFVO101调度使用。一个VIM103可能被指定管理某一特定类型的NFVI资源(例如，只管理计算资源/存储资源/网络资源)，也可以管理多种NFVI资源。
另外图1中还包括OSS(Operation Support System，运营支撑系统)/BSS(Business Support System，业务支撑系统)106和EM(Element Management，网元管理)107。其中，OSS是电信运营商的一体化、信息资源共享的支持系统，主要用于网络管理、系统管理、计费、营业、账务和客户服务等服务，BSS也是电信运营商的一体化、信息资源共享的支持系统，主要用于客户关系管理、业务供应链管理和经营决策支持等服务。EM107可以用于针对VNF执行传统的FCAPS功能。
图2为本发明一实施例提供的一种MANO架构示意图。主要在MANO原有网络架构基础上，对策略架构进行扩展和改进，在一种方案中，由NFVO/VNFM/VIM实现策略决策，策略执行，而本实施例中，将策略架构中的策略决策功能从NFVO/VNFM/VIM中剥离，设置单独的PDP(Policy Decision Point，策略决策单元)实现策略决策。如图2，3所示，Policy(策略组件)201包含了PLCM(Policy Life Cycle Management，策略生命周期管理)301、PDP(Policy Decision Point，策略决策单元)302、PEP(Policy Enforcement Point，策略执行点)303和PR(Policy Repository，策略存储库)304，其中：PLCM301主要用于策略的全生命周期管理，包括策略模板的加载以及策略规则的增加、删除、修改、查询、启动、停止和暂停，策略任务管理、模板管理、策略查询服务以及冲突混淆检测以及解决等。具体的，接收策略参数和模板信息，生成策略规则文件，将所述策略规则文件存储到PR304，并发送策略规则文件的描述信息给PDP302。所述策略规则文件的描述信息包括以下至少之一：文件名称、文件描述信息、事件主题信息、资源仓储坐标。其中，策略规则文件包含一条或多条策略规则。策略规则的基本模型为ECA(Events-事件、Condition-条件、Action-动作)，即策略规则包括策略事件、策略条件和策略动作，当发生策略事件，且该策略事件满足策略条件，则执行相应的策略动作。
PDP302为整个系统的决策中心，负责接收策略操作请求，并根据策略信 息做出决策，然后将相应的执行动作分配至PEP，以达到管理需求。具体的，PDP302接收PLCM301发送的策略操作请求，生成策略引擎，根据策略操作请求中携带的策略规则文件的描述信息，从PR304获取策略规则文件，解析所述策略规则文件获得策略规则，加载所述策略规则，监听所述策略规则中定义的事件，接收到所监听的事件，且所述事件匹配到策略规则(即符合策略条件)时，根据所述事件匹配到的策略规则触发对应的策略动作。需要说明的是，PDP302不限于从PR304获取策略规则文件，也可以直接从PLCM301获取策略规则文件，或者，从其他模块获取策略规则文件，或者，PDP302自身生成策略规则文件或策略规则，等等。
PEP303是接受PDP302的策略动作的网络实体，是策略的执行实体，即action的响应主题。它还可以向PDP转发信息，以使PDP了解网络或设备条件的变化。PEP303可以是NFVO、VNFM、VIM中的任一个或多个。PEP包含多种管理资源，其资源种类可包括Cloud、Network、VNF即所有网络节点上的软硬件资源，但是需要各个资源提供对外访问能力，以及注册该能力接口，以便于策略规则文件设计时，可以针对其接口进行策略设计以达到用户需要的执行结果，然后生成发布对应的策略模板或者具体的策略执行包。
PR304用于存储策略规则文件，还可存储资源分类业务规则包，以及业务规则和流程模型的版本控制等等。
本实施例提供的方案，将PDP和PEP进行分离，提供独立的PDP，由PDP统一对策略规则进行处理，相比由NFVO/VNFM/VIM充当PDP和PEP的方案，本实施例中，则无需分辨策略规则待下发的目标网元(在NFVO/VNFM/VIM中选择)，提高了策略执行效率。
该系统中还包括OSS/BSS205，EM206、VNF207和NFVI208，其功能参考图1中相应模块的描述，此处不再赘述。在一实施例中，所述PDP302可以是一个或多个，即形成PDP集群。多个PDP302分布式分布。随着系统中管理节点或资源的增加，策略规则有成千上万个，会产生性能瓶颈问题和单 节点故障问题，因此，以多节点的方式部署PDP。PDP数目根据业务规模来决定，如小区规模数，或VNF节点数。通过PDP的集群方式部署，相比只有单个PDP的实现方式，可以实现并发和大容量外部模块请求的快速响应，提升策略决策执行的效率和稳定性。
图3中策略设计器比如为VNF，NFVO等等。
在一实施例中，如图4所示，PEP303由NFVO/VNFM/VIM充当，此时策略组件201中包含PLCM301、PDP302和PR304。
如图5所示，为策略规则文件加载流程图，包括：步骤501，PLCM接收OSS/BSS或NFVO的操作请求，所述操作请求包括策略参数、模板信息；步骤502，所述PLCM校验所述策略参数，根据所述策略参数和模板信息生成策略规则文件，将所述策略规则文件存储于策略存储库；步骤503，所述PLCM生成策略操作请求，所述策略操作请求中携带策略规则文件的描述信息；所述策略规则文件的描述信息包括以下至少之一：文件名称、文件描述信息、事件主题信息、资源仓储坐标。
需要说明的是，PLCM也可对策略存储库中的策略规则文件进行修改，删除等，然后生成策略操作请求。
步骤504，所述PLCM发送所述策略操作请求至PDP；步骤505，所述PDP接收到所述策略操作请求后，根据所述策略操作请求中的策略规则文件的描述信息中的资源仓储坐标从所述策略存储库获取策略规则文件，解析所述策略规则文件获取策略规则，在内存中形成策略规则树；根据所述策略规则中的事件，注册并监听事件。
PDP作为策略系统的决策中心，负责针对外部模块的策略操作请求进行策略决策工作，具体的，接收外部模块的策略操作请求，在已发布的策略规则库中查找匹配该策略操作请求的相关策略规则文件，并将匹配成功后的策略规则文件加载到PEP内，根据策略规则中的策略动作将具体执行传递给PEP，让PEP执行相关操作。
图6a为本发明一实施例提供的PDP架构图。如图6a所示，PDP包括策略引擎模块601和事件主题管理器602，以及对外接口。其中：所述策略引擎模块601用于，创建策略引擎，使用所述策略引擎实现如下操作：加载策略规则以及，接收到所述事件主题管理器发送的事件时，根据所述事件匹配到的策略规则触发对应的策略动作；还用于管理策略引擎的生命周期；所述事件主题管理器602用于，根据策略规则监听事件，接收到事件时，将所述事件发送给该事件对应的策略引擎。需要说明的是，当事件发送到事件主题时，也可以通过监听事件主题达到监听事件的目的。策略规则包括事件、条件和动作，因此，事件有对应的策略规则，事件对应的策略引擎即加载事件对应的策略规则的策略引擎。
图6a中还包括多个接口：PDP管理接口603(PDP节点的资源)、主题管理接口604和引擎管理接口605(策略规则文件)。其中，PDP管理接口603用于对PDP节点的资源进行管理，主题管理接口604用于监听事件，接收事件等，引擎管理接口605用于策略引擎相关的信息的传输，比如，接收策略操作请求，接收策略规则文件等等，图6a中的消息中间件606是指触发策略动作发送消息至PEP时的消息转发单元。
策略引擎的基本机制是：对当前提交的事件进行检索，根据事件中各数据对象的当前属性值和它们之间的关系，与加载的策略规则进行匹配，发现匹配(符合策略条件)的策略规则，根据策略中声明的Action，触发对应的操作。当策略存储库中的策略规则文件改变时，策略引擎需要及时根据该策略规则文件进行更新。
其中，策略引擎和策略规则是一对多的关系，即一个策略引擎可以加载多条策略规则。PDP和策略引擎是一对多的关系，即一个PDP中可创建多个策略引擎。当然，策略引擎和策略规则、策略引擎和PDP也可以一对一。
在一实施例中，所述策略引擎模块601创建策略引擎包括：接收策略生命周期管理发送的策略操作请求，创建策略引擎。
在一实施例中，所述加载策略规则包括：根据所述策略操作请求中携带的策略规则文件的描述信息，从策略存储库中获取策略规则文件，解析所述策略规则文件获取策略规则。需要说明的是，也可以不从策略存储库中获取策略规则，比如，当策略操作请求中携带策略规则时，直接加载策略规则。或者，PDP自身生成策略规则并加载，等等。
如图6b所示，在一实施例中，所述PDP还包括集群管理模块607和通信接口608，所述集群管理模块607用于，当所述PDP为策略决策集群的管理节点时，确定所述策略决策集群中的PDP是否可作为其他PDP的备用PDP，以及，当所述策略决策集群中的PDP不可用时，使用所述备用PDP替代不可用的PDP。
如果可以作为备用PDP，记录其状态为coldstandby(冷备份)状态，如果不可以作为备用PDP，记录其状态为hotstandby(热备份)状态，此处仅为示例，可用其他信息指示是否可作为备用PDP。其中，判断是否可作为备用PDP可以根据PDP的性能和负荷(cpu负荷率、内存占用率等)等等确定。可以将状态信息记录在一状态管理实体表(StateManagementEntity)中，各PDP共享该状态管理实体表。通信接口608用于PDP间的交互。
在一实施例中，所述集群管理模块607还用于，周期性选举确定策略决策集群的管理节点。
其中，选举管理节点的算法可根据需要确定，本申请对此不作限定。比如，选择具有最低字典值(字典值即在字典中的顺序，字典顺序为a,b,c…，相应的字典值依次增大，本实施例中，使用PDP标识的首字母的字典值)的PDP作为管理节点。此处仅为示例，可以使用其他选举算法inxS选举。
另外，当存在多种策略语言的PDP时，可以为每种策略语言的PDP选择一个管理节点。即可以选取多个管理节点，每个管理节点管理同一策略语言的PDP。需要说明的是，此处仅为示例，可以只选取一个管理节点。
其中，选举周期可根据需要设定。另外，也可以不是周期性的选举，而 是被触发时进行选举，或者，接收到用户指令时进行选举。另外，也可以直接指定管理节点，等等。需要说明的是，策略决策集群中也可不选举管理节点，采用其他集群管理方法进行管理，本申请对此不作限定。比如，使用高可靠性的服务器对策略决策集群进行管理，等等。
在一实施例中，所述周期性选举确定策略决策集群的管理节点包括：根据管理实体表中的信息周期性选举确定策略决策集群的管理节点，其中，所述管理实体表中包括如下至少之一：所述策略决策单元的标识、资源名称、管理状态、可用状态、主备状态、创建修改时间信息。
如图7所示，本发明一实施例一种策略决策方法，包括：步骤701，PDP创建策略引擎，使用所述策略引擎实加载策略规则；步骤702，所述PDP根据所述策略规则监听事件，接收到所监听的事件时，将所述事件发送到所述策略引擎，由所述策略引擎根据所述事件匹配到的策略规则触发对应的策略动作。
在一实施例中，所述创建策略引擎包括：接收策略生命周期管理发送的策略操作请求，创建策略引擎。需要说明的是，也可以在接收到其他模块的策略操作请求后，创建策略引擎。比如，接收到NFVO的策略操作请求。
在一实施例中，所述加载策略规则包括：根据所述策略操作请求中携带的策略规则文件的描述信息，从策略存储库中获取策略规则文件，解析所述策略规则文件获取策略规则。
在一实施例中，所述事件包括其他策略决策单元匹配到策略规则时触发的策略动作。
在一实施例中，所述方法还包括，当所述PDP为策略决策集群的管理节点时，确定所述策略决策集群中的PDP是否可作为其他PDP的备用PDP，以及，当所述策略决策集群中的PDP不可用时，使用所述备用PDP替代不可用的PDP。
在一实施例中，所述方法还包括，所述PDP根据共享的管理实体表中的 信息周期性选举确定策略决策集群的管理节点。
在一实施例中，所述管理实体表中包括如下至少之一：所述策略决策单元的标识、资源名称、管理状态、可用状态、主备状态、创建修改时间信息。
如图8所示，本发明一实施例提供一种策略决策集群80，包括至少一个上述实施例中所述的PDP302。该策略决策集群中的PDP之间存在通信接口，基于PDP通信协议进行通信。策略规则分布在多个PDP中，监听同一事件实现策略的关联，通过PDP通信接口实现策略Action的关联。相关技术中，NFV MANO策略的应用基于各策略之间彼此分立，不存在策略关联。本申请至少一实施例中，通过PDP通信接口实现策略关联触发，从而提升决策效率。
策略可以采用多语言编写，因此如果要进行跨语言的策略执行时，则需要针对跨策略语言类型的策略执行体间通过消息方式，进行协作完成；另外同策略语言的PDP间，会根据实际的cpu负荷率、内存占用率等指标，通过消息方式，执行调度。
PDP通信协议是用于彼此通信以管理状态和部署的协议，接口目的主要为了PDP之间可以协作处理，完成策略的关联操作，以解决不同策略之间的关联协作流程。
PDP之间的通信接口包括以下至少之一：Intra-PDP Interface(PDP内接口)和Inter-PDP Interface(PDP间接口)两种通讯接口。Inter-PDP Interface即PDP间协议是任何PDP类型的实例可用于彼此通信以管理状态和部署的协议；Intra-PDP Interface即PDP内协议是用于同一类型的PDP彼此通信，以管理状态和部署的协议。
本实施例中，提供一状态管理实体表(StateManagementEntity)，该表中存储以下至少之一：PDP的标识(比如PDP的IP)、资源名称(即PDP的名称，比如显示给用户查看的一个名称)、管理状态(即PDP是否为管理节点)、可用状态、主备状态以及创建修改时间信息。其中，所述可用状态指示PDP是否可用，PDP已接入即为可用状态，未接入则为不可用状态，主备状态指 示PDP是否可以用作其他PDP的备用PDP，其中，处于hotstandby状态时不可用作备用PDP，处于coldstandby状态时可以用作备用PDP。备用PDP的含义是当有PDP故障时，其执行的功能可由备用PDP替代。比如备用PDP加载故障PDP上的数据(从各PDP共享的数据库中加载)后执行。创建修改时间信息为对该条信息的创建修改时间。所有PDP共享该管理实体表，并周期性更新管理实体表中的状态信息(管理状态、可用状态、主备状态)。
PDP集群中的所有PDP周期性地运行选举算法(当然，也可以在被触发后运行选举算法)，由于各PDP都使用相同的数据(共享的状态管理实体表中的数据)，所以所有PDP选举出相同的管理节点。其中被选中的PDP其管理状态更新为活动状态(或称提供服务状态，处于该状态的节点为集群中的管理节点)。因此，算法是分布式的，没有单点故障，假设数据库配置为高可用性。
本实施例中，还提供一个共享的PDP实体表(PdpEntity)，PdpEntity表中记录节点的选举算法当前是否正在运行以及节点最后被指定为管理节点的时间。
一般而言，定期收集所有PDP的状态。每个节点从StateManagementEntity表中读取所有其他节点的standbystatus(即状态信息)。对运行选举算法的PDP，如果该PDP当前被选举为管理节点，且被选举前已经是管理节点，则不需要任何操作。如果当前被选举为管理节点且被选举前不是管理节点，则修改该PDP的状态为活动状态；如果未被选举为管理节点，则不进行操作。初始时，可以将PDP设置为hotstandby状态(仅为示例，也可设置为其他状态)。如果选择的PDP是自己，它将从hotstandby状态变更为活动状态。如果选择的PDP不是自己，它将什么都不做。当PDP从hotstandby状态提升为活动状态时，将发生状态更改通知，并且状态更改处理程序将采取适当的操作。
本发明至少一实施例中，在OSS/BSS与MANO之间构建一个共享的策 略模块，通过分离策略决策单元和策略执行点，将策略决策单元单独提出，策略决策单元集群的方式部署，策略决策单元之间提供通信协议，更好的实现目前3/4G与5G之间的策略过渡问题，并很好的兼容原有网络设备的管理，提高NFVO的策略执行效率。
下面通过具体应用实例进一步说明本申请。
应用实例1基于策略的VNF扩容
网络服务自动扩容策略(NS Auto-scaling policy)由VNF提供(即VNF作为设计者)被VNFM(作为PEP)执行。策略设计者(即VNF)设计自动扩容策略，通过PLCM绑定一个给定类型的VNF封装在策略信息中，并下发给一个PDP。自动扩容策略的一个例子可能包含以下信息：如果VNF的第一指标值的变化被检测出来，则按照给定的动作进行VNF实例扩容。第一指标值可以根据需要设定，本申请对此不作限定。
VNF实例的监控指标信息上报指定的分析器(比如，性能管理器(Performance Management，PM))，PDP从分析器获取第一指标信息，将第一指标信息与当前扩容策略进行匹配，VNFM作为PEP来最终执行决策结果。详见图9，包括：步骤901，PDP接收PLCM发送的策略操作请求后，创建策略引擎；其中，PLCM接收到NFVO发送的策略参数和模板信息后，创建策略规则文件保存至PR，发送策略操作请求给PDP，所述策略操作请求中携带策略规则文件的描述信息，PDP接收到策略操作请求后，根据策略操作请求中携带的策略规则文件的描述信息从PR下载策略规则文件，需要说明的是，在其他实施例中，PDP也可以直接接收NFVO发送的策略参数和模板信息创建策略规则文件。
步骤902，PDP使用所述策略引擎加载策略规则文件，解析所述策略规则文件获得策略规则；步骤903，PM采集VIM的虚拟资源计数器的值，获得第一指标；步骤904，PDP订阅PM的第一指标变化事件；具体的，PDP的事件主题管理器订阅PM的第一指标变化事件，接收到第一指标变化事件； 步骤905，事件主题管理器发送第一指标变化事件给策略引擎模块；步骤906，策略引擎模块接收到第一指标变化事件，匹配到扩容规则，即第一指标的变化触发PDP中的扩容规则；步骤907，策略引擎模块根据扩容规则中的策略动作，向NFVO发起扩容请求；步骤908，NFVO接收到所述扩容请求后，对所述扩容请求进行校验；步骤909，验证通过后，所述NFVO向VNFM发起VNF实例化请求；步骤910，VNFM接收到所述VNF实例化请求后，解析VNFD(Virtualization Network Functions Descriptor，虚拟化网络功能描述符)获得部署VNF所需虚拟资源，生成扩容资源列表；步骤911，所述VNFM向NFVO返回扩容资源列表；步骤912，NFVO发送VNF扩容资源事件给PDP，具体的，发送给PDP的策略引擎模块；步骤913，PDP接收到所述VNF扩容资源事件后，匹配到资源规则；步骤914，根据资源规则中的策略动作，发送执行扩容请求至NFVO；步骤915，NFVO接收到所述执行扩容请求后，根据当前可用资源数量、本地策略等决定接受该执行扩容请求，向VIM请求分配资源，即发送资源分配请求至VIM；步骤916，VIM接收到所述NFVO的资源分配请求后，创建虚机；步骤917，VIM返回资源分配结果给NFVO；步骤918，NFVO发送资源配置完成通知给VNFM；步骤919，VNFM根据模板要求配置VNF，进行应用部署及参数配置；步骤920，VNFM通知NFVO完成VNF实例化；步骤921，NFVO向PDP发送扩容完成事件，完成VNF自动扩容的闭环。
应用实例2基于策略的VNF缩容
网络服务自动缩容策略(NS Auto-scaling policy)由VNF提供(即VNF作为设计者)被VNFM执行(即VNFM作为PEP)。策略设计者(即VNF)设计自动缩容策略，通过PLCM绑定一个给定类型的VNF封装在策略信息中，并下发给一个PDP。自动缩容策略的一个例子可能包含以下信息：如果某些VNF指标值的变化被检测出来，那么则按照给定的动作进行VNF实例缩容。 具体哪些指标值可以根据需要设定，本申请对此不作限定。
VNF实例的监控指标信息上报的指定的分析器，PDP从分析器获取指标信息，将指标信息与当前缩容策略进行匹配决策，VNFM作为PEP来最终执行决策结果。详见图10，包括：步骤1001，PDP接收PLCM发送的策略操作请求，创建策略引起；其中，PLCM接收到NFVO发送的策略参数和模板信息后，创建策略规则文件保存至PR，发送策略操作请求给PDP，所述策略操作请求中携带策略规则文件的描述信息，PDP接收到策略操作请求后，根据策略操作请求中携带的策略规则文件的描述信息从PR下载策略规则文件；步骤1002，PDP使用所述策略引擎加载策略规则文件，解析所述策略规则文件获得策略规则；步骤1003，VNFM使用VNF/VIM的性能管理接口的通知或获取性能准则操作，得到特定VNF的测量指标；步骤1004，PDP的事件主题管理器订阅VNFM的VNF测量指标事件，接收到VNF测量指标事件；步骤1005，PDP的事件主题管理器发送VNF测量指标时间给策略引擎；步骤1006，策略引擎模块接收到VNF测量指标时间，匹配到缩容规则，判断执行缩容；步骤1007，PDP向NFVO发起缩容请求；步骤1008，NFVO接收到所述缩容请求后，对所述缩容请求进行验证；步骤1009，验证通过后，所述NFVO发送VNF缩容请求至VNFM，所述VNF缩容请求携带VNFD；步骤1010，所述VNFM接收到所述VNF缩容请求后，解析VNFD，计算释放VNF所需资源，生成资源列表；步骤1011，所述VNFM返回资源列表给NFVO；步骤1012，NFVO发送VNF缩容资源事件给PDP，具体的，发送给PDP的策略引擎模块；步骤1013，PDP接收到所述VNF缩容资源事件后，匹配到资源规则，确定缩容；步骤1014，PDP发送执行缩容请求给NFVO；步骤1015，NFVO接收到所述执行缩容请求后，根据当前可用资源数量、本地策略等决定接受该执行缩容请求，变更VNF，包括调整网络参数、业务参数，变更分发机制，更新VNF管理列表等；步骤1016，NFVO向VIM请求释放资源；步骤1017，VIM释放相应的虚拟资源(包括网络资源和虚机资源)； 步骤1018，VIM返回资源释放结果给NFVO；步骤1019，NFVO通知VNFM完成释放资源；步骤1020，VNFM通知NFVO缩容完成；步骤1021，NFVO向PDP发送缩容完成事件，完成VNF自动缩容的闭环。
本实施例提供的方案，通过与PDP交互，实现了自动缩容。
应用实例3基于策略的VNF告警自愈
本实施例中，基于策略实现VNF告警自动化，通过设置策略，对某些告警自动分析和解决，从而达到告警智能自愈，减少运维成本。
如图11所示，该系统中包括告警采集模块1101、告警根因分析模块1102、机器规则学习模块1103、策略中心1104和智能脚本库1105，策略中心1104包括PLCM、PDP和PR，其中：告警采集模块1101用于，基于NFVO的告警订阅请求，以VNF为视角，采集VIM的虚拟资源告警并上报告警根因分析模块1102。
告警根因分析模块1102用于，以VNF为视角，将VNF告警、虚拟资源告警、物理资源告警进行关联；对告警进行分析，对于可以自动修复的告警，发送到策略中心1104；对于无法自动修复的告警，转人工处理；
机器规则学习模块1103用于，通过大数据机器学习分析历史告警给出分析模型和策略规则，所述策略规则包括自愈规则；比如，通过分析历史告警分析出生命周期短的闪断告警占比情况，通过分析历史告警分析出周期性发生的告警情况。
策略中心1104用于，负责策略触发，PDP接收到告警，且该告警匹配到PDP所管理的策略规则时，触发执行策略规则中的动作。动作包括调用智能脚本平台1105的脚本库。策略规则包括自愈规则，所述自愈规则来源于现场定制、专家经验导入和机器规则学习模块。
告警经过根因分析(RCA)后，对于可以自动修复的根告警，通过调用策略中心的自愈规则和智能脚本平台的脚本库进行自愈，自愈成功后，网元 上报告警恢复，从而实现告警智能自愈，减少运维成本。
如图12所示，本发明一实施例提供一种策略决策装置120，包括存储器121和处理器122，所述存储器121存储有程序，所述程序在被所述处理器122读取执行时，实现任一实施例所述的策略决策方法。
如图13所示，本发明一实施例提供一种计算机可读存储介质130，所述计算机可读存储介质130存储有一个或者多个程序131，所述一个或者多个程序131可被一个或者多个处理器执行，以实现任一实施例所述的策略决策方法。
本发明一实施例提供一种网管系统，如图14所示，包括NFVO201、VNFM202、VIM203还包括：上述任一实施例所述的策略决策集群80，所述策略决策集群独立于所述NFVO201、VNFM202、VIM203。
在一实施例中，还包括：PLCM301和PR304，其中，所述PLCM301用于，接收到策略参数和模板信息后，生成策略规则文件，将所述策略规则文件存储到策略存储库，发送携带策略规则文件的描述信息的策略操作请求至所述策略决策集群中的策略决策单元；所述PR304用于，存储所述策略规则文件。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或 其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。

Claims (19)

  1. 一种策略决策单元，其中，包括策略引擎模块和事件主题管理器，其中：
    所述策略引擎模块用于，创建策略引擎，使用所述策略引擎至少实现如下操作：加载策略规则，以及，接收到所述事件主题管理器发送的事件时，根据所述事件匹配到的策略规则触发对应的策略动作；
    所述事件主题管理器用于，根据所述策略规则监听事件，接收到所监听的事件时，将该事件发送给该事件对应的所述策略引擎。
  2. 根据权利要求1所述的策略决策单元，其中，所述策略引擎模块创建策略引擎包括：接收策略生命周期管理发送的策略操作请求，创建策略引擎。
  3. 根据权利要求2所述的策略决策单元，其中，所述加载策略规则包括：根据所述策略操作请求中携带的策略规则文件的描述信息，从策略存储库中获取策略规则文件，解析所述策略规则文件获取策略规则。
  4. 根据权利要求1至3任一所述的策略决策单元，其中，所述策略决策单元还包括集群管理模块，所述集群管理模块用于，当所述策略决策单元为策略决策集群的管理节点时，确定所述策略决策集群中的策略决策单元是否可作为其他策略决策单元的备用策略决策单元，以及，当所述策略决策集群中的策略决策单元不可用时，使用所述备用策略决策单元替代不可用的策略决策单元。
  5. 根据权利要求4所述的策略决策单元，其中，所述集群管理模块还用于，周期性选举确定策略决策集群的管理节点。
  6. 根据权利要求5所述的策略决策单元，其中，所述周期性选举确定策略决策集群的管理节点包括：根据管理实体表中的信息周期性选举确定策略决策集群的管理节点，其中，所述管理实体表中包括如下至少之一：所述策略决策单元的标识、资源名称、管理状态、可用状态、主备状态、创建修改 时间信息。
  7. 一种策略决策集群，包括至少一个如权利要求1至6任一所述的策略决策单元。
  8. 根据权利要求7所述的策略决策集群，其中，所述策略决策集群中包括多个策略决策单元时，所述策略决策单元之间存在通信接口。
  9. 一种策略决策方法，包括：
    策略决策单元创建策略引擎，使用所述策略引擎加载策略规则；
    所述策略决策单元根据所述策略规则监听事件，接收到所监听的事件时，将所述事件发送到所述策略引擎，由所述策略引擎根据所述事件匹配到的策略规则触发对应的策略动作。
  10. 根据权利要求9所述的策略决策方法，其中，所述创建策略引擎包括：接收策略生命周期管理发送的策略操作请求，创建策略引擎。
  11. 根据权利要求10所述的策略决策方法，其中，所述加载策略规则包括：根据所述策略操作请求中携带的策略规则文件的描述信息，从策略存储库中获取策略规则文件，解析所述策略规则文件获取策略规则。
  12. 根据权利要求9所述的策略决策方法，其中，所述事件包括其他策略决策单元匹配到策略规则时触发的策略动作。
  13. 根据权利要求9至12任一所述的策略决策方法，其中，所述方法还包括，当所述策略决策单元为策略决策集群的管理节点时，确定所述策略决策集群中的策略决策单元是否可作为其他策略决策单元的备用策略决策单元，以及，当所述策略决策集群中的策略决策单元不可用时，使用所述备用策略决策单元替代不可用的策略决策单元。
  14. 根据权利要求13所述的策略决策方法，其中，所述方法还包括，所 述策略决策单元根据共享的管理实体表中的信息周期性选举确定策略决策集群的管理节点。
  15. 根据权利要求13所述的策略决策方法，其中，所述管理实体表中包括如下至少之一：所述策略决策单元的标识、资源名称、管理状态、可用状态、主备状态、创建修改时间信息。
  16. 一种策略决策装置，其中，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求9至15任一所述的策略决策方法。
  17. 一种计算机可读存储介质，其中，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如权利要求9至15任一所述的策略决策方法。
  18. 一种网管系统，包括网络功能虚拟化NFV编排器、虚拟化网络功能管理器、虚拟化基础设施管理，其中，还包括：如权利要求7或8所述的策略决策集群，所述策略决策集群独立于所述NFV编排器、所述虚拟化网络功能管理器和所述虚拟化基础设备管理。
  19. 如权利要求18所述的网管系统，其中，还包括：策略生命周期管理和策略存储库，其中，
    所述策略生命周期管理用于，接收到策略参数和模板信息后，生成策略规则文件，将所述策略规则文件存储到策略存储库，发送携带策略规则文件的描述信息的策略操作请求至所述策略决策集群中的策略决策单元；
    所述策略存储库用于，存储所述策略规则文件。
PCT/CN2019/107368 2018-09-30 2019-09-23 策略决策方法及装置、系统、存储介质、策略决策单元及集群 WO2020063550A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811162422.3A CN110971439A (zh) 2018-09-30 2018-09-30 策略决策方法及装置、系统、存储介质、策略决策单元及集群
CN201811162422.3 2018-09-30

Publications (1)

Publication Number Publication Date
WO2020063550A1 true WO2020063550A1 (zh) 2020-04-02

Family

ID=69949306

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/107368 WO2020063550A1 (zh) 2018-09-30 2019-09-23 策略决策方法及装置、系统、存储介质、策略决策单元及集群

Country Status (2)

Country Link
CN (1) CN110971439A (zh)
WO (1) WO2020063550A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112784199A (zh) * 2021-01-28 2021-05-11 北京有竹居网络技术有限公司 事件流程处理方法、设备、存储介质及程序产品
CN113485765A (zh) * 2021-07-07 2021-10-08 上海顺舟智能科技股份有限公司 物联网智能设备的控制策略配置方法、装置、设备及介质
CN115037626A (zh) * 2022-06-17 2022-09-09 阿里巴巴（中国）有限公司 一种策略管理方法、装置、系统及电子设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20230069088A (ko) * 2020-09-18 2023-05-18 지티이 코포레이션 컨테이너 클러스터 관리 방법 및 그 시스템

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040267865A1 (en) * 2003-06-24 2004-12-30 Alcatel Real-time policy evaluation mechanism
CN101141307A (zh) * 2007-09-29 2008-03-12 北京邮电大学 一种应用于通信系统的基于策略管理的方法及体系结构
CN106489260A (zh) * 2014-05-12 2017-03-08 诺基亚通信管理国际两合公司 包括虚拟化网络功能的通信网络的控制
CN107113195A (zh) * 2015-06-01 2017-08-29 华为技术有限公司 用于控制平面和数据平面中的虚拟化功能的系统和方法
CN107852337A (zh) * 2015-07-23 2018-03-27 英特尔公司 支持网络功能虚拟化生命周期管理的网络资源模型

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1556613A (zh) * 2003-12-30 2004-12-22 上海交通大学 可信任主动式策略联动方法
KR20090001293A (ko) * 2007-06-29 2009-01-08 한국전자통신연구원 정책기반 관리 프레임워크에서의 정책 관리 방법 및 그장치
CN105659526B (zh) * 2014-09-26 2019-02-01 华为技术有限公司 一种策略实现方法和装置以及系统
CN106533724B (zh) * 2015-09-11 2020-02-11 中国移动通信集团公司 监控和优化网络功能虚拟化nfv网络的方法、装置及系统
EP3402121B1 (en) * 2016-02-06 2020-01-08 Huawei Technologies Co., Ltd. Method and device for policy transmission in nfv system
CN105847237B (zh) * 2016-03-15 2019-01-15 中国联合网络通信集团有限公司 一种基于nfv的安全管理方法和装置
CN108370328B (zh) * 2016-04-28 2020-09-11 华为技术有限公司 一种nfv mano策略描述符的管理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040267865A1 (en) * 2003-06-24 2004-12-30 Alcatel Real-time policy evaluation mechanism
CN101141307A (zh) * 2007-09-29 2008-03-12 北京邮电大学 一种应用于通信系统的基于策略管理的方法及体系结构
CN106489260A (zh) * 2014-05-12 2017-03-08 诺基亚通信管理国际两合公司 包括虚拟化网络功能的通信网络的控制
CN107113195A (zh) * 2015-06-01 2017-08-29 华为技术有限公司 用于控制平面和数据平面中的虚拟化功能的系统和方法
CN107852337A (zh) * 2015-07-23 2018-03-27 英特尔公司 支持网络功能虚拟化生命周期管理的网络资源模型

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112784199A (zh) * 2021-01-28 2021-05-11 北京有竹居网络技术有限公司 事件流程处理方法、设备、存储介质及程序产品
CN113485765A (zh) * 2021-07-07 2021-10-08 上海顺舟智能科技股份有限公司 物联网智能设备的控制策略配置方法、装置、设备及介质
CN113485765B (zh) * 2021-07-07 2023-09-22 上海顺舟智能科技股份有限公司 物联网智能设备的控制策略配置方法、装置、设备及介质
CN115037626A (zh) * 2022-06-17 2022-09-09 阿里巴巴（中国）有限公司 一种策略管理方法、装置、系统及电子设备
CN115037626B (zh) * 2022-06-17 2024-03-08 阿里巴巴（中国）有限公司 一种策略管理方法、装置、系统及电子设备

Also Published As

Publication number Publication date
CN110971439A (zh) 2020-04-07

Similar Documents

Publication Publication Date Title
WO2020063550A1 (zh) 策略决策方法及装置、系统、存储介质、策略决策单元及集群
WO2020253347A1 (zh) 一种容器集群管理方法、装置及系统
US20220197953A1 (en) Model pushing method and device, model requesting method and device, storage medium and electronic device
KR101891506B1 (ko) 하나 이상의 클라우드 시스템 상에 애플리케이션들을 이식 가능하게 배치하기 위한 방법들 및 시스템들
US20200382362A1 (en) Alarm information processing method, related device, and system
US7340654B2 (en) Autonomic monitoring in a grid environment
CN107005422B (zh) 用于第二天操作的基于拓扑的管理的系统和方法
CN104360878B (zh) 一种应用软件部署的方法及装置
US20190056975A1 (en) Virtualized network function manager determining method and network functions virtualization orchestrator
CN107005426B (zh) 一种虚拟网络功能的生命周期管理方法及装置
US20180234308A1 (en) Service orchestration
WO2022007552A1 (zh) 处理节点的管理方法、配置方法及相关装置
CN108370328B (zh) 一种nfv mano策略描述符的管理方法及装置
CN112035228A (zh) 一种资源调度方法及装置
US11196627B1 (en) Managed remediation of non-compliant resources
US10498817B1 (en) Performance tuning in distributed computing systems
US20210342178A1 (en) Method and device for instantiating virtualized network function
US20170339023A1 (en) Automatic Network Management System and Methods
US11769067B2 (en) Topology-based migration assessment
US20170339003A1 (en) Automatic network mangement system and methods
CN109902028A (zh) Acl特性的自动化测试方法、装置、设备及存储介质
US20220182851A1 (en) Communication Method and Apparatus for Plurality of Administrative Domains
WO2023045552A1 (zh) 服务部署方法、服务部署系统、电子设备及存储介质
CN110740047B (zh) 一种网络切片管理编排系统
CN107426012B (zh) 一种基于超融合架构的故障恢复方法及其装置

Legal Events

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

Ref document number: 19866976

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 24/08/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19866976

Country of ref document: EP

Kind code of ref document: A1