Vehicle-cloud service link monitoring method, apparatus, and related device

Abstract

The present application provides a vehicle-cloud service link monitoring method, an apparatus, and a related device. The method comprises: on the basis of a link node of a vehicle, determining at least one service link monitoring strategy for the vehicle, and synchronizing service link monitoring strategies of an in-vehicle infotainment terminal of the vehicle and a cloud server; on the basis of the synchronized service link monitoring strategies, acquiring a configuration result of the in-vehicle infotainment terminal monitoring an in-vehicle infotainment terminal service link on the basis of the service monitoring strategy; when the vehicle receives or generates a service proxy request, on the basis of the service link monitoring strategy configured for the in-vehicle infotainment terminal, generating corresponding monitoring information on each link node on a service link related to the service proxy request; and adding the monitoring information to service data in a service proxy request flow process and then feeding back same to the cloud server, so as to determine a result of monitoring a vehicle-cloud service link. In the monitoring process, there is no need to set a monitoring buried point or additionally create a monitoring system, thereby effectively reducing the costs of monitoring a vehicle-cloud service link, and ensuring the monitoring timeliness.

Description

A method, apparatus, and related equipment for monitoring vehicle-to-cloud service links. Technical Field

[0001] This application relates to the field of intelligent vehicle networking, and in particular to a method, apparatus and related equipment for monitoring vehicle-cloud service links. Background Technology

[0002] With the continuous development of automotive intelligence and connectivity, there are increasingly more proxy application service scenarios involving mutual function calls between user vehicles and cloud services provided by service providers. In these scenarios, ensuring the smooth operation of the service link between vehicles and the cloud is crucial. However, vehicle-cloud services involve numerous scenarios and have relatively complex service links. Different functions have different service links. Even if service A, involving the same link nodes, executes normally in one service call link, it doesn't guarantee that the same link nodes will function correctly in a service call link for service B. To ensure the smooth operation of the vehicle-cloud service link, comprehensive monitoring is necessary. Traditional industry monitoring methods require configuring link detection points on all relevant parties, including the corresponding service and business units, and obtaining the detection results of these points to determine the smoothness of the service link. However, there is data isolation between vehicle cloud service link data and vehicle cloud business data, as they mostly belong to different communication systems and the data is relatively separated. In order to carry out the above monitoring process, it is necessary to establish a dedicated monitoring data acquisition and analysis detection system with corresponding configured detection points, and align it with the business system of vehicle cloud service link in order to ensure the effectiveness of monitoring vehicle cloud service link. This traditional monitoring method has high system overhead, high monitoring cost, and poor monitoring accuracy.

[0003] Summary of the Invention

[0004] In view of this, embodiments of this application provide a method, apparatus, and related equipment for monitoring vehicle-cloud service links, so as to at least partially solve the above problems.

[0005] In a first aspect, embodiments of this application provide a method for monitoring vehicle-to-cloud service links, including:

[0006] Based on the link nodes involved in the vehicle's service functions, at least one service link monitoring strategy for the vehicle is determined, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information.

[0007] Based on the vehicle corresponding to the service link monitoring strategy, the service link monitoring strategy configured on the vehicle's in-vehicle terminal and cloud server is synchronized.

[0008] [Corrected according to detailed rule 91 25.08.2025] Based on the synchronized service link monitoring strategy, obtain the configuration result of the vehicle terminal monitoring the service link of the vehicle terminal according to the service link monitoring strategy. The configuration result is used to indicate whether the link monitoring configuration of at least one service function of the vehicle is successful or not according to the service link monitoring strategy.

[0009] When the vehicle receives or generates a service proxy request, based on the service link monitoring strategy configured on the vehicle terminal, corresponding monitoring information is generated for each link node on the service link involved in the service proxy request.

[0010] After the monitoring information is added to the business data in the service proxy request flow process, it is fed back to the cloud server so that the cloud server can extract one or more monitoring information from the business data to determine the monitoring result of the vehicle cloud service link used by the at least one service function.

[0011] Secondly, this application also provides a device for monitoring vehicle-to-cloud service links, comprising:

[0012] The determination module is used to determine at least one service link monitoring strategy for the vehicle based on the link nodes involved in the vehicle's service functions, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information.

[0013] The synchronization module is used to synchronize the service link monitoring policies configured on the vehicle's in-vehicle terminal and the cloud server based on the vehicle corresponding to the service link monitoring policy.

