CN107800556B

CN107800556B - Interface generation system, drilling service layer device and data transmission method

Info

Publication number: CN107800556B
Application number: CN201610806378.XA
Authority: CN
Inventors: 黄健; 徐代刚; 刘学生; 王淼
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-09-06
Filing date: 2016-09-06
Publication date: 2022-04-29
Anticipated expiration: 2036-09-06
Also published as: CN107800556A; WO2018045901A1

Abstract

The invention provides an interface generation system, a drilling service layer device and a data transmission method; wherein, this interface generation system includes: the system comprises a database, a UI interface layer device and a drilling service layer device; the system comprises a drilling service layer device, a UI interface layer device and a resource node selection device, wherein the UI interface layer device is used for sending a resource identification ID of a resource node clicked by a user to the drilling service layer device, receiving data corresponding to the resource ID returned by the drilling service layer device, and generating a UI interface of the resource node according to the returned data corresponding to the resource ID; the drilling service layer device is used for receiving the resource ID sent by the UI interface layer device and acquiring data corresponding to the resource ID from the database; sending the acquired data corresponding to the resource ID to the UI interface layer device; wherein the data corresponding to the resource ID includes: node topology relationship data of the resource nodes. The invention solves the problem that the root position of alarm generation can not be quickly positioned in the related technology.

Description

Interface generation system, drilling service layer device and data transmission method

Technical Field

The invention relates to the field of network function virtualization, in particular to an interface generation system, a drilling service layer device and a data sending method.

Background

In recent years, cloud computing and virtualization technologies are rapidly developed, a lot of innovations are brought, meanwhile, great pressure is brought to operators, the operators face to find new income growth points to offset the influence brought by the OTT service, and meanwhile, in order to reduce the operation cost OPEX, the functions of network equipment are enabled to be independent of special hardware through software and hardware decoupling and function abstraction, resources can be fully and flexibly shared, the rapid development and deployment of new services are realized, services such as automatic deployment, elastic expansion, fault isolation and self-healing are rapidly developed based on actual service requirements, and therefore the problems need to be solved through network function virtualization.

According to ETSI Network virtualization Management (NFV-MANO) architecture design, as shown in fig. 1, Management objects of Network Function virtualization Management nfvo (Network virtualization architecture) relate to Network services ns (Network service), virtual Network Functions vnf (virtualized Network Function), and virtual Network Function components vnfc (virtualized Network Function component) of a service layer; a virtual deployment unit vdu (virtualized deployment unit) of the virtual layer; HOST of physical layer. Therefore, the management range of the NFVO covers the physical layer, the virtual layer and the business layer, the NFVO has the characteristics of wide management range and multiple types of managed objects, and great challenges are brought to positioning the alarm source position and analyzing the alarm influence by a great amount of alarm information generated by the managed objects every day.

In the NFV domain, there is a relationship of attribution or deployment between managed objects (physical resources, virtual resources, business systems) of the NFVO, for example, a virtual machine is deployed on a physical host, a VNFC is deployed on the virtual machine, a plurality of VDUs are attributed to one VNF, and a plurality of VNFs are attributed to one NS. Therefore, the fault generated by the physical host often affects the operation of the virtual machine, and further affects the operation of the service system on the virtual machine, so that a plurality of pieces of alarm information are derived. A large amount of alarm information is gathered on the NFVO of the upper management system, and alarms reflecting root faults are submerged, so how to help monitoring personnel to quickly locate the root position of alarm generation and analyze the influence range of the alarms becomes a subject to be considered and solved.

For the above technical problem, no effective solution has been proposed at present.

Disclosure of Invention

The embodiment of the invention provides an interface generation system, a drilling service layer device and a data sending method, which at least solve the problem that the source position generated by an alarm cannot be quickly positioned in the related technology.

According to an embodiment of the present invention, there is provided an interface generation system including: the system comprises a database, a UI interface layer device and a drilling service layer device; the system comprises a drilling service layer device, a UI interface layer device and a resource node selection device, wherein the UI interface layer device is used for sending a resource identification ID of a resource node clicked by a user to the drilling service layer device, receiving data corresponding to the resource ID returned by the drilling service layer device, and generating a UI interface of the resource node according to the returned data corresponding to the resource ID; the drilling service layer device is used for receiving the resource ID sent by the UI interface layer device and acquiring data corresponding to the resource ID from the database; sending the acquired data corresponding to the resource ID to the UI interface layer device; wherein the data corresponding to the resource ID includes: node topology relationship data of the resource nodes.

Optionally, the node topology relationship data includes: data of a resource node, data of a parent node of a resource node, and/or data of a child node of a resource node.

Optionally, the data corresponding to the resource ID further includes: and alarm indication information used for indicating the alarm of the father node and/or the child node.

Optionally, the UI interface layer device is further configured to generate a topological relation graph of the resource node according to the node topological relation data and the alarm indication information, where the UI interface includes the topological relation graph.

Optionally, the data corresponding to the resource ID further includes: the resource node detailed information comprises alarm statistical information of the content of alarm generated by the resource node and/or the performance statistical information; wherein the resource node detail information includes: a key and a key value of the resource node.

Optionally, 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.

Optionally, the drill-out service layer device is further configured to obtain resource node details, alarm statistics, and/or performance statistics from the database by calling a data query application programming interface API.

Optionally, the UI interface layer means sends the resource ID to the drill-in service layer means through a representational state transfer, REST, interface.

According to an embodiment of the present invention, there is provided a service floor drilling apparatus including: the receiving module is used for receiving the resource identifier ID of the resource node sent by the UI interface layer; the acquisition module is used for acquiring data corresponding to the resource ID according to the resource ID; a sending module, configured to send data corresponding to the resource ID to the UI interface layer, where the data corresponding to the resource ID includes: node topological relation data of the resource nodes; and the data corresponding to the resource ID is used for the UI interface layer to generate the UI interface of the resource node.

Optionally, the drilling service layer device further comprises: the packaging module is used for packaging the data corresponding to the resource ID into a data object; wherein the data corresponding to the resource ID further comprises: the resource node detailed information comprises alarm statistical information and/or performance statistical information of the alarm content of the resource node; wherein the resource node detail information includes: a key and a key value of the resource node.

Optionally, the obtaining module is further configured to obtain resource node detailed information, alarm statistics information and/or performance statistics information from a database by calling a data query application programming interface API.

