Operation and maintenance method and operation and maintenance device

Abstract

The invention relates to the field of computers, in particular to an operation and maintenance method and an operation and maintenance device. In an existing operation and maintenance system, all non-central nodes report operation and maintenance data to a central node, and when the operation and maintenance system comprises a small number of nodes, the method is simple and effective. However, when some mass nodes or a business system of a multi-level organization structure are involved, the method puts forward a high requirement for the performance of a center node, and the cost of operation and maintenance of the system is too high. According to the method, the non-central nodes in the operation and maintenance system are divided into a plurality of levels, and the non-central nodes of different levels only report the operation and maintenance data to the father node, so that the resource consumption of the central nodes is reduced, and the deployment and maintenance cost of the operation and maintenance system is reduced.

Description

Technical Field

[0001] This application relates to the field of computers, and in particular, to an operation and maintenance method and an operation and maintenance device. Background Art

[0002] To ensure the reliability of the operation of a business system, each business system provides operation and maintenance capabilities, monitors and alarms the running state of the business system, and provides fault handling for abnormal situations to ensure the stability of the operation of the business system.

[0003] In the process of building operation and maintenance capabilities, the general process is that non-central nodes collect operation and maintenance data through components (such as Agents) and report the operation and maintenance data to the central node through an application programming interface (API). The central node provides operation and maintenance data processing functions, identifies abnormal situations in the operation of the business system through data processing and rules, and then reports the abnormal situations through events or alarms. Then, through a monitoring dashboard, a visual monitoring view is configured to assist in providing intuitive operation and maintenance capabilities.

[0004] The above method is simple and effective when applied to an operation and maintenance system with a small number of nodes. However, in some business systems with a large number of nodes or a multi-level organizational structure, the above method consumes a large amount of resources, resulting in too high an operation and maintenance cost for the operation and maintenance system. Summary of the Invention

[0005] Embodiments of this application provide an operation and maintenance method, an operation and maintenance device, an operation and maintenance system, a computer-readable storage medium, and a computer program product, which can reduce the operation and maintenance cost of a complex business system.

[0006] In a first aspect, an operation and maintenance method is provided. The execution subject of this method can be an electronic device with central node functions or a chip with central node functions. The method includes: determining a first topological relationship of a first node set, where the first node set includes a first node and at least one second node, and the first topological relationship is used to indicate the reporting nodes of the operation and maintenance data of each node in the first node set. The reporting node of the operation and maintenance data of at least one second node is the first node, and the reporting node of the operation and maintenance data of the first node is the central node; generating first topological information according to the first topological relationship, where the first topological information is used to indicate the first topological relationship; and sending the first topological information to each node in the first node set.

[0007] The central node is a node responsible for managing the topology of the operation and maintenance system. When configuring the first topological relationship, the central node configures the first topological relationship as a multi-level relationship. The first node can receive and process the operation and maintenance data of the second node, reducing the resource pressure on the central node. In addition, when the topological relationship of the first node or the second node needs to be changed, or when a new node needs to be added to the operation and maintenance system, the central node only needs to adjust the topological relationship of a partial node set, without having to adjust the topological relationship of all nodes, reducing the deployment and maintenance costs of the operation and maintenance system.

[0008] Optionally, before determining the first topological relationship of the first node set, the method further includes: obtaining the feature information of multiple nodes; determining the first node set from the multiple nodes according to the feature information of the multiple nodes, where each node in the first node set has at least one same feature; determining the first topological relationship of the first node set, including: determining the first topological relationship according to the first node set.

[0009] The first node set can be a set of nodes located in the same region, or a set of nodes with other same features. Configuring the topological relationship by taking the nodes with at least one same feature as a set is conducive to the management of the operation and maintenance system and the reporting of operation and maintenance data.

[0010] Optionally, the method further includes: sending configuration information to each node in the first node set, where the configuration information is used to configure the operation and maintenance data reporting service of each node in the first node set.

[0011] The content of the configuration information can be set according to the current scenario or user requirements. By configuring the operation and maintenance data reporting service of each node in the first node set through the configuration information, it can flexibly adapt to different scenarios or user requirements.

[0012] Optionally, the method further includes: receiving management operation and maintenance data from the first node, where the management operation and maintenance data is operation and maintenance data determined based on the operation and maintenance data reported by at least one second node.

[0013] After the first node processes the operation and maintenance data reported by at least one second node, management operation and maintenance data is generated. The data volume of the management operation and maintenance data is small. The central node receiving the management operation and maintenance data can reduce the demand for bandwidth resources, thereby reducing the cost of the operation and maintenance system.

[0014] Optionally, the method further includes: obtaining change information, where the change information is used to change the topological relationship of the target node in the first node set; determining the second topological relationship according to the change information and the first topological relationship; generating second topological information according to the second topological relationship; sending the second topological information to each node in the first node set.

[0015] After the topological relationship of the target node changes, the first topological relationship also needs to be adjusted. The central node sends the second topological information to each node in the first node set, which can enable the operation and maintenance function of the first node set to run properly.

[0016] Optionally, the change information is used to change the topological relationship of the target node in the first node set, including: the change information is used to indicate that the target node transfers from the first node set to the second node set; the method further includes: determining a fourth topological relationship according to the change information and the third topological relationship, where the third topological relationship is the topological relationship of the second node set; generating third topological information according to the fourth topological relationship; and sending the third topological information to each node in the second node set.

[0017] When the target node transfers from the first node set to the second node set, the topological relationship of the second node set also changes accordingly. The central node adjusts the topological relationship of the second node set, which can enable the operation and maintenance function of the second node set to run properly.