[0014] [Corrected according to detailed rule 91 25.08.2025] The configuration module is used to obtain the configuration result of the vehicle terminal monitoring the service link according to the service link monitoring strategy after synchronization. The configuration result is used to indicate whether the link monitoring configuration of at least one service function of the vehicle is successful or not.

[0015] The monitoring module, when the vehicle receives or generates a service proxy request, generates corresponding monitoring information for each link node on the service link involved in the service proxy request based on the service link monitoring strategy configured on the vehicle terminal.

[0016] The analysis module is used to add the monitoring information to the business data in the service proxy request flow process and then feed it back to the cloud server so that the cloud server can extract one or more monitoring information from the business data to determine the monitoring results of the vehicle-cloud service link used by the at least one service function.

[0017] Thirdly, embodiments of this application also provide a storage medium storing computer-executable instructions, which, when executed, perform any of the vehicle-cloud service link monitoring methods described in the first aspect of this application.

[0018] Fourthly, embodiments of this application also provide an electronic device, including: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other through the communication bus;

[0019] The memory is used to store at least one executable instruction, which causes the processor to perform an operation corresponding to any of the vehicle-cloud service link monitoring methods described in the first aspect of this application.

[0020] [Corrected according to Rule 91, August 25, 2025] This application provides a method, apparatus, and related equipment for monitoring vehicle-cloud service links. Based on the link nodes involved in the vehicle's service functions, at least one service link monitoring strategy for the vehicle is determined, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information; based on the vehicle corresponding to the service link monitoring strategy, the service link monitoring strategies configured on the vehicle's in-vehicle terminal and cloud server are synchronized; based on the synchronized service link monitoring strategy, a configuration result is obtained showing that the in-vehicle terminal monitors the service links according to the service link monitoring strategy, wherein the configuration result... This is used to indicate whether the link monitoring configuration for at least one service function of the vehicle is successful or not, based on the service link monitoring strategy. When the vehicle receives or generates a service proxy request, based on the service link monitoring strategy configured on the vehicle terminal, corresponding monitoring information is generated for each link node on the service link involved in the service proxy request. The monitoring information is added to the business data during the service proxy request flow and then fed back to the cloud server, so that the cloud server can extract one or more monitoring information from the business data to determine the monitoring result of the vehicle-cloud service link used by the at least one service function. This application, by configuring a service link monitoring strategy, generates corresponding link monitoring information when the various data flow and execution nodes of the vehicle-cloud service receive service instructions. This information is then merged with the service business data and sent to the cloud server for analysis to complete the monitoring of the service link between the vehicle and the cloud. During the monitoring process, there is no need to set up monitoring points or establish a separate monitoring system, which effectively reduces the cost of vehicle-cloud service link monitoring and ensures the timeliness of monitoring. Attached Figure Description

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

[0022] Figure 1 is a schematic diagram of the workflow of a vehicle-cloud service link monitoring method provided in an embodiment of this application;

[0023] Figure 2 is a schematic diagram of the structure of a vehicle-cloud service link monitoring device provided in an embodiment of this application.

[0024] Figure 3 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0025] To enable those skilled in the art to better understand the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art should fall within the protection scope of the embodiments of this application.

[0026] It should be understood that the steps described in the method embodiments of this application may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this application is not limited in this respect.

[0027] Example 1

[0028] This application provides a method for monitoring vehicle-to-cloud service links, as shown in Figure 1. Figure 1 is a schematic diagram of the workflow of the method for monitoring vehicle-to-cloud service links provided in this application, including:

[0029] Step S101: Based on the link nodes involved in the vehicle's service functions, determine at least one service link monitoring strategy for the vehicle. The service link monitoring strategy includes at least monitoring mode information and monitoring object information, indicating when or under which working conditions the link nodes on the service link involved in the service function will be monitored, and which link nodes will be monitored. Of course, this embodiment is merely an example illustrating the monitoring mode information and monitoring object information included in the service link monitoring strategy, and does not represent a limitation of this application. In this embodiment, the link node is a system node that generates service request data, receives service request instruction data, or executes the service request instruction data, including data forwarding nodes such as vehicle gateways, and data execution nodes such as ECU processors contained in different functional domains of the vehicle. This embodiment achieves rapid location of abnormal problems or faults occurring in the service link between the vehicle and the cloud by monitoring the status of the link nodes.

