Service call chain identification method and device

By analyzing the correlation coefficients of service call volume, duration, and success rate, and combining them with the application system sequence, the system automatically identifies cross-system service call chains, solving the problem of the inability to accurately obtain global call chains in existing technologies, and achieving efficient and accurate construction of global service call chains.

CN116846942BActive Publication Date: 2026-11-17CHINA MOBILE INFORMATION TECHNOLOGY CO LTD +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210305353.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-03-25
Publication Date
2026-11-17
Estimated Expiration
2042-03-25

AI Technical Summary

Technical Problem

Existing technologies struggle to automatically identify global service call chains across systems, especially in complex microservice architectures. They cannot accurately obtain call relationships at the individual service level, and existing methods place high demands on system performance and operational workload.

Method used

By collecting network mirror traffic data of the target global service, and using correlation coefficients to analyze call volume, total call duration, or successful call volume, the call relationship between services is automatically identified, and a global service call chain is constructed according to the application system sequence.

Benefits of technology

It achieves automated identification of global service call chains across systems, with high accuracy and real-time performance, without affecting the performance of existing systems, and is suitable for complex heterogeneous systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116846942B_ABST
    Figure CN116846942B_ABST
Patent Text Reader

Abstract

This application provides a service call chain identification method and apparatus, relating to the field of IT application technology. The method includes: determining whether a call relationship exists between any two services based on target data for each service in a target global service; determining the call order between the two services based on the application systems to which they belong; and determining the service call chain based on the call order. The target data includes at least one of the following: call volume, total call duration, or call success rate. The service call chain identification method and apparatus provided in this application, by acquiring call volume, total call duration, or call success rate data for all services, determining whether a call relationship exists between any two services, and determining the call relationship between services based on the systems to which they belong, achieves automated construction of a complete cross-system global service call chain.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of IT application technology, specifically to a service call chain identification method and apparatus. Background Technology

[0002] Completing a complex transaction often involves cross-system service calls. In the evolution of IT architecture, from Service-Oriented Architecture (SOA) providing heterogeneous system calls through Enterprise Service Bus (OSS), to modern IT application architectures, services are provided through distributed microservice clusters to achieve reusability and scalability. As business grows, these service call chains become increasingly complex, making manual analysis extremely difficult or even impossible. However, clearly defined service call chains are extremely valuable for fault location and diagnosis, and for optimizing service call relationships. Therefore, implementing automatic service call chain identification technology is crucial. Existing automatic identification technologies are as follows:

[0003] 1. By developing tracking points and outputting log data, a unique call trace identifier is added to each call stage. This allows for the reconstruction of the service call chain for each transaction through the trace identifiers in the transaction records. This approach has high requirements for service development standards, increases development workload, and can impact the performance of online services. It also involves significant work in modifying existing application services.

[0004] 2. By installing an agent on the service nodes, TCP connection data can be obtained to understand the network access relationships between nodes, and then the system-level service call relationships can be depicted. Installing an agent on the service nodes increases the workload of operations and maintenance, and can easily lead to cross-influence with the monitored services. Furthermore, this method can only obtain the call chain between nodes, not the call chain between specific services.

[0005] Existing technologies for automatically identifying global service call chains either rely on the application service's own output or can only obtain coarse-grained node call relationships, failing to complete the global call chain relationship at the level of a single service. Summary of the Invention

[0006] This application provides a service call chain identification method and apparatus to solve the technical problem of how to identify service call chains.

[0007] In a first aspect, embodiments of this application provide a service call chain identification method, including:

[0008] Based on the target data of each service in the target global service, determine whether there is a call relationship between any two services;

[0009] The order of calls between the two services with a call relationship is determined based on the application system to which they belong.

[0010] Determine the service call chain based on the call order;

[0011] The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

[0012] In one embodiment, determining whether a call relationship exists between any two services based on the target data of each service in the target global service includes:

[0013] Determine the correlation between any two services based on the target data of each service in the target global service;

[0014] Based on the correlation, determine whether there is a call relationship between any two services.

[0015] In one embodiment, determining the calling order between two services with a calling relationship based on the application systems to which they belong includes:

[0016] If two services with a calling relationship belong to different application systems, the calling order between the two services with a calling relationship is determined according to the preset application system order.

[0017] In one embodiment, the method for determining the calling order between two services with a calling relationship based on the application systems to which they belong further includes:

