KR101996029B1 - Method for designing network service descriptor in network function virtualization system, managing the network function descriptor and system thereof - Google Patents

Abstract

An embodiment of the present invention discloses a method of designing a network service descriptor (NSD) and a method of managing a designed network service descriptor in a network function virtualization (NFV) system.

Description

TECHNICAL FIELD [0002] The present invention relates to a network function virtualization system, a method for designing a network service descriptor, a method for managing a network service descriptor, and a system for implementing the methods. thereof}

The present invention relates to a method for designing a network service descriptor in a network function virtualization system, a method for managing a network service descriptor, and a system for implementing the methods. More particularly, in a network function virtualization system, And more particularly, to a method for supporting efficient design of an information model of a service and a system for implementing the method.

Network Function Virtualization (NFV) is a component technology that is the basis of 5G mobile communication (5G mobile communication), and is under active research and development. In particular, IFA Working Group has promoted standardization of APIs and information models between internal and external components of the MANO architecture through the NFV Industry Specification Group (ETSI) of the European Telecommunications Standards Institute (ETSI). . The IFA 014 standard, which was included in the previous Release 2 release, defines the NS Descriptor (NSD) data model for defining the Network Service in the NFV MANO domain.

The network service descriptor basically includes information on PNF, VNF, and Nested NS, which constitute the network service, and a virtual link that defines the network between the basic elements and a service access point, which is a service connection point of the network service (NS) unit. The Deployment Flavor and the Virtual Network Function Forwarding Graph (VNFFG), which define distribution shapes of basic elements as profiles and define distribution options and slice networks according to various operating environments and situations through combination of the profiles, : Virtual Network Function Forwarding Graph) information model exists.

In other words, the NSD data model of the ETSI IFA 014 standard is designed to define a number of distribution shapes, out of the existing one. Through this, operators can define a number of distribution shapes according to various operating conditions and environments, and design a transition policy between each shape to provide a basis for automated control of actual operating environment changes.

Recently, the NFV system has increased the role of design stage and complexity of work for network automation. Design-time role for designing NSD which is design artifact and performing life cycle management itself, and real- Function as a run-time role that manages the system.

However, most of the Opensoruce Projects (OSM, Open Baton, ONAP, etc.) focus mainly on the research and development of run-time functions to realize actual NFV operation. The solution is not doing much. Especially, in the case of the Open Baton and the OSM corresponding to the NFVO (NFV Ochestrator), there is no function for the flavor information model, and there is an inconvenience that the NSD should be created through the text editing.

1. Korean Patent Publication No. 10-2018-0080791 (published on July 13, 2018) 2. Korean Patent Publication No. 10-2018-0085187 (published on July 26, 2018) 3. Korean Patent Publication No. 10-2018-0084430 (published on July 25, 2018) 4. Korean Patent Publication No. 10-2018-0081965 (published on July 18, 2018)

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and it is an object of the present invention to provide an ETSI GS NFV-IFA014 standard, in which a distribution form of a network service is represented in a single model and an operation policy is defined according to each distribution form, Friendly GUI-based NSD design methodology and a system for implementing the method in order to avoid the existing design method that causes various user errors.

According to an aspect of the present invention, there is provided a method for configuring a micro-service architecture (MSA) through a Network Function Virtualization (NFV) system and an API service, A method for designing a network service descriptor (NSD), comprising: receiving a basic component of a network service from a user terminal and arranging the received basic component in a basic element output space; If an input to a predetermined relationship diagram is subsequently received after an input to any one of the arranged basic elements is received via the user terminal, Basic element copying batching step; A element tree output step of converting a connection relationship between the arranged basic elements into a tree structure and outputting the tree structure to the tree output space when at least two basic elements are arranged in the relation output space; An input value receiving step of receiving a property value for each elementary element located in the relation space output space from the user terminal to form a flavor; And a graph defining step of defining a virtual network function forwarding graph (VNFFG) as a result of combining at least two flavors.

According to another aspect of the present invention, there is provided a system for designing a network service descriptor (NSD), the system including a basic component of a network service from a user terminal An element placement unit that receives the basic elements and places the received basic elements in a basic element output space; If an input to a predetermined relationship diagram is subsequently received after an input to any one of the arranged basic elements is received via the user terminal, A basic element copy arrangement part; A element tree output unit for converting a connection relation between the arranged basic elements into a tree structure and outputting the tree structure to the tree output space when at least two basic elements are arranged in the relation output space; An input value receiver for receiving a characteristic value of each basic element located in the relation space output space from the user terminal and configuring a flavor; And a graph defining step of defining a virtual network function forwarding graph (VNFFG) based on a result of combining at least two flavors.

