Fault positioning method, fault positioning equipment, target network element and device

Abstract

The invention provides a fault positioning method, fault positioning equipment, a target network element and a device, the method is applied to the fault positioning equipment, the fault positioning equipment is connected with a plurality of network topology structures, the plurality of network topology structures comprise respective network elements, and the method comprises the following steps: responding to a fault positioning instruction; determining a fault collection file of a target network element to be positioned; sending the fault collection file to the target network element, wherein the fault collection file is used for the target network element to generate fault index data; receiving the fault index data sent by the target network element; and carrying out fault positioning on the target network element according to the fault index data. According to the scheme provided by the invention, the influence on the normal service of each network element in the network topology structure can be reduced, and the fault positioning efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a fault location method, a fault location device, a target network element and a device. Background Art

[0002] With the commercial advancement of 5G networks, peripheral networking has become more complex and diverse. If some network elements fail during networking, the normal operation of the entire network will be affected. Therefore, it is necessary to promptly discover and locate network element failures.

[0003] At present, the fault location of network elements is mainly achieved by analyzing logs. The source of logs is the hard-coded records made by R&D personnel during the software coding process. In the case of a fault in the network, the R&D personnel modify the software coding, and then upgrade the network elements in the network through the version release process. After the upgrade, reset each network element, control each network element to work again, reproduce the fault, and then extract the log of the network element based on the modified code, and locate the fault of the network element based on the newly extracted log.

[0004] The above fault location solution requires repeated updates and upgrades of versions, and resets of network elements in the network. These operations have a significant impact on normal services of the network, and the efficiency of fault location is low. Summary of the invention

[0005] The present application provides a fault location method, a fault location device, a target network element and a device to improve the efficiency of fault location.

[0006] In a first aspect, the present application provides a fault location method, which is applied to a fault location device, wherein the fault location device is connected to a plurality of network topology structures, and the plurality of network topology structures include respective network elements, and the method includes:

[0007] In response to the fault location instruction, determining a fault collection file of a target network element to be located;

[0008] Sending the fault collection file to the target network element, where the fault collection file is used by the target network element to generate fault indicator data;

[0009] Receiving the fault indicator data sent by the target network element;

[0010] The target network element is fault located according to the fault indicator data.

[0011] In a possible implementation manner, the determining, in response to the fault location instruction, a fault collection file of a target network element to be located includes:

[0012] In response to a first selection instruction for a network topology, selecting a target network topology from among the multiple network topologies, the target network topology including the target network element;

[0013] In response to a second selection instruction for a network element included in the target network topology structure, determining the target network element from the network elements included in the target network topology structure;

[0014] The fault collection file is generated in response to a configuration instruction for the target network element, wherein the fault location instruction includes the first selection instruction, the second selection instruction and the configuration instruction.

[0015] In a possible implementation manner, the generating the fault collection file in response to the configuration instruction for the target network element includes:

[0016] Determine, according to the category of the target network element and the position of the target network element in the target network topology, a collection information set of the target network element, wherein the collection information set includes a plurality of to-be-selected collection information of the target network element;

[0017] In response to the configuration instruction for the collection information set, determining the target collection information of the target network element from the plurality of to-be-selected collection information;

[0018] The fault collection file is generated according to the target collection information.

[0019] In a possible implementation, the collection information set includes a collection content set and a trigger condition set; and the determining, in response to the configuration instruction for the collection information set, the target collection information of the target network element from the multiple selected collection information includes:

[0020] In response to a first configuration instruction for the collection content set, determining a target collection content from a plurality of to-be-selected collection contents included in the collection content set;

[0021] Determine at least one of the candidate trigger conditions included in the trigger condition set that matches the target acquisition content;

[0022] In response to a second configuration instruction for the at least one selected trigger condition, a target trigger condition is determined among the at least one selected trigger condition; the configuration instruction includes the first configuration instruction and the second configuration instruction, and the target acquisition information includes the target acquisition content and the target trigger condition.

[0023] In a possible implementation manner, generating the fault collection file according to the target collection information includes:

[0024] According to the type of the target network element, acquiring an executable program corresponding to the target network element, wherein the executable program includes the plurality of to-be-selected collection information;

[0025] Generate a program configuration file of the target network element according to the target acquisition information, wherein the program configuration file is used to indicate the target acquisition information among the multiple pieces of collection information to be selected;

[0026] The fault collection file is generated according to the executable program and the program configuration file.

[0027] In a possible implementation manner, acquiring the executable program corresponding to the target network element according to the category of the target network element includes:

[0028] Get the initial acquisition program;

[0029] Determining, according to the category of the target network element, a cross-compilation chain matching the target network element;

[0030] The initial acquisition program is compiled according to the cross-compilation chain to generate the executable program.

[0031] In a possible implementation, the method further includes:

[0032] In response to a first editing instruction for the collection content set, acquiring newly added collection content of the target network element;

[0033] In response to a second editing instruction for the trigger condition set, acquiring a newly added trigger condition of the target network element;

[0034] The collection content set and the trigger condition set are updated according to the newly added collection content and the newly added trigger condition.

[0035] In a possible implementation manner, the sending the fault collection file to the target network element includes:

[0036] Obtaining the IP address of the target network element;

[0037] The fault collection file is sent to the target network element according to the IP address of the target network element.

[0038] In a second aspect, the present application provides a fault location method, which is applied to a target network element in a target network topology structure, wherein the target network topology structure is connected to a fault location device, and the method includes:

[0039] Receiving the fault collection file sent by the fault location device;

[0040] Generating fault indicator data of the target network element according to the fault collection file;

[0041] The fault indicator data is sent to the fault locating device, where the fault indicator data is used to locate the fault of the target network element.

[0042] In a possible implementation manner, generating the fault indicator data of the target network element according to the fault collection file includes:

[0043] According to the fault collection file, an executable program corresponding to the target network element and a program configuration file of the target network element are acquired, wherein the executable program includes a plurality of to-be-selected collection information, and the program configuration file is used to indicate the target collection information among the plurality of to-be-selected collection information;

[0044] The executable program is run according to the target collection information indicated by the program configuration file to generate the fault indicator data.

[0045] In a third aspect, the present application provides a fault location device, including a memory, a transceiver, and a processor;

[0046] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0047] In response to the fault location instruction, determining a fault collection file of a target network element to be located;

[0048] Sending the fault collection file to the target network element, where the fault collection file is used by the target network element to generate fault indicator data;

[0049] Receiving the fault indicator data sent by the target network element;

[0050] The target network element is fault located according to the fault indicator data.

[0051] In a possible implementation manner, the determining, in response to the fault location instruction, a fault collection file of a target network element to be located includes:

[0052] In response to a first selection instruction for a network topology structure, selecting a target network topology structure from a plurality of network topologies connected to the fault location, the target network topology structure including the target network element;

[0053] In response to a second selection instruction for a network element included in the target network topology structure, determining the target network element from the network elements included in the target network topology structure;

[0054] The fault collection file is generated in response to a configuration instruction for the target network element, wherein the fault location instruction includes the first selection instruction, the second selection instruction and the configuration instruction.

[0055] In a possible implementation manner, the generating the fault collection file in response to the configuration instruction for the target network element includes:

[0056] Determine, according to the category of the target network element and the position of the target network element in the target network topology, a collection information set of the target network element, wherein the collection information set includes a plurality of to-be-selected collection information of the target network element;

[0057] In response to the configuration instruction for the collection information set, determining the target collection information of the target network element from the plurality of to-be-selected collection information;

