Abnormity recognition expansion method, device and equipment and storage medium thereof

Abstract

The embodiment of the invention belongs to the technical field of research and development design, is applied to a program exception front setting scene, and relates to an exception recognition expansion method and device, equipment and a storage medium thereof. Inputting the service item configuration form into a preset exception identification expansion component; obtaining all the expanded abnormal display fields; taking all the expanded abnormal display fields as self-defined abnormal display fields, and generating corresponding calling paths; and adding the calling path to an exception display field acquisition configuration file of a target service system, and configuring an exception trigger function and a calling priority different from universality. The method is applied to the financial application field with various program functions and redundant data content, the program exception position can be accurately and quickly positioned by combining exception code values and exception message fields corresponding to service item names, calling method names, calling form names and form field names, and operation and maintenance personnel can quickly perform exception handling.

Description

Technical Field

[0001] This application relates to the technical field of R & D design, and is applied to the scenario of pre - setting program exceptions. In particular, it relates to an exception recognition and expansion method, device, equipment and its storage medium. Background Technique

[0002] Exception handling is an indispensable part of database procedural languages, which ensures that the program can quickly handle and recover when encountering errors. It is of great significance for ensuring data integrity, improving system stability, enhancing code robustness, improving development efficiency, enhancing user experience, and supporting the accurate expression of business logic. However, many database procedural languages only support exceptions set by system or general - purpose exception reporting components, such as Exception or Error, and lack a flexible solution for supporting custom exceptions.

[0003] Using the exception representation method that only supports exceptions set by system or general - purpose exception reporting components for exception screening and handling often has certain limitations, and is not detailed and accurate enough in exception recognition. For example, in the medical business field, when using a general - purpose exception reporting component, the field information or exception code value reported by it may not be understood by medical staff, and it is impossible to generate exception information that medical staff can easily understand. For instance, when the page of a certain medical application system cannot be loaded, the description of the error type is not detailed enough, and the error information of the exception is not intuitive enough, which is not conducive to operation and maintenance personnel or users to intuitively confirm and troubleshoot exceptions. Summary of the Invention

[0004] The purpose of the embodiments of this application is to propose an exception recognition and expansion method, device, equipment and its storage medium to solve the problem that using the existing exception representation method leads to certain limitations in exception troubleshooting, is not detailed and accurate enough in exception recognition, and is not conducive to operation and maintenance personnel or users to intuitively confirm and troubleshoot exceptions.

[0005] To solve the above - mentioned technical problems, the embodiments of this application provide an exception recognition and expansion method, which adopts the following technical solutions:

[0006] An exception recognition and expansion method includes the following steps:

[0007] Obtain the service item configuration form of the target business system, where at least one functional service item is recorded in the service item configuration form, at least one call method is recorded in each functional service item, and each call method matches a corresponding call form and form field;

[0008] Input the service item configuration form into a preset exception recognition and extension component, where the preset exception recognition and extension component includes syntax rules for exception variable declaration and construction rules for exception code value generation;

[0009] Obtain all the exception display fields extended by the exception recognition and extension component according to the service item configuration form, the syntax rules, and the construction rules;

[0010] Cache all the extended exception display fields as custom exception display fields in a preset storage space of the target business system;

[0011] Generate a corresponding call path according to the storage path of the custom exception display fields in the preset storage space;

[0012] Add the call path to the exception display field acquisition configuration file of the target business system, and configure an exception trigger function and call priority different from the generality, where the exception display field acquisition configuration file is provided by a general exception display service component used by the target business system, and the general exception display service component stipulates a general exception trigger function.

[0013] Further, after the step of obtaining the service item configuration form of the target business system, the method further includes:

[0014] Parse the service item configuration form to obtain all the function service item names recorded in the service item configuration form, the call method names respectively included in all the function service items, the call form names respectively corresponding to all the call methods, and the form field names;

[0015] Hierarchically organize the service item names, the call method names, the call form names, and the form field names according to the call relationship to obtain a hierarchically organized result.

[0016] Further, the step of inputting the service item configuration form into a preset exception recognition and extension component specifically includes:

[0017] Input the hierarchically organized result including the service item names, the call method names, the call form names, and the form field names into the exception recognition and extension component;

[0018] Before the step of obtaining all the exception display fields extended by the exception recognition and extension component according to the service item configuration form, the syntax rules, and the construction rules, the method further includes:

[0019] Start the exception recognition and extension component;

[0020] Taking the hierarchical sorting result including the service item name, the calling method name, the calling form name, and the form field name as the expansion control relationship, and taking the syntax rule and the construction rule as the expansion generation rules, generate all the expanded exception display fields;

[0021] The step of obtaining all the expanded exception display fields of the exception recognition expansion component according to the service item configuration form, the syntax rule, and the construction rule specifically includes:

[0022] Obtain all the expanded exception display fields generated according to the expansion control relationship and the expansion generation rules.

[0023] Further, the step of taking the hierarchical sorting result including the service item name, the calling method name, the calling form name, and the form field name as the expansion control relationship, and taking the syntax rule and the construction rule as the expansion generation rules, and generating all the expanded exception display fields specifically includes:

[0024] Generate the exception variable names corresponding to the service item name, the calling method name, the calling form name, and the form field name respectively according to the expansion control relationship and the syntax rule;

[0025] Generate different exception message fields according to the exception variable names corresponding to the service item name, the calling method name, the calling form name, and the form field name respectively;

[0026] Generate the exception code values corresponding to the service item name, the calling method name, the calling form name, and the form field name respectively according to the expansion control relationship and the construction rule;

[0027] Perform variable-code value mapping relationship binding processing on the exception variable names and exception code values corresponding to the same service item name, the same calling method name, the same calling form name, and the same form field name to obtain the variable-code value mapping relationship binding result;

