JP2018196036A - Management device and network service management method - Google Patents

Abstract

To improve reliability of a network service at the time of the network service being changed.SOLUTION: A management device M for managing an NS (Network Service) constructed in an NW (Network) including a core NW, a virtualization area, and an access NW, a non-virtualization area, comprises: a service configuration information management unit 16 for managing service configuration information, configuration information on the NS; a service configuration history management unit 17 for managing a history of the service configuration information on the NS; an instance management unit 18 for managing an instance generated on the basis of the service configuration information; and a workflow unit 11 that when an NS change request for requesting a change of the constructed NS is acquired from the outside, changes the service configuration information on the basis of an input parameter included in the NS change request and caused the instance management unit 18 to protect an instance generated on the basis of the service configuration information before the change.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a management apparatus and a network service management method.

  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 changing a constructed network service is not mentioned. Conventionally, when a constructed network service is changed, it is assumed that a new network service is constructed and service migration is performed. However, such a service transition may cause an influence such as interruption of service continuation for the user, and may impair the reliability of the network service.

  In view of the above circumstances, an object of the present invention is to improve the reliability of a network service when the network service is changed.

  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 configuration information management unit that manages service configuration information that is the NS configuration information, a service configuration history management unit that manages a history of the NS service configuration information, and the service configuration information When an instance management unit that manages an instance generated based on the request and an NS change request that requests a change in the constructed NS are acquired from the outside, the service configuration information is obtained based on an input parameter included in the NS change request. The instance management unit changes the instance generated based on the service configuration information before the change. And a workflow unit for protecting the device.

  The invention according to claim 8 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 virtualization area and an access NW serving as a non-virtualization area. A management method, wherein the management device obtains an NS change request for requesting a change of the constructed NS from outside, and configuration information of the NS based on an input parameter included in the NS change request And changing the service configuration information, and protecting the instance generated based on the service configuration information before the change.

According to the first and eighth aspects of the invention, since the instance instantiated based on the service configuration information before the change is protected, communication of the service using the instance is ensured, and the user can Can be used continuously.
Therefore, it is possible to improve the reliability of the network service when the network service is changed.

  The invention according to claim 2 is the management device according to claim 1, wherein the workflow unit gives a version number to the changed service configuration information each time the service configuration information is changed. Thus, generation management of the service configuration information is performed.

  According to the invention described in claim 2, it is possible to provide a user with a service using an instance instantiated based on service configuration information to which a desired version number is assigned.

  The invention according to claim 3 is the management device according to claim 2, wherein the workflow unit assigns the specific version number to the service configuration information management unit and the service configuration history management unit. The read service configuration information is read, and the request is processed based on the read service configuration information.

  According to the third aspect of the present invention, even a request corresponding to service configuration information to which a specific version number is assigned can be reliably processed.

  The invention according to claim 4 is the management apparatus according to any one of claims 1 to 3, wherein the workflow unit is generated based on the service configuration information before the change. When there is a user who uses the instance, the abolition of the service configuration information before the change is prevented.

  According to the fourth aspect of the present invention, it is possible to prevent service interruption by a user who uses an instance created by instantiation based on service configuration information before change.

  The invention according to claim 5 is the management apparatus according to any one of claims 1 to 3, wherein the workflow unit is generated based on the service configuration information before the change. When there is a user who uses the specified instance, a business restriction is executed so that processing can be executed for a business for which permission is set in advance.

  According to the fifth aspect of the present invention, it is possible to promote the gradual winding of the service based on the service configuration information before the change (reduction of the usage amount of the old version service).

  The invention according to claim 6 is the management apparatus according to claim 5, wherein the workflow unit sets a restriction level for changing the work restriction.

  According to the sixth aspect of the present invention, it is possible to further promote the gentle winding of the service based on the service configuration information before the change.

  The invention according to claim 7 is the management apparatus according to claim 5 or 6, wherein the workflow unit notifies a predetermined party that the job restriction has been executed. Features.

  According to the invention described in claim 7, it is possible to surely notify related parties of the service based on the service configuration information after the change, and further promote the gradual winding of the service based on the service configuration information before the change. Can do.

  According to the present invention, it is possible to improve the reliability of a network service when the network service is changed.

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 flowchart which shows NS production | generation processing. It is a UML (Unified Modeling Language) figure which shows the specific example of service structure information. It is a state transition diagram of the life cycle of Product Order. It is a state transition diagram of the life cycle of Product Inventory. It is a flowchart which shows NS change processing.

  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 device M monitors these devices by collecting 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 apparatus M includes an E2EO (End to End Orchestrator) 1, a server system apparatus management section 2, and an NW system apparatus management section 3 (network apparatus management). Part).

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. 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, a service configuration information management unit 16, a service configuration history management unit 17, and an instance. And a management unit 18.

