Method for determining time consumption of cross-site call of microservice, storage medium and electronic device

Abstract

The application discloses a method for determining off-site calling time consumption of microservices, a storage medium and an electronic device. The method relates to the field of cloud computing, and comprises the following steps: acquiring a plurality of first microservices and a calling relationship between the plurality of first microservices, wherein the plurality of first microservices are used for implementing a target business under a target business scenario; determining a target area where servers corresponding to the plurality of first microservices are located; determining off-site calling time consumption between the plurality of first microservices based on the calling relationship and the target area, wherein the off-site calling time consumption is used for representing additional calling time consumption due to the servers corresponding to the plurality of first microservices being located in different areas; and determining total off-site calling time consumption of the target business scenario based on the off-site calling time consumption between the plurality of first microservices. Through the application, the problem that the accuracy of calculating off-site calling time consumption of microservices is low in the prior art is solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of cloud computing, in particular to a method for determining time consumption of cross-site invocation of microservices, a storage medium and an electronic device. BACKGROUND

[0002] In traditional data center architecture, enterprises usually adopt a "two sites and three centers" strategy to ensure data security and business continuity, that is, two main data centers are set up in one city to achieve load balancing and failover, and a disaster recovery data center is set up in another city to prevent city-level disasters. However, with the continuous expansion of business scale and the acceleration of globalization process, 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 a "multi-site and multi-center" architecture strategy, that is, multiple data centers are built in multiple cities, and each city may contain multiple data centers, to further improve the availability and performance of the system. This architecture strategy not only can better disperse risks, but also can utilize network resources in different cities to provide more stable and faster services for users.

[0003] However, when microservices migrate from "two sites and three centers" to "multi-site and multi-center", the frequency of cross-city invocation will increase significantly, which will directly affect the response time and overall performance of the service. Cross-city invocation involves network transmission between different cities, which will increase additional time consumption, thereby affecting user experience and business efficiency. Therefore, how to accurately assess the time consumption growth that may be caused by cross-city invocation of microservices during the migration from "two sites and three centers" to "multi-site and multi-center" has become an important problem that enterprises need to solve.

[0004] Currently, there is no effective solution to the problem of low accuracy of calculating time consumption of cross-site invocation of microservices in the related art. SUMMARY

[0005] The main purpose of the present application is to provide a method for determining time consumption of cross-site invocation of microservices, a storage medium and an electronic device, to solve the problem of low accuracy of calculating time consumption of cross-site invocation of microservices in the related art.

[0006] In order to achieve the above object, according to one aspect of the present application, a method for determining time consumption of cross-region calling of microservices is provided. The method comprises: obtaining a plurality of first microservices involved in a target business scenario and a calling relationship between the plurality of first microservices, wherein the plurality of first microservices are used to implement a target business to be achieved in the target business scenario; determining 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; determining cross-region calling time consumption between the plurality of first microservices based on the calling relationship and the target region, wherein the cross-region calling time consumption is used to represent additional calling time consumption due to the servers corresponding to the plurality of first microservices being located in different regions; and determining total cross-region calling time consumption of the target business scenario based on the cross-region calling time consumption between the plurality of first microservices.

[0007] Further, the determination of the target region where the servers corresponding to the plurality of first microservices are located comprises: determining first identification information of a target server, wherein the target server is a server corresponding to any one of the first microservices; and determining the target region 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 a correspondence relationship between the first identification information and the target region.

[0008] Further, the determination of the cross-region calling time consumption between the plurality of first microservices based on the calling relationship and the target region comprises: determining at least one adjacent first microservice whose corresponding server is located in a cross-region based on the calling relationship and the target region; and determining cross-region calling time consumption of the at least one adjacent first microservice based on a second preset correspondence relationship and the target region, wherein the second preset correspondence relationship is used to represent cross-region calling time consumption between any two regions.

[0009] Further, the determination of the total cross-region calling time consumption of the target business scenario based on the cross-region calling time consumption between the plurality of first microservices comprises: aggregating the cross-region calling time consumption between the plurality of first microservices to obtain the total cross-region calling time consumption.

[0010] Further, the obtaining of the plurality of first microservices involved in the target business scenario and the calling relationship between the plurality of first microservices comprises: obtaining second identification information of the plurality of first microservices; traversing a topology structure recorded in a graph database to obtain a first node and a second node matched with the second identification information; and determining the calling relationship from the topology structure based on the first node and the second node.

[0011] Further, the determination of the calling relationship from the topology structure based on the first node and the second node comprises: calling a calling link from the topology structure with the first node as a starting node and the second node as an ending node; and determining the calling relationship based on the calling link.

[0012] Further, the method further includes: obtaining third identification information of the plurality of second microservices and transaction data of the plurality of 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 a selection instruction for the initial topology structure, determining a topology structure associated with the target business scenario, and storing the topology structure to the graph database.