Optionally, the receiving module is further configured to receive the resource ID through a representational state transfer REST interface.

According to an embodiment of the present invention, there is provided a data transmission method including: receiving a resource identifier ID of a resource node sent by a UI interface layer; acquiring 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, wherein the data corresponding to the resource ID comprises: node topological relation data of the resource nodes; and the data corresponding to the resource ID is used for the UI interface layer to generate the UI interface of the resource node.

Optionally, the data corresponding to the resource ID further includes: alarm indication information for indicating the parent node and/or the child node to alarm; and the alarm indication information is used for generating a topological relation graph together with the node topological relation data.

Optionally, the obtaining 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 resource node detailed information corresponding to the resource ID, alarm statistical information and/or performance statistical information including the content of alarm of the resource node from a database; encapsulating the node topological relation data, the resource node detailed information, the alarm statistical information and/or the performance statistical information into a data object, and sending the data object to a UI interface layer, wherein the resource node detailed information comprises: a key and a key value of a resource node.

Optionally, the obtaining of the resource node detailed information corresponding to the resource ID, the alarm statistical information including the content of the alarm generated by the resource node, and/or the performance statistical information from the database includes: and acquiring the detailed information of the resource nodes, the alarm statistical information and/or the performance statistical information from the database by calling a data query Application Programming Interface (API).

Optionally, the receiving the resource identifier ID of the resource node sent by the UI interface layer includes: the resource ID is received through a representational state transfer REST interface.

According to still another embodiment of the present invention, there is also provided a storage medium. The storage medium is configured to store program code for performing the steps of: receiving a resource identifier ID of a resource node sent by a UI interface layer; acquiring 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, wherein the data corresponding to the resource ID comprises: node topological relation data of the resource nodes; and the data corresponding to the resource ID is used for the UI interface layer to generate the UI interface of the resource node.

According to the invention, as the UI interface of the resource node is generated by the interface generation system according to the data corresponding to the resource ID, and the generated UI interface displays the node topological relation data of the resource node, the parent node icon or the child node icon on the UI interface can be clicked to quickly access the parent node or the child node, and further when one node gives an alarm, the root position of the alarm can be quickly positioned through the UI interface, the problem that the root position of the alarm cannot be quickly positioned in the related technology can be solved, and the efficiency of alarm positioning is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a schematic structural diagram of an interface generation system provided in accordance with an embodiment of the present invention;

FIG. 2 is a schematic block diagram of a layered drilling system provided in accordance with a preferred embodiment of the present invention;

FIG. 3 is a schematic flow chart of interface generation provided in accordance with 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 diagram of the NFV-MANO architecture in the ETSI standard according to the preferred embodiment of the present invention;

fig. 6 is a node relationship diagram of an NFVO management object provided in accordance with a preferred embodiment of the present invention;

fig. 7 is a schematic diagram of a node relationship corresponding to each node provided in the preferred embodiment of the present invention;

FIG. 8 is a schematic flow chart illustrating the operation of drill-down analysis from the business layer to the physical layer in accordance with a preferred embodiment of the present invention;

FIG. 9 is a schematic flow chart illustrating the operation of drill-down analysis from the physical layer to the business layer in accordance with a preferred embodiment of the present invention;

FIG. 10 is a block diagram of a drill-out service layer apparatus provided in accordance with the present invention;

fig. 11 is a flowchart illustrating a data transmission method according to a preferred embodiment of the present invention;

fig. 12 is a block diagram of a hardware configuration of a mobile terminal of a data transmission method according to an embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

Example 1

An embodiment of the present invention provides an interface generation system, and fig. 1 is a schematic structural diagram of an interface generation system provided in an embodiment of the present invention, and as shown in fig. 1, the system includes: a database 10, a UI interface layer means 12 and a drill-out service layer means 14;

the UI interface layer device 12 is used for sending the resource identifier ID of the resource node clicked by the user to the drilling service layer device 14, receiving data corresponding to the resource ID returned by the drilling service layer device 14, and generating a UI interface of the resource node according to the returned data corresponding to the resource ID;

a drilling service layer device 14 for receiving the resource ID sent by the UI interface layer device 12 and acquiring data corresponding to the resource ID from the database 10; and transmitting the acquired data corresponding to the resource ID to the UI interface layer device 12; wherein the data corresponding to the resource ID includes: node topology relationship data of the resource nodes.

Through the interface generation system, the UI interface layer device 12 generates the UI interface of the resource node according to the data corresponding to the resource ID, wherein the generated UI interface displays the node topological relation data of the resource node, so that clicking the parent node icon or the child node icon on the UI interface can quickly access the parent node or the child node, and when an alarm occurs on a node, the root position of the alarm can be quickly located through the UI interface, the problem that the root position of the alarm cannot be quickly located in the related art can be solved, and the efficiency of alarm location is improved.

It should be noted that the resource node may be a management object of the NFVO, such as, but not limited to, a network service NS, a virtual network function VNF, a virtual network function component VNFC, a virtual deployment unit of a virtual layer, a HOST of a physical layer, and the like.

It should be noted that, the node topology relationship data may include: data of a resource node, data of a parent node of a resource node, and/or data of a child node of a resource node. For example, when the resource node is HOST, the node topology relationship data includes: data of a parent node VDU; when the resource node is a VNFC, the node topology relationship data includes: data of a parent node VDU; when the resource node is a VDU, the node topology relationship 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 a VNF, the node topology relationship data includes: data of a parent node NS and data of a child node VDU; when the resource node is the NS, the node topology relationship data includes: data of child node VNFs; but is not limited thereto.

In one embodiment of the present invention, the data corresponding to the resource ID further includes: and alarm indication information used for indicating the alarm of the father node and/or the child node.

The UI interface layer device 12 may further be configured to generate a topological relation graph of the resource node according to the node topological relation data and the alarm indication information, where the UI interface includes the topological relation graph.

The warning indication information may be identification information such as color, highlight, or flashing, but is not limited thereto.

Taking the above alarm indication information as color and the color as red as an example, the icon of the node in which an alarm appears in the resource node, the child node of the resource node, and the parent node of the resource node in the topological relation diagram displayed on the UI interface is colored red, that is, the icon of the node in which a red color appears in the topological relation diagram displayed on the UI interface represents that an alarm appears in the node, and other alarm indication information is similar and is not described here again.

