Processing method and device of abnormal service function module, equipment and medium

Abstract

The application provides a processing method, device and equipment of an abnormal business function module and a medium. In the method, after obtaining the calling information of each business function module in a business system, for each business function module, when the calling information of the business function module meets the corresponding preset abnormal calling condition, the business function module is determined as an abnormal business function module, and then an abnormal list is generated and sent to a development end. The abnormal business function module is determined through the calling information of the business function module and the corresponding preset abnormal calling condition, the abnormal list is generated and sent to the development end, and the efficiency of identifying and processing the abnormal business function module is effectively improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of financial technology or other related fields, and in particular, to a processing method and device for an abnormal business function module, equipment and medium. BACKGROUND

[0002] With the rapid development of technology, the business of enterprises has also entered the digital age. By building an enterprise-level business architecture, guiding enterprise system design, and ensuring the integrity and collaboration of the construction of various systems, under the guidance of the enterprise-level business architecture, the enterprise-level business model is designed by a systematic method, which guides the design of enterprise reusable components; the business function module is designed by a systematic method, and the corresponding calling principle is matched to form a business system that inherits the business architecture.

[0003] In the prior art, for the construction of a business system, multiple development teams usually cooperate to build it, which may cause some problems that do not conform to the design principles, such as: non-standard method name, timeout call, too long call link depth, same layer call, and some technical problems such as research and development coupling and inefficient exit of historical business function modules. For the processing of these problems, the staff usually manually exports the call link information, subscription information, project list and other information, and then manually analyzes whether there is an abnormal business function module according to these information. Then the staff contacts the development team corresponding to the abnormal business function module to determine the improvement plan.

[0004] In summary, the existing processing method of the abnormal business function module is to manually determine the abnormal business function module and contact the development team, which leads to low efficiency in identifying and processing the abnormal business function module. SUMMARY

[0005] The embodiments of the present application provide a processing method, device, equipment and medium for an abnormal business function module, which is used to solve the problem that the existing processing method of the abnormal business function module is manually determined and the development team is contacted, which leads to low efficiency in identifying and processing the abnormal business function module.

[0006] In a first aspect, the embodiments of the present application provide a processing method for an abnormal business function module, comprising:

[0007] Obtaining the calling information of each business function module in a business system;

[0008] For each business function module, if the calling information of the business function module meets the preset abnormal calling condition corresponding to the calling information, at least one abnormal list is generated, and the abnormal list includes the identifier of the business function module and the abnormal type to which the business function module belongs.

[0009] send the at least one exception list to a development end.

[0010] In an embodiment, the call information includes a zero-call duration;

[0011] Correspondingly, the call information of each business function module in the business system includes:

[0012] The call quantity information corresponding to each business function module in the business system is obtained through the service registration center;

[0013] According to the call quantity information corresponding to each business function module, the zero-call duration of each business function module is determined.

[0014] In an embodiment, the call information further includes the common upgrade times of the cross-application called business function modules, and the call same-layer business function module result.

[0015] Correspondingly, the call information of each business function module in the business system further includes:

[0016] The business function module call link corresponding to the business system is obtained through the software resource management system;

[0017] The project list information corresponding to the business system, the application corresponding to each business function module in the business system, and the business level corresponding to each business function module in the business system are obtained through the project management system;

[0018] According to the application corresponding to each business function module, the business level corresponding to each business function module, the project list information, and the business function module call link, the common upgrade times of the cross-application called business function modules of each business function module and the call same-layer business function module result of each business function module are determined.

[0019] In an embodiment, for each business function module, if the call information of the business function module meets the preset abnormal call condition corresponding to the call information, at least one exception list is generated, including:

[0020] For each business function module, if the zero-call duration in the call information of the business function module is greater than a preset duration, a first exception list is generated, and the first exception list includes the identification of the business function module and a first exception type.

[0021] In an embodiment, the exception list further comprises an identifier of a co-upgraded business function module; and the method further comprises:

[0022] If the number of co-upgrades of the business function module in the call information of the business function module is greater than a preset number, a second exception list is generated, the second exception list comprising an identifier of the business function module, an identifier of a co-upgraded business function module, and a second exception type.

[0023] In an embodiment, the exception list further comprises an identifier of a co-upgraded business function module; and the method further comprises:

[0024] For each business function module, if the result of calling a same-layer business function module in the call information of the business function module is to call a same-layer business function module, a third exception list is generated, the third exception list comprising an identifier of the business function module, an identifier of a co-upgraded business function module, and a third exception type.

[0025] In an embodiment, the method further comprises:

[0026] For each business function module, if the length of the business function module call link is greater than a preset length threshold, a fourth exception list is generated, the fourth exception list comprising the business function module call link and a fourth exception type.

[0027] In an embodiment, the method further comprises:

[0028] For each exception list in the at least one exception list, a development end identifier and a sending frequency are determined according to an exception type in the exception list.

[0029] The exception list is sent to a development end corresponding to the development end identifier according to the sending frequency.

[0030] In an embodiment, the method further comprises:

[0031] For each exception list in the at least one exception list, a preset processing scheme and a preset strategy graph corresponding to an exception type in the exception list are obtained according to the exception type.

[0032] The preset processing scheme and the preset strategy graph corresponding to the exception type are added to the exception list.

[0033] In a second aspect, an embodiment of the present application provides a processing apparatus of an abnormal business function module, comprising:

