A service single-card single-reporting obstacle method, device, equipment and medium

Abstract

The application provides a business single-card single-reporting-obstacle method, device, equipment and medium, to solve the technical problems of low single-card single-identification efficiency and troublesome reporting-obstacle operation in related technologies. The method comprises the following steps: monitoring abnormal information related to a business single; calling an error matching rule to match the abnormal information, to determine whether a business single has occurred; if yes, performing reporting-obstacle processing on the business single.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of operation and maintenance, and particularly relates to a business single-card single-reporting-obstruction method, device, equipment and medium. BACKGROUND

[0002] With the development of the communication technology field, various new telecommunication services of operators emerge in endlessly, and various business orders increase year by year, so that the operation and maintenance complexity is continuously improved. Due to the improvement of the operation and maintenance complexity, the operation and maintenance management scene has the phenomena of lengthening of the service calling chain, difficulty in service positioning, and instability of service calling between services. In the process of developing a business, the business single-card single phenomenon may be caused by various problems such as system errors and service delays.

[0003] At present, the identification of the business single-card single phenomenon is mostly based on experience by manual work, for example, when a business order flows to a certain link and is not processed for a long time to enter the next link, the business order is determined to have the phenomenon of single-card single based on experience, or offline checking by an operation and maintenance personnel. Subsequent reporting of the single-card single phenomenon also needs to manually fill in a reporting order after the order single-card single is found by manual work, so that the business single-card single identification efficiency is low, and the reporting operation is troublesome. SUMMARY

[0004] The present application provides a business single-card single reporting-obstruction method, device, equipment and medium, to solve the technical problem of low business single-card single identification efficiency and troublesome reporting operation in the related art.

[0005] In a first aspect, an embodiment of the present application provides a method, which comprises:

[0006] monitoring abnormal information related to a business order;

[0007] matching an error matching rule with the abnormal information to determine whether the business order has the phenomenon of single-card single;

[0008] if yes, performing reporting-obstruction processing on the business order.

[0009] In a possible implementation manner, the monitoring of the abnormal information related to the business order comprises:

[0010] monitoring abnormal information generated by an error of the business order in a handling link and an implementation link;

[0011] recording the abnormal information and related information of the business order into a to-be-reported-obstruction task table to generate a to-be-reported-obstruction task of the business order.

[0012] In a possible implementation manner, before the matching of the error matching rule with the abnormal information, the method further comprises:

[0013] constructing a reporting-obstruction error rule library;

[0014] In response to the operation instruction for the error matching rule matched in the error reporting error rule library, performing a configuration operation of the error matching rule on the input error information and / or error code according to the operation instruction;

[0015] The table structure of the error reporting error rule library is used to configure a rule identifier, a rule type, and a matching mode of the error matching rule, and the rule type is divided according to a link to which the error information and / or error code belongs when the error information and / or error code is generated.

[0016] In a possible implementation, the error matching rule is called to match the exception information to determine whether the business order has been stuck, including:

[0017] The to-be-reported error task is read from the to-be-reported error task table, and the link to which the exception information belongs when the exception information is generated is determined according to the exception information and the business order;

[0018] The target rule type corresponding to the exception information is determined according to the link to which the exception information belongs when the exception information is generated;

[0019] The error matching rule is called in the error reporting error rule library according to the target rule type to match the exception information, to determine whether the business order has been stuck.

[0020] In a possible implementation, the matching mode includes a positive matching mode and a reverse matching mode;

[0021] The error matching rule is called to match the exception information to determine whether the business order has been stuck, including:

[0022] When the matching mode of the error matching rule is the positive matching, if the exception information matches the error matching rule, it is determined that the business order has been stuck;

[0023] When the matching mode of the error matching rule is the reverse matching, if the exception information matches the error matching rule, it is determined that the business order has not been stuck.

[0024] In a possible implementation, the positive matching mode includes an exact matching and a fuzzy matching;

[0025] The error matching rule is called to match the exception information to determine whether the business order has been stuck, including:

[0026] When the matching mode of the error matching rule is the exact matching, if the exception information is the same as the error matching rule, it is determined that the business order has been stuck;

[0027] When the matching mode of the error matching rule is the fuzzy matching, if the exception information matches a rule expression of the error matching rule, it is determined that the business order has been stuck.

[0028] In a possible implementation, the fault reporting processing on the service order comprises:

