CN108429631B

CN108429631B - Method and device for instantiating network service

Info

Publication number: CN108429631B
Application number: CN201710081686.5A
Authority: CN
Inventors: 方海鹏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-02-15
Filing date: 2017-02-15
Publication date: 2021-01-15
Anticipated expiration: 2037-02-15
Also published as: WO2018149263A1; CN108429631A

Abstract

The embodiment of the invention provides a method and a device for instantiating a network service, relates to the technical field of communication, and can ensure the resource requirement of a high-priority network service as far as possible under the condition of insufficient resources and improve the service quality of the high-priority network service in an NFV (network file virtualization) system. The method comprises the following steps: the OSS receives a creation request of a first NS instance to be created, wherein the creation request is used for indicating the preemption priority of the first NS instance; when the resources required by creating the first NS instance are insufficient, the OSS determines a second NS instance allowing the resources to be preempted according to the preemption priority of the first NS instance; and the OSS sends a capacity reduction request of the second NS instance to the NFVO, wherein the capacity reduction request is used for indicating the NFVO to execute capacity reduction operation on the resources occupied by the second NS instance so as to create the first NS instance by using the resources released after the capacity reduction of the second NS instance.

Description

Method and device for instantiating network service

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a method and a device for instantiating a network service.

Background

As shown in fig. 1, an architecture diagram of a Network Function Virtualization (NFV) system is shown, the NFV system including: network function virtualization scheduling Node (NFVO), virtual network function management node (VNFM), virtual machine infrastructure management node (VIM), Operation Support System (OSS) or Business Support System (BSS), network element management node (EM), Virtual Network Function (VNF) node, and virtual network function infrastructure (NFVI) node.

In the NFV system, NFVO, VNFM, and VIM nodes constitute a management orchestrator (NFV-MANO) of the NFV system, where NFVO may also be referred to as a network function virtualization orchestrator. Specifically, the VNFM is responsible for lifecycle management of VNF instances, such as instantiating, expanding/contracting, querying, updating, terminating, and so on; the VIM is a management entrance of infrastructure and resources, provides resource management for the VNF instance, and comprises functions of configuration maintenance, resource monitoring, alarming, performance management and the like of infrastructure-related hardware and virtualized resources for the VNF instance; the NFVO can perform management and coordination operations on the VIM, and the NFVO is connected with all VIMs and VNFMs in the NFV system.

A Network Service (NS) instance usually consists of multiple VNF instances with specific connection relationships, and in the process of creating an NS instance (i.e., NS instantiation), the NFVO node needs to apply for corresponding resources through VNFM to deploy the VNF instance, and the VNFM allocates resources according to the principle of "first-come-last-come", that is, resources are sequentially allocated for different NS instances according to the order of each NS instantiation request received by the VNFM, so that in the case of insufficient resources, the VNFM feeds back a message of resource application failure to the NFVO, resulting in a failure in creating the NS instance. Then, for the NS instance creation process of the important tenant or service, the method of NS instantiation cannot effectively guarantee the network service quality.

Disclosure of Invention

The application provides a method and a device for instantiating a network service, which can ensure the resource requirement of a high-priority network service as much as possible under the condition of insufficient resources and improve the service quality of the high-priority network service in an NFV (network file virtualization) system.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, a method for instantiating a network service is provided, which includes: the OSS receives a creation request of a first NS instance to be created, wherein the creation request is used for indicating the preemption priority of the first NS instance; when the resources required for creating the first NS instance are insufficient, the OSS may determine a second NS instance that is allowed to preempt resources according to the preemption priority of the first NS instance, the preemption priority of the second NS instance being lower than the preemption priority of the first NS instance; and the OSS sends a capacity reduction request of the second NS instance to the NFVO, wherein the capacity reduction request is used for indicating the NFVO to execute capacity reduction operation on the resources occupied by the second NS instance.

Subsequently, after receiving the message sent by the NFVO that the capacity reduction operation of the second NS instance is completed, the OSS may send an instantiation request of the first NS instance to the NFVO, where the instantiation request is used to instruct the NFVO to perform an instantiation operation to create the first NS instance.

That is to say, when a first NS instance with a higher preemption priority is instantiated, if the resources for creating the first NS instance are insufficient, a part of the resources occupied by a second NS instance can be released by capacity reduction and preemption of a second NS instance with a lower preemption priority, so that the first NS instance is created using the released resources, which not only can improve the resource utilization, but also can ensure the resource demand of the high-priority network service as much as possible, thereby improving the service quality of the high-priority network service in the NFV system.

In one possible design, the create request includes service type information and tenant information of the first NS instance; a resource preemption policy is stored in the OSS, wherein the resource preemption policy comprises the service type priority of the first NS instance, the tenant priority and the corresponding relation between preemption priorities; after the OSS receives a creation request of a first NS instance to be created, the method further includes: the OSS determines the service type priority and the tenant priority of the first NS instance according to the service type information, the tenant information and the resource preemption strategy of the first NS instance; and the OSS determines the preemption priority corresponding to the service type priority and the tenant priority of the first NS instance as the preemption priority of the first NS instance according to the service type priority, the tenant priority and the resource preemption policy of the first NS instance.

In a possible design manner, the resource preemption policy further includes a corresponding relation between the preemption priority and the preemption authority; wherein the OSS determining a second NS instance that is allowed to preempt resources based on the preemption priority of the first NS instance, comprising: the OSS searches the resource preemption policy for a preemption priority lower than that of the first NS instance, and the preemption authority is a target service type priority and a target tenant priority which are allowed to be preempted; the OSS uses as the second NS instance an NS instance that satisfies the target traffic type priority and the target tenant priority.

In one possible design, the resource preemption policy further includes a preemption condition for indicating a performance index that the NS instance allowed to be preempted needs to meet; wherein the OSS regards as the second NS instance an NS instance that satisfies the target service type priority and the target tenant priority, including: the OSS takes at least one NS instance meeting the target service type priority and the target tenant priority as a target NS instance; the OSS determining whether each target NS instance satisfies the preemption condition; the OSS determines one NS instance from the target NS instances that satisfy the preemption condition as the second NS instance.

