JP2017143452A - Management device, and network service management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve the convenience of a network by making the management of a life cycle of the construction, update and deletion of a network service quick and efficient.SOLUTION: A management device M for managing an NS (network service) includes an E2EO 1 for managing the NS, a server system device management part 2 for managing a server system device (device), and an NW system device management part 3 for managing an NW (network) system device (device). The E2EO 1 includes a request reception part 12 for acquiring an NS generation request including an input parameter necessary to designate a device to be used to provide the NS, a catalog management part 13 for managing a catalog to be a model of an NS, a resource arbitration part 14 for arbitrating resources of a device, a workflow part 11 for generating resources of a designated device in accordance with an input parameter and generating a slice for achieving an NS when a catalog is selected, and an NS life cycle management part 16 for managing the life cycle of the NS.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a technique for managing an NW (Network).

  Patent Document 1 discloses that “a plurality of computer nodes, one or a plurality of communication devices, and a physical infrastructure including a plurality of links connecting the computer nodes and the communication devices, and a physical infrastructure for each computer node of the physical infrastructure. The computer resource amount and the network resource amount for each link are grasped, the virtual machine and virtual connection necessary for the requested network function virtualization service are calculated, and the computer resource amount and the network resource amount are calculated based on the computer resource amount and the network resource amount. A network function virtualization infrastructure management system including a management computer that searches for a storage relationship between a virtual machine and the computer node and constructs the virtual machine and the virtual connection on the physical infrastructure is disclosed.

Japanese Patent Laying-Open No. 2015-162147 (Claim 1)

  According to Patent Document 1, only a technology for securing resources of server system devices and NW system devices is disclosed, and a technology for constructing a specific network service is not mentioned.

  In view of the above circumstances, an object of the present invention is to speed up and improve life cycle management such as construction, update, and deletion of a network service and improve the convenience of the network.

  In order to solve the above problem, the invention according to claim 1 manages an NS (Network Service) constructed in an NW including a core NW (Network) serving as a virtualized area and an access NW serving as a non-virtualized area. A service management unit that manages the NS, a server system device management unit that manages a server system device disposed in the NW, and an NW system that manages the NW system device disposed in the NW A request for externally obtaining an NS generation request including input parameters necessary for designating the server system device and the NW system device to be provided to the NS. A reception unit, a catalog management unit that manages a catalog that is a model of the NS, a resource arbitration unit that arbitrates resources of the server system device and resources of the NW system device, When the catalog is selected, a resource for the specified server system device and a resource for the specified NW system device are generated according to the input parameter, and a slice for realizing the NS is generated. And a NS life cycle management unit that manages the life cycle of the NS.

  The invention according to claim 9 is a network service in a management apparatus that manages an NS (Network Service) constructed in an NW including a core NW (Network) serving as a virtualized area and an access NW serving as a non-virtualized area. A management method, wherein the management apparatus obtains an NS generation request including an input parameter necessary for designating a server system apparatus and an NW system apparatus to be provided for the NS from the outside, and A catalog selection step of selecting a catalog as an NS model, a resource arbitration step of arbitrating the resource of the server system device and the resource of the NW system device, and when the catalog is selected, depending on the input parameter , The resource of the designated server device and the resource of the designated NW device Generating a slice for realizing the NS, and performing an NS life cycle management step for managing the life cycle of the NS.

According to the first and ninth aspects of the invention, when an NS is constructed in an NW including a core NW that is a virtualized area and an access NW that is a non-virtualized area, an input parameter is used for the selected catalog. What is necessary is just to request information necessary for designating the server system apparatus and NW system apparatus to be provided for NS. In addition, the constructed NS is appropriately managed by being updated or deleted using the life cycle.
Therefore, the life cycle management such as construction, update, and deletion of network services can be made quicker and more efficient, and the convenience of the network can be improved.

  The invention according to claim 2 is the management apparatus according to claim 1, wherein the catalog is used in (1) a part describing the configuration of the NS and (2) in the NS. A part describing an application; (3) a part describing a physical function used in the NS; (4) a part describing a connection relationship between applications used in the NS; And a part describing a link used in NS.

  According to the second aspect of the present invention, the NS can be specifically designed by including these parts in the catalog.

  The invention according to claim 3 is the management apparatus according to claim 1 or 2, wherein the catalog is a slice generated when the NS is constructed, wherein the slice realizing the NS is And an element for describing an instantiation opportunity flag for distinguishing whether the slice is additionally generated when a subscriber is added.

  According to the invention described in claim 3, by providing the instantiation opportunity flag, the workflow unit can determine an appropriate instantiation opportunity for each part of the NS scheduled to be constructed.

  The invention according to claim 4 is the management device according to any one of claims 1 to 3, wherein the resource arbitration unit provides resources of the server system device to be provided for the NS. And reserving resources of the NW system device for providing the NS.

  According to the fourth aspect of the present invention, the resources of the server system device and the NW system device are generated after being reserved, so that the resources required for instantiation of the application and the NW connection required for NS generation are generated. Resources required at the time of instantiation can be generated with certainty, and even when a plurality of NS generation requests conflict, instantiation failure can be avoided.

  The invention according to claim 5 is the management device according to claim 4, wherein the resource arbitration unit reserves resources of the server system device, and then reserves resources of the NW system device. It is characterized by performing.

  According to the fifth aspect of the present invention, it is possible to flexibly select a base for constructing a server system device during NS generation.

  The invention according to claim 5 is the management device according to claim 4, wherein the resource arbitration unit generates an NW connection from the resource reservation of the NW system device after the resource reservation is completed. -Validate, and then generate and validate an application from the reservation of the resource of the server system device.

  According to the fifth aspect of the present invention, the NS communication test can be performed simultaneously with the NS generation by securing the NW communication and then starting the application.

  The invention according to claim 6 is the management device according to claim 4 or claim 5, wherein the resource arbitration unit includes a resource reservation end time limit of the server system device and the NW system. It is characterized in that it is possible to set an end time limit for reservation of device resources.

  According to the sixth aspect of the present invention, it is possible to avoid resource occupation due to reserved resources.

  The invention according to claim 6 is the management device according to claim 4 or claim 5, wherein the resource arbitration unit includes a resource reservation start date and time of the server system device and the NW system It is possible to set the start date and time of device resource reservation.

  According to the sixth aspect of the present invention, the operator can perform an operation before the NS generation request date and time.

The invention according to claim 7 is the management device according to any one of claims 4 to 6, wherein the input parameter includes resource reservation of the designated server system device, and , Including a priority relating to resource reservation of the designated network device.
The priority is preferably weighted among the priorities.

  According to the seventh aspect of the present invention, even when a reservation conflict occurs due to resource reservations from a plurality of operators, it is possible to secure a resource with a higher priority, and to smoothly proceed with NS construction.

The invention according to claim 8 is the management apparatus according to any one of claims 1 to 3, wherein the resource arbitration unit includes:
The arbitration of the difference between the number of endpoints required by the resource of the server system device and the number of endpoints set in the resource of the NW system device is performed.

  According to the eighth aspect of the present invention, it is possible to collectively set connections between server system devices and NW system devices having different numbers of endpoints.

  According to the present invention, life cycle management such as construction, update, and deletion of a network service can be made quicker and more efficient, and the convenience of the network can be improved.