[0018] If two services with a calling relationship belong to the same application system, the calling order between the two services with a calling relationship is determined based on the call volume of the two services with a calling relationship within the target time period.

[0019] In one embodiment, before determining whether a call relationship exists between any two services based on the target data of each service in the target global service, the method further includes:

[0020] Based on the service identifier and call parameters of each service within the target period, the target data of each service is merged.

[0021] In one embodiment, the target data is determined in the following manner:

[0022] Collect network mirror traffic data of the links to be identified in the target global service;

[0023] The network mirror traffic data is parsed to determine the target data.

[0024] In one embodiment, after determining the service call chain, the method further includes:

[0025] Based on the service call chain, identify the preceding and / or following services of the service to be queried.

[0026] Secondly, embodiments of this application provide a service call chain identification device, comprising:

[0027] The first determining module is used to determine whether there is a call relationship between any two services based on the target data of each service in the target global service;

[0028] The second determining module is used to determine the calling order between the two services that have a calling relationship, based on the application system to which they belong.

[0029] The third determining module is used to determine the service call chain based on the call order;

[0030] The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

[0031] Thirdly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the computer program to implement the steps of the service call chain identification method described in the first aspect.

[0032] Fourthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the service call chain identification method described in the first aspect.

[0033] The service call chain identification method and apparatus provided in this application realize the automated construction of a complete cross-system global service call chain by obtaining the call volume, total call duration or call success rate data of all services, determining whether there is a call relationship between any two services, and determining the call relationship between services according to the system to which the services belong. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 This is one of the flowcharts illustrating the service call chain identification method provided in the embodiments of this application;

[0036] Figure 2 This is a second flowchart illustrating the service call chain identification method provided in this application embodiment;

[0037] Figure 3 This is a schematic diagram of the service call chain identification device provided in the embodiments of this application;

[0038] Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0040] Figure 1 This is one of the flowcharts illustrating the service call chain identification method provided in this application. (Refer to...) Figure 1 This application provides a service call chain identification method, which may include:

[0041] Step 110: Based on the target data of each service in the target global service, determine whether there is a call relationship between any two services;

[0042] Step 120: Determine the calling order between the two services that have a calling relationship, based on the application systems to which they belong;

[0043] Step 130: Determine the service call chain based on the call order;

[0044] The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

[0045] It should be noted that the execution subject of the service call chain identification method provided in this application embodiment can be an electronic device, a component in an electronic device, an integrated circuit, or a chip. The electronic device can be a mobile electronic device or a non-mobile electronic device. For example, a mobile electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc., while a non-mobile electronic device can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc., and this application does not make specific limitations.

[0046] A cross-system global service call chain refers to the service call chain between multiple heterogeneous systems required to complete a globally complete business transaction. Service call technologies include Enterprise Service Bus (ESB) in SOA architecture, microservice API gateway pattern, RPC calls, and intermediate message queue methods.

[0047] In step 110, based on the target data of each service in the target global service, it is determined whether there is a call relationship between any two services.

[0048] Collect target data for each service in the target global service, as shown in Table 1, where each row of data represents the target data for one service.

[0049] Target data may include: call volume, total call duration, number of successful calls, start time, end time, application system, service identifier, or call parameters, etc.

[0050] Table 1 Summary of Target Data

[0051]

[0052] The start and end times are used to determine the data statistics period for service calls. The principles for selecting this period are: 1) Services on the cross-system global service call chain must provide the same time statistics period data, such as all choosing 1 minute; 2) Ensure that there are service call volumes for each selected data period. The application system refers to the application system to which the service belongs. It is mainly used to set the call order, and can also be used for final external queries and to provide a directory for the service.

[0053] The service identifier can be an already mapped, readable name, or the original RESTful API path of the service interface obtained through parsing; the content of the call parameters is the key-value pair parameters used to distinguish all services with the same identifier; the call count refers to the total number of calls within the service period, including both successful and failed calls; the total call duration is the sum of the duration of a single service within the statistical period; the number of successful calls refers to the total number of successful calls within the service period.

[0054] By performing correlation analysis on the call volume, total call duration, or successful call volume of any two services in the global service, it can be determined whether there is a call relationship between any two services in the global service, and the two services with a call relationship can be filtered out.

[0055] In step 120, the calling order between the two services with a calling relationship is determined based on the application system to which they belong.

