Application topology information acquisition method, device and system, vehicle and storage medium

Abstract

The embodiment of the invention provides an application topology information obtaining method, device and system, a vehicle and a storage medium, the method is applied to a vehicle cloud interaction system, the system comprises a vehicle machine located on the vehicle side and a processing device and a database located on the cloud, and the method comprises the steps that in response to a user instruction, the vehicle machine sends application topology query information to the processing device; the processing device sends a query instruction to a database based on the application topology query information; the database calculates the obtained application topology information of the target application based on the query instruction, and feeds back the application topology information of the target application to the processing device; and the processing device sends the application topology information of the target application to the vehicle machine. When a user needs to obtain the topological information of the target application, the database completes the calculation of the topological information in the database, thereby greatly reducing the data transmission amount between the processing device and the data, further reducing the calculation amount of the processing device, reducing the risk of downtime of the processing device, and improving the operation stability of the vehicle cloud interaction system.

Description

Technical Field

[0001] The present application relates to the field of vehicle-cloud interaction technology, and in particular to a method and device, system, vehicle and storage medium for obtaining application topology information. Background Art

[0002] With the continuous development of intelligent networking, the information interaction between the vehicle and the cloud can provide various services for vehicle users. Among them, an operation of the user on the vehicle involves multiple cloud applications. However, the user cannot observe which applications on the cloud provide services, the relationship between the various applications providing services, and the status information of the vehicle-cloud link in the vehicle. When the user queries the application link topology, the current query method is to obtain all the relevant trace data from the database, and calculate the application topology information after traversing the data multiple times. This method obtains a large amount of data and a large amount of calculation, consumes a huge amount of device memory, and there is a risk of device downtime. Summary of the invention

[0003] The embodiments of the present application provide a method and device, system, vehicle and storage medium for obtaining application topology information. Through this method, when a user needs to obtain the topology information of a target application, the cloud database can complete the calculation of the topology information within the database, greatly reducing the amount of data transmission between the cloud processing device and the data, and can further reduce the calculation amount of the cloud processing device, reduce the risk of downtime of the cloud processing device, and improve the stability of the operation of the vehicle-cloud interaction system.

[0004] In a first aspect, an embodiment of the present application provides a method for obtaining application topology information, which is applied to a vehicle-to-cloud interaction system. The system includes a vehicle computer located on the vehicle side and a processing device and a database located on the cloud. The method includes: in response to a user instruction, the vehicle computer sends application topology query information to the processing device; the processing device sends a query instruction to the database based on the application topology query information; the database calculates application topology information of the target application based on the query instruction, and feeds back the application topology information of the target application to the processing device; and the processing device sends the application topology information of the target application to the vehicle computer.

[0005] In one implementable manner, the query instruction includes application information of the target application and a selected query time; the application topology information of the target application calculated by the database based on the query instruction includes: calculating link data of the target application within the selected query time based on the query instruction; calculating related application information based on the link data; and calculating topology information of the target application based on the link data and the related application information.

[0006] In one achievable manner, calculating the topology information of the target application based on link data and related application information includes: determining the upstream application in each call link and the number of calls between two applications in each call link based on the link data and related application information; calculating multiple time consumption indicators between each two applications in multiple call links based on the link data and related application information, the time consumption indicators including at least one of the P99 value, the P95 value and the P90 value; and calculating the execution call success rate of each two applications in multiple call links based on the link data and related application information.

[0007] In one feasible manner, based on link data and related application information, determining the upstream application in each call link and the number of calls between two applications in each call link includes: obtaining all link IDs related to the target application within the selected query time, and the application IDs of the applications related to all link IDs; based on all link IDs, determining the upstream application in each link; and based on all link IDs, determining the number of calls between two applications in each link.

[0008] In one achievable manner, based on link data and relevant application information, calculating multiple time consumption indicators in multiple call links between each two applications includes: obtaining all link IDs related to the target application within the selected query time, and the application IDs of the applications related to all link IDs; based on the application IDs of the applications related to all link IDs, determining the time consumption information of the two applications in each call link of the same application subject, wherein the call link of the same application subject is a call link in which the upstream application and the downstream application are the same two applications; based on the size sorting of the time consumption information of the two applications in each call link of the same application subject, determining at least one of the P90 value at the 90% position, the P95 value at the 95% position, and the P99 value at the 99% position, wherein the time consumption indicator may include at least one of the P99 value, the P95 value, and the P90 value.

