Business system calling relation construction method and device, equipment and storage medium

Abstract

The invention relates to the technical field of financial science and technology, in particular to a business system calling relation construction method and device, equipment and a storage medium, and the method comprises the steps: obtaining the identification information of two calling parties sent by a client integrated in a called party business system; constructing a business system calling relation graph based on the identification information of the two calling parties; or acquiring a calling application sent by the calling party service system; generating identification information of both calling parties based on the calling application and a called party identifier of a called party service system; and sending the identification information of the two calling parties to a monitor, so that the monitor constructs a business system calling relation graph based on the identification information of the two calling parties. The method is convenient for improving the security of calling the relation graph construction mode.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and in particular to a method, device, equipment and storage medium for establishing a business system call relationship. Background Art

[0002] With the rapid development of information technology, the business processing capabilities of enterprises have been greatly improved. For example, when a bank executes a certain business process, it can call multiple business systems to implement the business process. There are corresponding call links between the business systems. In order to facilitate the monitoring of the execution process of the business process, it is necessary to monitor the call links between the business systems and obtain the corresponding call relationship diagram.

[0003] Currently, one approach to building a call relationship graph is to integrate Zipkin, a link tracking system developed based on Google Dapper's tracking system, into the business process code. During the execution of the business process, Zipkin intercepts call requests between business systems related to the business process, and forms corresponding call relationship information based on the obtained call requests. The call relationship information is then sent to the preset collector, and the call relationship information stored in the collector is further spliced ​​in real time to obtain a call relationship graph.

[0004] However, the link tracking system Zipkin needs to be integrated into the business process code when in use, which means that the link tracking system Zipkin is invasive and cannot be completely decoupled from the business process, resulting in the current method of building a call relationship graph with low security. Summary of the invention

[0005] In order to facilitate improving the security of the call relationship graph construction method, the present application provides a business system call relationship construction method, device, equipment and storage medium.

[0006] In a first aspect, the present application provides a method for constructing a business system call relationship, comprising:

[0007] Obtain the identification information of the calling party and the calling party sent by the client integrated in the called party's business system;

[0008] A business system call relationship graph is constructed based on the identification information of the calling parties.

[0009] Through the above implementation, since the client used in this application is not integrated in the business process code but in each business system, this can avoid the intrusion of the link tracking system into the business process code and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0010] Preferably, the step of the client obtaining the identification information of the calling parties includes:

[0011] Obtaining a call application sent by the caller business system to the called business system;

[0012] Obtaining a caller identifier of a caller business system based on the call application;

[0013] The identification information of both calling parties is obtained based on the calling party identification and the called party identification of the called party business system.

[0014] Through the above implementation, it is convenient to subsequently construct a business system call relationship diagram based on the identification information of both parties.

[0015] Preferably, the business system call relationship construction method further includes:

[0016] Acquire the operation information sent by the client integrated in the called party's business system;

[0017] In response to the built-in analysis model determining that the operating information is abnormal, an abnormal alarm message is issued.

[0018] Through the above implementation, when the corresponding called party business system is judged to be abnormal through operation information, early warning information is issued in time, which is convenient for improving the operation stability of the business system.

[0019] In a second aspect, the present application provides a method for constructing a business system call relationship, comprising:

[0020] Get the call request sent by the caller's business system;

[0021] Generate identification information of both parties of the call based on the call application and the called party identification of the called party business system;

[0022] The identification information of the calling parties is sent to the monitor, so that the monitor builds a business system call relationship graph based on the identification information of the calling parties.

[0023] Through the above implementation, since the client used in this application is not integrated in the business process code but in each business system, this can avoid the intrusion of the link tracking system into the business process code and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0024] Preferably, the business system call relationship construction method further includes:

[0025] Obtaining the operation information of the called party's business system;

[0026] The operation information is sent to the monitor, so that the monitor issues an abnormality alarm message when determining that the operation information is abnormal.

[0027] Through the above implementation, when the corresponding called party business system is judged to be abnormal through operation information, early warning information is issued in time, which is convenient for improving the operation stability of the business system.