[0056] For any two services that have a calling relationship, the calling order between the two services is determined according to the application system to which the two services belong, and the order of the application system, i.e., which service calls which service.

[0057] In step 130, the service call chain is determined according to the call order.

[0058] Once the call order of all two services with a call relationship is determined, the complete service call chain in the global service can be identified.

[0059] The service call chain identification method provided in this application obtains the call volume, total call duration or call success rate of all services, determines whether there is a call relationship between any two services, and determines the call relationship between services based on the system to which the services belong, thereby realizing the automated construction of a complete cross-system global service call chain.

[0060] In one embodiment, determining whether a call relationship exists between any two services based on the target data of each service in the target global service includes:

[0061] Determine the correlation between any two services based on the target data of each service in the target global service;

[0062] Based on the correlation, determine whether there is a call relationship between any two services.

[0063] In probability theory and statistics, correlation can show the strength and direction of the linear relationship between two or more random variables. The correlation coefficient is typically used to describe correlation, with values ​​ranging from -1 to 1, where -1 represents a perfect negative correlation, 1 represents a perfect positive correlation, and 0 represents no correlation.

[0064] Independent variable: A variable that changes actively and belongs to the preceding service in the service call chain;

[0065] Dependent variable: A variable that changes passively and belongs to a subsequent service in the service call chain.

[0066] Optionally, the correlation between any two services can be determined based on the call volume, total call duration, or successful call volume of each service within the target period. The greater the correlation, the greater the probability that there is a call relationship between the two services.

[0067] For example, using service call volume as an example, we can determine the correlation between any two services. Table 2 is a statistical table of call volume data for three services. Referring to the data in Table 2, we can determine the correlation between any two services. The specific calculation process is as follows:

[0068] Table 2. Statistics on Call Volume

[0069]

[0070]

[0071] Table 2 contains 15 records, denoted as n=15. The formula for calculating the correlation coefficient is as follows:

[0072]

[0073] Where r is the correlation coefficient; i = 1, 2, 3, ..., n; x i This represents the number of calls to the i-th service x. y represents the average call volume of n services x; i This represents the number of calls to the i-th service y; This represents the average number of calls to n services y.

[0074] For example, in Table 2, the correlation coefficient between service x and service y is calculated, where the average call volume of service x is the 15 records. The average call volume for the 15 services is 419.27. The value is 820.53. According to the formula, for each row, the x-value is... The difference, and the y-value of each row. Multiply the differences and sum them, then divide by the x-value of each row. The sum of squares of the differences and the y-values ​​of each row The square root of the product of the sum of the squares of the differences is then used with the statistical formula CORREL(B2:B16,C2:C16), and CORREL finally returns the correlation coefficient between the two sets of values.

[0075] The final correlation coefficient was calculated to be r = 0.99592.

[0076] Similarly, the correlation coefficient between any two services can be calculated based on the total call duration or the number of successful calls for each service. The calculation process is the same as above, except that the call duration is replaced with the total call duration or the number of successful calls.

[0077] The correlation coefficients between services x and z, and between services y and z, can be determined through the above calculations, resulting in the pairwise correlation coefficient statistics table shown in Table 3. In the table, values ​​closer to 1 indicate a perfect positive correlation, -1 indicates a perfect negative correlation, and 0 indicates no correlation.

[0078] Table 3. Correlation Coefficient Statistics

[0079] Service Invocation x y z x 1 - - y 0.99592 1 - z -0.30263 -0.29606 1

[0080] As shown in Table 3, there is a clear positive correlation between service x and service y. However, neither x nor y shows much correlation with z, indicating that there is a calling relationship between service x and service y, but no calling relationship between service x and service z, or between service y and service z.

[0081] The service call chain identification method provided in this application calculates relevance based on the call volume, total call duration, or successful call volume of each service. The correlation coefficient determines whether a call relationship exists between any two services. Based on existing network service call data, the statistical calculations provide highly real-time and accurate identification of call relationships between services, achieving fully automated identification. Since all service call data is obtained from the current operating environment, the service call chains identified by this application are highly accurate and real-time.

[0082] In one embodiment, determining the calling order between two services with a calling relationship based on the application system to which they belong includes:

[0083] If two services with a calling relationship belong to different application systems, the calling order between the two services with a calling relationship is determined according to the preset application system order.

[0084] Optionally, the correlation coefficient can only determine the pairwise relationship between services, but it cannot obtain the order of two service calls, nor can it determine whether x is an independent variable or a dependent variable.