[0009] In one achievable manner, based on link data and relevant application information, calculating the execution call success rate of each two applications in multiple call links includes: obtaining all link IDs related to the target application within the selected query time, and the application IDs of the applications related to all link IDs; determining the execution call status of the two applications in each call link of the same application subject based on the application IDs of the applications related to all link IDs, wherein the call link of the same application subject is a call link in which the upstream application and the downstream application are the same two applications, and the execution call status includes a success status or a failure status; based on the execution call status of the upstream application and the downstream application in each call link of the same application subject, determining the cumulative number of successes of the upstream application and the downstream application in multiple call links, and calculating the execution call success rate of the upstream application and the execution call success rate of the downstream application in the call link of the same application subject.

[0010] In a second aspect, an embodiment of the present application provides an application topology information acquisition device, including: a processor and a memory, the memory is used to store at least one instruction, and when the instruction is loaded and executed by the processor, the application topology information acquisition method provided in the first aspect is implemented.

[0011] In a third aspect, an embodiment of the present application further provides a vehicle, which may include the application topology information acquisition device provided in the second aspect.

[0012] In a fourth aspect, an embodiment of the present application also provides a vehicle-cloud-cloud interaction system, comprising: a vehicle, a processing device located in the cloud, and a data volume, wherein the vehicle includes a vehicle computer; wherein, in response to a user instruction, the vehicle computer sends application topology query information to the processing device; the processing device sends a query instruction to a database based on the application topology query information; the database calculates application topology information of the target application based on the query instruction, and feeds back the application topology information of the target application to the processing device; and the processing device sends the application topology information of the target application to the vehicle computer.

[0013] In a fifth aspect, an embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method for obtaining application topology information provided in the first aspect is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0015] Figure 1A schematic diagram of an application scenario provided for an embodiment of the present application;

[0016] Figure 2 A schematic diagram of obtaining application topology information provided by an embodiment of the present application;

[0017] Figure 3 A flowchart of a method for obtaining application topology information provided by an embodiment of the present application;

[0018] Figure 4 A schematic diagram of the application topology information calculation process provided for an embodiment of the present application;

[0019] Figure 5 A schematic diagram of a related application link provided for an embodiment of the present application;

[0020] Figure 6 A schematic diagram of an application service call provided for an embodiment of the present application;

[0021] Figure 7a A schematic diagram of a visualization image of application topology information in a vehicle-side display interface provided by an embodiment of the present application;

[0022] Figure 7b A schematic diagram of a visualization image of application topology information in a vehicle-side display interface provided by an embodiment of the present application;

[0023] Figure 8 A schematic diagram of the structure of an application topology information acquisition device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, 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 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 are within the scope of protection of this application.

[0025] To facilitate understanding of the technical solution of the present application, the concepts involved are explained below.

[0026] 1. On-Line Analytical Processing (OLAP): OLAP is the main application of data warehouse systems. It supports complex analytical operations, focuses on decision support, and provides intuitive and easy-to-understand query results.

[0027] 2. ClickHouse: A columnar database management system for OLAP that allows creating tables and databases, loading data, and running queries at runtime without reconfiguring and restarting the server. It supports linear expansion, is simple and convenient, highly reliable, and fault-tolerant.

[0028] 3. Tracing: Restore a distributed request to a call link, and centrally display the call status of a distributed request, such as the time consumed on each service node, which machine the request specifically reaches, the request status of each service node, etc. Tracing can capture the exceptions and errors encountered by each request, as well as real-time information and valuable data.

[0029] Figure 1 A schematic diagram of an application scenario provided for an embodiment of the present application.

[0030] Reference Figure 1 As shown, the application scenario is an end-cloud interaction system, which may include a cloud 100 and a terminal 200, wherein the cloud 100 may provide corresponding services to the terminal 200 through end-cloud interaction based on the request of the terminal 200. In some embodiments, the terminal 200 may be a vehicle computer of a vehicle, that is, the end-cloud interaction system may be a vehicle-cloud interaction system. In other embodiments, the terminal 200 may also be an electronic device that can install applications and can receive services from the cloud 100, and this application does not limit the terminal type. For the convenience of explanation, the following embodiments of this application take a vehicle computer as an example to describe in detail the technical solution provided by this application.

