A method, device and storage medium for screening fault work orders

Abstract

The present application provides a method, device and storage medium for screening fault work orders, which relate to the field of communication technology and can accurately locate faults. The method includes: obtaining a fault work order, the fault work order includes multiple fault data, the multiple fault data correspond to multiple network layers, and each of the multiple fault data includes: device identification, fault time and device type. According to the device identification, fault time and device type of the multiple fault data, the target fault data is determined from the multiple fault data, the target fault data is the fault data of the same business, the difference between the fault times is less than the preset time difference threshold, and the target fault data is the fault data of the same business, and the network layer in the corresponding network layer that starts to transmit the service data generates the fault data.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a method, device and storage medium for screening fault work orders. Background Art

[0002] With the development of communication technology, various communication services (such as fixed-line telephone services, mobile phone services, and network services) are used in daily life. Among them, communication services require multiple network devices to transmit service data to complete communication services. In order to ensure the normal operation of communication services, in the event of a network device failure, the dispatching system can dispatch a fault work order to the operation and maintenance personnel, notifying the operation and maintenance personnel to repair the faulty network equipment.

[0003] However, in the communication business, when a network device fails and generates fault data, it may cause other network devices to generate fault data, thus making it impossible for the dispatch system to accurately locate the fault. Summary of the invention

[0004] The present application provides a method, device and storage medium for screening fault work orders, which can accurately locate faults.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In the first aspect, a method for screening fault work orders is provided. In the method, a fault work order is obtained, the fault work order includes multiple fault data, the multiple fault data correspond to multiple network layers, and each of the multiple fault data includes: device identification, fault time and device type, the device identification is used to indicate the business to which the fault data belongs, the fault time is the time when the fault data is generated, and the device type is used to indicate the network layer that generates the fault data. According to the device identification, fault time and device type of the multiple fault data, the target fault data is determined from the multiple fault data, and the target fault data is the fault data of the same business, the difference between the fault times is less than the preset time difference threshold, and the target fault data is the fault data of the same business, and the network layer in the corresponding network layer that starts to transmit the business data generates the fault data.

[0007] Based on the above technical solution, the fault data in the fault work order includes the device identification, device type and fault time. After obtaining the fault work order, the target fault data is determined from the multiple fault data according to the device identification, fault time and device type of the multiple fault data. The target fault data is the fault data of the same business, the difference between the fault times is less than the preset time difference threshold, and the target fault data is the fault data of the same business, and the network layer in the corresponding network layer that starts to transmit the business data generates the fault data. In this way, through the device identification, fault time and device type, it is possible to determine from the multiple fault data that the same business has a similar fault time, and the fault data is the network layer (i.e., the target fault data) that starts to transmit the business data in the network layer corresponding to the fault data of the same business. In this way, the fault can be accurately located. In addition, the dispatching system can only dispatch the target fault data to the operation and maintenance personnel, and does not dispatch fault data other than the target fault data, which reduces the number of fault work orders dispatched, improves the accuracy of dispatching, and improves the work efficiency of the operation and maintenance personnel.

[0008] In one possible design, a first fault group is determined based on device identifiers in multiple fault data, and the fault data in the first fault group belong to the same service. A second fault group is determined based on the fault time of the fault data in the first fault group, and the difference between the fault times of the fault data in the second fault group is less than a preset time difference threshold. Target fault data is determined based on the device type of the fault data in the second fault group, and the target fault data is the fault data generated by the network layer that starts transmitting the service data in the network layer corresponding to the fault data in the second fault group.

[0009] In one possible design, a target time range is determined based on the failure time of all the failure data in the first failure group. The target time range includes a start time and an end time. The time difference between the start time and the end time is less than a preset time difference threshold. The start time and the end time are the failure times in the first failure group. A second failure group is determined based on the failure time and the target time range of all the failure data in the first failure group. The failure time of the failure data in the second failure group is all within the target time range.

[0010] In a possible design, target location information is received, a fault work order is determined based on the target location information, and a plurality of fault data correspond to the target location information.