[0058] The fault collection file is generated according to the target collection information.

[0059] In a possible implementation, the collection information set includes a collection content set and a trigger condition set; and the determining, in response to the configuration instruction for the collection information set, the target collection information of the target network element from the multiple selected collection information includes:

[0060] In response to a first configuration instruction for the collection content set, determining a target collection content from a plurality of to-be-selected collection contents included in the collection content set;

[0061] Determine at least one of the candidate trigger conditions included in the trigger condition set that matches the target acquisition content;

[0062] In response to a second configuration instruction for the at least one selected trigger condition, a target trigger condition is determined among the at least one selected trigger condition; the configuration instruction includes the first configuration instruction and the second configuration instruction, and the target acquisition information includes the target acquisition content and the target trigger condition.

[0063] In a possible implementation manner, generating the fault collection file according to the target collection information includes:

[0064] According to the type of the target network element, acquiring an executable program corresponding to the target network element, wherein the executable program includes the plurality of to-be-selected collection information;

[0065] Generate a program configuration file of the target network element according to the target acquisition information, wherein the program configuration file is used to indicate the target acquisition information among the multiple pieces of collection information to be selected;

[0066] The fault collection file is generated according to the executable program and the program configuration file.

[0067] In a possible implementation manner, acquiring the executable program corresponding to the target network element according to the category of the target network element includes:

[0068] Get the initial acquisition program;

[0069] Determining, according to the category of the target network element, a cross-compilation chain matching the target network element;

[0070] The initial acquisition program is compiled according to the cross-compilation chain to generate the executable program.

[0071] In a possible implementation manner, the processor is further configured to read the computer program in the memory and perform the following operations:

[0072] In response to a first editing instruction for the collection content set, acquiring newly added collection content of the target network element;

[0073] In response to a second editing instruction for the trigger condition set, acquiring a newly added trigger condition of the target network element;

[0074] The collection content set and the trigger condition set are updated according to the newly added collection content and the newly added trigger condition.

[0075] In a possible implementation manner, the sending the fault collection file to the target network element includes:

[0076] Obtaining the IP address of the target network element;

[0077] The fault collection file is sent to the target network element according to the IP address of the target network element.

[0078] In a fourth aspect, the present application provides a target network element, including a memory, a transceiver, and a processor;

[0079] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0080] Receiving a fault collection file sent by a fault location device, wherein the target network element is a network element in a target network topology structure, and the target network topology structure is connected to the fault location device;

[0081] Generating fault indicator data of the target network element according to the fault collection file;

[0082] The fault indicator data is sent to the fault locating device, where the fault indicator data is used to locate the fault of the target network element.

[0083] In a possible implementation manner, generating the fault indicator data of the target network element according to the fault collection file includes:

[0084] According to the fault collection file, an executable program corresponding to the target network element and a program configuration file of the target network element are acquired, wherein the executable program includes a plurality of to-be-selected collection information, and the program configuration file is used to indicate the target collection information among the plurality of to-be-selected collection information;

[0085] The executable program is run according to the target collection information indicated by the program configuration file to generate the fault indicator data.

[0086] In a fifth aspect, the present application provides a fault location device, which is applied to a fault location device, wherein the fault location device is connected to a plurality of network topologies, and the plurality of network topologies include respective network elements, and the device includes:

[0087] A determination module, configured to determine a fault collection file of a target network element to be located in response to a fault location instruction;

[0088] A first sending module, configured to send the fault collection file to the target network element, wherein the fault collection file is used by the target network element to generate fault indicator data;

[0089] A first receiving module, configured to receive the fault indicator data sent by the target network element;

[0090] A fault location module is used to locate the fault of the target network element according to the fault indicator data.

[0091] In a possible implementation manner, the determining module is specifically configured to:

[0092] In response to a first selection instruction for a network topology, selecting a target network topology from among the multiple network topologies, the target network topology including the target network element;

[0093] In response to a second selection instruction for a network element included in the target network topology structure, determining the target network element from the network elements included in the target network topology structure;

[0094] The fault collection file is generated in response to a configuration instruction for the target network element, wherein the fault location instruction includes the first selection instruction, the second selection instruction and the configuration instruction.

[0095] In a possible implementation manner, the determining module is specifically configured to:

[0096] Determine, according to the category of the target network element and the position of the target network element in the target network topology, a collection information set of the target network element, wherein the collection information set includes a plurality of to-be-selected collection information of the target network element;

[0097] In response to the configuration instruction for the collection information set, determining the target collection information of the target network element from the plurality of to-be-selected collection information;

[0098] The fault collection file is generated according to the target collection information.

[0099] In a possible implementation manner, the collection information set includes a collection content set and a trigger condition set; and the determination module is specifically configured to:

[0100] In response to a first configuration instruction for the collection content set, determining a target collection content from a plurality of to-be-selected collection contents included in the collection content set;

[0101] Determine at least one of the candidate trigger conditions included in the trigger condition set that matches the target acquisition content;

[0102] In response to a second configuration instruction for the at least one selected trigger condition, a target trigger condition is determined among the at least one selected trigger condition; the configuration instruction includes the first configuration instruction and the second configuration instruction, and the target acquisition information includes the target acquisition content and the target trigger condition.

[0103] In a possible implementation manner, the determining module is specifically configured to:

[0104] According to the type of the target network element, acquiring an executable program corresponding to the target network element, wherein the executable program includes the plurality of to-be-selected collection information;

[0105] Generate a program configuration file of the target network element according to the target acquisition information, wherein the program configuration file is used to indicate the target acquisition information among the multiple pieces of collection information to be selected;

[0106] The fault collection file is generated according to the executable program and the program configuration file.

[0107] In a possible implementation manner, the determining module is specifically configured to:

[0108] Get the initial acquisition program;

[0109] Determining, according to the category of the target network element, a cross-compilation chain matching the target network element;

[0110] The initial acquisition program is compiled according to the cross-compilation chain to generate the executable program.

[0111] In a possible implementation manner, the determining module is further configured to:

[0112] In response to a first editing instruction for the collection content set, acquiring newly added collection content of the target network element;

[0113] In response to a second editing instruction for the trigger condition set, acquiring a newly added trigger condition of the target network element;

[0114] The collection content set and the trigger condition set are updated according to the newly added collection content and the newly added trigger condition.

[0115] In a possible implementation manner, the first sending module is specifically configured to:

[0116] Obtaining an Internet Protocol (IP) address of the target network element;

[0117] The fault collection file is sent to the target network element according to the IP address of the target network element.

[0118] In a sixth aspect, the present application provides a fault location device, which is applied to a target network element in a target network topology structure, wherein the target network topology structure is connected to a fault location device, and the device includes:

[0119] A second receiving module, used for receiving the fault collection file sent by the fault location device;

[0120] A generating module, used to generate fault indicator data of the target network element according to the fault collection file;

[0121] The second sending module is used to send the fault indicator data to the fault locating device, where the fault indicator data is used to locate the fault of the target network element.

[0122] In a possible implementation, the generating module is specifically used for:

[0123] According to the fault collection file, an executable program corresponding to the target network element and a program configuration file of the target network element are acquired, wherein the executable program includes a plurality of to-be-selected collection information, and the program configuration file is used to indicate the target collection information among the plurality of to-be-selected collection information;

[0124] The executable program is run according to the target collection information indicated by the program configuration file to generate the fault indicator data.

[0125] In a seventh aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the fault location method described in any one of the first aspect or the second aspect.