[0031] Figure 2 A schematic diagram of obtaining application topology information provided by an embodiment of the present application.

[0032] Reference Figure 2 As shown, the vehicle computer 200 can query the application topology information of the application (target application) currently running on the vehicle computer. Specifically, the vehicle computer 200 can send application topology query information to the cloud 100, thereby obtaining the application topology information fed back by the cloud 100. It should be noted that the target application is an application on the vehicle computer side, and the operation of the target application requires data interaction between multiple applications on the cloud side as support. Therefore, querying the application topology information of the target application is to query the topology information of multiple cloud applications related to the operation of the target application.

[0033] The cloud 100 may include a processing device 101 and a database 102, wherein the processing device 101 may send a corresponding query request (or query instruction) to the database 102 based on the application topology query information after receiving the application topology query information sent by the vehicle computer 200, so that the database 102 calculates the application topology information of the target application according to the query request and feeds it back to the processing device 101, and the processing device summarizes the application topology information fed back by the database 102, and generates a corresponding visualization image, and then sends the visualization image to the vehicle computer 200, and the user can view the application topology information of the application currently running on the vehicle computer 200. In other embodiments, the processing device may summarize the application topology information fed back by the database 102, and directly send the summarized application topology information to the vehicle computer 200, and the vehicle computer 200 generates a visualization image according to the received application topology information, that is, completes page rendering, and displays it on the display screen of the vehicle computer 200.

[0034] In some embodiments, the database 102 on the cloud 100 side can be a ClickHouse, so that after obtaining the query request sent by the processing device 101, the database 102 can complete the calculation of the application topology information within the database, that is, there is no need to export the full link data to the processing device 101 for calculation, thereby greatly reducing the data transmission volume between the processing device 101 and the database and the calculation volume of the processing device, thereby reducing the possibility of cloud device crashes.

[0035] In some embodiments, the vehicle computer 200 and all applications in the cloud 100 follow the opente lemetry protocol for data interaction, such as link (trace) data reporting. Furthermore, the database 102 records the link data, specifically using the OLAP database ClickHouse to record the link data of the application. During the calculation process of the database 102, complex calculation logic can be executed in the ClickHouse database 102 in sequence, and the calculation results can be directly fed back to the processing device 101. The processing device 101 only needs to aggregate the data, reduce the computing power consumption of the processing device 101, and improve the operating stability of the processing device 101.

[0036] Figure 3 A flowchart of a method for obtaining application topology information provided in accordance with an embodiment of the present application.

[0037] Reference Figure 3 As shown, the method for obtaining application topology information may include the following steps:

[0038] S101: In response to a user instruction, the vehicle computer sends application topology query information to a processing device in the cloud.

[0039] In some embodiments, when a user wants to query the application topology information of a certain application currently running on the vehicle computer, the user can select the application to be queried on the vehicle computer 200 side. For example, the user can touch the display screen of the vehicle computer 200 to enter the application topology query interface, and then select the application name of the application to be queried in the application list of the application topology query interface or click the icon of the corresponding application to complete the selection of the target application. In response to the above operation of the user, the vehicle computer 200 can determine the application information of the target application. Furthermore, the user can also select the query time range in the application topology query interface, so that the application topology information of the target application within the selected time range can be queried.

[0040] The application topology query information sent by the vehicle computer 200 may include application information of the application (target application) currently running on the vehicle computer. For example, the application information may be an application ID. The application topology query information may also include a query time range.

[0041] S102: The processing device sends a query instruction to the database based on the application topology query information.

[0042] The database 102 stores the link data of all cloud applications. If you want to query the application topology information of the target application, you need to query and calculate based on the link data of the cloud applications related to the target application. Then, after obtaining the application topology query information sent by the vehicle computer 200, the processing device 101 can send a query instruction to the database 102, so that the database 102 can query and calculate the application topology information of the target application based on the query instruction. Accordingly, the query instruction can include the application information of the target application and the query time range.