[0018] In a second aspect, an operation and maintenance method is provided. The execution subject of this method can be an electronic device with a non-central node function or a chip with a central node function. The method includes: receiving first topological information from a central node, where the first topological information is used to indicate the first topological relationship of a first node set. The first node set includes a first node and at least one second node. The first topological relationship is used to indicate the reporting node of the operation and maintenance data of each node in the first node set. The reporting node of the operation and maintenance data of at least one second node is the first node, and the reporting node of the operation and maintenance data of the first node is the central node; determining a first reporting node according to the first topological information, where the first reporting node is the parent node of the non-central node; and sending the operation and maintenance data to the first reporting node.

[0019] The central node is a node responsible for managing the topological structure of the operation and maintenance system. When configuring the first topological relationship, the central node configures the first topological relationship as a multi-level relationship. The first node can receive and process the operation and maintenance data of the second node, reducing the resource pressure on the central node. In addition, when the topological relationship of the first node or the second node needs to be changed, or when a new node needs to be added to the operation and maintenance system, the central node only needs to adjust the topological relationship of part of the node set, and does not need to adjust the topological relationship of all nodes, reducing the deployment and maintenance costs of the operation and maintenance system.

[0020] Optionally, the method further includes: receiving configuration information from the central node, where the configuration information is used to configure the reporting service of the operation and maintenance data of each node in the first node set.

[0021] The content of the configuration information can be set according to the current scenario or user requirements. By configuring the reporting services of the operation and maintenance data of each node in the first node set through the configuration information, different scenarios or user requirements can be flexibly adapted.

[0022] Optionally, the first reporting node is a central node. Sending operation and maintenance data to the first reporting node includes: sending management operation and maintenance data to the central node, where the management operation and maintenance data is the operation and maintenance data determined based on the operation and maintenance data reported by at least one second node.

[0023] After the first node processes the operation and maintenance data reported by at least one second node, management operation and maintenance data is generated. The amount of data of the management operation and maintenance data is small. Sending the management operation and maintenance data to the central node can reduce the demand for bandwidth resources, thereby reducing the cost of the operation and maintenance system.

[0024] Optionally, the first reporting node is a central node, and the method further includes: determining the fifth topological relationship of the first node set; generating fourth topological information according to the fifth topological relationship, where the fourth topological information is used to indicate the fifth topological relationship; sending the fourth topological information to at least one second node.

[0025] In this embodiment, the first node can adjust the topological relationship of the first node set, which can reduce the operation and maintenance pressure on the central node. The first node can also send the fifth topological relationship to the central node to facilitate the central node to manage the entire operation and maintenance system.

[0026] Optionally, the method further includes: receiving second topological information from the central node, where the second topological information is used to indicate the second topological relationship of the first node set; determining a second reporting node according to the second topological relationship, where the second reporting node is the parent node of the non - central node; sending operation and maintenance data to the second reporting node.

[0027] After the topological relationship of the target node changes, the first topological relationship also needs to be adjusted. Each node in the first node set obtains the second topological information and adjusts the reporting node according to the second topological information, which can enable the normal operation of the operation and maintenance function of the first node set.

[0028] In a third aspect, an embodiment of the present application provides an operation and maintenance device. The device may include a communication unit and a processing unit, and is used to execute: any method in the first aspect and its optional embodiments, or any method in the second aspect and its optional embodiments.

[0029] In a fourth aspect, an embodiment of the present application provides an operation and maintenance device. The device may be an electronic device or a chip applied to an electronic device. The device may include a processor and is used to execute: any method in the first aspect and its optional embodiments, or any method in the second aspect and its optional embodiments.

[0030] Optionally, the device may further include a transceiver. When the device is an electronic device, the transceiver may be a transceiver circuit, an antenna, etc.; when the device is a chip applied to an electronic device, the transceiver may be an input / output interface, a pin, a circuit, etc.

[0031] Optionally, the device may further include a memory for storing instructions, and the processor executes the instructions stored in the memory to enable the device to execute: any method in the first aspect and its optional embodiments, or any method in the second aspect and its optional embodiments. When the device is an electronic device, the memory may be a read-only memory, a random access memory, etc.; when the device is a chip applied to an electronic device, the memory may be a register, a cache, etc.

[0032] In a fifth aspect, an embodiment of the present application provides an operation and maintenance system, which includes: an operation and maintenance device that executes any method in the first aspect and its optional embodiments, and an operation and maintenance device that executes any method in the second aspect and its optional embodiments.

[0033] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed on a computer, the computer is enabled to execute: any method in the first aspect and its optional embodiments, or any method in the second aspect and its optional embodiments.

[0034] In a seventh aspect, an embodiment of the present application provides a computer program product, which includes: computer program code or computer program instructions. When the computer program code or computer program instructions are run on a computer, the computer is enabled to execute: any method in the first aspect and its optional embodiments, or any method in the second aspect and its optional embodiments.

[0035] For the beneficial effects of the third aspect to the seventh aspect, reference may be made to the beneficial effects of the first aspect and the second aspect, which will not be elaborated here. Description of the Drawings

[0036] Figure 1 is a schematic diagram of an operation and maintenance scenario applicable to the present application;

[0037] Figure 2 is a schematic diagram of the architecture of an operation and maintenance system provided by an embodiment of the present application;

[0038] Figure 3 is a schematic diagram of an operation and maintenance method provided by an embodiment of the present application;

[0039] Figure 4 It is a schematic diagram of the architecture of another operation and maintenance system provided by an embodiment of the present application;

[0040] Figure 5 It is a schematic diagram of the architecture of yet another operation and maintenance system provided by an embodiment of the present application;

[0041] Figure 6 It is a schematic diagram of the architecture of yet another operation and maintenance system provided by an embodiment of the present application;

[0042] Figure 7 It is a schematic diagram of the architecture of yet another operation and maintenance system provided by an embodiment of the present application;

[0043] Figure 8 It is a schematic diagram of the structure of an operation and maintenance device provided by an embodiment of the present application;