The request reception unit 12 acquires an NS generation request output from the upper apparatus U. 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.
In addition, the request reception unit 12 acquires an NS change request output from the upper apparatus U. The NS change request is information that causes the management apparatus M to change the constructed NS.

  The catalog management unit 13 manages a catalog as an NS template. The host device U can acquire a desired catalog from the catalog management unit 13. 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 system device and the resource of the NW system device. 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, for example, 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 workflow unit 11 manages a workflow for constructing an NS in response to an external request.

  The service configuration information management unit 16 manages service configuration information that is NS configuration information. For example, the service configuration information is stored in the DB 15. Details of the service configuration information will be described later.

  The service configuration history management unit 17 manages the history of service configuration information. The NS configuration history can be stored in the DB 15 as a result when, for example, generation management of service configuration information (described later) is executed.

  The instance management unit 18 manages an instance instantiated based on the constructed NS service configuration information (an instance generated based on the service configuration information). If there is an NS change, the instance management unit 18 manages the instantiated instance based on the NS service configuration information after the change, and instantiates based on the NS service configuration information before the change. Managed instances. The management information of these instances is stored in the DB 15, for example.

(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 Flavor includes information for identifying (nsFlavourID), information for maintenance (flavourKey), VNF information (ConstituentVNF), VL information (ConstituentVL), and VNFFG 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.

(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.

≪NS generation process≫
Next, NS generation processing when the management apparatus M generates NS at the time of NS construction 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.

  As shown in FIG. 4, first, the management apparatus M executes a resource reservation generation process (step S21). The resource reservation generation process is a process for reserving and generating a resource used for providing NS. Specifically, the management apparatus M acquires 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.

  Further, the E2EO1 of the management apparatus M 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.

  In addition, the SVRO 21 of the server system device management unit 2 of the management device M 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. As a result, in response to this request, a reserved virtual resource is generated in the VNF operating on the server system device specified by the resource reservation generation request from the higher-level device U.

Further, the NWRO 31 of the NW-system device management unit 3 of the management device M transmits an NW resource reservation generation request to the NIM 32. The NW resource reservation generation request is a request for ensuring that resources can be generated in the requested NW system device. As a result, in response to this request, a resource to be reserved is generated in the NW system device designated by the resource reservation generation request from the higher-level device U.
By the resource reservation generation process in step S21, it is possible to reliably generate a resource used for providing the NS to be constructed, and to prevent instantiation failure (see FIG. 3).

  Next, the management apparatus M executes NS generation processing (step S22). NS generation processing is processing for generating (constructing) an NS for an NW configuration in a state where resources are reserved. Specifically, the management apparatus M acquires 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.

  Further, the E2EO1 of the management apparatus M analyzes the received NS generation request and checks whether or not 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.

  The NWRO 31 of the NW system management unit 3 of the management device M transmits a resource generation request to the NIM 32. As a result, in response to this request, a resource is generated for the NW system managed by the NIM 32 itself.

  In addition, the SVRO 21 of the server system device management unit 2 of the management device M transmits a resource generation request to the VIM 22. In response to this request, a resource is generated for the server system device to be managed by the VIM 22 itself.

  In addition, the SVRO 21 of the server system device management unit 2 of the management device M transmits a VNF instantiation request to the VNFM 23. As a result, in response to this request, instantiation of the VNF operating on the server system apparatus engaged in the NS scheduled to be constructed is realized.

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

(Application of resource reservation)
The resource arbitration unit 14 can first make a reservation of (virtual) resources of the server system device by using the SVRO 21 and then make a reservation of (virtual) resources of the NW system device by using the NWRO 31. 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.

Further, after completing the resource reservation, the resource arbitration unit 14 generates and validates the NW connection from the resource reservation of the NW system device, and then generates and validates the application from the resource reservation of the server system device. The order of performing can be taken.
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.

(Instance management)
The orchestrator represented by the management apparatus M of the present embodiment creates an instance when there is a Product Order executed by Product Ordering defined by TMF (TeleManegement Forum) 622. The created instance is the instantiated VNF already described. The created instance is an NSR (Network Service Record) which is one of NFV (Network Function Virtualization) instance file types for registering virtualized NW function instances.

  The created instance is managed by Product Inventory. Product Inventry is defined in TMF637, for example, and is implemented as the instance management unit 18 in this embodiment.

  Various information used for managing instances in Product Inventry and the relationship between these information can be expressed in the UML diagram of FIG. 5 (expressed in the form of a composite structure diagram). In the present embodiment, the set of information shown in FIG. 5 is referred to as service configuration information. The service configuration information is stored in the DB 15 and is managed by the service configuration information management unit 16.

  The service configuration information shown in FIG. 5 includes, for example, a Product classifier 40a, a ProductSpecificationRef classifier 40b, a BillingAccountRef classifier 40c, a RealizingService classifier 40d, a ProductOfferingRef classifier 40e, a RealizingResource classifier 40f, and a ProductPrice classifier. 40g, Price classifier 40h, ProductRelationship classifier 40i, ProductRef classifier 40j, ProductCharacteristic classifier 40k, AgreementRef classifier 40l, and RelatedPartyRef classifier 40m.

The ProductSpecificationRef classifier 40b is associated with the Product classifier 40a by a ProductSpecification connector.
The BillingAccountRef classifier 40c is associated with the Product classifier 40a by the billingAccount connector.
The RealizingService classifier 40d is associated with the Product classifier 40a by the realizingService connector.
The ProductOfferingRef classifier 40e is associated with the Product classifier 40a by the productOffering connector.
The RealizingResource classifier 40f is associated with the Product classifier 40a by the realizingResource connector.
The ProductPrice classifier 40g is associated with the Product classifier 40a by the productPrice connector.
The Price classifier 40h is associated with the ProductPrice classifier 40g by the price connector.
The ProductRelationship classifier 40i is associated with the Product classifier 40a by the productRelationship connector.
The ProductRef classifier 40j is associated with the ProductRelationship classifier 40i by the product connector.
The ProductCharacteristic classifier 40k is associated with the Product classifier 40a by a productCharacteristic connector.
The AgreementRef classifier 40l is associated with the Product classifier 40a by an agreement connector.
The RelatedPartyRef classifier 40m is associated with the Product classifier 40a by the relatedParty connector.

  When the management apparatus M of the present embodiment changes the constructed NS, the service configuration information is changed, and various information (for example, the price classifier 40h) in FIG. 5 is changed. The service configuration information is changed by, for example, using Product Inventry Management API, which is an API for managing Product Inventry, by setting Modify as Action for Product Ordering API, which is API (Application Programming Interface) for Product Ordering. It can be executed by appropriately performing a PUT operation (update method for full replacement) and a PATCH operation (update method for partial replacement) for Product Inventry.

  The NS change request acquired from the upper apparatus U by the request receiving unit 12 includes the above PUT operation and PATCH operation as input parameters for changing the service configuration information. Changing the service configuration information in response to an NS change request does not change the catalog itself, but changes the values in the catalog. Therefore, compared to changing the catalog itself, the load associated with changing the NS is reduced. Can be

(NS lifecycle management)
In order to continue the service for the user, life cycle management such as NS update and deletion is performed. In the present embodiment, NS lifecycle management is handled by the instance management unit 18 (or the workflow unit 11 that controls the instance management unit 18). NS life cycle management can be classified into a product order life cycle and a product inventory life cycle.

[Product Lifecycle Management]
The life cycle of Product Order can be represented by the state transition diagram shown in FIG. The state transition diagram of FIG. 6 is “PRODUCTORDER LIFECYCLE” defined in TMF637 “Product_Ordering_API_REST_Specification”. As shown in FIG. 6, the life cycle of the Product Order is as follows: Acknowledged phase P11, Rejected phase P12, InProgress phase P13, Pending phase P14, Cancelled phase P15, Held phase P16, Completed phase P17, Failed. It can be expressed by transitions between the states such as phase P18 and partial phase P19.

  The Acknowledged phase P11 is a phase indicating that an order (related to NS change) is received and a notification is returned (to the upper apparatus U). Acknowledged phase P11 is reached when the order is successfully received (Yes in Accept Order branch B).

  The Rejected phase P12 is a phase indicating that order reception has been rejected. The Rejected phase P12 reaches when the order reception has failed (No in Accept Order branch B), and then the life cycle of the Product Order ends. The failure to receive an order includes, for example, check NG (order cannot be realized), order information error, and business rule incompatibility.

  The InProgress phase P13 is a phase indicating that the check that the order is feasible has been completed and the delivery of the service has started. In the rejected phase P12, when order processing is started in the Acknowledged phase P11 (Start Order treatment), when additional information is received in the Pending phase P14 (Extra information received), and when the problem is solved in the Held phase P16 ( Issue is solved).

  The Pending phase P14 is a phase indicating that an operation that must be completed in order to advance the order. The Pending phase P14 arrives when additional information is requested in the InProgress phase P13 (Ordering process needs extra information to continue).

  The Canceled phase P15 is a phase indicating that the order in circulation has been canceled normally. Canceled phase P15 arrives when additional information cannot be obtained in Pending phase P14 (Extra information cannot be supplied), when the problem cannot be solved in Held phase P16 (Issue is solved), and then Product The Order life cycle ends.

  The Held phase P16 is a phase indicating that the order cannot be advanced due to a problem (Issue) such as lack of equipment. The Held phase P16 arrives when the order process is blocked due to an issue in the InProgress phase P13.

  The Completed phase P17 is a phase indicating that the order is completed and the service is started. Completed phase P17 arrives when the order processing is completed (Order completely treated), and then the life cycle of Product Order ends.

  The Failed phase P18 is a phase indicating that all order items have failed and as a result, the entire order has failed. The Failed phase P18 is reached when all the order processes have failed (Order completely failed), and then the life cycle of the Product Order ends.

  The partial phase P19 is a phase indicating that some order items have failed and some have succeeded. The Partial phase P19 reaches when the order process is partially successful or failed (Order partially completed / failed), and then the life cycle of the Product Order ends.

[Product Inventry Lifecycle Management]
The life cycle of Product Inventry can be represented by a state transition diagram shown in FIG. The state transition diagram of FIG. 7 is “STATE MACHINE DIAGRAM FOR STATUS ATTRIBUTE ON PRODUCT” defined in TMF637 “Product_Inventory_Management_API_REST_Specification”. As shown in FIG. 7, the life cycle of Product Inventry includes a created phase P21, a pending active phase P22, an aborted phase P23, an active phase P24, a canceled phase P25, a suspended phase P26, and a terminated phase P27. It can be expressed by a transition between the states such as the pending terminated phase P28.

  The created phase P21 is a phase indicating that the service belongs when the system is newly entered and is not specified in any of the other phases P22 to P28. The created phase P21 is a phase indicating an initial state.

  The pending active phase P22 is a phase indicating that the customer (user) cannot use the service yet to be prepared. The pending active phase P22 arrives when activation is made in the created phase P21 (activate1).

  The aborted phase P23 is a phase indicating that the activation has been aborted due to technical or internal factors. The aborted phase P23 arrives when the activation is aborted (abort) in the pending active phase P22.

  The active phase P24 is a phase indicating that the customer can use the product. When the active phase P24 is activated in the created phase P21 (activate1) and activated in the pending active phase P22 (activate2), the customer can use the product in the suspended phase P26. Reach (re-enable).

  The cancelled phase P25 is a phase indicating that activation has been canceled due to a customer or a legal request. The cancelled phase P25 arrives when the activation is canceled in the pending active phase P22 (cancel).

  The suspended phase P <b> 26 is a phase indicating that the service is temporarily suspended due to unpaid fees or customer requests. The customer cannot use the service when in the suspended phase P26. The suspended phase P26 reaches when the service is suspended (suspended) in the active phase P24.

  The terminated phase P27 is a phase indicating that the customer cannot use the service. The terminated phase P27 reaches when the service is scheduled to be abolished in the active phase P24 (terminate1) and when the service is abolished in the pending terminated phase P28 (terminate2).

  The pending terminated phase P28 is a phase indicating that the service is scheduled to be discontinued but the customer can still use the product. The pending terminated phase P28 arrives when the service is scheduled to be canceled in the active phase P24 (terminate1).

The life cycle of Product Inventry can also be started after receiving a Product Order, for example. Specifically, the Product Inventory can be transitioned to the created phase P21 in the Product Inventry life cycle (FIG. 7) in response to the transition to the InProgress phase P13 of the life cycle of the Product Order (FIG. 6) (FIG. 7). Arrow A1). Also, Product Inventry processing is executed internally (see arrow A2 in FIG. 7), and when Product Inventry becomes active and transitions to active phase P24, Product Order is set to Completed phase P17 (FIG. 6). ).
Unlike the above, the life cycle of Product Inventory can be started in advance regardless of whether or not a Product Order is received, for example.