[0043] S103: The database calculates link data of the target application within the query time range based on the query instruction.

[0044] After obtaining the query instruction, the database 102 can directly determine all link data of the target application within the query time range (i.e., within the selected query time) in ClickHouse. In some embodiments, all link data of the target application within the query time range can be all link IDs of the target application within the query time range. Thus, the database 102 can calculate the application topology information of the target application based on the determined link ID.

[0045] S104: The database calculates relevant application information of the target application based on the link data.

[0046] After the database determines all link data of the target application within the query time range, exemplarily, after determining the link ID, the database can further determine application information of the relevant application based on the link ID, exemplarily, can determine the application ID of the relevant application.

[0047] Figure 5 A schematic diagram of a related application link provided for an embodiment of the present application.

[0048] Reference Figure 5 As shown, after determining all link IDs of the target application within the query time range, the database can determine the application ID of the related application based on the link ID. Among them, there is a calling relationship (i.e., calling or being called) between every two applications in the related applications, and each call corresponds to a link ID, that is, different calls between the same two applications correspond to different link IDs. Therefore, after determining all link IDs related to the target application within the query time range, the application IDs of the two applications related to each call can be determined based on the link ID. In some embodiments, the related application can be an application service provided by the cloud 100, wherein multiple application services can be provided in one application, and each application service has its own application ID.

[0049] S105: The database calculates application topology information of the target application based on the determined link data and related application information.

[0050] Reference Figure 4 As shown, S105 can be implemented by executing the following steps:

[0051] S105a: The database determines the upstream application in each call link and the number of calls between two applications in each call link based on the link data and related application information.

[0052] After obtaining all link IDs related to the target application within the query time range and the application IDs of all applications related to the link IDs, the database can determine the upstream application of each related application in the link.

[0053] Figure 6 A schematic diagram of an application service call provided for an embodiment of the present application.

[0054] Combination Figure 5 and Figure 6 As shown, based on the acquired link IDs and the application IDs of the applications related to the link IDs, each link is traversed to determine the upstream application of the two related applications in each link. Figure 6As shown, in the link where application a calls application b according to one of the link IDs, the caller is the upstream application and the callee is the downstream application, that is, in the call link corresponding to the link ID, application a is the upstream application and application b is the downstream application. In this way, the upstream application in the call link corresponding to each link ID can be traversed.

[0055] Since each call will generate a corresponding link ID, the number of calls between applications within the query time range can be determined based on the number of link IDs, that is, the number of calls between every two applications can be obtained. For example, a link is determined based on a link ID, and the link is the call link of application a calling application c, where the query time range is within the last 5 minutes, and the N times that application a called application c in the last 5 minutes can be determined.

[0056] S105b: The database calculates various time consumption indicators in multiple call links between every two applications based on the link data and relevant application information.

[0057] In some embodiments, after obtaining all link IDs related to the target application within the query time range, and the application IDs of all link ID-related applications, the database can determine the time-consuming information of each related application in each link when executing the call, that is, determine the time-consuming information of two applications in each call link of the same application subject, wherein the call link of the same application subject is the call link of the upstream application and the downstream application, and the application subject in the multiple call links of the same application subject is application a (upstream application) and application b (downstream application), and the multiple call links of the same application subject can be multiple links corresponding to application a calling application b multiple times within the query time range. Among them, in a call link, the time consumption of the upstream application (caller) and the downstream application (callee) may be different. Moreover, in multiple calls between the same pair of applications, the time consumption may also be different each time. Exemplarily, within the query time range, the total number of times application a calls application b is 50 times, and the time consumption of application a and application b in each call of the 50 calls is obtained as shown in Table 1:

[0058] Table 1

[0059] Call Information Application a time consuming Application b time 1st time ta1 tb1 2nd ta2 tb2 3rd ta3 tb3 … … … 49th ta49 tb49 50th ta50 tb50

[0060] Based on the above method, the time consumption information of each related application in multiple call links between each two identical applications within the query time range can be obtained. Figure 5 As shown in the figure, based on the obtained relevant link IDs within the query time range, according to the application classification involved in the call, it can be divided into the following categories: Figure 5The seven types of calls shown are application a calling application b, application a calling application c, application b calling application c, application b calling application d, application c calling application d, application c calling application e, and application d calling application e. Based on the same method as above, the time consumption information of each related application in executing the call in multiple call links between each two identical applications can be obtained, that is, 7 time consumption schematic tables similar to Table 1 are obtained.