[0044] Figure 9 It is a schematic diagram of the structure of another operation and maintenance device provided by an embodiment of the present application. Detailed implementation manners

[0045] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0046] Operation and maintenance, in essence, is the operation and maintenance of each stage of the life cycle of a network, server, or service, so that it reaches a consistent and acceptable state in terms of cost, stability, and efficiency. As an example, operation and maintenance can include various operations such as deploying an operating system and a running environment, deploying code, designing and deploying monitoring, preventing vulnerabilities and attacks, etc.

[0047] Figure 1 It is a schematic diagram of an operation and maintenance scenario applicable to the present application. The business system includes Node 1, Node 2, and Node 3. Node 1, Node 2, or Node 3 can be a terminal, a server, or a functional module (such as a software module or a hardware module). Embodiments of the present application do not limit the specific form of each node in the business system. The business system can also include more nodes.

[0048] Taking Node 1 as an example, Node 1 can be a mobile phone, a Pad, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a whole vehicle, a wireless communication module in a whole vehicle, a telematics box (T-box), a road site unit (RSU), a wireless terminal in autonomous driving, a smart speaker in IoT, a wireless user device in remote medical, a wireless user device in smart grid, a wireless user device in transportation safety, a wireless user device in smart city or a wireless user device in smart home.

[0049] By way of example and not limitation, Node 1 can also be a wearable device. A wearable device, also known as a wearable intelligent device, is a general term for devices developed by applying wearable technology to the intelligent design of daily wear, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is either directly worn on the body or integrated into the user's clothes or accessories. A wearable device is not just a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. Broadly speaking, wearable intelligent devices include electronic devices with complete functions, large sizes, and the ability to achieve complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, or electronic devices that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for measuring physical signs.

[0050] By way of example and not limitation, Node 1 can also be a server. For example, Node 1 can be a tower server, a blade server, a rack server or a cabinet server, or Node 1 can be a complex instruction set computer (CISC) server, a reduced instruction set computer (RISC) server or an explicitly parallel instruction computing (EPIC) server. Node 1 can also be a virtual server, such as a virtual machine (VM) or a container (docker).

[0051] Among the various nodes in the business system, communication can be carried out through wired connections or wireless connections. The wired connection can be an optical fiber or a cable, and the wireless connection can be a cellular network connection, wireless fidelity (WiFi), Bluetooth, or XingShan. Embodiments of this application do not limit the connection methods between the various nodes in the business system.

[0052] Node 1, Node 2, and Node 3 each include a business module and an operation and maintenance module. Among them, the business module and the operation and maintenance module can be set independently or integrated. Embodiments of this application do not limit the specific forms of the business module and the operation and maintenance module.

[0053] The business module is used to collect and process business data, and the operation and maintenance module is used to collect and process operation and maintenance data. The business data can be any one of the following types of data: Internet of Things (IoT) data, such as temperature, humidity, and pressure; financial data, such as stock prices, trading volumes, and exchange rates; commercial retail data, such as order transaction amounts, payment data, commodity inventories, and logistics data; industrial data, such as the real-time rotational speed, wind speed data, and power generation data of a wind turbine; artificial intelligence data, such as video, audio, and text data; energy and utility data, such as grid status and weather information; autonomous driving data, such as location and driving status; scientific research data, such as seismic data and biological data. The operation and maintenance data can be metrics, logs, events, and alarms, etc.

[0054] The above descriptions of business data and operation and maintenance data are examples rather than limitations. Embodiments of this application do not limit the specific contents of business data and operation and maintenance data.

[0055] Node 1, Node 2, and Node 3 can send the operation and maintenance data to the operation and maintenance device for automatic operation and maintenance, or the operation and maintenance engineer can perform operation and maintenance through the operation and maintenance device. Optionally, the operation and maintenance device can also be integrated with the nodes in the business system.

[0056] According to the different locations of the operation and maintenance engineer when performing operation and maintenance tasks, operation and maintenance can be divided into on-site operation and maintenance and remote operation. As an optional example, on-site operation and maintenance means that the operation and maintenance engineer performs operation and maintenance in the customer's computer room or data center, and remote operation means that the service provider or a third-party agency performs operation and maintenance on the customer's infrastructure (such as information technology (IT) infrastructure or communication technology (CT) infrastructure) or computing environment (such as a cloud computing environment or an edge computing environment) through remote access.

[0057] Remote operation and maintenance is usually realized based on an operation and maintenance terminal on the proximal side and an operation terminal on the distal side. Here, the proximal side refers to the customer side, including the customer's computer room or data center, and the distal side refers to the remote operation center side. The remote operation center is the place where the service provider or a third-party organization performs remote operation and maintenance. According to different security requirement levels, the remote operation center can configure an operation and maintenance environment separately for each customer of remote operation and maintenance, or multiple customers of remote operation and maintenance can share the remote operation and maintenance environment.

[0058] The operation and maintenance terminal is used to perform operation and maintenance on the equipment in the customer's computer room or data center. The operation and maintenance terminal is also called a bastion host and a jump host. The remote operation and maintenance engineer can connect to the operation and maintenance terminal based on the operation terminal through communication protocols such as remote desktop for command input and screen output observation, so as to realize remote operation and maintenance. Among them, the operation terminal can be an operation and maintenance workstation, and the operation and maintenance workstation can be a personal computer or a server installed with remote operation and maintenance software.