[0011] In a second aspect, a device for screening fault work orders is provided, the device comprising an acquisition unit and a determination unit.

[0012] The acquisition unit is used to acquire a fault work order, the fault work order includes multiple fault data, the multiple fault data correspond to multiple network layers, and each of the multiple fault data includes: device identification, fault time and device type, the device identification is used to indicate the business to which the fault data belongs, the fault time is the time when the fault data is generated, and the device type is used to indicate the network layer that generates the fault data. The determination unit is used to determine the target fault data from the multiple fault data according to the device identification, fault time and device type of the multiple fault data, the target fault data is the fault data of the same business, the difference between the fault times is less than the preset time difference threshold, and the target fault data is the fault data of the same business, and the network layer corresponding to the network layer that starts to transmit the business data is generated.

[0013] In one possible design, the determination unit is used to determine a first fault group based on device identifiers in multiple fault data, where the fault data in the first fault group belong to the same service. The determination unit is also used to determine a second fault group based on the fault time of the fault data in the first fault group, where the difference between the fault times of the fault data in the second fault group is less than a preset time difference threshold. The determination unit is also used to determine target fault data based on the device type of the fault data in the second fault group, where the target fault data is fault data generated by the network layer that starts transmitting service data in the network layer corresponding to the fault data in the second fault group.

[0014] In one possible design, the determination unit is specifically used to determine a target time range based on the failure time of all the failure data in the first failure group, the target time range including a start time and an end time, the time difference between the start time and the end time is less than a preset time difference threshold, and the start time and the end time are the failure times in the first failure group. A second failure group is determined based on the failure time and the target time range of all the failure data in the first failure group, and the failure time of the failure data in the second failure group is all within the target time range.

[0015] In a possible design, the acquisition unit is further used to receive target location information. The acquisition unit is specifically used to determine the fault work order according to the target location information, and the plurality of fault data correspond to the target location information.

[0016] In a third aspect, a server is provided, the device comprising: a processor and a memory; the processor and the memory are coupled; the memory is used to store one or more programs, the one or more programs comprising computer execution instructions, and when the server is running, the processor executes the computer execution instructions stored in the memory to implement the method for screening fault tickets as described in the first aspect and any possible implementation of the first aspect.

[0017] In a fourth aspect, a computer-readable storage medium is provided, in which instructions are stored. When the instructions are executed on a computer, the computer executes the method for screening fault tickets described in the above-mentioned first aspect and any possible implementation of the first aspect.

[0018] In a fifth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run a computer program or instructions to implement a method for screening fault tickets as described in the first aspect and any possible implementation of the first aspect.

[0019] In the above scheme, the technical problems that can be solved and the technical effects achieved by the fault work order screening device, server, computer storage medium or chip can be referred to the technical problems and technical effects solved by the above-mentioned first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A system architecture diagram of a communication system provided in an embodiment of the present application;

[0021] Figure 2A A flowchart of a method for screening fault work orders provided in an embodiment of the present application;

[0022] Figure 2B A flowchart of a method for screening fault work orders provided in an embodiment of the present application;

[0023] Figure 3 A flowchart of another method for screening fault work orders provided in an embodiment of the present application;

[0024] Figure 4 A schematic diagram of the structure of a device for screening fault work orders provided in an embodiment of the present application;

[0025] Figure 5 A schematic diagram of the structure of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0027] In this article, the character " / " generally indicates that the objects before and after are in an "or" relationship. For example, A / B can be understood as A or B.

[0028] The terms “first” and “second” in the description and claims of the present application are used to distinguish different objects rather than to describe a specific order of the objects.

[0029] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or modules is not limited to the listed steps or modules, but may optionally include other steps or modules that are not listed, or may optionally include other steps or modules that are inherent to these processes, methods, products or devices.

[0030] In addition, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present concepts in a specific way.

[0031] Before introducing the method for screening fault tickets in the embodiment of the present application in detail, the implementation environment and application scenarios of the embodiment of the present application are first introduced.