[0028] In a third aspect, the present application provides a business system call relationship construction device, comprising:

[0029] An information acquisition module is used to obtain the identification information of the calling party and the calling party sent by the client integrated in the business system of the called party;

[0030] The relationship building module is used to build a business system call relationship diagram based on the identification information of the calling parties.

[0031] Through the above implementation, since the client used in this application is not integrated in the business process code but in each business system, this can avoid the intrusion of the link tracking system into the business process code and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0032] In a fourth aspect, the present application provides a business system call relationship construction device, comprising:

[0033] The application acquisition module is used to obtain the call application sent by the caller's business system;

[0034] An information generation module, used to generate identification information of both parties of the call based on the call application and the called party identification of the called party business system;

[0035] The information sending module is used to send the identification information of the calling parties to the monitor, so that the monitor builds a business system call relationship diagram based on the identification information of the calling parties.

[0036] Through the above implementation, since the client used in this application is not integrated in the business process code but in each business system, this can avoid the intrusion of the link tracking system into the business process code and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0037] In a fifth aspect, the present application provides a computer device, the computer device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the steps in the above method when executing the computer program.

[0038] In a sixth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the steps in the above method when executed by a processor.

[0039] In a seventh aspect, the present application further provides a computer program product, wherein the computer program product comprises a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.

[0040] The above-mentioned business system call relationship construction method, device, equipment and storage medium obtain the identification information of the calling parties sent by the client integrated in the called party's business system; and construct the business system call relationship graph based on the identification information of the calling parties. Alternatively, obtain the call application sent by the caller's business system; generate the identification information of the calling parties based on the call application and the called party identification of the called party's business system; and send the identification information of the calling parties to the monitor so that the monitor constructs the business system call relationship graph based on the identification information of the calling parties. Through the above implementation, since the client used in this application is not integrated in the business process code, but integrated in each business system, this can avoid the intrusiveness of the link tracking system to the business process code, and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0041] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0043] Figure 1 A flow chart of a method for constructing a business system call relationship provided in an embodiment of the present application;

[0044] Figure 2 A schematic diagram of a business system call relationship diagram provided in an embodiment of the present application;

[0045] Figure 3 A flowchart of another method for constructing a business system call relationship provided in an embodiment of the present application;

[0046] Figure 4A schematic diagram of the structure of a business system call relationship building device provided in an embodiment of the present application;

[0047] Figure 5 A schematic diagram of the structure of another device for building a service system call relationship provided in an embodiment of the present application;

[0048] Figure 6 A schematic diagram of the structure of a computer device provided in an embodiment of the present application;

[0049] Figure 7 This is a diagram of the internal structure of a computer-readable storage medium provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not used to limit the present disclosure.

[0051] It should be noted that the terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0052] In this article, the term "and / or" is only a description of the association relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the related objects before and after are in an "or" relationship.

[0053] Embodiment 1

[0054] Figure 1 A flowchart of a method for constructing a business system call relationship provided in Example 1 of the present application, refer to Figure 1 The method may be performed by a device for performing the method, and the device may be implemented by software and / or hardware. The method includes:

[0055] S110: Obtain identification information of both parties of the call sent by the client integrated in the business system of the called party.

[0056] It should be noted that the operation of bank-related business processes often requires the invocation of multiple different business systems, and a business system often calls one or more other business systems during operation; for example, refer to Figure 2 Suppose that the operation of a bank-related business process requires 5 different business systems: service1, service2, service3, service4 and service5; among them, service3 is the first business system called, and service3 calls service4 and service5 respectively during the operation process, service4 calls service2 during the operation process, service2 calls service1 during the operation process, and service2 calls service1 during the operation process.