That is, by adding preemption conditions in the resource preemption policy, the conditions of the second NS instance of the preempted resource can be further limited, and the problem that the service quality of the second NS instance cannot be guaranteed after the second NS instance is excessively shrunk is avoided

In a possible design, the capacity reduction request of the second NS instance includes a resource change identifier, where the resource change identifier is used to indicate that the reason for performing the capacity reduction operation on the second NS instance is: the resources of the second NS instance are preempted.

In this way, the NFVO receiving the capacity reduction request may be triggered to save the resource information occupied by the current second NS instance. After the subsequent creation of the first NS instance is completed, the NFVO may also recover the preempted resource of the second NS instance according to the resource information.

In one possible design, after the OSS sends the capacity reduction request of the second NS instance to the NFVO, the method further includes: and the OSS sends an expansion request of the second NS instance to the NFVO, wherein the expansion request is used for indicating the NFVO to restore the preempted resources of the second NS instance.

In a second aspect, a method for instantiating a network service is provided, including: the NFVO receives a capacity reduction request of a second NS instance sent by an operation support system OSS, wherein the preemption priority of the second NS instance is lower than that of the first NS instance; and the NFVO executes a capacity reduction operation on the resources occupied by the second NS instance so as to create the first NS instance by using the resources released after the capacity reduction of the second NS instance.

In a possible design, after the NFVO performs the capacity reduction operation on the resource occupied by the second NS instance, the method further includes: the NFVO receives an instantiation request of the first NS instance sent by the OSS; the NFVO performs an instantiation operation to create the first NS instance.

In a possible design, before the NFVO receives the capacity reduction request of the second NS instance sent by the OSS, the method further includes: the NFVO receives a preemption identification of the first NS instance sent by the OSS, wherein the preemption identification is used for indicating that the first NS instance allows to preempt resources occupied by other NS instances; the NFVO determines that there are insufficient resources required to create the first NS instance; the NFVO keeps the session of the first NS instance for a preset period of time.

In one possible design, the NFVO performs an instantiation operation to create the first NS instance, including: the NFVO performs an instantiation operation according to the reserved session of the first NS instance to create the first NS instance.

Since resources of other NS instances may be preempted when the first NS instance is created, the NFVO need not release the issuance of the first NS instance this time of creation, but may reserve the session of the first NS instance for a preset period of time. If the resources required to create the first NS instance are sufficient within the preset time period, the NFVO may directly perform the instantiation operation using the already reserved session of the first NS instance, so that the creation time of the first NS instance may be shortened.

In a possible design, the capacity reduction request of the second NS instance includes a resource change identifier, where the resource change identifier is used to indicate that the reason for performing the capacity reduction operation on the second NS instance is: the resources of the second NS instance are preempted; before the NFVO performs the capacity reduction operation on the resource occupied by the second NS instance, the method further includes: the NFVO records the resource information occupied by the second NS instance; wherein, after the NFVO performs the instantiation operation to create the first NS instance, the method further comprises: the NFVO receives a capacity expansion request of the second NS instance sent by the OSS; and the NFVO restores the preempted resources of the second NS instance according to the recorded resource information occupied by the second NS instance.

In a third aspect, there is provided an OSS comprising: an acquisition unit, configured to receive a creation request of a first NS instance to be created, where the creation request is used to indicate a preemption priority of the first NS instance; a determining unit, configured to determine, when the resources required to create the first NS instance are insufficient, a second NS instance to which resources are allowed to be preempted according to a preemption priority of the first NS instance, where the preemption priority of the second NS instance is lower than the preemption priority of the first NS instance; a sending unit, configured to send a capacity reduction request of the second NS instance to a network function virtualization scheduling node NFVO, where the capacity reduction request is used to instruct the NFVO to perform a capacity reduction operation on resources occupied by the second NS instance, so as to create the first NS instance using resources released after the second NS instance is subjected to capacity reduction.

In a possible design manner, the obtaining unit is further configured to receive a message that the capacity reduction operation of the second NS instance is completed, where the message is sent by the NFVO; the sending unit is further configured to send an instantiation request of the first NS instance to the NFVO, where the instantiation request is used to instruct the NFVO to perform an instantiation operation to create the first NS instance.

In one possible design, the create request includes service type information and tenant information of the first NS instance; a resource preemption policy is stored in the OSS, wherein the resource preemption policy comprises the service type priority of the first NS instance, the tenant priority and the corresponding relation between preemption priorities; the determining unit is further configured to determine a service type priority and a tenant priority of the first NS instance according to the service type information, the tenant information, and the resource preemption policy of the first NS instance; and determining the preemption priority corresponding to the service type priority and the tenant priority of the first NS instance as the preemption priority of the first NS instance according to the service type priority, the tenant priority and the resource preemption policy of the first NS instance.

In a possible design manner, the resource preemption policy further includes a corresponding relation between the preemption priority and the preemption authority; the determining unit is specifically configured to: searching a preemption priority lower than that of the first NS instance in the resource preemption strategy, wherein the preemption authority is a target service type priority and a target tenant priority which are allowed to be preempted; one NS instance that satisfies the target traffic type priority and the target tenant priority is taken as the second NS instance.

In one possible design, the resource preemption policy further includes a preemption condition for indicating a performance index that the NS instance allowed to be preempted needs to meet; the determining unit is specifically configured to: taking at least one NS instance satisfying the target business type priority and the target tenant priority as a target NS instance; determining whether each target NS instance satisfies the preemption condition; one of the target NS instances that satisfies the preemption condition is determined to be the second NS instance.

In a possible design manner, the sending unit is further configured to send, to the NFVO, an expansion request of the second NS instance, where the expansion request is used to instruct the NFVO to restore the preempted resource of the second NS instance.

In a fourth aspect, there is provided an NFVO, comprising: an acquiring unit, configured to receive a capacity reduction request of a second NS instance sent by an OSS, where a preemption priority of the second NS instance is lower than a preemption priority of the first NS instance; and the capacity reduction unit is used for executing capacity reduction operation on the resources occupied by the second NS instance.

In a possible design, the NFVO further includes an instantiation unit, and the obtaining unit is further configured to receive an instantiation request of the first NS instance sent by the OSS; the instantiation unit is used for executing instantiation operation to create the first NS instance.

