Method for determining long-distance calling time consumption of micro service, storage medium and electronic equipment

Abstract

The invention discloses a microservice remote calling time consumption determination method, a storage medium and electronic equipment. Relates to the field of cloud computing, and the method comprises the following steps: obtaining a plurality of first micro-services involved in a target business scene and a calling relationship among the plurality of first micro-services, the plurality of first micro-services being used for implementing a target business to be implemented in the target business scene; determining a target area where a server corresponding to the plurality of first micro-services is located; on the basis of the calling relation and the target area, the remote calling time consumption among the multiple first micro-services is determined, and the remote calling time consumption is used for representing that the calling time consumption is additionally increased due to the fact that the servers corresponding to the multiple first micro-services are located in different areas; and determining the total remote calling time consumption of the target business scene based on the remote calling time consumption among the plurality of first micro-services. Through the method and the device, the problem of low time consumption and accuracy of remote calling of the computing micro-service in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of cloud computing, and more specifically, to a method for determining the time consumption of a remote call of a microservice, a storage medium, and an electronic device. Background Art

[0002] In the traditional data center architecture, enterprises usually adopt the "two locations and three centers" strategy to ensure data security and business continuity, that is, to set up two main data centers in one city to achieve load balancing and failover, and to set up a disaster recovery data center in another city to prevent city-level disasters. However, with the continuous expansion of business scale and the acceleration of globalization, this architecture has been difficult to meet the needs of enterprises for higher data security and shorter response time. In recent years, more and more enterprises have begun to adopt the "multi-location multi-center" architecture strategy, that is, to build multiple data centers in multiple cities, each city may contain multiple data centers, to further improve the availability and performance of the system. This architecture strategy can not only better disperse risks, but also utilize network resources in different cities to provide users with more stable and faster services.

[0003] However, when microservices migrate from "two locations and three centers" to "multiple locations and multiple centers", the frequency of cross-city calls will increase significantly, which will directly affect the response time and overall performance of the service. Cross-city calls involve network transmission in different cities, which will increase additional time consumption, thus affecting user experience and business efficiency. Therefore, how to accurately assess the time consumption increase that may be caused by cross-city calls of microservices during the migration process from "two locations and three centers" to "multiple locations and multiple centers" has become an important issue that enterprises need to solve urgently.

[0004] There is currently no effective solution to the problem of low accuracy in calculating the time consumption of remote calls to microservices in related technologies. Summary of the invention

[0005] The main purpose of the present application is to provide a method for determining the time consumption of remote calls of microservices, a storage medium, and an electronic device, so as to solve the problem of low accuracy in calculating the time consumption of remote calls of microservices in related technologies.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for determining the time consumption of remote calls of microservices is provided. The method includes: obtaining multiple first microservices involved in the target business scenario and the calling relationship between multiple first microservices, wherein the multiple first microservices are used to implement the target business to be implemented in the target business scenario; determining the target area where the servers corresponding to the multiple first microservices are located, wherein the server is used to represent the server providing the corresponding first microservice; based on the calling relationship and the target area, determining the remote call time consumption between the multiple first microservices, wherein the remote call time consumption is used to represent the additional call time consumption due to the servers corresponding to the multiple first microservices being in different areas; based on the remote call time consumption between the multiple first microservices, determining the total remote call time consumption of the target business scenario.

[0007] Further, determining the target area where the servers corresponding to the multiple first microservices are located includes: determining first identification information of the target server, wherein the target server is a server corresponding to any one of the first microservices; determining the target area where the target server is located based on a first preset correspondence relationship and the first identification information, wherein the first preset correspondence relationship is used to represent the correspondence between the first identification information and the target area.

[0008] Furthermore, determining the time consumption of remote calls between multiple first microservices based on the call relationship and the target area includes: determining at least one adjacent first microservice whose corresponding server is located in a remote location among the multiple first microservices based on the call relationship and the target area; determining the time consumption of remote calls of at least one adjacent first microservice based on a second preset corresponding relationship and the target area, wherein the second preset corresponding relationship is used to represent the time consumption of remote calls between any two areas.

[0009] Furthermore, based on the remote call time between multiple first microservices, the total remote call time of the target business scenario is determined, including: summarizing the remote call time between multiple first microservices to obtain the total remote call time.

[0010] Furthermore, obtaining the calling relationships between the multiple first microservices and the multiple first microservices involved in the target business scenario includes: obtaining the second identification information of the multiple first microservices; traversing the topological structure recorded in the graph database to obtain the first node and the second node matching the second identification information; and determining the calling relationship from the topological structure based on the first node and the second node.

[0011] Furthermore, based on the first node and the second node, determining the call relationship from the topological structure includes: retrieving a call link with the first node as the starting node and the second node as the ending node from the topological structure; and determining the call relationship based on the call link.

[0012] Furthermore, the method also includes: obtaining third identification information of multiple second microservices and transaction data of multiple second microservices; constructing an initial topology structure based on the third identification information and the transaction data, and outputting the initial topology structure; in response to receiving an instruction to select the initial topology structure, determining a topology structure associated with a target business scenario, and storing the topology structure in a graph database.