[0029] querying the fault reporting situation of the service order in the fault reporting record table according to the related information of the service order;

[0030] if the fault reporting situation of the service order is not reported, generating a fault reporting report of the service order according to the abnormal information and the related information of the service order;

[0031] transmitting the fault reporting report to the fault reporting record table, and updating the task state of the to-be-reported task of the service order to reported in the to-be-reported task table.

[0032] In a second aspect, an embodiment of the present application provides a service order card single fault reporting device, comprising:

[0033] a monitoring unit configured to monitor abnormal information related to the service order;

[0034] an identifying unit configured to call an error matching rule to match the abnormal information, so as to determine whether the service order has occurred card single;

[0035] a fault reporting unit configured to perform fault reporting processing on the service order.

[0036] In a possible implementation, the monitoring unit in the device provided by the embodiment of the present application is specifically configured to:

[0037] monitor abnormal information generated by errors occurring in the service order in the handling link and the implementation link;

[0038] record the abnormal information and the related information of the service order in the to-be-reported task table, and generate a to-be-reported task of the service order.

[0039] In a possible implementation, the device provided by the embodiment of the present application further comprises a constructing unit configured to, before calling the error matching rule to match the abnormal information:

[0040] construct a fault reporting error rule library;

[0041] in response to an operation instruction for the error matching rule in the fault reporting error rule library, perform a configuration operation of the error matching rule on the input error information and / or error code according to the operation instruction;

[0042] wherein, the table structure of the fault reporting error rule library is used to configure the rule identifier, the rule type and the matching mode of the error matching rule, and the rule type is divided according to the link to which the error information and / or error code belongs when it is generated.

[0043] In a possible implementation, the identifying unit in the device provided by the embodiment of the present application is specifically configured to:

[0044] read the abnormality information from the to-be-reported task table, and determine the link to which the abnormality information belongs according to the abnormality information and the service order;

[0045] determine the target rule type corresponding to the abnormality information according to the link to which the abnormality information belongs;

[0046] match the error matching rule with the abnormality information according to the target rule type, to determine whether the service order has a card order.

[0047] In a possible implementation manner, the device provided by the embodiment of the present application comprises a matching mode, and the identification unit is specifically configured to:

[0048] when the matching mode of the error matching rule is the positive matching, if the abnormality information matches the error matching rule, it is determined that the service order has a card order;

[0049] when the matching mode of the error matching rule is the reverse matching, if the abnormality information matches the error matching rule, it is determined that the service order does not have a card order.

[0050] In a possible implementation manner, the device provided by the embodiment of the present application comprises a positive matching mode, and the identification unit is specifically configured to:

[0051] when the matching mode of the error matching rule is the exact matching, if the abnormality information is the same as the error matching rule, it is determined that the service order has a card order;

[0052] when the matching mode of the error matching rule is the fuzzy matching, if the abnormality information matches the rule expression of the error matching rule, it is determined that the service order has a card order.

[0053] In a possible implementation manner, the device provided by the embodiment of the present application comprises a reporting unit, and the reporting unit is specifically configured to:

[0054] query the reporting situation of the service order in the reporting record table according to the related information of the service order;

[0055] if the reporting situation of the service order is not reported, generate a reporting report of the service order according to the abnormality information and the related information of the service order;

[0056] transmit the reporting report to the reporting record table, and update the task state of the to-be-reported task of the service order in the to-be-reported task table to reported.

[0057] In a third aspect, an electronic device is provided, which comprises at least one processor, at least one memory, and computer program instructions stored in the memory, and when the computer program instructions are executed by the processor, the method provided in the first aspect of the embodiment of the present application is implemented.

[0058] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the method according to the first aspect of the present application.

[0059] In the embodiment of the present application, the abnormal information related to the service order is monitored, and then the error matching rule is called to match the abnormal information, so as to determine whether the service order is blocked. Finally, in the case that the service order is blocked, the service order is handled. Compared with the related art, the service order blocking fault can be automatically identified according to the matching result of the error matching rule and the abnormal information, the identification efficiency of the service order blocking fault is improved, and after the service order blocking fault is identified, the fault handling is automatically performed, which can simplify the blocking fault handling operation and save the operation and maintenance cost consumed by manual fault handling. BRIEF DESCRIPTION OF DRAWINGS