In a possible design manner, the NFVO further includes a determining unit and an executing unit, where the obtaining unit is further configured to receive a preemption identifier of the first NS instance sent by an OSS, where the preemption identifier is used to indicate that the first NS instance allows preemption of resources occupied by other NS instances; the determining unit is used for determining that the resources required for creating the first NS instance are insufficient; the execution unit is configured to reserve the session of the first NS instance for a preset time period.

In a possible design, the instantiation unit is specifically configured to perform an instantiation operation according to the reserved session of the first NS instance to create the first NS instance.

In a possible design, the capacity reduction request of the second NS instance includes a resource change identifier, where the resource change identifier is used to indicate that the reason for performing the capacity reduction operation on the second NS instance is: the resources of the second NS instance are preempted; the NFVO further comprises a recording unit and a capacity expansion unit, wherein the recording unit is used for recording resource information occupied by the second NS instance; the acquiring unit is further configured to receive a capacity expansion request of the second NS instance sent by the OSS; and the capacity expansion unit is used for recovering the preempted resource of the second NS instance according to the recorded resource information occupied by the second NS instance.

In a fifth aspect, there is provided an OSS comprising: a processor, a memory, a bus, and a communication interface; the memory is configured to store computer executable instructions, the processor is coupled to the memory via the bus, and when the OSS is running, the processor executes the computer executable instructions stored by the memory to cause the OSS to perform the method of NS instantiation as in any one of the first aspects.

In a sixth aspect, there is provided an NFVO, comprising: a processor, a memory, a bus, and a communication interface; the memory is configured to store computer-executable instructions, and the processor is coupled to the memory via the bus, and when the NFVO is running, the processor executes the computer-executable instructions stored in the memory to cause the NFVO to perform the method as instantiated by the NS according to any of the second aspects.

In a seventh aspect, a computer-readable storage medium is provided, which stores instructions that, when run on the NFVO or OSS, cause the NFVO or OSS to perform the method of NS instantiation of the above aspects.

In an eighth aspect, there is provided a computer program comprising instructions which, when executed by a computer, cause the computer to perform the method of NS instantiation of the above aspects.

In the embodiment of the present invention, the names of the OSS and the NFVO do not limit the devices themselves, and in an actual implementation, the devices may appear by other names. Provided that the functions of the respective devices are similar to those of the embodiments of the present invention, they are within the scope of the claims of the present invention and their equivalents.

In addition, the technical effects brought by any one of the design manners in the second aspect to the eighth aspect can be referred to the technical effects brought by different design manners in the first aspect, and are not described herein again.

These and other aspects of embodiments of the invention will be apparent from, and elucidated with reference to, the embodiments described hereinafter.

Drawings

FIG. 1 is a schematic diagram of a prior art NFV system;

FIG. 2 is a first interaction diagram illustrating a method for instantiating an NS according to an embodiment of the present disclosure;

fig. 3 is a second interaction diagram of a method for instantiating an NS according to an embodiment of the present invention;

fig. 4 is a third interaction diagram of a method for instantiating an NS according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of an OSS according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of an NFVO according to an embodiment of the present invention;

fig. 7 is a first hardware structure diagram of an OSS (or NFVO) according to an embodiment of the present invention;

fig. 8 is a schematic diagram of a hardware structure of an OSS (or NFVO) according to an embodiment of the present invention.

Detailed Description

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present invention, "a plurality" means two or more unless otherwise specified.

The embodiment of the invention provides a method for instantiating an NS, which can be applied to an NFV system shown in FIG. 1.

The OSS may configure different priorities, that is, service type priorities, for different services in advance, for example, the service type priority of the service a may be configured to be a high priority (which may be denoted as H), the service type priority of the service B may be configured to be a medium priority (which may be denoted as M), and the service type priority of the service C may be configured to be a low priority (which may be denoted as L).

When a tenant subscribes to an NS instance, the tenant may sign up its own priority through the BSS, that is, the tenant priority, for example, the tenant priority of tenant 1 is high (H), the tenant priority of tenant 2 is medium (M), and the tenant priority of tenant 3 is low (L). The tenant priority and the like information may be stored in a database (DB, data base).

The OSS may configure a preemption priority, a preemption right, a preemption condition (optional), and the like of the NS instance according to the service type priority and/or the tenant priority, to form a resource preemption policy. The preemption condition is used to indicate: preemption permissions are performance indicators that the NS instance allowed to be preempted needs to meet.

Illustratively, as shown in table 1, an example of a resource preemption policy provided by the embodiment of the present invention is provided. In table 1, when the tenant priority is H and the service type priority is H, the highest preemption priority may be configured, that is, the preemption priority is 1, and at this time, the resources of the NS instance are not allowed to be preempted; when the tenant priority is H and the service type priority is M, the preemption priority can be configured to be 2, and at the moment, the resources of the NS instance are not allowed to be preempted; when the tenant priority is M and the service type priority is M, the preemption priority can be configured to be 4, at this time, the resources of the NS instance are allowed to be preempted, but the preemption condition that the memory is larger than 1G needs to be met; … …, respectively; when the tenant priority is L and the service type priority is L, the preemption priority may be configured to be the lowest, that is, the preemption priority is 6, and at this time, the resources of the NS instance are allowed to be preempted without preemption conditions.

TABLE 1

That is, the resource preemption policy indicates preemption authorities corresponding to different preemption priorities, for example, the resource preemption policy shown in table 1 includes correspondence between preemption priority, service priority, tenant priority, preemption conditions, and preemption authority.

It should be noted that the preemption permission may also be configured by the tenant when signing up the priority of the tenant, and this is not limited in the embodiment of the present invention.

