KR102062581B1 - Method and apparatus providing user interface for establishing virtual infrastructure management - Google Patents

Abstract

Disclosed are a method and an apparatus for providing a user interface for establishing a VIM. According to an embodiment of the present invention, a method for providing a user interface comprises the following steps of: displaying a first graphic element including multiple types of VIMs for establishing a network function virtualization (NFV) environment; receiving a first user input for the first graphic element by selecting a first type of VIM corresponding to any one of the multiple types of VIMs; displaying a second graphic element including authentication schemes allowed in the selected first type of VIM; receiving a second user input for the second graphic element by selecting a first authentication scheme corresponding to any one of the displayed authentication schemes; and providing the NFV environment to an NFV server based on the first type of VIM to which the first authentication scheme is applied.

Description

METHOD AND APPARATUS PROVIDING USER INTERFACE FOR ESTABLISHING VIRTUAL INFRASTRUCTURE MANAGEMENT}

The following embodiments are related to a method and apparatus for providing a user interface for building a VIM.

Network Functional Virtualization (NFV) is a new network architecture framework that can provide the infrastructure flexibility and agility needed to successfully compete in today's evolving communications environment. For example, to cope with the increased use of networks by Internet-of-Things (IoT) and to meet the need for new network services and performance guarantees, NFV can reduce costs and accelerate service deployment. Network operators or telecommunications service providers Communication Service Providers (CSPs) use virtualization and cloud technology to separate network functions from hardware and enable firewalls, routers, network address translation (NAT), dynamic host configuration protocol (DHCP), and domain (DNS). You can transform traditional networking by abstracting network services such as Name System (VNF) into software called Virtual Network Function (VNF). As a result, NFV offers the opportunity to significantly increase infrastructure flexibility, simplify resource management processes, and reduce capital and operating costs.

According to an embodiment, a method of providing a user interface for building a virtual infrastructure management (VIM) may include displaying a first graphic element including a plurality of types of VIMs for building a network function virtualization (NFV) environment; Receiving a first user input for the first graphical element that selects a first type of VIM corresponding to any one of the plurality of types of VIMs; Displaying a second graphical element comprising authentication schemes allowed in the selected first type of VIM; Receiving a second user input for the second graphical element selecting a first authentication scheme corresponding to any of the displayed authentication schemes; And providing the NFV environment to an NFV server based on the first type of VIM to which the first authentication method is applied.

The plurality of types of VIMs may include an OpenStack type VIM, a Kubernetes type VIM, and a VMware type VIM.

Pre-registered authentication methods include username and password-based authentication methods, bearer token-based authentication methods, and Secure Sockets Layer authentication (SSL) -based authentication methods, and are allowed in the selected first type of VIM. The authentication schemes may correspond to some of the pre-registered authentication schemes.

Each of the plurality of types of VIMs has unique authentication schemes according to the characteristics of each of the plurality of types of VIMs, and the second graphic element includes unique authentication schemes corresponding to the first type of VIM. can do.

The authentication schemes included in the second graphical element provided with respect to the first type of VIM and the authentication schemes included in a third graphical element provided with respect to a second type of VIM different from the first type may be different. have.

Displaying the first graphical element comprises accessing a database where available VIMs are stored; And configuring the first graphical element based on the database, wherein the available VIMs can be updated periodically or aperiodically.

The database further stores authentication schemes mapped to each of the available VIMs, and displaying the second graphical element accesses the database to extract authentication schemes mapped to the selected first type of VIM. step; And configuring the second graphic element based on the extracted authentication schemes.

According to an embodiment, an apparatus for providing a user interface for building a virtual infrastructure management (VIM) may include a processor; And a memory including instructions readable by the processor, wherein when the instructions are executed on the processor, the processor includes a plurality of types of VIMs for establishing a Network Function Virtualization (NFV) environment Receive a first user input for the first graphical element that indicates an element and selects a first type of VIM that corresponds to any one of the plurality of types of VIMs, and in the selected first type of VIM Receive a second user input for the second graphical element, indicating a second graphical element including allowed authentication schemes, selecting a first authentication scheme corresponding to any of the displayed authentication schemes, and The NFV environment is provided to an NFV server based on the first type of VIM to which the first authentication scheme is applied.

The processor accesses a database in which available VIMs are stored, configures the first graphical element based on the database, and the available VIMs can be updated periodically or aperiodically.

The database further stores authentication schemes mapped to each of the available VIMs, the processor accesses the database to extract authentication schemes mapped to the selected first type of VIM, and the extracted authentication schemes. Based on the second graphic element.