[0028] Take the exception variable names and exception code values corresponding to the service item name, the calling method name, the calling form name, and the form field name respectively, the exception message fields corresponding to the service item name, the calling method name, the calling form name, and the form field name respectively, and the variable-code value mapping relationship binding result as all the expanded exception display fields.

[0029] Further, the step of generating the exception variable names corresponding to the service item name, the calling method name, the calling form name, and the form field name respectively according to the expansion control relationship and the syntax rule specifically includes:

[0030] Use the first differentiating identifier and the service item name for splicing to generate the exception variable names corresponding to different service item names respectively;

[0031] In combination with the extended control relationship, use the second differentiating identifier and the call method name to continue splicing on the basis of the exception variable names corresponding to different service item names respectively, to generate the exception variable names corresponding to different call method names respectively;

[0032] In combination with the extended control relationship, use the third differentiating identifier and the call form name to continue splicing on the basis of the exception variable names corresponding to different call method names respectively, to generate the exception variable names corresponding to different call form names respectively;

[0033] In combination with the extended control relationship, use the fourth differentiating identifier and the form field name to continue splicing on the basis of the exception variable names corresponding to different call form names respectively, to generate the exception variable names corresponding to different form field names respectively.

[0034] Further, the step of generating the exception code values corresponding to the service item name, the call method name, the call form name, and the form field name respectively according to the extended control relationship and the construction rule specifically includes:

[0035] Generate the exception code values corresponding to different service item names respectively according to the first construction rule;

[0036] In combination with the extended control relationship, according to the second construction rule, perform code value splicing on the basis of the exception code values corresponding to different service item names respectively, to generate the exception code values corresponding to different call method names respectively;

[0037] In combination with the extended control relationship, according to the third construction rule, perform code value splicing on the basis of the exception code values corresponding to different call method names respectively, to generate the exception code values corresponding to different call form names respectively;

[0038] In combination with the extended control relationship, according to the fourth construction rule, perform code value splicing on the basis of the exception code values corresponding to different call form names respectively, to generate the exception code values corresponding to different form field names respectively.

[0039] Further, before performing the step of adding the call path to the exception display field acquisition configuration file of the target business system and configuring an exception trigger function and a call priority different from the generality, the method further includes:

[0040] Obtain different exception message fields generated according to the exception variable names corresponding to the service item name, call method name, call form name, and form field name respectively;

[0041] The exception trigger function includes two call parameters, which are the exception code value and the exception message field respectively. The steps of adding the call path to the exception display field acquisition configuration file of the target business system and configuring an exception trigger function and call priority different from the generality are specifically as follows:

[0042] Add the call paths of the exception code values corresponding to the service item name, call method name, call form name, and form field name respectively to the exception display field acquisition configuration file;

[0043] Add the call paths of the exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively to the exception display field acquisition configuration file;

[0044] Set the call priority of the exception trigger function to be higher than that of the general exception trigger function.

[0045] To solve the above technical problems, the embodiment of the present application also provides an exception recognition expansion device, which adopts the following technical solutions:

[0046] An exception recognition expansion device, including:

[0047] A service item configuration form acquisition module, used to acquire the service item configuration form of the target business system, where at least one functional service item is recorded in the service item configuration form, and at least one call method is recorded in each functional service item, and each call method matches a corresponding call form and form field;

[0048] A service item configuration form input module, used to input the service item configuration form into a preset exception recognition expansion component, where the preset exception recognition expansion component contains syntax rules for exception variable declaration and construction rules for exception code value generation;

[0049] A custom exception display field acquisition module, used to acquire all the exception display fields expanded by the exception recognition expansion component according to the service item configuration form, the syntax rules, and the construction rules;

[0050] A custom exception display field caching module, used to cache all the expanded exception display fields as custom exception display fields into a preset storage space of the target business system;

[0051] A call path generation module, configured to generate a corresponding call path according to the storage path of the customized exception display field in the preset storage space;

[0052] A relevant configuration content adding module, configured to add the call path to an exception display field acquisition configuration file of the target business system, and configure an exception trigger function and a call priority different from the generality, where the exception display field acquisition configuration file is provided by a general exception display service component used by the target business system, and a general exception trigger function is specified in the general exception display service component.

[0053] To solve the above technical problems, an embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0054] A computer device includes a memory and a processor. A computer-readable instruction is stored in the memory. When the processor executes the computer-readable instruction, the steps of the above-mentioned exception recognition and extension method are implemented.

[0055] To solve the above technical problems, an embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0056] A computer-readable storage medium has a computer-readable instruction stored thereon. When the computer-readable instruction is executed by a processor, the steps of the above-mentioned exception recognition and extension method are implemented.

[0057] Compared with the prior art, the embodiments of the present application mainly have the following beneficial effects:

[0058] In the exception recognition and extension method described in the embodiments of the present application, by obtaining a service item configuration form of a target business system; inputting the service item configuration form into a preset exception recognition and extension component; obtaining all exception display fields extended by the exception recognition and extension component according to the service item configuration form, the syntax rule, and the construction rule; using the extended all exception display fields as customized exception display fields and caching them in a preset storage space of the target business system; generating a corresponding call path according to the storage path of the customized exception display field in the preset storage space; adding the call path to an exception display field acquisition configuration file of the target business system, and configuring an exception trigger function and a call priority different from the generality. Applying the exception recognition and extension method to the business program exception troubleshooting scenario can accurately and quickly locate the program exception location by combining the exception code values and exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively, which helps the operation and maintenance personnel to quickly handle the exception. Description of the Drawings

[0059] To more clearly illustrate the solutions in this application, the following will briefly introduce the accompanying drawings required for the description of the embodiments of this application. Obviously, the accompanying drawings in the following description are some embodiments of this application. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can also be obtained based on these drawings.