[0030] Optionally, in one implementation of this application embodiment, determining at least one service link monitoring strategy for the vehicle based on the link nodes involved in the vehicle's service functions includes: determining the vehicle's basic configuration information and the user's personalized configuration information for the vehicle; determining the link nodes involved in at least one service function of the vehicle based on the basic configuration information and the personalized configuration information; and determining the service link monitoring strategy for the corresponding service link of the at least one service function based on the link nodes involved in the at least one service function. In the actual application scenario of this application embodiment, the vehicle's basic information includes basic configuration information related to the service functions configured in the vehicle's design or production process, such as the basic configuration information of the service functions set for the corresponding vehicle's in-vehicle terminal according to the vehicle's brand, model, or vehicle baseline, for example, remotely opening windows, air conditioning, or adjusting seats via the cloud. As the vehicle's service functions iterate and expand, the personalized configuration information is used to represent the service functions configured on the in-vehicle terminal after the user makes a personalized selection of the vehicle's service functions, such as advertising subscription information or weather forecast information. This embodiment of the application determines the service link monitoring strategy based on these two configuration information to ensure the comprehensiveness of monitoring the service link between the vehicle and the cloud, thereby improving the system stability of the user's use of the service functions between the vehicle and the cloud.

[0031] Optionally, in one embodiment of this application, the monitoring mode information includes at least one or more different monitoring modes selected from full-state monitoring, monitoring when an anomaly occurs, link monitoring, and no monitoring. The monitoring object information includes at least one or more monitoring object information selected from full service monitoring, specified service monitoring, specified service method monitoring, specified service event monitoring, and specified service field monitoring. Specifically, full-state monitoring means monitoring the service link and node status regardless of whether the service link corresponding to the service function is activated or not; monitoring when an anomaly occurs is used to monitor the service link and node status when a system failure occurs; link monitoring is used to monitor only the business data links of the service function. Full service monitoring means monitoring all service links; specified service monitoring means monitoring only the service links specified by the user or operator; specified service method monitoring is used to monitor some nodes or data transmission links in the service links specified under the service set by the user or service operator. Specified event monitoring means monitoring service links related to business notifications automatically generated by certain service businesses under certain conditions; and specified service field monitoring is monitoring service links for specific business attributes of certain vehicle services. This application embodiment sets up multiple monitoring modes and monitoring objects to enable the methods described in this application embodiment to flexibly monitor the service links between vehicles and the cloud according to needs. This saves system resources and improves the user's driving experience based on the actual working scenarios of services between vehicles and the cloud. In the actual application scenarios of this application embodiment, even if new link nodes need to be monitored as the vehicle terminal service business system expands, only the corresponding monitoring strategy needs to be adjusted, and the monitoring adjustment process is simple and easy to implement.

[0032] Step S102: Based on the vehicle corresponding to the service link monitoring strategy, synchronize the service link monitoring strategies configured on the vehicle's in-vehicle terminal and cloud server. In the actual application scenarios of this application embodiment, the service link monitoring strategy, in addition to monitoring the service applications on the vehicle terminal, often involves the data transmission and execution nodes of the cloud server and the third-party business cloud accessed by the cloud server during service calls. In this application embodiment, in addition to supporting the direct use of cloud services provided by the vehicle manufacturer or the in-vehicle system operator, it also supports using the cloud service to access the vehicle cloud service function provided by a trusted third-party business cloud, so as to provide users with a better service experience. Therefore, in order to ensure the comprehensiveness of the service link monitoring involved in the service between the vehicle and the cloud, in addition to monitoring the service link on the in-vehicle terminal, it is also necessary to monitor the status of the service link on the cloud server and the service link of the third-party business cloud accessed by the cloud server during service calls. By synchronizing the monitoring strategies for the dual-end service links, it is possible to effectively ensure that the monitoring objects of the dual-end service-related link nodes performing the same service call work are aligned according to the method described in the embodiments of this application, so as to achieve the effect of comprehensive monitoring, ensure that all parties related to the service link can work stably, and ensure the accuracy of the monitoring results.