1 is a diagram illustrating an NFV server and a user interface providing apparatus according to an exemplary embodiment.
2 is a diagram illustrating a user interface providing method according to an exemplary embodiment.
3 illustrates a database according to one embodiment.
4 illustrates a user interface in accordance with one embodiment.
5 illustrates an NFV architecture according to one embodiment.
6 illustrates an apparatus for providing a user interface according to an exemplary embodiment.

Specific structural or functional descriptions of the embodiments according to the inventive concept disclosed herein are merely illustrated for the purpose of describing the embodiments according to the inventive concept, and the embodiments according to the inventive concept. These may be embodied in various forms and are not limited to the embodiments described herein.

Embodiments according to the inventive concept may be variously modified and have various forms, so embodiments are illustrated in the drawings and described in detail herein. However, this is not intended to limit the embodiments in accordance with the concept of the present invention to specific embodiments, and includes modifications, equivalents, or substitutes included in the spirit and scope of the present invention.

Terms such as first or second may be used to describe various components, but the components should not be limited by the terms. The terms are only for the purpose of distinguishing one component from another component, for example, without departing from the scope of the rights according to the inventive concept, the first component may be called a second component, Similarly, the second component may also be referred to as the first component.

When a component is said to be “connected” or “connected” to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in the middle. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between. Expressions that describe the relationship between components, such as "between" and "immediately between," or "directly neighboring to," should be interpreted as well.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, the terms “comprise” or “have” are intended to designate that the stated feature, number, step, operation, component, part, or combination thereof exists, but includes one or more other features or numbers, It is to be understood that it does not exclude in advance the possibility of the presence or addition of steps, actions, components, parts or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are not construed in ideal or excessively formal meanings unless expressly defined herein. Do not.

Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings. However, the scope of the patent application is not limited or limited by these embodiments. Like reference numerals in the drawings denote like elements.

1 is a diagram illustrating an NFV server and a user interface providing apparatus according to an exemplary embodiment.

Referring to FIG. 1, an NFV server 110 includes an NFV Management and Orchestration 111 and an NFV Infrastructure 115. NFVI 115 includes hardware and software components on which Virtual Network Functions (VNFs) are deployed. The NFV MANO 111 includes an NFV Orchestrator (NFVO) 112, a VNF Manager (VNFM) 113, a Virtual Infrastructure Management (VIM) 114, and organizes and manages the lifecycle of NFVI resources and VNFs.

Currently, various types of VIMs are appearing in relation to OpenStack Tacker, and each type of VIM supports various authentication methods. However, there is no web interface that can manage these different types of VIM. As the number of VIM types increases, they will be integrated into the tacker according to industry requirements, requiring a new, flexible and user-friendly interface for managing different types of VIM.

The apparatus 120 for providing a VIM according to an embodiment may provide an interface for managing various types of VIM using a multiple authentication method. The user may select various VIM types through the user interface providing apparatus 120 and select different authentication methods for each type of VIM. The user may be an operator of the NFV server 110. The user interface providing apparatus 120 may provide an environment for communicating with the selected VIM. According to an embodiment, the apparatus 120 for providing a user interface may provide a Django-based web interface, and a user may list, display, create, and delete various types of VIM requiring various types of authentication. have. In addition, the user interface providing apparatus 120 may easily extend and support a user interface whenever a new kind of VIM is integrated into OpenStack.

To do this, a VIM registration form module must be created to include the selection of the VIM type, and the VIM registration form must be able to select an authentication method for each type. In addition, to provide the above functionality, a new JavaScript module is required in the registration form to switch between different VIM types and authentication methods.

OpenStack Tacker is a system for NFV management and orchestration, and Django Framework is an advanced Python web framework that promotes rapid development and clean, practical design. The Horizon dashboard provides a web-based user interface to OpenStack services such as Nova, Swift, Keystone, and Tacker. Python is the programming language used for the system's back end and web interface. JavaScript is the scripting language used to control front end logic and behavior.

2 is a diagram illustrating a user interface providing method according to an exemplary embodiment.

Referring to FIG. 2, in operation 210, the apparatus for providing a user interface displays a first graphic element. The first graphical element may comprise a plurality of types of VIMs for building an NFV environment. According to an embodiment, the plurality of types of VIMs may include at least one of an OpenStack type VIM, a Kubernetes type VIM, and a VMware type VIM. However, the plural types of VIMs are not limited thereto, and may be further registered when additional VIM types occur according to future development.

