U.S. patent application number 15/350598 was filed with the patent office on 2017-03-02 for network functions virtualization network system and data processing method, and apparatus.
The applicant listed for this patent is Huawei Technologies Co., Ltd.. Invention is credited to Anni Wei, Lei Zhu.
Application Number | 20170063598 15/350598 |
Document ID | / |
Family ID | 54479181 |
Filed Date | 2017-03-02 |
United States Patent
Application |
20170063598 |
Kind Code |
A1 |
Zhu; Lei ; et al. |
March 2, 2017 |
NETWORK FUNCTIONS VIRTUALIZATION NETWORK SYSTEM AND DATA PROCESSING
METHOD, AND APPARATUS
Abstract
Embodiments of the present invention provide a network functions
virtualization network system, method, and an apparatus. An NSO
node is connected to a first network node by using an operation
support-network service orchestration interface, the NSO node is
connected to an RO node by using a network service
orchestration-resource management orchestration interface, and the
NSO node is connected to a catalog; the RO node is connected to a
first network node by using an operation support-resource
management orchestration interface, the RO node is connected to a
VNFM node, the RO node is connected to a VIM node, and the RO node
is separately connected to the catalog, a network functions
virtualization instance, and a network functions virtualization
infrastructure resource. The system, method, and the apparatus are
used to deploy the network service orchestration function and the
resource management orchestration function.
Inventors: |
Zhu; Lei; (Beijing, CN)
; Wei; Anni; (Beijing, CN) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Huawei Technologies Co., Ltd. |
Shenzhen |
|
CN |
|
|
Family ID: |
54479181 |
Appl. No.: |
15/350598 |
Filed: |
November 14, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
PCT/CN2014/077581 |
May 15, 2014 |
|
|
|
15350598 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04L 41/20 20130101;
H04L 41/24 20130101; H04L 67/34 20130101; H04L 41/5041 20130101;
H04L 67/20 20130101; H04L 41/06 20130101; H04L 41/0893
20130101 |
International
Class: |
H04L 12/24 20060101
H04L012/24; H04L 29/08 20060101 H04L029/08 |
Claims
1. A network functions virtualization (NFV) network system,
comprising: a network service orchestration (NSO) node: a resource
management orchestration (RO) node; a first network node; a
virtualized network function manager (VNFM) node; a virtualized
infrastructure manager (VIM) node; a catalog; a network functions
virtualization (NFV) instance; and a network functions
virtualization infrastructure (NFVI) resource, wherein: the catalog
comprises a network service (NS) catalog and a virtualized network
function (VNF) catalog, the first network node is an operation
support system (OSS) or a third-party software system, the NSO node
is connected to the first network node by using an operation
support-network service orchestration interface, the NSO node is
connected to the RO node by using a network service
orchestration-resource management orchestration interface, the NSO
node is connected to the catalog, the RO node is connected to the
first network node by using an operation support-resource
management orchestration interface, the RO node is connected to the
VNFM node, the RO node is connected to the VIM node, and the RO
node is separately connected to the catalog, the network functions
virtualization instance, and the network functions virtualization
infrastructure resource.
2. The system according to claim 1, wherein the NFV network system
further comprises: N RO nodes and M VIM nodes, wherein N is an
integer greater than or equal to 1, and M is an integer greater
than or equal to 1; when N is equal to 1, and M is equal to 1, the
NSO node is connected to the RO node, and the RO node is connected
to the VIM node; when N is equal to 1, and M is greater than or
equal to 2, the NSO node is connected to the RO node, and the RO
node is connected to each of the VIM nodes; and when N is greater
than or equal to 2, and M is greater than or equal to 1, the NSO
node is connected to one of the RO nodes, the RO node is separately
connected to N-1 RO nodes, and each one of the N-1 RO nodes is
connected to at least one of the VIM nodes.
3. The system according to claim 1, wherein the NFV network system
further comprises: N RO nodes and M VIM nodes, wherein N is an
integer greater than or equal to 1, and M is an integer greater
than or equal to 1; when N is equal to 1, and M is equal to 1, the
NSO node is connected to the RO node, and the RO node is connected
to the VIM node; when N is equal to 1, and M is greater than or
equal to 2, the NSO node is connected to the RO node, and the RO
node is connected to each of the VIM nodes; and when N is greater
than or equal to 2, and M is greater than or equal to 1, the NSO
node is connected to each of the RO nodes, and each of the RO nodes
is connected to at least one of the VIM nodes.
4. The system according to claim 1, wherein the NFV network system
further comprises: a network service logic (NSL) catalog, wherein
the NSL catalog stores network service policy information, and the
network service policy information comprises logical data about
network service deployment, user-related data, and policy
information, and wherein the NSO node is connected to the NSL
catalog.
5. The system according to claim 1, wherein the NSO node has at
least one of network service functions, and the network service
functions comprise: automatically configuring a network service
requirement; managing uploading of a network service and a
virtualized network function (VNF) node; starting a network service
and managing a life cycle of a network service; managing VNF
instantiation in cooperation with the VNFM node; obtaining
information about an NFVI related to a network service and a VNF
node resource by performing a query by using the RO node or the
VNFM node; managing integrity and validity of a network service
instance during an execution cycle; managing a relationship between
a network service instance and a VNF instance; managing a topology
of a network service instance; managing automatic configuration of
a network service instance; managing policy information related to
a network service; and managing a fault of a network service.
6. The system according to claim 1, wherein the RO node has at
least one of a global resource management function or a coordinated
virtualized resource management allocation function, and the global
resource management function and the coordinated virtualized
resource management allocation function comprise: maintaining and
managing a resource network topological view; authenticating and
authorizing an NFVI resource request, wherein NFVI resource are
distributed in multiple VIM nodes; managing a network service
instance and distribution, reservation, and configuration of an
NFVI resource corresponding to a VNF instance; managing a VNF
instance, and managing a relationship between a VNF instance and an
NFVI resource allocated to the VNF instance; managing a policy and
managing execution of a network service instance and a VNF
instance; recording a view related to an NFVI resource used by a
VNF instance or a VNF instance group; and managing a fault of an
NFVI resource.
7. A network service orchestration (NSO) node, comprising: a
receiver, configured to receive a network service requirement
message sent by a first network node, wherein the network service
requirement message comprises a network service requirement, the
network service requirement is a parameter value required for
deploying a virtualized network function (VNF) node, and the first
network node is an operation support system (OSS) or a third-party
software system; a processer, configured to generate a second
configuration file according to the network service requirement and
a first configuration file, wherein the first configuration file is
a configuration file that describes the VNF node, and the second
configuration file is a configuration file that describes a network
service; a transmitter, configured to send a second configuration
file message to a resource management orchestration (RO) node,
wherein the second configuration file message comprises the second
configuration file; and wherein the receiver is further configured
to receive a second configuration file configuration response
message sent by the RO node.
8. The NSO node according to claim 7, wherein the processer is
further configured to: query a catalog, to obtain the first
configuration file from the catalog, wherein the NSO node is
connected to the catalog, and the catalog comprises a network
service (NS) catalog and a VNF catalog.
9. The NSO node according to claim 7, wherein: the transmitter is
further configured to send a catalog query request message to the
RO node; and the receiver is further configured to receive a
catalog query request response message sent by the RO node, wherein
the catalog query request response message comprises the first
configuration file.
10. The NSO node according to claim 8, wherein: the NSO node is
connected to two or more RO nodes; and the transmitter is further
configured to: send the second configuration file message to at
least one of the RO nodes according to a locally stored network
functions virtualization network resource global view, wherein: the
second configuration file comprises: network service-related
information, virtualized network node-related information,
virtualized network node feature-related information, and user
subscription-related information; the network service-related
information comprises: a network service type, a network service
capacity requirement, and a network scale policy; the virtualized
network node-related information comprises: a virtualized network
node type, a virtualized network node capacity requirement, a
virtualized network node deployment location, and a virtualized
network node interconnection link requirement; the virtualized
network node feature-related information comprises: a virtualized
network node channel quantity and a virtualized network node
service area setting; and the user subscription-related information
comprises: a user quantity, a network selection policy, and quality
of service.
11. The NSO node according to claim 8, wherein the NSO node is
connected to one RO node, the RO node is connected to at least one
RO node, and the transmitter is further configured to send the
second configuration file message to the RO node, wherein: the
second configuration file comprises: network service-related
information, virtualized network node-related information,
virtualized network node feature-related information, and user
subscription-related information; the network service-related
information comprises: a network service type, a network service
capacity requirement, and a network scale policy; the virtualized
network node-related information comprises: a virtualized network
node type, a virtualized network node capacity requirement, a
virtualized network node deployment location, and a virtualized
network node interconnection link requirement; the virtualized
network node feature-related information comprises: a virtualized
network node channel quantity and a virtualized network node
service area setting; and the user subscription-related information
comprises: a user quantity, a network selection policy, and quality
of service.
12. The NSO node according to claim 10, wherein the transmitter is
further configured to: send a network service instantiation request
message to the RO node.
13. The NSO node according to claim 12, wherein the receiver is
further configured to: receive a network service modification
requirement message sent by the first network node, wherein the
network service modification requirement message comprises a
network service modification requirement, and the network service
modification requirement is configuring the network service,
updating the network service, or terminating the network
service.
14. The NSO node according to claim 13, wherein the processer is
further configured to: obtain network service information from the
catalog and a network functions virtualization infrastructure
(NFVI) resource, wherein the network service information comprises
a state and load of the network service, and the NSO node is
separately connected to the catalog and the network functions
virtualization infrastructure resource; or obtain network service
information from the catalog and a network functions virtualization
infrastructure (NFVI) resource by using the RO node, wherein the
network service information comprises a state and load of the
network service.
15. The NSO node according to claim 14, wherein the transmitter is
further configured to: send a network service information query
response message to the first network node.
16. The NSO node according to claim 7, wherein the processer is
further configured to: manage a topology of a network service
instance; manage automatic configuration of the network service
instance; manage network service policy information; and manage a
fault of the network service.
17. A resource management orchestration (RO) node, comprising: a
receiver, configured to: receive a catalog query request message
sent by a network service orchestration (NSO) node; a processer,
configured to: query a catalog, to obtain a first configuration
file; and a transmitter, configured to: send a catalog query
request response message to the NSO node, wherein the catalog query
request response message comprises the first configuration file;
wherein the receiver is further configured to: receive a second
configuration file message sent by the NSO node, wherein the second
configuration file message comprises a second configuration file,
and the second configuration file is a configuration file that
describes a network service; and wherein the transmitter is further
configured to: send a second configuration file response message to
the NSO node.
18. The RO node according to claim 17, wherein the receiver is
further configured to: receive a network service instantiation
request message sent by the NSO node.
19. The RO node according to claim 17, wherein the processer is
further configured to: manage a fault of a network functions
virtualization infrastructure (NFVI) resource.
20. The RO node according to claim 17, wherein the transmitter is
configured to: send network functions virtualization infrastructure
(NFVI) resource fault information or network functions
virtualization infrastructure (NFVI) resource global view
information to a first network node, wherein the first network node
is an operation support system (OSS) or a third-party software
system.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of International
Application No. PCT/CN2014/077581, filed on May 15, 2014, the
disclosure of which is hereby incorporated by reference in its
entirety.
TECHNICAL FIELD
[0002] The present invention relates to the communications field,
and in particular, to a network functions virtualization network
system, a network functions virtualization network data processing
method, and an apparatus.
BACKGROUND
[0003] A network functions virtualization network is a
communications network that virtualizes a function of a physical
entity device in a communications network, that is, the function of
the physical entity device in the communications network is
implemented on at least one physical server by using only software
or by using a combination of software and hardware. The physical
entity device may be a radio access network device, a core network
device, or the like. A functional unit configured to implement the
physical entity device in the communications network on the at
least one physical server may be referred to as a virtualized
network node. A physical server may include at least one
virtualized network node, and a virtualized network node may be a
server group including multiple physical servers.
[0004] In the prior art, the network functions virtualization
network includes an operation support system (OSS) node, an element
management system (EMS) node, a virtualized network function (VNF)
node, a network functions virtualization orchestrator (NFVO) node,
a virtualized network function manager (VNFM) node, a virtualized
infrastructure manager (VIM) node, a network functions
virtualization infrastructure (NFVI) node, and the like. The OSS
node is an integrated operator system that supports information
resource sharing. The EMS node is a system that manages one or more
virtualized network nodes, and is configured to implement a fault
management, configuration management, accounting management,
performance management, security management (FCAPS) function for a
VNF. The VNF node is configured to implement a physical network
function (PNF), and may be a mobility management entity, a base
station, or the like. The NFVI node is configured to provide a
virtual resource for the VNF node. The NFVO node is configured to
implement a network service orchestration function and a resource
management orchestration function. The VNFM node is configured to
manage a life cycle of a VNF instance. The VIM node is configured
to control and manage a computing resource, a storage resource, a
network resource, and virtualized entities of the computing
resource, the storage resource, and the network resource.
[0005] However, an NFVO includes some functions of defining a
network service and abstracting a resource requirement of a VNF.
The network service belongs to the scope of network operation
maintenance and management, and resource management of an
abstracted network functions virtualization platform layer (an
NFVI) not only includes centralized global resource management, but
also includes a function of allocating a local virtualized resource
function in a coordinated manner. The two main function
requirements, a network service orchestration function and a
resource management orchestration function, are coupled and
completed in the same function entity NFVO, which causes a
difficulty in deployment. For example, it cannot be ensured that a
hierarchical resource management model of the NFVI and a planning
function of a network service instance are always deployed in a
same logic entity. For example, in a large-scale network
architecture, a granularity for deploying a resource management
orchestration function entity is much finer than a granularity for
deploying a network service orchestration function entity. In
addition, different from the resource management orchestration
function entity, the network service orchestration function entity
may be tightly coupled to an OSS for deployment.
SUMMARY
[0006] Embodiments of the present invention provide a network
functions virtualization network system, a network functions
virtualization network data processing method, and an apparatus,
which can make deployment of a network service orchestration
function and a resource management orchestration function of a
network functions virtualization network more flexible.
[0007] To achieve the foregoing objective, the following technical
solutions are used in the embodiments of the present invention.
[0008] According to a first aspect, a network functions
virtualization (NFV) network system is provided, including:
[0009] a network service orchestration (NSO) node, a resource
management orchestration (RO) node, a first network node, a
virtualized network function manager (VNFM) node, a virtualized
infrastructure manager (VIM) node, a catalog, a network functions
virtualization (NFV) instance, and a network functions
virtualization infrastructure (NFVI) resource, where the catalog
includes a network service (NS) catalog and a virtualized network
function (VNF) catalog, and the first network node is an operation
support system (OSS) or a third-party software system;
[0010] the NSO node is connected to the first network node by using
an operation support-network service orchestration interface, the
NSO node is connected to the RO node by using a network service
orchestration-resource management orchestration interface, and the
NSO node is connected to the catalog; and
[0011] the RO node is connected to the first network node by using
an operation support-resource management orchestration interface,
the RO node is connected to the VNFM node, the RO node is connected
to the VIM node, and the RO node is separately connected to the
catalog, the network functions virtualization instance, and the
network functions virtualization infrastructure resource.
[0012] With reference to the first aspect, in a first implementable
manner, the NFV network system further includes:
[0013] N RO nodes and M VIM nodes, where N is an integer greater
than or equal to 1, and M is an integer greater than or equal to
1;
[0014] when N is equal to 1, and M is equal to 1, the NSO node is
connected to the RO node, and the RO node is connected to the VIM
node;
[0015] when N is equal to 1, and M is greater than or equal to 2,
the NSO node is connected to the RO node, and the RO node is
connected to each of the VIM nodes; and
[0016] when N is greater than or equal to 2, and M is greater than
or equal to 1, the NSO node is connected to one of the RO nodes,
the RO node is separately connected to N-1 RO nodes, and each one
of the N-1 RO nodes is connected to at least one of the VIM
nodes.
[0017] With reference to the first aspect, in a second
implementable manner, the NFV network system further includes:
[0018] N RO nodes and M VIM nodes, where N is an integer greater
than or equal to 1, and M is an integer greater than or equal to
1;
[0019] when N is equal to 1, and M is equal to 1, the NSO node is
connected to the RO node, and the RO node is connected to the VIM
node;
[0020] when N is equal to 1, and M is greater than or equal to 2,
the NSO node is connected to the RO node, and the RO node is
connected to each of the VIM nodes; and
[0021] when N is greater than or equal to 2, and M is greater than
or equal to 1, the NSO node is connected to each of the RO nodes,
and each of the RO nodes is connected to at least one of the VIM
nodes.
[0022] With reference to the first implementable manner or the
second implementable manner, in a third implementable manner,
[0023] the NSO node is connected to the VNFM node.
[0024] With reference to any one of the first aspect or the first
implementable manner to the third implementable manner, in a fourth
implementable manner,
[0025] the NSO node is separately connected to the network
functions virtualization instance and the network functions
virtualization infrastructure resource.
[0026] With reference to any one of the first aspect or the first
implementable manner to the fourth implementable manner, in a fifth
implementable manner, the NFV network system further includes:
[0027] a network service logic (NSL) catalog, where the NSL catalog
stores network service policy information, and the network service
policy information includes logical data about network service
deployment, user-related data, and policy information, where the
NSO node is connected to the NSL catalog.
[0028] With reference to any one of the first aspect or the first
implementable manner to the fifth implementable manner, in a sixth
implementable manner, the NSO node has at least one of network
service functions, and the network service functions include:
[0029] automatically configuring a network service requirement;
[0030] managing uploading of a network service and a virtualized
network function (VNF) node;
[0031] starting a network service and managing a life cycle of a
network service;
[0032] managing VNF instantiation in cooperation with the VNFM
node;
[0033] obtaining information about an NFVI related to a network
service and a VNF node resource by performing a query by using the
RO node or the VNFM node;
[0034] managing integrity and validity of a network service
instance during an execution cycle;
[0035] managing a relationship between a network service instance
and a VNF instance;
[0036] managing a topology of a network service instance;
[0037] managing automatic configuration of a network service
instance;
[0038] managing policy information related to a network service;
and
[0039] managing a fault of a network service.
[0040] With reference to any one of the first aspect or the first
implementable manner to the sixth implementable manner, in a
seventh implementable manner, the RO node has at least one of a
global resource management function or a coordinated virtualized
resource management allocation function, and the global resource
management function and the coordinated virtualized resource
management allocation function include:
[0041] maintaining and managing a resource network topological
view;
[0042] authenticating and authorizing an NFVI resource request,
where NFVI resource are distributed in multiple VIM nodes;
[0043] managing a network service instance and distribution,
reservation, and configuration of an NFVI resource corresponding to
a VNF instance;
[0044] managing a VNF instance, and managing a relationship between
a VNF instance and an NFVI resource allocated to the VNF
instance;
[0045] managing a policy and managing execution of a network
service instance and a VNF instance;
[0046] recording a view related to an NFVI resource used by a VNF
instance or a VNF instance group; and
[0047] managing a fault of an NFVI resource.
[0048] According to a second aspect, a network functions
virtualization network data processing method is provided, where
the network functions virtualization network data processing method
is applied to a network service orchestration (NSO) node, and the
method includes:
[0049] receiving a network service requirement message sent by a
first network node, where the network service requirement message
includes a network service requirement, the network service
requirement is a parameter value required for deploying a
virtualized network function (VNF) node, and the first network node
is an operation support system (OSS) or a third-party software
system;
[0050] generating a second configuration file according to the
network service requirement and a first configuration file, where
the first configuration file is a configuration file that describes
the VNF node, and the second configuration file is a configuration
file that describes a network service;
[0051] sending a second configuration file message to a resource
management orchestration (RO) node, where the second configuration
file message includes the second configuration file; and
[0052] receiving a second configuration file configuration response
message sent by the RO node.
[0053] With reference to the second aspect, in a first
implementable manner, before the generating a second configuration
file according to the network service requirement and a first
configuration file, the method further includes:
[0054] querying a catalog, to obtain the first configuration file
from the catalog, where the NSO node is connected to the catalog,
and the catalog includes a network service (NS) catalog and a
virtualized network function (VNF) catalog.
[0055] With reference to the second aspect, in a second
implementable manner, before the generating a second configuration
file according to the network service requirement and a first
configuration file, the method further includes:
[0056] sending a catalog query request message to the RO node;
and
[0057] receiving a catalog query request response message sent by
the RO node, where the catalog query request response message
includes the first configuration file.
[0058] With reference to the first implementable manner or the
second implementable manner, in a third implementable manner, the
NSO node is connected to two or more RO nodes, and the sending a
second configuration file message to a resource management
orchestration (RO) node includes:
[0059] sending the second configuration file message to at least
one of the RO nodes according to a locally stored network functions
virtualization network resource global view, where the second
configuration file includes network service-related information,
virtualized network node-related information, virtualized network
node feature-related information, and user subscription-related
information, where the network service-related information includes
a network service type, a network service capacity requirement, and
a network scale policy; the virtualized network node-related
information includes a virtualized network node type, a virtualized
network node capacity requirement, a virtualized network node
deployment location, and a virtualized network node interconnection
link requirement; the virtualized network node feature-related
information includes a virtualized network node channel quantity
and a virtualized network node service area setting; and the user
subscription-related information includes a user quantity, a
network selection policy, and quality of service.
[0060] With reference to the first implementable manner or the
second implementable manner, in a fourth implementable manner, the
NSO node is connected to one RO node, the RO node is connected to
at least one RO node, and the sending a second configuration file
message to a resource management orchestration (RO) node
includes:
[0061] sending the second configuration file message to the RO
node, where the second configuration file includes network
service-related information, virtualized network node-related
information, virtualized network node feature-related information,
and user subscription-related information, where the network
service-related information includes a network service type, a
network service capacity requirement, and a network scale policy;
the virtualized network node-related information includes a
virtualized network node type, a virtualized network node capacity
requirement, a virtualized network node deployment location, and a
virtualized network node interconnection link requirement; the
virtualized network node feature-related information includes a
virtualized network node channel quantity and a virtualized network
node service area setting; and the user subscription-related
information includes a user quantity, a network selection policy,
and quality of service.
[0062] With reference to the third implementable manner or the
fourth implementable manner, in a fifth implementable manner, after
the receiving a second configuration file configuration response
message sent by the RO node, the method further includes:
[0063] sending a network service instantiation request message to
the RO node.
[0064] With reference to the fifth implementable manner, in a sixth
implementable manner, after the sending a network service
instantiation request message to the RO node, the method further
includes:
[0065] receiving a network service modification requirement message
sent by the first network node, where the network service
modification requirement message includes a network service
modification requirement, and the network service modification
requirement is configuring the network service, updating the
network service, or terminating the network service.
[0066] With reference to the sixth implementable manner, in a
seventh implementable manner, after the receiving a network service
modification requirement message sent by the first network node,
the method further includes:
[0067] obtaining network service information from the catalog and a
network functions virtualization infrastructure (NFVI) resource,
where the network service information includes a state and load of
the network service, and the NSO node is separately connected to
the catalog and the network functions virtualization infrastructure
resource; or
[0068] obtaining network service information from the catalog and a
network functions virtualization infrastructure (NFVI) resource by
using the RO node, where the network service information includes a
state and load of the network service.
[0069] With reference to the seventh implementable manner, in an
eighth implementable manner, after the querying for network service
information, the method further includes:
[0070] sending a network service information query response message
to the first network node.
[0071] With reference to any one of the second aspect or the first
implementable manner to the eighth implementable manner, in a ninth
implementable manner, after the receiving a second configuration
file configuration response message sent by the RO node, the method
further includes:
[0072] managing a topology of a network service instance;
[0073] managing automatic configuration of the network service
instance;
[0074] managing network service policy information; and
[0075] managing a fault of the network service.
[0076] According to a third aspect, a network functions
virtualization network data processing method is provided, where
the network functions virtualization network data processing method
is applied to a resource management orchestration (RO) node, and
the method includes:
[0077] receiving a catalog query request message sent by a network
service orchestration (NSO) node;
[0078] querying a catalog, to obtain a first configuration file;
sending a catalog query request response message to the NSO node,
where the catalog query request response message includes the first
configuration file;
[0079] receiving a second configuration file message sent by the
NSO node, where the second configuration file message includes a
second configuration file, and the second configuration file is a
configuration file that describes a network service; and
[0080] sending a second configuration file response message to the
NSO node.
[0081] With reference to the third aspect, in a first implementable
manner, after the receiving a second configuration file message
sent by the NSO node, the method further includes:
[0082] receiving a network service instantiation request message
sent by the NSO node.
[0083] With reference to the third aspect or the first
implementable manner, in a second implementable manner, the method
further includes:
[0084] managing a fault of an NFVI resource.
[0085] With reference to any one of the third aspect or the first
implementable manner to the second implementable manner, in a third
implementable manner, the method further includes:
[0086] sending NFVI resource fault info/Elation or NFVI resource
global view information to a first network node, where the first
network node is an operation support system (OSS) or a third-party
software system.
[0087] According to a fourth aspect, a network service
orchestration (NSO) node is provided, including:
[0088] a first receiving unit, configured to receive a network
service requirement message sent by a first network node, where the
network service requirement message includes a network service
requirement, the network service requirement is a parameter value
required for deploying a virtualized network function (VNF) node,
and the first network node is an operation support system (OSS) or
a third-party software system;
[0089] a generation unit, configured to generate a second
configuration file according to the network service requirement and
a first configuration file, where the first configuration file is a
configuration file that describes the VNF node, and the second
configuration file is a configuration file that describes a network
service;
[0090] a first sending unit, configured to send a second
configuration file message to a resource management orchestration
(RO) node, where the second configuration file message includes the
second configuration file; and
[0091] a second receiving unit, configured to receive a second
configuration file configuration response message sent by the RO
node.
[0092] With reference to the fourth aspect, in a first
implementable manner, the NSO node further includes:
[0093] a query unit, configured to query a catalog, to obtain the
first configuration file from the catalog, where the NSO node is
connected to the catalog, and the catalog includes a network
service (NS) catalog and a virtualized network function (VNF)
catalog.
[0094] With reference to the fourth aspect, in a second
implementable manner, the NSO node further includes:
[0095] a second sending unit, configured to send a catalog query
request message to the RO node; and
[0096] a third receiving unit, configured to receive a catalog
query request response message sent by the RO node, where the
catalog query request response message includes the first
configuration file.
[0097] With reference to the first implementable manner or the
second implementable manner, in a third implementable manner, the
NSO node is connected to two or more RO nodes, and the first
sending unit is further configured to:
[0098] send the second configuration file message to at least one
of the RO nodes according to a locally stored network functions
virtualization network resource global view, where the second
configuration file includes network service-related information,
virtualized network node-related information, virtualized network
node feature-related information, and user subscription-related
information, where the network service-related information includes
a network service type, a network service capacity requirement, and
a network scale policy; the virtualized network node-related
information includes a virtualized network node type, a virtualized
network node capacity requirement, a virtualized network node
deployment location, and a virtualized network node interconnection
link requirement; the virtualized network node feature-related
information includes a virtualized network node channel quantity
and a virtualized network node service area setting; and the user
subscription-related information includes a user quantity, a
network selection policy, and quality of service.
[0099] With reference to the first implementable manner or the
second implementable manner, in a fourth implementable manner, the
NSO node is connected to one RO node, the RO node is connected to
at least one RO node, and the first sending unit is further
configured to:
[0100] send the second configuration file message to the RO node,
where the second configuration file includes network
service-related information, virtualized network node-related
information, virtualized network node feature-related information,
and user subscription-related information, where the network
service-related information includes a network service type, a
network service capacity requirement, and a network scale policy;
the virtualized network node-related information includes a
virtualized network node type, a virtualized network node capacity
requirement, a virtualized network node deployment location, and a
virtualized network node interconnection link requirement; the
virtualized network node feature-related information includes a
virtualized network node channel quantity and a virtualized network
node service area setting; and the user subscription-related
information includes a user quantity, a network selection policy,
and quality of service.
[0101] With reference to the third implementable manner or the
fourth implementable manner, in a fifth implementable manner, the
NSO node further includes:
[0102] a third sending unit, configured to send a network service
instantiation request message to the RO node.
[0103] With reference to the fifth implementable manner, in a sixth
implementable manner, the NSO node further includes:
[0104] a fourth receiving unit, configured to receive a network
service modification requirement message sent by the first network
node, where the network service modification requirement message
includes a network service modification requirement, and the
network service modification requirement is configuring the network
service, updating the network service, or terminating the network
service.
[0105] With reference to the sixth implementable manner, in a
seventh implementable manner, the NSO node further includes:
[0106] an obtaining unit, configured to obtain network service
information from the catalog and a network functions virtualization
infrastructure (NFVI) resource, where the network service
information includes a state and load of the network service, and
the NSO node is separately connected to the catalog and the network
functions virtualization infrastructure resource; or
[0107] obtain network service information from the catalog and a
network functions virtualization infrastructure (NFVI) resource by
using the RO node, where the network service information includes a
state and load of the network service.
[0108] With reference to the seventh implementable manner, in an
eighth implementable manner, the NSO node further includes:
[0109] a fourth sending unit, configured to send a network service
information query response message to the first network node.
[0110] With reference to any one of the fourth aspect or the first
implementable manner to the eighth implementable manner, in a ninth
implementable manner, the NSO node further includes:
[0111] a management unit, configured to manage a topology of a
network service instance, where
[0112] the management unit is further configured to manage
automatic configuration of the network service instance;
[0113] the management unit is further configured to manage network
service policy information; and
[0114] the management unit is further configured to manage a fault
of the network service.
[0115] According to a fifth aspect, a resource management
orchestration (RO) node is provided, including:
[0116] a first receiving unit, configured to receive a catalog
query request message sent by a network service orchestration (NSO)
node;
[0117] a query unit, configured to query a catalog, to obtain a
first configuration file;
[0118] a first sending unit, configured to send a catalog query
request response message to the NSO node, where the catalog query
request response message includes the first configuration file;
[0119] a second receiving unit, configured to receive a second
configuration file message sent by the NSO node, where the second
configuration file message includes a second configuration file,
and the second configuration file is a configuration file that
describes a network service; and
[0120] a second sending unit, configured to send a second
configuration file response message to the NSO node.
[0121] With reference to the fifth aspect, in a first implementable
manner, the RO node further includes:
[0122] a third receiving unit, configured to receive a network
service instantiation request message sent by the NSO node.
[0123] With reference to the fifth aspect or the first
implementable manner, in a second implementable manner, the RO node
further includes:
[0124] a management unit, configured to manage a fault of an NFVI
resource.
[0125] With reference to any one of the fifth aspect or the first
implementable manner to the second implementable manner, in a third
implementable manner, the RO node further includes:
[0126] a third sending unit, configured to send NFVI resource fault
information or NFVI resource global view information to a first
network node, where the first network node is an operation support
system (OSS) or a third-party software system.
[0127] The embodiments of the present invention provide a network
functions virtualization network system, a network functions
virtualization network data processing method, and an apparatus.
The network functions virtualization network system includes: a
network service orchestration (NSO) node, a resource management
orchestration (RO) node, a first network node, a virtualized
network function manager (VNFM) node, a virtualized infrastructure
manager (VIM) node, a catalog, a network functions virtualization
(NFV) instance, and a network functions virtualization
infrastructure (NFVI) resource, where the catalog includes a
network service (NS) catalog and a virtualized network function
(VNF) catalog, and the first network node is an operation support
system (OSS) or a third-party software system; the NSO node is
connected to the first network node by using an operation
support-network service orchestration interface, the NSO node is
connected to the RO node by using a network service
orchestration-resource management orchestration interface, and the
NSO node is connected to the catalog; and the RO node is connected
to the first network node by using an operation support-resource
management orchestration interface, the RO node is connected to the
VNFM node, the RO node is connected to the VIM node, and the RO
node is separately connected to the catalog, the network functions
virtualization instance, and the network functions virtualization
infrastructure resource. In this way, a network service
orchestration function in the prior art is implemented by using the
NSO node, and a resource management orchestration function in the
prior art is implemented by using the RO node, which can make
deployment of the network service orchestration function and the
resource management orchestration function of a network functions
virtualization network more flexible compared with the prior
art.
BRIEF DESCRIPTION OF DRAWINGS
[0128] To describe the technical solutions in the embodiments of
the present invention or in the prior art more clearly, the
following briefly describes the accompanying drawings required for
describing the embodiments or the prior art. Apparently, the
accompanying drawings in the following description show merely some
embodiments of the present invention, and a person of ordinary
skill in the art may still derive other drawings from these
accompanying drawings without creative efforts.
[0129] FIG. 1 is a schematic architectural diagram of a logical
function of a network functions virtualization network in the prior
art according to an embodiment of the present invention;
[0130] FIG. 2 is a schematic diagram 1 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0131] FIG. 3 is a schematic diagram 2 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0132] FIG. 4 is a schematic diagram 3 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0133] FIG. 5 is a schematic diagram 4 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0134] FIG. 6 is a schematic diagram 5 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0135] FIG. 7 is a schematic diagram 6 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0136] FIG. 8 is a schematic diagram 7 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0137] FIG. 9 is a schematic diagram 8 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0138] FIG. 10 is a schematic diagram 9 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0139] FIG. 11 is a schematic diagram 10 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0140] FIG. 12 is a schematic diagram 11 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0141] FIG. 13 is a schematic diagram 12 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0142] FIG. 14 is a schematic diagram 13 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0143] FIG. 15 is a schematic diagram 14 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0144] FIG. 16 is a schematic diagram 15 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0145] FIG. 17 is a schematic diagram 16 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0146] FIG. 18 is a schematic diagram 17 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0147] FIG. 19 is a schematic diagram 18 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0148] FIG. 20 is a schematic diagram 19 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0149] FIG. 21 is a schematic diagram 20 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0150] FIG. 22 is a schematic diagram 21 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0151] FIG. 23 is a schematic diagram 22 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0152] FIG. 24 is a schematic diagram 23 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0153] FIG. 25 is a schematic diagram 24 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0154] FIG. 26 is a schematic diagram 25 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0155] FIG. 27 is a schematic diagram 26 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0156] FIG. 28 is a schematic diagram 27 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0157] FIG. 29 is a schematic diagram 28 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0158] FIG. 30 is a schematic diagram 29 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0159] FIG. 31 is a schematic diagram 30 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0160] FIG. 32 is a schematic diagram 31 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0161] FIG. 33 is a schematic diagram 32 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0162] FIG. 34 is a schematic diagram 33 of a network functions
virtualization network system according to an embodiment of the
present invention;
[0163] FIG. 35 is a flowchart 1 of a network functions
virtualization network data processing method according to an
embodiment of the present invention;
[0164] FIG. 36 is a flowchart 2 of a network functions
virtualization network data processing method according to an
embodiment of the present invention;
[0165] FIG. 37 is a flowchart 3 of a network functions
virtualization network data processing method according to an
embodiment of the present invention;
[0166] FIG. 38 is a schematic structural diagram 1 of a network
service orchestration node according to an embodiment of the
present invention;
[0167] FIG. 39 is a schematic structural diagram 2 of a network
service orchestration node according to an embodiment of the
present invention;
[0168] FIG. 40 is a schematic structural diagram 3 of a network
service orchestration node according to an embodiment of the
present invention;
[0169] FIG. 41 is a schematic structural diagram 1 of a resource
management orchestration node according to an embodiment of the
present invention;
[0170] FIG. 42 is a schematic structural diagram 2 of a resource
management orchestration node according to an embodiment of the
present invention;
[0171] FIG. 43 is a schematic structural diagram 3 of a network
service orchestration node according to an embodiment of the
present invention; and
[0172] FIG. 44 is a schematic structural diagram 4 of a resource
management orchestration node according to an embodiment of the
present invention.
DETAILED DESCRIPTION
[0173] The following clearly describes the technical solutions in
the embodiments of the present invention with reference to the
accompanying drawings in the embodiments of the present invention.
Apparently, the described embodiments are merely some but not all
of the embodiments of the present invention. All other embodiments
obtained by a person of ordinary skill in the art based on the
embodiments of the present invention without creative efforts shall
fall within the protection scope of the present invention.
[0174] As shown in FIG. 1, a schematic architectural diagram of a
logical function of a network functions virtualization network
based on a cloud system is provided in the prior art. The network
functions virtualization network includes an operation support
system (OSS) node 11, an element management system (EMS) node 12, a
virtualized network function (VNF) node 13, a network functions
virtualization orchestrator (NFVO) node 14, a virtualized network
function manager (VNFM) node 15, a virtualized infrastructure
manager (VIM) node 16, a network functions virtualization
infrastructure (NFVI) node 17, a catalog 18, a network functions
virtualization (NFV) instance 19, and a network functions
virtualization infrastructure (NFVI) resource 20. The catalog
includes a network service (NS) catalog 181 and a virtualized
network function (VNF) catalog 182. The operation support system 11
is separately connected to the element management system 12 and the
network functions virtualization orchestrator 14. The element
management system 12 is separately connected to the virtualized
network function 13 and the virtualized network function manager
15. The virtualized network function 13 is separately connected to
the network functions virtualization infrastructure 17 and the
virtualized network function manager 15. The network functions
virtualization orchestrator 14 is separately connected to the
virtualized network function manager 15, the virtualized
infrastructure manager 16, the catalog 18, the network functions
virtualization instance 19, and the network functions
virtualization infrastructure resource 20. The virtualized network
function manager 15 is separately connected to the virtualized
infrastructure manager 16 and the virtualized network function
catalog 182. The virtualized infrastructure manager 16 is connected
to the network functions virtualization infrastructure 17.
[0175] It should be noted that, the NFVO node, the VNFM node, and
the VIM node are included in a network functions virtualization
management and orchestration (NFV-MANO). The network functions
virtualization network may include at least one EMS node and at
least one VNF node. Each VNF node may have a different function. A
function of the EMS node and a function of the VNF node may be
integrated into a physical device for implementation. The NFVI node
of a bottom-layer support architecture includes a computing
resource, a storage resource, and a transmission resource.
[0176] The cloud system mainly includes cloud computing and cloud
storage. The cloud computing refers to distributed computing that
sets server clusters in data centers in different places to provide
different applications for users by using a network. The cloud
storage refers to storing user data in the cloud instead of using a
local resource, so as to achieve an objective of remote use and
remote storage.
[0177] Particularly, the NFVO node is configured to implement a
network service orchestration function and a resource management
orchestration function. For example, it is assumed that a network
service function needs to be implemented by using the network
functions virtualization network. First, an operator may use the
OSS node to manually configure a function of the VNF node according
to a parameter value required by the VNF node and a configuration
file such as a virtualized network function description (VNFD), to
generate a network service description (NSD) configuration file.
Then the OSS node may transmit the NSD configuration file to the
NFVO node by using an OSS-NFVO interface. The NFVO node checks
whether information such as a virtualized network function (VNF)
package or a hosting element of a VNF exists in the NSD
configuration file, and if information such as the virtualized
network function (VNF) package or the hosting element of the VNF
exists in the NSD configuration file, the NFVO node sends a network
service authentication description message to the catalog, so that
the catalog stores the NSD configuration file, and the NFVO node
sends a network service description loading success response
message to the OSS node. After the NFVO node successfully loads the
NSD configuration file, the NFVO node allocates a resource to the
VNF node by interacting with the VNFM node, the VIM node, the
catalog 18, the NFV instance 19, and the NFVI resource 20, to
implement network service instantiation.
[0178] An embodiment of the present invention provides a network
functions virtualization (NFV) network system 10, as shown in FIG.
2, including:
[0179] a network service orchestration (NSO) node 101, a resource
management orchestration (RO) node 102, a first network node 103, a
virtualized network function manager (VNFM) node 104, a virtualized
infrastructure manager (VIM) node 105, a catalog 106, a network
functions virtualization (NFV) instance 107, and a network
functions virtualization infrastructure (NFVI) resource 108, where
the catalog includes a network service (NS) catalog 1061 and a
virtualized network function (VNF) catalog 1062, and the first
network node is an operation support system (OSS) or a third-party
software system;
[0180] the NSO node 101 is connected to the first network node 103
by using an operation support-network service orchestration
interface (OS-NSO) a, the NSO node 101 is connected to the RO node
102 by using a network service orchestration-resource management
orchestration interface (NSO-RO) b, and the NSO node 101 is
connected to the catalog 106; and
[0181] the RO node 102 is connected to the first network node 103
by using an operation support-resource management orchestration
interface (OS-RO) c, the RO node 102 is connected to the VNFM node
104, the RO node 102 is connected to the VIM node 105, and the RO
node 102 is separately connected to the catalog 106, the network
functions virtualization instance 107, and the network functions
virtualization infrastructure resource 108.
[0182] It should be noted that, the NSO node 101 may be connected
to the network service catalog 1061 included in the catalog, and
the virtualized network function catalog 1062 may be connected to
the VNFM node 104.
[0183] In this way, a network service orchestration function of an
NFVO node in the prior art is implemented by using the NSO node,
and a resource management orchestration function of the NFVO node
in the prior art is implemented by using the RO node, which can
make deployment of the network service orchestration function and
the resource management orchestration function of a network
functions virtualization network more flexible compared with the
prior art.
[0184] It should be noted that, the network service catalog 1061
includes all network services that have been loaded; the
virtualized network function catalog 1062 includes all virtualized
network function packages (VNF Packages) that have been loaded; the
network functions virtualization instance 107 includes all network
service Instance and VNF Instance; and the network functions
virtualization infrastructure resource 108 includes all available
NFVI resource.
[0185] As shown in FIG. 3, the NFV network system 10 further
includes:
[0186] an element management system EMS node 109, a virtualized
network function (VNF) node 110, and a network functions
virtualization infrastructure NFVI node 111, where
[0187] the EMS node 109 is separately connected to the first
network node 103, the virtualized network function (VNF) node 110,
and the VNFM node 104;
[0188] the VNF node 110 is separately connected to the VNFM node
104 and the network functions virtualization infrastructure NFVI
node 111; and
[0189] the NFVI node 111 is connected to the VIM node 105.
[0190] The NFVO node, the VNFM node, and the VIM node are included
in a network functions virtualization management and orchestration
(NFV-MANO). A function of the EMS node and a function of the VNF
node may be integrated into a physical device for implementation.
The NFVI node of a bottom-layer support architecture includes a
computing resource, a storage resource, and a transmission
resource. It should be noted that, the NSO node has at least one of
network service functions, and the network service functions
include:
[0191] automatically configuring a network service requirement;
[0192] managing uploading of a network service and a virtualized
network function (VNF) node;
[0193] starting a network service and managing a life cycle of a
network service;
[0194] managing VNF instantiation in cooperation with the VNFM
node;
[0195] obtaining information about an NFVI related to a network
service and a VNF node resource by performing a query by using the
RO node or the VNFM node;
[0196] managing integrity and validity of a network service
instance during an execution cycle;
[0197] managing a relationship between a network service instance
and a VNF instance;
[0198] managing a topology of a network service instance; managing
automatic configuration of a network service instance;
[0199] managing policy information related to a network service;
and
[0200] managing a fault of a network service.
[0201] The RO node has at least one of a global resource management
function or a coordinated virtualized resource management
allocation function, and the global resource management function
and the coordinated virtualized resource management allocation
function include:
[0202] maintaining and managing a resource network topological
view;
[0203] authenticating and authorizing an NFVI resource request,
where NFVI resource are distributed in multiple VIM nodes;
[0204] managing a network service instance and distribution,
reservation, and configuration of an NFVI resource corresponding to
a VNF instance;
[0205] managing a VNF instance, and managing a relationship between
a VNF instance and an NFVI resource allocated to the VNF
instance;
[0206] managing a policy and managing execution of a network
service instance and a VNF instance;
[0207] recording a view related to an NFVI resource used by a VNF
instance or a VNF instance group; and
[0208] managing a fault of an NFVI resource.
[0209] Based on FIG. 3, as shown in FIG. 4, a difference from FIG.
3 lies in that the NSO node 101 in the NFV network system 10 may be
connected to the VNFM node 104 according to an actual situation. In
this way, the NSO node 101 can directly query for VNF instance
information and the like from the VNFM node 104, or send a VNF
instance management instruction, for example, establishing,
expanding, updating, or terminating a VNF instance, to the VNFM
node 104. If the NSO node 101 is not connected to the VNFM node
104, VNF instance management may be implemented by the RO node 102
by using the VNFM node 104.
[0210] Based on FIG. 3, as shown in FIG. 5, a difference from FIG.
3 lies in that the NSO node 101 may be connected to the catalog
106, the NFV instance 107, and the NFVI resource 108, and the RO
node 102 may be connected to the catalog 106, the NFV instance 107,
and the NFVI resource 108. That is, the NSO node 101 and the RO
node 102 share the catalog 106, the NFV instance 107, and NFVI
resource 108. The catalog includes the NS catalog 1061 and the VNF
catalog 1062. In this way, deployment of the network service
orchestration function and the resource management orchestration
function of the network functions virtualization network can be
more flexible.
[0211] Based on FIG. 3, as shown in FIG. 6, a difference from FIG.
3 lies in that the NSO node 101 in the NFV network system 10 may be
connected to the VNFM node 104 according to an actual situation,
the NSO node 101 may be connected to the catalog 106, the NFV
instance 107, and the NFVI resource 108, and the RO node 102 may be
connected to the catalog 106, the NFV instance 107, and the NFVI
resource 108. That is, the NSO node 101 and the RO node 102 share
the catalog 106, the NFV instance 107, and the NFVI resource 108.
The catalog includes the NS catalog 1061 and the VNF catalog
1062.
[0212] Based on FIG. 3, as shown in FIG. 7, a difference from FIG.
3 lies in that the NFV network system 10 may further include a
network service logic catalog (NSL) catalog 112. The NSL is used to
store service logical data related to deployment, user-related
data, and policy information, such as a network functions
virtualization (NFV) network address, an IP address, a user network
selection policy, quality of service (QoS) policy information, and
mobility management entity (MME) selection policy information in a
load balancing scenario. The NSO node 101 may be connected to the
NSL catalog 112.
[0213] Based on FIG. 4, as shown in FIG. 8, a difference from FIG.
4 lies in that the NFV network system 10 may further include a
network service logic (NSL) catalog 112, and the NSO node 101 may
be connected to the NSL catalog 112.
[0214] Based on FIG. 5, as shown in FIG. 9, a difference from FIG.
5 lies in that the NFV network system 10 may further include a
network service logic (NSL) catalog 112, and the NSO node 101 may
be connected to the NSL catalog 112.
[0215] Based on FIG. 6, as shown in FIG. 10, a difference from FIG.
6 lies in that the NFV network system 10 may further include a
network service logic (NSL) catalog 112, and the NSO node 101 may
be connected to the NSL catalog 112.
[0216] Further, the NFV network system may further include N RO
nodes and M VIM nodes, where N is an integer greater than or equal
to 1, and M is an integer greater than or equal to 1. The VIM nodes
may be deployed in a cascading manner, and the RO nodes may be
deployed in a cascading manner.
[0217] It is assumed that N is equal to 1 and M is equal to 2, that
is, it is assumed that the NFV network system 10 includes two VIM
nodes. The two VIM nodes are a first VIM node 1051 and a second VIM
node 1052. The following connection manners may be used.
[0218] Based on FIG. 3, as shown in FIG. 11, a difference from FIG.
3 lies in that the first VIM node 1051 is separately connected to
the VNFM node 104, the NFVI node 111, and the RO node 102;
[0219] the second VIM node 1052 is separately connected to the NFVI
node 111 and the RO node 102; and
[0220] the first VIM node 1051 is connected to the second VIM node
1052.
[0221] Based on FIG. 11, as shown in FIG. 12, a difference from
FIG. 11 lies in that the NSO node 101 in the NFV network system 10
may be connected to the VNFM node 104 according to an actual
situation. In this way, the NSO node 101 can directly query for VNF
instance information and the like from the VNFM node 104, or send a
VNF instance management instruction, for example, establishing,
expanding, updating, or terminating a VNF instance, to the VNFM
node 104. If the NSO node 101 is not connected to the VNFM node
104, VNF instance management may be implemented by the RO node 102
by using the VNFM node 104.
[0222] Based on FIG. 11, as shown in FIG. 13, a difference from
FIG. 11 lies in that the NSO node 101 may be connected to the
catalog 106, the NFV instance 107, and the NFVI resource 108, and
the RO node 102 may be connected to the catalog 106, the NFV
instance 107, and the NFVI resource 108. That is, the NSO node 101
and the RO node 102 share the catalog 106, the NFV instance 107,
and the NFVI resource 108. The catalog includes the NS catalog 1061
and the VNF catalog 1062. In this way, deployment of the network
service orchestration function and the resource management
orchestration function of the network functions virtualization
network can be more flexible.
[0223] Based on FIG. 11, as shown in FIG. 14, a difference from
FIG. 11 lies in that the NSO node 101 in the NFV network system 10
may be connected to the VNFM node 104 according to an actual
situation, the NSO node 101 may be connected to the catalog 106,
the NFV instance 107, and the NFVI resource 108, and the RO node
102 may be connected to the catalog 106, the NFV instance 107, and
the NFVI resource 108. That is, the NSO node 101 and the RO node
102 share the catalog 106, the NFV instance 107, and the NFVI
resource 108. The catalog includes the NS catalog 1061 and the VNF
catalog 1062.
[0224] Based on FIG. 11, as shown in FIG. 15, a difference from
FIG. 11 lies in that the NFV network system 10 may further include
a network service logic catalog (NSL) 112. The NSL is used to store
service logical data related to deployment, user-related data, and
policy information, such as a network functions virtualization
(NFV) network address, an IP address, a user network selection
policy, quality of service (QoS) policy information, and mobility
management entity (NNE) selection policy information in a load
balancing scenario. The NSO node 101 may be connected to the NSL
catalog 112.
[0225] Based on FIG. 12, as shown in FIG. 16, a difference from
FIG. 12 lies in that the NFV network system 10 may further include
a network service logic catalog (NSL Catalog) 112, and the NSO node
101 may be connected to the NSL catalog 112.
[0226] Based on FIG. 13, as shown in FIG. 17, a difference from
FIG. 13 lies in that the NFV network system 10 may further include
a network service logic (NSL) catalog 112, and the NSO node 101 may
be connected to the NSL catalog 112.
[0227] Based on FIG. 14, as shown in FIG. 18, a difference from
FIG. 14 lies in that the NFV network system 10 may further include
a network service logic (NSL) catalog 112, and the NSO node 101 may
be connected to the NSL catalog 112.
[0228] When N is greater than or equal to 2, and M is greater than
or equal to 1, the NSO node is connected to one of the RO nodes,
the RO node is separately connected to N-1 RO nodes, and each one
of the N-1 RO nodes is connected to at least one of the VIM
nodes.
[0229] In an implementation manner, it is assumed that N is equal
to 3 and M is equal to 3, that is, it is assumed that the NFV
network system 10 includes three VIM nodes and three resource
management orchestration (RO) nodes. The three VIM nodes are a
first VIM node 1051, a second VIM node 1052, and a third VIM node
1053, respectively. The three RO nodes are a first RO node 1021, a
second RO node 1022, and a third RO node 1023, respectively. The
following connection manners may be used.
[0230] Based on FIG. 3, as shown in FIG. 19, a difference from FIG.
3 lies in that the first RO node 1021 is separately connected to
the RO node 1022 and the RO node 1023, and the first RO node 1021
is further separately connected to the VNFM node 104, the catalog
106, the NFV instance 107, and the NFVI resource 108, and is
connected to the first network node 103 by using the interface c,
and is connected to the NSO node 101 by using the interface b;
[0231] the RO node 1022 is separately connected to the first VIM
node 1051 and the second VIM node 1052;
[0232] the third RO node 1023 is connected to the third VIM node
1053;
[0233] the first VIM node 1051 is separately connected to the
second VIM node 1052 and the NFVI node 111;
[0234] the second VIM node 1052 is connected to the NFVI node 111;
and
[0235] the third VIM node 1053 is connected to the NFVI node
111.
[0236] Based on FIG. 19, as shown in FIG. 20, a difference from
FIG. 19 lies in that the NSO node 101 in the NFV network system 10
may be connected to the VNFM node 104 according to an actual
situation. In this way, the NSO node 101 can directly query for VNF
instance information and the like from the VNFM node 104, or send a
VNF instance management instruction, for example, establishing,
expanding, updating, or terminating a VNF instance, to the VNFM
node 104. If the NSO node 101 is not connected to the VNFM node
104, VNF instance management may be implemented by the RO node 102
by using the VNFM node 104.
[0237] Based on FIG. 19, as shown in FIG. 21, a difference from
FIG. 19 lies in that the NSO node 101 may be connected to the
catalog 106, the NFV instance 107, and the NFVI resource 108, and
the RO node 102 may be connected to the catalog 106, the NFV
instance 107, and the NFVI resource 108. That is, the NSO node 101
and the RO node 102 share the catalog 106, the NFV instance 107,
and the NFVI resource 108. The catalog includes the NS catalog 1061
and the VNF catalog 1062. In this way, deployment of the network
service orchestration function and the resource management
orchestration function of the network functions virtualization
network can be more flexible.
[0238] Based on FIG. 19, as shown in FIG. 22, a difference from
FIG. 19 lies in that the NSO node 101 in the NFV network system 10
may be connected to the VNFM node 104 according to an actual
situation, the NSO node 101 may be connected to the catalog 106,
the NFV instance 107, and the NFVI resource 108, and the RO node
102 may be connected to the catalog 106, the NFV instance 107, and
the NFVI resource 108. That is, the NSO node 101 and the RO node
102 share the catalog 106, the NFV instance 107, and the NFVI
resource 108. The catalog includes the NS catalog 1061 and the VNF
catalog 1062.
[0239] Based on FIG. 19, as shown in FIG. 23, a difference from
FIG. 19 lies in that the NFV network system 10 may further include
network service logic (NSL) catalog 112. The NSL is used to store
service logical data related to deployment, user-related data, and
policy information, such as a network functions virtualization
(NFV) network address, an IP address, a user network selection
policy, quality of service (QoS) policy information, and mobility
management entity (MME) selection policy information in a load
balancing scenario. The NSO node 101 may be connected to the NSL
catalog 112.
[0240] Based on FIG. 20, as shown in FIG. 24, a difference from
FIG. 20 lies in that the NFV network system 10 may further include
an NSL catalog 112, and the NSO node 101 may be connected to the
NSL catalog 112.
[0241] Based on FIG. 21, as shown in FIG. 25, a difference from
FIG. 21 lies in that the NFV network system 10 may further include
an NSL catalog 112, and the NSO node 101 may be connected to the
NSL catalog 112.
[0242] Based on FIG. 22, as shown in FIG. 26, a difference from
FIG. 22 lies in that the NFV network system 10 may further include
an NSL catalog 112, and the NSO node 101 may be connected to the
NSL catalog 112.
[0243] In another implementation manner, it is assumed that N is
equal to 2 and M is equal to 3, that is, it is assumed that the NFV
network system 10 includes three VIM nodes and two RO nodes. The
three VIM nodes are a first VIM node 1051, a second VIM node 1052,
and a third VIM node 1053, respectively. The two RO nodes are a
first RO node 1021 and a second RO node 1022, respectively. The
following connection manners may be used.
[0244] Based on FIG. 3, as shown in FIG. 27, a difference from FIG.
3 lies in that the first RO node 1021 is connected to the third VIM
node 1053, and the first RO node 1021 is further separately
connected to the VNFM node 104, the catalog 106, the NFV instance
107, and the NFVI resource 108, and is connected to the first
network node 103 by using the interface c, and is connected to the
NSO node 101 by using the interface b;
[0245] the RO node 1022 is separately connected to the first VIM
node 1051 and the second VIM node 1052, and the RO node 1021 is
further separately connected to the VNFM node 104, the catalog 106,
the NFV instance 107, and the NFVI resource 108, and is connected
to the first network node 103 by using the interface c, and is
connected to the NSO node 101 by using the interface b;
[0246] the first VIM node 1051 is separately connected to the
second VIM node 1052 and the NFVI node 111;
[0247] the second VIM node 1052 is connected to the NFVI node 111;
and
[0248] the third VIM node 1053 is connected to the NFVI node
111.
[0249] Based on FIG. 27, as shown in FIG. 28, a difference from
FIG. 27 lies in that the NSO node 101 in the NFV network system 10
may be connected to the VNFM node 104 according to an actual
situation. In this way, the NSO node 101 can directly query for VNF
instance information and the like from the VNFM node 104, or send a
VNF instance management instruction, for example, establishing,
expanding, updating, or terminating a VNF instance, to the VNFM
node 104. If the NSO node 101 is not connected to the VNFM node
104, VNF instance management may be implemented by the RO node 102
by using the VNFM node 104.
[0250] Based on FIG. 27, as shown in FIG. 29, a difference from
FIG. 27 lies in that the NSO node 101 may be connected to the
catalog 106, the NFV instance 107, and the NFVI resource 108, and
the RO node 102 may be connected to the catalog 106, the NFV
instance 107, and the NFVI resource 108. That is, the NSO node 101
and the RO node 102 share the catalog 106, the NFV instance 107,
and the NFVI resource 108. The catalog includes the NS catalog 1061
and the VNF catalog 1062. In this way, deployment of the network
service orchestration function and the resource management
orchestration function of the network functions virtualization
network can be more flexible.
[0251] Based on FIG. 27, as shown in FIG. 30, a difference from
FIG. 27 lies in that the NSO node 101 in the NFV network system 10
may be connected to the VNFM node 104 according to an actual
situation, the NSO node 101 may be connected to the catalog 106,
the NFV instance 107, and the NFVI resource 108, and the RO node
102 may be connected to the catalog 106, the NFV instance 107, and
the NFVI resource 108. That is, the NSO node 101 and the RO node
102 share the catalog 106, the NFV instance 107, and the NFVI
resource 108. The catalog includes the NS catalog 1061 and the VNF
catalog 1062.
[0252] Based on FIG. 27, as shown in FIG. 31, a difference from
FIG. 27 lies in that the NFV network system 10 may further include
an NSL catalog 112. The NSL is used to store service logical data
related to deployment, user-related data, and policy information,
such as a network functions virtualization (NFV) network address,
an IP address, a user network selection policy, quality of service
(QoS) policy information, and mobility management entity (MME)
selection policy information in a load balancing scenario. The NSO
node 101 may be connected to the NSL catalog 112.
[0253] Based on FIG. 28, as shown in FIG. 32, a difference from
FIG. 28 lies in that the NFV network system 10 may further include
an NSL catalog 112, and the NSO node 101 may be connected to the
NSL catalog 112.
[0254] Based on FIG. 29, as shown in FIG. 33, a difference from
FIG. 29 lies in that the NFV network system 10 may further include
an NSL catalog 112, and the NSO node 101 may be connected to the
NSL catalog 112.
[0255] Based on FIG. 30, as shown in FIG. 34, a difference from
FIG. 30 lies in that the NFV network system 10 may further include
an NSL catalog 112, and the NSO node 101 may be connected to the
NSL catalog 112.
[0256] It should be noted that, a deployment of a resource
management orchestration (RO) node may be determined according to
data in a data center, that is, one RO node may be deployed in one
data center. For example, the Beijing branch of China Mobile
deploys five data centers in Beijing, and resource of all the five
data centers are managed by respective RO nodes. The Beijing branch
of China Mobile may deploy a head RO node. The head RO node manages
the five data centers, where one data center may be managed by one
or more cascading VIM nodes. Both RO nodes and VIM nodes may be
deployed in a cascading manner.
[0257] Particularly, the NFVO node may be divided into the NSO node
and the RO node, and an interface related to the NSO node and the
RO node may be an internal interface of the NFVO node. When the
first network node is third-party software Networker, capability
exposure of the NFV network system can be implemented, to provide
an application programming interface (API) for an external
application, so as to achieve user and service optimization.
[0258] The NFV network system described in the present invention is
merely an example for description, and a schematic diagram of any
one of the NFV network systems shown in FIG. 2 to FIG. 34 may
exist, which is not limited in the present invention. In actual
application, another scenario may exist, for example, more than two
NSO nodes may exist, where each NSO node may be connected to at
least one RO node.
[0259] An embodiment of the present invention provides a network
functions virtualization network data processing method. The
network functions virtualization network data processing method is
applied to a network service orchestration (NSO) node. As shown in
FIG. 35, the method includes:
[0260] Step 201: Receive a network service requirement message sent
by a first network node, where the network service requirement
message includes a network service requirement, the network service
requirement is a parameter value required for deploying a
virtualized network function (VNF) node, and the first network node
is an operation support system (OSS) or a third-party software
system.
[0261] Step 202: Generate a second configuration file according to
the network service requirement and a first configuration file,
where the first configuration file is a configuration file that
describes the VNF node, and the second configuration file is a
configuration file that describes a network service.
[0262] Step 203: Send a second configuration file message to a
resource management orchestration (RO) node, where the second
configuration file message includes the second configuration
file.
[0263] Step 204: Receive a second configuration file configuration
response message sent by the RO node.
[0264] In this way, a network service orchestration function in the
prior art is implemented by using the NSO node, which can make
deployment of the network service orchestration function and a
resource management orchestration function of a network functions
virtualization network more flexible compared with the prior
art.
[0265] Optionally, before the second configuration file is
generated according to the network service requirement and the
first configuration file, when the NSO node is connected to a
catalog, the NSO node may directly query the catalog, to obtain the
first configuration file from the catalog. The catalog includes a
network service (NS) catalog and a virtualized network function
(VNF) catalog.
[0266] Optionally, before the second configuration file is
generated according to the network service requirement and the
first configuration file, when the NSO node is connected to the RO
node, and the RO node is connected to the catalog, the NSO node may
send a catalog query request message to the RO node, and receive a
catalog query request response message sent by the RO node, where
the catalog query request response message includes the first
configuration file.
[0267] Optionally, the NSO node is connected to two or more RO
nodes, and the NSO node may send the second configuration file
message to at least one of the RO nodes according to a locally
stored network functions virtualization network resource global
view, where the second configuration file includes network
service-related information, virtualized network node-related
information, virtualized network node feature-related information,
and user subscription-related information, where the network
service-related information includes a network service type, a
network service capacity requirement, and a network scale policy;
the virtualized network node-related information includes a
virtualized network node type, a virtualized network node capacity
requirement, a virtualized network node deployment location, and a
virtualized network node interconnection link requirement; the
virtualized network node feature-related information includes a
virtualized network node channel quantity and a virtualized network
node service area setting; the user subscription-related
information includes a user quantity, a network selection policy,
and quality of service; and the network functions virtualization
network resource global view records a deployment of a resource of
the virtualized network function node in the network functions
virtualization network.
[0268] Optionally, the NSO node is connected to one RO node, the RO
node is connected to at least one RO node, and the NSO node may
send the second configuration file message to the RO node, where
the second configuration file includes network service-related
information, virtualized network node-related information,
virtualized network node feature-related information, and user
subscription-related information, where the network service-related
information includes a network service type, a network service
capacity requirement, and a network scale policy; the virtualized
network node-related information includes a virtualized network
node type, a virtualized network node capacity requirement, a
virtualized network node deployment location, and a virtualized
network node interconnection link requirement; the virtualized
network node feature-related information includes a virtualized
network node channel quantity and a virtualized network node
service area setting; and the user subscription-related information
includes a user quantity, a network selection policy, and quality
of service.
[0269] Further, after receiving the second configuration file
configuration response message sent by the RO node, the NSO node
may send a network service instantiation request message to the RO
node, and receive a network service modification requirement
message sent by the first network node, where the network service
modification requirement message includes a network service
modification requirement, and the network service modification
requirement is configuring the network service, updating the
network service, or terminating the network service.
[0270] Optionally, after receiving the network service modification
requirement message sent by the first network node, the NSO node
may obtain network service information from the catalog and a
network functions virtualization infrastructure (NFVI) resource,
where the network service information includes a state and load of
the network service, and the NSO node is separately connected to
the catalog and the network functions virtualization infrastructure
resource.
[0271] Optionally, the NSO node may obtain network service
information from the catalog and a network functions virtualization
infrastructure (NFVI) resource by using the RO node, where the
network service information includes a state and load of the
network service.
[0272] Optionally, after querying for the network service
information, the NSO node may send a network service information
query response message to the first network node.
[0273] The NSO node further performs at least one of the following
actions: managing a topology of a network service instance,
managing automatic configuration of the network service instance,
managing network service policy information, and managing a fault
of the network service.
[0274] An embodiment of the present invention provides a network
functions virtualization network data processing method. The
network functions virtualization network data processing method is
applied to a resource management orchestration (RO) node. As shown
in FIG. 36, the method includes:
[0275] Step 301: Receive a catalog query request message sent by a
network service orchestration (NSO) node.
[0276] Step 302: Query a catalog, to obtain a first configuration
file.
[0277] Step 303: Send a catalog query request response message to
the NSO node, where the catalog query request response message
includes the first configuration file.
[0278] Step 304: Receive a second configuration file message sent
by the NSO node, where the second configuration file message
includes a second configuration file, and the second configuration
file is a configuration file that describes a network service.
[0279] Step 305: Send a second configuration file response message
to the NSO node.
[0280] In this way, a resource management orchestration function in
the prior art is implemented by using the RO node, which can make
deployment of a network service orchestration function and the
resource management orchestration function of a network functions
virtualization network more flexible compared with the prior
art.
[0281] After the second configuration file message sent by the NSO
node is received, a network service instantiation request message
sent by the NSO node may be received.
[0282] After sending the second configuration file response message
to the NSO node, the RO node may manage a fault of an NFVI
resource, and send NFVI resource fault information or NFVI resource
global view information to a first network node, where the first
network node is an operation support system (OSS) or a third-party
software system.
[0283] An embodiment of the present invention provides a network
functions virtualization network data processing method, which is
applied to a network functions virtualization (NFV) network system.
As shown in FIG. 37, the method includes:
[0284] Step 401: A first network node sends a network service
requirement message to a network service orchestration (NSO)
node.
[0285] The network service requirement message includes a network
service requirement, the network service requirement is a parameter
value required for deploying a virtualized network function (VNF)
node, and the first network node is an operation support system
(OSS) or a third-party software system.
[0286] For example, video on-live services for 100 thousand users,
cluster services for two thousand users, data collection of 180
thousand machines, or the like need to be deployed. The network
service requirement includes a parameter value required for
deploying the virtualized network function (VNF) node, such as a
user quantity, time, a geographical location, a quality of service
requirement, or a capacity requirement.
[0287] Step 402: The NSO node generates a second configuration file
according to the network service requirement and a first
configuration file.
[0288] The first configuration file is a configuration file that
describes the VNF node, and the second configuration file is a
configuration file that describes a network service. The first
configuration file includes an information element of a VNF, and
the second configuration file includes an information element of a
network service description NSD. For example, the second
configuration file includes network service-related information,
virtualized network node-related information, virtualized network
node feature-related information, and user subscription-related
information, where the network service-related information includes
a network service type, a network service capacity requirement, and
a network scale policy; the virtualized network node-related
information includes a virtualized network node type, a virtualized
network node capacity requirement, a virtualized network node
deployment location, and a virtualized network node interconnection
link requirement; the virtualized network node feature-related
information includes a virtualized network node channel quantity
and a virtualized network node service area setting; and the user
subscription-related information includes a user quantity, a
network selection policy, and quality of service.
[0289] The NSO node may generate, by using a template, the second
configuration file according to the network service requirement, a
virtualized network function description (VNFD), a virtualized
network function component description (VNFCD), and the like. The
NSO node stores the template, and information such as the VNFD and
the VNFCD may be preset in the NSO node.
[0290] For example, video on-live services for 100 thousand users,
cluster services for two thousand users, data collection of 180
thousand machines, or the like need to be deployed. The network
service requirement includes a parameter value required for
deploying the virtualized network function (VNF) node, such as a
user quantity, time, a geographical location, a quality of service
requirement, or a capacity requirement. The NSO node determines,
according to the network service requirement, needed VNFs including
function nodes such as a mobility management entity (MME), a
signaling gateway (SGW), a packet data gateway (PGW), and a video
optimization gateway (VOG), determines requirements such as
performance and capacities corresponding to the different function
nodes, determines all information elements in the VNFD by querying
the VNFD, generates a Constituent VNF, and generates a Service
deployment flavour, that is, List of service deployment flavours in
the NSD, according to the Constituent VNF. Manners for determining
other information elements in the NSD are similar to this. It
should be noted that, for information element in configuration
files such as the NSD and the VNFD, refer to descriptions in the GS
NFV-MAN 001 V0.3.15 (Apr. 2014) protocol.
[0291] Optionally, before the NSO node generates the second
configuration file according to the network service requirement and
the first configuration file, the NSO node queries a catalog, to
obtain the first configuration file from the catalog, where the NSO
node is connected to the catalog, and the catalog includes a
network service (NS) catalog and a virtualized network function
(VNF) catalog.
[0292] Optionally, before the NSO node generates the second
configuration file according to the network service requirement and
the first configuration file, the NSO node sends a catalog query
request message to the RO node; the RO node queries the catalog, to
obtain the first configuration file; and the RO node sends a
catalog query request response message to the NSO node, where the
catalog query request response message includes the first
configuration file.
[0293] Step 403: The NSO node sends a second configuration file
message to the RO node.
[0294] The second configuration file message includes the second
configuration file.
[0295] Optionally, the NSO node is connected to two or more RO
nodes, and the NSO node sends the second configuration file message
to at least one of the RO nodes according to a locally stored
network functions virtualization network resource global view.
[0296] Optionally, the NSO node is connected to one RO node, the RO
node is connected to at least one RO node, the NSO node sends the
second configuration file message to the RO node, and then the RO
node may send the second configuration file message to the at least
one RO node according to a locally stored network functions
virtualization network resource global view.
[0297] Step 404: The RO node sends a second configuration file
response message to the NSO node.
[0298] Step 405: The NSO node sends a network service instantiation
request message to the RO node.
[0299] The NSO node, the RO node, a VNFM, and a VIM exchange
information with each other, to implement a process of network
service instantiation.
[0300] It should be noted that, the first network node may further
send a network service modification requirement message to the NSO
node, where the network service modification requirement message
includes a network service modification requirement, and the
network service modification requirement is configuring the network
service, updating the network service, or terminating the network
service. The NSO node is further configured to perform at least one
of the following actions: managing a topology of a network service
instance, managing automatic configuration of the network service
instance, managing network service policy information, and managing
a fault of the network service. The RO node is further configured
to manage a fault of an NFVI resource.
[0301] In this way, a network service orchestration function in the
prior art is implemented by using the NSO node, and a resource
management orchestration function in the prior art is implemented
by using the RO node, which can make deployment of the network
service orchestration function and the resource management
orchestration function of a network functions virtualization
network more flexible compared with the prior art.
[0302] An embodiment of the present invention provides a network
service orchestration (NSO) node 50, as shown in FIG. 38,
including: a first receiving unit 501, a generation unit 502, a
first sending unit 503, and a second receiving unit 504.
[0303] The first receiving unit 501 is configured to receive a
network service requirement message sent by a first network node,
where the network service requirement message includes a network
service requirement, the network service requirement is a parameter
value required for deploying a virtualized network function (VNF)
node, and the first network node is an operation support system
(OSS) or a third-party software system.
[0304] For example, video on-live services for 100 thousand users,
cluster services for two thousand users, data collection of 180
thousand machines, or the like need to be deployed. The network
service requirement includes a parameter value required for
deploying the virtualized network function (VNF) node, such as a
user quantity, time, a geographical location, a quality of service
requirement, or a capacity requirement.
[0305] The generation unit 502 is configured to generate a second
configuration file according to the network service requirement and
a first configuration file, where the first configuration file is a
configuration file that describes the VNF node, and the second
configuration file is a configuration file that describes a network
service.
[0306] The first configuration file is a configuration file that
describes the VNF node, and the second configuration file is a
configuration file that describes a network service. The first
configuration file includes an information element of a VNF, and
the second configuration file includes an information element of a
network service description NSD. For example, the second
configuration file includes network service-related information,
virtualized network node-related information, virtualized network
node feature-related information, and user subscription-related
information, where the network service-related information includes
a network service type, a network service capacity requirement, and
a network scale policy; the virtualized network node-related
information includes a virtualized network node type, a virtualized
network node capacity requirement, a virtualized network node
deployment location, and a virtualized network node interconnection
link requirement; the virtualized network node feature-related
information includes a virtualized network node channel quantity
and a virtualized network node service area setting; and the user
subscription-related information includes a user quantity, a
network selection policy, and quality of service.
[0307] The NSO node may generate, by using a template, the second
configuration file according to the network service requirement, a
virtualized network function description (VNFD), a virtualized
network function component description (VNFCD), and the like. The
NSO node stores the template, and information such as the VNFD and
the VNFCD may be preset in the NSO node.
[0308] For example, video on-live services for 100 thousand users,
cluster services for two thousand users, data collection of 180
thousand machines, or the like need to be deployed. The network
service requirement includes a parameter value required for
deploying the virtualized network function (VNF) node, such as a
user quantity, time, a geographical location, a quality of service
requirement, or a capacity requirement. The NSO node determines,
according to the network service requirement, needed VNFs including
function nodes such as a mobility management entity (MME), a
signaling gateway (SGW), a packet data gateway (PGW), and a video
optimization gateway (VOG), determines requirements such as
performance and capacities corresponding to the different function
nodes, determines all information elements in the VNFD by querying
the VNFD, generates a Constituent VNF, and generates a Service
deployment flavour, that is, List of service deployment flavours in
the NSD, according to the Constituent VNF. Manners for determining
other information elements in the NSD are similar to this. It
should be noted that, for information element in configuration
files such as the NSD and the VNFD, refer to descriptions in the GS
NFV-MAN 001 V0.3.15 (Apr. 2014) protocol.
[0309] The first sending unit 503 is configured to send a second
configuration file message to a resource management orchestration
(RO) node, where the second configuration file message includes the
second configuration file.
[0310] The second receiving unit 504 is configured to receive a
second configuration file configuration response message sent by
the RO node.
[0311] In this way, a network service orchestration function in the
prior art is implemented by using the NSO node, which can make
deployment of the network service orchestration function and a
resource management orchestration function of a network functions
virtualization network more flexible compared with the prior
art.
[0312] Optionally, as shown in FIG. 39, the NSO node 50 further
includes:
[0313] a query unit 505, configured to query a catalog, to obtain
the first configuration file from the catalog, where the NSO node
is connected to the catalog, and the catalog includes a network
service (NS) catalog and a virtualized network function (VNF)
catalog;
[0314] a third sending unit 508, configured to: send a network
service instantiation request message to the RO node;
[0315] a fourth sending unit 509, configured to: receive a network
service modification requirement message sent by the first network
node, where the network service modification requirement message
includes a network service modification requirement, and the
network service modification requirement is configuring the network
service, updating the network service, or terminating the network
service;
[0316] an obtaining unit 5010, configured to: obtain network
service information from the catalog and a network functions
virtualization infrastructure (NFVI) resource, where the network
service information includes a state and load of the network
service, and the NSO node is separately connected to the catalog
and the network functions virtualization infrastructure resource;
or obtain network service information from the catalog and a
network functions virtualization infrastructure (NFVI) resource by
using the RO node, where the network service information includes a
state and load of the network service;
[0317] a fourth sending unit 5011, configured to: send a network
service information query response message to the first network
node; and
[0318] a management unit 5012, configured to: manage a topology of
a network service instance, where
[0319] the management unit 5012 is further configured to manage
automatic configuration of the network service instance;
[0320] the management unit 5012 is further configured to manage
network service policy information; and
[0321] the management unit 5012 is further configured to manage a
fault of the network service.
[0322] Optionally, as shown in FIG. 40, the NSO node 50 further
includes:
[0323] a second sending unit 506, configured to send a catalog
query request message to the RO node;
[0324] a third receiving unit 507, configured to receive a catalog
query request response message sent by the RO node, where the
catalog query request response message includes the first
configuration file;
[0325] a third sending unit 508, configured to: send a network
service instantiation request message to the RO node;
[0326] a fourth sending unit 509, configured to: receive a network
service modification requirement message sent by the first network
node, where the network service modification requirement message
includes a network service modification requirement, and the
network service modification requirement is configuring the network
service, updating the network service, or terminating the network
service;
[0327] an obtaining unit 5010, configured to: obtain network
service information from the catalog and a network functions
virtualization infrastructure (NFVI) resource, where the network
service information includes a state and load of the network
service, and the NSO node is separately connected to the catalog
and the network functions virtualization infrastructure resource;
or obtain network service information from the catalog and a
network functions virtualization infrastructure (NFVI) resource by
using the RO node, where the network service information includes a
state and load of the network service;
[0328] a fourth sending unit 5011, configured to: send a network
service information query response message to the first network
node; and
[0329] a management unit 5012, configured to: the management unit
5012 is further configured to manage a topology of a network
service instance, where
[0330] the management unit 5012 is further configured to manage
automatic configuration of the network service instance;
[0331] the management unit 5012 is further configured to manage
network service policy information; and
[0332] the management unit 5012 is further configured to manage a
fault of the network service.
[0333] The NSO node is connected to two or more RO nodes, and the
first sending unit 503 is further configured to:
[0334] send the second configuration file message to at least one
of the RO nodes according to a locally stored network functions
virtualization network resource global view, where the second
configuration file includes network service-related information,
virtualized network node-related information, virtualized network
node feature-related information, and user subscription-related
information, where the network service-related information includes
a network service type, a network service capacity requirement, and
a network scale policy; the virtualized network node-related
information includes a virtualized network node type, a virtualized
network node capacity requirement, a virtualized network node
deployment location, and a virtualized network node interconnection
link requirement; the virtualized network node feature-related
information includes a virtualized network node channel quantity
and a virtualized network node service area setting; and the user
subscription-related information includes a user quantity, a
network selection policy, and quality of service.
[0335] The NSO node is connected to one RO node, the RO node is
connected to at least one RO node, and the first sending unit 503
is further configured to:
[0336] send the second configuration file message to the RO node,
where the second configuration file includes network
service-related information, virtualized network node-related
information, virtualized network node feature-related information,
and user subscription-related information, where the network
service-related information includes a network service type, a
network service capacity requirement, and a network scale policy;
the virtualized network node-related information includes a
virtualized network node type, a virtualized network node capacity
requirement, a virtualized network node deployment location, and a
virtualized network node interconnection link requirement; the
virtualized network node feature-related information includes a
virtualized network node channel quantity and a virtualized network
node service area setting; and the user subscription-related
information includes a user quantity, a network selection policy,
and quality of service.
[0337] The NSO node has at least one of network service functions,
and the network service functions include:
[0338] automatically configuring a network service requirement;
[0339] managing uploading of a network service and a virtualized
network function (VNF) node;
[0340] starting a network service and managing a life cycle of a
network service;
[0341] managing VNF instantiation in cooperation with the VNFM
node;
[0342] obtaining information about an NFVI related to a network
service and a VNF node resource by performing a query by using the
RO node or the VNFM node;
[0343] managing integrity and validity of a network service
instance during an execution cycle;
[0344] managing a relationship between a network service instance
and a VNF instance;
[0345] managing a topology of a network service instance; managing
automatic configuration of a network service instance;
[0346] managing policy information related to a network service;
and
[0347] managing a fault of a network service.
[0348] An embodiment of the present invention provides a resource
management orchestration (RO) node 60, as shown in FIG. 41,
including:
[0349] a first receiving unit 601, configured to receive a catalog
query request message sent by a network service orchestration (NSO)
node;
[0350] a query unit 602, configured to query a catalog, to obtain a
first configuration file;
[0351] a first sending unit 603, configured to send a catalog query
request response message to the NSO node, where the catalog query
request response message includes the first configuration file;
[0352] a second receiving unit 604, configured to receive a second
configuration file message sent by the NSO node, where the second
configuration file message includes a second configuration file,
and the second configuration file is a configuration file that
describes a network service; and
[0353] a second sending unit 605, configured to send a second
configuration file response message to the NSO node.
[0354] In this way, a resource management orchestration function in
the prior art is implemented by using the RO node, which can make
deployment of a network service orchestration function and the
resource management orchestration function of a network functions
virtualization network more flexible compared with the prior
art.
[0355] As shown in FIG. 42, the RO node 60 further includes:
[0356] a third receiving unit 606, configured to receive a network
service instantiation request message sent by the NSO node;
[0357] a management unit 607, configured to manage a fault of an
NFVI resource; and
[0358] a third sending unit 608, configured to send NFVI resource
fault information or NFVI resource global view information to a
first network node, where the first network node is an operation
support system (OSS) or a third-party software system.
[0359] The RO node has at least one of a global resource management
function or a coordinated virtualized resource management
allocation function, and the global resource management function
and the coordinated virtualized resource management allocation
function include:
[0360] maintaining and managing a resource network topological
view;
[0361] authenticating and authorizing an NFVI resource request,
where NFVI resource are distributed in multiple VIM nodes;
[0362] managing a network service instance and distribution,
reservation, and configuration of an NFVI resource corresponding to
a VNF instance;
[0363] managing a VNF instance, and managing a relationship between
a VNF instance and an NFVI resource allocated to the VNF
instance;
[0364] managing a policy and managing execution of a network
service instance and a VNF instance;
[0365] recording a view related to an NFVI resource used by a VNF
instance or a VNF instance group; and
[0366] managing a fault of an NFVI resource.
[0367] An embodiment of the present invention provides a network
service orchestration (NSO) node 70, as shown in FIG. 43,
including: a receiver 702, a processor 702, and a transmitter
703.
[0368] The receiver 701 is configured to receive a network service
requirement message sent by a first network node, where the network
service requirement message includes a network service requirement,
the network service requirement is a parameter value required for
deploying a virtualized network function (VNF) node, and the first
network node is an operation support system (OSS) or a third-party
software system.
[0369] For example, video on-live services for 100 thousand users,
cluster services for two thousand users, data collection of 180
thousand machines, or the like need to be deployed. The network
service requirement includes a parameter value required for
deploying the virtualized network function (VNF) node, such as a
user quantity, time, a geographical location, a quality of service
requirement, or a capacity requirement.
[0370] The processor 702 is configured to generate a second
configuration file according to the network service requirement and
a first configuration file, where the first configuration file is a
configuration file that describes the VNF node, and the second
configuration file is a configuration file that describes a network
service.
[0371] The first configuration file is a configuration file that
describes the VNF node, and the second configuration file is a
configuration file that describes a network service. The first
configuration file includes an information element of a VNF, and
the second configuration file includes an information element of a
network service description NSD. For example, the second
configuration file includes network service-related information,
virtualized network node-related information, virtualized network
node feature-related information, and user subscription-related
information, where the network service-related information includes
a network service type, a network service capacity requirement, and
a network scale policy; the virtualized network node-related
information includes a virtualized network node type, a virtualized
network node capacity requirement, a virtualized network node
deployment location, and a virtualized network node interconnection
link requirement; the virtualized network node feature-related
information includes a virtualized network node channel quantity
and a virtualized network node service area setting; and the user
subscription-related information includes a user quantity, a
network selection policy, and quality of service.
[0372] The NSO node may generate, by using a template, the second
configuration file according to the network service requirement, a
virtualized network function description (VNFD), a virtualized
network function component description (VNFCD), and the like. The
NSO node stores the template, and information such as the VNFD and
the VNFCD may be preset in the NSO node.
[0373] For example, video on-live services for 100 thousand users,
cluster services for two thousand users, data collection of 180
thousand machines, or the like need to be deployed. The network
service requirement includes a parameter value required for
deploying the virtualized network function (VNF) node, such as a
user quantity, time, a geographical location, a quality of service
requirement, or a capacity requirement. The NSO node determines,
according to the network service requirement, needed VNFs including
function nodes such as a mobility management entity (MME), a
signaling gateway (SGW), a packet data gateway (PGW), and a video
optimization gateway (VOG), determines requirements such as
performance and capacities corresponding to the different function
nodes, determines all information elements in the VNFD by querying
the VNFD, generates a Constituent VNF, and generates a Service
deployment flavour, that is, List of service deployment flavours in
the NSD, according to the Constituent VNF. Manners for determining
other information elements in the NSD are similar to this. It
should be noted that, for information element in configuration
files such as the NSD and the VNFD, refer to descriptions in the GS
NFV-MAN 001 V0.3.15 (Apr. 2014) protocol.
[0374] The transmitter 703 is configured to send a second
configuration file message to a resource management orchestration
(RO) node, where the second configuration file message includes the
second configuration file.
[0375] The receiver 701 is further configured to receive a second
configuration file configuration response message sent by the RO
node.
[0376] In this way, a network service orchestration function in the
prior art is implemented by using the NSO node, which can make
deployment of the network service orchestration function and a
resource management orchestration function of a network functions
virtualization network more flexible compared with the prior
art.
[0377] The processor 702 is further configured to query a catalog,
to obtain the first configuration file from the catalog, where the
NSO node is connected to the catalog, and the catalog includes a
network service (NS) catalog and a virtualized network function
(VNF) catalog.
[0378] The transmitter 703 is further configured to send a catalog
query request message to the RO node.
[0379] The receiver 701 is further configured to receive a catalog
query request response message sent by the RO node, where the
catalog query request response message includes the first
configuration file.
[0380] The NSO node is connected to two or more RO nodes, and the
transmitter 703 is further configured to:
[0381] send the second configuration file message to at least one
of the RO nodes according to a locally stored network functions
virtualization network resource global view, where the second
configuration file includes network service-related information,
virtualized network node-related information, virtualized network
node feature-related information, and user subscription-related
information, where the network service-related information includes
a network service type, a network service capacity requirement, and
a network scale policy; the virtualized network node-related
information includes a virtualized network node type, a virtualized
network node capacity requirement, a virtualized network node
deployment location, and a virtualized network node interconnection
link requirement; the virtualized network node feature-related
information includes a virtualized network node channel quantity
and a virtualized network node service area setting; and the user
subscription-related information includes a user quantity, a
network selection policy, and quality of service.
[0382] The NSO node is connected to one RO node, the RO node is
connected to at least one RO node, and the transmitter 703 is
further configured to:
[0383] send the second configuration file message to the RO node,
where the second configuration file includes network
service-related information, virtualized network node-related
information, virtualized network node feature-related information,
and user subscription-related information, where the network
service-related information includes a network service type, a
network service capacity requirement, and a network scale policy;
the virtualized network node-related information includes a
virtualized network node type, a virtualized network node capacity
requirement, a virtualized network node deployment location, and a
virtualized network node interconnection link requirement; the
virtualized network node feature-related information includes a
virtualized network node channel quantity and a virtualized network
node service area setting; and the user subscription-related
information includes a user quantity, a network selection policy,
and quality of service.
[0384] The transmitter 703 is further configured to send a network
service instantiation request message to the RO node.
[0385] The receiver 701 is further configured to receive a network
service modification requirement message sent by the first network
node, where the network service modification requirement message
includes a network service modification requirement, and the
network service modification requirement is configuring the network
service, updating the network service, or terminating the network
service.
[0386] The processor 702 is further configured to obtain network
service information from the catalog and a network functions
virtualization infrastructure (NFVI) resource, where the network
service information includes a state and load of the network
service, and the NSO node is separately connected to the catalog
and the network functions virtualization infrastructure resource;
or obtain network service information from the catalog and a
network functions virtualization infrastructure (NFVI) resource by
using the RO node, where the network service information includes a
state and load of the network service.
[0387] The transmitter 703 is further configured to send a network
service information query response message to the first network
node.
[0388] The processor 702 is further configured to: manage a
topology of a network service instance; manage automatic
configuration of the network service instance; manage network
service policy information; and manage a fault of the network
service.
[0389] The NSO node has at least one of network service functions,
and the network service functions include:
[0390] automatically configuring a network service requirement;
[0391] managing uploading of a network service and a virtualized
network function (VNF) node;
[0392] starting a network service and managing a life cycle of a
network service;
[0393] managing VNF instantiation in cooperation with the VNFM
node;
[0394] obtaining information about an NFVI related to a network
service and a VNF node resource by performing a query by using the
RO node or the VNFM node;
[0395] managing integrity and validity of a network service
instance during an execution cycle;
[0396] managing a relationship between a network service instance
and a VNF instance;
[0397] managing a topology of a network service instance;
[0398] managing automatic configuration of a network service
instance;
[0399] managing policy information related to a network service;
and
[0400] managing a fault of a network service.
[0401] An embodiment of the present invention provides a resource
management orchestration (RO) node 80, as shown in FIG. 44,
including:
[0402] a receiver 801, configured to receive a catalog query
request message sent by a network service orchestration (NSO)
node;
[0403] a processor 802, configured to query a catalog, to obtain a
first configuration file; and
[0404] a transmitter 803, configured to send a catalog query
request response message to the NSO node, where the catalog query
request response message includes the first configuration file,
where
[0405] the receiver 801 is further configured to receive a second
configuration file message sent by the NSO node, where the second
configuration file message includes a second configuration file,
and the second configuration file is a configuration file that
describes a network service; and
[0406] the transmitter 803 is further configured to send a second
configuration file response message to the NSO node.
[0407] In this way, a resource management orchestration function in
the prior art is implemented by using the RO node, which can make
deployment of a network service orchestration function and the
resource management orchestration function of a network functions
virtualization network more flexible compared with the prior
art.
[0408] The receiver 801 is further configured to receive a network
service instantiation request message sent by the NSO node.
[0409] The processor 802 is further configured to manage a fault of
an NFVI resource.
[0410] The transmitter 803 is further configured to send NFVI
resource fault information or NFVI resource global view information
to a first network node, where the first network node is an
operation support system (OSS) or a third-party software
system.
[0411] The RO node has at least one of a global resource management
function or a coordinated virtualized resource management
allocation function, and the global resource management function
and the coordinated virtualized resource management allocation
function include:
[0412] maintaining and managing a resource network topological
view;
[0413] authenticating and authorizing an NFVI resource request,
where NFVI resource are distributed in multiple VIM nodes;
[0414] managing a network service instance and distribution,
reservation, and configuration of an NFVI resource corresponding to
a VNF instance;
[0415] managing a VNF instance, and managing a relationship between
a VNF instance and an NFVI resource allocated to the VNF
instance;
[0416] managing a policy and managing execution of a network
service instance and a VNF instance;
[0417] recording a view related to an NFVI resource used by a VNF
instance or a VNF instance group; and
[0418] managing a fault of an NFVI resource.
[0419] It may be clearly understood by a person skilled in the art
that, for the purpose of convenient and brief description, for a
detailed working process of the foregoing apparatus and unit,
reference may be made to a corresponding process in the foregoing
method embodiments, and details are not described herein again.
[0420] In the several embodiments provided in the present
application, it should be understood that the disclosed apparatus
and method may be implemented in other manners. For example, the
described apparatus embodiment is merely exemplary. For example,
the unit division is merely logical function division and may be
other division in actual implementation. For example, a plurality
of units or components may be combined or integrated into another
system, or some features may be ignored or not performed. In
addition, the displayed or discussed mutual couplings or direct
couplings or communication connections may be implemented by using
some interfaces. The indirect couplings or communication
connections between the apparatuses or units may be implemented in
electronic, mechanical, or other forms.
[0421] The units described as separate parts may or may not be
physically separate, and parts displayed as units may or may not be
physical units, may be located in one position, or may be
distributed on a plurality of network units. Some or all of the
units may be selected according to actual needs to achieve the
objectives of the solutions of the embodiments.
[0422] In addition, functional units in the embodiments of the
present invention may be integrated into one processing unit, or
each of the units may exist alone physically, or two or more units
are integrated into one unit. The integrated unit may be
implemented in a form of hardware, or may be implemented in a form
of hardware in addition to a software functional unit.
[0423] A person of ordinary skill in the art may understand that
all or some of the steps of the method embodiments may be
implemented by a program instructing relevant hardware. The program
may be stored in a computer readable storage medium. When the
program runs, the steps of the method embodiments are performed.
The foregoing storage medium includes: any medium that can store
program code, such as a ROM, a RAM, a magnetic disk, or an optical
disc.
[0424] The foregoing descriptions are merely specific
implementation manners of the present invention, but are not
intended to limit the protection scope of the present invention.
Any variation or replacement readily figured out by a person
skilled in the art within the technical scope disclosed in the
present invention shall fall within the protection scope of the
present invention. Therefore, the protection scope of the present
invention shall be subject to the protection scope of the
claims.
* * * * *