It is a functional block diagram of the management apparatus of this embodiment. It is explanatory drawing of construction | assembly of NS with respect to a predetermined | prescribed NW structure. It is a comparative example which shows the failure of instantiation after a resource inquiry in a reference system. It is a sequence which shows the process of resource reservation production | generation (1/4). It is a sequence which shows the process of resource reservation production | generation (2/4). It is a sequence which shows the process of resource reservation production | generation (3/4). It is a sequence which shows the process of resource reservation production | generation (4/4). This is a sequence showing NS generation (1/2) processing. It is a sequence which shows the process of NS production | generation (2/2). It is a sequence which shows the process of miniNS generation (1/3). It is a sequence which shows the process of miniNS generation (2/3). It is a sequence which shows the process of miniNS generation (3/3).

  EMBODIMENT OF THE INVENTION The form (embodiment) for implementing this invention is demonstrated in detail, referring drawings.

  The management apparatus M according to the present embodiment manages the core NW that is a virtualization area and the access NW that is a non-virtualization area. Specifically, the management apparatus M monitors these devices by collecting various information from the devices arranged in the core NW and the devices arranged in the access NW. An NW configuration is completed by the devices arranged in the core NW and the devices arranged in the access NW.

  Further, the management device M manages an NS (Network Service) constructed in the NW including the core NW and the access NW. NS is an access NW held by an NS provider (eg, a telecommunications carrier) from a terminal on the NS user side (user), and a service provider (eg, ISP (Internet Service Provider) operator) from a device on the core NW. NS that can manage E2E (End to End) up to the end point.

  As shown in FIG. 1, the management device M includes an E2EO (End to End Orchestrator) 1 (service management unit), a server system device management unit 2, and an NW system device management unit. 3 (network device management unit).

E2EO1 is a functional unit that autonomously manages NS provided to users.
The server system device management unit 2 manages server system devices arranged in the NW including the core NW and the access NW.
The NW system device management unit 3 manages NW system devices arranged in the NW including the core NW and the access NW.
In response to a request from the host device U operated by the operator or another system U1 having a function equivalent to that of the host device U, the E2EO1, the server system device management unit 2, and the NW system device management unit 3 operate. The other system U1 corresponds to an OSS (Operation Support System) or a BSS (Business Support System). However, the description of the host device U also applies to the other system U1, and therefore, unless there are special circumstances, the other system U1. The description regarding U1 is omitted.

  The server system device is a device that executes NS. The server system devices include, for example, a DC (Data Center), a general-purpose server installed on the DC, and a virtual server (VM (Virtual Machine). Virtual machine) obtained by virtualizing the general-purpose server. It is not limited to these. One APL (Application) can be arranged in the virtual server. By operating the APL on the virtual server, a predetermined NS can be provided to the user. In the present embodiment, the APL is a VNFc (Virtual Network Function Component), or a VNF (Virtual Network Function: NW function) configured by combining one or more VNFc. Sometimes called. Moreover, DC may be called NFVI-PoP (Network Function Virtualization Infrastructure-Point of Presence).

  The NW system device is a device that transfers data for executing NS to another NW system device or a server system device. Examples of NW system devices include OLT (Optical Line Terminal), core router, L2SW (Layer2 Switch), L3SW (Layer3 Switch), and NTE (Network Terminal Equipment). It is not limited to these.

(E2EO1)
The E2EO1 includes a workflow unit 11, a request reception unit 12, a catalog management unit 13, a resource arbitration unit 14, a DB (DataBase) 15, an NS life cycle management unit 16, and a DB 17.

  The request reception unit 12 acquires an NS generation request output from the higher-level device U (request reception step). The NS generation request is information that causes the management apparatus M to generate (construct) NS. The NS generation request includes NS information obtained by appropriately arranging and combining descriptors of a plurality of types of server devices and descriptors of a plurality of types of NW devices in order to express a logical path set for a predetermined NW configuration. Including. E2EO1 maps these descriptors to corresponding server system devices and NW system devices arranged on the NW. The NS generation request includes an input parameter necessary for specifying a server system apparatus and an NW system apparatus that are provided for providing an NS using the logical path.

  The catalog management unit 13 manages a catalog as an NS template. The host device U can obtain a desired catalog from the catalog management unit 13 (catalog selection step). The operator can easily create a desired NS generation request by operating the host device U and inputting predetermined items (including input parameters described later) using the acquired catalog. There are one or more types of catalogs managed by the catalog management unit 113, and they are added, deleted, updated, provided, etc. as necessary. Details of the catalog will be described later.

The resource arbitration unit 14 arbitrates the resource of the server device and the resource of the NW device (resource arbitration step). The resource arbitration unit 14 outputs the result of the arbitration to the server system device management unit 2 and the NW system device management unit 3, and instructs resource mediation.
Note that the resource of the server system device includes a resource allocated to the server system device itself, and also includes a resource allocated to a link connected to a connection point set in the server device.
Further, the resources of the NW system device include resources allocated to the NW system device itself, and also include resources allocated to links connected to connection points set in the NW system device. The link includes a virtual link (VL). When the link connected to the connection point set in the server device and the link connected to the connection point set in the NW system device are the same, for example, the link can be treated as a resource of the server system device. it can. However, it may be handled as a resource of the NW system device.
Details of resource arbitration will be described later.

The DB 15 stores various information systematically. The information stored in the DB 15 includes the catalog C managed by the catalog management unit 13.
The workflow unit 11 is a functional unit that controls the entire processing of the management apparatus M.

The NS life cycle management unit 16 manages the life cycle (life) of the NS managed by the E2EO1. NS lifecycle management includes NS generation, generation NS update, and generation NS deletion.
The DB 17 stores various information systematically. The information stored in the DB 17 includes a record R managed by the NS life cycle management unit 16. Details of the record R will be described later.

(Server system management unit 2)
The server system management unit 2 includes an SVRO (Server Resource Orchestrator) 21, a VIM (Virtual Infrastructure Manager) 22, a VNFM (Virtual Network Function Manager) 23, An EMS (Element Management System) 24 for H / W (Hardware) and an EMS 25 for APL are provided.

The SVRO 21 is a functional unit that autonomously manages the resources of the server system device. A plurality of SVROs 21 can exist for one or a plurality of server devices arranged in the NW configuration.
The VIM 22 is a functional unit that manages and controls the VM generated in the general-purpose server. A plurality of VIMs 22 can exist for one or a plurality of generated VMs.
The VNFM 23 is a functional unit that manages and controls the APL installed in the VM generated in the general-purpose server. A plurality of VNFMs 23 can exist for one or more APLs operating on the NW configuration.
The H / W EMS 24 is a functional unit that manages and controls the server system device.
The EMS 25 for APL is a functional unit that manages and controls APL in accordance with request information from the host apparatus U.

(NW system management unit 3)
The NW system management unit 3 includes an NWRO (Network Resource Orchestrator) 31 and an NIM (Network Infrastructure Manager) 32.