In operation 220, the apparatus for providing a user interface receives a first user input I1 from a user. The user may input necessary information through the user terminal, and the user input may be received at the user interface providing device through a web environment. The first user input I1 may be for a first graphical element that selects a first type of VIM corresponding to any one of a plurality of types of VIMs. For example, the first graphic element may represent a plurality of types of VIMs in the form of a list, and the first user input I1 may correspond to an input of clicking or touching one of the VIM types in the list.

In operation 230, the apparatus for providing a user interface determines whether the user input I1 corresponds to the VIM type identifier V1. For example, the VIM type identifier V1 may correspond to an OpenStack type VIM. For convenience of description, the VIM type identifier V1 may be referred to as a first type of VIM. Step 231 may be performed when the user input I1 corresponds to the VIM type identifier V1, and step 240 may be performed when the user input I1 does not correspond to the VIM type identifier V1. .

In operation 231, the apparatus for providing a user interface displays a second graphic element. The second graphical element may include the authentication schemes allowed in the selected first type of VIM. Depending on the characteristics of each type of VIM, there may be unique authentication methods for each type of VIM, that is, authentication methods allowed for each type of VIM. The second graphic element corresponds to authentication schemes pre-registered in the user interface providing apparatus, that is, the authentication schemes allowed in the first type of VIM selected by the user among all the pre-registered authentication schemes, that is, the first type of VIM. May include unique authentication schemes.

For example, the pre-registered authentication schemes may include a username and password-based authentication scheme, a bearer token-based authentication scheme, and a secure sockets layer (SSL) -based authentication scheme. The authentication schemes allowed in the VIM may correspond to some of the pre-registered authentication schemes. The pre-registered authentication methods do not necessarily include one authentication method, and two or more authentication methods may be used in combination. For example, a username and password based authentication scheme and an SSL based authentication scheme may be used in combination.

The authentication method will be further described with reference to FIG. 3. 3 is a diagram illustrating a database according to an exemplary embodiment. The user interface providing apparatus may use the database 300. The database 300 may exist inside or outside the user interface providing apparatus. When the database 300 exists outside the user interface providing apparatus, the user interface providing apparatus connects to the database 300 through a network to access the database 300. ), Necessary information can be obtained.

The database 300 is configured with authentication schemes A1, A2, A3, A4, ... mapped to each of the available VIMs V1, V2, ..., and the available VIMs V1, V2, .... .) For example, the authentication methods A1 and A2 may be mapped and stored in the VIM V1, and the authentication methods A3 and A3 may be mapped and stored in the VIM V2. The authentication methods A1, A2, A3, A4, ... are extracted from the pre-registered authentication methods 310, or at least some of the respective components of the pre-registered authentication methods 310 are combined. It may be.

In operation 210 of FIG. 2, the user interface providing apparatus may access the database 300 and configure the first graphic element based on the database 300. More specifically, the apparatus for providing a user interface may configure the first graphic element using the available VIMs V1, V2,...

The available VIMs (V1, V2, ...) may be updated periodically or aperiodically. That is, available VIMs (V1, V2, ...) may be updated when additional VIM types occur according to future development.

The user interface providing apparatus accesses the database 300 and displays the authentication schemes A1, A2,... Mapped to the selected first type VIM V1 to display the second graphical element in step 231 of FIG. 2. ..) and construct a second graphical element based on the extracted authentication schemes A1, A2, ....

Referring back to FIG. 2, in operation 232, the apparatus for providing a user interface receives a second user input I2 from a user. The second user input I2 may be for the second graphical element, selecting a first authentication scheme corresponding to any one of the authentication schemes indicated through step 231. For example, the second graphical element may represent the authentication schemes allowed in the first type of VIM selected in a list format, and the second user input I2 may correspond to an input that clicks or touches any authentication scheme in the list. This may be the case.

In operation 233, the apparatus for providing a user interface determines whether the user input I 2 corresponds to the authentication method identifier A 1. For example, the authentication scheme identifier A1 may correspond to a username and password based authentication scheme. For convenience of description, the authentication method identifier A1 may be referred to as a first authentication method. If the user input I2 corresponds to the authentication method identifier A1, step 234 is performed. If the user input I1 does not correspond to the authentication method identifier A1, step 235 may be performed. .

