Business system calling relation management method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a business system calling relation management method and device, electronic equipment and a storage medium, and belongs to the technical field of finance and the field of medical services. The method comprises the following steps: acquiring calling relation burying point data from a target business system; grouping the calling relation burying point data according to a preset calling relation type to obtain a plurality of calling relation data groups; calculating the calling times of each calling relation in each calling relation data group, and generating a calling relation distribution matrix according to the calling times of each calling relation; for each calling relation data group, generating an alternative optimization calling relation list based on the calling relation distribution matrix and a preset first calling frequency threshold value; sending the alternative optimization calling relation list to the target object; and in response to the obtained target optimization calling relation list sent by the target object, deleting the corresponding calling relation according to the target optimization calling relation list. The embodiment of the invention can improve the management efficiency of the calling relationship of the business system.

Description

Technical Field

[0001] The present invention relates to the technical fields of finance and medical services, and particularly to a method and device for managing business system call relationships, an electronic device, and a storage medium. Background Art

[0002] In the technical fields of finance and medical services, multiple complex business systems need to be run to support daily operations. For example, financial institutions in the financial technology field need to run core accounting systems, payment and settlement systems, risk control systems, etc., and medical institutions in the medical service field need to run electronic medical record systems, medical imaging systems, drug management systems, etc. There are a large number of data exchanges and function call relationships between these business systems.

[0003] In the related art, the management of business system call relationships mainly relies on manual management. Operation and maintenance personnel manually sort out and maintain the call relationships between business systems by viewing system logs, deployment documents, etc. Manual management is inefficient. Especially when dealing with large-scale systems deployed across departments and regions, it is easy to have incomplete or inconsistent information. At the same time, after the business system is upgraded or transformed, the call relationships may change, and some outdated or redundant call relationships may exist for a long time. Therefore, there is an urgent need for a more efficient method for managing business system call relationships. Summary of the Invention

[0004] The main purpose of the embodiments of the present application is to propose a method and device for managing business system call relationships, an electronic device, and a storage medium, aiming to improve the management efficiency of business system call relationships.

[0005] To achieve the above object, the first aspect of the embodiments of the present application proposes a method for managing business system call relationships, and the method includes:

[0006] Obtain call relationship buried point data from a target business system;

[0007] Group the call relationship buried point data according to a preset call relationship type to obtain multiple call relationship data groups;

[0008] Calculate the call times of each call relationship in each call relationship data group, and generate a call relationship distribution matrix according to the call times of each call relationship;

[0009] For each call relationship data group, generate an alternative optimized call relationship list based on the call relationship distribution matrix and a preset first call times threshold;

[0010] Send the alternative optimized call relationship list to a target object so that the target object can screen and obtain a target optimized call relationship list from the alternative optimized call relationship list;

[0011] In response to obtaining the target optimized call relationship list sent by the target object, delete the corresponding call relationship according to the target optimized call relationship list.

[0012] In some embodiments, for each of the call relationship data groups, generating an alternative optimized call relationship list based on the call relationship distribution matrix and a preset first call count threshold includes:

[0013] For each of the call relationship data groups, obtain the call relationship distribution matrix data within a preset time window;

[0014] For each call relationship in the call relationship distribution matrix, calculate the total number of calls within the preset time window;

[0015] Compare the total number of calls with the first call count threshold, and if the total number of calls is less than the first call count threshold, add this call relationship to the alternative optimized call relationship list.

[0016] In some embodiments, the method further includes:

[0017] For each of the call relationship data groups, generate a list of invalid call relationships based on the call relationship distribution matrix and a preset second call count threshold; wherein the second call count threshold is lower than the first call count threshold;

[0018] Send the list of invalid call relationships to the target object;

[0019] If no feedback is received from the target object within a preset waiting time, perform a deletion operation on the call relationships in the list of invalid call relationships.

[0020] In some embodiments, the method further includes:

[0021] Calculate the call count change rate of each call relationship in the call relationship distribution matrix in adjacent time windows;

[0022] In response to detecting that the call count change rate of a call relationship exceeds a preset change rate threshold and the call count change rate is in a downward trend, add this call relationship to the alternative optimized call relationship list.

[0023] In some embodiments, the step of, in response to obtaining the target optimized call relationship list sent by the target object, deleting the corresponding call relationship according to the target optimized call relationship list includes:

[0024] Determine the optimization operation type for each call relationship in the target optimized call relationship list; wherein, the optimization operation type includes an immediate deletion type and a scheduled deletion type;

[0025] For the call relationships of the immediate deletion type, directly execute the deletion operation;

[0026] For the call relationships of the scheduled deletion type, obtain the preset system off-peak period time range, and execute the deletion operation within the system off-peak period time range;

[0027] Monitor the system running state after the deletion operation is executed. If system anomalies are detected, restore the deleted call relationships.

[0028] In some embodiments, the grouping of the call relationship buried point data according to the preset call relationship type to obtain multiple call relationship data groups includes:

[0029] Parse the caller identifier and the callee identifier in each piece of call relationship buried point data;

[0030] According to the caller identifier and the callee identifier, determine the call relationship type to which each call relationship belongs; wherein, the preset call relationship types include direct inter-system calls, message queue calls, database calls, and external interface calls;

[0031] Divide the call relationship buried point data with the same call relationship type into the same call relationship data group to obtain multiple call relationship data groups.

[0032] In some embodiments, after deleting the corresponding call relationships according to the target optimized call relationship list, it further includes:

[0033] Generate a call relationship deletion operation log; wherein, the call relationship deletion operation log includes the deleted call relationship identifier, deletion time, deletion reason, and the corresponding target object identifier;

[0034] Send the call relationship deletion operation log to the target operation and maintenance object through a preset notification method;

[0035] Within a preset monitoring period, obtain the system performance indicators of the callers and callees involved in the deleted call relationships;