[0085] Therefore, the order of service calls can be determined by the application systems to which the two services with a calling relationship belong, based on the order of the application systems.

[0086] The order of application systems is defined by the users of the application systems. The application systems can be assigned an ascending number based on whether they belong to the front end (such as a website) or the back end (such as an interface service) and the possible mutual call order between back end systems (such as a recharge system calling a payment system).

[0087] Taking the data in Table 4 as an example, A belongs to the front-end system, given as 1, and B belongs to the back-end system, given as 2.

[0088] Table 4 shows that services x and y are related services, meaning they have a calling relationship. Service x belongs to application system A, and service y belongs to application system B, thus confirming that service x calls service y. If the calling relationship between application systems cannot be clearly defined, the sequential numbers of the same application system can be used.

[0089] Table 4. Call Order Determination Table

[0090]

[0091] The service call chain identification method provided in this application determines the order of cross-system and intra-system service calls by actively setting the application system order after determining that there is a call relationship between any two services in the global service. The determination of the call order is very important for the fault location and diagnosis of subsequent service calls. The service call order relationship can be accurately obtained, thereby accurately obtaining the service call chain.

[0092] In one embodiment, determining the calling order between two services with a calling relationship based on the application system to which they belong further includes:

[0093] If two services with a calling relationship belong to the same application system, the calling order between the two services with a calling relationship is determined based on the call volume of the two services with a calling relationship within the target time period.

[0094] Optionally, if two services with a calling relationship belong to the same application system, the calling order cannot be determined based on the application system.

[0095] The order of service calls can be determined by the volume of calls: when application systems have the same order, the average number of calls per service within the same time period will be used as the criterion for determining the order. The service with the lower average number of calls is the caller, and the service with the higher average number of calls is the callee. If there is a call relationship between two services, it is unlikely that the service with the higher average number of calls will access the service with the lower average number of calls, but the reverse is possible because the service may be called by multiple channels.

[0096] For example, referring to the data in Table 4, service y and service y1 are related services, meaning they have a calling relationship. Both belong to system B, but the average service call volume y within the same time period is significantly greater than y1. Therefore, it can be determined that service y1 calls service y.

[0097] By setting the application system order and determining the call order between related services based on service call volume, the service call chain of the global service can be determined. Finally, the determined call relationships are saved for each service using the data structure shown in Table 5, which can be used for subsequent queries of the global service call chain data.

[0098] Table 5. Call Relationship Table

[0099] Pre-service Serve Post-service none x y x,y1 y none none y1 y

[0100] The service call chain setting application system order provided in this application embodiment, and the method for identifying the order of cross-system and intra-system service calls by combining service call volume, ensure that accurate service call order relationship can be obtained through dual methods, thereby accurately obtaining the service call chain.

[0101] In one embodiment, before determining whether a call relationship exists between any two services based on the target data of each service in the target global service, the method further includes:

[0102] Based on the service identifier and call parameters of each service within the target period, the target data of each service is merged.

[0103] Alternatively, in a real cross-system service call environment, many services have the same identifier and can only be distinguished by some key call parameters.

[0104] Therefore, before determining whether a call relationship exists between any two services based on the target data for each service, the target data can be processed according to the call parameters. For example, the call parameters can be categorized to determine which service identifiers can be aggregated and merged.

[0105] The specific calculation method is as follows: For the same call parameter name with the same service identifier, count the number of unique parameter values, denoted as D(service identifier / parameter name). The total number of calls within the statistical period of this service is C(service identifier). Use D(service identifier / parameter name) / C(service identifier) ​​to obtain the dispersion K(service identifier / parameter name) of the parameter.

[0106] You can refer to the data in rows 3 and 4 of Table 1 to obtain:

[0107] D(cash recharge service / account) = 2, which means that in the cash recharge service, the account parameter has appeared twice with different parameter values ​​zzz and yyy;

[0108] C (cash recharge service) = 3, which means that the cash recharge service has a total of 1 + 2 = 3 service calls;

[0109] K(cash recharge service / account) = 2 / 3, meaning that the account parameter had two different values ​​in the three cash recharge service calls.

[0110] Similarly, referring to the data in rows 1 and 2 of Table 1, we get: K( / xxx / yyy / code) = 2 / 300, which means that in a total of 300 service calls to / xxx / yyy, the code parameter has two different values.

