CN110417568B

CN110417568B - NFV strategy negotiation method and system

Info

Publication number: CN110417568B
Application number: CN201810399834.2A
Authority: CN
Inventors: 祝宁
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-04-28
Filing date: 2018-04-28
Publication date: 2021-10-26
Anticipated expiration: 2038-04-28
Also published as: CN110417568A; WO2019206234A1

Abstract

A method and a system for NFV policy negotiation are provided. The method comprises the following steps: a first network element receives strategy request information and generates a first strategy according to a local strategy of the first network element and a strategy request reason parameter carried in the request information; the first network element sends a policy negotiation request message to a second network element, wherein the policy negotiation request message comprises a policy request reason parameter, a first policy and the priority of the first policy; wherein the first network element and the second network element belong to different NFV management domains; the second network element carries out policy evaluation according to the reason parameters carried by the policy negotiation request message to generate a second policy; and the second network element compares the priorities of the first strategy and the second strategy, and generates and sends corresponding strategy indication information to the first network element. The strategy decision points of different management domains can make correct strategy decision by carrying out strategy negotiation, thereby avoiding the strategy decision points of different domains from making contradictory or repeated strategy decision.

Description

NFV strategy negotiation method and system

Technical Field

The present application relates to the field of computers, and in particular, to a method and a system for NFV policy negotiation.

Background

As shown in fig. 1, an architecture diagram of a Network Function Virtualization (NFV) provided in the prior art, an architecture of the NFV is divided into two management domains: one is a 3GPP management domain, which mainly includes Network Management (NM) and Element Management (EM) in the left frame, and mainly is operation and maintenance from an application layer to a service layer, and also considers information of a resource layer; the other is a management and organization (MANO) domain, such as the right frame in fig. 1, which is mainly responsible for the lifecycle management of Network Service (NS) and Virtual Network Function (VNF) entities, and is an operation and maintenance on the resource level.

As shown in fig. 2a, a framework diagram for policy management of a MANO domain provided in the prior art, a Policy Administration Point (PAP) centrally issues policy rules, and policy decision Points (PFs) are distributed on a Network Function Virtualization (NFVO), a VNF manager (VNF manager, VNFM), and a Virtual Infrastructure Management (VIM) for local decision making. This architecture requires the addition of new components on the NFV architecture.

Another framework diagram for policy management of MANO domains provided by the prior art, as shown in fig. 2b, proposes a distributed PAP concept, with PAP functions located in multiple network elements, respectively. This architecture NFV architecture does not require the addition of new components.

PAP, whether distributed or centralized, enables lifecycle management, self-healing and virtual resource management for NS and VNFs to be automated via a MANO policy management framework.

The EM/NM may also perform automated fault analysis and self-healing. The EM collects alarm information from the network element and the VNFM and reports the alarm information to the NM, and both the EM and the NM can carry out automatic fault detection, fault root analysis and self-healing action issuing in the management range. Thus, both NM and EM can be policy enforcement points if automated fault management is implemented through policy driven.

Fig. 3 is a schematic flowchart of a policy-driven implementation of automatic fault management in a 3GPP management domain, where the policy-driven implementation includes the following steps:

step 1 a: a non-virtualized NE (i.e. a Physical Network Function (PNF) network element shown in fig. 1) network element reports an alarm to the EM;

step 1 b: the virtualized NE (e.g., VNF a) reports an alarm to the EM: the burst rise of the traffic volume comprises the receiving of a large number of abnormal service messages;

step 1c, the VIM reports an alarm of resource layer resource shortage to the VNFM;

step 2, the VNFM performs association between the resource layer and the VNF, sends VNF A-related virtual resource alarm to the EM, and the VNF A resource occupancy rate reaches an alarm threshold value;

step 3, the EM sends the alarms collected from various sources to an Operation Support System (OSS) (specifically, NM);

and 4, the EM carries out strategy decision according to the fault analysis strategy rules set on the EM, and carries out fault association and fault root cause analysis. Different environmental contexts may lead to different policy decisions, the EM may make two different decisions:

step 5a (option 1): the EM finds a wrong service configuration on the VNF B, which causes the VNF B to send a large number of service packets to the VNF a, where many wrong packets are also included. The EM issues a configuration change command to the VNF B, and the traffic on the VNF A is recovered to be normal;

and 5b (option 2), if the EM decides to expand the volume of the VNF A, the EM sends a related life cycle management message to the VNFM. After VNF a expansion, the alarm is removed.

There are multiple policy decision points in the current 3GPP network management architecture (including MANOs). The policy rules of the local domain are usually configured on the policy decision points, and the environment context for making the policy decision is not global information but information available for the local domain. Policy enforcement within a MANO typically operates on the virtual resources of the NFVO through VIM. The policy enforcement of NM and EM is usually the configuration of VNF or the operation of virtual resources through VNFM/NFVO. There is a lack of coordination of policies between different policy decision points (e.g., EM and VNFM), such as:

1. the traffic configuration causes a large burst of traffic flow from VNF a to VNF B, the EM may trigger the VNF a to issue a command to modify the configuration, and direct a part of the traffic flow to VNF C, and the VNFM may trigger the expansion of VNF B according to a resource policy preset in VNFD.

2. Because of resource occupation exception caused by software error in the business layer, actions such as restarting a thread of the VNF, updating software and the like can be triggered on the EM, and a policy of the VNFM may be to expand the volume of the VNF with insufficient resources.

3. Due to LB configuration or user movement, part of the resource occupancy rate of the network element is too high, and the other part of the resource occupancy rate of the network element is too low. The EM may trigger modification of the VNF configuration to adjust traffic to an "idle" network element, and the policy of the VNFM may perform a capacity expansion and reduction operation, and actions of the VNFM and the VNF may conflict to form oscillation.

4. When a virtual network (such as vSwitch) fails, a MANO performs resource layer processing according to a preset policy, but because input information is insufficient, an EM misjudges that the input information is a VNF application layer failure, and performs operations such as restarting or configuration modification on a VNF.

The 3GPP management domain and the MANO management domain respectively have a policy decision point, the environment context for executing the policy is different, the execution point of the policy decision can also be different, and repeated redundancy, contradiction or a correct and wrong decision can be made on a service layer and a resource layer aiming at the same exception, and the decision is executed according to the own policy.

