CN111726237A

CN111726237A - Method, NFVO, storage medium and system for processing NS priority

Info

Publication number: CN111726237A
Application number: CN201910205495.4A
Authority: CN
Inventors: 陈礼娟
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2019-03-18
Filing date: 2019-03-18
Publication date: 2020-09-29

Abstract

The invention provides a method for processing the priority of a Network Service (NS), an NFVO, a storage medium and a system, which can ensure that when the NS carrying a priority parameter and the NS not carrying the priority parameter simultaneously propose resource related applications to the NFV-MANO by managing the priority information of the NS and managing virtual resources for the NS according to the priority information of the NS, the NFV-MANO can normally process, and avoid the occurrence of phenomena of abnormal network services and the like caused by insufficient virtual resources of an NS instance due to the disordered management of the virtual resources of the NFV-MANO.

Description

Method, NFVO, storage medium and system for processing NS priority

Technical Field

The present invention relates to Network Function virtualization technologies, and more particularly, to a method for processing Network service NS priority, a Network virtualization Function orchestrator (NFVO), a storage medium, and a Network Function virtualization management and Orchestration system (NFV-MANO).

Background

Network Function Virtualization (NFV) is a software processing technology for carrying other Functions by using general hardware and Virtualization technology, and aims to reduce the cost of expensive equipment of a Network. The NFV decouples software and hardware and abstracts functions, so that functions of network equipment do not depend on special hardware any more, resources can be shared fully and flexibly, rapid development and deployment of new services are realized, and automatic deployment, elastic expansion, fault isolation, self-healing and the like are carried out based on actual service requirements.

As shown in fig. 1, the NFV system architecture defined by the European Telecommunications Standards Institute (ETSI) mainly includes: service Operation Support systems and Management Support platforms (OSS/BSS, Operation-Support System/Business Support System), Virtualized Network Functions (VNF), Network Function Virtualization Infrastructure (NFVI), and Network Function virtualization Management and Orchestration systems (NFV-MANO, VNF-Management and organization). The NFVI is mainly responsible for comprehensively virtualizing hardware resources such as calculation, storage and network and mapping the hardware resources into virtual resources; the VNF implements various conventional physical network functions by using software, runs on the NFVI, and uses virtual resources virtualized by the NFVI. The NFV-MANO is responsible for managing and orchestrating the relationships between VNFs and NFVI and the connectivity between VNFs and/or with other Physical Network Functions (PNFs).

The NFV-MANO includes a Virtualization Infrastructure Manager (VIM), a Virtual Network Function Manager (VNFM), and a Network Virtualization Function Orchestrator (NFVO). The VIM is responsible for controlling and managing virtualized resources; the VNFM is responsible for lifecycle management of the VNF; NFVO is responsible for orchestration and management of virtual infrastructure, as well as lifecycle management for Network Services (NS).

Network Slicing (Network Slicing) a logical Network that can flexibly provide one or more services as needed. Network slicing can be implemented with network services in the ETSI NFV system architecture, which is an important feature for NFV technology to be applied in the 5G phase. The management of network slices can be divided into two parts, namely service related part and virtual resource related part: the Management related to the service is realized by adding a Network Slice Management Function (NSMF) and a Network sub-Slice Management Function (NSSMF) at the OSS level; virtual resource-related management is implemented by the NFV-MANO, which manages network slices as network services within the NFV-MANO system.

In the 3GPP specification, a network slice priority parameter is also defined for a network slice, which is used to solve the problem of resource contention between different network slices in the same network. The network slice is managed by the NFV-MANO as a network service, a priority parameter is introduced for the network service, and when the network service carrying different priorities simultaneously puts forward related requirements of virtual resources, the NFVO responds to the requirements according to the priority order. The network service NS representing the network slice carries a priority parameter, the priority is added into the NS template as a new parameter in the NS template, the OSS/BSS uploads the template to the NFVO, and then a specific network service instance is deployed according to the NS template for providing the network service, and the network service instance has the same priority as the NS template.

Currently, a network slice is only one application form of a network service, and not all network services are network slices and carry priority parameters. In the actual networking application, some network services carry the priority parameters, and some network services do not carry the priority parameters. When the network service carrying the priority parameter and the network service not carrying the priority parameter simultaneously apply for resources to the NFV-MANO, the NFV-MANO may have a disturbed virtual resource management, which may cause the NS instance to generate network service abnormality due to insufficient virtual resources.

Disclosure of Invention

The method for processing the network service NS priority, the NFVO, the storage medium and the system provided by the embodiment of the invention mainly solve the technical problem that when a network service carrying a priority parameter and a network service NS not carrying the priority parameter simultaneously apply for resources related to the NFV-MANO in the prior art, the virtual resource management of the NFV-MANO may be disordered, and the phenomena of network service abnormity and the like caused by insufficient virtual resources of an NS instance are caused.