Subsequently, as shown in fig. 2, when it is needed to create an NS instance, for example, a first NS instance, the BSS sends a create request for creating the first NS instance to the OSS, where the create request may be used to indicate a preemption priority of the first NS instance, for example, a service type priority and a tenant priority of the first NS instance may be carried in the create request; furthermore, the OSS may interact with the NFVO to determine whether resources required to create the first NS instance are sufficient, and when the OSS determines that the resources required to create the first NS instance are insufficient, the OSS may determine, according to the preemption priority of the first NS instance indicated in the creation request, a second NS instance that allows the resources to be preempted (the preemption priority of the second NS instance is lower than the preemption priority of the first NS instance), for example, the OSS may determine, according to the service type priority and the tenant priority, the preemption priority of the first NS instance, and further determine, according to the resource preemption policy shown in table 1, that the preemption priority is lower than the preemption priority of the first NS instance, that the preemption right is the instance that is allowed to be preempted and that satisfies the preemption condition, as the second NS instance.

Furthermore, the OSS may further send, to the NFVO, a capacity reduction request of the second NS instance, that is, instruct the NFVO to perform a capacity reduction operation on resources occupied by the second NS instance, and release a part of resources occupied by the second NS instance, so that the released part of resources may be used to create the first NS instance, and then, when resources required for creating the first NS instance are sufficient, the OSS sends, to the NFVO, an instantiation request of the first NS instance, that is, instructs the NFVO to perform an instantiation operation, and finally creates the first NS instance.

That is to say, when instantiating the first NS instance with higher preemption priority, if the resources for creating the first NS instance are insufficient, the second NS instance with lower preemption priority can be reduced to release a part of the resources occupied by the second NS instance, so that the first NS instance is created using the released resources, which not only can improve the resource utilization, but also can ensure the resource demand of the high-priority network service as much as possible.

In addition, the condition of the second NS instance of the preempted resource can be further limited by adding the preemption condition in the resource preemption strategy, and the problem that the service quality of the second NS instance cannot be ensured after the second NS instance is excessively shrunk and contained is avoided.

It should be noted that, in the embodiment of the present invention, any one of the functional nodes or network elements involved in the NFV system, for example, the OSS, the BSS, the NFVO, the VNFM, the VIM, and the VNF, may be implemented by one entity device, or may be implemented by multiple entity devices together, and multiple functional nodes in the NFV system may be implemented by different entity devices, or may be implemented by the same entity device. It is to be understood that any functional node in the NFV system may be a logical functional module in an entity device, or may be a logical functional module composed of a plurality of entity devices.

In addition, in the embodiment of the present invention, the NFV system may be applied to a future fifth-Generation mobile communication (5rd-Generation, 5G) system, a Long Term Evolution (LTE) communication system, an LTE evolution communication system, such as an LTE-a (long term evolution advanced) system, a third-Generation mobile communication (3rd-Generation, 3G) system such as WCDMA, and the like, and the embodiment of the present invention is not limited.

In the following embodiments of the present invention, in order to more clearly describe the method for instantiating NS provided in the embodiments of the present invention, a logical function module is hereinafter described as an execution subject, and it can be understood by those skilled in the art that the logical function module needs to depend on hardware resources on an entity device where the logical function module is located when being specifically implemented.

As shown in fig. 3, the method for instantiating an NS provided in the embodiment of the present invention includes:

301. the OSS receives a create request for a first NS instance to be created.

For example, the OSS may receive a create request sent by the BSS for a first NS instance to be created.

Wherein the create request is to indicate a preemption priority for the first NS instance. For example, the creation request may include service type information and tenant information of the first NS instance.

Since the OSS configures different service type priorities for different services in advance, the OSS may determine a service type priority of the first NS instance according to the service type information, for example, the service type priority of the first NS instance is a high priority (H).

In addition, the OSS may also check whether the OSS stores the tenant priority of the tenant according to the received tenant information, for example, the tenant ID. If not, the OSS may obtain a tenant priority corresponding to the tenant ID from the DB, e.g., the tenant priority is a medium priority (M).

In this way, the OSS determines, according to the service type priority and the tenant priority of the first NS instance, the preemption priority and the preemption permission of the first NS instance in the resource preemption policy shown in table 1, that is, the preemption priority of the first NS instance is 3, and the preemption permission is not allowed to be preempted.

302. The OSS sends a first instantiation request of the first NS instance to the NFVO, wherein the first instantiation request comprises a preemption identification.

In step 302, after receiving the request for creating the first NS instance, the OSS sends a first instantiation request of the first NS instance to the NFVO, that is, triggers the NFVO to apply for a resource for the first NS instance, and performs an instantiation operation to create the first NS instance.

At this time, the first instantiation request includes a preemption identifier, and the preemption identifier is used for indicating whether the first NS instance allows to preempt the resources occupied by other NS instances. For example, the resources occupied by other NS instances are preempted when the preemption flag is "on", i.e., when the first NS instance is allowed to be created, and when the preemption flag is "off", i.e., when the first NS instance is not allowed to be created.

The following description will take the example of allowing the first NS instance to preempt the resources occupied by other NS instances when creating the first NS instance.

303. The NFVO determines whether the resources needed to create the first NS instance are sufficient.

After receiving the first instantiation request carrying the preemption identifier, the NFVO may determine, according to the preemption identifier, that resources occupied by other NS instances may be preempted when the first NS instance is created.

Further, the NFVO may interact with the VNFM to determine whether the resources needed to create the first NS instance are sufficient, according to existing NS instance creation flows.

If the resources required for creating the first NS instance are sufficient, the NFVO may perform NS instantiation operations according to the existing NS instance creation flow, and finally create the first NS instance.

If the resources required to create the first NS instance are insufficient, then the following steps 304 and 312 are performed.

304. If the resources needed to create the first NS instance are not sufficient, the NFVO reserves the session of the first NS instance for a preset period of time.

In step 304, if the resources required for creating the first NS instance are not enough, because the NFVO already knows, through the preemption identifier, that the resources of other NS instances can be preempted when creating the first NS instance, the NFVO does not need to directly release the session that creates the first NS instance this time, but can reserve the session of the first NS instance for a preset time period.

For example, the NFVO may start a timer, so that if the resources required for creating the first NS instance are sufficient within the preset time period set by the timer, and the NFVO re-receives the instantiation request of the first NS instance sent by the OSS, the NFVO may directly perform the instantiation operation using the already reserved session of the first NS instance without acquiring the session of the first NS instance again, so that the creation time of the first NS instance may be shortened.