[0126] The fault location method, fault location device, target network element and device provided by the present application are applied to the fault location device, the fault location device is connected to multiple network topology structures, and the multiple network topology structures include their own network elements; the fault location device responds to the fault location instruction, determines the fault collection file of the target network element to be located, and then sends the fault collection file to the target network element, the fault collection file is used to generate fault indicator data for the target network element, and the generated fault indicator data is sent by the target network element to the fault location device, and the fault location device can locate the fault of the target network element based on the fault indicator data. The scheme of the present application does not need to repeatedly release updated versions, nor does it need to reset each network element. Instead, it can directly generate a fault collection file according to the target network element to be located to collect fault indicator data, thereby realizing fault location, reducing the downtime of the network element, reducing the impact on the normal business of each network element in the network topology structure, and improving the efficiency of fault location. BRIEF DESCRIPTION OF THE DRAWINGS

[0127] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0128] Figure 1 This is a schematic diagram of the networking structure in a single peripheral scenario;

[0129] Figure 2 This is a schematic diagram of the network structure in the indoor distribution scenario;

[0130] Figure 3 This is a schematic diagram of the networking structure in a multi-mode scenario;

[0131] Figure 4 This is a schematic diagram of the networking structure in a cascade scenario;

[0132] Figure 5 A schematic diagram of a flow chart of a fault location method provided in an embodiment of the present application;

[0133] Figure 6A schematic diagram of a process for determining a fault collection file of a target network element provided in an embodiment of the present application;

[0134] Figure 7 A schematic diagram of determining a target network element provided in an embodiment of the present application;

[0135] Figure 8 A schematic diagram of a process for generating a fault collection file based on a configuration instruction provided in an embodiment of the present application;

[0136] Fig. 9 A schematic diagram of fault collection for the executable program and program configuration file provided in the embodiment of the present application;

[0137] Fig.10 A schematic diagram of the working cycle of an executable program provided in an embodiment of the present application;

[0138] Fig.11 A schematic diagram of the structure of a fault location device provided in an embodiment of the present application;

[0139] Fig.12 A schematic diagram of the structure of a target network element provided in an embodiment of the present application;

[0140] Fig.13 A schematic diagram of the structure of a fault location device provided in an embodiment of the present application;

[0141] Fig.14 A schematic diagram of the structure of a fault location device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0142] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in this application will be clearly and completely described below in conjunction with the drawings in this application. Obviously, the described embodiments are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0143] Networking refers to the network topology structure formed by connecting various network elements with certain connection relationships. Each network element works independently and together provides communication services for the networking.

[0144] In networking, if some network elements fail, it will affect the normal operation of the entire network. Therefore, it is very necessary to discover and locate the failure of network elements in a timely manner.

[0145] At present, the fault location of network elements is mainly achieved by analyzing logs. The source of the logs is the hard-coded records made by R&D personnel during the software coding process. In the case of a fault in the network, when the log information is not sufficient to meet the fault location requirements, the R&D personnel modify the software coding, and then upgrade the network elements in the network through the version release process. After the upgrade, reset each network element, control each network element to work again, reproduce the fault, and then extract the log of the network element based on the modified code, and locate the fault of the network element based on the newly extracted log. After the problem is located, the R&D personnel delete the relevant positioning code that is no longer used in the software.

[0146] However, in the existing network environment, due to business development needs and product cost considerations, there are situations where multi-standard and multi-model peripherals coexist and are used. Compared with the early simple situation of a baseband board connected to a single peripheral, various scenarios such as cascading, indoor distribution, and multi-mode coexist, and the network topology and interaction processes are relatively complex.

[0147] Figures 1 to 4 The networking structures in several different scenarios are exemplified. The networks include multiple network elements. The interface between the network elements is the interface between the RRU and the BBU (Ir).

[0148] Figure 1 This is a schematic diagram of the network structure in a single peripheral scenario, such as Figure 1 As shown, the networking structure in a single peripheral scenario includes a baseband unit (BBU) and a radio remote unit (RRU), and the BBU and the RRU are connected.

[0149] Figure 2 This is a schematic diagram of the network structure in the indoor distribution scenario. Figure 2 As shown, the networking structure in the indoor distribution scenario includes a BBU and at least one remote radio unit hub (RHUB), each RHUB is connected to the BBU, and each RHUB is connected to at least one pico remote radio unit (pRRU).

[0150] Figure 3 is a schematic diagram of the network structure in a multi-mode scenario, such as Figure 3 As shown, the networking structure in a multi-mode scenario includes a central control unit (CCU), the CCU is connected to multiple BBUs, and each BBU is connected to an RRU or an active antenna unit (AAU).

[0151] Figure 4 The following is a schematic diagram of the network structure in a cascade scenario. Figure 4 As shown, the networking structure in the cascade scenario includes a BBU, the BBU is connected to multiple RRUs, and different numbers of RRUs are distributed on each branch and connected in sequence.

[0152] like Figures 1 to 4 As shown in the figure, with the commercial advancement of 5G networks, peripheral networking situations are becoming more complex and diverse. In various scenarios such as 4 / 5G coexistence, indoor distribution, and multi-mode, AAU, RRU, RHUB, pRRU, etc. work together. The network element types are different, the interaction process is complex, and it is difficult to locate faults.

[0153] As the network topology of current peripherals becomes more and more complex, the above-mentioned method of upgrading and resetting the network elements in the network through version release to locate the fault has defects, mainly including the following aspects:

[0154] First, the method of recording fault location information through logs in the code is inefficient. Due to the complexity of the current networking environment, the existing hard-coded logging methods are difficult to meet the needs of obtaining fault location information. Often, as fault location progresses, after providing a location version, it is found that there is still information that needs to be supplemented, and the location version needs to be updated repeatedly. And each release requires a series of subsequent operations, resulting in low efficiency in fault location.

[0155] Second, the fault location process has a great impact on normal business. The replacement of the location version requires the upgrading and resetting of the equipment in the network to reproduce the fault, which has a great impact on normal business development.

[0156] Third, the fault location information is not accurate. The pre-installed logs in the upgraded version are just simple records, which are difficult to highlight the problem and have poor effect in extracting effective information.

[0157] Based on this, the embodiment of the present application provides a fault location solution, which reduces the impact of the location behavior on the existing network by automatically deploying and installing the location program and collecting location information triggered by the problem, thereby achieving the purpose of improving the efficiency of fault resolution and improving the operation stability. The solution of the embodiment of the present application is introduced below in conjunction with the accompanying drawings.

[0158] Figure 5 A schematic diagram of a flow chart of a fault location method provided in an embodiment of the present application, wherein the method is applied to a fault location device, wherein the fault location device is connected to multiple network topologies, wherein the multiple network topologies include respective network elements, such as Figure 5 As shown, the method includes:

[0159] S51, in response to a fault locating instruction, determining a fault collection file of a target network element to be located.

[0160] The execution subject of the embodiment of the present application is a fault location device, which is an electronic device. The fault location device is connected to multiple network topologies and is a peripheral device independent of the multiple network topologies. The fault location device can manage multiple network topologies.

[0161] The network topology structure in the embodiment of the present application is a networking structure formed by various types of network elements with certain connection relationships. For any network topology structure, the network topology structure can be as follows: Figure 1 The network structure in the example single peripheral scenario can be as follows Figure 2 The networking structure in the example indoor distribution scenario can be as follows Figure 3 The network structure in the multi-mode scenario can be Figure 4 The networking structure in the cascade scenario of the example may also be a combination of networking structures in different scenarios, which is not limited in the embodiments of the present application. Each network topology structure includes its own network element, and the connection relationship of the network element is set according to actual needs.