It should be noted that the alarm may have many levels, such as four levels of normal, secondary, primary and severe, and the alarm indication information corresponding to the alarms of different levels is different, such as a severe alarm may be indicated by red, a primary alarm by orange, a secondary alarm by yellow, and a normal alarm by blue, but is not limited thereto. It should be noted that, if two or more levels of alarms occur in one node, for example, a child node of a resource node, the topological relation graph is generated with the alarm indication information of the highest level together with the node topological relation data, but the present invention is not limited thereto.

The embodiment facilitates a user to quickly find the node with the alarm indication information, namely the node with the alarm, through the topological relation graph of the UI interface, and further can quickly locate the root position of the alarm generation.

In an embodiment of the present invention, the data corresponding to the resource ID further includes: the resource node detailed information comprises alarm statistical information of the content of alarm generated by the resource node and/or the performance statistical information; wherein the resource node detail information includes: a key and a key value of the resource node. That is, the drill service layer means 14 may be further adapted to retrieve resource node details, alarm statistics and/or performance statistics corresponding to the resource ID from the database 10 and to send the resource node details, alarm statistics and/or performance statistics to the UI interface layer means 12. Specifically, the drill service layer device 14 may be 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 12. That is, the UI interface generated by the UI interface layer device 12 may include alarm statistical information, performance statistical information, and/or resource node detailed information, that is, the content really concerned by the user is focused, and a comprehensive analysis may be quickly performed on the concerned resource node, where the interface presentation manner is different from that of the conventional management system (topology, resources, alarms, and performance are managed separately, and each management interface is owned, and when the user wants to check the topology relation diagram, alarm statistical information, and performance statistical information of a resource node, it is necessary to switch to a different page to check), and the content of generating an alarm, that is, the root cause of the alarm generation, may be obtained by checking the alarm statistical information.

It should be noted that the performance statistics information is information used for indicating the performance of the resource node, such as CPU utilization, memory utilization, and the like of the resource node, but is not limited thereto, and it should be noted that the performance statistics information may be periodically collected, and the performance statistics information may support a table or graphically present a variation trend of the performance index in the generated UI interface, and may assist the operation and maintenance staff to analyze and locate the reason for generating the alarm.

It should be noted that the 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; alarm data of resources are stored in an alarm database; the performance database stores performance data for the resources.

It should be noted that the drill-out service layer device 14 may also be used to obtain resource node details, alarm statistics and/or performance statistics from the database 10 by calling a data query application programming interface API. The UI interface layer means 12 sends the resource ID to the drill-down service layer means 14 via a representational state transfer REST interface.

It should be noted that the interface generation system has universality, after the interface generation system generates a UI interface of a resource node, if it is found that an alarm identifier (first alarm indication information and/or second alarm indication information) is marked on a parent node and/or a child node icon of the resource node in a topological relation diagram of the resource node displayed on the UI interface, if the parent node icon is clicked, the interface generation system generates the UI interface of the parent node, if the child node icon is clicked, the interface generation system generates the UI interface of the child node, and in combination with the interface generation system, when an alarm occurs on a resource node of a physical layer, a range affected by the alarm can be quickly accessed to the resource node of the physical layer by drilling up to the layer, and when an alarm occurs on a service node, and the source position of the alarm generated by the service node can be quickly accessed through the operation of drilling down layer by layer.

For a better understanding of the present invention, the present invention is further explained below with reference to preferred examples.

Fig. 2 is a schematic structural diagram of a layered drilling system provided according to a preferred embodiment of the present invention, as shown in fig. 2, the system including:

UI interface presentation layer (corresponding to the UI interface layer device): and providing a user operation interface, and presenting a node relation graph (equivalent to the topological relation graph), alarm statistical information and performance statistical information of different node types.

Drilling services (equivalent to the drilling service layer devices described above): and inquiring and acquiring related data through API interfaces provided by resource management, alarm management and performance management, and providing the data to a UI interface presentation layer through an REST interface to present a related interface.

Resource management: and providing an API (application programming interface) query interface of the resource detail data and the resource topological relation data.

And (3) alarm management: and providing an API inquiry interface of the alarm statistical data of the resource.

And (3) performance management: an API query interface that provides performance statistics for a performance.

Resource database: and storing resource instance data of different resource types and node relation data thereof.

An alarm database: alarm data for the resource is stored.

A performance database: performance data of the resources is stored.

Fig. 3 is a schematic flow chart of interface generation provided in accordance with a preferred embodiment of the present invention, and as shown in fig. 3, the flow chart includes: clicking a parent-child node icon on the node relation graph by a user; and the UI interface layer sends the resource ID of the resource clicked by the user to a drilling service layer of the service end through the REST interface. After receiving the request, the drilling service layer sends the resource ID transmitted by the UI interface layer to resource management through an API (application program interface) provided by the resource management module, and the resource management module inquires the resource detailed information corresponding to the resource ID and the parent-child node information related to the resource through an inquiry interface provided by the resource database and then returns the resource detailed information and the parent-child node information to the drilling service layer. After receiving the detailed resource information and the parent-child node information related to the resource returned by the resource management, the drilling service layer continues to send the resource ID information to the alarm management module through an API (application programming interface) provided by the alarm management module, and the alarm management module inquires the alarm statistical information corresponding to the resource ID through an inquiry interface provided by the alarm database and returns the inquired alarm statistical information to the drilling service layer. And after receiving the alarm statistical information returned by the alarm management, the drilling service layer continues to send the resource ID information to the performance management module through an API (application programming interface) provided by the performance management module, and the performance management module inquires the performance statistical information corresponding to the resource ID through an inquiry interface provided by the performance database and returns the performance statistical information to the drilling service layer. And the drilling service layer summarizes the resource detail information, the parent-child node information, the alarm statistical information and the performance statistical information corresponding to the inquired resource ID into a data object and returns the data object to the UI interface layer. And after receiving the data returned by the drilling service layer, the UI interface layer generates an interface shown in the figure 4, and intensively presents the resource details of the resources selected by the user, the resource parent-child node relation graph, the alarm statistical information of the resources and the performance statistical information of the resources to the user.