(Product Order processing for service configuration information)
When service configuration information is changed, specifically, when a PUT operation or PATCH operation is performed on Product Inventory, conventionally, a subscriber (user) of a target service and a subscription to a cooperative service linked to the service The service configuration information after the change is applied to the user (user) by default. However, for example, in the case of (1) transition to a service provision impossible state (example: transition to suspended phase P26 (FIG. 7)), (2) change accompanied by bandwidth reduction (example: 100M → 32M) Impact can occur.

Therefore, the management apparatus M of the present embodiment executes the following means 1 to means 3 when changing the service configuration information.
Means 1: Save service configuration information before change.
Means 2: Generation management in which the version number is automatically assigned to the service configuration information before the change is executed.
Means 3: The service configuration information after the last change is handled as the latest generation.

  The service configuration information management unit 16 is in charge of the means 1. The service configuration information management unit 16 transitions to the state of the Product Order life cycle (FIG. 6) and the state of the Product Inventry life cycle (FIG. 6) for the service configuration information before the change. It also stores whether it has transitioned to. The storage destination is DB15.

  The service configuration history management unit 17 is responsible for the means 2 and 3. Each time the service configuration information is changed, the service configuration history management unit 17 assigns a new version number, and the service configuration information to which the version number is assigned is stored in the DB 15 as a whole.

  When there is a new Product Order, it is possible to set which generation (version number) of service configuration information is used. The workflow unit 11 has parameters for enabling the operator of the higher-level apparatus U to set the generation of service configuration information.

  The workflow unit 11 may have a function of automatically determining which generation of service configuration information is used according to a predetermined condition. For example, when the Product Order acquired from the outside is a Product Order for an instance (managed by the instance management unit 18) associated with the old version of the service configuration information, the service configuration information management unit 16 automatically determines the old version of the service configuration. Information can be selected to provide services. Generally, when the Product Order acquired from the outside is a Product Order for an instance linked to a specific generation (arbitrary generation) of service configuration information, the service configuration information management unit 16 automatically determines the service of the specific generation Services can be provided by selecting configuration information.