[0013] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a device for determining the time consumption of remote calls of microservices is provided. The device includes: a relationship acquisition module, which is used to obtain the calling relationship between multiple first microservices and multiple first microservices involved in the target business scenario, wherein the multiple first microservices are used to implement the target business to be implemented in the target business scenario; an area determination module, which is used to determine the target area where the servers corresponding to the multiple first microservices are located, wherein the server is used to represent the server providing the corresponding first microservice; a first determination module, which is used to determine the remote call time consumption between the multiple first microservices based on the calling relationship and the target area, wherein the remote call time consumption is used to represent the additional call time consumption due to the servers corresponding to the multiple first microservices being in different areas; a second determination module, which is used to determine the total remote call time consumption of the target business scenario based on the remote call time consumption between the multiple first microservices.

[0014] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer-readable storage medium is provided, and the computer-readable storage medium includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the methods in various embodiments of the present invention.

[0015] In order to achieve the above-mentioned purpose, according to another aspect of the present application, an electronic device is provided, comprising: a memory storing an executable program; and a processor for running the program, wherein the method in each embodiment of the present invention is executed when the program is running.

[0016] In order to achieve the above objective, according to another aspect of the present application, a computer program product is provided, including computer instructions, and when the computer instructions are executed by a processor, the methods in various embodiments of the present invention are implemented.

[0017] In an embodiment of the present application, a method is adopted in which the calling relationships between multiple first microservices and multiple first microservices involved in the target business scenario are obtained; the target area where the servers corresponding to the multiple first microservices are located is determined; based on the calling relationship and the target area, the remote calling time between the multiple first microservices is determined; based on the remote calling time between the multiple first microservices, the total remote calling time of the target business scenario is determined. By analyzing the calling relationship between the microservices, it is possible to identify which microservices are indispensable components in the implementation process of the target business scenario. By accurately locating the target area where the server corresponding to each microservice is located, the impact of geographical distance on the remote calling time of the microservice can be considered. Combined with the above-mentioned calling relationship and target area, the time consumption of each remote call can be accurately calculated, and by aggregating all the remote calling time consumptions, the total remote calling time consumption under the entire target business scenario can be determined, thereby achieving the purpose of accurately calculating the time consumption that may increase in the process of multi-location and multi-center construction, thereby achieving the technical effect of accurately evaluating the time consumption increase of microservices in the cross-city calling scenario, and thus solving the technical problem of low accuracy in calculating the remote calling time consumption of microservices in the related technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 A hardware structure block diagram of a computer terminal for implementing a method for determining the time consumption of a remote call of a microservice is shown;

[0020] Figure 2 This is a flow chart of a method for determining the time consumption of a remote call of a microservice according to an embodiment of the present application;

[0021] Figure 3 is a schematic diagram of a device for determining the time consumption of a remote call of a microservice according to an embodiment of the present application;

[0022] Figure 4 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application 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 interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising 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 devices.

[0025] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following explanations:

[0026] Cross-city calls: The data centers involved in service calls are in different cities, which will increase additional time due to network transmission.

[0027] Two locations, three centers: Build two main data centers in one city, and build a disaster recovery data center in another city that is farther away.

[0028] Multi-location and multi-center: Multiple data centers are built in multiple cities without geographical restrictions. Each city may have n data centers.

[0029] Full-link monitoring: A systematic monitoring method that records every link from user requests to backend microservices to ensure system performance and reliability, and transmits information such as transaction identifiers along with the transactions.

[0030] Business tags: Tags set according to business scenarios, set on microservices, and transmitted with full-link monitoring (full-link coloring technology).

[0031] It should be noted that the collected information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with relevant laws, regulations and standards, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions to provide users with corresponding operation entrances for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0032] Example 1

[0033] According to an embodiment of the present application, an embodiment of a method for determining the time consumption of a remote call of a microservice is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0034] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal (or mobile device) for implementing a method for determining the time consumption of a remote call of a microservice is shown. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0035] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0036] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the method for determining the time consumption of remote calls of microservices in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the remote call time consumption determination method of the above-mentioned microservice is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0037] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0038] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0039] Under the above operating environment, this application provides Figure 2 The method for determining the time consumption of remote calls to microservices is shown. Figure 2 It is a flowchart of a method for determining the time consumption of a remote call of a microservice according to an embodiment of the present application.

[0040] Step S202: Acquire multiple first microservices involved in the target business scenario and the calling relationship between the multiple first microservices, wherein the multiple first microservices are used to implement the target business to be realized in the target business scenario.

[0041] The target business scenario may be a business scenario that needs to evaluate the time-consuming growth. For example, a transfer business process of an online banking system, that is, a whole set of operations from the user initiating a transfer request to transaction confirmation, fund transfer, balance update, etc., can be regarded as a target business scenario, but is not limited to this. The target business scenario is usually composed of a call link of a series of microservices, which work together to complete a specific business goal. The first microservice may be each independent microservice that directly participates in the business implementation in the target business scenario. For example, the first microservice may include a transaction confirmation microservice, a fund transfer microservice, a balance update microservice, etc., but is not limited to this. The target business may be the ultimate business goal or function to be achieved by the target business scenario. For example, in the bank transfer business scenario, the target business is to realize the transfer of user funds from one account to another, but is not limited to this.