[0162] When fault location is required, a fault location instruction is sent by controlling the fault location device. The fault location device responds to the fault location instruction and determines the fault collection file of the target network element to be located.

[0163] The target network element is a network element in a certain network topology structure connected to the fault location device, and the target network element is a network element that may have a fault. In order to locate the fault of the target network element, it is necessary to first determine the target network element and then determine the fault collection file of the target network element.

[0164] The fault location of the target network element includes two aspects: one is to determine whether the target network element actually has a fault; the other is to determine the type of fault in the target network element if the target network element actually has a fault.

[0165] The fault collection file of the target network element is a file used to collect the fault indicator data of the target network element. The corresponding fault collection file can be determined according to the possible faults of the target network element and the connection relationship between the target network element and other network elements in the network topology. For example, if there is a communication failure between the target network element and a certain network element, the fault collection file can be an executable program, and the executable program will collect the communication data between the target network element and the network element as the fault indicator data during operation; for example, if there is an operation failure in the target network element, the fault collection file can be an executable program, and the executable program will collect the operation data of the target network element as the fault indicator data during operation, and so on.

[0166] S52, sending a fault collection file to a target network element, where the fault collection file is used by the target network element to generate fault indicator data.

[0167] After generating the fault collection file of the target network element, the fault location device sends the fault collection file to the target network element. The target network element receives the fault collection file sent by the fault location device and generates fault indicator data of the target network element according to the fault collection file. For example, if the fault collection file is an executable program, the target network element runs the executable program to generate corresponding fault indicator data.

[0168] S53, receiving fault indicator data sent by the target network element.

[0169] After generating the fault indicator data, the target network element sends the fault indicator data to the fault locating device, and the fault locating device receives the fault indicator data sent by the target network element.

[0170] S54, locating the fault of the target network element according to the fault indicator data.

[0171] The fault indicator data is used to locate the fault of the target network element. After receiving the fault indicator data, the fault location device can locate the fault of the target network element based on the fault indicator data. The fault indicator data may include the operation log of the target network element, the communication data between the target network element and other network elements, and other possible data. Based on these data, it can be determined whether the target network element has a fault, and if the target network element has a fault, the type of fault in the target network element can be determined.

[0172] The fault location method provided in the embodiment of the present application is applied to a fault location device, the fault location device is connected to multiple network topology structures, and the multiple network topology structures include respective network elements; the fault location device responds to the fault location instruction, determines the fault collection file of the target network element to be located, and then sends the fault collection file to the target network element, the fault collection file is used to generate fault indicator data for the target network element, the generated fault indicator data is sent by the target network element to the fault location device, and the fault location device can locate the fault of the target network element based on the fault indicator data. The scheme of the embodiment of the present application does not need to repeatedly release updated versions, nor does it need to reset each network element, but directly generates a fault collection file according to the target network element to be located to collect fault indicator data, so as to realize fault location, reduce the downtime of the network element, reduce the impact on the normal business of each network element in the network topology structure, and improve the efficiency of fault location.

[0173] The solution of the embodiment of the present application is further introduced below with reference to the accompanying drawings.

[0174] First combine Figure 6 This section describes the process of determining fault collection files.

[0175] Figure 6 A schematic diagram of a process for determining a fault collection file of a target network element provided in an embodiment of the present application, such as Figure 6 As shown, including:

[0176] S61, in response to a first selection instruction for a network topology structure, selecting a target network topology structure from a plurality of network topologies, where the target network topology structure includes a target network element.

[0177] The fault location device is connected to multiple network topology structures and can manage the multiple network topology structures. Therefore, the connection relationship of the multiple network topology structures is also stored inside the fault location device.

[0178] Among the multiple network topologies connected to the fault location device, a target network topology can be selected through a first selection instruction. The fault location device responds to the first selection instruction for the network topology and determines the target network topology among the multiple network topologies, and the target network topology is the network topology that needs to be subsequently fault located.

[0179] Optionally, the first selection instruction may be an interface interaction instruction. For example, multiple network topologies connected to the fault locating device may be displayed on the display screen of the fault locating device, and the user may select a target network topology from the multiple network topologies by interacting with the interface of the fault locating device.

[0180] Optionally, the first selection instruction may be a key instruction. For example, the fault locating device includes a key corresponding to each network topology structure, and the user selects a target network topology structure from multiple network topologies by operating the corresponding key.

[0181] The first selection instruction may also be other possible instruction forms. The embodiments of the present application only introduce interface interaction instructions and key instructions as examples. Any instruction that can select a target network topology structure from multiple network topologies can be the first selection instruction.

[0182] S62: In response to a second selection instruction for network elements included in the target network topology structure, determine a target network element from the network elements included in the target network topology structure.

[0183] After determining the target network topology, it is necessary to select a target network element to be located in the target network topology. The target network element is a network element for which fault location is required subsequently.

[0184] The target network element may be selected from among the multiple network elements included in the target network topology structure by a second selection instruction. The fault location device determines the target network element from among the network elements included in the target network topology structure in response to the second selection instruction for the network elements included in the target network topology structure.

[0185] Optionally, the second selection instruction may be an interface interaction instruction. For example, multiple network elements in the target network topology may be displayed on the display screen of the fault locating device, and the user may select the target network element from the multiple network elements by interacting with the interface of the fault locating device.

[0186] Optionally, the second selection instruction may be a key instruction. For example, the fault location device includes a key corresponding to each network element in the network topology structure, and the user selects a target network element from multiple network elements by operating the corresponding key.

[0187] The second selection instruction may also be other possible instruction forms. The embodiments of the present application only introduce interface interaction instructions and button instructions as examples. Any instruction that can select a target network element from multiple network elements can be the second selection instruction.

[0188] Figure 7 A schematic diagram of determining a target network element provided in an embodiment of the present application, such as Figure 7 As shown, taking the second selection instruction as an interface interaction instruction as an example, the target network topology is illustrated on the interface. The target network topology includes a CCU, 3 BBUs, 1 AAU, 1 RRU, 1 RHUB and 1 pRRU. The connection relationship between multiple network elements can be seen in Figure 7 Examples in .

[0189] exist Figure 7 In the example, each network element has its own collection point location, including location 1 corresponding to CCU, location 2, location 4 and location 6 corresponding to the three BBUs, location 3 corresponding to AAU, location 5 corresponding to RRU, location 7 corresponding to RHUB, and location 8 corresponding to pRRU. If in the form of interface interaction, these 8 locations can be 8 controls, and the interface interaction is performed in the form of controls to select the corresponding target network element.

[0190] S63, generating a fault collection file in response to a configuration instruction for the target network element, wherein the fault location instruction includes a first selection instruction, a second selection instruction, and a configuration instruction.

[0191] The fault location instruction includes a first selection instruction and a second selection instruction. The first selection instruction determines the target network topology structure, and the second selection instruction determines the target network element in the target network topology structure. The fault location instruction also includes a configuration instruction, which is used to generate a fault collection file for the target network element. Figure 8 This section introduces the process.

[0192] Figure 8 A schematic diagram of a process for generating a fault collection file based on a configuration instruction provided in an embodiment of the present application, such as Figure 8 As shown, including:

[0193] S81, determining a collection information set of the target network element according to the type of the target network element and the position of the target network element in the target network topology structure, wherein the collection information set includes a plurality of to-be-selected collection information of the target network element.

[0194] For any network element, the collection information set of the network element includes multiple collection information to be selected for the network element, and the collection information of different network elements includes different collection information to be selected. The collection information to be selected included in the collection information set of the network element is associated with the category of the network element and the position of the network element in the corresponding network topology structure.