Further, for example, in the case of changing the service configuration information accompanied by a bandwidth reduction (when the latest generation service configuration information is used), the workflow unit 11 dares to use the old version of the service configuration information to reduce the bandwidth. Automatic discrimination such as avoidance may be performed. Further, in the case of a change in service configuration information that accompanies a price change, the workflow unit 11 may automatically determine that the latest generation service configuration information is always used. In this way, it is possible to improve the convenience by using different generations according to the business.
If there is no condition for automatic determination, the workflow unit 11 may use the latest generation service configuration information.

(Avoid interruption of service continuation for users)
When changing the NS, when using the new version of the service configuration information after the change, the conventional technology abolishes the old version of the service configuration information before the change. At this time, in the prior art, the number of subscribers of the instantiated subscribers in the old version service (users using the instantiated VNFs used in the NS constructed based on the old version service configuration information) is related. First, the orchestrator executes the order process when receiving the abolished (deleted) Product Order from the outside, and transitions the old version of the service configuration information (Product Inventory) to terminated (Product Inventory (Fig. 7)) To the terminated phase P27). In the prior art, no processing is defined for subscribers already instantiated in the old version of the service, so when the service configuration information of the old version transitions to terminated, the service is deleted including the instantiated subscribers. The As a result, when the service configuration information is changed, a subscriber's service interruption (interruption of service continuation for the user) occurs, which may impair the reliability of the NS.

  The workflow unit 11 of the management apparatus M according to the present embodiment has an old version service subscriber guard function and an operation restriction function for the old version service as functions for preventing a subscriber from losing service.