[0036] If the system performance indicators are lower than the preset performance threshold, send an alarm message to the preset operation and maintenance personnel.

[0037] To achieve the above object, a second aspect of the embodiments of the present application proposes a business system call relationship management device, the device includes:

[0038] The buried point data acquisition module is used to acquire the call relationship buried point data from the target business system;

[0039] The data group module is used to group the call relationship buried point data according to the preset call relationship types to obtain multiple call relationship data groups;

[0040] The distribution matrix module is used to calculate the call times of each call relationship in each call relationship data group, and generate a call relationship distribution matrix according to the call times of each call relationship;

[0041] The alternative list module is used to generate an alternative optimized call relationship list for each call relationship data group based on the call relationship distribution matrix and the preset first call times threshold;

[0042] The target list module is used to send the alternative optimized call relationship list to the target object, so that the target object can screen and obtain the target optimized call relationship list from the alternative optimized call relationship list;

[0043] The deletion module is used to respond to obtaining the target optimized call relationship list sent by the target object, and delete the corresponding call relationship according to the target optimized call relationship list.

[0044] To achieve the above object, a third aspect of the embodiments of the present application proposes an electronic device, which includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the method described in the first aspect above is implemented.

[0045] To achieve the above object, a fourth aspect of the embodiments of the present application proposes a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the method described in the first aspect above is implemented.

[0046] The business system call relationship management method, device, electronic device and storage medium proposed by the present application acquire the call relationship buried point data from the target business system, group the call relationship buried point data according to the preset call relationship types to obtain multiple call relationship data groups, calculate the call times of each call relationship in each call relationship data group, generate a call relationship distribution matrix according to the call times of each call relationship, generate an alternative optimized call relationship list for each call relationship data group based on the call relationship distribution matrix and the preset first call times threshold, send the alternative optimized call relationship list to the target object, so that the target object can screen and obtain the target optimized call relationship list from the alternative optimized call relationship list, and respond to obtaining the target optimized call relationship list sent by the target object, and delete the corresponding call relationship according to the target optimized call relationship list.

[0047] First, by obtaining the call relationship buried point data of the target business system, the call relationships between various modules or services in the target business system can be comprehensively and accurately captured, providing a reliable data basis for subsequent analysis. By grouping the call relationship buried point data according to the preset call relationship types, multiple call relationship data groups are obtained, enabling classification management according to the characteristics of different call relationships and improving the pertinence and efficiency of call relationship analysis. By calculating the call times of the call relationships in each call relationship data group and generating a call relationship distribution matrix, the distribution and call frequency of the call relationships in the system can be intuitively reflected, providing data support for optimization decisions. Generating a list of alternative optimized call relationships based on the call relationship distribution matrix and the preset first call times threshold can automatically identify potential inefficient or redundant call relationships and reduce the workload of manual screening. By sending the list of alternative optimized call relationships to the target object for screening, the accuracy and rationality of the optimization decision can be ensured by combining manual judgment and system analysis. Finally, deleting the corresponding call relationships according to the target optimized call relationship list can effectively optimize the call structure of the business system and improve the management efficiency of the call relationships in the business system. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 is a flowchart of the business system call relationship management method provided by an embodiment of the present application;

[0049] Figure 2 is another flowchart of the business system call relationship management method provided by an embodiment of the present application;

[0050] Figure 3 is another flowchart of the business system call relationship management method provided by an embodiment of the present application;

[0051] Figure 4 is another flowchart of the business system call relationship management method provided by an embodiment of the present application;

[0052] Figure 5 is another flowchart of the business system call relationship management method provided by an embodiment of the present application;

[0053] Figure 6 is another flowchart of the business system call relationship management method provided by an embodiment of the present application;

[0054] Figure 7 is another flowchart of the business system call relationship management method provided by an embodiment of the present application;

[0055] Figure 8 is a schematic structural diagram of the business system call relationship management device provided by an embodiment of the present application;

[0056] Figure 9 It is a schematic diagram of the hardware structure of the electronic device provided by the embodiment of the present application. Detailed implementation manners

[0057] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

[0058] It should be noted that although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order from the module division in the device or the flowchart. Terms such as "first" and "second" in the specification, claims and the above drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence.

[0059] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application, and are not intended to limit this application.

[0060] Based on this, the embodiments of the present application provide a method and device for managing the call relationship of business systems, an electronic device and a storage medium, aiming to improve the management efficiency of the call relationship of business systems.

[0061] The method and device for managing the call relationship of business systems, the electronic device and the storage medium provided by the embodiments of the present application will be described in detail through the following embodiments. First, the method for managing the call relationship of business systems in the embodiments of the present application will be described.

[0062] The method for managing the call relationship of business systems provided by the embodiments of the present application relates to the technical field of financial services. The method for managing the call relationship of business systems provided by the embodiments of the present application can be applied to a terminal, or to a server side, or can also be software running on a terminal or a server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or can be configured as a server cluster or a distributed system composed of multiple physical servers, or can also be configured as a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the method for managing the call relationship of business systems, etc., but is not limited to the above forms.

[0063] This application can be used in numerous general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and so on. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This application can also be practiced in a distributed computing environment where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0064] It should be noted that in each specific embodiment of this application, when it comes to relevant processing based on data related to the user's identity or characteristics, such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first. Moreover, the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiments of this application need to obtain the user's sensitive personal information, the user's separate permission or separate consent will be obtained through methods such as pop-up windows or jumping to a confirmation page. After clearly obtaining the user's separate permission or separate consent, the necessary user-related data for the normal operation of the embodiments of this application will be obtained.

[0065] Figure 1 is an optional flowchart of the business system call relationship management method provided by the embodiments of this application, Figure 1 The method in may include but is not limited to steps S101 to S106.

[0066] Step S101, obtain call relationship buried point data from the target business system.

[0067] Step S102, group the call relationship buried point data according to a preset call relationship type to obtain multiple call relationship data groups.