Therefore, in the NFV architecture, how each policy decision point makes a correct policy decision is a problem to be solved at present.

Disclosure of Invention

The application provides an NFV strategy negotiation method and system, so that each strategy decision point can make correct strategy decisions, and contradiction or repeated strategy decisions made by strategy decision points in different domains are avoided.

In a first aspect, a method for NFV policy negotiation is provided, including: a first network element receives strategy request information and generates a first strategy according to a local strategy of the first network element and a strategy request reason parameter carried in the request information; the first network element sends a policy negotiation request message to a second network element, wherein the policy negotiation request message comprises a policy request reason parameter, a first policy and the priority of the first policy; wherein the first network element and the second network element belong to different NFV management domains; the second network element carries out policy evaluation according to the reason parameters carried by the policy negotiation request message to generate a second policy; and the second network element compares the priorities of the first strategy and the second strategy, and generates and sends corresponding strategy indication information to the first network element.

In this aspect, each policy decision point of different management domains can make a correct policy decision by performing policy negotiation, thereby avoiding the policy decision points of different domains from making contradictory or repeated policy decisions.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the receiving, by the first network element, a policy request message includes: the first network element receives a policy request message reported by other network elements of an NFV management domain where the first network element is located, wherein the policy request message comprises a policy request reason parameter.

In this implementation, the first network element serves as a policy decision point of another network element in the NFV management domain where the first network element is located, and receives a policy request message reported by the other network element.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the policy request cause parameter includes resource early warning or failure.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the performing, by the second network element, policy evaluation according to a cause parameter carried in the policy negotiation request message, to generate a second policy includes: if the reason parameter is the resource early warning, acquiring resource and load information of each VNF acquired by other network elements of the NFV management domain where the second network element is located, and generating a second strategy for the VNF causing the resource early warning; or if the cause parameter is a fault, determining whether an application or virtual machine configuration of the NFV management domain where the second network element is located is in error, and generating a second policy for reconfiguring the application or virtual machine.

In this implementation manner, according to different policy request cause parameters, the second network element performs corresponding policy evaluation to generate a corresponding policy.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the policy indication information includes at least one of the following indication information: instructing the first network element to execute the first policy, instructing the first network element not to execute the first policy, and instructing the first network element to execute a third policy adjusted to the first policy.

With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the comparing, by the second network element, the priority of the first policy and the priority of the second policy to generate corresponding policy indication information includes: if the priority of the first policy is higher than that of the second policy, the second network element generates policy indication information indicating that the first network element executes the first policy or generates policy indication information indicating that the first network element executes a third policy adjusted by the first policy; and if the priority of the second strategy is higher than that of the first strategy, the second network element generates strategy indicating information indicating that the first network element does not execute the first strategy.

In this implementation, according to the priorities of the policies made by the two policy decision points, corresponding policy indication information is generated to determine which policy decision point to use for making the policy, or the policy decision point with the higher priority may adjust the policy made by the other policy decision point with the lower priority.

With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the method further includes: and if the priority of the second strategy is higher than that of the first strategy, the second network element generates strategy indication information indicating that the first network element does not execute the first strategy, and executes the second strategy.

In a second aspect, a method for NFV policy negotiation is provided, including: a first network element receives strategy request information and generates a first strategy according to a local strategy of the first network element and a strategy request reason parameter carried in the request information; the first network element sends a policy negotiation request message to a policy arbitration network element, wherein the policy negotiation request message comprises a policy request reason parameter, a first policy, the priority of the first policy and the identifier of a second network element performing policy negotiation with the first network element; wherein the first network element and the second network element belong to different NFV management domains; the policy arbitration network element sends the policy negotiation request message to the second network element; the second network element carries out policy evaluation according to the reason parameters carried by the policy negotiation request message, generates and sends a second policy to the policy arbitration network element; and the policy arbitration network element compares the priorities of the first policy and the second policy, generates and sends corresponding policy arbitration information to the first network element and/or the second network element.

In this aspect, each policy decision point of different management domains performs policy arbitration through the policy arbitration network element, so that a correct policy decision can be made, and the policy decision points of different domains are prevented from making contradictory or repeated policy decisions.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the policy arbitration information includes at least one of: instructing the first network element to execute the first policy or instructing the second network element to execute the second policy.

In various possible implementations of the first aspect or the first aspect above or of the second aspect or the second aspect above, the first network element comprises any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or the first network element comprises any one of: NFVO and VNFM, the second network element comprising any one of: OSS and EMS.

In various possible implementations of the above first aspect or of the second aspect or second aspect, the NFV administrative domain comprises a management and orchestration MANO domain and a 3GPP administrative domain.

In a third aspect, a NFV policy negotiation system is provided, including: a first network element and a second network element; the first network element is used for receiving the strategy request information and generating a first strategy according to a local strategy of the first network element and a strategy request reason parameter carried in the request information; the first network element is further configured to send a policy negotiation request message to a second network element, where the policy negotiation request message includes a policy request cause parameter, a first policy, and a priority of the first policy; wherein the first network element and the second network element belong to different NFV management domains; the second network element is used for performing policy evaluation according to the reason parameter carried by the policy negotiation request message to generate a second policy; and the second network element is also used for comparing the priorities of the first strategy and the second strategy, and generating and sending corresponding strategy indication information to the first network element.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the first network element is configured to receive a policy request message reported by another network element of an NFV management domain where the first network element is located, where the policy request message includes a policy request cause parameter.

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the policy request cause parameter includes resource early warning or failure.

With reference to the third aspect or the first possible implementation manner of the third aspect or the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the second network element is configured to, if the cause parameter is a resource early warning, obtain resource and load information of each VNF acquired by another network element of the NFV management domain where the second network element is located, and generate a second policy for the VNF causing the resource early warning; or the second network element is configured to, if the cause parameter is a failure, determine whether an error occurs in the configuration of the application or virtual machine in the NFV management domain where the second network element is located, and generate a second policy for reconfiguring the application or virtual machine.

With reference to the third aspect or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the policy indication information includes at least one of the following indication information: instructing the first network element to execute the first policy, instructing the first network element not to execute the first policy, and instructing the first network element to execute a third policy adjusted to the first policy.