[0034] an acquisition module configured to acquire calling information of each business function module in a business system;

[0035] a processing module configured to, for each business function module, if the calling information of the business function module meets a preset abnormal calling condition corresponding to the calling information, generate at least one abnormal list, the abnormal list comprising an identifier of the business function module and an abnormal type to which the business function module belongs;

[0036] a sending module configured to send the at least one abnormal list to a development end.

[0037] In a third aspect, an embodiment of the present application provides an electronic device, comprising:

[0038] a processor, a memory, and a communication interface;

[0039] the memory is configured to store executable instructions of the processor;

[0040] The processor is configured to execute the executable instructions to implement the processing method of the abnormal business function module according to any one of the first aspect.

[0041] In a fourth aspect, an embodiment of the present application provides a readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the processing method of the abnormal business function module according to any one of the first aspect.

[0042] In a fifth aspect, an embodiment of the present application provides a computer program product comprising a computer program, the computer program being executed by a processor to implement the processing method of the abnormal business function module according to any one of the first aspect.

[0043] The processing method, apparatus, device and medium of the abnormal business function module provided by the embodiments of the present application, after acquiring the calling information of each business function module in a business system, for each business function module, when the calling information of the business function module meets the corresponding preset abnormal calling condition, the business function module is determined to be an abnormal business function module, and then an abnormal list is generated and sent to a development end. The present application determines the abnormal business function module through the calling information of the business function module and the corresponding preset abnormal calling condition, generates an abnormal list and sends it to the development end, which effectively improves the efficiency of identifying and processing the abnormal business function module. BRIEF DESCRIPTION OF DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings described below are some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

[0045] Figure 1 The flowchart of the processing method of the abnormal service function module provided by the present application is shown in the embodiment one.

[0046] Figure 2 The flowchart of the processing method of the abnormal service function module provided by the present application is shown in the embodiment two.

[0047] Figure 3 The flowchart of the processing method of the abnormal service function module provided by the present application is shown in the embodiment three.

[0048] Figure 4 The flowchart of the processing method of the abnormal service function module provided by the present application is shown in the embodiment four.

[0049] Figure 5a The flowchart of the processing method of the abnormal service function module provided by the present application is shown in the embodiment five.

[0050] Figure 5b The strategy diagram corresponding to the first abnormal type provided by the present application is shown in the embodiment.

[0051] Figure 5c The strategy diagram corresponding to the second abnormal type provided by the present application is shown in the embodiment.

[0052] Figure 5d The strategy diagram corresponding to the third abnormal type provided by the present application is shown in the embodiment.

[0053] Figure 6 The structural diagram of the processing device of the abnormal service function module provided by the present application is shown in the embodiment.

[0054] Figure 7 The structural diagram of the electronic device provided by the present application is shown in the embodiment. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions in the embodiments of the present application will be described clearly and completely below with the drawings in the embodiments of the present application. Obviously, the described embodiments are some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments made by those skilled in the art based on the inspiration of the present embodiments are within the scope of protection of the present application.

[0056] The terms "first", "second", "third", "fourth" and the like in the description and in the claims of the present application, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the use of these terms herein is to be construed as interchangeable in order to comfort the description of the embodiments of the present application as outlined herein. Furthermore, the terms "comprising", "having", "including", and "containing" and any variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, system, product or apparatus that comprises, has, includes or contains a list of elements is not necessarily limited to those elements but can include other elements not expressly listed or inherent to such process, method, system, product or apparatus.

[0057] With the development of science and technology, in order to facilitate the business of enterprises, the business handling mode enters the digitalization, and the business system appears. Through the business system, the user can complete the business handling online, and the staff can also complete the internal work flow through the business system, which greatly improves the work efficiency.

[0058] For the construction of the business system, it is usually constructed by multiple development teams, and some problems that do not conform to the design principles will occur, such as: non-standard method name, timeout call, too long call link depth, same layer call, and some technical problems such as research and development coupling, inefficient exit of historical business function modules of business function modules. For the processing of these problems, the staff usually manually exports the call link information, subscription information, project list and other information, and then manually analyzes whether there is an abnormal business function module according to the information. Then the staff contacts the development team corresponding to the abnormal business function module to determine the improvement scheme, which leads to low efficiency of identification and processing of the abnormal business function module.

[0059] In view of the problems in the prior art, the inventors found, in the process of researching the processing method of the abnormal business function module, that in order to improve the identification and processing efficiency of the abnormal business function module, the calling information of each business function module in the business system can be obtained through a software resource management system, a project management system and a service registration center. Then for each business function module, whether the calling information of the business function module is abnormal is judged according to a preset abnormal calling condition. If there is an abnormality, it means that the business function module is an abnormal business function module, and then an abnormal list is generated and sent to the development end corresponding to the abnormal function module, which effectively improves the identification and processing efficiency of the abnormal business function module. Based on the above invention concept, the processing scheme of the abnormal business function module in the present application is designed.

[0060] The following describes the business hierarchy and calling rules between hierarchies of business function modules in a business system.

[0061] Business function modules in the business system are divided into four hierarchies, namely, a User Case (UC) hierarchy, an Application Transaction Service (ATS) hierarchy, an Application Component Service (ACS) hierarchy, and a Business Object Service (BOS) hierarchy.

