WO2018045901A1 - 界面生成***、钻取服务层装置、数据发送方法 - Google Patents

界面生成***、钻取服务层装置、数据发送方法 Download PDF

Info

Publication number
WO2018045901A1
WO2018045901A1 PCT/CN2017/099678 CN2017099678W WO2018045901A1 WO 2018045901 A1 WO2018045901 A1 WO 2018045901A1 CN 2017099678 W CN2017099678 W CN 2017099678W WO 2018045901 A1 WO2018045901 A1 WO 2018045901A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
node
alarm
data
interface
Prior art date
Application number
PCT/CN2017/099678
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 中兴通讯股份有限公司
Publication of WO2018045901A1 publication Critical patent/WO2018045901A1/zh

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/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H04L41/065—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving logical or physical relationship, e.g. grouping and hierarchies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies

Definitions

  • the present invention relates to the field of network function virtualization, and in particular to an interface generation system, a drill service layer device, and a data transmission method.
  • OTT Over The Top
  • OPEX operating costs
  • NFVO Network Function Virtualisation Management & Orchestration
  • the management object relates to the network service (Network Service, NS for short), the virtualised network function (VNF), the virtualized network function component (VNFC), and the virtual deployment unit of the virtual layer ( Virtualised Deploy Unit (VDU); the physical layer host (HOST).
  • Network Service Network Service
  • NS Network Service
  • VNF virtualised network function
  • VNFC virtualized network function component
  • VDU Virtualised Deploy Unit
  • HOST physical layer host
  • the management scope of NFVO covers the physical layer, the virtual layer, and the service layer. It has the characteristics of wide management scope and many types of management objects. The large number of alarms generated by these managed objects every day provide the location of the alarm and the impact of the alarm. Brought great challenges.
  • NFV Network Function Virtualization
  • a virtual machine is deployed on a physical host
  • VNFC is deployed on the virtual machine
  • multiple VDUs belong to a VNF.
  • Multiple VNFs are attributed to one NS. Therefore, the faults generated by the physical host often affect the operation of the virtual machine, which in turn affects the operation of the service system on the virtual machine, thus generating multiple pieces of alarm information.
  • a large amount of alarm information is collected on the NFVO of the upper management system, flooding the alarms that reflect the root cause failure. Therefore, how to help the monitoring personnel quickly locate the root cause of the alarm and analyze the impact range of the alarm becomes a subject that must be considered and solved.
  • the embodiments of the present invention provide an interface generation system, a drill service layer device, and a data transmission method, so as to at least solve the problem that the root cause of the alarm cannot be quickly located in the related art.
  • an interface generation system including: a database, a user interface (UI) interface layer device, and a drill service layer device; wherein, the UI interface layer device is configured to be a user
  • the resource identifier (ID) of the clicked resource node is sent to the drill service layer device, and the data corresponding to the resource ID returned by the drill service layer device is received, and the resource node is generated according to the returned data corresponding to the resource ID.
  • the service layer device is configured to receive the resource ID sent by the UI interface layer device, obtain data corresponding to the resource ID from the database, and send the acquired data corresponding to the resource ID to the UI interface layer device;
  • the data corresponding to the resource ID includes: node topology relationship data of the resource node.
  • the node topology relationship data includes: data of the resource node, data of the parent node of the resource node, and/or data of the child node of the resource node.
  • the data corresponding to the resource ID further includes: alarm indication information used to indicate that the parent node and/or the child node generate an alarm.
  • the UI interface layer device is further configured to generate a topology relationship diagram of the resource node according to the node topology relationship data and the alarm indication information, where the UI interface includes the topology. relation chart.
  • the data corresponding to the resource ID further includes: resource node detailed information, alarm statistical information including content of the resource node generating an alarm, and/or the performance statistical information;
  • the resource node detailed information includes: a keyword and a keyword value of the resource node.
  • the drilling service layer device is further configured to encapsulate the acquired data corresponding to the resource ID into a data object, and send the data object to the UI interface layer device.
  • the drill service layer device is further configured to acquire resource node detailed information, alarm statistical information, and/or performance statistical information from a database by calling a data query application programming interface (API).
  • API application programming interface
  • the UI interface layer device sends the resource ID to the drill service layer device through a Representational State Transfer (REST) interface.
  • REST Representational State Transfer
  • a device for drilling service layer comprising: a receiving module, configured to receive a resource identifier ID of a resource node sent by a UI interface layer; and an obtaining module configured to acquire and a resource ID according to the resource ID
  • the sending module is configured to send data corresponding to the resource ID to the UI interface layer, where the data corresponding to the resource ID includes: node topology relationship data of the resource node; and data corresponding to the resource ID, used for the UI
  • the interface layer generates a UI interface of the resource node.
  • the node topology relationship data includes: data of the resource node, data of the parent node of the resource node, and/or data of the child node of the resource node.
  • the data corresponding to the resource ID further includes: alarm indication information used to indicate that the parent node and/or the child node generate an alarm.
  • the drilling service layer device further includes: the encapsulating module is configured to encapsulate the data corresponding to the resource ID into a data object; wherein the data corresponding to the resource ID further includes: a resource
  • the node detailed information includes alarm statistics and/or performance statistics of the content of the resource node that generates an alarm; wherein the resource node detailed information includes: The keyword and keyword value of the resource node.
  • the obtaining module is further configured to acquire resource node detailed information, alarm statistical information, and/or performance statistical information from the database by calling a data query application programming interface API.
  • the receiving module is further configured to receive the resource ID through the expressive state transfer REST interface.
  • a data sending method includes: receiving a resource identification ID of a resource node sent by a UI interface layer; acquiring data corresponding to the resource ID according to the resource ID, and acquiring data corresponding to the resource ID The data is sent to the UI interface layer, where the data corresponding to the resource ID includes: node topology relationship data of the resource node; and the data corresponding to the resource ID, which is used by the UI interface layer to generate a UI interface of the resource node.
  • the node topology relationship data includes: data of the resource node, data of the parent node of the resource node, and/or data of the child node of the resource node.
  • the data corresponding to the resource ID further includes: alarm indication information used to indicate that the parent node and/or the child node generate an alarm; wherein the alarm indication information is used to generate a topology relationship diagram together with the node topology relationship data. .
  • acquiring the data corresponding to the resource ID according to the resource ID, and sending the data corresponding to the resource ID to the UI interface layer further includes: acquiring, from the database, the resource node detailed information corresponding to the resource ID, including the resource.
  • the alarm statistics and/or performance statistics of the content of the alarm generated by the node; the node topology relationship data, the resource node detailed information, the alarm statistics, and/or the performance statistics information are encapsulated into one data object, and the data object is sent to the UI interface layer.
  • the resource node detailed information includes: a keyword and a keyword value of the resource node.
  • obtaining the resource node detailed information corresponding to the resource ID from the database, and the alarm statistical information and/or performance statistical information including the content of the resource node alarming includes: calling the data query application programming interface API from the data query Obtain resource node details, alarm statistics, and/or performance statistics in the database.
  • the resource identifier ID packet of the resource node sent by the UI interface layer is received. Include: Receive the resource ID through the Representational State Transfer REST interface.
  • a storage medium comprising a stored program, wherein the program is executed to perform the method of any of the above.
  • a processor for running a program wherein the program is executed to perform the method of any of the above.
  • the UI interface of the resource node is generated according to the data corresponding to the resource ID by the interface generation system, wherein the generated UI interface displays the node topology relationship data of the resource node, so that the parent on the UI interface can be clicked.
  • the node icon or the child node icon can quickly access the parent node or the child node, so that when a node generates an alarm, the UI interface can quickly locate the root cause of the alarm, which can solve the problem that the root cause of the alarm cannot be quickly located in the related art.
  • the problem is to improve the efficiency of alarm location.
  • FIG. 1 is a schematic structural diagram of an interface generation system according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural view of a layered drilling system according to a preferred embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of interface generation according to a preferred embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a UI interface provided in accordance with a preferred embodiment of the present invention.
  • FIG. 5 is a schematic diagram of an NFV-MANO architecture in an ETSI standard in accordance with a preferred embodiment of the present invention
  • FIG. 6 is a node relationship diagram of an NFVO management object according to a preferred embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a node relationship corresponding to each node according to a preferred embodiment of the present invention.
  • FIG. 8 is a drill-through analysis from a service layer to a physical layer according to a preferred embodiment of the present invention. Schematic diagram of the operational process
  • FIG. 9 is a schematic diagram of an operation flow for performing drill analysis from a physical layer to a service layer according to a preferred embodiment of the present invention.
  • FIG. 10 is a block diagram showing the structure of a drill service layer device provided in accordance with the present invention.
  • FIG. 11 is a schematic flowchart of a data sending method according to a preferred embodiment of the present invention.
  • FIG. 12 is a block diagram showing the hardware structure of a mobile terminal according to a data transmission method according to an embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of an interface generation system according to an embodiment of the present invention. As shown in FIG. 1, the system includes: a database 10, a UI interface layer device 12, and a drill. Service layer device 14;
  • the UI interface layer device 12 is configured to send the resource identifier ID of the resource node that the user clicks to the drill service layer device 14, and receive the data corresponding to the resource ID returned by the drill service layer device 14 according to the returned resource ID.
  • the service layer device 14 is configured to receive the resource ID sent by the UI interface layer device 12, and obtain data corresponding to the resource ID from the database 10; and send the acquired data corresponding to the resource ID to the UI interface layer device 12;
  • the data corresponding to the resource ID includes: node topology relationship data of the resource node.
  • the UI interface layer device 12 generates a UI interface of the resource node according to the data corresponding to the resource ID, wherein the generated UI interface displays the resource node.
  • the node topology relationship data can be used to quickly access the parent node or the child node by clicking the parent node icon or the child node icon on the UI interface, so that when a node generates an alarm, the UI interface can quickly locate the root cause of the alarm.
  • the problem that the root cause of the alarm cannot be quickly located in the related art can be solved, and the efficiency of the alarm location is improved.
  • the resource node may be a management object of the NFVO, such as a network service NS, a virtual network function VNF, a virtual network function component VNFC, a virtual layer virtual deployment unit, a physical layer host HOST, etc., but is not limited thereto. .
  • the foregoing node topology relationship data may include: data of a resource node, data of a parent node of the resource node, and/or data of a child node of the resource node.
  • the node topology relationship data includes: data of the parent node VDU; when the resource node is VNFC, the node topology relationship data includes: data of the parent node VDU; when the resource node is a VDU, the node topology relationship The data includes: data of the parent node VNF and data of the child node VNFC, or data of the parent node VNF and data of the child node HOST; when the resource node is the VNF, the node topology relationship data includes: data of the parent node NS and data of the child node VDU; When the resource node is an NS, the node topology relationship data includes: data of the child node VNF; but is not limited thereto.
  • the data corresponding to the resource ID further includes: alarm indication information used to indicate that the parent node and/or the child node generate an alarm.
  • the UI interface layer device 12 may be configured to generate a topology relationship diagram of the resource node according to the node topology relationship data and the alarm indication information, where the UI interface includes a topology relationship diagram.
  • alarm indication information may be identification information such as color, highlight, or blinking, but is not limited thereto.
  • the icon of the node in which the resource node, the child node of the resource node, and the parent node of the resource node appear in the topological relationship diagram displayed on the UI interface are The red, that is, the icon of the red node in the topology diagram displayed on the UI interface indicates that the node has an alarm.
  • the other alarm indications are similar, and are not described here.
  • the alarms can be in many levels, such as normal, secondary, primary, and critical.
  • the alarm information corresponding to different levels of alarms is different.
  • the critical alarm can be indicated in red, and the main alarm is indicated in orange.
  • the alarm is indicated by yellow, and the normal alarm is indicated by blue, but is not limited to this.
  • the top-level alarm information is generated together with the node topology relationship data, but is not limited to this.
  • the node with the alarm indication information that is, the node where the alarm is generated
  • the node where the alarm is generated can be quickly viewed through the topology relationship diagram of the UI interface, so that the root cause of the alarm can be located more quickly.
  • the data corresponding to the resource ID further includes: resource node detailed information, alarm statistical information including content of the resource node generating an alarm, and/or the performance statistical information;
  • the resource node detailed information includes: a keyword and a keyword value of the resource node. That is, the drill service layer device 14 may be further configured to acquire resource node detailed information, alarm statistical information, and/or performance statistical information corresponding to the resource ID from the database 10, and to allocate resource node details, alarm statistics, and/or performance.
  • the statistical information is sent to the UI interface layer device 12.
  • the drill service layer device 14 may further be configured to encapsulate the acquired data corresponding to the resource ID into a data object, and send the data object to the UI interface layer device 12.
  • the UI interface generated by the UI interface layer device 12 may include alarm statistics information, performance statistics information, and/or resource node detailed information in addition to the topological relationship map, that is, the content that the user really cares about is focused, and may be very Quickly perform a comprehensive analysis of the resource nodes of interest.
  • This interface presentation is different from the traditional management system (separate management of topology, resources, alarms, and performance, and have their own management interfaces. Users should view the topology of a resource node. You need to switch to different pages to view the relationship graphs, alarm statistics, and performance statistics. You can view the alarm statistics to obtain the alarms, which is the root cause of the alarms.
  • the performance statistics information is used to indicate the performance of the resource node, such as the central processing unit (CPU) usage rate and memory usage rate of the resource node, but is not limited thereto.
  • the above performance statistics can be The periodic collection of the performance statistics information in the generated UI interface can support a change trend of the table or graphical presentation performance indicators, which can assist the operation and maintenance personnel to analyze the cause of the location alarm.
  • the foregoing database 10 may include a resource database, an alarm database, and/or a performance database, where the resource database stores resource instance data of different resource nodes and node relationship data thereof; and alarm data of the storage resource in the alarm database; performance Performance data for storage resources in the database.
  • drill service layer device 14 may also be configured to acquire resource node detailed information, alarm statistical information and/or performance statistical information from the database 10 by calling a data query application programming interface API.
  • the UI interface layer device 12 transmits the resource ID to the drill service layer device 14 via the expressive state transfer REST interface.
  • the interface generation system is universal.
  • the interface generation system When the interface generation system generates the UI interface of the resource node, if the topology node of the resource node displayed on the UI interface is found, the parent node of the resource node and/or The child node icon has an alarm identifier (first alarm indication information and/or second alarm indication information).
  • the interface generation system If the parent node icon is clicked, the interface generation system generates a UI interface of the parent node, if the child node icon When clicked, the interface generation system generates a UI interface of the child node, and combines the interface generation system to quickly access the physical layer through an operation of drilling up to a physical layer when an alarm occurs on a resource node of a physical layer.
  • the resource node generates the range affected by the alarm. When an alarm occurs on a service node, the operation of the lower layer can quickly access the root cause of the alarm generated by the service node.
  • FIG. 2 is a schematic structural diagram of a layered drilling system according to a preferred embodiment of the present invention. As shown in FIG. 2, the system includes:
  • UI interface presentation layer (equivalent to the above UI interface layer device): providing a user operation interface, presenting node relationship diagrams of different node types (equivalent to the above topology relationship diagram), and alarm statistics Information, performance statistics.
  • Drilling service acquires relevant data through API interface query provided by resource management, alarm management, and performance management, and provides data to the UI interface presentation layer through the REST interface, and presents a related interface.
  • Resource management An API query interface that provides resource detail data and resource topology relationship data.
  • Alarm Management An API query interface that provides alarm statistics for resources.
  • Performance Management An API query interface that provides performance statistics for performance.
  • Resource database Stores resource instance data and node relationship data of different resource types.
  • Alarm database Alarm data of storage resources.
  • Performance Database Performance data for storage resources.
  • FIG. 3 is a schematic flowchart of interface generation according to a preferred embodiment of the present invention.
  • the process includes: a user clicking a parent-child node icon on a node relationship diagram; and a UI interface layer passing a resource ID of a resource that the user clicks
  • the REST interface is sent to the drill service layer of the server.
  • the drill service layer After receiving the request, the drill service layer sends the resource ID transmitted by the UI interface layer to the resource management through the API interface provided by the resource management module, and the resource management module details the resource corresponding to the resource ID through the query interface provided by the resource database.
  • the information about the parent and child nodes associated with the resource and the resource are returned to the drill service layer.
  • the drill service layer After receiving the resource detailed information returned by the resource management and the parent-child information of the resource association, the drill service layer continues to send the resource ID information to the alarm management module through the API interface provided by the alarm management module, and the alarm management module provides the alarm database through the alarm database.
  • the query interface queries the alarm statistics corresponding to the resource ID and returns the information to the drill service layer.
  • the drill service layer After receiving the alarm statistics returned by the alarm management, the drill service layer continues to send the resource ID information to the performance management module through the API interface provided by the performance management module, and the performance management module corresponds the resource ID through the query interface provided by the performance database. The performance statistics are queried and returned to the drill service layer.
  • the drill service layer aggregates the resource detail information, the parent and child node information, the alarm statistics, and the performance statistics information corresponding to the resource ID into a data object and returns it to the UI interface layer.
  • the UI interface layer After receiving the data returned by the service layer, the UI interface layer generates the interface shown in FIG. 4, and presents the user with the resource details of the resource selected by the user, the resource parent-child node relationship diagram, Alarm statistics of resources and performance statistics of resources.
  • the preferred embodiment of the present invention is designed according to the NFV-MANO architecture of the ETSI.
  • the physical layer and the virtual layer resources and their alarm and performance data are collected by the VIM (Virtualized Infrastructure Manager) management system and reported to the NFVO through the Nfvo-Vi interface. As shown in Figure 5.
  • the resources of the service layer and its alarm and performance data are collected by the Virtual Network Function Manager (VNFM) management system and reported to the NFVO through the Nfvo-Vnfm interface, as shown in Figure 5.
  • VNFM Virtual Network Function Manager
  • resources, alarms, and performance data of all physical layers, virtual layers, and business layers are aggregated in the NFVO management system, and are uniformly managed and arranged by the NFVO system.
  • the preferred embodiment of the present invention follows the Tosca-NFV (Topology and Orchestration Specification for Cloud Applications) specification when modeling the resources of the physical layer, the virtual layer, and the service layer in the NFVO system, and maps these resource types to Tosca-
  • the node type defined by the NFV specification for example: NS/VNF/VNFC/VDU.
  • the node relationship types defined in the Tosca-NFV specification are used to describe the deployment relationship and attribution relationship between node types in the NFV domain.
  • the present invention places any resource node and its directly associated parent and child nodes in the same topological relationship diagram, as shown in FIG. 7.
  • the interface will present the resource details of the new node and the topological relationship diagram of the parent and child nodes directly associated with the new node.
  • the user can implement the layer drill function between the physical layer, the virtual layer, and the business layer resource node.
  • the invention combines the alarm rendering function.
  • the alarm is rendered on the icon of the resource node, and the resource icon in which the alarm occurs is colored. If the bottom layer The physical host generates an alarm, and the virtual machine running on the host also generates an alarm. At the same time, the virtual machine alarm affects the service running on it, thus generating a service alarm. Then, the alarm rendering will be performed on the corresponding HOST, VDU and VNF resource nodes at the same time. As shown in Figure 7, if three resource nodes of HOST1/VDU1/VNF1 are alerted, the three resource nodes will perform alarm rendering at the same time.
  • a physical node when a physical node generates an alarm, it can also start from the node and quickly locate the traffic generated by the physical layer/virtual layer by means of the upper layer drilling.
  • the preferred embodiment of the present invention provides three perspectives of the service layer, the virtual layer, and the physical layer to monitor the running status of the entire network service system, virtual resources, and physical resources.
  • the service layer perspective is used to monitor the operation of the network service NS and the virtual network function VNF.
  • the virtual layer perspective is used to monitor the operation of the virtual deployment unit (ie virtual machine) VDU.
  • the physical layer perspective is used to monitor the operation of the physical host HOST.
  • a topology overview of the NS of the whole network and the independent VNF is provided (see Figure 71).
  • the NS-VNF node attribution graph is also displayed.
  • the NS alarm information is derived from the VNF alarm.
  • the VNF When the VNF generates an alarm, the alarm is generated on the VNF topology node and the NS node to which it belongs.
  • the user can view the NS-VNF node affiliation map. Quickly locate the VNF node that causes the NS to generate an alarm.
  • VNF topology node Click the VNF topology node to enter the VNF detailed information page, view the basic information description of the VNF, alarm statistics, and performance indicator statistics, and present the node attribution graph of the NS-VNF-VDU. Similarly, the user can quickly locate the VDU node that causes the VNF to generate an alarm by viewing the NS-VNF-VDU node affiliation map.
  • VNF-VDU-VNFC and VNF-VDU-HOST Click the VDU topology node to go to the VDU detailed information page to view the basic information description, alarm statistics, and performance indicator statistics of the VDU.
  • the node attribution/deployment relationship diagram of VNF-VDU-VNFC and VNF-VDU-HOST is also presented. .
  • the VNF-VDU-VNFC node relationship diagram describes which VNFCs are deployed on the VDU.
  • the VNF-VDU-HOST node relationship diagram describes the VDU deployed on the HOST.
  • VNFC node Click the VNFC node from the VNF-VDU-VNFC node to enter the detailed information page of the VNFC, and view the basic information description, alarm statistics, and performance indicator statistics of the VNFC, and the node deployment relationship of the VDU-VNFC.
  • Each node's page contains basic information and alarms of the node. Statistics and performance indicators statistics. You can quickly analyze whether the running status of the node is normal and whether it is the root cause of the service alarm.
  • each node's topology map contains its attribution and deployment associated nodes, this way of drilling can also be a bottom-up approach.
  • a physical host frequently generates alarms with high CPU usage. Although such alarms do not immediately affect the operation of the service system, they also need to analyze the causes. After discovering such an alarm, the user can drill up to see which virtual machines are running on the physical host, and which business systems are running on the virtual machines, so as to know which business systems are affected by the alarm of the physical host. The operation can also analyze whether these service systems are caused by the increase of the traffic volume, causing the physical host to generate a high CPU usage alarm, and then whether it needs to be expanded or level negative. Load balance is the basis for decision making.
  • the preferred embodiment of the present invention centrally allocates resource details, alarm statistics, and performance statistics information of a resource to a page, and also presents a topological relationship diagram of the parent node that is directly associated with the resource node, such as Figure 4 shows. Focusing on what the user really cares about, you can quickly perform a comprehensive analysis of the resource nodes of interest.
  • This interface is different from the traditional management system.
  • the traditional management system manages the topology, resources, alarms, and performance separately. It has its own management interface.
  • the user needs to view the topology relationship, alarm statistics, and performance statistics of a resource. You need to switch to a different page to view, and each page has to do a query operation to filter out information about the resource.
  • the invention extracts the drilling service layer on the server side of the system, and provides data support service for the layer drilling operation performed by the interface.
  • the front-end interface UI only interacts with the drill service layer.
  • the resource ID of the resource is sent to the drill service layer through the REST interface.
  • the drill service layer uses the resource ID as a parameter to invoke the data query API interface of resource management, alarm management, and performance management, and obtains resource data, topology relationship data, alarm data, and performance data information of the resource.
  • the four kinds of data are encapsulated in a data object and returned to the UI interface.
  • the UI interface layer generates a corresponding interface as shown in FIG. 4, and fills in the data returned by the drill service layer into the interface.
  • the root cause of the alarm of the resource node may be analyzed, and the analysis method includes: determining that the resource node in the virtual network generates an alarm; according to the topological relationship between the resource nodes in the virtual network, The alarm rendering feature of the resource node (corresponding to the first alarm indication information and/or the second alarm indication information), determining that the resource node generates the root cause of the alarm; wherein the alarm rendering characteristic is The resource node identifier corresponding to the resource node where the alarm occurs is colored in the topology relationship.
  • determining that the resource node generates the root cause of the alarm includes: according to the topology relationship and the The alarm rendering feature determines that the resource node generates the root cause of the alarm by using an upper layer drill or a lower layer drill; wherein the upward layer is drilled with the resource node as a starting point.
  • determining, by means of the upper layer drilling, that the resource node generates the root cause of the alarm comprises: when the parent node of the resource node is not a virtual service NS, using the resource node as a starting node, and circulating Performing the following steps until the termination condition is met: determining whether an alarm is generated by the starting node; and determining that an alarm is generated by the starting node, acquiring between the starting node and a parent node of the starting node a topological relationship; determining, according to a topological relationship between the starting node and a parent node of the starting node, whether a parent node of the starting node has an alarm rendering; a parent node of the starting node appears In the case of alarm rendering, the parent node of the starting node is used as the starting node; wherein the termination condition is that the starting node has an alarm and the parent node of the starting node does not have an alarm; Determining that the resource node generates the root location of the alarm as a starting node
  • the method further includes: displaying between the start node and a parent node of the start node Topological relationship.
  • a topological relationship between the starting node and a parent node of the starting node is between a virtual deployment unit VDU and a HOST of the virtual layer.
  • Topological relationship in the case that the starting node is a VDU, the topological relationship between the starting node and the parent node of the starting node is a topological relationship between VNF, VDU and HOST or VNF, VDU and The topological relationship between the VNFC and the VNFC; the topological relationship between the start node and the parent node of the start node is a topological relationship between the VDU and the VNFC;
  • the start node is a VNF
  • the topological relationship between the start node and the parent node of the start node is a topological relationship between the NS, the VNF, and the VDU.
  • determining, by using the method of drilling in an upper layer, that the resource node generates the root cause of the alarm includes: acquiring, between the resource node and the parent node, when the parent node of the resource node is an NS Topological relationship; according to the extension between the resource node and the parent node The pinging relationship determines whether the parent node has an alarm rendering. In the case that it is determined that the parent node has an alarm rendering, the root node of the resource node generating the alarm is determined to be the NS.
  • determining, by using a downward layer drilling manner, that the resource node generates the root cause of the alarm comprises: when a child node of the resource node is not a virtual network function component VNFC or a host HOST of a physical layer, The resource node is a start node, and the following steps are performed cyclically until the termination condition is met: determining whether the start node has an alarm; and determining that the start node has an alarm, acquiring the start node and the Determining a topological relationship between the child nodes of the starting node; determining whether a child node of the starting node has an alarm rendering according to a topological relationship between the starting node and a child node of the starting node; In the case that the child node of the starting node has an alarm rendering, the child node of the starting node is used as the starting node; wherein the termination condition is that the starting node has an alarm rendering and the The child node of the originating node does not have an alarm rendering; the root no
  • the method further includes: displaying between the starting node and the child node of the starting node Topological relationship.
  • a topological relationship between the starting node and a child node of the starting node is a topological relationship between the NS and the VNF; and the starting node is a VNF
  • the topological relationship between the start node and the child node of the start node is a topological relationship between the NS, the VNF, and the VDU; when the start node is a VDU, the start node and the The topological relationship between the child nodes of the starting node is the topological relationship between the VNF, the VDU and the VNFC, or the topological relationship between the VNF, the VDU and the HOST.
  • determining, by using a layer-up method, that the resource node generates the root cause of the alarm if the child node of the resource node is VNFC or HOST, acquiring the resource node and the child node a topological relationship between the resource node and the child node, determining whether the child node has an alarm rendering according to a topological relationship between the resource node and the child node; determining the resource if it is determined that the child node has an alarm rendering The node generates the root location of the alarm Is the VNFC or the HOST.
  • the method further includes: acquiring alarm statistics information of the root source location; and determining, according to the alarm statistics information, a source of the alarm generated by the resource node.
  • the analysis method implemented based on the system can be implemented by a specific analysis tool or manually.
  • FIG. 6 is a node relationship diagram of an NFVO management object according to a preferred embodiment of the present invention.
  • the VDU and the VNF are in a many-to-one relationship, and the VNF and the NS are also many-to-one. Relationship; VNFC and VDU are one-to-one deployment relationships, and VDU and HOST are many-to-one deployment relationships.
  • FIG. 8 is an operational flow of drilling analysis from a business layer to a physical layer. As shown in FIG. 8, the method includes:
  • Step 801 View the network service service topology map of the entire network. If an NS is found to generate an alarm, go to step 802.
  • Step 802 View detailed information of the specified NS, including basic information, alarm statistics, performance indicator statistics, and a node relationship diagram of the NS-VNF.
  • Step 803 drills into the VNF node.
  • Step 804 View detailed information of the specified VNF, including basic information, alarm statistics, performance indicator statistics, and node relationship diagram of the NS-VNF-VDU.
  • Step 805 is drilled to the VDU node.
  • Step 806 View detailed information of the specified VDU, including basic information, alarm statistics, performance indicator statistics, and node relationship diagrams of VNF-VDU-VNFC and VNF-VDU-HOST.
  • Step 807 is drilled to the VNFC node.
  • Step 808 View detailed information of the specified VNFC, including basic information, alarm statistics, performance indicator statistics, and node relationship diagram of the VDU-VNFC.
  • Step 809 drills into the HOST node.
  • Step 810 View detailed information of the specified HOST, including basic information, alarm statistics, performance indicator statistics, and a node relationship diagram of the VDU-HOST.
  • FIG. 9 is an operational flow of drilling analysis from the physical layer to the business layer. As shown in FIG. 9, the process includes:
  • Step 901 View the physical host or the board topology of the entire network. If an alarm is generated on a physical host or a board, go to step 902.
  • Step 902 View detailed information about the specified physical host or board, including basic information, alarm statistics, performance indicator statistics, and node relationship diagram of the VDU-HOST.
  • Step 903 drills into the VDU node.
  • Step 904 is to view detailed information of the specified VDU, including basic information, alarm statistics, performance indicator statistics, and node relationship diagrams of VNF-VDU-VNFC and VNF-VDU-HOST.
  • Step 905 drills into the VNFC node.
  • Step 906 View detailed information of the specified VNFC, including basic information, alarm statistics, performance indicator statistics, and a node relationship diagram of the VDU-VNFC.
  • Step 907 drills into the VNF node.
  • Step 908 View detailed information of the specified VNF, including basic information, alarm statistics, performance indicator statistics, and node relationship diagram of the NS-VNF-VDU.
  • Step 909 drills into the NS node.
  • Step 910 View detailed information of the specified NS, including basic information, alarm statistics, performance indicator statistics, and node relationship diagram of the NS-VNF.
  • Figure 3 is a server processing flow of a drill operation, the process includes:
  • step 301 the user clicks on any of the parent and child resource nodes.
  • Step 302 The UI interface presentation layer sends the resource ID clicked by the user to the drill service layer.
  • Step 303 The drill service layer invokes an API query interface provided by the resource management module, and searches for the detailed information of the resource from the resource database according to the resource ID and the parent-child node information directly associated with the resource.
  • Step 304 The drill service layer invokes an API query interface provided by the alarm management module, and searches for the alarm statistics corresponding to the resource from the alarm database according to the resource ID.
  • Step 305 The drill service layer invokes an API query interface provided by the performance management module, and searches for performance statistics corresponding to the resource from the performance database according to the resource ID.
  • Step 306 The drill service layer returns the detailed information of the resource, the parent and child node information associated with the same, the alarm statistical information, and the performance statistics information to the UI interface presentation layer.
  • Step 307 The UI interface presentation layer presents the resource details, the topology relationship diagram, the alarm statistics, and the performance statistics information of the resource clicked by the user on the interface according to the data returned by the drill service layer.
  • Step 1 The user views the NS topology of the entire network and finds that NS1 has an alarm rendering.
  • Step 2 The NS1 node icon is displayed, and the NS1 detailed information page is displayed.
  • the alarm statistics of the node are displayed. View the topology relationship diagram of the NS-VNF node and find that the VNF1 node also has alarm rendering.
  • Step 3 Click the VNF1 node icon to enter the VNF1 detailed information page, and view the alarm statistics to find that VNF1 also sent a retreat alarm. Check the NS-VNF-VDU node relationship diagram and find that the VUD1 node also has alarm rendering.
  • Step 4 Click the VDU1 node icon to enter the detailed information page of VDU1, and view the alarm statistics to find that the VDU1 has sent a broken link alarm. Check the VNF-VDU-HOST node relationship diagram and find that the HOST1 node has alarm rendering.
  • Step 5 Click the HOST1 node icon to enter the HOST1 detailed information page, and view the alarm statistics to find that HOST1 has issued a power failure alarm. Therefore, the redirection of the NS1 can be caused by the power failure of the physical host HOST1 running the service, thereby locating the root cause of the alarm. position.
  • Step 1 The user views the NS-VNF node relationship diagram and finds that the VNF1 node has an alarm rendering.
  • Step 2 The user clicks the VNF1 node icon to enter the VNF1 detailed information page to view the alarm statistics of the node.
  • the VNF1 sends an alarm indicating that the service processing capability is degraded.
  • Step 3 Click the VDU1 node icon to enter the detailed information page of VDU1. Check the alarm statistics and find that the VDU1 sends an alarm that the CPU and memory usage are extremely high. Therefore, the service processing capability of the VNF1 can be located due to the high memory and CPU usage of one of the virtual machine VDUs running the service, thereby locating the root cause of the alarm.
  • Step 1 The user checks the alarm statistics of the HOST1 node and finds that the HOST1 node sends an alarm with a high CPU usage. View the VDU-HOST node relationship diagram and find that the VDU1 node has alarm rendering.
  • Step 2 The user clicks the VDU1 node icon to enter the detailed information page of the VDU1 node to view the alarm statistics of the node. It is found that the VDU1 also issues an alarm that the CPU is used too high. View the VNF-VDU-HOST and VNF-VDU-VNFC node relationship diagrams, and locate the VDU to support the operation of those service nodes VNF and VNFC.
  • Step 3 Click the VNFC1 and VNF1 node icons to enter the detailed information page. Check the performance statistics to analyze whether the VNFC and VNF are insufficiently allocated due to the increase in traffic. The CPU of VDU1 and HOST1 is used. Too high.
  • FIG. 10 is a structural block diagram of a drilling service layer device according to the present invention. As shown in FIG. 10, the drilling server device includes:
  • the receiving module 1000 is configured to receive a resource identifier ID of the resource node sent by the UI interface layer;
  • the obtaining module 1002 is connected to the receiving module 1000, and is configured to acquire data corresponding to the resource ID according to the resource ID;
  • the sending module 1004 is connected to the acquiring module 1002, and configured to send data corresponding to the resource ID to the UI interface layer, where the data corresponding to the resource ID includes: node topology relationship data of the resource node; and data corresponding to the resource ID.
  • the data corresponding to the resource ID includes: node topology relationship data of the resource node; and data corresponding to the resource ID.
  • the resource node may be a management object of the NFVO, such as a network service NS, a virtual network function VNF, a virtual network function component VNFC, a virtual layer virtual deployment unit, a physical layer host HOST, etc., but is not limited thereto. .
  • the foregoing node topology relationship data may include: data of a resource node, data of a parent node of the resource node, and/or data of a child node of the resource node.
  • the node topology relationship data includes: data of the parent node VDU; when the resource node is VNFC, the node topology relationship data includes: data of the parent node VDU; when the resource node is a VDU, the node topology relationship The data includes: parent node VNF data and child node VNFC The data, or the data of the parent node VNF and the data of the child node HOST; when the resource node is the VNF, the node topology relationship data includes: the data of the parent node NS and the data of the child node VDU; when the resource node is the NS, the node topology relationship data Including: data of the child node VNF; but is not limited to this.
  • the data corresponding to the resource ID may further include: alarm indication information used to indicate that the parent node and/or the child node generate an alarm.
  • alarm indication information may be identification information such as color, highlight, or blinking, but is not limited thereto.
  • the drilling service layer device may further include: a packaging module, connected to the obtaining module 1002 and the sending module 1004, configured to encapsulate data corresponding to the resource ID into a data object;
  • the data corresponding to the resource ID further includes: resource node detailed information, alarm statistics information and/or performance statistics information including content of the resource node generating an alarm; wherein the resource node detailed information includes: The keyword and keyword value of the resource node.
  • the obtaining module 1002 may be configured to obtain, from the database, the resource node detailed information corresponding to the resource ID, and the alarm statistical information and/or the performance statistical information of the content including the resource node alarm.
  • the obtaining module 1002 may be further configured to obtain resource node detailed information, alarm statistical information, and/or performance statistical information from a database by calling a data query application programming interface API.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • FIG. 11 is a schematic flowchart diagram of a data transmission method according to a preferred embodiment of the present invention. As shown in FIG.
  • Step S1102 Receive a resource identifier ID of a resource node sent by the UI interface layer.
  • Step S1104 Acquire data corresponding to the resource ID according to the resource ID.
  • Step S1106 The data corresponding to the resource ID is sent to the UI interface layer, where the data corresponding to the resource ID includes: node topology relationship data of the resource node; and the data corresponding to the resource ID, used by the UI interface layer to generate the resource node.
  • UI interface The data corresponding to the resource ID is sent to the UI interface layer, where the data corresponding to the resource ID includes: node topology relationship data of the resource node; and the data corresponding to the resource ID, used by the UI interface layer to generate the resource node.
  • the data of the clicked resource node is obtained, and the data is sent to the UI interface layer for generating a UI interface of the resource node, wherein the generated UI interface displays the node topology relationship data of the resource node, and thus
  • the parent node icon or the child node icon on the UI interface can be quickly accessed to the parent node or the child node, so that when a node generates an alarm, the UI interface can quickly locate the root cause of the alarm, which can be solved in the related art.
  • the problem of the root cause generated by the alarm cannot be quickly located, and the efficiency of the alarm location is improved.
  • the resource node may be a management object of the NFVO, such as a network service NS, a virtual network function VNF, a virtual network function component VNFC, a virtual layer virtual deployment unit, a physical layer host HOST, etc., but is not limited thereto. .
  • the foregoing node topology relationship data may include: data of a resource node, data of a parent node of the resource node, and/or data of a child node of the resource node.
  • the node topology relationship data includes: data of the parent node VDU; when the resource node is VNFC, the node topology relationship data includes: data of the parent node VDU; when the resource node is a VDU, the node topology relationship The data includes: data of the parent node VNF and data of the child node VNFC, or data of the parent node VNF and data of the child node HOST; when the resource node is the VNF, the node topology relationship data includes: data of the parent node NS and data of the child node VDU; When the resource node is an NS, the node topology relationship data includes: data of the child node VNF; but is not limited thereto.
  • the data corresponding to the resource ID further includes: alarm indication information used to indicate that the parent node and/or the child node generate an alarm; wherein the alarm indication information is used to generate a topology relationship diagram together with the node topology relationship data.
  • alarm indication information may be identification information such as color, highlight, or blinking, but is not limited thereto.
  • step S1104 and step S1106 may further include: from the database Obtaining the detailed information of the resource node corresponding to the resource ID, the alarm statistical information and/or the performance statistical information of the content including the alarm generated by the resource node; and the node topology relationship data, the resource node detailed information, the alarm statistics, and/or the performance statistics
  • the data object is encapsulated into a data object, and the data object is sent to the UI interface layer, where the resource node detailed information includes: a keyword and a keyword value of the resource node.
  • obtaining the resource node detailed information corresponding to the resource ID from the database, and the alarm statistical information and/or performance statistics information including the content of the resource node alarm may include: querying the application programming interface API from the database by calling the data query Get resource node details, alarm statistics, and/or performance statistics.
  • receiving the resource identifier ID of the resource node sent by the UI interface layer includes: receiving the resource ID by using the expressive state transition REST interface.
  • FIG. 12 is a block diagram showing a hardware structure of a mobile terminal according to a data transmission method according to an embodiment of the present invention.
  • the mobile terminal 1200 can include one or more (only one shown) processor 1202 (the processor 1202 can include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA).
  • the structure shown in FIG. 12 is merely illustrative and does not limit the structure of the above electronic device.
  • the mobile terminal 1200 may also include more or less components than those shown in FIG. 12, or have a different configuration than that shown in FIG.
  • the memory 1204 can be used to store software programs and modules of application software, such as program instructions/modules corresponding to the data transmission method in the embodiment of the present invention, and the processor 1202 executes various programs by running software programs and modules stored in the memory 1204. Functional application and data processing, that is, the above method is implemented.
  • Memory 1204 can include high speed random access memory, and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 1204 can further include memory remotely located relative to processor 1202, which can be connected to the mobile terminal via a network End 1200. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 1206 is for receiving or transmitting data via a network.
  • the network specific example described above may include a wireless network provided by a communication provider of the mobile terminal 1200.
  • transmission device 1206 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • NIC Network Interface Controller
  • the transmission device 1206 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.
  • RF Radio Frequency
  • the execution body of the above steps may be a drill service layer device or the like, but is not limited thereto.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • Embodiments of the present invention also provide a storage medium.
  • the above storage medium may be set to store program code for executing the steps in Embodiment 3.
  • the foregoing storage medium may include, but not limited to, a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), and a mobile device.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • the processor is stored according to the storage medium.
  • the program code performs the steps of the method in Embodiment 3.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the UI interface of the resource node is generated according to the data corresponding to the resource ID by the interface generation system, wherein the generated UI interface displays the node topology relationship data of the resource node, and thus
  • the parent node icon or the child node icon on the UI interface can be quickly accessed to the parent node or the child node, so that when a node generates an alarm, the UI interface can quickly locate the root cause of the alarm, which can solve the problem in the related art.
  • the problem of quickly locating the root cause of the alarm improves the efficiency of alarm location.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供了一种界面生成***、钻取服务层装置、数据发送方法；其中，该界面生成***，包括：数据库、UI界面层装置和钻取服务层装置；其中，UI界面层装置，用于将用户点击的资源节点的资源标识ID发送给钻取服务层装置，以及接收钻取服务层装置返回的与资源ID对应的数据，依据返回的与资源ID对应的数据生成资源节点的UI界面；钻取服务层装置，用于接收UI界面层装置发送的资源ID，从数据库中获取与资源ID对应的数据；以及将获取的与资源ID对应的数据发送给UI界面层装置；其中，与资源ID对应的数据包括：资源节点的节点拓扑关系数据。通过本发明，解决了相关技术中不能快速定位告警产生的根源位置的问题。

Description

界面生成***、钻取服务层装置、数据发送方法 技术领域
本发明涉及网络功能虚拟化领域，具体而言，涉及一种界面生成***、钻取服务层装置、数据发送方法。
背景技术
近年来，云计算、虚拟化技术发展迅速，带来了很多创新，同时也给运营商带来很大的压力，运营商面临寻找新的收入增长点，以抵消OTT(Over The Top)业务(OTT业务是通过互联网向用户提供各种应用服务，这种应用和目前运营商所提供的通信行业不同，它仅利用运营商的网络，而服务由运营商之外的第三方提供)带来的影响，同时为了降低运营成本(Operating Expense，简称OPEX)，通过软硬件解耦及功能抽象，使网络设备功能不再依赖于专用硬件，资源可以充分灵活共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等快速开展业务，因此需要通过网络功能虚拟化来解决这些问题。
按照欧洲电信标准化协会(European Telecommunication Standards Institute，简称ETSI)的网络虚拟化管理(Network Function Virtualiation Management&Orchestration，简称NFV-MANO)架构设计，如图1，网络功能虚拟管理(Network Functions Virtualisation Orchestrator，简称NFVO)的管理对象涉及业务层的网络服务(Network Service，简称NS)、虚拟网络功能(Virtualised Network Function，简称VNF)、虚拟网络功能组件(Virtualised Network Function Component，简称VNFC)；虚拟层的虚拟部署单元(Virtualised Deploy Unit，简称VDU)；物理层的主机(HOST)。可见，NFVO的管理范围涵盖了物理层、虚拟层、业务层，具有管理范围广、管理对象类型多的特点，这些被管对象每天产生的大量告警信息，给定位告警根源位置、分析告警影响都带来了极大的挑战。
由于在网络功能虚拟化(Network Function Virtualization，简称NFV) 领域，NFVO的被管对象(物理资源、虚拟资源、业务***)之间存在着归属或部署的关系，例如物理主机上部署着虚拟机，虚拟机上部署着VNFC，多个VDU归属于一个VNF，多个VNF又归属于一个NS。因此，物理主机产生的故障往往会影响虚拟机的运行，进而影响虚拟机上的业务***的运行，于是衍生出多条告警信息。大量的告警信息汇聚到了上层管理***NFVO上，淹没了反映根源性故障的告警，因此，如何帮助监控人员快速定位告警产生的根源位置、分析告警的影响范围成为不得不考虑和解决的课题。
对于上述技术问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种界面生成***、钻取服务层装置、数据发送方法，以至少解决相关技术中不能快速定位告警产生的根源位置的问题。
根据本发明的一个实施例，提供了一种界面生成***，包括：数据库、用户界面(User Interface，简称UI)界面层装置和钻取服务层装置；其中，UI界面层装置，设置为将用户点击的资源节点的资源标识(Identification，简称ID)发送给钻取服务层装置，以及接收钻取服务层装置返回的与资源ID对应的数据，依据返回的与资源ID对应的数据生成资源节点的UI界面；钻取服务层装置，设置为接收UI界面层装置发送的资源ID，从数据库中获取与资源ID对应的数据；以及将获取的与资源ID对应的数据发送给UI界面层装置；其中，与资源ID对应的数据包括：资源节点的节点拓扑关系数据。
在本发明实施例中，节点拓扑关系数据包括：资源节点的数据、资源节点的父节点的数据和/或资源节点的子节点的数据。
在本发明实施例中，与资源ID对应的数据还包括：用于指示父节点和/或子节点发生告警的告警指示信息。
在本发明实施例中，UI界面层装置还设置为根据节点拓扑关系数据以及告警指示信息生成资源节点的拓扑关系图，其中，UI界面包括拓扑 关系图。
在本发明实施例中，所述与所述资源ID对应的数据还包括：资源节点详细信息、包括所述资源节点发生告警的内容的告警统计信息和/或所述性能统计信息；其中，所述资源节点详细信息包括：所述资源节点的关键字和关键字值。
在本发明实施例中，钻取服务层装置还设置为将获取的与所述资源ID对应的数据封装成一个数据对象，将数据对象发送给UI界面层装置。
在本发明实施例中，钻取服务层装置还设置为通过调用数据查询应用程序编程接口(Application Programming Interface，简称API)从数据库中获取资源节点详细信息、告警统计信息和/或性能统计信息。
在本发明实施例中，UI界面层装置通过表述性状态转移(Representational State Transfer，简称REST)接口将资源ID发送给钻取服务层装置。
根据本发明的一个实施例，提供了一种钻取服务层装置，包括：接收模块，设置为接收UI界面层发送的资源节点的资源标识ID；获取模块，设置为根据资源ID获取与资源ID对应的数据；发送模块，设置为将与资源ID对应的数据发送给UI界面层，其中，与资源ID对应的数据包括：资源节点的节点拓扑关系数据；与资源ID对应的数据，用于UI界面层生成资源节点的UI界面。
在本发明实施例中，节点拓扑关系数据包括：资源节点的数据、资源节点的父节点的数据和/或资源节点的子节点的数据。
在本发明实施例中，与资源ID对应的数据还包括：用于指示父节点和/或子节点发生告警的告警指示信息。
在本发明实施例中，钻取服务层装置还包括：封装模块设置为将与所述资源ID对应的数据封装成一个数据对象；其中，所述与所述资源ID对应的数据还包括：资源节点详细信息、包括所述资源节点发生告警的内容的告警统计信息和/或性能统计信息；其中，所述资源节点详细信息包括： 所述资源节点的关键字和关键字值。
在本发明实施例中，获取模块还设置为通过调用数据查询应用程序编程接口API从数据库中获取资源节点详细信息、告警统计信息和/或性能统计信息。
在本发明实施例中，接收模块还设置为通过表述性状态转移REST接口接收资源ID。
根据本发明的一个实施例，提供了一种数据发送方法，包括：接收UI界面层发送的资源节点的资源标识ID；根据资源ID获取与资源ID对应的数据，以及将与资源ID对应的数据发送给UI界面层，其中，与资源ID对应的数据包括：资源节点的节点拓扑关系数据；与资源ID对应的数据，用于UI界面层生成资源节点的UI界面。
在本发明实施例中，节点拓扑关系数据包括：资源节点的数据、资源节点的父节点的数据和/或资源节点的子节点的数据。
在本发明实施例中，与资源ID对应的数据还包括：用于指示父节点和/或子节点发生告警的告警指示信息；其中，告警指示信息用于与节点拓扑关系数据一起生成拓扑关系图。
在本发明实施例中，根据资源ID获取与资源ID对应的数据，以及将与资源ID对应的数据发送给UI界面层还包括：从数据库中获取与资源ID对应的资源节点详细信息、包括资源节点发生告警的内容的告警统计信息和/或性能统计信息；将节点拓扑关系数据、资源节点详细信息、告警统计信息和/或性能统计信息封装成一个数据对象，将数据对象发送给UI界面层，其中，资源节点详细信息包括：资源节点的关键字和关键字值。
在本发明实施例中，从数据库中获取与资源ID对应的资源节点详细信息、包括资源节点发生告警的内容的告警统计信息和/或性能统计信息包括：通过调用数据查询应用程序编程接口API从数据库中获取资源节点详细信息、告警统计信息和/或性能统计信息。
在本发明实施例中，接收UI界面层发送的资源节点的资源标识ID包 括：通过表述性状态转移REST接口接收资源ID。
根据本发明的又一个实施例，还提供了一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行上述任一项所述的方法。
根据本发明的又一个实施例，还提供了一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述任一项所述的方法。
通过本发明，由于通过界面生成***根据与资源ID对应的数据生成了资源节点的UI界面，其中，生成的UI界面中显示了资源节点的节点拓扑关系数据，因而可以实现点击UI界面上的父节点图标或者子节点图标能够快速访问到父节点或者子节点，进而在一个节点发生告警时，通过UI界面可以快速定位到告警产生的根源位置，能够解决相关技术中不能快速定位告警产生的根源位置的问题，提高了告警定位的效率。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例提供的界面生成***的结构示意图；
图2是根据本发明优选实施例提供的分层钻取***的结构示意图；
图3是根据本发明优选实施例提供的界面生成的流程示意图；
图4是根据本发明优选实施例提供的UI界面的示意图；
图5是根据本发明优选实施例的ETSI标准中NFV-MANO架构示意图；
图6是根据本发明优选实施例提供的NFVO管理对象的节点关系图；
图7是根据本发明优选实施例提供的每一个节点对应的节点关系示意图；
图8是根据本发明优选实施例提供的从业务层往物理层进行钻取分析 的操作流程示意图；
图9是根据本发明优选实施例提供的从物理层往业务层进行钻取分析的操作流程示意图；
图10是根据本发明提供的钻取服务层装置的结构框图；
图11是根据本发明优选实施例提供的数据发送方法的流程示意图；
图12是本发明实施例的一种数据发送方法的移动终端的硬件结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本发明实施例提供了一种界面生成***，图1是根据本发明实施例提供的界面生成***的结构示意图，如图1所示，该***包括：数据库10、UI界面层装置12和钻取服务层装置14；
UI界面层装置12，用于将用户点击的资源节点的资源标识ID发送给钻取服务层装置14，以及接收钻取服务层装置14返回的与资源ID对应的数据，依据返回的与资源ID对应的数据生成资源节点的UI界面；
钻取服务层装置14，设置为接收UI界面层装置12发送的资源ID，从数据库10中获取与资源ID对应的数据；以及将获取的与资源ID对应的数据发送给UI界面层装置12；其中，与资源ID对应的数据包括：资源节点的节点拓扑关系数据。
通过上述界面生成***，UI界面层装置12根据与资源ID对应的数据生成了资源节点的UI界面，其中，生成的UI界面中显示了资源节点的 节点拓扑关系数据，因而可以实现点击UI界面上的父节点图标或者子节点图标能够快速访问到父节点或者子节点，进而在一个节点发生告警时，通过UI界面可以快速定位到告警产生的根源位置，能够解决相关技术中不能快速定位告警产生的根源位置的问题，提高了告警定位的效率。
需要说明的是，上述资源节点可以是NFVO的管理对象，比如网络服务NS，虚拟网络功能VNF，虚拟网络功能组件VNFC，虚拟层的虚拟部署单元、物理层的主机HOST等，但并不限于此。
需要说明的是，上述节点拓扑关系数据可以包括：资源节点的数据、资源节点的父节点的数据和/或资源节点的子节点的数据。比如，在资源节点为HOST时，节点拓扑关系数据包括：父节点VDU的数据；在资源节点为VNFC时，节点拓扑关系数据包括：父节点VDU的数据；在资源节点为VDU时，节点拓扑关系数据包括：父节点VNF的数据和子节点VNFC的数据，或者父节点VNF的数据和子节点HOST的数据；在资源节点为VNF时，节点拓扑关系数据包括：父节点NS的数据和子节点VDU的数据；在资源节点为NS时，节点拓扑关系数据包括：子节点VNF的数据；但并不限于此。
在本发明的一个实施例中，与资源ID对应的数据还包括：用于指示父节点和/或子节点发生告警的告警指示信息。
上述UI界面层装置12还可以设置为根据节点拓扑关系数据以及告警指示信息生成资源节点的拓扑关系图，其中，UI界面包括拓扑关系图。
需要说明的是，上述告警指示信息可以是颜色、高亮或者闪烁等标识信息，但并不限于此。
以上述告警指示信息为颜色，并且颜色为红色为例，则UI界面上显示的拓扑关系图中的资源节点、资源节点的子节点和资源节点的父节点中出现了告警的节点的图标是着了红色的，即在UI界面上显示的拓扑关系图中出现红色的节点的图标，代表该节点出现了告警，对于其他的告警指示信息类似，此处不再赘述。
需要说明的是，告警可以有很多级别，比如普通、次要、主要和严重四个级别，不同级别的告警对应的告警指示信息不同，比如严重告警可以用红色指示，主要告警用橙色指示，次要告警用黄色指示，普通告警用蓝色指示，但并不限于此。需要说明的是，如果一个节点，比如资源节点的子节点出现了两个或者两个以上级别的告警，则以最高级别的告警指示信息与节点拓扑关系数据一起生成拓扑关系图，但并不限于此。
本实施例方便用户通过UI界面的拓扑关系图中能够快速查看到带有告警指示信息的节点，即出现了告警的节点，进而能够更快地定位告警产生的根源位置。
在本发明的一个实施例中，上述与资源ID对应的数据还包括：资源节点详细信息、包括所述资源节点发生告警的内容的告警统计信息和/或所述性能统计信息；其中，所述资源节点详细信息包括：所述资源节点的关键字和关键字值。即钻取服务层装置14还可以设置为从数据库10中获取与资源ID对应的资源节点详细信息、告警统计信息和/或性能统计信息，以及将资源节点详细信息、告警统计信息和/或性能统计信息发送给UI界面层装置12。具体的，上述钻取服务层装置14还可以设置为将获取的与所述资源ID对应的数据封装成一个数据对象，将数据对象发送给UI界面层装置12。即UI界面层装置12生成的UI界面除了包括拓扑关系图之外，还可以包括告警统计信息，性能统计信息和/或资源节点详细信息，即将用户真正所关心的内容都聚焦了起来，可以很快捷的对所关心的资源节点进行一个综合分析，这种界面呈现方式不同于传统的管理***(将拓扑、资源、告警、性能分开管理，拥有各自的管理界面，用户要查看一个资源节点的拓扑关系图、告警统计信息、性能统计信息时需要切换到不同的页面去查看)，通过查看告警统计信息可以实现获得产生告警的内容，即导致告警产生的根本原因。
需要说明的是，性能统计信息为用于指示资源节点的性能的信息，比如资源节点的中央处理器(Central Processing Unit，简称CPU)使用率、内存使用率等，但并不限于此，需要说明的是，上述性能统计信息可以是 周期性采集的，上述性能统计信息在生成的UI界面中可以支持表格或者图形化呈现性能指标的一个变化趋势，可以辅助运维人员分析定位告警产生的原因。
需要说明的是，上述数据库10可以包括资源数据库、告警数据库和/或性能数据库，其中，资源数据库中存储不同资源节点的资源实例数据以及其节点关系数据；告警数据库中存储资源的告警数据；性能数据库中存储资源的性能数据。
需要说明的是，上述钻取服务层装置14还可以设置为通过调用数据查询应用程序编程接口API从数据库10中获取资源节点详细信息、告警统计信息和/或性能统计信息。UI界面层装置12通过表述性状态转移REST接口将资源ID发送给钻取服务层装置14。
需要说明的是，上述界面生成***具有普遍性，当上述界面生成***生成了资源节点的UI界面后，如果发现UI界面上显示的资源节点的拓扑关系图中该资源节点的父节点和/或子节点图标有告警标识(第一告警指示信息和/或第二告警指示信息)，如果该父节点图标被点击，则该界面生成***则会生成该父节点的UI界面，如果该子节点图标被点击，则该界面生成***会生成该子节点的UI界面，结合这种界面生成***，在一个物理层的资源节点发生告警时，可以通过向上层层钻取的操作快速访问到该物理层的资源节点产生告警所影响的范围，在一个业务节点发生告警时，可以通过向下层层钻取的操作，快速访问到该业务节点产生告警的根源位置。
为了更好地理解本发明，以下结合优选的实施例对本发明做进一步解释。
图2是根据本发明优选实施例提供的分层钻取***的结构示意图，如图2所示，该***包括：
UI界面呈现层(相当于上述UI界面层装置)：提供用户操作界面，呈现不同节点类型的节点关系图(相当于上述的拓扑关系图)、告警统计 信息、性能统计信息。
钻取服务(相当于上述钻取服务层装置)：通过资源管理、告警管理、性能管理提供的API接口查询获取相关数据，并通过REST接口将数据提供给UI界面呈现层，呈现相关的界面。
资源管理：提供资源详情数据、资源拓扑关系数据的API查询接口。
告警管理：提供资源的告警统计数据的API查询接口。
性能管理：提供性能的性能统计数据的API查询接口。
资源数据库：存储不同资源类型的资源实例数据及其节点关系数据。
告警数据库：存储资源的告警数据。
性能数据库：存储资源的性能数据。
图3是根据本发明优选实施例提供的界面生成的流程示意图，如图3所示，该流程包括：用户在节点关系图上点击父子节点图标；UI界面层将用户点击的资源的资源ID通过REST接口发到服务端的钻取服务层。钻取服务层收到请求后，通过资源管理模块提供的API接口，将UI界面层传过来的资源ID发送给资源管理，资源管理模块通过资源数据库提供的查询接口将该资源ID对应的资源详细信息、资源关联的父子节点信息查询后返回给钻取服务层。钻取服务层收到资源管理返回的资源详细信息和资源关联的父子节点信息后，继续通过告警管理模块提供的API接口，将资源ID信息发送给告警管理模块，告警管理模块通过告警数据库提供的查询接口将该资源ID对应的告警统计信息查询后返回给钻取服务层。钻取服务层收到告警管理返回的告警统计信息后，继续通过性能管理模块提供的API接口，将资源ID信息发送给性能管理模块，性能管理模块通过性能数据库提供的查询接口将该资源ID对应的性能统计信息查询后返回给钻取服务层。钻取服务层将查询到该资源ID对应的资源详情信息、父子节点信息、告警统计信息、性能统计信息汇总成一个数据对象返回给UI界面层。UI界面层收到钻取服务层返回的数据后，生成图4所示的界面，给用户集中呈现用户所选择资源的资源详情、资源父子节点关系图、 资源的告警统计信息、资源的性能统计信息。
本发明优选实施例按照ETSI的NFV-MANO架构设计，物理层、虚拟层的资源及其告警、性能数据是通过VIM(Virtualized Infrastructure Manager)管理***来收集，并通过Nfvo-Vi接口上报给NFVO，如图5所示。业务层的资源及其告警、性能数据是通过虚拟网络功能管理器(VNF Manager，简称VNFM)管理***来收集，并通过Nfvo-Vnfm接口上报给NFVO，如图5所示。在NFV领域，所有物理层、虚拟层、业务层的资源、告警、性能数据都汇聚在了NFVO管理***中，由NFVO***进行统一的管理和编排。本发明优选实施例在NFVO***中对这些物理层、虚拟层、业务层的资源进行建模时遵循了Tosca-NFV(Topology and Orchestration Specification for Cloud Applications)规范，将这些资源类型映射成为了Tosca-NFV规范所定义的节点类型，例如：NS/VNF/VNFC/VDU等。同时遵循Tosca-NFV规范里所定义的节点关系类型来描述了NFV领域内节点类型之间的部署关系、归属关系等。按照Tosca-NFV规范，我们可以将全网的资源节点建立起一张逻辑拓扑关系图，如图6所示。
利用这张全网的逻辑拓扑关系图，本发明将任意一个资源节点和它直接关联的父子节点放在同一个拓扑关系图中，如图7所示。用户通过界面点击父节点图标或子节点图标，可快速访问到与当前资源节点相关联的父子资源节点。并且界面会呈现新节点的资源详细信息，以及新节点与它直接关联的父子节点的拓扑关系图。利用该特性，用户可以从一个物理节点出发，通过向上层层钻取的操作，快速访问到该物理节点上所部署的虚拟层的虚拟资源节点，以及业务层运行的业务节点。也可以从一个业务节点出发，通过向下层层钻取的操作，快速访问到该业务节点是部署在虚拟层的哪一个虚拟资源节点上，以及虚拟节点又是部署在物理层的哪一个物理资源节点上的，从而用户可实现在物理层、虚拟层、业务层资源节点之间的层层钻取的功能。
同时本发明结合告警渲染功能，当资源节点出现告警时，会在该资源节点的图标上进行告警渲染，对出现告警的资源图标进行着色。如果底层 物理主机产生了告警，并导致该主机上运行的虚拟机也产生了告警，同时虚拟机的告警又影响了它上面所运行的业务，从而产生了业务告警。那么会同时在对应的HOST、VDU和VNF资源节点上进行告警渲染。以图7举例，假如是HOST1/VDU1/VNF1这三个资源节点出现了告警，那么这三个资源节点会同时进行告警渲染，当用户发现VNF1资源节点产生了业务告警时(图7③)，通过查看该节点的父子节点拓扑关系图，利用告警渲染的特性，可以一眼看出VDU1资源节点也出现了告警，并通过点击VDU1节点图标快速访问到VDU1资源节点(图7④)。同样通过查看VDU1资源节点的父子节点拓扑关系图，利用告警渲染的特性可发现HOST1资源节点也出现了告警，从而继续点击HOST1资源节点图标，可进入到HOST1的详细信息页面，从而定位VNF1业务告警的根源位置就是HOST1。这样就完成了一次从业务层到虚拟层再到物理层的跨层关联分析，从而定位了产生业务告警的根源位置的过程。
同样，当一个物理节点产生告警时，也能从该节点出发，通过向上层层钻取的方式，快速定位物理层/虚拟层产生的告警它所影响的业务范围。
本发明优选实施例提供了业务层、虚拟层、物理层三个视角来监控全网业务***、虚拟资源、物理资源的运行状态。其中业务层视角用来监控网络服务NS、虚拟网络功能VNF的运行。虚拟层视角用来监控虚拟部署单元(即虚拟机)VDU的运行。物理层视角用来监控物理主机HOST的运行。
在业务层监控中，提供了全网的NS、以及独立VNF的拓扑概览图(如图7①)。通过点击NS拓扑节点可进入NS的详细信息页面，查看NS的基本信息描述、告警统计信息和性能指标统计信息，同时呈现NS-VNF的节点归属关系图。由于NS的告警信息是根据VNF的告警衍生出来的，因此当VNF产生告警时，会在VNF拓扑节点以及它归属的NS节点上同时渲染告警，用户通过查看NS-VNF的节点归属关系图便可快速定位导致NS产生告警的VNF节点。
通过点击VNF拓扑节点可进入VNF的详细信息页面，查看VNF的基本信息描述、告警统计信息和性能指标统计信息，同时呈现NS-VNF-VDU的节点归属关系图。同样用户通过查看NS-VNF-VDU节点归属关系图中可快速定位导致VNF产生告警的VDU节点。
通过点击VDU拓扑节点可进入到VDU的详细信息页面，查看VDU的基本信息描述、告警统计信息和性能指标统计信息，同时呈现VNF-VDU-VNFC和VNF-VDU-HOST的节点归属/部署关系图。其中VNF-VDU-VNFC节点关系图描述了该VDU上部署了哪些VNFC，VNF-VDU-HOST节点关系图描述了该VDU部署在那台HOST上。
从VNF-VDU-VNFC节点关系图中点击VNFC节点可进入到VNFC的详细信息页面，查看VNFC的基本信息描述、告警统计信息和性能指标统计信息，以及VDU-VNFC的节点部署关系图。
从VNF-VDU-HOST节点关系图中点击HOST节点可进入HOST的详细信息页面，查看HOST的基本信息描述、告警统计信息和性能指标统计信息，以及VDU-HOST的节点部署关系图。
通过这种层层钻取的方式，用户可依托这些被管节点的归属、部署关系，快速的访问到与它直接相关联的节点，每一个节点的页面都包含了该节点的基本信息、告警统计信息和性能指标统计信息，用户可以快速分析出该节点的运行状态是否正常，是否是产生业务告警的根源位置。
同时，由于每个节点的拓扑图都包含它的归属、部署关联节点，因此这种钻取方式也可以是至下往上的方式。例如在物理层监控中，发现某个物理主机最近频繁产生CPU使用率高的告警，虽然这类告警不一定立即影响业务***的运行，但也需要分析其产生的原因。用户发现此类告警后可通过向上钻取，查看该物理主机上运行着哪些虚拟机，这些虚拟机上运行着哪些业务***，从而得知这条物理主机的告警可能会影响到哪些业务***的运行，同时也可以分析这些业务***是否是由于业务量的增加而导致物理主机产生CPU使用率高的告警，进而为是否需要扩容或做水平负 载均衡做决策依据。
本发明优选实施例以资源为中心，将一个资源的资源详情、告警统计信息、性能统计信息集中到了一个页面上，同时还呈现了该资源节点与它直接关联的父子节点的拓扑关系图，如图4所示。将用户真正所关心的内容都聚焦了起来，可以很快捷的对所关心的资源节点进行一个综合分析。这种界面呈现方式不同于传统的管理***，传统管理***是将拓扑、资源、告警、性能分开管理，拥有各自的管理界面，用户要查看一个资源的拓扑关系图、告警统计信息、性能统计信息时需要切换到不同的页面去查看，并且每个页面都要做一次查询操作才能过滤出该资源的相关信息。本发明在***的服务端抽取出了钻取服务层，为界面所进行的层层钻取操作提供数据支撑服务。前端界面UI只跟钻取服务层进行交互，当用户点击任意一个资源图标时，将该资源的资源ID通过REST接口发送给钻取服务层。钻取服务层收到请求后以资源ID作为参数，分别调用资源管理、告警管理、性能管理的数据查询API接口，获取到该资源的资源数据、拓扑关系数据、告警数据和性能数据信息，将这四种数据封装在一个数据对象中返回给UI界面，最终UI界面层按图4所示生成对应的界面，并将钻取服务层返回的数据填入界面中。
需要说明的是，基于上述***，可以实现对资源节点的告警根源进行分析，分析方法包括：确定虚拟网络中的资源节点产生告警；根据所述虚拟网络中各资源节点之间的拓扑关系、各资源节点的告警渲染特性(相当于上述第一告警指示信息和/或第二告警指示信息)，确定所述资源节点产生所述告警的根源位置；其中，所述告警渲染特性为对在所述拓扑关系中与出现告警的资源节点对应的资源节点标识进行了着色。
需要说明的是，根据所述虚拟网络中各资源节点之间的拓扑关系和各资源节点的告警渲染特性，确定所述资源节点产生所述告警的根源位置包括：根据所述拓扑关系和所述告警渲染特性，采用向上层层钻取或者向下层层钻取的方式，确定所述资源节点产生所述告警的根源位置；其中，所述向上层层钻取为以所述资源节点为起点，向所述资源节点的父节点的方 向层层钻取；所述向下层层钻取为以所述资源节点为起点，向所述资源节点的子节点的方向层层钻取。
进一步，在采用向上层层钻取的方式确定所述资源节点产生所述告警的根源位置包括：在所述资源节点的父节点不是虚拟服务NS时，以所述资源节点为起始节点，循环执行以下步骤直到满足终止条件：确定所述起始节点是否出现了告警；在确定所述起始节点出现了告警的情况下，获取所述起始节点与所述起始节点的父节点之间的拓扑关系；根据所述起始节点与所述起始节点的父节点之间的拓扑关系确定所述起始节点的父节点是否出现了告警渲染；在所述起始节点的父节点出现了告警渲染的情况下，将所述起始节点的父节点作为所述起始节点；其中，所述终止条件为所述起始节点出现了告警且所述起始节点的父节点未出现告警；确定所述资源节点产生所述告警的根源位置为循环结束后得到的起始节点。
优选地，在获取所述起始节点与所述起始节点的父节点之间的拓扑关系之后，所述方法还包括：显示所述起始节点与所述起始节点的父节点之间的拓扑关系。
优选地，在所述起始节点为物理层主机HOST的情况下，所述起始节点与所述起始节点的父节点之间的拓扑关系为虚拟层的虚拟部署单元VDU与HOST之间的拓扑关系；在所述起始节点为VDU的情况下，所述起始节点与所述起始节点的父节点之间的拓扑关系为VNF、VDU与HOST之间的拓扑关系或者VNF、VDU与VNFC之间的拓扑关系；在所述起始节点为VNFC的情况下，所述起始节点与所述起始节点的父节点之间的拓扑关系为VDU与VNFC之间的拓扑关系；在所述起始节点为VNF的情况下，所述起始节点与所述起始节点的父节点之间的拓扑关系为NS、VNF与VDU之间的拓扑关系。
优选地，在采用向上层层钻取的方式确定所述资源节点产生所述告警的根源位置包括：在所述资源节点的父节点为NS时，获取所述资源节点与所述父节点之间的拓扑关系；根据所述资源节点与所述父节点之间的拓 扑关系确定所述父节点是否出现了告警渲染；在确定所述父节点出现了告警渲染的情况下，确定所述资源节点产生所述告警的根源位置为所述NS。
优选地，在采用向下层层钻取的方式确定所述资源节点产生所述告警的根源位置包括：在所述资源节点的子节点不是虚拟网络功能组件VNFC或物理层的主机HOST时，以所述资源节点为起始节点，循环执行以下步骤直到满足终止条件：确定所述起始节点是否出现了告警；在确定所述起始节点出现了告警的情况下，获取所述起始节点与所述起始节点的子节点之间的拓扑关系；根据所述起始节点与所述起始节点的子节点之间的拓扑关系确定所述起始节点的子节点是否出现了告警渲染；在所述起始节点的子节点出现了告警渲染的情况下，将所述起始节点的子节点作为所述起始节点；其中，所述终止条件为所述起始节点出现了告警渲染且所述起始节点的子节点未出现告警渲染；确定所述资源节点产生所述告警的根源位置为循环结束后得到的起始节点。
优选地，在获取所述起始节点与所述起始节点的子节点之间的拓扑关系之后，所述方法还包括：显示所述起始节点与所述起始节点的子节点之间的拓扑关系。
优选地，在所述起始节点为NS时，所述起始节点与所述起始节点的子节点之间的拓扑关系为NS与VNF之间的拓扑关系；在所述起始节点为VNF时，所述起始节点与所述起始节点的子节点之间的拓扑关系为NS、VNF与VDU之间的拓扑关系；在所述起始节点为VDU时，所述起始节点与所述起始节点的子节点之间的拓扑关系为VNF、VDU与VNFC之间的拓扑关系或VNF、VDU与HOST之间的拓扑关系。
优选地，在采用向上层层钻取的方式确定所述资源节点产生所述告警的根源位置包括：在所述资源节点的子节点为VNFC或HOST时，获取所述资源节点与所述子节点之间的拓扑关系；根据所述资源节点与所述子节点之间的拓扑关系确定所述子节点是否出现了告警渲染；在确定所述子节点出现了告警渲染的情况下，确定所述资源节点产生所述告警的根源位置 为所述VNFC或所述HOST。
优选地，在确定所述资源节点产生所述告警的根源位置之后，所述方法还包括：获取所述根源位置的告警统计信息；根据所述告警统计信息确定所述资源节点产生告警的根源。
基于该***实现的分析方法可以通过具体的分析工具实现，也可以通过人工实现，以下结合优选的实施例进行说明：
需要说明的是，图6是根据本发明优选实施例提供的NFVO管理对象的节点关系图，如图6所示，VDU与VNF是多对一的归属关系，VNF与NS也是多对一的归属关系；VNFC与VDU是一对一的部署关系，VDU与HOST是多对一的部署关系。
图8为从业务层往物理层进行钻取分析的操作流程，如图8所示，该方法包括：
步骤801，查看全网网络服务业务拓扑图，如果发现某个NS产生了告警则进入步骤802。
步骤802查看指定NS的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及NS-VNF的节点关系图。
步骤803钻取到VNF节点。
步骤804查看指定VNF的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及NS-VNF-VDU的节点关系图。
步骤805钻取到VDU节点。
步骤806查看指定VDU的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及VNF-VDU-VNFC和VNF-VDU-HOST的节点关系图。
步骤807钻取到VNFC节点。
步骤808查看指定VNFC的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及VDU-VNFC的节点关系图。
步骤809钻取到HOST节点。
步骤810查看指定HOST的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及VDU-HOST的节点关系图。
图9为从物理层往业务层进行钻取分析的操作流程，如图9所示，该流程包括：
步骤901查看全网物理主机或单板拓扑图，如果发现某个物理主机或单板产生了告警则进入步骤902。
步骤902查看指定物理主机或单板的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及VDU-HOST的节点关系图。
步骤903钻取到VDU节点。
步骤904查看指定VDU的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及VNF-VDU-VNFC和VNF-VDU-HOST的节点关系图。
步骤905钻取到VNFC节点。
步骤906查看指定VNFC的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及VDU-VNFC的节点关系图。
步骤907钻取到VNF节点。
步骤908查看指定VNF的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及NS-VNF-VDU的节点关系图。
步骤909钻取到NS节点。
步骤910查看指定NS的详细信息，包括其基本信息、告警统计信息、性能指标统计信息，以及NS-VNF的节点关系图。
图3为钻取操作的服务端处理流程，该流程包括：
步骤301，用户点击任意一个父子资源节点。
步骤302，UI界面呈现层将用户点击的资源ID发送给钻取服务层。
步骤303，钻取服务层调用资源管理模块提供的API查询接口，根据资源ID从资源数据库中查找出该资源的详细信息以及该资源直接关联的父子节点信息。
步骤304，钻取服务层调用告警管理模块提供的API查询接口，根据资源ID从告警数据库中查找出该资源对应的告警统计信息。
步骤305，钻取服务层调用性能管理模块提供的API查询接口，根据资源ID从性能数据库中查找出该资源对应的性能统计信息。
步骤306，钻取服务层将该资源的详细信息、与其关联的父子节点信息、告警统计信息、性能统计信息返回给UI界面呈现层。
步骤307，UI界面呈现层根据钻取服务层返回的数据在界面上呈现用户所点击资源的资源详情、拓扑关系图、告警统计信息、性能统计信息。
优选实施例1
用户发现NS发出退服告警，定位告警根源位置的流程，如图8、图7。
步骤1：用户查看全网NS拓扑图，发现NS1出现了告警渲染。
步骤2：用户点击NS1节点图标，进入NS1的详细信息页面，查看该节点的告警统计信息，发现NS1发出了退服告警。查看NS-VNF节点拓扑关系图，发现VNF1节点也出现了告警渲染。
步骤3：点击VNF1节点图标进入VNF1的详细信息页面，查看告警统计信息发现VNF1也发出了退服告警。查看NS-VNF-VDU节点关系图，发现VUD1节点也出现了告警渲染。
步骤4：点击VDU1节点图标进入VDU1的详细信息页面，查看告警统计信息发现VDU1发出了断链告警。查看VNF-VDU-HOST节点关系图，发现HOST1节点出现了告警渲染。
步骤5：点击HOST1节点图标进入HOST1的详细信息页面，查看告警统计信息发现HOST1发出了掉电告警。从而可定位NS1的退服是由于运行该服务的物理主机HOST1发生了掉电所引起，从而定位告警的根源 位置。
优选实施例2：
用户发现VNF发出业务处理能力下降告警，定位告警根源位置的流程，如图8、图7。
步骤1：用户查看NS-VNF节点关系图，发现VNF1节点出现了告警渲染
步骤2：用户点击VNF1节点图标，进入VNF1的详细信息页面，查看该节点的告警统计信息，发现VNF1发出了业务处理能力下降的告警。查看NS-VNF-VDU节点关系图，发现VUD1节点也出现了告警渲染。
步骤3：点击VDU1节点图标进入VDU1的详细信息页面，查看告警统计信息发现VDU1发出了CPU、内存使用率超高的告警。从而可定位VNF1的业务处理能力下降是因为运行该业务的其中一个虚拟机VDU的内存、CPU使用率超高所引起，从而定位告警的根源位置。
优选实施例3：
用户发现HOST发出CPU使用率超高的告警，定位该告警对上层业务影响范围的流程，如图9、图7。
步骤1：用户查看HOST1节点告警统计信息，发现HOST1节点发出了CPU使用率超高的告警，查看VDU-HOST节点关系图，发现VDU1节点出现了告警渲染。
步骤2：用户点击VDU1节点图标，进入VDU1节点的详细信息页面，查看该节点的告警统计信息，发现VDU1也发出了CPU使用超高的告警。查看VNF-VDU-HOST、VNF-VDU-VNFC节点关系图，可定位该VDU支撑着那些业务节点VNF、VNFC的运行。
步骤3：点击VNFC1、VNF1节点图标进入其详细信息页面，查看性能统计信息可分析该VNFC、VNF是否是由于业务量增加导致运行该业务的虚拟机资源分配不足，从而导致VDU1、HOST1的CPU使用过高。
至此便可定位HOST1产生的告警对上层业务影响的范围，从而可帮助用户决策是不是需要进行扩容或做负载均衡操作，提前规避发生业务告警。
实施例2
本发明实施例还提供了一种钻取服务层装置，图10是根据本发明提供的钻取服务层装置的结构框图，如图10所示，该钻取服务器装置包括：
接收模块1000，设置为接收UI界面层发送的资源节点的资源标识ID；
获取模块1002，与上述接收模块1000连接，设置为根据资源ID获取与资源ID对应的数据；
发送模块1004，与上述获取模块1002连接，设置为将与资源ID对应的数据发送给UI界面层，其中，与资源ID对应的数据包括：资源节点的节点拓扑关系数据；与资源ID对应的数据，设置为UI界面层生成资源节点的UI界面。
通过上述钻取服务层装置，获取被点击的资源节点的数据，并将该数据发送给UI界面层，设置为生成资源节点的UI界面，其中，生成的UI界面中显示了资源节点的节点拓扑关系数据，因而可以实现点击UI界面上的父节点图标或者子节点图标能够快速访问到父节点或者子节点，进而在一个节点发生告警时，通过UI界面可以快速定位到告警产生的根源位置，能够解决相关技术中不能快速定位告警产生的根源位置的问题，提高了告警定位的效率。
需要说明的是，上述资源节点可以是NFVO的管理对象，比如网络服务NS，虚拟网络功能VNF，虚拟网络功能组件VNFC，虚拟层的虚拟部署单元、物理层的主机HOST等，但并不限于此。
需要说明的是，上述节点拓扑关系数据可以包括：资源节点的数据、资源节点的父节点的数据和/或资源节点的子节点的数据。比如，在资源节点为HOST时，节点拓扑关系数据包括：父节点VDU的数据；在资源节点为VNFC时，节点拓扑关系数据包括：父节点VDU的数据；在资源节点为VDU时，节点拓扑关系数据包括：父节点VNF的数据和子节点VNFC 的数据，或者父节点VNF的数据和子节点HOST的数据；在资源节点为VNF时，节点拓扑关系数据包括：父节点NS的数据和子节点VDU的数据；在资源节点为NS时，节点拓扑关系数据包括：子节点VNF的数据；但并不限于此。
在本发明的一个实施例中，与资源ID对应的数据还可以包括：用于指示父节点和/或子节点发生告警的告警指示信息。需要说明的是，上述告警指示信息可以是颜色、高亮或者闪烁等标识信息，但并不限于此。
在本发明的一个实施例中，上述钻取服务层装置还可以包括：封装模块，与上述获取模块1002和发送模块1004连接，设置为将与所述资源ID对应的数据封装成一个数据对象；其中，所述与所述资源ID对应的数据还包括：资源节点详细信息、包括所述资源节点发生告警的内容的告警统计信息和/或性能统计信息；其中，所述资源节点详细信息包括：所述资源节点的关键字和关键字值。即上述获取模块1002还可以设置为从数据库中获取与资源ID对应的资源节点详细信息、包括资源节点发生告警的内容的告警统计信息和/或性能统计信息。
在本发明的一个实施例中，上述获取模块1002还可以设置为通过调用数据查询应用程序编程接口API从数据库中获取资源节点详细信息、告警统计信息和/或性能统计信息。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
根据本发明的一个实施例，提供了一种数据发送方法，图11是根据本发明优选实施例提供的数据发送方法的流程示意图，如图11所示，该方法包括：
步骤S1102，接收UI界面层发送的资源节点的资源标识ID；
步骤S1104，根据资源ID获取与资源ID对应的数据；
步骤S1106，将与资源ID对应的数据发送给UI界面层，其中，与资源ID对应的数据包括：资源节点的节点拓扑关系数据；与资源ID对应的数据，用于UI界面层生成资源节点的UI界面。
通过上述步骤，获取被点击的资源节点的数据，并将该数据发送给UI界面层，用于生成资源节点的UI界面，其中，生成的UI界面中显示了资源节点的节点拓扑关系数据，因而可以实现点击UI界面上的父节点图标或者子节点图标能够快速访问到父节点或者子节点，进而在一个节点发生告警时，通过UI界面可以快速定位到告警产生的根源位置，能够解决相关技术中不能快速定位告警产生的根源位置的问题，提高了告警定位的效率。
需要说明的是，上述资源节点可以是NFVO的管理对象，比如网络服务NS，虚拟网络功能VNF，虚拟网络功能组件VNFC，虚拟层的虚拟部署单元、物理层的主机HOST等，但并不限于此。
需要说明的是，上述节点拓扑关系数据可以包括：资源节点的数据、资源节点的父节点的数据和/或资源节点的子节点的数据。比如，在资源节点为HOST时，节点拓扑关系数据包括：父节点VDU的数据；在资源节点为VNFC时，节点拓扑关系数据包括：父节点VDU的数据；在资源节点为VDU时，节点拓扑关系数据包括：父节点VNF的数据和子节点VNFC的数据，或者父节点VNF的数据和子节点HOST的数据；在资源节点为VNF时，节点拓扑关系数据包括：父节点NS的数据和子节点VDU的数据；在资源节点为NS时，节点拓扑关系数据包括：子节点VNF的数据；但并不限于此。
在本发明实施例中，与资源ID对应的数据还包括：用于指示父节点和/或子节点发生告警的告警指示信息；其中，告警指示信息用于与节点拓扑关系数据一起生成拓扑关系图。需要说明的是，上述告警指示信息可以是颜色、高亮或者闪烁等标识信息，但并不限于此。
需要说明的是，上述步骤S1104和步骤S1106还可以包括：从数据库 中获取与资源ID对应的资源节点详细信息、包括资源节点发生告警的内容的告警统计信息和/或性能统计信息；将节点拓扑关系数据、资源节点详细信息、告警统计信息和/或性能统计信息封装成一个数据对象，将数据对象发送给UI界面层，其中，资源节点详细信息包括：资源节点的关键字和关键字值。
需要说明的是，从数据库中获取与资源ID对应的资源节点详细信息、包括资源节点发生告警的内容的告警统计信息和/或性能统计信息可以包括：通过调用数据查询应用程序编程接口API从数据库中获取资源节点详细信息、告警统计信息和/或性能统计信息。
需要说明的是，接收UI界面层发送的资源节点的资源标识ID包括：通过表述性状态转移REST接口接收资源ID。
需要说明的是，本申请实施例3所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例，图12是本发明实施例的一种数据发送方法的移动终端的硬件结构框图。如图12所示，移动终端1200可以包括一个或多个(图中仅示出一个)处理器1202(处理器1202可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、用于存储数据的存储器1204、以及用于通信功能的传输装置1206。本领域普通技术人员可以理解，图12所示的结构仅为示意，其并不对上述电子装置的结构造成限定。例如，移动终端1200还可包括比图12中所示更多或者更少的组件，或者具有与图12所示不同的配置。
存储器1204可用于存储应用软件的软件程序以及模块，如本发明实施例中的数据发送方法对应的程序指令/模块，处理器1202通过运行存储在存储器1204内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器1204可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器1204可进一步包括相对于处理器1202远程设置的存储器，这些远程存储器可以通过网络连接至移动终 端1200。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置1206用于经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端1200的通信供应商提供的无线网络。在一个实例中，传输装置1206包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置1206可以为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通讯。
在本发明实施例中，上述步骤的执行主体可以为钻取服务层装置等，但不限于此。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例4
本发明的实施例还提供了一种存储介质。在本发明实施例中，在本实施例中，上述存储介质可以被设置为存储用于执行实施例3中的步骤的程序代码。
在本发明实施例中，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
在本发明实施例中，在本实施例中，处理器根据存储介质中已存储的 程序代码执行实施例3中的方法的步骤。
在本发明实施例中，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，由于通过界面生成***根据与资源ID对应的数据生成了资源节点的UI界面，其中，生成的UI界面中显示了资源节点的节点拓扑关系数据，因而可以实现点击UI界面上的父节点图标或者子节点图标能够快速访问到父节点或者子节点，进而在一个节点发生告警时，通过UI界面可以快速定位到告警产生的根源位置，能够解决相关技术中不能快速定位告警产生的根源位置的问题，提高了告警定位的效率。

Claims (22)

  1. 一种界面生成***，包括：数据库、UI界面层装置和钻取服务层装置；其中，
    所述UI界面层装置，设置为将用户点击的资源节点的资源标识ID发送给钻取服务层装置，以及接收所述钻取服务层装置返回的与所述资源ID对应的数据，依据返回的与所述资源ID对应的数据生成所述资源节点的UI界面；
    所述钻取服务层装置，设置为接收所述UI界面层装置发送的所述资源ID，从所述数据库中获取与所述资源ID对应的数据；以及将获取的与所述资源ID对应的数据发送给所述UI界面层装置；其中，与所述资源ID对应的数据包括：所述资源节点的节点拓扑关系数据。
  2. 根据权利要求1所述的***，其中，所述节点拓扑关系数据包括：所述资源节点的数据、所述资源节点的父节点的数据和/或所述资源节点的子节点的数据。
  3. 根据权利要求2所述的***，其中，所述与所述资源ID对应的数据还包括：用于指示所述父节点和/或子节点发生告警的告警指示信息。
  4. 根据权利要求3所述的***，其中，所述UI界面层装置还设置为根据所述节点拓扑关系数据以及所述告警指示信息生成所述资源节点的拓扑关系图，其中，所述UI界面包括所述拓扑关系图。
  5. 根据权利要求1所述的***，其中，所述与所述资源ID对应的数据还包括：资源节点详细信息、包括所述资源节点发生告警的内容的告警统计信息和/或性能统计信息；其中，所述资源节点详细信息包括：所述资源节点的关键字和关键字值。
  6. 根据权利要求1至5中任一项所述的***，其中，所述钻取 服务层装置还设置为将获取的与所述资源ID对应的数据封装成一个数据对象，将所述数据对象发送给所述UI界面层装置。
  7. 根据权利要求5所述的***，其中，所述钻取服务层装置还设置为通过调用数据查询应用程序编程接口API从所述数据库中获取所述资源节点详细信息、所述告警统计信息和/或所述性能统计信息。
  8. 根据权利要求1所述的***，其中，所述UI界面层装置通过表述性状态转移REST接口将所述资源ID发送给所述钻取服务层装置。
  9. 一种钻取服务层装置，包括：
    接收模块，设置为接收UI界面层发送的资源节点的资源标识ID；
    获取模块，设置为根据所述资源ID获取与所述资源ID对应的数据；
    发送模块，设置为将所述与所述资源ID对应的数据发送给所述UI界面层，其中，所述与所述资源ID对应的数据包括：所述资源节点的节点拓扑关系数据；所述与所述资源ID对应的数据，用于所述UI界面层生成所述资源节点的UI界面。
  10. 根据权利要求9所述的钻取服务层装置，其中，所述节点拓扑关系数据包括：所述资源节点的数据、所述资源节点的父节点的数据和/或所述资源节点的子节点的数据。
  11. 根据权利要求10所述的钻取服务层装置，其中，所述与所述资源ID对应的数据还包括：用于指示所述父节点和/或子节点发生告警的告警指示信息。
  12. 根据权利要求9所述的钻取服务层装置，其中，所述钻取服 务层装置还包括：封装模块，设置为将与所述资源ID对应的数据封装成一个数据对象；其中，所述与所述资源ID对应的数据还包括：资源节点详细信息、包括所述资源节点发生告警的内容的告警统计信息和/或性能统计信息；其中，所述资源节点详细信息包括：所述资源节点的关键字和关键字值。
  13. 根据权利要求12所述的钻取服务层装置，其中，所述获取模块还设置为通过调用数据查询应用程序编程接口API从数据库中获取所述资源节点详细信息、所述告警统计信息和/或所述性能统计信息。
  14. 根据权利要求9所述的钻取服务层装置，其中，所述接收模块还设置为通过表述性状态转移REST接口接收所述资源ID。
  15. 一种数据发送方法，包括：
    接收UI界面层发送的资源节点的资源标识ID；
    根据所述资源ID获取与所述资源ID对应的数据，以及将所述与所述资源ID对应的数据发送给所述UI界面层，其中，所述与所述资源ID对应的数据包括：所述资源节点的节点拓扑关系数据；所述与所述资源ID对应的数据，用于所述UI界面层生成所述资源节点的UI界面。
  16. 根据权利要求15所述的方法，其中，所述节点拓扑关系数据包括：所述资源节点的数据、所述资源节点的父节点的数据和/或所述资源节点的子节点的数据。
  17. 根据权利要求16所述的方法，其中，所述与所述资源ID对应的数据还包括：用于指示所述父节点和/或所述子节点发生告警的告警指示信息；其中，所述告警指示信息用于与所述节点拓扑关系数据 一起生成拓扑关系图。
  18. 根据权利要求15所述的方法，其中，根据所述资源ID获取与所述资源ID对应的数据，以及将所述与所述资源ID对应的数据发送给所述UI界面层还包括：
    从数据库中获取与所述资源ID对应的资源节点详细信息、包括所述资源节点发生告警的内容的告警统计信息和/或性能统计信息；
    将所述节点拓扑关系数据、所述资源节点详细信息、所述告警统计信息和/或所述性能统计信息封装成一个数据对象，将所述数据对象发送给所述UI界面层，其中，所述资源节点详细信息包括：所述资源节点的关键字和关键字值。
  19. 根据权利要求18所述的方法，其中，从所述数据库中获取与所述资源ID对应的资源节点详细信息、包括所述资源节点发生告警的内容的告警统计信息和/或性能统计信息包括：
    通过调用数据查询应用程序编程接口API从所述数据库中获取所述资源节点详细信息、所述告警统计信息和/或所述性能统计信息。
  20. 根据权利要求15所述的方法，其中，接收UI界面层发送的资源节点的资源标识ID包括：通过表述性状态转移REST接口接收所述资源ID。
  21. 一种存储介质，其特征在于，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求15至20中任一项所述的方法。
  22. 一种处理器，其特征在于，所述处理器用于运行程序，其中，所述程序运行时执行权利要求15至20中任一项所述的方法。
PCT/CN2017/099678 2016-09-06 2017-08-30 界面生成***、钻取服务层装置、数据发送方法 WO2018045901A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610806378.XA CN107800556B (zh) 2016-09-06 2016-09-06 界面生成***、钻取服务层装置、数据发送方法
CN201610806378.X 2016-09-06

Publications (1)

Publication Number Publication Date
WO2018045901A1 true WO2018045901A1 (zh) 2018-03-15

Family

ID=61530948

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/099678 WO2018045901A1 (zh) 2016-09-06 2017-08-30 界面生成***、钻取服务层装置、数据发送方法

Country Status (2)

Country Link
CN (1) CN107800556B (zh)
WO (1) WO2018045901A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111191937A (zh) * 2019-12-31 2020-05-22 深圳市计通智能技术有限公司 一种告警危害评估方法、***及终端设备
EP3761563A4 (en) * 2018-03-30 2021-07-07 Samsung Electronics Co., Ltd. DEVICE AND METHOD FOR MANAGING NETWORK RESOURCES IN A NETWORK FUNCTION VIRTUALIZATION ENVIRONMENT
CN113643757A (zh) * 2020-12-02 2021-11-12 广东美格基因科技有限公司 一种微生物组学数据交互分析***

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109446291B (zh) * 2018-10-23 2022-05-13 山东中创软件商用中间件股份有限公司 一种路网状态统计方法、装置和计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101854343A (zh) * 2009-04-01 2010-10-06 华为终端有限公司 提供节点信息的方法、获取节点信息的方法及设备
CN102394778A (zh) * 2011-11-04 2012-03-28 中兴通讯股份有限公司 网络拓扑的显示方法及装置
CN102571417A (zh) * 2011-12-15 2012-07-11 江苏亿通高科技股份有限公司 动态拓扑的实现方法
CN105207793A (zh) * 2014-05-30 2015-12-30 亿阳信通股份有限公司 一种树状拓扑结构中节点信息的获取方法和***

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202670B (zh) * 2007-12-21 2011-04-06 中兴通讯股份有限公司 一种网络管理拓扑的处理方法及***
JP5941703B2 (ja) * 2012-02-27 2016-06-29 株式会社日立製作所 管理サーバ及び管理方法
CN103595550A (zh) * 2012-08-16 2014-02-19 上海未来宽带技术股份有限公司 一种eoc设备网络拓扑显示方法
CN102932201B (zh) * 2012-09-26 2016-08-03 迈普通信技术股份有限公司 一种网络监控数据的显示控制***和方法
CN103873288B (zh) * 2012-12-18 2017-10-13 中国电信股份有限公司 基于告警信息对通信网络设备故障进行定位的***和方法
CN103634147A (zh) * 2013-11-28 2014-03-12 华为技术服务有限公司 一种网络拓扑管理方法及设备
CN104243236B (zh) * 2014-09-17 2017-10-03 深圳供电局有限公司 一种监控***运维告警数据分析的方法、***及服务器
CN104410538A (zh) * 2014-12-22 2015-03-11 上海斐讯数据通信技术有限公司 一种网络拓扑结构管理方法及***
CN105847025A (zh) * 2015-01-16 2016-08-10 中兴通讯股份有限公司 告警处理方法及装置
CN105915380A (zh) * 2016-04-19 2016-08-31 广东威创视讯科技股份有限公司 一种故障管理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101854343A (zh) * 2009-04-01 2010-10-06 华为终端有限公司 提供节点信息的方法、获取节点信息的方法及设备
CN102394778A (zh) * 2011-11-04 2012-03-28 中兴通讯股份有限公司 网络拓扑的显示方法及装置
CN102571417A (zh) * 2011-12-15 2012-07-11 江苏亿通高科技股份有限公司 动态拓扑的实现方法
CN105207793A (zh) * 2014-05-30 2015-12-30 亿阳信通股份有限公司 一种树状拓扑结构中节点信息的获取方法和***

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3761563A4 (en) * 2018-03-30 2021-07-07 Samsung Electronics Co., Ltd. DEVICE AND METHOD FOR MANAGING NETWORK RESOURCES IN A NETWORK FUNCTION VIRTUALIZATION ENVIRONMENT
CN111191937A (zh) * 2019-12-31 2020-05-22 深圳市计通智能技术有限公司 一种告警危害评估方法、***及终端设备
CN111191937B (zh) * 2019-12-31 2023-12-29 深圳市计通智能技术有限公司 一种告警危害评估方法、***及终端设备
CN113643757A (zh) * 2020-12-02 2021-11-12 广东美格基因科技有限公司 一种微生物组学数据交互分析***
CN113643757B (zh) * 2020-12-02 2024-04-02 广东美格基因科技有限公司 一种微生物组学数据交互分析***

Also Published As

Publication number Publication date
CN107800556B (zh) 2022-04-29
CN107800556A (zh) 2018-03-13

Similar Documents

Publication Publication Date Title
WO2018045901A1 (zh) 界面生成***、钻取服务层装置、数据发送方法
US20200382362A1 (en) Alarm information processing method, related device, and system
US8285800B2 (en) Service model creation using monitored data of the performance management tool
CN108370341B (zh) 资源配置方法、虚拟网络功能管理器和网元管理***
US8443078B2 (en) Method of determining equivalent subsets of agents to gather information for a fabric
CN109964507B (zh) 网络功能的管理方法、管理单元及***
US10680926B2 (en) Displaying adaptive content in heterogeneous performance monitoring and troubleshooting environments
CN106304136B (zh) 获取网络状态信息的方法、***、控制器和模拟移动设备
EP3806392A1 (en) Fault management method and related device
CN114791846A (zh) 一种针对云原生混沌工程实验实现可观测性的方法
WO2014056345A1 (zh) 监控任务的管理方法及装置
CN103581238A (zh) 泛在网的统一业务平台及业务实现方法
EP3937425A1 (en) Deriving network device and host connection
CN111371570A (zh) 一种nfv网络的故障检测方法及装置
CN114726789A (zh) 流量管理、配置流量管理策略的方法、装置、设备及介质
CN104461553A (zh) 一种符合smi-s标准的存储管理方法
US10715608B2 (en) Automatic server cluster discovery
CN109088779A (zh) 设备服务测试方法及无线电测试***
CN111045757A (zh) It资源运行状态的可视化展示***和方法及存储介质
CN115378853A (zh) 一种网络监控方法、装置和设备
CN103618624B (zh) 利用snmp告警实现设备自动发现的方法
CN112135302A (zh) 基站拓扑信息的控制方法、装置及计算机可读存储介质
CN112068953B (zh) 一种云资源精细化管理溯源***及方法
CN112306848B (zh) 微服务***的架构视图生成方法及装置
US20240223441A1 (en) Apparatus and method for centralized fault monitoring

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: 17848074

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17848074

Country of ref document: EP

Kind code of ref document: A1