[0068] Step S103, calculate the call times of each call relationship in each call relationship data group, and generate a call relationship distribution matrix based on the call times of each call relationship.

[0069] Step S104, for each call relationship data group, generate an alternative optimized call relationship list based on the call relationship distribution matrix and a preset first call times threshold.

[0070] Step S105: Send the list of alternative optimized call relationships to the target object, so that the target object can screen out the target optimized call relationship list from the list of alternative optimized call relationships.

[0071] Step S106: In response to obtaining the target optimized call relationship list sent by the target object, delete the corresponding call relationships according to the target optimized call relationship list.

[0072] Steps S101 to S106 illustrated in the embodiments of the present application can, first of all, comprehensively and accurately capture the call relationships between various modules or services in the target business system by obtaining the call relationship buried point data of the target business system, providing a reliable data basis for subsequent analysis; by grouping the call relationship buried point data according to the preset call relationship types to obtain multiple call relationship data groups, it is possible to classify and manage according to the characteristics of different call relationships, improving the pertinence and efficiency of call relationship analysis; by calculating the call times of the call relationships in each call relationship data group and generating a call relationship distribution matrix, it is possible to intuitively reflect the distribution and call frequency of the call relationships in the system, providing data support for optimization decisions; generating a list of alternative optimized call relationships based on the call relationship distribution matrix and the preset first call times threshold can automatically identify potential inefficient or redundant call relationships, reducing the workload of manual screening; by sending the list of alternative optimized call relationships to the target object for screening, it is possible to combine manual judgment and system analysis to ensure the accuracy and rationality of optimization decisions; finally, deleting the corresponding call relationships according to the target optimized call relationship list can effectively optimize the call structure of the business system and improve the management efficiency of the call relationships in the business system.

[0073] In step S101 of some embodiments, the target business system refers to the business system that needs to have its call relationships sorted out and optimized. For example, it can be used to support the daily operations of financial institutions or medical institutions, involving complex call relationships between multiple modules or services. In the field of financial technology, the target business system usually includes a core accounting system, a payment and settlement system, a risk control system, a user authentication system, etc. With the increase in business requirements and the continuous expansion of the system, the architecture of the target business system may become bloated, and the call relationships may also become redundant or inefficient.

[0074] It is understandable that call relationship buried point data between various modules or services in the target business system is obtained in real time through the buried point technology. The call relationship buried point data includes various types of information such as, but not limited to, call source, call target, call time, call parameters, etc. Among them, the call source mainly involves the module or service that initiates the call; the call target includes the module or service that is called; the call time records the specific time point of the call; and the call parameters contain the key data passed during the call. The call relationship buried point data can be preliminarily processed, including removing duplicate data, supplementing metadata such as call context information, and classifying and storing it in the corresponding database according to different call relationship types.

[0075] Exemplarily, in the field of financial technology, call relationship buried point data in the target business system is obtained through the buried point technology. For example, the call relationship buried point data includes "records of the core accounting system calling the payment and settlement system", "records of the payment and settlement system calling the risk control system", "records of the risk control system calling the user authentication system", etc. Each piece of call relationship buried point data can include information such as the source, target, time, and parameters of the call. In the field of medical services, the call relationship buried point data includes "records of the electronic medical record system calling the medical imaging system", "records of the drug management system calling the electronic medical record system", "records of the medical imaging system calling the diagnostic assistance system", etc.

[0076] In step S102 of some embodiments, the call relationship buried point data is grouped according to the preset call relationship types to obtain multiple call relationship data groups. The preset call relationship types can include different types such as inter-service calls, inter-module calls, and inter-system calls. Each call relationship data group contains call relationship data of the same type, which is convenient for subsequent statistics and analysis. According to the specific characteristics of the target business system, such as system architecture, service division, call frequency, etc., specific grouping rules are adopted to classify the call relationship buried point data to ensure that each call relationship data group can accurately reflect the characteristics of a certain type of call relationship. For example, in the banking business system, the synchronous calls between the payment and settlement system and the core accounting system are classified into the direct inter-system call group, and the operations of the business system accessing the customer information database are classified into the database call group.

[0077] Please refer to Figure 2 , in some embodiments, step S102 may include, but is not limited to, steps S201 to S203:

[0078] Step S201, parse the call party identifier and the called party identifier in each piece of call relationship buried point data.

[0079] Step S202, determine the call relationship type to which each call relationship belongs according to the call party identifier and the called party identifier.

[0080] Among them, the preset call relationship types include direct system calls, message queue calls, database calls, and external interface calls.

[0081] Step S203: Divide the call relationship buried point data with the same call relationship type into the same call relationship data group to obtain multiple call relationship data groups.

[0082] In step S201 of some embodiments, the caller identifier and the callee identifier in each piece of call relationship buried point data are parsed. The caller identifier is used to identify the module or service that initiates the call, and the callee identifier is used to identify the module or service that is called. For example, a piece of call relationship buried point data obtained by parsing is "Caller: Electronic Medical Record System, Callee: Medical Imaging System". By parsing the caller identifier and the callee identifier, the source and target of each call relationship can be accurately identified, providing basic data for subsequent call relationship classification.

[0083] In step S202 of some embodiments, according to the caller identifier and the callee identifier, determine the call relationship type to which each call relationship belongs; among them, the preset call relationship types include direct system calls, message queue calls, database calls, and external interface calls. For example, in the financial field, the direct call from the trading system to the clearing system is identified as a direct system call, and the batch transaction processing of the accounting system through the message queue is identified as a message queue call, the query of customer information by the account system is identified as a database call, and the call from the bank system to the external credit investigation service is identified as an external interface call; in the medical field, the call from the emergency system to the patient history system is identified as a direct system call, the distribution of test results through the message queue is identified as a message queue call, the access of the pharmacy system to the drug inventory database is identified as a database call, and the connection of the hospital system to the external insurance verification service is identified as an external interface call.