In the preferred embodiment of the present invention, the resources of the physical layer and the virtual layer, and the alarm and performance data thereof are designed according to the NFV-MANO architecture of ETSI, and are collected by a vim (virtual Infrastructure manager) management system, and are reported to the Nfvo through an Nfvo-Vi interface, as shown in fig. 5. The resources of the service layer, the alarms and performance data thereof are collected by a Vnfm (vnf manager) management system and reported to the Nfvo through an Nfvo-Vnfm interface, as shown in fig. 5. In the NFV field, resource, alarm, and performance data of all physical, virtual, and business layers are aggregated in an NFVO management system, and are uniformly managed and organized by the NFVO system. The preferred embodiment of the present invention follows the Tosca-NFV (topology and organization Specification for Cloud applications) Specification when modeling the resources of these physical, virtual, and business layers in the NFVO system, and maps these resource types into node types defined by the Tosca-NFV Specification, for example: NS/VNF/VNFC/VDU, etc. Meanwhile, the deployment relationship, the attribution relationship and the like among the node types in the NFV field are described according to the node relationship type defined in the Tosca-NFV specification. According to the Tosca-NFV specification, we can build a logical topological relation graph of the resource nodes of the whole network, as shown in fig. 6.

By using the logical topological relation graph of the whole network, the invention places any resource node and the parent-child node directly related to the resource node in the same topological relation graph, as shown in fig. 7. And the user can quickly access the parent-child resource node associated with the current resource node by clicking the parent node icon or the child node icon through the interface. And the interface presents the resource details of the new node and the topological relationship graph of the new node and its directly associated parent-child nodes. By utilizing the characteristic, a user can quickly access the virtual resource nodes of the virtual layer deployed on the physical node and the service nodes operated by the service layer from one physical node through the operation of drilling upwards layer by layer. The method can also be started from one service node, and quickly accesses which virtual resource node of the virtual layer the service node is deployed on and which physical resource node of the physical layer the virtual node is deployed on by drilling downwards layer by layer, so that a user can realize the function of drilling layer by layer among the physical layer, the virtual layer and the service layer resource nodes.

Meanwhile, the invention combines the alarm rendering function, when the resource node gives an alarm, the alarm rendering is carried out on the icon of the resource node, and the resource icon giving the alarm is colored. If the underlying physical host generates an alarm and causes the virtual machine running on the host to generate an alarm, the alarm of the virtual machine affects the service running on the virtual machine, and thus a service alarm is generated. Then alarm rendering will be performed on the corresponding HOST, VDU and VNF resource nodes simultaneously. Taking fig. 7 as an example, if three resource nodes, i.e., HOST1/VDU1/VNF1, have alarms, the three resource nodes perform alarm rendering simultaneously, and when a user finds that a service alarm is generated in a VNF1 resource node (fig. 7 c), by looking at a topological relationship diagram of parent and child nodes of the node and using the characteristic of alarm rendering, it can be seen at a glance that an alarm also occurs in the VDU1 resource node, and quickly access the VDU1 resource node by clicking a VDU1 node icon (fig. 7 c). Similarly, by viewing a topological relation graph of parent and child nodes of the VDU1 resource node, the characteristic of alarm rendering is utilized to find that an alarm appears in the HOST1 resource node, so that the HOST1 resource node icon is continuously clicked, the detailed information page of the HOST1 can be entered, and the root position of the VNF1 service alarm is located, namely the HOST 1. Thus, cross-layer correlation analysis from the service layer to the virtual layer and then to the physical layer is completed once, and the process of generating the root position of the service alarm is positioned.

Similarly, when an alarm is generated by a physical node, the service range influenced by the alarm generated by the physical layer/virtual layer can be quickly positioned by drilling upwards from the node layer by layer.

The preferred embodiment of the invention provides three views of a service layer, a virtual layer and a physical layer to monitor the running states of a whole network service system, virtual resources and physical resources. Wherein the business layer view is used to monitor the operation of the network service NS and the virtual network function VNF. The virtual layer view is used to monitor the operation of the virtual deployment unit (i.e., virtual machine) VDU. The physical layer view is used to monitor the operation of the physical HOST.

In the service layer monitoring, a topology overview of the entire network of the NS and the independent VNF is provided (as in fig. 7 (r)). The detailed information page of the NS can be accessed by clicking the NS topology node, the basic information description, the alarm statistical information and the performance index statistical information of the NS are checked, and the node attribution relationship graph of the NS-VNF is presented. Because the alarm information of the NS is derived according to the alarm of the VNF, when the VNF generates an alarm, the alarm is rendered simultaneously on the VNF topology node and the NS node to which the VNF belongs, and the user can quickly locate the VNF node that causes the NS to generate the alarm by looking up the node attribution relationship graph of the NS-VNF.

The VNF topology node is clicked to enter a detailed information page of the VNF, basic information description, alarm statistical information and performance index statistical information of the VNF are checked, and meanwhile a node attribution relation graph of the NS-VNF-VDU is presented. Similarly, a user can quickly locate a VDU node causing the VNF to generate an alarm by looking at the NS-VNF-VDU node home relationship graph.

The detailed information page of the VDU can be accessed by clicking the topological node of the VDU, the basic information description, the alarm statistical information and the performance index statistical information of the VDU are checked, and the node attribution/deployment relation graph of the VNF-VDU-VNFC and the VNF-VDU-HOST is presented. Wherein the VNF-VDU-VNFC node relationship graph describes which VNFCs are deployed on the VDU, and the VNF-VDU-HOST node relationship graph describes which vsfcs are deployed on which HOST.

Clicking a VNFC node from a VNF-VDU-VNFC node relation graph can enter a detailed information page of the VNFC, and basic information description, alarm statistical information and performance index statistical information of the VNFC and a node deployment relation graph of the VDU-VNFC are checked.

Clicking the HOST node from the VNF-VDU-HOST node relation graph can enter a HOST detailed information page, and checking basic information description, alarm statistical information and performance index statistical information of the HOST and a node deployment relation graph of the VDU-HOST.

Through the layer drilling mode, a user can quickly access the nodes directly associated with the managed nodes according to the attribution and deployment relations of the managed nodes, the page of each node comprises the basic information, the alarm statistical information and the performance index statistical information of the node, and the user can quickly analyze whether the running state of the node is normal or not and whether the running state is the root position for generating business alarm or not.