With reference to the fourth possible implementation manner of the third aspect, in a fifth possible implementation manner of the third aspect, the second network element is configured to generate policy indication information indicating that the first network element executes the first policy or generate policy indication information indicating that the first network element executes a third policy after the first policy is adjusted, if the priority of the first policy is higher than the priority of the second policy; or the second network element is configured to generate policy indication information indicating that the first network element does not execute the first policy, if the priority of the second policy is higher than the priority of the first policy.

With reference to the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner of the third aspect, the second network element is further configured to generate policy indication information indicating that the first network element does not execute the first policy and execute the second policy, if the priority of the second policy is higher than the priority of the first policy.

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner of the third aspect, or the sixth possible implementation manner of the third aspect, in a seventh possible implementation manner of the third aspect, the first network element includes any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or the first network element comprises any one of: NFVO and VNFM, the second network element comprising any one of: OSS and EMS.

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner of the third aspect, or the sixth possible implementation manner of the third aspect, or the seventh possible implementation manner of the third aspect, in an eighth possible implementation manner of the third aspect, the NFV management domain includes a management and orchestration MANO domain and a 3GPP management domain.

In a fourth aspect, a NFV policy negotiation system is provided, including: the system comprises a first network element, a second network element and a policy arbitration network element; the first network element is used for receiving the strategy request information and generating a first strategy according to a local strategy of the first network element and a strategy request reason parameter carried in the request information; the first network element is further configured to send a policy negotiation request message to a policy arbitration network element, where the policy negotiation request message includes a policy request reason parameter, a first policy, a priority of the first policy, and an identifier of a second network element performing policy negotiation with the first network element; wherein the first network element and the second network element belong to different NFV management domains; the policy arbitration network element is configured to send the policy negotiation request message to the second network element; the second network element is used for performing policy evaluation according to the reason parameter carried by the policy negotiation request message, and generating and sending a second policy to the policy arbitration network element; and the policy arbitration network element is further configured to compare priorities of the first policy and the second policy, generate and send corresponding policy arbitration information to the first network element and/or the second network element.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the policy arbitration information includes at least one of: instructing the first network element to execute the first policy or instructing the second network element to execute the second policy.

With reference to the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the first network element includes any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or the first network element comprises any one of: NFVO and VNFM, the second network element comprising any one of: OSS and EMS.

With reference to the fourth aspect or the first possible implementation manner of the fourth aspect or the second possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the NFV management domain includes a management and orchestration MANO domain and a 3GPP management domain.

In a fifth aspect, a computer-readable storage medium is provided, having stored therein instructions, which, when run on a computer, cause the computer to perform the method of the above aspects.

In a sixth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present invention, the drawings required to be used in the embodiments or the background art of the present invention will be described below.

FIG. 1 is a diagram of a network function virtualization architecture provided by the prior art;

FIG. 2a is a block diagram of a policy management framework for managing and orchestrating domains according to the prior art;

FIG. 2b is a block diagram of another policy management framework for managing and orchestrating domains provided by the prior art;

fig. 3 is a schematic flowchart of a policy-driven implementation of automatic fault management in a 3GPP management domain according to the prior art;

fig. 4 is an interaction flow diagram of an NFV policy negotiation method according to an embodiment of the present application;

fig. 5 is an interaction flow diagram illustrating an NFV policy negotiation method in an exemplary communication scenario;

fig. 6 is an interaction flow diagram illustrating an NFV policy negotiation method in another exemplary communication scenario;

fig. 7 is an interaction flow diagram of another NFV policy negotiation method provided in the embodiment of the present application;

fig. 8 is an interaction flow diagram illustrating an NFV policy negotiation method in yet another exemplary communication scenario;

fig. 9 is a schematic structural diagram of an NFV policy negotiation system according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of another NFV policy negotiation system according to an embodiment of the present application.

Detailed Description

The embodiments of the present invention will be described below with reference to the drawings.

The embodiment of the present application can be applied to the architecture of the NFV shown in fig. 1, and is certainly not limited to the architecture of the NFV shown in fig. 1. It can be applied to policy negotiation between any two policy decision points.

As shown in fig. 1, the 3GPP management domain includes, from top to bottom, an Operation Support System (OSS)/service support system (BSS), a Device Manager (DM), and a Network Function (NF) entity. The OSS/BSS is an operation/service support system of the entire NFV architecture, and is responsible for managing operations/services of the entire system. Besides the traditional management function, the OSS/BSS interacts with the NFVO to complete the operation and maintenance of the network aiming at the virtualized application. The DM mainly comprises EM. The NF entities include Physical Network Function (PNF) entities and VNFs. This application relates primarily to VNF.

The MANO management domain, top to bottom, includes NFVO, VNFM and VIM. The NFVO mainly functions to implement NS lifecycle management (such as deployment/capacity expansion/capacity reduction/offline) in an operator domain, and NFVI resource orchestration, policy management, and other functions. The NFVO decomposes the requirements of each VNF according to NS descriptor (NSD), and realizes the deployment of the VNF by matching with VNFM. The VNFM mainly functions to implement life cycle management of the VNF, such as automation capabilities of deployment/capacity expansion/capacity reduction/offline. And the VNFM decomposes the requirements on virtual resources such as a virtual machine and the like according to the template and the VNF capacity requirements, and completes the instantiation of the VNF by matching with the Orchester and the VIM. The VIM functions primarily to manage and monitor the resources of the entire infrastructure layer, including computing, storage, and network resources.

The NFV makes the network element into software, so that the network element can run on various general hardware; and the network element deployment process is automated through the MANO system; the operator can perform the capacity expansion rapidly and dynamically according to the service requirement.

Both NM and EM of the 3GPP management system may be abstracted into PDP. If the fault/anomaly is handled in EM analysis, EM is PDP; and if the scene is a cross-domain and cross-EM scene, the NM is required to perform fault/abnormal analysis processing, and the NM is the PDP. The final policy enforcement point in the 3GPP management system may be the VNF (performing the traffic layer configuration or operation) or the VNFM (performing the VNF lifecycle management related operation, eventually to be operated on the resource by the NFVI). Within the 3GPP management system, different policy decision points are easily coordinated. For example, the policy of the OSS is to be issued to the EM, and the policy of the EM itself may consider the policy of the OSS, and for the VNF, the EM may not receive more than one contradictory policy. The policy sent by the EM to the VNF and the policy sent by the EM to the VNFM are sent by the EM in a unified manner, so that the policy executed by the VNF and the policy executed by the VNFM are not contradictory.