To solve the foregoing technical problem, an embodiment of the present invention provides a network virtualization function orchestrator NFVO, where the NFVO includes: the network service NS priority management module and the network service NS arranging management module;

the NS priority management module is used for managing the priority information of the network service NS;

and the NS arranging and managing module is used for managing the virtual resources for the NS according to the priority information of the NS.

The embodiment of the invention also provides a method for managing the network service NS priority, which comprises the following steps:

managing priority information of the network service NS;

and managing the virtual resources for the NS according to the priority information of the NS.

Embodiments of the present invention also provide a storage medium storing one or more programs, which are executable by one or more processors to implement the steps of the method for managing network services NS priority as described above.

The embodiment of the invention also provides a network function virtualization management and orchestration system NFV-MANO, wherein the NFV-MANO comprises a virtualization infrastructure manager VIM, a virtualization network function manager VNFM and the network virtualization function orchestrator NFVO;

the VIM is used for controlling and managing virtualized resources;

the VNFM is used to manage the lifecycle of the virtualized network function VNF;

NFVO is used to orchestrate and manage the virtual infrastructure and manage the life cycle of the NS.

The invention has the beneficial effects that:

according to the method for processing the network service NS priority, the NFVO, the storage medium and the system, virtual resources are managed for the NS according to the priority information of the NS by managing the priority information of the network service NS, so that when the network service carrying the priority parameter and the network service not carrying the priority parameter simultaneously apply resources to the NFV-MANO, the NFV-MANO can normally process, and the phenomena of network service abnormity and the like caused by insufficient virtual resources of an NS instance due to the disordered management of the virtual resources of the NFV-MANO are avoided.

Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.

Drawings

The invention will be further described with reference to the accompanying drawings and examples, in which:

FIG. 1 is a diagram of an ETSI NFV system architecture provided by the present invention;

FIG. 2 is a schematic basic flowchart of a method for managing network service NS priority according to an embodiment of the present invention;

fig. 3 is a schematic diagram of docking different OSS/BSSs by the NFVO according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of an NFVO provided in the second embodiment of the present invention;

fig. 5 is a diagram illustrating a specific management network service NS priority according to a third embodiment of the present invention;

fig. 6 is a diagram illustrating a specific management network service NS priority according to a fourth embodiment of the present invention;

fig. 7 is a diagram illustrating a specific management network service NS priority according to a fifth embodiment of the present invention;

fig. 8 is a diagram illustrating a specific management network service NS priority according to a sixth embodiment of the present invention;

FIG. 9 is a diagram illustrating the structure of an NFV-MANO according to a seventh embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The first embodiment is as follows:

in order to solve the problem that when a network service carrying a priority parameter and a network service not carrying the priority parameter simultaneously apply for resources to an NFV-MANO in the prior art, the NFV-MANO virtual resource management may be disordered, causing phenomena such as network service abnormity caused by insufficient virtual resources of an NS instance, and the like. Referring to fig. 2, fig. 2 is a basic flowchart of a method for managing NS priority of a network service according to this embodiment.

S201: managing priority information of the network service NS.

In this embodiment, NFVO may interface different OSS/BSSs, for example, please refer to fig. 3, the OSS/BSSs interfaced with NFVO are OSS/BSS1 and OSS/BSS2, respectively, where OSS/BSS1 supports the NS priority parameter, and OSS/BSS2 does not support the NS priority parameter. In practical application, the number of OSS/BSSs to be docked according to NFVO is the same, and may be three or four, for example.

In this embodiment, there are two cases of the priority information of the NS managed by the NFVO, one of which is that the priority information is null, that is, the OSS/BSS does not support the NS priority parameter, and the other of which is that the priority information is non-null, that is, the OSS/BSS supports the NS priority parameter.

In this embodiment, when the priority information of the NS is null, a priority may be allocated to the NS according to a first preset rule. In this embodiment, the allocating the priority to the NS according to the first preset rule at least includes the following three ways:

the first method is as follows: the NS is assigned priority directly by the NFVO.

In some examples of this embodiment, a fixed value may be provided by NFVO to assign priorities to each NS without priority, for example, NFVO directly assigns priorities of 1, 2, 3 to NS1, NS2, and NS3, respectively, where NS1, NS2, and NS3 may be from the same OSS/BSS or different OSS/BSS.

The second method comprises the following steps: and distributing corresponding priority for NS uploaded by each OSS/BSS according to each OSS/BSS strategy docked with the NFVO.