[0032] like Figure 1 As shown in FIG. 1 , a communication system provided by an embodiment of the present application includes a plurality of network devices and a server 105 in different network layers. The different network layers may include an access network, an IP radio access network (IP RAN) network (referred to as an IP network), a transmission network, a core network, etc. For example, Figure 1 As shown, the plurality of network devices include: a first network device 101, a second network device 102, a third network device 103 and a fourth network device 104. The first network device 101 and the second network device 102 are in a transmission network, and the third network device 103 and the fourth network device 104 are in an IP network.

[0033] Optionally, the first network device 101, the second network device 102, the third network device 103 and the fourth network device 104 may be connected via a wire (such as an optical cable).

[0034] It should be noted that the embodiment of the present application does not limit the connection between the first network device 101, the second network device 102, the third network device 103 and the fourth network device 104. For example, the first network device 101 and the third network device 103 are connected. For another example, the first network device 101, the second network device 102 and the fourth network device 104 are connected. For another example, the first network device 101, the third network device 103 and the fourth network device 104 are connected.

[0035] In the embodiment of the present application, the server 105 can obtain a fault work order, which includes fault data of multiple network devices in different network layers. In addition, the server 105 can manage the fault work order. Afterwards, the server 105 can dispatch the fault work order to the operation and maintenance personnel through the dispatching system.

[0036] It should be noted that the dispatching system can be built on the server 105 or on other servers other than the server 105, and this embodiment of the present application does not limit this.

[0037] In the embodiment of the present application, the network equipment includes base stations, servers, routers, wavelength division multiplexing (WDM) equipment and synchronous digital hierarchy (SDH) equipment, etc. The base station may include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, access points, etc. Specifically, it can be: an access point (AP) in a wireless local area network (WLAN), a base station (Base Transceiver Station, BTS) in a global system for mobile communications (GSM) or code division multiple access (CDMA), a base station (NodeB, NB) in wideband code division multiple access (WCDMA), an evolved base station (Evolved Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and the next generation Node B (The Next Generation Node B, gNB) in the future 5G network or a base station in the future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

[0038] The embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0039] like Figure 2A As shown, a method for screening fault work orders provided in an embodiment of the present application includes:

[0040] S201. Obtain a fault work order.

[0041] The fault work order includes multiple fault data, and the multiple fault data correspond to multiple network layers and multiple fault data also correspond to multiple network devices.

[0042] Exemplarily, the plurality of fault data include: fault data A, fault data B and fault data C. Fault data A is fault data of network device A, fault data B is fault data of network device B, and fault data C is fault data of network device C.

[0043] Optionally, one or more pieces of fault data among the multiple pieces of fault data correspond to the same network device.

[0044] Exemplarily, the plurality of fault data include: fault data A, fault data B, fault data C and fault data D. Fault data A and fault data D are fault data of network device A, fault data B is fault data of network device B, and fault data C is fault data of network device C.

[0045] In a possible design, each of the multiple fault data includes: a device identification, a fault time, and a device type, where the fault time is the time when the fault data is generated.

[0046] Exemplarily, as shown in Table 1, it shows multiple fault data in a fault work order.

[0047] Table 1

[0048] Fault data Equipment identification Failure time Device Type Data A JZ-DAPXF1 2021-09-01-09:00:01 WDM Data B JZ-DAPXF21 2021-09-01-09:00:15 WDM Data C JR-SDHJ1 2021-09-01-09:00:35 IPRAN Data D JR-GNHJ11 2021-09-01-09:00:55 IPRAN Data E JZ-DAPXF2111 2021-09-01-09:05:01 WDM

[0049] That is to say, the device ID of the network device corresponding to data A is JZ-DAPXF1, the time of failure is 09:00:01 on September 1, 2021, and the device type is "WDM". For the specific introduction of data B-data E, please refer to the introduction of data A, which will not be repeated here.

[0050] It should be noted that in the embodiment of the present application, the device identification can also be represented by the device name of the network device. The device identification can include hardware information (such as board information) in the network device. For example, "DAPXF1" in the device identification "JZ-DAPXF1" is the board information, and "DAPXF21" in the device identification "JZ-DAPXF21" is the board information.