[0084] Exemplarily, in the financial field, the direct call from the trading system to the clearing system is identified as a direct system call and is further divided into real-time clearing components, batch clearing components, etc.; the query of customer information by the accounting system is identified as a database call and is divided into specific types such as Oracle customer information database, MySQL transaction flow database, etc.; in the medical field, the call from the emergency system to the patient history system is identified as a direct system call and is further divided into medical record query components, prescription components, test components, etc.

[0085] In step S203 of some embodiments, the call relationship buried point data with the same call relationship type is divided into the same call relationship data group, and multiple call relationship data groups are obtained. For example, the data of the core accounting system calling the payment and settlement system is divided into the same call relationship data group; the call relationship of the risk control system to the user authentication system is divided into the "database call data group (Oracle)", which realizes the call relationship through the Oracle database, and the complex call relationship buried point data is classified according to the type and specific implementation method.

[0086] Through the above steps S201 to S203, the efficient classification and management of the call relationships of the business systems are realized, the sources and targets of the call relationships are accurately identified, and a reliable data basis is provided for subsequent analysis. Through refined classification (such as direct calls between systems, message queue calls, database calls, external interface calls), the call relationships are grouped by type, which is convenient for targeted optimization, significantly improves the call relationship management efficiency, and reduces the system complexity and operation and maintenance costs.

[0087] In step S103 of some embodiments, the call times of each call relationship in each call relationship data group are calculated, and a call relationship distribution matrix is generated according to the call times. The call relationship distribution matrix can intuitively reflect the call frequencies and distribution of each call relationship in the system. Through the call relationship distribution matrix, high-frequency call relationships and low-frequency call relationships can be quickly identified, providing data support for subsequent optimization decisions.

[0088] Exemplarily, the call relationship distribution matrix is a two-dimensional matrix, where the rows represent the callers (i.e., the modules or services that initiate the calls), the columns represent the callees (i.e., the modules or services that are called), and each element in the matrix represents the call times of the corresponding call relationship. Through the call relationship distribution matrix, it can be clearly seen which call relationships in the system are high-frequency, which are low-frequency, and even which call relationships have not been used for a long time. The call relationship distribution matrix can also be analyzed in combination with the time dimension. For example, in the financial field, a call relationship distribution matrix within the most recent 30 days can be generated to analyze the change trend of the call times. Through the analysis of the time dimension, the activity changes of the call relationships can be more dynamically identified, providing more comprehensive data support for optimization decisions.

[0089] In step S104 of some embodiments, for each call relationship data group, an alternative optimized call relationship list is generated based on the call relationship distribution matrix and a preset first call count threshold. The first call count threshold is used to filter out call relationships with too low or too high call counts. For example, it can identify cross-system interfaces with low call frequencies in a banking business system or database access operations with low usage frequencies in a medical service system. These call relationships may have redundancy or inefficiency issues. By automatically generating an alternative optimized call relationship list, the workload of manual screening can be reduced and the optimization efficiency can be improved.

[0090] Please refer to Figure 3 , in some embodiments, step S104 may include but is not limited to steps S301 to S303:

[0091] Step S301, for each call relationship data group, obtain the call relationship distribution matrix data within a preset time window.

[0092] Step S302, for each call relationship in the call relationship distribution matrix, calculate the total call count within the preset time window.

[0093] Step S303, compare the total call count with the first call count threshold. If the total call count is less than the first call count threshold, add the call relationship to the alternative optimized call relationship list.

[0094] In step S301 of some embodiments, for each call relationship data group, obtain the call relationship distribution matrix data within a preset time window. The preset time window can be different time dimensions such as daily, weekly, or monthly, and is used to dynamically analyze the activity of call relationships. By obtaining the call relationship distribution matrix data within the preset time window, time-dimensional support can be provided for subsequent call count statistics and optimization decisions.

[0095] In step S302 of some embodiments, for each call relationship in the call relationship distribution matrix, calculate the total call count within the preset time window. By calculating the total call count, the activity level of each call relationship within the preset time window can be accurately quantified. For example, the total call count of the pharmacy system calling the drug inventory database (a MySQL type database) in the last 7 days is 2 times.

[0096] In step S303 of some embodiments, the total number of calls is compared with the first call number threshold. If the total number of calls is less than the first call number threshold, the call relationship is added to the alternative optimized call relationship list. For example, in the medical field, the first call number threshold can be preset to 5 times. If the total number of calls of "the electronic medical record system calls the medical imaging database" is 50 times (greater than the first call number threshold), it is not added to the alternative optimized call relationship list; if the total number of calls of "the pharmacy system calls the drug inventory database (MySQL)" is 2 times (less than the first call number threshold), it is added to the alternative optimized call relationship list. The first call number threshold is used to screen out call relationships with too low or redundant call numbers. By automatically generating the alternative optimized call relationship list, the workload of manual screening can be reduced and the optimization efficiency can be improved.

[0097] Through the above steps S301 to S303, the efficient monitoring and analysis of the call relationships of the business system are realized. Based on the call relationship distribution matrix data within the preset time window, the activity degree of the call relationships can be dynamically identified; by calculating the total number of calls and comparing it with the first call number threshold, inefficient or redundant call relationships can be automatically screened out, providing data support for subsequent optimization decisions and better meeting the requirements of call relationship management.

[0098] In step S105 of some embodiments, the alternative optimized call relationship list is sent to the target object, so that the target object can screen out the target optimized call relationship list from the alternative optimized call relationship list. The target object can be a system administrator or a developer, and they screen and confirm the alternative optimized call relationship list according to the business requirements and the actual situation of the system to form the final target optimized call relationship list.

[0099] It can be understood that the alternative optimized call relationship list is generated based on the call relationship distribution matrix and the preset first call number threshold, and it contains call relationships with too low call numbers. These call relationships may be redundant, inefficient or no longer in use, but the final optimization decision needs to be manually confirmed in combination with the business requirements and the actual situation of the system. Therefore, sending the alternative optimized call relationship list to the target object can ensure the accuracy and rationality of the optimization decision.