The policy decision point of the MANO management system may be NFVO, VNFM or VIM, and the final policy enforcement point is NFVI. The three strategy decision points are divided, and the strategy decision of a plurality of strategy decision points can not be triggered by the same event in the process.

The method establishes a policy negotiation mechanism between a PDP of a 3GPP management system and a PDP of a MANO management system. Avoiding two management systems from making contradictory or repeated strategies.

The embodiment of the application provides a method and a system for NFV policy negotiation, and each policy decision point of different management domains can make a correct policy decision by performing policy negotiation, so that the policy decision points of different domains are prevented from making contradictory or repeated policy decisions.

As shown in fig. 4, an interaction flow diagram of an NFV policy negotiation method provided in the embodiment of the present application is shown, where the method includes the following steps:

s101, the first network element receives the strategy request information, and generates a first strategy according to the local strategy of the first network element and the strategy request reason parameter carried in the request information.

S102, the first network element sends a policy negotiation request message to a second network element, where the first network element and the second network element belong to different NFV administrative domains, and the policy negotiation request message includes: a policy request cause parameter, a first policy, and a priority of the first policy. The second network element receives the policy negotiation request message.

S103, the second network element carries out policy evaluation according to the reason parameter carried by the policy negotiation request message to generate a second policy.

S104, the second network element compares the priority of the first strategy and the priority of the second strategy to generate corresponding strategy indication information.

S105, the second network element sends the policy indication information to the first network element. The first network element receives the policy indication information.

S106, the first network element executes the strategy indication information.

In S101, a first network element receives policy request information. The first network element may be a network element of a 3GPP administrative domain, or may be a network element of a MANO domain. In this embodiment, the first network element serves as a policy decision point of the NFV management domain. The first network element may receive the policy request information from other network elements of the NFV management domain to which the first network element belongs. The policy request information includes a policy request cause parameter. The policy request cause parameter includes resource pre-warning or failure. And making resource early warning, wherein the resource early warning comprises resource warning, traffic load warning and the like. The resource alarm may refer to an insufficient VNF configuration, and the traffic load alarm may refer to an excessively low or high load on a certain VNF, and the like.

The policy decision points of different NFV management domains may make different policies according to the local policy and the policy request cause parameter. For example, if the first network element is a policy decision point of the 3GPP administrative domain, a policy may be made on traffic load or application troubleshooting; if the first network element is a policy decision point of the MANO management domain, a policy may be made on configuring resources or virtual machine troubleshooting. In this step, the first network element generates the first policy according to the local policy of the first network element and the policy request cause parameter carried in the request information.

In the embodiment, considering the policy for avoiding contradiction or redundancy of policy decision points of the service layer and the resource layer, when the first policy is made by the first network element, policy negotiation should be performed with the second network element. Therefore, proceeding to S102, the first network element sends a policy negotiation request message to the second network element. The first network element is in a different administrative domain than the second network element. For example, if the first network element is a network element of a 3GPP management domain (e.g., EM, NM), the second network element is a network element of a MANO domain (e.g., NFVO, VNFM, or VIM); if the first network element is a network element of a MANO domain (e.g., NFVO, VNFM, or VIM), the second network element is a network element of a 3GPP management domain (e.g., EM, NM). In addition, referring to fig. 1, the first network element and the second network element may also be network elements of different administrative domains of the same hierarchy. For example, if the first network element is NM, the second network element is NFVO; and if the first network element is EM, the second network element is VNFM.

The policy negotiation request message includes: a policy request cause parameter, a first policy, and a priority of the first policy. In the entire NFV architecture, the priority of the policy may be uniformly set.

The second network element receives the policy negotiation request message. And proceeds to S103.

In S103, the second network element performs policy evaluation according to the reason parameter carried in the policy negotiation request message, and generates a second policy. Specifically, after receiving the policy negotiation request message, the second network element adopts different policy evaluation modes according to different reason parameters. If the reason parameter is the resource early warning, acquiring resource and load information of each VNF acquired by other network elements of the NFV management domain where the second network element is located, and generating a second strategy for the VNF causing the resource early warning; or if the cause parameter is a fault, determining whether an application or virtual machine configuration of the NFV management domain where the second network element is located is in error, and generating a second policy for reconfiguring the application or virtual machine. For example, if the cause parameter is the resource early warning, and the second network element is a network element of the 3GPP management domain, the second network element checks each dynamic value of the current FCAPS, analyzes the application layer configuration of each network element in the network service, and the network traffic information of the service layer, and generates the second policy. And if the second network element detects that the load of a certain NFV is overlarge, making a second strategy for transferring the load, and if the load problem of the NFV does not exist, indicating the first network element to execute the first strategy. If the cause parameter is failure, it may be that the failure occurs due to application or virtual machine configuration, if the second network element is a network element of a 3GPP management domain, the second network element detects whether the failure occurs due to application, if so, a second policy is made for the application configuration, and if not, the first network element is instructed to execute the first policy

After the second network element generates the second policy, the process proceeds to S104. In S104, the second network element compares the priority of the first policy with the priority of the first policy, and generates corresponding policy indication information. The policy indication information includes at least one of the following: instructing the first network element to execute the first policy, instructing the first network element not to execute the first policy, and instructing the first network element to execute a third policy adjusted to the first policy.

Specifically, S104 includes:

if the priority of the first policy is higher than that of the second policy, the second network element generates policy indication information indicating that the first network element executes the first policy or generates policy indication information indicating that the first network element executes a third policy adjusted by the first policy;

and if the priority of the second strategy is higher than that of the first strategy, the second network element generates strategy indicating information indicating that the first network element does not execute the first strategy.

Since the first network element and the second network element belong to different administrative domains, the first policy generated by the first network element and the second policy generated by the second network element are policies of different levels, for example, the first policy is a policy for adjusting traffic load, and the second policy is a policy for adjusting resources of the VNF. In this implementation, the second network element may determine, according to the priority of the policy, that is, if the priority of the first policy is higher than the priority of the second policy, the second network element generates policy indication information indicating that the first network element executes the first policy; and if the priority of the first strategy is lower than that of the second strategy, the second network element generates strategy indicating information indicating that the first network element does not execute the first strategy, and the second network element executes the second strategy.