[0013] To achieve the above object, according to another aspect of the present application, a device for determining off-site calling time consumption of microservices is provided. The device comprises: a relationship obtaining module, configured to obtain a plurality of first microservices involved in a target business scenario and a calling relationship between the plurality of first microservices, wherein the plurality of first microservices are used to implement a target business to be achieved in the target business scenario; a region determining module, configured 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; a first determining module, configured to determine off-site calling time consumption between the plurality of first microservices based on the calling relationship and the target region, wherein the off-site calling time consumption is used to represent additional calling time consumption due to the servers corresponding to the plurality of first microservices being located in different regions; and a second determining module, configured to determine total off-site calling time consumption of the target business scenario based on the off-site calling time consumption between the plurality of first microservices.

[0014] To achieve the above object, according to another aspect of the present application, a computer readable storage medium is provided, which comprises a stored executable program, wherein the computer readable storage medium controls a device where the computer readable storage medium is located to execute the method in various embodiments of the present application when the executable program is run.

[0015] To achieve the above object, according to another aspect of the present application, an electronic device is provided, which comprises: a memory storing an executable program; and a processor configured to run the program, wherein the program is executed to perform the method in various embodiments of the present application when the program is run.

[0016] To achieve the above object, according to another aspect of the present application, a computer program product is provided, which comprises computer instructions, wherein the computer instructions are executed by a processor to implement the method in various embodiments of the present application.

[0017] In the embodiment of the present application, the method comprises the following steps: acquiring a plurality of first microservices involved in a target business scenario and a calling relationship between the plurality of first microservices; determining target areas where servers corresponding to the plurality of first microservices are located; determining cross-region calling time consumption between the plurality of first microservices based on the calling relationship and the target areas; and determining total cross-region calling time consumption of the target business scenario based on the cross-region calling time consumption between the plurality of first microservices. By analyzing the calling relationship between microservices, it can be identified which microservices are indispensable components in the implementation process of the target business scenario. By accurately locating the target areas where the servers corresponding to each microservice are located, the influence of geographical distance on the cross-region calling time consumption of microservices can be considered. In combination with the above calling relationship and target areas, the cross-region calling time consumption of each time can be accurately calculated, and by summarizing all cross-region calling time consumption, the total cross-region calling time consumption under the target business scenario can be determined, thereby achieving the technical effect of accurately calculating the time consumption that may be increased in the multi-region and multi-center construction process, and accurately evaluating the time consumption growth of microservices in the cross-city calling scenario, thereby solving the technical problem of low accuracy in calculating the cross-region calling time consumption of microservices in the related art. BRIEF DESCRIPTION OF DRAWINGS

[0018] The accompanying drawings, which form a part of this application, are included to provide a further understanding of the application and are incorporated in and constitute a part of this application. The embodiments of this application illustrate the embodiments of the present application and the best mode presently contemplated by the inventor(s) of carrying out the application, and are, therefore, to be considered as illustrative and not restrictive of the application as claimed. In the drawings:

[0019] Figure 1 Fig. 1 shows a hardware structure block diagram of a computer terminal for implementing a cross-region calling time consumption determination method of microservices;

[0020] Figure 2 Fig. 2 is a flowchart of a cross-region calling time consumption determination method of microservices according to an embodiment of the present application;

[0021] Figure 3 Fig. 3 is a schematic diagram of a cross-region calling time consumption determination device according to an embodiment of the present application;

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

[0023] In order for those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should be 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 in the above drawings are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to only those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

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

[0026] Cross-city call: the data center involved in service calls is in different cities, which will increase additional time consumption due to network transmission.

[0027] Two-geographical three-centers: two main data centers are built in one city, and a disaster recovery data center is built in another city that is far away.

[0028] Multi-geographical multi-centers: multiple data centers are built in multiple cities without geographical restrictions, and each city may have n data centers.

[0029] Full link monitoring: a systematic monitoring method that records every link from user request to backend microservice to ensure system performance and reliability, and transmits transaction identifiers and other information along with the transaction.

[0030] Business label: a label set according to the business scenario, set on the microservice, and transmitted along with the full link monitoring (full link dyeing technology).

[0031] It should be noted that the information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for display, analyzed data, etc.) involved in the present application are information and data authorized by the user or authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with relevant laws, regulations and standards, necessary security measures are taken, do not violate public order and good customs, and provide corresponding operation portal for user to choose authorization or refusal. For example, the system and related users or institutions have an interface between them, providing a corresponding operation portal for users to choose to agree or refuse automatic decision results; if the user chooses to refuse, the expert decision-making process is entered.

[0032] Embodiment 1

[0033] According to an embodiment of this application, an embodiment of a method for determining the time consumption of remote calls to microservices is also provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0034] The method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, computer terminal, or similar computing device. Figure 1 A hardware block diagram of a computer terminal (or mobile device) for implementing a method to determine the time consumption of remote calls to microservices is shown. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), 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 a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0035] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0036] The memory 104 can be used to store software programs of application software and modules, such as program instructions / data storage means corresponding to the off-site invocation time consumption determination method of the microservice in the embodiments 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, implements the off-site invocation time consumption determination method of the microservice as described above. The memory 104 can include a high-speed random access memory, and can also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 104 can further include a memory remotely arranged with respect to the processor 102, which can be connected to the computer terminal 10 through 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 a combination thereof.

[0037] The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network can 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 (Radio Frequency, RF) module, which is used to communicate with the Internet in a wireless manner.

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