[0060] Figure 1 A flowchart of a service order blocking fault handling method according to an embodiment of the present application is shown.

[0061] Figure 2 A flowchart of another service order blocking fault handling method according to an embodiment of the present application is shown.

[0062] Figure 3 A structural diagram of a service order blocking fault handling device according to an embodiment of the present application is shown.

[0063] Figure 4 A structural diagram of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0064] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the drawings. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0065] Some words appearing in the text will be explained below:

[0066] 1. In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after it.

[0067] The following description, in conjunction with the accompanying drawings and embodiments, provides a more detailed account of the service single card single fault reporting method, apparatus, equipment, and medium provided by the present invention.

[0068] This invention provides a method for reporting a single service card fault, such as... Figure 1 As shown, it includes:

[0069] Step S101: Monitor abnormal information related to business orders.

[0070] In real-world business scenarios, order delays can occur during both front-end business processing and back-end business execution. Therefore, in practical implementation, it is necessary to monitor abnormal information related to business orders, including abnormal information arising from errors in the processing and execution stages of business orders. Then, the abnormal information and relevant business order information are recorded in the pending fault task table to generate pending fault tasks for business orders.

[0071] For example, frontline operators may perform actions such as ordering goods and adding items to their shopping carts on the front-end business processing interface. These actions occur before the official order is generated. If database errors or validation errors occur in the live system during these operations, the system, after detecting these problems, will not only record abnormal information describing these problems, but also summarize relevant business order information such as employee ID and contact information and record it in the pending fault reporting task table.

[0072] During the backend fulfillment of business orders, the system can periodically or in real time monitor business order data. For example, it can query business order information from the order table, work order table, and interface log table to determine if there is any abnormal information in the business order. If abnormal information is detected, the order information and error information are recorded in the pending fault task table.

[0073] Step S102: Invoke the error matching rules and match them with the exception information to determine whether the business order has been blocked.

[0074] In one possible implementation, an error rule base can be built before invoking error matching rules to match exception information. The error rule base configuration supports error information generated by the network, applications, databases, etc., and error matching rules can be configured based on this error information. The error rule base supports visual configuration capabilities, providing query, addition, deletion, import, and export operations for error matching rules. After operations and maintenance personnel input operation commands for error matching rules in the fault reporting error rule base, the error rule base executes the error matching rule configuration operation according to the input error information and / or error code.

[0075] The table structure of the error rule library is used to configure the rule identification, rule type and matching mode of the error matching rule, and the rule type can be divided according to the error information and / or the link to which the error code generation belongs. The table structure of the error rule library is as follows:

[0076]

[0077]

[0078] wherein, NUMBER represents a numeric type, and VARCHAR represents a character type.

[0079] In the embodiments of the present disclosure, the error matching rule can be configured and generated according to the input error information and / or error code. In some cases, the error information and error code can be directly used as the error matching rule, and in other cases, the rule expression generated according to the error information can be used as the error matching rule.

[0080] The error information can be divided into two categories according to the business link, i.e., a business handling link and an order fulfillment link. The error information of the business handling link includes error information generated in the case of system exception, database exception, middleware exception and business exception. The error information of the order fulfillment link includes error information generated in the case of system exception, order exception, work order exception and business exception. Correspondingly, the error matching rule configured and generated according to the error information and error code can also be divided into two categories according to the business link, i.e., a business handling link and an order fulfillment link.

[0081] For example, a system exception refers to a failure caused by an abnormal program running during a service process, resulting in an abnormal service process, such as a null pointer, an illegal request, a timeout, and the like. A database exception refers to a failure caused by an unavailable database service or an error in a database table, resulting in an abnormal service process, such as a database connection failure, a non-existent table or table field, and various database errors. A middleware exception refers to an exception caused by a middleware service, resulting in an abnormal service process, such as a failure in invoking a BPM (Business Process Management) process engine, a failure in starting an ILOG (Integrated Logic) fee calculation engine, a failure in interface invocation, and the like. A service exception refers to a failure caused by a limitation of a service rule or a failure in meeting a service requirement, resulting in an abnormal service process, such as an empty user payment method, a user state error, and the like. An order exception refers to an abnormal order task processing, resulting in a carded order, such as a failure in generating a background order or a failure in an order decomposition and fulfillment process. A work order exception refers to an abnormal work order opening, resulting in a service opening failure, such as a failure in sending a work order to a network element or a network element feedback failure. A data upload failure refers to a failure in synchronizing three-party data or a subscription relationship to a billing system, resulting in a carded order.

