WO2017188682A1 - Nfvo ayant une fonction de gestion de licence de vnf et procédé de gestion de licence de vnf l'utilisant - Google Patents

Nfvo ayant une fonction de gestion de licence de vnf et procédé de gestion de licence de vnf l'utilisant Download PDF

Info

Publication number
WO2017188682A1
WO2017188682A1 PCT/KR2017/004336 KR2017004336W WO2017188682A1 WO 2017188682 A1 WO2017188682 A1 WO 2017188682A1 KR 2017004336 W KR2017004336 W KR 2017004336W WO 2017188682 A1 WO2017188682 A1 WO 2017188682A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
license
manager
vendor
network function
Prior art date
Application number
PCT/KR2017/004336
Other languages
English (en)
Korean (ko)
Inventor
옥기상
백은경
한제찬
Original Assignee
주식회사 케이티
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 케이티 filed Critical 주식회사 케이티
Publication of WO2017188682A1 publication Critical patent/WO2017188682A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0613—Third-party assisted
    • G06Q30/0619—Neutral agent
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G06Q20/145—Payments according to the detected use or quantity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0645—Rental transactions; Leasing transactions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements

Definitions

  • the present invention relates to network function virtualization (NFV), and more particularly, to a network function virtualization orchestrator that enables to manage licenses of virtualized network functions (VNFs) provided according to NFV technology.
  • NFVO NFV Orchestrator
  • VNF license management method using the same.
  • Network Function Virtualization (NFV) technology is a technology that enables faster and more flexible service by installing and removing network devices previously provided as hardware in the form of software in a general-purpose server infrastructure.
  • license management In the NFV service environment, license management has changed dramatically. In the past, licenses were assigned to hardware devices, and hardware and licenses were 1: 1. However, in a softwareized NFV service environment, license management is based on the same software image. Since instances can be created, the relationship between the software image and the license changes to 1: n.
  • VNF Virtualized Network Function
  • a license must be newly assigned and activated, and when the VNF is deleted, a process of removing license information is required.
  • these licenses must be issued or returned by the vendor providing the VNF, and each of these VNF licenses is a unit in which the vendor bills the carrier for the VNF, or a unit in which the carrier provides services to the customer. Management is a very sensitive and important issue.
  • VNF license management should be managed automatically when scaling through VNF or lifecycle management functions such as creation, deletion, modification, etc. of VNF. Every time a user installs, deletes, or increases or decreases the number of VNFs installed in a network of numerous customers or in a national network, it is difficult and manual to assign, remove, and measure licenses manually. In addition, it is necessary to measure a customer's usage of the license application status applied to each VNF or to the VNF to which the license is assigned, and deliver it to a billing system for billing. In this way, the measured usage information should be automatically applied for settlement between the service provider and the VNF vendor.
  • VNF license management is required to commercialize a virtual network with Network Function Virtualization (NFV), but there is insufficient standardization in this field.
  • NFV Network Function Virtualization
  • the reality is that each VNF vendor is designing information structures and processing functions to handle licenses in different forms.
  • the ETSI / NFV Standards Committee defines the structure and interface specifications for managing VNFs in a standardized way among different VNF vendors, and it is necessary to define standard license-driven interfaces and processes for standardized VNF license management.
  • the first object of the present invention for solving the above problems is, in the NFV technology-based service environment provided by the network device is provided in the software, VNF license allocation, release, usage measurement, etc. according to the creation and deletion of the VNF It provides a network function virtualization orchestrator with VNF license management.
  • a second object of the present invention for solving the above problems, in the NFV technology-based service environment provided by the network device is provided in the software, VNF license allocation, release, usage measurement, etc. according to the creation and deletion of the VNF It provides a way to manage VNF licenses.
  • a third object of the present invention for solving the above problems is, in the NFV technology-based service environment provided by the network device is provided in the software, VNF license allocation, release, usage measurement, etc. according to the creation and deletion of the VNF It is to provide a network virtualization system that can be done.
  • Network function virtualization orchestrator (NFVO) according to an aspect of the present invention for achieving the first object of the present invention described above request and return the license key of the VNF to the license manager of the VNF vendor, the VNF A license management function unit configured to set the license key in and check or verify a license state of the VNF; And a license management database that stores a license state of the VNF.
  • NFVO Network function virtualization orchestrator
  • the license manager of the VNF vendor may be a VNF manager (VNFM) of the VNF vendor.
  • VNFM VNF manager
  • the license manager of the VNF vendor may be a local license manager existing in a service provider's internal network or a global license manager existing on the Internet.
  • the license management function unit may further include a function of collecting license usage information according to the license key set in the VNF and providing the billing system of a telecommunication company or a billing system of the VNF vendor.
  • the license usage information may be used for mutual settlement between the telecommunication company and the VNF vendor.
  • the license management function unit secures a license to be provided to the VNF from the license manager of the VNF vendor in the form of a license pool in the license management database, or on-demand at the request of the VNF. ) Can be secured in the form of.
  • the VNF license management method may be performed by a network function virtualization orchestrator (NFVO).
  • NFVO network function virtualization orchestrator
  • the license manager of the VNF vendor may be a VNF manager (VNFM) of the VNF vendor.
  • VNFM VNF manager
  • the license manager of the VNF vendor may be a local license manager existing in a service provider's internal network or a global license manager existing on the Internet.
  • the VNF license management method may further include collecting license usage information according to the license key set in the VNF, and providing the license usage information to a billing system of a telecommunication company or a billing system of the VNF vendor.
  • the license usage information may be used for mutual settlement between the telecommunication company and the VNF vendor.
  • Network function virtualization system for achieving the third object of the present invention described above is composed of a VNF element, Network Function Virtualization Infrastructure (NFV), and NFV, VNFM, and VIM (Virtualization Infrastructure Manager) A Management and Coordination (MANO) element, wherein the NFVO requests and returns a license key of the VNF to the license manager of the VNF vendor, sets the license key to the VNF, and displays the license status of the VNF. License management function to verify or verify; And a license management database that stores a license state of the VNF.
  • NFV Network Function Virtualization Infrastructure
  • VNFM Virtualization Infrastructure Manager
  • VIM Virtualization Infrastructure Manager
  • the license management function unit may further include a function of collecting license usage information according to the license key set in the VNF and providing the billing system of a telecommunication company or a billing system of the VNF vendor.
  • the license usage information may be used for mutual settlement between the telecommunication company and the VNF vendor.
  • the license management function unit secures a license to be provided to the VNF from the license manager of the VNF vendor in the form of a license pool in the license management database, or on-demand at the request of the VNF. ) Can be secured in the form of.
  • the license of the NFVO compared to the conventional license management method that allows the VNF vendor license manager to directly issue or return a license every time a VNF is created / modified / deleted.
  • the management function it is possible to obtain license information from the license manager of the VNF vendor, to install / delete the VNF license information to the VNF, and to measure the amount of usage thereof. It can be solved.
  • a carrier may be provided with a means to reliably charge for VNF that can be created / deleted at any time by software.
  • the VNF vendor license manager manages licenses for each VNF, and does not manage any network services provided by a telecommunications company.
  • the network management criteria are provided through the license management function unit of the NFVO. VNF license management can be done.
  • network services are not a single VNF but a combination of VNFs from various vendors, the relationship between them and license management centered on network services can only be achieved by having a corresponding license management module and database in NFVO.
  • VNF vendor license manager the license processing due to the network failure of the network service unit is very difficult.
  • the structure of the NFVO according to an embodiment of the present invention, it may be possible to recover by reassigning a license for network failure using VNF and VNF license allocation information for each network service stored in a database.
  • FIG. 1 is a block diagram illustrating an ETST NFV architecture to which a VNF scaling method and a virtualization network function manager according to the present invention are applied.
  • FIG. 2 is a block diagram illustrating a configuration of an NFVO including a license management function according to an embodiment of the present invention.
  • FIG. 3 is a flowchart illustrating a VNF generation step of the VNF license management method according to an embodiment of the present invention.
  • FIG. 4 is a flowchart illustrating a license usage information collection step of the VNF license management method according to an embodiment of the present invention.
  • FIG. 5 is a conceptual diagram illustrating an example of a method for providing a license in an NFV license management method according to the present invention.
  • FIG. 6 is a conceptual diagram illustrating another example of a method for providing a license in the NFV license management method according to the present invention.
  • FIG. 7 is a conceptual diagram illustrating another example of a method of providing a license in the NFV license management method according to the present invention.
  • first, second, A, and B may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
  • the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.
  • FIG. 1 is a block diagram illustrating an ETST NFV architecture to which a VNF scaling method and a virtualization network function manager according to the present invention are applied.
  • the NFV architecture proposed by ETSI may include a virtualized network function (VNF) 120 and a network function virtualization infrastructure (NFVI) 140. .
  • VNF virtualized network function
  • NFVI network function virtualization infrastructure
  • the Operations Support System is a system for supporting the operator's network operation and the provision and maintenance of customer service
  • the Business Support System is the billing for the customer, the customer relationship management (CRM) Relationship management) and call center business automation.
  • At least one VNF instance 121-1,..., 121 -N may exist on the VNF 120, and element management (EM) 122-1,..., 122 -N (EM) corresponding to each of these may exist.
  • EM element management
  • NFV Management and Orchestration Component (MANO) 150 for managing and coordinating the components on the NFV architecture.
  • MANO NFV Management and Orchestration Component
  • the MANO 150 manages virtual resources (networking resources, network resources, storage resources) and orchestrate the virtual resources. Therefore, it checks the availability of virtual resources for network services consisting of multiple VNFs, takes charge of the actual deployment of them, and configures the distribution order and related information between VNFs for successful initiation of services. Must be delivered.
  • a coordinator 151 coordinating the overall operation, a virtualized network function manager (VNFM) 152 managing the VNF 120, and a virtualization infrastructure managing the NFVI 140.
  • VNFM virtualized network function manager
  • VIP virtualized infrastructure manager
  • the role of the VNFM 152 is to perform lifecycle management of the VNFs between the VNFs and the orchestrator 151 that manages virtual resources and services.
  • the VNFM 152 manages the association between virtual resources and VNFs in a cloud environment and immediately maintains and optimizes the continuity of services provided by VNFs in response to events or state changes occurring between them. do.
  • the role of the VIM 153 is responsible for the control and management of the NFVI to be described later, and typically serves to control and manage the NFVI existing in the infrastructure domain of the operator unit.
  • NFVI refers to the hardware and software elements that make up the environment where VNF can run. OpenStack, CloudStack, and others are based on open source, and each NFVI provides its own application program interface.
  • NFVI can be divided into three domains, compute domain (including storage), hypervisor domain, and infrastructure network domain.
  • Virtual computing and virtual storage belonging to the hypervisor domain refer to virtual resources allocated to virtual machines based on physical resources, and the virtualization layer refers to hypervisors such as KVM and XEN.
  • NFVI has a Virtualized Infrastructure Manager (VIM) and a reference point Nf-Vi, and has a VNF and Vn-Nf reference architecture.
  • VIP Virtualized Infrastructure Manager
  • FIG. 2 is a block diagram illustrating a configuration of an NFVO including a license management function according to an embodiment of the present invention.
  • the NFVO 200 may include a license management function 210 and a license management database 220.
  • the license management unit 210 may include at least one of a license classification unit 211, a license policy management unit 212, a license key management unit 213, and a license usage metering unit 214. have.
  • the detailed elements 211 to 214 of the license management function 210 are only examples of components corresponding to the roles performed by the license management function 210, and the detailed components are one. It may be configured as a software module of, or may be configured as two or more software modules that perform two or more roles.
  • the license management unit 210 may include a VNF instance (eg, 230), a VNFM 240, a billing system 250 of a provider BSS / OSS, a local license manager 260 of a VNF vendor, and a global license of a VNF vendor. It may have an interface with at least one of the manager 270 and the OSS billing system 280 of the VNF vendor.
  • the license management function 210 of the NFVO 200 may have an interface (Vnf-Nfvo.Lm) with respective VNF instances, and interface with the operator's billing system 250 (Oss.Bill-Nfvo. Lm) and an interface (VnfLIm-Nfvo.Lm) with the local license manager 260 of the VNF vendor.
  • the interfaces (Nfvo.Lm-Vnfm.Lm, Nfvo.Lm-VnfLm, Nfvo.Lm-VnfOss.Bill) are license management function 210, VNFM 240, and global license manager 270 of VNF vendor, respectively.
  • an interface with the OSS billing system 280 of the VNF vendor are license management function 210, VNFM 240, and global license manager 270 of VNF vendor.
  • the local license manager 260 of the VNF vendor is a license manager directly connected to the VNF.
  • the local license manager 260 is located in the same host as the VNF instance or in the same network domain as the host where the VNF instance is created, It may be a license manager that resides within a network domain of a (i.e., service provider internal network specific point).
  • the global license manager 270 of the VNF vendor is a license manager of a vendor existing on the Internet, and is a component that provides a service to various customers of the vendor without providing a service limited to a specific telecommunication company.
  • FIG. 3 is a flowchart illustrating a VNF generation step of the VNF license management method according to an embodiment of the present invention.
  • the VNF license management method described in FIG. 3 is a method performed in the VNF generation step.
  • the license management function unit 211 of the NFVO 210 and the license manager 260 or 270 of the VNF vendor and the VNF described in FIG. It may be performed by the interworking between the 230.
  • the function of the license manager of the VNF vendor may be configured to be performed by the VNFM 240 described with reference to FIG. 2.
  • the NFVO 200 ie, the license management function 210 of the NFVO
  • the NFVO 200 identifies the category of the VNF to be generated (S301), and checks the license availability of the identified VNF category for the license manager of the VNF vendor.
  • S310 if a license is available, a license key is requested to the VNF vendor license manager 260 or 270 (S321), and a license key is received (S322).
  • the license manager (260 or 270) of the VNF vendor or the NFVO (i.e., the license management function 210 of the NFVO) generates the requested VNF 230 through the VNFM 240 and generates the received license key.
  • Set to 230 (S330).
  • the generated VNF 230 and the license manager 260 or 270 of the VNF vendor may additionally perform a process S331 of mutually verifying the set license key.
  • the NFVO ie, the license management function unit 210 of the NFVO
  • the NFVO may perform a procedure for verifying a license setting state of the VNF 230 (S340).
  • steps S331 and S340 are not essential procedures, and may be performed according to the requirements of the license management function unit 210 of the VNF vendor or the NFVO, or may be performed differently from the illustrated procedures. have.
  • the NFVO (ie, the license management function 210 of the NFVO) may update the license management database 220 to manage the assignment state of the license key for the NFV 230 (S350).
  • the NFVO 200 may transmit a deletion (release) request of the VNF 230 to the VNF 230 (S360).
  • the NFVO ie, NFVO's license management function 210) requests the license manager 260 or 270 of the VNF vendor to release the license assigned to the VNF 230 in response to the deletion of the VNF 230.
  • the license release fact of the VNF 230 may be updated on the license management database 220 (S380).
  • FIG. 4 is a flowchart illustrating a license usage information collection step of the VNF license management method according to an embodiment of the present invention.
  • the VNF license management method described in FIG. 4 is a method of collecting and providing license usage information performed at the VNF usage stage.
  • the license management function 210 of the NFVO 200 described in FIG. 2 and a license of a VNF vendor are described. It may be performed by the interworking between the manager 260 or 270, the VNF 230, the carrier's billing system 250, and the VNF vendor's billing system 280.
  • License usage information is information required to charge customers or settle costs with VNF vendors based on usage, and may be collected through the VNF entity 230 and the license manager 260 or 270 of the VNF vendor (S411, S412).
  • the collected license usage information is verified by comparing the information recorded in the license management database 220 by the license management unit 210 of the NFVO 200 (S420).
  • the verified license usage information is provided to the billing system 250 of the telecommunication company (S430) and used for billing, and is also provided to the billing system 270 of the VNF vendor to be used for mutual settlement (S440).
  • a license management function 210 and a license management database 220 need to be defined in the NFVO.
  • new entities such as license managers 260 or 270 of VNF vendors, are defined and also need to define standard interfaces between these entities and NFVO, VNF vendors' VNFMs, and VNF instances.
  • the VNF vendor may also provide license management functionality through a vendor's internal license manager, which may be in the form of a local license manager 260 or a global license manager 270 on the Internet that exists inside a service provider (carrier). May also be present.
  • the vendor may provide a license management function in the VNFM 240.
  • License usage of each VNF may be measured and provided for billing in the billing system. This usage information is needed to settle costs between the service provider and the VNF vendor.
  • Table 1 summarizes the functional requirements that the license management function 210 of NFVO, that is, NFVO, has to manage VNF licenses.
  • Nfvo.LM.001 When a VNF is created or capacity is increased, NFVO must be able to provide license key assignment capabilities to the VNF License Manager or VNF Manager. Nfvo.LM.002 When a VNF object is running, the NFVO must be able to request and receive the VNF license status or information for a particular VNF object through the VNF License Manager or the VNF Manager. Nfvo.LM.003 When a VNF object is deleted, the NFV orchestrator must be able to release license key information through the VNF Manager or Vendor VNF License Manager.
  • Nfvo.LM.004 When a VNF object is running, the NFVO must be able to request collection of license usage information through either the vendor VMF Manager or the Vendor VNF License Manager. Nfvo.LM.005 When license information is collected through the VNF License Manager or VNF Manager, the NFVO must be able to verify and compare the collected information with the information managed by NFV Orchestrator.
  • the VNF may have a different license allocation method and billing method for each vendor.
  • the license allocation and charging through the NFVO may be performed in at least one of the following three methods described with reference to FIGS. 5 to 7.
  • FIG. 5 is a conceptual diagram illustrating an example of a method for providing a license in an NFV license management method according to the present invention.
  • the NFVO 200 of a carrier may form a license pool 400 by obtaining a license from an NFV vendor 300 (eg, a license manager of a VNF vendor) in advance (S510).
  • the information about the license pool 400 secured in advance may be stored in the license management database 220 of the NFVO described above.
  • a license key is requested to the NFVO 200 (S520), and the license key is distributed in response to the request (S530). License authentication is performed between the license manager 260 or 270 of the VNF vendor 300 and the VNF (S540 and S550; see step S331 of FIG. 3), and the license fee is post-billed by the vendor (S560).
  • the difference between the license pool 400 of FIG. 5 and the license pool 410 described in FIG. 6 is that the method described in FIG. 6 configures a license pool by purchasing a license from a VNF vendor in advance. Is that you only get a license that can be assigned to the VNF and you do not pay for it before you actually use it.
  • An advantage of the scheme described in FIG. 5 is that a license can be provided immediately when the VNF is created, and there is no need to pay a license fee before using the software image in the actual VNF.
  • FIG. 6 is a conceptual diagram illustrating another example of a method for providing a license in the NFV license management method according to the present invention.
  • the license pool 410 is formed by purchasing as many licenses as expected from the vendor 300 in advance (S610).
  • the information about the license pool 410 secured in advance may be stored in the license management database 220 of the NFVO described above.
  • An advantage of the scheme described in FIG. 6 is that a license can be provided immediately when the VNF is created, and that the license can be reused.
  • the disadvantage of the method described in Figure 6 is that the license information associated with the vendor should be secured, licenses must be secured in advance according to various request types according to the customer, and the license of the unused state must also be secured.
  • FIG. 7 is a conceptual diagram illustrating another example of a method of providing a license in the NFV license management method according to the present invention.
  • the method described in FIG. 7 is a method of obtaining a license from a vendor only when necessary (ie, an on-demand method).
  • the license function management unit 210 of the NFVO receives a license request (S710), obtains a license from a vendor (purchase or lease) (S720), and distributes the obtained license to the NFV (S730). .
  • An advantage of the scheme described in FIG. 7 is that it does not have to have an unused license.
  • the drawback of the scheme described in Figure 7 is that because the license is assigned when necessary, there is a delay in the initial service provision, and it is difficult to recycle the license because it identifies the license assignment based on MAC address, the authorization server for obtaining a license key It is necessary to develop interlocking functions between the vendor and the vendor.
  • the methods according to the invention can be implemented in the form of program instructions that can be executed by various computer means and recorded on a computer readable medium.
  • Computer-readable media may include, alone or in combination with the program instructions, data files, data structures, and the like.
  • the program instructions recorded on the computer readable medium may be those specially designed and constructed for the present invention, or may be known and available to those skilled in computer software.
  • Examples of computer readable media include hardware devices that are specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like.
  • Examples of program instructions include machine language code, such as produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like.
  • the hardware device described above may be configured to operate with at least one software module to perform the operations of the present invention, and vice versa.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un NFVO ayant une fonction de gestion de licence de VNF et un procédé de gestion de licence de NFV l'utilisant. Le NFVO capable de gérer la licence d'une VNF peut comprendre : une unité de fonction de gestion de licence pour demander une clé de licence de la VNF auprès d'un gestionnaire de licence d'un vendeur de VNF et répondre à cette dernière, régler la clé de licence dans la VNF, et vérifier un état de licence de la VNF ; et une base de données de gestion de licence pour stocker l'état de licence de la VNF. Par conséquent, des informations de licence de VNF peuvent être gérées d'une manière unifiée pour différents éléments d'informations de licence de VNF de différents vendeurs, une quantité d'utilisation de licence entre le vendeur de VNF et le NFVO peut être vérifiée mutuellement, et une facturation fiable peut être réalisée pour la VNF, qui peut être créée/supprimée fréquemment par un fournisseur de communication dans un réseau basé sur une technologie de NFV.
