WO2016155023A1 - 一种网络管理系统、设备及方法 - Google Patents

一种网络管理系统、设备及方法 Download PDF

Info

Publication number
WO2016155023A1
WO2016155023A1 PCT/CN2015/075926 CN2015075926W WO2016155023A1 WO 2016155023 A1 WO2016155023 A1 WO 2016155023A1 CN 2015075926 W CN2015075926 W CN 2015075926W WO 2016155023 A1 WO2016155023 A1 WO 2016155023A1
Authority
WO
WIPO (PCT)
Prior art keywords
service request
network
domain
oss
entity
Prior art date
Application number
PCT/CN2015/075926
Other languages
English (en)
French (fr)
Inventor
季莉
邹兰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2017551624A priority Critical patent/JP6538192B2/ja
Priority to BR112017021248A priority patent/BR112017021248A2/pt
Priority to EP15886993.3A priority patent/EP3276883A4/en
Priority to CN201580061925.XA priority patent/CN107113190B/zh
Priority to PCT/CN2015/075926 priority patent/WO2016155023A1/zh
Publication of WO2016155023A1 publication Critical patent/WO2016155023A1/zh
Priority to US15/722,782 priority patent/US20180026855A1/en

Links

Images

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/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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/509—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to media content delivery, e.g. audio, video or TV
    • 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/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a network management system, device, and method.
  • the network system architecture defined by the existing network function virtualization may include an operation support device (English: operations support system, Abbreviation: OSS), at least one element management (English: element management, abbreviation: EM) and the following major virtual function nodes: virtualized network function (English: virtualized network function, abbreviation: VNF), network function virtualization infrastructure (English: NFV infrastructure, abbreviation: NFVI), network function virtualization management and coordination process (English: NFV Management and Orchestration, abbreviation: NFV MANO).
  • NFVI is the most basic infrastructure in the NFV architecture, including Virtualised Resources, Virtualisation Layer, and Hardware Resources.
  • the three functional blocks, the physical resources include three hardware resources of computing, storage and network, the virtual layer is between the physical resource and the virtual resource, and the hardware resource is virtualized into a virtual resource that can be dynamically requested to be provided to the VNF;
  • NFV MANO plays an important role in overall control and coordination in the NFV architecture, including: virtual network function scheduling (English: NFV Orchestrator, abbreviation: NFVO), virtual network function management (English: VNF Manager, acronym: VNFM) and virtual NFV MANO will coordinate, verify and authorize related resource requests, and manage the life cycle of VNF.
  • NFV MANO It is also responsible for the policy management of network services, the collection and transfer of related events, and the allocation of infrastructure-related resources, such as adding resources to virtual machines, improving energy efficiency, and returning resources; OSS represents the respective operations of operators.
  • Supporting equipment responsible for network management services such as alarms, traffic statistics, configuration management, network planning, etc. of different domains of the operator (such as fixed network domain or mobile network domain), while providing various convenient services for users, according to users' own
  • the operational business model and the charging principle are used to coordinate the allocation of public resources.
  • OSS can carry the service requirements of different domains of the operator, the OSS needs to configure policies according to different algorithms for different domains. As a result, the functions of the OSS become complicated and huge, which increases the burden of the OSS.
  • the embodiments of the present invention provide a network management system, device, and method, which solve the problem that the functions of the OSS are complicated and burdensome in the existing NFV architecture.
  • an embodiment of the present invention provides a network management system, including: an operation support device OSS, a domain function entity, and at least one virtual function node;
  • the OSS is configured to receive a service request of a user, and send the service request to the domain function entity;
  • the domain function entity is configured to receive a service request sent by the OSS;
  • the first virtual network function node is configured to perform related processing according to the analysis result sent by the domain function entity, and send the processing result to the domain function entity;
  • the domain function entity is further configured to receive a processing result sent by the first virtual network function node, and feed back the processing result to the OSS.
  • the network management system includes: at least one domain functional entity;
  • the at least one domain functional entity includes: a mobile domain functional entity and a fixed network Domain functional entity;
  • the mobile domain functional entity is configured to process a service request of the mobile network
  • the fixed domain functional entity is configured to process a service request of a fixed network.
  • the OSS is specifically configured to:
  • the network type includes: a mobile network and a fixed network.
  • the at least one virtual function node includes: at least one or more of a virtualized network function VNF, a network function virtualization infrastructure NFVI, and a network function virtualization management and coordination process NFV MANO;
  • the network management system further includes: a network element management EM, the EM is used to manage at least one VNF;
  • the OSS is coupled to the domain functional entity, the domain functional entity being coupled to the EM and the NFV MANO.
  • an embodiment of the present invention provides a domain functional entity, including:
  • a receiving unit configured to receive a service request sent by the OSS
  • An analyzing unit configured to obtain an analysis result according to a service request received by the receiving unit and an analysis algorithm corresponding to the service request;
  • a sending unit configured to send the analysis result to the first virtual network function node corresponding to the service request in a device that includes at least one virtual function node, where the first virtual function node is configured according to the analysis result Process
  • the receiving unit is further configured to receive a processing result sent by the first virtual function node
  • the sending unit is further configured to send the processing result to the OSS.
  • the domain functional entity is a mobile domain functional entity or a fixed domain functional entity
  • the mobile domain functional entity is configured to process a service request of the mobile network
  • the fixed domain functional entity is configured to process a service request of a fixed network.
  • an operation support device OSS including:
  • a receiving unit configured to receive a service request of the user
  • a sending unit configured to send the service request to the domain function entity, where the domain function entity analyzes and processes the service request;
  • the receiving unit is further configured to receive a processing result sent by the domain function entity.
  • the OSS further includes:
  • a determining unit configured to determine, according to the service request, a network type corresponding to the service request
  • the sending unit is specifically configured to send the service request to a domain function entity corresponding to the network type.
  • the embodiment of the present invention provides a network management method, which is applied to a domain functional entity, and includes:
  • the domain functional entity is a mobile domain functional entity or a fixed domain functional entity
  • the mobile domain functional entity is configured to process a service request of the mobile network
  • the fixed domain functional entity is configured to process a service request of a fixed network.
  • an embodiment of the present invention provides a network management method, which is applied to a camp.
  • Transport support device OSS including:
  • the method further includes:
  • the sending the service request to the domain functional entity includes:
  • an embodiment of the present invention provides a domain functional entity, including:
  • a communication interface configured to receive a service request sent by the OSS
  • a processor configured to obtain an analysis result according to a service request received by the communication interface, and an analysis algorithm corresponding to the service request;
  • the communication interface is further configured to send the analysis result to the first virtual network function node corresponding to the service request in a device that includes at least one virtual function node, where the first virtual function node is configured according to the The analysis results are processed;
  • the communication interface is further configured to receive a processing result sent by the first virtual function node, and send the processing result to the OSS.
  • the domain functional entity is a mobile domain functional entity or a fixed domain functional entity
  • the mobile domain functional entity is configured to process a service request of the mobile network
  • the fixed domain functional entity is configured to process a service request of a fixed network.
  • an operation support device OSS including:
  • a communication interface configured to receive a service request of the user
  • the communication interface is further configured to send the service request to a domain function entity, where the domain function entity analyzes and processes the service request;
  • the communication interface is further configured to receive a processing result sent by the domain function entity.
  • the OSS in combination with the seventh aspect, also includes:
  • a processor configured to determine, according to the service request, a network type corresponding to the service request
  • the communication interface is specifically configured to send the service request to a domain function entity corresponding to the network type.
  • an embodiment of the present invention provides a network management system, a device, and a method, where an OSS receives a service request of a user, and sends the service request to a domain function entity, where the domain function entity analyzes and processes the service request, and The processing result of the domain function entity feedback is fed back to the user.
  • OSS no longer analyzes and processes business requests, greatly reducing the burden on the OSS.
  • FIG. 1 is a schematic diagram of an existing NFV architecture
  • FIG. 2 is a structural diagram of a domain function entity 201 according to an embodiment of the present invention.
  • FIG. 3 is a structural diagram of an OSS 202 according to an embodiment of the present invention.
  • 3A is a structural diagram of an OSS 202 according to an embodiment of the present invention.
  • FIG. 4 is a structural diagram of a network management system 20 according to an embodiment of the present invention.
  • FIG. 4A is a structural diagram of a network management system 20 according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a network management method according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a network management method according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a network management method according to an embodiment of the present invention.
  • FIG. 7A is a flowchart of a network management method according to an embodiment of the present invention.
  • FIG. 7B is a flowchart of still another network management method according to an embodiment of the present invention.
  • FIG. 7C is a flowchart of another network management method according to an embodiment of the present invention.
  • FIG. 8 is a structural diagram of a domain function entity 401 according to an embodiment of the present invention.
  • FIG. 9 is a structural diagram of an OSS 402 according to an embodiment of the present invention.
  • FIG. 10 is a structural diagram of a network management system 40 according to an embodiment of the present invention.
  • FIG. 2 is a structural diagram of a domain function entity 201, which may be connected to a virtual function node through an interface managed by an operator, and is responsible for a network of a corresponding type of each domain functional entity.
  • Network management functions such as alarm, traffic statistics, configuration management, and network planning;
  • the domain functional entity 201 may include:
  • the receiving unit 2011 is configured to receive a service request sent by the OSS.
  • the analyzing unit 2012 is configured to obtain an analysis result according to the service request and an analysis algorithm corresponding to the service request;
  • the sending unit 2013 is configured to send the analysis result to the first virtual network function node corresponding to the service request in a device that includes at least one virtual function node.
  • the first virtual network function node corresponding to the service request may be: a virtual network function node that can satisfy the service request of the user after performing related processing according to the analysis result;
  • the receiving unit 2011 is further configured to receive a processing result that is returned by the first virtual function node after being processed according to the analysis result.
  • the processing result includes: some performance parameters (such as initial buffer delay, number of interruptions, and interrupt delay) in the analysis result.
  • some performance parameters such as initial buffer delay, number of interruptions, and interrupt delay
  • the service request is a request to add a virtual network element node
  • the processing result is: the corresponding virtual resource combination has been performed according to the analysis result.
  • the sending unit is further configured to send the processing result to the OSS.
  • the domain function entity is processed by using different analysis algorithms for different service requests, where the analysis algorithm may receive the service request from the OSS in the existing NFV architecture, and the service request is requested for the service request.
  • the adopted algorithm can also be an innovative algorithm for the later development of communication technology;
  • the analysis algorithm corresponding to the service request may be: able to accurately obtain parameters that reflect the performance of the video (such as initial buffer delay, number of interruptions, and interruption delay). And, after collecting the video performance data, the algorithm capable of performing pre-analysis, for example, using the mean opinion score (MOS) algorithm to calculate the score of the customer experience to represent the customer experience, and feedback to the OSS;
  • MOS mean opinion score
  • the analysis algorithm corresponding to the service request is: a combination of how many virtual resources (such as computing resources, storage resources, and network resources) can be quantitatively calculated.
  • the domain function entity specifically processes the service request of a domain; it may be a mobile domain functional entity, a fixed domain functional entity, or a domain functional entity of another domain added with the development of the communication technology;
  • the mobile domain functional entity is configured to process a service request of the mobile network
  • the fixed domain functional entity is configured to process a service request of a fixed network.
  • an embodiment of the present invention provides a domain function entity, which receives a service request sent by an OSS, and obtains an analysis result according to a service request and an analysis algorithm corresponding to the service request, to a device that includes at least one virtual function node.
  • the first virtual network function node corresponding to the service request sends the analysis result, and receives a processing result that the device performs feedback after processing according to the analysis result,
  • the OSS sends the processing result.
  • the domain function entity replaces the OSS to obtain the execution function of the analysis result according to the service request and the analysis algorithm corresponding to the service request, thereby greatly reducing the burden of the OSS.
  • FIG. 3 is a structural diagram of an OSS 202 according to an embodiment of the present invention.
  • the OSS 202 is different from a traditional network management node, and is no longer responsible for network management functions such as alarm, traffic statistics, configuration management, and network planning. Rather, it is connected to the domain function entity through an interface managed by the operator, and the received service request is sent to the corresponding domain function entity, and the domain function entity performs related processing functions according to the service request;
  • the OSS 202 can include:
  • the receiving unit 2021 is configured to receive a service request of the user.
  • the service request may be sent by the user through the user interaction interface of the OSS 202, or may be sent by the user through the user's handheld terminal.
  • the sending unit 2022 is configured to send the service request to the domain function entity, where the domain function entity analyzes and processes the service request.
  • the receiving unit 2021 is further configured to receive a processing result fed back by the domain function entity.
  • the OSS 202 may further feed the processing result to the user through a user interaction interface
  • the processing result is sent to the user's handheld terminal, and the user selects to view.
  • the problem of burden of the domain functional entity is further required.
  • the service request is sent to the special domain function entity.
  • the OSS 202 may further include:
  • a determining unit 2023 configured to determine, according to the service request, a network type corresponding to the service request
  • the receiving unit 2021 is specifically configured to perform domain work corresponding to the network type.
  • the entity can send the service request.
  • the network type may include: a fixed network, a mobile network, and other networks newly added with the development of communication technologies;
  • the network type corresponding to the service request may be: a network type of a network where the user who sends the service request is located; for example, if the user in the mobile network sends the service request, the network type corresponding to the service request is a mobile network.
  • the domain function entity corresponding to the network type is: a domain function entity dedicated to performing related processing according to a service request sent from the network type, and may be a mobile domain functional entity or a fixed domain functional entity;
  • the mobile domain function entity user processes a service request of the mobile network;
  • the fixed domain function entity is configured to process a service request of the fixed network;
  • a service request is from a mobile network
  • the network type is a mobile network
  • the domain function entity 1 only processes the mobile network service
  • the domain function entity 2 only processes the fixed network service
  • the domain functional entity corresponding to the service request is a domain functional entity. 1, but not domain functional entity 2.
  • an embodiment of the present invention provides an OSS, which receives a service request of a user, and sends the service request to a domain function entity, where the domain function entity analyzes and processes the service request, and processes the domain function entity feedback. The results are fed back to the user.
  • OSS no longer analyzes and processes business requests, greatly reducing the burden on the OSS.
  • FIG. 4 is a structural diagram of a network management system 20 according to an embodiment of the present invention.
  • the network management system 20 may include: an OSS 202, at least one domain function entity 201, and at least one virtual function node. ;
  • the OSS 202 has the same function as the OSS 202 described in the first embodiment. Unlike the traditional network management node, the OSS 202 is no longer responsible for network management functions such as alarm, traffic statistics, configuration management, and network planning of the network.
  • the service request sent by the internal management of the operator is sent to the corresponding domain function entity, and the domain function entity performs the relevant processing function according to the service request;
  • the domain functional entity 201 has the same domain function entity 201 as described in the second embodiment.
  • the function can be connected to the virtual function node through the internal management interface of the operator, and is responsible for network management functions such as alarm, traffic statistics, configuration management, and network planning of the network corresponding to each domain functional entity;
  • the virtual function node may be located on any shared device that the operator provides to provide network services, such as a shared server, a storage device, or a switch, for virtualizing and deploying to a data center, a network node, or an end user using standard virtualization technologies.
  • Routers, firewalls, load balancers, switches, servers, and other information infrastructure devices that have the same function do not directly interact with the OSS, but are connected to the domain function entity 201 through an interface managed by the operator. Users provide a variety of services.
  • the OSS 202 is configured to receive a service request of a user, and send the service request to the domain function entity 201.
  • the service request may be sent by the user through a user interaction interface of the OSS 202.
  • It can also be sent by the user to the OSS 202 through the user's handheld terminal.
  • the domain function entity 201 is configured to receive a service request sent by the OSS 202, obtain an analysis result according to the service request and an analysis algorithm corresponding to the service request, and send the information corresponding to the service request.
  • a virtual network function node sends the analysis result.
  • the service request can be divided into: mobile network service request, fixed network service request and other network service requests according to the source.
  • the domain function entity is processed by using different analysis algorithms for different service requests, where the analysis algorithm may receive the service request from the OSS in the existing NFV architecture, and the service request is requested for the service request.
  • the adopted algorithm can also be an innovative algorithm for the later development of communication technology;
  • the analysis algorithm corresponding to the service request may be: able to accurately obtain parameters that reflect the performance of the video (such as initial buffer delay, number of interruptions, and interruption delay). ), and the algorithm that can perform the preset analysis after collecting the video performance data, for example, using the average opinion score
  • the mean opinion score (MOS) algorithm calculates the customer experience score to represent the customer experience and feeds back to the OSS; if the service request is a request to add a virtual network element node, the analysis algorithm corresponding to the service request is An algorithm that can quantitatively calculate how many virtual resources (such as computing resources, storage resources, and network resources) can implement the physical functions of the network element.
  • the first virtual network function node corresponding to the service request may be: a virtual network function node that can satisfy the service request of the user after performing related processing according to the analysis result;
  • the first virtual network function node is configured to perform related processing according to the analysis result sent by the domain function entity 201, and send the processing result to the domain function entity 201.
  • the related processing for different analysis results may be related to the prior art, for example, finding corresponding nodes to collect related information, etc., and details are not described herein;
  • the processing result includes: data of some performance parameters (such as initial buffer delay, number of interruptions, and interruption delay) in the analysis result; if the service request is to add a virtual network element node The request is processed as follows: The corresponding virtual resource combination has been performed according to the analysis result.
  • data of some performance parameters such as initial buffer delay, number of interruptions, and interruption delay
  • the domain function entity 201 is further configured to receive a processing result sent by the first virtual network function node, and feed back the processing result to the OSS 202.
  • OSS 202 can also be used to:
  • the processing result is fed back to the user through the user interaction interface, or the processing result is sent to the user's handheld terminal, and the user selects to view.
  • the network management system 20 can include at least one domain functional entity, one domain functional entity processing only one domain's service request.
  • the OSS 202 is specifically configured to:
  • the network type may include: a fixed network, a mobile network, and other networks newly added with the development of the communication technology; the network type corresponding to the service request may be: a network of a network where the user who sends the service request is located. Type; for example, if the user in the mobile network sends the service request, the network type corresponding to the service request is a mobile network.
  • the domain function entity corresponding to the network type is: a domain function entity dedicated to performing related processing according to a service request sent from the network type, and may be a mobile domain functional entity or a fixed domain functional entity;
  • the mobile domain function entity is configured to process a service request of the mobile network;
  • the fixed domain function entity is configured to process a service request of the fixed network;
  • a service request is from a mobile network
  • the network type is a mobile network
  • the domain function entity 1 only processes the mobile network service
  • the domain function entity 2 only processes the fixed network service
  • the domain functional entity corresponding to the service request is a domain functional entity. 1, but not domain functional entity 2.
  • the virtual function node in the network management system may include: at least one virtualized network function (English: virtualized network function, abbreviation: VNF), network function virtualization infrastructure (English: NFV infrastructure, abbreviation) : NFVI), network function virtualization management and coordination process (English: NFV Management and Orchestration, abbreviation: NFV MANO) and some new virtual function nodes added with the development of communication technology in the later stage;
  • VNF virtualized network function
  • NFV infrastructure NFV infrastructure
  • NFVI network function virtualization management and coordination process
  • NFV MANO can include: virtual network function scheduling (English: NFV Orchestrator, abbreviation: NFVO), virtual network function management (English: VNF Manager, abbreviation: VNFM) and virtual infrastructure management (English: Virtualised Infrastructure Manager, abbreviation :VIM) three parts; at the same time, in order to realize the interaction between the domain functional entity and the VNF, the network management system also needs to include a network element management between the domain functional entity and the VNF (English: element manager, abbreviation: EM Each EM manages and is responsible for one or more VNFs; or may not include EMs, so that the domain functional entities are directly connected to the VNF; Therefore, this article only uses the EM between the domain functional entity and the VNF as an example.
  • the network management system 20 may have the following structure:
  • the OSS 202 is connected to the domain functional entity 201, the domain functional entity is connected to the EM2031 and the NFV MANO 2034, the EM2031 is connected to the VNF 2032, the VNF 2032 is connected to the NFVI 2033, and the NFV MANO 2034 is connected to the EM 2031, VNF 2032 and NFVI 2033, respectively;
  • EM2031, VNF2034, NFVI2033, and NFV MANO2034 have the same functions as EM, VNF, NFVI, and NFV MANO in the NFV architecture shown in FIG. 1, and will not be described herein.
  • the following service requests are: video performance data request, network service (English: network service, abbreviation: NS) instantiation request, network planning request, specific functions of OSS, domain functional entity, EM, VNF, NFVI, NFV MANO Introduce:
  • the network service request is a video performance data request.
  • the OSS 202 is configured to receive a video performance data request sent by the user, and send the video performance data request to the mobile domain function entity.
  • the video performance data request is from a mobile network, and is used to request to acquire video experience analysis data of the mobile network.
  • the mobile domain function entity 201 is configured to perform analysis according to an analysis algorithm to obtain a parameter that can reflect video performance.
  • the parameter can accurately reflect the video experience of the user, including: at least one of initial buffer delay, number of interruptions, and interruption delay.
  • the mobile domain function entity 201 is further configured to receive service data corresponding to the parameter sent by the EM, process the received service data, and send the data to the OSS 202, and the OSS 202 feeds back to the user.
  • the mobile domain function entity 201 may be configured to: send the video performance data request to the EM, and include an analysis result of the parameter, and receive the EM according to the The parameter is obtained from service data acquired with the EM managed VNF;
  • the service data corresponding to the parameter that the EM actively reported by the EM has received is received.
  • the data acquisition process between the EM and the VNF is an existing process, which is not described in detail in the present invention.
  • the processing of the received service data may include: collecting service data to form data directly reflecting the user's video experience. Or a dynamic picture;
  • the service data includes a large amount of interrupt delay.
  • the data conversion delay time is larger, smaller, and the like directly reflects the data of the user video experience.
  • the network service request is an NS instantiation request.
  • the OSS 202 is configured to receive an NS instantiation request sent by the user, and send the NS instantiation request to the mobile domain function entity 201.
  • the NS instantiation request is from the mobile network, and is used to request to allocate corresponding resources to the user to meet certain requirements of the user, such as reducing delay and improving user experience.
  • the mobile domain function entity 201 is configured to analyze the required resources of the NS instantiation according to the analysis algorithm, execute a corresponding configuration policy, and send the NS instantiation request and the configuration information to the NFVO in the NFV MANO.
  • the NFVO is configured to perform NS instantiation according to the configuration information, and send an NS instantiation success message to the domain function entity, where the domain function entity sends the NS instantiation success message to the OSS.
  • Network service request is a network planning request
  • the OSS 202 is configured to receive a network planning request sent by the user, and send the network planning request to the mobile domain function entity 201.
  • the network planning request may be a network planning request for the mobile network, where the request is: adding a network element node to the network management system;
  • a mobile domain function entity 201 configured to analyze a network planning request according to an analysis algorithm The required resources, execute the corresponding configuration policy, and send the network planning request and the configuration information to the NFVO in the NFV MANO.
  • the configuration policy is a related configuration of resources constituting the network element node, and the network element node formed according to the configuration has the same function as the entity node.
  • the NFVO is configured to perform network planning according to the configuration information, and send a network planning success message to the domain function entity, where the domain function entity sends the network planning success message to the OSS.
  • the domain management entity is added to the network management architecture in this embodiment, and the domain function entity analyzes and processes the service request by using the corresponding algorithm, so that the OSS no longer receives the service request.
  • Algorithm analysis greatly reduces the burden on the OSS.
  • FIG. 5 is a flowchart of a network management method according to an embodiment of the present disclosure.
  • the method may be applied to the domain function entity according to the first embodiment.
  • the method may include:
  • the first virtual network function node corresponding to the service request may be: a virtual network function node that can satisfy the service request of the user after performing related processing according to the analysis result;
  • the domain function entity is processed by using different analysis algorithms for different service requests, where the analysis algorithm may receive the service request from the OSS in the existing NFV architecture, and the service request is requested for the service request.
  • the adopted algorithm can also be an innovative algorithm for the later development of communication technology;
  • the analysis algorithm corresponding to the service request may be: able to accurately obtain parameters that reflect the performance of the video (such as initial buffer delay, number of interruptions, and interruption delay). ) and collecting An algorithm capable of performing pre-analysis after the video performance data, for example, using a mean opinion score (MOS) algorithm to calculate a customer experience score to represent the customer experience and feedback to the OSS; if the service request is a new one
  • MOS mean opinion score
  • the analysis algorithm corresponding to the service request is: an algorithm that can quantitatively calculate how many virtual resources (such as computing resources, storage resources, and network resources) can implement the physical functions of the network element.
  • the processing result includes: data of some performance parameters (such as initial buffer delay, number of interruptions, and interruption delay) in the analysis result; if the service request is to add a virtual network element node The request is processed as follows: The corresponding virtual resource combination has been performed according to the analysis result.
  • data of some performance parameters such as initial buffer delay, number of interruptions, and interruption delay
  • the domain function entity specifically processes the service request of a domain; it may be a mobile domain functional entity, a fixed domain functional entity, or a domain functional entity of another domain added with the development of the communication technology;
  • the mobile domain functional entity is configured to process a service request of the mobile network
  • the fixed domain functional entity is configured to process a service request of a fixed network.
  • the embodiment of the present invention provides a network management method, which receives a service request sent by an OSS, and obtains an analysis result according to a service request and an analysis algorithm corresponding to the service request, to a device that includes at least one virtual function node.
  • the first virtual network function node corresponding to the service request sends the analysis result, and receives a processing result that the device performs processing back according to the analysis result, and sends the processing result to the OSS.
  • the domain function entity replaces the OSS to obtain the analysis result according to the service request and the analysis algorithm corresponding to the service request. Execution functions greatly reduce the burden on the OSS.
  • FIG. 6 is a flowchart of a network management method according to an embodiment of the present invention. The method is applied to the OSS according to the second embodiment. As shown in FIG. 6, the method may include:
  • the service request may be sent by a user through a user interaction interface of the OSS;
  • the OSS may further feed the processing result to the user through the user interaction interface, or send the processing result to the user's handheld terminal, and the user selects to view.
  • the problem of burden of the domain functional entity is further required.
  • the service request is sent to a dedicated domain function entity, and the network management method may further include:
  • the network type may include: a fixed network, a mobile network, and other networks newly added with the development of communication technologies;
  • the network type corresponding to the service request may be: a network type of a network where the user who sends the service request is located; for example, if the user in the mobile network sends the service request, the network type corresponding to the service request is a mobile network.
  • the domain function entity corresponding to the network type is: a domain function entity dedicated to performing related processing according to a service request sent from the network type, and may be a mobile domain functional entity or a fixed domain functional entity;
  • the mobile domain function entity user processes the service request of the mobile network;
  • the fixed domain function entity is used to process the fixed network Business request;
  • a service request is from a mobile network
  • the network type is a mobile network
  • the domain function entity 1 only processes the mobile network service
  • the domain function entity 2 only processes the fixed network service
  • the domain functional entity corresponding to the service request is a domain functional entity. 1, but not domain functional entity 2.
  • the embodiment of the present invention provides a network management method, which receives a service request of a user, and sends the service request to a domain function entity, where the domain function entity analyzes and processes the service request, and feedbacks the domain function entity. The processing results are fed back to the user.
  • OSS no longer analyzes and processes business requests, greatly reducing the burden on the OSS.
  • FIG. 7 is a flowchart of still another network management method according to an embodiment of the present invention, which is applied to the network management system according to Embodiment 3, including: an OSS, at least one domain function entity, and at least one virtual function node; As shown in FIG. 7, the method may include:
  • the OSS receives a service request of the user, and sends the service request to the domain function entity.
  • the service request may be sent by the user through the user interaction interface of the OSS;
  • the domain function entity obtains an analysis result according to the received service request and an analysis algorithm corresponding to the service request, and sends the analysis result to a first virtual network function node corresponding to the service request.
  • the first virtual network function node performs related processing according to the analysis result, and sends a processing result to the domain function entity.
  • the domain function entity feeds back the received processing result to the OSS.
  • the OSS feeds back the processing result to the user.
  • the OSS may feed the processing result to the user through the user interaction interface
  • the processing result is sent to the user's handheld terminal, and the user selects to view.
  • the network management system 20 may include: at least one domain functional entity, and one domain functional entity processes only one domain's service request,
  • the OSS receiving the service request of the user and sending the service request to the domain function entity may include:
  • the network type may include: a fixed network, a mobile network, and other networks newly added with the development of the communication technology; the network type corresponding to the service request may be: a network of a network where the user who sends the service request is located. Type; for example, if the user in the mobile network sends the service request, the network type corresponding to the service request is a mobile network.
  • the domain function entity corresponding to the network type is: a domain function entity dedicated to performing related processing according to a service request sent from the network type, and may be a mobile domain functional entity or a fixed domain functional entity;
  • the mobile domain function entity user processes a service request of the mobile network;
  • the fixed domain function entity is configured to process a service request of the fixed network;
  • a service request is from a mobile network
  • the network type is a mobile network
  • the domain function entity 1 only processes the mobile network service
  • the domain function entity 2 only processes the fixed network service
  • the domain functional entity corresponding to the service request is a domain functional entity. 1, but not domain functional entity 2.
  • the virtual function node in the network management system may include: at least one virtualized network function (English: virtualized network function, abbreviation: VNF), network function virtualization infrastructure (English: NFV infrastructure, abbreviation) :NFVI), Network Function Virtualization Management and Coordination Process Text: NFV Management and Orchestration, abbreviation: NFV MANO) and some new virtual function nodes with the development of communication technology
  • NFV MANO can include: virtual network function scheduling (English: NFV Orchestrator, abbreviation: NFVO) Virtual network function management (English: VNF Manager, abbreviation: VNFM) and virtual infrastructure management (English: Virtualised Infrastructure Manager, abbreviation: VIM) three parts;
  • the network management system also needs to include a network element management (English: element manager, abbreviation: EM) between the domain functional entity and the VNF, and each EM management And the NF is responsible for the one or more VNFs; or the EM is not included, and the domain function entity is directly connected to the VNF; the comparison of the embodiments of the present invention is not limited, and only the EM between the domain functional entity and the VNF is used as an example for description.
  • EM network element management
  • the OSS can be connected with the domain functional entity, and the domain functional entity can be connected with the EM and the NFV MANO, and the EM can Connected to VNF, VNF can be connected to NFVI, EM and VNFM.
  • NFV MANO can be connected to EM, VNF and NFVI respectively; among them, VNF, NFVI, NFV MANO and existing VNF in NFV architecture as shown in Figure 1. , NFVI, NFV MANO have the same function, and will not be described here;
  • the following service requests are: video performance data request, network service (English: network service, abbreviation: NS) instantiation request, network planning request, respectively, interaction between OSS, domain functional entity, VNF, NFVI, NFV MANO Specific introduction:
  • FIG. 7A is a flowchart of a network management method provided by the present invention when a network service request is a video performance data request. As shown in FIG. 7A, the method may include:
  • the OSS receives a video performance data request sent by the user.
  • the video performance data request is from a mobile network, and is used to request video experience analysis data of a user of the mobile network.
  • the OSS sends a video performance data request to the mobile domain functional entity.
  • the mobile domain functional entity analyzes according to an analysis algorithm to obtain a parameter that can reflect video performance.
  • the parameter can accurately reflect the video experience of the user, including: at least one of initial buffer delay, number of interruptions, and interruption delay.
  • the mobile domain function entity receives the service data corresponding to the parameter sent by the EM.
  • the mobile domain function entity may send the video performance data request and the analysis result including the parameter to the EM, and receive the service data acquired by the EM from the VNF managed by the EM according to the parameter.
  • the mobile domain function entity receives the service data corresponding to the parameter that the EM actively reported by the EM has collected.
  • the data acquisition process between the EM and the VNF is an existing process, and the present invention is not described in detail.
  • the 305A and the mobile domain function entity process the received service data, and then send the data to the OSS, and the OSS feeds back to the user.
  • the processing the received service data may include: collecting service data to form data or a dynamic picture that directly reflects the user's video experience; for example, the service data includes a large number of interrupt delays, and The data conversion interruption delay is larger, smaller, and the like directly reflects the data of the user's video experience.
  • FIG. 7B is a flowchart of a network management method provided by the present invention when the network service request is an NS instantiation request. As shown in FIG. 7B, the method may include:
  • the OSS receives the NS instantiation request sent by the user.
  • the NS instantiation request is from the mobile network, and is used to request to allocate corresponding resources to the user to meet certain requirements of the user, such as reducing delay and improving user experience.
  • the OSS sends an NS instantiation request to the mobile domain functional entity.
  • the mobile domain functional entity analyzes the required requirements of the NS instantiation according to the analysis algorithm. Resources, perform the corresponding configuration strategy.
  • the mobile domain function entity sends the NS instantiation request and the configuration information to the NFVO in the NFV MANO.
  • the NFVO performs NS instantiation according to the configuration information.
  • the NFVO sends an NS instantiation success message to the mobile domain function entity, and the mobile domain function entity sends the NS instantiation success message to the OSS.
  • FIG. 7C is a flowchart of a network management method provided by the present invention when a network service request is a network planning request. As shown in FIG. 7C, the method may include:
  • the OSS receives a network planning request sent by the user.
  • the network planning request may be a network planning request for the mobile network, and is used for requesting: adding a network element node to the network management system, or changing a capacity of an existing network node in the network management system.
  • the OSS sends a network planning request to the mobile domain functional entity.
  • the mobile domain functional entity analyzes the resources required by the network planning request according to the analysis algorithm, and executes a corresponding configuration policy.
  • the configuration policy is a related configuration of resources constituting the network element node, and the network element node formed according to the configuration has the same function as the entity node.
  • the mobile domain function entity sends the network planning request and the configuration information to the NFVO in the NFV MANO.
  • 305C and NFVO perform network planning according to the configuration information.
  • the NFVO sends a network planning success message to the mobile domain function entity, and the mobile domain function entity sends the network planning success message to the OSS.
  • the domain function entity analyzes and processes the service request by using the corresponding algorithm, so that the OSS no longer performs algorithm analysis on the received service request, thereby greatly reducing the burden of the OSS.
  • FIG. 8 is a domain function entity 401 according to an embodiment of the present invention.
  • the domain function entity can be connected to a virtual function node through an interface managed by an operator, and is responsible for alarms and messages of a network corresponding to each domain function entity.
  • Network management functions such as statistics, configuration management, and network planning;
  • the domain function entity 401 may include: a communication interface 4011, a processor 4012, a memory 4013, and at least one communication bus 4014 for implementing connection and mutual communication between the devices;
  • the communication interface 4011 is an interface implemented by hardware, such as a user interaction interface, for implementing input and output functions of a device where the communication interface is located, and collecting touch operations on or near the user (such as a user using a finger, a stylus, etc.)
  • a suitable object or accessory operates on the communication interface, and drives the corresponding connection device according to a preset program, and can also be used to send information input by the user or information provided to the user; and can also be an interface implemented by software, The embodiment of the invention does not limit this.
  • the processor 4012 may be a central processing unit (English: central processing unit, referred to as CPU);
  • the memory 4013 may be a volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); or non-volatile memory (English: non-volatile memory), for example only Read memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD); or a combination of the above types of memory for providing instructions and data to a processor on a device in which the memory resides.
  • volatile memory such as random access memory (English: random-access memory, abbreviation: RAM); or non-volatile memory (English: non-volatile memory), for example only Read memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD);
  • the communication interface 4011 is configured to receive a service request sent by the OSS.
  • the processor 4012 is configured to obtain an analysis result according to the service request and an analysis algorithm corresponding to the service request.
  • the communication interface 4011 is further configured to send the analysis result to the first virtual network function node corresponding to the service request in a device that includes at least one virtual function node;
  • the processing result is sent to the OSS.
  • the domain function entity is processed by using different analysis algorithms for different service requests, where the analysis algorithm may receive the service request from the OSS in the existing NFV architecture, and the service request is requested for the service request.
  • the adopted algorithm can also be an innovative algorithm for the later development of communication technology;
  • the analysis algorithm corresponding to the service request may be: able to accurately obtain parameters that reflect the performance of the video (such as initial buffer delay, number of interruptions, and interruption delay). And, after collecting the video performance data, an algorithm capable of performing pre-analysis, for example, using a mean opinion score (MOS) algorithm to calculate a customer experience score to represent the customer experience and feedback to the OSS; if the service The request is a request for adding a virtual network element node, and the analysis algorithm corresponding to the service request is: a combination of how many virtual resources (such as computing resources, storage resources, and network resources) can be quantitatively calculated to implement the network element.
  • the algorithm of the entity function.
  • the domain function entity specifically processes the service request of a domain; it may be a mobile domain functional entity, a fixed domain functional entity, or a domain functional entity of another domain added with the development of the communication technology;
  • the mobile domain functional entity is configured to process a service request of the mobile network
  • the fixed domain functional entity is configured to process a service request of a fixed network.
  • an embodiment of the present invention provides a domain function entity, which receives a service request sent by an OSS, and obtains an analysis result according to a service request and an analysis algorithm corresponding to the service request, to a device that includes at least one virtual function node.
  • the first virtual network function node corresponding to the service request sends the analysis result, and receives a processing result that the device performs processing back according to the analysis result, and sends the processing result to the OSS.
  • the domain functional entity replaces the OSS industry.
  • the request and the analysis algorithm corresponding to the service request obtain the execution function of the analysis result, which greatly reduces the burden of the OSS.
  • FIG. 9 is a structural diagram of an OSS 402 according to an embodiment of the present invention.
  • the network management function is not responsible for network management functions such as alarm, traffic statistics, configuration management, and network planning.
  • the service request sent by the internal management of the operator is sent to the corresponding domain function entity, and the domain function entity performs the relevant processing function according to the service request;
  • FIG. 9 it may include: a communication interface 4021, a processor 4022, a memory 4023, and at least one communication bus 4024 for implementing connection and mutual communication between the devices;
  • the communication interface 4021 can be an interface implemented by hardware, such as a user interaction interface, for implementing input and output functions of a device where the communication interface is located, and collecting touch operations on or near the user (such as a user using a finger, a stylus, etc.) Any suitable object or accessory operates on the communication interface) and drives the corresponding connection device according to a preset program, and can also be used to transmit information input by the user or information provided to the user; and can also be an interface implemented by software. This embodiment of the present invention does not limit this.
  • the processor 4022 may be a central processing unit (English: central processing unit, referred to as CPU);
  • the memory 4023 may be a volatile memory, such as a random access memory (English-random-access memory, abbreviated as RAM), or a non-volatile memory (for example, only non-volatile memory).
  • RAM random access memory
  • non-volatile memory for example, only non-volatile memory.
  • Read memory English read-only memory, abbreviated ⁇ ROM
  • flash memory English flash memory
  • hard disk English: hard disk drive, abbreviated HDD
  • solid state drive English solid-state drive, abbreviation ⁇ SSD
  • the communication interface 4021 is configured to receive a service request of a user
  • the service request may be sent by the user through a user interaction interface of the OSS 202.
  • the communication interface 4021 can feed the processing result to the user through a user interaction interface
  • the processing result is sent to the user's handheld terminal, and the user selects to view.
  • the problem of burden of the domain functional entity is further required.
  • Send the service request to a dedicated domain function entity as follows:
  • the processor 4022 is configured to determine, according to the service request, a network type corresponding to the service request;
  • the communication interface 4021 is specifically configured to send the service request to a domain function entity corresponding to the network type.
  • the network type may include: a fixed network, a mobile network, and other networks newly added with the development of the communication technology; the network type corresponding to the service request may be: a network of a network where the user who sends the service request is located. Type; for example, if the user in the mobile network sends the service request, the network type corresponding to the service request is a mobile network.
  • the domain function entity corresponding to the network type is: a domain function entity dedicated to performing related processing according to a service request sent from the network type, and may be a mobile domain functional entity or a fixed domain functional entity;
  • the mobile domain function entity is configured to process a service request of a mobile network;
  • the fixed domain function entity is configured to process a service request of a fixed network.
  • a service request is from a mobile network
  • the network type is a mobile network
  • the domain function entity 1 only processes the mobile network service
  • the domain function entity 2 only processes the fixed network service.
  • the domain functional entity corresponding to the service request is the domain functional entity 1, but not the domain functional entity 2.
  • an embodiment of the present invention provides an OSS, which receives a service request of a user, and sends the service request to a domain function entity, where the domain function entity analyzes and processes the service request, and processes the domain function entity feedback. The results are fed back to the user.
  • OSS no longer analyzes and processes business requests, greatly reducing the burden on the OSS.
  • FIG. 10 is a structural diagram of a network management system 40 according to an embodiment of the present invention, for performing the method described in Embodiment 6.
  • the system 40 may include: an OSS 402, a domain functional entity. 401 and including at least one virtual function node;
  • the OSS 402 has the same function as the OSS 402 described in the seventh embodiment. Unlike the traditional network management node, the OSS 402 is no longer responsible for network management functions such as alarm, traffic statistics, configuration management, and network planning.
  • the service request sent by the internal management of the operator is sent to the corresponding domain function entity, and the domain function entity performs the relevant processing function according to the service request;
  • the domain function entity 401 has the same function as the domain function entity 401 described in the eighth embodiment, and can be connected to the virtual function node through an interface managed by the operator, and is responsible for the alarm and traffic of the network corresponding to each domain function entity.
  • Network management functions such as statistics, configuration management, and network planning;
  • the virtual function node may be located on any shared device that the operator provides to provide network services, such as a shared server, a storage device, or a switch, for virtualizing and deploying to a data center, a network node, or an end user using standard virtualization technologies.
  • a router, a firewall, a load balancer, a switch, a server, and the like, which have the same functions, are not directly interacted with the OSS, but are connected to the domain function entity 401 through an interface managed by the operator. Users provide a variety of services.
  • the OSS 402 is configured to receive a service request of a user, and send the service request to the domain function entity 401.
  • the service request may be sent by the user through the user interaction interface of the OSS 402, or may be sent by the user to the OSS 402 through the user's handheld terminal.
  • the domain function entity 401 is configured to receive a service request sent by the OSS 402, obtain an analysis result according to the service request and an analysis algorithm corresponding to the service request, and send the information corresponding to the service request.
  • a virtual network function node sends the analysis result.
  • the service request can be divided into: mobile network service request, fixed network service request and other network service requests according to the source.
  • the domain function entity is processed by using different analysis algorithms for different service requests, where the analysis algorithm may receive the service request from the OSS in the existing NFV architecture, and the service request is requested for the service request.
  • the adopted algorithm can also be an innovative algorithm for the later development of communication technology;
  • the analysis algorithm corresponding to the service request may be: able to accurately obtain parameters that reflect the performance of the video (such as initial buffer delay, number of interruptions, and interruption delay). And an algorithm capable of performing preset analysis after collecting video performance data, for example, using a mean opinion score (MOS) algorithm to calculate a customer experience score to represent the customer experience and feedback to the OSS;
  • MOS mean opinion score
  • the service request is a request for adding a virtual network element node
  • the analysis algorithm corresponding to the service request is: a combination of how many virtual resources (such as computing resources, storage resources, and network resources) can be quantitatively calculated to implement the network element.
  • the algorithm of the entity function.
  • the first virtual network function node corresponding to the service request may be: a virtual network function node that can satisfy the service request of the user after performing related processing according to the analysis result;
  • the first virtual network function node is configured to perform related processing according to the analysis result sent by the domain function entity 401, and send the processing result to the domain function entity 401.
  • the related processing for different analysis results may be related to the prior art, for example, finding corresponding nodes to collect related information, etc., and details are not described herein;
  • the processing result includes: data of some performance parameters (such as initial buffer delay, number of interruptions, and interruption delay) in the analysis result; if the service request is to add a virtual network element node The request is processed as follows: The corresponding virtual resource combination has been performed according to the analysis result.
  • data of some performance parameters such as initial buffer delay, number of interruptions, and interruption delay
  • the domain function entity 401 is further configured to receive a processing result sent by the first virtual network function node, and feed back the processing result to the OSS 402.
  • OSS 402 can also be used to:
  • the processing result is fed back to the user through the user interaction interface, or the processing result is sent to the user's handheld terminal, and the user selects to view.
  • the network management system 40 can include at least one domain functional entity, one domain functional entity processing only one domain's service request.
  • the OSS 402 is specifically configured to:
  • the network type may include: a fixed network, a mobile network, and other networks newly added with the development of the communication technology; the network type corresponding to the service request may be: a network of a network where the user who sends the service request is located. Type; for example, if the user in the mobile network sends the service request, the network type corresponding to the service request is a mobile network.
  • the domain function entity corresponding to the network type is: a domain function entity dedicated to performing related processing according to a service request sent from the network type, and may be a mobile domain functional entity or a fixed domain functional entity;
  • the mobile domain function entity is configured to process a service request of a mobile network;
  • the fixed domain function entity is configured to process a service request of a fixed network.
  • a service request is from a mobile network
  • the network type is a mobile network
  • the domain function entity 1 only processes the mobile network service
  • the domain function entity 2 only processes the fixed network service.
  • the domain functional entity corresponding to the service request is the domain functional entity 1, but not the domain functional entity 2.
  • the virtual function node in the network management system may include: at least one virtualized network function (English: virtualized network function, abbreviation: VNF), network function virtualization infrastructure (English: NFV infrastructure, abbreviation) : NFVI), network function virtualization management and coordination process (English: NFV Management and Orchestration, abbreviation: NFV MANO) and some new virtual function nodes with the development of communication technology
  • NFV MANO can include: virtual Network function scheduling (English: NFV Orchestrator, abbreviation: NFVO), virtual network function management (English: VNF Manager, abbreviation: VNFM) and virtualization infrastructure management (English: Virtualised Infrastructure Manager, abbreviation: VIM) three parts;
  • the network management system also needs to include a network element management (English: element manager, abbreviation: EM) between the domain functional entity and the VNF, and each EM management and Responsible for one or more VNFs; or may not include EM, the domain functional entity is directly connected to the VNF; the comparison of the embodiments of the present invention is not limited, and only the EM between the domain functional entity and the VNF is taken as an example for description.
  • EM network element management
  • the network management system 40 may have the following structure:
  • the OSS 402 is connected to the domain functional entity 401, the domain functional entity is connected to the EM and the NFV MANO, the EM is connected to the VNF, the VNF is connected to the NFVI, and the NFV MANO is connected to the EM, VNF and NFVI respectively; wherein EM, VNF, NFVI and NFV MANO have the same functions as EM, VNF, NFVI, and NFV MANO in the NFV architecture shown in FIG. 1, and will not be described here.
  • the following service requests are: video performance data request, network service (English: network service, abbreviation: NS) instantiation request, network planning request, specific functions of OSS, domain functional entity, EM, VNF, NFVI, NFV MANO Introduce:
  • the network service request is a video performance data request.
  • the OSS 402 is configured to receive a video performance data request sent by the user, and send the video performance data request to the mobile domain function entity.
  • the video performance data request is from a mobile network, and is used to request to acquire video experience analysis data of the mobile network.
  • the mobile domain function entity 401 is configured to perform analysis according to an analysis algorithm to obtain a parameter that can reflect video performance.
  • the parameter can accurately reflect the video experience of the user, including: at least one of initial buffer delay, number of interruptions, and interruption delay.
  • the mobile domain function entity 401 is further configured to receive the service data corresponding to the parameter sent by the EM, process the received service data, and send the data to the OSS 402, and the OSS 402 feeds back to the user.
  • the mobile domain function entity 401 may be configured to: send the video performance data request to the EM, and include an analysis result of the parameter, and receive, by the EM, the service data acquired from the VNF managed by the EM according to the parameter. Or receiving the service data corresponding to the parameter that the EM actively reported by the EM has collected.
  • the data acquisition process between the EM and the VNF is an existing process, which is not described in detail in the present invention.
  • the processing of the received service data may include: collecting service data to form data directly reflecting the user's video experience. Or a dynamic picture; for example, the service data includes a large amount of interrupt delay, and at this time, the data can be converted into a data with a large delay and a small delay, which directly reflects the user's video experience.
  • the network service request is an NS instantiation request.
  • the OSS 402 is configured to receive an NS instantiation request sent by the user, and send the NS instantiation request to the mobile domain function entity 401.
  • the NS instantiation request is from the mobile network, and is used to request to allocate corresponding resources to the user to meet certain requirements of the user, such as reducing delay and improving user experience.
  • the mobile domain function entity 401 is configured to analyze the required resources of the NS instantiation according to the analysis algorithm, execute a corresponding configuration policy, and send the NFVO to the NFV MANO. Sending the NS instantiation request and the configuration information.
  • the NFVO is configured to perform NS instantiation according to the configuration information, and send an NS instantiation success message to the domain function entity, where the domain function entity sends the NS instantiation success message to the OSS.
  • Network service request is a network planning request
  • the OSS 402 is configured to receive a network planning request sent by the user, and send the network planning request to the mobile domain function entity 401.
  • the network planning request may be a network planning request for the mobile network, and is used for requesting: adding a network element node to the network management system, or changing a capacity of an existing network node in the network management system.
  • the mobile domain function entity 401 is configured to analyze resources required by the network planning request according to the analysis algorithm, execute a corresponding configuration policy, and send the network planning request and the configuration information to the NFVO in the NFV MANO.
  • the configuration policy is a related configuration of resources constituting the network element node, and the network element node formed according to the configuration has the same function as the entity node.
  • the NFVO is configured to perform network planning according to the configuration information, and send a network planning success message to the domain function entity, where the domain function entity sends the network planning success message to the OSS.
  • the domain management entity is added to the network management architecture in this embodiment, and the domain function entity analyzes and processes the service request by using the corresponding algorithm, so that the OSS no longer receives the service request.
  • Algorithm analysis greatly reduces the burden on the OSS.
  • the OSS after receiving the service request, the OSS does not analyze and process the service request according to the corresponding analysis algorithm, thereby greatly reducing the burden of the OSS.
  • the disclosed systems, devices, and methods 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 mutual 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 in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, 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 purpose of the solution of the 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.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the software functional units described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform portions of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.
  • the program can be stored in a computer readable storage medium, which can include: a read only memory, a random access memory, a magnetic disk or an optical disk, and the like.