[0195] In the embodiment of the present application, for different categories of network elements, possible to-be-selected collection information of network elements of each category may be pre-set as a collection template.

[0196] The collection information set may include a collection content set and a trigger condition set, wherein the collection content set includes multiple collection contents to be selected, and the selected collection contents may include, for example, signaling information, register information, input / output (I / O) information of the device, etc.; the trigger condition set includes multiple trigger conditions to be selected, and the selected trigger conditions may include, for example, a specified trigger time, a specified trigger event, etc.

[0197] Network elements of different categories and network elements at different locations may involve different collection contents and trigger conditions to be selected. For any network element, the collection content set and trigger condition set of the network element can be pre-set according to the collection contents and trigger conditions that it may involve, forming the collection information set of the network element.

[0198] In a possible implementation, if new collection content and / or new trigger conditions appear, they can also be edited and saved. Specifically, the fault location device responds to the first editing instruction for the collection content set to obtain the newly added collection content of the target network element; responds to the second editing instruction for the trigger condition set to obtain the newly added trigger condition of the target network element, and updates the collection content set and trigger condition set of the target network element according to the newly added collection content and the newly added trigger condition, that is, the newly added collection content is added to the collection content set of the target network element, and the newly added trigger condition is added to the trigger condition set of the target network element. In this way, the editing of collection content and trigger conditions can be realized to expand the applicability of fault location.

[0199] For the target network element, the collection information set of the target network element can be determined according to the category of the target network element and the position of the target network element in the target network topology structure. The collection information set includes multiple collection information to be selected of the target network element. The multiple collection information to be selected include multiple collection contents to be selected and multiple trigger conditions to be selected.

[0200] S82: In response to the configuration instruction for the collection information set, determine target collection information of a target network element from a plurality of collection information to be selected.

[0201] The configuration instruction includes a first configuration instruction and a second configuration instruction, wherein the first configuration instruction is used to determine the target acquisition content, and the second configuration instruction is used to determine the target trigger condition, and the target acquisition information includes the target acquisition content and the target trigger condition.

[0202] Specifically, the fault location device determines the target collection content from the multiple collection contents to be selected included in the collection content set in response to the first configuration instruction for the collection content set of the target network element. The first configuration instruction may be an interface interaction instruction or a key instruction, which is not limited in this embodiment.

[0203] After the target acquisition content is determined, the trigger conditions involved in the target acquisition content are certain. Therefore, at least one candidate trigger condition matching the target acquisition content can be determined from among the multiple candidate trigger conditions included in the trigger condition set. Then, the fault location device responds to the second configuration instruction for the at least one candidate trigger condition and determines the target trigger condition from among the at least one candidate trigger condition.

[0204] S83, generating a fault collection file according to the target collection information.

[0205] The fault location device first obtains the executable program corresponding to the target network element according to the type of the target network element, and the executable program includes a plurality of collection information to be selected.

[0206] Specifically, the fault location device first obtains the initial acquisition program, and then determines the cross-compilation chain that matches the target network element according to the category of the target network element. In an embodiment of the present application, the initial acquisition program can be automatically deployed on each network element and can be run without installation on various system environments. For the initial acquisition program, the software environment that matches the target network element can be determined according to the category of the target network element, and then the cross-compilation chain that matches the target network element is determined based on the software environment that matches the target network element. Then, the initial acquisition program is compiled according to the cross-compilation chain to obtain an executable program corresponding to the target network element.

[0207] Optionally, if the executable program of this version has been compiled, you can also skip the compilation and directly download the corresponding executable program. If the executable program already exists on the target network element, you can just update the configuration. In this way, when the fault location means is adjusted, there is no need to upgrade the version and reset. Depending on the adjustment situation, you can just replace the collection configuration file or the executable program.

[0208] After obtaining the executable program corresponding to the target network element, a program configuration file of the target network element is generated according to the target collection information, and the program configuration file is used to indicate the target collection information of the target network element in multiple collection information to be selected. Then, a fault collection file of the target network element is generated according to the executable program and the program configuration file.

[0209] Fig. 9 A schematic diagram of fault collection for the executable program and program configuration file provided in the embodiment of the present application, such as Fig. 9 As shown, the program configuration file consists of the main program interface part, information collection, information sending, information storage and collection configuration as the program configuration file.

[0210] The main program interface part is used to connect with the main program of the target network element. On the one hand, it reports its own existence and version information to the main program of the target network element; on the other hand, it receives commands issued by the main program of the target network element, such as receiving and configuring various acquisition-related information and related information for sending data to the receiver.

[0211] The content to be collected includes signaling information, register information (also called Field Programmable Gate Array (FPGA) register information) and device I / O information. The collection method varies with the data source: the collection of signaling information adopts the interception and forwarding copy method to monitor the Ir messages between the baseband board and the peripherals, and also monitors the custom messages between the network elements; the collection of FPGA register information adopts the internal embedding method of the register read and write function to monitor the register changes; the collection of device I / O information adopts the internal embedding method of the command word read and write function to monitor the input / output management (input / output control, ioctl) operations.

[0212] Information transmission uses socket communication and the User Datagram Protocol (UDP) protocol. The destination IP address and port can be configured, and different ports are used to distinguish each information collection. The peer receives multiple ports, which requires the corresponding port configurations of both parties. In terms of data collection filtering, filtering can be performed through configuration. Signaling collection can be configured with source, destination address, protocol type, and signaling type; register information collection can be configured with processor and read / write operation type; device I / O information collection can be configured with command word and read / write operation type.

[0213] Taking the problem of locating lost heartbeats as an example, the heartbeat message of RRU No. 171 of the Ir protocol can be collected. For example, to locate the delay measurement problem of the main and auxiliary optical ports when AAU is cross-connected, register information is collected on two BBUs (BBU in slot 2 is connected to the main optical port 0, and BBU in slot 3 is connected to the auxiliary optical port 1), and the contents of register 0x80 of BBU in slot 2 and register 0x81 of BBU in slot 3 are collected. For example, to locate the problem of bit errors at the RF optical port, the read information of the custom extended command word 0x2009 on the BBU is collected. Information storage is used as local storage when the conditions for sending are not met. The overwrite write mode is used to record in the specified storage space. The collection configuration file records the collection trigger, end condition, and collection content. After being loaded by the executable program, it is executed according to the configuration. When the configuration changes, it can be reloaded by the executable program and the collection work is performed according to the new configuration content.

[0214] That is to say, the executable program includes various related execution programs for the selected collection content and the selected trigger conditions. However, for the target network element, it is only necessary to collect the target collection content under the target trigger conditions. Therefore, the program configuration file generated according to the target collection information is used to instruct the execution of the program in the executable program for collecting the target collection content under the target trigger conditions.

[0215] After generating the fault collection file based on the executable program and the program configuration file, the fault location device sends the fault collection file to the target network element. Specifically, the fault location device obtains the IP address of the target network element, uses it as the download target address, and then sends the fault collection file to the target network element according to the IP address of the target network element.

[0216] The target network element receives the fault collection file sent by the fault locating device, and generates the fault indicator data of the target network element according to the fault collection file. Specifically, the target network element obtains the executable program corresponding to the target network element and the program configuration file of the target network element according to the fault collection file, wherein the executable program includes multiple collection information to be selected, and the program configuration file is used to indicate the target collection information among the multiple collection information to be selected; then, according to the target collection information indicated by the program configuration file, the executable program is run to generate the fault indicator data. Finally, the target network element sends the fault indicator data to the fault locating device, and the fault indicator data is used to locate the fault of the target network element.