The NWRO 31 is a functional unit that autonomously manages the resources of the NW system device.
The NIM 32 is a functional unit that manages and controls the NW system device.

(catalog)
The catalog managed by the catalog management unit 13 is, for example, NSD (NS Descriptor), VNFD (VNF Descriptor), PNFD (Physical Network Function Descriptor), VLD (VL Descriptor), and VNFFGD (VNF Forwarding Graph Descriptor). Contains elements.

NSD is a part that describes the configuration of NS. The NSD holds information necessary for identifying and constructing the NS, information referring to the VNFD, PNFD, VNFFGD, and VLD related to the NS.
VNFD is a part that describes an application (VNF) used in NS. The VNFD holds information necessary for identifying and constructing the VNF.
The PNFD is a part that describes a physical function (NW function provided by the server system device and the NW system device; PNF (Physical Network Function)) used in the NS. The PNFD holds information necessary for identifying and constructing the PNF.
VLD is a part that describes a VL (link) used in NS. The VLD holds information necessary for identifying and constructing the VL.
VNFFGD includes a portion describing the cooperation by a plurality of applications (VNF) used in the NS. Cooperation by an application means that a plurality of (VNF) are connected to provide one function. The VNFFGD holds information for identifying the VNFFGD, link information between linked VNFs, VLD related to the VNFFGD, information for identifying the VNFD, and the like.

(Details of NSD)
The NSD includes a name (nsdName) for identifying the NSD, version information (nsdVersion), information (NS Deployment Flavor) describing requirements such as capacity and performance for generating the NS, and an NS endpoint. Described information (Service Access Point), information on the maximum number of Service Access Points (maxEndPoint), information for setting input parameters that can be specified at NS generation in NSD (runtimePolicyInfo), and alarm notification destination information (notifications) And such elements.

  The NS Deplotyment Flovour includes information for identifying (nsFlavourID), information for maintenance (flavourKey), information of VNF to be configured (ConstituentVNF), information of VL to be configured (ConstituentVL), and information of VNFFG to be configured It includes elements such as information (ConstitutentVnffg), affinity policy (AffinityType), anti-affinity policy (AntiAffinityType), and constraint information (constraint).

  The Service Access Point includes elements such as identification information (cpId), end point type information (ConnectionPointType), and maximum generation number information (maxEndPoint).

  The Constituent VNF includes information for referencing the VNFD (vnfReference), information describing the requirements for generating the VNF (DeplotymentFlavour), and information for determining the instantiation opportunity (instantiateMode) ), Redundancy model information (redundancyModel), affinity policy (AffinityType), anti-affinity policy (AntiAffinityType), constraint information (constraint), capability (capability), number of instantiations (numberOfInstances), etc. Elements included.

  The Consituent VL includes information (vlReference) for referring to a VLD, information (VldFlavour) describing requirements for generating a VL, information (instantiateMode) for determining an instantiation opportunity, constraint information ( constraint).

  The constitutive VNFFG includes elements such as information (vnffgReference) for referring to VNFFGD, information (instantiateMode) for determining an instantiation opportunity, and constraint information (constraint).

  The Affinity Type includes elements such as affinity policy rule scope information (affinityScope) and a list of information (policyRules) for identifying resources to which the affinity policy rule is applied.

  The Anti Affinity Type includes elements such as anti-affinity policy rule scope information (antiAffinityScope) and a list of information (policyRules) identifying resources to which the anti-affinity policy rule is applied.

  The Connection Point Type includes elements such as end point information (ConnectionPointValue) related to the server system device and end point information (ConnectionPointValue) related to the NW system device.

  The Connection Point Value includes end point type (NNI (Network Network Interface), base terminal point, DC Gateway Router end point, UNI (User Network Interface), etc.), information for identifying the corresponding Service Access Point, port information ( Access port, trunk port, etc.), VLAN-ID information, IPv4 address information, IPv6 address information, IPv4 prefix information, IPv6 prefix information, IPv4 filter information, IPv6 filter information, and usage protocol information (BGP) , OSPF, Statics, Direct, VRRP, etc.), proximity A information S, proximity IPv4 address information, proximity IPv6 address information, authentication key information, area information, metric information, MD5 key information, Tics route information (StaticRoute), group ID information, role ID information, virtual IPv4 address information, virtual IPv6 information, virtual IPv4 prefix information, virtual IPv6 Prefix information and other elements are included.

  The Static Route includes elements such as address type information (IPv4, IPv6, etc.), address information, prefix information, and next hop information.

(Details of VNFD)
The VNFD includes a name (vnfdName) for identifying the VNFD, version information (vnfdVersion), information on the VNF components constituting the VNF (Virtulised Development Unit), and connectivity within the VNF (including between VNFc). It includes elements such as described information (IntervalVirtualLinkDescriptor), information describing an end point outside the VNF (ExternalConnectionPointDescriptor), and information describing requirements such as capacity and performance for generating the VNF (Deployment Flavor).

  The Virtulised Development Unit includes elements such as information for identifying (vduId) and information describing connectivity between VNFc (InternalConnectionPointDescriptor).

  The Internal Connection Point Descriptor includes elements such as information for identifying (icpId), information for referring to the Internal Virtual Link Descriptor, and end point type information (ConnectionPointType).

  The Internal Virtual Link Descriptor refers to the name (vldName) for identifying, version information (vldVersion), summary information (description), information for referring to the Internal Connection Point Descriptor, and the External Connection Point Descriptor. Information describing the connection type (Connectivity Type), information describing the requirements for generating the VL (Vld Flavor), affinity policy (AffinityType), and anti-affinity policy (AntiAffinityType). Elements included.

  The External Connection Point Descriptor includes information for identifying (cpId), information for referring to the Internal Virtual Link Descriptor, information for referring to the Internal Connection Point Descriptor, information on the end point type (ConnectionPointType), Such elements are included.

  The Deplotyment Flavor includes information for identifying (dFlavourId), information for maintenance (flavourKey), VDU information (ConstituentVDU), VL information (ConstituentVl), and constraint information (constraint) And such elements.

  The Constituent VDU includes elements such as information for referring to the Virtualization Deployment Unit, information on the number of requested instances (numberOfInstances), and information on the VNFc to be configured (ConstituentVnfc).

  The constitutive Vnfc includes elements such as information for identifying (vnfcId) and information for referring to the internal connection point descriptor.

  The Connectivity Type includes elements such as a provision type (L1, L2, L3, etc.) and connectivity requirements (E-Line, E-LAN, E-Tree, IPv6, IPv4, etc.).

  The VLD Flavor includes elements such as identification information (vldFlavourId), information describing bandwidth requirements (BandWidthRequirements), information describing QoS (QoSDescription), and availability level information.

  The BandWidthRequirements includes elements such as necessary bandwidth information at the aggregation point and necessary bandwidth information at the end points.

  The QoSDescription includes elements such as maximum delay information, maximum jitter information, maximum packet discard rate, and priority level.

(Details of VLD)
The VLD includes a name (vldName) for identifying a VLD, version information (vldVersion), information for referring to a connection point, information describing a connection type (Connectivity Type), and a VL. Information including requirements (Vld Flavor), affinity policy (AffinityType), and anti-affinity policy (AntiAffinityType) are included.