In some examples of this embodiment, a policy may be set by each OSS/BSS interfaced with the NFVO, and then a corresponding priority may be assigned to each uploaded NS according to its respective set policy. For example, referring to table one, the OSS/BSS interfacing with the NFVO has OSS/BSS1, OSS/BSS2, and OSS/BSS3, respectively, where the OSS/BSS1 defines a policy that the priorities assigned to NS1, NS2, and NS3 are 1, 2, and 3, respectively, the OSS/BSS2 defines a policy that the priorities assigned to NS1, NS2, and NS3 are 2, 1, and 3, respectively, and the OSS/BSS3 defines a policy that the priorities assigned to NS1, NS2, and NS3 are 3, 2, and 1, respectively; further, NFVO assigns priorities of 1, 2, and 3 to NS1, NS2, and NS3 in OSS/BSS1, priorities of 2, 1, and 3 to NS1, NS2, and NS3 in OSS/BSS2, and priorities of 3, 2, and 1 to NS1, NS2, and NS3 in OSS/BSS 3.

Watch 1

It should be noted that the table one is only an example, and in practical applications, the policy specifically established according to the OSS/BSS is the standard.

The third method comprises the following steps: and distributing the priority for the NS according to the external priority information transmitted by the interface correspondingly set to the NFVO.

In some examples of this embodiment, an interface corresponding to the NFVO may be set, an operation and maintenance person or other staff sets a corresponding priority for each NS according to an actual demand, and then transmits the set priority corresponding to each NS to the NFVO through the interface, and the NFVO allocates the corresponding priority to each NS, for example, the priorities set by the operation and maintenance person for NS1, NS2, and NS3 according to the actual demand are 1, 2, and 3, and are transmitted to the NFVO through the interface, and the priorities allocated by the NFVO for NS1, NS2, and NS3 are 1, 2, and 3, respectively.

It should be noted that, three exemplary manners for assigning priorities to the NS are provided herein, and the present invention is not limited to these three manners, and in fact, any manner that can implement assigning priorities to the NS is within the protection scope of the present invention, and in practical applications, the present invention can be flexibly adjusted according to specific application scenarios.

In this embodiment, there are two cases that the OSS/BSS has uploaded the NS template without priority to the NFVO and has not uploaded the NS template without priority to the NFVO, where the uploading of the NS template without priority to the NFVO by the OSS/BSS refers to receiving the NS template without priority that the OSS/BSS has uploaded before the NFVO is not upgraded; the non-priority-carrying NS template uploaded to the NFVO refers to the non-priority-carrying NS template received from the OSS/BSS after the NFVO is upgraded. In some examples of this embodiment, when the NFVO is not upgraded, an NS template that carries no priority and is uploaded by an OSS/BSS interfacing with the NFVO has been received, it may be understood that an NS instance that is instantiated by using the NS template runs in the system, and the NS instance carries no priority, and then, after the NFVO is upgraded, a priority is assigned to the NS according to a first preset rule for the NS template that carries no priority and the NS instance that is instantiated by using the NS template and is uploaded by the OSS/BSS and is received before the NFVO is upgraded. In some examples of this embodiment, when receiving an NS template without priority uploaded by an OSS/BSS interfacing with an NFVO after NFVO is upgraded, directly assigning a priority to the NS template without priority uploaded by the OSS/BSS according to a first preset rule, and it is understood that NS instances instantiated from the NS template with priority assigned also carry priorities.

In this embodiment, the priority information of the managed NS may be readjusted according to the second preset rule, and of course, the readjustment may be to allocate priority information to the NS according to the first preset rule only when the priority information of the NS is null, or only when the priority information of the NS is non-null, or to adjust both of them simultaneously. In this embodiment, readjusting the priority information of the managed NS according to the second preset rule at least includes the following two ways:

the first method is as follows: and establishing a strategy according to each OSS/BSS in butt joint with the NFVO, distributing a corresponding priority initial value for the NS uploaded by each OSS/BSS, and calculating the priority initial value and the priority initial value of the NS uploaded by the OSS/BSS to obtain the adjusted priority of each NS.

In some examples of this embodiment, a corresponding priority value (referred to as a priority initial value) may be allocated to the NS created by each OSS/BSS according to the importance weight of the accessed OSS/BSS, and then the NS priority value (referred to as a priority initial value) uploaded by each OSS/BSS and the priority initial value are calculated to obtain an adjusted priority of each NS, and the subsequent NFVO manages virtual resources for each NS according to the adjusted priority of each NS. It is understood that the calculation described herein may be simple addition, subtraction, multiplication, division or some other more complex calculation, and in practical applications, it needs to be flexibly adjusted according to a specific application scenario.