[0217] For the life cycle of the executable program, if there is no special designation, information collection will continue until the fault location device receives a stop command. The collection time period can also be pre-specified, and a combination of the start time, collection duration, or end time can be specified.

[0218] Fig.10 A schematic diagram of the working cycle of an executable program provided in an embodiment of the present application is shown in FIG. Fig.10 As shown, the fault location device can be pre-configured with an executable program, and the executable program is run by the target network element to achieve the collection of target collection content.

[0219] The fault location device can create a collection timer, start the collection when the start time arrives, and stop the collection when the collection duration or end time point is reached. The fault location device can also specify trigger conditions, collect the collection content when the trigger conditions are met, or stop the collection of the collection content when the trigger conditions are met, such as using alarms and register query content to trigger the collection operation of the collection content.

[0220] Taking the pRRU access fault location as an example, under the existing technical means, R&D personnel may conventionally locate on the BBU based on their own judgment, and then may add RHUB and pRRU location, but may miss the processing on the CCU, and will modify and upgrade different small versions of multiple network elements, which is a lot of work, and is prone to new errors. The upgrade positioning period will also affect the service for a long time. However, the solution of the embodiment of the present application does not require code modification, version upgrade and device reset. For access faults, the deployment template can be referred to under the technical accumulation, and it can be deployed on the relevant network elements at one time, only collecting access-related Ir signaling and transparent signaling, focusing on problem location, and providing standardized information for subsequent analysis, so as to achieve the purpose of improving positioning efficiency.

[0221] In summary, the solution of the embodiment of the present application does not need to repeatedly release updated versions, nor does it need to reset each network element. Instead, it automatically deploys executable programs and directly generates fault collection files based on the target network element to be located to collect fault indicator data, thereby realizing fault location, reducing the downtime of the network element, reducing the impact on the normal business of each network element in the network topology, and improving the efficiency of fault location. Moreover, the collection content, trigger conditions, and collection time can be adjusted according to actual needs, with high flexibility.

[0222] Fig.11 A schematic diagram of a fault location device provided in an embodiment of the present application is shown in FIG. Fig.11 As shown, the fault location device includes a memory 1120, a transceiver 1100, and a processor 1110, wherein:

[0223] The memory 1120 is used to store computer programs; the transceiver 1100 is used to send and receive data under the control of the processor 1110; the processor 1110 is used to read the computer program in the memory 1120 and perform the following operations:

[0224] In response to the fault location instruction, determining a fault collection file of a target network element to be located;

[0225] Sending the fault collection file to the target network element, where the fault collection file is used by the target network element to generate fault indicator data;

[0226] Receiving the fault indicator data sent by the target network element;

[0227] The target network element is fault located according to the fault indicator data.

[0228] Among them, Fig.11 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1110 and various circuits of memory represented by memory 1120 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1100 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and other transmission media. For different user devices, the user interface 1130 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0229] The processor 1110 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1110 when performing operations.

[0230] In some embodiments, the processor 1110 may be a CPU, an ASIC, an FPGA, or a CPLD, and the processor may also adopt a multi-core architecture.

[0231] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0232] In a possible implementation manner, the determining, in response to the fault location instruction, a fault collection file of a target network element to be located includes:

[0233] In response to a first selection instruction for a network topology structure, selecting a target network topology structure from a plurality of network topologies connected to the fault location, the target network topology structure including the target network element;

[0234] In response to a second selection instruction for a network element included in the target network topology structure, determining the target network element from the network elements included in the target network topology structure;

[0235] The fault collection file is generated in response to a configuration instruction for the target network element, wherein the fault location instruction includes the first selection instruction, the second selection instruction and the configuration instruction.

[0236] In a possible implementation manner, the generating the fault collection file in response to the configuration instruction for the target network element includes:

[0237] Determine, according to the category of the target network element and the position of the target network element in the target network topology, a collection information set of the target network element, wherein the collection information set includes a plurality of to-be-selected collection information of the target network element;

[0238] In response to the configuration instruction for the collection information set, determining the target collection information of the target network element from the plurality of to-be-selected collection information;

[0239] The fault collection file is generated according to the target collection information.

[0240] In a possible implementation, the collection information set includes a collection content set and a trigger condition set; and the determining, in response to the configuration instruction for the collection information set, the target collection information of the target network element from the multiple selected collection information includes:

[0241] In response to a first configuration instruction for the collection content set, determining a target collection content from a plurality of to-be-selected collection contents included in the collection content set;

[0242] Determine at least one of the candidate trigger conditions included in the trigger condition set that matches the target acquisition content;

[0243] In response to a second configuration instruction for the at least one selected trigger condition, a target trigger condition is determined among the at least one selected trigger condition; the configuration instruction includes the first configuration instruction and the second configuration instruction, and the target acquisition information includes the target acquisition content and the target trigger condition.

[0244] In a possible implementation manner, generating the fault collection file according to the target collection information includes:

[0245] According to the type of the target network element, acquiring an executable program corresponding to the target network element, wherein the executable program includes the plurality of to-be-selected collection information;

[0246] Generate a program configuration file of the target network element according to the target acquisition information, wherein the program configuration file is used to indicate the target acquisition information among the multiple pieces of collection information to be selected;

[0247] The fault collection file is generated according to the executable program and the program configuration file.

[0248] In a possible implementation manner, acquiring the executable program corresponding to the target network element according to the category of the target network element includes:

[0249] Get the initial acquisition program;

[0250] Determining, according to the category of the target network element, a cross-compilation chain matching the target network element;

[0251] The initial acquisition program is compiled according to the cross-compilation chain to generate the executable program.

[0252] In a possible implementation manner, the processor is further configured to read the computer program in the memory and perform the following operations:

[0253] In response to a first editing instruction for the collection content set, acquiring newly added collection content of the target network element;

[0254] In response to a second editing instruction for the trigger condition set, acquiring a newly added trigger condition of the target network element;

[0255] The collection content set and the trigger condition set are updated according to the newly added collection content and the newly added trigger condition.

[0256] In a possible implementation manner, the sending the fault collection file to the target network element includes:

[0257] Obtaining the IP address of the target network element;

[0258] The fault collection file is sent to the target network element according to the IP address of the target network element.

[0259] It should be noted here that the above-mentioned fault location device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the fault location device, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0260] Fig.12 A schematic diagram of the structure of a target network element provided in an embodiment of the present application is shown in FIG. Fig.12 As shown, the target network element includes a memory 1220, a transceiver 1200, and a processor 1210, wherein:

[0261] The memory 1220 is used to store computer programs; the transceiver 1200 is used to send and receive data under the control of the processor 1210; the processor 1210 is used to read the computer program in the memory 1220 and perform the following operations:

[0262] Receiving a fault collection file sent by a fault location device, wherein the target network element is a network element in a target network topology structure, and the target network topology structure is connected to the fault location device;

[0263] Generating fault indicator data of the target network element according to the fault collection file;

[0264] The fault indicator data is sent to the fault locating device, where the fault indicator data is used to locate the fault of the target network element.

[0265] Specifically, the transceiver 1200 is used to receive and send data under the control of the processor 1210 .

[0266] Among them, Fig.12In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1210 and various circuits of memory represented by memory 1220 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1200 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include transmission media such as wireless channels, wired channels, optical cables, etc. The processor 1210 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1210 when performing operations.

[0267] Optionally, processor 1210 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor may also adopt a multi-core architecture.

