EP3262795B1 - Système et procédé de gestion des ressources - Google Patents

Système et procédé de gestion des ressources Download PDF

Info

Publication number
EP3262795B1
EP3262795B1 EP16789305.6A EP16789305A EP3262795B1 EP 3262795 B1 EP3262795 B1 EP 3262795B1 EP 16789305 A EP16789305 A EP 16789305A EP 3262795 B1 EP3262795 B1 EP 3262795B1
Authority
EP
European Patent Office
Prior art keywords
entity
vnfm
vnf
nfvo
granting
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.)
Active
Application number
EP16789305.6A
Other languages
German (de)
English (en)
Other versions
EP3262795A1 (fr
EP3262795A4 (fr
Inventor
Zhixian Xiang
Jianning Liu
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 EP3262795A1 publication Critical patent/EP3262795A1/fr
Publication of EP3262795A4 publication Critical patent/EP3262795A4/fr
Application granted granted Critical
Publication of EP3262795B1 publication Critical patent/EP3262795B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • 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
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities

Definitions

  • the present disclosure relates to telecommunications, and, in particular embodiments, to methods and system for resource management in a network function virtualization (NFV) system.
  • NFV network function virtualization
  • NFV Network Function Virtualization
  • NFs network functions
  • NFs network functions
  • NFV environment NFs are separated from the hardware they run on using virtual hardware abstraction to virtualize entire classes of NFs into building blocks that may be connected, or chained, together to create communication services.
  • ETSI Network Functions Virtualisation (NFV); Management and Orchestration
  • pages 1-184 relates to network functions virtualisation, management and orchestration.
  • WO 2016/048430 relates to network functions virtualisation.
  • a method for resource management includes receiving, by a virtualized network function (VNF) manager (VNFM) entity, from a network functions virtualization orchestrator (NFVO) entity a granting indication including a granting granularity in which the NFVO entity permits the VNFM entity to perform multiple VNF management operations for one or more VNFs, determining, by the VNFM entity, that a first VNF management operation is in a scope of permission based on the granting indication upon the first VNF management operation being triggered, and sending, by the VNFM entity, a first resource allocation request for the first VNF management operation to a virtual infrastructure manager (VIM) entity.
  • VNF virtualized network function
  • NFVO network functions virtualization orchestrator
  • a system in another embodiment, includes a memory storage that stores instructions and one or more processors in communication with the memory that execute the instructions.
  • the instructions are executed to receive by a virtualized network function manager, VNFM, from a network functions virtualization orchestrator (NFVO) entity a granting indication including a granting granularity in which the NFVO entity permits the virtualized network function (VNF) manager (VNFM) entity to perform multiple VNF management operations for one or more VNFs, determine by the VNFM entity that a first VNF management operation is in a scope of permission based on the granting indication upon the first VNF management operation being triggered, and send by the VNFM entity a first resource allocation request for the first VNF management operation to a virtual infrastructure manager (VIM) entity.
  • VNFM virtualized network function manager
  • FIG. 1 is a schematic diagram of an embodiment of an NFV system 100. Some of this system is described in Network Functions Virtualization (NFV): Management and Orchestration (NFV-MANO), ETSI NFV-MAN 001 v1.1.1 (2014-12), http://www.etsi.org/deliver/etsi_gs/NFV-MAN/001_099/001/01.01.01_60/gs_NFV-MAN001v010101p.pdf .
  • NFV Network Functions Virtualization
  • NFV-MANO Management and Orchestration
  • ETSI NFV-MAN 001 v1.1.1 2014-12
  • the NFV system 100 may comprise an NFV Management and Orchestration (NFV-MANO) entity 128, an NFV Infrastructure (NFVI) entity 126, a virtual function entity 140, and one or more Operations Support Systems (OSSs) and Business Support Systems (BSSs) (OSS/BSS) 124.
  • the virtual function entity 140 may comprise a plurality of virtual network function (VNF) elements 160, 162, and 164, a plurality of element management system (EMS) elements 170, 172, and 174 that can be configured to perform the typical management functionality for the plurality of VNF elements 160, 162, and 164.
  • VNF virtual network function
  • EMS element management system
  • the VNF elements are used to perform a virtualisation of a network function in a non-virtualised network.
  • the network functions in the non-virtualised network may be 3GPP Evolved Packet Core (EPC) network elements, e.g. Mobility Management Entity (MME), Serving Gateway(SGW), Packet Data Network Gateway (PGW); elements in a home network, e.g. Residential Gateway (RGW); and conventional network functions, e.g. Dynamic Host Configuration Protocol (DHCP) servers, firewalls, etc.
  • EPC Evolved Packet Core
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • RGW Residential Gateway
  • conventional network functions e.g. Dynamic Host Configuration Protocol (DHCP) servers, firewalls, etc.
  • VNF 160 can be composed of one or more internal components, called virtualised network function components (VNFCs).
  • VNFCs virtualised network function components
  • Each VNFC provides a defined sub-set of that VNF's functionality, with the main characteristic that a single instance of this component maps 1:1 against a single virtualisation container.
  • one VNF can be deployed over multiple Virtual Machines (VMs), where each VM hosts a VNFC of the VNF.
  • VMs Virtual Machines
  • a VM may be virtualized computation environment that behaves like a physical computer or server, which has all its ingredients (processor, memory/storage, interfaces/ports) of a physical computer/server and is generated by a hypervisor, which partitions the underlying physical resources and allocates them to VMs.
  • a hypervisor may be piece of software which partitions the underlying physical resources and creates virtual machines, and isolates the virtual machines from each other.
  • the NFV-MANO entity 128 may be responsible for the operation, management, and coordination of VNF elements 160, 162, and 164 and the respective NFVI entity 126.
  • the NFV-MANO entity 128 may comprise an NFV Orchestrator (NFVO) entity 102, one or more VNF manager (VNFM) entities 104, and one or more Virtualized Infrastructure Manager (VIM) entities 106.
  • NFVO entity 102 can manage the network service (NS) lifecycle and coordinates the management of NS lifecycle, VNF lifecycle (supported by the VNFM entity 104) and NFVI resources (supported by the VIM entity 106) to ensure an optimized allocation of the necessary resources and connectivity.
  • NS network service
  • the VNFM entity 104 may communicate with VNF elements 160, 162, and 164 and be responsible for VNF lifecycle management (e.g. instantiation, update, query, scaling, and termination). For example, in one embodiment a VNFM entity 104 may be deployed for each VNF elements 160, 162, and 164. In other embodiments, a VNFM entity 104 may serve multiple VNF elements 160, 162, and 164.
  • the VIM entity 106 can be responsible for controlling and managing the NFVI compute, storage and network resources. In other words, the VIM entity 106 may be configured to control and manage the interaction of a VNF with the compute, storage and network resources in NFVI entity 126.
  • the VIM entity 106 may perform resource management functions, such as management of infrastructure resource and allocation (e.g. increase resources to VMs, improve energy efficiency, and resource reclamation).
  • the VIM entity 106 and the VNFM entity 104 may communicate with each other for resource allocation requests and to exchange virtualized hardware resource configuration and state information.
  • the NFVI entity 126 represents various hardware and software components which build up the environment in which VNFs are deployed, managed and executed.
  • the hardware components in the NFVI entity 126 may include computing hardware 112, storage hardware 114, and network hardware 116 that provide processing, storage and connectivity to VNF entities 160, 162, and 164 through a virtualization layer 130.
  • the computing hardware 112 may be any device configured to, designed to, or otherwise enabled to provide processing and computing resources.
  • the storage hardware 114 may be any kind of device which is used to store information for later retrieval. Examples of storage devices include flash memory, magnetic rotation disks, optical disks, or any other mechanism capable of storing information for later retrieval.
  • Storage hardware 114 may be differentiated between shared network attached storage (NAS) and local storage that is connected directly to the NFVI using an internal bus or other attachment mechanism.
  • the resources from the computing hardware 112 and storage hardware 114 may be pooled together.
  • the network hardware 116 may be switches that is configured to perform switching functions, e.g. routers, and wired or wireless links.
  • the network hardware 116 may span across a plurality of network domains.
  • the virtualization layer 130 within the NFVI entity 126 may abstract the hardware resources, i.e., computing hardware 112, storage hardware 114, and network hardware 116 and decouple one or more of the VNF elements 160, 162, and 164 from the underlying hardware.
  • the virtualization layer 130 may be responsible for abstracting and logically partitioning hardware resources, enabling the software that implements the VNF to use the underlying virtualized infrastructure, and providing virtualized resources to the VNF entity.
  • the virtualized resources controlled by the Virtualization Layer 130 may include a virtual computing 110, a virtual storage 118, and a virtual network 120.
  • FIG. 2 illustrates a flow diagram of an embodiment of a method 200 for resource management.
  • the embodiment method 200 may be implemented in the context of the NFV system as illustrated in FIG. 1 .
  • a network node for example, a VNFM entity receives a granting indication from a NFVO entity.
  • the granting permission may be a message from a NFVO entity used to define permissions for the VNFM entity thereby defining, in some embodiments, functionality for the VNFM entity.
  • the granting indication may further indicate a constraint or condition allowed for the one or multiple VNFs. It is understood that the multiple VNF management operations permitted by the NFVO entity may be multiple operations which are of the same type or different types. It is understood that in some implementations the granting indication can also be modified as a non-granting indication indicating that each VNF management operation to be performed needs to receive explicit permission from the NFVO entity.
  • VNF management operations is intended to include, but not be limited to, VNF-related management operations.
  • the VNF management operations may comprise VNF lifecycle management (LCM) operations, i.e., all operations needed to request and manage associations of NFVI Resources to a VNF, and maintain such associations in conformance with the VNF Descriptor and authorized run-time changes, throughout the lifecycle of the VNF.
  • the VNF lifecycle management (LCM) operations may comprise different types of operations (e.g., instantiating, scaling, updating, upgrading or terminating operations).
  • the granting indication may include a granting granularity in which the NFVO entity permits the VNFM entity to perform multiple VNF management operations for one or more VNFs.
  • the types of the granting granularity described below fall into three types which may be used alone or in combination with one another.
  • the first type of the granting granularity is an operation granularity.
  • the operation granularity indicates which type of VNF management operation the VNFM entity is permitted to conduct with the VIM entity without asking explicit permission from the NFVO entity each time the type of VNF management operation is to be performed.
  • the second type of the granting granularity is a VNF granularity.
  • the VNF granularity indicates that the VNFM entity is permitted to conduct all VNF management operations of a specific VNF or group of VNFs with the VIM entity without asking explicit permission from the NFVO entity each time one of the operations is to be performed.
  • the third type of the granting granularity is a VNFM granularity.
  • the VNFM granularity indicates that the VNFM entity is permitted to conduct all VNF management operations of VNFs that are managed by this VNFM entity without asking explicit permission from the NFVO entity each time one of the operations is to be performed.
  • the granting granularity may indicate the one or more VNFs permitted to the VNFM entity and the multiple VNF management operations granted for each of the permitted one or more VNFs.
  • the granting indication may further include a constraint or condition.
  • the constraint or condition in which the NFVO entity allows the VNFM entity to conduct VNF management operation may be allowed for one or more VNFs.
  • the VNFM entity needs to get permission from the NFVO entity to conduct each VNF management operation with the VIM entity.
  • the constraint for example, may be a capacity related constraint, performance related constraint, or operation status related constraint.
  • the VNFM entity may further send a request for the granting indication to the NFVO entity. Therefore, the receipt of a granting indication from a NFVO 202 may be in response to a request which is not explicitly illustrated.
  • the VNFM entity checks whether a VNF management operation is in a scope of permission based on the granting indication when the VNF management operation is triggered. If no, in step 206, the VNFM entity asks for a permission of the VNF management operation from the NFVO entity. Then in step 208, the VNFM entity initiates a resource allocation request for the VNF management operation to a VIM entity. If yes, then the method process skips to step 208 and the VNFM entity then initiates a resource allocation request to a VIM entity for the VNF management operation without asking for the permission. For the initiation of the resource allocation request, in some implementations, the VNFM entity may directly send the resource allocation request to the VIM entity.
  • the resource allocation request is received by the VIM entity from the VNFM entity without going through the NFVO entity.
  • the VNFM entity may send the resource allocation request to the NFVO entity and then the NFVO entity sends the resource allocation request to the VIM entity.
  • steps 204-208 may repeat for each of subsequent VNF management operation when triggered. For example, for each subsequent VNF management operation which is triggered, the VNFM entity may check whether it is in a scope of permission based on the granting indication and proceed accordingly. It is explicitly understood that another system, computer, or device may request permission to trigger the management operation in this, and other embodiments disclosed herein.
  • indicate is used in the specification or claims, it is intended to mean not only “explicitly indicate” but also “implicitly indicate”. In this way, the indication may be positive (explicit), neutral (passive), or any other indication that access is not precluded. While this example shows a permissive system, whereby access is granted if not explicitly denied, it is understood that the systems and methods disclosed herein could be implemented using a non-permissive system where explicit permissions were required.
  • the VNFM entity does not have to send a request for permission to the NFVO entity for each VNF management operation to be performed, it can reduce a high traffic exchange between the VNFM entity and the NFVO entity during VNF management operations.
  • the efficiency of interaction between the NFVO entity and the VNFM entity is improved.
  • the risk of NFVO entity as a single point of failure is reduced and the VNFM's overall response time on VNF management operations is also reduced.
  • a more flexibility and intelligence system for resource management is provided.
  • FIG. 3 illustrates a flow diagram of another embodiment of a method 300 for resource management.
  • the embodiment method 300 may be implemented in the context of the NFV system as illustrated in FIG. 1 .
  • a VNFM entity sends a VNF LCM operation grant request to a NFVO entity, to request the NFVO entity to permit the VNFM entity to perform multiple operations (for example, scaling out, scaling up operations) without asking explicit permission from the NFVO entity each time one of the multiple operations is to be performed.
  • the VNF LCM operation grant request may include a VNFM capability indication.
  • the VNFM capability indication indicates that the VNFM entity supports the capability to conduct the VNF LCM operation without obtaining permission from the NFVO entity for each VNF LCM operation.
  • the NFVO entity sends a VNF LCM operation grant response to the VNFM entity.
  • the grant response carries a granting indication which includes an operation granularity and a capacity related constraint.
  • the operation granularity indicates the VNFM entity can conduct scaling out operations without asking explicit permission from the NFVO entity for each scaling out operation.
  • the operation granularity also indicates the VNFM entity cannot conduct scaling up operations without asking explicit permission from the NFVO entity for each scaling up operation.
  • the capacity related constraint can indicate a maximum permitted capacity for a VNF (e.g. 100 VMs), based on any number of factors including hardware limitations.
  • the interaction about the indication and the capability may be implemented in any desired procedure or mechanism. For example, such interaction may be implemented during initial connection establishment between the VNFM entity and NFVO entity.
  • the scaling ability may include scaling out ability to scale by add resource instances. In other cases, the scaling ability may include scaling up ability to scale by changing allocated resource, e.g. increase memory, CPU capacity/power or storage size.
  • the VNFM entity determines that the scaling out is in the scope of the permission based on the granting indication.
  • the VNFM entity sends a resource allocation request for adding 10 VMs on the VNF to the VIM entity. While 10 VMs are mentioned in this embodiment, it is expressly contemplated that any suitable number of VMs may be implemented, and the selection of 10 VMs is purely for the purpose of illustration.
  • the VIM entity sends a resource allocation response to the VNFM entity.
  • the VNFM entity determines that the scaling up is outside the scope of the permission based on the granting indication.
  • the VNFM entity sends a scaling up granting request to ask explicit permission for this scaling up operation from the NFVO entity.
  • the NFVO entity sends a scaling up granting response to grant this scaling up operation.
  • the VNFM entity sends a resource allocation request for increasing CPU power for the VNF.
  • FIG. 4 illustrates a flow diagram of another embodiment of a method 400 for resource management.
  • the embodiment method 400 may be implemented in the context of the NFV system 100 as illustrated in FIG. 1 .
  • a VNFM entity starts a VNF LCM operation, for example, a scaling out operation.
  • the VNFM entity sends a VNF LCM operation grant request to a NFVO entity, to request the NFVO entity to permit the VNFM entity to perform multiple scaling out operations without asking explicit permission from the NFVO entity each time one of the multiple operations is to be performed.
  • the VNF LCM operation grant request may include a VNFM capability indication.
  • the VNFM capability indication indicates that the VNFM entity supports the capability to conduct the VNF LCM operation without obtaining permission from the NFVO entity for each VNF LCM operation.
  • the NFVO entity sends a VNF LCM operation grant response to the VNFM entity.
  • the grant response carries a granting indication which includes an operation granularity and a capacity related constraint.
  • the operation granularity indicates the VNFM entity is permitted to conduct scaling out operations without asking explicit permission from the NFVO entity for each scaling out operation.
  • the capacity related constraint indicates a maximum permitted capacity (e.g. 100 VMs) for a VNF.
  • the VNFM entity determines that the scaling out operation triggered is in the scope of the permission based on the granting indication, and then sends a resource allocation request for adding 10 VMs on the VNF to the VIM entity.
  • the VIM entity sends a resource allocation response to the VNFM entity.
  • the VNFM entity determines that the another scaling out operation is in the scope of the permission based on the granting indication, and then perform step 414.
  • the VNFM entity sends a resource allocation request for adding 10 VMs on the VNF to the VIM entity.
  • FIG. 5 illustrates a flow diagram of another embodiment of a method 500 for resource management.
  • the embodiment method 500 may be implemented in the context of the NFV system 100 as illustrated in FIG. 1 .
  • a NFVO entity sends to a VNFM entity a grant message.
  • the grant message carries a granting indication including a VNF granularity.
  • the VNF granularity indicates that the NFVO entity permits the VNFM entity to conduct all VNF management operations of VNF1 without asking explicit permission from the NFVO entity each time one of the operations is to be performed.
  • the VNF granularity may indicate the identifier of the granted VNF1.
  • the VNFM entity responds a grant ACK message.
  • the VNFM entity determines that the VNF1 operation is in the scope of the permission based on the granting indication, and then performs step 508. It is explicitly understood that another system, computer, or device may request permission to trigger the management operation in this, and other embodiments disclosed herein.
  • the VNFM entity sends a VNF1 resource allocation request to a VIM entity.
  • the VIM entity responds a VNF1 resource allocation response.
  • the VNFM entity receives from the VIM entity a resource change notify message, and then send the resource change notify message to the NFVO entity.
  • the resource change notify message may include information about consumed capacity during the VNF1 operation.
  • the NFVO entity responds a resource change notify ACK to the VIM entity through the VNFM entity.
  • step 516 when a VNF2 management operation is triggered the VNFM entity determines that the VNF2 operation is outside the scope of the permission based on the granting indication, and then performs step 518.
  • the VNFM entity sends a grant request to the NFVO entity, to request explicit permission for the VNF2 operation from the NFVO entity.
  • FIG. 6 illustrates a flow diagram of another embodiment of a method 600 for resource management.
  • the embodiment method 600 may be implemented in the context of the NFV system 100 as illustrated in FIG. 1 .
  • a NFVO entity sends to a VNFM entity a grant message.
  • the grant message carries a granting indication including a VNFM granularity.
  • the VNFM granularity indicates that the NFVO entity permits the VNFM entity to conduct all VNF management operations of VNFs (e.g. VNF1, VNF2 and VNF3) that are managed by the VNFM entity without asking explicit permission from the NFVO entity each time one of the operations is to be performed.
  • the VNFM entity responds a grant ACK message.
  • the VNFM entity determines that the VNF1 operation is in the scope of the permission based on the granting indication, and then performs step 608.
  • the VNFM entity sends a VNF1 resource allocation request to a VIM entity.
  • the VIM entity responds a VNF1 resource allocation response.
  • the VNFM entity receives from the VIM entity a resource change notify message, and then send the resource change notify message to the NFVO entity.
  • the resource change notify message may include information about consumed capacity during the VNF1 operation.
  • the NFVO entity responds a resource change notify ACK to the VIM entity through the VNFM entity.
  • the VNFM entity determines that the VNF2 operation is also in the scope of the permission based on the granting indication, and then performs step 618.
  • the VNFM entity sends a VNF2 resource allocation request to a VIM entity.
  • the VIM entity responds a VNF2 resource allocation response.
  • the VNFM entity receives from the VIM entity a resource change notify message, and then send the resource change notify message to the NFVO entity.
  • the resource change notify message may include information about consumed capacity during the VNF2 operation.
  • the NFVO entity responds a resource change notify ACK to the VIM entity through the VNFM entity.
  • FIG. 7 illustrates a flow diagram of another embodiment of a method 700 for resource management.
  • the embodiment method 700 may be implemented in the context of the NFV system 100 as illustrated in FIG. 1 .
  • a VNFM entity starts a VNF LCM operation, for example, a scaling out operation.
  • the VNFM entity sends a VNF LCM operation grant request to a NFVO entity, to request the NFVO entity to permit the VNFM entity to perform multiple scaling out operations without asking explicit permission from the NFVO entity each time one of the multiple operations is to be performed.
  • the VNF LCM operation grant request may further include a VNFM capability indication.
  • the VNFM capability indication indicates that the VNFM entity supports the capability to conduct the VNF LCM operation without obtaining permission from the NFVO entity for each VNF LCM operation.
  • the NFVO entity sends a VNF LCM operation grant response to the VNFM entity.
  • the grant response carries a granting indication which includes an operation granularity and a capacity related constraint.
  • the operation granularity indicates the VNFM entity is permitted to conduct scaling out operations without asking explicit permission from the NFVO entity for each scaling out operation.
  • the capacity related constraint indicates a maximum permitted capacity (e.g. 100 VMs) for a VNF.
  • the VNFM entity determines that the triggered scaling out operation is in the scope of the permission based on the granting indication, and then sends a resource allocation request for adding 10 VMs on the VNF to the VIM entity. While 10 VMs are mentioned in this embodiment, it is expressly contemplated that any suitable number of VMs may be implemented, and the selection of 10 VMs is purely for the purpose of illustration.
  • the VIM entity sends a resource allocation response to the VNFM entity.
  • the VNFM entity determines that the another scaling out operation is outside the scope of the permission based on the granting indication because the maximum permitted capacity for the VNF is reached.
  • the VNFM entity sends to the NFVO entity a scaling out granting request for adding 90 VMs, to ask explicit permission for the scaling out operation (adding 90 VMs) from the NFVO entity.
  • the NFVO entity sends a scaling out granting response to grant this scaling out operation (adding 90 VMs).
  • the VNFM entity sends to the VIM entity a resource allocation request for adding 90 VMs.
  • FIG. 8 illustrates a flow diagram of another embodiment of a method 800 for resource management.
  • the embodiment method 800 may be implemented in the context of the NFV system as illustrated in FIG. 1 .
  • a VNFM entity sends a VNFM capability indication to a NFVO entity.
  • the VNFM capability indication indicates that the VNFM entity supports a capability to manage the virtualised resources needed for the lifecycle management of the VNF.
  • the VNFM entity is capable to perform VNF-related resource management in direct mode, i.e., is capable to directly interact with a VIM entity for virtualised resource management.
  • the NFVO entity sends a NFVO capability indication to the VNFM entity.
  • the NFVO capability indication may indicate whether the NFVO entity supports a capability to manage the virtualised resources needed for the lifecycle management of the VNF.
  • the NFVO capability indication may further indicate that the NFVO entity grants the VNFM entity to perform VNF-related resource management in direct mode.
  • the VNFM entity sends to the NFVO entity a VNF LCM operation granting request, to ask permission for one or more VNF LCM operations from the NFVO entity.
  • the NFVO entity responds a VNF LCM operation granting response to permit the VNFM entity to perform the one or more VNF LCM operations.
  • the VNFM entity may support the capability to request to the VIM entity the management of virtualised resources needed for VNFs instantiation, scaling and termination.
  • the VNFM entity directly sends a resource allocation request to the VIM entity.
  • the resource allocation request is received by the VIM entity from the VNFM entity without going through the NFVO entity. Thus the interaction about VNF-related resource management between the VNFM entity and the VIM entity needs not go through the NFVO entity.
  • FIG. 9 illustrates a flow diagram of yet another embodiment of a method 900 for resource management.
  • the embodiment method 900 may be implemented in the context of the NFV system as illustrated in FIG. 1 .
  • a VNFM entity sends a VNFM capability indication to a NFVO entity.
  • the VNFM capability indication indicates that the VNFM entity does not supports a capability to manage the virtualised resources needed for the lifecycle management of the VNF.
  • the VNFM entity is capable to perform VNF-related resource management in indirect mode, i.e., is not capable to directly interact with a VIM entity for virtualised resource management.
  • the NFVO entity sends a NFVO capability indication to the VNFM entity.
  • the NFVO capability indication may indicate whether the NFVO entity supports a capability to manage the virtualised resources needed for the lifecycle management of the VNF.
  • the NFVO capability indication indicates that the NFVO entity supports a capability to manage the virtualised resources needed for the lifecycle management of the VNF.
  • the NFVO capability indication may be used to further indicate that the NFVO entity grants the VNFM entity to perform VNF-related resource management in indirect mode..
  • the VNFM entity sends to the NFVO entity a VNF LCM operation granting request, to ask permission for one or more VNF LCM operations from the NFVO entity.
  • the NFVO entity responds a VNF LCM operation granting response to permit the VNFM entity to perform the one or more VNF LCM operations.
  • the VNFM entity may support the capability to request to NFVO entity the management of virtualised resources needed for VNFs instantiation, scaling and termination.
  • the NFVO entity may support the capability to invoke resource management operations toward the VIM entity as requested by the VNFM entity.
  • the NFVO entity may also support the capability to request to the VIM entity the management of virtualised resources needed for VNFs instantiation, scaling and termination.
  • the VNFM entity sends a resource allocation request to the NFVO entity.
  • the NFVO entity sends the resource allocation request to the VIM entity.
  • the VIM entity sends a resource allocation response to the NFVO entity.
  • the NFVO entity sends the resource allocation response to the VNFM entity.
  • the interaction about VNF-related resource management between the VNFM entity and the VIM entity has to go through the NFVO entity.
  • a system for resource management comprising means that receives from a network functions virtualization orchestrator (NFVO) entity a granting indication including a granting granularity in which the NFVO entity permits the VNFM entity to perform multiple VNF management operations for one or more VNFs is disclosed.
  • This embodiment also includes means that determines that a first VNF management operation is in a scope of permission based on the granting indication upon the first VNF management operation being triggered and means that sends a first resource allocation request for the first VNF management operation to a virtual infrastructure manager (VIM) entity.
  • VIP virtual infrastructure manager
  • FIG. 10 is a block diagram of a processing system 1000 that may be used for implementing the devices and methods disclosed herein.
  • System 1000 may be used in any hardware with functionality that is discussed in FIG. 1 or may be located in support functions (not shown). Specific devices may utilize all of the components shown, or only a subset of the components and levels of integration may vary from device to device. Furthermore, a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc.
  • the processing system may comprise a processing unit equipped with one or more input/output devices 1002, such as a speaker, microphone, mouse, touchscreen, keypad, keyboard, printer, and the like.
  • the processing unit may include a central processing unit (CPU) 1004, memory 1006, a mass storage device 1008, a video adapter 1010, and an I/O interface 1012 connected to a bus 1014.
  • CPU central processing unit
  • the bus 1014 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, video bus, or the like.
  • the CPU 1004 may comprise any type of electronic data processor.
  • the memory 1006 may comprise any type of non-transitory system memory such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), a combination thereof, or the like.
  • the memory 1006 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.
  • the mass storage device 1008 may comprise any type of non-transitory storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus.
  • the mass storage device 1008 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, an optical disk drive, or the like.
  • the video adapter 1010 and the I/O interface 1012 provide interfaces to couple external input and output devices to the processing unit.
  • input and output devices include a display 1018 coupled to the video adapter 1010 and the mouse/keyboard/printer coupled to the I/O interface 1012.
  • Other devices may be coupled to the processing system 1000, and additional or fewer interface devices may be utilized.
  • a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for a printer.
  • USB Universal Serial Bus
  • the processing system 1000 also includes one or more network interfaces 1016, which may comprise wired links, such as an Ethernet cable or the like, and/or wireless links to access nodes or different networks, illustrated in Figure 10 as network 1020.
  • the network interface 1016 allows the processing system 1000 to communicate with remote units via the networks.
  • the network interface 1016 may provide wireless communication via one or more transmitters/transmit antennas and one or more receivers/receive antennas.
  • the processing system 1000 is coupled to a local-area network or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, remote storage facilities, or the like.

Landscapes

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

Claims (15)

  1. Procédé de gestion de ressources dans un système de virtualisation de fonctions de réseau (NFV), consistant à :
    recevoir (602), par une entité gestionnaire de fonctions de réseau virtualisées (VNFM), en provenance d'une entité orchestratrice de virtualisation de fonctions de réseau (NFVO), une indication d'octroi incluant une granularité d'octroi dans laquelle l'entité NFVO permet à l'entité VNFM de réaliser de multiples opérations de gestion de VNF pour une ou plusieurs VNF ;
    déterminer (606), par l'entité VNFM, qu'une première opération de gestion de VNF est dans un champ d'application d'une permission, sur la base de l'indication d'octroi au déclenchement de la première opération de gestion de VNF ; et
    envoyer (608), par l'entité VNFM, une première demande d'affectation de ressources pour la première opération de gestion de VNF à une entité gestionnaire d'infrastructure virtuelle (VIM).
  2. Procédé selon la revendication 1, dans lequel la granularité d'octroi indique la ou les VNF permises à l'entité VNFM et les multiples opérations de gestion de VNF octroyées pour chacune de la ou des VNF permises.
  3. Procédé selon la revendication 2, dans lequel la ou les VNF comprennent une unique VNF, un groupe de VNF ou toutes les VNF appartenant à l'entité VNFM.
  4. Procédé selon l'une quelconque des revendications 1 à 3, dans lequel l'indication d'octroi comprend en outre une contrainte autorisée par l'entité NFVO pour la ou les VNF
  5. Procédé selon la revendication 4, dans lequel la contrainte comprend une capacité permise.
  6. Procédé selon la revendication 5, le procédé consistant en outre à :
    envoyer, par l'entité VNFM, à l'entité NFVO, un message de notification incluant une capacité consommée pendant la première opération de gestion de VNF
  7. Procédé selon l'une quelconque des revendications 1 à 6, dans lequel la première opération de gestion de VNF comprend une opération de gestion de cycle de vie (LCM) de VNF
  8. Procédé selon la revendication 7, dans lequel l'opération de LCM de VNF comprend une opération d'instanciation, d'échelonnement, de mise à jour, de mise à niveau ou d'interruption.
  9. Procédé selon l'une quelconque des revendications 1 à 7, le procédé consistant en outre à :
    déterminer, par l'entité VNFM, qu'une seconde opération de gestion de VNF est dans le champ d'application de la permission, sur la base de l'indication d'octroi au déclenchement de la seconde opération de gestion de VNF ; et
    envoyer, par l'entité VNFM, une seconde demande d'affectation de ressources pour la seconde opération de gestion de VNF à l'entité VIM.
  10. Procédé selon l'une quelconque des revendications 1 à 7, le procédé consistant en outre à :
    déterminer, par l'entité VNFM, qu'une troisième opération de gestion de VNF est en dehors du champ d'application de la permission, sur la base de l'indication d'octroi au déclenchement de la troisième opération de gestion de VNF ; et
    envoyer, par l'entité VNFM, une demande d'octroi pour la permission de la troisième opération de gestion de VNF à l'entité NFVO.
  11. Système de gestion de ressources dans un système de virtualisation de fonctions de réseau (NFV), comprenant :
    un stockage de mémoire (1006) comprenant des instructions ; et
    un ou plusieurs processeurs (1004) en communication avec la mémoire, le ou les processeurs exécutant les instructions pour :
    recevoir, par une entité gestionnaire de fonctions de réseau virtualisées (VNFM), en provenance d'une entité orchestratrice de virtualisation de fonctions de réseau (NFVO), une indication d'octroi incluant une granularité d'octroi dans laquelle l'entité NFVO permet à l'entité gestionnaire de fonctions de réseau virtualisées (VNFM) de réaliser de multiples opérations de gestion de VNF pour une ou plusieurs VNF ;
    déterminer, par l'entité VNFM qu'une première opération de gestion de VNF est dans un champ d'application d'une permission, sur la base de l'indication d'octroi au déclenchement de la première opération de gestion de VNF ; et
    envoyer, par l'entité VNFM, une première demande d'affectation de ressources pour la première opération de gestion de VNF à une entité gestionnaire d'infrastructure virtuelle (VIM).
  12. Système selon la revendication 11, dans lequel la granularité d'octroi indique la ou les VNF permises à l'entité VNFM et les multiples opérations de gestion de VNF octroyées pour chacune de la ou des VNF permises.
  13. Système selon la revendication 12, dans lequel la ou les VNF comprennent une unique VNF, un groupe de VNF ou toutes les VNF appartenant à l'entité VNFM.
  14. Système selon l'une quelconque des revendications 11 à 13, dans lequel l'indication d'octroi comprend en outre une contrainte autorisée par l'entité NFVO pour la ou les VNF
  15. Système selon la revendication 14, dans lequel la contrainte comprend une capacité permise.
EP16789305.6A 2015-05-01 2016-05-03 Système et procédé de gestion des ressources Active EP3262795B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201562155845P 2015-05-01 2015-05-01
US15/144,629 US10263911B2 (en) 2015-05-01 2016-05-02 System and method for resource management
PCT/CN2016/080906 WO2016177311A1 (fr) 2015-05-01 2016-05-03 Système et procédé de gestion des ressources

Publications (3)

Publication Number Publication Date
EP3262795A1 EP3262795A1 (fr) 2018-01-03
EP3262795A4 EP3262795A4 (fr) 2018-03-21
EP3262795B1 true EP3262795B1 (fr) 2020-03-04

Family

ID=57205311

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16789305.6A Active EP3262795B1 (fr) 2015-05-01 2016-05-03 Système et procédé de gestion des ressources

Country Status (5)

Country Link
US (1) US10263911B2 (fr)
EP (1) EP3262795B1 (fr)
CN (1) CN107534579B (fr)
RU (1) RU2681371C1 (fr)
WO (1) WO2016177311A1 (fr)

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9578664B1 (en) 2013-02-07 2017-02-21 Sprint Communications Company L.P. Trusted signaling in 3GPP interfaces in a network function virtualization wireless communication system
US9686240B1 (en) 2015-07-07 2017-06-20 Sprint Communications Company L.P. IPv6 to IPv4 data packet migration in a trusted security zone
BR112018003775A2 (pt) * 2015-08-31 2018-09-25 Huawei Tech Co Ltd método e aparelho de gerenciamento de recursos
US9749294B1 (en) 2015-09-08 2017-08-29 Sprint Communications Company L.P. System and method of establishing trusted operability between networks in a network functions virtualization environment
KR20180061299A (ko) * 2015-09-29 2018-06-07 후아웨이 테크놀러지 컴퍼니 리미티드 네트워크 기능 가상화 자원 처리 방법 및 가상 네트워크 기능 관리자
JP6636142B2 (ja) * 2015-09-30 2020-01-29 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． スケールアウト関連付けの方法および装置、ならびにシステム
US10542115B1 (en) 2015-10-01 2020-01-21 Sprint Communications Company L.P. Securing communications in a network function virtualization (NFV) core network
US9811686B1 (en) 2015-10-09 2017-11-07 Sprint Communications Company L.P. Support systems interactions with virtual network functions in a trusted security zone
US10938638B2 (en) * 2015-10-26 2021-03-02 Nokia Solutions And Networks Oy Method and apparatus for virtualized network function decomposition
US9781016B1 (en) 2015-11-02 2017-10-03 Sprint Communications Company L.P. Dynamic addition of network function services
WO2017078790A1 (fr) * 2015-11-02 2017-05-11 Intel IP Corporation Rétablissement des performances de fonctions de réseau virtuelles (vnf) via une réinitialisation vnf de management du cycle de vie
US10250498B1 (en) 2016-10-03 2019-04-02 Sprint Communications Company L.P. Session aggregator brokering of data stream communication
WO2018090299A1 (fr) * 2016-11-17 2018-05-24 华为技术有限公司 Procédé et dispositif d'octroi d'autorisation de gestion de cycle de vie de service réseau
CN110199262A (zh) * 2016-11-23 2019-09-03 诺基亚通信公司 针对基于云的联网应用的容量缩放
CN108234158B (zh) * 2016-12-14 2021-04-20 中国电信股份有限公司 Vnf的建立方法、nfvo以及网络系统
US10445117B2 (en) * 2017-02-24 2019-10-15 Genband Us Llc Predictive analytics for virtual network functions
CN109257201B (zh) * 2017-07-14 2021-10-19 华为技术有限公司 一种License的发送方法和装置
US10348488B1 (en) 2017-08-25 2019-07-09 Sprint Communications Company L.P. Tiered distributed ledger technology (DLT) in a network function virtualization (NFV) core network
US11240135B1 (en) 2018-05-23 2022-02-01 Open Invention Network Llc Monitoring VNFCs that are composed of independently manageable software modules
US11855857B2 (en) * 2020-07-03 2023-12-26 Nippon Telegraph And Telephone Corporation Network virtualization system, virtual resource management device, virtual resource management method and program
RU2744940C1 (ru) * 2020-10-21 2021-03-17 Константин Евгеньевич Самуйлов Способ распределения виртуальных ресурсов оператора связи
US11847205B1 (en) 2020-10-26 2023-12-19 T-Mobile Innovations Llc Trusted 5G network function virtualization of virtual network function elements embedded on a system-on-chip

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040210623A1 (en) 2003-03-06 2004-10-21 Aamer Hydrie Virtual network topology generation
US8219807B1 (en) * 2004-12-17 2012-07-10 Novell, Inc. Fine grained access control for linux services
US9354927B2 (en) * 2006-12-21 2016-05-31 Vmware, Inc. Securing virtual machine data
US9847915B2 (en) 2013-01-11 2017-12-19 Huawei Technologies Co., Ltd. Network function virtualization for a network device
US9973375B2 (en) * 2013-04-22 2018-05-15 Cisco Technology, Inc. App store portal providing point-and-click deployment of third-party virtualized network functions
WO2015135611A1 (fr) * 2014-03-10 2015-09-17 Nokia Solutions And Networks Oy Notification concernant une migration en direct d'une machine virtuelle vers un gestionnaire vnf
BR112017001698A2 (pt) * 2014-08-07 2018-03-13 Intel Ip Corp gerenciamento de funções de rede virtualizadas
CN104219127B (zh) 2014-08-30 2018-06-26 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
KR102438042B1 (ko) 2014-09-25 2022-08-29 애플 인크. 네트워크 기능 가상화
CN105006634B (zh) * 2015-07-20 2018-10-02 清华大学 双层平面调相装置
US10187324B2 (en) * 2015-08-10 2019-01-22 Futurewei Technologies, Inc. System and method for resource management

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP3262795A1 (fr) 2018-01-03
EP3262795A4 (fr) 2018-03-21
CN107534579A (zh) 2018-01-02
US10263911B2 (en) 2019-04-16
US20160323200A1 (en) 2016-11-03
CN107534579B (zh) 2020-02-21
RU2681371C1 (ru) 2019-03-06
WO2016177311A1 (fr) 2016-11-10

Similar Documents

Publication Publication Date Title
EP3262795B1 (fr) Système et procédé de gestion des ressources
US11429408B2 (en) System and method for network function virtualization resource management
US10375015B2 (en) Methods and system for allocating an IP address for an instance in a network function virtualization (NFV) system
US10187324B2 (en) System and method for resource management
US11463384B2 (en) System and method for dynamic virtualized network function descriptor management
US10701139B2 (en) Life cycle management method and apparatus
US10397132B2 (en) System and method for granting virtualized network function life cycle management
EP2724244B1 (fr) Informatique en nuage native par intermédiaire de segmentation de réseau
US9225596B2 (en) Undifferentiated service domains
KR20120071981A (ko) 클라우드 컴퓨팅 시스템 및 클라우드 컴퓨팅 시스템에서의 트래픽 분산 방법 및 제어 방법
Takefusa et al. Virtual cloud service system for building effective inter-cloud applications
CN113424149A (zh) 跨虚拟机边界的低时延事件
EP4009160A1 (fr) Procédés de déploiement d'une application à travers de multiples domaines informatiques et dispositifs associés
US20180098327A1 (en) Congestion control method and network element device
US11824943B1 (en) Managed connectivity between cloud service edge locations used for latency-sensitive distributed applications
US20240256356A1 (en) Lcs emulated-physical-function-enabled resource system

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170928

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20180220

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/24 20060101AFI20180214BHEP

RIN1 Information on inventor provided before grant (corrected)

Inventor name: XIANG, ZHIXIAN

Inventor name: LIU, JIANNING

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/24 20060101AFI20190821BHEP

Ipc: G06F 9/455 20180101ALI20190821BHEP

INTG Intention to grant announced

Effective date: 20190923

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1241665

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200315

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016031159

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200604

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20200422

Year of fee payment: 5

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200304

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200604

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200605

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200729

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200704

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1241665

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200304

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016031159

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200531

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200531

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

26N No opposition filed

Effective date: 20201207

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200531

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20200604

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200503

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200604

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200503

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200504

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200531

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602016031159

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012240000

Ipc: H04L0041000000

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602016031159

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211201

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304