The second method comprises the following steps: and setting an interface corresponding to the NFVO and used for receiving the external priority information, wherein the NFVO allocates the corresponding external priority information to the NS managed by the NFVO, and the external priority information allocated to the NS is used as the priority adjusted by the NS.

In some examples of this embodiment, an interface corresponding to the NFVO may be set, where the interface may be the same as or different from the interface for allocating priorities to the NS according to the first preset rule, and an operation and maintenance person or other staff sets a corresponding priority for each NS according to an actual requirement, transmits the priority corresponding to each NS to the NFVO through the interface, and the NFVO replaces an original priority of the NS with the transmitted priority to obtain an adjusted priority of each NS, and a subsequent NFVO manages virtual resources for each NS according to the adjusted priority of each NS.

S202: and managing the virtual resources for the NS according to the priority information of the NS.

In this embodiment, managing virtual resources for the NS according to the priority information of the NS refers to that when the OSS/BSS initiates a request related to NS virtual resources to the NFVO, the NFVO processes the request related to virtual resources according to the priority information, that is, when the NFVO receives a plurality of requests, the requests are processed according to a priority order, a high-priority request is processed first, and a low-priority request is processed later; or when the available virtual resources are not able to satisfy all requests, the NFVO may preempt the virtual resources of the low-priority NS instance to satisfy the requests of the high-priority NS instance. It is to be appreciated that the NS virtualized resource related request includes, but is not limited to, NS lifecycle management operations as defined in the ETSI NFV specification, wherein the NS lifecycle management operations include NS instantiation, NS scaling, etc. operations related to virtual resources.

According to the method for managing the network service NS priority, provided by the embodiment of the invention, the virtual resources are managed for the NS according to the priority information of the NS by managing the priority information of the network service NS, so that when the network service carrying the priority parameter and the network service not carrying the priority parameter simultaneously propose resource related applications to the NFV-MANO, the NFV-MANO can normally process, and the phenomena of network service abnormity and the like caused by insufficient virtual resources of an NS instance due to the disordered management of the virtual resources of the NFV-MANO are avoided.

Example two:

an embodiment of the present invention provides a network virtualization function orchestrator NFVO, please refer to fig. 4, where the NFVO includes a network service NS priority management module 401 and a network service NS orchestration management module 402;

the NS priority management module 401 is configured to manage priority information of the network service NS;

the NS orchestration management module 402 is configured to manage virtual resources for the NS according to the priority information of the NS.

In this embodiment, NFVO may interface different OSS/BSSs, for example, NFVO interfaces OSS/BSSs 1 and OSS/BSS2, respectively, where OSS/BSS1 supports NS priority parameter and OSS/BSS2 does not support NS priority parameter. In practical application, the number of OSS/BSSs to be docked according to NFVO is the same, and may be three or four, for example.

In this embodiment, the NS priority information managed by the NS priority management module 401 has two situations, one is that the priority information is null, i.e., the OSS/BSS does not support the NS priority parameter, and the other is that the priority information is non-null, i.e., the OSS/BSS supports the NS priority parameter.

In this embodiment, when the priority information of the NS managed by the NS priority management module 401 is null, a priority may be assigned to the NS according to a first preset rule. In this embodiment, the allocating, by the NS priority management module 401 according to the first preset rule, the priorities to the NS at least includes the following three ways:

the first method is as follows: NS priority management module 401 assigns priorities directly to the NS.

In some examples of this embodiment, a fixed value may be provided by the NS priority management module 401 to assign priorities to each NS without priority, for example, the priorities assigned by the NS priority management module 401 directly to the NS1, NS2, and NS3 are 1, 2, 3, etc., where the NS1, NS2, and NS3 may be from the same OSS/BSS or from different OSS/BSSs.

The second method comprises the following steps: the NS priority management module 401 allocates a corresponding priority to the NS uploaded by each OSS/BSS according to each OSS/BSS policy docked with the NFVO.

In some examples of this embodiment, a policy may be set by each OSS/BSS interfaced with the NFVO, and the NS priority management module 401 may allocate a corresponding priority to each uploaded NS according to the policy set by each OSS/BSS. For example, referring to table two, the OSS/BSS interfacing with the NFVO has OSS/BSS1, OSS/BSS2, and OSS/BSS3, respectively, wherein the OSS/BSS1 defines a policy that the priorities assigned to NS1, NS2, and NS3 are 1, 2, and 3, respectively, the OSS/BSS2 defines a policy that the priorities assigned to NS1, NS2, and NS3 are 2, 1, and 3, respectively, and the OSS/BSS3 defines a policy that the priorities assigned to NS1, NS2, and NS3 are 3, 2, and 1, respectively; further, the NS priority management module 401 assigns priorities 1, 2, and 3 to NS1, NS2, and NS3 in the OSS/BSS1, assigns priorities 2, 1, and 3 to NS1, NS2, and NS3 in the OSS/BSS2, and assigns priorities 3, 2, and 1 to NS1, NS2, and NS3 in the OSS/BSS 3.