[0033] Optionally, in one implementation of this application, synchronizing the service link monitoring policies configured on the vehicle's in-vehicle terminal and the cloud server includes actively acquiring the service link monitoring policies through the in-vehicle terminal. Alternatively, in a preferred implementation, based on the vehicle corresponding to the service link monitoring policy, synchronizing the service link monitoring policies configured on the vehicle's in-vehicle terminal and the cloud server includes: storing the service link monitoring policy corresponding to the vehicle on the cloud server; and transmitting the vehicle-cloud service link monitoring policy corresponding to the vehicle to the vehicle's in-vehicle terminal when it is determined that the vehicle has established a service link with the cloud server. This facilitates the configuration of service link monitoring policies for various vehicle models in the cloud, facilitates the management of the configured service link monitoring policies, and ensures that either the vehicle or cloud terminal can promptly acquire the latest version of the service link monitoring policy from the cloud server after establishing a vehicle-cloud communication link to monitor its own service link.

[0034] [Corrected according to Rule 91, August 25, 2025] Step S103: Based on the synchronized service link monitoring strategy, obtain the configuration result of the vehicle-mounted terminal monitoring the service links according to the service link monitoring strategy. The configuration result indicates whether the link monitoring configuration for at least one service function of the vehicle according to the service link monitoring strategy was successful. In the actual application scenario of this application, the vehicle-mounted terminal is configured through the synchronization of the synchronized service link monitoring strategy. Only after confirming successful configuration can the monitoring of the service links between the vehicle and the terminal be accurately implemented according to the configured service link monitoring strategy, thus ensuring the effectiveness of monitoring. This avoids situations where link monitoring cannot be performed or monitoring errors occur due to configuration failure, affecting the user experience.

[0035] Step S104: When the vehicle receives or generates a service proxy request, based on the service link monitoring strategy configured on the vehicle terminal, corresponding monitoring information is generated for each link node on the service link involved in the service proxy request. That is, the corresponding monitoring information is generated when the service proxy request flows to that link node or when the link node executes the service instruction data corresponding to the received service proxy request. This monitoring information includes, for example, monitoring information on whether the request flows to this link node, or monitoring information on whether the link node successfully or failed to execute the service instruction. Of course, this embodiment is only an illustrative example of the generated monitoring information and does not represent that this application is limited to this. In a preferred implementation of this application embodiment, the monitoring information is a simple identification information, such as a binary code identifier, so that the monitoring analysis end can quickly extract and analyze the identification information to determine the link monitoring result.

[0036] Step S105: After adding the monitoring information to the business data in the service proxy request flow process, it is fed back to the cloud server so that the cloud server can extract one or more monitoring information from the business data to determine the monitoring result of the vehicle-cloud service link used by the at least one service function. In this embodiment, by fusing the monitoring information generated by the link nodes, such as the various data distribution (forwarding) nodes or instruction execution nodes involved in the vehicle-cloud service, with the business data of the service function and feeding it back (forwarding) it to the cloud server, the cloud server can monitor and analyze the service link based on the monitoring information extracted from the received fused data, thereby directly determining the monitoring result of the vehicle-cloud service link. This service link monitoring method eliminates the need to set monitoring points on the vehicle terminal or cloud server during the entire vehicle-cloud service link monitoring process. It also eliminates the need to build a separate link monitoring system to obtain the monitoring data generated by the detection points and then analyze it to determine the monitoring result, thereby reducing the system overhead and monitoring cost in the service link monitoring process, and improving the accuracy of the monitoring effect. Specifically, in this embodiment, the generated monitoring information does not change the structure of the business data during the transmission and execution of the service proxy request, that is, the structure or code of the instruction data of the service proxy request. For example, the business data of the service proxy request can be set to include: service-name, method, data, and track. When the service proxy request data flows to the link node to be monitored, a corresponding identifier is generated at that link node to indicate whether the node has successfully received or executed the request. This identifier is added to the empty data after the corresponding track, and the empty data is replaced. When the business flows to the next link node involved in the service link, the identifier after the track will not be read or executed. Thus, the monitoring information can be fed back to the analysis end through the process of business data flow. The analysis end can extract the corresponding identifier information for accurate monitoring of each link node through simple and quick data stripping, and determine the monitoring results of the service link simply and efficiently. Of course, this embodiment is only an example of the process of adding the monitoring information to the business data during the service proxy request flow, and does not mean that this application is limited to this.