Meanwhile, since the topology of each node includes its home, deployment related node, the drilling mode may be a down-to-up mode. For example, in physical layer monitoring, it is found that a physical host frequently generates an alarm with high CPU utilization recently, and although such an alarm does not necessarily affect the operation of the service system immediately, the reason for the generation needs to be analyzed. After finding the alarm, the user can drill upwards to check which virtual machines run on the physical host and which service systems run on the virtual machines, so that the user can know which service systems are possibly influenced by the alarm of the physical host, and can analyze whether the service systems generate the alarm with high CPU utilization rate due to the increase of the service volume, thereby making a decision basis for whether expansion is needed or horizontal load balancing is needed.

The preferred embodiment of the invention takes resources as a center, centralizes the resource details, the alarm statistical information and the performance statistical information of one resource on one page, and presents a topological relation graph of the resource node and a parent-child node directly related to the resource node, as shown in fig. 4. The method focuses on the content really concerned by the user, and can quickly and comprehensively analyze the concerned resource nodes. The interface presentation mode is different from the traditional management system which separately manages topology, resources, alarms and performance and has respective management interfaces, when a user needs to check a topological relation graph, alarm statistical information and performance statistical information of one resource, the user needs to switch to different pages to check, and each page needs to perform query operation once to filter out relevant information of the resource. The drilling service layer is extracted from the service end of the system, and data support service is provided for layer-by-layer drilling operation performed on the interface. And the front-end interface UI only interacts with the drilling service layer, and when a user clicks any one resource icon, the resource ID of the resource is sent to the drilling service layer through the REST interface. And after receiving the request, the drilling service layer calls data query API interfaces of resource management, alarm management and performance management respectively by taking the resource ID as a parameter, acquires resource data, topological relation data, alarm data and performance data information of the resource, packages the four data in a data object and returns the data object to the UI interface, finally generates a corresponding interface according to the graph shown in FIG. 4 by the UI interface layer, and fills the data returned by the drilling service layer into the interface.

It should be noted that, based on the above system, the analysis of the alarm source of the resource node can be realized, and the analysis method includes: determining that a resource node in a virtual network generates an alarm; determining the source position of the alarm generated by the resource node according to the topological relation among the resource nodes in the virtual network and the alarm rendering characteristics (equivalent to the first alarm indication information and/or the second alarm indication information) of the resource nodes; and the alarm rendering characteristic is that the resource node identification corresponding to the resource node with the alarm in the topological relation is colored.

It should be noted that, determining, according to the topological relation among the resource nodes in the virtual network and the alarm rendering characteristic of each resource node, a source position where the resource node generates the alarm includes: determining the source position of the alarm generated by the resource node by adopting a mode of drilling upwards layer by layer or drilling downwards layer by layer according to the topological relation and the alarm rendering characteristic; the upward layer-by-layer drilling is to drill layer-by-layer in the direction of a father node of the resource node by taking the resource node as a starting point; and the downward layer-by-layer drilling is to drill layer-by-layer in the direction of the sub-node of the resource node by taking the resource node as a starting point.

Further, determining the source position of the alarm generated by the resource node by adopting a mode of drilling upward layer by layer comprises the following steps: when the father node of the resource node is not the virtual service NS, taking the resource node as an initial node, and circularly executing the following steps until a termination condition is met: determining whether an alarm occurs at the originating node; under the condition that the starting node is determined to have an alarm, acquiring a topological relation between the starting node and a father node of the starting node; determining whether alarm rendering occurs in the father node of the initial node according to the topological relation between the initial node and the father node of the initial node; taking the father node of the initial node as the initial node under the condition that the father node of the initial node generates alarm rendering; wherein the termination condition is that an alarm occurs in the starting node and no alarm occurs in a father node of the starting node; and determining that the source position of the alarm generated by the resource node is the initial node obtained after the circulation is finished.

Preferably, after acquiring the topological relationship between the starting node and the parent node of the starting node, the method further comprises: and displaying the topological relation between the starting node and the parent node of the starting node.

Preferably, in a case that the starting node is a physical layer HOST, a topological relationship between the starting node and a parent node of the starting node is a topological relationship between a virtual deployment unit VDU and HOST of a virtual layer; in the case that the starting node is a VDU, a topological relationship between the starting node and a parent node of the starting node is a topological relationship between VNF, VDU and HOST, or a topological relationship between VNF, VDU and VNFC; in the case that the starting node is a VNFC, a topological relationship between the starting node and a parent node of the starting node is a topological relationship between a VDU and the VNFC; in the case that the starting node is a VNF, a topological relationship between the starting node and a parent node of the starting node is a topological relationship between an NS, a VNF, and a VDU.

Preferably, determining the source location of the alarm generated by the resource node by drilling up layer by layer includes: when the father node of the resource node is NS, acquiring the topological relation between the resource node and the father node; determining whether alarm rendering occurs in the father node according to the topological relation between the resource node and the father node; and under the condition that the parent node is determined to have alarm rendering, determining that the source position of the alarm generated by the resource node is the NS.

Preferably, determining the source location of the alarm generated by the resource node by drilling down a layer by layer includes: when the child node of the resource node is not a virtual network function component VNFC or a HOST of a physical layer, taking the resource node as a starting node, and circularly performing the following steps until a termination condition is met: determining whether an alarm occurs at the originating node; under the condition that the starting node is determined to have an alarm, acquiring a topological relation between the starting node and child nodes of the starting node; determining whether the child nodes of the starting node generate alarm rendering according to the topological relation between the starting node and the child nodes of the starting node; taking the child node of the starting node as the starting node under the condition that the child node of the starting node generates alarm rendering; wherein the termination condition is that the alarm rendering occurs in the starting node and no alarm rendering occurs in the child nodes of the starting node; and determining that the source position of the alarm generated by the resource node is the initial node obtained after the circulation is finished.

Preferably, after obtaining the topological relation between the starting node and the child nodes of the starting node, the method further includes: and displaying the topological relation between the starting node and the child nodes of the starting node.

Preferably, when the starting node is the NS, the topological relationship between the starting node and the child nodes of the starting node is the topological relationship between the NS and the VNF; when the starting node is a VNF, the topological relation between the starting node and the child nodes of the starting node is the topological relation between NS, the VNF and the VDU; when the starting node is a VDU, the topological relationship between the starting node and the child nodes of the starting node is a topological relationship between VNF, VDU and VNFC or a topological relationship between VNF, VDU and HOST.