[0057] Among them, each business system that initiates the call may also be the called business system. In order to facilitate the solution of the problem that the existing link tracking system is invasive to the business process code, this embodiment creatively integrates a client in each business system, and the client is used to track the call information of one business system to another business system. In this embodiment, the client can be integrated into the corresponding business system in a plug-in manner through Java agent and other methods; if one business system calls another business system, the system that initiates the call is the caller business system, and the called business system is the called business system; the client integrated in the called business system is used to generate call information of the caller business system to the called business system after the caller business system initiates a call to the called business system, and the calling party identification information is also the call information generated by the client, and the calling party identification information is used to indicate and form the calling business system and the called business system; after the client integrated in the called business system generates the calling party identification information, it further sends the calling party identification information to the monitor, and the monitor is also Figure 2 The moniter in the system is used to obtain the identification information of the calling parties sent by the clients integrated in the business systems of the called parties.

[0058] Specifically, after the calling business system initiates a call to the called business system, the client integrated in the called business system generates identification information of the calling parties, and further sends the identification information of the calling parties to the monitor moniter. Then, the monitor moniter obtains the identification information of the calling parties sent by the client integrated in the called business system.

[0059] S120: Construct a business system call relationship diagram based on the identification information of the calling parties.

[0060] Among them, since the calling party identification information can indicate and form the calling party business system and the called party business system, the monitor can sequentially combine the calling party identification information after obtaining multiple calling party identification information, thereby forming the following Figure 2 The call chain diagram shown in the embodiment is recorded as a business system call relationship diagram. The monitor moniter can sequentially combine the calling party identification information sent by the client integrated in each called party business system to construct the business system call relationship diagram.

[0061] Specifically, the monitor sequentially combines the calling party identification information sent by the client integrated in each called party business system, thereby constructing a call relationship graph of the business system.

[0062] It should be noted that in this embodiment, since the client used in this application is not integrated in the business process code, but is integrated in each business system, this can avoid the intrusion of the link tracking system into the business process code and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0063] Embodiment 2

[0064] A method for establishing a business system call relationship is provided in Embodiment 2 of the present application. The method refines the "step of the client obtaining the identification information of the calling parties" in Embodiment 1. It should be noted that for the parts not described in detail in this embodiment, reference can be made to the descriptions of other embodiments. The method includes:

[0065] S210: Obtain identification information of both parties of the call sent by the client integrated in the business system of the called party.

[0066] The step of the client obtaining the identification information of the calling parties includes:

[0067] A110. Obtain a calling application sent by the calling business system to the called business system.

[0068] Among them, the call application is sent by the caller business system to the called party business system to be called, and the call application is used to represent the caller business system's application to call the corresponding called party business system; in this embodiment, in order to facilitate the subsequent tracking of the call relationship between the caller business system and the called party business system, a caller identifier is set for the caller business system, and the call application sent by the caller business system to the called party business system contains the caller identifier.

[0069] Specifically, when the calling business system initiates a call to the called business system, it sends a call application including the caller identifier to the called business system; the client integrated in the called business system obtains the call application including the caller identifier.

[0070] A120. Obtain a caller identifier of the caller business system based on the call application.

[0071] The client integrated in the called party's business system can obtain the caller identifier in the call application by parsing the obtained call application.

[0072] Specifically, the client integrated in the called party's business system parses the acquired call application to obtain the caller identifier in the call application.

[0073] A130. Obtain identification information of both calling parties based on the calling party identification and the called party identification of the called party business system.

[0074] Among them, in order to facilitate the subsequent tracking of the calling relationship between the caller business system and the called party business system, a called party identifier is also set for the called party business system, and the client can obtain the called party identifier of the called party business system integrated with the client; the calling party identification information includes the caller identifier of the caller business system and the called party identifier of the called party business system, and the calling party identification information is generated by the client.

[0075] Specifically, the client in the called party business system obtains the caller identification of the caller business system and the called party identification of the called party business system, and combines the caller identification of the caller business system and the called party identification of the called party business system to obtain identification information of both calling parties.

[0076] S220: Construct a business system call relationship diagram based on the identification information of the calling parties.

[0077] It should be noted that by generating identification information of both callers, and after the subsequent monitor obtains multiple identification information of both callers, a corresponding business system call relationship graph is constructed according to the multiple identification information of both callers.

[0078] Embodiment 3

