WO2016054922A1 - 决策协调方法、执行装置和决策协调器 - Google Patents

决策协调方法、执行装置和决策协调器 Download PDF

Info

Publication number
WO2016054922A1
WO2016054922A1 PCT/CN2015/080241 CN2015080241W WO2016054922A1 WO 2016054922 A1 WO2016054922 A1 WO 2016054922A1 CN 2015080241 W CN2015080241 W CN 2015080241W WO 2016054922 A1 WO2016054922 A1 WO 2016054922A1
Authority
WO
WIPO (PCT)
Prior art keywords
decision
coordinated
component
coordination
network function
Prior art date
Application number
PCT/CN2015/080241
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 EP15848256.2A priority Critical patent/EP3197102A4/en
Publication of WO2016054922A1 publication Critical patent/WO2016054922A1/zh
Priority to US15/481,751 priority patent/US10567196B2/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
    • 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
    • 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • 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/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
    • 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
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • 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
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present invention relates to the field of domain network function virtualization, and more particularly to a decision coordination method, an execution device, and a decision coordinator in a network function virtualization system.
  • NFV Network Functions Virtualization
  • IT information technology
  • NS networks and network services
  • FIG. 1 is a schematic diagram of a system architecture of an NFV system 100 that can be applied according to an embodiment of the present invention.
  • the NFV system can be implemented over a variety of networks, such as a data center network, a service provider network, or a local area network (LAN).
  • the NFV system may include an NFV Management and Orchestration System (MANO) 128, an NFV Infrastructure (NFVI) 130, and a plurality of Virtual Network Functions (VNF) 108.
  • MANO NFV Management and Orchestration System
  • NFVI NFV Infrastructure
  • VNF Virtual Network Functions
  • EMS enterprise management system
  • VNF virtual network operator
  • Infrastructure Description service, VNF and Infrastructure Description
  • operational support systems / business support systems Opera Support System / Business Support System, OSS/BSS
  • the NFV MANO 128 may include an NFV Orchestrator (NFVO) 102, one or more VNF Managers (VNFMs) 104, and one or more Virtualized Infrastructure Managers (VIMs) 106. .
  • NFVI 130 A virtual resource layer comprised of computing hardware 112, storage hardware 114, network hardware 116, virtualization layer, and virtual computing 110 (eg, virtual machine), virtual storage 118, and virtual network 120 may be included.
  • Computing hardware 112 can be a dedicated processor or a general purpose processor for providing processing and computing functions.
  • the storage hardware 114 is configured to provide storage capabilities, which may be provided by the storage hardware 114 itself (eg, a server's local memory), or may be provided over a network (eg, the server connects to a network storage device over a network).
  • Network hardware 116 may be a switch, router, and/or other network device, and network hardware 116 is used to enable communication between multiple devices, with wireless or wired connections between multiple devices.
  • the virtualization layer in NFVI 130 is used to abstract the hardware resources of the hardware resource layer, decouple the VNF 108 from the physical layer to which the hardware resources belong, and provide virtual resources to the VNF. As shown in FIG. 1, virtual resources may include virtual computing 110, virtual storage 118, and virtual network 120.
  • Virtual computing 110 virtual storage 118 may be provided to VNF 108 in the form of a virtual machine or other virtual container, for example, one or more VNFs 108 may be deployed on a virtual machine.
  • the virtualization layer forms a virtual network 120 through abstract network hardware 116.
  • Virtual networks 120 such as virtual switches (eg, Vswitches), are used to enable communication between multiple virtual machines, or between other types of virtual containers hosting VNFs.
  • Virtualization of network hardware can be virtualized by virtual LAN (Vritual LAN, VLAN), Virtual Private LAN Service (VPLS), Virtual eXtensible Local Area Network (VxLAN), or general routing encapsulation network ( Nerwork Virtualization using Generic Routing Encapsulation, NVGRE) and other technical implementations.
  • OSS/BSS 124 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 such as billing management
  • customer service management such as customer service management.
  • the VNF and the infrastructure description system 126 are described in detail in the ETSI GS NFV 002 v1.1.1 standard, and will not be described herein again.
  • NFV MANO 128 can be used to monitor and manage VNF 108 and NFVI 130.
  • NFVO 102 is mainly responsible for NS lifecycle management, completes network service orchestration functions, and NFVI resource scheduling across multiple VIMs to complete resource orchestration functions.
  • the NFVO can communicate with one or more VNFMs 104 to implement resource related requests, send configuration information to the VNFM 104, and collect status information for the VNF 108.
  • NFVO 102 can also communicate with VIM 106 to enable resource allocation, and/or to implement provisioning and exchange of configuration information and status information for virtualized hardware resources.
  • the VNFM 104 can be used to manage one or more VNFs 108, performing various management functions, such as initializing, updating, querying, and/or terminating the VNF 108.
  • VIM 106 can be used for control and management The interaction of VNF 108 and computing hardware 112, storage hardware 114, network hardware 116, virtual computing 110, virtual storage 118, virtual network 120.
  • VIM 106 can be used to perform resource allocation operations to VNF 108.
  • VNFM 104 and VIM 106 can communicate with each other to exchange virtualized hardware resource configuration and status information.
  • NFVI 130 includes both hardware and software that together create a virtualized environment to deploy, manage, and execute VNF 108.
  • the hardware resource layer and the virtual resource layer are used to provide virtual resources, such as virtual machines or other forms of virtual containers, to the VNF 108.
  • VNFM 104 can communicate with VNF 108 and EMS 122 to perform VNF lifecycle management and implement exchange of configuration/status information.
  • the VNF 108 is a virtualization of at least one network function that was previously provided by a physical network device.
  • the VNF 108 can be a virtualized Mobility Management Entity (MME) node for providing all network functions provided by a typical non-virtualized MME device.
  • MME Mobility Management Entity
  • the VNF 108 can be used to implement the functionality of some of the components provided on the non-virtualized MME device.
  • One or more VNFs 108 can be deployed on a virtual machine (or other form of virtual container).
  • the EMS 122 can be used to manage one or more VNFs.
  • NFV policy management refers to the management of rules governing different NFV functions (eg, VNF or NS scaling operations, access control, resource management, fault management, etc.).
  • the policy is defined as a condition and a corresponding action.
  • a scaling policy may stipulate that if the required condition (such as a low resource utilization rate of a VNF) is satisfied, the related action (such as reducing the size of the VNF) is performed.
  • NFVO in NFV MANO provides policy management interfaces to NFVO and VIM to NFVO to OSS/BSS and VNFM respectively to allow authorized entities or functional blocks to manage NFV policies.
  • the NFVO exposed interfaces provide support for NS instances, VNF instances, and NFVI resource-related policy management (such as authorization/access control, resource reservation/layout/allocation, etc.).
  • the VNFM and VIM exposed interfaces provide support for managing policies related to VNF and NFVI resources under NFVO requirements. Possible operations on these interfaces include the creation, update, deletion, query, activation, deactivation, etc. of the policy.
  • VNF instance scaling may be OSS/BSS, EMS, NFVO, VNFM or VIM.
  • the triggering of their decision-making process may be their own monitoring function, or it may be event detection and reporting from other entities or function blocks.
  • VIM may be due to network congestion, number of sessions, etc.
  • VNFM may be due to VNF resource usage, etc.
  • Factors NFVO may be due to resource scheduling and other factors
  • EMS may be due to cross-VNF management and other factors
  • OSS / BSS may be triggered into the scaling decision process because of factors such as cross-EMS management or just operation and maintenance plans. They then determine whether the conditions defined in the established strategy are met, and then decide whether to initiate the execution of the defined actions. Finally, the scaling decisions they make will be handed over to VNFM for execution.
  • the execution component may receive the decision of the various components in the NFV system (including the execution component itself) to be executed by it. Due to the lack of a good decision coordination mechanism, the execution component can only be rigid. It is not flexible enough to implement these decisions one by one.
  • Embodiments of the present invention provide a decision coordination method, an execution device, and a decision coordinator to improve the flexibility of executing components to perform decisions.
  • a method for decision coordination comprising: receiving a decision coordination request message from an execution component in a network function virtualization system, wherein the decision coordination request message includes a decision to be coordinated; according to the decision to be coordinated Determining a coordinated decision; transmitting a decision coordination response message to the execution component, the decision coordination response message including the coordinated decision, the decision coordination response message being used to instruct the execution component to perform the coordination Decision making.
  • the decision to be coordinated is one or more decisions for a target operation, the coordinated decision being a final decision for the target operation, Determining the coordinated decision according to the decision to be coordinated includes: determining the final decision according to the one or more decisions.
  • the plurality of decisions are generated by a plurality of decision components in the network function virtualization system
  • the decision The coordination request message further includes an identifier of the plurality of decision components
  • the method further includes: determining, according to the plurality of decision components, the plurality of Determining a priority of the decision components, determining a decision component having the highest priority among the plurality of decision components; determining the final decision according to the plurality of decisions, including: The decision generated by the highest priority decision component is determined as the final decision.
  • the determining a coordination request message further includes a sequence in which the executing component obtains the multiple decisions, where Determining the final decision based on the plurality of decisions, including: based on the sequence In order, the first or last obtained decision among the plurality of decisions is determined as the final decision.
  • the to-coordinated decision is a decision for a target operation, and according to the decision to be coordinated, Before determining the coordinated decision, the method further includes: obtaining association information of the target operation from the network function virtualization system; and determining, according to the to-coordinated decision, the coordinated decision, including: The decision to be coordinated and the associated information determine the coordinated decision.
  • the determining, according to the to-coordinated decision and the associated information, determining the coordinated decision including And determining, by the big data analysis, the coordinated decision according to the decision to be coordinated and the associated information.
  • the sending, by the executing component, the decision coordination response message further includes: when the coordination is not determined In the subsequent decision, the decision coordination failure information is sent to the execution component.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy.
  • the decision coordination request message further includes an identifier of a decision component that makes the decision to be coordinated.
  • the determining component is a network function virtualization orchestrator, a virtual network function manager, a virtualized infrastructure manager , component management system, operational support system or business support system.
  • the executing component is a network function virtualization orchestrator, a virtual network function manager, and a virtualized infrastructure manager. , component management system, operational support system or business support system.
  • a method for decision coordination including: obtaining a decision to be coordinated; and transmitting a decision coordination request message to a decision coordinator in a network function virtualization system, wherein the decision coordination request message includes the to-be-coordinated a decision, the decision coordination request message is used to instruct the decision coordinator to determine a coordinated decision according to the decision to be coordinated; receive a decision coordination response message from the decision coordinator, the decision coordination response message including the Coordinated decision making.
  • the method further includes: determining a feasibility of the coordinated decision; and performing the coordinated decision when the coordinated decision is feasible When the coordinated decision is not feasible, the coordinated decision is not executed.
  • the to-coordinated decision is a decision for a target operation
  • the determining the feasible of the coordinated decision includes: acquiring association information of the target operation; and determining feasibility of the coordinated decision according to the association information.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy.
  • the method further includes: making the to-be-coordinated The decision component of the decision is sent with indication information for indicating an execution result of the coordinated decision.
  • the decision coordination request message further includes an identifier of a decision component that makes the decision to be coordinated.
  • a decision coordinator comprising: a receiving unit, configured to receive a decision coordination request message from an execution component in a network function virtualization system, wherein the decision coordination request message includes a decision to be coordinated; a determining unit, configured to determine a coordinated decision according to the to-be-coordinated decision received by the receiving unit, and a sending unit, configured to send a decision coordination response message to the executing component, where the decision coordination response message includes the The coordinated decision determined by the first determining unit, the decision coordination response message is used to instruct the executing component to perform the coordinated decision.
  • the decision to be coordinated is one or more decisions for a target operation, the coordinated decision being a final decision for the target operation,
  • the first determining unit is specifically configured to determine the final decision according to the one or more decisions.
  • the plurality of decisions are generated by a plurality of decision components in the network function virtualization system
  • the decision The coordination request message further includes an identifier of the plurality of decision components
  • the decision coordinator further includes a second determining unit, configured to determine, according to a correspondence between an identifier of the plurality of decision components and a priority of the plurality of decision components, a decision component having the highest priority among the plurality of decision components;
  • a determining unit is specifically configured to determine, in the plurality of decisions, a decision generated by the highest priority decision component as the final decision.
  • the decision coordination request message further includes a sequence in which the executing component obtains the multiple decisions, where The first determining unit is specifically configured to determine, as the final decision, the first or last obtained decision among the plurality of decisions based on the sequence.
  • the decision to be coordinated is a decision for a target operation
  • the decision coordinator further includes: an acquiring unit, Acquiring information for acquiring the target operation from other components in the network function virtualization system other than the execution component; the first determining unit is specifically configured to be according to the to-be-coordinated decision and the Associate the information to determine the coordinated decision.
  • the first determining unit is specifically configured to use, according to the to-coordinated decision and the associated information, Data analysis to determine the coordinated decision.
  • the sending unit is further configured to: when the coordinated decision is not determined, to the executing component Send decision coordination failure information.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy.
  • the decision coordination request message further includes an identifier of the decision component that makes the to-coordinated decision.
  • the determining component is a network function virtualization orchestrator, a virtual network function manager, and a virtualized infrastructure manager. , component management system, operational support system or business support system.
  • the executing component is a network function virtualization orchestrator, a virtual network function manager, and a virtualized infrastructure manager. , component management system, operational support system or business support system.
  • the fourth aspect provides an execution component, including: an obtaining unit, configured to obtain a decision to be coordinated; a first sending unit, configured to send a decision coordination request message to a decision coordinator in the network function virtualization system, where The decision coordination request message includes the to-coordinated decision acquired by the acquiring unit, and the decision coordination request message is used to instruct the decision coordinator to determine the coordinated decision according to the to-coordinated decision; Receiving a decision coordination response message from the decision coordinator, the decision coordination response message including the coordinated decision.
  • the executing component further includes: a determining unit, configured to determine a feasibility of the coordinated decision; an executing unit, configured to: when the coordinated When the decision is feasible, the coordinated decision is performed; when the coordinated decision is not feasible, the coordinated decision is not executed.
  • the to-coordinated decision is a decision for a target operation
  • the determining unit is specifically configured to acquire the target The associated information of the operation; determining the feasibility of the coordinated decision based on the associated information.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy.
  • the executing component further includes: a second sending unit, configured to make a decision to make the decision to be coordinated The component sends indication information, the indication information being used to indicate an execution result of the coordinated decision.
  • the decision coordination request message further includes an identifier of a decision component that makes the decision to be coordinated.
  • a decision coordinator is introduced, and the execution component determines the coordinated decision from the decision to be coordinated through the decision coordinator, so that only the coordinated decision needs to be performed, which is more flexible than the prior art.
  • Figure 1 is a block diagram of the NFV system.
  • FIG. 2 is a schematic flowchart of a decision coordination method according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a decision coordination method according to an embodiment of the present invention.
  • FIG. 4 is a schematic block diagram of a decision coordinator of an embodiment of the present invention.
  • Figure 5 is a schematic block diagram of an executing component of an embodiment of the present invention.
  • FIG. 6 is a schematic block diagram of a decision coordinator of an embodiment of the present invention.
  • Figure 7 is a schematic block diagram of an executing component of an embodiment of the present invention.
  • the embodiment of the present invention introduces a decision coordinator, or a Policy-based Decision Coordinator (PDC), in the NFV field, and the decision coordinator is responsible for coordinating the decision of the execution component acquisition, and the decision may be the execution.
  • the decision coordinator can be a separate entity or function block, or it can be a component of other entities or function blocks, such as deployed in NFVO, as one of the functions of NFVO.
  • FIG. 2 is a schematic flowchart of a decision coordination method according to an embodiment of the present invention.
  • the method of Figure 2 is performed by a decision coordinator, and the method of Figure 2 includes:
  • 210 Receive a decision coordination request message from an execution component in a network function virtualization system, where the decision coordination request message includes a decision to be coordinated.
  • execution components may be any components (or entities or functional blocks) in the NFV system, for example, may be NFVO 102, VNFM 104, VIM 106, EMS 122, or OSS/BSS 124 in FIG.
  • the execution component is responsible for performing one or some operations in the NFV system. It can also be said that the execution component is responsible for implementing one or some functions in the NFV system.
  • a decision can be directed to an operation (or function), or a decision indicates how the execution component performs an operation. For example, when the execution component is VNFM, the VNFM is responsible for performing the scaling operation of the VNF, then the decision for the VNF scaling operation may be: reducing the VNF by 50%; or, scaling the VNF by 40%.
  • the decision for the NS scaling operation may be: reducing the NS by 50%; Or, zoom in on the NS by 40%.
  • the above-mentioned reduction or amplification of VNF or NS may refer to reduction or enlargement of the scale of VNF or NS, and more progress, may refer to an increase or decrease of resources occupied by VNF or NS.
  • the above-mentioned decision to be coordinated may be one decision or multiple decisions, which may be decisions for the same operation of the execution component, or may be decisions for different operations of the execution component.
  • the execution component can apply for coordination to the decision coordinator for each decision execution request, or it can be directed to the decision coordinator when requested by multiple parties (for example, any combination of OSS/BSS, EMS, VNFM, and VIM).
  • parties for example, any combination of OSS/BSS, EMS, VNFM, and VIM.
  • To apply for coordination it is necessary to include relevant information requested by the parties at the time of application coordination.
  • the decision to be coordinated may be a decision made by the execution component itself based on the established policy, or may be generated by other components (or entities or functional components) in the NFV system based on the respective established policies, requesting execution of the execution component.
  • the decision that is, the execution component is the executor of the decision, but not necessarily the decision maker.
  • the execution component can be a VNFM
  • the decision to be coordinated can be a decision made by the VNFM itself; or the decision to be coordinated can be other components (eg, OSS/BSS, EMS, NFVO, or VIM)
  • the decision is made and then the decision is sent to the VNFM side through an interface with the VNFM to trigger (or request) the VNFM to perform the decision.
  • the VNFM can monitor the resource usage rate of the VNF. When the VNF resource usage rate is below a certain threshold, the VNFM makes a decision: the VNF is reduced; or, the VIM can monitor the network congestion or session. The number, when the network is congested, the VIM reports information indicating congestion to the VNFM, and the VNFM makes a decision based on the information: the VNF is amplified.
  • the executing component when the executing component receives a request sent by another component to perform a certain decision, the validity of the request may be verified first, for example, whether the requester is authorized to issue the request, and if the verification fails, the requester returns a failure. Respond and can carry information such as the reason for the failure.
  • the coordinated decision may be a decision selected from the decisions to be coordinated, or a new decision based on the decision to be coordinated. Take the decision of the VNF scaling operation as an example.
  • the decision to be coordinated may include two decisions. The first decision instructs the VNFM to reduce the target VNF by 50%, and the second decision instructs the VNFM to reduce the target VNF by 60%. Then, the coordinated decision may be in the first decision or the second decision. One, or a new decision, the new decision instructs VNFM to reduce the target VNF by 55%.
  • the implementation manner of the step 220 is not specifically limited, and the decision coordinator may use the analysis processing means of various data or the preset rules to obtain the coordinated decision based on the decision to be coordinated.
  • the decision to be coordinated is a decision for the target operation.
  • the method of FIG. 2 may further include: acquiring association information of the target operation from the network function virtualization system; step 220 may include : Determine the coordinated decision based on the decision to be coordinated and the associated information.
  • the embodiment of the present invention does not specifically limit the form of the related information, and the manner of determining the coordinated decision according to the decision to be coordinated and the related information.
  • any information related to the target operation may be used to analyze the coordinated decision.
  • the scaling of the VNF may involve information such as resources occupied by the VNF, and the VNF may be obtained from the VIM.
  • Information such as resources, VNF scaling may also lead to NS adjustment, at this time you can get information from the NFVO whether to allow VNF scaling, or VNF scaling range.
  • the manner of determining the coordinated decision is also various.
  • the decision to be coordinated is to reduce the VNF by 30%, and the related information indicates that the VNF can be reduced by 20%, then the selection can be selected.
  • the decision to be coordinated is to amplify the VNF by 50%, and the associated information indicates the number of computing resources occupied by the VNF, and then the prediction method may be based on a certain data analysis, for example, big data analysis, probability analysis prediction, etc. Decision making.
  • the decision coordinator can query the related information of the target VNF from the VIM in the NFV system. If the target VNF is currently occupied by the resource status, and the target VNF is found to be up to 30%, the decision coordinator determines that the coordinated decision is to amplify the target VNF by 30%. For another example, if the decision coordinator queries the NFVO discovery target VNF to be restricted by management and cannot be amplified by more than 40%, then the decision coordinator determines that the coordinated decision is to amplify the target VNF by 40%.
  • the decision coordinator may, after receiving the decision coordination request message, query the related resource status or management restriction information, or may have monitored and reported the event through itself or other components before receiving the decision coordination request message.
  • the function gets this information.
  • the decision-making association The modulator determines that the coordinated decision based on the decision to be coordinated can use various information analysis and prediction techniques including big data analysis.
  • the coordinated decision can also include multiple conflicting decisions.
  • the decision coordinator can coordinate these conflicting decisions based on certain decision coordination rules to generate a final decision, thus solving the conflicting decision between the execution of the component acquisition. The following will describe in detail how to coordinate conflicting decisions in conjunction with specific embodiments, which will not be described in detail herein.
  • the decision coordinator may also send the coordinated decision to other relevant components in the NFV system to confirm the feasibility of the coordinated decision.
  • the decision coordinator may also send the coordinated decision to other relevant components in the NFV system to confirm the feasibility of the coordinated decision.
  • the decision to be coordinated is generated by the VNFM itself, requesting to reduce the target VNF by 10%, and the coordinated decision is also to reduce the target VNF by 10%, and the decision coordinator can coordinate the coordinated The decision is sent to NFVO so that NFVO confirms that it is feasible to reduce the target VNF by 10%.
  • the target VNF can only be reduced by 5%, then the coordination made by the decision coordinator is not feasible, and the decision coordinator can make new decisions again or return information such as decision coordination failure to the VNFM.
  • the ground can also be accompanied by the reason for the failure of decision coordination.
  • a decision coordinator is introduced, and the execution component determines the coordinated decision from the decision to be coordinated through the decision coordinator, so that only the coordinated decision needs to be performed, which is more flexible than the prior art.
  • the decision to be coordinated is a plurality of decisions for the target operation, and the coordinated decision is a final decision for the operation, and the coordinated decision is determined according to the decision to be coordinated, including: And determining a final decision; sending a decision coordination response message to the executing component, comprising: sending a decision coordination response message to the executing component, the coordination response message being used to instruct the executing component to perform the operation according to the final decision.
  • VIM can make decisions to scale VNF based on factors such as network congestion and number of sessions
  • VNFM can make decisions to scale VNF based on factors such as VNF resource usage
  • NFVO can make decisions to scale VNF based on factors such as NS orchestration
  • EMS The decision to scale the VNF can be made based on factors such as cross-VNF management
  • the OSS/BSS can make decisions to scale the VNF based on factors such as EMS management or operation and maintenance plans.
  • the decision to be coordinated includes multiple decisions for the target operation, there will be inconsistencies or conflicts between the decisions.
  • the decision on the target operation is transformed into a final decision, which effectively solves the conflicting problem between the decisions.
  • the decision coordination request message further includes identifiers of the plurality of decision components, before determining the final decision according to the multiple decisions.
  • the method further includes: determining a target component with the highest priority among the plurality of decision components according to the correspondence between the identifiers of the plurality of decision components and the priority of the plurality of decision components; determining the final decision according to the plurality of decisions, including: determining the plurality of decisions The decision generated by the highest priority target component is determined as the final decision.
  • decision component can be any component in the NFV system, and in addition, the decision component can also be the execution component itself.
  • the decision to be coordinated includes two decisions, the first decision is a decision made by NFVO, which requires the target VNF to be reduced by 20%; the second decision is made by VIM. Amplify the target VNF by 10%.
  • a priority order table of components in the NFV system is pre-established in the decision coordinator, wherein the VIM for managing the lower layer resources has a higher priority than the NFVO for managing the NS, and therefore, the decision coordinator takes the decision of the VIM as the final decision,
  • the target VNF is amplified by 10%.
  • the decision coordination request message further includes a sequence in which the execution component obtains multiple decisions, and determines a final decision according to the multiple decisions, including: first or last among the plurality of decisions based on the sequence The decision obtained is determined as the final decision.
  • the decision to be coordinated includes two decisions, and the VNFM obtains the first decision time later than the time for obtaining the second decision, and the VNFM can carry the information indicating the order of the two decisions (such as the time for obtaining the decision) in the decision coordination request.
  • the decision coordinator can use the decision that was first obtained as the final decision, or the final decision to make the final decision.
  • the decision coordination method of the embodiment of the present invention is described in detail from the decision coordinator side.
  • the decision coordination method of the embodiment of the present invention is described in detail from the perspective of executing components in conjunction with FIG. 3, and it should be understood that the decision coordinator
  • the functions and interactions between the execution components and the decision-making components correspond to each other, and the duplicate descriptions are omitted as appropriate for brevity.
  • FIG. 3 is a schematic flowchart of a decision coordination method according to an embodiment of the present invention.
  • the method of Figure 3 includes:
  • the executing component When the executing component receives the coordinated decision, it can first verify its source legality and parameter feasibility, such as whether the coordination reply corresponds to the coordination request, whether the scaling operation parameter can be supported by the resource status and the management restriction.
  • the execution component may also return the result of performing the coordinated decision to the component that originally requested the decision to be executed.
  • the coordinated decision is generated by the NFVO, and the NFVO requests the VNFM to perform the decision.
  • the VNFM sends the decision to be coordinated to the decision coordinator to obtain the coordinated decision.
  • the VNFM performs this coordinated decision and then returns the results of the execution to NFVO. If the execution fails, it will return a failure response to NFVO, and may also include information such as the reason for the failure. If the downgrade process is adopted, the specific information of the downgrade process can be clearly indicated in the return result.
  • the NFVO request reduces the target VNF by 50%, and the VNFM performs the downgrade process based on the coordinated decision, and the target VNF is reduced by 40%, and the VNFM can be 40%.
  • the parameters used in this degradation process are returned to NFVO.
  • a decision coordinator is introduced, and the execution component determines the coordinated decision from the decision to be coordinated through the decision coordinator, so that only the coordinated decision needs to be performed, which is more flexible than the prior art.
  • the decision to be coordinated is a plurality of decisions for the target operation
  • the coordinated decision is a final decision for the operation
  • the step 340 may include: performing the operation according to the final decision.
  • VIM can make decisions to scale VNF based on factors such as network congestion and number of sessions
  • VNFM can make decisions to scale VNF based on factors such as VNF resource usage
  • NFVO can make decisions to scale VNF based on factors such as NS orchestration
  • EMS The decision to scale the VNF can be made based on factors such as cross-VNF management
  • the OSS/BSS can make decisions to scale the VNF based on factors such as EMS management or operation and maintenance plans.
  • the decision to be coordinated includes multiple decisions for the target operation, there will be inconsistencies or conflicts between the decisions.
  • the decision on the target operation is transformed into a final decision, which effectively solves the conflicting problem between the decisions.
  • the method of FIG. 3 may further include: determining feasibility of the coordinated decision; performing coordinated decision when the coordinated decision is feasible; and when the coordinated decision is not feasible, Perform coordinated decisions.
  • the method of FIG. 3 may further include: receiving coordination failure information sent by the decision coordinator.
  • the executing component may not perform the decision to be coordinated, or perform the decision to be coordinated according to other manners, such as sequential execution.
  • the decision to be coordinated is a decision for the target operation
  • the determining the feasibility of the coordinated decision may include: acquiring association information of the target operation; determining feasibility of the coordinated decision according to the associated information. Sex.
  • the association information may include the current resource status of the VNF or the management restriction information of the VNF, or the current resource status of the VNF or the management restriction information of the VNF.
  • the decision to be coordinated is generated by the decision component in the network function virtualization system based on the predetermined policy.
  • the method of FIG. 3 may further include: sending the indication information to the decision component, indicating the information. The result of the execution of the decision indicating the coordination.
  • the decision to be coordinated is generated by NFVO, which indicates that the VNF is reduced by 40%, and the coordinated decision indicates that the VNF is reduced by 30%.
  • the NFVO After the VNFM performs the decision, the NFVO returns the current resource status of the VNF, etc., so that the NFVO knows the The VNF has been reduced, and the NFVO can determine from the execution results whether the scale of the VNF reduction meets the requirements, and whether it is necessary to generate a request to reduce the VNF again.
  • the decision to be coordinated is generated by the decision component in the network function virtualization system based on a predetermined policy, and the decision coordination request message further includes an identifier of the decision component.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • Decision coordinator 400 is a schematic block diagram of a decision coordinator of an embodiment of the present invention.
  • the decision coordinator 400 of FIG. 4 is capable of implementing the various steps performed by the decision coordinator of FIGS. 1 through 3, to avoid duplication, appropriate provinces A slightly repeated description.
  • Decision coordinator 400 includes:
  • the receiving unit 410 is configured to receive a decision coordination request message from an execution component in the network function virtualization system, where the decision coordination request message includes a decision to be coordinated;
  • a first determining unit 420 configured to determine, according to the to-coordinated decision received by the receiving unit 410, a coordinated decision
  • the sending unit 430 is configured to send a decision coordination response message to the executing component, where the decision coordination response message includes the coordinated decision determined by the first determining unit 420, where the decision coordination response message is used to indicate The execution component performs the coordinated decision.
  • a decision coordinator is introduced, and the execution component determines the coordinated decision from the decision to be coordinated through the decision coordinator, so that only the coordinated decision needs to be performed, which is more flexible than the prior art.
  • the decision to be coordinated is one or more decisions for a target operation
  • the coordinated decision is a final decision for the target operation, the first determining unit 420
  • the final decision is determined according to the one or more decisions.
  • the multiple decisions are generated by multiple decision components in the network function virtualization system
  • the decision coordination request message further includes an identifier of the multiple decision components
  • the decision The coordinator further includes: a second determining unit, configured to determine, according to a correspondence between the identifiers of the plurality of decision components and priorities of the plurality of decision components, a decision component having the highest priority among the plurality of decision components;
  • the first determining unit 420 is specifically configured to determine, in the plurality of decisions, a decision generated by the highest priority decision component as the final decision.
  • the decision coordination request message further includes a sequence in which the executing component obtains the multiple decisions, where the first determining unit 420 is specifically configured to use the sequence according to the sequence. The first or last decision made in the plurality of decisions is determined as the final decision.
  • the decision to be coordinated is a decision for a target operation
  • the decision coordinator further includes: an obtaining unit, configured to remove the execution component from the network function virtualization system.
  • the other components are used to obtain the associated information of the target operation;
  • the first determining unit 420 is specifically configured to determine the coordinated decision according to the decision to be coordinated and the associated information.
  • the first determining unit 420 is specifically configured to determine, by using big data analysis, the coordinated decision according to the to-coordinated decision and the associated information.
  • the sending unit 430 is further configured to: when the association is not determined In the adjusted decision, the decision coordination failure information is sent to the execution component.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy.
  • the decision coordination request message further includes an identifier of a decision component that makes the to-coordination decision.
  • the decision component is a network function virtualization orchestrator, a virtual network function manager, a virtualization infrastructure manager, a component management system, an operation support system, or a service support system.
  • the execution component is a network function virtualization orchestrator, a virtual network function manager, a virtualization infrastructure manager, a component management system, an operation support system, or a service support system.
  • FIG. 5 is a schematic block diagram of an executing component of an embodiment of the present invention. It should be understood that the execution component 500 of FIG. 5, which may be referred to as an execution device, can implement the various steps performed by the execution components in FIGS. 1-3, and the repeated description is omitted as appropriate to avoid redundancy.
  • the execution component 500 includes:
  • the obtaining unit 510 is configured to obtain a decision to be coordinated
  • a first sending unit 520 configured to send a decision coordination request message to a decision coordinator in the network function virtualization system, where the decision coordination request message includes the to-coordinated decision acquired by the obtaining unit 510, The decision coordination request message is used to instruct the decision coordinator to determine the coordinated decision according to the decision to be coordinated;
  • the receiving unit 530 is configured to receive a decision coordination response message from the decision coordinator, where the decision coordination response message includes the coordinated decision.
  • a decision coordinator is introduced, and the execution component determines the coordinated decision from the decision to be coordinated through the decision coordinator, so that only the coordinated decision needs to be performed, which is more flexible than the prior art.
  • the executing component further includes: a determining unit, configured to determine a feasibility of the coordinated decision; and an executing unit, configured to: when the coordinated decision is feasible, perform the Coordinated decision; when the coordinated decision is not feasible, the coordinated decision is not executed.
  • the decision to be coordinated is a decision for a target operation
  • the determining unit is specifically configured to acquire association information of the target operation, and determine, according to the association information, the coordinated The feasibility of decision making.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy.
  • the executing component further includes: a second sending unit, configured to send, to the decision component that makes the decision to be coordinated, the indication information, where the indication information is used to indicate the coordinated The execution result of the decision.
  • a second sending unit configured to send, to the decision component that makes the decision to be coordinated, the indication information, where the indication information is used to indicate the coordinated The execution result of the decision.
  • the receiving unit 530 is further configured to receive the coordination failure information sent by the decision coordinator.
  • the execution component 500 may not perform the decision to be coordinated, or perform the decision to be coordinated according to other manners, such as sequential execution.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy, where the decision coordination request message further includes a decision component that makes the decision to be coordinated.
  • the decision coordination request message further includes a decision component that makes the decision to be coordinated.
  • Decision coordinator 600 is a schematic block diagram of a decision coordinator of an embodiment of the present invention.
  • the decision coordinator 600 of FIG. 6 can implement the various steps performed by the decision coordinator in FIGS. 1 through 3, and redundant descriptions are omitted as appropriate to avoid repetition.
  • Decision coordinator 600 includes:
  • the receiver 610 is configured to receive a decision coordination request message from an execution component in the network function virtualization system, where the decision coordination request message includes a decision to be coordinated;
  • the processor 620 is configured to determine, according to the decision to be coordinated, a coordinated decision.
  • a transmitter 630 configured to send a decision coordination response message to the executing component, where the decision coordination response message includes the coordinated decision, the decision coordination response message is used to instruct the executing component to perform the coordinated decision making.
  • a decision coordinator is introduced, and the execution component determines the coordinated decision from the decision to be coordinated through the decision coordinator, so that only the coordinated decision needs to be performed, which is more flexible than the prior art.
  • the decision to be coordinated is one or more decisions for a target operation
  • the coordinated decision is a final decision for the target operation
  • the processor 620 specifically uses The final decision is determined based on the one or more decisions.
  • the multiple decisions are generated by multiple decision components in the network function virtualization system, and the decision coordination request message further includes an identifier of the multiple decision components, the processing The controller 630 is further configured to determine, according to the correspondence between the identifiers of the multiple decision components and the priorities of the multiple decision components, the highest priority decision component among the multiple decision components; In the plurality of decisions, the decision with the highest priority The decision to generate the component is determined as the final decision.
  • the decision coordination request message further includes a sequence in which the executing component obtains the multiple decisions, where the processor 630 is specifically configured to: The first or last decision made in the decision is determined as the final decision.
  • the decision to be coordinated is a decision for a target operation
  • the decision coordinator further includes: an obtaining unit, configured to remove the execution component from the network function virtualization system.
  • the other components are used to obtain the associated information of the target operation;
  • the processor 630 is specifically configured to determine the coordinated decision according to the to-coordinated decision and the associated information.
  • the processor 630 is specifically configured to determine, according to the decision to be coordinated and the associated information, the coordinated decision by using big data analysis.
  • the transmitter 630 is further configured to send the decision coordination failure information to the executing component when the coordinated decision is not determined.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy.
  • the decision coordination request message further includes an identifier of a decision component that makes the to-coordination decision.
  • the decision component is a network function virtualization orchestrator, a virtual network function manager, a virtualization infrastructure manager, a component management system, an operation support system, or a service support system.
  • the execution component is a network function virtualization orchestrator, a virtual network function manager, a virtualization infrastructure manager, a component management system, an operation support system, or a service support system.
  • FIG. 7 is a schematic block diagram of an executing component of an embodiment of the present invention. It should be understood that the execution component 700 of FIG. 7 , which may be referred to as an execution device, can implement the various steps performed by the execution components in FIGS. 1-3 , and the repeated description is omitted as appropriate to avoid redundancy.
  • the execution component 700 includes:
  • the processor 710 is configured to obtain a decision to be coordinated.
  • the sender 720 is configured to send a decision coordination request message to the decision coordinator in the network function virtualization system, where the decision coordination request message includes the to-coordinated decision, and the decision coordination request message is used to indicate the The decision coordinator determines the coordinated decision according to the decision to be coordinated;
  • a receiver 730 configured to receive, from the decision coordinator, a decision coordination response message, where the decision coordination response message includes the coordinated decision;
  • the processor 710 is further configured to perform the coordinated decision.
  • a decision coordinator is introduced, and the execution component determines the coordinated decision from the decision to be coordinated through the decision coordinator, so that only the coordinated decision needs to be performed, which is more flexible than the prior art.
  • the processor 710 is further configured to determine a feasibility of the coordinated decision; the processor 710 is specifically configured to perform the coordination when the coordinated decision is feasible Subsequent decision; when the coordinated decision is not feasible, the coordinated decision is not executed.
  • the decision to be coordinated is a decision for a target operation
  • the determining unit is specifically configured to acquire association information of the target operation, and determine, according to the association information, the coordinated The feasibility of decision making.
  • the decision to be coordinated is generated by a decision component in the network function virtualization system based on a predetermined policy.
  • the sender 720 is further configured to send, to the decision component that makes the decision to be coordinated, the indication information, where the indication information is used to indicate an execution result of the coordinated decision.
  • the decision coordination request message further includes an identifier of a decision component that makes the decision to be coordinated.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division, and may be implemented in actual implementation.
  • multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

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

Abstract

本发明公开了一种决策协调方法和装置，该方法包括：从网络功能虚拟化系统中的执行部件接收决策协调请求消息，其中，该决策协调请求消息包括待协调的决策；根据该待协调的决策，确定协调后的决策；向该执行部件发送决策协调响应消息，该决策协调响应消息包括该协调后的决策，该决策协调响应消息用于指示该执行部件执行该协调后的决策。本发明实施例中引入决策协调器，执行部件通过该决策协调器，从待协调的决策中确定出协调后的决策，从而仅需要执行协调后的决策，与现有技术相比，更加灵活。

Description

决策协调方法、执行装置和决策协调器
本申请要求于2014年10月10日提交中国专利局、申请号为201410529933.X、发明名称为“决策协调方法、执行装置和决策协调器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及领域网络功能虚拟化领域，并且更具体地，涉及一种网络功能虚拟化系统中的决策协调方法、执行装置和决策协调器。
背景技术
网络功能虚拟化(Network Functions Virtualization,NFV)旨在采用演进中信息技术(Information Technology,IT)领域的虚拟化技术，将大量的网络设备类型统一到符合产业标准的高容量服务器、交换机和存储设备上去实现，从而改变网络运营商构建和运营网络以及网络业务(Network Service,NS)的方式。NFV通过可在一系列符合产业标准的服务器硬件上运行的软件来实现网络功能，从而改变了网络的架构，并且因为这些软件可以按照要求动态地移动或者实例化于网络中不同的位置而不必安装新设备，从而也改变了网络的运作。
请参考图1，为本发明实施例可以应用的NFV系统100的系统架构示意图。该NFV系统可以通过多种网络实现，例如数据中心网络、服务提供者网络、或者局域网(Local Area Network,LAN)。如图1所示，该NFV系统可以包括NFV管理和编排系统(Management and Orchestration System,MANO)128，NFV基础设施(NFV Infrastructure,NFVI)130，多个虚拟网络功能(Virtual Network Function,VNF)108，多个组件管理系统(element management system,EMS)122，服务、VNF和基础设施描述(Service,VNF and Infrastructure Description)系统126，以及一个或多个运营支撑系统/业务支撑系统(Operation Support System/Business Support System,OSS/BSS)124。
NFV MANO 128可以包括NFV编排器(NFV Orchestrator,NFVO)102、一个或多个VNF管理器(VNF Manager,VNFM)104，以及一个或多个虚拟化基础设施管理器(Virtualized Infrastructure Manager,VIM)106。NFVI 130 可以包括计算硬件112、存储硬件114、网络硬件116组成的硬件资源层、虚拟化层、以及虚拟计算110(例如虚拟机)、虚拟存储118和虚拟网络120组成的虚拟资源层。计算硬件112可以为专用的处理器或通用的用于提供处理和计算功能的处理器。存储硬件114用于提供存储能力，该存储能力可以是存储硬件114本身提供的(例如一台服务器的本地内存)，也可以通过网络提供(例如服务器通过网络连接一个网络存储设备)。网络硬件116可以是交换机、路由器和/或其他网络设备，网络硬件116用于实现多个设备之间的通信，多个设备之间通过无线或有线连接。NFVI 130中的虚拟化层用于抽象硬件资源层的硬件资源，将VNF 108和硬件资源所属的物理层解耦，向VNF提供虚拟资源。如图1所示，虚拟资源可以包括虚拟计算110、虚拟存储118和虚拟网络120。虚拟计算110、虚拟存储118可以以虚拟机或其他虚拟容器的形式向VNF 108提供，例如一个或多个VNF 108可以部署在一台虚拟机上。虚拟化层通过抽象网络硬件116形成虚拟网络120。虚拟网络120，例如虚拟交换机(例如Vswitches)，用于实现多个虚拟机之间，或多个承载VNF的其他类型的虚拟容器之间的通信。网络硬件的虚拟化可以通过虚拟LAN(Vritual LAN,VLAN)、虚拟专用局域网业务(Virtual Private LAN Service,VPLS)、虚拟可扩展局域网(Virtual eXtensible Local Area Network,VxLAN)或通用路由封装网络虚拟化(Nerwork Virtualization using Generic Routing Encapsulation，NVGRE)等技术实现。OSS/BSS 124主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。VNF和基础设施描述系统126在ETSI GS NFV 002v1.1.1标准中有详细介绍，本发明实施例在此不再赘述。
NFV MANO 128可以用于实现VNF 108和NFVI 130的监控和管理。NFVO 102主要负责NS的生命周期管理，完成网络业务编排功能；以及跨多个VIM的NFVI资源编排，完成资源编排功能。NFVO可以与一个或多个VNFM 104通信以实现与资源相关的请求、发送配置信息给VNFM 104、以及收集VNF 108的状态信息。另外，NFVO 102还可以与VIM 106进行通信以实现资源分配，和/或实现虚拟化硬件资源的配置信息和状态信息的预留和交换。VNFM 104可以用于管理一个或多个VNF 108，执行各种管理功能，例如初始化、更新、查询、和/或终止VNF 108。VIM 106可以用于控制和管 理VNF 108和计算硬件112、存储硬件114、网络硬件116、虚拟计算110、虚拟存储118、虚拟网络120的交互。例如，VIM 106可以用于执行资源向VNF 108的分配操作。VNFM 104和VIM 106可以互相通信以交换虚拟化硬件资源配置和状态信息。
NFVI 130包含硬件和软件，二者共同建立虚拟化环境以部署、管理和执行VNF 108。换句话说，硬件资源层和虚拟资源层用于向VNF 108提供虚拟资源，例如虚拟机或其他形式的虚拟容器。
如图1所示，VNFM 104可以与VNF 108和EMS 122通信以执行VNF生命周期管理和实现配置/状态信息的交换。VNF 108是至少一个网络功能的虚拟化，该网络功能之前是由物理网络设备提供的。在一种实现方式下，VNF 108可以是一个虚拟化的移动管理实体(Mobility Management Entity，MME)节点，用于提供典型的非虚拟化的MME设备提供的所有网络功能。在另一种实现方式下，VNF108可以用于实现非虚拟化的MME设备上提供的全部组件中的部分组件的功能。一个虚拟机(或其他形式的虚拟容器)上可以部署有一个或多个VNF 108。EMS 122可以用于管理一个或多个VNF。
NFV策略管理指对管制不同NFV功能(例如VNF或者NS缩放操作、访问控制、资源管理、故障管理等)的规则进行管理。策略定义为条件及对应的行动，例如一条缩放策略可以规定：如果要求的条件(比如某VNF的资源使用率偏低)满足，就执行相关的行动(比如缩小该VNF的规模)。
NFV MANO中的NFVO向OSS/BSS、VNFM向NFVO、VIM向NFVO分别提供策略管理接口，以允许被授权的实体或功能块管理NFV策略。NFVO暴露的接口为NS实例、VNF实例和NFVI资源相关策略管理(例如授权/访问控制、资源预留/布局/分配等)提供支持。VNFM和VIM暴露的接口为在NFVO要求下管理与VNF和NFVI资源相关的策略分别提供支持。这些接口上可能进行的操作包括对策略的创建、更新、删除、查询、激活、去活等。
以VNF实例缩放为例：虽然对VNF实例进行缩放的操作是由VNFM执行的，但是基于既定策略做出进行缩放的决策的却可能是OSS/BSS、EMS、NFVO、VNFM或VIM。触发它们进入决策过程的可能是它们自己执行的监测功能，也可能是来自其它实体或功能块的事件检测和报告功能。例如VIM可能因为网络拥塞、会话数量等因素，VNFM可能因为VNF资源使用率等 因素，NFVO可能因为资源编排等因素、EMS可能因为跨VNF管理等因素，OSS/BSS可能因为跨EMS管理或者仅仅是运维计划等因素而被触发进入缩放决策过程。然后它们判断既定策略中定义的条件是否满足，从而决定是否发起执行定义的行动。最终它们做出的缩放决策将交给VNFM执行。
由上可知，在NFV系统中，执行部件可能会收到NFV系统中的多种部件(包括该执行部件自身)交由其执行的决策，由于缺乏很好的决策协调机制，执行部件只能呆板地逐个执行这些决策，不够灵活。
发明内容
本发明实施例提供了一种决策协调方法、执行装置和决策协调器，以提高执行部件执行决策的灵活性。
第一方面，提供一种决策协调方法，包括：从网络功能虚拟化系统中的执行部件接收决策协调请求消息，其中，所述决策协调请求消息包括待协调的决策；根据所述待协调的决策，确定协调后的决策；向所述执行部件发送决策协调响应消息，所述决策协调响应消息包括所述协调后的决策，所述决策协调响应消息用于指示所述执行部件执行所述协调后的决策。
结合第一方面，在第一方面的一种实现方式中，所述待协调的决策为针对目标操作的一个或多个决策，所述协调后的决策为针对所述目标操作的一个最终决策，所述根据所述待协调的决策，确定协调后的决策，包括：根据所述一个或多个决策，确定所述最终决策。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述多个决策由所述网络功能虚拟化系统中的多个决策部件生成，所述决策协调请求消息还包括所述多个决策部件的标识，在所述根据所述多个决策，确定所述最终决策之前，所述方法还包括：根据所述多个决策部件的标识与所述多个决策部件的优先级的对应关系，确定所述多个决策部件中优先级最高的决策部件；所述根据所述多个决策，确定所述最终决策，包括：将所述多个决策中，由所述优先级最高的决策部件生成的决策确定为所述最终决策。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述决策协调请求消息中还包括所述执行部件获得所述多个决策的先后顺序，所述根据所述多个决策，确定所述最终决策，包括：基于所述先后 顺序，将所述多个决策中最先或最后获得的决策确定为所述最终决策。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述待协调的决策为针对目标操作的决策，在所述根据所述待协调的决策，确定协调后的决策之前，所述方法还包括：从所述网络功能虚拟化系统中获取所述目标操作的关联信息；所述根据所述待协调的决策，确定协调后的决策，包括：根据所述待协调的决策和所述关联信息，确定所述协调后的决策。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述根据所述待协调的决策和所述关联信息，确定所述协调后的决策，包括：根据所述待协调的决策和所述关联信息，通过大数据分析，确定所述协调后的决策。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述向所述执行部件发送所述决策协调响应消息还包括：当未确定出所述协调后的决策时，向所述执行部件发送决策协调失败信息。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述决策协调请求消息还包括作出所述待协调的决策的决策部件的标识。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述决策部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
结合第一方面或其上述实现方式的任一种，在第一方面的另一种实现方式中，所述执行部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
第二方面，提供一种决策协调方法，包括：获取待协调的决策；向网络功能虚拟化系统中的决策协调器发送决策协调请求消息，其中，所述决策协调请求消息包括所述待协调的决策，所述决策协调请求消息用于指示所述决策协调器根据所述待协调的决策确定协调后的决策；从所述决策协调器接收决策协调响应消息，所述决策协调响应消息包括所述协调后的决策。
结合第二方面，在第二方面的一种实现方式中，所述方法还包括：确定所述协调后的决策的可行性；当所述协调后的决策可行时，执行所述协调后的决策；当所述协调后的决策不可行时，不执行所述协调后的决策。
结合第二方面或其上述实现方式的任一种，在第二方面的另一种实现方式中，所述待协调的决策为针对目标操作的决策，所述确定所述协调后的决策的可行性，包括：获取所述目标操作的关联信息；根据所述关联信息，确定所述协调后的决策的可行性。
结合第二方面或其上述实现方式的任一种，在第二方面的另一种实现方式中，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
结合第二方面或其上述实现方式的任一种，在第二方面的另一种实现方式中，在所述执行所述协调后的决策之后，所述方法还包括：向作出所述待协调的决策的决策部件发送指示信息，所述指示信息用于指示所述协调后的决策的执行结果。
结合第二方面或其上述实现方式的任一种，在第二方面的另一种实现方式中，所述决策协调请求消息还包括作出所述待协调的决策的决策部件的标识。
第三方面，提供一种决策协调器，包括：接收单元，用于从网络功能虚拟化系统中的执行部件接收决策协调请求消息，其中，所述决策协调请求消息包括待协调的决策；第一确定单元，用于根据所述接收单元接收的所述待协调的决策，确定协调后的决策；发送单元，用于向所述执行部件发送决策协调响应消息，所述决策协调响应消息包括所述第一确定单元确定的所述协调后的决策，所述决策协调响应消息用于指示所述执行部件执行所述协调后的决策。
结合第三方面，在第三方面的一种实现方式中，所述待协调的决策为针对目标操作的一个或多个决策，所述协调后的决策为针对所述目标操作的一个最终决策，所述第一确定单元具体用于根据所述一个或多个决策，确定所述最终决策。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述多个决策由所述网络功能虚拟化系统中的多个决策部件生成，所述决策协调请求消息还包括所述多个决策部件的标识，所述决策协调器还包 括：第二确定单元，用于根据所述多个决策部件的标识与所述多个决策部件的优先级的对应关系，确定所述多个决策部件中优先级最高的决策部件；所述第一确定单元具体用于将所述多个决策中，由所述优先级最高的决策部件生成的决策确定为所述最终决策。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述决策协调请求消息中还包括所述执行部件获得所述多个决策的先后顺序，所述第一确定单元具体用于基于所述先后顺序，将所述多个决策中最先或最后获得的决策确定为所述最终决策。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述待协调的决策为针对目标操作的决策，所述决策协调器还包括：获取单元，用于从所述网络功能虚拟化系统中的除所述执行部件之外的其他部件获取所述目标操作的关联信息；所述第一确定单元具体用于根据所述待协调的决策和所述关联信息，确定所述协调后的决策。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述第一确定单元具体用于根据所述待协调的决策和所述关联信息，通过大数据分析，确定所述协调后的决策。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述发送单元还用于当未确定出所述协调后的决策时，向所述执行部件发送决策协调失败信息。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述决策协调请求消息还包括作出所述待协调决策的决策部件的标识。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述决策部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
结合第三方面或其上述实现方式的任一种，在第三方面的另一种实现方式中，所述执行部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
第四方面，提供一种执行部件，包括：获取单元，用于获取待协调的决策；第一发送单元，用于向网络功能虚拟化系统中的决策协调器发送决策协调请求消息，其中，所述决策协调请求消息包括所述获取单元获取的所述待协调的决策，所述决策协调请求消息用于指示所述决策协调器根据所述待协调的决策确定协调后的决策；接收单元，用于从所述决策协调器接收决策协调响应消息，所述决策协调响应消息包括所述协调后的决策。
结合第四方面，在第四方面的一种实现方式中，所述执行部件还包括：确定单元，用于确定所述协调后的决策的可行性；执行单元，用于当所述协调后的决策可行时，执行所述协调后的决策；当所述协调后的决策不可行时，不执行所述协调后的决策。
结合第四方面或其上述实现方式的任一种，在第四方面的另一种实现方式中，所述待协调的决策为针对目标操作的决策，所述确定单元具体用于获取所述目标操作的关联信息；根据所述关联信息，确定所述协调后的决策的可行性。
结合第四方面或其上述实现方式的任一种，在第四方面的另一种实现方式中，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
结合第四方面或其上述实现方式的任一种，在第四方面的另一种实现方式中，所述执行部件还包括：第二发送单元，用于向作出所述待协调的决策的决策部件发送指示信息，所述指示信息用于指示所述协调后的决策的执行结果。
结合第四方面或其上述实现方式的任一种，在第四方面的另一种实现方式中，所述决策协调请求消息还包括作出所述待协调的决策的决策部件的标识。
本发明实施例中引入决策协调器，执行部件通过该决策协调器，从待协调的决策中确定出协调后的决策，从而仅需要执行协调后的决策，与现有技术相比，更加灵活。
附图说明
图1是NFV系统的框架图。
图2是本发明实施例的决策协调方法的示意性流程图。
图3是本发明实施例的决策协调方法的示意性流程图。
图4是本发明实施例的决策协调器的示意性框图。
图5是本发明实施例的执行部件的示意性框图。
图6是本发明实施例的决策协调器的示意性框图。
图7是本发明实施例的执行部件的示意性框图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明的一部分实施例，而不是全部实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动的前提下所获得的所有其他实施例，都应属于本发明保护的范围。
本发明实施例在NFV领域引入决策协调器，或称基于策略的决策协调器(Policy-based Decision Coordinator，PDC)，该决策协调器负责对执行部件获取的决策进行协调，该决策可以是该执行部件基于既定的策略做出的决策，也可以是NFV系统中的其他部件基于各自制定的策略做出的决策。该决策协调器可以是独立的实体或功能块，也可以是其它实体或功能块的组件，例如部署于NFVO中，作为NFVO的功能之一。
图2是本发明实施例的决策协调方法的示意性流程图。图2的方法由决策协调器执行，图2的方法包括：
210、从网络功能虚拟化系统中的执行部件接收决策协调请求消息，其中，决策协调请求消息包括待协调的决策。
应理解，上述执行部件可以是NFV系统中的任意部件(或称实体或功能块)，例如，可以是图1中的NFVO 102、VNFM 104、VIM 106、EMS 122或OSS/BSS 124。
需要说明的是，执行部件负责执行NFV系统中的某项或某些操作，也可以说，执行部件负责实现NFV系统中的某项或某些功能。一个决策可针对一项操作(或功能)，或者说，一个决策指示了执行部件执行一项操作的方式。例如，执行部件为VNFM时，VNFM负责执行VNF的缩放操作，那么，针对VNF缩放操作的决策可以是：对VNF进行缩小50％；或者，对VNF进行放大40％。又如，执行部件为NFVO，NFVO负责的操作包括NS缩放的操作，那么，针对NS缩放操作的决策可以是：对NS进行缩小50％； 或者，对NS进行放大40％。应理解，上述对VNF或NS的缩小或放大可以指对VNF或NS的规模的缩小或放大，更进步一地，可以指对VNF或NS所占用的资源的增加或减少。
上述待协调的决策可以是一个决策，也可以是多个决策，这些决策可以是针对执行部件的相同操作的决策，也可以是针对执行部件的不同操作的决策。换句话说，执行部件可以对每个决策执行请求都向决策协调器申请协调，也可能在被多方(例如OSS/BSS、EMS、VNFM和VIM中的任意组合)同时请求时才向决策协调器申请协调，相应这时也需在申请协调时附带各方请求的相关信息。
此外，待协调的决策可以是执行部件自己基于既定的策略做出的决策，也可以是NFV系统中的其他部件(或称实体或功能构件)基于各自制定的策略生成的、请求该执行部件执行的决策，也就是说，执行部件是决策的执行者，但不一定是决策的制定者。例如，针对VNF缩放的操作，执行部件可以为VNFM，待协调的决策可以是VNFM自己做出的决策；或者，待协调的决策可以是其他部件(例如，OSS/BSS、EMS、NFVO或VIM)做出的决策，然后通过与VNFM之间的接口将决策发送至VNFM侧，以触发(或请求)VNFM执行该决策。
还需要说明的是，无论上述待协调的决策来自执行部件自身，还是来自NFV系统中的其他部件(为了描述方便，下称生成决策的部件为决策者)，促使决策者做出相应决策的方式可以有多种，例如，可以由决策者自身的监测功能触发，也可以由其他部件的事件监测和报告功能上报功能触发。以VNF缩放操作的决策为例，VNFM可以监测VNF的资源使用率，当VNF资源使用率低于一定阈值时，该VNFM做出决策：对VNF进行缩小操作；或者，VIM可以监测网络拥塞或会话数量，当网络发生拥塞时，VIM向VNFM上报指示拥塞的信息，VNFM基于该信息做出决策：对VNF进行放大操作。
此外，当执行部件收到其他部件发送的执行某个决策的请求时，可以先验证该请求的合法性，例如，请求者是否被授权发出该请求，若验证不通过，则向请求者返回失败响应，并可以携带失败的原因等信息。
220、根据待协调的决策，确定协调后的决策。
需要说明的是，协调后的决策可以是从待协调的决策中选择出的决策，也可以是基于待协调的决策生成的新的决策。以VNF缩放操作的决策为例， 待协调的决策可包括2个决策，第1决策指示VNFM将目标VNF缩小50％，第2决策指示VNFM将目标VNF缩小60％，那么，协调后的决策可以是第1决策或第2决策中的1个，也可以是新的决策，该新的决策指示VNFM将目标VNF缩小55％。
需要说明的是，本发明实施例对步骤220的实现方式不作具体限定，决策协调器可以基于待协调的决策，利用各种数据的分析处理手段或预先设定的规则得到协调后的决策。
可选地，作为一个实施例，待协调的决策为针对目标操作的决策，步骤220之前，图2的方法还可包括：从网络功能虚拟化系统中获取目标操作的关联信息；步骤220可包括：根据待协调的决策以及关联信息，确定协调后的决策。
需要说明的是，本发明实施例对关联信息的形式，以及根据待协调的决策以及关联信息确定协调后的决策的方式等不作具体限定。实际中，只要是与目标操作相关的任何信息，均有可能用来分析协调后的决策，例如，VNF的缩放会涉及到该VNF占用的资源等信息，此时可以从VIM中获取该VNF所占的资源等信息，VNF的缩放还可能会导致NS的调整，此时可以从NFVO中获取是否允许VNF缩放、或者VNF缩放范围等信息。进一步地，基于待协调的决策和关联信息，确定协调后的决策的方式也多种多样，例如，待协调的决策是要将VNF缩小30％，关联信息指示VNF可以缩小20％，那么可以选取两个数值中的最小值。又如，待协调的决策是要将VNF放大50％，关联信息指示VNF占据的计算资源的数目，那么可以基于一定的数据分析预测方式，例如，大数据分析，概率分析预测等方式得到协调后的决策。
以VNF缩放操作的决策为例，假设待协调的决策是让VNFM将目标VNF放大50％，决策协调器收到该待协调的决策后，可以从NFV系统中的VIM查询该目标VNF的关联信息，如目标VNF当前占用的资源状况，发现该目标VNF最多能放大30％，那么决策协调器确定协调后的决策为将目标VNF放大30％。又如，决策协调器查询NFVO发现目标VNF受到管理的限制，不能放大超过40％，那么，决策协调器确定协调后的决策为将目标VNF放大40％。应理解，决策协调器可以收到决策协调请求消息后，再去查询相关的资源状况或管理限制等信息，也可以在收到决策协调请求消息之前，已经通过自身或其他部件的事件监测和上报功能获得这些信息。此外，决策协 调器基于待协调的决策确定协调后的决策可以运用包括大数据分析在内的各种信息分析和预测技术。
待协调决策还可包括多个相互冲突的决策，决策协调器可以基于一定的决策协调规则协调这些相互冲突的决策，生成一个最终的决策，从而解决了执行部件获取的决策之间相互冲突的问题，后续会结合具体的实施例详细描述如何协调相互冲突的决策，此处不再详述。
230、向执行部件发送决策协调响应消息，决策协调响应消息包括协调后的决策，决策协调响应消息用于指示执行部件执行协调后的决策。
可选地，在步骤230之前，决策协调器还可以将协调后的决策发送至NFV系统中的其他相关部件，以确认协调后的决策的可行性。以VNF缩放操作的决策为例，假设待协调的决策是VNFM自己生成的，请求将目标VNF缩小10％，协调后的决策也是将该目标VNF缩小10％，决策协调器可以将该协调后的决策发送至NFVO，以便NFVO确认将目标VNF缩小10％是否可行。比如，NFVO创建的NS中，规定该目标VNF仅能缩小5％，则决策协调器做出的协调不可行，决策协调器可以再次做出新的决策或者向VNFM返回决策协调失败等信息，进一步地，还可以附带决策协调失败的原因。
本发明实施例中引入决策协调器，执行部件通过该决策协调器，从待协调的决策中确定出协调后的决策，从而仅需要执行协调后的决策，与现有技术相比，更加灵活。
可选地，作为一个实施例，待协调的决策为针对目标操作的多个决策，协调后的决策为针对操作的一个最终决策，根据待协调的决策，确定协调后的决策，包括：根据多个决策，确定最终决策；向执行部件发送决策协调响应消息，包括：向执行部件发送决策协调响应消息，协调响应消息用于指示执行部件按照最终决策执行操作。
应理解，针对目标操作的多个决策可以由不同的部件基于不同的策略(或考虑不同的因素)做出。例如，VIM可以基于网络拥塞、会话数量等因素做出缩放VNF的决策；VNFM可以基于VNF资源使用率等因素做出缩放VNF的决策；NFVO可以基于NS编排等因素做出缩放VNF的决策；EMS可以基于跨VNF管理等因素做出缩放VNF的决策；OSS/BSS可以基于跨EMS管理或者运维计划等因素做出缩放VNF的决策。待协调的决策包括针对目标操作的多个决策时，会出现决策之间不一致或相互冲突的现象，本发 明实施例中，将针对目标操作的决策转化为一个最终的决策，有效解决了决策之间相互冲突的问题。
需要说明的是，决策协调器解决决策相互冲突的方式可以有多种，下面给出两种具体的实现方式，但本发明实施例不限于此，只要能将多个决策转化为一个决策的冲突协调解决方式都应落入本发明实施例的保护范围。
可选地，作为一种实现方式，多个决策由网络功能虚拟化系统中多个决策部件生成，决策协调请求消息还包括多个决策部件的标识，在根据多个决策，确定最终决策之前，方法还包括：根据多个决策部件的标识与多个决策部件优先级的对应关系，确定多个决策部件中优先级最高的目标部件；根据多个决策，确定最终决策，包括：将多个决策中，由优先级最高的目标部件生成的决策确定为最终决策。
应理解，决策部件可以是NFV系统中的任意部件，此外，决策部件也可以是执行部件自身。
以VNF缩放操作的决策为例，假设待协调的决策包括2个决策，第1决策是由NFVO做出的决策，要求将目标VNF缩小20％；第2决策是由VIM做出的决策，要求将目标VNF放大10％。在决策协调器中预先建立了NFV系统中部件的优先级顺序表，其中，管理低层资源的VIM的优先级高于管理NS的NFVO，因此，决策协调器将VIM的决策作为最终的决策，即将目标VNF放大10％。
可选地，作为一个实施例，决策协调请求消息中还包括执行部件获得多个决策的先后顺序，根据多个决策，确定最终决策，包括：基于先后顺序，将多个决策中最先或最后获得的决策确定为最终决策。
假设待协调的决策包括2个决策，VNFM获取第1决策时间晚于获取第2决策的时间，VNFM可以将指示该2个决策获取先后顺序的信息(如获取决策的时间)携带在决策协调请求消息，决策协调器可以将最先获得的决策作为最终的决策，也可以将最后获得决策作为最终的决策。
上文结合图2，从决策协调器侧详细描述了本发明实施例的决策协调方法，下文结合图3，从执行部件的角度详细描述本发明实施例的决策协调方法，应理解，决策协调器和决策的执行部件之间的功能和交互相互对应，为了简洁，适当省略重复的描述。
图3是本发明实施例的决策协调方法的示意性流程图。图3的方法包括：
310、获取待协调的决策。
320、向网络功能虚拟化系统中的决策协调器发送决策协调请求消息，其中，决策协调请求消息包括待协调的决策，决策协调请求消息用于指示决策协调器根据待协调的决策确定协调后的决策。
330、从决策协调器接收决策协调响应消息，决策协调响应消息包括协调后的决策。
执行部件收到协调后的决策时，可以先验证其来源合法性和参数可行性，例如协调答复与协调申请是否对应、缩放操作参数是否可以得到资源状况支持和管理限制的允许等。
执行部件还可以将执行所述协调后的决策的结果返回给最初请求执行该决策的部件。以VNF缩放操作的决策为例，待协调决策由NFVO生成，NFVO向VNFM请求执行该决策。VNFM将该待协调的决策发送至决策协调器，得到协调后的决策。VNFM执行该协调后的决策，然后将执行的结果返回至NFVO。若执行失败将返回失败响应给NFVO，还可附带失败原因等信息。若采取了降级处理也可以在返回结果中明确指示降级处理的具体信息，例如，NFVO请求缩小目标VNF50％，VNFM基于协调后的决策进行降级处理，将目标VNF缩小40％，VNFM可以将40％这一降级处理采用的参数返回至NFVO。
本发明实施例中引入决策协调器，执行部件通过该决策协调器，从待协调的决策中确定出协调后的决策，从而仅需要执行协调后的决策，与现有技术相比，更加灵活。
可选地，作为一个实施例，待协调的决策为针对目标操作的多个决策，协调后的决策为针对操作的一个最终决策，步骤340可包括：按照最终决策执行操作。
应理解，针对目标操作的多个决策可以由不同的部件基于不同的策略(或考虑不同的因素)做出。例如，VIM可以基于网络拥塞、会话数量等因素做出缩放VNF的决策；VNFM可以基于VNF资源使用率等因素做出缩放VNF的决策；NFVO可以基于NS编排等因素做出缩放VNF的决策；EMS可以基于跨VNF管理等因素做出缩放VNF的决策；OSS/BSS可以基于跨EMS管理或者运维计划等因素做出缩放VNF的决策。待协调的决策包括针对目标操作的多个决策时，会出现决策之间不一致或相互冲突的现象，本发 明实施例中，将针对目标操作的决策转化为一个最终的决策，有效解决了决策之间相互冲突的问题。
可选地，作为一个实施例，图3的方法还可包括：确定协调后的决策的可行性；当协调后的决策可行时，执行协调后的决策；当协调后的决策不可行时，不执行协调后的决策。
可选地，作为一个实施例，图3的方法还可包括：接收决策协调器发送的协调失败信息。执行部件收到该协调失败信息后，可以不执行待协调的决策，或者按照其他方式执行该待协调的决策，如顺序执行。
可选地，作为一个实施例，待协调的决策为针对目标操作的决策，上述确定协调后的决策的可行性可包括：获取目标操作的关联信息；根据关联信息，确定协调后的决策的可行性。
以VNF缩放操作的决策为例，关联信息可包括VNF的当前资源状况或VNF的管理限制信息，或者同时包括VNF的当前资源状况或VNF的管理限制信息等。
可选地，作为一个实施例，待协调的决策由网络功能虚拟化系统中的决策部件基于预定策略生成，步骤340之后，图3的方法还可包括：向决策部件发送指示信息，指示信息用于指示协调后的决策的执行结果。
例如，待协调的决策由NFVO生成，指示将VNF缩小40％，协调后的决策指示将VNF缩小30％，VNFM执行该决策之后，向NFVO返回VNF当前占据的资源状况等，从而让NFVO获知该VNF已经被缩小，NFVO可以从执行结果中确定VNF缩小的规模是否满足要求，是否需要再次生成请求缩小VNF的决策。
可选地，作为一个实施例，待协调的决策由网络功能虚拟化系统中的决策部件基于预定策略生成，决策协调请求消息还包括决策部件的标识。
应理解，在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
上文中结合图1至图3，详细描述了根据本发明实施例的决策协调方法，下面将结合图4至图7，描述根据本发明实施例的决策协调器和执行部件。
图4是本发明实施例的决策协调器的示意性框图。图4的决策协调器400能够实现图1至图3中由决策协调器执行的各个步骤，为避免重复，适当省 略重复的描述。决策协调器400包括：
接收单元410，用于从网络功能虚拟化系统中的执行部件接收决策协调请求消息，其中，所述决策协调请求消息包括待协调的决策；
第一确定单元420，用于根据所述接收单元410接收的所述待协调的决策，确定协调后的决策；
发送单元430，用于向所述执行部件发送决策协调响应消息，所述决策协调响应消息包括所述第一确定单元420确定的所述协调后的决策，所述决策协调响应消息用于指示所述执行部件执行所述协调后的决策。
本发明实施例中引入决策协调器，执行部件通过该决策协调器，从待协调的决策中确定出协调后的决策，从而仅需要执行协调后的决策，与现有技术相比，更加灵活。
可选地，作为一个实施例，所述待协调的决策为针对目标操作的一个或多个决策，所述协调后的决策为针对所述目标操作的一个最终决策，所述第一确定单元420具体用于根据所述一个或多个决策，确定所述最终决策。
可选地，作为一个实施例，所述多个决策由所述网络功能虚拟化系统中的多个决策部件生成，所述决策协调请求消息还包括所述多个决策部件的标识，所述决策协调器还包括：第二确定单元，用于根据所述多个决策部件的标识与所述多个决策部件的优先级的对应关系，确定所述多个决策部件中优先级最高的决策部件；所述第一确定单元420具体用于将所述多个决策中，由所述优先级最高的决策部件生成的决策确定为所述最终决策。
可选地，作为一个实施例，所述决策协调请求消息中还包括所述执行部件获得所述多个决策的先后顺序，所述第一确定单元420具体用于基于所述先后顺序，将所述多个决策中最先或最后获得的决策确定为所述最终决策。
可选地，作为一个实施例，所述待协调的决策为针对目标操作的决策，所述决策协调器还包括：获取单元，用于从所述网络功能虚拟化系统中的除所述执行部件之外的其他部件获取所述目标操作的关联信息；所述第一确定单元420具体用于根据所述待协调的决策和所述关联信息，确定所述协调后的决策。
可选地，作为一个实施例，所述第一确定单元420具体用于根据所述待协调的决策以及所述关联信息，通过大数据分析，确定所述协调后的决策。
可选地，作为一个实施例，所述发送单元430还用于当未确定出所述协 调后的决策时，向所述执行部件发送决策协调失败信息。
可选地，作为一个实施例，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
可选地，作为一个实施例，所述决策协调请求消息还包括作出所述待协调决策的决策部件的标识。
可选地，作为一个实施例，所述决策部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
可选地，作为一个实施例，所述执行部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
图5是本发明实施例的执行部件的示意性框图。应理解，图5的执行部件500又可称为执行装置，能够实现图1-图3中由执行部件执行的各个步骤，为避免重复，适当省略重复的描述。执行部件500包括：
获取单元510，用于获取待协调的决策；
第一发送单元520，用于向网络功能虚拟化系统中的决策协调器发送决策协调请求消息，其中，所述决策协调请求消息包括所述获取单元510获取的所述待协调的决策，所述决策协调请求消息用于指示所述决策协调器根据所述待协调的决策确定协调后的决策；
接收单元530，用于从所述决策协调器接收决策协调响应消息，所述决策协调响应消息包括所述协调后的决策。
本发明实施例中引入决策协调器，执行部件通过该决策协调器，从待协调的决策中确定出协调后的决策，从而仅需要执行协调后的决策，与现有技术相比，更加灵活。
可选地，作为一个实施例，所述执行部件还包括：确定单元，用于确定所述协调后的决策的可行性；执行单元，用于当所述协调后的决策可行时，执行所述协调后的决策；当所述协调后的决策不可行时，不执行所述协调后的决策。
可选地，作为一个实施例，所述待协调的决策为针对目标操作的决策，所述确定单元具体用于获取所述目标操作的关联信息；根据所述关联信息，确定所述协调后的决策的可行性。
可选地，作为一个实施例，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
可选地，作为一个实施例，所述执行部件还包括：第二发送单元，用于向作出所述待协调的决策的决策部件发送指示信息，所述指示信息用于指示所述协调后的决策的执行结果。
可选地，作为一个实施例，接收单元530还用于接收决策协调器发送的协调失败信息。执行部件500收到该协调失败信息后，可以不执行待协调的决策，或者按照其他方式执行该待协调的决策，如顺序执行。
可选地，作为一个实施例，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成，所述决策协调请求消息还包括作出所述待协调的决策的决策部件的标识。
图6是本发明实施例的决策协调器的示意性框图。图6的决策协调器600能够实现图1至图3中由决策协调器执行的各个步骤，为避免重复，适当省略重复的描述。决策协调器600包括：
接收器610，用于从网络功能虚拟化系统中的执行部件接收决策协调请求消息，其中，所述决策协调请求消息包括待协调的决策；
处理器620，用于根据所述待协调的决策，确定协调后的决策；
发送器630，用于向所述执行部件发送决策协调响应消息，所述决策协调响应消息包括所述协调后的决策，所述决策协调响应消息用于指示所述执行部件执行所述协调后的决策。
本发明实施例中引入决策协调器，执行部件通过该决策协调器，从待协调的决策中确定出协调后的决策，从而仅需要执行协调后的决策，与现有技术相比，更加灵活。
可选地，作为一个实施例，所述待协调的决策为针对目标操作的一个或多个决策，所述协调后的决策为针对所述目标操作的一个最终决策，所述处理器620具体用于根据所述一个或多个决策，确定所述最终决策。
可选地，作为一个实施例，所述多个决策由所述网络功能虚拟化系统中的多个决策部件生成，所述决策协调请求消息还包括所述多个决策部件的标识，所述处理器630还可用于根据所述多个决策部件的标识与所述多个决策部件的优先级的对应关系，确定所述多个决策部件中优先级最高的决策部件；所述处理器630具体用于将所述多个决策中，由所述优先级最高的决策 部件生成的决策确定为所述最终决策。
可选地，作为一个实施例，所述决策协调请求消息中还包括所述执行部件获得所述多个决策的先后顺序，所述处理器630具体用于基于所述先后顺序，将所述多个决策中最先或最后获得的决策确定为所述最终决策。
可选地，作为一个实施例，所述待协调的决策为针对目标操作的决策，所述决策协调器还包括：获取单元，用于从所述网络功能虚拟化系统中的除所述执行部件之外的其他部件获取所述目标操作的关联信息；所述处理器630具体用于根据所述待协调的决策以及所述关联信息，确定所述协调后的决策。
可选地，作为一个实施例，所述处理器630具体用于根据所述待协调的决策以及所述关联信息，通过大数据分析，确定所述协调后的决策。
可选地，作为一个实施例，所述发送器630还用于当未确定出所述协调后的决策时，向所述执行部件发送决策协调失败信息。
可选地，作为一个实施例，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
可选地，作为一个实施例，所述决策协调请求消息还包括作出所述待协调决策的决策部件的标识。
可选地，作为一个实施例，所述决策部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
可选地，作为一个实施例，所述执行部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
图7是本发明实施例的执行部件的示意性框图。应理解，图7的执行部件700，又可称为执行装置，能够实现图1-图3中由执行部件执行的各个步骤，为避免重复，适当省略重复的描述。执行部件700包括：
处理器710，用于获取待协调的决策；
发送器720，用于向网络功能虚拟化系统中的决策协调器发送决策协调请求消息，其中，所述决策协调请求消息包括所述待协调的决策，所述决策协调请求消息用于指示所述决策协调器根据所述待协调的决策确定协调后的决策；
接收器730，用于从所述决策协调器接收决策协调响应消息，所述决策协调响应消息包括所述协调后的决策；
处理器710还用于执行所述协调后的决策。
本发明实施例中引入决策协调器，执行部件通过该决策协调器，从待协调的决策中确定出协调后的决策，从而仅需要执行协调后的决策，与现有技术相比，更加灵活。
可选地，作为一个实施例，所述处理器710还用于确定所述协调后的决策的可行性；所述处理器710具体用于当所述协调后的决策可行时，执行所述协调后的决策；当所述协调后的决策不可行时，不执行所述协调后的决策。
可选地，作为一个实施例，所述待协调的决策为针对目标操作的决策，所述确定单元具体用于获取所述目标操作的关联信息；根据所述关联信息，确定所述协调后的决策的可行性。
可选地，作为一个实施例，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
可选地，作为一个实施例，所述发送器720还用于向作出所述待协调的决策的决策部件发送指示信息，所述指示信息用于指示所述协调后的决策的执行结果。
可选地，作为一个实施例，所述决策协调请求消息还包括作出所述待协调的决策的决策部件的标识。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可 以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本发明实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (30)

  1. 一种网络功能虚拟化系统中决策协调的方法，其特征在于，包括：
    从网络功能虚拟化系统中的执行部件接收决策协调请求消息，其中，所述决策协调请求消息包括待协调的决策；
    根据所述待协调的决策，确定协调后的决策；
    向所述执行部件发送决策协调响应消息，所述决策协调响应消息包括所述协调后的决策，所述决策协调响应消息用于指示所述执行部件执行所述协调后的决策。
  2. 如权利要求1所述的方法，其特征在于，所述待协调的决策为针对目标操作的一个或多个决策，所述协调后的决策为针对所述目标操作的一个最终决策，
    所述根据所述待协调的决策，确定协调后的决策，包括：
    根据所述一个或多个决策，确定所述最终决策。
  3. 如权利要求2所述的方法，其特征在于，所述多个决策由所述网络功能虚拟化系统中的多个决策部件生成，所述决策协调请求消息还包括所述多个决策部件的标识，
    在所述根据所述多个决策，确定所述最终决策之前，所述方法还包括：
    根据所述多个决策部件的标识与所述多个决策部件的优先级的对应关系，确定所述多个决策部件中优先级最高的决策部件；
    所述根据所述多个决策，确定所述最终决策，包括：
    将所述多个决策中，由所述优先级最高的决策部件生成的决策确定为所述最终决策。
  4. 如权利要求2所述的方法，其特征在于，所述决策协调请求消息中还包括所述执行部件获得所述多个决策的先后顺序，
    所述根据所述多个决策，确定所述最终决策，包括：
    基于所述先后顺序，将所述多个决策中最先或最后获得的决策确定为所述最终决策。
  5. 如权利要求1所述的方法，其特征在于，所述待协调的决策为针对目标操作的决策，
    在所述根据所述待协调的决策，确定协调后的决策之前，所述方法还包括：
    从所述网络功能虚拟化系统中获取所述目标操作的关联信息；
    则所述根据所述待协调的决策，确定协调后的决策，包括：
    根据所述待协调的决策和所述关联信息，确定所述协调后的决策。
  6. 如权利要求5所述的方法，其特征在于，所述根据所述待协调的决策和所述关联信息，确定所述协调后的决策，包括：
    根据所述待协调的决策和所述关联信息，通过大数据分析，确定所述协调后的决策。
  7. 如权利要求1-6中任一项所述的方法，其特征在于，所述向所述执行部件发送所述决策协调响应消息还包括：
    当未确定出所述协调后的决策时，向所述执行部件发送决策协调失败信息。
  8. 如权利要求1-7中任一项所述的方法，其特征在于，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
  9. 如权利要求3或8所述的方法，其特征在于，其中所述决策部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
  10. 如权利要求1-9中任一项所述的方法，其特征在于，其中所述执行部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
  11. 一种网络功能虚拟化系统中的决策协调方法，其特征在于，包括：
    获取待协调的决策；
    向网络功能虚拟化系统中的决策协调器发送决策协调请求消息，其中，所述决策协调请求消息包括所述待协调的决策，所述决策协调请求消息用于指示所述决策协调器根据所述待协调的决策确定协调后的决策；
    从所述决策协调器接收决策协调响应消息，所述决策协调响应消息包括所述协调后的决策。
  12. 如权利要求11所述的方法，其特征在于，所述方法还包括：
    确定所述协调后的决策的可行性；
    当所述协调后的决策可行时，执行所述协调后的决策。
  13. 如权利要求12所述的方法，其特征在于，所述待协调的决策为针对目标操作的决策，
    所述确定所述协调后的决策的可行性，包括：
    获取所述目标操作的关联信息；
    根据所述关联信息，确定所述协调后的决策的可行性。
  14. 如权利要求11-13中任一项所述的方法，其特征在于，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
  15. 如权利要求11-14中任一项所述的方法，其特征在于，在所述执行所述协调后的决策之后，所述方法还包括：
    向作出所述待协调的决策的决策部件发送指示信息，所述指示信息用于指示所述协调后的决策的执行结果。
  16. 一种网络功能虚拟化系统中的决策协调器，其特征在于，包括：
    接收单元，用于从网络功能虚拟化系统中的执行部件接收决策协调请求消息，其中，所述决策协调请求消息包括待协调的决策；
    第一确定单元，用于根据所述接收单元接收的所述待协调的决策，确定协调后的决策；
    发送单元，用于向所述执行部件发送决策协调响应消息，所述决策协调响应消息包括所述第一确定单元确定的所述协调后的决策，所述决策协调响应消息用于指示所述执行部件执行所述协调后的决策。
  17. 如权利要求16所述的决策协调器，其特征在于，所述待协调的决策为针对目标操作的一个或多个决策，所述协调后的决策为针对所述目标操作的一个最终决策，
    所述第一确定单元具体用于根据所述接收单元接收的所述一个或多个决策，确定所述最终决策。
  18. 如权利要求17所述的决策协调器，其特征在于，所述多个决策由所述网络功能虚拟化系统中的多个决策部件生成，所述决策协调请求消息还包括所述多个决策部件的标识，
    所述决策协调器还包括：第二确定单元，用于根据所述多个决策部件的标识与所述多个决策部件的优先级的对应关系，确定所述多个决策部件中优先级最高的决策部件；
    所述第一确定单元具体用于在所述接收单元接收的所述多个决策中，由所述优先级最高的决策部件生成的决策确定为所述最终决策。
  19. 如权利要求17所述的决策协调器，其特征在于，所述决策协调请 求消息中还包括所述执行部件获得所述多个决策的先后顺序，
    所述第一确定单元具体用于基于所述先后顺序，将所述多个决策中最先或最后获得的决策确定为所述最终决策。
  20. 如权利要求16所述的决策协调器，其特征在于，所述待协调的决策为针对目标操作的决策，
    所述决策协调器还包括：获取单元，用于从所述网络功能虚拟化系统中获取所述目标操作的关联信息；
    所述第一确定单元具体用于根据所述待协调的决策和所述关联信息，确定所述协调后的决策。
  21. 如权利要求20所述的决策协调器，其特征在于，所述第一确定单元具体用于根据所述待协调的决策和所述关联信息，通过大数据分析，确定所述协调后的决策。
  22. 如权利要求16-21中任一项所述的决策协调器，其特征在于，所述发送单元还用于当未确定出所述协调后的决策时，向所述执行部件发送决策协调失败信息。
  23. 如权利要求18所述的决策协调器，其特征在于，所述决策部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
  24. 如权利要求16-23中任一项所述的决策协调器，其特征在于，所述执行部件为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
  25. 一种网络功能虚拟化系统中的执行装置，其特征在于，包括：
    获取单元，用于获取待协调的决策；
    第一发送单元，用于向网络功能虚拟化系统中的决策协调器发送决策协调请求消息，其中，所述决策协调请求消息包括所述获取单元获取的所述待协调的决策，所述决策协调请求消息用于指示所述决策协调器根据所述待协调的决策确定协调后的决策；
    接收单元，用于从所述决策协调器接收决策协调响应消息，所述决策协调响应消息包括所述协调后的决策。
  26. 如权利要求25所述的执行装置，其特征在于，所述执行装置还包括：
    确定单元，用于确定所述协调后的决策的可行性；
    执行单元，用于当所述协调后的决策可行时，执行所述协调后的决策；当所述协调后的决策不可行时，不执行所述协调后的决策。
  27. 如权利要求26所述的执行装置，其特征在于，所述待协调的决策为针对目标操作的决策，所述确定单元具体用于获取所述目标操作的关联信息；根据所述关联信息，确定所述协调后的决策的可行性。
  28. 如权利要求25-27中任一项所述的执行装置，其特征在于，所述待协调的决策由所述网络功能虚拟化系统中的决策部件基于预定策略生成。
  29. 如权利要求25-28中任一项所述的执行装置，其特征在于，所述执行部件还包括：
    第二发送单元，用于向作出所述待协调的决策的决策部件发送指示信息，所述指示信息用于指示所述协调后的决策的执行结果。
  30. 如权利要求25-29中任一项所述的执行装置，其特征在于，所述执行装置为网络功能虚拟化编排器、虚拟网络功能管理器、虚拟化基础设施管理器、组件管理系统、运营支撑系统或业务支撑系统。
PCT/CN2015/080241 2014-10-10 2015-05-29 决策协调方法、执行装置和决策协调器 WO2016054922A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15848256.2A EP3197102A4 (en) 2014-10-10 2015-05-29 Decision coordination method, implementation device and decision coordinator
US15/481,751 US10567196B2 (en) 2014-10-10 2017-04-07 Decision coordination method, execution apparatus, and decision coordinator

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410529933.X 2014-10-10
CN201410529933.XA CN105577499B (zh) 2014-10-10 2014-10-10 决策协调方法、执行装置和决策协调器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/481,751 Continuation US10567196B2 (en) 2014-10-10 2017-04-07 Decision coordination method, execution apparatus, and decision coordinator

Publications (1)

Publication Number Publication Date
WO2016054922A1 true WO2016054922A1 (zh) 2016-04-14

Family

ID=55652551

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/080241 WO2016054922A1 (zh) 2014-10-10 2015-05-29 决策协调方法、执行装置和决策协调器

Country Status (4)

Country Link
US (1) US10567196B2 (zh)
EP (1) EP3197102A4 (zh)
CN (1) CN105577499B (zh)
WO (1) WO2016054922A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107623712A (zh) * 2016-07-15 2018-01-23 Kt株式会社 网络功能虚拟化环境中的虚拟客户端设备服务提供系统及用于其的网络功能虚拟云
WO2018138553A1 (en) * 2017-01-30 2018-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatuses and products for automated network management
EP3461087A4 (en) * 2016-06-16 2019-04-24 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR MANAGING NETWORK SLICE RESOURCES
CN115981610A (zh) * 2023-03-17 2023-04-18 科大国创软件股份有限公司 一种基于Lua脚本实现的光伏储能系统的综合运算平台

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106685683A (zh) * 2015-11-11 2017-05-17 中兴通讯股份有限公司 管理指示发送、vnf自动伸缩功能的管理方法及装置
CN108370328B (zh) * 2016-04-28 2020-09-11 华为技术有限公司 一种nfv mano策略描述符的管理方法及装置
CN107483222B (zh) * 2016-06-08 2021-08-27 中兴通讯股份有限公司 一种基于微服务化的虚拟网络功能的管理方法及网管系统
US10768920B2 (en) * 2016-06-15 2020-09-08 Microsoft Technology Licensing, Llc Update coordination in a multi-tenant cloud computing environment
PL3484547T3 (pl) 2016-07-15 2022-08-16 Eli Lilly And Company Moduł wykrywania dawki w wyrobie do dostarczania leku
WO2018014172A1 (zh) * 2016-07-19 2018-01-25 华为技术有限公司 核心网中业务处理的方法和网络设备
US10698713B2 (en) * 2016-11-29 2020-06-30 Red Hat Israel, Ltd. Virtual processor state switching virtual machine functions
CN110417568B (zh) * 2018-04-28 2021-10-26 华为技术有限公司 Nfv策略协商方法及系统
US11240135B1 (en) 2018-05-23 2022-02-01 Open Invention Network Llc Monitoring VNFCs that are composed of independently manageable software modules
JP7260820B2 (ja) * 2019-08-20 2023-04-19 日本電信電話株式会社 処理装置、処理システム、処理方法、および処理プログラム
CN114513424B (zh) * 2020-10-26 2024-09-27 中国移动通信有限公司研究院 网络服务扩缩容处理方法、装置、设备及可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102081754A (zh) * 2011-01-26 2011-06-01 王爱民 多专家动态协调评判方法及智能化辅助决策支持系统
CN103179642A (zh) * 2013-03-05 2013-06-26 北京邮电大学 具有网络接口自治选择功能的多接口终端及其工作方法
CN103974387A (zh) * 2013-01-25 2014-08-06 电信科学技术研究院 一种网络选择方法和装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7328261B2 (en) * 2001-11-21 2008-02-05 Clearcube Technology, Inc. Distributed resource manager
CN102655532B (zh) * 2012-04-18 2014-10-22 上海和辰信息技术有限公司 分布式异构虚拟资源集成管理方法及系统
CN104335162B (zh) * 2012-05-09 2018-02-23 英特尔公司 使用多个页表的执行
US9336031B2 (en) * 2013-02-27 2016-05-10 International Business Machines Corporation Managing allocation of hardware resources in a virtualized environment
JP6441951B2 (ja) * 2014-02-19 2018-12-19 コンヴィーダ ワイヤレス， エルエルシー システム間モビリティのためのサービングゲートウェイ拡張
US10298714B2 (en) * 2014-06-11 2019-05-21 Convida Wireless, Llc Mapping service for local content redirection
US10129206B2 (en) * 2015-06-05 2018-11-13 Cisco Technology, Inc. Addressing and managing an internal network of a virtual branch node
US20170031699A1 (en) * 2015-07-29 2017-02-02 Netapp, Inc. Multiprocessing Within a Storage Array System Executing Controller Firmware Designed for a Uniprocessor Environment
US10257166B2 (en) * 2016-08-30 2019-04-09 Red Hat Israel, Ltd Guest netfilter protection by virtual machine function
US10642972B2 (en) * 2016-10-20 2020-05-05 Intel Corporation Extending packet processing to trusted programmable and fixed-function accelerators

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102081754A (zh) * 2011-01-26 2011-06-01 王爱民 多专家动态协调评判方法及智能化辅助决策支持系统
CN103974387A (zh) * 2013-01-25 2014-08-06 电信科学技术研究院 一种网络选择方法和装置
CN103179642A (zh) * 2013-03-05 2013-06-26 北京邮电大学 具有网络接口自治选择功能的多接口终端及其工作方法

Non-Patent Citations (1)

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

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3461087A4 (en) * 2016-06-16 2019-04-24 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR MANAGING NETWORK SLICE RESOURCES
CN107623712A (zh) * 2016-07-15 2018-01-23 Kt株式会社 网络功能虚拟化环境中的虚拟客户端设备服务提供系统及用于其的网络功能虚拟云
CN107623712B (zh) * 2016-07-15 2023-01-10 Kt株式会社 网络功能虚拟化环境中的虚拟客户端设备服务提供系统及用于其的网络功能虚拟云
WO2018138553A1 (en) * 2017-01-30 2018-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatuses and products for automated network management
CN115981610A (zh) * 2023-03-17 2023-04-18 科大国创软件股份有限公司 一种基于Lua脚本实现的光伏储能系统的综合运算平台
CN115981610B (zh) * 2023-03-17 2023-06-02 科大国创软件股份有限公司 一种基于Lua脚本实现的光伏储能系统的综合运算平台

Also Published As

Publication number Publication date
EP3197102A4 (en) 2017-10-25
US10567196B2 (en) 2020-02-18
CN105577499A (zh) 2016-05-11
EP3197102A1 (en) 2017-07-26
US20170214544A1 (en) 2017-07-27
CN105577499B (zh) 2019-05-28

Similar Documents

Publication Publication Date Title
WO2016054922A1 (zh) 决策协调方法、执行装置和决策协调器
US10601656B2 (en) Network element upgrade method and device
US11277306B2 (en) Sending information of a network repository function instance storing network function instance information
US11032214B2 (en) Method, apparatus, and system for managing network slice instance
US20190123963A1 (en) Method and apparatus for managing resources of network slice
US10644952B2 (en) VNF failover method and apparatus
US20200177458A1 (en) Cloud zone network analytics platform
WO2018171459A1 (zh) 网络切片的管理方法和装置
US20200162345A1 (en) Method, system and options for multi-operator service life cycle management
CN108400998B (zh) 一种部署vnf的方法和系统
KR20210020084A (ko) 경보 방법 및 디바이스
CN104584484A (zh) 提供基于策略的数据中心网络自动化的系统和方法
US11811632B2 (en) Systems and methods for high availability and performance preservation for groups of network functions
US10447703B2 (en) VNF package operation method and apparatus
US20180062946A1 (en) Method and Apparatus for Establishing Network Service Instance
US11902109B2 (en) Method of network slice resource allocation and visualization
WO2019029704A1 (zh) 网络对象管理方法及其装置
CN109417501A (zh) 网络资源的编排方法和设备
WO2017133020A1 (zh) 一种nfv系统中的策略传输方法和装置
WO2018127068A1 (zh) 网络管理方法和装置
CN114143185B (zh) 一种网络通信的方法及装置、电子设备、存储介质
US11271859B2 (en) Method and apparatus for realizing intelligent traffic scheduling, computer readable storage medium thereof and computer device
JP5523599B1 (ja) ネットワークシステムの資源管理システムおよび方法

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: 15848256

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015848256

Country of ref document: EP