[go: up one dir, main page]

WO2019206234A1 - Procédé et système de négociation de politique de nfv - Google Patents

Procédé et système de négociation de politique de nfv Download PDF

Info

Publication number
WO2019206234A1
WO2019206234A1 PCT/CN2019/084343 CN2019084343W WO2019206234A1 WO 2019206234 A1 WO2019206234 A1 WO 2019206234A1 CN 2019084343 W CN2019084343 W CN 2019084343W WO 2019206234 A1 WO2019206234 A1 WO 2019206234A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
network element
network
negotiation
request message
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/084343
Other languages
English (en)
Chinese (zh)
Inventor
祝宁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2019206234A1 publication Critical patent/WO2019206234A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present application relates to the field of computers, and in particular, to an NFV policy negotiation method and system.
  • NFV network function virtualization
  • the NFV architecture is divided into two management domains: one is a 3GPP management domain, mainly including the left frame Network management (NM) and element management (EM), mainly from application level to business layer operation and maintenance, also consider resource layer information; the other is management and orchestration (management and orchestration,
  • the MANO) domain as shown in the right border of Figure 1, is responsible for the lifecycle management of the network service (NS) and virtual network function (VNF) entities, and is the operation and maintenance at the resource level.
  • a framework diagram for policy management of a MANO domain a policy administration point (PAP) centrally issues policy rules, and a policy enforcement point (PF) Distributed in the network function virtualization orchestrator (NFVO), VNF manager (VNFM) and virtual infrastructure management (VIM) for local decision making.
  • PAP policy administration point
  • PF policy enforcement point
  • NFVO network function virtualization orchestrator
  • VNFM VNF manager
  • VIP virtual infrastructure management
  • a framework diagram for policy management of another MANO domain is provided, and a distributed PAP concept is proposed.
  • the functions of the PAP are respectively set in multiple network elements.
  • This architecture NFV architecture does not require the addition of new components.
  • the lifecycle management, self-healing and virtual resource management of NS and VNF can be automated through the MANO policy management framework.
  • EM/NM can also perform automated fault analysis and self-healing.
  • the EM collects alarm information from the NE and the VNFM and reports it to the NM.
  • Both the EM and the NM can perform automatic fault detection, fault root cause analysis, and self-healing actions. Therefore, if automated fault management is implemented through policy-driven, both NM and EM can be used as policy enforcement points.
  • FIG. 3 A schematic diagram of a process driven by the prior art shown in FIG. 3 to implement automatic fault management of a 3GPP management domain, where the process includes the following steps:
  • Step 1a The non-virtualized NE (ie, the physical network function (PNF) shown in FIG. 1) reports the alarm to the EM;
  • PNF physical network function
  • Step 1b The virtualized NE (for example, VNF A) reports an alarm to the EM: the traffic suddenly rises, and includes a service packet that receives a large number of abnormalities;
  • VNF A virtualized NE
  • Step 1c The VIM reports an alarm that the resource layer resource is insufficient to the VNFM.
  • Step 2 The VNFM performs an association between the resource layer and the VNF, and sends a VNF A-related virtual resource alarm to the EM, and the VNF A resource occupancy rate reaches an alarm threshold.
  • Step 3 The EM sends the alarms collected from the various sources to the operational support system (OSS) (specifically, NM);
  • OSS operational support system
  • NM operational support system
  • Step 4 The EM makes policy decisions according to the fault analysis policy rules set on the EM, and performs fault correlation and fault root cause analysis. Different environmental contexts can lead to different policy decisions, and EM can make two different decisions:
  • Step 5a (option 1): The EM finds a faulty service configuration on the VNF B.
  • the VNF B sends a large number of service packets to the VNF A, which also contains many incorrect packets.
  • the EM sends a configuration change command to the VNF B, and the traffic on the VNF A returns to normal.
  • Step 5b (option 2): The EM decision should be used to expand the VNF A, and the EM sends the relevant lifecycle management message to the VNFM. After VNF A is expanded, the alarm is cleared.
  • policy decision points There are multiple policy decision points in the current 3GPP network management architecture (including MANO). These policy decision points usually configure the policy rules of the domain, and the environment context for making policy decisions is not global information, but information available to the domain.
  • the policy execution in MANO is generally to operate on the virtual resources of NFVO through VIM.
  • the policy enforcement of NM and EM is usually the configuration of the VNF or the operation of virtual resources through VNFM/NFVO.
  • EM and VNFM There is a lack of coordination between different policy decision points (such as EM and VNFM), such as:
  • the service configuration causes a large amount of traffic to be transmitted from VNF A to VNF B.
  • the EM can trigger the command to modify the configuration of the VNF A, and part of the traffic is directed to the VNF C.
  • the VNFM may be based on the preset resources in the VNFD.
  • the policy triggers the expansion of VNF B.
  • the EM can trigger the action of restarting the thread and updating the software, and the VNFM strategy may be to expand the VNF with insufficient resources.
  • the EM can trigger the modification of the VNF configuration to adjust the traffic to the "free" network element, and the VNFM policy may perform the expansion and contraction operation, and the actions of the two may cause conflicts and form a shock.
  • the virtual network (such as vSwitch) is faulty.
  • MANO performs resource layer processing according to the preset policy. However, because the input of the input information is insufficient, the EM misjudges the fault of the VNF application layer and restarts or modifies the VNF.
  • the 3GPP management domain and the MANO management domain each have a policy decision point.
  • the environment context of the execution strategy is different, and the execution point of the policy decision may be different.
  • the same exception may be repeatedly redundant or contradictory in the service layer and the resource layer. Or a correct and wrong decision, and each is executed according to its own strategy.
  • the present application provides an NFV policy negotiation method and system, so that each policy decision point makes a correct policy decision, and avoids contradictory or repeated policy decisions of policy decision points in different domains.
  • the first aspect provides an NFV policy negotiation method, including: receiving, by a first network element, policy request information, and generating a first policy according to a local policy of the first network element and a policy request reason parameter carried in the request information; The first network element sends a policy negotiation request message to the 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, where the first network element and the second network element
  • the network element belongs to a different NFV management domain; the second network element performs policy evaluation according to the reason parameter carried in the policy negotiation request message, and generates a second policy; and the second network element compares the first policy with the second The priority of the policy is generated and sent corresponding to the first network element.
  • each policy decision point of different management domains can make correct policy decisions by conducting policy negotiation, and avoiding contradictory or repeated policy decisions of policy decision points in different domains.
  • the receiving, by the first network element, a policy request message includes: receiving, by the first network element, an NFV management domain where the first network element is located The policy request message reported by the other network element, where the policy request information includes a policy request cause parameter.
  • the first network element as a policy decision point of other network elements in the NFV management domain, receives the policy request message reported by other network elements.
  • the policy request cause parameter includes a resource alert or a fault.
  • the second network element is The reason parameter carried in the policy negotiation request message is used to perform the policy evaluation, and the second policy is generated.
  • the method includes: if the reason parameter is a resource early warning, acquiring each of the other network element collections of the NFV management domain where the second network element is located.
  • the resource and load information of the VNF generates a second policy for the VNF that causes the resource to be alerted; or if the cause parameter is a fault, determining whether the application or the virtual machine configuration of the NFV management domain where the second network element is located occurs. Error, generating a second policy that reconfigures the application or virtual machine.
  • the second network element performs a corresponding policy evaluation according to different policy request reason parameters, and generates a corresponding policy.
  • the policy indication information includes at least one indication information: instructing the first network element to perform the first policy, instructing the first network element not to perform the first policy, and indicating the The first network element performs a third policy adjusted by the first policy.
  • the second network element compares priorities of the first policy and the second policy, and generates a corresponding policy indication
  • the information includes: if the priority of the first policy is higher than the priority of the second policy, the second network element generates policy indication information or generates information indicating that the first network element performs the first policy Instructing the first network element to perform policy indication information on the third policy after the first policy adjustment; if the priority of the second policy is higher than the priority of the first policy, the second network The meta-instruction indicates that the first network element does not execute the policy indication information of the first policy.
  • the method further includes: if the second policy has a higher priority than the first policy The second network element generates policy indication information indicating that the first network element does not perform the first policy, and the second network element performs the second policy.
  • the second aspect provides an NFV policy negotiation method, including: receiving, by the first network element, policy request information, and generating a first policy according to a local policy of the first network element and a policy request reason parameter carried in the request information;
  • the first network element sends a policy negotiation request message to the policy arbitration network element, where the policy negotiation request message includes a policy request cause parameter, a first policy, a priority of the first policy, and a policy negotiation with the first network element.
  • the policy arbitration network element sends the policy negotiation request message to the second network element;
  • the second network element performs policy evaluation according to the reason parameter carried in the policy negotiation request message, generates and sends a second policy to the policy arbitration network element, and compares the first policy and the second policy by the policy arbitration network element. Priority, generating and transmitting corresponding policy arbitration information to the first network element and/or the second network element.
  • each policy decision point of a different management domain performs policy arbitration through a policy arbitration network element, and can make a correct policy decision, thereby avoiding contradictory or repeated policy decisions of policy decision points in different domains.
  • the policy arbitration information includes at least one of: indicating that the first network element performs the first policy, or indicates the second The network element executes the second policy.
  • the first network element includes any one of the following: a service support system OSS and The network element management system EMS
  • the second network element includes any one of the following: a network function virtualization orchestrator NFNO and a virtual network function entity manager VNFM; or the first network element includes any one of the following: NFVO and VNFM, and the second network element includes Any of the following: OSS and EMS.
  • the NFV management domain includes a management and orchestration MANO domain and a 3GPP management domain.
  • the third aspect provides an NFV policy negotiation system, including: a first network element and a second network element; the first network element is configured to receive policy request information, according to a local policy of the first network element, and the request information The policy request cause parameter carried in the first policy is generated; the first network element is further configured to send a policy negotiation request message to the second network element, where the policy negotiation request message includes a policy request cause parameter, a first policy, and a first a priority of the policy, where the first network element and the second network element belong to different NFV management domains; the second network element is configured to perform policy evaluation and generate according to the reason parameter carried in the policy negotiation request message. And the second network element is further configured to compare the priorities of the first policy and the second policy, and generate and send corresponding policy indication information to the first network element.
  • the first network element is configured to receive a policy request message that is reported by another network element of the NFV management domain where the first network element is located, where The policy request information includes a policy request reason parameter.
  • the policy request cause parameter includes a resource alert or a fault.
  • the cause parameter is a resource early warning, acquiring resource and load information of each VNF collected by other network elements of the NFV management domain where the second network element is located, and generating a second policy for the VNF that causes the resource early warning;
  • the second network element is configured to: if the cause parameter is a fault, determine whether an application or a virtual machine configuration of the NFV management domain where the second network element is located is incorrect, and generate a second reconfiguration of the application or the virtual machine.
  • the policy indication information includes at least one indication information: instructing the first network element to perform the first policy, instructing the first network element not to perform the first policy, and indicating the The first network element performs a third policy adjusted by the first policy.
  • the second network element is used, if the first policy has a higher priority than the second a policy indicating information indicating that the first network element performs the first policy or generating policy indication information that is used by the first network element to perform a third policy after adjusting the first policy; Or the second network element is configured to: if the priority of the second policy is higher than the priority of the first policy, generate policy indication information that indicates that the first network element does not perform the first policy.
  • the second network element is further configured to: if the second policy has a higher priority than the foregoing a policy priority, generating policy indication information indicating that the first network element does not execute the first policy, and executing the second policy.
  • the first network element includes any one of the following The service support system OSS and the network element management system EMS
  • the second network element includes any one of the following: a network function virtualization orchestrator NFNO and a virtual network function entity manager VNFM; or the first network element includes any one of the following: NFVO and VNFM
  • the second network element includes any one of the following: OSS and EMS.
  • the NFV management domain includes managing and orchestrating MANO domains and 3GPP administrative domains.
  • the fourth aspect provides an NFV policy negotiation system, including: a first network element, a second network element, and a policy arbitration network element; the first network element is configured to receive policy request information, according to the locality of the first network element The policy and the policy request cause parameter carried in the request information generate a first policy; the first network element is further configured to send a policy negotiation request message to the policy arbitration network element, where the policy negotiation request message includes a policy request cause parameter, a first policy, a priority of the first policy, and an identifier of the second network element that negotiates 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 configured to perform policy evaluation according to the reason parameter carried in the policy negotiation request message, generate and send the first 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, and generate and send corresponding policy arbitration
  • the policy arbitration information includes at least one of: indicating that the first network element performs the first policy, or indicates the second The network element executes the second policy.
  • the first network element includes any one of the following: a service support system OSS and a network element management
  • the second network element includes any one of the following: a network function virtualization orchestrator NFNO and a virtual network function entity manager VNFM; or the first network element includes any one of the following: NFVO and VNFM, and the second network element includes any one of the following : OSS and EMS.
  • the NFV management domain includes management And orchestrate the MANO domain and the 3GPP administrative domain.
  • a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the methods described in the various aspects above.
  • FIG. 1 is a schematic diagram of a network function virtualization architecture provided by the prior art
  • 2a is a framework diagram of policy management for a management and orchestration domain provided by the prior art
  • FIG. 2b is a schematic diagram of policy management for another management and orchestration domain provided by the prior art
  • FIG. 3 is a schematic flowchart of a policy-driven automatic fault management of a 3GPP management domain provided by the prior art
  • FIG. 4 is a schematic diagram of an interaction process of an NFV policy negotiation method according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of an interaction process of an NFV policy negotiation method in an exemplary communication scenario
  • FIG. 6 is a schematic diagram of an interaction process of an NFV policy negotiation method in another communication scenario
  • FIG. 7 is a schematic diagram of an interaction process of another NFV policy negotiation method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of an interaction process of an NFV policy negotiation method in another communication scenario
  • FIG. 9 is a schematic structural diagram of an NFV policy negotiation system according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another NFV policy negotiation system according to an embodiment of the present application.
  • the embodiment of the present application can be applied to the architecture of the NFV shown in FIG. 1, and is of course not limited to the architecture of the NFV shown in FIG. 1. Can be applied to policy negotiation between any two policy decision points.
  • the 3GPP management domain includes an operational support system (OSS)/business support system (BSS), device manager (DM), and network functions.
  • OSS/BSS is the operation/service support system of the entire NFV architecture, which is responsible for managing the operation/business of the entire system.
  • OSS/BSS interacts with NFVO for virtualized applications to complete the operation and maintenance of the network.
  • the DM mainly includes EM.
  • the NF entity includes a physical network function (PNF) entity and a VNF. This application mainly relates to VNF.
  • PNF physical network function
  • the MANO management domain includes NFVO, VNFM, and VIM.
  • NFVO the main function of NFVO is to implement NS lifecycle management (such as deployment/expansion/reduction/downline) in the carrier domain, as well as NFVI resource scheduling and policy management.
  • NFVO decomposes the requirements of each VNF according to the NS descriptor (NSD), and implements VNF deployment with VNFM.
  • NSD NS descriptor
  • the main function of VNFM is to realize VNF lifecycle management, such as deployment/expansion/reduction/downline automation.
  • VNFM decomposes the requirements for virtual resources such as virtual machines, and cooperates with Orchestrator and VIM to instantiate VNF.
  • the main function of VIM is to manage and monitor the entire infrastructure layer resources (including computing, storage, network resources).
  • NFV softwareizes network elements so that network elements can run on a variety of general-purpose hardware; and through the MANO system, the network element deployment process is automated; operators can quickly and dynamically expand and shrink according to business needs.
  • Both NM and EM of the 3GPP management system can be abstracted into PDPs. If the fault/abnormal is processed in the EM analysis, the EM is a PDP; if it is a cross-domain cross-EM scenario, and the NM is required to perform the fault/abnormal analysis processing, the NM is a PDP.
  • the final policy enforcement point in the 3GPP management system may be VNF (Perform Business Layer Configuration or Operation) or VNFM (Perform VNF Lifecycle Management related operations, and ultimately the NFVI operates on resources).
  • VNF Perform Business Layer Configuration or Operation
  • VNFM Perform VNF Lifecycle Management related operations, and ultimately the NFVI operates on resources.
  • different policy decision points are easily coordinated. For example, the OSS strategy should be sent to EM. EM's own strategy will take into account the OSS strategy.
  • VNF For VNF, it will not receive more than one conflicting strategy.
  • the strategic decision point of the MANO management system may be NFVO, VNFM or VIM, and the final policy enforcement point is NFVI.
  • the three strategic decision points are divided, and the process ensures that the same event does not trigger multiple policy decision points to make policy decisions.
  • This application establishes a policy negotiation mechanism between the PDP of the 3GPP management system and the PDP of the MANO management system. Avoid conflicting or repetitive strategies between the two management systems.
  • the embodiment of the present application provides an NFV policy negotiation method and system.
  • Each policy decision point of different management domains can make a correct policy decision by performing policy negotiation, and avoids contradictory or repeated policy decisions of policy decision points in different domains.
  • FIG. 4 is a schematic diagram of an interaction process of an NFV policy negotiation method according to an embodiment of the present application, where the method may include the following steps:
  • the first network element receives the policy request information, and generates a first policy according to the local policy of the first network element and the policy request cause parameter carried in the request information.
  • the first network element sends a policy negotiation request message to the second network element, where the first network element and the second network element belong to different NFV management domains, and the policy negotiation request message includes: a policy. Request the reason parameter, the first policy, and the priority of the first policy.
  • the second network element receives the policy negotiation request message.
  • the second network element performs policy evaluation according to the reason parameter carried in the policy negotiation request message, and generates a second policy.
  • the second network element compares priorities of the first policy and the second policy, and generates corresponding policy indication information.
  • the second network element sends the policy indication information to the first network element.
  • the first network element receives the policy indication information.
  • the first network element performs the policy indication information.
  • the first network element receives the policy request information.
  • the first network element may be a network element of the 3GPP management domain, or may be a network element of the MANO domain.
  • 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 reason parameter.
  • the policy request cause parameter includes a resource alert or a failure.
  • the resource warning includes resource alarms, service load alarms, and the like.
  • a resource alarm can indicate that the VNF configuration is insufficient.
  • the service load alarm can refer to a load on a VNF that is too low or too high.
  • Policy decision points of different NFV management domains may make different policies according to the local policy and the policy request reason parameters. For example, if the first network element is a policy decision point of the 3GPP management domain, the policy may be made on the service load or application troubleshooting; if the first network element is a policy decision point of the MANO management domain, the resource or virtual machine may be configured. Make a strategy on troubleshooting. In this step, the first network element generates a first policy according to the local policy of the first network element and the policy request reason parameter carried in the request information.
  • the 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 and the second network element are in different management domains.
  • the second network element is a network element of the MANO domain (for example, NFVO, VNFM, or VIM); if the first network element is a MANO domain
  • the network element for example, NFVO, VNFM or VIM
  • the second network element is a network element (for example, EM, NM) of the 3GPP management domain.
  • the first network element and the second network element may also be network elements of different management domains of the same level. For example, if the first network element is NM, the second network element is NFVO; if the first network element is EM, the second network element is VNFM.
  • the policy negotiation request message includes: a policy request reason parameter, a first policy, and a priority of the first policy. Among them, in the entire NFV architecture, the priority of the policy can be uniformly set.
  • the second network element receives the policy negotiation request message. And proceed to 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 manners according to different reason parameters. If the cause parameter is a resource alert, obtain the resource and load information of each VNF collected by other network elements of the NFV management domain where the second network element is located, and generate a second policy for the VNF that causes the resource early warning; or The cause parameter is a fault, and it is determined whether the application of the NFV management domain where the second network element is located or the configuration of the virtual machine is incorrect, and a second policy for reconfiguring the application or the virtual machine is generated.
  • the second network element checks the dynamic values of the current FCAPS, analyzes the application layer configuration of each network element in the network service, and the service layer. The network traffic information generates a second policy. If the second network element detects that the load of the NFV is too large, the second policy of transferring the load is performed. If the load problem of the NFV is not detected, the first network element is instructed to execute the first policy. If the cause parameter is a fault, the application or the virtual machine configuration may cause a fault. If the second network element is the network element of the 3GPP management domain, the second network element detects whether the application is faulty. If yes, the application configuration is made. The second policy, if not, instructs execution of the first network element to execute the first policy
  • the process proceeds to S104.
  • the second network element compares the priorities of the first policy and the first policy, and generates corresponding policy indication information.
  • the policy indication information includes at least one indication information: instructing the first network element to perform the first policy, instructing the first network element not to perform the first policy, and instructing the first network element to perform pairing The third policy after the first policy adjustment.
  • S104 includes:
  • the second network element If the priority of the first policy is higher than the priority of the second policy, the second network element generates policy indication information or generates an indication indicating that the first network element performs the first policy Performing, by a network element, policy indication information of the third policy adjusted by the first policy;
  • the second network element If the priority of the second policy is higher than the priority of the first policy, the second network element generates policy indication information indicating that the first network element does not perform the first policy.
  • the first network element and the second network element belong to different management domains, and the first policy generated by the first network element and the second policy generated by the second network element are respectively different levels of policies.
  • the first policy is to adjust services.
  • the strategy of the load, the second strategy is the strategy of adjusting the resources of the VNF.
  • the second network element agrees that the first network element executes the first policy, or the second network element does not agree that the first network element executes the first policy, and the second network element executes the second policy.
  • the priority of the first policy is determined, 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; If the priority of the second policy is lower, the second network element generates policy indication information indicating that the first network element does not perform the first policy, and the second network element performs the second policy.
  • the priority of the first policy is higher than the priority of the second policy, but the second network element considers that the first network element cannot perform the first policy to solve the resource alarm or the fault is rectified, and the first policy needs to be adjusted. Therefore, the second network element generates policy indication information, where the policy indication information is used to instruct the first network element to perform policy indication information on the third policy after the first policy adjustment.
  • the first strategy is to reconfigure the 30% load on VNF A to VNF B, but the second network element combines the resource information of VNF A and VNF B, and considers that 30% of the load is insufficient, and VNF A may still have resources. If the alarm is generated, the second network element may instruct the first network element to transfer 40% of the load to the VNF B.
  • the process proceeds to S105, where the second network element sends the policy indication information to the first network element.
  • the policy indication information includes at least one indication information: the first network element is instructed to execute the first policy, the first network element is instructed not to execute the first policy, and the indication is The first network element performs the adjusted first strategy.
  • the first network element receives the policy indication information. Further, the first network element executes the policy indication information.
  • the policy indication information includes policy indication information that indicates that the first network element performs the first policy
  • the first network element performs the first policy.
  • the second network element has made the second policy, since the priority of the second policy is lower than the priority of the first policy, the second network element does not need to execute the second policy.
  • the policy indication information includes indicating that the first network element does not perform the first policy
  • the first network element does not perform policy indication information of the first policy.
  • the second network element indicates that the first network element does not execute the first policy, and the second network element itself performs the second policy that it makes.
  • the first network element performs the indication information of the third policy after the first policy adjustment.
  • the second network element has made the second policy, since the priority of the second policy is lower than the priority of the first policy, the second network element does not need to execute the second policy.
  • the first network policy may be adjusted, and the second network element may adjust the first policy to obtain the third policy, and the first network element is instructed to perform the third policy, because the first policy may not be able to solve the resource alarm or the fault is rectified. .
  • each policy decision point of different management domains can make a correct policy decision by performing policy negotiation, and avoiding contradictory or repeated policy decisions of policy decision points in different domains.
  • FIG. 5 is a schematic diagram of an interaction process of an NFV policy negotiation method in a communication scenario. The method may include the following steps:
  • the VIM obtains a resource alarm from the VNFI that the CPU usage exceeds the threshold.
  • the VNFM associates the resource alarm to the VNF A.
  • the expansion of VNF A is triggered.
  • the local policy also requires that the policy requires policy negotiation with the element management system (EMS).
  • the EMS includes one or more EMs.
  • the VNFM sends a policy negotiation request message to the EMS.
  • the policy negotiation request message carries the following information: the priority Pri1 of the local execution policy, the reason for the execution of the policy (the CPU usage exceeds the threshold), and the policy execution action (the VNF A is expanded to a specific specification).
  • the EMS After receiving the policy negotiation request message, the EMS triggers the policy evaluation to check the dynamic values of the current fault, configuration, accounting, performance, and security (FCAPS).
  • FCAPS current fault, configuration, accounting, performance, and security
  • the application layer configuration of each network element in the network service and the network traffic information of the service layer are analyzed. It is found that the VNF B sends a large number of incorrect packets to the VNF A, resulting in a high load of the VNF A service.
  • EMS can solve the problem by making business configuration changes to VNF B. And this strategy has a higher priority.
  • S206 The EMS sends a policy negotiation response message to the VNFM, indicating that the VNF A is not expanded.
  • the EMS sends a service configuration command to the VNF B to correct the previously configured error, so that the VNF B stops sending a large number of incorrect packets to the VNF A.
  • the traffic on the VNF A is rapidly degraded, the CPU usage is normal, and the fault is eliminated.
  • the VNFM does not negotiate with the EMS, the VNFM makes a policy for VNF A expansion, and the EMS does not control the VNF B to stop sending a large number of incorrect packets to the VNF A, even if the VNF A is expanded to a larger scale.
  • the problem that the CPU usage of VNF A exceeds the threshold is still unresolved and resources are wasted.
  • Negotiating with the EMS through the VNFM makes no wrong decisions at the business and resource layers.
  • FIG. 6 is a schematic diagram of an interaction process of an NFV policy negotiation method in another communication scenario. The method may include the following steps:
  • S301 and EMS collect the values of multiple VNFs and find that the traffic load of some VNFs is very high.
  • S302 and EMS find that the traffic load of some VNFs of the same type is very low, and the load can be adjusted by changing the service configuration.
  • the policy of adjusting the service configuration is configured to negotiate a policy with the VNFM.
  • the EMS sends a policy negotiation request message to the VNFM.
  • the policy negotiation request message carries the following information: priority Pri1 of the local policy, reason for policy execution (VNF A overload is too high), and policy enforcement action (reconfiguring 30% of the traffic load onto VNF B).
  • the VNFM After receiving the policy negotiation request message, the VNFM triggers the policy evaluation, and queries the virtual resource status of the VNF A and the VNF B, and finds that the VNF A is to be expanded by the triggering policy, and the VNF B is reduced. Since the local policy has a lower priority, it is decided to adopt the EMS policy. The local does not trigger the expansion and contraction, and waits until the effect of the policy execution on the EMS.
  • the VNFM sends a policy negotiation response message to the EMS, indicating that the policy execution of the EMS is agreed.
  • S306 The EMS sends service configuration commands to VNF A and VNF B to adjust respective service loads.
  • the VNFM does not trigger the expansion and contraction strategy for VNF A and VNF B.
  • the load of VNF A and VNF B is balanced by the configuration changes of the service layer.
  • S305 may also be a policy execution indicating that the EMS is rejected.
  • VNFM may trigger its own strategy to perform expansion and contraction operations.
  • the S305 may also be an instruction to instruct the EMS to perform the adjusted policy, such as reconfiguring the 40% traffic load of the VNF A to the VNF B.
  • the EMS makes a policy of reconfiguring 30% of the traffic load on the VNF A to the VNF B, and the VNFM makes a policy of expanding the VNF A and shrinking the VNF B. .
  • the load of VNF A is configured to VNF B, it is found that VNF B is reduced, and a resource alarm is triggered on VNF B.
  • the EMS then reconfigures the traffic load portion of VNF B to VNF A. Since EMS and VNFM have made a contradictory strategy, this will lead to a "ping-pong effect.”
  • EMS negotiates with VNFM to avoid conflicting strategies at the business and resource levels.
  • each policy decision point of different management domains can make a correct policy decision by performing policy negotiation, thereby avoiding contradictory or repeated policy decisions of policy decision points in different domains.
  • FIG. 7 is a schematic diagram of an interaction process of another NFV policy negotiation method according to an embodiment of the present application, where the method may include the following steps:
  • the first network element receives the policy request information, and generates a first policy according to the local policy of the first network element and the policy request cause parameter carried in the request information.
  • the first network element sends a policy negotiation request message to the policy arbitration network element.
  • the policy arbitration network element receives the policy negotiation request message.
  • the policy negotiation request message includes: a policy request cause parameter, a first policy, a priority of the first policy, and an identifier of the second network element that performs policy negotiation with the first network element; where the first network The 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 receives the policy negotiation request message.
  • the second network element performs policy evaluation according to the reason parameter carried in the policy negotiation request message, and generates a second policy.
  • the second network element sends a second policy to the policy arbitration network element.
  • the policy arbitration network element receives the second policy.
  • the policy arbitration network element compares priorities of the first policy and the second policy, and generates corresponding policy arbitration information.
  • 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 receive the policy arbitration information.
  • the policy negotiation party does not directly send the policy negotiation request message to another policy negotiation party, but is forwarded through the policy arbitration network element.
  • the policy arbitration network element generates corresponding policy indication information according to the priorities of the first policy and the second policy. Policy arbitration by the policy arbitration network element can reduce the workload of any policy negotiation party.
  • the policy arbitration network element can be physically deployed on existing management function nodes such as NM and EM.
  • the policy negotiation request message carries the negotiating party identifier, that is, the network element that the first network element wants to negotiate with, and carries the identifier of the negotiating party.
  • the identifier of the second network element that performs policy negotiation with the first network element should be carried.
  • the policy arbitration network element sends the policy negotiation request message to the second network element identified by the negotiating party identifier according to the received policy negotiation request message.
  • the second network element performs policy evaluation according to the reason parameter carried in the policy negotiation request message, and generates a second policy. For details, refer to the foregoing embodiments. Then, the second network element sends a 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 performs the second policy, Then, after receiving the policy arbitration information, the second network element executes the second policy.
  • FIG. 8 is a schematic diagram of an interaction process of an NFV policy negotiation method in another communication scenario. The method may include the following steps:
  • the VIM obtains a resource alarm from the NFVI that the CPU usage exceeds the threshold.
  • the VNFM associates the resource alarm to the VNF A.
  • the VNF A is to be expanded, but the local policy also requires the policy to negotiate with the EMS.
  • the VNFM sends a policy negotiation message to the policy arbitration network element.
  • the policy negotiation message carries the following information: the priority of the local execution policy, Pri1, the policy execution reason (the CPU usage exceeds the threshold), the policy execution action (VNF A is expanded to a specific specification), and the policy arbitration with whom.
  • the policy arbitration network element sends a VNFM policy to the EMS according to the information carried by the VNFM, where 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.
  • the SMS After receiving the policy negotiation request message, the SMS triggers the policy evaluation to check the dynamic values of the current FCAPS.
  • the application layer configuration of each network element in the network service and the network traffic information of the service layer are analyzed. It is found that the VNF B sends a large number of incorrect packets to the VNF A, resulting in a high load of the VNF A service.
  • EMS can solve the problem by making business configuration changes to VNF B.
  • the EMS sends a policy negotiation message to the policy arbitration network element, where the carrying information includes a priority Pri1 of the local execution policy, a policy execution reason, a policy execution action, and a policy negotiation ID.
  • the policy arbitration network element performs an EMS policy according to a priority of the EMS and the VNFM policy.
  • the policy arbitration network element sends a policy arbitration result to the EM, and agrees to the EM execution policy.
  • the policy arbitration network element sends a policy arbitration result to the VNFM, disagreeing with the VNFM execution policy.
  • the EMS sends a service configuration command to the VNF B to correct the previously configured error, so that the VNF B stops sending a large number of incorrect packets to the VNF A.
  • the traffic on the VNF A is rapidly degraded, the CPU usage is normal, and the fault is eliminated.
  • the policy negotiator does not directly send the policy negotiation request message to another policy negotiator, but is forwarded through the policy arbitration network element.
  • the policy arbitration network element generates corresponding policy indication information according to the priorities of the first policy and the second policy. Policy negotiation by the policy arbitration network element can reduce the workload of any policy negotiation party.
  • each policy decision point of different management domains sends a respective policy to a policy arbitration network element, and the policy arbitration network element uniformly performs policy arbitration, and sends the policy arbitration result to the corresponding
  • the execution of strategic decision points can avoid conflicting or repeated policy decisions for policy decision points in different domains.
  • FIG. 9 is a schematic structural diagram of an NFV policy negotiation system according to an embodiment of the present disclosure.
  • the system 1000 includes a first network element 11 and a second network element 12;
  • the first network element 11 is configured to receive the policy request information, and generate a first policy according to the local policy of the first network element and the policy request cause parameter carried in the request information; the first network element 11 is further configured to send The policy negotiation request message is sent to the 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, where the first network element and the second network element belong to different NFVs.
  • the second network element 12 is configured to perform policy evaluation according to the reason parameter carried in the policy negotiation request message, to generate a second policy, and the second network element 12 is further configured to compare the first policy and the first The priority of the second policy is generated and sent corresponding to the first network element.
  • the first network element 11 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 information includes a policy request cause parameter.
  • the policy request cause parameter includes a resource alert or a failure.
  • the second network element 12 is configured to acquire resources and loads of each VNF collected by other network elements of the NFV management domain where the second network element is located, if the cause parameter is a resource early warning.
  • the second network policy is configured to generate a second policy for the VNF that causes the resource to be alerted; or the second network element 12 is configured to determine, if the cause parameter is a fault, whether the application is the NFV management domain where the second network element is located or An error occurred in the virtual machine configuration, generating a second policy that reconfigures the application or virtual machine.
  • the policy indication information includes at least one indication information: instructing the first network element to perform the first policy, instructing the first network element not to perform the first policy, and Instructing the first network element to perform a third policy adjusted by the first policy.
  • the second network element 12 is configured to: when the priority of the first policy is higher than the priority of the second policy, generate the indication that the first network element performs the first Policy policy information of the policy or generating policy indication information indicating that the first network element performs a third policy adjusted by the first policy; or the second network element 12 is used to prioritize the second policy The level is higher than the priority of the first policy, and generates policy indication information indicating that the first network element does not perform the first policy.
  • the second network element 12 is further configured to: if the priority of the second policy is higher than the priority of the first policy, generate, that the first network element does not perform the The policy of the first policy indicates information and the second policy is executed.
  • the first network element includes any one of the following: a service support system OSS and a network element management system (EMS), and the second network element includes any one of the following: a network function virtualization orchestrator NFNO and a virtual network function.
  • the NFV management domain includes a management and orchestration MANO domain and a 3GPP administrative domain.
  • each policy decision point of different management domains can make a correct policy decision by performing policy negotiation, thereby avoiding contradictory or repeated policy decisions of policy decision points in different domains.
  • FIG. 10 is a schematic structural diagram of another NFV policy negotiation system according to an embodiment of the present disclosure.
  • the system 2000 includes: a first network element 21, a policy arbitration network element 22, and a second network element 23;
  • the first network element 21 is configured to receive the policy request information, and generate a first policy according to the local policy of the first network element and the policy request reason parameter carried in the request information; the first network element 21 is further configured to send The policy negotiation request message is sent to the policy arbitration network element, where the policy negotiation request message includes a policy request cause parameter, a first policy, a priority of the first policy, and an identifier of the second network element that performs policy negotiation with the first network element.
  • 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 element 23 is configured to perform policy evaluation according to the reason parameter carried in the policy negotiation request message, 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 first policy and The priority of the second policy is generated and sent corresponding to the first network element and/or the second network element.
  • the policy arbitration information includes at least one of: instructing the first network element to perform the first policy, or instructing the second network element to perform the second policy.
  • the first network element includes any one of the following: a service support system OSS and a network element management system (EMS), and the second network element includes any one of the following: a network function virtualization orchestrator NFNO and a virtual network function.
  • the NFV management domain includes a management and orchestration MANO domain and a 3GPP administrative domain.
  • each policy decision point of different management domains performs policy arbitration through a policy arbitration network element, which can make a correct policy decision, and avoid conflicting or repeated policy decision points of different domains. Strategic decision making.
  • the embodiment of the present application further provides a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • the embodiment of the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method described in the above aspects.
  • 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.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • 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, and may be in an electrical, mechanical or other form.
  • 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 purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application 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 embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it 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.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)). )Wait.
  • the foregoing storage medium includes: a read-only memory (ROM) or a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé et un système de négociation de politique de NFV. Le procédé comprend les étapes suivantes : un premier élément de réseau reçoit des informations de demande de politique, et génère une première politique d'après une politique locale du premier élément de réseau et d'un paramètre de raison de demande de politique transporté dans les informations de demande ; le premier élément de réseau envoie un message de demande de négociation de politique à un second élément de réseau, le message de demande de négociation de politique contenant le paramètre de raison de demande de politique, la première politique, et la priorité de la première politique, et le premier élément de réseau et le second élément de réseau appartenant à différents domaines de gestion de NFV ; d'après le paramètre de raison transporté dans le message de demande de négociation de politique, le second élément de réseau exécute une évaluation de politique, et génère une seconde politique ; et le second élément de réseau compare les priorités de la première politique et de la seconde politique, génère des informations d'indication de politique correspondantes, et les envoie au premier élément de réseau. Des points de prise de décision de politique dans différents domaines de gestion peuvent prendre des décisions de politique correctes via l'exécution d'une négociation de politique, ce qui empêche les points de prise de décision de politique dans différents domaines de prendre des décisions de politique contradictoires ou répétées.