[0060] Figure 1 is an exemplary system architecture diagram to which this application can be applied;

[0061] Figure 2 is a flowchart of an embodiment of the anomaly recognition and expansion method according to this application;

[0062] Figure 3 is a flowchart of a specific embodiment of parsing and organizing the service item configuration form in the anomaly recognition and expansion method described in this application;

[0063] Figure 4 is a flowchart of a specific embodiment of generating all the expanded anomaly display fields in the anomaly recognition and expansion method described in this application;

[0064] Figure 5 is Figure 4 a flowchart of a specific embodiment of step 402 shown;

[0065] Figure 6 is Figure 5 a flowchart of a specific embodiment of step 501 shown;

[0066] Figure 7 is Figure 5 a flowchart of a specific embodiment of step 503 shown;

[0067] Figure 8 is Figure 2 a flowchart of a specific embodiment of step 206 shown;

[0068] Figure 9 is a schematic structural diagram of an embodiment of the anomaly recognition and expansion device according to this application;

[0069] Figure 10 is a schematic structural diagram of an embodiment of the computer device according to this application. Detailed implementation manners

[0070] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terms used in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above drawings are intended to cover non-exclusive inclusion. The terms "first", "second", etc. in the specification and claims of this application or the above drawings are used to distinguish different objects and not to describe a specific order.

[0071] Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The phrase appearing in various places in the specification is not necessarily referring to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive of other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0072] To enable those skilled in the art of this technology to better understand the solution of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0073] As Figure 1 shown, the system architecture 100 may include a terminal device 101, a network 102, and a server 103. The terminal device 101 may be a laptop computer 1011, a tablet computer 1012, or a mobile phone 1013. The network 102 is a medium for providing a communication link between the terminal device 101 and the server 103. The network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0074] Users can use the terminal device 101 to interact with the server 103 through the network 102 to receive or send messages, etc. Various communication client applications may be installed on the terminal device 101, such as a web browser application, a shopping application, a search application, an instant messaging tool, an email client, a social platform software, etc.

[0075] The terminal device 101 can be various electronic devices with a display screen and supporting web browsing. In addition to the laptop 1011, tablet computer 1012, or mobile phone 1013, the terminal device 101 can also be an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV) player, a laptop portable computer, a desktop computer, and the like.

[0076] The server 103 can be a server that provides various services, such as a background server that supports the pages displayed on the terminal device 101.

[0077] It should be noted that the anomaly recognition and extension method provided by the embodiments of the present application is generally executed by the server. Correspondingly, the anomaly recognition and extension device is generally set in the server.

[0078] It should be understood that Figure 1 the numbers of the terminal devices, networks, and servers in

[0079] Continue to refer to Figure 2 , which shows a flowchart of an embodiment of the anomaly recognition and extension method according to the present application. The anomaly recognition and extension method includes the following steps:

[0080] Step 201, obtain a service item configuration form of the target business system, where at least one functional service item is recorded in the service item configuration form, at least one call method is recorded in each functional service item, and each call method matches a corresponding call form and form field.

[0081] In this embodiment, the target business system includes a medical service application system, a financial wealth management business system, a financial loan business system, a financial insurance business system, a financial claim settlement business system, and the like.

[0082] Taking the financial claim settlement business system as an example, the service item configuration form may include a user login service item for the client, a user claim data upload service item, a claim request result feedback receiving service item, and may also include a claim data verification service item, a claim amount calculation service item, a claim result reporting service item, a claim progress display service item, etc. for the server side.

[0083] It should be understood that the service item configuration form may contain multiple service items, and each service item contains multiple call methods. For example, in the user login service item, it includes the calls of input methods, verification methods, page redirection methods, etc. When each call method is called, it involves operating different call forms and form fields. Here, the service item name, the call method name, the call form name, and the form field name are pre-written into the service item configuration form according to the business logic call relationship, so as to facilitate subsequent parsing of the service item configuration form and setting the exception display fields by combining the specific business content and the form of specific operations.

[0084] Step 202, input the service item configuration form into a preset exception recognition and extension component, where the preset exception recognition and extension component contains a syntax rule for exception variable declaration and a construction rule for exception code value generation.

[0085] In this embodiment, the preset exception recognition and extension component can be implanted into the target business system in the form of a plug-in component for the target business system to flexibly expand the exception display fields.

[0086] Specifically, for the syntax rule for exception variable declaration, for example, for the service item name, it is stipulated that the exception variable declaration is carried out in the way of splicing the service item name with the first distinguishing identifier. Assuming that the service item name of the login service item is loginService and the first distinguishing identifier is "#", the exception variable declaration result corresponding to the service item name is "#loginService".

[0087] For the construction rule for exception code value generation, for example, for the service item name, it is stipulated that the exception code value is generated according to the first construction rule. Assuming that the first construction rule is to uniformly assign the exception code value to the service item name in binary. For example, the binary code corresponding to the login service item is 0001, then the binary code 0001 is set as the exception code value of the login service item.

[0088] It should be understood that the syntax rule for exception variable declaration and the construction rule for exception code value generation are not only specified at the service item level, but also specified at the levels of call method name, call form name, and form field name respectively. By making exception recognition and extension regulations at the levels of service item, call method name, call form name, and form field name respectively, it is convenient to accurately and quickly locate the program exception position by combining the exception code values and exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively, which helps the operation and maintenance personnel to quickly handle exceptions.

[0089] Step 203: Obtain all the exception display fields extended by the exception recognition extension component based on the service item configuration form, the syntax rules, and the construction rules.

[0090] Step 204: Cache all the extended exception display fields as custom exception display fields in the preset storage space of the target business system.