[0061] After obtaining the time information of each related application in the multiple call links between each two identical applications when executing the call, multiple time indicators of each pair of identical applications in the multiple call links can be further calculated. In some embodiments, the time indicator may include at least one of the P99 value, the P95 value, and the P90 value. Among them, the time consumption is arranged from small to large, the value at the 90% position in the order is the P90 value, the value at the 95% position in the order is the P95 value, and the value at the 99% position in the order is the P99 value. Taking the time consumption information shown in Table 1 as an example, among the 50 calls of application a to application b, the 50 time consumptions of application a are sorted in ascending order, and the values ​​at the 90% position, 95% position and 99% position are determined, so as to obtain the time consumption index of application a, wherein the time consumption index includes P99 value, P95 value and P90 value. Similarly, among the 50 calls of application a to application b, the 50 time consumptions of application b are sorted in ascending order, and the values ​​at the 90% position, 95% position and 99% position are determined, so as to obtain the time consumption index of application b, wherein the time consumption index includes P99 value, P95 value and P90 value.

[0062] Based on the same method as above, the time consumption index of calling each related application in multiple call links between every two identical applications within the query time range can be calculated.

[0063] S105c: The database calculates the execution call success rate of each application in the selected link based on the link data and related application information.

[0064] In some embodiments, after obtaining all link IDs related to the target application within the query time range, and the application IDs of all link ID-related applications, the database can determine the number of executions of each related application in each link when executing the call. Among them, in a call link, the number of execution calls of the upstream application (caller) and the downstream application (callee) may be different, wherein the upstream application may issue a request to call the downstream application, but the downstream application does not provide a call service, that is, in this call, the execution number of the upstream application is 1, and the execution number of the downstream application is 0. Exemplarily, within the query time range, the total number of times application a calls application b is 50 times, wherein the execution call status (success / failure) of each call is shown in Table 2:

[0065] Table 2

[0066] Call Information Application a execution call status Application b execution call status 1st time success success 2nd success fail 3rd fail fail … … … 49th success fail 50th success success Total calls 50 times A total of 45 successful executions 40 successful executions in total

[0067] The execution call status of each application in multiple calls between the same two applications can be obtained in the above manner. Figure 5 As shown in the figure, based on the obtained relevant link IDs within the query time range, according to the application classification involved in the call, it can be divided into the following categories: Figure 5 The seven types of calls shown in Table 2 can obtain the seven application execution call status table information similar to that in Table 2.

[0068] Furthermore, the execution call success rate of each related application in the multiple call links between every two identical applications within the query time range can be obtained. In some embodiments, the execution call success rate of the application can be calculated based on the ratio of the cumulative number of successful executions of each application in the selected link (i.e., the multiple call links between two applications) to the total number of calls. Exemplarily, based on the call link of application a calling application b shown in Table 2, the total number of calls is 50 times, and application a has accumulated 45 successful executions, then the execution call success rate of application a is 90% (45 / 50), and the execution call success rate of application b is 82% (40 / 50).

[0069] Based on the same method as above, the application execution call success rate of each related application in multiple call links between every two identical applications within the query time range can be calculated.

[0070] It should be noted that the present application does not limit the execution order of S105a, S105b and S105c. In some embodiments, S105a, S105b and S105c can be executed in sequence, in other embodiments, they can be executed in other orders, and in other embodiments, S105a, S105b and S105c can be executed simultaneously. By way of example, the execution tasks of S105a, S105b and S105c are assigned to different computing units in the database for calculation.

[0071] S106: The database feeds back the calculated information to the processing device.

[0072] S107: The processing device receives and summarizes the information fed back by the database, and generates a visualization image based on the summarized information.

[0073] S108: The processing device transmits the visualized image to the vehicle computer.

[0074] S109: The vehicle computer displays a visualized image on the display screen.

[0075] Figure 7a A schematic diagram of a visualization image of topological information applied in a vehicle-side display interface provided in one embodiment of the present application.