Or although the priority of the first policy is higher than that of the second policy, the second network element considers that the first policy executed by the first network element cannot solve the resource alarm or eliminate the fault, and needs to adjust the first policy. Therefore, the second network element generates policy indication information, where the policy indication information is used to indicate that the first network element executes the policy indication information of the third policy after the first policy is adjusted. For example, the first policy is to reconfigure 30% of the load on the VNF a to the VNF B, but the second network element considers that the load transfer of 30% is not enough and the VNF a may still have resource alarm in combination with the resource information of the VNF a and the VNF B, and then the second network element may instruct the first network element to transfer 40% of the load to the VNF B.

After the second network element generates the corresponding policy indication information, the process proceeds to S105, and the second network element sends the policy indication information to the first network element. According to the foregoing implementation, the policy indication information includes at least one of the following: instructing the first network element to execute the first policy, instructing the first network element not to execute the first policy, and instructing the first network element to execute the adjusted first policy.

The first network element receives the policy indication information. Further the first network element executes the policy indication information.

Specifically, in an implementation manner, if the policy indication information includes policy indication information indicating that the first network element executes the first policy, the first network element executes the first policy. Correspondingly, although the second policy is made by the second network element, the second policy does not need to be executed by the second network element because the priority of the second policy is lower than that of the first policy.

In another implementation, if the policy indication information includes policy indication information indicating that the first network element does not execute the first policy, the first network element does not execute the first policy. Correspondingly, since the second policy has a higher priority than the first policy, the second network element instructs the first network element not to execute the first policy, and the second network element itself executes the second policy it made.

In yet another implementation, if the policy indication information includes an indication that the first network element executes the adjusted first policy, the first network element executes indication information of a third policy that is adjusted to the first policy. Correspondingly, although the second policy is made by the second network element, the second policy does not need to be executed by the second network element because the priority of the second policy is lower than that of the first policy. Meanwhile, since the first policy may not solve the resource alarm or eliminate the fault, and the first policy needs to be adjusted, the second network element may adjust the first policy to obtain a third policy, and instruct the first network element to execute the third policy.

It can be seen that, by using the NFV policy negotiation method of the embodiment of the present application, each policy decision point in different management domains can make a correct policy decision by performing policy negotiation, thereby avoiding the policy decision points in different domains from making contradictory or repeated policy decisions.

How each decision point performs policy negotiation is described below by two example communication scenarios:

scenario 1, VNFM requests policy negotiation from EM:

taking the policy request cause parameter as the resource alarm as an example, fig. 5 is an interaction flow diagram of an NFV policy negotiation method in a communication scenario of an example, where the method may include the following steps:

s201, the VIM obtains resource alarm with the CPU occupancy rate exceeding a threshold value from the VNFI.

S202, the VIM informs the VNFM of the CPU resource alarm.

S203, the VNFM associates the resource alarm to the VNF a. According to the policy rule described in the VNFD, the capacity expansion of the VNF a is to be triggered. However, local policies also require that the policy require policy negotiation with an Element Management System (EMS). Wherein the EMS comprises one or more EM.

S204, the VNFM sends a strategy negotiation request message to the EMS. The policy negotiation request message carries the following information: priority Pri1 of the local execution policy, policy execution reason (CPU occupancy exceeds a threshold), and policy execution action (VNF a is scaled to a specific specification).

S205, after receiving the policy negotiation request message, the EMS triggers policy evaluation to check dynamic values of current error, configuration, accounting, performance, and security (FCAPS). Analyzing the application layer configuration of each network element in the network service and the network traffic information of the service layer, and finding that a large number of wrong messages are sent to the VNF a by the VNF B, which causes the service load of the VNF a to be too high. According to the set policy, the EMS may change the service configuration of the VNF B to solve the problem. And this strategy is of higher priority.

S206, the EMS sends a strategy negotiation response message to the VNFM, and indicates that the capacity of the VNF A is not expanded.

S207, the EMS sends a service configuration command to the VNF B, corrects the error configured before, and causes the VNF B to stop sending a large number of error messages to the VNF a.

Traffic on the VNF A is rapidly reduced, the CPU occupancy rate is normal, and the fault is eliminated.

In this example, if the VNFM does not perform policy negotiation with the EMS, the VNFM makes a policy for expanding the VNF a, and the EMS does not control the VNF B to stop sending a large number of erroneous messages to the VNF a, the problem that the CPU occupancy of the VNF a exceeds the threshold value is still not solved and resources are wasted even if the VNF a is expanded to a large scale. Through negotiation between the VNFM and the EMS, wrong decisions cannot be made at a service layer and a resource layer.

Scenario 2, EM requests policy negotiation from VNFM:

taking the policy request cause parameter as the resource alarm, fig. 6 is an interaction flow diagram of another exemplary NFV policy negotiation method in a communication scenario, where the method may include the following steps:

s301, the EMS collects session values of multiple VNFs, and finds that traffic loads of some VNFs are very high.

S302, EMS finds that the service load of some VNFs of the same type is very low, and the load can be adjusted by changing the service configuration. But the policy to adjust the traffic configuration is configured to require negotiation of the policy with the VNFM.

S303, the EMS sends a policy negotiation request message to the VNFM. The policy negotiation request message carries the following information: priority Pri1 of local policy, policy enforcement reason (VNF a is overloaded), and policy enforcement action (30% traffic load is reconfigured onto VNF B).

S304, after receiving the policy negotiation request message, the VNFM triggers policy evaluation, queries the virtual resource status of the VNF a and the VNF B, finds that the policy to be triggered expands the volume of the VNF a, and contracts the VNF B. Because the local strategy has lower priority, the strategy of the EMS is decided to be adopted, and the expansion and contraction capacity is not triggered locally for a while until the strategy execution effect on the EMS is achieved.

S305, the VNFM sends a strategy negotiation response message to the EMS, and the strategy negotiation response message indicates that the EMS is agreed to execute the strategy.

S306, the EMS sends a service configuration command to the VNF a and the VNF B, and adjusts respective service loads.

The volume expansion and reduction strategies of the VNF A and the VNF B are not triggered on the VNFM, and the load of the VNF A and the load of the VNF B are balanced through configuration change of a business layer.