[0062] Business function modules in the ATS hierarchy can only be called by business function modules in the UC hierarchy, and are responsible for defining the capabilities provided by the system from the perspective of users, and calling business function modules in the ACS hierarchy to implement business functions.

[0063] Business function modules in the ACS hierarchy can only be called by business function modules in the ATS hierarchy, and are responsible for assembling business function modules in the BOS hierarchy within the application.

[0064] Business function modules in the BOS hierarchy can only be called by business function modules in the ACS hierarchy, and are responsible for providing specific processing capabilities for business objects, encapsulating business rules, decoupling business logic and data access, and operating databases through a technical framework.

[0065] The execution subject of the processing method of the abnormal business function module in the application can be a server, and can also be a computer, a terminal device, or the like, which is not limited in the application. The following describes the server as an example.

[0066] The following describes an application scenario of the processing method of the abnormal business function module provided in the application.

[0067] For example, in this application scenario, the abnormal business function module needs to be identified and processed during the construction and later maintenance of the business system. The server can obtain calling information of each business function module in the business system from a software resource management system, a project management system, and a service registration center. For example, the calling information includes a zero-call duration, a common upgrade number of a cross-application called business function module, and a result of calling a same-level business function module.

[0068] Further, the server determines whether the call information meets the corresponding preset abnormal call condition to determine the abnormal business function module. For example, the zero call duration is greater than the preset duration, the common upgrade number of the business function module of the cross-application call is greater than the preset number, and the call of the same layer business function module is all the call of the same layer business function module, which all belong to the preset abnormal call condition. When the call information meets the corresponding preset abnormal call condition, an abnormal list is generated.

[0069] It should be noted that the preset duration can be 1 month, 2 months, or 3 months. The preset number can be 3 times, 5 times, or 7 times. The preset duration and the preset number are not specifically limited in the embodiment of the application, and can be set according to actual conditions.

[0070] Further, the server sends the abnormal list to the development end corresponding to the abnormal business function module to realize identification and processing of the abnormal business function module.

[0071] It should be noted that the above scenario is only an example of an application scenario provided by the embodiment of the application, and the actual form of various devices included in the scenario is not limited, nor is the interaction mode between the devices limited. In the specific application of the scheme, the actual needs can be set.

[0072] In the following, the technical scheme of the application is described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described in detail in some embodiments.

[0073] Figure 1 The flowchart of the abnormal business function module processing method provided by the embodiment of the application is shown in the following figure. The embodiment of the application describes the case that the abnormal business function module is determined according to the call information of each business function module in the business system and the corresponding preset abnormal call condition, and the abnormal list is generated and sent to the development end. The method in this embodiment can be realized by software, hardware or a combination of software and hardware. As shown in the figure, Figure 1 The abnormal business function module processing method specifically includes the following steps:

[0074] S101: Obtain the call information of each business function module in the business system.

[0075] In this step, when the abnormal business function module in the business system needs to be identified and processed, the server needs to first obtain the call information of each business function module in the business system.

[0076] In the process of business system construction, release and operation, the related information of the business system is stored in the software resource management system, the project management system and the service registration center and the like, and the calling information of each business function module in the business system can be obtained from these systems.

[0077] S102: For each business function module, it is judged whether the calling information of the business function module meets the preset abnormal calling condition corresponding to the calling information; if the calling information of the business function module meets the preset abnormal calling condition corresponding to the calling information, S103 is executed; if the calling information of the business function module does not meet the preset abnormal calling condition corresponding to the calling information, S105 is executed.

[0078] S103: At least one exception list is generated.

[0079] S104: The at least one exception list is sent to the development end.

[0080] S105: The current scheme execution is ended.

[0081] In the above steps, after obtaining the calling information of each business function module in the business system, in order to determine the abnormal business function module in the business system, the server judges whether the calling information of each business function module meets the preset abnormal calling condition corresponding to the calling information.

[0082] If the calling information of the business function module meets the preset abnormal calling condition corresponding to the calling information, it means that there is an abnormal business function module in the business system, and at least one exception list is generated. Since the calling information includes at least one data, each data has a corresponding preset abnormal calling condition, when there is a data meeting the corresponding preset abnormal calling condition, it is determined that the business function module is an abnormal business function module, and then an exception list is generated. The number of exception lists is the same as the number of data meeting the preset abnormal calling condition.

[0083] For example, the calling information can include zero calling quantity duration, common upgrade times of the business function module called across applications, and calling same-layer business function module result; the corresponding preset abnormal calling condition can be that the zero calling duration is greater than a preset duration, the common upgrade times of the business function module called across applications is greater than a preset number of times, and the calling same-layer business function module result is calling same-layer business function module; the preset duration can be 1 month, 2 months or 3 months. The preset number of times can be 3 times, 5 times or 7 times.

[0084] It should be noted that the above examples are only examples of the data included in the calling information, the preset abnormal calling condition, the preset time length, and the preset number of times. The embodiments of the present application do not specifically limit the data included in the calling information, the preset abnormal calling condition, the preset time length, and the preset number of times, which can be set according to actual conditions.

[0085] After the server generates the exception list, for each exception list, the server sends the exception list to the development end of the exception business function module corresponding to the exception list.

[0086] If the calling information of the business function module does not satisfy the preset abnormal calling condition corresponding to the calling information, it indicates that there is no abnormal business function module in the business system, and the execution of the present scheme is ended.