[0079] A method for constructing a business system call relationship is provided in Embodiment 3 of the present application. The method supplements the method described in Embodiment 1. It should be noted that, for the parts not described in detail in this embodiment, reference may be made to the descriptions of other embodiments. The method includes:

[0080] S310: Obtain identification information of both parties of the call sent by the client integrated in the business system of the called party.

[0081] S320: Construct a business system call relationship diagram based on the identification information of the calling parties.

[0082] S330: Acquire the operation information sent by the client integrated in the called party's business system.

[0083] Among them, the operation information is the status information of the caller's business system during the process of being called and run by the called party's business system; in this embodiment, the operation information includes call response time, CPU usage rate and memory usage rate. In other embodiments, there is no specific limitation; the operation information is obtained by the client integrated in the called party's business system to monitor the called party's business system.

[0084] Specifically, after the calling business system sends a call request to the called business system, if the called business system responds to the call request, the client further monitors the call response time, CPU usage and memory usage of the called business system to obtain the operation information of the called business system.

[0085] S340: In response to the built-in analysis model determining that the operation information is abnormal, an abnormal alarm message is issued.

[0086] Among them, the built-in analysis model is built into the monitor, and the built-in analysis model is used to judge various operating information, so as to determine whether the corresponding operating information is abnormal; in this embodiment, the built-in analysis model is a model constructed based on the normal distribution 3σ law, or a regression model. In other embodiments, it is not specifically limited. Exemplarily, if the CPU usage threshold range defined by the built-in analysis model is the CPU usage mean ± 3 times the CPU usage standard deviation, if it is determined that the built-in analysis model analyzes that the CPU usage exceeds the usage threshold range, the controller will be further linked to send an abnormal alarm message to the corresponding staff.

[0087] Specifically, the monitor obtains the operation information sent by the client, and the built-in analysis model in the monitor determines whether the operation information is abnormal. If it is determined that the operation information is abnormal, the linkage controller sends an abnormal alarm message to the corresponding staff.

[0088] It should be noted that when the built-in analysis model determines that the operating information is abnormal, it immediately links the controller to send abnormal alarm information to the corresponding staff, so as to quickly locate the called business system with problems, and facilitate the staff to suspend the called business system with problems in time, thereby ensuring the operating stability of the called business system.

[0089] Embodiment 4

[0090] Figure 3 A flowchart of a method for constructing a business system call relationship provided in Example 1 of the present application, refer to Figure 3 The method may be performed by a device for performing the method, and the device may be implemented by software and / or hardware. The method includes:

[0091] S410: Obtain a call request sent by the caller's business system.

[0092] When calling a corresponding called party business system, the calling party business system will send a calling request to the corresponding called party business system; the client integrated in the called party business system will obtain the calling request.

[0093] Specifically, after the calling business system sends a calling application to the corresponding called business system, the client integrated in the called business system obtains the calling application.

[0094] S420: Generate calling party identification information based on the calling application and the called party identification of the called party business system.

[0095] Among them, the calling application includes the caller identifier of the calling business system. The client can parse the calling application it obtains to obtain the caller identifier of the calling business system in the calling application; the client can also obtain the callee identifier of the called business system integrated with the client; the calling party identification information includes the caller identifier and the called party identifier; the client can combine the obtained caller identifier and the called party identifier to generate the calling party identification information.

[0096] Specifically, the client parses the obtained call application to obtain the caller identifier of the caller business system; the client also obtains the callee identifier of the callee business system; further, the client combines the obtained caller identifier and the callee identifier to generate identifier information of both callers.

[0097] S430: Send the identification information of the calling parties to a monitor, so that the monitor constructs a business system call relationship graph based on the identification information of the calling parties.

[0098] Among them, after the client generates the identification information of the calling parties, it is further necessary to send the identification information of the calling parties to the monitor in the called business system, so that the monitor can build a business system call relationship graph based on the identification information of the calling parties; wherein, the specific steps of the monitor building the business system call relationship graph based on the identification information of the calling parties can be referred to step S120 in Example 1, which will not be repeated here.