[0039] Under the above-mentioned operating environment, the present application provides an off-site invocation time consumption determination method of a microservice as shown in Figure 2 Figure 2 is a flowchart of an off-site invocation time consumption determination method of a microservice according to an embodiment of the present application.

[0040] In step S202, a plurality of first microservices involved in a target business scenario and a calling relationship between the plurality of first microservices are acquired, wherein the plurality of first microservices are used to implement a target business to be achieved in the target business scenario.

[0041] ​The target business scenario can be a business scenario that needs to evaluate time consumption growth. For example, a transfer business process of an online bank system, that is, a whole set of operations from user initiation of a transfer request to transaction confirmation, fund transfer, balance update, etc., can be regarded as a target business scenario, but is not limited thereto. The target business scenario is usually composed of a series of microservice call links that jointly achieve a specific business target. The first microservice can be each independent microservice that directly participates in business implementation in the target business scenario. For example, the first microservice can include a transaction confirmation microservice, a fund transfer microservice, a balance update microservice, etc., but is not limited thereto. The target business can be the final business target or function to be achieved by the target business scenario. For example, in the bank transfer business scenario, the target business is to achieve the transfer of user funds from one account to another, but is not limited thereto.

[0042] In an optional embodiment, considering that the related art usually only considers one-time call time consumption between a direct number of microservices, and ignores real call links and multi-level call relationships in a target business scenario, which leads to inaccurate and incomplete time consumption estimation, and further considering that in a "multi-city multi-center" data center layout, microservices can be distributed in different cities, and cross-city calls can introduce additional network delay, only when it is clear which microservices will participate in cross-city calls, the specific impact of such a layout on business time consumption can be accurately calculated. Therefore, the cross-region call time consumption calculation system (hereinafter referred to as the calculation system) can first obtain a plurality of first microservices involved in a target business scenario and a call relationship between the plurality of first microservices, thereby providing a data basis for subsequent cross-region call time consumption calculation, and further improving the accuracy of calculating cross-region call time consumption.

[0043] For example, in order to more accurately obtain a plurality of first microservices involved in a target business scenario and a call relationship between the plurality of first microservices, the calculation system can pre-deploy a full-link monitoring program that can record each link from a user request to a backend microservice, including but not limited to service response time, request time, microservice name, cluster name, application name, and transaction identifier, etc. important information. Since the data monitored by the full-link monitoring program can contain a large amount of redundant data, in order to filter out the call links related to the target business scenario, the calculation system can add a business tag to the monitoring data. The business tag can be set at the starting point of the user request (i.e., the entry service) to mark all microservice calls in the business scenario, thereby filtering out data directly related to the target business scenario from the monitoring data. Subsequently, the calculation system can restore the plurality of microservice call relationships in the target business scenario based on the data directly related to the target business scenario, thereby providing a data basis for subsequent cross-region call time consumption calculation.

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

[0045] The server can be a physical or virtual computing device that carries and processes microservice requests. In a microservice architecture, each microservice can run on a group of servers located in a data center or cloud environment, responsible for executing the specific functions defined by the microservice. The server can be a traditional physical server, or a virtual server dynamically created and managed in a cloud platform. In a "multi-city multi-center" data center layout, servers can be distributed in different geographic locations to provide high availability, disaster recovery capability and proximity to user service response. The target region can be a specific geographic region where the server is located. For example, in a "multi-city multi-center" architecture, the target region can 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-city multi-center" architecture, servers for providing the first microservice can be distributed in different cities or regions, in a cross-city invocation scenario, the invocation between the plurality of first microservices can be affected by network transmission delay, and traditional time-consuming calculation methods often lack consideration of the location information of the servers running the microservices, thereby ignoring the influence of geographic distance on network transmission time consumption, resulting in poor accuracy of microservice cross-region invocation time consumption calculation. Therefore, by determining the target region where the servers corresponding to the first microservices are located, the computing system can use a pre-established inter-city network delay database to accurately calculate the additional time consumption of cross-city invocation, thereby quantitatively evaluating the network delay in the entire business scenario.

[0047] For example, in order to more accurately determine the target region where the servers corresponding to the plurality of first microservices are located, the computing system can pre-construct a database for recording detailed information of a plurality of microservices, including the name of the microservice, the cluster name, the application name, etc., and the physical location of the servers corresponding to the plurality of microservices. Subsequently, the computing system can construct a topology structure of microservice invocation in the target business scenario based on the plurality of first microservices and the invocation relationship between the plurality of first microservices obtained in the foregoing steps. Then, the computing system can extract the information of each microservice from the topology structure, and match the extracted microservice information with the data in the database, so as to confirm the target region where the servers corresponding to each microservice are located.

[0048] In step S206, the cross-region calling time consumption between the plurality of first microservices is determined based on the calling relationship and the target region, where the cross-region calling time consumption is used to represent the additional calling time consumption due to the servers corresponding to the plurality of first microservices being located in different regions.