PCT/CN2019/084343 2018-04-28 2019-04-25 Procédé et système de négociation de politique de nfv Ceased WO2019206234A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810399834.2A CN110417568B (zh) 2018-04-28 2018-04-28 Nfv策略协商方法及系统
CN201810399834.2 2018-04-28

Publications (1)

Publication Number Publication Date
WO2019206234A1 true WO2019206234A1 (fr) 2019-10-31

Family

ID=68294797

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/084343 Ceased WO2019206234A1 (fr) 2018-04-28 2019-04-25 Procédé et système de négociation de politique de nfv

Country Status (2)

Country Link
CN (1) CN110417568B (fr)
WO (1) WO2019206234A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025081494A1 (fr) * 2023-10-20 2025-04-24 华为技术有限公司 Procédé et appareil de communication à prise de décision de confiance

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105577499A (zh) * 2014-10-10 2016-05-11 华为技术有限公司 决策协调方法、执行装置和决策协调器
CN106209409A (zh) * 2015-05-07 2016-12-07 中国移动通信集团公司 一种基于虚拟网络功能vnf的调度消息处理方法及装置
WO2016197301A1 (fr) * 2015-06-08 2016-12-15 华为技术有限公司 Procédé et appareil de coordination de politiques dans un système nfv
US20170141944A1 (en) * 2015-11-13 2017-05-18 Electronics And Telecommunications Research Institute Verifier for network function virtualization resource allocation

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101945446B (zh) * 2009-07-10 2013-12-04 中兴通讯股份有限公司 一种用户设备处理策略冲突的方法及系统
CN104104615B (zh) * 2014-07-21 2017-07-07 华为技术有限公司 策略冲突解决方法以及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105577499A (zh) * 2014-10-10 2016-05-11 华为技术有限公司 决策协调方法、执行装置和决策协调器
CN106209409A (zh) * 2015-05-07 2016-12-07 中国移动通信集团公司 一种基于虚拟网络功能vnf的调度消息处理方法及装置
WO2016197301A1 (fr) * 2015-06-08 2016-12-15 华为技术有限公司 Procédé et appareil de coordination de politiques dans un système nfv
US20170141944A1 (en) * 2015-11-13 2017-05-18 Electronics And Telecommunications Research Institute Verifier for network function virtualization resource allocation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE: "pCR TR 32.871 Adding the Concepts of Policy Conflict Detection and Resolution", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #117, 2 February 2018 (2018-02-02), pages 5 - 181514, XP051409400 *