In operation 234, the apparatus for providing a user interface may provide an NFV environment according to the registration information V1 and A1 to the NFV server based on the registration information V1 and A1. The registration information V1 and A1 may indicate the VIM type corresponding to the VIM type identifier V1 to which the authentication method corresponding to the authentication method identifier A1 is applied. In other words, when the authentication method identifier A1 indicates the first authentication method and the VIM type identifier V1 indicates the VIM of the first type, the apparatus for providing a user interface is assigned to the VIM of the first type to which the first authentication method is applied. Based on this, the NFV server can be provided to the NFV server.

In operation 235, the apparatus for providing a user interface determines whether the user input I 2 corresponds to the authentication method identifier A 2. For example, the authentication scheme identifier A2 may correspond to a bearer token based authentication scheme. For convenience of description, the authentication scheme identifier A2 may be referred to as a second authentication scheme. If the user input I2 corresponds to the authentication scheme identifier A2, step 236 may be performed.

In operation 236, the apparatus for providing a user interface may provide an NFV environment according to the registration information V1 and A2 to the NFV server based on the registration information V1 and A2. In other words, when the authentication method identifier A2 indicates the second authentication method and the VIM type identifier V1 indicates the VIM of the first type, the user interface providing apparatus is assigned to the VIM of the first type to which the second authentication method is applied. Based on this, the NFV server can be provided to the NFV server.

If it is determined in step 235 that the user input I2 does not correspond to the authentication method identifier A2, the apparatus for providing a user interface continuously performs the determination on the authentication method identifier as in steps 233 and 235. can do.

As described above, step 240 may be performed if the user input I1 does not correspond to the VIM type identifier V1. In operation 240, the user interface providing apparatus determines whether the user input I1 corresponds to the VIM type identifier V2. For example, the VIM type identifier V2 may correspond to a VIM of Kubernetes type. If the user input I1 corresponds to the VIM type identifier V2, step 241 may be performed.

In operations 241 through 246, an operation corresponding to operations 231 through 236 may be performed. The authentication schemes included in the second graphical element provided with respect to the first type of VIM and the authentication schemes included in the third graphical element provided with respect to the second type of VIM different from the first type may be different. As a result, an NFV environment according to registration information V2 and A3 may be provided in step 244, and an NFV environment according to registration information V2 and A4 may be provided in step 246.

If it is determined in step 240 that the user input I1 does not correspond to the VIM type identifier A2, the apparatus for providing a user interface continues to determine the VIM type identifier as in steps 230 and 240. can do.

4 illustrates a user interface according to an exemplary embodiment.

Referring to FIG. 4, the selection window 410 is for inputting a VIM type and may include a plurality of types of VIMs. The selection window 410 may correspond to the first graphical element described above. When the small arrow in the selection window 410 is selected, a plurality of types of VIMs may appear in a list form, and the user may select any one of them.

The input window 420 is for inputting the name of the VIM, and the input window 430 is for inputting a detailed description of the VIM. The input window 440 is for inputting an authentication uniform resource locator (URL).

The selection window 450 is for inputting an authentication method, and may include authentication methods allowed by the VIM type selected through the selection window 410. The selection window 450 may correspond to the second graphical element described above. When a small arrow in the selection window 450 is selected, the authentication methods allowed in the selected VIM type through the selection window 410 may appear in a list form, and the user may select any one of them.

The input window 460 is for inputting a user name, and the input window 470 is for inputting a password. An input window 480 is for inputting a project name, and an input window 490 is for inputting an SSL Secure Sockets Layer Certificate Authority (CA) certificate.

Whether the input windows 460, 470, 490 are activated may be changed depending on which input method is selected in the input window 450. For example, when using the user name and password in the input window 450 and using the SSL authentication method are selected, the input windows 460, 470, 490 may be activated. Alternatively, when the bearer token method is selected in the input window 450, an input window corresponding to the bearer token method may be activated. An asterisk next to each item may indicate a required entry.

5 is a diagram illustrating an NFV architecture according to an embodiment.

The Network Functional Virtualization (NFV) architecture includes 1) a software implementation version of the network function, Virtual Network Function (VNF), 2) an NFV Infrastructure (NFVI) that includes the hardware and software components on which the VNF is deployed, and 3) an NFV Orchestrator. ), Including VNF Manager (VNFM) and Virtualized Infrastructure Manager (VIM), and NFV Management and Orchestration (MANO) to organize and manage NFVI resources and the life cycle of VNF.