[0100] In step S106 of some embodiments, in response to obtaining the target optimized call relationship list sent by the target object, the corresponding call relationships are deleted according to the target optimized call relationship list. By deleting redundant or inefficient call relationships, the call structure of the business system can be effectively optimized, the system complexity can be reduced, and the system performance and maintainability can be improved.

[0101] Please refer to Figure 4, in some embodiments, step S106 may include but is not limited to steps S401 to S404:

[0102] Step S401, determine the optimization operation type of each call relationship in the target optimization call relationship list.

[0103] Among them, the optimization operation types include the immediate deletion type and the scheduled deletion type.

[0104] Step S402, for the call relationships of the immediate deletion type, directly execute the deletion operation.

[0105] Step S403, for the call relationships of the scheduled deletion type, obtain the preset low-peak period of the system, and execute the deletion operation during the low-peak period of the system.

[0106] Step S404, monitor the running state of the system after the deletion operation is executed. If the system anomaly is detected, restore the deleted call relationships.

[0107] In step S401 of some embodiments, determine the optimization operation type of each call relationship in the target optimization call relationship list. The optimization operation types include the immediate deletion type and the scheduled deletion type, which are used to select the appropriate deletion strategy according to the importance of the call relationship and the degree of business impact. For example, in the financial field, if the call relationship of "the accounting system calls the customer information database" is included in the target optimization call relationship list, and the number of calls of this call relationship has been continuously decreasing in the past three months, it can be marked as the "immediate deletion type"; if the call relationship of "the payment module of the bank APP calls the risk control system" is included in the list, and the number of calls of this call relationship is relatively low during non-peak hours, it can be marked as the "scheduled deletion type". By determining the optimization operation type, it is possible to select the appropriate deletion strategy according to the actual situation of the call relationship and avoid unnecessary impacts on the business system.

[0108] In step S402 of some embodiments, for the call relationships of the immediate deletion type, directly execute the deletion operation. The immediate deletion type is applicable to the situation where the call relationship has little impact on the business system or the call relationship has been clearly no longer used. By directly executing the deletion operation, redundant or inefficient call relationships can be quickly cleared, improving the system performance.

[0109] In step S403 of some embodiments, for the call relationship of the planned deletion type, obtain the preset system low-peak period, and perform the deletion operation during the system low-peak period. The planned deletion type is applicable to situations where the call relationship has a certain impact on the business system or needs to perform the deletion operation within a specific time period. For example, in the medical field, if "the electronic medical record system calls the medical imaging database" is marked as the planned deletion type, the system will obtain the preset low-peak period (such as 1:00 pm to 2:00 pm) and perform the deletion operation during this period. By performing the deletion operation during the system low-peak period, the impact on the business system can be minimized to ensure the stable operation of the system.

[0110] In step S404 of some embodiments, monitor the system running state after the deletion operation is executed. If the system is detected to be abnormal, restore the deleted call relationship. After the deletion operation is executed, monitor the key performance indicators (such as response time, error rate, system load, etc.) in real time. If an abnormal situation is detected, automatically restore the deleted call relationship to ensure the security of the deletion operation and avoid irreversible impacts on the business system.

[0111] Through the above steps S401 to S404, the efficient processing of the target optimized call relationship list is realized: First, determine the optimization operation type (immediate deletion type or planned deletion type) according to the importance and business impact degree of the call relationship; directly perform the deletion operation on the call relationship of the immediate deletion type to quickly clean up redundant or inefficient call relationships; perform the deletion operation on the call relationship of the planned deletion type during the system low-peak period to minimize the impact on the business system; through the monitoring and recovery mechanism, ensure the security of the deletion operation, and significantly improve the management efficiency of the call relationship in the business system.

[0112] Please refer to Figure 5 , in some embodiments, after deleting the corresponding call relationship according to the target optimized call relationship list, it may include but is not limited to steps S501 to S504:

[0113] Step S501, generate a call relationship deletion operation log.

[0114] Among them, the call relationship deletion operation log includes the deleted call relationship identifier, deletion time, deletion reason, and the corresponding target object identifier.

[0115] Step S502, send the call relationship deletion operation log to the target operation and maintenance object through the preset notification method.

[0116] Step S503, within the preset monitoring period, obtain the system performance indicators of the callers and callees involved in the deleted call relationship.

[0117] Step S504: If the system performance index is lower than the preset performance threshold, send an alarm message to the preset operation and maintenance personnel.

[0118] In step S501 of some embodiments, an operation log for deleting the call relationship is generated. The operation log for deleting the call relationship is used to record the detailed information of the call relationship deletion operation, including the call relationship identifier to be deleted, the deletion time, the deletion reason, and the corresponding target object identifier.

[0119] In step S502 of some embodiments, the operation log for deleting the call relationship is sent to the target operation and maintenance object through a preset notification method. The preset notification methods may include emails, text messages, instant messaging tools, etc., which are used to ensure that the target operation and maintenance object can obtain the relevant information of the deletion operation in a timely manner. The preset notification method can be personalized according to the preferences of the target operation and maintenance object. For example, some target operation and maintenance objects prefer to receive notifications through instant messaging tools, while others prefer to receive notifications through emails.

[0120] In step S503 of some embodiments, within the preset monitoring period, the system performance indexes of the callers and callees involved in the deleted call relationship are obtained. The preset monitoring period can be a time period such as 24 hours or 7 days after the deletion operation is executed, which is used to comprehensively evaluate the impact of the deletion operation on the system performance. It can be dynamically adjusted according to the complexity of the system and business requirements. For example, for a critical business system, a longer monitoring period can be set to ensure the stability of the system performance. The system performance indexes may include response time, error rate, system load, etc.