Preferably, determining the source location of the alarm generated by the resource node by drilling up layer by layer includes: when a child node of the resource node is VNFC or HOST, acquiring a topological relation between the resource node and the child node; determining whether the child node generates alarm rendering according to the topological relation between the resource node and the child node; and under the condition that the child node is determined to have alarm rendering, determining that the source position of the alarm generated by the resource node is the VNFC or the HOST.

Preferably, after determining the source location where the resource node generates the alarm, the method further comprises: acquiring alarm statistical information of the root position; and determining the source of the alarm generated by the resource node according to the alarm statistical information.

The analysis method implemented based on the system can be implemented by a specific analysis tool or manually, and is described below with reference to the preferred embodiments:

it should be noted that fig. 6 is a node relationship diagram of the NFVO management object provided according to the preferred embodiment of the present invention, as shown in fig. 6, a VDU and a VNF are in a many-to-one home relationship, and a VNF and an NS are also in a many-to-one home relationship; the VNFC and the VDU are in one-to-one deployment relationship, and the VDU and the HOST are in many-to-one deployment relationship.

Fig. 8 is a flow chart of operations of drill-down analysis from the service layer to the physical layer, as shown in fig. 8, the method includes:

step 801, checking the topology map of the network service of the whole network, and entering step 802 if finding that a certain NS generates an alarm.

Step 802 looks up the detailed information of the designated NS, including its basic information, alarm statistics, performance index statistics, and the node relationship graph of the NS-VNF.

Step 803 drills to VNF node.

Step 804 looks up the detailed information of the designated VNF, including its basic information, alarm statistics information, performance index statistics information, and the node relationship graph of the NS-VNF-VDU.

Step 805 drills to the VDU node.

Step 806 looks at detailed information of the specified VDU, including its basic information, alarm statistics, performance index statistics, and a node relationship graph of VNF-VDU-VNFC and VNF-VDU-HOST.

Step 807 drills into the VNFC node.

Step 808 checks detailed information of the designated VNFC, including basic information, alarm statistics information, performance index statistics information, and a node relationship diagram of the VDU-VNFC.

Step 809 drills to the HOST node.

Step 810 looks up detailed information of the specified HOST, including its basic information, alarm statistics, performance index statistics, and the node relationship graph of the VDU-HOST.

Fig. 9 is a flow of operations of drill-down analysis from the physical layer to the business layer, as shown in fig. 9, the flow includes:

step 901 looks up the topology map of the physical hosts or single boards in the whole network, and if some physical host or single board is found to generate an alarm, step 902 is entered.

Step 902 looks up the detailed information of the designated physical HOST or board, including its basic information, alarm statistics information, performance index statistics information, and the node relationship graph of VDU-HOST.

Step 903 drills to the VDU node.

Step 904 looks at detailed information of the designated VDU, including its basic information, alarm statistics, performance index statistics, and the node relationship graph of VNF-VDU-VNFC and VNF-VDU-HOST.

Step 905 drills to a VNFC node.

Step 906 checks detailed information of the designated VNFC, including basic information, alarm statistics information, performance index statistics information, and a node relationship diagram of the VDU-VNFC.

Step 907 drills to the VNF node.

Step 908 looks at the detailed information of the specified VNF, including its basic information, alarm statistics, performance index statistics, and node relationship graph of NS-VNF-VDU.

Step 909 drills into the NS node.

Step 910 looks up detailed information of the designated NS, including its basic information, alarm statistics, performance index statistics, and node relationship graph of the NS-VNF.

FIG. 3 is a process flow at the service end of a drill operation, comprising:

step 301 a user clicks on any one of the parent and child resource nodes.

Step 302 the UI interface presentation layer sends the resource ID clicked on by the user to the drill-out service layer.

Step 303, drilling an API query interface provided by the service layer calling the resource management module, and finding out the detailed information of the resource and the parent-child node information directly associated with the resource from the resource database according to the resource ID.

Step 304, the drilling service layer calls an API query interface provided by the alarm management module, and searches the alarm statistical information corresponding to the resource from the alarm database according to the resource ID.

Step 305, drilling a service layer to call an API query interface provided by the performance management module, and finding out performance statistics corresponding to the resource from the performance database according to the resource ID.

Step 306, the drilling service layer returns the detailed information of the resource, the parent-child node information associated with the resource, the alarm statistical information and the performance statistical information to the UI interface presentation layer.

And 307, the UI interface presentation layer presents the resource details, the topological relation graph, the alarm statistical information and the performance statistical information of the resources clicked by the user on the interface according to the data returned by the drilling service layer.

Preferred embodiment 1

And (3) the user finds that the NS sends out the out-of-service alarm and positions the root position of the alarm, such as the process shown in the figure 8 and the figure 7.

Step 1: the user views the network-wide NS topology and finds that the NS1 has a rendered alarm.

Step 2: the user clicks the icon of the NS1 node, enters a detailed information page of the NS1, checks the alarm statistical information of the node, and finds that the NS1 sends out the fallback alarm. And looking at the NS-VNF node topological relation graph, the VNF1 node is found to have alarm rendering.

And step 3: clicking the VNF1 node icon to enter the details page of VNF1, and viewing the alarm statistics finds that VNF1 also issues a fallback alarm. And looking at the NS-VNF-VDU node relation graph, finding VUD1 that the node also presents alarm rendering.

And 4, step 4: clicking the VDU1 node icon to enter the detailed information page of the VDU1, and viewing the alarm statistics to find that the VDU1 issues a chain breaking alarm. And viewing the VNF-VDU-HOST node relation graph, and finding that the HOST1 node has alarm rendering.

And 5: clicking the HOST1 node icon to enter the detailed information page of HOST1, and viewing the alarm statistics to find that HOST1 issues a power down alarm. The fallback of NS1 can thus be located due to the power loss to the physical HOST1 running the service, thereby locating the source of the alarm.

Preferred embodiment 2:

the user finds that the VNF sends a service processing capability reduction alarm, and locates the root position of the alarm, as shown in fig. 8 and 7.

Step 1: the user views the NS-VNF node relation graph and discovers that the VNF1 node has alarm rendering