(Details of VNFFGD)
The VNFFGD includes a name (vnffgdName) for identifying the VNFFGD, version information (vnffgdVersion), end point number information (numberOfEndponts), VL number information (numberOfVirtualLinks), information for referring to the VLD, and Network Forwarding It includes elements such as information describing the Path (NFP), information for referring to the Connection Point, and information for referring to the VNFD of the VNF to be configured.

  The NFP includes elements such as information (nfpId) for identifying the NFP, policy rules (MAC transfer rules, routing entries, etc.) applied to the NFP, and information for referring to the Connection Point.

(Details of PNFD)
The PNFD includes elements such as a name (pnfdName) for identifying the PNFD, version information (pnfdVersion), and information (ConnectionPoint) describing an end point of a VL to be connected.

  The Connection Point includes elements such as identification information (cpId) and end point type information.

  The NSD is prepared for each NS, for example, for each service such as an ISP connection service or a dedicated line service, and can be expressed by a combination of VNFD, PNFD, VLD, and VNFFGD. The operator can easily create a desired NS generation request by operating the host device U and inputting input parameters. The operator basically selects a catalog that matches the NS configuration from the DB 15 regarding the creation of the NS generation request.

  For example, with respect to the NW configuration (symbol N1) shown in FIG. 2, the upper apparatus U has a catalog in which NSD (c1), VNFD (c2), PNFD (c3), VNFFGD (c5), and VLD (c4) are defined. Can be acquired from the management apparatus M, and input parameters can be input to the acquired catalog. As an example, this NW configuration is an access NW (f2, f3) connected to a house (internal terminal device) with respect to the core NW (f1) by a connection point indicated by a circled number, ISP, Businesses A and B (f4, f5) and DCs (f6 to f8) installed in a predetermined area (Zone) are connected. The input parameter specifies No. 12 as the connection point on the access side (specified on the access NW, the connection point indicated by the circled number 12), and A (the circled number) as the ISP provider of the access destination 2 is connected to the connection point indicated by 1), as shown by reference numeral N2 in FIG. Built. In addition, the input parameter specifies number 9 as the connection point on the access side (specified on the access NW, the connection point indicated by the circled number 9), and B (circle) as the ISP provider of the access destination 2 is connected to the connection point indicated by the number 2), as shown by reference numeral N3 in FIG. 2, a VL is applied to the second connection point and the ninth connection point. Another NS (bold box) is constructed.

  In this NS, vNTEAPL (virtual NTE APL) (f9) is mounted on a VM arranged in a DC (or NTE on this DC) connected to the sixth connection point in accordance with VNFD. In the NS, another vNTEAPL (f10) is mounted on a VM arranged in a DC (or NTE on this DC) connected to the seventh connection point. vNTEAPL is an APL that operates on a virtualized NTE.

  In this way, the management apparatus M manages the NS template as a catalog, can construct the NS according to the input parameters included in the NS generation request, reuse the same catalog, and have different requirements Can be provided.

When the catalog is selected in response to the NS generation request from the host device U, the workflow unit 11 generates the specified server device resource and the specified NW device resource according to the input parameters. Then, a slice for realizing NS is generated (slice generation step). A slice is an NW obtained by virtualizing a part of an existing NW. The workflow unit 11 can generate one or more independent slices that are not affected by other virtual environments.
In the present embodiment, “generating a slice that realizes NS” may be simply expressed as “generating NS”.

As described above, when an NS is constructed in an NW including a core NW that is a virtualized area and an access NW that is a non-virtualized area, a server system apparatus that provides NS with input parameters for the selected catalog It is sufficient to request information necessary for designating the NW system device. The necessary information may be, for example, information specifying a server system device and an NW system device, or information indicating a result selected by a predetermined internal logic.
Therefore, the construction of the network service can be made faster and more efficient, and the convenience of the network can be improved.

  The NS life cycle management unit 16 manages the life cycle of the generated NS (NS life cycle step). Specifically, for each slice that realizes the generated NS, the life cycle of the slice is stored in the DB 17 so as to be readable and writable as a record R.

  The NS life cycle management unit 16 externally sends an NS update request including input parameters necessary for designating the NS, server system device, and NW system device to be used for updating the generated NS in the NS life cycle management step. Request step acquired from NS, NS selection step for selecting NS, resource arbitration step for arbitrating server system resource and NW system resource, specified server system resource, and specified NW A slice update step for updating the resource of the system device to update a slice for realizing the NS and a life cycle management step for managing the life cycle of the updated NS are executed.

  Thereby, when updating NS constructed in the NW including the core NW that becomes the virtualized area and the access NW that becomes the non-virtualized area, the server system that is used to update the NS with the input parameter for the constructed NS What is necessary is just to request information necessary for specifying the device and the NW system device. The necessary information may be, for example, information specifying a server system device and an NW system device, or information indicating a result selected by a predetermined internal logic. Therefore, the network service can be updated quickly and efficiently, and the convenience of the network can be improved.

  Further, the NS life cycle management unit 16 obtains an NS deletion request including an input parameter necessary for designating the NS, which is used for deleting the NS generated in the NS life cycle management step, from the outside. NS selection step for selecting the NS, resource arbitration step for arbitrating the resource of the server system device and the resource of the NW system device, the resource of the specified server system device, and the specified NW system A slice deletion step of deleting a device resource and deleting a slice realizing the NS, and a life cycle management step of ending the life cycle of the deleted NS are executed.

  As a result, when deleting the NS constructed in the NW including the core NW that becomes the virtualized area and the access NW that becomes the non-virtualized area, the record R that is used to delete the NS with the input parameter for the constructed NS Can be specified. Therefore, the network service can be deleted quickly and efficiently, and the convenience of the network can be improved.

(Resource reservation)
When an NS is constructed, a predetermined amount of resources are allocated to the target server system device and NW system device, and then instantiation for implementing the necessary VNF is executed. However, since the NW configuration handled in the present embodiment receives, for example, NS generation requests from a plurality of operators, it may not be possible to secure resources necessary for instantiation.

  For example, as shown in FIG. 3, it is assumed that a reference system having a function of constructing an NS receives a free resource inquiry from operators A and B (steps S1 and S2). However, it is assumed that the empty resource inquiry from the operator A is slightly earlier than the empty resource inquiry from the operator B. At this time, the reference system determines that there is an available resource to the operator A (step S3), and transmits a response to that effect (step S4). However, since the resource inquiry from the operator B is too early, the resource inquiry from the operator A erroneously determines that the operator B has an available resource even though there is essentially no available space (step) S5), a response to that effect is transmitted (step S6).

  As a result, in response to the instantiation request from the operator A (step S7), instantiation is executed as usual and a completion notification is sent (step S8), but the instantiation request from the operator B (step S9) On the other hand, since there are no free resources (step S10), instantiation fails (step S11).

  In order to avoid such inconvenience, the resource arbitration unit 14 of the management apparatus M includes “available resource” and “reserved resource” in resource information for managing resources to be allocated to the server system apparatus and the NW system apparatus. , “Use resource” flag.