[0042] In an optional embodiment, considering that the relevant technology often only considers the one-time call time between an intuitive number of microservices, while ignoring the actual call links and multi-level call relationships in the target business scenario, which leads to inaccurate and incomplete time estimation, and further considering that in the "multi-site multi-center" data center layout, microservices may be distributed in different cities, and cross-city calls will introduce additional network delays. Only by clarifying which microservices will participate in cross-city calls can the specific impact of this layout on business time be accurately calculated. Therefore, the off-site call time calculation system (hereinafter referred to as the calculation system) can first obtain the call relationships between multiple first microservices and multiple first microservices involved in the target business scenario, thereby providing a data basis for subsequent off-site call time calculations, thereby improving the accuracy of calculating off-site call time.

[0043] For example, in order to more accurately obtain the calling relationships between multiple first microservices and multiple first microservices involved in the target business scenario, the computing system can pre-deploy a full-link monitoring program, which can record every link from the user request to the backend microservice, including but not limited to important information such as service response time, request time, microservice name, cluster name, application name, and transaction identity identifier. Since the data monitored by the above-mentioned full-link monitoring program may contain a large amount of redundant data, in order to filter out the calling links related to the target business scenario, the computing system can add business tags to the monitoring data. The above-mentioned business tags can be set at the starting point of the user request (i.e., the entry service) to mark all microservice calls under the business scenario, thereby filtering out the data directly related to the target business scenario from the monitoring data. Subsequently, the computing system can restore the calling relationships of multiple microservices under the target business scenario based on the data directly related to the target business scenario, thereby providing a data basis for the subsequent off-site call time-consuming calculation.

[0044] Step S204: determine a target area where servers corresponding to the plurality of first microservices are located, wherein a server is used to represent a server providing the corresponding first microservice.

[0045] The above-mentioned servers may be physical or virtual computing devices that carry and process microservice requests. In a microservice architecture, each microservice may run on a group of servers located in a data center or cloud environment and are responsible for performing specific functions defined by the microservice. The above-mentioned servers may be traditional physical servers or virtual servers dynamically created and managed in a cloud platform. In a "multi-site, multi-center" data center layout, servers may be distributed in different geographical locations to provide high availability, disaster recovery capabilities, and service responses close to users. The above-mentioned target area may be a specific geographical area where the server is located. For example, in a "multi-site, multi-center" architecture, the above-mentioned target area may be a city, a data center, or a geographically defined range, but is not limited thereto.

[0046] In an optional embodiment, considering that in a "multi-site multi-center" architecture, the servers used to provide the above-mentioned first microservice may be distributed in different cities or regions, in the scenario of cross-city calls, the calls between multiple first microservices may be affected by network transmission delays, and the traditional time calculation method often lacks consideration of the location information of the server running the microservice, thereby ignoring the impact of geographical distance on network transmission time, resulting in poor calculation accuracy of the time consumption of microservice remote calls. Therefore, by determining the target area where the server corresponding to the above-mentioned first microservice is located, the computing system can use the pre-established inter-city network delay database to accurately calculate the additional time consumption of cross-city calls, thereby quantitatively evaluating the network delay in the entire business scenario.

[0047] For example, in order to more accurately determine the target area where the servers corresponding to the above-mentioned multiple first microservices are located, the computing system can pre-build a database to record the detailed information of the multiple microservices, including the name of the microservice, the cluster name, the application name, etc., and the physical location of the servers corresponding to the above-mentioned multiple microservices. Subsequently, the computing system can build a topological structure of microservice calls in the target business scenario based on the calling relationships between the multiple first microservices and the multiple first microservices obtained in the aforementioned steps. Subsequently, the computing system can extract the information of each microservice from the above-mentioned topological structure, and match the extracted microservice information with the data in the above-mentioned database to confirm the target area where the server corresponding to each microservice is located.

[0048] Step S206: Determine the remote call time between the multiple first microservices based on the call relationship and the target area, where the remote call time is used to indicate the additional call time due to the fact that the servers corresponding to the multiple first microservices are in different areas.

[0049] The above-mentioned remote call time may refer to the additional delay time in the microservice architecture when a microservice calls another microservice located in a different geographical area because the data needs to be transmitted from one area to another through the network. This time consumption is mainly caused by factors such as network transmission delay, possible cross-region routing delay, and network quality differences between different data centers.

[0050] In an optional embodiment, considering that in a "multi-site, multi-center" architecture, the communication between microservices may span different geographical locations, the traditional time calculation method is difficult to accurately reflect the network delay when the microservice is called remotely. Therefore, the computing system determines the remote call time between multiple first microservices based on the call relationship and the target area, which can improve the calculation accuracy of the remote call time of the first microservice in the "multi-site, multi-center" architecture. The above steps quantify the network delay when the first microservice is called remotely, which can help the computing system understand which service calls will increase the response time due to geographical factors, so as to make better decisions in service deployment, architecture design and resource allocation.