[0076] Reference Figure 7a As shown, in some embodiments, the visualization image fed back by the processing device in the cloud may include the call relationship between related applications within the query time range and the number of calls between each two applications with a call relationship. Among them, each application display box can also display the time consumption index information (such as the time consumption P99 value) and the execution call success rate of the application in the selected link. The user can clearly know the call relationship between related applications within the query time range and the number of calls between each two applications with a call relationship through the visualization image displayed by the car computer, the time consumption index and execution call success rate of each application in the selected call link, and the driving image presentation to the user can be more intuitive.

[0077] In some embodiments, in a selected call link, when the execution call success rate of a certain application is less than the success rate threshold, the display box of the application can be highlighted. In one embodiment, the success rate threshold can be 100%, and in other embodiments, the success rate threshold can also be other values, which is not limited by the present application.

[0078] Reference Figure 7a As shown, the execution call success rate of application e is 90%, so the display box of application e is highlighted in the display interface, and the user can quickly identify the applications whose execution call success rate is less than the success rate threshold among multiple applications.

[0079] In some embodiments, when it is determined that there is an application whose execution call success rate is less than the success rate threshold, the vehicle computer outputs an alarm notification to the relevant technicians, thereby notifying the relevant technicians to perform maintenance. The alarm notification may include the application ID, time consumption index, and execution call success rate of the application. The technicians can quickly and directly analyze the root cause based on the time consumption index and the execution call success rate, thereby improving the efficiency of equipment maintenance.

[0080] Figure 7b A schematic diagram of a visualization image of topological information applied in a vehicle-side display interface provided in one embodiment of the present application.

[0081] Reference Figure 7b As shown, in some embodiments, the user can also select applications to view within the query time range, so that the relevant topological information of the currently selected application can be displayed on the vehicle display screen. The visualization image fed back by the cloud processing device can also include the call execution count of the current application. In one embodiment, the call execution count of the current application can be displayed in the form of a curve graph. The horizontal axis of the curve graph represents time, and the vertical axis represents the execution count. The call execution count represented by the curve graph is the call execution count of the current application represented from the perspective of the current application. In some embodiments, the visualization image can also include relevant information about the upstream and downstream applications of the current application, which can specifically include the number of calls made by the upstream application to the current application, and the number of calls made by the current application to the downstream application, the HTTP name and HTTP code when calling the downstream application, wherein the HTTP code represents the call status (success / failure) of the current application calling the downstream application, wherein when the HTTP code is 200, it indicates a successful call, and when the HTTP code is 500, it indicates a failed call. For example, refer to Figure 7b As shown, the upstream application of the current application (application b) is application a, and application a called the current application 65 times within the query time range. The downstream applications of the current application are application c and application d, and the current application called application c 67 times, and the corresponding HTTP code was 200, which means that all 65 calls were successful, and called application d 68 times, and the corresponding HTTP code was 200, which means that all 68 calls were successful. If at least one call fails, the corresponding HTTP code is 500, and the number of calls shows the number of failed calls.

[0082] Figure 8 A schematic diagram of the structure of an application topology information acquisition device provided in one embodiment of the present application.

[0083] Reference Figure 8As shown, the device may include: a processor 801 and a memory 802, the memory 802 is used to store at least one instruction, and when the instruction is loaded and executed by the processor 801, the application topology information acquisition method provided in any embodiment of the present application is implemented.

[0084] The embodiment of the present application also provides a vehicle, which may include Figure 8 The illustrated embodiment provides a device for acquiring application topology information.

[0085] An embodiment of the present application also provides a vehicle-cloud interaction system, comprising: a vehicle, a processing device located in the cloud, and a data volume, wherein the vehicle includes a vehicle computer; wherein, in response to a user instruction, the vehicle computer sends application topology query information to the processing device; the processing device sends a query instruction to a database based on the application topology query information; the database calculates application topology information of the target application based on the query instruction, and feeds back the application topology information of the target application to the processing device; and the processing device sends the application topology information of the target application to the vehicle computer.

[0086] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method for obtaining application topology information provided in any embodiment of the present application is implemented.

[0087] It is understandable that the application may be an application program (naturalApp) installed on the terminal, or may also be a web page program (webApp) of a browser on the terminal, and this embodiment of the present application does not limit this.