The old version service subscriber guard function is a function that prevents transition of the old version service configuration information (Product Inventory) to terminated when there is a subscriber that has been instantiated in the old version service. In the DB 15 (FIG. 1), information on subscribers that have been instantiated with the old version of the service is registered, and the workflow unit 11 can confirm the presence or absence of the subscribers by referring to the DB 15. In addition, when there are subscribers that have been instantiated in the old version of the service, the workflow unit 11 makes a transition from the active phase P24 to the terminated phase P27 and pending terminated in the product inventory lifecycle of FIG. Transition from phase P28 to terminated phase P27 is prohibited.
The old version service subscriber guard function can protect the old version service subscriber from service interruption when the service configuration information is changed.

  The business restriction function for the old version service is the function that restricts the Product Order when there are subscribers that have been instantiated in the old version service, or when the old version service is linked with other services. It is. The restriction of Product Order means that the business input to the management apparatus M is classified into a business that permits processing and a business that prohibits processing, and only business that permits processing is executed.

For example, the workflow unit 11 of the management apparatus M presets a task for which processing is permitted by an input from the higher-level apparatus U. In other words, the workflow unit 11 employs a white list method in which the work permitted for processing is included in the white list. The workflow unit 11 can register a work permitted for processing in the DB 15. When a job that does not exist in the white list is requested from the upper apparatus U, it is treated as a job for which processing is prohibited and an error is returned. This error return can be realized by extending NgReason and defining it, for example.
Alternatively, a business that is not permitted to be processed can be set in advance. In other words, the workflow unit 11 can adopt a black list method in which a work that is not permitted to be processed is included in the black list. The workflow unit 11 can register a business that is not permitted to be processed in the DB 15. When a task that exists in the black list is requested from the host apparatus U, it is treated as a task that prohibits processing, and an error is returned. This error return can be realized by extending and defining NgReason, for example.

  The business restriction function for the old version service prohibits the addition of a new subscriber who intends to use the old version service. Further, the business restriction function for the old version service prohibits the linkage of the new service to the old version service, that is, the introduction of a new service that can be used by using the old version service. The workflow unit 11 performs processing related to these prohibitions.

  With the business restriction function for the old version service, it is possible to promote the gentle winding of the old version service (reduction of the usage amount of the old version service). As a result, when the service configuration information is changed, it is possible to reduce service interruptions for subscribers of the old version service.