[0051] For example, it can be assumed that the computing system has constructed the topological structure of the microservice transaction through the above steps. The structure can be an N-ary tree, where the points of the N-ary tree are the information of the microservice (microservice name, cluster name, application name, etc.), and the edges of the N-ary tree are the information of the microservice call relationship (identifier, starting point, and end point of the business scenario). The computing system can also build a maintenance table containing network delays between different regions based on the historical data of microservice calls. For each edge in the N-ary tree that is determined to be a remote call, the computing system can query the above maintenance table to obtain the network delay between the regions where the calling parties are located. The above network delay value is added to the original time consumption of the call process to obtain the total time consumption of the remote call. Through this calculation, the specific impact of remote calls on the performance of the microservice architecture can be quantified.

[0052] Step S208: Determine the total remote call time of the target business scenario based on the remote call time between the multiple first microservices.

[0053] The total remote call duration can be obtained by adding up the additional duration of all remote calls in the target business scenario. In the target business scenario, a request may need to be processed by multiple microservices, some of which may be local calls within the same geographic area, while others may span different regions, i.e., remote calls. The total remote call duration quantifies the sum of the additional duration of all these remote calls, providing an important reference indicator for the overall performance of the business scenario.

[0054] In an optional embodiment, considering that in a "multi-site multi-center" architecture, business scenarios often involve calls to multiple microservices, due to the existence of network transmission delays, especially when these calls span different geographical areas, the time consumption of each call will increase. If the time consumption of all remote calls is not summarized, it may cause the computing system to calculate the time consumption of remote calls in the entire business scenario inaccurately, and the traditional time consumption calculation method is difficult to summarize and analyze the time consumption of all remote calls in the entire business scenario, resulting in inaccurate overall performance evaluation. Therefore, the computing system can determine the total remote call time consumption of the target business scenario based on the remote call time consumption between multiple first microservices. For example, the computing system can calculate the specific time consumption of each remote call based on the aforementioned steps. At this time, the computing system can summarize the specific time consumption of all the above remote calls to obtain the total remote call time consumption in the target business scenario.

[0055] Optionally, in the method for determining the time consumption of remote calls of microservices provided in an embodiment of the present application, determining the target area where servers corresponding to multiple first microservices are located includes: determining first identification information of the target server, wherein the target server is a server corresponding to any one of the first microservices; determining the target area where the target server is located based on a first preset correspondence relationship and the first identification information, wherein the first preset correspondence relationship is used to represent the correspondence between the first identification information and the target area.

[0056] The above-mentioned target server may refer to a specific server in the microservice architecture that is responsible for executing or hosting each first microservice. The above-mentioned first identification information may be information used to uniquely identify the target server. For example, the above-mentioned first identification information may be the Internet Protocol address, host name, cluster name, etc. of the server, but is not limited to this. The above-mentioned first preset correspondence may be a correspondence between the above-mentioned first identification information and the target area. Specifically, the above-mentioned first preset correspondence may associate the identification information of the server (such as cluster name, Internet Protocol address, etc.) with the specific geographical area (such as city, data center location, etc.) where the server is located.

[0057] In an optional embodiment, considering that a microservice architecture may include multiple microservices, and each microservice may run on a different server, in order to accurately distinguish the server corresponding to each microservice, and thus improve the accuracy of the time-consuming calculation of microservice remote calls, the computing system can pre-set unique identity information for each of the above servers. In order to accurately determine the target area where the servers corresponding to multiple first microservices are located, the computing system can first determine the identity of the server corresponding to any first microservice, that is, the first identification information of the above target server. Since the first preset correspondence establishes an association between the above first identification information and the target area, the computing system can further determine the target area where the target server is located based on the first preset correspondence and the first identification information. Based on the above steps, the computing system can more accurately determine the target area where the target server is located, thereby ensuring the accuracy of the subsequent remote call time calculation.

[0058] For example, in a "multi-site multi-center" architecture, the computing system can pre-set a unique identifier for each server based on the Internet Protocol address of each server, and the identifier can be used to distinguish different servers. Subsequently, the computing system can construct a maintenance table, which can include the correspondence between the first identification information of each server and the target area where the server is located, thereby constructing the above-mentioned first preset correspondence. If the computing system needs to evaluate the time consumption of a first microservice call, it can directly query the specific area where the server is located from the above-mentioned first preset correspondence based on the identification information of the server corresponding to the first microservice.

[0059] Optionally, in the method for determining the time consumption of a remote call of a microservice provided in an embodiment of the present application, the time consumption of a remote call between multiple first microservices is determined based on the call relationship and the target area, including: based on the call relationship and the target area, determining at least one adjacent first microservice whose corresponding server among the multiple first microservices is located in a remote location; based on a second preset corresponding relationship and the target area, determining the time consumption of a remote call of at least one adjacent first microservice, wherein the second preset corresponding relationship is used to represent the time consumption of a remote call between any two areas.

[0060] The adjacent first microservice may be another first microservice directly called by a first microservice in a business process or transaction. The second preset correspondence may be a correspondence of the time consumption of remote calls between any two regions (data centers or server cluster locations).