[0088] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0089] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, 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 an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0090] 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.

[0091] 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 hardware plus software functional units.

[0092] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (Processor) to perform some steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0093] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

[0094] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for obtaining application topology information, characterized in that: Applied to a vehicle-cloud interaction system, the system includes a vehicle computer located on the vehicle side and a processing device and a database located on the cloud, and the method includes: In response to a user instruction, the vehicle computer sends application topology query information to the processing device; The processing device sends a query instruction to the database based on the application topology query information; The database calculates application topology information of the target application based on the query instruction, and feeds back the application topology information of the target application to the processing device; and The processing device sends the application topology information of the target application to the vehicle computer.

2. The method according to claim 1, characterized in that The query instruction includes application information of the target application and a selected query time; The application topology information of the target application calculated by the database based on the query instruction includes: Calculate the link data of the target application within the selected query time based on the query instruction; Calculating relevant application information based on the link data; and The topology information of the target application is calculated based on the link data and the related application information.

3. The method according to claim 2, characterized in that The calculating the topology information of the target application based on the link data and the related application information includes: Based on the link data and relevant application information, determine the upstream application in each call link and the number of calls between two applications in each call link; Based on the link data and relevant application information, calculate multiple time consumption indicators in multiple call links between every two applications, where the time consumption indicators include at least one of a P99 value, a P95 value, and a P90 value; and Based on the link data and relevant application information, the execution call success rate of every two applications in the multiple call links is calculated.

4. The method according to claim 3, characterized in that The determining, based on the link data and the relevant application information, the upstream application in each call link and the number of calls between two applications in each call link comprises: Obtaining all link IDs related to the target application within the selected query time, and application IDs of applications related to all link IDs; Based on the all link IDs, determining the upstream application in each link; and Based on the all link IDs, the number of calls between two applications in each link is determined.

5. The method according to claim 3, characterized in that: The calculating of multiple time consumption indicators in multiple call links between each two applications based on the link data and related application information includes: Obtaining all link IDs related to the target application within the selected query time, and application IDs of applications related to all link IDs; Based on the application IDs of the applications related to the all link IDs, determining the time consumption information of the two applications in each call link of the same application subject, wherein the call link of the same application subject is a call link in which the upstream application and the downstream application are the same two applications; Based on the size sorting of the time-consuming information of the two applications in each call link of the same application subject, at least one of the P90 value at the 90% position, the P95 value at the 95% position, and the P99 value at the 99% position is determined, wherein the time-consuming index may include at least one of the P99 value, the P95 value, and the P90 value.

6. The method according to claim 3, characterized in that: The calculating, based on the link data and the relevant application information, the execution call success rate of each two applications in the multiple call links comprises: Obtaining all link IDs related to the target application within the selected query time, and application IDs of applications related to all link IDs; Based on the application IDs of the applications related to the all link IDs, determining the execution call status of the two applications in each call link of the same application subject, wherein the call link of the same application subject is a call link in which the upstream application and the downstream application are the same two applications, and the execution call status includes a success status or a failure status; Based on the execution call status of the upstream application and the downstream application in each call link of the same application subject, the cumulative number of successes of the upstream application and the downstream application in multiple call links is determined, and the execution call success rate of the upstream application and the execution call success rate of the downstream application in the call link of the same application subject are calculated.

7. An application topology information acquisition device, characterized in that: The device comprises: A processor and a memory, wherein the memory is used to store at least one instruction, and when the instruction is loaded and executed by the processor, the method for obtaining application topology information according to any one of claims 1 to 6 is implemented.

8. A vehicle, characterized in that: The vehicle includes the application topology information acquisition device according to claim 7.

9. A vehicle-to-cloud interaction system, characterized in that: The system comprises: The vehicle of claim 8, and the processing device and database located in the cloud, wherein the vehicle comprises a vehicle computer; Wherein, in response to a user instruction, the vehicle computer sends application topology query information to the processing device; The processing device sends a query instruction to the database based on the application topology query information; The database calculates application topology information of the target application based on the query instruction, and feeds back the application topology information of the target application to the processing device; and The processing device sends the application topology information of the target application to the vehicle computer.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for obtaining application topology information according to any one of claims 1 to 6 is implemented.

Images