As a possible implementation, S305 may also be an instruction to reject policy enforcement of the EMS. In this case, the VNFM may trigger its own policy to perform the scaling operation.

As another possible implementation, S305 may also instruct the EMS to perform an adjusted policy, for example, to reconfigure 40% of the traffic load of the VNF a to the VNF B.

In this example, if the EMS does not perform policy negotiation with the VNFM, the EMS performs policy reconfiguration of 30% of the traffic load on the VNF a to the VNF B, and the VNFM performs policy of capacity expansion and capacity reduction on the VNF a and the VNF B. When the load of the VNF a is configured to the VNF B, it is found that the VNF B is shrunk, and a resource alarm may be triggered on the VNF B. The EMS in turn then reconfigures the traffic load portion on VNF B to VNF a. This causes a "ping-pong effect" due to conflicting strategies being made by EMS and VNFM. The EMS avoids making contradictory strategies at the service layer and the resource layer by carrying out strategy negotiation with the VNFM.

According to the NFV policy negotiation method provided by the embodiment of the application, each policy decision point of different management domains can make a correct policy decision by performing policy negotiation, so that the policy decision points of different domains are prevented from making contradictory or repeated policy decisions.

As shown in fig. 7, an interaction flow diagram of another NFV policy negotiation method provided in the embodiment of the present application is shown, where the method includes the following steps:

s401, the first network element receives the strategy request information, and generates a first strategy according to the local strategy of the first network element and the strategy request reason parameter carried in the request information.

S402, the first network element sends a strategy negotiation request message to a strategy arbitration network element. And the strategy arbitration network element receives the strategy negotiation request message. Wherein the policy negotiation request message includes: the method comprises the steps that a policy request reason parameter, a first policy, the priority of the first policy and the identification of a second network element performing policy negotiation with the first network element are obtained; wherein the first network element and the second network element belong to different NFV management domains.

S403, the policy arbitration network element sends the policy negotiation request message to the second network element. The second network element receives the policy negotiation request message.

S404, the second network element carries out strategy evaluation according to the reason parameter carried by the strategy negotiation request message, and generates a second strategy.

S405, the second network element sends a second policy to the policy arbitration network element. The policy arbitration network element receives the second policy.

S406, the policy arbitration network element compares the priorities of the first policy and the second policy to generate corresponding policy arbitration information.

S407, the policy arbitration network element sends the policy arbitration information to the first network element and/or the second network element. The first network element and/or the second network element receives the policy arbitration information.

Unlike the previous embodiments, the policy negotiating party does not directly send the policy negotiation request message to another policy negotiating party, but forwards it through the policy arbitration network element. And generating corresponding policy indication information by the policy arbitration network element according to the priorities of the first policy and the second policy. The strategy arbitration network element carries out strategy arbitration uniformly, and the workload of any strategy negotiation party can be reduced.

The policy arbitration network element can be physically deployed on the existing management function nodes such as NM and EM.

In this embodiment, the policy negotiation request message should carry an identifier of a negotiation party, that is, the first network element wants to negotiate with which network element, the identifier of the negotiation party is carried. For example, in this embodiment, the identifier of the second network element that performs policy negotiation with the first network element should be carried. And the strategy arbitration network element sends the strategy negotiation request message to the second network element identified by the negotiation party identification according to the received strategy negotiation request message. And the second network element carries out strategy evaluation according to the reason parameters carried by the strategy negotiation request message and generates a second strategy. Reference may be made in particular to the preceding embodiments. Then, the second network element sends the second policy to the policy arbitration network element. The policy arbitration network element may generate corresponding policy arbitration information according to the priority of the first policy and the priority of the second policy, and send the policy arbitration information to the first network element and/or the second network element. If the policy arbitration information indicates that the first network element executes the first policy, the first network element executes the first policy after receiving the policy arbitration information; and if the policy arbitration information indicates that the second network element executes the second policy, the second network element executes the second policy after receiving the policy arbitration information.

How a logically independent policy arbitration component (which may be physically deployed on an existing management function node such as NM, EM, etc.) makes policy decisions is described below in conjunction with an exemplary specific scenario:

taking the policy request cause parameter as the resource alarm, fig. 8 is an interaction flow diagram of an NFV policy negotiation method in another exemplary communication scenario, where the method may include the following steps:

s501, the VIM obtains resource alarm with the CPU occupancy rate exceeding a threshold value from the NFVI.

S502, the VIM informs the VNFM of the CPU resource alarm.

S503, the VNFM associates the resource alarm to the VNF a. According to the policy rule in the VNFD, the VNF a needs to be triggered to expand, but the local policy also requires that the policy needs to be negotiated with the EMS.

S504, the VNFM sends a strategy negotiation message to a strategy arbitration network element. The policy negotiation message carries the following information: priority Pri1 of the local execution policy, policy execution reason (CPU occupancy exceeds a threshold), policy execution action (VNF a is scaled to a specific specification), and with whom policy arbitration is done.

And S505, the policy arbitration network element sends the policy of the VNFM to the EMS according to the information carried by the VNFM, wherein the policy negotiation ID is carried. The policy negotiation ID may be an ID generated by the policy arbitration network element for the policy negotiation message after receiving the policy negotiation message.

S506, after receiving the policy negotiation request message, the EMS triggers policy evaluation to check dynamic values of the current FCAPS. Analyzing the application layer configuration of each network element in the network service and the network traffic information of the service layer, and finding that a large number of wrong messages are sent to the VNF a by the VNF B, which causes the service load of the VNF a to be too high. According to the set policy, the EMS may change the service configuration of the VNF B to solve the problem.

S507, EMS sends strategy negotiation information to strategy arbitration network element, the carried information includes priority Pri1 of local execution strategy, reason of strategy execution, action of strategy execution and ID of strategy negotiation.

S508, the strategy arbitration network element selects to execute the EMS strategy according to the priority of the EMS and VNFM strategies.

S509, the strategy arbitration network element sends a strategy arbitration result to the EM, and the EM is agreed to execute the strategy.

S510, the strategy arbitration network element sends a strategy arbitration result to the VNFM, and the VNFM is not approved to execute the strategy.

S511, the EMS sends a service configuration command to the VNF B, corrects the error configured before, and stops sending a large number of error messages to the VNF a by the VNF B.