[0051] Optionally, the fault data also includes: location information.

[0052] In some embodiments, before obtaining the fault work order, the target location information is received. Afterwards, obtaining the fault work order includes: determining the fault work order according to the target location information, and the plurality of fault data in the fault work order corresponds to the target location information.

[0053] For example, the maintenance personnel can input the location information (such as city A) through the dispatch system according to the current area. Afterwards, the server receives the location information from the dispatch system and determines the fault work order from the national fault data, and the multiple fault data of the fault work order are the fault data of city A.

[0054] It is understandable that, through the location information, the fault data corresponding to the location information can be screened out. In this way, work orders can be more accurately issued to operation and maintenance personnel, thereby improving the work efficiency of operation and maintenance personnel.

[0055] It should be noted that the fault data also includes: the name of the computer room, alarm location information (such as peer network element and port information), etc. The embodiment of the present application does not limit this.

[0056] S202: Determine target fault data from the multiple pieces of fault data according to device identifications, fault times, and device types of the multiple pieces of fault data.

[0057] Among them, the target fault data is the fault data of the same service, the difference between the fault times is less than the preset time difference threshold, and the target fault data is the fault data of the same service, and the network layer in the corresponding network layer that starts transmitting the service data generates the fault data.

[0058] For example, if the service data is transmitted from network layer A to network layer B, and then transmitted from network layer B to network layer C, then network layer A is the network layer that starts transmitting the service data.

[0059] In a possible implementation, the fault data of the same service in the multiple fault data are determined according to the device identifiers of the multiple fault data. Then, according to the fault time, the fault data of the same service whose difference between the fault times is less than the preset time difference threshold is determined. Then, according to the device type, in the fault data of the same service, the difference between the fault times is less than the preset time difference threshold, and the target fault data is the fault data generated by the network layer that starts to transmit the service data in the corresponding network layer in the fault data of the same service.

[0060] It should be noted that the embodiment of the present application does not limit the order of determining the target fault data by device identification, fault time and device type.

[0061] Based on the above technical solution, the fault data in the fault work order includes the device identification, device type and fault time. After obtaining the fault work order, the target fault data is determined from the multiple fault data according to the device identification, fault time and device type of the multiple fault data. The target fault data is the fault data of the same business, the difference between the fault times is less than the preset time difference threshold, and the target fault data is the fault data of the same business, and the network layer in the corresponding network layer that starts to transmit the business data generates the fault data. In this way, through the device identification, fault time and device type, it is possible to determine from the multiple fault data that the same business has a similar fault time, and the fault data is the network layer (i.e., the target fault data) that starts to transmit the business data in the network layer corresponding to the fault data of the same business. In this way, the fault can be accurately located. In addition, the dispatching system can only dispatch the target fault data to the operation and maintenance personnel, and does not dispatch fault data other than the target fault data, which reduces the number of fault work orders dispatched, improves the accuracy of dispatching, and improves the work efficiency of the operation and maintenance personnel.

[0062] As another possible implementation, Figure 2B As shown, S202 may include S2021-S2023.

[0063] S2021. Determine a first fault group according to device identifiers in multiple pieces of fault data.

[0064] The fault data in the first fault group belongs to the same service.

[0065] In the embodiment of the present application, the device identifier is used to indicate the service that generates the fault data. The server stores multiple device identifiers corresponding to each service.

[0066] In a possible implementation, the services corresponding to the multiple pieces of fault data are determined according to the device identifiers in the multiple pieces of fault data. Then, the first fault group is determined according to the services corresponding to the multiple pieces of fault data.

[0067] For example, if service A includes: DAPXF1, DAPXF21, GNHJ11 and DAPXF2111, and service B includes SDHJ1 and DAPXF2111. Combining the multiple fault data in Table 1, it can be seen that data A, data B, data D and data E are all fault data of service A. In other words, the first fault group includes data A, data B, data D and data E.