Of course, if sufficient resources cannot be applied for the first NS instance within the preset time period set by the timer, the timer may automatically release the session and other information of the first NS instance after timeout.

305. The NFVO sends an answer response to the OSS indicating that the resources needed to create the first NS instance are insufficient.

Since the resources required to create the first NS instance are insufficient, after step 303, the response sent by the NFVO to the OSS carries the result of the first instantiation request, that is, the resources required to create the first NS instance are insufficient. It should be noted that the execution sequence between step 304 and step 305 is not limited by the embodiment of the present invention.

In addition, the response may also carry an identifier of the session continuation of the first NS instance, so that after receiving the identifier of the session continuation, the OSS may know that the NFVO does not release the session of the first NS instance.

Optionally, the response may also carry the size of the resource required to create the first NS instance. For example, the total amount of resources required to create the first NS instance is 50G, while the currently available resources are 40G in size; alternatively, the resource size required to create the first NS, i.e., 10G, in addition to the currently available resource size may be directly carried in the above-described response to reply.

306. And the OSS searches the preemption priority lower than that of the first NS instance in the resource preemption strategy according to the preemption priority of the first NS instance, and the preemption authority is the target service type priority and the target tenant priority which are allowed to be preempted.

307. The OSS uses the NS instance that satisfies the target traffic type priority and the target tenant priority as at least one target NS instance.

In step 301, the OSS determines a preemption priority and preemption authority for the first NS instance according to the service type information and tenant information carried in the creation request of the first NS instance. Then, in order to successfully create the first NS instance, the resources preempted by the first NS instance need to be further determined for subsequent use of the preempted resources to create the first NS instance.

Specifically, in step 306-. Further, NS instances that satisfy the target traffic type priority and the target tenant priority may be considered as at least one target NS instance.

Illustratively, as shown in table 1, the preemption priority for the first NS instance is still illustrated as 3. First, according to the resource preemption policy shown in table 1, the OSS may determine that the preemption priority lower than preemption priority 3 is: 4. 5 and 6. And, when the preemption priority is: 4. 5 or 6, the preemption authority is allowed to be preempted.

That is, any NS instance (excluding the first NS instance) with tenant priority M and service type priority M may be the target NS instance; any NS instance with the tenant priority of M and the service type priority of L can be used as a target NS instance; any NS instance with the tenant priority of L and the service type priority of L can be used as the target NS instance.

Since the service type priority and the tenant priority of each created NS instance are recorded in the OSS, the OSS may determine the target NS instance according to the service type priority and the tenant priority of each NS instance recorded.

308. The OSS determines a second NS instance from the at least one target NS instance.

First, if the resource preemption policy includes preemption conditions, the OSS further determines whether each of the at least one target NS instance satisfies the corresponding preemption conditions.

For example, as shown in table 1, if the tenant priority of the destination NS instance 1 is M and the service type priority is M, then the preemption conditions of the destination NS instance 1 are: when the memory of the target NS instance 1 is greater than 1G, preemption of the resources of the target NS instance 1 is allowed. At this time, the OSS may further query the memory size of the target NS instance 1, and if the memory size of the target NS instance 1 is greater than 1G, it may be used as the second NS instance, and if the memory size of the target NS instance 1 is less than or equal to 1G, it may not be used as the second NS instance.

Further, since there may be a plurality of target NS instances satisfying the preemption condition, in this case, the OSS may use the target NS instance with the lowest preemption priority as the second NS instance according to the preemption priority of the target NS instances. Of course, the OSS may also randomly select one of the target NS instances as the second NS instance, which is not limited in this embodiment of the present invention.

In addition, if the response obtained in step 305 carries the size of the resource required to create the first NS instance. Then, the OSS may further obtain resource sizes of the target NS instances, further calculate sizes of resources that can be released by each target NS instance, and finally, according to the sizes of the resources that can be released by each target NS instance, use one or more target NS instances that can satisfy the resource size required for creating the first NS instance as the second NS instance. In this way, the OSS may directly determine, for the first NS instance, a second NS instance that can meet its resource requirement, and accurately calculate the size of the resource released by the second NS instance when it subsequently performs the capacity reduction operation.

309. And the OSS sends a capacity reduction request of the second NS instance to the NFVO, wherein the capacity reduction request is used for indicating the NFVO to execute capacity reduction operation on the resources occupied by the second NS instance.

At this time, if the OSS determines that there are multiple second NS instances, the OSS may send a capacity reduction request to the NFVO for each second NS instance.

310. And the NFVO executes the capacity reduction operation on the resources occupied by the second NS instance.

And after the OSS determines the second NS instance which is preempted, sending a capacity reduction request of the second NS instance to the NFVO to indicate the NFVO which receives the capacity reduction request to execute capacity reduction operation on resources occupied by the second NS instance.

In one possible implementation, since the NS instances are all created through a Network Service Descriptor (NSD) file, a specification of resource capacity of the NS instance is recorded in the NSD file through a deployment specification ID, for example, a maximum specification of occupied resources of the NS instance 1 is 100G, and a minimum specification is 50G. And the OSS records the delivery _ flag _ ID of all the created NS instances, so the OSS may determine the minimum specification of the resource capacity of the second NS instance by looking up the delivery _ flag _ ID of the second NS instance.

Then, the minimum specification of the resource capacity of the second NS instance may be carried in the capacity reduction request of the second NS instance sent by the OSS to the NFVO. In this way, NFVO can scale the second NS instance to its minimum specification of resource capacity through a scaling operation. This may ensure proper operation of the second NS instance.

In another possible implementation manner, if in step 308, the OSS has already calculated the size of the resource released when the second NS instance performs the capacity reduction operation, the OSS may carry the size of the resource into the capacity reduction request and send the capacity reduction request to the NFVO, and the NFVO releases the resource with the same size as the resource through the capacity reduction operation.

Further, the capacity reduction request of the second NS instance may further carry a resource change identifier, where the resource change identifier is used to indicate that the reason for executing the capacity reduction operation on the second NS instance is: resources of the second NS instance are preempted.

In this way, the NFVO receiving the capacity reduction request may save the information of the resource occupied by the current second NS instance, for example, the resource occupied by the current second NS instance is 80G. Then, after the subsequent creation of the first NS instance is completed, the NFVO may also recover the preempted resource of the second NS instance according to the resource information.