[0091] By obtaining all the exception display fields extended by the exception recognition extension component based on the service item configuration form, the syntax rules, and the construction rules, and caching all the extended exception display fields as custom exception display fields in the preset storage space of the target business system, it is convenient to use the custom exception display fields during the actual business exception troubleshooting and business maintenance processes.

[0092] Step 205: Generate a corresponding call path according to the storage path of the custom exception display fields in the preset storage space.

[0093] Step 206: Add the call path to the exception display field acquisition configuration file of the target business system, and configure an exception trigger function and a call priority different from the generality, where the exception display field acquisition configuration file is provided by the general exception display service component used by the target business system, and the general exception trigger function is specified in the general exception display service component.

[0094] By configuring an exception trigger function and a call priority different from the generality in the exception display field acquisition configuration file of the target business system, it is possible to first use this exception trigger function and then use the general exception trigger function during the subsequent actual exception troubleshooting. This is convenient for the operation and maintenance personnel to quickly locate and handle exceptions in combination with the custom exception display fields.

[0095] In this embodiment, by obtaining a service item configuration form of a target business system; inputting the service item configuration form into a preset exception recognition and extension component; obtaining all exception display fields extended by the exception recognition and extension component according to the service item configuration form, the syntax rules, and the construction rules; using the extended all exception display fields as custom exception display fields and caching them in a preset storage space of the target business system; generating a corresponding call path according to the storage path of the custom exception display fields in the preset storage space; adding the call path to an exception display field acquisition configuration file of the target business system, and configuring an exception trigger function and a call priority different from the generality. Applying the exception recognition and extension method to the scenario of business program exception troubleshooting, especially in the financial application field with numerous program functions and redundant data content, can accurately and quickly locate the program exception position by combining the exception code values and exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively, which helps the operation and maintenance personnel quickly handle exceptions.

[0096] Specifically, for example: applying the exception recognition and extension method to a medical service application system can combine the business processes of medical staff and use the exception code values and exception display fields named by the medical staff themselves, which is convenient for medical staff to understand exception messages and fully combines medical business information; furthermore, applying the exception recognition and extension method to a financial claims business system can combine financial business information and use the exception code values and exception display fields named by financial practitioners themselves, which is convenient for financial practitioners to understand exception messages and fully combines financial business information. The above exception code values and exception display fields can be generated using database language and pre-put into the target cache library, and when in use, corresponding call languages or statements are used for call and display.

[0097] Continue to refer to Figure 3 , in some alternative implementation manners, after step 201, it further includes a step of parsing and organizing the service item configuration form. Figure 3 FIG. is a flowchart of a specific embodiment of parsing and organizing the service item configuration form in the exception recognition and extension method of the present application, including the following steps:

[0098] Step 301, parsing the service item configuration form to obtain all function service item names recorded in the service item configuration form, call method names respectively included in all function service items, call form names corresponding to all call methods, and form field names.

[0099] Step 302: Hierarchically organize the service item name, the calling method name, the calling form name, and the form field name according to the call relationship to obtain a hierarchically organized result.

[0100] In this embodiment, by parsing and organizing the service item configuration form, a hierarchically organized result is obtained to facilitate subsequent generation of exception display fields based on the hierarchically organized result.

[0101] In this embodiment, the step of inputting the service item configuration form into a preset exception recognition and extension component specifically includes: inputting the hierarchically organized result including the service item name, the calling method name, the calling form name, and the form field name into the exception recognition and extension component.

[0102] Continue to refer to Figure 4 , in some alternative implementation manners, before step 203, there is also a step of generating all the extended exception display fields. Figure 4 FIG.

[0103] Step 401: Start the exception recognition and extension component;

[0104] Step 402: Use the hierarchically organized result including the service item name, the calling method name, the calling form name, and the form field name as the extension control relationship, and use the syntax rule and the construction rule as the extension generation rules to generate all the extended exception display fields.

[0105] In this embodiment, the step of obtaining all the extended exception display fields obtained by the exception recognition and extension component according to the service item configuration form, the syntax rule, and the construction rule specifically includes: obtaining all the exception display fields generated according to the extension control relationship and the extension generation rules.

[0106] Specifically, generate all the exception display fields according to the extension control relationship and the extension generation rules to ensure that all the generated exception display fields are closely connected to the hierarchically organized result of the service item name, the calling method name, the calling form name, and the form field name in the business logic, so as to quickly locate the exceptions in the business program through the exception display fields.

[0107] Continue to refer to Figure 5 , Figure 5 is Figure 4 A flowchart of a specific embodiment of step 402 shown above, including the following steps:

[0108] Step 501: Generate the exception variable names corresponding to the service item name, call method name, call form name, and form field name respectively according to the extended control relationship and the syntax rules;

[0109] Step 502: Generate different exception message fields according to the exception variable names corresponding to the service item name, call method name, call form name, and form field name respectively;

[0110] Step 503: Generate the exception code values corresponding to the service item name, call method name, call form name, and form field name respectively according to the extended control relationship and the construction rules;

[0111] Step 504: Perform variable and code value mapping relationship binding processing on the exception variable names and exception code values corresponding to the same service item name, the same call method name, the same call form name, and the same form field name to obtain the variable and code value mapping relationship binding result;

[0112] Step 505: Use the exception variable names and exception code values corresponding to the service item name, call method name, call form name, and form field name respectively, the exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively, and the variable and code value mapping relationship binding result as all the extended exception display fields.

[0113] Specifically, for the service item name, call method name, call form name, and form field name, exception variable names, exception code values, and exception message fields are generated respectively, and the mapping relationship binding result between the exception variable name and the exception code value is set. This is for subsequent exception location screening in combination with custom exception display fields.

[0114] Continue to refer to Figure 6 , Figure 6 is Figure 5 a flowchart of a specific embodiment of step 501 shown in