Step 2: the user clicks the VNF1 node icon, enters the detailed information page of the VNF1, views the alarm statistical information of the node, and finds that the VNF1 issues an alarm of the reduction of the service processing capability. And looking at the NS-VNF-VDU node relation graph, finding VUD1 that the node also presents alarm rendering.

And step 3: clicking a VDU1 node icon to enter a detailed information page of the VDU1, and viewing alarm statistical information to find that the VDU1 sends an alarm with ultrahigh utilization rate of a CPU and a memory. Therefore, the service processing capacity of the localizable VNF1 is reduced due to the fact that the memory and CPU utilization rate of one of the VDUs running the service is very high, and therefore the source position of the alarm is located.

Preferred embodiment 3:

the user finds that the HOST sends an alarm indicating that the CPU utilization rate is over high, and locates the flow of the influence range of the alarm on the upper-layer service, as shown in fig. 9 and 7.

Step 1: a user checks the alarm statistical information of the HOST1 node, finds that the HOST1 node sends an alarm with ultrahigh CPU utilization rate, checks a VDU-HOST node relation graph, and finds that the VDU1 node generates alarm rendering.

Step 2: the user clicks the icon of the VDU1 node, enters a detailed information page of the VDU1 node, checks the alarm statistical information of the node, and finds that the VDU1 also gives an alarm of the overhigh CPU usage. Looking at the VNF-VDU-HOST, VNF-VDU-VNFC node relationship graph, the VDU can be positioned to support the operation of those service nodes VNF, VNFC.

And step 3: clicking the VNFC1 or VNF1 node icon into its detailed information page, looking at the performance statistics may analyze whether the VNFC or VNF is under-allocated resources of the virtual machine running the service due to the increase of the traffic volume, which may result in over-usage of the CPU of the VDU1 or HOST 1. Therefore, the influence range of the alarm generated by HOST1 on the upper-layer service can be positioned, so that the user can be helped to decide whether the expansion or load balancing operation is needed, and the occurrence of the service alarm can be avoided in advance.

Example 2

An embodiment of the present invention further provides a drilling service layer device, fig. 10 is a block diagram of a structure of the drilling service layer device provided by the present invention, and as shown in fig. 10, the drilling server device includes:

a receiving module 1000, configured to receive a resource identifier ID of a resource node sent by a UI interface layer;

an obtaining module 1002, connected to the receiving module 1000, configured to obtain data corresponding to the resource ID according to the resource ID;

a sending module 1004, connected to the obtaining module 1002, configured to send data corresponding to the resource ID to the UI interface layer, where the data corresponding to the resource ID includes: node topological relation data of the resource nodes; and the data corresponding to the resource ID is used for the UI interface layer to generate the UI interface of the resource node.

The data of the clicked resource node is obtained through the drilling service layer device and sent to the UI interface layer for generating the UI interface of the resource node, wherein the generated UI interface displays the node topological relation data of the resource node, so that a father node icon or a son node icon on the UI interface can be clicked to quickly access the father node or the son node, when one node gives an alarm, the root position of the alarm can be quickly positioned through the UI interface, the problem that the root position of the alarm cannot be quickly positioned in the related technology can be solved, and the alarm positioning efficiency is improved.

In an embodiment of the present invention, the data corresponding to the resource ID may further include: and alarm indication information used for indicating the alarm of the father node and/or the child node. The warning indication information may be identification information such as color, highlight, or flashing, but is not limited thereto.

In an embodiment of the present invention, the above drilling service layer device may further include: the encapsulating module is connected with the acquiring module 1002 and the sending module 1004, and is configured to encapsulate data corresponding to the resource ID into a data object; wherein the data corresponding to the resource ID further comprises: the resource node detailed information comprises alarm statistical information and/or performance statistical information of the alarm content of the resource node; wherein the resource node detail information includes: a key and a key value of the resource node. That is, the obtaining module 1002 may be further configured to obtain the resource node detailed information corresponding to the resource ID, the alarm statistical information including the content of the alarm generated by the resource node, and/or the performance statistical information from the database.

In an embodiment of the present invention, the obtaining module 1002 may further be configured to obtain the resource node detail information, the alarm statistic information, and/or the performance statistic information from the database by calling a data query application programming interface API.

It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.

Example 3

According to an embodiment of the present invention, a data transmission method is provided, and fig. 11 is a flowchart illustrating the data transmission method according to the preferred embodiment of the present invention, as shown in fig. 11, the method includes:

step S1102, receiving a resource identifier ID of a resource node sent by a UI interface layer;

step S1104, acquiring data corresponding to the resource ID according to the resource ID;

step S1106, sending data corresponding to the resource ID to the UI interface layer, where the data corresponding to the resource ID includes: node topological relation data of the resource nodes; and the data corresponding to the resource ID is used for the UI interface layer to generate the UI interface of the resource node.

Through the steps, the data of the clicked resource node is obtained and sent to the UI interface layer for generating the UI interface of the resource node, wherein the generated UI interface displays the node topological relation data of the resource node, so that the father node icon or the son node icon on the UI interface can be clicked to quickly access the father node or the son node, when one node gives an alarm, the root position of the alarm can be quickly positioned through the UI interface, the problem that the root position of the alarm cannot be quickly positioned in the related technology can be solved, and the alarm positioning efficiency is improved.

Optionally, the data corresponding to the resource ID further includes: alarm indication information for indicating the parent node and/or the child node to alarm; and the alarm indication information is used for generating a topological relation graph together with the node topological relation data. The warning indication information may be identification information such as color, highlight, or flashing, but is not limited thereto.

It should be noted that the steps S1104 and S1106 may further include: acquiring resource node detailed information corresponding to the resource ID, alarm statistical information and/or performance statistical information including the content of alarm of the resource node from a database; encapsulating the node topological relation data, the resource node detailed information, the alarm statistical information and/or the performance statistical information into a data object, and sending the data object to a UI interface layer, wherein the resource node detailed information comprises: a key and a key value of a resource node.

It should be noted that, the obtaining of the resource node detailed information corresponding to the resource ID, the alarm statistical information including the content of the alarm generated by the resource node, and/or the performance statistical information from the database may include: and acquiring the detailed information of the resource nodes, the alarm statistical information and/or the performance statistical information from the database by calling a data query Application Programming Interface (API).

It should be noted that the resource identifier ID of the resource node sent by the UI interface layer includes: the resource ID is received through a representational state transfer REST interface.