[0037] Optionally, in one implementation of this application embodiment, the method further includes: caching or persistently storing monitoring information generated by each link node on the service link corresponding to the at least one service function locally on the vehicle. Correspondingly, the service link monitoring strategy further includes: adding the cached or persistently stored monitoring information locally on the vehicle to business data and then feeding it back to the cloud server based on a preset data feedback mechanism. In the actual application scenarios of this application embodiment, there may be situations where the link between the vehicle and cloud services is unstable or other circumstances prevent data from being fed back to the cloud server in a timely manner. For example, if the vehicle to be fed back is driving in a mountainous area or tunnel, the communication signal between the vehicle and the cloud is weak or disconnected, or the amount of data to be fed back is large, resulting in the inability to timely transmit the service link monitoring data of the vehicle terminal. In this case, the monitoring information of the relevant link nodes generated when the service function of the vehicle terminal is woken up can be cached locally on the vehicle, and then fed back to the cloud server when the communication bandwidth between the vehicle and the cloud is relatively idle, so as to determine the result of the service link monitoring. Alternatively, the cloud server might be configured not to monitor specific vehicles, but an anomaly occurs at a certain time, requiring investigation of service link issues. In this case, a feedback mechanism can be used to retrieve corresponding data from the monitoring information cached or persistently stored locally on the vehicle's device, and then perform comparative analysis to ensure the traceability of service link monitoring. The preset feedback mechanism can include, for example, real-time feedback of monitoring data to the cloud server, periodic feedback of monitoring data to the cloud server, the duration of the feedback feedback, and the size of the monitoring data fed back each time, to improve the flexibility of the service link monitoring method described in this application embodiment.

[0038] Optionally, in one embodiment of this application, the method further includes: generating unique identifier information for service proxy requests and establishing a mapping relationship between the unique identifier information and the monitored object, used to determine the monitoring information to be fed back to the cloud server. In this embodiment, by establishing a mapping relationship between unique identifier information and monitored objects to identify the monitoring information, when an anomaly occurs in the service link, it supports obtaining the corresponding monitoring information based on the unique identifier information for backflow analysis, avoiding the acquisition of other irrelevant data. Targeted acquisition of monitoring data improves the accuracy of service link monitoring, saves bandwidth traffic spent during service link monitoring, and reduces the consumption of data analysis resources.

[0039] Optionally, in one embodiment of this application, the method further includes: adding corresponding data flow timestamp information or business data execution timestamp information to the monitoring information on the generated link nodes to achieve orderly data tracking. This application uses timestamp information as one of the monitoring parameters for the service link. The analysis process is relatively simple. For example, it presets the time required for a certain service function to be awakened and completed, the time required for the entire workflow of feeding back the execution result business data to the analysis end, and the time required for the instruction data of the service proxy request to be transmitted to each link node. If the analysis determines that the flow time has expired or the execution time has expired based on the added data flow timestamp information or business data execution timestamp information, orderly data tracking of the relevant timestamp information can efficiently and accurately determine which link nodes in the service link have experienced anomalies, thereby improving the monitoring efficiency of the service link and easily achieving full-link data tracking.

[0040] [Corrected according to Rule 91, August 25, 2025] This application provides a method for monitoring vehicle-cloud service links. Based on the link nodes involved in the vehicle's service functions, at least one service link monitoring strategy for the vehicle is determined. The service link monitoring strategy includes at least monitoring mode information and monitoring object information. Based on the vehicle corresponding to the service link monitoring strategy, the service link monitoring strategies configured on the vehicle's in-vehicle terminal and the cloud server are synchronized. Based on the synchronized service link monitoring strategy, a configuration result is obtained of the in-vehicle terminal monitoring the service links according to the service link monitoring strategy. This configuration result indicates whether the link monitoring configuration for at least one service function of the vehicle according to the service link monitoring strategy was successful. When the vehicle receives or generates a service proxy request, based on the service link monitoring strategy configured on the in-vehicle terminal, corresponding monitoring information is generated for each link node on the service link involved in the service proxy request. The monitoring information is added to the business data during the service proxy request flow and then fed back to the cloud server. The cloud server then extracts one or more monitoring information from the business data to determine the monitoring result of the vehicle-cloud service links used for the at least one service function. This application configures a service link monitoring strategy. When the various data flow and execution nodes of the vehicle-cloud service receive service instructions, the corresponding link monitoring information is generated and integrated with the service business data before being sent to the cloud server for analysis. This completes the monitoring of the service link between the vehicle and the cloud. During the monitoring process, there is no need to set up monitoring points and establish a separate monitoring system, which effectively reduces the cost and system overhead of vehicle-cloud service link monitoring and ensures the timeliness and accuracy of link monitoring.

[0041] Example 2