[0082] Therefore, in a specific implementation, the error matching rule is invoked to match the exception information to determine whether the service order is carded. The pending trouble shooting task can be read from a pending trouble shooting task table, and the exception information and the service order are used to determine a link to which the exception information belongs when generated. Then, the target rule type corresponding to the exception information is determined according to the link to which the exception information belongs when generated. Finally, the error matching rule is invoked to match the exception information in the trouble shooting error rule library to determine whether the service order is carded.

[0083] In a possible implementation, the matching mode includes a positive matching mode and a reverse matching mode. The error matching rule is invoked to match the exception information to determine whether the service order is carded, including: when the matching mode of the error matching rule is the positive matching, if the exception information matches the error matching rule, it is determined that the service order is carded. When the matching mode of the error matching rule is the reverse matching, if the exception information matches the error matching rule, it is determined that the service order is not carded.

[0084] The positive matching mode includes an exact matching and a fuzzy matching. When the matching mode of the error matching rule is the exact matching, if the exception information is the same as the error matching rule, it is determined that the service order is carded. When the matching mode of the error matching rule is the fuzzy matching, if the exception information matches the rule expression of the error matching rule, it is determined that the service order is carded.

[0085] For example, the exact match can be an exact match according to the interface error code or error information, for example, a specific interface failure return information is configured, if the call interface returns the failure information consistent with the configuration information, it is considered that the business single occurs card single, and the fault condition is met. In this case, the error information and the error code can be directly used as the error matching rule.

[0086] The fuzzy match can be a fuzzy match according to the error information, for example, a regular expression is configured according to the error information to perform partial matching of the error information. The regular expression is a rule expression, which is an expression used to describe string patterns, and can be used to match, search or replace specific patterns or rules in text. Since the system error information may contain dynamic variable information, a regular expression is generated according to the error information to perform partial matching of the error information, and if the matching is successful, it is considered that the business single occurs card single, and the fault condition is met.

[0087] For example, the reverse match can be a reverse match according to the error information, such as the error information of some business rule level in some business scenarios does not belong to the fault problem, and for this case, a reverse matching mode of the error information is configured, and if the matching is successful, it is considered that the business single does not occur card single, and the fault condition is not triggered.

[0088] For example, the reverse match can also be a reverse match according to the error code, and the reverse match is performed according to the configured interface code, such as some order transparency and construction node information feedback interface, even if the interface fails, it does not affect the order construction, and if the matching of such error code is successful, it is considered that the business single does not occur card single, and such interface error does not need to be reported.

[0089] If yes, step S103 is performed.

[0090] In step S103, the fault handling of the business single is performed.

[0091] In specific implementation, the fault handling of the business single can be queried in the fault record table according to the related information of the business single. If the fault handling of the business single is not reported, a fault report of the business single is generated according to the abnormal information and the related information of the business single. The fault report is transmitted to the fault record table, and the task state of the to-be-reported task of the business single is updated to reported in the to-be-reported task table.

[0092] If the business single is identified as not card single through the error matching rule matching, the to-be-reported task is deleted in the to-be-reported task table.

[0093] For example, for the order identified as occurring card single, the order number can be used to query whether there is a reported fault order in the fault record table, if the order is not reported, the fault is automatically initiated, and the task state is updated to reported after the fault is reported successfully.

[0094] When the front-end service handling interface card single fault reporting is performed, the work number, contact information and other elements are extracted according to the preset fault reporting template, and the extracted information is filled in the fault reporting template, so as to generate the fault reporting content of the service single.

[0095] When the back-end card single fault reporting is performed, the fault reporting elements that need to be filled in are extracted according to the preset fault reporting template, and the fault reporting content is generated according to the abnormal type and error information of the card single.

[0096] In addition, for the error information that has not been configured with the error matching rule in the error rule library, when such error information appears as abnormal information, it cannot be matched successfully with the existing error matching rule in the error rule library, and the system will pop up the option of "whether to report fault". After clicking the "one-key fault reporting" option, the system will call the automatic reporting service to obtain the related information and display the one-key fault reporting page. The operation and maintenance personnel can confirm the information on this page and report the fault.