The NFV architecture can be largely divided into functional blocks and reference points. First, the functional blocks include VNF, EM, NFVI, VIM, NFVO, VNFM, Service, VNF and Infrastructure Description, and OSS / BSS, and the reference points are VI-ha, Vn-Nf, Or-Vnfm, Vi-Vnfm, Or -Vi, Nf-Vi, Os-Ma and Ve-Vnfm.

Element Management (EM) is an entity that has a VNF related configuration and monitoring function and has a log of it. EM detects, detects, and secures VNFs, measures performance, and configures them. OSS / BSS means the service operation and business support system of network operators.

NFVI refers to all physical and logical elements for the management and execution of the VNF from the time the VNF is deployed. In other words, it refers to an entity that provides resources through the virtualization stage with physical elements. From the VNF point of view, virtualized resources are eventually used, so there is no need to separate physical and logical elements.

There are two main components of NFVI. The first is hardware resources. In other words, it refers to actual physical resources that VNF will use through the virtualization layer. The second is the virtualization layer. It is responsible for abstracting physical resources through the virtualization layer so that the resources can be used flexibly.

VIM refers to the part that manages and controls the physical resources used by the VNF, such as computing, storage, and network. It is responsible for deploying and managing virtualized resources based on physical resources. The VIM also provides management functions through visualization of NFVI and NFVI error monitoring and management by collecting defect information and resource status from NFVI.

VNFM performs management and control functions for VNF lifecycle management and interoperability between VNFs. NFVO has an orchestration function for resources and services. NFVO manages the collection of VNF-related resource usage information on the resource side and manages the lifecycle and automation on the service side.

The NFV reference point is the interface between the components described above and consists of eight interfaces. Vi-Ha is an interface used between the virtualization layer and hardware resources to provide resources for the VNF, and to collect status information about hardware. Vn-Nf is an interface used between VNF and NFVI, which is used by NFVI to provide resources to VNF. Or-Vnfm is the interface between NFVO and VNF Manager. It is used when VNFM makes a resource related request (user authentication, validity, reservation, allocation) to NFVO, or when NFVO sends configuration information to VNFM. It is also used to collect VNF information for network service lifecycle management.

Vi-Vnfm is an interface used between VIM and VNFM. It is used when VNFM requests resource allocation from VIM or sets up virtualized hardware resources and exchanges status information. OR-Vi is an interface used when NFVO makes a reservation for a resource or requests allocation of a resource to VIM. This interface is also used to exchange virtualized hardware resource configuration and status information. Nf-Vi is an interface defined in the connection between VIM and NFVI. It is used when responding to resource allocation request, transferring resource status information, or setting hardware resource.

Ve-Vnfm is an interface defined between VNF / EM and VNFM. It is used when a request related to VNF lifecycle management is required, configuration and event related information is communicated, or status information is exchanged for network service lifecycle management. do. Os-Ma is an interface defined between OSS / BSS and NFVO. Requests related to network service lifecycle management or requests related to VNF lifecycle management, communication of status information related to NFV, management policy delivery, data analysis exchange, and related to NFV. Used to transfer billing and usage records, exchange information about NFVI functions, and inventory.

6 illustrates an apparatus for providing a user interface according to an exemplary embodiment.

Referring to FIG. 6, the apparatus 600 for providing a user interface for building a VIM may include a processor 610, a memory 620, and a database 630.

The memory 620 may include instructions that can be read by the processor. When instructions stored in the memory 620 are executed in the processor 610, the processor 610 displays a first graphic element including a plurality of types of VIMs for establishing an NFV environment, and among the plurality of types of VIMs. Receive a first user input for the first graphical element, selecting a first type of VIM that corresponds to any one, and display a second graphical element that includes the authentication schemes allowed in the selected first type of VIM, Receive a second user input for a second graphical element that selects a first authentication scheme corresponding to any of the indicated authentication schemes, and NFV to the NFV server based on the first type of VIM to which the first authentication scheme is applied. It can provide an environment. The database 630 may correspond to the database 300 described with reference to FIG. 3. In addition, the above description may be applied to the user interface providing apparatus 600.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the devices and components described in the embodiments are, for example, processors, controllers, Arithmetic Logic Units (ALUs), digital signal processors, microcomputers, field programmable gate arrays (FPGAs). Can be implemented using one or more general purpose or special purpose computers, such as a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of the software. For convenience of explanation, one processing device may be described as being used, but one of ordinary skill in the art will appreciate that the processing device includes a plurality of processing elements and / or a plurality of types of processing elements. It can be seen that it may include. For example, the processing device may include a plurality of processors or one processor and one controller. In addition, other processing configurations are possible, such as parallel processors.