[0059] Whether it is on-site operation and maintenance or remote operation and maintenance, it is necessary to manage each node in the business system. An optional method is to specify a central node in the operation and maintenance system, and the central node manages the non-central nodes. For example, the non-central nodes collect operation and maintenance data through the Agent component and report the operation and maintenance data to the central node through the API. This method is very convenient when building an operation and maintenance system for a small number of nodes. Deploying an operation and maintenance system for a small number of nodes can quickly complete the operation and maintenance of the nodes. However, in the operation and maintenance of business systems involving a large number of nodes or a multi-level organizational structure, it is very difficult to quickly complete the overall construction of the above method, and a large amount of work needs to be done for adaptation, resulting in low efficiency. In addition, in the operation and maintenance of business systems involving a large number of nodes or a multi-level organizational structure, when a new node needs to be added to the business system, or when a node needs to be removed, the entire operation and maintenance system needs to be adjusted adaptively, resulting in an increase in operation and maintenance costs.

[0060] According to the function, the operation and maintenance system can be divided into Figure 2The architecture shown. This architecture includes an operation and maintenance topology management module, an operation and maintenance topology monitoring and parsing module, an operation and maintenance data collection module, and an operation and maintenance data reporting module. Among them, the operation and maintenance topology management module is the module of the central node, responsible for managing the topology structure of the operation and maintenance system, including generating topology relationships according to the organizational structure and adjusting topology relationships according to organizational management requirements; the operation and maintenance topology monitoring and parsing module, the operation and maintenance data collection module, and the operation and maintenance data reporting module are non-central node modules. The operation and maintenance topology monitoring and parsing module is responsible for monitoring the topology relationships published by the central node, obtaining the topology relationships through the monitoring mechanism and parsing them, and synchronizing the parsed reporting node addresses to the operation and maintenance data reporting module; the operation and maintenance data collection module is responsible for collecting operation and maintenance data, such as logs, metrics, etc.; the operation and maintenance data reporting module is responsible for reporting the operation and maintenance data collected by the operation and maintenance data collection module to the reporting node. The reporting node can be the central node or a non-central node, and operation and maintenance engineers can perform operation and maintenance operations on the reporting node.

[0061] Figure 2 Each of the modules shown can be implemented by hardware, software, or a combination of both. Different modules can be integrated or set independently.

[0062] Next, the operation and maintenance method provided by the embodiments of the present application will be introduced. As Figure 3 shown, method 300 includes the following content.

[0063] S310, determine the first topology relationship of the first node set. The first node set includes a first node and at least one second node. The first topology relationship is used to indicate the reporting nodes of the operation and maintenance data of each node in the first node set. The reporting node of the operation and maintenance data of at least one second node is the first node, and the reporting node of the operation and maintenance data of the first node is the central node.

[0064] The first node or the second node can be called a non-central node. Among them, the first node is a child node of the central node, and the second node is a child node of the first node.

[0065] The first node set is, for example, Figure 1 nodes 1, 2, and 3 in. Optionally, node 1 is the central node, node 2 is the first node, and node 3 is the second node.

[0066] Optionally, when the business system includes more nodes, the first node set can Figure 4 the node set in the operation and maintenance system shown. Figure 4Among them, the central node, Region A, Region B, Region C, Factory 1, Factory 2, Factory 3, Factory 4, Factory 5, and Factory 6 are all nodes of the operation and maintenance system. Region A, Factory 1, and Factory 2 form a node set. Among them, Region A is an example of the first node, and Factory 1 and Factory 2 are examples of at least one second node. Region B, Factory 3, Factory 4, and Factory 5 form a node set. Among them, Region B is an example of the first node, and Factory 3, Factory 4, and Factory 5 are examples of at least one second node. Region C and Factory 6 form a node set. Among them, Region C is an example of the first node, and Factory 6 is an example of at least one second node.

[0067] Figure 4 Among them, the connections between each node represent the reporting paths of operation and maintenance data. For the node set where Region A is located, the reporting node for the operation and maintenance data of Factory 1 and Factory 2 is Region A, and the reporting node for the operation and maintenance data of Region A is the central node. For the node set where Region B is located, the reporting nodes for the operation and maintenance data of Factory 3, Factory 4, and Factory 5 are Region B, and the reporting node for the operation and maintenance data of Region B is the central node. For the node set where Region C is located, the reporting node for the operation and maintenance data of Factory 6 is Region C, and the reporting node for the operation and maintenance data of Region C is the central node.

[0068] Figure 4 Among them, each node contains an operation and maintenance module. Optionally, Factory 1, Factory 2, Factory 3, Factory 4, Factory 5, and Factory 6 contain business modules.

[0069] It should be noted that Figure 4 these are examples rather than limitations. The operation and maintenance system can also have more nodes and more levels. As Figure 5 shown, the node set where Region A is located also includes Branch Factory 1 and Branch Factory 2. Both Branch Factory 1 and Branch Factory 2 contain operation and maintenance modules. Optionally, Branch Factory 1 and Branch Factory 2 also contain business modules (the modules contained in Branch Factory 1 and Branch Factory 2 are not shown in Figure 5 the figure). As the lower-level nodes of Factory 2, Branch Factory 1 and Branch Factory 2 can report operation and maintenance data to Factory 2. The central node can configure the topological relationship for Branch Factory 1 and Branch Factory 2.

[0070] Optionally, a non-central node can share some management functions for the central node, adjust the topological relationship of the lower-level nodes managed by this non-central node, and relieve the operation and maintenance pressure on the central node. The non-central node can report the adjusted topological relationship to the central node to facilitate the central node to manage the entire operation and maintenance system.

[0071] For example, for Figure 5For the operation and maintenance system shown, Region A, as the upper-level node of Factory 1, Factory 2, Branch Factory 1, and Branch Factory 2, can adjust the topological relationships of Factory 1, Factory 2, Branch Factory 1, and Branch Factory 2. As an optional example, Region A can adjust the reporting node of Branch Factory 1 from Factory 2 to Factory 1 or Region A, or Region A can delete Factory 1 from the topological relationship; Region A can report the adjusted topological relationship to the central node. Factory 2, as the upper-level node of Branch Factory 1 and Branch Factory 2, can adjust the topological relationships of Branch Factory 1 and Branch Factory 2. As an optional example, Factory 2 can delete Branch Factory 2 from the topological relationship; Factory 2 can report the adjusted topological relationship to the central node, or Factory 2 can report the adjusted topological relationship to Region A, and Region A reports it to the central node.