In addition, the workflow unit 11 can set the restriction level of the work restriction for the old version service, and can appropriately change the restriction work according to the restriction level. For example, immediately after the introduction of the new version service, the subscriber is allowed to change to the old version service, but after n (natural number) years have passed since the introduction of the new version service, the restriction level is raised and the change to the use of the old version service is allowed. Without canceling, it is only possible to cancel subscribers of the old version service and cancel service linkage with the old version service.
By setting the restriction level, it is possible to further promote the gentle winding of the old service.

Further, the workflow unit 11 may have a notification function for notifying related parties that the business restriction by the business restriction function for the old version service has been executed. Here, examples of the related party include, but are not limited to, a subscriber who uses the old version service, a provider of a cooperation destination service linked to the old version service, a use service provider related to the old version service, and the like. As a means for notifying the notification function, for example, a well-known means such as a mail notification can be used. Further, the notification timing by the notification function can be a predetermined timing such as the start of business restriction or when the restriction level is changed, but is not limited thereto.
By the notification by the notification function, it is possible to surely notify related parties of the existence of the new version service, and it is possible to further promote the gradual winding of the old version service.

≪NS change processing≫
Next, NS change processing when the management apparatus M changes NS when NS is changed will be described.
As illustrated in FIG. 8, first, the management device M acquires an NS change request from the higher-level device U by the request reception unit 12 (step S31).

  Next, the management apparatus M causes the workflow unit 11 to change the service configuration information (see FIG. 5) corresponding to the current NS based on the input parameters included in the request receiving unit 12 (step S32).

  Next, the management apparatus M changes NS using the instance instantiated based on the changed service configuration information by the workflow unit 11 (step S33). The instance management unit 18 manages the instance instantiated based on the changed service configuration information. Further, when changing the NS, the instance instantiated based on the (current) service configuration information before the change is protected by the instance management unit 18. The protection of the instance instantiated based on the service configuration information before the change means that the service configuration information before the change is prevented from being abolished. Specifically, the old version service subscriber guard function described above, This applies to the business restriction function for the old version service.

  Next, the management apparatus M gives a version number to the changed service configuration information by the service configuration history management unit 17 (step S34). The version number assigned to the changed service configuration information is a version number that represents the latest generation. The service configuration history management unit 17 registers the version number assigned to the changed service configuration information in the DB 15 so as to be associated with the changed service configuration information.

  Next, the management apparatus M uses the service configuration information management unit 16 to store the changed service configuration information in the DB 15 (step S35). At this time, the version number assigned to the changed service configuration information is stored in the DB 15 so as to be associated with the changed service configuration information.

  Next, the management apparatus M uses the workflow unit 11 to execute the old service service restriction process (step S36). More specifically, the workflow unit 11 executes the old service subscriber guard function, the business restriction function for the old version service, the setting of the restriction level of the business restriction for the old version service, and the notification function for notifying the related parties. As a result, after the service configuration information is changed, the old version service is gently rolled up.

  According to the NS change process of FIG. 8, even if the service configuration information is changed, in order to protect the instance based on the service configuration information before the change, the service of the subscriber that has been instantiated with the service by the instance is continued. Can do.

  In addition, according to the NS change process of FIG. 8, version management (generation management) of service configuration information is performed, so that the service of the instantiated subscriber can be continued based on the version number. it can. Therefore, when a service based on service configuration information of a specific generation is requested, the service configuration information management unit 16 and the service configuration history management unit 17 perform service configuration information of a specific generation (given a specific version number). Can be read from the DB 15 and the request (order) can be processed based on the read service configuration information. At this time, an instance based on the service configuration information of the specific generation managed by the instance management unit 18 is used.