[0111] In practice, the degree of dispersion is very easy to define; key parameters or enumerated parameters will be below 1% or even lower.

[0112] As can be seen in the example, the parameter `account` is a mergeable parameter for the cash recharge service, while `code` is a key enumeration parameter for ` / xxx / yyy`. Non-key parameters can be ignored.

[0113] Therefore, the two cash recharge service records in the target data of Table 2 can be merged into one record.

[0114] Specifically, the data in rows 3 and 4 are merged, and the sum of three key metrics—call volume, total call duration, and successful call volume—is calculated to create a single cash recharge service call record. See Table 6 for details.

[0115] Table 6: Merged Target Data Table

[0116]

[0117] By merging parameters, we can effectively identify which service call parameter values ​​need to be considered in their call path branches, and which parameters, although different in value, will ultimately point to the same call chain. Merging service calls with the same call chain into one can effectively reduce the number of service call records, allowing for the final pairwise correlation calculation.

[0118] The service call chain identification method provided in this application can effectively identify which service call parameter values ​​need to consider the branches of their call paths by merging parameters, and which parameters, although different in value, will ultimately point to the same call chain. Merging service calls with the same call chain into one can effectively reduce the number of service call records, allowing for efficient pairwise correlation calculations.

[0119] In one embodiment, the target data is determined in the following way:

[0120] Collect network mirror traffic data of the links to be identified in the target global service;

[0121] The network mirror traffic data is parsed to determine the target data.

[0122] Optionally, network mirror traffic for all links requiring automatic identification can be routed to a dedicated data collection and analysis server. After processing the network packets, data on call volume, response time, and response success rate for all business services can be obtained. This network mirror traffic collection method uses a bypass approach, having no impact on business link data and requiring no modification to existing business systems.

[0123] The service call chain identification method provided in this application uses network mirror traffic collection in a bypass manner, which has no impact on the data of the business link and does not require modification to the original business system.

[0124] In one embodiment, after determining the service call chain, the method further includes:

[0125] Based on the service call chain, identify the preceding and / or following services of the service to be queried.

[0126] Optionally, after the service call chain is determined, that is, after the previous steps are completed, the preceding and following services of each service can be determined. This application embodiment provides a service query interface. By entering the name of the service to be queried, the data of the service call chain can be recursively returned.

[0127] For example, inputting x, the query retrieves its downstream service y. Then, using y as input, the query retrieves its upstream services x and y1. x is a node that has already been queried and does not need to be described again. Querying y1 retrieves its downstream service y, which has also been queried. The final query results are as follows:

[0128] x,y1->y means that both service x and service y1 call service y.

[0129] The service call chain identification method provided in this application embodiment can display a complete global service call chain containing the keyword of a service to be queried by inputting the keyword of that service.

[0130] Figure 2 This is the second flowchart illustrating the service call chain identification method provided in this application embodiment. (Refer to...) Figure 2 This application provides a service call chain identification method, which may include:

[0131] Step 210: Collect and parse network mirror data.

[0132] All network mirror traffic for links that require automatic identification is directed to a dedicated data collection and parsing server. After processing the network packets, data on the call volume, response time, and response success rate of all business services are finally obtained.

[0133] Step 220: Input key service call metrics.

[0134] By providing a data input interface, the received data includes start and end times, application system, service identifier, call parameters, call volume, total call duration, and number of successful calls.

[0135] Step 230: Classify service parameters.

[0136] When many services share the same identifier, they can only be distinguished by some key call parameters. Therefore, it is necessary to classify the call parameters to determine which service identifiers can be aggregated and merged.

[0137] Parameter merging can effectively identify which service call parameter values ​​need to consider the branches of their call paths, and which parameters, although different in value, will ultimately point to the same call chain. Merging service calls with the same call chain into one can effectively reduce the number of service call records, allowing for the final pairwise correlation calculation.

[0138] Step 240: Calculate the correlation coefficient of the service.

[0139] Based on the three key metrics data obtained in step 230, namely, the call volume, total call duration, and successful call volume, any one of these metrics data can be selected to calculate the correlation coefficient between each pair.

[0140] Step 250: Establish service call relationships.

[0141] The calling relationship is determined according to the order of the application systems to which the services belong. This order is defined by the application systems themselves. For example, if two related services belong to the front-end and back-end systems respectively, then it is obvious that the service in the front-end system calls the service in the back-end system.