[0042] Based on the vehicle-to-cloud service link monitoring method provided in Embodiment 1 of this application, this embodiment of the application also provides a vehicle-to-cloud service link monitoring device, as shown in FIG2. FIG2 is a schematic diagram of the structure of a vehicle-to-cloud service link monitoring device 20 provided in this embodiment of the application. The vehicle-to-cloud service link monitoring device 20 includes:

[0043] The determination module 201 is used to determine at least one service link monitoring strategy for the vehicle based on the link nodes involved in the vehicle's service functions, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information.

[0044] The synchronization module 202 is used to synchronize the service link monitoring policies configured on the vehicle's in-vehicle terminal and the cloud server based on the vehicle corresponding to the service link monitoring policy.

[0045] [Corrected according to detailed rules 91 25.08.2025] Configuration module 203 is used to obtain the configuration result of the vehicle terminal monitoring the service link according to the service link monitoring strategy after synchronization. The configuration result is used to indicate whether the link monitoring configuration of at least one service function of the vehicle is successful or not.

[0046] When the vehicle receives or generates a service proxy request, the monitoring module 204 generates corresponding monitoring information for each link node on the service link involved in the service proxy request based on the service link monitoring strategy configured on the vehicle terminal.

[0047] The analysis module 205 is used to add the monitoring information to the business data in the service proxy request flow process and then feed it back to the cloud server so that the cloud server can extract one or more monitoring information from the business data to determine the monitoring result of the vehicle cloud service link used by the at least one service function.

[0048] Optionally, in one implementation of this application embodiment, the determining module 201 is further configured to:

[0049] Determine the vehicle's basic configuration information and the user's personalized configuration information for the vehicle;

[0050] Based on the basic configuration information and personalized configuration information, determine the link nodes involved in at least one service function of the vehicle;

[0051] Based on the link nodes involved in the at least one service function, determine the service link monitoring strategy for the corresponding service link of the at least one service function;

[0052] Optionally, in one implementation of this application embodiment, the monitoring mode information includes at least one or more different monitoring modes selected from full-state monitoring, monitoring when an anomaly occurs, link monitoring, and no monitoring;

[0053] The monitoring object information includes at least full service monitoring, specified service monitoring, specified service method monitoring, specified service event monitoring, and specified service field monitoring;

[0054] Optionally, in one implementation of this application embodiment, the device further includes a storage module (not shown in the figures), which is used to cache or persistently store the monitoring information generated by each link node on the service link corresponding to the at least one service function locally on the vehicle; correspondingly, the service link monitoring strategy further includes: based on a preset data backflow mechanism, adding the cached or persistently stored monitoring information locally on the vehicle to the business data and then backflowing it to the cloud server.

[0055] Optionally, in one implementation of this application embodiment, the device further includes an identification module (not shown in the figures), the identification module being used to generate unique identification information for service proxy requests and establish a mapping relationship between the unique identification information and the monitoring information, for determining the monitoring information to be fed back to the cloud server.

[0056] Optionally, in one implementation of this application embodiment, the device adds a module (not shown in the figures), which is used to add corresponding data flow timestamp information or business data execution timestamp information to the monitoring information on the generated link node, so as to achieve orderly data tracking.

[0057] Optionally, in one implementation of this application embodiment, the synchronization module 202 is further configured to: store the service link monitoring strategy corresponding to the vehicle on the cloud server; and when it is determined that the vehicle establishes a service link with the cloud server, transmit the vehicle-cloud service link monitoring strategy corresponding to the vehicle to the vehicle terminal.

[0058] [Correction based on Rule 91, August 25, 2025] The vehicle-cloud service link monitoring device provided in this application includes a setting and determining module that determines at least one service link monitoring strategy for the vehicle based on the link nodes involved in the vehicle's service functions, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information; a setting and synchronization module that synchronizes the service link monitoring strategy configured on the vehicle's in-vehicle terminal and cloud server based on the vehicle corresponding to the service link monitoring strategy; and a setting and configuration module that, based on the synchronized service link monitoring strategy, obtains the configuration result of the in-vehicle terminal monitoring the service link according to the service link monitoring strategy, wherein the configuration result is used for... This indicates the success or failure of configuring link monitoring for at least one service function of the vehicle according to the service link monitoring strategy. The monitoring module generates corresponding monitoring information for each link node in the service link involved in the service proxy request based on the service link monitoring strategy configured on the vehicle terminal when the vehicle receives or generates a service proxy request. The analysis module adds the monitoring information to the business data during the service proxy request flow and feeds it back to the cloud server. The cloud server then extracts one or more monitoring information from the business data to determine the monitoring result of the vehicle-cloud service link used by the at least one service function. The vehicle-cloud service link monitoring device provided in this application, by configuring a service link monitoring strategy, generates corresponding link monitoring information when each data flow and execution node of the vehicle-cloud service receives a service instruction. This information is then integrated with the service business data and sent to the cloud server for analysis to complete the monitoring of the service link between the vehicle and the cloud. During the monitoring process, there is no need to set up monitoring points or establish a separate monitoring system, effectively reducing the cost of vehicle-cloud service link monitoring and ensuring the timeliness of monitoring.