[0049] The cross-region calling time consumption mentioned above can refer to, in a microservice architecture, when one microservice calls another microservice located in a different geographic region, the additional delay time generated due to the data needing to be transmitted from one region to another region through a network. Such time consumption is mainly caused by network transmission delay, possible cross-region routing delay, and network quality difference between different data centers, and the like.

[0050] In an optional embodiment, considering that under the "multi-region multi-center" architecture, the communication between microservices can cross different geographic locations, the traditional time consumption calculation method is difficult to accurately reflect the network delay of the microservices in cross-region calling, therefore, the computing system determines the cross-region calling time consumption between the plurality of first microservices based on the calling relationship and the target region, which can improve the calculation accuracy of the cross-region calling time consumption of the first microservice under the "multi-region multi-center" architecture. The above step quantifies the network delay of the first microservice in cross-region calling, which can help the computing system to understand which service calling will increase the response time due to the geographic location factor, so as to make more optimal decisions in service deployment, architecture design and resource allocation.

[0051] For example, it can be assumed that the computing system has constructed the topology structure of the microservice transaction through the foregoing steps, which can be an N-ary tree, where the points of the N-ary tree are the information of the microservices (microservice name, cluster name, application name, and the like), and the edges of the N-ary tree are the information of the microservice calling relationship (identity identifier of the business scenario, starting point, and ending point). The computing system can also construct a maintenance table containing network delays between different regions based on the historical data of the microservice calling. For each edge in the N-ary tree determined to be cross-region calling, the computing system can query the maintenance table to obtain the network delay between the regions where the calling parties are located, and add the network delay value to the original time consumption of the calling process to obtain the total time consumption of the cross-region calling. Through this calculation, the specific influence of the cross-region calling on the performance of the microservice architecture can be quantified.

[0052] In step S208, the total cross-region calling time consumption of the target business scenario is determined based on the cross-region calling time consumption between the plurality of first microservices.

[0053] The total cross-region calling time can be a result of adding up the additional time consumed by all cross-region calls in the target business scenario. In the target business scenario, a request can need to go through the processing of multiple microservices, some of which can be local calls within the same geographical region, and some of which can cross different regions, i.e., cross-region calls. The total cross-region calling time quantifies the sum of the additional time consumed by all cross-region calls, providing an important reference index for the overall performance of the business scenario.

[0054] In an optional embodiment, considering that in the "multi-region multi-center" architecture, a business scenario often involves the calling of multiple microservices, and due to the existence of network transmission delay, especially when the calls cross different geographical regions, the time consumed by each call will increase, if the time consumed by all cross-region calls is not summarized, the calculation of the time consumed by cross-region calls for the entire business scenario by the computing system can be inaccurate, and the traditional time consumption calculation method is difficult to summarize and analyze the time consumed by all cross-region calls in the entire business scenario, resulting in inaccurate overall performance evaluation. Therefore, the computing system can determine the total cross-region calling time of the target business scenario based on the cross-region calling time between the multiple first microservices. For example, the computing system can calculate the specific time consumed by each cross-region call based on the foregoing steps, at this time, the computing system can summarize the specific time consumed by each cross-region call to obtain the total cross-region calling time of the target business scenario.

[0055] Optionally, in the method for determining the cross-region calling time of the microservice provided in the embodiments of the present application, the target region where the server corresponding to the multiple first microservices is located is determined, including: determining first identification information of a target server, wherein the target server is a server corresponding to any first microservice; determining the target region 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 relationship between the first identification information and the target region.

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

[0057] In an optional embodiment, considering that in the micro-service architecture, multiple micro-services can be included, and each micro-service can run on a different server, in order to accurately distinguish the server corresponding to each micro-service, and further improve the accuracy of the time-consuming calculation of the cross-region call of the micro-service, the computing system can set a unique identity information for each server in advance. In order to accurately determine the target region where the server corresponding to the multiple first micro-services is located, the computing system can first determine the identity of the server corresponding to any first micro-service, that is, the first identity information of the target server. Since the first preset correspondence establishes the association between the first identity information and the target region, the computing system can further determine the target region where the target server is located based on the first preset correspondence and the first identity information. Based on the above steps, the computing system can more accurately determine the target region where the target server is located, thereby ensuring the accuracy of the subsequent cross-region call time-consuming calculation.

[0058] For example, under the "multi-region multi-center" architecture, the computing system can set a unique identifier for each server based on the Internet Protocol address of each server, which can be used to distinguish different servers. Subsequently, the computing system can construct a maintenance table that can include the first identity information of each server and the corresponding relationship between the target region where the server is located, thereby constructing the first preset correspondence. If the computing system needs to evaluate the time-consuming of a first micro-service call, it can directly query the specific region where the server corresponding to the first micro-service is located from the first preset correspondence based on the identity information of the server.

[0059] Optionally, in the method for determining the cross-region call time-consuming of the micro-service provided in the embodiments of the present application, the cross-region call time-consuming between the multiple first micro-services is determined based on the call relationship and the target region, which includes: determining at least one adjacent first micro-service whose corresponding server is in a cross-region based on the call relationship and the target region; determining the cross-region call time-consuming of the at least one adjacent first micro-service based on the second preset correspondence and the target region, wherein the second preset correspondence is used to represent the cross-region call time-consuming between any two regions.