[0142] When the order of the application systems to which the services belong is the same, the calling order is determined by the amount of calls made within the same time period. That is, the service with the smaller call volume is called and the service with the larger call volume is selected.

[0143] Step 260: Provide external service call chain query.

[0144] By providing a query service interface, you can simply enter the name of the service you want to query to find the call chain containing that service.

[0145] The service call chain identification method provided in this application utilizes a decoupled service model. By collecting comprehensive service key indicator data, it calculates pairwise correlation coefficients between global services to determine call relationships and ultimately automatically constructs a complete cross-system global service call chain. It also provides a standard method for parsing service call indicator data using traffic data; simply inputting a service keyword displays the complete global service call chain containing that keyword. The results of this service call chain can be applied in real-time to monitoring business service calls, detecting faults at specific service points, and performing root cause analysis.

[0146] The service call chain identification method provided in this application has the following advantages:

[0147] 1. Easy to promote: It can automatically identify global service call chains across systems without application modification, and there is no need to worry about any impact on the system services themselves. Therefore, it is very conducive to promotion to older systems and heterogeneous systems with complex call relationships. By providing supporting data collection tools and standardized interfaces, it can support service call chains of different technology stacks.

[0148] 2. Accuracy: Accuracy refers to the consistency between the automatically identified call chain and the actual service call chain running in production. Since all service call metrics are obtained in the current operating environment, the service call chain automatically identified by the method provided in this application embodiment is highly accurate and real-time.

[0149] The service call chain identification device provided in the embodiments of this application is described below. The service call chain identification device described below can be referred to in correspondence with the service call chain identification method described above.

[0150] Figure 3 A schematic diagram of the service call chain identification device provided in an embodiment of this application. (Refer to...) Figure 3 This application provides a service call chain identification device, which may include:

[0151] The first determining module 310 is used to determine whether there is a calling relationship between any two services based on the target data of each service in the target global service;

[0152] The second determining module 320 is used to determine the calling order between two services that have a calling relationship based on the application system to which the two services belong.

[0153] The third determining module 330 is used to determine the service call chain based on the call order;

[0154] The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

[0155] The service call chain identification device provided in this application embodiment obtains the call volume, total call duration or call success rate data of all services, determines whether there is a call relationship between any two services, and determines the call relationship between services according to the system to which the services belong, thereby realizing the automated construction of a complete cross-system global service call chain.

[0156] In one embodiment, the first determining module 310 is specifically used for:

[0157] Determine the correlation between any two services based on the target data of each service in the target global service;

[0158] Based on the correlation, determine whether there is a call relationship between any two services.

[0159] In one embodiment, the second determining module 320 is specifically used for:

[0160] If two services with a calling relationship belong to different application systems, the calling order between the two services with a calling relationship is determined according to the preset application system order.

[0161] In one embodiment, the second determining module 320 is further configured to:

[0162] If two services with a calling relationship belong to the same application system, the calling order between the two services with a calling relationship is determined based on the call volume of the two services with a calling relationship within the target time period.

[0163] In one embodiment, before determining whether a call relationship exists between any two services based on the target data of each service in the target global service, the method further includes:

[0164] Based on the service identifier and call parameters of each service within the target period, the target data of each service is merged.

[0165] In one embodiment, the target data is determined in the following way:

[0166] Collect network mirror traffic data of the links to be identified in the target global service;

[0167] The network mirror traffic data is parsed to determine the target data.

[0168] In one embodiment, after determining the service call chain, the method further includes:

[0169] Based on the service call chain, identify the preceding and / or following services of the service to be queried.

[0170] Figure 4 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 4 As shown, the electronic device may include: a processor 410, a communication interface 420, a memory 430, and a communication bus 440, wherein the processor 410, the communication interface 420, and the memory 430 communicate with each other via the communication bus 440. The processor 410 can call a computer program in the memory 430 to execute a service call chain identification method, such as including:

[0171] Based on the target data of each service in the target global service, determine whether there is a call relationship between any two services;

[0172] Determine the calling order between two services that have a calling relationship based on the application system to which they belong;

[0173] Determine the service call chain based on the call order;

[0174] The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

[0175] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0176] On the other hand, embodiments of this application also provide a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the service call chain identification method provided in the above embodiments, for example including:

[0177] Based on the target data of each service in the target global service, determine whether there is a call relationship between any two services;

[0178] Determine the calling order between two services that have a calling relationship based on the application system to which they belong;