[0087] The processing method of the abnormal business function module provided in the embodiment is used to acquire, by a server, calling information of each business function module in a business system, and then determine an abnormal business function module when the calling information satisfies a corresponding preset abnormal calling condition, generate an exception list, and send the exception list to a development end. Compared with the manual determination of the abnormal business function module and the contact with the development team in the prior art, the present application determines the abnormal business function module according to the calling information of each business function module, and then sends the generated exception list to the development end, thereby effectively improving the processing efficiency of the abnormal business function module in the business system.

[0088] Figure 2 The flowchart of the processing method of the abnormal business function module provided in the second embodiment of the present application is shown in FIG. 2, which is based on the above-mentioned embodiments. The present embodiment describes the case where the server acquires the calling information of each business function module in the business system when the calling information includes a zero calling quantity duration. As shown in FIG. 2, the processing method of the abnormal business function module specifically includes the following steps: Figure 2

[0089] S201: Acquire, by a service registration center, calling quantity information corresponding to each business function module in a business system.

[0090] In this step, since the related information of the business system is stored in the service registration center and other systems during the construction, release, and running of the business system, the server can acquire the calling quantity information corresponding to each business function module in the business system from the service registration center. The calling quantity information includes the calling quantity of each business function module per month.

[0091] S202: Determine the zero calling quantity duration of each business function module according to the calling quantity information corresponding to each business function module.

[0092] ​In this step, after the server obtains the calling quantity information corresponding to each business function module, since the calling quantity information includes the calling quantity of each business function module per month, the zero calling quantity duration of each business function module can be determined according to the calling quantity information corresponding to each business function module.

[0093] The processing method of the abnormal business function module provided in this embodiment can obtain the zero calling quantity duration of each business function module by obtaining the calling quantity information corresponding to each business function module from the service registration center, thereby effectively improving the accuracy of obtaining the calling information of each business function module in the business system.

[0094] Figure 3 The flowchart of the third embodiment of the processing method of the abnormal business function module provided in this application is based on the above embodiments. In the case where the calling information includes the common upgrade times of the cross-application calling business function module and the calling same-layer business function module result, the server obtains the calling information of each business function module in the business system. As shown in the Figure 3 The processing method of the abnormal business function module specifically includes the following steps:

[0095] S301: Obtain the business function module calling link corresponding to the business system through the software resource management system.

[0096] In this step, since the related information of the business system is stored in the software resource management system, the project management system and other systems during the construction, release and running of the business system, the server can obtain the business function module calling link corresponding to the business system from the software resource management system.

[0097] S302: Obtain the project list information corresponding to the business system, the application corresponding to each business function module in the business system and the business level corresponding to each business function module in the business system through the project management system.

[0098] In this step, since the related information of the business system is stored in the software resource management system, the project management system and other systems during the construction, release and running of the business system, the server can obtain the project list information corresponding to the business system, the application corresponding to each business function module in the business system and the business level corresponding to each business function module in the business system from the project management system. The project list information includes the business function modules that are commonly upgraded in the business system and the upgrade times of each business function module.

[0099] It should be noted that the execution sequence of step S301 and step S302 can be that step S301 is executed first and then step S302 is executed, or step S302 is executed first and then step S301 is executed, or step S301 and step S302 are executed simultaneously. The execution sequence of step S301 and step S302 is not limited in the embodiment of the application, and can be selected according to actual conditions.

[0100] S303: determining, according to the application corresponding to each service function module, the service level corresponding to each service function module, the project list information, and the service function module calling link, the common upgrade times of each service function module and the service function module calling across applications, and the calling same-level service function module result of each service function module.

[0101] In this step, after the server obtains the service function module calling link, the project list information, the application corresponding to each service function module in the service system, and the service level corresponding to each service function module in the service system, it can determine whether each service function module is upgraded together with other service function modules across applications according to the service function module calling link, the application corresponding to each service function module, and the common upgraded service function module in the project list information, and then determine the common upgrade times of each service function module and the service function module calling across applications according to the upgrade times of each service function module.

[0102] According to the service function module calling link and the service level corresponding to each service function module, it can be determined whether each service function module calls a same-level service function module, and then the calling same-level service function module result is obtained.

[0103] The processing method of the abnormal service function module provided in the embodiment obtains the application corresponding to each service function module, the service level corresponding to each service function module, the project list information, and the service function module calling link from the software resource management system and the project management system, and then obtains the common upgrade times of each service function module and the service function module calling across applications and the calling same-level service function module result, thereby effectively improving the accuracy of obtaining the calling information of each service function module in the service system.

[0104] Figure 4 The flowchart of the processing method of the abnormal service function module provided in the fourth embodiment of the application is based on the above-mentioned embodiments, and the embodiment of the application explains the case that the calling information includes zero calling quantity duration, the common upgrade times of the service function module calling across applications, and the calling same-level service function module result, and determines the abnormal service function module according to the calling information and the preset abnormal calling condition, generates an abnormal list, and sends it to the development end. Figure 4As shown, the processing method of the abnormal business function module specifically includes the following steps:

[0105] S401: Obtain the calling information of each business function module in the business system.

[0106] In this step, the server can obtain the calling information of each business function module in the business system from the software resource management system, the project management system and the service registration center. The calling information includes the zero-call duration, the common upgrade times of the business function module for cross-application calling and the calling result of the business function module in the same layer.