[0060] The adjacent first micro-service can be another first micro-service directly called by a first micro-service in a business process or transaction. The second preset correspondence can be a correspondence between the cross-region call time-consuming of any two regions (data centers or server cluster locations).

[0061] In an optional embodiment, considering the complex deployment scenario of "multi-center in multiple regions", microservices can be distributed in multiple different regions, and the difference in network delay between different regions affects the accuracy of the calculation of the time consumption of cross-region calls. In order to accurately evaluate the influence of network delay on microservice calls, the computing system can pre-build the second preset correspondence to determine the cross-region call time consumption between any two regions. Based on the call relationship and the target region, the computing system can accurately find out those adjacent microservices deployed in different geographical regions (i.e. cross-region) and having direct call relationship. Then, the computing system can combine the target region (i.e. the geographical region where the caller and the callee are located) and the second preset correspondence to calculate the cross-region call time consumption of the adjacent microservices, which not only includes the pure network transmission time, but also may cover the additional processing time caused by cross-region calls, thereby improving the calculation accuracy of the computing system for the cross-region call time consumption of microservices.

[0062] For example, the computing system can construct the topology of the call relationship of the plurality of first microservices based on the foregoing steps, and can pre-build 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 contains microservice A, and the computing system determines that the adjacent microservice directly interacting with microservice A in the target region is microservice B by analyzing the topology. If microservice B is deployed in a geographical region different from the target region, the communication between microservice A and microservice B constitutes a cross-region call. In this embodiment, it can be further assumed that the region where microservice B is located is region C which is different from the target region, and at this time, the computing system can query the data table to obtain the time consumption data between the target region and region C.

[0063] Optionally, in the method for determining the cross-region call time consumption of the microservices provided in the embodiments of the present application, the total cross-region call time consumption of the target business scenario is determined based on the cross-region call time consumption between the plurality of first microservices, comprising: aggregating the cross-region call time consumption between the plurality of first microservices to obtain the total cross-region call time consumption.

[0064] In an optional embodiment, it is considered that in a "multi-geographical multi-center" microservice architecture, a business transaction can involve calls between multiple microservices, some of which can cross different geographical regions, i.e., cross-region calls. It should be noted that each cross-region call can increase the additional time consumption due to network delay, and if the time consumption of a single call is only concerned without time consumption aggregation, the cumulative network delay effect in the overall transaction process can be ignored, thereby reducing the calculation accuracy of the overall cross-region call time consumption in the current business scenario. Therefore, the computing system can aggregate the cross-region call time consumption between multiple first microservices to obtain the total cross-region call time consumption, so as to improve the accuracy of the cross-region call time consumption in the above microservice architecture.

[0065] Optionally, in the method for determining the cross-region call time consumption of the microservice provided in the embodiments of the present application, the multiple first microservices involved in the target business scenario and the call relationship between the multiple first microservices are obtained, including: obtaining second identification information of the multiple first microservices; traversing the topology structure recorded in the graph database to obtain a first node and a second node matched with the second identification information; and determining the call relationship from the topology structure based on the first node and the second node.

[0066] The second identification information can be an attribute or feature for uniquely identifying a microservice node in the graph database. For example, the second identification information can include at least one or more of a service name, a version number, a cluster name, an application name, or an identity identifier of a service instance, but is not limited thereto. The graph database can be a database for storing the call relationship between services. The first node can refer to a node corresponding to the first microservice in the second identification information in the topology structure of the graph database. The second node can refer to a node corresponding to the microservice called by the first microservice in the topology structure of the graph database.

[0067] In an optional embodiment, in order to accurately locate the nodes related to the multiple first microservices in the graph database and then analyze the call relationship between the multiple first microservices, the computing system can first obtain the second identification information of the multiple first microservices. Since the topology structure of the entire microservice architecture is stored in the graph database, the computing system can traverse the topology structure recorded in the graph database to find the nodes matched with the second identification information in the graph database, i.e., the first node and the second node. Once the first node and the second node are found through traversal, the computing system can determine the call relationship between the multiple first microservices and the multiple first microservices based on the path relationship of the 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, wherein the cluster name of service A can be X, and the cluster name of service B can be Y, and service A and service B both take the cluster name in which each is located as the second identification information. In the graph database, the calling relationship between microservices is modeled as nodes and edges in the graph. By traversing the topology structure recorded in the graph database, the computing system can query the nodes that satisfy the second identification information of service A, that is, the node a corresponding to service A and the node b corresponding to service B, then the node a is the first node and the node b is the second node, at this time the computing system can determine the calling relationship between microservice A and service B, that is, service A calls service B.

[0069] Optionally, in the method for determining the time consumption of cross-site calling of microservices provided in the embodiments of the present application, the calling relationship is determined from the topology structure based on the first node and the second node, comprising: calling the calling link from the first node as the starting node and the second node as the ending node from the topology structure; and determining the calling relationship based on the calling link.

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