[0068] It is understandable that when multiple fault data are fault data under the same service, due to the transmission of faults, a network device failure may cause network devices at other network layers to be unable to complete services and generate fault data. In other words, fault data under the same service may have derived fault data. Therefore, fault data under the same service can be screened to reduce the number of fault work orders.

[0069] Optionally, each piece of fault data further includes a port identifier. Before determining the first fault group according to the device identifiers in the plurality of fault data, a preset fault group is determined according to the port identifiers in the plurality of fault data, and the network devices corresponding to the fault data in the preset fault group are all connected.

[0070] Exemplarily, the server stores the relationship between the port identifier and the physical device connection group. For example, if the network device with port 50 is connected to the network device with port 100. If the port of data A is 50, the port of data B is 20, the port of data C is 100, and the port of data D is 80, then the network device corresponding to data A is connected to the network device corresponding to data C.

[0071] In a possible implementation, the first fault group is determined according to a device identifier in preset fault data.

[0072] It is understandable that the same service can only be executed when the network devices are connected.

[0073] S2022: Determine a second fault group according to the fault time of the fault data in the first fault group.

[0074] The difference between the fault times of the fault data in the second fault group is less than a preset time difference threshold.

[0075] In a possible implementation, the difference between the two fault times in the first fault group is calculated based on the fault time of the fault data in the first fault group. Then, the data corresponding to the two fault data whose difference is less than the preset time difference threshold and whose fault times have an intersection are merged to obtain a preset second fault group. Then, the second fault group is determined based on the earliest fault time in the second fault group and the preset fault time difference threshold.

[0076] For example, if the preset time difference threshold is 1 minute, the first fault group includes data A, data B, data D, and data E in Table 1. In combination with Table 1, it can be seen that the failure time of data A is "2021-09-01-09:00:01", the failure time of data B is "2021-09-01-09:00:15", the failure time of data D is "2021-09-01-09:00:55", and the failure time of data E is "2021-09-01-09:05:01". Then the second fault group includes data A, data B, and data D.

[0077] In another possible implementation, Figure 3 As shown, S2022 may include S301 - S302 .

[0078] S301. Determine a target time range according to the failure time of all failure data in a first failure group.

[0079] The target time range includes a start time and an end time, the time difference between the start time and the end time is less than a preset time difference threshold, and the start time and the end time are fault times in the first fault group.

[0080] In a possible implementation, the earliest fault time is determined from the fault time of all fault data in the first fault group, and the earliest fault time in the first fault group is used as the start time of the target time range. After that, the preset end time is obtained according to the start time and the preset time difference threshold, and the fault time in the first fault group that is earlier than the preset end time and closest to the preset end time is used as the end time according to the preset end time.

[0081] Exemplarily, if the preset time difference threshold is 1 minute, the first fault group includes data A, data B, data D, and data E in Table 1. In combination with Table 1, it can be seen that the failure time of data A is "2021-09-01-09:00:01", the failure time of data B is "2021-09-01-09:00:15", the failure time of data D is "2021-09-01-09:00:55", and the failure time of data E is "2021-09-01-09:05:01". Among them, the failure time of data A is the start time, the preset end time is 2021-09-01-09:01:01, and the end time is the failure time of data D. In other words, the target time range is "2021-09-01-09:00:01" to "2021-09-01-09:00:55".

[0082] S302: Determine a second fault group according to the fault time and target time range of all fault data in the first fault group.

[0083] The failure times of the failure data in the second failure group are all within the target time range.

[0084] Exemplarily, if the target time range is "2021-09-01-09:00:01" to "2021-09-01-09:00:55", the first fault group includes data A, data B, data D, and data E in Table 1. In combination with Table 1, it can be seen that the second fault group includes data A, data B, and data D.

[0085] It is understandable that, if the fault data is under the same service and the time of the fault occurrence is close, it can be determined that there may be derived fault data in the fault data.

[0086] S2023. Determine target fault data according to the device type of the fault data in the second fault group.

[0087] The target fault data is fault data generated by a network layer that starts transmitting service data in a network layer corresponding to the fault data in the second fault group.