Abstract

本发明提供一种网络管理系统、设备及方法，涉及通信技术领域，解决了现有NFV架构中OSS的功能复杂庞大，负担加重的问题。本发明提供的网络管理系统包括：营运支持设备OSS、域功能实体、以及至少一个虚拟功能节点；OSS用于接收用户的业务请求，并向域功能实体发送业务请求；域功能实体用于接收OSS发送的业务请求，根据业务请求以及与业务请求相对应的分析算法获得分析结果，并向与业务请求对应的第一虚拟网络功能节点发送分析结果；第一虚拟网络功能节点用于根据域功能实体发送的分析结果进行相关处理，并向域功能实体发送处理结果；域功能实体还用于向OSS反馈处理结果。

Description

一种网络管理系统、设备及方法 技术领域
本发明涉及通信技术领域，尤其涉及一种网络管理系统、设备及方法。
背景技术
随着网络通信技术的发展，现有网络功能虚拟化(英文：network function virtualization，缩写：NFV)标准定义的网络系统架构，如图1所示，可包括营运支持设备(英文：operations support system，缩写：OSS)、至少一个网元管理(英文：element management，缩写：EM)以及以下几大虚拟功能节点：虚拟化网络功能(英文：virtualized network function，缩写：VNF)、网络功能虚拟化基础建设(英文：NFV infrastructure，缩写：NFVI)、网络功能虚拟化管理与协调流程(英文：NFV Management and Orchestration，缩写：NFV MANO)。
其中，每个VNF各自具备相对应的EM对其进行操作和管理；NFVI为NFV架构中最基本的基础建设，主要包括虚拟资源(Virtualised Resources)、虚拟层(Virtualisation Layer)、实体资源(Hardware Resources)三个功能区块，实体资源包括计算、储存与网络三大硬件资源，虚拟层介于实体资源与虚拟资源之间，将硬件资源虚拟化为成为可动态请求使用的虚拟资源提供给VNF；NFV MANO为NFV架构中进行整体控管与协调的重要角色，主要包括：虚拟网络功能调度(英文：NFV Orchestrator，缩写：NFVO)、虚拟网络功能管理(英文：VNF Manager，缩写：VNFM)及虚拟化基础建设管理(英文：Virtualised Infrastructure Manager，缩写：VIM)三个部分，当有软件及硬件资源的需求时，NFV MANO将协调、验证与授权相关资源的请求，同时负责管理VNF的生命周期，如实例化、弹性组织、更新、查询、终止VNF等，此外，NFV MANO 也负责网络服务的策略管理(Policy Management)、关联事件的收集与转送、以及基础建设相关资源的配置，如为虚拟机添增资源、提升能源效率、资源归还等；OSS代表营运商各自的营运支持设备，负责营运商不同域(如固定网络域或移动网络域)的告警、话务统计、配置管理、网络规划等网络管理业务，在为用户提供各式便利服务的同时，根据用户自身的营运业务模式与计费原则进行公共资源的协调配置。
由于，OSS可以承载营运商不同域的业务需求，使得OSS针对不同域的业务需要根据不同的算法来配置策略，如此，导致OSS的功能变得复杂庞大，加重了OSS的负担。
发明内容
本发明的实施例提供一种网络管理系统、设备及方法，以解决现有NFV架构中，OSS的功能复杂庞大，负担加重的问题。
为达到上述目的，本发明的实施例采用如下技术方案：
第一方面，本发明实施例提供一种网络管理系统，包括：营运支持设备OSS、域功能实体、以及至少一个虚拟功能节点；
所述OSS，用于接收用户的业务请求，并向所述域功能实体发送所述业务请求；
所述域功能实体，用于接收所述OSS发送的业务请求；
根据所述业务请求以及与所述业务请求相对应的分析算法获得分析结果，并向与所述业务请求对应的第一虚拟网络功能节点发送所述分析结果；
所述第一虚拟网络功能节点，用于根据所述域功能实体发送的分析结果进行相关处理，并向所述域功能实体发送处理结果；
所述域功能实体，还用于接收所述第一虚拟网络功能节点发送的处理结果，并向所述OSS反馈所述处理结果。
在第一方面的第一种可实现方式中，结合第一方面，
所述网络管理系统包括：至少一个域功能实体；
所述至少一个域功能实体包括：移动网域功能实体和固定网 域功能实体；
所述移动域功能实体用于处理移动网络的业务请求；
所述固定域功能实体用于处理固定网络的业务请求。
在第一方面的第二种可实现方式中，结合第一方面的第一种的第一种可实现方式，
所述OSS，具体用于：
根据接收到的业务请求确定所述业务请求对应的网络类型；
向与所述网络类型对应的域功能实体发送所述业务请求；
其中，所述网络类型包括：移动网络和固定网络。
在第一方面的第三种可实现方式中，结合第一方面至第一方面的第二种可实现方式，
所述至少一个虚拟功能节点包括：至少虚拟化网络功能VNF、网络功能虚拟化基础建设NFVI和网络功能虚拟化管理与协调流程NFV MANO中的任意一个或多个；
所述网络管理系统还包括：网元管理EM，所述EM用于管理至少一个VNF；
所述OSS与所述域功能实体相连接，所述域功能实体与所述EM和所述NFV MANO相连接。
第二方面，本发明实施例提供一种域功能实体，包括：
接收单元，用于接收OSS发送的业务请求；
分析单元，用于根据所述接收单元接收到的业务请求、以及与所述业务请求相对应的分析算法获得分析结果；
发送单元，用于向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，由所述第一虚拟功能节点根据所述分析结果进行处理；
所述接收单元，还用于接收所述第一虚拟功能节点发送的处理结果；
所述发送单元，还用于向所述OSS发送所述处理结果。
在第二方面的第一种可实现方式中，结合第二方面，
所述域功能实体为移动域功能实体或者固定域功能实体；
所述移动域功能实体用于处理移动网络的业务请求；
所述固定域功能实体用于处理固定网络的业务请求。
第三方面，本发明实施例提供一种营运支持设备OSS，包括：
接收单元，用于接收用户的业务请求；
发送单元，用于向域功能实体发送所述业务请求，由所述域功能实体对所述业务请求进行分析处理；
所述接收单元，还用于接收所述域功能实体发送的处理结果。
在第三方面的第一种可实现方式中，结合第三方面，所述OSS还包括：
确定单元，用于根据所述业务请求确定所述业务请求对应的网络类型；
所述发送单元，具体用于向与所述网络类型对应的域功能实体发送所述业务请求。
第四方面，本发明实施例提供一种网络管理方法，应用于域功能实体，包括：
接收OSS发送的业务请求；
根据所述业务请求、以及与所述业务请求相对应的分析算法获得分析结果；
向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，由所述第一虚拟功能节点根据所述分析结果进行处理；
接收所述第一虚拟功能节点发送的处理结果，所述域功能实体，还用于向所述OSS发送所述处理结果。
在第四方面的第一种可实现方式中，结合第四方面，
所述域功能实体为移动域功能实体或者固定域功能实体；
所述移动域功能实体用于处理移动网络的业务请求；
所述固定域功能实体用于处理固定网络的业务请求。
第五方面，本发明实施例提供一种网络管理方法，应用于营 运支持设备OSS，包括：
接收用户的业务请求；
向域功能实体发送所述业务请求，由所述域功能实体对所述业务请求进行分析处理；
接收所述域功能实体发送的处理结果。
在第五方面的第一种可实现方式中，结合第五方面，
在接收用户的业务请求之后，所述方法还包括：
根据所述业务请求确定所述业务请求对应的网络类型；
所述向域功能实体发送所述业务请求包括：
向与所述网络类型对应的域功能实体发送所述业务请求。
第六方面，本发明实施例提供一种域功能实体，包括：
通信接口，用于接收OSS发送的业务请求；
处理器，用于根据所述通信接口接收到的业务请求、以及与所述业务请求相对应的分析算法获得分析结果；
所述通信接口，还用于向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，由所述第一虚拟功能节点根据所述分析结果进行处理；
所述通信接口，还用于接收所述第一虚拟功能节点发送的处理结果，并向所述OSS发送所述处理结果。
在第六方面的第一种可实现方式中，结合第六方面，
所述域功能实体为移动域功能实体或者固定域功能实体；
所述移动域功能实体用于处理移动网络的业务请求；
所述固定域功能实体用于处理固定网络的业务请求。
第七方面，本发明实施例提供一种营运支持设备OSS，包括：
通信接口，用于接收用户的业务请求；
所述通信接口，还用于向域功能实体发送所述业务请求，由所述域功能实体对所述业务请求进行分析处理；
所述通信接口，还用于接收所述域功能实体发送的处理结果。
在第七方面的第一种可实现方式中，结合第七方面，所述OSS 还包括：
处理器，用于根据所述业务请求确定所述业务请求对应的网络类型；
所述通信接口，具体用于向与所述网络类型对应的域功能实体发送所述业务请求。
由上可知，本发明实施例提供一种网络管理系统、设备及方法，OSS接收用户的业务请求，并将所述业务请求发送至域功能实体，由域功能实体对业务请求进行分析处理，并将域功能实体反馈的处理结果反馈给用户。如此，OSS不再对业务请求进行分析处理，大大降低了OSS负担。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为现有NFV架构的示意图；
图2为本发明实施例提供的一种域功能实体201的结构图；
图3为本发明实施例提供的一种OSS202的结构图；
图3A为本发明实施例提供的一种OSS202的结构图；
图4为本发明实施例提供的一种网络管理系统20的结构图；
图4A为本发明实施例提供的一种网络管理系统20的结构图；
图5为本发明实施例提供的一种网络管理方法的流程图；
图6为本发明实施例提供的一种网络管理方法的流程图；
图7为本发明实施例提供的一种网络管理方法的流程图；
图7A为本发明实施例提供的一种网络管理方法的流程图；
图7B为本发明实施例提供的又一种网络管理方法的流程图；
图7C为本发明实施例提供的另一种网络管理方法的流程图；
图8为本发明实施例提供的一种域功能实体401的结构图；
图9为本发明实施例提供的一种OSS402的结构图；
图10为本发明实施例提供的一种网络管理系统40的结构图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
实施例一
图2为本发明实施例提供的一种域功能实体201的结构图，该域功能实体可以与虚拟功能节点之间通过运营商内部管理的接口连接，负责每个域功能实体对应类型的网络的告警、话务统计、配置管理、网络规划等网络管理功能；
如图2所示，所述域功能实体201可以包括：
接收单元2011，用于接收OSS发送的业务请求。
分析单元2012，用于根据所述业务请求以及与所述业务请求相对应的分析算法获得分析结果；
发送单元2013，用于向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果。
其中，所述与所述业务请求对应的第一虚拟网络功能节点可以为：根据分析结果执行相关处理后，处理结果能够满足用户的业务请求的虚拟网络功能节点；
所述接收单元2011，还用于接收所述第一虚拟功能节点根据所述分析结果进行处理后返回的处理结果。
例如，若用户请求视频性能数据，则处理结果包含：分析结果中的一些性能参数(如初始缓冲时延、中断次数、中断时延)的 数据；若该业务请求为新增一个虚拟网元节点的请求，则处理结果为：已根据分析结果进行相应的虚拟资源组合。
所述发送单元，还用于向OSS发送所述处理结果。
需要说明的是，本发明实施例中，针对不同的业务请求，域功能实体采用不同的分析算法进行处理，其中，该分析算法可以为现有NFV架构中OSS接收到业务请求，针对该业务请求采用的算法，也可以为后期随着通信技术的发展，革新的算法；
例如，若该业务请求为视频性能数据请求，则与该业务请求对应的分析算法可以为：能够准确地获得反映该视频性能的参数为哪些参数(如初始缓冲时延、中断次数、中断时延)，并且在收集到视频性能数据后能够进行预分析的算法，例如采用平均意见分(mean opinion score，MOS)算法计算出客户体验的分值来表征客户体验，并反馈给OSS；
若该业务请求为新增一个虚拟网元节点的请求，则与该业务请求对应的分析算法为：能够定量的计算出多少虚拟资源(如计算资源、存储资源和网络资源)的组合可以实现该网元的实体功能的算法。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，所述域功能实体专门处理一个域的业务请求；可以为移动域功能实体，也可以为固定域功能实体，还可以为随着通信技术发展新增的其他域的域功能实体；
所述移动域功能实体用于处理移动网络的业务请求；
所述固定域功能实体用于处理固定网络的业务请求。
由上可知，本发明实施例提供一种域功能实体，接收OSS发送的业务请求，根据业务请求以及与所述业务请求相对应的分析算法获得分析结果，向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，并接收所述设备根据所述分析结果进行处理后反馈回的处理结果，向 OSS发送所述处理结果。如此，由域功能实体代替了OSS根据业务请求以及与所述业务请求相对应的分析算法获得分析结果的执行功能，大大降低了OSS的负担。
实施例二
图3为本发明实施例提供的一种OSS202的结构图，其中，所述OSS202与传统的网络管理节点不同，不再负责网络的告警、话务统计、配置管理、网络规划等网络管理功能，而是与域功能实体之间通过运营商内部管理的接口连接，将接收到的业务请求发送至相应的域功能实体，由域功能实体根据业务请求执行相关的处理功能；
如图3所示，所述OSS202可以包括：
接收单元2021，用于接收用户的业务请求。
其中，所述业务请求可以由用户通过所述OSS202的用户交互界面发送，还可以由用户通过用户的手持终端发送。
发送单元2022，用于向域功能实体发送所述业务请求，由所述域功能实体对所述业务请求进行分析处理。
所述接收单元2021，还用于接收所述域功能实体反馈的处理结果。
可选的，所述OSS202还可以将所述处理结果通过用户交互界面反馈给用户；
或者，将处理结果发送至用户的手持终端，由用户选择查看。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，还需要将业务请求发送至专门的域功能实体上，具体的，如图3A所示，所述OSS202还可以包括：
确定单元2023，用于根据所述业务请求确定所述业务请求对应的网络类型；
所述接收单元2021，具体用于向与所述网络类型对应的域功 能实体发送所述业务请求。
其中，所述网络类型可以包括：固定网络、移动网络、以及后期随着通信技术发展新增的其他网络；
所述与业务请求对应的网络类型可以为：发出业务请求的用户所在的网络的网络类型；例如，处于移动网的用户发送该业务请求，则与所述业务请求对应的网络类型为移动网络。
所述与所述网络类型对应的域功能实体为：专门用于根据从该网络类型发出的业务请求执行相关处理的域功能实体，可以为移动域功能实体，也可以为固定域功能实体；所述移动域功能实体用户处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求；
例如，某一业务请求来自移动网络，网络类型为移动网络，域功能实体1仅处理移动网业务，域功能实体2仅处理固定网业务，则与该业务请求对应的域功能实体为域功能实体1，而不能是域功能实体2。
由上可知，本发明实施例提供一种OSS，接收用户的业务请求，并将所述业务请求发送至域功能实体，由域功能实体对业务请求进行分析处理，并将域功能实体反馈的处理结果反馈给用户。如此，OSS不再对业务请求进行分析处理，大大降低了OSS负担。
实施例三
图4示出了本发明实施例提供的一种网络管理系统20的结构图，如图4所示，该网络管理系统20可以包括：OSS202、至少一个域功能实体201、以及至少一个虚拟功能节点；
其中，OSS202与实施一所述的OSS202具有相同功能，与传统的网络管理节点不同，不再负责网络的告警、话务统计、配置管理、网络规划等网络管理功能，而是与域功能实体之间通过运营商内部管理的接口连接，将接收到的业务请求发送至相应的域功能实体，由域功能实体根据业务请求执行相关的处理功能；
域功能实体201与实施例二所述的域功能实体201具有相同 功能，可以与虚拟功能节点之间通过运营商内部管理的接口连接，负责每个域功能实体对应类型的网络的告警、话务统计、配置管理、网络规划等网络管理功能；
所述虚拟功能节点可以位于营运商用以提供网络服务的任一共享设备，如共享服务器、存储设备或者交换机上，为利用标准虚拟化技术虚拟出的与部署于数据中心、网络节点或终端用户处的路由器、防火墙、负载均衡器、交换机、服务器等各式信息基础设备具有相同功能的节点，不再与OSS直接进行交互，而是与域功能实体201通过运营商内部管理的接口进行连接，为用户提供各式服务。
所述OSS202，用于接收用户的业务请求，并向域功能实体201发送所述业务请求。
其中，所述业务请求可以由用户通过所述OSS202的用户交互界面发送；
也可以由用户通过用户的手持终端发送给OSS202。
所述域功能实体201，用于接收所述OSS202发送的业务请求，根据所述业务请求以及与所述业务请求相对应的分析算法获得分析结果，并向与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果。
其中，业务请求可以根据来源分为：移动网业务请求、固定网业务请求及其他网络业务请求。
需要说明的是，本发明实施例中，针对不同的业务请求，域功能实体采用不同的分析算法进行处理，其中，该分析算法可以为现有NFV架构中OSS接收到业务请求，针对该业务请求采用的算法，也可以为后期随着通信技术的发展，革新的算法；
例如，若该业务请求为视频性能数据请求，则与该业务请求对应的分析算法可以为：能够准确地获得反映该视频性能的参数为哪些参数(如初始缓冲时延、中断次数、中断时延)，并且在收集到视频性能数据后能够进行预设分析的算法，例如采用平均意见分 (mean opinion score，MOS)算法计算出客户体验的分值来表征客户体验，并反馈给OSS；若该业务请求为新增一个虚拟网元节点的请求，则与该业务请求对应的分析算法为：能够定量的计算出多少虚拟资源(如计算资源、存储资源和网络资源)的组合可以实现该网元的实体功能的算法。
所述与所述业务请求对应的第一虚拟网络功能节点可以为：根据分析结果执行相关处理后，处理结果能够满足用户的业务请求的虚拟网络功能节点；
所述第一虚拟网络功能节点，用于根据所述域功能实体201发送的分析结果进行相关处理，并向域功能实体201发送处理结果。
其中，所述针对不同的分析结果的相关处理可以为现有技术，例如找到对应节点搜集相关信息等等，在此不再详细介绍；
例如，若用户请求视频性能数据，则处理结果包含：分析结果中的一些性能参数(如初始缓冲时延、中断次数、中断时延)的数据；若该业务请求为新增一个虚拟网元节点的请求，则处理结果为：已根据分析结果进行相应的虚拟资源组合。
所述域功能实体201，还用于接收所述第一虚拟网络功能节点发送的处理结果，向OSS202反馈所述处理结果。
进一步的，所述OSS202，还可以用于：
将所述处理结果通过用户交互界面反馈给用户，或者将处理结果发送至用户的手持终端，由用户选择查看。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，所述网络管理系统20可以包括：至少一个域功能实体，一个域功能实体仅处理一个域的业务请求。
相应的，所述OSS202，具体用于：
根据所述业务请求确定所述业务请求对应的网络类型；
向与所述网络类型对应的域功能实体发送所述业务请求。
其中，所述网络类型可以包括：固定网络、移动网络、以及后期随着通信技术发展新增的其他网络；所述与业务请求对应的网络类型可以为：发出业务请求的用户所在的网络的网络类型；例如，处于移动网的用户发送该业务请求，则与所述业务请求对应的网络类型为移动网络。
所述与所述网络类型对应的域功能实体为：专门用于根据从该网络类型发出的业务请求执行相关处理的域功能实体，可以为移动域功能实体，也可以为固定域功能实体；所述移动域功能实体用于处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求；
例如，某一业务请求来自移动网络，网络类型为移动网络，域功能实体1仅处理移动网业务，域功能实体2仅处理固定网业务，则与该业务请求对应的域功能实体为域功能实体1，而不能是域功能实体2。
可选的，本发明提供的网络管理系统中的虚拟功能节点可以包括：至少一个虚拟化网络功能(英文：virtualized network function，缩写：VNF)、网络功能虚拟化基础建设(英文：NFV infrastructure，缩写：NFVI)、网络功能虚拟化管理与协调流程(英文：NFV Management and Orchestration，缩写：NFV MANO)以及后期随着通信技术的发展，新增加的一些虚拟功能节点；
其中，NFV MANO可以包括：虚拟网络功能调度(英文：NFV Orchestrator，缩写：NFVO)、虚拟网络功能管理(英文：VNF Manager，缩写：VNFM)及虚拟化基础建设管理(英文：Virtualised Infrastructure Manager，缩写：VIM)三个部分；同时，为了实现域功能实体与VNF之间的交互，所述网络管理系统还需要在域功能实体与VNF之间包括一个网元管理(英文：element manager，缩写：EM)，每个EM管理和负责一个或者多个VNF；也可以不包括EM，使域功能实体与VNF直接相连；本发明实施例对比不进行限 定，本文仅以域功能实体与VNF之间有EM为例进行说明。
可选的，当网络管理系统包含：EM2031、以及VNF2032、NFVI2033和NFV MANO2034时，如图4A所示，所述网络管理系统20的结构可以如下：
OSS202与域功能实体201相连接，域功能实体与EM2031和NFV MANO2034相连接，EM2031与VNF2032相连接，VNF2032与NFVI2033相连接，NFV MANO2034分别与EM2031、VNF2032和NFVI2033相连接；
其中，EM2031、VNF2034、NFVI2033、NFV MANO2034与现有如图1所示的NFV架构中的EM、VNF、NFVI、NFV MANO具有相同功能，在此不再赘述。
下面以业务请求为：视频性能数据请求、网络业务(英文：network service，缩写：NS)实例化请求、网络规划请求，分别对OSS、域功能实体、EM、VNF、NFVI、NFV MANO的具体功能进行介绍：
(1)网络业务请求为视频性能数据请求
OSS202，用于接收用户发送的视频性能数据请求，向移动域功能实体发送所述视频性能数据请求。
其中，所述视频性能数据请求来自移动网络，用于请求获取移动网络的视频体验分析数据。
移动域功能实体201、用于根据分析算法进行分析，获得可反映视频性能的参数。
其中，所述参数可以准确反映用户的视频体验，包括：初始缓冲时延，中断次数，中断时延中的至少一个。
所述移动域功能实体201，还用于接收EM发送的与所述参数对应的服务数据，将接收到的服务数据进行处理后，发送给OSS202，由OSS202反馈给用户。
具体的，所述移动域功能实体201，可以用于：向EM发送所述视频性能数据请求以及包含所述参数的分析结果，接收EM根据 所述参数从与EM管理的VNF中获取的服务数据；
或者，接收EM主动上报的EM已收集到的与所述参数对应的服务数据。
其中，EM和VNF之间的数据获取流程为现有流程，本发明不详细描述；所述将接收到的服务数据进行处理可以包括：将服务数据进行统计，形成直接能够反映用户视频体验的数据或者动态图片；
例如，服务数据中包含大量的中断时延，此时可以将该数据转化中断时延较大、较小等直接反映用户视频体验的数据。
(2)网络业务请求为NS实例化请求
OSS202，用于接收用户发送的NS实例化请求，向移动域功能实体201发送所述NS实例化请求。
其中，所述NS实例化请求来自于移动网络，用于请求为所述用户分配相应的资源，以满足用户的某种需求，如降低时延，提高用户体验。
移动域功能实体201，用于根据分析算法分析NS实例化所需求的资源，执行相应的配置策略，并向NFV MANO中的NFVO发送所述NS实例化请求以及所述配置信息。
NFVO，用于根据所述配置信息进行NS实例化，并向域功能实体发送NS实例化成功消息，由域功能实体向OSS发送所述NS实例化成功消息。
其中，所述NS实例化的过程为现有技术，在此不再详细描述。
(3)网络业务请求为网络规划请求
OSS202，用于接收用户发送的网络规划请求，并向移动域功能实体201发送所述网络规划请求。
其中，所述网络规划请求可以为针对移动网络的网络规划请求，用于请求：在网络管理系统上新增一个网元节点；
或者，更改网络管理系统中现有网络节点的容量等特性。
移动域功能实体201，用于根据分析算法分析网络规划请求所 需求的资源，执行相应的配置策略，并向NFV MANO中的NFVO发送所述网络规划请求以及所述配置信息。
例如，若网络规划请求为新增一个网元节点，则配置策略为组成该网元节点的资源的相关配置，且按照该配置组成的网元节点与实体节点具有相同的功能。
NFVO，用于根据所述配置信息进行网络规划，并向域功能实体发送网络规划成功消息，由域功能实体向OSS发送所述网络规划成功消息。
其中，所述网络规划的过程为现有技术，在此不再详细描述。
由上可知，与现有NFV架构相比，本实施例中的网络管理架构中增加了域功能实体，由域功能实体采用相应算法对业务请求进行分析处理，使得OSS不再对接收到业务请求进行算法分析，大大降低了OSS的负担。
实施例四
图5示出了本发明实施例提供的一种网络管理方法的流程图，应用于实施例一所述的域功能实体，所述方法可以包括：
101、接收OSS发送的业务请求。
其中，所述与所述业务请求对应的第一虚拟网络功能节点可以为：根据分析结果执行相关处理后，处理结果能够满足用户的业务请求的虚拟网络功能节点；
102、根据所述业务请求、以及与所述业务请求相对应的分析算法获得分析结果。
需要说明的是，本发明实施例中，针对不同的业务请求，域功能实体采用不同的分析算法进行处理，其中，该分析算法可以为现有NFV架构中OSS接收到业务请求，针对该业务请求采用的算法，也可以为后期随着通信技术的发展，革新的算法；
例如，若该业务请求为视频性能数据请求，则与该业务请求对应的分析算法可以为：能够准确地获得反映该视频性能的参数为哪些参数(如初始缓冲时延、中断次数、中断时延)，并且在收集 到视频性能数据后能够进行预分析的算法，例如采用平均意见分(mean opinion score，MOS)算法计算出客户体验的分值来表征客户体验，并反馈给OSS；若该业务请求为新增一个虚拟网元节点的请求，则与该业务请求对应的分析算法为：能够定量的计算出多少虚拟资源(如计算资源、存储资源和网络资源)的组合可以实现该网元的实体功能的算法。
103、向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，由所述第一虚拟功能节点根据所述分析结果进行处理。
104、接收所述第一虚拟功能节点发送的处理结果，向所述OSS发送所述处理结果。
例如，若用户请求视频性能数据，则处理结果包含：分析结果中的一些性能参数(如初始缓冲时延、中断次数、中断时延)的数据；若该业务请求为新增一个虚拟网元节点的请求，则处理结果为：已根据分析结果进行相应的虚拟资源组合。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，所述域功能实体专门处理一个域的业务请求；可以为移动域功能实体，也可以为固定域功能实体，还可以为随着通信技术发展新增的其他域的域功能实体；
所述移动域功能实体用于处理移动网络的业务请求；
所述固定域功能实体用于处理固定网络的业务请求。
由上可知，本发明实施例提供一种网络管理方法，接收OSS发送的业务请求，根据业务请求以及与所述业务请求相对应的分析算法获得分析结果，向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，并接收所述设备根据所述分析结果进行处理后反馈回的处理结果，向OSS发送所述处理结果。如此，由域功能实体代替了OSS根据业务请求以及与所述业务请求相对应的分析算法获得分析结果的 执行功能，大大降低了OSS的负担。
实施例五
图6示出了本发明实施例提供的一种网络管理方法的流程图，应用于实施例二所述的OSS，如图6所示，所述方法可以包括：
201、接收用户的业务请求。
其中，所述业务请求可以由用户通过所述OSS的用户交互界面发送；
还可以由用户通过用户的手持终端发送。
202、向域功能实体发送所述业务请求，由所述域功能实体对所述业务请求进行分析处理。
203、接收所述域功能实体发送的处理结果。
可选的，所述OSS还可以将所述处理结果通过用户交互界面反馈给用户，或者将处理结果发送至用户的手持终端，由用户选择查看。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，还需要将业务请求发送至专门的域功能实体上，所述网络管理方法还可以包括：
根据所述业务请求确定所述业务请求对应的网络类型；
向与所述网络类型对应的域功能实体发送所述业务请求。
其中，所述网络类型可以包括：固定网络、移动网络、以及后期随着通信技术发展新增的其他网络；
所述与业务请求对应的网络类型可以为：发出业务请求的用户所在的网络的网络类型；例如，处于移动网的用户发送该业务请求，则与所述业务请求对应的网络类型为移动网络。
所述与所述网络类型对应的域功能实体为：专门用于根据从该网络类型发出的业务请求执行相关处理的域功能实体，可以为移动域功能实体，也可以为固定域功能实体；所述移动域功能实体用户处理移动网络的业务请求；所述固定域功能实体用于处理固定网 络的业务请求；
例如，某一业务请求来自移动网络，网络类型为移动网络，域功能实体1仅处理移动网业务，域功能实体2仅处理固定网业务，则与该业务请求对应的域功能实体为域功能实体1，而不能是域功能实体2。
由上可知，本发明实施例提供一种网络管理方法，接收用户的业务请求，并将所述业务请求发送至域功能实体，由域功能实体对业务请求进行分析处理，并将域功能实体反馈的处理结果反馈给用户。如此，OSS不再对业务请求进行分析处理，大大降低了OSS负担。
实施例六
图7示出了本发明实施例提供的又一种网络管理方法的流程图，应用于实施例三所述的网络管理系统，包括：OSS、至少一个域功能实体、以及至少一个虚拟功能节点；如图7所示，所述方法可以包括：
301、OSS接收用户的业务请求，并向域功能实体发送所述业务请求。
其中，业务请求可以由用户通过所述OSS的用户交互界面发送；
也可以由用户通过用户的手持终端发送。
302、域功能实体根据接收到的所述业务请求、以及与所述业务请求相对应的分析算法获得分析结果，并向与所述业务请求对应的第一虚拟网络功能节点发送所述分析结果。
303、第一虚拟网络功能节点根据所述分析结果进行相关处理，并向所述域功能实体发送处理结果。
304、域功能实体将接收到的所述处理结果反馈给所述OSS。
305、OSS将所述处理结果反馈给所述用户。
优选的，OSS可以将所述处理结果通过用户交互界面反馈给用户；
或者，将处理结果发送至用户的手持终端，由用户选择查看。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，所述网络管理系统20可以包括：至少一个域功能实体，一个域功能实体仅处理一个域的业务请求，
相应的，所述OSS接收用户的业务请求，并向域功能实体发送所述业务请求可以包括：
所述OSS根据所述业务请求确定所述业务请求对应的网络类型；
并向与所述网络类型对应的域功能实体发送所述业务请求。
其中，所述网络类型可以包括：固定网络、移动网络、以及后期随着通信技术发展新增的其他网络；所述与业务请求对应的网络类型可以为：发出业务请求的用户所在的网络的网络类型；例如，处于移动网的用户发送该业务请求，则与所述业务请求对应的网络类型为移动网络。
所述与所述网络类型对应的域功能实体为：专门用于根据从该网络类型发出的业务请求执行相关处理的域功能实体，可以为移动域功能实体，也可以为固定域功能实体；所述移动域功能实体用户处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求；
例如，某一业务请求来自移动网络，网络类型为移动网络，域功能实体1仅处理移动网业务，域功能实体2仅处理固定网业务，则与该业务请求对应的域功能实体为域功能实体1，而不能是域功能实体2。
可选的，本发明提供的网络管理系统中的虚拟功能节点可以包括：至少一个虚拟化网络功能(英文：virtualized network function，缩写：VNF)、网络功能虚拟化基础建设(英文：NFV infrastructure，缩写：NFVI)、网络功能虚拟化管理与协调流程(英 文：NFV Management and Orchestration，缩写：NFV MANO)以及后期随着通信技术的发展，新增加的一些虚拟功能节点，其中，NFV MANO可以包括：虚拟网络功能调度(英文：NFV Orchestrator，缩写：NFVO)、虚拟网络功能管理(英文：VNF Manager，缩写：VNFM)及虚拟化基础建设管理(英文：Virtualised Infrastructure Manager，缩写：VIM)三个部分；
同时，为了实现域功能实体与VNF之间的交互，所述网络管理系统还需要在域功能实体与VNF之间可以包括一个网元管理(英文：element manager，缩写：EM)，每个EM管理和负责一个或者多个VNF；也可以不包括EM，使域功能实体与VNF直接相连；本发明实施例对比不进行限定，本文仅以域功能实体与VNF之间有EM为例进行说明。
当网络管理系统包含：EM、VNF、NFVI、NFV MANO几大功能节点时，所述网络管理系统中，OSS可以与域功能实体相连接，域功能实体可以与EM和NFV MANO相连接，EM可以与VNF相连接，VNF可以与NFVI，EM以及VNFM相连接，NFV MANO可以分别与EM、VNF和NFVI相连接；其中，VNF、NFVI、NFV MANO与现有如图1所示的NFV架构中的VNF、NFVI、NFV MANO具有相同功能，在此不再赘述；
下面以业务请求为：视频性能数据请求、网络业务(英文：network service，缩写：NS)实例化请求、网络规划请求，分别对OSS、域功能实体、VNF、NFVI、NFV MANO之间的交互进行具体介绍：
图7A示出了当网络业务请求为视频性能数据请求时，本发明提供的一种网络管理方法的流程图，如图7A所示，所述方法可以包括：
301A、OSS接收用户发送的视频性能数据请求。
其中，所述视频性能数据请求来自移动网络，用于请求获取移动网络的用户的视频体验分析数据。
302A、OSS向移动域功能实体发送视频性能数据请求。
303A、移动域功能实体根据分析算法进行分析，获得可反映视频性能的参数。
其中，所述参数可以准确反映用户的视频体验，包括：初始缓冲时延，中断次数，中断时延中的至少一个。
304A、移动域功能实体接收EM发送的与所述参数对应的服务数据；
优选的，移动域功能实体可以向EM发送所述视频性能数据请求以及包含所述参数的分析结果，接收EM根据所述参数从与EM管理的VNF中获取的服务数据。
或者移动域功能实体接收EM主动上报的EM已收集到的与所述参数对应的服务数据。
具体的，EM和VNF之间的数据获取流程为现有流程，本发明不详细描述。
305A、移动域功能实体将接收到的服务数据进行处理后，发送给OSS，由OSS反馈给用户。
其中，所述将接收到的服务数据进行处理可以包括：将服务数据进行统计，形成直接能够反映用户视频体验的数据或者动态图片；例如，服务数据中包含大量的中断时延，此时可以将该数据转化中断时延较大、较小等直接反映用户视频体验的数据。
图7B示出了当网络业务请求为NS实例化请求时，本发明提供的一种网络管理方法的流程图，如图7B所示，所述方法可以包括：
301B：OSS接收用户发送的NS实例化请求。
其中，所述NS实例化请求来自于移动网络，用于请求为所述用户分配相应的资源，以满足用户的某种需求，如降低时延，提高用户体验。
302B：OSS向移动域功能实体发送NS实例化请求。
303B、移动域功能实体根据分析算法分析NS实例化所需求的 资源，执行相应的配置策略。
304B、移动域功能实体向NFV MANO中的NFVO发送所述NS实例化请求以及所述配置信息。
305B、NFVO根据所述配置信息进行NS实例化。
其中，所述NS实例化的过程为现有技术，在此不再详细描述。
306B、NFVO向移动域功能实体发送NS实例化成功消息，由移动域功能实体向OSS发送所述NS实例化成功消息。
图7C示出了当网络业务请求为网络规划请求时，本发明提供的一种网络管理方法的流程图，如图7C所示，所述方法可以包括：
301C：OSS接收用户发送的网络规划请求。
其中，所述网络规划请求可以为针对移动网络的网络规划请求，用于请求：在网络管理系统上新增一个网元节点，或者更改网络管理系统中现有网络节点的容量等特性。
302C：OSS向移动域功能实体发送网络规划请求。
303C、移动域功能实体根据分析算法分析网络规划请求所需求的资源，执行相应的配置策略。
例如，若网络规划请求为新增一个网元节点，则配置策略为组成该网元节点的资源的相关配置，且按照该配置组成的网元节点与实体节点具有相同的功能。
304C、移动域功能实体向NFV MANO中的NFVO发送所述网络规划请求以及所述配置信息。
305C、NFVO根据所述配置信息进行网络规划。
其中，所述网络规划的过程为现有技术，在此不再详细描述。
306C、NFVO向移动域功能实体发送网络规划成功消息，由移动域功能实体向OSS发送所述网络规划成功消息。
由上可知，本实施例提供的网络管理方法中，由域功能实体采用相应算法对业务请求进行分析处理，使得OSS不再对接收到业务请求进行算法分析，大大降低了OSS的负担。
实施例七
图8为本发明实施例提供的一种域功能实体401，该域功能实体可以与虚拟功能节点之间通过运营商内部管理的接口连接，负责每个域功能实体对应类型的网络的告警、话务统计、配置管理、网络规划等网络管理功能；
如图8所示，所述域功能实体401可以包括：通信接口4011，处理器4012、存储器4013、至少一个通信总线4014，用于实现这些装置之间的连接和相互通信；
通信接口4011为用硬件方式实现的接口，如用户交互界面，用于实现通信接口所在设备的输入和输出功能，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在通信接口上操作)，并根据预先设定的程式驱动相应的连接装置，还可用于发送用户输入的信息或提供给用户的信息；还可以为软件方式实现的接口，本发明实施例对此不做限定。
处理器4012可能是一个中央处理器(英文：central processing unit，简称为CPU)；
存储器4013可以为易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；或者非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；或者上述种类的存储器的组合，用于向存储器所在设备上的处理器提供指令和数据。
所述通信接口4011，用于接收OSS发送的业务请求。
所述处理器4012，用于根据所述业务请求以及与所述业务请求相对应的分析算法获得分析结果。
所述通信接口4011，还用于并向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果；
接收所述设备根据所述分析结果进行处理后反馈回的处理结果；
向OSS发送所述处理结果。
需要说明的是，本发明实施例中，针对不同的业务请求，域功能实体采用不同的分析算法进行处理，其中，该分析算法可以为现有NFV架构中OSS接收到业务请求，针对该业务请求采用的算法，也可以为后期随着通信技术的发展，革新的算法；
例如，若该业务请求为视频性能数据请求，则与该业务请求对应的分析算法可以为：能够准确地获得反映该视频性能的参数为哪些参数(如初始缓冲时延、中断次数、中断时延)，并且在收集到视频性能数据后能够进行预分析的算法，例如采用平均意见分(mean opinion score，MOS)算法计算出客户体验的分值来表征客户体验，并反馈给OSS；若该业务请求为新增一个虚拟网元节点的请求，则与该业务请求对应的分析算法为：能够定量的计算出多少虚拟资源(如计算资源、存储资源和网络资源)的组合可以实现该网元的实体功能的算法。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，所述域功能实体专门处理一个域的业务请求；可以为移动域功能实体，也可以为固定域功能实体，还可以为随着通信技术发展新增的其他域的域功能实体；
所述移动域功能实体用于处理移动网络的业务请求；
所述固定域功能实体用于处理固定网络的业务请求。
由上可知，本发明实施例提供一种域功能实体，接收OSS发送的业务请求，根据业务请求以及与所述业务请求相对应的分析算法获得分析结果，向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，并接收所述设备根据所述分析结果进行处理后反馈回的处理结果，向OSS发送所述处理结果。如此，由域功能实体代替了OSS根据业 务请求以及与所述业务请求相对应的分析算法获得分析结果的执行功能，大大降低了OSS的负担。
实施例八
图9为本发明实施例提供一种OSS402的结构图，与传统的网络管理节点不同，不再负责网络的告警、话务统计、配置管理、网络规划等网络管理功能，而是与域功能实体之间通过运营商内部管理的接口连接，将接收到的业务请求发送至相应的域功能实体，由域功能实体根据业务请求执行相关的处理功能；
如图9所示，可以包括：通信接口4021，处理器4022、存储器4023、至少一个通信总线4024，用于实现这些装置之间的连接和相互通信；
通信接口4021可以为用硬件方式实现的接口，如用户交互界面，用于实现通信接口所在设备的输入和输出功能，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在通信接口上操作)，并根据预先设定的程式驱动相应的连接装置，还可用于发送用户输入的信息或提供给用户的信息；还可以为软件方式实现的接口，本发明实施例对此不做限定。
处理器4022可能是一个中央处理器(英文：central processing unit，简称为CPU)；
存储器4023可以为易失性存储器(英文·volatile memory)，例如随机存取存储器(英文·random-access memory，缩写·RAM)；或者非易失性存储器(英文·non-volatile memory)，例如只读存储器(英文·read-only memory，缩写·ROM)，快闪存储器(英文·flash memory)，硬盘(英文：hard disk drive，缩写·HDD)或固态硬盘(英文·solid-state drive，缩写·SSD)；或者上述种类的存储器的组合，用于向存储器所在设备上的处理器提供指令和数据。
所述通信接口4021，用于接收用户的业务请求；
向域功能实体发送所述业务请求，由所述域功能实体对所述 业务请求进行分析处理；
接收所述域功能实体反馈的处理结果，并将所述处理结果反馈给所述用户。
其中，所述业务请求可以由用户通过所述OSS202的用户交互界面发送；
还可以由用户通过用户的手持终端发送。
可选的，所述通信接口4021，可以将所述处理结果通过用户交互界面反馈给用户；
或者，将处理结果发送至用户的手持终端，由用户选择查看。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，还需要将业务请求发送至专门的域功能实体上，具体实现如下：
所述处理器4022，用于根据所述业务请求确定所述业务请求对应的网络类型；
所述通信接口4021，具体用于向与所述网络类型对应的域功能实体发送所述业务请求。
其中，所述网络类型可以包括：固定网络、移动网络、以及后期随着通信技术发展新增的其他网络；所述与业务请求对应的网络类型可以为：发出业务请求的用户所在的网络的网络类型；例如，处于移动网的用户发送该业务请求，则与所述业务请求对应的网络类型为移动网络。
所述与所述网络类型对应的域功能实体为：专门用于根据从该网络类型发出的业务请求执行相关处理的域功能实体，可以为移动域功能实体，也可以为固定域功能实体；所述移动域功能实体用于处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求。
例如，某一业务请求来自移动网络，网络类型为移动网络，域功能实体1仅处理移动网业务，域功能实体2仅处理固定网业务， 则与该业务请求对应的域功能实体为域功能实体1，而不能是域功能实体2。
由上可知，本发明实施例提供一种OSS，接收用户的业务请求，并将所述业务请求发送至域功能实体，由域功能实体对业务请求进行分析处理，并将域功能实体反馈的处理结果反馈给用户。如此，OSS不再对业务请求进行分析处理，大大降低了OSS负担。
实施例九
图10示出了本发明实施例提供的一种网络管理系统40的结构图，用于执行实施例六所述的方法，如图10所示，所述系统40可以包括：OSS402、域功能实体401以及包含至少一个虚拟功能节点；
其中，OSS402与实施七所述的OSS402具有相同功能，与传统的网络管理节点不同，不再负责网络的告警、话务统计、配置管理、网络规划等网络管理功能，而是与域功能实体之间通过运营商内部管理的接口连接，将接收到的业务请求发送至相应的域功能实体，由域功能实体根据业务请求执行相关的处理功能；
域功能实体401与实施例八所述的域功能实体401具有相同功能，可以与虚拟功能节点之间通过运营商内部管理的接口连接，负责每个域功能实体对应类型的网络的告警、话务统计、配置管理、网络规划等网络管理功能；
所述虚拟功能节点可以位于营运商用以提供网络服务的任一共享设备，如共享服务器、存储设备或者交换机上，为利用标准虚拟化技术虚拟出的与部署于数据中心、网络节点或终端用户处的路由器、防火墙、负载均衡器、交换机、服务器等各式信息基础设备具有相同功能的节点，不再与OSS直接进行交互，而是与域功能实体401通过运营商内部管理的接口进行连接，为用户提供各式服务。
所述OSS402，用于接收用户的业务请求，并向域功能实体401发送所述业务请求。
其中，所述业务请求可以由用户通过所述OSS402的用户交互界面发送，也可以由用户通过用户的手持终端发送给OSS402。
所述域功能实体401，用于接收所述OSS402发送的业务请求，根据所述业务请求以及与所述业务请求相对应的分析算法获得分析结果，并向与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果。
其中，业务请求可以根据来源分为：移动网业务请求、固定网业务请求及其他网络业务请求。
需要说明的是，本发明实施例中，针对不同的业务请求，域功能实体采用不同的分析算法进行处理，其中，该分析算法可以为现有NFV架构中OSS接收到业务请求，针对该业务请求采用的算法，也可以为后期随着通信技术的发展，革新的算法；
例如，若该业务请求为视频性能数据请求，则与该业务请求对应的分析算法可以为：能够准确地获得反映该视频性能的参数为哪些参数(如初始缓冲时延、中断次数、中断时延)，并且在收集到视频性能数据后能够进行预设分析的算法，例如采用平均意见分(mean opinion score，MOS)算法计算出客户体验的分值来表征客户体验，并反馈给OSS；若该业务请求为新增一个虚拟网元节点的请求，则与该业务请求对应的分析算法为：能够定量的计算出多少虚拟资源(如计算资源、存储资源和网络资源)的组合可以实现该网元的实体功能的算法。
所述与所述业务请求对应的第一虚拟网络功能节点可以为：根据分析结果执行相关处理后，处理结果能够满足用户的业务请求的虚拟网络功能节点；
所述第一虚拟网络功能节点，用于根据所述域功能实体401发送的分析结果进行相关处理，并向域功能实体401发送处理结果。
其中，所述针对不同的分析结果的相关处理可以为现有技术，例如找到对应节点搜集相关信息等等，在此不再详细介绍；
例如，若用户请求视频性能数据，则处理结果包含：分析结果中的一些性能参数(如初始缓冲时延、中断次数、中断时延)的数据；若该业务请求为新增一个虚拟网元节点的请求，则处理结果为：已根据分析结果进行相应的虚拟资源组合。
所述域功能实体401，还用于接收所述第一虚拟网络功能节点发送的处理结果，向OSS402反馈所述处理结果。
进一步的，所述OSS402，还可以用于：
将所述处理结果通过用户交互界面反馈给用户，或者将处理结果发送至用户的手持终端，由用户选择查看。
可选的，本发明实施例中，为了避免网络业务处理之间交叉处理带来的不便、以及将不同域的处理功能集中在同一域功能实体上，加重域功能实体的负担的问题，所述网络管理系统40可以包括：至少一个域功能实体，一个域功能实体仅处理一个域的业务请求。
相应的，所述OSS402，具体用于：
根据所述业务请求确定所述业务请求对应的网络类型；
向与所述网络类型对应的域功能实体发送所述业务请求。
其中，所述网络类型可以包括：固定网络、移动网络、以及后期随着通信技术发展新增的其他网络；所述与业务请求对应的网络类型可以为：发出业务请求的用户所在的网络的网络类型；例如，处于移动网的用户发送该业务请求，则与所述业务请求对应的网络类型为移动网络。
所述与所述网络类型对应的域功能实体为：专门用于根据从该网络类型发出的业务请求执行相关处理的域功能实体，可以为移动域功能实体，也可以为固定域功能实体；所述移动域功能实体用于处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求。
例如，某一业务请求来自移动网络，网络类型为移动网络，域功能实体1仅处理移动网业务，域功能实体2仅处理固定网业务， 则与该业务请求对应的域功能实体为域功能实体1，而不能是域功能实体2。
可选的，本发明提供的网络管理系统中的虚拟功能节点可以包括：至少一个虚拟化网络功能(英文：virtualized network function，缩写：VNF)、网络功能虚拟化基础建设(英文：NFV infrastructure，缩写：NFVI)、网络功能虚拟化管理与协调流程(英文：NFV Management and Orchestration，缩写：NFV MANO)以及后期随着通信技术的发展，新增加的一些虚拟功能节点，其中，NFV MANO可以包括：虚拟网络功能调度(英文：NFV Orchestrator，缩写：NFVO)、虚拟网络功能管理(英文：VNF Manager，缩写：VNFM)及虚拟化基础建设管理(英文：Virtualised Infrastructure Manager，缩写：VIM)三个部分；
同时，为了实现域功能实体与VNF之间的交互，所述网络管理系统还需要在域功能实体与VNF之间包括一个网元管理(英文：element manager，缩写：EM)，每个EM管理和负责一个或者多个VNF；也可以不包括EM，使域功能实体与VNF直接相连；本发明实施例对比不进行限定，本文仅以域功能实体与VNF之间有EM为例进行说明。
可选的，当网络管理系统包含：EM、以及VNF、NFVI和NFV MANO时，所述网络管理系统40的结构可以如下：
OSS402与域功能实体401相连接，域功能实体与EM和NFV MANO相连接，EM与VNF相连接，VNF与NFVI相连接，NFV MANO分别与EM、VNF和NFVI相连接；其中，EM、VNF、NFVI、NFV MANO与现有如图1所示的NFV架构中的EM、VNF、NFVI、NFV MANO具有相同功能，在此不再赘述。
下面以业务请求为：视频性能数据请求、网络业务(英文：network service，缩写：NS)实例化请求、网络规划请求，分别对OSS、域功能实体、EM、VNF、NFVI、NFV MANO的具体功能进行介绍：
(1)网络业务请求为视频性能数据请求
OSS402，用于接收用户发送的视频性能数据请求，向移动域功能实体发送所述视频性能数据请求。
其中，所述视频性能数据请求来自移动网络，用于请求获取移动网络的视频体验分析数据。
移动域功能实体401、用于根据分析算法进行分析，获得可反映视频性能的参数。
其中，所述参数可以准确反映用户的视频体验，包括：初始缓冲时延，中断次数，中断时延中的至少一个。
所述移动域功能实体401，还用于接收EM发送的与所述参数对应的服务数据，将接收到的服务数据进行处理后，发送给OSS402，由OSS402反馈给用户。
具体的，所述移动域功能实体401，可以用于：向EM发送所述视频性能数据请求以及包含所述参数的分析结果，接收EM根据所述参数从与EM管理的VNF中获取的服务数据；或者接收EM主动上报的EM已收集到的与所述参数对应的服务数据。
其中，EM和VNF之间的数据获取流程为现有流程，本发明不详细描述；所述将接收到的服务数据进行处理可以包括：将服务数据进行统计，形成直接能够反映用户视频体验的数据或者动态图片；例如，服务数据中包含大量的中断时延，此时可以将该数据转化中断时延较大、较小等直接反映用户视频体验的数据。
(2)网络业务请求为NS实例化请求
OSS402，用于接收用户发送的NS实例化请求，向移动域功能实体401发送所述NS实例化请求。
其中，所述NS实例化请求来自于移动网络，用于请求为所述用户分配相应的资源，以满足用户的某种需求，如降低时延，提高用户体验。
移动域功能实体401，用于根据分析算法分析NS实例化所需求的资源，执行相应的配置策略，并向NFV MANO中的NFVO发 送所述NS实例化请求以及所述配置信息。
NFVO，用于根据所述配置信息进行NS实例化，并向域功能实体发送NS实例化成功消息，由域功能实体向OSS发送所述NS实例化成功消息。
其中，所述NS实例化的过程为现有技术，在此不再详细描述。
(3)网络业务请求为网络规划请求
OSS402，用于接收用户发送的网络规划请求，并向移动域功能实体401发送所述网络规划请求。
其中，所述网络规划请求可以为针对移动网络的网络规划请求，用于请求：在网络管理系统上新增一个网元节点，或者更改网络管理系统中现有网络节点的容量等特性。
移动域功能实体401，用于根据分析算法分析网络规划请求所需求的资源，执行相应的配置策略，并向NFV MANO中的NFVO发送所述网络规划请求以及所述配置信息。
例如，若网络规划请求为新增一个网元节点，则配置策略为组成该网元节点的资源的相关配置，且按照该配置组成的网元节点与实体节点具有相同的功能。
NFVO，用于根据所述配置信息进行网络规划，并向域功能实体发送网络规划成功消息，由域功能实体向OSS发送所述网络规划成功消息。
其中，所述网络规划的过程为现有技术，在此不再详细描述。
由上可知，与现有NFV架构相比，本实施例中的网络管理架构中增加了域功能实体，由域功能实体采用相应算法对业务请求进行分析处理，使得OSS不再对接收到业务请求进行算法分析，大大降低了OSS的负担。
由上可知，与现有NFV架构相比，本实施例中的网络管理系统，OSS在接收到业务请求后，不根据相应的分析算法对业务请求进行分析处理，大大降低了OSS的负担。
所属领域的技术人员可以清楚地了解到，为描述的方便和简 洁，上述描述的单元和系统的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件(例如处理器)来 完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：只读存储器、随机存储器、磁盘或光盘等。
最后应说明的是：以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (16)

  1. 一种网络管理系统，其特征在于，包括：营运支持设备OSS、域功能实体、以及至少一个虚拟功能节点；
    所述OSS，用于接收用户的业务请求，并向所述域功能实体发送所述业务请求；
    所述域功能实体，用于接收所述OSS发送的业务请求，根据所述业务请求以及与所述业务请求相对应的分析算法获得分析结果，并向与所述业务请求对应的第一虚拟网络功能节点发送所述分析结果；
    所述第一虚拟网络功能节点，用于根据所述域功能实体发送的分析结果进行相关处理，并向所述域功能实体发送处理结果；
    所述域功能实体，还用于接收所述第一虚拟网络功能节点发送的处理结果，并向所述OSS反馈所述处理结果。
  2. 根据权利要求1所述的网络管理系统，其特征在于，所述网络管理系统包括：至少一个域功能实体；
    所述至少一个域功能实体包括：移动网域功能实体和固定网域功能实体；所述移动域功能实体用于处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求。
  3. 根据权利要求2所述的网络管理系统，其特征在于，所述OSS，具体用于：
    根据接收到的业务请求确定所述业务请求对应的网络类型；
    向与所述网络类型对应的域功能实体发送所述业务请求；
    其中，所述网络类型包括：移动网络和固定网络。
  4. 根据权利要求1-3任一项所述的网络管理系统，其特征在于，所述至少一个虚拟功能节点包括：至少虚拟化网络功能VNF、网络功能虚拟化基础建设NFVI和网络功能虚拟化管理与协调流程NFV MANO中的任意一个或多个；所述网络管理系统还包括：网元管理EM，所述EM用于管理至少一个VNF；
    所述OSS与所述域功能实体相连接，所述域功能实体与所述EM和所述NFV MANO相连接。
  5. 一种域功能实体，其特征在于，包括：
    接收单元，用于接收OSS发送的业务请求；
    分析单元，用于根据所述接收单元接收到的业务请求、以及与所述业务请求相对应的分析算法获得分析结果；
    发送单元，用于向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，由所述第一虚拟功能节点根据所述分析结果进行处理；
    所述接收单元，还用于接收所述第一虚拟功能节点发送的处理结果；
    所述发送单元，还用于向所述OSS发送所述处理结果。
  6. 根据权利要求5所述的域功能实体，其特征在于，
    所述域功能实体为移动域功能实体或者固定域功能实体；
    所述移动域功能实体用于处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求。
  7. 一种营运支持设备OSS，其特征在于，包括：
    接收单元，用于接收用户的业务请求；
    发送单元，用于向域功能实体发送所述业务请求，由所述域功能实体对所述业务请求进行分析处理；
    所述接收单元，还用于接收所述域功能实体发送的处理结果。
  8. 根据权利要求7所述的OSS，其特征在于，所述OSS还包括：
    确定单元，用于根据所述业务请求确定所述业务请求对应的网络类型；
    所述发送单元，具体用于向与所述网络类型对应的域功能实体发送所述业务请求。
  9. 一种网络管理方法，其特征在于，应用于域功能实体，包括：
    接收OSS发送的业务请求；
    根据所述业务请求、以及与所述业务请求相对应的分析算法获得分析结果；
    向包含至少一个虚拟功能节点的设备中的与所述业务请求对应 的所述第一虚拟网络功能节点发送所述分析结果，由所述第一虚拟功能节点根据所述分析结果进行处理；
    接收所述第一虚拟功能节点发送的处理结果，所述域功能实体，还用于向所述OSS发送所述处理结果。
  10. 根据权利要求9所述的网络管理方法，其特征在于，
    所述域功能实体为移动域功能实体或者固定域功能实体；
    所述移动域功能实体用于处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求。
  11. 一种网络管理方法，其特征在于，应用于营运支持设备OSS，包括：
    接收用户的业务请求；
    向域功能实体发送所述业务请求，由所述域功能实体对所述业务请求进行分析处理；
    接收所述域功能实体发送的处理结果。
  12. 根据权利要求11所述的网络管理方法，其特征在于，在接收用户的业务请求之后，所述方法还包括：
    根据所述业务请求确定所述业务请求对应的网络类型；
    所述向域功能实体发送所述业务请求包括：
    向与所述网络类型对应的域功能实体发送所述业务请求。
  13. 一种域功能实体，其特征在于，包括：
    通信接口，用于接收OSS发送的业务请求；
    处理器，用于根据所述通信接口接收到的业务请求、以及与所述业务请求相对应的分析算法获得分析结果；
    所述通信接口，还用于向包含至少一个虚拟功能节点的设备中的与所述业务请求对应的所述第一虚拟网络功能节点发送所述分析结果，由所述第一虚拟功能节点根据所述分析结果进行处理；
    所述通信接口，还用于接收所述第一虚拟功能节点发送的处理结果，并向所述OSS发送所述处理结果。
  14. 根据权利要求13所述的域功能实体，其特征在于，
    所述域功能实体为移动域功能实体或者固定域功能实体；
    所述移动域功能实体用于处理移动网络的业务请求；所述固定域功能实体用于处理固定网络的业务请求。
  15. 一种营运支持设备OSS，其特征在于，包括：
    通信接口，用于接收用户的业务请求；
    所述通信接口，还用于向域功能实体发送所述业务请求，由所述域功能实体对所述业务请求进行分析处理；
    所述通信接口，还用于接收所述域功能实体发送的处理结果。
  16. 根据权利要求15所述的OSS，其特征在于，所述OSS还包括：
    处理器，用于根据所述业务请求确定所述业务请求对应的网络类型；
    所述通信接口，具体用于向与所述网络类型对应的域功能实体发送所述业务请求。