[0071] In an optional embodiment, considering that in the microservice architecture, the calling relationship between microservices constitutes a complex network, that is, a topology structure. When the calling relationship between the first node and the second node needs to be analyzed, the calling link between the two nodes needs to be accurately located from the topology structure, therefore, the computing system can first call the calling link from the first node as the starting node and the second node as the ending node from the topology structure, and can further determine the calling relationship based on the calling 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 the microservice A corresponding to node a and the microservice B corresponding to node b, the computing system can take node a as the starting node and node b as the ending node, and use a graph database query statement to call the calling link from node a to node b from the topology structure, assuming that the link is as follows: node a-node c-node d-node b, which indicates that service A successively calls service C, service D, and finally service B, 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 cross-site calling of microservices provided in the embodiments of the present application, the method further comprises: obtaining third identification information of the plurality of second microservices and transaction data of the plurality of 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 a selection instruction for the initial topology structure, determining a topology structure associated with a target business scenario, and storing the topology structure to a graph database.

[0074] The second microservice can refer to a microservice other than the entry microservice in the microservice architecture, which can directly or indirectly participate in the processing of the business scenario. The third identification information can be the unique identity information of the second microservice, which is used to distinguish different second microservices. The transaction data can be specific data records generated by microservice calling in one or more business transactions, for example, the transaction data can include at least one or more of the following: transaction time, transaction type, transaction amount, identification information of the calling party and the service party, calling state (success / failure), and calling time consumption, but not limited thereto. The initial topology structure can be the original mapping of the calling relationship between the plurality of microservices without specifying the business scenario. The selection instruction can be an instruction for filtering and focusing the microservice calling relationship in the initial topology structure according to the required business scenario. For example, the selection instruction can be a specified business label, but not limited thereto.

[0075] In an optional embodiment, considering that in the microservice architecture, each service can have multiple instances, and the calling relationship between services is complex. Therefore, the computing system can obtain the third identification information of the plurality of second microservices and the transaction data, so as to more accurately identify and manage the running state of different microservice instances, i.e., 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 the business process, the computing system can construct an initial topology structure based on the third identification information and the transaction data, and output the initial topology structure. Further considering that in the microservice architecture, there can be multiple different business scenarios. When receiving the selection instruction, the computing system can determine a topology structure related to the target business scenario, and store the topology structure to the graph database, so as to realize the persistent and structured storage of data, which not only facilitates 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 under the current business scenario through a full-link dyeing technology to obtain monitoring data. The computing system can analyze the monitoring data to extract third identification information of the second microservice under the current business scenario and transaction data related to the microservice call. Subsequently, based on the collected third identification information and transaction data, the computing system can construct an initial topology structure of the microservice architecture, which includes the calling relationship between the plurality of second microservices. The computing system can output the constructed initial topology structure in a visual form. When receiving a selection instruction containing the business label A, the computing system can filter all microservice calling relationships associated with the business label A from the initial topology structure to construct a topology subgraph focusing on the target business scenario corresponding to the business label A. Finally, the computing system can store the filtered topology structure associated with the target business scenario in the graph database to support subsequent calculation of the cross-region calling time, thereby improving the accuracy of the cross-region calling time.

[0077] The method for determining the cross-region calling time of the microservice provided in the embodiments of the present application can identify which microservices are indispensable components in the implementation process of the target business scenario by analyzing the calling relationship between the microservices. The influence of the geographical distance on the cross-region calling time of the microservice can be considered by accurately locating the target region where the server corresponding to each microservice is located. In combination with the calling relationship and the target region, the cross-region calling time of each cross-region call can be accurately calculated, and the total cross-region calling time under the target business scenario can be determined by aggregating all the cross-region calling times. The technical effect of accurately calculating the increased calling time in the multi-region and multi-center construction process is achieved, thereby accurately evaluating the increase of the calling time of the microservice in the cross-city calling scenario, and the technical problem of low accuracy in calculating the cross-region calling time of the microservice in the related art is solved.

[0078] 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 the logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown herein.

[0079] Embodiment 2

[0080] The embodiments of the present application also provide a device for determining the cross-region calling time of a microservice. It should be noted that the device for determining the cross-region calling time of a microservice provided in the embodiments of the present application can be used to execute the method for determining the cross-region calling time of a microservice provided in the embodiments of the present application. The device for determining the cross-region calling time of a microservice provided in the embodiments of the present application is introduced as follows.

[0081] According to the embodiment of the present application, a device for implementing the method for determining the time consumption of cross-region calling of microservices is also provided, Figure 3 is a schematic diagram of a device for determining the time consumption of cross-region calling of microservices according to the embodiment of the present application, as Figure 3 shown, the device comprises:

[0082] The relationship obtaining module 302 is configured to obtain a plurality of first microservices involved in a target business scenario and a calling relationship between the plurality of first microservices, wherein the plurality of first microservices are used to implement a target business to be achieved in the target business scenario.

[0083] The region determining module 304 is configured 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 determining module 306 is configured to determine the time consumption of cross-region calling between the plurality of first microservices based on the calling relationship and the target region, wherein the time consumption of cross-region calling is used to represent the additional calling time consumption due to the servers corresponding to the plurality of first microservices being located in different regions.

[0085] The second determining module 308 is configured to determine the total time consumption of cross-region calling of the target business scenario based on the time consumption of cross-region calling between the plurality of first microservices.