[0107] S402: For each business function module, determine whether the zero-call duration in the calling information of the business function module is greater than a preset duration. If the zero-call duration in the calling information of the business function module is greater than the preset duration, perform S403; if the zero-call duration in the calling information of the business function module is less than or equal to the preset duration, perform S404.

[0108] S403: Generate a first abnormal list.

[0109] In the above step, after the server obtains the calling information of each business function module in the business system, in order to determine the abnormal business function module, it is necessary to determine, for each business function module, whether the zero-call duration in the calling information of the business function module is greater than a preset duration.

[0110] If the zero-call duration in the calling information of the business function module is greater than the preset duration, it means that the business function module has not been called for a long time, that is, it has not been subscribed for a long time, and it should be deleted. The business function module is an abnormal business function module, so a first abnormal list is generated. The first abnormal list includes the identifier of the business function module and a first abnormal type.

[0111] It should be noted that the preset duration can be 1 month, 2 months or 3 months. The preset duration is not limited in the embodiment of the application and can be set according to actual conditions.

[0112] S404: Determine whether the common upgrade times of the business function module for cross-application calling in the calling information of the business function module are greater than a preset number of times. If the common upgrade times of the business function module for cross-application calling are greater than the preset number of times, perform S405; if the common upgrade times of the business function module for cross-application calling are less than or equal to the preset number of times, perform S406.

[0113] S405: Generate a second abnormal list.

[0114] In the above step, if the zero invocation duration in the invocation information of the service function module is less than or equal to the preset duration, it indicates that the service function module is still being invoked, and whether the service function module is an abnormal service function module needs to be further determined. In addition, in the case of generating the first exception list, it also needs to be judged whether the service function module has other exceptions. This requires judging whether the number of common upgrades of the service function module in the invocation information of the service function module and the service function module invoked across applications is greater than a preset number.

[0115] If the number of common upgrades of the service function module and the service function module invoked across applications is greater than the preset number, it indicates that the service function module has been upgraded multiple times in cooperation with other application service function modules, and needs to be decoupled. The service function module is an abnormal service function module, and a second exception list is generated. The second exception list includes the identifier of the service function module, the identifier of the service function module that is commonly upgraded, and a second exception type.

[0116] It should be noted that the preset number can be 3, 5, or 7. The present application does not limit the preset number, which can be set according to actual conditions.

[0117] S406: Determine whether the invocation of the same layer service function module result in the invocation information of the service function module is the invocation of the same layer service function module. If the invocation of the same layer service function module result is the invocation of the same layer service function module, perform S407. If the invocation of the same layer service function module result is not the invocation of the same layer service function module, perform S408.

[0118] S407: Generate a third exception list.

[0119] S408: For each exception list in the at least one exception list, determine the development end identifier and the sending frequency according to the exception type in the exception list.

[0120] In the above step, if the number of common upgrades of the service function module and the service function module invoked across applications is less than or equal to the preset number, it indicates that the service function module is only occasionally upgraded with the service function module invoked across applications, and does not need to be decoupled. Whether the service function module is an abnormal service function module needs to be further determined. In addition, in the case of generating the first exception list and / or the second exception list, it also needs to be judged whether the service function module has other exceptions. This requires judging whether the invocation of the same layer service function module result in the invocation information of the service function module is the invocation of the same layer service function module.

[0121] If the result of calling the same layer business function module is calling the same layer business function module, it is explained that the calling rule is not met, the business function module is an abnormal business function module, and a third abnormality list is generated. The third abnormality list includes the identification of the business function module, the identification of the same layer calling business function module, and a third abnormality type.

[0122] If the result of calling the same layer business function module is not calling the same layer business function module, it is explained that the business function module does not exist the abnormality of the same layer calling.

[0123] After generating the third abnormality list or the server judges that the result of calling the same layer business function module is not calling the same layer business function module, the server judges how many abnormality lists are generated for the business function module.

[0124] If no abnormality list is generated, it is explained that the business function module has no problem, the processing of the business function module is ended, the next business function module is judged whether it exists abnormality, and if each business function module does not exist abnormality, the scheme execution is ended.

[0125] If at least one abnormality list is generated, it is necessary to determine the development end identification and the sending frequency according to the abnormality type in each abnormality list in the at least one abnormality list. Since the server stores the corresponding relationship between the abnormality type and the development end type and the sending frequency, and the project list also includes the corresponding relationship between the development end type and the development end identification, the server can determine the development end identification and the sending frequency according to the abnormality type. For example, the development end type can be a front-end design type, a front-end development type, a back-end operation and maintenance type, a back-end test type, a back-end research and development type, etc.

[0126] It should be noted that after the server generates the abnormality list, the abnormality list can also be copied and stored, which can prevent data loss.

[0127] It should be noted that, for judging whether the zero call duration in the calling information of the business function module is greater than the preset duration, whether the common upgrade times of the cross-application called business function module is greater than the preset times, and whether the result of calling the same layer business function module is the order of calling the same layer business function module, the common upgrade times of the cross-application called business function module can be first judged to be greater than the preset times, then whether the result of calling the same layer business function module is the order of calling the same layer business function module is judged, and finally whether the zero call duration in the calling information of the business function module is greater than the preset duration is judged. The order of judging whether the zero call duration in the calling information of the business function module is greater than the preset duration, whether the common upgrade times of the cross-application called business function module is greater than the preset times, and whether the result of calling the same layer business function module is the order of calling the same layer business function module is not limited in the embodiment of the application, and can be determined according to actual conditions.

