WO2015172362A1 - 一种网络功能虚拟化网络系统、数据处理方法及装置 - Google Patents
一种网络功能虚拟化网络系统、数据处理方法及装置 Download PDFInfo
- Publication number
- WO2015172362A1 WO2015172362A1 PCT/CN2014/077581 CN2014077581W WO2015172362A1 WO 2015172362 A1 WO2015172362 A1 WO 2015172362A1 CN 2014077581 W CN2014077581 W CN 2014077581W WO 2015172362 A1 WO2015172362 A1 WO 2015172362A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- node
- network service
- nso
- service
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
- H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/20—Network management software packages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/24—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using dedicated network management hardware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/53—Network services using third party service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
Definitions
- Network function virtualization network system data processing method and device
- the present invention relates to the field of communications, and in particular, to a network function virtualization network system, a data processing method, and a device.
- Network function Virtualized network is a communication network that virtualizes the functions of physical physical devices in a communication network, that is, the functions of physical physical devices in the communication network are implemented by software only on at least one physical server, or 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 for implementing physical physical devices in a communication network on at least one physical server may be referred to as a virtualized network node.
- a physical server can include at least one virtualized network node, and a virtualized network node can also be a server group composed of multiple physical servers.
- the network function virtualization network includes an OS S (Operation Support System) node, an EMS (Element Management System) node, a VNF (Virtual Network Function) node, and an NFVO.
- OS S Operaation Support System
- EMS Electronic Management System
- VNF Virtual Network Function
- NFVI Network Function Virtual Infrastructure, Network function virtual facility
- the OS S node is an integrated system of operator integration and information resource sharing
- the EMS node is a system for managing one or more virtualized network nodes, and is used to implement FCAP S for VNF ( Fault Management, Configuration Management, Accounting Management, Performance Management, Security Management, Fault Management, Westing
- the FNF node is used to implement the PNF (Physical Network Function), which may be a mobility management entity or a base station.
- PNF Physical Network Function
- the NFVI node is used to provide virtual resources for the VNF node.
- the NFVO node is used to implement the network service orchestration function and the resource management orchestration function
- the VNFM node is used to manage the life cycle of the VNF instance
- the VIM node is used to control and manage the computing resources, the storage resources and the network resources, and the computing resources, the storage resources, and A virtualized entity of network resources.
- NFVO includes some functions for defining network services and abstracting the VNF requirements for resources.
- Network services are in the scope of network operation and maintenance and management, while abstracting the network function virtualization platform layer (NFVI) resource management in centralized global resource management.
- NFVI network function virtualization platform layer
- NFVI network function virtualization platform layer
- the two main functional requirements of the network service orchestration function and the resource management orchestration function are coupled in the same functional entity NFVO, which will cause difficulties in deployment.
- the NFVI's tiered resource management model does not guarantee that the planning functions of the tributary network service instances are deployed in the same logical entity.
- the granularity of the resource management orchestration functional entity deployment is much finer than the granularity of the network service storage functional entity deployment.
- the network service orchestration functional entity can be tightly coupled with the OSS.
- Embodiments of the present invention provide a network function virtualization network system, a data processing method, and a device, which can make the deployment of the network service orchestration function and the resource management orchestration function of the network function virtualization network more flexible.
- a network function virtualization NFV network system including: a network service orchestration NSO node, a resource management orchestration RO node, a first network node, and a virtual Network function manager VNFM node, virtual facility manager VIM node, directory catalogue, network function virtualization instance NFV Instances and network function virtual NFVI Resources, the directory includes a network service directory NS catalog and a virtual network function catalog VNF catalog, the first network node being an operation support system OS S or a third-party software system,
- the NSO node is connected to the first network node through an operation support-network service orchestration interface, and the NSO node is connected to the RO node through a network service orchestration-resource management orchestration interface, and the NSO node is connected to the directory. ;
- 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, and the RO node is connected to the VIM node, and the RO node is respectively associated with The directory, network function virtualization instance, and network function virtual facility resource connection.
- the network function virtualization NFV network system further includes:
- N is an integer that is greater than or equal to 1, and the N is an integer greater than or equal to 1, and the M is an integer greater than or equal to 1, and the M is an integer greater than or equal to 1;
- NSO node 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;
- NSO 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;
- the NSO node is connected to one of the RO nodes, and the RO node is respectively connected to N-1 of the RO nodes, and each of the N-1 RO nodes One RO node is connected to at least one of the VIM nodes.
- the network function virtualization NFV network system further includes:
- N is an integer that is greater than or equal to 1, and the N is an integer greater than or equal to 1, and the M is an integer greater than or equal to 1, and the M is an integer greater than or equal to 1;
- N 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;
- the NSO node is respectively connected to each of the RO nodes, and each of the RO nodes is connected to at least one of the VIM nodes.
- the network function virtualization NFV network system further includes:
- the NSO node is connected to the VNFM node.
- the network function virtualization NFV network system further includes:
- the NSO nodes are respectively connected to the network function virtualization instance and the network function virtual facility resource.
- the network function virtualization NFV network system further includes:
- the network service logical directory NSL catalogue stores network service policy information, where the network service policy information includes logical data, user related data, and policy information for deploying the network service;
- the NSO node is connected to the network service logical directory.
- Network service features include:
- VNF instantiation is managed in conjunction with the VNFM node; Obtaining information about the NFVI and VNF node resources related to the network service through the RO node or the VNFM node query;
- the RO node has a global resource management function and a unified management and allocation virtualized resource function.
- At least one of the global resource management functions and the integrated management function of allocating virtualized resources include:
- NFVI resource request verification and authorization NFVI resources are distributed across multiple VIM nodes
- VNF instances Relation Management of VNF instances, relationship management between VNF instances and NFVI resources assigned to VNF instances;
- a data processing method for a network function virtualization network where the data processing method of the network function virtualization network is used for a network service orchestration NSO node, and the method includes:
- the network service requirement message includes a network service requirement, where the network service requirement is a virtual network function
- the parameter value required by the VNF node, where the first network node is an operation support system OSS or a third-party software system
- the first configuration file is a configuration file describing the VNF node
- the second configuration file is a configuration file describing a network service
- the method before the generating the second configuration file according to the network service requirement and the first configuration file, the method further includes:
- the catalogue catalogue includes a web service catalog NS catalog and a virtual network function catalog VNF catalog.
- the method before the generating the second configuration file according to the network service requirement and the first configuration file, the method further includes:
- the network service orchestration NSO node connects two or more resource management orchestration RO nodes, and the resource management orchestration is arranged.
- the RO node sends the second profile message including:
- the second configuration file message Transmitting, according to the locally stored network function virtualized network resource global view, the second configuration file message to at least one of the resource management orchestration RO nodes, where the second configuration file includes network service related information, virtualized network node related information, Virtual The network node related information and the user subscription related information, the network service related information includes a network service type, a network service capacity requirement, and a network scaling policy scale policy, where the virtualized network node related information includes a virtualized network node type, and a virtual The network node capacity requirement, the virtualized network node deployment location, and the virtualized network node interconnection link requirement, the virtualized network node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting, where The information about the user subscription includes the number of users, the network selection policy, and the quality of service.
- the network service orchestration NSO node is connected to a resource management orchestration RO node, and the RO node is connected to at least one resource management orchestration RO
- the sending, by the node, the sending, by the resource management RO node, the second configuration file message includes:
- the second configuration file includes network service related information, virtualized network node related information, virtualized network node characteristic related information, and user subscription related information
- the network service related information includes a network service type, a network service capacity requirement, and a network scaling policy, where the virtualized network node related information includes a virtualized network node type, a virtualized network node capacity requirement, and a virtualized network node deployment location.
- virtualizing the network node interconnection link requirement where the virtualized network node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting, where the user subscription related information includes a number of users, a network selection policy And quality of service.
- the method further includes:
- a network service instantiation request message is sent to the RO node.
- the method further includes: receiving the network sent by the first network node Service modification request message, the network
- the network service modification requirement message includes a network service modification requirement, and the network service modification requirement is to configure a network service, update a network service, or terminate a network service.
- the method further includes:
- the network service information including a status and a load of the network service, wherein the NSO node is respectively connected to the directory and the network function virtual facility resource;
- the network service information includes a status and a load of the network service.
- the method further includes:
- any one of the first implementable manner to the eighth implementable manner, in the ninth implementable manner, the configuration response of the second configuration file sent by the receiving the RO node After the message, the method further includes:
- the third aspect provides a data processing method for a network function virtualization network, where the data processing method of the network function virtualization network is used for resource management orchestrating an RO node, and the method includes:
- the request response message includes a first configuration file
- the method further includes: receiving a network service instantiation request sent by the NSO node Message.
- the method further includes:
- the method further includes:
- the NFVI resource failure information or the NFVI resource global view information is sent to the first network, where the first network node is an operation support system OS S or a third-party software system.
- a network service orchestration NSO node including:
- a first receiving unit configured to receive a network service requirement message sent by the first network node, where the network service requirement message includes a network service requirement, where the network service requirement is a parameter value required for deploying a virtual network function VNF node,
- the first network node is an operation support system OS S or a third-party software system;
- a generating unit configured to generate a second configuration file according to the network service requirement and the first configuration file, where the first configuration file is a configuration file describing the VNF node, and the second configuration file is a configuration describing a network service Document
- a first sending unit configured to send a second configuration file message to the resource management orchestration RO node, where the second configuration file message includes a second configuration file;
- a second receiving unit configured to receive a second configuration file configuration response message sent by the RO node.
- the NSO node also includes:
- a query unit configured to query a directory catalogue, obtains a first configuration file from the directory, and the NSO node is connected to the directory, and the directory includes a network service directory NS catalog and a virtual network function directory VNF catalog.
- the network service orchestration NSO node further includes:
- a second sending unit configured to send a query directory request message to the RO node
- a third receiving unit configured to receive a query directory request response message sent by the RO node, where the query directory request response message includes a first configuration file .
- the network service orchestration NSO node connects two or more resource management orchestration RO nodes, and the first sending unit Specifically used for:
- the second configuration file message Transmitting, according to the locally stored network function virtualized network resource global view, the second configuration file message to at least one of the resource management orchestration RO nodes, where the second configuration file includes network service related information, virtualized network node related information, Virtual network node feature related information and user subscription related information, the network service related information includes a network service type, a network service capacity requirement, and a network scaling policy, the virtualized network node related information includes a virtualized network node type, Virtualized network node capacity requirements, virtualized network node deployment locations, and virtualized network node interconnection link requirements, the virtualized network node characteristic related information including a virtualized network node channel number and a virtualized network node service area setting,
- the user subscription related information includes the number of users, the network selection policy, and the quality of service.
- the network service orchestration NSO node is connected to a resource management orchestration RO node, and the RO node is connected to at least one resource management orchestration RO a node, where the first sending unit is specifically configured to: Sending, by the resource management orchestration RO node, the second configuration file message, where the second configuration file includes network service related information, virtualized network node related information, virtualized network node characteristic related information, and user subscription related information,
- the network service related information includes a network service type, a network service capacity requirement, and a network scaling policy, where the virtualized network node related information includes a virtualized network node type, a virtualized network node capacity requirement, and a virtualized network node deployment location.
- the virtualized network node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting, where the user subscription related information includes a number of users, a network selection policy And quality of service.
- the network service orchestration NSO node further includes:
- a third sending unit configured to send a network service instantiation request message to the RO node.
- the network service orchestration NSO node further includes:
- 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, where the network service modification requirement is to configure a network service, update a network service, or Terminate network services.
- the network service orchestration NSO node further includes:
- An obtaining unit configured to obtain network service information from the directory and network function virtual facility resource NFVI Resources, where the network service information includes a status and a load of the network service, where the NSO node is virtualized with the directory and the network function respectively Facility resource connection;
- network service information includes network service State of affairs and load.
- the network service orchestration NSO node further includes:
- a fourth sending unit configured to send the query network service information response message to the first network node.
- the network service orchestration NSO node further includes:
- the management unit is further configured to manage a network service instance automation configuration
- the management unit is further configured to manage network service policy information
- the management unit is also used to manage network service failures.
- a resource management RO node including:
- a first receiving unit configured to receive a query directory request message sent by the network service orchestration NSO node
- a query unit configured to query a directory catalogue to obtain a first configuration file
- a first sending unit configured to send a query directory request response message to the NSO node, where the query directory request response message includes a first configuration file
- 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, where the second configuration file is a configuration file describing a network service;
- a second sending unit configured to send a second profile response message to the NSO node.
- the resource management orchestration RO node further includes:
- the resource management orchestration RO node further includes:
- the resource management orchestration RO node further includes:
- a third sending unit configured to send NFVI resource failure information or NFVI resource global view information to the first network, where the first network node is an operation support system OS S or a third-party software system.
- An embodiment of the present invention provides a network function virtualization network system, a data processing method, and a device
- the network function virtualization network system includes: a network service orchestration NSO node, a resource management orchestration RO node, a first network node, and a virtual Network function manager VNFM node, virtual facility manager VIM node, directory catalogue, network function virtualization instance NF V Instances and network function virtual facility resource NFVI Resources
- the directory includes network service directory NS catalog and virtual network function directory VNF catalog
- the first network node is an operation support system 0 SS or a third-party software system
- the NS0 node is connected to the first network node by using an operation support-network service orchestration interface
- the NS0 node is arranged through a network service-resource
- the management orchestration interface is connected to the R0 node, and the NS0 node is connected to the directory; the R0 node is connected to the first network node by using an operation support-resource management orchestration interface
- the network service orchestration function in the prior art is implemented by the NS0 node, and the resource management orchestration function in the prior art is implemented by the RO node.
- the network function of the network function virtualization network can be enabled.
- the deployment of orchestration and resource management orchestration functions is more flexible.
- FIG. 1 is a schematic diagram of a logical functional architecture of a prior art network function virtualization network according to an embodiment of the present invention
- FIG. 2 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 3 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 4 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 5 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 6 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 7 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 8 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 9 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 10 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 11 is a schematic diagram 10 of a network function virtualization network system according to an embodiment of the present invention
- 12 is a schematic diagram 11 of a network function virtualization network system for implementing the present invention
- FIG. 13 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- FIG. 14 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- 15 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- 16 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- 17 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- FIG. 18 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- 19 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- 20 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- 21 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- FIG. 22 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- FIG. 23 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- FIG. 24 is a schematic diagram of a network function virtualization network system for implementing the present invention.
- FIG. 25 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention Figure 24;
- 26 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 27 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 28 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- 29 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 30 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 31 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 32 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG 33 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- FIG. 34 is a schematic diagram of a network function virtualization network system according to an embodiment of the present invention.
- 35 is a flowchart of a data processing method for a network function virtualization network according to an embodiment of the present invention.
- 36 is a flowchart of a data processing method for a network function virtualization network according to an embodiment of the present invention.
- FIG. 37 is a flowchart of a data processing method for a network function virtualization network according to an embodiment of the present invention.
- FIG. 38 is a schematic structural diagram of a network service orchestration node according to an embodiment of the present invention.
- FIG. 40 is a schematic structural diagram of a network service orchestration node according to an embodiment of the present invention.
- FIG. 42 is a schematic structural diagram of a resource management orchestration node according to an embodiment of the present invention
- FIG. 43 is a schematic structural diagram of a network service orchestration node according to an embodiment of the present invention.
- 44 is a schematic structural diagram of a resource management orchestration node according to an embodiment of the present invention.
- the network function virtualization network includes an OS S (Operation Support System) node 1 1 , an EMS (Element Management System) node 12 , a VNF (Virtual Network Function ) node 13 , and an NFVO (Network Function Virtualization Orchestrator) Node 14, VNFM (Virtual Network Function Manager) node 15, VIM (Virtualised Infrastructure Manager) node 16, NFVI (Network Function Virtual Infrastructure, virtual network function Prototype facility) node 17, catalogue 18, NFV Instances and network function virtual facility resource 20 (NFVI Resources), the directory includes web service directory 1 81 (NS catalog ) and virtual network Function Directory 182 (VNF catalog).
- OS S Operating Support System
- EMS Event Management System
- VNF Virtual Network Function
- NFVO Network Function Virtualization Orchestrator
- VNFM Virtual Network Function Manager
- VIM Virtualised Infrastructure Manager
- NFVI Network Function Virtual Infrastructure, virtual network function Prototype facility
- catalogue 18 NFV Instances and network function virtual facility resource 20 NFVI Resources
- the operation support system 1 1 is respectively connected to the network element management system 12 and the network function virtualization arranger 14 , and the network element management system 12 is respectively connected with the virtual network function 13 and the virtual network function manager 15 , and the virtual network function 13 respectively Connected with the network function virtual facility 17 and the virtual network function manager 15, the network function virtualization arranger 14 and the virtual network function manager 15, the virtual facility manager 16, the directory 18 network function virtualization instance 19, and the network function virtual
- the facility resources 20 are connected, the virtual network function manager 15 is connected to the virtual facility manager 16 and the virtual network function directory 182, respectively, and the virtual facility manager 16 is connected to the network function virtual facility 17.
- the NFVO node, the VNFM node, and the VIM node are included in the NFV-MANO (Network Function Virtualisation Management and Orchestrator); the network function virtualization network may include at least one EMS node and at least one VNF. Nodes, each VNF node can have different functions. The functions of the EMS node and the functions of the VNF node can also be integrated into one physical device.
- the NFVI nodes of the underlying supporting architecture include computing resources, storage resources, and transmission resources.
- Cloud systems mainly include cloud computing and cloud storage.
- Cloud computing refers to distributed computing. Server clusters are set up in various data centers to provide users with different applications through the network. Cloud storage is to store user data in the cloud, avoiding the use of local resource storage, and achieving off-site use and off-site storage.
- NFVO nodes are used to implement network service orchestration functions and resource management orchestration functions.
- the operator can use the OS S node according to the parameter values and VNFD (Virtual Network Function Descriptions) required by the VNF node. Describe the configuration file, manually configure the function of the VNF node, generate the NSD (network service descriptions) configuration file, and then the OS S node can transfer the NSD configuration file to the NFVO node through the interface between the OSS and the NFVO, the NFVO node. Check whether the VNF virtual machine function package (VNF Package) or managed element exists in the NSD configuration file.
- VNFD Virtual Network Function Descriptions
- VNF virtual network function package
- the NFVO node If there is VNF virtual network function package (VNF Package) or managed element information in the NSD configuration file, the NFVO node The directory sends a verification network service description message, so that the directory stores the NSD configuration file, and the NFVO node sends a network service description load success response message to the OSS node. After the NFVO node loads the NSD configuration file successfully, the NFVO node interacts with the VNFM node, the VIM node, the catalogue 18, the NFV Instances, and the NFVI Resources to the VNF. The node allocates resources to implement network service instantiation.
- VNF Package VNF virtual network function package
- the embodiment of the present invention provides a network function virtualization NFV network system 10, as shown in FIG. 2, including:
- Network service orchestration NSO node 101 resource management orchestration RO node 102, first network node 103, virtual network function manager VNFM node 104, virtual facility manager VIM node 105, directory catalogue 106, network function virtualization instance NFV Instances l 07 And a network function virtual facility resource NFVI Resources 108, the directory includes a network service directory NS catalog l 061 and a virtual network function directory VNF catalog 1062, the first network node being an operation support system OS S or a third-party software system,
- the NSO node 101 is connected to the first network node 103 through an Operation Support Network Service Orchestration Interface (OS-NSO) a, which passes the Network Service Orchestration-Resource Management Orchestration Interface (NSO-RO) b and The RO node 102 is connected, and the NSO node 101 is connected to the directory 106;
- OS-NSO Operation Support Network Service Orchestration Interface
- NSO-RO Network Service Orchestration-Resource Management Orchestration Interface
- the RO node 102 is connected to the first network node 103 through an operation support-resource management orchestration interface (OS-RO) c, the RO node 102 and the VNFM Nodes 104 are connected, the RO node 102 is connected to the VIM node 105, and the RO node 102 is connected to the directory 106, the network function virtualization instance 107, and the network function virtual facility resource 108, respectively.
- OS-RO operation support-resource management orchestration interface
- the NSO node 101 may be connected to the directory including the network service directory 1061; the virtual network function directory 1062 may be connected to the VNFM node 104.
- the network service orchestration function of the NFVO node in the prior art is implemented by the NSO node, and the resource management orchestration function of the NFVO node in the prior art is implemented by the RO node, and the network function can be enabled compared to the prior art.
- the deployment of the network service orchestration function and the resource management orchestration function of the virtualized network is more flexible.
- the network service directory 1061 includes all the loaded network services; the virtual network function directory 1062 includes all the loaded virtual network function packages (VNF Packages); the network function virtualization instance 107 includes all the network service instances and VNF Instance; Network Function Virtual facility resource 108 includes all available NFVI resources.
- VNF Packages virtual network function packages
- the network function virtualization instance 107 includes all the network service instances and VNF Instance
- Network Function Virtual facility resource 108 includes all available NFVI resources.
- the network function virtualization NFV network system 10 further includes: a network element management system EMS node 109, a virtual network function VNF node 1 10, a network function virtual facility NFVI node 1 1 1 ,
- the EMS node 109 is respectively connected to the first network node 103, the virtual network function VNF node 1 10, and the VNFM node 104;
- the VNF node 1 10 is connected to the VNFM node 104 and the network function virtual facility NFVI node 1 1 1 respectively;
- the NFVI node 1 1 1 is connected to the VIM node 105.
- the NFVO node, the VNFM node, and the VIM node are included in the NFV-MANO (Network Function Virtualisation Management and Orchestrator); the functions of the EMS node and the functions of the VNF node can also be integrated into one physical device;
- the architecture of the NFVI node includes Computing resources, storage resources, and transmission resources.
- the NSO node has at least one network service function in the network service function, and the network service function includes:
- VNFM node is used to manage VNF instantiation
- the RO node has at least one of a global resource management function and a coordinated management allocation virtualized resource function, and the global resource management function and the unified management allocation virtualized resource function include:
- NFVI resource request verification and authorization NFVI resources are distributed across multiple VIM nodes
- VNF instances Relation Management of VNF instances, relationship management between VNF instances and NFVI resources assigned to VNF instances;
- NFVI resource-related view records used by VNF instances or instance groups; NFVI resource fault management.
- the network function virtualization NFV network system 10 in the network service orchestration (NSO) node 101 can select the deployment and virtual network function manager (VNFM) node according to the actual situation. 104 connection.
- the Network Service Orchestration (NSO) node 101 can directly query the VNF instance information and the like from the Network Function Manager (VNFM) node 104, or send a VNF instance management instruction to the Network Function Manager (VNFM) node 104, for example, , expand, update, terminate VNF instances, and more.
- VNFM Virtual Network Function Manager
- the network service orchestration (NSO) node 101 can be associated with the catalogue 106, the network function virtualization instance NFV (Instances) 107, and the network function virtual.
- the directory includes a network service catalog (NS catalog) 1061 and a virtual network function catalog (VNF catalog) 1062.
- NSO network service orchestration
- RO resource management orchestration
- the network function virtualization NFV network system 10 in the network service orchestration (NSO) node 101 can select the deployment and virtual network function manager (VNFM) node according to the actual situation. 104 connection, office
- the Network Service Orchestration (NSO) node 101 can be connected to the catalogue 106, the network function virtualization instance NF V (Instances) 107, and the network function virtual facility resource (NFVI Resources) 108, while the resource management orchestration (
- the RO node node 102 can also be coupled to the catalogue 106, the network function virtualization instance NFV (Instances) 107, and the network function virtual facility resource (NF VI Resources) 108, ie, the network service orchestration (NSO) node 101.
- the resource management orchestration (RO) node 102 simultaneously shares the catalogue 106, the network function virtualization instance NF V (Instances) 107, and the network function virtual facility resource (NFVI Resources) 108, the directory including the network service The directory (NS catalog) 1061 and the virtual network function catalog (VNF catalog) 1062.
- the network function virtualization NFV network system 10 may further include an NSL Catalog (Network Service Logic) 112 for storing deployment-related Business logic data, user-related data, and policy information, such as network function virtualization NFV network address, IP address, etc., user network selection policy, QoS (Quality of Service) policy information, load balancing scenario MME (Mobility Management Entity) , mobility management entity) Select policy information, etc.
- NSL Catalog Network Service Logic
- a Network Service Orchestration (NSO) node 101 can be coupled to the Network Service Logical Directory (NSL Catalog) 112.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the NFV network system 10 may also include a Network Service Logical Directory (NSL Catalog) 112 to which the Network Service Orchestration (NSO) node 101 may be connected.
- NSO Network Service Orchestration
- the network function virtualization NF V network system may further include N the RO nodes and the M VIM nodes, where N is an integer greater than or equal to 1, and the M is an integer greater than or equal to 1, the virtual facility Manager (VIM) nodes can be deployed in cascade, and resource management orchestration (RO) nodes can be cascaded.
- VIM virtual facility Manager
- RO resource management orchestration
- the network function virtualization NFV network system 10 includes two virtual facility manager (VIM) nodes, and the two virtual facility manager (VIM) nodes are respectively
- the first virtual facility manager (VIM) node 1051 and the second virtual facility manager (VIM) node 1052 may have the following connection modes:
- the difference from FIG. 3 is that the first virtual facility manager (VIM) node 1051 is respectively connected to the VNFM node 104, the NFVI node 111, and the RO node 102;
- VIM virtual facility manager
- the second virtual facility manager (VIM) node 1052 is connected to the NFVI node 111 and the RO node 102, respectively;
- the first virtual facility manager VIM node 1051 is coupled to the second virtual facility manager VIM node 1052.
- the network function virtualization (NFO) node 101 in the network function virtualization NFV network system 10 can select the deployment and virtual network function manager (VNFM) node according to the actual situation. 104 connection.
- the Network Service Orchestration (NSO) node 101 can directly query the VNF instance information and the like from the Network Function Manager (VNFM) node 104, or send a VNF instance management instruction to the Network Function Manager (VNFM) node 104, for example, , expand, update, terminate VNF instances, and more.
- VNFM Virtual Network Function Manager
- the difference from FIG. 11 is that the network service orchestration (NSO) node 101 can be associated with the catalogue 106, the network function virtualization instance NF V ( Instances ) 107 and The network function virtual facility resource (NFVI Resources) 108 is connected, and the resource management orchestration (RO) node 102 can also be associated with the catalogue 106, the network function virtualization instance NFV.
- NSO network service orchestration
- NF V Instances
- NFVI Resources The network function virtual facility resource
- NFVI Resources network function virtual facility resource
- NSO network service orchestration
- the (RO) node 102 simultaneously shares the catalogue 106, the network function virtualization instance NF V ( Instances ) 107 and the network function virtual facility resource ( NFVI Resources ) 108 , the directory including the web service catalog ( NS catalog ) 1061 And the VNF catalog 1062. In this way, the deployment of the network service orchestration function and the resource management orchestration function of the network function virtualization network can be made more flexible.
- the network function virtualization NFV network system 10 in the network service orchestration ( NSO ) node 101 can select the deployment and virtual network function manager according to the actual situation ( VNFM
- the node 104 is connected, and the network service orchestration (NSO) node 101 can be connected to the catalogue 106, the network function virtualization instance NF V (Instances) 107, and the network function virtual facility resource (NFVI Resources) 108,
- the resource management orchestration (RO) node 102 can also be connected to the catalogue 106, the network function virtualization instance NFV (Instances) 107, and the network function virtual facility resource (NFVI Resources) 108, that is, the network service orchestration.
- the (NSO) node 101 and the resource management orchestration (RO) node 102 simultaneously share the catalogue 106, the network function virtualization instance NF V (Instances) 107, and the network function virtual facility resource (NFVI Resources) 108,
- the directory includes the NS catalog 1061 and VNF catalog 1062.
- the network function virtualization NFV network system 10 may further include an NSL Catalog (Network Service Logic) 112 for storing deployment-related Business logic data, user-related data, and policy information, such as network function virtualization NFV network address, IP address, etc., user network selection policy, QoS (Quality of Service) policy information, load balancing scenario MME (Mobility Management Entity) , mobility management entity) Select policy information, etc.
- NSL Catalog Network Service Logic
- a Network Service Orchestration (NSO) node 101 can be coupled to the Network Service Logical Directory (NSL Catalog) 112.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the NSO node is connected to one of the RO nodes, and the RO node is respectively connected to N-1 the RO nodes, and each of the N-1 RO nodes One RO node is connected to at least one of the VIM nodes.
- the network function virtualization NFV network system 10 includes three virtual facility manager (VIM) nodes and three resource management orchestration (RO) nodes.
- the three virtual facility managers (VIM) The nodes are a first virtual facility manager (VIM) node 1051, a second virtual facility manager (VIM) node 1052, a third virtual facility manager (VIM) node 1053, respectively; the three resource management orchestration (RO) nodes
- the first resource management orchestration (RO) node 1021, the second resource management orchestration (RO) node 1022, and the third resource management orchestration (RO) node 1023 may have the following connection manners:
- the (RO) node 1021 is connected to the second resource management orchestration (RO) node 1022 and the third resource management orchestration (RO) node 1023, respectively, and the first resource management orchestration (RO) node 1021 is also associated with the virtual network function manager (VNFM). ) node 104, directory
- Network function virtualization instance (NFV Instances) 107 and network function virtual facility resource (NFVI Resources) 108 are connected, connected to the first network node 103 through the c interface, and through the b interface and the network service orchestration (NSO) node 101 connection;
- NSO network service orchestration
- a second resource management orchestration (RO) node 1022 is coupled to a first virtual facility manager (VIM) node 1051 and a second virtual facility manager (VIM) node 1052, respectively;
- a third resource management orchestration (RO) node 1023 is coupled to a third virtual facility manager (VIM) node 1053;
- a first virtual facility manager (VIM) node 1051 is coupled to a second virtual facility manager (VIM) node 1052 and the NFVI node 111, respectively;
- a second virtual facility manager (VIM) node 1052 is coupled to the NFVI node 111;
- a third virtual facility manager (VIM) node 1053 is coupled to the NFVI node 111.
- the network function virtualization (NFO) node 101 in the network function virtualization NFV network system 10 can select the deployment and virtual network function manager (VNFM) node according to the actual situation. 104 connection.
- the network service orchestration (NS0) node 101 can directly query the VNF instance information and the like from the network function manager (VNFM) node 104, or send a VNF instance management instruction to the network function manager (VNFM) node 104, for example, , expand, update, terminate VNF instances, and more.
- VNFM Virtual Network Function Manager
- the Network Service Orchestration (NSO) node 101 can be associated with the catalogue 106, the network function virtualization instance NF V (Instances) 107, and the network function.
- a virtual facility resource (NFVI Resources) 108 is connected, and the resource management orchestration (RO) node 102 can also be associated with the catalogue 106, a network function virtualization instance NFV.
- NFVI Resources network function virtual facility resource
- NSO network service orchestration
- the (RO) node 102 simultaneously shares the catalogue 106, the network function virtualization instance NF V ( Instances ) 107 and the network function virtual facility resource ( NFVI Resources ) 108 , the directory including the web service catalog ( NS catalog ) 1061 And the VNF catalog 1062. In this way, the deployment of the network service orchestration function and the resource management orchestration function of the network function virtualization network can be made more flexible.
- the difference from FIG. 19 is that the network function virtualization (NFO) node 101 in the network function virtualization NFV network system 10 can select the deployment and virtual network function manager (VNFM) node according to the actual situation.
- NFO network function virtualization
- VNFM virtual network function manager
- the network service orchestration (NSO) node 101 can be connected to the catalogue 106, the network function virtualization instance NF V (Instances) 107, and the network function virtual facility resource (NFVI Resources) 108, Resource Management Orchestration (RO) node 102 can also be associated with the catalogue (catalogue) 106, network function virtualization instance
- the NFV (Instances) 107 and the Network Function Virtual Facility (NF VI Resources) 108 are connected, that is, the Network Service Orchestration (NSO) node 101 and the Resource Management Orchestration (RO) node 102 share the catalogue at the same time.
- the network function virtualization instance NF V (Instances) 107 and the network function virtual facility resource (NFVI Resources) 108, the directory includes a network service directory (NS catalog) 1061 and a virtual network function catalog (VNF catalog) 1062.
- the network function virtualization NFV network system 10 may further include an NSL Catalog (Network Service Logic) 112 for storing deployment-related Business logic data, user-related data, and policy information, such as network function virtualization NFV network address, IP address, etc., user network selection policy, QoS (Quality of Service) policy information, load balancing scenario MME (Mobility Management Entity) , mobility management entity) Select policy information, etc.
- NSL Catalog Network Service Logic
- a Network Service Orchestration (NSO) node 101 can be coupled to the Network Service Logical Directory (NSL Catalog) 112.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the virtualized NFV network system 10 includes three virtual facility manager (VIM) nodes and two resource management orchestration (RO) nodes, which are respectively the first virtual facility manager ( VIM) node 1051, second virtual facility manager (VIM) node 1052, third virtual facility manager (VIM) node 1053; the two resource management orchestration (RO) nodes are respectively the first resource management orchestration (RO)
- the node 1021 and the second resource management orchestration (RO) node 1022 may have the following connection manners:
- the difference from FIG. 3 is that the first resource management orchestration (RO) node 1021 is connected to the third virtual facility manager (VIM) node 1053, and the first resource management orchestration (RO) node 1021 is connected. Also connected to a virtual network function manager (VNFM) node 104, a catalogue 106, a network function virtualization instance (NFV Instances) 107, and a network function virtual facility resource (NF VI Resources) 108, respectively, through the c interface and the first The network node 103 is connected, and is connected to the network service orchestration (NSO) node 101 through the b interface;
- VNFM virtual network function manager
- NSO network service orchestration
- the second resource management orchestration (RO) node 1022 is connected to the first virtual facility manager (VIM) node 1051 and the second virtual facility manager (VIM) node 1052, respectively, and the second resource management orchestration (RO) node 1021 is also respectively associated with A virtual network function manager (VNFM) node 104, a catalogue 106, a network function virtualization instance (NFV Instances) 107, and a network function virtual facility resource (NFVI Resources) 108 are connected, and are connected to the first network node 103 through the c interface. Connected to the Network Service Orchestration (NSO) node 101 via the b interface;
- NSO Network Service Orchestration
- a first virtual facility manager (VIM) node 1051 is coupled to a second virtual facility manager (VIM) node 1052 and the NFVI node 111, respectively;
- a second virtual facility manager (VIM) node 1052 is coupled to the NFVI node 111;
- a third virtual facility manager (VIM) node 1053 is connected to the NFVI node 111.
- the network function virtualization (NFO) node 101 in the network function virtualization NFV network system 10 can select the deployment and virtual network function manager (VNFM) node according to the actual situation. 104 connection.
- the Network Service Orchestration (NSO) node 101 can directly query the VNF instance information and the like from the Network Function Manager (VNFM) node 104, or send a VNF instance management instruction to the Network Function Manager (VNFM) node 104, for example, , expand, update, terminate VNF instances, and more.
- VNFM Virtual Network Function Manager
- the network service orchestration (NSO) node 101 can be associated with the catalogue 106, the network function virtualization instance NF V (Instances) 107, and the network function.
- a virtual facility resource (NFVI Resources) 108 is connected, and the resource management orchestration (RO) node 102 can also be associated with the catalogue 106, a network function virtualization instance NFV.
- NFVI Resources network function virtual facility resource
- NSO network service orchestration
- the (RO) node 102 simultaneously shares the catalogue 106, the network function virtualization instance NF V ( Instances ) 107 and the network function virtual facility resource ( NFVI Resources ) 108 , the directory including the web service catalog ( NS catalog ) 1061 And the VNF catalog 1062. In this way, the deployment of the network service orchestration function and the resource management orchestration function of the network function virtualization network can be made more flexible.
- the difference from FIG. 27 is that the network function virtualization (NFO) node 101 in the network function virtualization NFV network system 10 can select the deployment and virtual network function manager (VNFM) node according to the actual situation.
- NFO network function virtualization
- VNFM virtual network function manager
- the network service orchestration (NSO) node 101 can be associated with the catalogue (
- the network function virtualization instance NF V ( Instances ) 107 and the network function virtual facility resource ( NFVI Resources ) 108 are connected, and the resource management orchestration ( RO ) node 102 can also be associated with the catalogue ( catalogue ) 106 , network function virtualization
- the instance NFV (Instances) 107 and the network function virtual facility resource (NF VI Resources) 108 are connected, that is, the network service orchestration (NSO) node 101 and the resource management orchestration (RO) node 102 simultaneously share the catalogue ( catalogue) 106.
- the network function virtualization instance NF V (Instances) 107 and the network function virtual facility resource (NFVI Resources) 108, the directory includes a network service directory (NS catalog) 1061 and a virtual network function catalog (VNF catalog) 1062.
- the network function virtualization NFV network system 10 may further include an NSL Catalog (Network Service Logic) 112 for storing deployment-related Business logic data, user-related data, and policy information, such as network function virtualization NFV network address, IP address, etc., user network selection policy, QoS (Quality of Service) policy information, load balancing scenario MME (Mobility Management Entity) , mobility management entity) Select policy information, etc.
- NSL Catalog Network Service Logic
- a Network Service Orchestration (NSO) node 101 can be coupled to the Network Service Logical Directory (NSL Catalog) 112.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112 to which the network service orchestration (NSO) node 101 can communicate with the network.
- NSL Catalog network service logical directory
- the Service Logical Directory ( NSL Catalog ) 112 is connected.
- the network function virtualization NFV network system 10 may further include a network service logical directory (NSL Catalog) 112, A Network Service Orchestration (NSO) node 101 can be coupled to the Network Service Logical Directory (NSL Catalog) 1 12 .
- NSO Network Service Orchestration
- the deployment of the resource management RO node can be determined according to the data of the data center, that is, one RO node can be deployed in one data center. For example, Beijing Mobile deployed five data centers in Beijing, and five data centers all manage resources by their respective RO nodes. Beijing Mobile can deploy a total RO node. The total RO node manages the five data centers.
- One data center can be managed by one or more VIM nodes in cascade. Both the RO node and the VIM node are managed. Can be cascaded deployment.
- the division of the NSO node and the RO node can also be divided within the NFVO node, and the interface associated with the NSO node and the RO node is also the internal interface of the NF VO node.
- the first network is a third-party software Networker
- network function virtualization can be realized.
- the NFV network system capability is open, and an external application is provided with an API (Application Program Interface) for user and service optimization.
- the network function virtualization NF V network system of the present invention is only a schematic description, and there may be a virtualized NFV network system diagram of any one of the network functions in FIG. 2 to FIG. 34, which is not limited by the present invention. In practical applications, There may be other scenarios as well, for example there may be more than two NSO nodes, each NSO node may be connected to at least one RO node.
- An embodiment of the present invention provides a data processing method for a network function virtualization network, where the data processing method of the network function virtualization network is used for a network service orchestration NSO node, as shown in FIG. 35, the method includes:
- Step 201 Receive a network service requirement message sent by the first network node, where the network service requirement message includes a network service requirement, where the network service requirement is a parameter value required for deploying a virtual network function VNF node, where the first network node Support OSES or third-party software systems for operations.
- Step 202 Generate a second configuration according to the network service requirement and the first configuration file.
- the first configuration file is a configuration file describing the VNF node
- the second configuration file is a configuration file describing a network service.
- Step 203 Send a second configuration file message to the resource management orchestration RO node, where the second configuration file message includes a second configuration file.
- Step 204 Receive a second configuration file configuration response message sent by the RO node.
- the network service orchestration function in the prior art is implemented by the NSO node, and the deployment of the network service scheduling function and the resource management orchestration function of the network function virtualization network can be more flexible than the prior art.
- the NSO node may directly query the directory catalogue, from the The first configuration file is obtained in the directory, and the directory includes a network service directory NS catalog and a virtual network function directory VNF catalog.
- the NSO node may send a query directory request message to the RO node, and receive a query directory request response message sent by the RO node, where the query directory request response message includes a first configuration file.
- the network service orchestration NSO node connects two or more resource management orchestration RO nodes, and the network service orchestration NSO node may virtualize the global view of the network resources to at least one of the resources according to the locally stored network function.
- the management orchestration RO node sends the second configuration file message, where the second configuration file includes network service related information, virtualized network node related information, virtualized network node characteristic related information, and user subscription related information, where the network service is related.
- the information includes a network service type, a network service capacity requirement, and a network policy
- the virtualized network node related information includes a virtualized network node type and a virtualized network node.
- the network function virtualized network resource global view records the deployment of resources of the virtual network function nodes in the network function virtualization network.
- the network service orchestration NSO node is connected to a resource management orchestration RO node, and the RO node is connected to at least one resource management orchestration RO node, where the network service orchestration NSO node may send the RO node to the one resource management orchestration
- the second configuration file includes: network service related information, virtualized network node related information, virtualized network node characteristic related information, and user subscription related information, where the network service related information includes a network service type
- 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 chain.
- the virtualized network node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting
- the user subscription related information includes a number of users, a network selection policy, and a service quality.
- the network service orchestration NSO node may send a network service instantiation request message to the RO node, and then receive the first network.
- the network service modification request message sent by the node includes the network service modification requirement, where the network service modification requirement is to configure the network service, update the network service, or terminate the network service.
- the network service orchestration NSO node may obtain network service information from the directory and network function virtual facility resource NFVI Resources, Internet service The information includes the status and load of the network service, and the NSO node is respectively connected to the directory and the network function virtual facility resource.
- the network service orchestration NSO node may obtain network service information from the directory and network function virtual facility resource NFVI Resources through the RO node, where the network service information includes a status and a load of the network service.
- the network service orchestration NSO node may further send the query network service information response message to the first network node.
- the network service orchestration NSO node further has at least one of a management network service instance topology, a management network service instance automation configuration, a management network service policy information, and a management network service failure.
- An embodiment of the present invention provides a data processing method for a network function virtualization network, where the data processing method of the network function virtualization network is used for resource management or RO node, as shown in FIG. 36, the method includes:
- Step 301 Receive a network service orchestration query request message sent by the NSO node.
- Step 302 Query the directory catalogue to obtain the first configuration file.
- Step 303 Send a query directory request response message to the NSO node, where the query directory request response message includes a first configuration file.
- Step 304 Receive a second configuration file message sent by the NSO node, where the second configuration file message includes a second configuration file, where the second configuration file is a configuration file that describes a network service.
- Step 305 Send a second configuration file response message to the NSO node.
- the resource management orchestration function in the prior art is implemented through the RO node, and the deployment of the network service orchestration function and the resource management orchestration function of the network function virtualization network can be more flexible than the prior art.
- the resource management orchestration RO node may also manage the NFVI resource failure, and send the NFVI resource failure information or the NFVI resource global view information to the first network, where the first network
- the node is an operational support system OS S or a third-party software system.
- the embodiment of the invention provides a data processing method for a network function virtualization network, which is applied to a network function virtualization NFV network system. As shown in FIG. 37, the method includes:
- Step 401 The first network node sends a network service requirement message to the network service orchestration NSO node.
- the network service requirement message includes a network service requirement, which is a parameter value required for deploying a virtual network function V N F node, and the first network node is an operation support system OS S or a third-party software system.
- the network service requirements include the number of users, time, geographic location, service quality requirements, and capacity requirements.
- Step 402 The NSO node generates a second configuration file according to the network service requirement and the first configuration file.
- the first configuration file is a configuration file describing the VNF node
- the second configuration file is a configuration file describing a network service
- the first configuration file includes an information element of a VNF
- the second configuration file includes a network.
- the service describes the information element of the NSD.
- the second configuration file includes network service related information, virtualized network node related information, virtualized network node characteristic 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 extension.
- the virtualized network node related information includes a virtualized network node type, a virtualized network node capacity requirement, and a virtualized network node deployment
- the location and virtualization network node interconnect link requirements, the virtualized network node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting, where the user subscription related information includes the number of users, network selection Strategy and quality of service.
- the NSO node may generate a second configuration file by using a template according to a network service requirement, a virtual network function description (VNFD), and a virtual network function parameter description (VNFCD), where the NSO node stores a template, and the VNFD, VNFCD, and the like may be pre- Configured in the NSO node.
- VNFD virtual network function description
- VNFCD virtual network function parameter description
- the network service requirements include number of users, time, geographic location, service quality requirements, capacity requirements, etc.
- the parameter values required for deploying the virtual network function VNF node, and the NS 0 node determines the required VNF through the network service requirement, including MME (Mobility Management Entity, mobility management entity), SGW (Signal Gate Way), and packet data network.
- a function node such as a gateway (PGW), a VOG (Vedio Optimization Gateway), and determining the corresponding performance and capacity requirements of the different function nodes, and determining all the information elements in the VNFD by finding the VNFD to generate a Constituent VNF.
- PGW gateway
- VOG Vedio Optimization Gateway
- Service deployment flavour is generated, that is, List of service deployment flavours in NSD, and other information elements in NSD are determined in a similar manner.
- the information elements of the configuration files such as NSD and VNFD can be referred to the description in the GS NFV-MAN 001 V0.3.15 (2014-04) protocol.
- the NSO node queries the directory catalogue, and obtains a first configuration file from the directory, where the NSO node Connected to the directory, the directory includes a network service directory NS catalog and a virtual network function directory VNF catalog.
- the NSO node is configured according to the network service requirement and the first configuration Before the file generates the second configuration file, the NSO node sends a query directory request message to the RO node; the RO node queries the directory catalogue to obtain a first configuration file; and the RO node sends a query directory request response to the NSO node.
- the message, the query directory request response message includes a first configuration file.
- Step 403 The NSO node sends a second configuration file message to the resource management orchestration RO node.
- the second profile message includes a second profile.
- the network service orchestration NSO node connects two or more resource management orchestration RO nodes, and the NSO node manages the RO node to at least one of the resource management according to the locally stored network function virtualization network resource global view. Sending the second profile message.
- the network service orchestration NSO node is connected to a resource management orchestration RO node, the RO node is connected to at least one resource management orchestration RO node, and the NSO node sends the second node to the one resource management orchestration RO node.
- the resource management orchestration RO node may send the second profile message to the at least one resource management orchestration RO node according to the locally stored network function virtualization network resource global view.
- Step 404 The RO node sends a second configuration file response message to the NSO node.
- Step 405 The NSO node sends a network service instantiation request message to the RO node.
- the NSO node, the RO node, the VNFM, and the VIM exchange information to perform a network service instantiation process.
- 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, where the network service modification requirement is to configure a network service, update Network service or termination of network services.
- the NSO node is also used to manage a network service instance topology, Management network service instance automation configuration, management network service policy information and management network service failure at least one; the RO node is also used to manage NFVI resource failure.
- the network service orchestration function in the prior art is implemented by the NSO node, and the resource management orchestration function in the prior art is implemented by the RO node.
- the network function of the network function virtualization network can be enabled.
- the deployment of orchestration and resource management orchestration functions is more flexible.
- the embodiment of the present invention provides a network service orchestration NSO node 50, as shown in FIG. 38, including:
- the first receiving unit 501 is configured to receive a network service requirement message sent by the first network node, where the network service requirement message includes a network service requirement, where the network service requirement is a parameter value required for deploying the virtual network function VNF node, where The first network node is an operation support system OS S or a third-party software system.
- the network service requirements include the number of users, time, geographic location, service quality requirements, and capacity requirements.
- a generating unit 502 configured to generate a second configuration file according to the network service requirement and the first configuration file, where the first configuration file is a configuration file describing the VN F node, and the second configuration file is a description network service Configuration file.
- the first configuration file is a configuration file describing the VNF node
- the second configuration file is a configuration file describing a network service
- the first configuration file includes an information element of a VNF
- the second configuration file includes a network.
- the service describes the information element of the NSD.
- the second configuration file includes network service related information, virtualized network node related information, virtualized network node characteristic 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 extension.
- the virtualized network node related information includes a virtualized network node type, a virtualized network node capacity requirement, and a virtualized network node deployment
- the location and virtualization network node interconnect link requirements, the virtualized network node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting, where the user subscription related information includes the number of users, network selection Strategy and quality of service.
- the NSO node may generate a second configuration file by using a template according to a network service requirement, a virtual network function description (VNFD), and a virtual network function parameter description (VNFCD), where the NSO node stores a template, and the VNFD, VNFCD, and the like may be pre- Configured in the NSO node.
- VNFD virtual network function description
- VNFCD virtual network function parameter description
- the network service requirements include number of users, time, geographic location, service quality requirements, capacity requirements, etc.
- the parameter values required for deploying the virtual network function VNF node, and the NS 0 node determines the required VNF through the network service requirement, including MME (Mobility Management Entity, mobility management entity), SGW (Signal Gate Way), and packet data network.
- a function node such as a gateway (PGW), a VOG (Vedio Optimization Gateway), and determining the corresponding performance and capacity requirements of the different function nodes, and determining all the information elements in the VNFD by finding the VNFD to generate a Constituent VNF.
- PGW gateway
- VOG Vedio Optimization Gateway
- Service deployment flavour is generated, that is, List of service deployment flavours in NSD, and other information elements in NSD are determined in a similar manner.
- the information elements of the configuration files such as NSD and VNFD can be referred to the description in the GS NFV-MAN 001 V0.3.15 (2014-04) protocol.
- the first sending unit 503 is configured to send a second configuration file message to the resource management orchestration RO node, where the second configuration file message includes a second configuration file.
- the second receiving unit 504 is configured to receive a second configuration file configuration response message sent by the RO node.
- the network service orchestration function in the prior art is implemented by the NSO node, and the network service of the network function virtualization network can be edited compared to the prior art.
- the deployment of the platoon function and the resource management orchestration function is more flexible.
- the network service orchestration NSO node 50 further includes: a querying unit 505, configured to query a directory catalogue, obtain a first configuration file from the directory, where the NSO node is connected to the directory,
- the directory includes a web service directory NS catalog and a virtual network function catalog VNF catalog.
- the third sending unit 508 is configured to:
- a network service instantiation request message is sent to the RO node.
- the fourth receiving unit 509 is configured to:
- Network service modification requirement message sent by the first network node, where the network service modification requirement message includes a network service modification requirement, where the network service modification requirement is to configure a network service, update a network service, or terminate a network service.
- the obtaining unit 5010 is configured to:
- the network service information including a status and a load of the network service, wherein the NSO node is respectively connected to the directory and the network function virtual facility resource;
- the network service information includes a status and a load of the network service.
- the fourth sending unit 501 1 is configured to:
- Management unit 5012 for:
- the management unit 5012 is further configured to manage a network service instance topology
- the management unit 5012 is also used to manage the network service instance automation configuration
- the management unit 5012 is further configured to manage network service policy information
- the management unit 5012 is also used to manage network service failures.
- the network service orchestration NSO node 50 further includes: a second sending unit 506, configured to send a query directory request to the RO node.
- Interest rate a second sending unit 506, configured to send a query directory request to the RO node.
- the third receiving unit 507 is configured to receive a query directory request response message sent by the RO node, where the query directory request response message includes a first configuration file.
- the third sending unit 508 is configured to:
- a network service instantiation request message is sent to the RO node.
- the fourth receiving unit 509 is configured to:
- Network service modification requirement message sent by the first network node, where the network service modification requirement message includes a network service modification requirement, where the network service modification requirement is to configure a network service, update a network service, or terminate a network service.
- the obtaining unit 5010 is configured to:
- the network service information including a status and a load of the network service, wherein the NSO node is respectively connected to the directory and the network function virtual facility resource;
- the network service information includes a status and a load of the network service.
- the fourth sending unit 501 1 is configured to:
- Management unit 5012 for:
- the management unit 5012 is further configured to manage a network service instance topology
- the management unit 5012 is also used to manage the network service instance automation configuration
- the management unit 5012 is further configured to manage network service policy information
- the management unit 5012 is also used to manage network service failures.
- the network scheduling service NSO node connects two or more resource management RO nodes, and the first sending unit 503 is specifically configured to:
- the configuration file includes network service related information, virtualized network node related information, virtualized network node characteristic related information, and user subscription related information
- the network service related information includes network service type, network service capacity requirement, and network scaling policy (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, and the virtualized network node characteristic related information
- the virtual network node channel number and the virtualized network node service area setting are included, and the user subscription related information includes a number of users, a network selection policy, and a quality of service.
- the network service orchestration NSO node is connected to a resource management orchestration RO node, and the RO node is connected to at least one resource management orchestration RO node, and the first sending unit 503 is specifically configured to:
- the network service related information includes a network service type, a network service capacity requirement, and a network policy, where the virtualized network node related information includes a virtualized network node type, a virtualized network node capacity requirement, and a virtualized network node. a deployment location and a virtualized network node interconnection link requirement, where the virtualized network node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting, and the user subscription related information includes a number of users, a network choose a strategy and quality of service.
- the NSO node has at least one network service function in a network service function, and the network service function includes:
- VNFM node is used to manage VNF instantiation
- the embodiment of the present invention provides a resource management orchestration RO node 60, as shown in FIG. 41, including:
- the first receiving unit 601 is configured to receive a query directory request message sent by the network service orchestration NSO node.
- the query unit 602 is configured to query the directory catalogue to obtain the first configuration file.
- the first sending unit 603 is configured to send a query directory request response message to the NSO node, where the query directory request response message includes a first configuration file.
- the second receiving unit 604 is configured to receive a second configuration file message sent by the NSO node, where the second configuration file message includes a second configuration file, where the second configuration file is a configuration file describing a network service.
- the second sending unit 605 is configured to send a second configuration file response message to the NSO node.
- the resource management orchestration function in the prior art is implemented through the RO node, and the deployment of the network service orchestration function and the resource management orchestration function of the network function virtualization network can be more flexible than the prior art.
- the resource management orchestration RO node 60 further includes:
- the third receiving unit 606 is configured to receive a network service instantiation request message sent by the NSO node.
- the management unit 607 is used to manage NF VI resource failure.
- the third sending unit 608 is configured to send the NFVI resource failure information to the first network.
- the first network node is an operation support system OSS or a third-party software system.
- the RO node has at least one of a global resource management function and a coordinated management allocation virtualized resource function, and the global resource management function and the unified management allocation virtualized resource function include:
- NFVI resource request verification and authorization NFVI resources are distributed across multiple VIM nodes
- VNF instances Relation Management of VNF instances, relationship management between VNF instances and NFVI resources assigned to VNF instances;
- the embodiment of the present invention provides a network service orchestration NSO node 70, as shown in FIG. 43, and includes:
- the receiver 701 is configured to receive a network service requirement message sent by the first network node, where the network service requirement message includes a network service requirement, where the network service requirement is a parameter value required for deploying the virtual network function VNF node, where A network node is an operational support system OS S or a third-party software system.
- the network service requirements include the number of users, time, geographic location, service quality requirements, and capacity requirements.
- the processor 702 is configured to generate a second configuration file according to the network service requirement and the first configuration file, where the first configuration file is a configuration file describing the VNF node.
- the second configuration file is a configuration file describing a network service.
- the first configuration file is a configuration file describing the VNF node
- the second configuration file is a configuration file describing a network service
- the first configuration file includes an information element of a VNF
- the second configuration file includes a network.
- the service describes the information element of the NSD.
- the second configuration file includes network service related information, virtualized network node related information, virtualized network node characteristic 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 extension.
- 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
- the node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting, and the user subscription related information includes a number of users, a network selection policy, and a quality of service.
- the NSO node may generate a second configuration file by using a template according to a network service requirement, a virtual network function description (VNFD), and a virtual network function parameter description (VNFCD), where the NSO node stores a template, and the VNFD, VNFCD, and the like may be pre- Configured in the NSO node.
- VNFD virtual network function description
- VNFCD virtual network function parameter description
- the network service requirements include number of users, time, geographic location, service quality requirements, capacity requirements, etc.
- the parameter values required for deploying the virtual network function VNF node, and the NS 0 node determines the required VNF through the network service requirement, including MME (Mobility Management Entity, mobility management entity), SGW (Signal Gate Way), and packet data network.
- a function node such as a gateway (PGW), a VOG (Vedio Optimization Gateway), and determining the corresponding performance and capacity requirements of the different function nodes, and determining all the information elements in the VNFD by finding the VNFD to generate a Constituent VNF.
- PGW gateway
- VOG Vedio Optimization Gateway
- Constituent VNF generate Service deployment flavour, ie List of service deployment flavours in NSD, other information elements in NSD are determined in a similar way.
- the information elements of the configuration files such as NSD and VNFD can be referred to the description in the GS NFV-MAN 001 V0.3.15 (2014-04) protocol.
- the transmitter 703 is configured to send a second configuration file message to the resource management orchestration RO node, where the second configuration file message includes a second configuration file.
- the receiver 701 is further configured to receive a second configuration file configuration response message sent by the RO node.
- the network service orchestration function in the prior art is implemented by the NSO node, and the deployment of the network service scheduling function and the resource management orchestration function of the network function virtualization network can be more flexible than the prior art.
- the processor 702 is further configured to query a directory catalogue, and obtain a first configuration file from the directory, where the NSO node is connected to the directory, and the directory includes a network service directory NS catalog and a virtual network function directory VNF catalog.
- the transmitter 703 is further configured to send a query directory request message to the RO node;
- the receiver 701 is further configured to receive a query directory request response message sent by the RO node, where the query directory request response message includes a first configuration file.
- the network monthly scheduling NSO node connects two or more resource management RO nodes, and the transmitter 703 is specifically configured to:
- the second configuration file message Transmitting, according to the locally stored network function virtualized network resource global view, the second configuration file message to at least one of the resource management orchestration RO nodes, where the second configuration file includes network service related information, virtualized network node related information, Virtualizing network node characteristic related information and user subscription related information, the network service related information includes a network service type, a network service capacity requirement, and a network scaling policy, where the virtualized network node related information includes a virtualized network node Type, virtualized network node capacity requirement, virtualized network node deployment location, and virtualized network node interconnection link requirement, the virtualized network node characteristic related information including virtualization
- the network node channel number and the virtualized network node service area setting, the user subscription related information includes the number of users, the network selection policy, and the quality of service.
- the network service orchestration NSO node is connected to a resource management orchestration RO node, and the RO node is connected to at least one resource management orchestration RO node, and the transmitter 703 is specifically configured to:
- the network service related information includes a network service type, a network service capacity requirement, and a network policy, where the virtualized network node related information includes a virtualized network node type, a virtualized network node capacity requirement, and a virtualized network node. a deployment location and a virtualized network node interconnection link requirement, where the virtualized network node characteristic related information includes a virtualized network node channel number and a virtualized network node service area setting, and the user subscription related information includes a number of users, a network choose a strategy and quality of service.
- the transmitter 703 is also used to:
- a network service instantiation request message is sent to the RO node.
- the receiver 701 is further configured to:
- Network service modification requirement message sent by the first network node, where the network service modification requirement message includes a network service modification requirement, where the network service modification requirement is to configure a network service, update a network service, or terminate a network service.
- the processor 702 is further configured to:
- the network service information including a status and a load of the network service, wherein the NSO node is respectively connected to the directory and the network function virtual facility resource;
- the transmitter 703 is also used to:
- the processor 702 is further configured to:
- the NSO node has at least one network service function in a network service function, and the network service function includes:
- VNF instantiation is managed in conjunction with the VNFM node
- the embodiment of the present invention provides a resource management orchestration RO node 80, as shown in FIG. 44, including:
- the receiver 801 is configured to receive a query directory request message sent by the network service orchestration NSO node.
- the processor 802 is configured to query the directory catalogue to obtain the first configuration file.
- the query directory request response message includes a first configuration file.
- 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, where the second configuration file is a configuration file describing a network service;
- the transmitter 803 is further configured to send a second profile response message to the NSO node.
- the resource management orchestration function in the prior art is implemented through the RO node, and the deployment of the network service orchestration function and the resource management orchestration function of the network function virtualization network can be more flexible than the prior art.
- the receiver 801 is further configured to receive a network service instantiation request message sent by the NSO node.
- the processor 802 is also used to manage NFVI resource failures.
- the transmitter 803 is further configured to send NFVI resource failure information or NFVI resource global view information to the first network, where the first network node is an operation support system OS S or a third-party software system.
- the RO node has at least one of a global resource management function and a coordinated management allocation virtualized resource function, and the global resource management function and the unified management allocation virtualized resource function include:
- NFVI resource request verification and authorization NFVI resources are distributed across multiple VIM nodes
- VNF instances Relation Management of VNF instances, relationship management between VNF instances and NFVI resources assigned to VNF instances;
- NFVI resource-related view records used by VNF instances or instance groups; NFVI resource fault management.
- the disclosed apparatus and method may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
- the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
- the units described as separate components may or may not be physically separated, and the components displayed as the units may or may not be physical units, and may be located in one place or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiment of the present embodiment.
- each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
- the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14891882.4A EP3133794B1 (en) | 2014-05-15 | 2014-05-15 | Network function virtualization network system |
PCT/CN2014/077581 WO2015172362A1 (zh) | 2014-05-15 | 2014-05-15 | 一种网络功能虚拟化网络系统、数据处理方法及装置 |
CN201480017564.4A CN105284094B (zh) | 2014-05-15 | 2014-05-15 | 一种网络功能虚拟化网络系统、数据处理方法及装置 |
BR112016026543-2A BR112016026543B1 (pt) | 2014-05-15 | 2014-05-15 | Sistema de rede de virtualização de funções de rede |
US15/350,598 US10298439B2 (en) | 2014-05-15 | 2016-11-14 | Network functions virtualization network system and data processing method, and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2014/077581 WO2015172362A1 (zh) | 2014-05-15 | 2014-05-15 | 一种网络功能虚拟化网络系统、数据处理方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/350,598 Continuation US10298439B2 (en) | 2014-05-15 | 2016-11-14 | Network functions virtualization network system and data processing method, and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015172362A1 true WO2015172362A1 (zh) | 2015-11-19 |
Family
ID=54479181
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/077581 WO2015172362A1 (zh) | 2014-05-15 | 2014-05-15 | 一种网络功能虚拟化网络系统、数据处理方法及装置 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10298439B2 (zh) |
EP (1) | EP3133794B1 (zh) |
CN (1) | CN105284094B (zh) |
BR (1) | BR112016026543B1 (zh) |
WO (1) | WO2015172362A1 (zh) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107222324A (zh) * | 2016-03-22 | 2017-09-29 | 华为技术有限公司 | 网络服务的业务配置方法和装置 |
WO2017181875A1 (zh) * | 2016-04-22 | 2017-10-26 | 华为技术有限公司 | 虚拟化网络的部署方法和部署系统 |
CN107404410A (zh) * | 2017-09-08 | 2017-11-28 | 北京百悟科技有限公司 | 一种云环境下构建虚拟网络功能平台的方法及装置 |
EP3285439A4 (en) * | 2015-12-30 | 2018-05-16 | Huawei Technologies Co., Ltd. | Network service lifecycle management method and device |
CN108370329A (zh) * | 2016-06-30 | 2018-08-03 | 华为技术有限公司 | 管理功能对象的管理方法及装置 |
CN109219090A (zh) * | 2017-06-30 | 2019-01-15 | 中兴通讯股份有限公司 | 商务特性数据上报方法及装置、网络切片编排方法及装置 |
EP3468105A4 (en) * | 2016-06-30 | 2019-06-26 | Huawei Technologies Co., Ltd. | METHOD AND APPARATUS FOR ARRANGING NETWORK RESOURCES |
Families Citing this family (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10700946B2 (en) * | 2017-08-08 | 2020-06-30 | Amdocs Development Limited | System, method, and computer program for automatically certifying a virtual network function (VNF) for use in a network function virtualization (NFV) based communication network |
EP3158686B1 (en) * | 2014-06-26 | 2020-01-08 | Huawei Technologies Co., Ltd. | System and method for virtual network function policy management |
US10291689B2 (en) * | 2014-08-20 | 2019-05-14 | At&T Intellectual Property I, L.P. | Service centric virtual network function architecture for development and deployment of open systems interconnection communication model layer 4 through layer 7 services in a cloud computing system |
US9742690B2 (en) | 2014-08-20 | 2017-08-22 | At&T Intellectual Property I, L.P. | Load adaptation architecture framework for orchestrating and managing services in a cloud computing system |
US9473567B2 (en) | 2014-08-20 | 2016-10-18 | At&T Intellectual Property I, L.P. | Virtual zones for open systems interconnection layer 4 through layer 7 services in a cloud computing system |
CN110661647A (zh) * | 2015-07-20 | 2020-01-07 | 华为技术有限公司 | 一种生命周期管理方法及装置 |
US10432461B2 (en) | 2015-12-04 | 2019-10-01 | T-Mobile Usa, Inc. | Peer-to-peer distribution of radio protocol data for software defined radio (SDR) updates |
WO2017166075A1 (zh) * | 2016-03-29 | 2017-10-05 | 华为技术有限公司 | 一种云无线接入网系统、数据处理方法及装置 |
CN107294752A (zh) * | 2016-04-01 | 2017-10-24 | 中兴通讯股份有限公司 | 实现网络功能通信的架构、方法及装置 |
CN107483222B (zh) * | 2016-06-08 | 2021-08-27 | 中兴通讯股份有限公司 | 一种基于微服务化的虚拟网络功能的管理方法及网管系统 |
WO2018006381A1 (zh) * | 2016-07-07 | 2018-01-11 | 华为技术有限公司 | 一种网络资源的管理方法、装置及系统 |
CN107769932B (zh) * | 2016-08-15 | 2021-02-09 | 华为技术有限公司 | 一种计费方法、装置及系统 |
US10616776B2 (en) * | 2016-09-30 | 2020-04-07 | T-Mobile Usa, Inc. | Dynamic provisioning of a gateway role to user devices |
US10257165B2 (en) | 2016-09-30 | 2019-04-09 | T-Mobile Usa, Inc. | Dynamic provisioning of a firewall role to user devices |
US10362482B2 (en) | 2016-12-21 | 2019-07-23 | T-Mobile Usa, Inc. | Network operation and trusted execution environment |
EP3580894A1 (en) * | 2017-02-10 | 2019-12-18 | Intel IP Corporation | Systems, methods and devices for virtual resource metric management |
US10805172B2 (en) | 2017-04-14 | 2020-10-13 | At&T Intellectual Property I, L.P. | Closed-loop deployment of virtual functions and cloud infrastructure |
CN110546980A (zh) * | 2017-04-25 | 2019-12-06 | 英特尔Ip公司 | 虚拟化无线电接入网络中的集中式单元和分布式单元连接 |
US10200463B2 (en) | 2017-05-22 | 2019-02-05 | At&T Intellectual Property I, L.P. | Systems and methods to improve the performance of a network by more efficient virtual network resource allocation |
US11403149B2 (en) * | 2017-10-17 | 2022-08-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Management of a virtual network function |
US10555278B2 (en) * | 2017-11-03 | 2020-02-04 | Comptel Oy | Method and arrangement for allocating communication resources in a communication network |
CN110086640B (zh) * | 2018-01-26 | 2022-01-14 | 华为技术有限公司 | 业务使能的方法和装置 |
WO2019227483A1 (en) * | 2018-06-01 | 2019-12-05 | Huawei Technologies Co., Ltd. | Multiple server-architecture cluster for providing a virtual network function |
KR102036731B1 (ko) * | 2018-09-06 | 2019-10-25 | 숭실대학교산학협력단 | 가상화 네트워크 기능 클러스터링 구성 시스템 및 방법 |
WO2020074687A1 (en) * | 2018-10-11 | 2020-04-16 | Koninklijke Kpn N.V. | Dynamic slice priority handling |
CN109379699B (zh) * | 2018-11-12 | 2020-08-25 | 中国联合网络通信集团有限公司 | 创建虚拟化转发面网元的方法及装置 |
US10797968B2 (en) * | 2018-11-15 | 2020-10-06 | Cisco Technology, Inc. | Automated provisioning of radios in a virtual radio access network |
WO2020098946A1 (en) * | 2018-11-15 | 2020-05-22 | Huawei Technologies Co., Ltd. | Network node and method for supporting a service based architecture |
CN111352767B (zh) * | 2018-12-24 | 2023-07-18 | 中国电信股份有限公司 | 网络功能虚拟化平台资源管理方法、备份平台和系统 |
US10708124B1 (en) * | 2018-12-31 | 2020-07-07 | Facebook, Inc. | System and method of data communication |
CN111641515B (zh) * | 2019-03-01 | 2021-11-19 | 华为技术有限公司 | Vnf的生命周期管理方法及装置 |
CN111082960B9 (zh) * | 2019-04-15 | 2023-01-24 | 中兴通讯股份有限公司 | 数据的处理方法及装置 |
CN112764873B (zh) | 2019-11-05 | 2023-07-14 | 华为技术有限公司 | 实例化ns的方法及nfvo |
CN111510428B (zh) * | 2020-03-09 | 2022-08-05 | 联通(广东)产业互联网有限公司 | 安全资源运维平台系统及管控方法 |
CN111901154B (zh) * | 2020-07-04 | 2022-05-27 | 烽火通信科技股份有限公司 | 基于nfv的安全架构系统和安全部署及安全威胁处理方法 |
CN112261676B (zh) * | 2020-10-10 | 2021-07-09 | 广州爱浦路网络技术有限公司 | 一种5gs中集中式oam资源分配的方法 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102546735A (zh) * | 2011-01-04 | 2012-07-04 | 中兴通讯股份有限公司 | 一种云计算系统、方法及云 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8429630B2 (en) * | 2005-09-15 | 2013-04-23 | Ca, Inc. | Globally distributed utility computing cloud |
CN100493089C (zh) * | 2005-12-26 | 2009-05-27 | 北京航空航天大学 | 基于服务与底层资源分离的服务计算系统 |
JP5644150B2 (ja) * | 2010-03-23 | 2014-12-24 | 日本電気株式会社 | サービス提供システム、仮想マシンサーバ、サービス提供方法及びサービス提供プログラム |
US9276816B1 (en) * | 2011-01-17 | 2016-03-01 | Cisco Technology, Inc. | Resource management tools to create network containers and virtual machine associations |
US9973375B2 (en) * | 2013-04-22 | 2018-05-15 | Cisco Technology, Inc. | App store portal providing point-and-click deployment of third-party virtualized network functions |
US9384028B1 (en) * | 2013-12-19 | 2016-07-05 | Amdocs Software Systems Limited | System, method, and computer program for preserving service continuity in a network function virtualization (NFV) based communication network |
US9760428B1 (en) * | 2013-12-19 | 2017-09-12 | Amdocs Software Systems Limited | System, method, and computer program for performing preventative maintenance in a network function virtualization (NFV) based communication network |
US9430262B1 (en) * | 2013-12-19 | 2016-08-30 | Amdocs Software Systems Limited | System, method, and computer program for managing hierarchy and optimization in a network function virtualization (NFV) based communication network |
EP3094049B1 (en) * | 2014-01-29 | 2018-01-10 | Huawei Technologies Co., Ltd. | Method for upgrading virtualized network function and network function virtualization orchestrator |
EP3104662B1 (en) * | 2014-03-21 | 2019-08-21 | Huawei Technologies Co., Ltd. | Service allocation method and related device |
JP6408602B2 (ja) * | 2014-03-24 | 2018-10-17 | 華為技術有限公司Huawei Technologies Co.,Ltd. | Nfvシステムにおけるサービス実装のための方法および通信ユニット |
US9998320B2 (en) * | 2014-04-03 | 2018-06-12 | Centurylink Intellectual Property Llc | Customer environment network functions virtualization (NFV) |
-
2014
- 2014-05-15 CN CN201480017564.4A patent/CN105284094B/zh active Active
- 2014-05-15 BR BR112016026543-2A patent/BR112016026543B1/pt active IP Right Grant
- 2014-05-15 EP EP14891882.4A patent/EP3133794B1/en active Active
- 2014-05-15 WO PCT/CN2014/077581 patent/WO2015172362A1/zh active Application Filing
-
2016
- 2016-11-14 US US15/350,598 patent/US10298439B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102546735A (zh) * | 2011-01-04 | 2012-07-04 | 中兴通讯股份有限公司 | 一种云计算系统、方法及云 |
Non-Patent Citations (3)
Title |
---|
BHUMIP, KHASNABISH ET AL.: "Virtualizing Network and Service Functions: Impact on ICT Transformation and Standardization", ZTE COMMUNICATIONS, 11 December 2013 (2013-12-11), XP055236157, Retrieved from the Internet <URL:http://www.cnki.net/kcms/detail/34.1294.TN.20131211.1452.002.html> * |
CHEN, WEI ET AL.: "Discussion and Practice on Key Problem of NFV in Mobile Networks", ZTE TECHNOLOGY JOURNAL, vol. 03, 24 April 2014 (2014-04-24), XP055236150, Retrieved from the Internet <URL:http://www.cnki.net/kcms/detail/34.1228.TN.20140425.1003.001.html> * |
See also references of EP3133794A4 * |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3668009A1 (en) * | 2015-12-30 | 2020-06-17 | Huawei Technologies Co. Ltd. | Life cycle management method and device for network service |
EP3285439A4 (en) * | 2015-12-30 | 2018-05-16 | Huawei Technologies Co., Ltd. | Network service lifecycle management method and device |
US10700947B2 (en) | 2015-12-30 | 2020-06-30 | Huawei Technologies Co., Ltd | Life cycle management method and device for network service |
CN107222324B (zh) * | 2016-03-22 | 2021-05-14 | 华为技术有限公司 | 网络服务的业务配置方法和装置 |
CN107222324A (zh) * | 2016-03-22 | 2017-09-29 | 华为技术有限公司 | 网络服务的业务配置方法和装置 |
EP3373518A4 (en) * | 2016-03-22 | 2018-12-12 | Huawei Technologies Co., Ltd. | Service configuration method and device for network service |
US10911331B2 (en) | 2016-03-22 | 2021-02-02 | Huawei Technologies Co., Ltd. | Service configuration method and apparatus for network service |
WO2017181875A1 (zh) * | 2016-04-22 | 2017-10-26 | 华为技术有限公司 | 虚拟化网络的部署方法和部署系统 |
CN108370329A (zh) * | 2016-06-30 | 2018-08-03 | 华为技术有限公司 | 管理功能对象的管理方法及装置 |
EP3468105A4 (en) * | 2016-06-30 | 2019-06-26 | Huawei Technologies Co., Ltd. | METHOD AND APPARATUS FOR ARRANGING NETWORK RESOURCES |
RU2716742C1 (ru) * | 2016-06-30 | 2020-03-16 | Хуавэй Текнолоджиз Ко., Лтд. | Способ и устройство для администрирования объекта администрируемой функции |
EP3462672A4 (en) * | 2016-06-30 | 2019-04-10 | Huawei Technologies Co., Ltd. | ADMINISTRATIVE PROCESS AND DEVICE FOR AN ADMINISTRATIVE FUNCTIONAL OBJECT |
KR20190018520A (ko) * | 2016-06-30 | 2019-02-22 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 관리 기능 대상을 위한 관리 방법 및 장치 |
KR102135651B1 (ko) | 2016-06-30 | 2020-07-20 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 관리 기능 대상을 위한 관리 방법 및 장치 |
CN108370329B (zh) * | 2016-06-30 | 2021-05-18 | 华为技术有限公司 | 管理功能对象的管理方法及装置 |
US11388036B2 (en) | 2016-06-30 | 2022-07-12 | Huawei Technologies Co., Ltd. | Method and apparatus for managing managed function object |
CN109219090A (zh) * | 2017-06-30 | 2019-01-15 | 中兴通讯股份有限公司 | 商务特性数据上报方法及装置、网络切片编排方法及装置 |
CN109219090B (zh) * | 2017-06-30 | 2022-11-08 | 中兴通讯股份有限公司 | 商务特性数据上报方法及装置、网络切片编排方法及装置 |
CN107404410A (zh) * | 2017-09-08 | 2017-11-28 | 北京百悟科技有限公司 | 一种云环境下构建虚拟网络功能平台的方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
EP3133794A4 (en) | 2017-03-29 |
CN105284094B (zh) | 2019-05-28 |
BR112016026543B1 (pt) | 2023-01-24 |
CN105284094A (zh) | 2016-01-27 |
BR112016026543A2 (pt) | 2018-05-15 |
US10298439B2 (en) | 2019-05-21 |
EP3133794B1 (en) | 2019-04-03 |
EP3133794A1 (en) | 2017-02-22 |
US20170063598A1 (en) | 2017-03-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10298439B2 (en) | Network functions virtualization network system and data processing method, and apparatus | |
US11051183B2 (en) | Service provision steps using slices and associated definitions | |
EP3610670B1 (en) | Service provision for offering network slices to a customer | |
CN109952796B (zh) | 可共享切片实例的创建及修改 | |
EP3530037B1 (en) | System and method for network slice management in a management plane | |
US9999030B2 (en) | Resource provisioning method | |
CN108293004B (zh) | 用于网络切片管理的系统和方法 | |
US20180317134A1 (en) | Nssmf nsmf interaction connecting virtual 5g networks and subnets | |
CN110383769B (zh) | 集成服务、网络、和域管理子系统的架构 | |
RU2643451C2 (ru) | Система и способ виртуализации функции мобильной сети | |
US20190021010A1 (en) | Methods and systems for network slicing | |
CN109040276B (zh) | 一种构建云平台的方法、装置、计算机存储介质及终端 | |
WO2017036288A1 (zh) | 一种网元升级方法及设备 | |
CN111183614B (zh) | 5g和非5g管理功能实体间的交互 | |
US20220209991A1 (en) | Systems and methods for automated network configurations with a network as a service (naas) system | |
Ungureanu et al. | Collaborative cloud-edge: A declarative api orchestration model for the nextgen 5g core | |
US20180123896A1 (en) | Systems and methods for hierarchical network management | |
WO2022110944A1 (zh) | 网络切片规划的方法以及相关设备 | |
JP6460743B2 (ja) | 設定情報生成システム及び設定情報生成方法 | |
WO2019024514A1 (en) | VIRTUAL ANCHORING IN MOBILE NETWORKS WITHOUT ANCHORING | |
Oguchi et al. | Virtual data planes for easy creation and operation of end-to-end virtual networks | |
WO2022089291A1 (zh) | 一种数据流镜像方法及装置 | |
US20240147259A1 (en) | Repair atomic deterministic next action | |
CN116074896A (zh) | 多接入边缘计算切片 | |
CN118118447A (zh) | 分布式交换机部署方法及服务器 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201480017564.4 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14891882 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2014891882 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014891882 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112016026543 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112016026543 Country of ref document: BR Kind code of ref document: A2 Effective date: 20161111 |