The “available resource” flag is turned on when the target resource is available, and turned off otherwise.
The flag of “reserved resource” is turned on when the target resource is inquired by the operator of the upper apparatus U, and turned off otherwise.
The “resource in use” flag is turned on when the target resource is already used for providing NS, and turned off otherwise.

  As described above, when there is a resource inquiry from a certain operator, it can be ensured that the resource exists at the time of instantiation by securing the resource as a reserved resource. In the example of FIG. 3, when the reference system is replaced with the management apparatus M of the present embodiment, when it is determined that there is an available resource for the operator A (step S <b> 3), the resource is set as a reserved resource. Thus, even if the management apparatus M receives an empty resource inquiry from the operator B, the management apparatus M can reply to the operator B that there is no empty resource because it has already been reserved and there is no other empty space. Therefore, the instantiation request from the operator B (step S9 in FIG. 3) can be made unnecessary.

<< Process >>
Next, various processes for the management apparatus M to construct the NS will be described. In the core NW and the access NW, a plurality of types of server devices and a plurality of types of NW devices are installed. In the following description of processing, status codes such as “200 OK”, “202 Accepted”, “ACK” are exchanged for various requests and notifications (see FIGS. 4 to 12). The description of the status code is omitted. The OSS 4 described in this process corresponds to the other system U1, and can exchange predetermined information with the host device U.

(Resource reservation generation)
First, processing for reserving and generating resources used for providing NS is executed. As shown in FIGS. 4 to 7, this process starts from step A1.

  In step A1, the OSS 4 obtains a resource reservation generation request from the upper apparatus U. The resource reservation generation request includes identification information for identifying a server system device and an NW system device involved in the NS to be constructed among the server system devices and the NW system devices arranged in the target NW configuration.

  Next, in step A2, the OSS 4 searches the Product catalog 15a. The Product catalog 15a is provided in the E2EO1 DB 15 and functions as a repository for the OSS4. The OSS 4 acquires the NSD corresponding to the server system device and the NW system device identified by the identification information included in the resource reservation generation request.

  Next, in step A3, the OSS 4 transmits an NS resource reservation generation request to E2EO1. The NS resource reservation generation request includes, for example, the NSD designated by the operator of the higher-level apparatus U among the NSDs acquired by the OSS 4 from the product catalog 15a. When specifying the NSD, the contents of the NSD acquired from the Product catalog 15a may be changed as appropriate.

  Next, in step A4, the E2EO1 checks the catalog information registered in the product catalog 15a in response to the NS resource reservation generation request. E2EO1 checks the consistency between the NSD designated by OSS4 and the catalog information.

Next, in step A5, the E2EO1 pays out an E2E-NS-ID serving as identification information of the NS to the NS scheduled to be constructed.
Next, in step A6, E2EO1 holds instance information at the time of resource reservation. The instance information is information that identifies a server system device and an NW system device that will implement the VNF to be instantiated. Instance information is stored in the DB 15.

  Next, in step A7, E2EO1 extracts VNFD from the NSD included in the NS resource reservation generation request. That is, the VNFD related to the NS identified by the designated NSD is read.

  Next, in step A8, E2EO1 decomposes the designated NSD to generate a plurality of mini NSDs. For example, the E2EO1 can decompose the NSD so that a small NS based on the generated miniNSD can provide a predetermined small-scale service. The decomposition method is arbitrary, and the description thereof is omitted.

Next, in step A9, the E2EO1 pays out a miniNSD-ID serving as identification information of the miniNSD for each generated miniNSD.
Next, in step A10, the E2EO1 selects, from the extracted VNFD, the VNF identified by the VNFD or the SVRO 21 that manages the resources of the server device on which the VNF is mounted.
Thereafter, the following steps A11 to A22 are repeatedly performed for the generated miniNSD.

As shown in FIG. 5, in step A <b> 11, E2EO <b> 1 transmits a mini NSD registration request from which the mini NSD-ID has been issued to the selected SVRO 21.
Next, in step A12, the SVRO 21 verifies the mini NSD for which a registration request has been made. Specifically, it is verified whether or not the miniNSD to be verified is cataloged. For example, if the miniNSD to be verified is an NSD that is highly useful to such an extent that it is selected from a predetermined number or more operators of the host device U, the SVRO 21 determines to catalog this miniNSD.

  Next, in step A13, the miniNSD requested for registration is cataloged and registered in the miniNS catalog 15b. The miniNS catalog 15b is a database that stores and manages the miniNSD, and is provided in the NWRO 31. The miniNS catalog 15b is a repository for the SVRO 21. Further, the DB 15 may have a miniNS catalog 15b.

Next, in step A14, the SVRO 21 notifies E2EO1 that the miniNSD registration has been completed.
Next, in step A15, the E2EO1 transmits a registered mini NSD reservation generation request to the selected SVRO 21. The mini NSD reservation generation request is a request for reliably generating an NS described in mini NSD.

Next, in step A16, the SVRO 21 verifies the mini NSD reservation generation request received from the E2EO1. Specifically, it is verified whether or not the reservation generation request to be verified contains all the identification information of the server system device and the identification information of the NW system device provided for providing NS described in miniNSD.
Next, in step A17, the SVRO 21 selects a VIM 22 or a DC that can satisfy the received mini NSD reservation generation request. Specifically, feasibility check (realization) based on capacity information (eg, information indicating data storage capacity, processing speed, etc.) of DC (NFVI-PoP) managed by each VIM 22 grasped by SVRO 21 (Evaluation of possibility) and VIM 22 or DC under the control of VIM 22 is selected for each VNF.
Thereafter, the following steps A18 to A21 are repeatedly performed on the selected VIM (necessary VIM).

  As shown in FIG. 6, in step A18, the SVRO 21 transmits a virtual resource reservation generation request to the VIM 22. The virtual resource reservation generation request is a request for ensuring that a virtual resource can be generated in the requested VNF.

Next, in step A19, the VIM 22 verifies the received virtual resource reservation generation request. Specifically, it is verified whether the virtual resource reservation generation request to be verified includes the identification information of the VNF to be managed by the VIM 22 or the identification information of the DC in which the VNF is arranged.
Next, in step A20, the VIM 22 reserves a virtual resource for the VNF to be managed by itself (generates a reserved virtual resource).
Next, in Step A21, the VIM 22 sends a virtual resource reservation generation completion notification (Step S21) to the SVRO 21 indicating that the virtual resource reservation has been completed for the VNF to be managed by itself. It is transmitted as a response of A18).

  Next, in step A22, the SVRO 21 transmits, to E2EO1, a mini NSD reservation generation completion notification indicating that the mini NSD reservation is completed as a response to the mini NSD reservation generation request (step A15).

  Next, in step A23, the E2EO1 stores reserved gCP information indicating connection points (gCP (GW (GateWay) Connection Point)) set in all reserved mini NSDs in the DB 15, for example. The reservation gCP information is information that defines the connection relationship between each mini NSD. For example, by performing base resource conversion from information indicating virtual resource reservations created by each VIM 22 in response to a virtual resource reservation generation request from the SVRO 21 can get.

  Next, in step A24, E2EO1 extracts VLD and VNFFGD from the NSD included in the NS resource reservation generation request. That is, the VLD and VNFFGD related to the NS identified by the designated NSD are read out.