[0115] Step 601: Concatenate the first differentiation identifier and the service item name to generate the exception variable names corresponding to different service item names respectively;

[0116] Step 602: In combination with the extended control relationship, concatenate the second differentiation identifier and the call method name on the basis of the exception variable names corresponding to different service item names respectively to generate the exception variable names corresponding to different call method names respectively;

[0117] Specifically, for example: after being processed in step 601, the obtained abnormal variable name corresponding to the login service item is "#loginService", and at this time, the first distinguishing identifier is "#"; assuming that there is a user name verification method userCheck corresponding to the login service item and the second distinguishing identifier is "##", then the abnormal variable name corresponding to the user name verification method may be "#loginService##userCheck".

[0118] Step 603: Combine the extended control relationship, and use the third distinguishing identifier and the call form name to continue splicing on the basis of the abnormal variable names corresponding to different call method names respectively, so as to generate the abnormal variable names corresponding to different call form names respectively;

[0119] Step 604: Combine the extended control relationship, and use the fourth distinguishing identifier and the form field name to continue splicing on the basis of the abnormal variable names corresponding to different call form names respectively, so as to generate the abnormal variable names corresponding to different form field names respectively.

[0120] Similarly, the abnormal variable names corresponding to different call form names respectively and the abnormal variable names corresponding to different form field names respectively can be obtained in sequence. The above first distinguishing identifier, second distinguishing identifier, third distinguishing identifier, and fourth distinguishing identifier can be set by the operation and maintenance personnel themselves.

[0121] Continue to refer to Figure 7 , Figure 7 Yes Figure 5 is a flowchart of a specific embodiment of step 503 shown in

[0122] Step 701: Generate the abnormal code values corresponding to different service item names according to the first construction rule;

[0123] Step 702: Combine the extended control relationship, and according to the second construction rule, perform code value splicing on the basis of the abnormal code values corresponding to different service item names respectively, so as to generate the abnormal code values corresponding to different call method names respectively;

[0124] Step 703: Combine the extended control relationship, and according to the third construction rule, perform code value splicing on the basis of the abnormal code values corresponding to different call method names respectively, so as to generate the abnormal code values corresponding to different call form names respectively;

[0125] Step 704: Combine the extended control relationship, and according to the fourth construction rule, perform code value splicing on the basis of the abnormal code values corresponding to different call form names respectively, so as to generate the abnormal code values corresponding to different form field names respectively.

[0126] Specifically, the first construction rule, the second construction rule, the third construction rule, and the fourth construction rule can also be set by the operation and maintenance personnel. For example, the first construction rule, the second construction rule, the third construction rule, and the fourth construction rule respectively construct the code values of 8-bit binary codes as the exception code values corresponding to different service item names, the code values of 16-bit binary codes as the exception code values corresponding to different call method names, the code values of 32-bit binary codes as the exception code values corresponding to different call form names, and the code values of 20-bit binary codes as the exception code values corresponding to different form field names.

[0127] In this embodiment, before performing the step of adding the call path to the exception display field acquisition configuration file of the target business system and configuring an exception trigger function and a call priority different from the generality, the method further includes: obtaining different exception message fields generated according to the exception variable names corresponding to the service item name, the call method name, the call form name, and the form field name respectively.

[0128] In this embodiment, the exception trigger function includes two call parameters, which are the exception code value and the exception message field respectively. Specifically, when the exception trigger function is triggered, it will, according to the first call parameter (exception code value), combined with the binding result of the mapping relationship between the exception variable name and the exception code value, screen out the corresponding exception variable name, and then, according to the position information of the exception variable name in the exception trigger statement, use the first call parameter (exception code value) and the second call parameter (exception message field) as the actual output message for replacement output. That is, when outputting the exception message, the exception code value and the exception message field corresponding to the exception variable name are directly output, which is convenient for subsequent exception troubleshooting and positioning.

[0129] Continue to refer to Figure 8 , Figure 8 is Figure 2 A flowchart of a specific embodiment of step 206 shown in the figure, including the following steps:

[0130] Step 801, add the call paths of the exception code values corresponding to the service item name, the call method name, the call form name, and the form field name respectively to the exception display field acquisition configuration file;

[0131] Step 802, add the call paths of the exception message fields corresponding to the service item name, the call method name, the call form name, and the form field name respectively to the exception display field acquisition configuration file;

[0132] Step 803, set the call priority of the exception trigger function to be higher than that of the general exception trigger function.

[0133] Specifically, the calling paths of the exception code values ​​corresponding to the service item name, calling method name, calling form name, and form field name are added to the exception display field acquisition configuration file, and the calling paths of the exception message fields corresponding to the service item name, calling method name, calling form name, and form field name are added to the exception display field acquisition configuration file, and the calling priority of the exception trigger function is set higher than the general exception trigger function, so as to achieve priority calling of the custom exception trigger function for exception display field output when troubleshooting business program exceptions, so as to facilitate operation and maintenance personnel to perform exception troubleshooting in combination with the custom exception display fields.

[0134] The present application obtains a service item configuration form of a target business system, wherein the service item configuration form records at least one functional service item, each functional service item records at least one calling method, and each calling method matches a corresponding calling form and form field; inputs the service item configuration form into a preset exception identification extension component, wherein the preset exception identification extension component contains grammatical rules for abnormal variable declaration and construction rules for abnormal code value generation; obtains all abnormal display fields extended by the abnormal identification extension component according to the service item configuration form, the grammatical rules and the construction rules; caches all the extended abnormal display fields as custom abnormal display fields in a preset storage space of the target business system; generates a corresponding calling path according to the storage path of the custom abnormal display field in the preset storage space; adds the calling path to the abnormal display field acquisition configuration file of the target business system, and configures an abnormal trigger function and a calling priority different from the general one, wherein the abnormal display field acquisition configuration file is provided by a general abnormal display service component used by the target business system, and a general abnormal trigger function is specified in the general abnormal display service component. The exception identification expansion method is applied to business program exception troubleshooting scenarios, especially in financial application fields with numerous program functions and complex data content. It can combine the exception code values ​​and exception message fields corresponding to the service item name, calling method name, calling form name, and form field name, respectively, to accurately and quickly locate the program exception location, which helps operation and maintenance personnel to quickly handle exceptions.