[0072] Optionally, the central node can determine the first topological relationship in the following way: obtain the feature information of multiple nodes, determine the first node set from the multiple nodes according to the feature information of the multiple nodes, and each node in the first node set has at least one same feature; determine the first topological relationship according to the first node set.

[0073] As an optional example, as Figure 4 shown, the multiple nodes can be Region A, Region B, Region C, Factory 1, Factory 2, Factory 3, Factory 4, Factory 5, and Factory 6. Among them, Region A, Factory 1, and Factory 2 are nodes located in Region 1, Region B, Factory 3, Factory 4, and Factory 5 are nodes located in Region 2, and Region C and Factory 6 are nodes located in Region 3. Then the central node can divide Region A, Factory 1, and Factory 2 into one node set according to the regional features of each node, divide Region B, Factory 3, Factory 4, and Factory 5 into another node set, and divide Region C and Factory 6 into yet another node set.

[0074] The central node can also divide each node in the operation and maintenance system into different node sets according to other features of the nodes. Configuring the topological relationship with nodes having at least one same feature as a set is beneficial to the management of the operation and maintenance system and the reporting of operation and maintenance data.

[0075] After the central node determines the first topological relationship, it can execute S320 and S330.

[0076] S320, generate first topological information according to the first topological relationship, and the first topological information is used to indicate the first topological relationship.

[0077] The first topological information can be any kind of information used to indicate the first topological relationship, and the embodiments of the present application do not limit the specific form of the first topological information.

[0078] Optionally, the central node may also send configuration information to each node in the first node set, and the configuration information is used to configure the operation and maintenance data reporting service of each node in the first node set.

[0079] For example, for Region A, the configuration information may be the information for configuring the address of the central node, and Region A may report operation and maintenance data to this address. For Factory 1, the configuration information may be the information for configuring the address of Region A, and Factory 1 may report operation and maintenance data to this address.

[0080] The configuration information may also configure the types of operation and maintenance data reported by each node. For example, the configuration information may configure Region A to report management operation and maintenance data, and configure Factory 1 to report non-management operation and maintenance data. Among them, the non-management operation and maintenance data may be metrics, logs, events, alarms, etc., and the management operation and maintenance data may be statistical data obtained based on the non-management operation and maintenance data.

[0081] The content of the configuration information can be set according to the current scenario or user requirements. By configuring the operation and maintenance data reporting service of each node in the node set through the configuration information, different scenarios or user requirements can be flexibly adapted.

[0082] S330, send the first topology information to each node in the first node set.

[0083] Correspondingly, each node (i.e., non-central node) in the first node set receives the first topology information from the central node.

[0084] In the operation and maintenance system, there is a communication connection between adjacent upper-level nodes and lower-level nodes, and there may or may not be a communication connection between other nodes.

[0085] Such as Figure 4As shown, for Region A and the central node, Region A is the subordinate node and the central node is the superior node. Moreover, these two nodes are adjacent nodes, so there is a communication connection between Region A and the central node. Region A and Region B are not in the relationship of superior node and subordinate node. There may or may not be a communication connection between Region A and Region B. For Region A and Factory 1, Region A is the superior node and Factory 1 is the subordinate node. Moreover, these two nodes are adjacent nodes, so there is a communication connection between Region A and Factory 1. For Region A and Factory 2, Region A is the superior node and Factory 2 is the subordinate node. Moreover, these two nodes are adjacent nodes, so there is a communication connection between Region A and Factory 2. Factory 1 and Factory 2 are not in the relationship of superior node and subordinate node. There may or may not be a communication connection between Factory 1 and Factory 2. Factory 1 and the central node are not adjacent superior and subordinate nodes. There may or may not be a communication connection between Factory 1 and the central node. Factory 2 and the central node are not adjacent superior and subordinate nodes. There may be a communication connection between Factory 2 and the central node. If there is no communication connection between the central node and Factory 1, the central node can forward the first topology relationship to Factory 1 through Region A. If there is a communication connection between the central node and Factory 1, the central node can forward the first topology relationship to Factory 1 through Region A, or directly send the first topology relationship to Factory 1.

[0086] The above communication connection can be a wired connection or a wireless connection. The wired connection can be an optical fiber or a cable, and the wireless connection can be a cellular network connection, WiFi, Bluetooth, or XingShan. The embodiments of the present application do not limit the connection methods between various nodes in the operation and maintenance system.

[0087] After receiving the first topology information, the non - central node can execute S340 and S350.

[0088] S340, determine the first reporting node according to the first topology information. The first reporting node is the parent node of the non - central node.

[0089] The parent node of the non - central node is the adjacent superior node to the non - central node. If the non - central node is the first node, the first reporting node is the central node. If the non - central node is the second node, the first reporting node is the first node. As an optional example, as Figure 5 shown, if the non - central node is Region A, the first reporting node is the central node. If the non - central node is Factory 1, the first reporting node is Region A. If the non - central node is Branch Factory 1, the first reporting node is Factory 1.

[0090] S350, send the operation and maintenance data to the first reporting node.

[0091] As can be seen from the above, in method 300, the central node is the node responsible for managing the topology of the operation and maintenance system. When configuring the first topology relationship, the central node configures the first topology relationship as a multi-level relationship. The first node can receive and process the operation and maintenance data of the second node, reducing the resource pressure on the central node (such as computing resource pressure and transmission bandwidth pressure). Since the first node shares some functions of the central node, method 300 has higher reliability compared to the method of completely managing the operation and maintenance system by the central node. In addition, when the topology relationship of the first node or the second node needs to be changed, or when a new node needs to be added to the operation and maintenance system, the central node only needs to adjust the topology relationship of a partial node set, without having to adjust the topology relationship of all nodes, reducing the deployment and maintenance costs of the operation and maintenance system.