[0086] The device for determining the time consumption of cross-region calling of microservices provided by the embodiment of the present application can identify which microservices are indispensable components in the implementation process of the target business scenario by analyzing the calling relationship between the microservices, can consider the influence of geographical distance on the time consumption of cross-region calling of the microservices by accurately positioning the target region where the servers corresponding to each microservice are located, can accurately calculate the time consumption of each cross-region calling by combining the calling relationship and the target region, and can determine the total time consumption of cross-region calling of the entire target business scenario by aggregating all the time consumption of cross-region calling, thereby achieving the technical effect of accurately evaluating the time consumption growth of the microservices in the cross-city calling scenario, and further solving the technical problem of low accuracy in calculating the time consumption of cross-region calling of the microservices in the related art.

[0087] Optionally, in the device for determining the time consumption of cross-region calling of microservices provided by the embodiment of the present application, the region determining module is further configured to: determine first identification information of a target server, wherein the target server is a server corresponding to any one of the first microservices; and determine the target region 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 relationship between the first identification information and the target region.

[0088] Optionally, in the device for determining cross-region calling time consumption of microservices provided in the embodiments of the present application, the first determining module is further configured to: determine at least one adjacent first microservice whose corresponding server is in a cross-region based on the calling relationship and the target region; and determine the cross-region calling time consumption of the at least one adjacent first microservice based on a second preset correspondence relationship and the target region, where the second preset correspondence relationship is used to represent the cross-region calling time consumption between any two regions.

[0089] Optionally, in the device for determining cross-region calling time consumption of microservices provided in the embodiments of the present application, the second determining module is further configured to: aggregate the cross-region calling time consumption between the plurality of first microservices to obtain total cross-region calling time consumption.

[0090] Optionally, in the device for determining cross-region calling time consumption of microservices provided in the embodiments of the present application, the relationship obtaining module is further configured to: obtain second identification information of the plurality of first microservices; traverse the topological structure recorded in the graph database to obtain a first node and a second node matched with the second identification information; and determine the calling relationship from the topological structure based on the first node and the second node.

[0091] Optionally, in the device for determining cross-region calling time consumption of microservices provided in the embodiments of the present application, the relationship obtaining module is further configured to: call a calling link with the first node as a starting node and the second node as an ending node from the topological structure; and determine the calling relationship based on the calling link.

[0092] Optionally, in the device for determining cross-region calling time consumption of microservices provided in the embodiments of the present application, the device further includes: a first obtaining module configured to obtain third identification information of the plurality of second microservices and transaction data of the plurality of second microservices; a first output module configured to construct an initial topological structure based on the third identification information and the transaction data, and output the initial topological structure; and a third determining module configured to determine a topological structure associated with a target business scenario in response to receiving a selection instruction for the initial topological structure, and store the topological structure to the graph database.

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

[0094] Embodiment 3

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

[0096] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the methods and apparatus in the embodiments of this application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby implementing the above-described methods. The memory may include high-speed random access memory, and may also include 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 memory remotely located relative to the processor, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0097] The processor can invoke information and applications stored in the memory through the transmission device to perform the following steps: obtaining multiple first microservices involved in the target business scenario and the calling 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; determining the target region 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; determining the cross-regional call time between the multiple first microservices based on the calling relationships and the target region, wherein the cross-regional call time is used to represent the additional call time due to the servers corresponding to the multiple first microservices being located in different regions; and determining the total cross-regional call time of the target business scenario based on the cross-regional call time between the multiple first microservices.

[0098] The processor can also invoke information and applications stored in the memory through the transmission device to perform the following steps: determining the first identification information of the target server, wherein the target server is the server corresponding to any first microservice; determining the target region 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 region.

[0099] The processor can also invoke information and applications stored in the memory via the transmission device to perform the following steps: based on the call relationship and the target region, determine at least one adjacent first microservice whose server is located in a different location among a plurality of first microservices; based on the second preset correspondence relationship and the target region, determine the cross-regional call time of at least one adjacent first microservice, wherein the second preset correspondence relationship is used to represent the cross-regional call time between any two regions.

[0100] The processor can further call information and application programs stored in the memory through the transmission device to perform the following steps: aggregating time consumption of cross-region calls between the plurality of first microservices to obtain total cross-region call time consumption.

[0101] The processor can further call information and application programs stored in the memory through the transmission device to perform the following steps: obtaining second identification information of the plurality of first microservices; traversing the topology structure recorded in the graph database to obtain a first node and a second node matched with the second identification information; determining the call relationship from the topology structure based on the first node and the second node.

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

[0103] The processor can further call information and application programs stored in the memory through the transmission device to perform the following steps: obtaining third identification information of the plurality of second microservices and transaction data of the plurality of 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 a selection instruction for the initial topology structure, determining a topology structure associated with a target business scenario, and storing the topology structure to the graph database.