[0121] In step S504 of some embodiments, if the system performance index is lower than the preset performance threshold, send an alarm message to the preset operation and maintenance personnel. The preset performance threshold is used to determine whether the system performance is within the normal range. The preset performance threshold can be dynamically adjusted according to historical data and system load conditions to improve the accuracy and timeliness of the alarm. If the system performance index is lower than the threshold, it indicates that the deletion operation may have a negative impact on the system. By sending an alarm message, the operation and maintenance personnel can be reminded to take timely measures to ensure the stable operation of the system.

[0122] Through steps S501 to S504, the comprehensive monitoring and management of the call relationship deletion operation are realized. An operation log for deleting the call relationship is generated to record the detailed information of the deletion operation; the operation log for deleting the call relationship is sent to the target operation and maintenance object to ensure the transparency and traceability of the operation; the system performance indexes are obtained within the preset monitoring period to evaluate the impact of the deletion operation on the system; if the system performance index is lower than the preset threshold, an alarm message is sent to remind the operation and maintenance personnel to handle it in a timely manner, significantly improving the security and controllability of the deletion operation and ensuring the stable operation of the business system after optimizing the call relationship.

[0123] Please refer to Figure 6 In some embodiments, the method for managing the call relationship of the service system may further include but is not limited to steps S601 to S603:

[0124] Step S601: For each call relationship data group, generate a list of invalid call relationships based on the call relationship distribution matrix and a preset second call count threshold.

[0125] Among them, the second call count threshold is lower than the first call count threshold.

[0126] Step S602: Send the list of invalid call relationships to the target object.

[0127] Step S603: If no feedback is received from the target object within the preset waiting time, perform a deletion operation on the call relationships in the list of invalid call relationships.

[0128] In step S601 of some embodiments, for each call relationship data group, a list of invalid call relationships is generated based on the call relationship distribution matrix and a preset second call count threshold. The list of invalid call relationships is used to record the call relationships whose call counts are lower than the second call count threshold. These call relationships may have become invalid or are no longer in use. The second call count threshold is lower than the first call count threshold and is used to identify call relationships that have not been used for a long time.

[0129] In step S602 of some embodiments, the list of invalid call relationships is sent to the target object. The target object can be a system administrator, a developer, or a business person in charge, and is used to confirm and provide feedback on the list of invalid call relationships. The notification methods may include emails, text messages, instant messaging tools, etc., to ensure that the target object can timely learn about potential invalid call relationships and make corresponding decisions.

[0130] In step S603 of some embodiments, if no feedback is received from the target object within the preset waiting time, a deletion operation is performed on the call relationships in the list of invalid call relationships. The preset waiting time can be 24 hours, 48 hours, etc., to give the target object sufficient time to confirm and provide feedback. For example, in the medical field, if the target object does not provide feedback on the "pharmacy system calls the drug inventory database" in the list of invalid call relationships within 48 hours, this call relationship will be automatically deleted.

[0131] Through the above steps S601 to S603, the automatic identification and cleaning of invalid call relationships are realized. An invalid call relationship list is generated based on the call relationship distribution matrix and the second call count threshold to identify call relationships that have not been used for a long time. The invalid call relationship list is sent to the target object to ensure that it can promptly understand potential problems. If no feedback is received within the preset waiting time, the invalid call relationships are automatically deleted, further optimizing system resources, enhancing the automation level of the call relationship management in the business system, and reducing system complexity and operation and maintenance costs.

[0132] Please refer to Figure 7 , in some embodiments, the method for managing call relationships in a business system may further include, but is not limited to, steps S701 to S702:

[0133] Step S701, calculate the change rate of the call count of each call relationship in the adjacent time windows in the call relationship distribution matrix.

[0134] Step S702, in response to detecting that the change rate of the call count of a call relationship exceeds a preset change rate threshold and the change rate of the call count is in a downward trend, add this call relationship to the alternative optimization call relationship list.

[0135] In step S701 of some embodiments, calculate the change rate of the call count of each call relationship in the adjacent time windows in the call relationship distribution matrix. The change rate of the call count is used to quantify the change in the call count of the call relationship in the adjacent time windows. By calculating the change rate of the call count, the active change trend of the call relationship can be dynamically identified.

[0136] In step S702 of some embodiments, in response to detecting that the change rate of the call count of a call relationship exceeds a preset change rate threshold and the change rate of the call count is in a downward trend, add this call relationship to the alternative optimization call relationship list. The preset change rate threshold is used to determine whether the active change of the call relationship is significant. The downward trend indicates that the usage frequency of the call relationship is decreasing. By identifying the call relationships with abnormal change rates of the call count, potential inefficient or redundant call relationships can be discovered in a timely manner.

[0137] Through the above steps S701 to S702, the dynamic monitoring and analysis of the active change of the call relationship are realized. Calculate the change rate of the call count of the call relationship in the adjacent time windows to quantify the active change trend of the call relationship. Identify the call relationships whose change rates of the call count exceed the preset threshold and are in a downward trend, and add them to the alternative optimization call relationship list, which can discover potential inefficient or redundant call relationships in a timely manner and improve the efficiency and accuracy of the call relationship management in the business system.

[0138] The business system call relationship management method, device, electronic device, and storage medium proposed in this application obtain call relationship buried point data from a target business system, group the call relationship buried point data according to a preset call relationship type to obtain multiple call relationship data groups, calculate the call times of each call relationship in each call relationship data group, generate a call relationship distribution matrix based on the call times of each call relationship, generate an alternative optimized call relationship list for each call relationship data group based on the call relationship distribution matrix and a preset first call times threshold, send the alternative optimized call relationship list to a target object so that the target object can screen and obtain a target optimized call relationship list from the alternative optimized call relationship list, and in response to obtaining the target optimized call relationship list sent by the target object, delete the corresponding call relationship according to the target optimized call relationship list.