[0092] Optionally, when the non-central node is the first node, method 300 further includes: the central node receives management operation and maintenance data from the first node, and the management operation and maintenance data is operation and maintenance data determined based on the operation and maintenance data reported by at least one second node.

[0093] After the first node processes the operation and maintenance data reported by at least one second node, management operation and maintenance data is generated. The amount of data of the management operation and maintenance data is smaller. The central node receiving the management operation and maintenance data can reduce the demand for bandwidth resources, thereby reducing the cost of the operation and maintenance system.

[0094] As an optional example, as Figure 5 shown, Region A can receive multiple events from Factory 1 and Factory 2. Region A can count the multiple events, determine the number of events, and report the number of events to the central node. Among them, the multiple events received by Region A are examples of the operation and maintenance data reported by the second node, and the number of events reported by Region A is an example of the management operation and maintenance data. The number of events occupies less transmission bandwidth than the multiple events, thereby reducing the cost of the operation and maintenance system.

[0095] Optionally, in method 300, after the central node sends the first topology information, the following steps can also be performed: obtaining change information, where the change information is used to change the topology relationship of the target node in the first node set; determining the second topology relationship according to the change information and the first topology relationship; generating second topology information according to the second topology relationship; and sending the second topology information to each node in the first node set.

[0096] After the topology relationship of the target node changes, the first topology relationship also needs to be adjusted. The central node sending the second topology information to each node in the first node set can enable the normal operation of the operation and maintenance functions of the first node set.

[0097] As an optional example, as Figure 4As shown, Region A, Factory 1, and Factory 2 form the first node set. The topological relationship among Region A, Factory 1, and Factory 2 is the first topological relationship. According to user requirements, Branch Factory 1 (an example of a target node) and Branch Factory 2 (an example of a target node) need to be added to the first node set. Then, the operation and maintenance personnel can input change information on the central node to add Branch Factory 1 and Branch Factory 2 to the first node set. The central node determines the second topological relationship based on the change information and the first topological relationship. The second topological relationship is as shown in Figure 5 the topological relationship among Region A, Factory 1, Factory 2, Branch Factory 1, and Branch Factory 2. The central node can generate the second topological information based on the second topological relationship and send the second topological information to each node in the first node set, that is, send the second topological information to Region A, Factory 1, Factory 2, Branch Factory 1, and Branch Factory 2. Branch Factory 1 and Branch Factory 2 start reporting operation and maintenance data to Region A, so that the operation and maintenance function of the first node set operates normally.

[0098] As an optional example, as shown in Figure 4 Region B, Factory 3, Factory 4, and Factory 5 form the first node set. The topological relationship among Region B, Factory 3, Factory 4, and Factory 5 is the first topological relationship. According to user requirements, Factory 5 (an example of a target node) needs to be removed from the first node set. Then, the operation and maintenance personnel can input change information on the central node to delete Factory 5 from the child nodes of Region B. The central node determines the second topological relationship based on the change information and the first topological relationship. The second topological relationship is as shown in Figure 6 the topological relationship among Region B, Factory 3, and Factory 4. The central node can generate the second topological information based on the second topological relationship and send the second topological information to each node in the first node set, that is, send the second topological information to Region B, Factory 3, and Factory 4. Region B no longer manages Factory 5, so that the operation and maintenance function of the first node set operates normally. If Factory 5 does not join other node sets after being removed from the first node set, the central node can send a command to Factory 5 to stop reporting operation and maintenance data or disable the operation and maintenance function, instructing Factory 5 to stop reporting operation and maintenance data.

[0099] Optionally, the change information is used to change the topological relationship of the target node in the first node set, including: the change information is used to indicate that the target node transfers from the first node set to the second node set. Then, in method 300, the central node can also execute: determining the fourth topological relationship according to the change information and the third topological relationship, where the third topological relationship is the topological relationship of the second node set; generating the third topological information according to the fourth topological relationship; sending the third topological information to each node in the second node set.

[0100] When the target node transfers from the first node set to the second node set, the topological relationship of the second node set also changes accordingly. The central node adjusts the topological relationship of the second node set, which can enable the normal operation of the operation and maintenance function of the second node set.

[0101] As an optional example, as Figure 4 shown, Region B, Factory 3, Factory 4, and Factory 5 form the first node set, and Region C and Factory 6 form the second node set. According to user requirements, Factory 5 needs to be a sub-node of Region C and be managed by Region C. The operation and maintenance personnel can input change information on the central node to transfer Factory 5 (an example of the target node) from the first node set to the second node set. The central node determines the fourth topological relationship based on the change information and the third topological relationship. The third topological relationship is as Figure 4 shown by the topological relationship between Region C and Factory 6 in Figure 7 The fourth topological relationship is as shown by the topological relationship between Region C, Factory 6, and Factory 5 in shown by the topological relationship between Region C, Factory 6, and Factory 5 in

[0102] The above text has introduced in detail the method examples provided by the embodiments of the present application. It can be understood that for the corresponding device to implement the above functions, it includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0103] Figure 8 FIG. 16 is a schematic structural diagram of an operation and maintenance device 800 provided by an embodiment of the present application. The device 800 includes a processing unit 810 and a communication unit 820. The communication unit 820 executes the receiving step or the input step under the control of the processing unit 810.