[0097] As shown in the overall flow of the business single card single fault reporting method Figure 2

[0098] The embodiments of the present disclosure can automatically identify the business single card single fault according to the matching result of the error matching rule and the abnormal information, improve the identification efficiency of the business single card single fault, and automatically perform fault reporting processing after identifying the business single card single fault, which can simplify the card single fault reporting operation and save the operation and maintenance cost consumed by manual fault reporting.

[0099] As shown in the overall flow of the business single card single fault reporting method Figure 3 Based on the same inventive concept as the method, the present disclosure also provides a business single card single fault reporting device, which comprises:

[0100] The monitoring unit 301 is configured to monitor the abnormal information related to the business single;

[0101] The identification unit is configured to call the error matching rule to match the abnormal information, so as to determine whether the business single has the card single 302;

[0102] The fault reporting unit 303 is configured to perform fault reporting processing on the business single.

[0103] In one possible implementation, the device provided by the embodiments of the present disclosure is configured such that the monitoring unit 301 is specifically configured to:

[0104] Monitor the abnormal information generated by the error of the business single in the handling link and the implementation link;

[0105] Record the abnormal information and the related information of the business single in the to-be-reported fault task table, and generate the to-be-reported fault task of the business single.

[0106] ​In a possible implementation, the device provided by the embodiment of the present application further comprises a constructing unit 304 configured to, before calling the error matching rule to match the exception information:

[0107] construct an error reporting error rule library;

[0108] in response to an operation instruction for the error matching rule in the error reporting error rule library, perform a configuration operation of the error matching rule on the input error information and / or error code according to the operation instruction;

[0109] wherein the table structure of the error reporting error rule library is configured to configure the rule identifier, the rule type and the matching mode of the error matching rule, and the rule type is divided according to the link to which the error information and / or error code belongs when generated.

[0110] In a possible implementation, the device provided by the embodiment of the present application comprises an identifying unit 302, configured to:

[0111] read the to-be-reported task from the to-be-reported task table, and determine the link to which the exception information belongs when generated according to the exception information and the business single;

[0112] determine the target rule type corresponding to the exception information according to the link to which the exception information belongs when generated;

[0113] call the error matching rule in the error reporting error rule library according to the target rule type to match the exception information, so as to determine whether the business single has a card single.

[0114] In a possible implementation, the device provided by the embodiment of the present application comprises a matching mode comprising a positive matching mode and a reverse matching mode; the identifying unit 302 is specifically configured to:

[0115] when the matching mode of the error matching rule is the positive matching mode, if the exception information matches the error matching rule, it is determined that the business single has a card single;

[0116] when the matching mode of the error matching rule is the reverse matching mode, if the exception information matches the error matching rule, it is determined that the business single does not have a card single.

[0117] In a possible implementation, the device provided by the embodiment of the present application comprises a positive matching mode comprising an exact match and a fuzzy match; the identifying unit 302 is specifically configured to:

[0118] when the matching mode of the error matching rule is the exact match, if the exception information is the same as the error matching rule, it is determined that the business single has a card single;

[0119] When the matching mode of the error matching rule is fuzzy matching, if the exception information matches the rule expression of the error matching rule, it is determined that the business order is reported.

[0120] In a possible implementation, the device provided by the embodiment of the present application is specifically configured for:

[0121] querying the reporting situation of the business order in the reporting record table according to the related information of the business order;

[0122] if the reporting situation of the business order is not reported, generating a reporting report of the business order according to the exception information and the related information of the business order;

[0123] transmitting the reporting report to the reporting record table, and updating the task state of the to-be-reported task of the business order to reported in the to-be-reported task table.

[0124] In addition, the business order carding reporting method and device can be implemented by an electronic device. Figure 4 A hardware structure schematic diagram of the electronic device is shown.

[0125] The following will be specifically described Figure 4 which shows a structure schematic diagram of the electronic device 400 suitable for implementing the embodiment of the present application. Figure 4 The electronic device shown is only an example, and should not bring any limitation to the function and use range of the embodiment of the present application.