Watch two

OSS/BSS	NS1	NS2	NS3
				OSS/BSS1	1	2	3
OSS/BSS2	2	1	3
				OSS/BSS3	3	2	1
……	……	……	……

It should be noted that table two is only an example, and in practical applications, the policy specifically formulated according to the OSS/BSS is the standard.

The third method comprises the following steps: the NS priority management module 401 assigns a priority to the NS according to the external priority information transmitted by the interface set corresponding to the NFVO.

In some examples of this embodiment, an interface corresponding to the NFVO may be set, an operation and maintenance person or other staff sets a corresponding priority for each NS according to an actual demand, and then transmits the set priority corresponding to each NS to the NS priority management module 401 through the interface, the NS priority management module 401 allocates a corresponding priority to each NS, for example, the priorities set by the operation and maintenance person for NS1, NS2, and NS3 according to the actual demand are 1, 2, and 3, and are transmitted to the NFVO through the interface, and the priorities allocated by the NS priority management module 401 for NS1, NS2, and NS3 are 1, 2, and 3, respectively.

It should be noted that, three exemplary manners for assigning priorities to the NS are only used here, and the present invention is not limited to these three manners, and in fact, any manner that can implement the NS priority management module 401 to assign priorities to the NS is within the protection scope of the present invention, and in practical application, the present invention can be flexibly adjusted according to a specific application scenario.

In this embodiment, there are two cases that the OSS/BSS has uploaded the NS template without the priority to the NFVO and has not uploaded the NS template without the priority to the NFVO, where the fact that the OSS/BSS has uploaded the NS template without the priority to the NFVO indicates that the NFVO does not include the NS priority management module 401 before the NFVO is upgraded, the OSS/BSS has uploaded the NS template without the priority; the non-priority-carrying NS template uploaded to the NFVO means that the non-priority-carrying NS template uploaded by the OSS/BSS is received when the NFVO includes the NS priority management module 401 after being upgraded. In some examples of this embodiment, when the NFVO is not upgraded, an NS template that carries no priority and is uploaded by an OSS/BSS that interfaces with the NFVO is received, it is understood that there is an NS instance that is instantiated by using the NS template and runs in the system, and the NS instance carries no priority, and then after the NFVO is upgraded, the NS priority management module 401 allocates a priority to the NS template that carries no priority and is uploaded by the OSS/BSS that is received before the NFVO is upgraded, and the NS instance that is instantiated by using the NS template according to a first preset rule. In some examples of this embodiment, when receiving an NS template without priority uploaded by an OSS/BSS interfacing with an NFVO after NFVO is upgraded, the NS priority management module 401 directly assigns priority to the NS template without priority uploaded by the OSS/BSS according to a first preset rule, and it is understood that NS instances instantiated from the NS template with priority assigned also carry priority.

In this embodiment, the NS priority management module 401 may readjust the priority information of the managed NS according to the second preset rule, and of course, the readjustment may be to allocate priority information to the NS according to the first preset rule only when the priority information of the NS is null, or only when the priority information of the NS is non-null, or to adjust both. In this embodiment, the adjusting of the priority information of the managed NS by the NS priority management module 401 according to the second preset rule at least includes the following two ways:

the first method is as follows: the NS priority management module 401 allocates a corresponding priority initial value to the NS uploaded by each OSS/BSS according to each OSS/BSS policy set by the NFVO, and calculates the priority initial value and the priority initial value of the NS uploaded by the OSS/BSS to obtain the adjusted priority of each NS.

In some examples of this embodiment, the NS priority management module 401 may allocate a corresponding priority value (referred to as a priority initial value) to the NS created by each OSS/BSS according to the importance weight of the accessed OSS/BSS, further calculate the NS priority value (referred to as a priority initial value) uploaded by each OSS/BSS and the priority initial value to obtain the adjusted priority of each NS, and the subsequent NS scheduling management module 402 manages the virtual resource for each NS according to the adjusted priority of each NS. It is understood that the calculation may be simple addition, subtraction, multiplication, division or some other more complex calculation, and in practical applications, it needs to be flexibly adjusted according to a specific application scenario.

The second method comprises the following steps: an interface corresponding to the NFVO for receiving the external priority information is set, and the NS priority management module 401 allocates the corresponding external priority information to the NS managed by the NS priority management module, and uses the external priority information allocated to the NS as the adjusted priority of the NS.