[0268] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0269] In a possible implementation manner, generating the fault indicator data of the target network element according to the fault collection file includes:

[0270] According to the fault collection file, an executable program corresponding to the target network element and a program configuration file of the target network element are acquired, wherein the executable program includes a plurality of to-be-selected collection information, and the program configuration file is used to indicate the target collection information among the plurality of to-be-selected collection information;

[0271] The executable program is run according to the target collection information indicated by the program configuration file to generate the fault indicator data.

[0272] It should be noted here that the above-mentioned target network element provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the above-mentioned execution subject is the target network element, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0273] Fig.13 A schematic diagram of the structure of a fault location device provided in an embodiment of the present application, wherein the device is applied to a fault location device, wherein the fault location device is connected to a plurality of network topologies, wherein the plurality of network topologies include respective network elements, such as Fig.13 As shown, the device comprises:

[0274] A determination module 131, configured to determine a fault collection file of a target network element to be located in response to a fault location instruction;

[0275] A first sending module 132, configured to send the fault collection file to the target network element, wherein the fault collection file is used by the target network element to generate fault indicator data;

[0276] A first receiving module 133, configured to receive the fault indicator data sent by the target network element;

[0277] The fault location module 134 is used to locate the fault of the target network element according to the fault indicator data.

[0278] In a possible implementation manner, the determining module 131 is specifically configured to:

[0279] In response to a first selection instruction for a network topology, selecting a target network topology from among the multiple network topologies, the target network topology including the target network element;

[0280] In response to a second selection instruction for a network element included in the target network topology structure, determining the target network element from the network elements included in the target network topology structure;

[0281] The fault collection file is generated in response to a configuration instruction for the target network element, wherein the fault location instruction includes the first selection instruction, the second selection instruction and the configuration instruction.

[0282] In a possible implementation manner, the determining module 131 is specifically configured to:

[0283] Determine, according to the category of the target network element and the position of the target network element in the target network topology, a collection information set of the target network element, wherein the collection information set includes a plurality of to-be-selected collection information of the target network element;

[0284] In response to the configuration instruction for the collection information set, determining the target collection information of the target network element from the plurality of to-be-selected collection information;

[0285] The fault collection file is generated according to the target collection information.

[0286] In a possible implementation, the collection information set includes a collection content set and a trigger condition set; the determination module 131 is specifically configured to:

[0287] In response to a first configuration instruction for the collection content set, determining a target collection content from a plurality of to-be-selected collection contents included in the collection content set;

[0288] Determine at least one of the candidate trigger conditions included in the trigger condition set that matches the target acquisition content;

[0289] In response to a second configuration instruction for the at least one selected trigger condition, a target trigger condition is determined among the at least one selected trigger condition; the configuration instruction includes the first configuration instruction and the second configuration instruction, and the target acquisition information includes the target acquisition content and the target trigger condition.

[0290] In a possible implementation manner, the determining module 131 is specifically configured to:

[0291] According to the type of the target network element, acquiring an executable program corresponding to the target network element, wherein the executable program includes the plurality of to-be-selected collection information;

[0292] Generate a program configuration file of the target network element according to the target acquisition information, wherein the program configuration file is used to indicate the target acquisition information among the multiple pieces of collection information to be selected;

[0293] The fault collection file is generated according to the executable program and the program configuration file.

[0294] In a possible implementation manner, the determining module 131 is specifically configured to:

[0295] Get the initial acquisition program;

[0296] Determining, according to the category of the target network element, a cross-compilation chain matching the target network element;

[0297] The initial acquisition program is compiled according to the cross-compilation chain to generate the executable program.

[0298] In a possible implementation manner, the determining module 131 is further configured to:

[0299] In response to a first editing instruction for the collection content set, acquiring newly added collection content of the target network element;

[0300] In response to a second editing instruction for the trigger condition set, acquiring a newly added trigger condition of the target network element;

[0301] The collection content set and the trigger condition set are updated according to the newly added collection content and the newly added trigger condition.

[0302] In a possible implementation manner, the first sending module 132 is specifically configured to:

[0303] Obtaining an Internet Protocol (IP) address of the target network element;

[0304] The fault collection file is sent to the target network element according to the IP address of the target network element.

[0305] Specifically, the above-mentioned fault location device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the fault location device, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0306] Fig.14 A schematic diagram of the structure of a fault location device provided in an embodiment of the present application, wherein the device is applied to a target network element in a target network topology structure, wherein the target network topology structure is connected to a fault location device, such as Fig.14 As shown, the device comprises:

[0307] The second receiving module 141 is used to receive the fault collection file sent by the fault location device;

[0308] A generating module 142, configured to generate fault indicator data of the target network element according to the fault collection file;

[0309] The second sending module 143 is used to send the fault indicator data to the fault locating device, where the fault indicator data is used to locate the fault of the target network element.

[0310] In a possible implementation, the generating module 142 is specifically configured to:

[0311] According to the fault collection file, an executable program corresponding to the target network element and a program configuration file of the target network element are acquired, wherein the executable program includes a plurality of to-be-selected collection information, and the program configuration file is used to indicate the target collection information among the plurality of to-be-selected collection information;

[0312] The executable program is run according to the target collection information indicated by the program configuration file to generate the fault indicator data.

[0313] Specifically, the above-mentioned fault location device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the target network element, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0314] It should be noted that the division of units / modules in the above embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, the functional units in the various embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated units may be implemented in the form of hardware or in the form of software functional units.

[0315] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0316] In some embodiments, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the frequency domain resource allocation method provided by the above-mentioned method embodiments.

[0317] Specifically, the above-mentioned computer-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0318] It should be noted that the computer-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0319] It should also be noted that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more.

[0320] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0321] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0322] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0323] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0324] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0325] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

[0326] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0327] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0328] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0329] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0330] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A fault location method, characterized in that: Applied to a fault location device, the fault location device is connected to a plurality of network topologies, the plurality of network topologies include respective network elements, the method includes: In response to the fault location instruction, determining a fault collection file of a target network element to be located; Sending the fault collection file to the target network element, where the fault collection file is used by the target network element to generate fault indicator data; Receiving the fault indicator data sent by the target network element; The target network element is fault located according to the fault indicator data.

2. The method according to claim 1, characterized in that The step of determining the fault collection file of the target network element to be located in response to the fault location instruction includes: In response to a first selection instruction for a network topology, selecting a target network topology from among the multiple network topologies, the target network topology including the target network element; In response to a second selection instruction for a network element included in the target network topology structure, determining the target network element from the network elements included in the target network topology structure; The fault collection file is generated in response to a configuration instruction for the target network element, wherein the fault location instruction includes the first selection instruction, the second selection instruction and the configuration instruction.

3. The method according to claim 2, characterized in that The generating the fault collection file in response to the configuration instruction for the target network element includes: Determine, according to the category of the target network element and the position of the target network element in the target network topology, a collection information set of the target network element, wherein the collection information set includes a plurality of to-be-selected collection information of the target network element; In response to the configuration instruction for the collection information set, determining the target collection information of the target network element from the plurality of to-be-selected collection information; The fault collection file is generated according to the target collection information.

4. The method according to claim 3, characterized in that: The collection information set includes a collection content set and a trigger condition set; The step of determining the target acquisition information of the target network element from the plurality of to-be-selected acquisition information in response to the configuration instruction for the acquisition information set includes: In response to a first configuration instruction for the collection content set, determining a target collection content from a plurality of to-be-selected collection contents included in the collection content set; Determine at least one trigger condition to be selected that matches the target acquisition content among a plurality of trigger conditions to be selected included in the trigger condition set; In response to a second configuration instruction for the at least one selected trigger condition, a target trigger condition is determined among the at least one selected trigger condition; the configuration instruction includes the first configuration instruction and the second configuration instruction, and the target acquisition information includes the target acquisition content and the target trigger condition.