Next, as shown in FIG. 7, in step A25, the E2EO1 transmits a resource reservation generation request to the NWRO31. The resource reservation generation request is a request for ensuring that resources can be generated in the requested NW system device.
Next, in step A26, the NWRO 31 verifies the received resource reservation generation request. Specifically, it is verified whether or not the resource reservation generation request to be verified includes identification information of the NW system device to be managed by the NIM 32.

Next, in step A27, the NWRO 31 transmits a resource reservation generation request (similar to step A25) to the NIM 32.
Next, in step A28, the NIM 32 reserves and generates a resource for the NW system device to be managed (generates a reserved resource).

Next, in Step A29, the NIM 32 sends a resource reservation generation completion notification (Step S29) to the NWRO 31 indicating that the resource reservation generation has been completed for the NW system device to be managed. A27) is transmitted as a response.
Next, in step A30, the NWRO 31 sends a resource reservation generation completion notification to the E2EO1 indicating that the resource reservation generation has been completed for the NW system device to be managed by itself (step S30). A25) is transmitted as a response.

Next, in step A31, the E2EO1 notifies the OSS4 of an NS resource reservation generation completion notification indicating that the resource reservation generation has been completed for, for example, the NS described by the NSD designated by the operator of the upper apparatus U. The NS resource reservation generation request (step A3) is transmitted as a response.
Next, in step A32, the OSS 4 transmits a resource reservation generation completion notification indicating that a set of reservation resources has been generated to the upper apparatus U as a response to the resource reservation generation request (step A1). .

  The resource reservation generation process shown in FIGS. 4 to 7 can surely generate a resource used for providing the NS scheduled to be constructed, and prevent instantiation failure (see FIG. 3).

(NS generation)
Next, a process of generating (constructing) NS for the NW configuration in a state where resources are reserved is executed. As shown in FIGS. 8 and 9, this process starts from step B1.

  In step B1, the OSS 4 obtains an NS generation request from the upper apparatus U. The NS generation request includes identification information for identifying the server system apparatus and the NW system apparatus that are engaged in the NS that is scheduled to be constructed and whose resources are reserved. NS generation requests can be identified with input parameters.

  In step B2, the OSS 4 searches the Product instance table 15c. The Product instance table 15c is provided in the E2EO1 and functions as an OSS4 repository. The OSS 4 determines whether or not an instance (Product instance) is mounted on the server system device and the NW system device arranged in the target NW configuration. If the Product instance used for the requested NS already exists, the Product instance can be used for NS generation.

  In step B3, the OSS 4 transmits an NS generation request to E2EO1. This NS generation request is equivalent to the NS generation request acquired from the host device U in step B1.

  In step B4, the E2EO1 analyzes the received NS generation request and checks whether the NS to be requested is reserved. Specifically, it is checked whether or not the resources of the server system device and the NW system device involved in the NS scheduled for construction are reserved. Here, it is assumed that the resource is reserved and generated.

In step B5, E2EO1 transmits a resource generation request to NWRO31. The resource generation request includes identification information for identifying the NW system device for which the resource has been reserved. The E2EO1 performs resource generation first (not from the server system device) from the NW system device, and first requests the NWRO 31 (not from the SVRO 21). By making such an order, it is possible to easily construct NS services collectively. However, the resource may be generated first from the server system device.
Thereafter, the following steps B6 to B8 are repeatedly performed by the number of necessary NW apparatuses (necessary number) for which resources are to be generated.

  In step B6, the NWRO 31 transmits a resource generation request to the NIM 32. The resource generation request includes identification information for managing the NW system device managed by the NIM 32 and reserved for the resource.

In step B7, the NIM 32 generates a resource for its own management target NW system device.
In step B8, the NIM 32 transmits a resource generation completion notification indicating that the generation of resources has been completed to the NWRO 31 as a response to the resource generation request in step B6.
In step B9, the NWRO 31 transmits, to E2EO1, a resource generation completion notification indicating that resource generation has been completed as a response to the resource generation request in step B5.
Thereby, the resource generation process for the NW system device is completed.

  As illustrated in FIG. 9, in step B <b> 10, E2EO <b> 1 transmits a miniNS generation request to the SVRO 21. The miniNS generation request includes identification information for identifying the server system device for which the target miniNS is constructed and the resource is reserved. The miniNS generation request is transmitted by the number of miniNSs constituting the NS to be generated.

  In step B11, miniNS generation processing is executed. The miniNS generation process is executed for the number of miniNS. Details of the miniNS generation process will be described later. As a result, miniNS is generated as a whole, and NS is generated as a combination of miniNS.

  In step B12, the SVRO 21 transmits, to E2EO1, a miniNS generation completion notification indicating that the miniNS generation is completed as a response to the miniNS generation request in step B10. As many miniNS generation completion notifications as the number of generated miniNS are transmitted.

In step B13, the E2EO1 transmits an NS generation completion notification indicating that the NS generation has been completed as a response to the NS generation request in step B3. In this step, an NS is generated by connecting each connection point (gCP) of the generated miniNS using VL.
In step B14, the OSS 4 is involved in the NS notified by the NS generation completion notification, starts the Product instance for the server device and the NW device in which the resource is generated, and registers the product instance in the Product instance table 15c. . Thereby, NS generation is completed.

  In step B15, the OSS 4 transmits an NS generation completion notification indicating that NS generation has been completed to the upper apparatus U as a response to the NS generation request in step B1.

The requested NS can be constructed by the NS generation process shown in FIGS.
The workflow unit 11 generates a slice that implements the constructed NS.

(MiniNS generation)
The miniNS generation process in step B11 will be described. As shown in FIGS. 10 to 12, this process starts from step C1 after the SVRO 21 receives the miniNS generation request from E2EO1 in step B10 already described.

  As shown in FIG. 10, in the miniNS generation request received by the SVRO 21 in step B10, “Os-Manfvo” is set as the reference point RP (Reference Point), and “Network” is set as the interface IF (Inter Face). “service lifecycle management” is set, and “Instatiate NS” is set as the operation Op (Operation). In this case, the miniNS generation request means that the operation of “Instatiate NS” is performed using the “Network service lifecycle management” interface at the reference point of “Os-Manfvo”.

In step C1, the SVRO 21 transmits a VNF instantiation request to the VNFM 23. The VNF instantiation request includes RP (Or-Vnfm), IF (VNF lifecycle management), and Op (Instantiate VNF) shown in FIG. 10, and causes the VNFM 23 to execute VNF instantiation.
This VNF instantiation request is made for all VNFs in miniNS.
Further, the processing from step C1 to step C7 is repeatedly performed by the number of VNFs included in the miniNS.