It should be noted that the method embodiment provided in embodiment 3 of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking the operation on the mobile terminal as an example, fig. 12 is a hardware structure block diagram of the mobile terminal of a data transmission method according to an embodiment of the present invention. As shown in fig. 12, mobile terminal 1200 may include one or more (only one shown) processors 1202 (processor 1202 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 1204 for storing data, and a transmitting device 1206 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 12 is only an illustration and is not intended to limit the structure of the electronic device. For example, mobile terminal 1200 may also include more or fewer components than shown in FIG. 12, or have a different configuration than shown in FIG. 12.

The memory 1204 can be used for storing 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 functional applications and data processing by running the software programs and modules stored in the memory 1204, so as to implement the method described above. The memory 1204 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 1204 may further include memory located remotely from processor 1202, which may be connected to mobile terminal 1200 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmitting device 1206 is used for receiving or sending data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal 1200. In one example, the transmitting device 1206 includes a Network Interface Controller (NIC) that can be connected to other Network devices via a base station to communicate with the internet. In one example, the transmitting device 1206 can be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

Alternatively, the main body for performing the above steps may be a drilling service layer device, etc., but is not limited thereto.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

Example 4

The embodiment of the invention also provides a storage medium. Alternatively, in the present embodiment, the above-mentioned storage medium may be configured to store program codes for executing the steps in embodiment 3.

Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

Alternatively, in the present embodiment, the processor executes the steps of the method in embodiment 3 according to the program code stored in the storage medium.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. An interface generation system, comprising: the system comprises a database, a UI interface layer device and a drilling service layer device; wherein,

the UI interface layer device is used for sending the resource identification ID of the resource node clicked by the user to the drilling service layer device, receiving the data corresponding to the resource ID returned by the drilling service layer device, and generating the UI interface of the resource node according to the returned data corresponding to the resource ID;

the drilling service layer device is used for receiving the resource ID sent by the UI interface layer device and acquiring data corresponding to the resource ID from the database; sending the acquired data corresponding to the resource ID to the UI interface layer device; wherein the data corresponding to the resource ID includes: node topology relationship data of the resource nodes;

wherein the node topology relationship data comprises: data of the resource node, data of a parent node of the resource node, and/or data of a child node of the resource node; the data corresponding to the resource ID further includes: alarm indication information used for indicating the father node and/or the child node to generate an alarm; the UI interface layer device is further configured to generate a topological relation graph of the resource node according to the node topological relation data and the alarm indication information, where the UI interface includes the topological relation graph.

2. The system of claim 1, wherein the data corresponding to the resource ID further comprises: the resource node detailed information comprises alarm statistical information and/or performance statistical information of the alarm content of the resource node; wherein the resource node detail information includes: a key and a key value of the resource node.

3. The system according to any one of claims 1 to 2, wherein said drill service layer means is further configured to encapsulate the acquired data corresponding to said resource ID into a data object, and send said data object to said UI interface layer means.

4. The system of claim 2, wherein the drill service layer means is further configured to obtain the resource node details, the alarm statistics, and/or the performance statistics from the database by calling a data query Application Programming Interface (API).

5. The system of claim 1, wherein the UI interface layer means sends the resource ID to the drill-down service layer means through a representational state transfer, REST, interface.

6. A service floor drilling apparatus, comprising:

the receiving module is used for receiving the resource identifier ID of the resource node sent by the UI interface layer;

an obtaining module, configured to obtain data corresponding to the resource ID according to the resource ID;

a sending module, configured to send the 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 nodes; the data corresponding to the resource ID is used for the UI interface layer to generate a UI interface of the resource node;

wherein the node topology relationship data comprises: data of the resource node, data of a parent node of the resource node, and/or data of a child node of the resource node; the data corresponding to the resource ID further includes: alarm indication information used for indicating the father node and/or the child node to generate an alarm; the UI interface layer is further used for generating a topological relation graph of the resource node according to the node topological relation data and the alarm indication information, wherein the UI interface comprises the topological relation graph.

7. The drilling service layer device of claim 6, further comprising: the encapsulation module is used for encapsulating the data corresponding to the resource ID into a data object; wherein the data corresponding to the resource ID further comprises: the resource node detailed information comprises alarm statistical information and/or performance statistical information of the alarm content of the resource node; wherein the resource node detail information includes: a key and a key value of the resource node.

8. The drill service layer apparatus of claim 7, wherein the obtaining module is further configured to obtain the resource node details, the alarm statistics, and/or the performance statistics from a database by calling a data query Application Programming Interface (API).

9. The drill-to-service layer apparatus of claim 6, wherein the receiving module is further configured to receive the resource ID through a representational state transfer (REST) interface.

10. A data transmission method, comprising:

receiving a resource identifier ID of a resource node sent by a UI interface layer;

acquiring 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, wherein the data corresponding to the resource ID comprises: node topology relationship data of the resource nodes; the data corresponding to the resource ID is used for the UI interface layer to generate a UI interface of the resource node;

wherein the node topology relationship data comprises: data of the resource node, data of a parent node of the resource node, and/or data of a child node of the resource node; the data corresponding to the resource ID further includes: alarm indication information for indicating that an alarm occurs at the parent node and/or the child node; the alarm indication information is used for generating a topological relation graph together with the node topological relation data, and the UI comprises the topological relation graph.

11. The method of claim 10, wherein obtaining data corresponding to the resource ID from the resource ID and sending the data corresponding to the resource ID to the UI interface layer further comprises:

acquiring resource node detailed information corresponding to the resource ID, alarm statistical information and/or performance statistical information including the content of alarm of the resource node from a database;

encapsulating the node topological relation data, the resource node detailed information, the alarm statistical information and/or the performance statistical information into a data object, and sending the data object to the UI interface layer, wherein the resource node detailed information comprises: a key and a key value of the resource node.

12. The method according to claim 11, wherein obtaining resource node detail information corresponding to the resource ID, alarm statistic information including content of alarm occurrence of the resource node, and/or performance statistic information from the database comprises:

and acquiring the detailed information of the resource node, the alarm statistical information and/or the performance statistical information from the database by calling a data query Application Programming Interface (API).

13. The method of claim 10, wherein receiving the resource identifier ID of the resource node sent by the UI interface layer comprises: receiving the resource ID through a representational state transfer (REST) interface.