[0135] It should be understood that the main focus of the present invention is that, through this anomaly recognition extension method, operation and maintenance personnel or system users can, according to their personal text expression habits, customize the settings of custom anomaly recognition extension components, custom anomaly code values, custom anomaly display fields, and set a custom anomaly trigger function with a call priority higher than that of the general anomaly trigger function. In addition, using this anomaly recognition extension method, the custom anomaly recognition extension components, custom anomaly code values, custom anomaly display fields, and custom anomaly trigger functions can be encapsulated into an anomaly recognition extension plugin, facilitating operation and maintenance personnel or system users to perform anomaly monitoring and personalized use according to the custom anomaly display fields in multiple systems they are responsible for, and facilitating users to understand anomalies.

[0136] Embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to obtain the best results.

[0137] Artificial intelligence basic technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, and mechatronics. Artificial intelligence software technologies mainly include several major directions such as computer vision technology, robotics, biometric technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0138] In the embodiments of the present application, by obtaining a service item configuration form of a target business system; inputting the service item configuration form into a preset exception recognition and extension component, where the preset exception recognition and extension component includes a syntax rule for exception variable declaration and a construction rule for exception code value generation; obtaining all exception display fields extended by the exception recognition and extension component according to the service item configuration form, the syntax rule, and the construction rule; caching all the extended exception display fields as custom exception display fields into a preset storage space of the target business system; generating a corresponding call path according to the storage path of the custom exception display fields in the preset storage space; adding the call path to an exception display field acquisition configuration file of the target business system, and configuring an exception trigger function and a call priority different from the generality. Applying the exception recognition and extension method to the scenario of business program exception troubleshooting, especially in the financial application field with numerous program functions and redundant data content, can accurately and quickly locate the program exception location by combining the exception code values and exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively, which helps the operation and maintenance personnel quickly handle exceptions.

[0139] Further referring to Figure 9 , as an implementation of the method shown above Figure 2 , the present application provides an embodiment of an exception recognition and extension device. This device embodiment corresponds to Figure 2 the method embodiment shown, and this device can be specifically applied to various electronic devices.

[0140] As Figure 9 shown, the exception recognition and extension device 900 described in this embodiment includes: a service item configuration form acquisition module 901, a service item configuration form input module 902, a custom exception display field acquisition module 903, a custom exception display field caching module 904, a call path generation module 905, and a relevant configuration content addition module 906. Among them:

[0141] The service item configuration form acquisition module 901 is used to obtain a service item configuration form of a target business system, where at least one functional service item is recorded in the service item configuration form, and at least one call method is recorded in each functional service item, and each call method matches a corresponding call form and form field;

[0142] The service item configuration form input module 902 is used to input the service item configuration form into a preset exception recognition and extension component, where the preset exception recognition and extension component includes a syntax rule for exception variable declaration and a construction rule for exception code value generation;

[0143] Custom exception display field acquisition module 903, which is used to acquire all the exception display fields extended by the exception recognition and extension component according to the service item configuration form, the syntax rules, and the construction rules;

[0144] Custom exception display field caching module 904, which is used to cache all the extended exception display fields as custom exception display fields into a preset storage space of the target business system;

[0145] Call path generation module 905, which is used to generate a corresponding call path according to the storage path of the custom exception display fields in the preset storage space;

[0146] Related configuration content addition module 906, which is used to add the call path to the exception display field acquisition configuration file of the target business system, and configure an exception trigger function and a call priority different from the generality, where the exception display field acquisition configuration file is provided by a general exception display service component used by the target business system, and a general exception trigger function is specified in the general exception display service component.

[0147] This application obtains the service item configuration form of the target business system; inputs the service item configuration form into a preset exception recognition and extension component, where the preset exception recognition and extension component includes syntax rules for exception variable declaration and construction rules for exception code value generation; obtains all the exception display fields extended by the exception recognition and extension component according to the service item configuration form, the syntax rules, and the construction rules; caches all the extended exception display fields as custom exception display fields into a preset storage space of the target business system; generates a corresponding call path according to the storage path of the custom exception display fields in the preset storage space; adds the call path to the exception display field acquisition configuration file of the target business system, and configures an exception trigger function and a call priority different from the generality. Applying the exception recognition and extension method to the business program exception troubleshooting scenario, especially in the financial application field with numerous program functions and redundant data content, can accurately and quickly locate the program exception location by combining the exception code values and exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively, which helps the operation and maintenance personnel to quickly handle exceptions.

[0148] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, an optical disc, a read-only memory (ROM), or a random access memory (RAM), etc.

[0149] It should be understood that although the steps in the flowchart of the accompanying drawings are shown in sequence according to the indication of the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

[0150] To solve the above technical problems, the embodiments of the present application also provide a computer device. Specifically, please refer to Figure 10 , Figure 10 which is the basic structural block diagram of the computer device in this embodiment.

[0151] The computer device 10 includes a memory 10a, a processor 10b, and a network interface 10c that are communicatively connected to each other through a system bus. It should be noted that Figure 10 only the computer device 10 with components such as a memory 10a, a processor 10b, and a network interface 10c is shown in

[0152] The computer device may be a computing device such as a desktop computer, notebook, handheld computer, and cloud server. The computer device can interact with the user through a keyboard, mouse, remote control, touchpad, or voice control device.