[0128] S409: According to the sending frequency, the exception list is sent to the development end corresponding to the development end identifier.

[0129] In this step, after the server determines the sending frequency and the development end identifier, the exception list can be sent to the development end corresponding to the development end identifier according to the sending frequency.

[0130] The processing method of the abnormal business function module provided in the embodiment determines the abnormal business function module by judging whether the zero call duration in the calling information of the business function module is greater than the preset duration, whether the common upgrade times of the cross-application called business function module is greater than the preset times, and whether the result of calling the same layer business function module is the order of calling the same layer business function module, generates an exception list and sends it to the development end, and effectively improves the efficiency of identifying and processing the abnormal business function module.

[0131] The case of generating the fourth exception list when the length of the business function module calling link is greater than the preset length threshold provided in the embodiment of the application is described below.

[0132] The server, after identifying the abnormal service function module, further judges whether the length of the service function module calling link is greater than a preset length threshold, so as to ensure that the service function module calling link is not too long. If the length of the service function module calling link is greater than the preset length threshold, it indicates that the service function module calling link is too long, and a fourth abnormal list is generated. The fourth abnormal list includes the service function module calling link and a fourth abnormal type. If the length of the service function module calling link is less than or equal to the preset length threshold, it indicates that the service function module calling link is normal and does not need to be processed.

[0133] For the determination of the length of the service function module calling link, the number of nodes of the longest single chain in the service function module calling link can be determined as the length of the service function module calling link.

[0134] It should be noted that the preset length threshold can be 5, 10, or 15, and the present application does not limit the preset length threshold, which can be set according to actual conditions.

[0135] The processing method for the abnormal service function module provided in the embodiment can determine that the service function module calling link is too long when the length of the service function module calling link is greater than the preset length threshold, and further generate and send an abnormal list, thereby realizing the identification and processing of the abnormal service function module calling link.

[0136] Figure 5a The flowchart of the processing method for the abnormal service function module provided in the present application is shown in the above embodiment. Before the abnormal list is sent to the development end, the present application adds a preset processing scheme and a preset strategy graph to the abnormal list. As shown in Figure 5a The processing method for the abnormal service function module specifically includes the following steps:

[0137] S501: For each abnormal list in the at least one abnormal list, a preset processing scheme and a preset strategy graph corresponding to the abnormal type in the abnormal list are obtained according to the abnormal type in the abnormal list.

[0138] In this step, after the server generates the abnormal list, in order to enable the corresponding developer of the development end to more intuitively and quickly determine how to process the abnormal service function module, a preset processing scheme and a preset strategy graph corresponding to the abnormal type in the abnormal list are obtained for each abnormal list in the at least one abnormal list according to the abnormal type in the abnormal list.

[0139] S502: The preset processing scheme and the preset strategy graph corresponding to the abnormal type are added to the abnormal list.

[0140] In this step, after the server obtains the preset processing scheme and the preset strategy graph corresponding to the abnormal type, the preset processing scheme and the preset strategy graph corresponding to the abnormal type are added to the abnormal list.

[0141] For example, Figure 5b The strategy graph corresponding to the first abnormal type provided by the embodiment of the application is as shown in the left side of Figure 5b Figure 5b Business function module A calls business function module B and business function module C, but the zero call duration of business function module C is greater than the preset duration, and business function module C needs to be deleted. Therefore, as shown in the right side of Figure 5b

[0142] For example, Figure 5c The strategy graph corresponding to the second abnormal type provided by the embodiment of the application is as shown in the left side of Figure 5c Figure 5c Business function module A calls business function module B, business function module C and business function module D, business function module A, business function module B, business function module C and business function module D belong to different applications, business function module B, business function module C and business function module D are upgraded together with business function module A, and the number of times of common upgrading is greater than the preset number of times, so decoupling is needed. Therefore, as shown in the right side of Figure 5c

[0143] For example, Figure 5d The strategy graph corresponding to the third abnormal type provided by the embodiment of the application is as shown in the left side of Figure 5d Figure 5d Business function module A calls business function module B and business function module C, and business function module A, business function module B and business function module C all belong to the ACS layer, and business function module A calls in the same layer, so business function module A needs to be upgraded to the ATS layer. Therefore, as shown in the right side of Figure 5d

[0144] ​​​​​​It should be noted that the above examples are only examples of the policy graph, and the embodiments of the present application do not limit the form of the policy graph and the content of the policy graph. The actual situation can be selected.

[0145] The processing method of the abnormal business function module provided in the embodiment improves the intuitiveness of the exception list and the efficiency of the corresponding developers of the development end in processing the abnormal business function module by adding the preset processing scheme and the preset policy graph in the exception list.

[0146] The following is an apparatus embodiment of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the apparatus embodiments of the present application, please refer to the method embodiments of the present application.

[0147] Figure 6 The structure diagram of the processing apparatus of the abnormal business function module provided in the present application is shown in FIG. 1. As shown in FIG. 1, the processing apparatus 60 of the abnormal business function module comprises: Figure 6

[0148] The acquisition module 61 is configured to acquire the calling information of each business function module in the business system;

[0149] The processing module 62 is configured to, for each business function module, if the calling information of the business function module meets the preset abnormal calling condition corresponding to the calling information, generate at least one exception list, the exception list comprising the identifier of the business function module and the exception type to which the business function module belongs.