[0059] Example 3

[0060] This application also provides a storage medium storing a computer program that, when executed by a processor, implements any of the vehicle-cloud service link monitoring methods described in Embodiment 1 of this application.

[0061] The methods for monitoring the vehicle-cloud service link include, but are not limited to:

[0062] Based on the link nodes involved in the vehicle's service functions, at least one service link monitoring strategy for the vehicle is determined, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information.

[0063] Based on the vehicle corresponding to the service link monitoring strategy, the service link monitoring strategy configured on the vehicle's in-vehicle terminal and cloud server is synchronized.

[0064] [Corrected according to detailed rule 91 25.08.2025] Based on the synchronized service link monitoring strategy, obtain the configuration result of the vehicle terminal monitoring the service link of the vehicle terminal according to the service link monitoring strategy. The configuration result is used to indicate whether the link monitoring configuration of at least one service function of the vehicle is successful or not according to the service link monitoring strategy.

[0065] When the vehicle receives or generates a service proxy request, based on the service link monitoring strategy configured on the vehicle terminal, corresponding monitoring information is generated for each link node on the service link involved in the service proxy request.

[0066] The monitoring information is added to the business data during the service proxy request flow and then fed back to the cloud server. The cloud server then extracts one or more monitoring information from the business data to determine the monitoring result of the vehicle-cloud service link used by the at least one service function.

[0067] Example 4

[0068] This application also provides an electronic device, as shown in FIG3. FIG3 is a schematic diagram of the structure of an electronic device 30 provided in this application embodiment. The electronic device 30 includes:

[0069] One or more processors 301;

[0070] Memory 302 is used to store one or more programs;

[0071] When the one or more programs are executed by the one or more processors 303, causing the one or more processors to perform the operations corresponding to any of the vehicle-cloud service link monitoring methods described in Embodiment 1 of this application, the method includes:

[0072] Based on the link nodes involved in the vehicle's service functions, at least one service link monitoring strategy for the vehicle is determined, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information.

[0073] Based on the vehicle corresponding to the service link monitoring strategy, the service link monitoring strategy configured on the vehicle's in-vehicle terminal and cloud server is synchronized.

[0074] [Corrected according to detailed rule 91 25.08.2025] Based on the synchronized service link monitoring strategy, obtain the configuration result of the vehicle terminal monitoring the service link of the vehicle terminal according to the service link monitoring strategy. The configuration result is used to indicate whether the link monitoring configuration of at least one service function of the vehicle is successful or not according to the service link monitoring strategy.

[0075] When the vehicle receives or generates a service proxy request, based on the service link monitoring strategy configured on the vehicle terminal, corresponding monitoring information is generated for each link node on the service link involved in the service proxy request.

[0076] After the monitoring information is added to the business data in the service proxy request flow process, it is fed back to the cloud server so that the cloud server can extract one or more monitoring information from the business data to determine the monitoring result of the vehicle cloud service link used by the at least one service function.

[0077] This application has now described specific embodiments of the subject matter. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing can be advantageous.

[0078] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system layer onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0079] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0080] The system layers, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0081] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0082] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0083] Those skilled in the art will understand that embodiments of this application can be provided as methods, system-level, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0084] This application can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific transactions or implement specific abstract data types. This application can also be practiced in distributed computing environments where transactions are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0085] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system-level embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0086] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. [Corrected according to detailed rule 91, August 25, 2025] A method for monitoring vehicle-cloud service links, characterized in that, include: Based on the link nodes involved in the vehicle's service functions, at least one service link monitoring strategy for the vehicle is determined, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information. Based on the vehicle corresponding to the service link monitoring strategy, the service link monitoring strategy configured on the vehicle's in-vehicle terminal and cloud server is synchronized. Based on the synchronized service link monitoring strategy, the configuration result of the vehicle terminal monitoring the service link according to the service link monitoring strategy is obtained. The configuration result is used to indicate whether the link monitoring configuration for at least one service function of the vehicle is successful or not. When the vehicle receives or generates a service proxy request, based on the service link monitoring strategy configured on the vehicle terminal, corresponding monitoring information is generated for each link node on the service link involved in the service proxy request. After the monitoring information is added to the business data in the service proxy request flow process, it is fed back to the cloud server so that the cloud server can extract one or more monitoring information from the business data to determine the monitoring result of the vehicle cloud service link used by the at least one service function.