[0139] First, by obtaining the call relationship buried point data of the target business system, this application can comprehensively and accurately capture the call relationships between various modules or services in the target business system, providing a reliable data basis for subsequent analysis; by grouping the call relationship buried point data according to the preset call relationship type to obtain multiple call relationship data groups, it can classify and manage according to the characteristics of different call relationships, improving the pertinence and efficiency of call relationship analysis; by calculating the call times of the call relationships in each call relationship data group and generating a call relationship distribution matrix, it can intuitively reflect the distribution and call frequency of the call relationships in the system, providing data support for optimization decisions; generating an alternative optimized call relationship list based on the call relationship distribution matrix and the preset first call times threshold can automatically identify potential inefficient or redundant call relationships, reducing the workload of manual screening; by sending the alternative optimized call relationship list to the target object for screening, it can combine manual judgment and system analysis to ensure the accuracy and rationality of optimization decisions; finally, deleting the corresponding call relationships according to the target optimized call relationship list can effectively optimize the call structure of the business system and improve the management efficiency of the business system call relationships.

[0140] Please refer to Figure 8 , this application embodiment also provides a business system call relationship management device that can implement the above business system call relationship management method. The device includes:

[0141] A buried point data acquisition module, configured to acquire call relationship buried point data from a target business system;

[0142] A data group module, configured to group the call relationship buried point data according to a preset call relationship type to obtain multiple call relationship data groups;

[0143] A distribution matrix module, configured to calculate the number of calls for each call relationship in each call relationship data group, and generate a call relationship distribution matrix based on the number of calls for each call relationship;

[0144] An alternative list module, configured to generate an alternative optimized call relationship list for each call relationship data group based on the call relationship distribution matrix and a preset first call number threshold;

[0145] A target list module, configured to send the alternative optimized call relationship list to a target object, so that the target object can screen and obtain a target optimized call relationship list from the alternative optimized call relationship list;

[0146] A deletion module, configured to, in response to obtaining the target optimized call relationship list sent by the target object, delete the corresponding call relationship according to the target optimized call relationship list.

[0147] The specific implementation manner of the call relationship management device of the service system is basically the same as the specific embodiments of the above-mentioned call relationship management method of the service system, and will not be elaborated herein.

[0148] An embodiment of the present application further provides an electronic device. The electronic device includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the above-mentioned call relationship management method of the service system is implemented. The electronic device can be any intelligent terminal including a tablet computer, an in-vehicle computer, etc.

[0149] Please refer to Figure 9 , Figure 9 which illustrates the hardware structure of an electronic device in another embodiment. The electronic device includes:

[0150] A processor 901, which can be implemented in a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., and is configured to execute relevant programs to implement the technical solutions provided by the embodiments of the present application;

[0151] A memory 902, which can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM), etc. The memory 902 can store an operating system and other application programs. When implementing the technical solutions provided by the embodiments of the present specification through software or firmware, the relevant program codes are stored in the memory 902, and the processor 901 is called to execute the call relationship management method of the service system in the embodiments of the present application;

[0152] An input / output interface 903 for implementing information input and output;

[0153] A communication interface 904 for implementing communication interaction between this device and other devices, which can implement communication through a wired manner (such as USB, network cable, etc.) or through a wireless manner (such as mobile network, WIFI, Bluetooth, etc.);

[0154] A bus 905 for transmitting information between various components of the device (such as a processor 901, a memory 902, an input / output interface 903, and a communication interface 904);

[0155] Among them, the processor 901, the memory 902, the input / output interface 903, and the communication interface 904 achieve communication connections with each other inside the device through the bus 905.

[0156] The embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, it implements the above-mentioned business system call relationship management method.

[0157] As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory can include high-speed random access memory, and can also include non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory optionally includes a memory remotely set relative to the processor, and these remote memories can be connected to the processor through a network. Examples of the above-mentioned network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0158] The business system call relationship management method, device, electronic device, and storage medium proposed in the present application obtain call relationship buried point data from a target business system, group the call relationship buried point data according to a preset call relationship type to obtain multiple call relationship data groups, calculate the call times of each call relationship in each call relationship data group, generate a call relationship distribution matrix based on the call times of each call relationship, for each call relationship data group, generate an alternative optimized call relationship list based on the call relationship distribution matrix and a preset first call times threshold, send the alternative optimized call relationship list to a target object, so that the target object can screen and obtain a target optimized call relationship list from the alternative optimized call relationship list, and in response to obtaining the target optimized call relationship list sent by the target object, delete the corresponding call relationship according to the target optimized call relationship list.

[0159] This application first captures the call relationship buried point data of the target business system, which can comprehensively and accurately capture the call relationships between various modules or services in the target business system, providing a reliable data basis for subsequent analysis. By grouping the call relationship buried point data according to the preset call relationship types, multiple call relationship data groups are obtained, which can be classified and managed according to the characteristics of different call relationships, improving the pertinence and efficiency of call relationship analysis. By calculating the call times of the call relationships in each call relationship data group and generating a call relationship distribution matrix, the distribution and call frequency of the call relationships in the system can be intuitively reflected, providing data support for optimization decisions. Generating an alternative optimized call relationship list based on the call relationship distribution matrix and the preset first call times threshold can automatically identify potential inefficient or redundant call relationships, reducing the workload of manual screening. By sending the alternative optimized call relationship list to the target object for screening, the combination of manual judgment and system analysis can ensure the accuracy and rationality of the optimization decision. Finally, deleting the corresponding call relationships according to the target optimized call relationship list can effectively optimize the call structure of the business system and improve the management efficiency of the call relationships in the business system.

[0160] The embodiments described in the embodiments of this application are for more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those skilled in the art will know that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

[0161] Those skilled in the art can understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than those shown, or combine some steps, or different steps.

[0162] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, that is, they may be located in one place, or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0163] Those of ordinary skill in the art can understand that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, and their appropriate combinations.