[0150] The sending module 63 is configured to send the at least one exception list to the development end.

[0151] Further, the calling information comprises a zero-call duration, and the acquisition module 61 is specifically configured to:

[0152] acquire, through a service registration center, the calling quantity information corresponding to each business function module in the business system;

[0153] determine the zero-call duration of each business function module according to the calling quantity information corresponding to each business function module.

[0154] Further, the calling information comprises the common upgrade times of the business function module of cross-application calling and the calling same-layer business function module result, and the acquisition module 61 is specifically further configured to:

[0155] acquire, through a software resource management system, the business function module calling link corresponding to the business system;

[0156] ​acquire, by a project management system, project list information corresponding to the business system, applications corresponding to each business function module in the business system, and business levels corresponding to each business function module in the business system;

[0157] determine, according to the applications corresponding to each business function module, the business levels corresponding to each business function module, the project list information, and the business function module calling link, a common upgrade number of each business function module and a calling same-level business function module result of each business function module.

[0158] Further, the processing module 62 is specifically configured to:

[0159] For each business function module, if a zero-call duration in the calling information of the business function module is greater than a preset duration, a first exception list is generated, and the first exception list includes an identifier of the business function module and a first exception type.

[0160] Further, the exception list further includes an identifier of a common upgrade business function module; and the processing module 62 is specifically further configured to:

[0161] For each business function module, if a common upgrade number of a cross-application calling business function module in the calling information of the business function module is greater than a preset number, a second exception list is generated, and the second exception list includes an identifier of the business function module, an identifier of the common upgrade business function module, and a second exception type.

[0162] Further, the exception list further includes an identifier of a calling same-level business function module; and the processing module 62 is specifically further configured to:

[0163] For each business function module, if a calling same-level business function module result in the calling information of the business function module is a calling same-level business function module, a third exception list is generated, and the third exception list includes an identifier of the business function module, an identifier of the calling same-level business function module, and a third exception type.

[0164] Further, the processing module 62 is further configured to:

[0165] If a length of the business function module calling link is greater than a preset length threshold, a fourth exception list is generated, and the fourth exception list includes the business function module calling link and a fourth exception type.

[0166] Further, the sending module 62 is specifically configured to:

[0167] For each of the at least one exception list, according to an exception type in the exception list, a development end identifier and a sending frequency are determined;

[0168] According to the sending frequency, the exception list is sent to a development end corresponding to the development end identifier.

[0169] Further, the processing module 62 is further configured to:

[0170] For each of the at least one exception list, according to an exception type in the exception list, a preset processing scheme and a preset strategy graph corresponding to the exception type are obtained;

[0171] The preset processing scheme and the preset strategy graph corresponding to the exception type are added to the exception list.

[0172] The processing device of the exception service function module provided in the embodiment is used to execute the technical solutions in any of the method embodiments, and has similar implementation principles and technical effects, which will not be described here.

[0173] Figure 7 A structural schematic diagram of an electronic device is provided in the present application. As shown in the figure, Figure 7 The electronic device 70 includes:

[0174] A processor 71, a memory 72, and a communication interface 73;

[0175] The memory 72 is configured to store executable instructions of the processor 71;

[0176] The processor 71 is configured to execute the technical solutions in any of the method embodiments by executing the executable instructions.

[0177] Optionally, the memory 72 can be independent or integrated with the processor 71.

[0178] Optionally, when the memory 72 is independent of the processor 71, the electronic device 70 can further include:

[0179] A bus 74, the memory 72 and the communication interface 73 are connected with the processor 71 through the bus 74 and complete communication among each other, and the communication interface 73 is configured to communicate with other devices.

[0180] Optionally, the communication interface 73 can be implemented by a transceiver. The communication interface is used to realize the communication between the database access device and other devices (for example, a client, a read-write library and a read-only library). The memory can include a random access memory (RAM) and can also include a non-volatile memory, for example, at least one disk memory.

[0181] The bus 74 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or only one type of bus.

[0182] The processor described above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component.

[0183] The electronic device is used to execute the technical solutions in any of the preceding method embodiments, and has similar implementation principles and technical effects, which will not be described here.

[0184] The embodiment of the present application also provides a readable storage medium, which stores a computer program. The computer program is executed by a processor to realize the technical solutions provided by any of the preceding method embodiments.

[0185] The embodiment of the present application also provides a computer program product, which includes a computer program. The computer program is executed by a processor to realize the technical solutions provided by any of the preceding method embodiments.

[0186] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction-related hardware. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the foregoing storage medium includes a ROM, a RAM, a magnetic disk or an optical disk and various storage media that can store program codes.