[0088] In the embodiment of the present application, the device type is used to indicate the network layer that generates the fault data. The server stores the network layer corresponding to the device type. The network layer that generates the fault data refers to the network layer where the network device that generates the fault data is located.

[0089] For example, if the network layer corresponding to the device type "WDM" is the transmission network, and the network layer corresponding to the device type "IPRAN" is the IP network. According to Table 1, data A, data B, and data E are fault data generated by the transmission network, and data C and data D are fault data generated by the IP network.

[0090] In a possible implementation, the network layer corresponding to each piece of fault data in the second fault group is determined according to the device type of the fault data in the second fault group. Then, the position of the network layer corresponding to each piece of fault data in the second fault group in the professional network architecture is compared to determine the target fault data.

[0091] Exemplarily, in combination with Table 1, if the second fault group includes data A, data B, and data D, data A and data B are fault data generated by the transmission network, and data D is fault data generated by the IP network. The transmission network is at the lower layer of the IP network. That is, data A and data B are target fault data.

[0092] It should be noted that, in the embodiment of the present application, the lowest network layer in the network layers corresponding to the fault data in the second fault group refers to the network layer that starts transmitting service data in the network layers corresponding to the fault data.

[0093] Optionally, the work order screening rate may be determined according to the number of target fault data and the number of multiple fault data. For example, the work order screening rate = the number of multiple fault data in the fault work order - the number of target fault data) / the number of multiple fault data in the fault work order.

[0094] For example, if there are 5 pieces of fault data in the fault work order and 2 pieces of target fault data, the work order screening rate is 60%.

[0095] In some embodiments, after the target fault data is determined, the target fault data may be sent to a dispatch system.

[0096] Exemplarily, the second fault group includes data A, data B, and data D, and data A and data B are target fault data. Then data A and data B are sent to the dispatch system, but data D is not sent. In other words, the operation and maintenance personnel can obtain information about data A and data B through the dispatch system and perform maintenance, but will not obtain data D and will not perform maintenance on data D.

[0097] Based on the above technical solution, the fault data in the fault work order includes the device identification, the device type and the fault time. After obtaining the fault work order, since the device identification is used to indicate the business that generates the fault data, the fault data belonging to the same business in multiple fault data can be screened out according to the device identification (i.e., the first fault group). Afterwards, according to the fault time of the fault data in the first fault group, the fault data with similar fault time is determined (i.e., the second fault group, the difference between the fault time of the fault data in the second fault group is less than the preset time difference threshold). Then, according to the device type of the fault data in the second fault group, the target fault data is determined, and the target fault data is the fault data generated by the lowest network layer in the network layer corresponding to the fault data in the second fault group. In this way, through the device identification, fault time and device type, it can be determined from multiple fault data that the same business has a similar fault time, and the fault data is generated by the lowest network layer (i.e., the target fault data). In this way, the dispatching system can only dispatch the target fault data to the operation and maintenance personnel, and does not dispatch the fault data other than the target fault data in the second fault group, thereby reducing the number of fault work orders dispatched and improving the work efficiency of the operation and maintenance personnel.

[0098] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of computer equipment. It is understandable that in order to realize the above functions, the computer equipment includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the steps of the screening method of the fault work order of each example described in the embodiment disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0099] The embodiment of the present application also provides a device for screening fault work orders. The device for screening fault work orders can be a computer device, a CPU in the computer device, a processing module for screening fault work orders in the computer device, or a client in the computer device for screening fault work orders.

[0100] The embodiment of the present application can divide the screening of fault work orders into functional modules or functional units according to the above method example. For example, each functional module or functional unit can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules or functional units. Among them, the division of modules or units in the embodiment of the present application is schematic, which is only a logical function division. There may be other division methods in actual implementation.

[0101] like Figure 4 FIG. 1 is a schematic diagram of a structure of a device for screening fault work orders provided in an embodiment of the present application. The device for screening fault work orders is used to perform Figure 2A , Figure 2B or Figure 3 The method for screening fault work orders shown in the figure. The device for screening fault work orders may include an acquisition unit 401 and a determination unit 402 .