≪Summary≫
According to the present embodiment, since the instance instantiated based on the service configuration information before the change is protected, communication of the service using the instance is ensured, and the user continues to use the service. be able to.
Therefore, it is possible to improve the reliability of the network service when the network service is changed.

In addition, a service using an instance instantiated based on service configuration information to which a desired version number is assigned can be provided to the user.
Further, even a request corresponding to service configuration information to which a specific version number is assigned can be reliably processed.
In addition, it is possible to prevent service interruption by a user who uses an instance created by instantiation based on service configuration information before change.
In addition, it is possible to promote gentle winding of the service based on the service configuration information before the change.
Further, the service based on the service configuration information after the change can be surely notified to the parties concerned, and the gentle winding of the service based on the service configuration information before the change can be further promoted.

(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
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 Service Configuration Information Management Unit 17 Service Configuration History Management Unit 18 Instance Management Unit 21 SVRO
22 VIM
23 VNFM
EMS for 24 H / W
25 EMS for APL
31 NWRO
32 NIM

Claims (8)

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 configuration information management unit for managing service configuration information which is NS configuration information;
A service configuration history management unit for managing the history of NS service configuration information;
An instance management unit for managing an instance generated based on the service configuration information;
When an NS change request for requesting the change of the constructed NS is acquired from the outside, the service configuration information is changed based on an input parameter included in the NS change request, and based on the service configuration information before the change. A workflow unit that protects the instance generated by the instance management unit,
A management device characterized by that. The workflow part
The generation management of the service configuration information is performed by giving a version number to the changed service configuration information every time the service configuration information is changed.
The management apparatus according to claim 1. The workflow part
Causing the service configuration information management unit and the service configuration history management unit to read the service configuration information to which the specific version number is assigned, and process the request based on the read service configuration information;
The management apparatus according to claim 2. The workflow part
When there is a user who uses an instance generated based on the service configuration information before the change, the abolition of the service configuration information before the change is prevented.
The management apparatus according to any one of claims 1 to 3, wherein the management apparatus is configured as described above. The workflow part
When there is a user who uses an instance generated based on the service configuration information before the change, a business restriction is executed that allows processing to be performed for a business for which permission is set in advance.
The management apparatus according to any one of claims 1 to 3, wherein the management apparatus is configured as described above. The workflow part
Setting a restriction level for changing the work restriction;
The management apparatus according to claim 5. The workflow part
Notifying predetermined parties that the business restriction has been executed,
The management apparatus according to claim 5, 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
Obtaining an NS change request for requesting a change of the constructed NS from the outside;
Changing service configuration information, which is configuration information of the NS, based on input parameters included in the NS change request;
Performing the step of protecting the generated instance based on the service configuration information before the change,
And a network service management method.

Images