[0104] When the device 800 is used to implement the function of the central node, the processing unit 810 is used to: determine the first topological relationship of the first node set, the first node set includes a first node and at least one second node, and the first topological relationship is used to indicate the reporting nodes of the operation and maintenance data of each node in the first node set. The reporting node of the operation and maintenance data of at least one second node is the first node, and the reporting node of the operation and maintenance data of the first node is the central node; generate first topological information according to the first topological relationship, and the first topological information is used to indicate the first topological relationship; the communication unit 820 is used to: send the first topological information to each node in the first node set.

[0105] Optionally, the processing unit 810 is specifically used to: obtain the feature information of multiple nodes; determine the first node set from the multiple nodes according to the feature information of the multiple nodes, and each node in the first node set has at least one same feature; determine the first topological relationship according to the first node set.

[0106] Optionally, the communication unit 820 is further used to: send configuration information to each node in the first node set, and the configuration information is used to configure the operation and maintenance data reporting service of each node in the first node set.

[0107] Optionally, the communication unit 820 is further used to: receive management operation and maintenance data from the first node, and the management operation and maintenance data is the operation and maintenance data determined based on the operation and maintenance data reported by at least one second node.

[0108] Optionally, the processing unit 810 is further used to: obtain change information, and the change information is used to change the topological relationship of the target node in the first node set; determine the second topological relationship according to the change information and the first topological relationship; generate second topological information according to the second topological relationship; the communication unit 820 is further used to: send the second topological information to each node in the first node set.

[0109] Optionally, the change information is used to change the topological relationship of the target node in the first node set, including: the change information is used to indicate that the target node transfers from the first node set to the second node set; the processing unit 810 is further used to: determine the fourth topological relationship according to the change information and the third topological relationship, and the third topological relationship is the topological relationship of the second node set; generate third topological information according to the fourth topological relationship; the communication unit 820 is further used to: send the third topological information to each node in the second node set.

[0110] When the device 800 is used to implement the function of a non-central node, the communication unit 820 is configured to: receive first topology information from the central node, where the first topology information is used to indicate the first topological relationship of a first node set, the first node set includes a first node and at least one second node, the first topological relationship is used to indicate the reporting node of the operation and maintenance data of each node in the first node set, the reporting node of the operation and maintenance data of at least one second node is the first node, and the reporting node of the operation and maintenance data of the first node is the central node; the processing unit 810 is configured to: determine a first reporting node according to the first topology information, where the first reporting node is the parent node of the non-central node; the communication unit 820 is further configured to: send the operation and maintenance data to the first reporting node.

[0111] Optionally, the communication unit 820 is further configured to: receive configuration information from the central node, where the configuration information is used to configure the reporting service of the operation and maintenance data of each node in the first node set.

[0112] Optionally, the first reporting node is the central node, and the communication unit 820 is specifically configured to: send management operation and maintenance data to the central node, where the management operation and maintenance data is operation and maintenance data determined based on the operation and maintenance data reported by at least one second node.

[0113] Optionally, the first reporting node is the central node, and the processing unit 810 is further configured to: determine a fifth topological relationship of the first node set; generate fourth topology information according to the fifth topological relationship, where the fourth topology information is used to indicate the fifth topological relationship; the communication unit 820 is further configured to: send the fourth topology information to at least one second node.

[0114] Optionally, the communication unit 820 is further configured to: receive second topology information from the central node, where the second topology information is used to indicate the second topological relationship of the first node set; the processing unit 810 is further configured to: determine a second reporting node according to the second topological relationship, where the second reporting node is the parent node of the non-central node; the communication unit 820 is further configured to: send the operation and maintenance data to the second reporting node.

[0115] Those skilled in the art can clearly understand the specific working process of the device 800 and the technical effects generated by the execution steps, and can refer to the description in the corresponding method embodiments mentioned above. For the sake of brevity, it will not be repeated here.

[0116] The device 800 can be a server or a chip. The processing unit 810 can be implemented by hardware or software. When implemented by hardware, the processing unit 810 can be a logic circuit, an integrated circuit, etc.; when the processing unit 810 is implemented by software, the processing unit 810 can be a general-purpose processor, which is implemented by reading the software code stored in the storage unit. The storage unit can be integrated in the processing unit 810 or exist independently outside the processing unit 810.

[0117] Figure 9 It is a schematic structural diagram of another operation and maintenance device provided by an embodiment of the present application. For the sake of convenience of description, Figure 9 only the main components of the operation and maintenance device are shown. As Figure 9 shown, the device 900 includes a processor 910, a memory 920, and an input / output device 930. The processor 910 is mainly used to process operation and maintenance system-related commands and operation and maintenance data, and to control the entire device 900, execute software programs, and process the data of software programs, for example, to support the device 900 to perform the actions described in the above method embodiments. The memory 920 is mainly used to store software programs and data. The input / output device 930 is, for example, a network card, an antenna, etc., and is mainly used to receive data and output data. The processor 910, the memory 920, and the input / output device 930 can be connected through a bus.

[0118] The processor 910 and the memory 920 can serve one or more single boards. That is to say, a memory and a processor can be separately provided on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits can be provided on each single board.

[0119] Those skilled in the art can understand that, for the sake of convenience of description, Figure 9 only one memory and one processor are shown. In an actual server, there can be multiple processors and multiple memories. The memory can also be referred to as a storage medium or a storage device, etc., and the present application does not make any limitations thereto.

[0120] It can be understood that the processors in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or instructions in software form. The above-mentioned processor can be a central processing unit (CPU), a system on chip (SoC), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a micro controller unit (MCU), a programmable logic device (PLD), or other logic devices, such as discrete gates, transistor logic devices, or discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application.

[0121] It can be understood that the memories in the embodiments of the present application can be volatile memories or non-volatile memories, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that the memories in the systems and methods described herein are intended to include but not be limited to these and any other suitable types of memories.

[0122] In the implementation process, the steps of the above method can be completed by the integrated logic circuit in the hardware of the processor or the instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware processor, or can be executed and completed by the combination of the hardware and software modules in the processor. The software module can be located in a random register, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register and other mature storage media in the art. This storage media is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