An embodiment of the present invention can provide a computer-readable recording medium storing a program for implementing the method.

The design management system according to the present invention is an independent web application program. It can edit the network service in a third environment other than the NFV MANO environment, download the design results according to the standard specification in a file form, and freely utilize the OSS or NFVO have.

In addition, the design system according to the present invention can be integrated into a commercial or open source NFVO when designing a network service operating in one NFV domain, and can be utilized for editing and designing an NSD data model of the system have.

The present invention can be integrated in a simple manner through mapping between the standard model and the model of the target system. Through this, according to the methodology proposed in the present invention, it is possible to define multiple distribution shapes and transition policies for a network service through a GUI-based editing tool and to operate as a solution to a design-time function.

1 is a block diagram of an example of a network functional virtualization system in which the present invention is implemented.
2 is a schematic diagram of an overall system in which a system according to the present invention is implemented.
3 is a diagrammatic representation of a block diagram of an example of an NSD design management system 300 in accordance with the present invention.
4 is a diagram schematically illustrating an example of an NSD design screen output to the user terminal by the first system.
FIG. 5 is a view showing an example of the NSD design screen illustrated in FIG.
6 is an example of a screen for designing an NSD using a text editor.
FIG. 7 is a diagram schematically illustrating an NSD designed through the NSD design screen shown in FIG. 5 and serving as an API to another system (client or NFVO) and related interworking standards.
8 is a diagram for explaining a method of managing an NSD designed according to the present invention.
Figure 9 is a diagrammatic representation of a flow diagram of an example of a method for designing a network service descriptor in accordance with the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The present invention is capable of various modifications and various embodiments, and specific embodiments are illustrated in the drawings and described in detail in the detailed description. The effects and features of the present invention and methods of achieving them will be apparent with reference to the embodiments described in detail below with reference to the drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings, wherein like reference numerals refer to like or corresponding components throughout the drawings, and a duplicate description thereof will be omitted .

In the following embodiments, the terms first, second, and the like are used for the purpose of distinguishing one element from another element, not the limitative meaning.

In the following examples, the singular forms "a", "an" and "the" include plural referents unless the context clearly dictates otherwise.

In the following embodiments, terms such as inclusive or possessed mean that a feature or element described in the specification is present, and does not exclude the possibility that one or more other features or components are added in advance.

If certain embodiments are otherwise feasible, the particular process sequence may be performed differently from the sequence described. For example, two processes that are described in succession may be performed substantially concurrently, and may be performed in the reverse order of the order described.

1 is a block diagram of an example of a network functional virtualization system in which the present invention is implemented.

Referring to FIG. 1, a network functional virtualization system 10 in which the present invention is implemented includes a VNF 110, an NFVI 130, and a MANO 150.

A VNF (Virtual Network Function) 110 is a module for performing network equipment functions, and includes L4, Security, and the like.

The Network Function Virtualization Infrastructure (NFVI) 130 is a network function virtualization infrastructure, which is composed of a Kernel-based Virtual Machine (KVM) 131 and a Hardware Resource 133, which are hypervisors.

Management and Orchestration (MANO) manages network functions. The management and orchestration (MANO) 151 includes an NFVO (NFVO Orchestrator) 151 for managing the VNFM 153 of many devices at the service level, a VNFM (VNF Manager) 153 for managing the VNF, And a Virtual Infra Manager (VIM) 155, which is a virtual support manager.

The network function virtualization system 10, which is an object on which the present invention is implemented, performs the same functions as the network function virtualization system 10 known in the art, so that the functions performed by the respective modules are considered to follow a known method.

2 is a schematic diagram of an overall system in which a system according to the present invention is implemented.

2, the overall system including the network functional virtualization system 10 includes a model-driven data store 200, an OSS 230, NFVOs 250, an NSD Artifact Repository 270, , And an NSD design management system (300).

First, the model-driven data store 200 defines the network service in various forms in the NFV environment through the ETSI NFV-IFA014 standard, and designs the transfer policy between each shape in advance, thereby enabling automated network control Which includes the network function virtualization system 10 and the API Service Module 210 described in FIG.