[0104] By analyzing the call relationship between the microservices, it can be identified which microservices are indispensable components in the implementation process of the target business scenario. By accurately positioning the target area where the server corresponding to each microservice is located, the influence of geographical distance on the cross-region call time consumption of the microservice can be considered. In combination with the above call relationship and target area, the time consumption of each cross-region call can be accurately calculated, and by aggregating all cross-region call time consumptions, the total cross-region call time consumption under the target business scenario can be determined. The technical effect of accurately evaluating the time consumption growth of the microservice in the cross-city calling scenario is achieved, and the technical problem of low accuracy in calculating the cross-region call time consumption of the microservice in the related art is solved.

[0105] Those skilled in the art can understand that Figure 4 The structure shown is only schematic, and the electronic device can also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet Device (MID), a PAD, and the like. Figure 4It does not cause limitation to the structure of the electronic device. For example, the electronic device can further include more or less components (such as a network interface, a display device, etc.) or have a different configuration from that shown in Figure 4 Figure 4

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

[0107] Embodiment 4

[0108] The embodiments of the present application further provide a storage medium. Optionally, in the embodiment, the storage medium can be used to save the program code executed by the method for determining the time consumption of the remote invocation of the micro service provided in the embodiment 1.

[0109] Optionally, in the embodiment, the storage medium can be located in any one of the computer terminals in the computer terminal group in the computer network, or in any one of the mobile terminals in the mobile terminal group.

[0110] The present application further provides a computer program product adapted to execute the steps of the method for determining the time consumption of the remote invocation of the micro service when executed on a data processing device.

[0111] The serial numbers of the embodiments of the present application are only for description, 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 focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0113] In the several embodiments provided by the present application, it should be understood that the disclosed technology can be implemented in other ways. Of course, the unit division in the above device embodiment is only a logical function division, and there can be another division manner during actual implementation; for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, units or modules, and can be electrical or other forms.

[0114] ​​The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

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

[0116] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part of the prior art that contributes to the technical solutions or all or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk, and various program code storage media.

[0117] The above is only the preferred embodiment of the present application, and it should be pointed out that for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, and these improvements and refinements should be considered as the protection scope of the present application.

Claims

1. A method for determining time consumption of cross-location invocation of microservices, characterized in that, The method comprises the following steps: obtaining a plurality of first microservices involved in a target business scenario and a calling relationship between the plurality of first microservices, wherein the plurality of first microservices are used to implement a target business to be achieved in the target business scenario; determining a target area where servers corresponding to the plurality of first microservices are located, wherein the servers are used to represent servers providing the corresponding first microservices; based on the calling relationship and the target area, determining cross-region calling time consumption between the plurality of first microservices, wherein the cross-region calling time consumption is used to represent additional calling time consumption due to the servers corresponding to the plurality of first microservices being located in different areas; based on the cross-region calling time consumption between the plurality of first microservices, determining total cross-region calling time consumption of the target business scenario.

2. The method of claim 1, wherein, Determining the target area where the servers corresponding to the plurality of first microservices are located comprises: determining first identification information of a target server, wherein the target server is a server corresponding to any one of the first microservices; based on a first preset correspondence relationship and the first identification information, determining the target area where the target server is located, wherein the first preset correspondence relationship is used to represent a correspondence relationship between the first identification information and the target area.

3. The method of claim 1, wherein, Based on the calling relationship and the target area, determining the cross-region calling time consumption between the plurality of first microservices, comprises: based on the calling relationship and the target area, determining at least one adjacent first microservice whose corresponding server is located in a cross-region among the plurality of first microservices; based on a second preset correspondence relationship and the target area, determining cross-region calling time consumption of the at least one adjacent first microservice, wherein the second preset correspondence relationship is used to represent the cross-region calling time consumption between any two areas.

4. The method of claim 1, wherein, Based on the cross-region calling time consumption between the plurality of first microservices, determining total cross-region calling time consumption of the target business scenario, comprises: summarizing the cross-region calling time consumption between the plurality of first microservices to obtain the total cross-region calling time consumption.

5. The method of claim 1, wherein, Obtaining a plurality of first microservices involved in a target business scenario and a calling relationship between the plurality of first microservices, comprises: obtaining second identification information of the plurality of first microservices; traversing a topology structure recorded in a graph database to obtain a first node and a second node matched with the second identification information; based on the first node and the second node, determining the calling relationship from the topology structure.

6. The method of claim 5, wherein, Based on the first node and the second node, determining the calling relationship from the topology structure, comprises: calling a calling link from the topology structure, wherein the calling link has the first node as a starting node and the second node as an ending node; based on the calling link, determining the calling relationship.

7. The method of claim 5, wherein, The method further comprises: obtaining third identification information of a plurality of second microservices and transaction data of the plurality of second microservices; based on the third identification information and the transaction data, constructing an initial topology structure, and outputting the initial topology structure; In response to receiving the selection instruction of the initial topology structure, the topology structure associated with the target service scenario is determined, and the topology structure is stored to the graph database.

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

9. An electronic device, comprising: Comprise: A memory storing an executable program; A processor for running the program, wherein the program executes the method in any one of claims 1 to 7 when the program is running.

10. A computer program product comprising computer instructions, characterized in that, The computer instructions are executed by the processor to implement the steps of the method in any one of claims 1 to 7. The computer instructions are executed by the processor to implement the steps of the method in any one of claims 1 to 7.

Images