5. The method according to claim 3, characterized in that: The generating the fault collection file according to the target collection information includes: According to the type of the target network element, acquiring an executable program corresponding to the target network element, wherein the executable program includes the plurality of to-be-selected collection information; Generate a program configuration file of the target network element according to the target acquisition information, wherein the program configuration file is used to indicate the target acquisition information among the multiple pieces of collection information to be selected; The fault collection file is generated according to the executable program and the program configuration file.

6. The method according to claim 5, characterized in that The acquiring, according to the category of the target network element, an executable program corresponding to the target network element includes: Get the initial acquisition program; Determining a cross-compilation chain matching the target network element according to the category of the target network element; The initial acquisition program is compiled according to the cross-compilation chain to generate the executable program.

7. The method according to any one of claims 4 to 6, characterized in that: The method further comprises: In response to a first editing instruction for the collection content set, acquiring newly added collection content of the target network element; In response to a second editing instruction for the trigger condition set, acquiring a newly added trigger condition of the target network element; The collection content set and the trigger condition set are updated according to the newly added collection content and the newly added trigger condition.

8. The method according to any one of claims 1 to 6, characterized in that: The sending the fault collection file to the target network element includes: Obtaining an Internet Protocol (IP) address of the target network element; The fault collection file is sent to the target network element according to the IP address of the target network element.

9. A fault location method, characterized in that: Applied to a target network element in a target network topology structure, the target network topology structure is connected to a fault location device, the method comprising: Receiving the fault collection file sent by the fault location device; Generating fault indicator data of the target network element according to the fault collection file; The fault indicator data is sent to the fault locating device, where the fault indicator data is used to locate the fault of the target network element.

10. The method according to claim 9, characterized in that The generating the fault indicator data of the target network element according to the fault collection file includes: According to the fault collection file, an executable program corresponding to the target network element and a program configuration file of the target network element are acquired, wherein the executable program includes a plurality of to-be-selected collection information, and the program configuration file is used to indicate the target collection information among the plurality of to-be-selected collection information; The executable program is run according to the target collection information indicated by the program configuration file to generate the fault indicator data.

11. A fault location device, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: In response to the fault location instruction, determining a fault collection file of a target network element to be located; Sending the fault collection file to the target network element, where the fault collection file is used by the target network element to generate fault indicator data; Receiving the fault indicator data sent by the target network element; The target network element is fault located according to the fault indicator data.

12. The fault location device according to claim 11, characterized in that: The step of determining the fault collection file of the target network element to be located in response to the fault location instruction includes: In response to a first selection instruction for a network topology structure, selecting a target network topology structure from a plurality of network topologies connected to the fault location, the target network topology structure including the target network element; In response to a second selection instruction for a network element included in the target network topology structure, determining the target network element from the network elements included in the target network topology structure; The fault collection file is generated in response to a configuration instruction for the target network element, wherein the fault location instruction includes the first selection instruction, the second selection instruction and the configuration instruction.

13. The fault location device according to claim 12, characterized in that: The generating the fault collection file in response to the configuration instruction for the target network element includes: Determine, according to the category of the target network element and the position of the target network element in the target network topology, a collection information set of the target network element, wherein the collection information set includes a plurality of to-be-selected collection information of the target network element; In response to the configuration instruction for the collection information set, determining the target collection information of the target network element from the plurality of to-be-selected collection information; The fault collection file is generated according to the target collection information.

14. The fault location device according to claim 13, characterized in that: The collection information set includes a collection content set and a trigger condition set; The step of determining the target acquisition information of the target network element from the plurality of to-be-selected acquisition information in response to the configuration instruction for the acquisition information set includes: In response to a first configuration instruction for the collection content set, determining a target collection content from a plurality of to-be-selected collection contents included in the collection content set; Determine at least one trigger condition to be selected that matches the target acquisition content among a plurality of trigger conditions to be selected included in the trigger condition set; In response to a second configuration instruction for the at least one selected trigger condition, a target trigger condition is determined among the at least one selected trigger condition; the configuration instruction includes the first configuration instruction and the second configuration instruction, and the target acquisition information includes the target acquisition content and the target trigger condition.

15. The fault location device according to claim 13, characterized in that: The generating the fault collection file according to the target collection information includes: According to the type of the target network element, acquiring an executable program corresponding to the target network element, wherein the executable program includes the plurality of to-be-selected collection information; Generate a program configuration file of the target network element according to the target acquisition information, wherein the program configuration file is used to indicate the target acquisition information among the multiple pieces of collection information to be selected; The fault collection file is generated according to the executable program and the program configuration file.

16. The fault location device according to claim 15, characterized in that: The acquiring, according to the category of the target network element, an executable program corresponding to the target network element includes: Get the initial acquisition program; Determining a cross-compilation chain matching the target network element according to the category of the target network element; The initial acquisition program is compiled according to the cross-compilation chain to generate the executable program.

17. The fault location device according to any one of claims 14 to 16, characterized in that: The processor is further configured to read the computer program in the memory and perform the following operations: In response to a first editing instruction for the collection content set, acquiring newly added collection content of the target network element; In response to a second editing instruction for the trigger condition set, acquiring a newly added trigger condition of the target network element; The collection content set and the trigger condition set are updated according to the newly added collection content and the newly added trigger condition.

18. The fault location device according to any one of claims 11 to 16, characterized in that: The sending the fault collection file to the target network element includes: Obtaining the IP address of the target network element; The fault collection file is sent to the target network element according to the IP address of the target network element.

19. A target network element, characterized in that: Including memory, transceiver, processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Receiving a fault collection file sent by a fault location device, wherein the target network element is a network element in a target network topology structure, and the target network topology structure is connected to the fault location device; Generating fault indicator data of the target network element according to the fault collection file; The fault indicator data is sent to the fault locating device, where the fault indicator data is used to locate the fault of the target network element.

20. The target network element according to claim 19, characterized in that: The generating the fault indicator data of the target network element according to the fault collection file includes: According to the fault collection file, an executable program corresponding to the target network element and a program configuration file of the target network element are acquired, wherein the executable program includes a plurality of to-be-selected collection information, and the program configuration file is used to indicate the target collection information among the plurality of to-be-selected collection information; The executable program is run according to the target collection information indicated by the program configuration file to generate the fault indicator data.

21. A fault location device, characterized in that: Applied to a fault location device, the fault location device is connected to a plurality of network topology structures, the plurality of network topology structures include respective network elements, the device includes: A determination module, configured to determine a fault collection file of a target network element to be located in response to a fault location instruction; A first sending module, configured to send the fault collection file to the target network element, wherein the fault collection file is used by the target network element to generate fault indicator data; A first receiving module, configured to receive the fault indicator data sent by the target network element; A fault location module is used to locate the fault of the target network element according to the fault indicator data.

22. A fault location device, characterized in that: The device is applied to a target network element in a target network topology structure, wherein the target network topology structure is connected to a fault location device, and the device comprises: A second receiving module, used for receiving the fault collection file sent by the fault location device; A generating module, used to generate fault indicator data of the target network element according to the fault collection file; The second sending module is used to send the fault indicator data to the fault locating device, and the fault indicator data is used to locate the fault of the target network element.

23. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the fault location method according to any one of claims 1 to 10.

Images