[0061] In an optional embodiment, considering that in a complex deployment scenario of "multiple locations and multiple centers", microservices may be distributed in multiple different regions, and the network delay differences between the above different regions affect the accuracy of the calculation of the time consumption of remote calls. In order to accurately evaluate the impact of network delay on microservice calls, the computing system can pre-construct the above second preset correspondence relationship to clarify the time consumption of remote calls between any two regions. Based on the call relationship and the target area, the computing system can accurately find out those adjacent microservices that are deployed in different geographical areas (i.e., remote locations) and have direct call relationships. Then, the computing system can combine the target area (i.e., the geographical area where the caller and the callee are located) with the above second preset correspondence relationship to calculate the remote call time consumption of the above adjacent microservice calls. The above remote call time consumption not only includes the pure network transmission time, but also may cover the additional processing time caused by cross-regional calls, thereby improving the computing system's calculation accuracy of the time consumption of remote microservice calls.

[0062] For example, the computing system can construct a topological structure of the calling relationship of multiple first microservices based on the aforementioned steps, and can pre-construct a data table containing the network time consumption between different regions based on historical call data, which can be used to represent the average time consumption or network delay of microservice calls between any two different regions. In this embodiment, it can be assumed that the target business scenario includes microservice A, and the computing system determines that the adjacent microservice that directly interacts with microservice A in the target area is microservice B by analyzing the above topological structure. If microservice B is deployed in a geographical area different from the above target area, then the communication between microservice A and microservice B constitutes a remote call. In this embodiment, it can be further assumed that the area where microservice B is located is area C different from the target area. At this time, the computing system can obtain the time consumption data between the target area and area C by querying the above data table.

[0063] Optionally, in the method for determining the remote call time consumption of a microservice provided in an embodiment of the present application, the total remote call time consumption of the target business scenario is determined based on the remote call time consumption between multiple first microservices, including: summarizing the remote call time consumption between multiple first microservices to obtain the total remote call time consumption.

[0064] In an optional embodiment, considering that in a "multi-site multi-center" microservice architecture, business transactions may involve calls between multiple microservices, some of which may span different geographical areas, that is, remote calls. It should be noted that each remote call may add additional time due to network delays. If the time consumption is not summarized and only the time consumption of a single call is focused on, the accumulated network delay effect in the overall transaction process may be ignored, thereby reducing the calculation accuracy of the overall remote call time consumption in the current business scenario. Therefore, the computing system can summarize the remote call time consumption between multiple first microservices to obtain the total remote call time consumption, so as to improve the accuracy of the remote call time consumption in the above microservice structure.

[0065] Optionally, in the method for determining the time consumption of remote calls of microservices provided in an embodiment of the present application, multiple first microservices involved in the target business scenario and the calling relationship between the multiple first microservices are obtained, including: obtaining second identification information of the multiple first microservices; traversing the topological structure recorded in the graph database to obtain the first node and the second node matching the second identification information; based on the first node and the second node, determining the calling relationship from the topological structure.

[0066] The above-mentioned second identification information may be an attribute or feature used to uniquely identify a microservice node in a graph database. For example, the above-mentioned second identification information may include at least one or more of the following: service name, version number, cluster name, application name or service instance identifier, etc., but not limited to this. The above-mentioned graph database may be a database for storing call relationships between services. The above-mentioned first node may refer to a node in the topology of the graph database that corresponds to the first microservice in the second identification information. The above-mentioned second node may refer to a node in the topology of the graph database that corresponds to the microservice called by the first microservice.

[0067] In an optional embodiment, in order to accurately locate nodes related to multiple first microservices in the above-mentioned graph database, and then analyze the calling relationship between the multiple first microservices, the computing system can first obtain the second identification information of the multiple first microservices. Since the graph database stores the topological structure of the entire microservice architecture, the computing system can traverse the topological structure recorded in the graph database, so as to find nodes matching the second identification information in the graph database, that is, the above-mentioned first node and second node. Once the first node and the second node are found through traversal, the computing system can determine the calling relationship between multiple first microservices and multiple first microservices based on the path relationship between these nodes in the graph database.

[0068] For example, it can be assumed that there are currently two first microservices, respectively denoted as service A and service B, where the cluster name of service A can be X, and the cluster name of service B can be Y, and both service A and service B use their respective cluster names as the above-mentioned second identification information. In the above-mentioned graph database, the calling relationship between microservices is modeled as nodes and edges in the graph. By traversing the topological structure recorded in the graph database, the computing system can query the nodes that meet the second identification information of service A, that is, node a corresponding to service A and node b corresponding to service B. Then node a is the above-mentioned first node, and node b is the above-mentioned second node. At this time, the computing system can determine the calling relationship between microservices A and service B, that is, service A calls service B.

[0069] Optionally, in the method for determining the time consumption of remote calls of microservices provided in an embodiment of the present application, a call relationship is determined from a topological structure based on a first node and a second node, including: retrieving a call link with the first node as the starting node and the second node as the ending node from the topological structure; and determining the call relationship based on the call link.

[0070] The above starting node can be the source of the call link, that is, the microservice node that initiates the request or calls. The above ending node can be the destination of the call link, that is, the microservice node that receives the request or is called. The above call link can be a path of a series of microservice calls from the starting node to the ending node. In the microservice architecture, the call link may involve the calls of multiple intermediate services, forming a complex path.