[0099] Specifically, the client sends the identification information of the calling parties to the monitor in the called business system, so that the monitor constructs a business system call relationship graph based on the identification information of the calling parties.

[0100] It should be noted that in this embodiment, since the client used in this application is not integrated in the business process code, but is integrated in each business system, this can avoid the intrusion of the link tracking system into the business process code and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0101] Embodiment 5

[0102] A method for constructing a business system call relationship is provided in Embodiment 5 of the present application. The method supplements the method described in Embodiment 4. It should be noted that for the parts not described in detail in this embodiment, reference may be made to the descriptions of other embodiments. The method includes:

[0103] S510: Obtain a call request sent by the caller's business system.

[0104] S520: Generate calling party identification information based on the calling application and the called party identification of the called party business system.

[0105] S530: Send the identification information of the calling parties to a monitor, so that the monitor constructs a business system call relationship graph based on the identification information of the calling parties.

[0106] S540: Obtain operation information of the called party's business system.

[0107] Among them, the operation information is the status information of the caller's business system during the process of being called and run by the called party's business system; in this embodiment, the operation information includes call response time, CPU usage rate and memory usage rate. In other embodiments, there is no specific limitation; the operation information is obtained by the client integrated in the called party's business system to monitor the called party's business system.

[0108] Specifically, after the calling business system sends a call request to the called business system, if the called business system responds to the call request, the client further monitors the call response time, CPU usage and memory usage of the called business system to obtain the operation information of the called business system.

[0109] S550: Send the operation information to the monitor, so that the monitor issues an abnormality alarm message when determining that the operation information is abnormal.

[0110] Among them, the built-in analysis model is built into the monitor, and the built-in analysis model is used to judge various operating information, so as to determine whether the corresponding operating information is abnormal; in this embodiment, the built-in analysis model is a model constructed based on the normal distribution 3σ law, or a regression model. In other embodiments, it is not specifically limited. Exemplarily, if the CPU usage threshold range defined by the built-in analysis model is the CPU usage mean ± 3 times the CPU usage standard deviation, if it is determined that the built-in analysis model analyzes that the CPU usage exceeds the usage threshold range, the controller will be further linked to send an abnormal alarm message to the corresponding staff.

[0111] Specifically, the client sends the operation information to the monitor. After the monitor obtains the operation information sent by the client, the built-in analysis model in the monitor determines whether the operation information is abnormal. If the operation information is determined to be abnormal, the linkage controller sends an abnormal alarm message to the corresponding staff.

[0112] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0113] Embodiment 6

[0114] Based on the same inventive concept, this embodiment also provides a business system call relationship construction device for implementing the business system call relationship construction method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more business system call relationship construction device embodiments provided below can refer to the limitations of the business system call relationship construction method above, and will not be repeated here.

[0115] In this embodiment, Figure 4 As shown, a business system call relationship construction device is provided, comprising:

[0116] An information acquisition module is used to obtain the identification information of the calling party and the calling party sent by the client integrated in the business system of the called party;

[0117] The relationship building module is used to build a business system call relationship diagram based on the identification information of the calling parties.

[0118] Each module in the above-mentioned business system call relationship construction device can be implemented in whole or in part by software, hardware and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.

[0119] It should be noted that in this embodiment, since the client used in this application is not integrated in the business process code, but is integrated in each business system, this can avoid the intrusion of the link tracking system into the business process code and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0120] In an optional embodiment, in terms of the client acquiring the identification information of the calling parties, the information acquisition module is specifically used to:

[0121] Obtaining a call application sent by the caller business system to the called business system;

[0122] Obtaining a caller identifier of a caller business system based on the call application;

[0123] The identification information of both calling parties is obtained based on the calling party identification and the called party identification of the called party business system.

[0124] In an optional embodiment, the business system call relationship building device further includes:

[0125] An operation information acquisition module, used to acquire the operation information sent by the client integrated in the called party's business system;

[0126] The alarm issuing module is used to issue abnormal alarm information in response to the built-in analysis model judging that the operation information is abnormal.

[0127] Embodiment 7