PCT/CN2015/075926 2015-04-03 2015-04-03 一种网络管理系统、设备及方法 WO2016155023A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2017551624A JP6538192B2 (ja) 2015-04-03 2015-04-03 ネットワーク管理のシステム、デバイス、および方法
BR112017021248A BR112017021248A2 (pt) 2015-04-03 2015-04-03 sistema e método de gerenciamento de rede, entidade de função de domínio e sistema de suporte de operações.
EP15886993.3A EP3276883A4 (en) 2015-04-03 2015-04-03 Network management system, device and method
CN201580061925.XA CN107113190B (zh) 2015-04-03 2015-04-03 一种网络管理系统、设备及方法
PCT/CN2015/075926 WO2016155023A1 (zh) 2015-04-03 2015-04-03 一种网络管理系统、设备及方法
US15/722,782 US20180026855A1 (en) 2015-04-03 2017-10-02 Network management system, device, and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/075926 WO2016155023A1 (zh) 2015-04-03 2015-04-03 一种网络管理系统、设备及方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/722,782 Continuation US20180026855A1 (en) 2015-04-03 2017-10-02 Network management system, device, and method

Publications (1)

Publication Number Publication Date
WO2016155023A1 true WO2016155023A1 (zh) 2016-10-06

Family

ID=57003917

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/075926 WO2016155023A1 (zh) 2015-04-03 2015-04-03 一种网络管理系统、设备及方法