Also Published As

Publication number Publication date
CN110417568A (zh) 2019-11-05
CN110417568B (zh) 2021-10-26

Similar Documents

Publication Publication Date Title
EP3800926B1 (fr) Procédé et dispositif d'alarme
EP3119034B1 (fr) Procédé, dispositif et système de traitement de défauts sur la base d'une virtualisation d'une fonction de réseau
US10601656B2 (en) Network element upgrade method and device
CN101040486B (zh) 动态分布式环境中的自动拓扑形成方法及系统
US9584369B2 (en) Methods of representing software defined networking-based multiple layer network topology views
EP3468151B1 (fr) Procédé et appareil de traitement de ressources d'accélération
TWI722145B (zh) 網路功能虛擬化
JP6466003B2 (ja) Ｖｎｆフェイルオーバの方法及び装置
JP6724095B2 (ja) 分散システムにおける集中ネットワーク構成
US20190056975A1 (en) Virtualized network function manager determining method and network functions virtualization orchestrator
CN111095900A (zh) 用于分布式云环境中sla管理的方法和装置
EP4177742A1 (fr) Procédé et appareil de gestion multi-occupants
KR20170129253A (ko) 네트워크 기능 가상화 기반 장애 처리 방법 및 장치
CN106161076A (zh) 虚拟网络功能扩展方法和装置
WO2019174000A1 (fr) Procédé et appareil de gestion de service
CN109960634A (zh) 一种应用程序监控方法、装置及系统
CN117201381A (zh) 算力路由方法和网关
WO2018210075A1 (fr) Procédé et appareil de gestion de réseau et dispositif de réseau
WO2016197301A1 (fr) Procédé et appareil de coordination de politiques dans un système nfv
EP3251320A1 (fr) Contrôleur de mise en réseau définie par logiciel
WO2019206234A1 (fr) Procédé et système de négociation de politique de nfv
CN108737144B (zh) 资源管理的方法和设备
EP3662695B1 (fr) Élément sensible au réseau et son procédé d'utilisation
WO2025062451A1 (fr) Procédé et système d'évaluation d'une hystérésis pour un événement d'erreur
WO2025062450A1 (fr) Procédé et système de mise en œuvre d'actions correctives pendant un événement d'erreur de seuil de ressource

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19792995

Country of ref document: EP

Kind code of ref document: A1