[0179] Determine the service call chain based on the call order;

[0180] The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

[0181] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing a processor to execute the service call chain identification method provided in the above embodiments, such as including:

[0182] Based on the target data of each service in the target global service, determine whether there is a call relationship between any two services;

[0183] Determine the calling order between two services that have a calling relationship based on the application system to which they belong;

[0184] Determine the service call chain based on the call order;

[0185] The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

[0186] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0187] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0188] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0189] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A service call chain identification method, characterized in that, include: Based on the service identifier and call parameters of each service within the target period, the target data for each service is merged, including classifying the call parameters to determine which service identifiers can be aggregated and merged. Specifically, for the same call parameter name with the same service identifier, the number of deduplicated parameter values ​​is counted as D, the total number of calls within the service statistical period is C, and the dispersion K of the parameter is obtained by using D / C. The dispersion of key parameters or enumerated parameters will be less than 1% or lower, and non-key parameters can be ignored. Through parameter merging, it is identified which service call parameter values ​​need to consider the branches of their call paths, and which parameters, although different in value, will ultimately point to the same call chain. Service calls with the same call chain are merged into one, and the sum of three key indicators—call volume, total call duration, and call success rate—is calculated to effectively reduce the number of service call records, allowing the final pairwise correlation calculation to be performed. Based on the target data of each service in the target global service, determine whether there is a call relationship between any two services; The calling order between two services with a calling relationship is determined based on the application systems to which they belong. This includes determining the calling order based on a preset application system order when the two services belong to different application systems; and determining the calling order based on the call volume of the two services within a target time period when the two services belong to the same application system. When the application system order is the same, the average call volume of the services within the same time period is used as the order determination criterion, with the service with the lower average call volume being the caller and the service with the higher average call volume being the callee. Determine the service call chain based on the call order; The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

2. The service call chain identification method according to claim 1, characterized in that, The step of determining whether a call relationship exists between any two services based on the target data of each service in the target global service includes: Determine the correlation between any two services based on the target data of each service in the target global service; Based on the correlation, determine whether there is a call relationship between any two services.

3. The service call chain identification method according to claim 1 or 2, characterized in that, The target data is determined in the following way: Collect network mirror traffic data of the links to be identified in the target global service; The network mirror traffic data is parsed to determine the target data.

4. The service call chain identification method according to claim 1 or 2, characterized in that, Following the determination of the service call chain, the following is also included: Based on the service call chain, identify the preceding and / or following services of the service to be queried.

5. A service call chain identification device, characterized in that, include: The first determination module is used to merge the target data of each service based on the service identifier and call parameters of each service within the target period. This includes classifying the call parameters to determine which service identifiers can be aggregated and merged. Specifically, it includes counting the number of duplicate parameter values ​​for the same call parameter name with the same service identifier, denoted as D, and the total number of calls within the service statistical period, denoted as C. The dispersion K of the parameter is obtained by using D / C. The module is used to determine whether there is a call relationship between any two services based on the target data of each service in the target global service. The dispersion of key parameters or enumerated parameters will be less than 1% or lower, and non-key parameters can be ignored. Through parameter merging, it identifies which service call parameter values ​​need to consider the branches of their call paths, and which parameters, although different in value, will ultimately point to the same call chain. Service calls with the same call chain are merged into one, and the sum of three key indicators—call volume, total call duration, and call success rate—is calculated to effectively reduce the number of service call records, so that the final pairwise correlation calculation can be performed. The second determining module is used to determine the calling order between two services with a calling relationship based on the application systems to which they belong. This includes determining the calling order based on a preset application system order when the application systems to which the two services with a calling relationship belong are different; and determining the calling order based on the call volume of the two services with a calling relationship within a target time period when the application systems to which the two services with a calling relationship belong are the same. When the application system order is the same, the average call volume of the services within the same time period is used as the order judgment standard, with the service with the lower average call volume being the caller and the service with the higher average call volume being the callee. The third determining module is used to determine the service call chain based on the call order; The target data includes at least one of the following: number of calls, total call duration, or number of successful calls.

6. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the service call chain identification method according to any one of claims 1 to 4.

7. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the service call chain identification method as described in any one of claims 1 to 4.

Citation Information

Patent Citations

  • Determination program, determination method and determination system

    JP2014127025A

  • Computer product, request grouping apparatus, and request grouping method

    US20070260589A1