Country Status (6)

Country Link
US (1) US20180026855A1 (zh)
EP (1) EP3276883A4 (zh)
JP (1) JP6538192B2 (zh)
CN (1) CN107113190B (zh)
BR (1) BR112017021248A2 (zh)
WO (1) WO2016155023A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019123093A1 (en) * 2017-12-21 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Oss dispatcher for policy-based customer request management

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10728054B2 (en) * 2015-11-04 2020-07-28 Futurewei Technologies, Inc. System and method for VNF termination management
CN110011834B (zh) * 2019-03-11 2020-09-22 烽火通信科技股份有限公司 一种管控融合型电信网络管理方法及系统
CN111556481A (zh) * 2020-06-01 2020-08-18 段云云 一种基于区块链的移动通信节点信息获取系统及方法
CN113839794B (zh) * 2020-06-08 2023-03-31 中国移动通信有限公司研究院 数据处理方法、装置、设备及存储介质
US20220294692A1 (en) * 2021-03-09 2022-09-15 Ciena Corporation Limiting the scope of a declarative configuration editing operation

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207789A (zh) * 2007-12-25 2008-06-25 深圳市同洲电子股份有限公司 一种利用数字电视系统的付费方法、运营系统及服务器
CN101562659A (zh) * 2009-05-22 2009-10-21 深圳市同洲电子股份有限公司 一种通过手机托收电视费用的方法和系统
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
WO2014176105A1 (en) * 2013-04-22 2014-10-30 Cisco Technology, Inc. App store portal providing point-and-click deployment of third-party virtualized network functions

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9130760B2 (en) * 2011-04-26 2015-09-08 Openet Telecom Ltd Systems, devices and methods of establishing a closed feedback control loop across multiple domains
JP2014220675A (ja) * 2013-05-09 2014-11-20 日本電信電話株式会社 通信制御システム
CN105325027B (zh) * 2013-06-17 2019-04-26 日本电气株式会社 自组织网络所用的装置、方法、基站装置及其所用的方法
BR112016004183A8 (pt) * 2013-08-27 2020-02-11 Huawei Tech Co Ltd método para virtualização de função de rede móvel e computador
WO2016022698A1 (en) * 2014-08-07 2016-02-11 Intel IP Corporation Virtualized network function management
KR102398401B1 (ko) * 2014-09-25 2022-05-13 애플 인크. 네트워크 기능 가상화
US9825813B2 (en) * 2014-10-31 2017-11-21 At&T Intellectual Property I, L.P. Creating and using service control functions
WO2016086991A1 (en) * 2014-12-04 2016-06-09 Nokia Solutions And Networks Management International Gmbh Steering of virtualized resources
US9560078B2 (en) * 2015-02-04 2017-01-31 Intel Corporation Technologies for scalable security architecture of virtualized networks
WO2016128062A1 (en) * 2015-02-13 2016-08-18 Nokia Solutions And Networks Oy Security mechanism for hybrid networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207789A (zh) * 2007-12-25 2008-06-25 深圳市同洲电子股份有限公司 一种利用数字电视系统的付费方法、运营系统及服务器
CN101562659A (zh) * 2009-05-22 2009-10-21 深圳市同洲电子股份有限公司 一种通过手机托收电视费用的方法和系统
WO2014176105A1 (en) * 2013-04-22 2014-10-30 Cisco Technology, Inc. App store portal providing point-and-click deployment of third-party virtualized network functions
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3276883A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019123093A1 (en) * 2017-12-21 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Oss dispatcher for policy-based customer request management