In some examples of this embodiment, an interface corresponding to the NFVO may be set, where the interface may be the same as or different from the interface for allocating priority to the NS according to the first preset rule, and similarly, an operation and maintenance person or other staff sets a corresponding priority for each NS according to an actual requirement, transmits the priority corresponding to each NS to the NS priority management module 401 through the interface, the NS priority management module 401 replaces an original priority of the NS with the transmitted priority to obtain an adjusted priority of each NS, and the subsequent NS scheduling management module 402 manages virtual resources for each NS according to the adjusted priority of each NS.

In this embodiment, the NS orchestration management module 402 manages virtual resources for the NS according to the priority information of the NS means that when the OSS/BSS initiates a request related to NS virtual resources to the NFVO, and the NFVO processes the request related to virtual resources according to the priority information, that is, when the NFVO receives multiple requests, the NS orchestration management module 402 processes the requests according to a priority order, a high-priority request is processed first, and a low-priority request is processed later; or when all requests cannot be satisfied by the available virtual resources, NS orchestration management module 402 may preempt the virtual resources of the low priority NS instance to satisfy the requests of the high priority NS instance. It is to be appreciated that the NS virtualized resource related request includes, but is not limited to, NS lifecycle management operations as defined in the ETSI NFV specification, wherein the NS lifecycle management operations include NS instantiation, NS scaling, etc. operations related to virtual resources.

The NFVO provided by the embodiment of the invention comprises a network service NS priority management module 401 and a network service NS arranging management module 402, wherein the NS priority management module 401 manages the priority information of the network service NS, and the NS arranging management module 402 manages virtual resources for the NS according to the priority information of the NS, so that when the network service carrying the priority parameter and the network service not carrying the priority parameter simultaneously propose resource related applications to the NFV-MANO, the NFV-MANO can normally process, and the phenomena of network service abnormity and the like caused by insufficient virtual resources of an NS instance due to the disordered management of the NFV-MANO virtual resources are avoided.

Example three:

the embodiment of the present invention provides a specific process for managing network service NS priority, please refer to fig. 5 for illustration:

s501: the OSS/BSS1 is not null each time priority information is uploaded into the NS template of the NS priority management module 401.

In this step, the orchestration management module is instructed to process the NS instance-related virtual resource operations created by OSS/BSS1 in order of priority.

S502: the OSS/BSS2 is null each time priority information is uploaded to the NS template of the NS priority management module 401.

In this step, the orchestration management module is instructed to process the NS instance-related virtual resource operations created by OSS/BSS2 in chronological order.

S503: the NS priority management module 401 performs priority management on each uploaded NS, and assigns a priority to an NS whose priority information is empty according to a first preset rule.

In this step, NS priority management module 401 may provide a fixed default value, assigning a fixed value to each NS without priority; or providing a setting interface for operation and maintenance personnel to set default priority values in the system according to requirements; or according to the importance weight of the accessed OSS/BSS platform, allocating corresponding priority to the NS created by the OSS/BSS.

S504: the OSS/BSS1 initiates an NS virtual resource related request to NS orchestration management module 402.

In this step, the NS virtualization resource related request refers to an NS lifecycle management operation defined in ETSI NFV specification, and includes operations related to the virtual resource, such as NS instantiation, NS scaling, and the like.

S505: the OSS/BSS2 initiates an NS virtual resource related request to NS orchestration management module 402.

S506: the NS orchestration management module 402 processes the NS virtual resource related requests according to priority.

In this step, the NS orchestration management module 402 processes the virtual resource related requests according to priority, which means that when the NFVO receives multiple requests, the orchestration management module processes the requests according to priority ranking, where a high-priority request is processed first and a low-priority request is processed later; or when the available virtual resources are not able to satisfy all requests, the NFVO may preempt the virtual resources of the low-priority NS instance to satisfy the requests of the high-priority NS instance.

In this embodiment, NFVO interfaces OSS/BSS1 and OSS/BSS2, where OSS/BSS1 supports NS priority parameter, OSS/BSS2 does not support NS priority parameter, NS priority management module 401 adjusts priority information of all NSs, subsequent NS orchestration management module 402 processes virtual resource related request according to NS priority information, and the difference between the requirement and support capability for NS priority parameter between OSS/BSS1 and OSS/BSS2 does not affect the orchestration management module.

Example four:

the embodiment of the present invention provides a specific process for managing network service NS priority, please refer to fig. 6:

s601: after the NFVO supports the version operation of the NS priority information, the NS priority management module 401 allocates priorities to the NS template in the system before the upgrade and the NS instance instantiated from the NS template according to a first preset rule.