[0071] In an optional embodiment, considering that in a microservice architecture, the call relationship between microservices constitutes a complex network, namely, a topological structure. When it is necessary to analyze the call relationship between the first node and the second node, it is necessary to accurately locate the call link between the two nodes from the topological structure. Therefore, the computing system can first retrieve the call link with the first node as the starting node and the second node as the ending node from the topological structure, and can further determine the call relationship based on the call link.

[0072] For example, it can be assumed that the computing system has determined that the first node is node a and the second node is node b. In order to accurately determine the calling relationship between microservice A corresponding to node a and microservice B corresponding to node b, the computing system can use node a as the starting node and node b as the ending node, and use the graph database query statement to retrieve the calling link from node a to node b from the topology structure. Assume that the link is as follows: node a-node c-node d-node b, which indicates that starting from service A, service C and service D are called in sequence, and finally service B is called. Based on this, the computing system can determine the following calling relationship: service A calls service C, service C calls service D, and service D calls service B.

[0073] Optionally, in the method for determining the time consumption of remote calls of microservices provided in an embodiment of the present application, the method also includes: obtaining third identification information of multiple second microservices and transaction data of multiple second microservices; constructing an initial topology structure based on the third identification information and the transaction data, and outputting the initial topology structure; in response to receiving an instruction to select the initial topology structure, determining a topology structure associated with the target business scenario, and storing the topology structure in a graph database.

[0074] The second microservice may refer to other microservices other than the entry microservice in the microservice architecture, and the second microservice may directly or indirectly participate in the processing of the business scenario. The third identification information may be the unique identification information of the second microservice, which is used to distinguish different second microservices. The transaction data may be a specific data record generated by a microservice call in one or more business transactions. For example, the transaction data may include at least one or more of the following: transaction time, transaction type, transaction amount, identification information of the caller and the service party, call status (success / failure), and call time, but not limited to this. The initial topology may be the original mapping of the call relationship between multiple microservices without specifying a business scenario. The selection instruction may refer to an instruction for the user to filter and focus on the microservice call relationship in the initial topology according to the required business scenario. For example, the selection instruction may be a specified business tag, but not limited to this.

[0075] In an optional embodiment, considering that each service may have multiple instances in a microservice architecture, and the calling relationship between services is complex. Therefore, the computing system can obtain the third identification information and transaction data of multiple second microservices to more accurately identify and manage the operating status of different microservice instances, that is, the calling relationship between different microservice instances. In order to present the calling relationship between microservices in a graphical manner and realize the visualization of business processes, the computing system can build an initial topology structure based on the third identification information and transaction data, and output the initial topology structure. Further considering that there may be multiple different business scenarios in the microservice architecture. After receiving the selection instruction, the computing system can determine the topology structure related to the target business scenario, and store the topology structure in the graph database to realize the persistence and structured storage of data, which is not only conducive to the query and analysis of historical data, but also improves the efficiency of data processing.

[0076] For example, the computing system can monitor the process in the current business scenario through the full-link dyeing technology to obtain monitoring data. The computing system can analyze the above monitoring data to extract the third identification information of the second microservice in the current business scenario, as well as the transaction data related to the calls of these microservices. Subsequently, based on the collected third identification information and transaction data, the computing system can construct an initial topological structure of the microservice architecture, which includes the call relationship between the above multiple second microservices. The computing system can output the constructed initial topological structure in a visual form. When receiving a selection instruction containing a business tag A, the computing system can filter out all microservice call relationships associated with the business tag A from the above initial topological structure, thereby constructing a topological subgraph that is more focused on the target business scenario corresponding to the business tag A. Finally, the computing system can store the filtered topological structure associated with the above target business scenario in the graph database, thereby providing support for the subsequent calculation of the remote call time, thereby improving the accuracy of the remote call time.

[0077] The method for determining the time consumption of remote calls of microservices provided in the embodiment of the present application can identify which microservices are indispensable components in the process of realizing the target business scenario by analyzing the calling relationship between microservices, and can consider the impact of geographical distance on the time consumption of remote calls of microservices by accurately locating the target area where the server corresponding to each microservice is located. Combined with the above-mentioned calling relationship and target area, the time consumption of each remote call can be accurately calculated, and by aggregating the time consumption of all remote calls, the total time consumption of remote calls in the entire target business scenario can be determined, thereby achieving the purpose of accurately calculating the time consumption that may increase in the process of multi-site and multi-center construction, thereby realizing the technical effect of accurately evaluating the time consumption increase of microservices in cross-city calls, and further solving the technical problem of low accuracy in calculating the time consumption of remote calls of microservices in related technologies.

[0078] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0079] Example 2

[0080] The embodiment of the present application also provides a device for determining the time consumption of a remote call of a microservice. It should be noted that the device for determining the time consumption of a remote call of a microservice in the embodiment of the present application can be used to execute the method for determining the time consumption of a remote call of a microservice provided in the embodiment of the present application. The device for determining the time consumption of a remote call of a microservice provided in the embodiment of the present application is introduced below.