Also Published As

Publication number Publication date
US20180026855A1 (en) 2018-01-25
CN107113190B (zh) 2019-12-17
EP3276883A4 (en) 2018-03-21
JP2018510591A (ja) 2018-04-12
EP3276883A1 (en) 2018-01-31
JP6538192B2 (ja) 2019-07-03
BR112017021248A2 (pt) 2018-06-26
CN107113190A (zh) 2017-08-29

Similar Documents

Publication Publication Date Title
US10698717B2 (en) Accelerator virtualization method and apparatus, and centralized resource manager
WO2016155023A1 (zh) 一种网络管理系统、设备及方法
Buyya et al. Software-defined cloud computing: Architectural elements and open challenges
US10523748B2 (en) Managing health status of network devices in a distributed global server load balancing system
US10917294B2 (en) Network function instance management method and related device
US9503387B2 (en) Instantiating incompatible virtual compute requests in a heterogeneous cloud environment
EP3698532B1 (en) Method to track ssl session states for ssl optimization of saas based applications
JP2017517170A (ja) Ｎｆｖシステムにおけるサービス実装のための方法および通信ユニット
US10911310B2 (en) Network traffic steering with programmatically generated proxy auto-configuration files
WO2020139816A1 (en) System and method to operate devices with dns caches
US11586484B2 (en) Automatically replicate API calls to separate data centers
WO2021120633A1 (zh) 一种负载均衡方法及相关设备
Choudhury et al. Shareon: Shared resource dynamic container migration framework for real-time support in mobile edge clouds
Cerroni Network performance of multiple virtual machine live migration in cloud federations
US11558812B2 (en) System and methods for multi-links SD-WAN using cellular device connections
CN114124740A (zh) 一种vnf实例化的方法和装置
Muhammad et al. Service orchestration over clouds and networks
US11056112B2 (en) Voice-based operations
JP2023065176A (ja) プログラム、情報処理方法および情報処理装置
Li Large Scale Distributed Information System Emulation Platform Based on Cloud Computing Technology
Shahzad et al. Minimizing SLA Violations and VMs Migration to Reduce Network Load in Cloud Data Centres

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15886993

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017551624

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017021248

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112017021248

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20171003