In step C2, the VNFM 23 transmits a VNF life cycle operation permission request to the SVRO 21. The VNF life cycle operation permission request includes RP (Or-Vnfm), IF (VNF life cycle operation granting), and Op (Grant Lifecycle Operation) shown in FIG. 10, and the life cycle (lifetime) of VNF is shown. The SVRO 21 is allowed to execute permission to allow the VNFM 23 to perform the operation (change of the start time or end time of the lifetime).
The SVRO 21 can confirm that all the VNFMs 23 continue processing by receiving this permission request from the VNFM 23. Considering that the VNFM 23 will be used in the form of a multi-vendor in the future, it is preferable to execute a VNF life cycle operation permission request from the VNFM 23 before the virtual resource allocation described later.

  In step C3, the SVRO 21 transmits a VNF life cycle operation permission response to the VNF life cycle operation permission request in step C2 to the VNFM 23.

  In step C4, the VNFM 23 transmits a virtual resource allocation request to the SVRO 21 (when the permission by the VNF life cycle operation permission request is obtained). This virtual resource allocation request includes RP (Or-Vnfm), IF (Virtualized resources management), and Op (Allocate Resource) shown in FIG. 10, and causes the SVRO 21 to execute allocation of virtual resources to the VNF. . The virtual resource allocation request may be in the same format for any type of computer, storage, network, etc., or the format may be different for each type.

In step C5, the SVRO 21 transmits a virtual resource allocation request to the VIM 22. This virtual resource allocation request includes RP (Or-Vim), IF (Virtualized resources management), and Op (Allocate Resource) shown in FIG. 10, and causes the VIM 22 to allocate virtual resources to the VNF. . Since the virtual resource to be allocated is reserved, the corresponding reservation ID is included in this virtual resource allocation request.
In step C51, the VIM 22 refers to the reservation ID included in the received virtual resource allocation request, and allocates resources to the VNF 52 to be managed by the VIM 22 itself via the NFVI-PoP 51.

In step C6, the VIM 22 transmits a virtual resource allocation response to the virtual resource allocation request in step C5 to the SVRO 21.
In step C7, the SVRO 21 transmits a virtual resource allocation response to the virtual resource allocation request in step C4 to the VNFM 23.

As illustrated in FIG. 11, in step C <b> 8, the VNFM 23 transmits a VNF setting request related to the deployment specific setting to the VNF 52. This VNF setting request includes an RP (Ve-Vnfm-vnf), an IF (VNF configuration management), and an Op (Get / Create / Set Config Object) shown in FIG. 11, and is unique to the VNF 52 itself. Then, the VNF 52 is made to deploy the VNF 52 itself on the NW configuration. The VNF setting related to the deployment specific setting can be executed based on information such as VNFD by a script, for example.
In step C9, the VNF 52 transmits a VNF setting response to the VNF setting request in step C8 to the VNFM 23.

In step C10, the VNFM 23 transmits a VNF setting request related to the APL specific setting to the EMS 25 for APL. This VNF setting request includes RP (Ve-Vnfm-em), IF (VNF configuration management), and Op (Get / Create / Set Config Object) shown in FIG. The APL is executed by the APL EMS 25 to set the APL in the VNF 52. The VNF setting related to the APL specific setting can be executed based on information such as VNFD by a script, for example.
When the APL EMS 25 receives the VNF setting request related to the APL specific setting, the APL is set in the VNF 52.
When the VNF setting related to the deployment specific setting and the VNF setting related to the APL specific setting are completed, the instantiation of the VNF 52 is completed, and the VNF instance ID serving as the identification information of this instance is issued.

  In step C11, the VNFM 23 transmits a VNF instantiation response to the VNF instantiation request in step C1 to the SVRO 21. The SVRO 21 acquires the VNF instance ID of the instantiated VNF 52 from the VNF instantiation response.

As shown in FIG. 12, in step C12, the SVRO 21 transmits a subscribe request to the VNFM 23. The subscribe request includes an RP (Or-Vnfm), an IF (VNF Lifecycle Change notification), and an Op (Subscribe) shown in FIG. 12. When a predetermined change operation regarding the performance of the VNF is performed, Notification of change is notified to SVRO21. For example, when there is a change in the life cycle of the VNF, the SVRO 21 specifies the VNF instance ID acquired in step C11 and notifies the VNFM 23 that the change of the life cycle of the corresponding VNF has been approved.
In step C13, the VNFM 23 transmits a subscribe response to the subscribe request in step C12 to the SVRO 21.

In step C14, the SVRO 21 reflects the change in the VNF performance approved in step C12 in VNFD, miniNSD, VLD, VNFFGD, etc., and registers it in the NFV instance file (21a). The NFV instance file (21a) has a function of registering a virtualized NW function instance, and is provided in the SVRO 21.
Thereafter, the SVRO 21 transmits to the E2EO1 the miniNS generation completion notification of Step B12 already described.
The requested miniNS can be constructed by the miniNS generation process shown in FIGS.
Note that the workflow unit 11 can generate a slice that implements the built miniNS.

According to the present embodiment, when an NS is constructed in an NW including a core NW that is a virtualized area and an access NW that is a non-virtualized area, a server that provides NS with input parameters for the selected catalog What is necessary is just to request information necessary to specify the system device and the NW system device. In addition, the constructed NS is appropriately managed by being updated or deleted using the life cycle.
Therefore, the life cycle management such as construction, update, and deletion of network services can be made quicker and more efficient, and the convenience of the network can be improved.

  Further, NS can be specifically designed by including elements such as NSD, VNFD, PNFD, VLD, and VNFFGD in the catalog.

  In addition, the resources of the server system device and the NW system device are generated after being reserved, so that they are required when instantiating the application (VNF) required for NS generation and for instantiating the NW connection. Resources can be generated reliably, and instantiation failure can be avoided even if multiple NS generation requests compete.

(Application of resource reservation)
In the present embodiment, the resource arbitration unit 14 first reserves (virtual) resources of the server system device by the SVRO 21 (steps A18 to A21 in FIG. 6), and then the (virtual) resources of the NW system device by the NWRO 31. The reservation is made (steps A27 to A29 in FIG. 7). By taking such an order, it is possible to flexibly select a base (such as a DC) for constructing a server system at the time of NS generation.

  Due to the nature of the NW configuration, many NW devices are connected to one server device, whereas only a few limited server devices are connected to one NW device. There are many. For this reason, if the NW system device that generates the resource is determined first, the limited server system device that is connected to the previously determined NW system device can only be selected as the server system device that generates the resource. There is no inconvenience. This inconvenience can be avoided if the order is as in this embodiment.