[0123] The present application also provides a computer-readable medium, on which a computer program is stored, and when the computer program is executed by the computer, it realizes the functions of any one of the above method embodiments.

[0124] The present application also provides a computer program product, and when the computer program product is executed by the computer, it realizes the functions of any one of the above method embodiments.

[0125] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (such as infrared, wireless, or microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, or magnetic tape), an optical medium (such as a high-density digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0126] It should be understood that the "embodiments" mentioned throughout the specification mean that specific features, structures, or characteristics related to the embodiments are included in at least one embodiment of the present application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the terminal device and / or network device can execute some or all of the steps in the embodiments. These steps or operations are only examples, and the embodiments of the present application can also execute other operations or various deformations of the operations. In addition, the various steps can be executed in different orders presented in the embodiments, and it is possible not to execute all the operations in the embodiments of the present application. Moreover, the magnitudes of the sequence numbers of the above processes do not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0127] It should also be understood that in the present application, "when...", "if", and "in case" all mean that the execution subject will perform corresponding processing under certain objective circumstances, not limited to time, and it is not required that the execution subject must have a judgment action when implemented, nor does it mean there are other limitations.

[0128] In addition, the terms "system" and "network" in this document are often used interchangeably herein. The term "and / or" in this document is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone.

[0129] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0130] The above content is an optional embodiment of the technical solution of the present application and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the principle of the present application shall be included in the protection scope of the present application.

Claims

1. An operation and maintenance method, characterized in that, The method is applied to a central node, and the method includes: Determine a first topological relationship of a first node set, where the first node set includes a first node and at least one second node, and the first topological relationship is used to indicate the reporting nodes of the operation and maintenance data of each node in the first node set. The reporting node of the operation and maintenance data of the at least one second node is the first node, and the reporting node of the operation and maintenance data of the first node is the central node; Generate first topological information according to the first topological relationship, where the first topological information is used to indicate the first topological relationship; Send the first topological information to each node in the first node set.

2. The method according to claim 1, characterized in that, Before determining the first topological relationship of the first node set, the method further includes: Obtain the characteristic information of multiple nodes; Determine the first node set from the multiple nodes according to the characteristic information of the multiple nodes, and each node in the first node set has at least one same characteristic; The determining of the first topological relationship of the first node set includes: Determine the first topological relationship according to the first node set.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Send configuration information to each node in the first node set, where the configuration information is used to configure the operation and maintenance data reporting service of each node in the first node set.

4. The method according to any one of claims 1 to 3, characterized in that The method further includes: Receive management operation and maintenance data from the first node, where the management operation and maintenance data is operation and maintenance data determined based on the operation and maintenance data reported by the at least one second node.

5. The method according to any one of claims 1 to 4, characterized in that The method further includes: Obtain change information, where the change information is used to change the topological relationship of a target node in the first node set; Determine a second topological relationship according to the change information and the first topological relationship; Generate second topological information according to the second topological relationship; Send the second topological information to each node in the first node set.

6. The method according to claim 5, wherein The change information is used to change the topological relationship of a target node in the first node set, including: the change information is used to indicate that the target node transfers from the first node set to a second node set; The method further includes: Determine a fourth topological relationship according to the change information and a third topological relationship, where the third topological relationship is the topological relationship of the second node set; Generate third topological information according to the fourth topological relationship; Send the third topological information to each node in the second node set.

7. An operation and maintenance method, characterized in that, The method is applied to a non - central node, and the method includes: Receive first topological information from a central node, where the first topological information is used to indicate a first topological relationship of a first node set, the first node set includes a first node and at least one second node, the first topological relationship is used to indicate the reporting nodes of the operation and maintenance data of each node in the first node set. The reporting node of the operation and maintenance data of the at least one second node is the first node, and the reporting node of the operation and maintenance data of the first node is the central node; Determine a first reporting node according to the first topological information, where the first reporting node is the parent node of the non - central node; Send operation and maintenance data to the first reporting node.

8. The method according to claim 7, wherein The method further includes: Receive configuration information from the central node, where the configuration information is used to configure the operation and maintenance data reporting services of each node in the first node set.

9. The method according to claim 7 or 8, characterized in that, The first reporting node is the central node, and the sending of operation and maintenance data to the first reporting node includes: Send management operation and maintenance data to the central node, where the management operation and maintenance data is operation and maintenance data determined based on the operation and maintenance data reported by the at least one second node.

10. The method according to any one of claims 7 to 9, characterized in that The first reporting node is the central node, and the method further includes: Determine the fifth topological relationship of the first node set; Generate fourth topological information according to the fifth topological relationship, where the fourth topological information is used to indicate the fifth topological relationship; Send the fourth topological information to the at least one second node.

11. The method according to any one of claims 7 to 10, characterized in that, The method further includes: Receive second topological information from the central node, where the second topological information is used to indicate the second topological relationship of the first node set; Determine a second reporting node according to the second topological relationship, where the second reporting node is the parent node of the non-central node; Send operation and maintenance data to the second reporting node.

12. An operation and maintenance device, characterized in that, The device includes: A module for executing the method according to any one of claims 1 to 11.

13. An operation and maintenance device, characterized in that, Includes: A processor and an interface circuit, where the interface circuit is used to receive signals from other devices and transmit them to the processor or send signals from the processor to other devices, and the processor is used to implement the method according to any one of claims 1 to 11 through logic circuits or by executing code instructions.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instruction, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 1 to 11 is implemented.

15. An operation and maintenance system, characterized in that, The system includes: An operation and maintenance system management device for executing the method according to any one of claims 1 to 6, and an operation and maintenance system management device for executing the method according to any one of claims 7 to 11.

Images