S602: the priority information in the NS template subsequently uploaded to NS priority management module 401 by the OSS/BSS is non-null.

S603: the OSS/BSS initiates an NS virtual resource-related request to NS orchestration management module 402.

In this step, the NS that needs to perform the virtual resource related operation may be an NS that has been deployed before the upgrade, or an NS that is newly uploaded after the upgrade.

S604: the NS orchestration management module 402 processes the NS virtual resource related requests according to priority.

In this step, the NS orchestration management module 402 processes the virtual resource related requests according to priority, which means that when the NFVO receives multiple requests, the requests are processed according to priority order, a high-priority request is processed first, and a low-priority request is processed later; or when the available virtual resources are not able to satisfy all requests, the NFVO may preempt the virtual resources of the low-priority NS instance to satisfy the requests of the high-priority NS instance.

In this embodiment, the NFVO supports that the NS priority belongs to a new function, and for a system already deployed and operated, the upgrade of the NFV-MANO does not affect the network service already deployed, so after the NFV-MANO upgrades from the version that does not support management of the NS priority information to the version that supports management of the NS priority information, the NS priority management module 401 adds the priority information to the NS before upgrade.

Example five:

the embodiment of the present invention provides a specific process for managing network service NS priority, please refer to fig. 7 for illustration:

s701: the OSS/BSS1 sets NS priorities according to the relative order between managed NS and uploads to the NS priority management module 401.

In this step, NFVO is instructed to process in priority order for NS instance related virtual resource operations created by OSS/BSS 1.

S702: the OSS/BSS2 sets NS priorities according to the relative order between managed NS and uploads to the NS priority management module 401.

In this step, NFVO is instructed to process in priority order for NS instance related virtual resource operations created by OSS/BSS 2.

S703: the NS priority processing module 401 adjusts the priority for the NS between different OSS/BSSs according to a second preset rule, and reorders the NS priority as needed.

In this step, the NS priority processing module 401 may allocate a corresponding priority starting value to the NS created by the OSS/BSS according to the importance weight of the accessed OSS/BSS platform, and a value obtained by adding (or subtracting) the uploaded NS priority original value and the priority starting value is used as a priority value for the NS to take effect in the NFVO; or a setting interface is provided for operation and maintenance personnel to manually adjust the priority value of the NS managed by the NFVO according to the requirement.

S704: the OSS/BSS1 initiates an NS virtual resource related request to NS orchestration management module 402.

In this step, the virtual NS virtualization resource related request refers to an NS lifecycle management operation defined in ETSI NFV specification, and includes operations related to an NS instantiation, a scaling of the NS, and the like.

S705: the OSS/BSS2 initiates an NS virtual resource related request to NS orchestration management module 402.

S706: the NS orchestration management module 402 processes the NS virtual resource related requests according to priority.

In this embodiment, NFVO interfaces with different OSS/BSSs and all support NS priority parameters, but OSS/BSS1 and OSS/BSS2 do not share service management information, and each sets NS priority according to a relative order between NS within its own platform, and these NS priority information cannot objectively reflect the relative priority between all NS within the NFV platform. The NS priority management module 401 adjusts priorities of all the NS, the subsequent NS orchestration management module 402 processes the virtual resource related request according to the adjusted priorities, and different criteria for setting NS priority parameters between the OSS/BSS1 and the OSS/BSS2 do not affect the orchestration management module.

Example six:

the embodiment of the present invention provides a specific process for managing network service NS priority, please refer to fig. 8:

s801: the priority information uploaded by the OSS/BSS to the NS template of the NS priority management module 401 is non-null.

In this step, the NFVO is instructed to process the corresponding NS instance-related virtual resource operations in a priority order.

S802: the priority information uploaded by the OSS/BSS to the NS template of the NS priority management module 401 is null.

In this step, the NFVO is instructed to process the virtual resource operations associated with the corresponding NS instance according to the chronological order.

S803: the NS priority management module 401 performs priority management on each uploaded NS, and assigns a priority to an NS whose priority information is empty according to a first preset rule.

In this step, NS priority handling module 401 may provide a fixed default value, assigning a fixed value to each non-prioritized NS; or providing a setting interface for operation and maintenance personnel to set default priority values in the system according to requirements; or different priority default values are set for different service types according to the policy agreed between the OSS/BSS and the NFVO.

S804: the OSS/BSS initiates an NS virtual resource-related request to NS orchestration management module 402.

S805: the NS orchestration management module 402 processes the NS virtual resource related requests according to priority.