Unlike the previous example, the policy negotiating party does not directly send the policy negotiation request message to another policy negotiating party, but forwards it through the policy arbitration network element. And generating corresponding policy indication information by the policy arbitration network element according to the priorities of the first policy and the second policy. The strategy arbitration network element carries out strategy negotiation uniformly, and the workload of any strategy negotiation party can be reduced.

According to the NFV policy negotiation method provided in the embodiment of the present application, each policy decision point in different management domains sends its own policy to the policy arbitration network element, the policy arbitration network element performs policy arbitration in a unified manner, and sends the policy arbitration result to the corresponding policy decision point for execution, so that it is possible to avoid making contradictory or repeated policy decisions by the policy decision points in different domains.

The method of embodiments of the present invention is set forth above in detail and the apparatus of embodiments of the present invention is provided below.

Fig. 9 is a schematic structural diagram of an NFV policy negotiation system according to an embodiment of the present application, where the system 1000 includes a first network element 11 and a second network element 12; wherein:

the first network element 11 is configured to receive policy request information, and generate a first policy according to a local policy of the first network element and a policy request cause parameter carried in the request information; the first network element 11 is further configured to send a policy negotiation request message to a second network element, where the policy negotiation request message includes a policy request reason parameter, a first policy, and a priority of the first policy; wherein the first network element and the second network element belong to different NFV management domains; the second network element 12 is configured to perform policy evaluation according to the reason parameter carried in the policy negotiation request message, and generate a second policy; and the second network element 12 is further configured to compare priorities of the first policy and the second policy, and generate and send corresponding policy indication information to the first network element.

In an implementation manner, the first network element 11 is configured to receive a policy request message reported by another network element of an NFV management domain where the first network element is located, where the policy request message includes a policy request cause parameter.

In another implementation, the policy request cause parameter includes resource pre-warning or failure.

In another implementation manner, the second network element 12 is configured to, if the cause parameter is a resource early warning, acquire resource and load information of each VNF acquired by another network element of the NFV management domain where the second network element is located, and generate a second policy for the VNF causing the resource early warning; or the second network element 12 is configured to, if the cause parameter is a failure, determine whether an error occurs in the configuration of the application or virtual machine in the NFV management domain where the second network element is located, and generate a second policy for reconfiguring the application or virtual machine.

In yet another implementation, the policy indication information includes at least one of the following: instructing the first network element to execute the first policy, instructing the first network element not to execute the first policy, and instructing the first network element to execute a third policy adjusted to the first policy.

In yet another implementation, the second network element 12 is configured to generate policy indication information indicating that the first network element executes the first policy or generate policy indication information indicating that the first network element executes a third policy after the first policy is adjusted, if the priority of the first policy is higher than the priority of the second policy; or the second network element 12 is configured to generate policy indication information indicating that the first network element does not execute the first policy, if the priority of the second policy is higher than the priority of the first policy.

In yet another implementation, the second network element 12 is further configured to generate policy indication information indicating that the first network element does not execute the first policy and execute the second policy if the priority of the second policy is higher than the priority of the first policy.

In yet another implementation, the first network element includes any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or the first network element comprises any one of: NFVO and VNFM, the second network element comprising any one of: OSS and EMS.

In yet another implementation, the NFV administrative domains include a management and orchestration MANO domain and a 3GPP administrative domain.

According to the NFV policy negotiation system provided in the embodiment of the present application, each policy decision point in different management domains can make a correct policy decision by performing policy negotiation, thereby avoiding the policy decision points in different domains from making contradictory or repeated policy decisions.

Fig. 10 is a schematic structural diagram of another NFV policy negotiation system provided in an embodiment of the present application, where the system 2000 includes: a first network element 21, a policy arbitration network element 22 and a second network element 23; wherein:

the first network element 21 is configured to receive policy request information, and generate a first policy according to a local policy of the first network element and a policy request cause parameter carried in the request information; the first network element 21 is further configured to send a policy negotiation request message to a policy arbitration network element, where the policy negotiation request message includes a policy request reason parameter, a first policy, a priority of the first policy, and an identifier of a second network element performing policy negotiation with the first network element; wherein the first network element and the second network element belong to different NFV management domains; the policy arbitration network element 22 is configured to send the policy negotiation request message to the second network element; the second network element 23 is configured to perform policy evaluation according to the reason parameter carried in the policy negotiation request message, and generate and send a second policy to the policy arbitration network element; and the policy arbitration network element 24 is further configured to compare the priorities of the first policy and the second policy, generate and send corresponding policy arbitration information to the first network element and/or the second network element.

In one implementation, the policy arbitration information includes at least one of: instructing the first network element to execute the first policy or instructing the second network element to execute the second policy.

In another implementation, the first network element includes any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or the first network element comprises any one of: NFVO and VNFM, the second network element comprising any one of: OSS and EMS.

According to the NFV policy negotiation system provided in the embodiment of the present application, each policy decision point in different management domains performs policy arbitration through a policy arbitration network element, so that a correct policy decision can be made, and the policy decision points in different domains are prevented from making contradictory or repeated policy decisions.

Embodiments of the present application also provide a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.

Embodiments of the present application also provide a computer program product containing instructions which, when executed on a computer, cause the computer to perform the method of the above aspects.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in or transmitted over a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)), or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., Digital Versatile Disk (DVD)), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

One of ordinary skill in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the above method embodiments. And the aforementioned storage medium includes: various media that can store program codes, such as a read-only memory (ROM) or a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Claims

1. A Network Function Virtualization (NFV) policy negotiation method is characterized by comprising the following steps:

a first network element receives strategy request information and generates a first strategy according to a local strategy of the first network element and a strategy request reason parameter carried in the request information;

the first network element sends a policy negotiation request message to a second network element, wherein the policy negotiation request message comprises a policy request reason parameter, a first policy and the priority of the first policy; wherein the first network element and the second network element belong to different NFV management domains;

the second network element carries out policy evaluation according to the reason parameters carried by the policy negotiation request message to generate a second policy;

and the second network element compares the priorities of the first strategy and the second strategy, and generates and sends corresponding strategy indication information to the first network element.

2. The method of claim 1, wherein the first network element receiving a policy request message comprises:

the first network element receives a policy request message reported by other network elements of an NFV management domain where the first network element is located, wherein the policy request message comprises a policy request reason parameter.