[0102] The acquisition unit 401 is used to acquire a fault work order including multiple fault data, the multiple fault data corresponding to multiple network layers, each of the multiple fault data including: device identification, fault time and device type, the device identification is used to indicate the business to which the fault data belongs, the fault time is the time when the fault data is generated, and the device type is used to indicate the network layer that generates the fault data. The determination unit 402 is used to determine target fault data from the multiple fault data according to the device identification, fault data and device type of the multiple fault data, the target fault data is the fault data of the same business, the difference between the fault times is less than the preset time difference threshold, and the target fault data is the fault data of the same business, and the network layer corresponding to the network layer that starts to transmit the business data is generated.

[0103] Optionally, the determination unit 402 is used to determine a first fault group based on device identifiers in multiple fault data, where the fault data in the first fault group belong to the same service. The determination unit 402 is also used to determine a second fault group based on the fault time of the fault data in the first fault group, where the difference between the fault times of the fault data in the second fault group is less than a preset time difference threshold. The determination unit 402 is also used to determine target fault data based on the device type of the fault data in the second fault group, where the target fault data is fault data generated by the network layer that starts transmitting service data in the network layer corresponding to the fault data in the second fault group.

[0104] Optionally, the determination unit 402 is specifically configured to determine a target time range according to the failure time of all the failure data in the first failure group, the target time range including a start time and an end time, the time difference between the start time and the end time being less than a preset time difference threshold, and the start time and the end time being the failure time in the first failure group. A second failure group is determined according to the failure time and the target time range of all the failure data in the first failure group, and the failure time of the failure data in the second failure group is all within the target time range.

[0105] Optionally, the acquisition unit 401 is further configured to receive target location information. The acquisition unit 401 is specifically configured to determine a fault work order according to the target location information, and the plurality of fault data correspond to the target location information.

[0106] Figure 5Another possible structure of the server involved in the above embodiment is shown. The server includes: a processor 501 and a communication interface 502. The processor 501 is used to control and manage the actions of the device, for example, to execute the various steps in the method flow shown in the above method embodiment, and / or to execute other processes of the technology described herein. The communication interface 502 is used to support the communication between the server and other network entities. The server may also include a memory 503 and a bus 504, and the memory 503 is used to store program codes and data of the device.

[0107] Among them, the above-mentioned processor 501 can implement or execute various exemplary logic blocks, units and circuits described in conjunction with the disclosure of the present invention. The processor can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic blocks, units and circuits described in conjunction with the disclosure of the present invention. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of DSP and microprocessors, etc.

[0108] The memory 503 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk or a solid-state drive; the memory may also include a combination of the above types of memory.

[0109] The bus 504 may be an Extended Industry Standard Architecture (EISA) bus, etc. The bus 504 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0110] In actual implementation, the acquisition unit 401 may be composed of Figure 5 The communication interface 502 shown in FIG. 4 is implemented, and the determination unit 402 can be implemented by Figure 5 The processor 501 shown calls the program code in the memory 503 to implement. The specific execution process can be referred to Figure 2A , Figure 2B or Figure 3 The description of the screening method of the fault work order shown is not repeated here.

[0111] Through the description of the above implementation methods, technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0112] An embodiment of the present application provides a computer program product including instructions. When the computer program product is run on a computer, the computer is enabled to execute the method for screening fault work orders in the above method embodiment.

[0113] An embodiment of the present application also provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a computer, the computer executes the method for screening fault work orders in the method flow shown in the above method embodiment.

[0114] Among them, the computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a register, a hard disk, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above, or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application-specific integrated circuit (ASIC). In the embodiments of the present application, a computer-readable storage medium may be any tangible medium that contains or stores a program, which may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0115] Since the fault ticket screening device, computer-readable storage medium, and computer program product in the embodiments of the present invention can be applied to the above method, the technical effects that can be obtained can also refer to the above method embodiments, and the embodiments of the present invention will not be repeated here.