[0126] As Figure 4 shown, the electronic device 400 can include a processing device (for example, a central processor, a graphic processor, etc.) 401, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 402 or the program loaded from the storage device 408 to the random access memory (RAM) 403 to implement the business order carding reporting method of the embodiment as described in the present disclosure. In the RAM 403, various programs and data required for the operation of the electronic device 400 are also stored. The processing device 401, the ROM 402 and the RAM 403 are connected to each other through a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0127] Generally, the following devices can be connected to the I / O interface 405: an input device 406 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 407 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 408 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 409. The communication device 409 can allow the electronic device 400 to communicate with other devices wirelessly or by wire to exchange data. AlthoughFigure 4 The electronic device 400 is illustrated with various means, but it is understood that not all of the illustrated means need be present in every embodiment. A greater or lesser number of means can alternatively be implemented.

[0128] In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for executing the methods illustrated by the flowcharts, thereby implementing the business single-card single-reporting-obstacle method as described above. In such embodiments, the computer program can be downloaded and installed from the network through the communication device 409, or installed from the storage device 408, or installed from the ROM 402. When the computer program is executed by the processing device 401, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are performed.

[0129] It should be noted that the computer-readable medium described above in the present disclosure can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium, for example, can be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination thereof. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program used or used in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take on many forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to a wire, a cable, a radio frequency (RF) link, or the like, or any suitable combination thereof.

[0130] In some embodiments, the client, server, or both can communicate using any known or later developed network protocols, such as the HyperText Transfer Protocol (HTTP), and can be interconnected with any form or medium of digital data communication (for example, a communication network) and any additional processes not shown. Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet, and peer-to-peer networks (for example, ad hoc peer-to-peer networks), as well as any current or later developed networks.

[0131] The computer-readable medium described above can be included in the electronic device described above; alternatively, the computer-readable medium can exist on its own as a separate device.

[0132] The computer-readable medium described above carries one or more programs which, when executed by the electronic device, cause the electronic device to perform:

[0133] monitoring exception information related to the service order;

[0134] calling an error matching rule to match the exception information, to determine whether the service order has occurred a card order;

[0135] if so, performing a fault handling on the service order.

[0136] Optionally, when the one or more programs are executed by the electronic device, the electronic device can further perform other steps described in the above embodiments.

[0137] Computer program code for carrying out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0138] The computer program product of the first aspect can include one or more non-transitory computer-readable media storing instructions that, when executed, cause one or more processors to perform the operations of the first aspect. The computer program product of the first aspect can include a non-transitory computer-readable medium storing code for causing a computer to perform the operations of the first aspect.

[0139] The units described in the embodiments of the present disclosure can be implemented by software, or by hardware, or by a combination of software and hardware. In some cases, the names of the units do not constitute a limitation on the units themselves.

[0140] The functions described in this specification can be implemented in hardware, software, or any combination thereof. In some embodiments, the functionality described can be provided as a service or software that can be used on a computer system, e.g., that is implemented in software, or that is provided by a service that is executed on a computer system. In some embodiments, the functions described can be implemented in software such as one or more computer programs.

[0141] In the context of the present disclosure, a machine-readable medium can be a tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0142] Compared with the related art, the business order card fault can be automatically identified according to the matching result of the error matching rule and the abnormal information, the identification efficiency of the business order card fault is improved, and after the business order card fault is identified, the fault reporting processing is automatically performed, so that the card order fault reporting operation is simplified, and the operation and maintenance cost consumed by manual fault reporting is saved.

[0143] Those skilled in the art will understand that embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage, etc.) containing computer-usable program code.

[0144] The present application is described with reference to flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce a device that implements the functions specified in the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that implements the functions specified in the flowcharts and / or block diagrams.

[0145] These computer program instructions can also be stored in a computer-readable memory that can direct the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including instruction apparatus, which implements the functions specified in the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that implements the functions specified in the flowcharts and / or block diagrams.

[0146] These computer program instructions can also be loaded into a computer or other programmable data processing apparatus, so that a series of operation steps are performed on the computer or other programmable data processing apparatus to produce a computer-implemented process, so that the instructions executed on the computer or other programmable data processing apparatus provide a process for implementing the functions specified in the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1steps of the functions specified in the block or blocks.

[0147] While the preferred embodiments of the application have been described, additional variations and modifications can be made to the preferred embodiments by those skilled in the art once they learn of the basic inventive concepts. Therefore, the appended claims are intended to encompass within their scope all such variations and modifications as are included within the scope of the application.