PCT/KR2017/004336 2016-04-25 2017-04-24 Nfvo ayant une fonction de gestion de licence de vnf et procédé de gestion de licence de vnf l'utilisant WO2017188682A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2016-0050433 2016-04-25
KR20160050433 2016-04-25

Publications (1)

Publication Number Publication Date
WO2017188682A1 true WO2017188682A1 (fr) 2017-11-02

Family

ID=60160980

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/004336 WO2017188682A1 (fr) 2016-04-25 2017-04-24 Nfvo ayant une fonction de gestion de licence de vnf et procédé de gestion de licence de vnf l'utilisant

Country Status (2)

Country Link
KR (1) KR102319503B1 (fr)
WO (1) WO2017188682A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019207156A1 (fr) * 2018-04-27 2019-10-31 Comptel Oy Procédé et agencement pour gestion de licence dans un environnement de réseau nfv
US11663298B2 (en) * 2019-12-11 2023-05-30 At&T Intellectual Property I, L.P. Managing enterprise software licenses for virtual network functions
US11784875B1 (en) 2022-07-29 2023-10-10 Cisco Technology, Inc. Systems and methods for automatic license management of carrier neutral facility (CNF) services

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102500137B1 (ko) * 2018-03-30 2023-02-15 삼성전자주식회사 네트워크 기능 가상화 환경에서 네트워크 자원 관리를 위한 장치 및 방법

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110132286A (ko) * 2010-06-01 2011-12-07 인터내셔널 비지네스 머신즈 코포레이션 가상화 환경에서 라이센스 권리부여의 관리를 위한 시스템 및 방법
WO2014138148A2 (fr) * 2013-03-06 2014-09-12 Siemens Aktiengesellschaft Système de gestion de licence à base de fichier dans un environnement de virtualisation
US20140282821A1 (en) * 2013-03-15 2014-09-18 Symantec Corporation Systems and methods for identifying a secure application when connecting to a network
US20160043944A1 (en) * 2014-08-05 2016-02-11 Amdocs Software Systems Limited System, method, and computer program for augmenting a physical system utilizing a network function virtualization orchestrator (nfv-o)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101239301B1 (ko) 2009-07-06 2013-03-05 한국전자통신연구원 라이센스 관리 장치 및 방법
JP5449283B2 (ja) * 2011-09-26 2014-03-19 株式会社日立システムズ クラウド共用型リソース提供システム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110132286A (ko) * 2010-06-01 2011-12-07 인터내셔널 비지네스 머신즈 코포레이션 가상화 환경에서 라이센스 권리부여의 관리를 위한 시스템 및 방법
WO2014138148A2 (fr) * 2013-03-06 2014-09-12 Siemens Aktiengesellschaft Système de gestion de licence à base de fichier dans un environnement de virtualisation
US20140282821A1 (en) * 2013-03-15 2014-09-18 Symantec Corporation Systems and methods for identifying a secure application when connecting to a network
US20160043944A1 (en) * 2014-08-05 2016-02-11 Amdocs Software Systems Limited System, method, and computer program for augmenting a physical system utilizing a network function virtualization orchestrator (nfv-o)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KIM, HYUN-CHUL: "Management, Orchestration and Security in Network Function Virtualization", CONVERGENCE SECURITY JURNAL, vol. 16, 2 March 2016 (2016-03-02), pages 19 - 23 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019207156A1 (fr) * 2018-04-27 2019-10-31 Comptel Oy Procédé et agencement pour gestion de licence dans un environnement de réseau nfv
US10999161B2 (en) 2018-04-27 2021-05-04 Comptel Oy Method and arrangement for licence management in NFV network environment
US11663298B2 (en) * 2019-12-11 2023-05-30 At&T Intellectual Property I, L.P. Managing enterprise software licenses for virtual network functions
US11784875B1 (en) 2022-07-29 2023-10-10 Cisco Technology, Inc. Systems and methods for automatic license management of carrier neutral facility (CNF) services