[0153] The memory 10a includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (such as SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disc, etc. In some embodiments, the memory 10a may be an internal storage unit of the computer device 10, such as the hard disk or memory of the computer device 10. In other embodiments, the memory 10a may also be an external storage device of the computer device 10, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, Flash Card, etc. equipped on the computer device 10. Of course, the memory 10a may also include both the internal storage unit and the external storage device of the computer device 10. In this embodiment, the memory 10a is generally used to store the operating system and various application software installed on the computer device 10, such as computer-readable instructions of an anomaly recognition extension method. In addition, the memory 10a can also be used to temporarily store various data that have been output or will be output.

[0154] In some embodiments, the processor 10b may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. The processor 10b is generally used to control the overall operation of the computer device 10. In this embodiment, the processor 10b is used to run the computer-readable instructions stored in the memory 10a or process data, such as running the computer-readable instructions of the anomaly recognition extension method.

[0155] The network interface 10c may include a wireless network interface or a wired network interface, and the network interface 10c is generally used to establish a communication connection between the computer device 10 and other electronic devices.

[0156] The computer device proposed in this embodiment belongs to the technical field of R & D design and is applied to the scenario of program exception pre - setting. This application obtains the service item configuration form of the target business system; inputs the service item configuration form into a preset exception recognition and expansion component, where the preset exception recognition and expansion component contains syntax rules for exception variable declaration and construction rules for exception code value generation; obtains all the exception display fields expanded by the exception recognition and expansion component according to the service item configuration form, the syntax rules, and the construction rules; caches all the expanded exception display fields as custom exception display fields in the preset storage space of the target business system; generates a corresponding call path according to the storage path of the custom exception display fields in the preset storage space; adds the call path to the exception display field acquisition configuration file of the target business system, and configures an exception trigger function and call priority different from the general ones. Applying the exception recognition and expansion method to the scenario of business program exception troubleshooting, especially in the financial application field with numerous program functions and redundant data content, can accurately and quickly locate the program exception location by combining the exception code values and exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively, which helps the operation and maintenance personnel quickly handle exceptions.

[0157] This application also provides another implementation manner, that is, to provide a computer - readable storage medium storing computer - readable instructions that can be executed by a processor to cause the processor to execute the steps of the above - mentioned exception recognition and expansion method.

[0158] The computer-readable storage medium proposed in this embodiment belongs to the technical field of R & D design and is applied to the scenario of program exception pre-setting. This application obtains the service item configuration form of the target business system; inputs the service item configuration form into a preset exception recognition and expansion component, where the preset exception recognition and expansion component includes syntax rules for exception variable declaration and construction rules for exception code value generation; obtains all the exception display fields expanded by the exception recognition and expansion component according to the service item configuration form, the syntax rules, and the construction rules; caches all the expanded exception display fields as custom exception display fields in the preset storage space of the target business system; generates a corresponding call path according to the storage path of the custom exception display fields in the preset storage space; adds the call path to the exception display field acquisition configuration file of the target business system, and configures an exception trigger function and call priority different from the general ones. Applying the exception recognition and expansion method to the scenario of business program exception troubleshooting, especially in the financial application field with numerous program functions and complex data content, can accurately and quickly locate the program exception position by combining the exception code values and exception message fields corresponding to the service item name, call method name, call form name, and form field name respectively, which helps the operation and maintenance personnel quickly handle exceptions.

[0159] Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases, the former is a better implementation method. Based on such an understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

[0160] Obviously, the above-described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. The accompanying drawings show the preferred embodiments of this application, but do not limit the patent scope of this application. This application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosed content of this application more thorough and comprehensive. Although this application has been described in detail with reference to the foregoing embodiments, for those skilled in the art, they can still modify the technical solutions described in the foregoing specific embodiments, or perform equivalent replacements for some of the technical features. Any equivalent structure directly or indirectly using the content of the specification and drawings of this application in other related technical fields shall be within the scope of the patent protection of this application by the same token.

Claims

1. A method for expanding anomaly identification, characterized in that: The steps include: Obtaining a service item configuration form of the target business system, wherein the service item configuration form records at least one functional service item, each functional service item records at least one calling method, and each calling method matches a corresponding calling form and form fields; Inputting the service item configuration form into a preset exception identification extension component, wherein the preset exception identification extension component includes grammatical rules for abnormal variable declaration and construction rules for abnormal code value generation; Obtain all exception display fields expanded by the exception identification expansion component according to the service item configuration form, the grammar rule and the construction rule; All the expanded exception display fields are used as custom exception display fields and cached in a preset storage space of the target business system; Generate a corresponding call path according to the storage path of the customized exception display field in the preset storage space; The call path is added to the exception display field acquisition configuration file of the target business system, and an exception trigger function and a call priority different from the general exception display function are configured, wherein the exception display field acquisition configuration file is provided by the general exception display service component used by the target business system, and the general exception display service component specifies the general exception trigger function.

2. The abnormality identification and expansion method according to claim 1 is characterized in that: After executing the step of obtaining the service item configuration form of the target business system, the method further includes: Parse the service item configuration form to obtain all function service item names recorded in the service item configuration form, the names of the calling methods respectively contained in all function service items, and the calling form names and form field names respectively corresponding to all the calling methods; According to the calling relationship, the service item name, the calling method name, the calling form name and the form field name are hierarchically sorted to obtain a hierarchical sorting result.

3. The abnormality identification and expansion method according to claim 2 is characterized in that: The step of inputting the service item configuration form into a preset abnormality identification extension component specifically includes: Inputting the hierarchical arrangement result including the service item name, the calling method name, the calling form name and the form field name into the abnormality identification expansion component; Before executing the step of obtaining all the abnormal display fields expanded by the abnormal identification expansion component according to the service item configuration form, the grammatical rules and the construction rules, the method further includes: Starting the anomaly identification expansion component; Taking the hierarchical arrangement result including the service item name, the calling method name, the calling form name and the form field name as the extended control relationship, taking the grammar rule and the construction rule as the extended generation rule, all the extended exception display fields are generated; The step of obtaining all the abnormal display fields expanded by the abnormal identification expansion component according to the service item configuration form, the grammatical rules and the construction rules specifically includes: Acquire all abnormal display fields generated according to the extended control relationship and the extended generation rule.

4. The abnormality identification and expansion method according to claim 3 is characterized in that: The step of using the hierarchical arrangement result including the service item name, the calling method name, the calling form name and the form field name as the extended control relationship, using the grammar rule and the construction rule as the extended generation rule, and generating all the extended abnormal display fields specifically includes: Generate exception variable names corresponding to the service item name, calling method name, calling form name, and form field name, respectively, according to the extended control relationship and the grammatical rules; Generate different exception message fields according to the exception variable names corresponding to the service item name, calling method name, calling form name, and form field name; Generate exception code values ​​corresponding to the service item name, calling method name, calling form name, and form field name respectively according to the extended control relationship and the construction rule; Perform variable and code value mapping relationship binding processing on the abnormal variable names and abnormal code values ​​corresponding to the same service item name, the same calling method name, the same calling form name, and the same form field name, and obtain the variable and code value mapping relationship binding result; The exception variable names and exception code values ​​corresponding to the service item name, calling method name, calling form name, and form field name, the exception message fields corresponding to the service item name, calling method name, calling form name, and form field name, and the binding results of the variable and code value mapping relationship are used as all the expanded exception display fields.

5. The anomaly identification and expansion method according to claim 4 is characterized in that: The step of generating abnormal variable names corresponding to the service item name, the calling method name, the calling form name, and the form field name respectively according to the extended control relationship and the grammatical rule specifically includes: The first distinguishing identifier and the service item name are concatenated to generate abnormal variable names corresponding to different service item names; In combination with the extended control relationship, the second distinguishing identifier and the calling method name are used to continue splicing on the basis of the abnormal variable names corresponding to the different service item names, so as to generate the abnormal variable names corresponding to the different calling method names; In combination with the extended control relationship, the third distinguishing identifier and the calling form name are used to continue splicing on the basis of the abnormal variable names corresponding to the different calling method names, so as to generate the abnormal variable names corresponding to the different calling form names; In combination with the extended control relationship, the fourth distinguishing identifier and the form field name are used to continue splicing on the basis of the abnormal variable names corresponding to different calling form names, so as to generate abnormal variable names corresponding to different form field names.

6. The anomaly identification and expansion method according to claim 4 is characterized in that: The step of generating the exception code values ​​corresponding to the service item name, the calling method name, the calling form name, and the form field name respectively according to the extended control relationship and the construction rule specifically includes: According to the first construction rule, generating exception code values ​​corresponding to different service item names respectively; In combination with the extended control relationship, according to the second construction rule, on the basis of the exception code values ​​corresponding to the names of different service items, code value splicing is performed to generate exception code values ​​corresponding to the names of different calling methods; In combination with the extended control relationship, according to the third construction rule, on the basis of the exception code values ​​corresponding to the different calling method names, code value splicing is performed to generate exception code values ​​corresponding to the different calling form names; In combination with the extended control relationship, according to the fourth construction rule, on the basis of the exception code values ​​corresponding to different calling form names, code value splicing is performed to generate exception code values ​​corresponding to different form field names.

7. The abnormality identification and expansion method according to claim 4 is characterized in that: Before executing the step of adding the call path to the abnormal display field acquisition configuration file of the target business system and configuring the abnormal trigger function and call priority different from the general ones, the method further includes: Get the different exception message fields generated according to the exception variable names corresponding to the service item name, calling method name, calling form name, and form field name; The exception trigger function includes two call parameters, which are an exception code value and an exception message field. The step of adding the call path to the exception display field acquisition configuration file of the target business system and configuring an exception trigger function and a call priority different from the general one specifically includes: Add the calling paths of the exception code values ​​corresponding to the service item name, calling method name, calling form name, and form field name to the exception display field acquisition configuration file; Add the calling paths of the exception message fields corresponding to the service item name, calling method name, calling form name, and form field name to the exception display field acquisition configuration file; The calling priority of the exception triggering function is set to be higher than that of the general exception triggering function.

8. An abnormality identification and expansion device, characterized in that: include: A service item configuration form acquisition module is used to acquire a service item configuration form of a target business system, wherein the service item configuration form records at least one functional service item, each functional service item records at least one calling method, and each calling method matches a corresponding calling form and form fields; A service item configuration form input module, used to input the service item configuration form into a preset exception identification extension component, wherein the preset exception identification extension component includes grammatical rules for abnormal variable declaration and construction rules for abnormal code value generation; A custom exception display field acquisition module is used to acquire all exception display fields expanded by the exception identification expansion component according to the service item configuration form, the grammar rules and the construction rules; A custom exception display field cache module, used to cache all the expanded exception display fields as custom exception display fields in a preset storage space of the target business system; A calling path generation module, used to generate a corresponding calling path according to the storage path of the customized abnormal display field in the preset storage space; A related configuration content adding module is used to add the call path to the exception display field acquisition configuration file of the target business system, and configure an exception trigger function and a call priority that are different from the general exception display service component, wherein the exception display field acquisition configuration file is provided by the general exception display service component used by the target business system, and the general exception trigger function is specified in the general exception display service component.

9. A computer device, characterized in that: It includes a memory and a processor, wherein the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, the steps of the abnormality identification and expansion method as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the anomaly identification and expansion method according to any one of claims 1 to 7 are implemented.

Images