[0187] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for processing an abnormal business function module, characterized in that: The method comprises: obtaining calling information of each business function module in a business system; wherein the calling information comprises zero calling quantity duration, common upgrade times of the business function module with cross-application calling, and calling same-layer business function module result; for each business function module, if the calling information of the business function module meets a preset abnormal calling condition corresponding to the calling information, at least one abnormal list is generated, the abnormal list comprising an identifier of the business function module and an abnormal type to which the business function module belongs; the preset abnormal calling condition comprises that the zero calling quantity duration is greater than a preset duration, the common upgrade times of the business function module with cross-application calling is greater than a preset number of times, and the calling same-layer business function module result is calling a same-layer business function module; the abnormal type comprises at least one of a first abnormal type, a second abnormal type, and a third abnormal type, the first abnormal type corresponding to the zero calling quantity duration being greater than the preset duration, the second abnormal type corresponding to the common upgrade times of the business function module with cross-application calling being greater than the preset number of times, and the third abnormal type corresponding to the calling same-layer business function module result being calling the same-layer business function module; sending the at least one abnormal list to a development end; the obtaining of the calling information of each business function module in the business system comprises: obtaining, through a service registration center, calling quantity information corresponding to each business function module in the business system; and determining, according to the calling quantity information corresponding to each business function module, a zero calling quantity duration of each business function module. obtaining, through a software resource management system, a business function module calling link corresponding to the business system; obtaining, through a project management system, project list information corresponding to the business system, an application corresponding to each business function module in the business system, and a business level corresponding to each business function module in the business system; and determining, according to the application corresponding to each business function module, the business level corresponding to each business function module, the project list information, and the business function module calling link, common upgrade times of each business function module with cross-application calling and calling same-layer business function module result of each business function module.

2. The method of claim 1, wherein, the generation of the at least one abnormal list for each business function module if the calling information of the business function module meets the preset abnormal calling condition corresponding to the calling information comprises: for each business function module, if the zero calling quantity duration in the calling information of the business function module is greater than a preset duration, a first abnormal list is generated, the first abnormal list comprising an identifier of the business function module and a first abnormal type.

3. The method according to claim 1 or 2, characterized in that, the abnormal list further comprises an identifier of a common upgrade business function module; and the generation of the at least one abnormal list for each business function module if the calling information of the business function module meets the preset abnormal calling condition corresponding to the calling information comprises: For each business function module, if the common upgrade times of the business function module with the cross-application invoked business function module in the calling information of the business function module is greater than a preset number of times, a second exception list is generated, the second exception list comprising an identification of the business function module, an identification of the commonly upgraded business function module, and a second exception type.

4. The method of claim 3, wherein, The exception list further comprises an identification of a same-layer invoked business function module; and the method further comprises: For each business function module, if the calling same-layer business function module result in the calling information of the business function module is calling a same-layer business function module, a third exception list is generated, the third exception list comprising an identification of the business function module, an identification of the same-layer invoked business function module, and a third exception type.

5. The method of claim 4, wherein, The method further comprises: If the length of the business function module calling link is greater than a preset length threshold, a fourth exception list is generated, the fourth exception list comprising the business function module calling link and a fourth exception type.

6. The method of claim 5, wherein, The sending of the at least one exception list to the development end comprises: For each exception list in the at least one exception list, a development end identification and a sending frequency are determined according to the exception type in the exception list; The exception list is sent to the development end corresponding to the development end identification according to the sending frequency.

7. The method of claim 6, wherein, Before the sending of the at least one exception list to the development end, the method further comprises: For each exception list in the at least one exception list, a preset processing scheme and a preset strategy graph corresponding to the exception type are obtained according to the exception type in the exception list; The preset processing scheme and the preset strategy graph corresponding to the exception type are added to the exception list.

8. A processing device of an abnormal service function module, characterized by, comprises: an obtaining module, configured to obtain calling information of each business function module in a business system; wherein the calling information comprises a zero-call-quantity duration, common upgrade times of the business function module with a cross-application invoked business function module, and a calling same-layer business function module result; a processing module, configured to, for each business function module, if the calling information of the business function module satisfies a preset exception calling condition corresponding to the calling information, generate at least one exception list, the exception list comprising an identification of the business function module and an exception type to which the business function module belongs; the preset exception calling condition comprises that the zero-call-quantity duration is greater than a preset duration, the common upgrade times of the business function module with the cross-application invoked business function module is greater than a preset number of times, and the calling same-layer business function module result is calling a same-layer business function module; the exception type comprises at least one of a first exception type, a second exception type, and a third exception type, the first exception type corresponding to the zero-call-quantity duration being greater than the preset duration, the second exception type corresponding to the common upgrade times of the business function module with the cross-application invoked business function module being greater than the preset number of times, and the third exception type corresponding to the calling same-layer business function module result being calling the same-layer business function module; a sending module, configured to send the at least one exception list to a development end; the obtaining module is specifically configured to: Obtain, through the service registry center, calling quantity information corresponding to each business function module in the business system; determine a zero calling quantity duration of each business function module according to the calling quantity information corresponding to each business function module; Obtain, through the software resource management system, a business function module calling link corresponding to the business system; obtain, through the project management system, project list information corresponding to the business system, an application corresponding to each business function module in the business system, and a business level corresponding to each business function module in the business system; determine a common upgrade number of each business function module and a business function module called by each business function module according to the application corresponding to each business function module, the business level corresponding to each business function module, the project list information, and the business function module calling link.

9. An electronic device, comprising: Comprise: A processor, a memory, and a communication interface; The memory is configured to store executable instructions of the processor; The processor is configured to execute the executable instructions to perform the processing method of the abnormal business function module according to any one of claims 1 to 7.

10. A readable storage medium having a computer program stored thereon, characterized in that: The computer program is executed by the processor to implement the processing method of the abnormal business function module according to any one of claims 1 to 7.

11. A computer program product, characterised in that, The computer program is executed by the processor to implement the processing method of the abnormal business function module according to any one of claims 1 to 7.

Images