In this embodiment, the resource arbitration unit 14 generates and validates the NW connection from the resource reservation of the NW system device after the resource reservation is completed, and then the server The order of generating and validating the application from the resource reservation of the system device is taken (step B5 in FIG. 8 to step B12 in FIG. 9).
By adopting such an order, it is possible to ensure NW communication, and then start an application to perform NS communication tests simultaneously with NS generation.

  The resource arbitration unit 14 can set a resource reservation end time limit regarding the resource reservation of the server device and the resource reservation of the NW device. For example, for a resource for which the “reserved resource” flag is on, the resource arbitration unit 14 sets the “reserved resource” flag if the resource is not generated before the end deadline is reached. Turn off. As a result, it is possible to avoid resource occupation by reserved resources.

  Further, the resource arbitration unit 14 can set a resource reservation (acceptance) start date and time for the server system resource reservation and the NW system resource reservation. Thereby, the operator can perform an operation before the NS generation request date and time. As a result, the operator of the host apparatus U can make a strategic resource reservation with an eye on the future, and the operation of the host apparatus U can be reduced and the operator's work efficiency can be improved.

  In addition, reservation priority can be set by an input parameter for resource reservation of the server system device and resource reservation of the NW system device. Specifically, a priority flag for resource reservation is set in the resource information, and “highest priority” (high priority), “priority” (medium priority), “general” (low priority) are set in the priority flag. ). As a result, even if a reservation conflict occurs due to resource reservations from a plurality of operators, it is possible to secure a resource with a higher priority, and the NS construction can proceed smoothly. For example, a resource with a high priority may be a resource recognized as socially and economically important.

  Depending on the contents of the NS, when connecting the server system device and the NW system device, the number of endpoints (number of connection points) required by the server system resource (server resource) and the NW system resource ( There are cases where the number of end points (number of connection points) set in (NW resource) is different. At this time, the resource arbitration unit 14 obtains information necessary for setting the NW system resource from the VLAN (Virtual Local Area Network) -ID, the subnet range, the default gateway, or the like as the end point NW information required by the server system resource. Extraction can be performed to mediate the difference between the numbers of both ends. Thereby, the connection between the server system apparatus and the NW system apparatus having different numbers of endpoints can be collectively set. For example, four VNFs having one connection point can be collectively connected to a GW router having one connection point (an example of an NW system device).

(Application of catalog)
As an NS component, an instance is created when the NS is initially constructed (subscriber-independent portion), and additional instances are created as needed for each subscriber (for example, for each ISP) after the initial construction. Part (subscriber dependent part) exists. The subscriber-independent portion is, for example, a core NW slice (L3 (Layer 3) -VPN (Virtual Private Network) slice, etc.) common to each subscriber, which is a basic portion of E2E-NS, and the subscriber-dependent portion is For example, it can be an individual slice (L2 (Layer 2) -VPN slice or the like) corresponding to the access NW and subscriber-specific APL generated when a subscriber is added.

  In order to realize such NS, as a catalog element, instantiation that distinguishes whether a slice that realizes NS is a slice generated when NS is constructed or a slice that is additionally generated when a subscriber is added It has an element that describes an opportunity flag. By providing the instantiation opportunity flag, the workflow unit 11 can determine an appropriate instantiation opportunity for each part of the NS scheduled to be constructed.

(Other)
The management apparatus M of the present embodiment includes an input / output unit configured by an input / output I / F (interface), a storage unit configured by a hard disk, a flash memory, a RAM (Random Access Memory), and the like, a CPU (Central It is a computer equipped with hardware such as a control unit composed of a processing unit. For example, the control unit executes the above-described processing by expanding and executing a program (network management program) stored in the storage unit in the storage area of the storage unit. The management apparatus M according to the present embodiment can realize such cooperation between software and hardware.

  In the present embodiment, the catalog managed by the catalog management unit 13 is a catalog that includes five elements such as NSD, VNFD, PNFD, VLD, and VNFFGD. However, other elements may be added (for example, the instantiation trigger flag already described), or at least one of the five elements may be excluded. For example, if the application used for the NS to be built does not require cooperation with other applications, VNFFGD may not be included in the catalog.

A technique obtained by appropriately combining various techniques described in the present embodiment can also be realized.
The software described in this embodiment can be realized as hardware, and the hardware can also be realized as software.
In addition, hardware, software, flowcharts, and the like can be changed as appropriate without departing from the spirit of the present invention.

M Management device U Host device (external)
1 E2EO (Service Management Department)
2 Server system management unit 3 NW system management unit 4 OSS
11 Workflow unit 12 Request reception unit 13 Catalog management unit 14 Resource arbitration unit 15 DB
16 NS Lifecycle Management Department 17 DB
21 SVRO
22 VIM
23 VNFM
EMS for 24 H / W
25 EMS for APL
31 NWRO
32 NIM

Claims (9)

A management device that manages a core NW (Network) that is a virtualized area and an NS (Network Service) that is constructed in an NW that includes an access NW that is a non-virtualized area,
A service management unit for managing the NS;
A server device management unit for managing server devices arranged in the NW;
An NW system device management unit for managing the NW system device arranged in the NW,
The service management unit
A request accepting unit for obtaining an NS generation request including input parameters necessary for designating the server system device and the NW system device to be provided for the NS;
A catalog management unit for managing a catalog as a template of the NS;
A resource arbitration unit that arbitrates the resource of the server system device and the resource of the NW system device;
When the catalog is selected, a resource for the specified server system device and a resource for the specified NW system device are generated according to the input parameter, and a slice for realizing the NS is generated. A workflow part;
An NS life cycle management unit for managing the life cycle of the NS;
Comprising
A management device characterized by that. The catalog is
(1) a part describing the configuration of the NS, (2) a part describing an application used in the NS, (3) a part describing a physical function used in the NS, and (4) ) Including a portion describing a connection relationship between applications used in the NS; and (5) a portion describing a link used in the NS.
The management apparatus according to claim 1. The catalog includes an element that describes an instantiation opportunity flag that distinguishes whether a slice that realizes the NS is a slice that is generated when the NS is constructed or a slice that is additionally generated when a subscriber is added.
The management apparatus according to claim 1, wherein the management apparatus is a management apparatus. The resource arbitration unit
Reserving the resource of the server system device to be provided for the NS and the resource of the NW system device to be provided for the NS;
The management apparatus according to any one of claims 1 to 3, wherein the management apparatus is configured as described above. The resource arbitration unit
Reserving the resource of the server system device, and then reserving the resource of the NW system device,
After the resource reservation is completed, the NW connection is generated / validated from the resource reservation of the NW system device, and then the application is generated / validated from the resource reservation of the server system device,
The management apparatus according to claim 4. The resource arbitration unit
The start date and time of the resource reservation of the server system device, and the start date and time of the resource reservation of the NW system device,
A resource reservation end time limit for the server system device, and a resource reservation end time limit for the NW system device;
Can be set,
The management apparatus according to claim 4 or 5, wherein The input parameters are
Including priority for resource reservation of the specified server system device and resource reservation of the specified NW system device,
The management apparatus according to any one of claims 4 to 6, wherein the management apparatus is configured as described above. The resource arbitration unit
Mediating the difference between the number of endpoints required by the resource of the server system device and the number of endpoints set in the resource of the NW system device,
The management apparatus according to any one of claims 1 to 3, wherein the management apparatus is configured as described above. A network service management method in a management apparatus for managing a NS (Network Service) constructed in an NW including a core NW (Network) serving as a virtualized area and an access NW serving as a non-virtualized area,
The management device is
A request accepting step for obtaining an NS generation request including an input parameter necessary for designating a server system device and an NW system device for providing the NS;
A catalog selection step of selecting a catalog to be a template of the NS;
A resource arbitration step of arbitrating the resource of the server system device and the resource of the NW system device;
When the catalog is selected, a resource for the specified server system device and a resource for the specified NW system device are generated according to the input parameter, and a slice for realizing the NS is generated. A slice generation step;
Performing NS life cycle management step for managing the life cycle of the generated NS;
And a network service management method.

Images