The software may include a computer program, code, instructions, or a combination of one or more of the above, and configure the processing device to operate as desired, or process it independently or collectively. You can command the device. Software and / or data may be any type of machine, component, physical device, virtual equipment, computer storage medium or device in order to be interpreted by or to provide instructions or data to the processing device. Or may be permanently or temporarily embodied in a signal wave to be transmitted. The software may be distributed over networked computer systems so that they may be stored or executed in a distributed manner. Software and data may be stored on one or more computer readable recording media.

The method according to the embodiment may be embodied in the form of program instructions that can be executed by various computer means and recorded in a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Magneto-optical media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also 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 as one or more software modules to perform the operations of the embodiments, and vice versa.

Although the embodiments have been described by the limited embodiments and the drawings as described above, various modifications and variations are possible to those skilled in the art from the above description. For example, the described techniques may be performed in a different order than the described method, and / or components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different form than the described method, or other components. Or even if replaced or substituted by equivalents, an appropriate result can be achieved.

Therefore, other implementations, other embodiments, and equivalents to the claims are within the scope of the claims which follow.

Claims (10)

In the operation method of the user interface providing apparatus for building the VIM (Virtual Infrastructure Management)
Displaying a first graphical element comprising a plurality of types of VIMs for establishing a Network Function Virtualization (NFV) environment;
Receiving a first user input for the first graphical element selecting a first type of VIM corresponding to any one of the plurality of types of VIMs;
Displaying a second graphical element comprising authentication schemes allowed in the selected first type of VIM;
Receiving a second user input for the second graphical element selecting a first authentication scheme corresponding to any of the displayed authentication schemes; And
Providing the NFV environment to an NFV server based on the first type of VIM to which the first authentication method is applied
Method of operating a user interface providing apparatus comprising a. The method of claim 1,
The plurality of types of VIMs include an OpenStack type VIM, a Kubernetes type VIM, and a VMware type VIM.
A method of operating a user interface providing device. The method of claim 1,
Pre-registered authentication methods include a username and password based authentication method, a bearer token based authentication method, and a Secure Sockets Layer authentication (SSL) based authentication method, and are allowed in the selected first type of VIM. The authentication schemes that correspond to some of the pre-registered authentication schemes,
A method of operating a user interface providing device. The method of claim 1,
Each of the plurality of types of VIMs has unique authentication schemes according to the characteristics of each of the plurality of types of VIMs,
Wherein the second graphical element comprises unique authentication schemes corresponding to the first type of VIM;
A method of operating a user interface providing device. The method of claim 1,
The authentication schemes included in the second graphical element provided with respect to the first type of VIM and the authentication schemes included in a third graphical element provided with respect to a second type of VIM different from the first type are different,
A method of operating a user interface providing device. The method of claim 1,
Displaying the first graphical element may
Accessing a stored database of available VIMs; And
Constructing the first graphical element based on the database
Including,
The available VIMs are updated periodically or aperiodically,
A method of operating a user interface providing device. The method of claim 6,
The database further stores authentication schemes mapped to each of the available VIMs,
Displaying the second graphical element may
Accessing the database to extract authentication schemes mapped to the selected first type of VIM; And
Configuring the second graphical element based on the extracted authentication schemes
Operating method of the user interface providing apparatus comprising a. In the apparatus for providing a user interface for building a virtual infrastructure management (VIM),
A processor; And
A memory containing instructions readable by the processor
Including,
When the instruction is executed on the processor, the processor
Display a first graphical element comprising a plurality of types of VIMs for establishing a Network Function Virtualization (NFV) environment,
Receive a first user input for the first graphical element, selecting a first type of VIM corresponding to any one of the plurality of types of VIMs,
Indicate a second graphical element comprising authentication schemes allowed in the selected first type of VIM,
Receive a second user input for the second graphical element, selecting a first authentication scheme corresponding to any of the displayed authentication schemes,
Providing the NFV environment to an NFV server based on the first type of VIM to which the first authentication scheme is applied,
User interface provision device. The method of claim 8,
The processor is
Available VIMs access a stored database, construct the first graphical element based on the database,
The available VIMs are updated periodically or aperiodically,
User interface provision device. The method of claim 9,
The database further stores authentication schemes mapped to each of the available VIMs,
The processor accessing the database to extract authentication schemes mapped to the selected first type of VIM and to configure the second graphical element based on the extracted authentication schemes;
User interface provision device.

Images