[0148] It is apparent that those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. It is therefore intended to include all such changes and modifications in so far as they come within the scope of the claims or the equivalent thereof.

Claims

1. A method for service single card single report trouble, characterized in that, The method comprises the following steps: monitoring abnormal information related to a service order; constructing a fault reporting error rule library, and in response to an operation instruction for a fault matching rule in the fault reporting error rule library, performing a configuration operation of the fault matching rule on the input error information and / or error code according to the operation instruction; reading a to-be-reported task from a to-be-reported task table, and determining a link to which the abnormal information belongs when the abnormal information occurs according to the abnormal information and the service order; determining a target rule type corresponding to the abnormal information according to the link to which the abnormal information belongs when the abnormal information occurs; and matching the abnormal information with a fault matching rule in the fault reporting error rule library according to the target rule type, so as to determine whether a card order occurs for the service order; wherein a table structure of the fault reporting error rule library is used to configure a rule identifier, a rule type and a matching mode of the fault matching rule, and the rule type is divided according to a link to which error information and / or error code belongs when the error information and / or error code occurs; if yes, querying a fault reporting record table according to related information of the service order to obtain a fault reporting situation of the service order; if the fault reporting situation of the service order is not reported, generating a fault reporting report of the service order according to the abnormal information and the related information of the service order; and transmitting the fault reporting report to the fault reporting record table, and updating a task state of the to-be-reported task of the service order to reported in the to-be-reported task table.

2. The method of claim 1, wherein, The monitoring abnormal information related to a service order comprises the following steps: monitoring abnormal information generated due to an error occurring in a handling link and an implementation link of the service order; recording the abnormal information and related information of the service order into a to-be-reported task table, and generating a to-be-reported task of the service order.

3. The method of claim 1, wherein, The matching mode comprises a forward matching mode and a reverse matching mode; The matching of the fault matching rule with the abnormal information to determine whether a card order occurs for the service order comprises the following steps: when the matching mode of the fault matching rule is forward matching, if the abnormal information matches the fault matching rule, it is determined that a card order occurs for the service order; when the matching mode of the fault matching rule is reverse matching, if the abnormal information matches the fault matching rule, it is determined that a card order does not occur for the service order.

4. The method of claim 3, wherein, The forward matching mode comprises exact matching and fuzzy matching; The matching of the fault matching rule with the abnormal information to determine whether a card order occurs for the service order comprises the following steps: when the matching mode of the fault matching rule is exact matching, if the abnormal information is the same as the fault matching rule, it is determined that a card order occurs for the service order; when the matching mode of the fault matching rule is fuzzy matching, if the abnormal information matches a rule expression of the fault matching rule, it is determined that a card order occurs for the service order.

5. A service single card single report trouble device, characterized by, The method comprises the following steps: a monitoring unit, configured to monitor abnormal information related to a service order; An identifying unit is configured to construct a fault reporting error rule library, and in response to an operation instruction for a fault matching rule in the fault reporting error rule library, perform a configuration operation of the fault matching rule on the input error information and / or error code according to the operation instruction; read a to-be-reported fault task from a to-be-reported fault task table, and determine a link to which the abnormal information belongs when the abnormal information is generated according to the abnormal information and the service order; determine a target rule type corresponding to the abnormal information according to the link to which the abnormal information belongs when the abnormal information is generated; and perform matching between a fault matching rule and the abnormal information according to the target rule type in the fault reporting error rule library, to determine whether the service order is a stuck order; wherein a table structure of the fault reporting error rule library is configured to configure a rule identifier, a rule type and a matching mode of the fault matching rule, and the rule type is divided according to a link to which error information and / or error code belongs when the error information and / or error code is generated; A fault reporting unit is configured to query a fault reporting record table according to related information of the service order to determine a fault reporting situation of the service order; if the fault reporting situation of the service order is not reported, generate a fault reporting report of the service order according to the abnormal information and the related information of the service order; transmit the fault reporting report to the fault reporting record table, and update a task state of the to-be-reported fault task of the service order to a reported state in the to-be-reported fault task table.

6. An electronic device, comprising: comprising: at least one processor, at least one memory, and computer program instructions stored in the memory that, when executed by the processor, implement the method of any one of claims 1-4.

7. A computer-readable storage medium having stored thereon computer program instructions, wherein, when the computer program instructions are executed by the processor, implement the method of any one of claims 1-4.

Images