[0116] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for screening fault work orders, characterized in that: Applied to a server, the method comprises: Obtain a fault work order, the fault work order including multiple fault data, the multiple fault data corresponding to multiple network layers, each of the multiple fault data including: a device identifier, a fault time, and a device type, the device identifier is used to indicate the service to which the fault data belongs, the fault time is the time when the fault data is generated, and the device type is used to indicate the network layer that generates the fault data; Determine a first fault group according to device identifiers in the plurality of pieces of fault data, where the fault data in the first fault group belong to the same service; According to the fault time of the fault data in the first fault group, the difference between the fault times of each two in the first fault group is calculated; Merge the data corresponding to the two fault data whose difference is less than the preset time difference threshold and whose fault times have an intersection, to obtain a second fault group, wherein the difference between the fault times of the fault data in the second fault group is less than the preset time difference threshold; According to the device type of the fault data in the second fault group, target fault data is determined, where the target fault data is fault data generated by a network layer that starts transmitting service data in a network layer corresponding to the fault data in the second fault group.

2. The method according to claim 1, characterized in that The determining the second fault group according to the fault time of all fault data in the first fault group includes: Determine a target time range according to the failure time of all failure data in the first failure group, the target time range includes a start time and an end time, the time difference between the start time and the end time is less than a preset time difference threshold, and the start time and the end time are the failure times in the first failure group; The second fault group is determined according to the fault times of all fault data in the first fault group and the target time range, and the fault times of the fault data in the second fault group are all within the target time range.

3. The method according to claim 1 or 2, characterized in that: Each piece of fault data also includes location information. Before obtaining the fault work order, the method further includes: receiving target location information; The obtaining of the fault work order includes: The fault work order is determined according to the target location information, and the multiple fault data correspond to the target location information.

4. A device for screening fault work orders, characterized in that: The device comprises: an acquisition unit, configured to acquire a fault work order, wherein the fault work order includes a plurality of fault data, wherein the plurality of fault data corresponds to a plurality of network layers, and each of the plurality of fault data includes: a device identifier, a fault time, and a device type, wherein the device identifier is used to indicate the service to which the fault data belongs, the fault time is the time when the fault data is generated, and the device type is used to indicate the network layer that generates the fault data; A determining unit, configured to determine a first fault group according to device identifiers in the plurality of pieces of fault data, wherein the fault data in the first fault group belong to the same service; The determining unit is further configured to calculate the difference between the fault times of each pair of faults in the first fault group according to the fault times of the fault data in the first fault group; The determining unit is further configured to merge the data corresponding to the two fault data whose difference is less than a preset time difference threshold and whose fault times have an intersection, to obtain a second fault group, wherein the difference between the fault times of the fault data in the second fault group is less than the preset time difference threshold; The determination unit is further used to determine target fault data according to the device type of the fault data in the second fault group, and the target fault data is the fault data generated by the network layer that starts transmitting business data in the network layer corresponding to the fault data in the second fault group.

5. The device according to claim 4, characterized in that The determining unit is specifically configured to: Determine a target time range according to the failure time of all failure data in the first failure group, the target time range includes a start time and an end time, the time difference between the start time and the end time is less than a preset time difference threshold, and the start time and the end time are the failure times in the first failure group; The second fault group is determined according to the fault times of all fault data in the first fault group and the target time range, and the fault times of the fault data in the second fault group are all within the target time range.

6. The device according to claim 4 or 5, characterized in that The acquisition unit is further used to receive target location information; The acquisition unit is specifically used to determine the fault work order according to the target location information, and the multiple fault data correspond to the target location information.

7. A server, characterized in that: include: Processor and memory; The processor is coupled to the memory; The memory is used to store one or more programs, which include computer-executable instructions. When the server is running, the processor executes the computer-executable instructions stored in the memory to enable the server to perform the method as described in any one of claims 1-3.

8. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, characterized in that: When a computer executes the instruction, the computer performs the method according to any one of claims 1 to 3.

Images