[0128] Based on the same inventive concept, this embodiment also provides a business system call relationship construction device for implementing the business system call relationship construction method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more business system call relationship construction device embodiments provided below can refer to the limitations of the business system call relationship construction method above, and will not be repeated here.

[0129] In this embodiment, Figure 5As shown, a business system call relationship construction device is provided, comprising:

[0130] The application acquisition module is used to obtain the call application sent by the caller's business system;

[0131] An information generation module, used to generate identification information of both parties of the call based on the call application and the called party identification of the called party business system;

[0132] The information sending module is used to send the identification information of the calling parties to the monitor, so that the monitor builds a business system call relationship diagram based on the identification information of the calling parties.

[0133] Each module in the above-mentioned business system call relationship construction device can be implemented in whole or in part by software, hardware and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.

[0134] It should be noted that in this embodiment, since the client used in this application is not integrated in the business process code, but is integrated in each business system, this can avoid the intrusion of the link tracking system into the business process code and achieve complete decoupling between the link tracking system and the business process, thereby facilitating the improvement of the security of the call relationship graph construction method.

[0135] In an optional embodiment, the business system call relationship building device further includes:

[0136] A system information acquisition module, used to acquire the operation information of the called party's business system;

[0137] The system information sending module is used to send the operation information to the monitor, so that the monitor can send abnormal alarm information when it is determined that the operation information is abnormal.

[0138] Embodiment 8

[0139] In this embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 6As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for building a business system call relationship is implemented.

[0140] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the scheme of the present disclosure, and does not constitute a limitation on the computer device to which the scheme of the present disclosure is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0141] Embodiment 9

[0142] In this embodiment, a computer readable storage medium is provided. Figure 7 As shown, a computer program is stored thereon, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0143] Embodiment 10

[0144] In this embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0145] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0146] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided by the present disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided by the present disclosure may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited thereto. The processor involved in each embodiment provided by the present disclosure may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited thereto.

[0147] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0148] The above-described embodiments only express several implementation methods of the present disclosure, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present invention. It should be pointed out that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present disclosure, and these all belong to the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the attached claims.

Claims

1. A method for constructing a business system call relationship, characterized in that: include: Obtain the calling party identification information sent by the client integrated in the called party's business system; A business system call relationship graph is constructed based on the identification information of the calling parties.

2. The method according to claim 1, characterized in that The step of the client obtaining the identification information of the calling parties includes: Obtaining a call application sent by the caller business system to the called business system; Obtaining a caller identifier of a caller business system based on the call application; The identification information of both calling parties is obtained based on the calling party identification and the called party identification of the called party business system.

3. The method according to claim 1, characterized in that Also includes: Acquire the operation information sent by the client integrated in the called party's business system; In response to the built-in analysis model determining that the operating information is abnormal, an abnormal alarm message is issued.

4. A method for constructing a business system call relationship, characterized in that: include: Get the call request sent by the caller's business system; Generate identification information of both parties of the call based on the call application and the called party identification of the called party business system; The identification information of the calling parties is sent to the monitor, so that the monitor builds a business system call relationship graph based on the identification information of the calling parties.

5. The method according to claim 4, characterized in that Also includes: Obtaining the operation information of the called party's business system; The operation information is sent to the monitor, so that the monitor issues an abnormality alarm message when determining that the operation information is abnormal.

6. A business system call relationship construction device, characterized in that: The device comprises: An information acquisition module is used to obtain the identification information of the calling party and the calling party sent by the client integrated in the business system of the called party; The relationship building module is used to build a business system call relationship diagram based on the identification information of the calling parties.

7. A business system call relationship building device, characterized in that: The device comprises: The application acquisition module is used to obtain the call application sent by the caller's business system; An information generation module, used to generate identification information of both parties of the call based on the call application and the called party identification of the called party business system; The information sending module is used to send the identification information of the calling parties to the monitor, so that the monitor builds a business system call relationship diagram based on the identification information of the calling parties.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 3 or 4 to 5 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 3 or 4 to 5 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 3 or 4 to 5 are implemented.

Images