311. The OSS sends a second instantiation request of the first NS instance to the NFVO to determine whether the resources required to create the first NS instance are sufficient.

After the NFVO performs the capacity reduction operation on the resources occupied by the second NS instance, the NFVO sends a message that the capacity reduction operation is completed to the OSS, and since after the NFVO performs the capacity reduction operation on the resources occupied by the second NS instance, a part of the resources originally occupied by the second NS instance are released, after receiving the message that the capacity reduction operation is completed, the OSS may continue to attempt to send a second instantiation request of the first NS instance to the NFVO, and the NFVO determines whether the resources required for creating the first NS instance at this time are sufficient, and feeds back the determined result to the OSS.

If the resources required to create the first NS instance are still insufficient, step 304 and step 310 may be repeated until sufficient resources are required to create the first NS instance.

If sufficient resources are needed to create the first NS instance at this point, step 312, described below, is performed.

312. If the resources required to create the first NS instance are sufficient, the NFVO performs an instantiation operation of the first NS instance to create the first NS instance.

As can be seen from the foregoing step 301 and 312, when the first NS instance with higher preemption priority is instantiated, if the resources for creating the first NS instance are insufficient, the second NS instance with lower preemption priority can be reduced to release a part of the resources occupied by the second NS instance, so that the first NS instance is created using the released resources, which not only can improve the resource utilization, but also can ensure the resource demand of the high-priority network service as much as possible.

Further, after the successful creation of the first NS instance, the second NS instance is operated to maximize non-interference with the normal operation of the preempted resource. The preempted resources of the second NS instance may also be restored through steps 401-402 described below, as shown in fig. 4.

401. The OSS sends a capacity expansion request for the second NS instance to the NFVO.

402. And the NFVO executes the capacity expansion operation of the second NS instance according to the recorded resource information occupied by the second NS instance.

403. And the NFVO sends a message of completing the capacity expansion operation to the OSS.

In step 401, there are two scenarios in which the OSS sends a capacity expansion request of the second NS instance to the NFVO.

One is, if the real-time resource occupation condition of each NS instance is not stored in the OSS, the OSS cannot determine the size of the resource available in the NFV system, and therefore, the OSS may periodically send a capacity expansion request of the second NS instance to the NFVO, and the NFVO determines whether the resource available in the NFV system is sufficient to recover the resource preempted by the second NS instance, where the capacity expansion request carries an identifier of the second NS instance.

If the real-time resource occupation condition of each NS instance is stored in the OSS, the OSS may determine whether the size of the resource available in the NFV system is greater than or equal to the size of the resource occupied by the second NS instance according to the real-time resource occupation condition of each NS instance, and if the size of the resource available in the NFV system is greater than or equal to the size of the resource occupied by the second NS instance, the OSS may be triggered to send a capacity expansion request of the second NS instance to the NFVO, where the capacity expansion request also carries an identifier of the second NS instance.

Of course, the capacity expansion request of the second NS instance may also carry the resource change identifier, which is not limited in this embodiment of the present invention.

Since, in step 310, the NFVO has stored the resource information occupied by the second NS instance before performing the capacity reduction operation, in step 402, after the NFVO receives the capacity expansion request of the second NS instance, if the size of the resource available in the NFV system is greater than or equal to the size of the resource occupied by the second NS instance, the NFVO may find the stored resource information occupied by the second NS instance according to the identifier of the second NS instance, and then, the NFVO performs the capacity expansion operation of the second NS instance according to the resource information occupied by the second NS instance, and expands the resource occupied by the second NS instance to the capacity specification before the capacity reduction of the second NS instance.

After NFVO completes the capacity expansion operation of the second NS instance, in step 403, a message of completion of the capacity expansion operation may be sent to the OSS.

The above-mentioned scheme provided by the embodiment of the present invention is introduced mainly from the perspective of interaction between network elements. It is to be understood that the OSS, NFVO, etc. described above contain hardware structures and/or software modules corresponding to the respective functions for implementing the functions described above. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.

According to the method example, the embodiments of the present invention may perform functional module division on OSS, NFVO, and the like, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In the case of dividing the functional modules by corresponding functions, fig. 5 shows a possible structural schematic diagram of the OSS involved in the above embodiment, where the OSS includes: an acquisition unit 51, a determination unit 52 and a transmission unit 53.

The obtaining unit 51 is configured to support the OSS to execute the process 301 in fig. 3 and the process 501 and 503 in fig. 5; the determining unit 52 is configured to support NFVO to execute the process 306-308 in fig. 3; sending unit 53 is configured to support NFVO to perform processes 302, 309, 311 in fig. 3, and process 401 in fig. 4. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the case of dividing each functional module by corresponding functions, fig. 6 shows a possible structural diagram of the NFVO according to the foregoing embodiment, where the NFVO includes: the device comprises an acquisition unit 61, a capacity reduction unit 62, an instantiation unit 63, a capacity expansion unit 64, a determination unit 65, an execution unit 66 and a recording unit 67.

Capacity reduction unit 62 is used to support NFVO to perform process 310 in FIG. 3; instantiation unit 63 is used to support NFVO to execute process 312 in fig. 3; the capacity expansion unit 64 is configured to support NFVO to execute the process 402 in fig. 4; determination unit 65 is configured to support NFVO to perform process 303 in fig. 3; execution unit 66 is configured to support NFVO to execute process 304 in fig. 3; the acquiring unit 61 is configured to support the NFVO to receive a capacity reduction request of the second NS instance sent by the OSS, where a preemption priority of the second NS instance is lower than a preemption priority of the first NS instance; if the resources required for creating the first NS instance are sufficient, receiving an instantiation request of the first NS instance sent by the OSS; receiving a preemption identification of a first NS instance sent by an OSS, wherein the preemption identification is used for indicating that the first NS instance allows to preempt resources occupied by other NS instances; receiving a capacity expansion request of a second NS instance sent by the OSS; the recording unit 67 is configured to support the NFVO to record resource information occupied by the second NS instance. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the case of integrated units, fig. 7 shows a possible structural diagram of the OSS (or NFVO) involved in the above-described embodiment. OSS (or NFVO) includes: a processing module 72 and a communication module 73. The processing module 72 is used to control and manage the actions of the OSS (or NFVO), for example, the processing module 72 is used to support the OSS (or NFVO) to perform the process 301-. The communication module 73 is used to support communication of OSS (or NFVO) with other network entities. The OSS (or NFVO) may also include a storage module 71 for storing program code and data of the OSS (or NFVO).