The network function virtualization system 10 is a system including all the modules necessary for implementing the network equipment as software as described in FIG. Although not shown in FIG. 2, the network functional virtualization system 10 may include version management of installed software, lifecycle management, connection management between modules, subscription management, notification management, and the like.

The API Service Module 210 functions to allow the network function virtualization system 10 to integrate network control with the OSS 230 and NFVOs 250.

The OSS 230 and the NFVOs 250 configure a REST API (REpresentational State Transfer API) through the API Service Module 210 to convert a command for a resource defined as an HTTP URI of the network function virtualization system 10 into an HTTP Method define. At this time, the contents of resources defined by the OSS 230 and the NFVOs 250 can be defined in various expression languages such as json, xml, yaml, and the like.

The NSD Artifact Repository 270 performs a storage function for storing a network service descriptor designed according to the present invention.

The NSD design management system 300 includes a first system 301 for designing and managing a network service descriptor (NSD) and designing an NSD and a second system 302 for managing the designed NSD . The first system 301 and the second system 302 can design and manage the NSD in the network function virtualization system 10 by configuring the REST API through the API Service Module 210. [ That is, the NSD design management system 300 can operate through the network functional virtualization system 10 and the method of constructing the MSA (MicroService Architecture) through the API service.

The first system 301 and the second system 302 may be physical devices and may be implemented as a logical device in the form of a web application, depending on the embodiment. When the first system 301 and the second system 302 are implemented in the form of a web application, a web application that performs the functions of the first system 301 and the second system 302 is installed, It is obvious that the hardware device to be driven is included in the scope of the present invention.

3 is a diagrammatic representation of a block diagram of an example of an NSD design management system 300 in accordance with the present invention.

Referring to FIG. 3, it can be seen that the NSD design management system 300 according to the present invention includes a first system 301 and a second system 302. The NSD design management system 300 according to the present invention may be implemented as a web application, and may be implemented as a logical device or system that controls a screen output to a user terminal according to a user's input. The user can design and manage the NSD using the NSD design management system 300 through the address of the NSD design management system installed in the user terminal or the address of the NSD design management system accessible to the web browser installed in the user terminal .

In the following, "basic element" is regarded as a basic component constituting a network service unless otherwise specified.

The first system 301 is a WYSIWYG type design tool that performs the function of designing the NSD. The first system 301 includes an element placement unit 310, a basic element copy placement unit 330, a element tree output unit 350, An input value receiving unit 370 and a graph defining unit 390.

The element arrangement unit 310 receives a basic element of the network service from the user terminal and arranges the basic element in the basic element output space. The basic element is a unit for configuring the network service and means VNF, PNF, Nested NS, etc. When outputting to the screen through the user terminal, the basic element is outputted in stencil form and can be freely moved according to the input of the user And can be implemented in a form that can be copied.

The basic elements include SAP, Virtual Link as the common elements by default. The basic element output space is a space for collecting the basic elements of the network service. When outputting through the screen of the user terminal, the basic element output space is output as a fixed size area including a plurality of stencil basic elements. In addition, the basic element output space will be described later with reference to FIG.

The basic element copy placement unit 330 may be configured such that when an input to one of the basic elements arranged in the basic element output space is received through the user terminal and an input to a predetermined relationship output space is subsequently received, Relational diagrams copy and place the basic elements in the output space. The user can input an input to any one of the basic elements arranged in the basic element output space through the input device (hard button input or touch screen input) of the user terminal so as to transfer the relationship to the output space, , The underlying element that is placed is the copy of the base element placed in the base element output space so that the base element defined in the base element output space is not deleted or modified . The user can move the basic elements arranged in the basic element arrangement space to the relation degree output space by applying a specific input through the user terminal, and since a plurality of basic elements are arranged in the relation output degree space, A correlation diagram is formed.

The relationship diagram output space is a space (area) in which a distribution shape of a flavor, which is a unit constituting a network service descriptor designed by the present invention, can be designed in advance, and an output space can be corresponded to each flavor have. The flavor will be described later together with the input value receiving unit 370. [

According to the present invention, the user can design the network service descriptor by arranging the basic elements arranged in the basic element output space in the relation diagram output space and establishing the connection relationship, so that the network service descriptor Not only does it provide greater convenience than when designing descriptors, but it also increases the efficiency of design work, preventing various user errors that may be included in a designed network service.

The element tree output unit 350 transforms the connection relationship between the arranged basic elements into a tree structure and outputs the tree structure to the tree output space when at least two basic elements are arranged in the relation output view space.

When at least two basic elements are arranged in the relation diagram output space by the basic element copy arrangement unit 330 and the connection between the basic elements is established, the element tree output unit 350 outputs, based on the established connection And transforms the connection relationship between basic elements into a tree structure. For example, if each elementary element is arranged such that the elementary element 2 and the elementary element 3 are connected to the elementary element 1 and the elementary element 4 is connected to the elementary element 2, the elementary tree output unit 350 outputs The relationship between the basic element and the basic elements placed in the output space is detected, and the basic element 1 is used as a base, the basic element 2 and the basic element 3 are used as a branch, A lower branch of the element 2 is generated, and the tree structure is arranged so as to be output to the tree output space.

In the case where the number of basic elements is increased and the connection relation between the basic element and the basic element is complicated, it is difficult for the user to grasp the network service intuitively only by the connection relationship between the basic elements existing in the output space , It can function as a means for assisting it, and the effect of allowing the user to intuitively grasp the hierarchical structure between basic elements according to the characteristics of the tree structure can be expected.

In an alternative embodiment, the tree output space may be configured not only to output the connection relationships between basic elements moved from the basic element arrangement space to the relation output space in the form of a tree, All the elements constituting the function forwarding graph (VNFFG) may be represented by a tree structure.

The input value receiving unit 370 receives property values of the respective basic elements located in the relationship diagram output space from the user terminal and constitutes a deployment flavor (hereinafter, "flavor"). A flavor is a unit for configuring a network service descriptor, and can be defined as a unit or a module capable of independently performing a specific function. Relationships The basic elements that are placed in the output space are input into the property values, and when the wiring is completed between the basic elements, the shape of the relationship relationship between the basic elements of the output space corresponds to the output space It becomes a distribution shape of the flavor and can be combined with other flavors according to the units.

The user can input and update the characteristic information of the basic element by inputting to the user terminal. More specifically, when the user inputs specific information through the user terminal, the input value receiving unit 370 controls the input value input by the user to be reflected in the characteristic value of the basic element.

As an example in which the input value input by the user is reflected in the property value of the basic element, information on the flavor and instance generation level for VNF, PNF, Nested NS, bandwidth for virtual link, Network configuration such as time delay, IPv4 GW, DHCP, subnet information, and network interface information for SAP.

The property value of the basic element can be defined as the attribute information or requirement of the basic element selected by the user terminal. A plurality of instance creation levels can be defined for each flavor, and a graph defining unit 390 described later defines distribution shapes through profile mapping of elementary elements corresponding to each instantiation level do.

The graph defining unit 390 defines a Virtual Network Function Forwarding Graph (VNFFG) based on the property value and the setting value received by the input value receiving unit 370. The graph defining unit 390 defines VNFFG by a method of selecting information to be included in individual slices in the output space and grouping them in correspondence with each flavor of basic elements, and defines a VNFFG defined by the graph defining unit 390 Function as an NSD (network service descriptor) representing the network service. More specifically, the VNFFG defined by the graph defining unit 390 means an object obtained by hierarchically accumulating distributions of the flavors of the plurality of relations existing in the output space and grouping them. That is, VNFFG can be defined based on a result of combining at least two flavors.

In an alternative embodiment, the graph defining unit 390 may further define a context-based transfer policy for VNFFG. The graph defining unit 390 can define, based on the information received from the user terminal or the function information previously set for each flavor, from the viewpoint of what network service the defined VNFFG is intended to use. Transition policies defined in addition to VNFFG include flavors and instantiation levels that meet the conditions of VNFFG.

A further description of the NSD design functions performed by the first system 301 described above will be described below with reference to FIG. 4 for efficient illustration.

The second system 302 may then be physically or logically connected to the first system 301 to provide a network functional virtualization system (" virtualization ") for integrated management of design outcomes (NSD) 10) to perform a life cycle management function according to a predetermined standard. As an example of the predetermined standard, there is IFA 013, but it is obvious that the second system 302 can perform the management function according to other standard specifications according to the embodiment.

As an alternative embodiment, the second system 302 may detect whether the network service descriptor according to VNFFG defined in the graph defining unit 390 of the first system 301 is changed by the NFVO in the interworking state When the lifecycle is changed, the lifecycle may be notified to the user terminal in response to the registration information before the network service according to the network service descriptor is on-boarded.

A further description of the NSD management functions performed by the second system 302 described above will be described below with reference to FIG. 8 for an efficient description.

As an optional embodiment, the NSD design management system 300 including the first system 301 and the second system 302 may be a system having a WEB-WAS-DB structure. Since the NSD design management system 300 is a system having a WEB-WAS-DB structure, it includes a function of a Web server that provides static data common to all user terminals connected to the NSD design management system 300 (WAS) function for reading out various system languages (development languages) constituting the task command, as well as an operation for performing a specific logic among the requests of the user terminal and returning the result value. In this process, the WAS accesses the database server (DB server) using SQL (Structured Query Language) when necessary. The WAS transmits the result of the logic to the data requested by the user terminal to the user terminal do.

That is, by configuring the NSD design management system 300 as a 3-tier architecture, a more improved result value can be provided for the request of the user terminal. The NSD designed by the first system 301 may be stored in the WAS-DB to provide a version control function to perform change tracking or version management on the design itself. The feature of life cycle management of the NSD through the present invention distinguished from the prior art is that the state management can be performed for an unfinished network service which is only a design stage and has not yet been on-boarded. In order to effectively manage the state of the NSD, the state of the NSD before being on-boarded from the operations support system (OSS) 230 should be defined variously and efficiently, and this will be described later with reference to FIG.

4 is a diagram schematically illustrating an example of an NSD design screen output to the user terminal by the first system.

4, the NSD design screen 400 output to the user terminal includes a basic element output space 410, a relation diagram output space 430, a tree output space 450, and a characteristic information display space 470 . FIG. 4 is a screen implemented by the first system 301, which will be described below with reference to FIG. 3, and a description overlapping with that described in FIG. 3 will be omitted.

First, at least two basic elements are arranged and output in the basic element output space 410. The basic elements can be arranged and output in the basic element output space 410 in a stencil form. In the basic element output space 410 shown in FIG. 4, only six basic elements are arranged, The number of elementary elements placed in the elementary element output space 410 may be smaller or larger than six, as the present invention does not limit the number of elementary elements to a specific number.

The relationship diagram output space 430 includes basic elements generated when the basic elements arranged in the basic element output space 410 are copied and arranged in the relation diagram output space 430 according to a specific input inputted to the user terminal Outputs the connection relationship between basic elements. Here, it is obvious that the specific input inputted to the user terminal is information corresponding to the relation diagram output space 430 among the information received by the input value receiver 370 described above. The elementary elements arranged in the relationship diagram output space 430 constitute a node, and their characteristics can be determined according to characteristic values input from the user terminal. The characteristic values of the elementary elements arranged in the relationship diagram output space 430 can be effectively stored in correspondence with the elementary elements only when they are input in the blank space of the characteristic information display space 470 described later. Relational diagram of FIG. 4 The output space 430 is a relation to the flavor 1, and the output space 430 is one of the relationship output view 430, one for each flavor.

The tree output space 450 is a tree structure in which at least two basic elements are arranged in the relation diagram output space 430 and the relationship between the basic elements inevitably generated when the basic elements are connected is established as a tree structure As a space for outputting, it has been already described that the user can intuitively grasp the potential error of the designed network service by referring to the tree structure output to the tree output space 450. Referring to FIG. 4, for example, the tree output space 450 may include VNF-A and VNF as sub-base elements of a basic element called NF, based on the connection relationship between basic elements disposed in the relationship diagram output space 430 -B is defined, and outputs it.

The characteristic information display space 470 is a space into which the received information is inputted to the input value receiver 370. After the characteristic information of the basic element is inputted through the characteristic information display space 470 and stored, By re-inputting the basic element, the user can visually confirm the characteristic information stored corresponding to each elementary element, and modify it as necessary. In the characteristic information display space 470, the same function is performed not only for the characteristic value of the basic element but also for a setting value (for example, a transition policy for each network situation) of the connection relation between the basic element and the basic element.

FIG. 5 is a view showing an example of the NSD design screen illustrated in FIG.

5 more specifically discloses the basic element output space 410, the relation diagram output space 430, the tree output space 450, and the characteristic information display space 470 described with reference to FIG.

5, characteristic values of basic elements input through the characteristic information display space and set values of connection relations between basic elements are reflected in the relationship diagram output space and reflected in various values (6 to 21) . The user can design the network service descriptor while intuitively understanding the relationship diagram outputted through the output space as a supplementary index to the tree output in the tree output space, thereby increasing the efficiency of the design, It is possible to quickly detect possible information.

6 is an example of a screen for designing an NSD using a text editor.

As shown in FIG. 6, when designing a network service descriptor using a text editor, intuitive analysis is difficult. Therefore, it is not possible to quickly detect information that may cause an error in the process of designing an NSD. However, As the NSD design screen can be implemented as shown in FIG. 5, the efficiency of the user's NSD design work can be maximized.

FIG. 7 is a diagram schematically illustrating an NSD designed through the NSD design screen shown in FIG. 5 and serving as an API to another system (client or NFVO) and related interworking standards.

Referring to FIG. 7, although the NSD designed by the present invention can be implemented as text similar to the conventional NSD, a graphical user interface (GUI) -based design Tool that you can use.

8 is a diagram for explaining a method of managing an NSD designed according to the present invention.

FIG. 8 can be implemented by the second system 302 of the NSD design management system 300 according to FIG. 3, and will be described with reference to FIG. 3. Hereinafter, It will be omitted.

Once the NSD is designed by the first system 301, the second system 302 manages the life cycle of the designed NSD. According to the present invention, it is possible to perform state management for an unfinished work (NSD) at the design stage, and to define and manage at least two states of the NSD before on-boarding from the OSS perspective have.

The second system 302 defines the Working 810 as the first state and considers the Working 810 to be a temporary storage state in which the design of the network service according to the designed NSD is in progress.

The second system 302 defines under review 830 as the second state and validates the validity of the network service according to the NSD according to the standard model by performing under review 830 It can be regarded as a state in which

The second system 302 defines the Confirmed 850 as the third state and can regard the Confirmed 850 as a state just before being verified for the network service according to the designed NSD to be on-board the NFVO have.

The second system 302 may define a Deployed 870 as a fourth state and may regard Deployed 870 as being on-boarded to the NFVO according to the designed NSD.

The second system 302 may define Archived 890 as a fifth state and may regard Archived 890 as a state of keeping network services according to the NSD designed in the first system 301 for maintenance have.

If the second system 302 is edited during the course of designing the network service, is determined to be invalid in the under review 830, or updated in the Confirmed 850, the second system 302 determines the lifecycle of the designed NSD Is regarded as a working (810) and managed.

After the design of the network service according to the designed NSD is completed, the second system 302 regards the life cycle of the designed NSD as under review (830) and manages it.

The second system 302 may verify that the network service according to the designed NSD has been completed or that the network service according to the designed NSD has been on-boarded and dropped on the NFVO, When unarchive, the life cycle of the designed NSD is regarded as Confirmed (850) and managed.

The second system 302 regards the designed life cycle of the NSD as Deployed 870 if the network service according to the designed NSD is not dropped within a preset time after on-boarding the NFVO do.

If the second system 302 has been verified for the network service according to the designed NSD and is maintained on the NFVO before being on-boarded, maintenance of the network service according to the NSD is required and is not on-board the NFVO , And manages the designed NSD life cycle as Archived (890).

As described above, the second system 302 can define and manage the life cycle before and after the designed NSD is on-boarded to the NFVO after the NSD is designed by the first system 301, When the cycle is changed to a state different from the existing state, the fact that the cycle has changed is notified to the user terminal so that the user can recognize the fact that the life cycle of the designed NSD is changed.

Figure 9 is a diagrammatic representation of a flow diagram of an example of a method for designing a network service descriptor in accordance with the present invention.

FIG. 9 can be implemented by the NSD design management system 300 according to FIG. 3, and will be described below with reference to FIG. 3, and a description overlapping with that described in FIG. 3 will be omitted.

First, the element arrangement unit 310 receives a basic element of the network service from the user terminal, receives the received basic element, and arranges the basic element in the basic element output space (S910). Although it is described in step S910 that the basic element is received from the user terminal, according to the embodiment, the predetermined basic element may be previously arranged in the elementary element output space even if not received from the user terminal, A basic element stored in a specific database by an input to a user terminal may be transferred to the first system 301 and placed in a basic element output space.

The basic element copy placement unit 330 arranges the input basic elements in such a manner as to copy the input basic elements to the relationship diagram output space (S920). More specifically, after the input to any one of the basic elements arranged in the basic element output space is received via the user terminal, the basic element copy placement unit 330 outputs the input to the preset relation degree output space successively Once received, the relationship is also copied and placed in the output space.

When at least two basic elements are arranged in the relation space output space 350, the element tree output unit 350 converts the connection relations between the arranged basic elements into a tree structure and outputs the tree structure to the tree output space (S930).

In operation S940, the input value receiving unit 370 receives the property values of the respective basic elements located in the relation diagram output space from the user terminal and the setting values for the connection relations between the basic elements.

The graph defining unit 390 defines a virtual network function forwarding graph VNFFG based on the property value and the setting value received in step S940 (S950). As an expansive embodiment of step S950, the designed NSD can be defined and managed by the second system 302 with at least two states, which has already been described in FIG.

The design management system according to the present invention is an independent web application program. It can edit the network service in a third environment other than the NFV MANO environment, download the design results according to the standard specification in a file form, and freely utilize the OSS or NFVO have.

In addition, the design system according to the present invention can be integrated into a commercial or open source NFVO when designing a network service operating in one NFV domain, and can be utilized for editing and designing an NSD data model of the system have.

The present invention can be integrated in a simple manner through mapping between the standard model and the model of the target system. Through this, according to the methodology proposed in the present invention, it is possible to define multiple distribution shapes and transition policies for a network service through a GUI-based editing tool and to operate as a solution to a design-time function.

The management system according to the present invention can be utilized for NSD design support according to the GUI tool and management tool of the present invention when designing and distributing an NSD in an OSS environment in which a plurality of NFVOs are integratedly managed, Management can perform the normalized design process and management of the design.

The embodiments of the present invention described above can be embodied in the form of a computer program that can be executed on various components on a computer, and the computer program can be recorded on a computer-readable medium. At this time, the medium may be a magnetic medium such as a hard disk, a floppy disk and a magnetic tape, an optical recording medium such as CD-ROM and DVD, a magneto-optical medium such as a floptical disk, , A RAM, a flash memory, and the like, which are specifically configured to store and execute program instructions.

Meanwhile, the computer program may be designed and configured specifically for the present invention or may be known and used by those skilled in the computer software field. Examples of computer programs may include machine language code such as those produced by a compiler, as well as high-level language code that may be executed by a computer using an interpreter or the like.

The specific acts described in the present invention are, by way of example, not intended to limit the scope of the invention in any way. For brevity of description, descriptions of conventional electronic configurations, control systems, software, and other functional aspects of such systems may be omitted. Also, the connections or connecting members of the lines between the components shown in the figures are illustrative of functional connections and / or physical or circuit connections, which may be replaced or additionally provided by a variety of functional connections, physical Connection, or circuit connections. Also, unless explicitly mentioned, such as " essential ", " importantly ", etc., it may not be a necessary component for application of the present invention.

The use of the terms " above " and similar indication words in the specification of the present invention (particularly in the claims) may refer to both singular and plural. In addition, in the present invention, when a range is described, it includes the invention to which the individual values belonging to the above range are applied (unless there is contradiction thereto), and each individual value constituting the above range is described in the detailed description of the invention The same. Finally, the steps may be performed in any suitable order, unless explicitly stated or contrary to the description of the steps constituting the method according to the invention. The present invention is not necessarily limited to the order of description of the above steps. The use of all examples or exemplary language (e.g., etc.) in this invention is for the purpose of describing the invention in detail and is not to be construed as a limitation on the scope of the invention, It is not. It will also be appreciated by those skilled in the art that various modifications, combinations, and alterations may be made depending on design criteria and factors within the scope of the appended claims or equivalents thereof.

Claims (15)

The present invention relates to a method for designing and managing a network service descriptor (NSD) by a system constituting a micro service architecture (MSA) through a network function virtualization (NFV) system and an API service,
An element placement step of receiving a basic component of a network service from a user terminal and arranging the received basic element in a basic element output space;
If an input to a predetermined relationship diagram is subsequently received after an input to any one of the arranged basic elements is received via the user terminal, Basic element copying batching step;
A element tree output step of converting a connection relationship between the arranged basic elements into a tree structure and outputting the tree structure to the tree output space when at least two basic elements are arranged in the relation output space;
An input value receiving step of receiving a property value for each elementary element located in the relation space output space from the user terminal to form a flavor;
A graph defining step of defining a virtual network function forwarding graph (VNFFG) based on a result of combining at least two flavors;
A change detection step of detecting whether the network service descriptor according to the defined virtual network function forwarding graph defines whether the life cycle is changed by the NFVO in the interworking; And
The lifecycle of the network service descriptor before on-boarding is changed to one of at least five, in response to the registration information before the on-boarding of the network service according to the descriptor, A change information notification step of notifying the change information,
The graph defining step may include:
Further defining a type of a network service provided by the defined virtual network function forwarding graph (VNFFG) based on information received from the user terminal or function information preset for each flavor,
Wherein the change detection step and the change information notification step comprise:
Wherein the second system is implemented by a second system different from the first system performing the element placement step, the basic element copy placement step, the element tree output step, the input value reception step, and the graph definition step. A method for designing and managing a network service descriptor in a virtualization system. The method according to claim 1,
The graph defining step may include:
And defining a context-based transfer policy for the defined VNFFG in the network functional virtualization system. The method according to claim 1,
Wherein the input value receiving step comprises:
At least two instance generation levels are defined in the flavor,
The relationship diagram output space comprises:
Wherein the network service descriptor includes at least one address corresponding to each flavor. The method according to claim 1,
The basic element
VNF, PNF, and Nested NS in the network function virtualization system. The method according to claim 1,
The method comprises:
WEB-WAS-DB structure in a network function virtualization system according to the present invention. delete The method according to claim 1,
The life cycle includes:
A first state in which a design of a network service according to the descriptor is in progress;
A second state for performing a validity check according to a standard model and a verification of an operational suitability of a network service according to the descriptor;
A third state immediately before the verification of the network service according to the descriptor is completed and the NFVO is on-boarding;
A fourth state in which a network service according to the descriptor is on-board the NFVO; And
And a fifth state for maintaining a network service according to the descriptor for maintenance. A computer-readable recording medium storing a program for implementing the method according to any one of claims 1 to 5 and 7. The present invention relates to a system for designing and managing a network service descriptor (NSD) by configuring a micro service architecture (MSA) through a network function virtualization (NFV) system and an API service,
The system comprising a first system and a second system,
A first system for designing a network service descriptor comprises:
An element arrangement unit for receiving a basic component of a network service from a user terminal and arranging the received basic element in a basic element output space;
If an input to a predetermined relationship diagram is subsequently received after an input to any one of the arranged basic elements is received via the user terminal, A basic element copy arrangement part;
A element tree output unit for converting a connection relation between the arranged basic elements into a tree structure and outputting the tree structure to the tree output space when at least two basic elements are arranged in the relation output space;
An input value receiver for receiving a characteristic value of each basic element located in the relation space output space from the user terminal and configuring a flavor; And
And a graph defining unit that defines a virtual network function forwarding graph (VNFFG) based on a result of combining at least two flavors,
Wherein the graph defining unit comprises:
Further defining a type of a network service provided by the defined virtual network function forwarding graph (VNFFG) based on information received from the user terminal or function information preset for each flavor,
A second system for managing the designed network service descriptor,
The network service descriptor according to the defined virtual network function forwarding graph detects whether the lifecycle is changed by the NFVO in the interworking mode,
Wherein the network function virtualization system notifies the user terminal of a change in the life cycle in response to registration information before the network service is on-boarded according to the descriptor when the life cycle is changed. A system for designing and managing network service descriptors. 10. The method of claim 9,
Wherein the graph defining unit comprises:
Wherein a transfer policy for a context for the defined VNFFG is additionally defined in the network function virtualization system. 10. The method of claim 9,
Wherein the input value receiver comprises:
At least two instance generation levels are defined in the flavor,
The relationship diagram output space comprises:
Wherein the network service descriptor is present in at least one of a plurality of addresses of the plurality of users. 10. The method of claim 9,
The basic element comprises:
VNF, PNF, and Nested NS of the network service descriptor. 10. The method of claim 9,
The system comprises:
WEB-WAS-DB structure. ≪ / RTI > delete 10. The method of claim 9,
The life cycle includes:
A first state in which a design of a network service according to the descriptor is in progress;
A second state for performing a validity check according to a standard model and a verification of an operational suitability of a network service according to the descriptor;
A third state immediately before the verification of the network service according to the descriptor is completed and the NFVO is on-boarding;
A fourth state in which a network service according to the descriptor is on-board the NFVO; And
And a fifth state for storing a network service according to the descriptor for maintenance.

Images