2. The method for monitoring the vehicle-to-cloud service link according to claim 1, characterized in that, The vehicle-based service functions involve link nodes, and at least one service link monitoring strategy for the vehicle is determined, including: Determine the vehicle's basic configuration information and the user's personalized configuration information for the vehicle; Based on the basic configuration information and personalized configuration information, determine the link nodes involved in at least one service function of the vehicle; Based on the link nodes involved in the at least one service function, determine the service link monitoring strategy for the corresponding service link of the at least one service function.

3. The method for monitoring the vehicle-to-cloud service link according to claim 1, characterized in that, The monitoring mode information includes at least one or more different monitoring modes among full-state monitoring, monitoring when an anomaly occurs, link monitoring, and no monitoring. The monitoring object information includes at least one or more of the following: full service monitoring, specified service monitoring, specified service method monitoring, specified service event monitoring, and specified service field monitoring.

4. The method for monitoring the vehicle-to-cloud service link according to claim 1, characterized in that, The method further includes: caching or persistently storing monitoring information generated by each link node on the service link corresponding to the at least one service function locally on the vehicle. Correspondingly, the service link monitoring strategy also includes: based on a preset data backflow mechanism, adding the monitoring information cached or persistently stored locally on the vehicle to the business data and then backflowing it to the cloud server.

5. The method for monitoring the vehicle-to-cloud service link according to claim 4, characterized in that, It is characterized in that The method further includes: generating unique identifier information for service proxy requests and establishing a mapping relationship between the unique identifier information and the monitoring information, used to determine the monitoring information to be fed back to the cloud server.

6. The method for monitoring the vehicle-to-cloud service link according to claim 1, characterized in that, The method further includes adding corresponding data flow timestamp information or business data execution timestamp information to the monitoring information on the generated link nodes to achieve orderly data tracking.

7. The method for monitoring the vehicle-to-cloud service link according to claim 1, characterized in that, The synchronization of the service link monitoring policies configured on the vehicle's in-vehicle terminal and cloud server for the vehicle corresponding to the service link monitoring policy includes: The service link monitoring policy corresponding to the vehicle is stored on the cloud server. When it is determined that the vehicle has established a service link with the cloud server, the vehicle-cloud service link monitoring policy corresponding to the vehicle is transmitted to the vehicle terminal.

8. [Corrected according to Rule 91, August 25, 2025] A device for monitoring vehicle-to-cloud service links, characterized in that, include: The determination module is used to determine at least one service link monitoring strategy for the vehicle based on the link nodes involved in the vehicle's service functions, wherein the service link monitoring strategy includes at least monitoring mode information and monitoring object information. The synchronization module is used to synchronize the service link monitoring policies configured on the vehicle's in-vehicle terminal and the cloud server based on the vehicle corresponding to the service link monitoring policy. The configuration module is used to obtain the configuration result of the vehicle terminal monitoring the service link according to the synchronized service link monitoring strategy. The configuration result is used to indicate whether the link monitoring configuration for at least one service function of the vehicle is successful or not. The monitoring module, when the vehicle receives or generates a service proxy request, generates corresponding monitoring information for each link node on the service link involved in the service proxy request based on the service link monitoring strategy configured on the vehicle terminal. The analysis module is used to add the monitoring information to the business data in the service proxy request flow process and then feed it back to the cloud server so that the cloud server can extract one or more monitoring information from the business data to determine the monitoring results of the vehicle-cloud service link used by the at least one service function.

9. A computer storage medium, characterized in that, The computer storage medium stores computer-executable instructions, which, when executed, perform the vehicle-cloud service link monitoring method as described in any one of claims 1-7.

10. An electronic device, characterized in that, include: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the vehicle-cloud service link monitoring method as described in any one of claims 1-7.

Images