3. The method of claim 1 or 2, wherein the policy request cause parameter comprises a resource warning or a failure.

4. The method according to any one of claims 1 to 2, wherein the performing, by the second network element, policy evaluation according to a cause parameter carried in the policy negotiation request message to generate a second policy includes:

if the reason parameter is resource early warning, acquiring resource and load information of each virtual network function VNF acquired by other network elements of the NFV management domain where the second network element is located, and generating a second strategy for the VNF causing the resource early warning; or

And if the reason parameter is that a fault occurs, judging whether an error occurs in the configuration of the application or the virtual machine of the NFV management domain where the second network element is located, and generating a second strategy for reconfiguring the application or the virtual machine.

5. The method according to any one of claims 1 to 2, wherein the policy indication information comprises any one of the following indication information: instructing the first network element to execute the first policy, instructing the first network element not to execute the first policy, and instructing the first network element to execute a third policy adjusted to the first policy.

6. The method of claim 5, wherein the second network element compares the priorities of the first policy and the second policy to generate corresponding policy indication information, and wherein the step of generating the corresponding policy indication information comprises:

7. The method of claim 6, wherein the method further comprises:

and if the priority of the second strategy is higher than that of the first strategy, the second network element generates strategy indication information indicating that the first network element does not execute the first strategy, and executes the second strategy.

8. The method of claim 1 or 2, wherein the first network element comprises any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or

The first network element comprises any one of: NFVO and VNFM, the second network element comprising any one of: OSS and EMS.

9. The method according to claim 1 or 2, wherein the NFV administrative domains include a management and orchestration MANO domain and a 3GPP administrative domain.

10. A method for negotiating NFV policy, comprising:

the first network element sends a policy negotiation request message to a policy arbitration network element, wherein the policy negotiation request message comprises a policy request reason parameter, a first policy, the priority of the first policy and the identifier of a second network element performing policy negotiation with the first network element; wherein the first network element and the second network element belong to different NFV management domains;

the policy arbitration network element sends the policy negotiation request message to the second network element;

the second network element carries out policy evaluation according to the reason parameters carried by the policy negotiation request message, generates and sends a second policy to the policy arbitration network element;

and the strategy arbitration network element compares the priorities of the first strategy and the second strategy, generates and sends corresponding strategy arbitration information to the first network element and/or the second network element.

11. The method of claim 10, wherein the policy arbitration information comprises at least one of: instructing the first network element to execute the first policy or instructing the second network element to execute the second policy.

12. The method according to claim 10 or 11, wherein the first network element comprises any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or

13. The method according to claim 10 or 11, wherein the NFV administrative domains include a management and orchestration MANO domain and a 3GPP administrative domain.

14. An NFV policy negotiation system, comprising: a first network element and a second network element;

the first network element is used for receiving the strategy request information and generating a first strategy according to a local strategy of the first network element and a strategy request reason parameter carried in the request information;

the first network element is further configured to send a policy negotiation request message to a second network element, where the policy negotiation request message includes a policy request cause parameter, a first policy, and a priority of the first policy; wherein the first network element and the second network element belong to different NFV management domains;

the second network element is used for performing policy evaluation according to the reason parameter carried by the policy negotiation request message to generate a second policy;

the second network element is further configured to compare priorities of the first policy and the second policy, and generate and send corresponding policy indication information to the first network element.

15. The system of claim 14, wherein:

the first network element is configured to receive a policy request message reported by another network element of the NFV management domain where the first network element is located, where the policy request message includes a policy request cause parameter.

16. The system of claim 14 or 15, wherein the policy request cause parameter comprises a resource warning or a failure.

17. The system of claim 14 or 15, wherein:

the second network element is configured to, if the reason parameter is the resource early warning, acquire resource and load information of each VNF acquired by another network element of the NFV management domain where the second network element is located, and generate a second policy for the VNF causing the resource early warning; or

And the second network element is configured to, if the cause parameter is a failure, determine whether an error occurs in the configuration of the application or virtual machine in the NFV management domain where the second network element is located, and generate a second policy for reconfiguring the application or virtual machine.

18. The system according to claim 14 or 15, wherein the policy indication information includes any one of the following: instructing the first network element to execute the first policy, instructing the first network element not to execute the first policy, and instructing the first network element to execute a third policy adjusted to the first policy.

19. The system of claim 18, wherein:

the second network element is configured to generate policy indication information indicating that the first network element executes the first policy or generate policy indication information indicating that the first network element executes a third policy after the first policy is adjusted, if the priority of the first policy is higher than the priority of the second policy;

the second network element is configured to generate policy indication information indicating that the first network element does not execute the first policy, if the priority of the second policy is higher than the priority of the first policy.

20. The system of claim 19, wherein:

the second network element is further configured to generate policy indication information indicating that the first network element does not execute the first policy and execute the second policy, if the priority of the second policy is higher than the priority of the first policy.

21. The system according to claim 14 or 15, wherein the first network element comprises any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or

22. The system of claim 14 or 15, wherein the NFV administrative domains include a management and orchestration MANO domain and a 3GPP administrative domain.

23. An NFV policy negotiation system, comprising: the system comprises a first network element, a second network element and a policy arbitration network element;

the first network element is further configured to send a policy negotiation request message to a policy arbitration network element, where the policy negotiation request message includes a policy request reason parameter, a first policy, a priority of the first policy, and an identifier of a second network element performing policy negotiation with the first network element; wherein the first network element and the second network element belong to different NFV management domains;

the policy arbitration network element is configured to send the policy negotiation request message to the second network element;

the second network element is used for performing policy evaluation according to the reason parameter carried by the policy negotiation request message, and generating and sending a second policy to the policy arbitration network element;

the policy arbitration network element is further configured to compare priorities of the first policy and the second policy, generate and send corresponding policy arbitration information to the first network element and/or the second network element.

24. The system of claim 23, wherein the policy arbitration information comprises at least one of: instructing the first network element to execute the first policy or instructing the second network element to execute the second policy.

25. The system according to claim 23 or 24, wherein the first network element comprises any one of: the service support system OSS and the network element management system EMS, the second network element comprises any one of the following: a network function virtualization orchestrator NFVO and a virtual network function entity manager VNFM; or

26. The system of claim 23 or 24, wherein the NFV administrative domains include a management and orchestration MANO domain and a 3GPP administrative domain.