Also Published As

Publication number Publication date
KR102319503B1 (ko) 2021-10-29
KR20170121714A (ko) 2017-11-02

Similar Documents

Publication Publication Date Title
WO2017188682A1 (fr) Nfvo ayant une fonction de gestion de licence de vnf et procédé de gestion de licence de vnf l'utilisant
WO2018203635A1 (fr) Procédé de conteneurisation d'une application sur une plateforme en nuage
WO2020017844A1 (fr) Procédé de surveillance d'une pluralité de grappes et d'applications dans une plateforme en nuage
WO2018135766A1 (fr) Dispositif et procédé de gestion de données au moyen d'une chaîne de blocs
WO2013137528A1 (fr) Système de règlement de transaction hors-ligne, et procédé et dispositif à cet effet
WO2019198885A1 (fr) Plate-forme de service décentralisée utilisant une pluralité de nœuds de service basés sur une chaînes de blocs
WO2019132314A1 (fr) Appareil et procédé de virtualisation de fonction de réseau dans un système de communication sans fil
WO2013028009A2 (fr) Système de bureau intelligent, serveur destiné au fonctionnement et procédé de fonctionnement
CN108446102A (zh) 一种开发部署应用程序的一体化系统及方法
CN111835679B (zh) 多租户场景下的租户资源管理方法和装置
CN111651738A (zh) 基于前后端分离架构的细粒度角色权限统一管理方法及电子装置
WO2014084608A1 (fr) Procédé et système de gestion d'élément sécurisé
CN106412576A (zh) 测试方法和装置
CN115129423A (zh) 资源管理方法、装置、设备及存储介质
WO2019190095A1 (fr) Dispositif et procédé de gestion de ressources de réseau dans un environnement de virtualisation de fonction de réseau
US12013750B2 (en) Network service management apparatus and network service management method
EP4227813A1 (fr) Système de gestion de service de réseau et procédé de gestion de service de réseau
CN100531053C (zh) 一种设备管理的方法及系统
US20230333952A1 (en) Infrastructure management system and method
WO2019098428A1 (fr) Procédé de fourniture de fonction erp faisant appel à une table de gestion extensible spécifique à un utilisateur, et système de fourniture de fonction erp permettant la mise en œuvre dudit procédé
WO2018021864A1 (fr) Procédé pour fournir un service en nuage
WO2023050110A1 (fr) Procédé de mise en œuvre d'un changement automatique de mot de passe ayant un mécanisme de tolérance aux défauts pour hôte en nuage et hôte bastion en nuage
WO2020145458A1 (fr) Procédé de fourniture d'un service de réseau hôte neutre à l'aide d'une chaîne de blocs, et système et dispositif associés
WO2019168239A1 (fr) Système de compte virtuel utilisant un réseau de chaîne de blocs et une émission de compte virtuel ainsi que son procédé de dépôt
WO2019117404A1 (fr) Serveur et procédé de commande de transmission de paquets

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17789866

Country of ref document: EP

Kind code of ref document: A1

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

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

122 Ep: pct application non-entry in european phase

Ref document number: 17789866

Country of ref document: EP

Kind code of ref document: A1