In this embodiment, the OSS/BSS interfacing with the NFVO may manage and support multiple types of services, such as communication services, internet services, enterprise network services, vertical industry services, etc., each defined by a different specification, and the NS defined by the non-3 GPP specification does not have priority information. The NS part of this OSS/BSS upload to NFVO carries the NS priority parameter, and part does not carry the NS priority parameter. The NS priority management module 401 adjusts priority parameters of all the NS, and the subsequent NS orchestration management module 402 processes the virtual resource related request according to the priority, and whether different NS carry the priority parameters does not affect the NS orchestration management module.

Example seven:

an embodiment of the present invention provides a network function virtualization management and orchestration system NFV-MANO, please refer to fig. 9, where the NFV-MANO includes a virtualization infrastructure manager VIM 901, a virtualization network function manager VNFM 902, and a network virtualization function orchestrator NFVO 903 according to the second embodiment;

the VIM 901 is used to control and manage virtualized resources;

the VNFM 902 is used to manage the lifecycle of the virtualized network function VNF;

NFVO 903 is used to orchestrate and manage the virtual infrastructure and manage the life cycle of the NS.

It is noted that, for non-redundant description, the NFVO in the above embodiments is not fully described in the present embodiment, and it should be clear that the NFV-MANO in the present embodiment includes all the examples of the NFVO described in the above embodiments.

Embodiments of the present invention also provide a storage medium storing one or more programs, where the one or more programs are executable by one or more processors to implement the steps of the method for managing network service NS priority as described in the above embodiments.

The storage media includes volatile or nonvolatile, removable or non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, computer program modules or other data. Storage media includes, but is not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact disk Read-Only Memory), Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software (which may be implemented in program code executable by a computing device), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed over computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media), executed by a computing device, and in some cases may perform the steps shown or described in a different order than here. The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art. Thus, the present invention is not limited to any specific combination of hardware and software.

The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.

Claims

1. A network virtualization function orchestrator, NFVO, comprising: the network service NS priority management module and the network service NS arranging management module;

2. The network virtualization function orchestrator NFVO of claim 1, wherein the NS is assigned a priority according to a first preset rule when the NS priority information managed by the NS priority management module is null.

3. The network virtualization function orchestrator NFVO of claim 1, wherein the NS priority management module adjusts the priority of the NS managed according to a second preset rule.

4. The network virtualization function orchestrator NFVO of claim 2, wherein when the NS priority management module receives an NS template that carries no priority and is uploaded by a business operations support system and a management support platform OSS/BSS interfacing with the NFVO, the NS priority management module assigns a priority to the NS according to a first preset rule.

5. The network virtualization function orchestrator NFVO of claim 2, wherein when the NS priority management module detects that a business operations support system and management support platform OSS/BSS interfacing with the NFVO has uploaded an NS template that does not carry a priority and an NS instance instantiated from the NS template, the NS is assigned a priority according to a first preset rule.

6. The network virtualization function orchestrator NFVO of claim 2, wherein the assigning of the priority to the NS according to a first preset rule when the priority information of the NS managed by the NS priority management module is null comprises:

the NS priority management module directly allocates priority to the NS;

or the like, or, alternatively,

the NS priority management module allocates corresponding priorities to the NS uploaded by each OSS/BSS according to the strategy formulated by each OSS/BSS in butt joint with the NFVO;

or the like, or, alternatively,

and distributing the priority for the NS according to the external priority information transmitted by the interface correspondingly set to the NFVO.

7. The network virtualization function orchestrator NFVO of claim 3, wherein the NS priority management module adjusts the priority of the managed NS according to a second preset rule, comprising:

the NS priority management module allocates a corresponding priority initial value to the NS uploaded by each OSS/BSS according to a strategy formulated by each OSS/BSS in butt joint with the NFVO, and calculates the priority initial value and the priority initial value of the NS uploaded by the OSS/BSS to obtain the adjusted priority of each NS;

or the like, or, alternatively,

setting an interface corresponding to the NFVO and used for receiving external priority information, distributing the corresponding external priority information for the NS managed by the NS priority management module, and taking the external priority information distributed for the NS as the adjusted priority of the NS.

8. A method for managing network services, NS, priority, the method comprising:

managing priority information of the network service NS;

and managing virtual resources for the NS according to the priority information of the NS.

9. A storage medium storing one or more programs, the one or more programs being executable by one or more processors for performing the steps of the method for managing network services, NS, priority of claim 8.

10. A network function virtualization management, orchestration system, NFV-MANO, comprising a virtualization infrastructure manager, VIM, a virtualization network function manager, VNFM, and a network virtualization function orchestrator, NFVO, according to any of claims 1-7;

the VIM is used for controlling and managing virtualized resources;

the VNFM is to manage a lifecycle of a virtualized network function VNF;

the NFVO is used to orchestrate and manage the virtual infrastructure and manage the life cycle of the NS.