[0164] In the description of this application and the above-mentioned accompanying drawings, the terms "first", "second", "third", "fourth", etc. (if any) are used to distinguish similar objects and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that comprises a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0165] It should be understood that in this application, "at least one (item)" means one or more, and "a plurality" means two or more. "And / or" is used to describe the association relationship of associated objects and indicates that three relationships can exist. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist at the same time. Among them, A and B can be singular or plural. The character " / " generally means that the associated objects before and after are in an "or" relationship. "At least one (one) of the following" or its similar expression refers to any combination of these items, including any combination of single item (one) or plural items (ones). For example, at least one (one) of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0166] In several embodiments provided by this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the above-mentioned division of units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of devices or units can be in electrical, mechanical or other forms.

[0167] The units described above as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0168] In addition, in each embodiment of the present application, each functional unit can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0169] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes multiple instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in each embodiment of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store programs.

[0170] The preferred embodiments of the embodiments of the present application have been described above with reference to the accompanying drawings. This does not limit the scope of the rights of the embodiments of the present application. Any modification, equivalent replacement, and improvement made by those skilled in the art without departing from the scope and essence of the embodiments of the present application shall be within the scope of the rights of the embodiments of the present application.

Claims

1. A method for managing business system call relationships, characterized in that: include: Obtain call relationship tracking data from the target business system; Grouping the call relationship tracking data according to preset call relationship types to obtain multiple call relationship data groups; Calculating the number of calls of each call relation in each of the call relation data groups, and generating a call relation distribution matrix according to the number of calls of each of the call relations; For each of the call relationship data groups, generating a candidate optimized call relationship list based on the call relationship distribution matrix and a preset first call number threshold; Sending the candidate optimization call relationship list to a target object, so that the target object can filter the candidate optimization call relationship list to obtain a target optimization call relationship list; In response to obtaining the target optimized call relationship list sent by the target object, the corresponding call relationship is deleted according to the target optimized call relationship list.

2. The method for managing business system call relationships according to claim 1, characterized in that: For each of the call relationship data groups, generating a candidate optimized call relationship list based on the call relationship distribution matrix and a preset first call number threshold includes: For each of the call relationship data groups, obtaining call relationship distribution matrix data within a preset time window; For each call relationship in the call relationship distribution matrix, calculating the total number of calls within the preset time window; The total number of calls is compared with the first call number threshold, and if the total number of calls is less than the first call number threshold, the call relationship is added to the candidate optimization call relationship list.

3. The method for managing business system call relationships according to claim 1, characterized in that: The method further comprises: For each of the call relationship data groups, generating a failed call relationship list based on the call relationship distribution matrix and a preset second call number threshold; wherein the second call number threshold is lower than the first call number threshold; Sending the invalid call relationship list to the target object; If no feedback is received from the target object within the preset waiting time, a deletion operation is performed on the call relationship in the invalid call relationship list.

4. The method for managing business system call relationships according to claim 1, characterized in that: The method further comprises: Calculating the call count change rate of each call relationship in the call relationship distribution matrix in adjacent time windows; In response to detecting that a call number change rate of a call relationship having a call relationship exceeds a preset change rate threshold, and the call number change rate is in a downward trend, the call relationship is added to the candidate optimization call relationship list.

5. The method for managing business system call relationships according to claim 1, characterized in that: In response to obtaining the target optimized call relationship list sent by the target object, deleting the corresponding call relationship according to the target optimized call relationship list, including: Determine the optimization operation type of each call relationship in the target optimization call relationship list; wherein the optimization operation type includes an immediate deletion type and a planned deletion type; For the call relationship of the immediate deletion type, directly execute the deletion operation; For the call relationship of the planned deletion type, a preset system off-peak period is obtained, and the deletion operation is performed within the system off-peak period; The system operation status after the deletion operation is executed is monitored, and if a system abnormality is detected, the deleted call relationship is restored.

6. The method for managing business system call relationships according to claim 1, characterized in that: The calling relationship tracking data is grouped according to the preset calling relationship type to obtain multiple calling relationship data groups, including: Parse the caller ID and callee ID in each call relationship tracking data; Determine the call relationship type to which each call relationship belongs according to the caller identifier and the callee identifier; wherein the preset call relationship types include direct call between systems, message queue call, database call and external interface call; The call relationship tracking data with the same call relationship type are divided into the same call relationship data group to obtain multiple call relationship data groups.

7. The method for managing business system call relationships according to claim 1, characterized in that: After deleting the corresponding call relationship according to the target optimized call relationship list, the method further includes: Generate a call relationship deletion operation log; wherein the call relationship deletion operation log includes the deleted call relationship identifier, deletion time, deletion reason and corresponding target object identifier; Sending the call relationship deletion operation log to the target operation and maintenance object through a preset notification method; Within a preset monitoring period, obtaining system performance indicators of the caller and the callee involved in the deleted call relationship; If the system performance indicator is lower than the preset performance threshold, an alarm message is sent to the preset operation and maintenance personnel.

8. A business system call relationship management device, characterized in that: include: The tracking data acquisition module is used to obtain the call relationship tracking data from the target business system; A data group module, used for grouping the call relationship tracking data according to a preset call relationship type to obtain a plurality of call relationship data groups; A distribution matrix module, used for calculating the call times of each call relation in each call relation data group, and generating a call relation distribution matrix according to the call times of each call relation; An alternative list module, for generating, for each of the call relationship data groups, an alternative optimized call relationship list based on the call relationship distribution matrix and a preset first call number threshold; A target list module, used for sending the candidate optimization call relationship list to the target object, so that the target object can filter the candidate optimization call relationship list to obtain the target optimization call relationship list; The deleting module is used to delete the corresponding calling relationship according to the target optimized calling relationship list in response to obtaining the target optimized calling relationship list sent by the target object.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the method for managing the business system call relationship according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The storage medium stores a program, and the program is executed by a processor to implement the business system call relationship management method as described in any one of claims 1 to 7.

Images