[0081] According to an embodiment of the present application, a device for implementing the above-mentioned method for determining the time consumption of remote invocation of microservices is also provided. Figure 3 is a schematic diagram of a device for determining the time consumption of a remote call of a microservice according to an embodiment of the present application, such as Figure 3 As shown, the device comprises:

[0082] The relationship acquisition module 302 is used to acquire multiple first microservices involved in the target business scenario and the calling relationship between the multiple first microservices, wherein the multiple first microservices are used to implement the target business to be realized in the target business scenario.

[0083] The region determination module 304 is used to determine a target region where servers corresponding to the plurality of first microservices are located, wherein the server is used to represent a server providing the corresponding first microservice.

[0084] The first determination module 306 is used to determine the remote call time between the multiple first microservices based on the call relationship and the target area, wherein the remote call time is used to indicate the additional call time due to the fact that the servers corresponding to the multiple first microservices are in different areas.

[0085] The second determination module 308 is used to determine the total remote call time consumption of the target business scenario based on the remote call time consumption between the multiple first microservices.

[0086] The device for determining the time consumption of remote calls of microservices provided in the embodiment of the present application can identify which microservices are indispensable components in the process of realizing the target business scenario by analyzing the calling relationship between microservices, and can consider the impact of geographical distance on the time consumption of remote calls of microservices by accurately locating the target area where the server corresponding to each microservice is located. Combined with the above-mentioned calling relationship and target area, the time consumption of each remote call can be accurately calculated, and by aggregating the time consumption of all remote calls, the total time consumption of remote calls in the entire target business scenario can be determined, thereby achieving the purpose of accurately calculating the time consumption that may increase in the process of multi-site and multi-center construction, thereby realizing the technical effect of accurately evaluating the time consumption increase of microservices in the cross-city call scenario, and further solving the technical problem of low accuracy in calculating the time consumption of remote calls of microservices in related technologies.

[0087] Optionally, in the device for determining the time consumption of remote calls of microservices provided in an embodiment of the present application, the area determination module is also used to: determine the first identification information of the target server, wherein the target server is a server corresponding to any first microservice; determine the target area where the target server is located based on the first preset correspondence relationship and the first identification information, wherein the first preset correspondence relationship is used to represent the correspondence between the first identification information and the target area.

[0088] Optionally, in the device for determining the time consumption of a remote call of a microservice provided in an embodiment of the present application, the first determination module is further used to: determine, based on the call relationship and the target area, at least one adjacent first microservice whose corresponding server among multiple first microservices is located in a remote location; based on the second preset corresponding relationship and the target area, determine the time consumption of a remote call of at least one adjacent first microservice, wherein the second preset corresponding relationship is used to represent the time consumption of a remote call between any two areas.

[0089] Optionally, in the device for determining the remote call time consumption of a microservice provided in an embodiment of the present application, the second determination module is further used to: summarize the remote call time consumption between multiple first microservices to obtain a total remote call time consumption.

[0090] Optionally, in the device for determining the time consumption of remote calls of microservices provided in an embodiment of the present application, the relationship acquisition module is also used to: obtain second identification information of multiple first microservices; traverse the topological structure recorded in the graph database to obtain the first node and the second node that match the second identification information; based on the first node and the second node, determine the call relationship from the topological structure.

[0091] Optionally, in the device for determining the time consumption of remote calls of microservices provided in an embodiment of the present application, the relationship acquisition module is also used to: retrieve a call link with the first node as the starting node and the second node as the ending node from the topological structure; and determine the call relationship based on the call link.

[0092] Optionally, in the device for determining the time consumption of remote calls of microservices provided in an embodiment of the present application, the device also includes: a first acquisition module, used to obtain third identification information of multiple second microservices and transaction data of multiple second microservices; a first output module, used to build an initial topology structure based on the third identification information and the transaction data, and output the initial topology structure; a third determination module, used to determine the topology structure associated with the target business scenario in response to receiving an instruction to select the initial topology structure, and store the topology structure in a graph database.

[0093] It should be noted that the above-mentioned modules or units can be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n), and the above-mentioned modules can also be run as part of the device in the computer terminal 10 provided in Example 1.

[0094] Example 3

[0095] An embodiment of the present application may provide an electronic device, Figure 4 is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 4As shown, the electronic device may include: one or more ( Figure 4 (only one is shown) processor 1002, memory 1004, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0096] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0097] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: obtain multiple first microservices involved in the target business scenario and the calling relationship between the multiple first microservices, wherein the multiple first microservices are used to implement the target business to be achieved under the target business scenario; determine the target area where the servers corresponding to the multiple first microservices are located, wherein the server is used to represent the server providing the corresponding first microservice; based on the calling relationship and the target area, determine the remote calling time between the multiple first microservices, wherein the remote calling time is used to represent the additional calling time due to the servers corresponding to the multiple first microservices being in different areas; based on the remote calling time between the multiple first microservices, determine the total remote calling time for the target business scenario.

[0098] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: determine the first identification information of the target server, wherein the target server is a server corresponding to any one of the first microservices; determine the target area where the target server is located based on the first preset correspondence and the first identification information, wherein the first preset correspondence is used to represent the correspondence between the first identification information and the target area.