The Processing module 72 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the embodiment disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 73 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 61 may be a memory.

When the processing module 72 is a processor, the communication module 73 is a transceiver, and the storage module 71 is a memory, the OSS (or NFVO) according to the embodiment of the present invention may be the OSS (or NFVO) shown in fig. 8.

Referring to fig. 8, the OSS (or NFVO) includes: a processor 82, a transceiver 81, a memory 83, and a bus 84. Wherein, the transceiver 81, the processor 82 and the memory 83 are connected to each other by a bus 84; the bus 84 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.

Further, the embodiment of the present invention further provides a computer program, where the computer program includes instructions, and when the computer program is executed by a computer, the computer may enable the computer to perform the method for instantiating the associated NS in steps 301 and 312 or steps 401 and 403.

Further, an embodiment of the present invention also provides a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the method for NS instantiation in any of the above embodiments.

In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware or any combination thereof. When implemented using a software program, may take the form of a computer program product, either entirely or partially. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of network service NS instantiation, comprising:

an operation support system OSS receives a creation request of a first NS instance to be created, wherein the creation request is used for indicating the preemption priority of the first NS instance;

when the resources required for creating the first NS instance are insufficient, the OSS determines a second NS instance which allows the resources to be preempted according to the preemption priority of the first NS instance, wherein the preemption priority of the second NS instance is lower than that of the first NS instance;

and the OSS sends a capacity reduction request of the second NS instance to a network function virtualization scheduling Node (NFVO), wherein the capacity reduction request is used for indicating the NFVO to execute capacity reduction operation on the resources occupied by the second NS instance, so that the first NS instance is created by using the resources released after the second NS instance is subjected to capacity reduction.

2. The method according to claim 1, further comprising, after said OSS sending a capacity reduction request of said second NS instance to a network functions virtualization scheduling node, NFVO:

the OSS receives a message sent by the NFVO that the capacity reduction operation of the second NS instance is completed;

the OSS sends an instantiation request of the first NS instance to the NFVO, the instantiation request being used to instruct the NFVO to perform an instantiation operation to create the first NS instance.

3. The method of claim 1 or 2, wherein the create request includes service type information and tenant information for the first NS instance; a resource preemption policy is stored in the OSS, wherein the resource preemption policy comprises the service type priority of the first NS instance, the tenant priority and the corresponding relation between preemption priorities;

after the OSS receives a creation request of a first NS instance to be created, the method further includes:

the OSS determines the service type priority and the tenant priority of the first NS instance according to the service type information, the tenant information and the resource preemption strategy of the first NS instance;

and the OSS determines the preemption priority corresponding to the service type priority and the tenant priority of the first NS instance as the preemption priority of the first NS instance according to the service type priority, the tenant priority and the resource preemption policy of the first NS instance.

4. The method according to claim 3, wherein the resource preemption policy further comprises a correspondence between preemption priority and preemption authority;

wherein the OSS determining a second NS instance that is allowed to preempt resources based on the preemption priority of the first NS instance, comprising:

the OSS searches the resource preemption strategy for a preemption priority lower than that of the first NS instance, and the preemption authority is a target service type priority and a target tenant priority which are allowed to be preempted;

the OSS uses as the second NS instance one NS instance that satisfies the target traffic type priority and the target tenant priority.

5. The method of claim 4, wherein the resource preemption policy further comprises a preemption condition indicating a performance metric that the preempted NS instance is allowed to meet;

wherein the OSS regarding as the second NS instance an NS instance that satisfies the target traffic type priority and the target tenant priority comprises:

the OSS takes at least one NS instance meeting the target business type priority and the target tenant priority as a target NS instance;

the OSS determining whether each target NS instance satisfies the preemption condition;

the OSS determines one of the target NS instances that satisfies the preemption condition as the second NS instance.

6. The method according to any one of claims 1, 2, 4, and 5, wherein the capacity reduction request of the second NS instance includes a resource change identifier, and the resource change identifier is used to indicate a reason for performing a capacity reduction operation on the second NS instance as follows: resources of the second NS instance are preempted.

7. The method of claim 3, wherein the capacity reduction request of the second NS instance includes a resource change identifier, and the resource change identifier is used for indicating a reason for performing a capacity reduction operation on the second NS instance as follows: resources of the second NS instance are preempted.

8. The method as claimed in any one of claims 1, 2, 4, 5, and 7, further comprising, after the OSS sending the second NS instance's capacity reduction request to NFVO:

and the OSS sends an expansion request of the second NS instance to the NFVO, wherein the expansion request is used for indicating the NFVO to restore the preempted resource of the second NS instance.

9. The method of claim 3, after the OSS sends a capacity reduction request for a second NS instance to the NFVO, further comprising:

10. The method of claim 6, after an OSS sends a capacity reduction request of the second NS instance to an NFVO, further comprising:

11. A method of network service NS instantiation, comprising:

when the resources required by the creation of a first NS instance are insufficient, a network function virtualization scheduling Node (NFVO) receives a capacity reduction request of a second NS instance sent by an Operation Support System (OSS), wherein the preemption priority of the second NS instance is lower than that of the first NS instance;

and the NFVO executes a capacity reduction operation on the resources occupied by the second NS instance so as to create the first NS instance by using the resources released after the capacity reduction of the second NS instance.

12. The method of claim 11, after the NFVO performs a capacity reduction operation on the resources occupied by the second NS instance, further comprising:

the NFVO receives an instantiation request of the first NS instance sent by the OSS;

the NFVO performs an instantiation operation to create the first NS instance.

13. The method of claim 12, wherein before the NFVO receives the capacity reduction request of the second NS instance sent by the OSS, the method further comprises:

the NFVO receives a preemption identification of the first NS instance sent by the OSS, wherein the preemption identification is used for indicating that the first NS instance is allowed to preempt resources occupied by other NS instances;

the NFVO determining that insufficient resources are required to create the first NS instance;

the NFVO reserves the session of the first NS instance for a preset period of time.

14. The method of claim 13, wherein the NFVO performs an instantiation operation to create the first NS instance, comprising:

and the NFVO executes instantiation operation according to the reserved session of the first NS instance to create the first NS instance.

15. The method as claimed in any one of claims 11-14, wherein the capacity reduction request of the second NS instance includes a resource change identifier, and the resource change identifier is used to indicate a reason for performing the capacity reduction operation on the second NS instance as follows: preempting resources of the second NS instance;

before the NFVO performs the capacity reduction operation on the resource occupied by the second NS instance, the method further includes:

the NFVO records resource information occupied by the second NS instance;

wherein, after the NFVO performs an instantiation operation to create the first NS instance, further comprising:

the NFVO receives a capacity expansion request of the second NS instance sent by the OSS;

and the NFVO restores the preempted resources of the second NS instance according to the recorded resource information occupied by the second NS instance.

16. An operation support system, OSS, comprising:

an obtaining unit, configured to receive a creation request of a first NS instance to be created, where the creation request is used to indicate a preemption priority of the first NS instance;

a determining unit, configured to determine, when the resources required to create the first NS instance are insufficient, a second NS instance to which resources are allowed to be preempted according to a preemption priority of the first NS instance, where the preemption priority of the second NS instance is lower than the preemption priority of the first NS instance;

a sending unit, configured to send a capacity reduction request of the second NS instance to a network function virtualization scheduling node NFVO, where the capacity reduction request is used to instruct the NFVO to perform a capacity reduction operation on resources occupied by the second NS instance, so as to create the first NS instance using resources released after the second NS instance is subjected to capacity reduction.

17. The OSS of claim 16, wherein,

the obtaining unit is further configured to receive a message that the capacity reduction operation of the second NS instance is completed, where the message is sent by the NFVO;

the sending unit is further configured to send an instantiation request of the first NS instance to the NFVO, where the instantiation request is used to instruct the NFVO to perform an instantiation operation to create the first NS instance.

18. The OSS of claim 16 or claim 17, wherein the create request includes service type information and tenant information for the first NS instance; a resource preemption policy is stored in the OSS, wherein the resource preemption policy comprises the service type priority of the first NS instance, the tenant priority and the corresponding relation between preemption priorities;

the determining unit is further configured to determine a service type priority and a tenant priority of the first NS instance according to the service type information of the first NS instance, tenant information, and the resource preemption policy; and determining the preemption priority corresponding to the service type priority and the tenant priority of the first NS instance as the preemption priority of the first NS instance according to the service type priority, the tenant priority and the resource preemption policy of the first NS instance.

19. The OSS of claim 18, wherein the resource preemption policy further comprises a correspondence between preemption priority and preemption authority;

the determining unit is specifically configured to: searching a preemption priority lower than that of the first NS instance in the resource preemption strategy, wherein the preemption authority is a target service type priority and a target tenant priority which are allowed to be preempted; and using one NS instance meeting the target service type priority and the target tenant priority as the second NS instance.

20. The OSS of claim 19, wherein the resource preemption policy further comprises preemption conditions indicating performance metrics that the preempted NS instance is allowed to meet;

the determining unit is specifically configured to: taking at least one NS instance satisfying the target business type priority and the target tenant priority as a target NS instance; determining whether each target NS instance satisfies the preemption condition; determining one of the target NS instances that satisfies the preemption condition as the second NS instance.

21. The OSS according to any of claims 16, 17, 19, 20,

the sending unit is further configured to send, to the NFVO, an expansion request of the second NS instance, where the expansion request is used to instruct the NFVO to restore the preempted resource of the second NS instance.

22. The OSS of claim 18,

23. A network function virtualization scheduling node, NFVO, comprising:

an acquiring unit, configured to receive a capacity reduction request of a second NS instance sent by an operation support system OSS when resources required to create a first NS instance are insufficient, where a preemption priority of the second NS instance is lower than a preemption priority of the first NS instance;

and the capacity reduction unit is used for executing capacity reduction operation on the resources occupied by the second NS instance so as to create the first NS instance by using the resources released after the second NS instance is subjected to capacity reduction.

24. The NFVO of claim 23, wherein the NFVO further comprises an instantiation unit,

the obtaining unit is further configured to receive an instantiation request of the first NS instance sent by the OSS;

the instantiation unit is used for executing instantiation operation so as to create the first NS instance.

25. The NFVO of claim 24, wherein the NFVO further comprises a determining unit and an executing unit,

the acquiring unit is further configured to receive a preemption identifier of the first NS instance sent by the OSS, where the preemption identifier is used to indicate that the first NS instance allows preemption of resources occupied by other NS instances;

the determining unit is used for determining that the resources required for creating the first NS instance are insufficient;

the execution unit is configured to reserve the session of the first NS instance for a preset time period.

26. The NFVO of claim 25,

the instantiation unit is specifically configured to perform an instantiation operation according to the reserved session of the first NS instance, so as to create the first NS instance.

27. The NFVO of any one of claims 23-26, wherein the capacity reduction request of the second NS instance includes a resource change identifier, and wherein the resource change identifier is used to indicate a reason for performing a capacity reduction operation on the second NS instance as follows: preempting resources of the second NS instance; the NFVO further includes a recording unit and a capacity expansion unit,

the recording unit is used for recording the resource information occupied by the second NS instance;

the obtaining unit is further configured to receive a capacity expansion request of the second NS instance sent by the OSS;

and the capacity expansion unit is used for recovering the preempted resource of the second NS instance according to the recorded resource information occupied by the second NS instance.

28. A computer readable storage medium having instructions stored therein, which when run on an operations support system, OSS, according to any of claims 16-21, cause the OSS to perform a method of instantiating the network service, NS.

29. A computer-readable storage medium having stored therein instructions that, when run on a network function virtualization scheduling node, NFVO, according to any of claims 23-27, cause the NFVO to perform a method of instantiating the network service, NS.