[0099] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: based on the call relationship and the target area, determine at least one adjacent first microservice whose corresponding server among the multiple first microservices is located in a different location; based on the second preset correspondence relationship and the target area, determine the time consumption of the remote call of at least one adjacent first microservice, wherein the second preset correspondence relationship is used to represent the time consumption of the remote call between any two areas.

[0100] The processor may also call the information and application program stored in the memory through the transmission device to perform the following steps: summarizing the remote call time between multiple first microservices to obtain a total remote call time.

[0101] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: obtain the second identification information of multiple first microservices; traverse the topological structure recorded in the graph database to obtain the first node and the second node matching the second identification information; based on the first node and the second node, determine the calling relationship from the topological structure.

[0102] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: retrieve a call link with the first node as the starting node and the second node as the ending node from the topology structure; and determine the call relationship based on the call link.

[0103] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: obtain the third identification information of multiple second microservices and the transaction data of multiple second microservices; build an initial topology structure based on the third identification information and the transaction data, and output the initial topology structure; in response to receiving an instruction to select the initial topology structure, determine the topology structure associated with the target business scenario, and store the topology structure in a graph database.

[0104] By adopting the embodiment of the present application, a solution for determining the time consumption of remote calls of microservices is provided. By analyzing the calling relationship between microservices, it is possible to identify which microservices are indispensable components in the process of realizing the target business scenario. By accurately locating the target area where the server corresponding to each microservice is located, the impact of geographical distance on the time consumption of remote calls of microservices can be considered. Combining the above calling relationship and target area, the time consumption of each remote call can be accurately calculated, and by summarizing the time consumption of all remote calls, the total time consumption of remote calls in the entire target business scenario can be determined, achieving the purpose of accurately calculating the time consumption that may increase in the process of multi-site and multi-center construction, thereby achieving the technical effect of accurately evaluating the time consumption increase of microservices in cross-city calls, and then solving the technical problem of low accuracy in calculating the time consumption of remote calls of microservices in related technologies.

[0105] It can be understood by those skilled in the art that Figure 4 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 4The structure of the electronic device is not limited. Figure 4 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 4 Different configurations are shown.

[0106] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0107] Example 4

[0108] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the method for determining the time consumption of a remote call of a microservice provided in the first embodiment.

[0109] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0110] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing the steps of a method for determining the time consumption of a remote call of a microservice.

[0111] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0112] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0113] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

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

[0115] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0116] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0117] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for determining the time consumption of remote calls of microservices, characterized in that: include: Acquire multiple first microservices involved in a target business scenario and call relationships between the multiple first microservices, wherein the multiple first microservices are used to implement the target business to be achieved in the target business scenario; Determine a target area where servers corresponding to the plurality of first microservices are located, wherein the servers are servers used to represent servers providing corresponding first microservices; Based on the call relationship and the target area, determine the remote call time between the multiple first microservices, wherein the remote call time is used to represent the additional call time due to the servers corresponding to the multiple first microservices being in different areas; Based on the remote call times between the multiple first microservices, the total remote call time of the target business scenario is determined.

2. The method according to claim 1, characterized in that Determining the target area where the servers corresponding to the multiple first microservices are located includes: Determine first identification information of a target server, wherein the target server is a server corresponding to any one of the first microservices; A target area where the target server is located is determined based on a first preset corresponding relationship and the first identification information, wherein the first preset corresponding relationship is used to represent a corresponding relationship between the first identification information and the target area.

3. The method according to claim 1, characterized in that Determining the remote call time consumption between the plurality of first microservices based on the call relationship and the target area includes: Based on the call relationship and the target area, determining at least one adjacent first microservice whose corresponding server among the plurality of first microservices is located in a different location; Based on the second preset corresponding relationship and the target area, a time consumption of a remote call of the at least one adjacent first microservice is determined, wherein the second preset corresponding relationship is used to represent the time consumption of the remote call between any two areas.

4. The method according to claim 1, characterized in that Determining the total remote call time of the target business scenario based on the remote call time between the multiple first microservices includes: The remote call time consumptions between the multiple first microservices are summarized to obtain the total remote call time consumption.

5. The method according to claim 1, characterized in that Acquiring multiple first microservices involved in a target business scenario and call relationships between the multiple first microservices includes: Obtain second identification information of the multiple first microservices; Traversing the topological structure recorded in the graph database to obtain a first node and a second node matching the second identification information; The calling relationship is determined from the topology structure based on the first node and the second node.

6. The method according to claim 5, characterized in that Determining the calling relationship from the topology structure based on the first node and the second node includes: Retrieving, from the topology structure, a call link with the first node as a starting node and the second node as an ending node; The calling relationship is determined based on the calling link.

7. The method according to claim 5, characterized in that The method further comprises: Obtaining third identification information of multiple second microservices and transaction data of the multiple second microservices; constructing an initial topological structure based on the third identification information and the transaction data, and outputting the initial topological structure; In response to receiving an instruction to select the initial topology structure, the topology structure associated with the target business scenario is determined, and the topology structure is stored in the graph database.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

9. An electronic device, characterized in that: include: A memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 7 when running.

10. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images