Vehicle-mounted service data acquisition method, system, equipment and medium

By building a master-slave structure in the automotive field, service-based data collection is realized, the problem of insufficient service-based data collection in the existing technology is solved, and the feedback and user experience of service quality is improved.

CN119071335APending Publication Date: 2024-12-03UNITED AUTOMOTIVE ELECTRONICS SYST
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410840763.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-06-27
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The existing technology lacks effective service-based data collection methods in the automotive field, resulting in the inability to provide timely feedback on the service quality of vehicle-side applications, affecting the user experience.

Method used

By building a master-slave structure on the vehicle end, the master-slave node receives cloud data acquisition requests, matches auxiliary nodes, subscribes to target nodes and application services, collects and preprocesses service data, and feeds back to the cloud to realize customized service data acquisition.

Benefits of technology

It realizes flexible collection and analysis of service-oriented data on the vehicle side, meets different service data needs, and improves the feedback and user experience of application service quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071335A_ABST
    Figure CN119071335A_ABST
Patent Text Reader

Abstract

The invention also provides a vehicle-mounted servitization data acquisition method, system, device and medium, the method comprises the following steps: receiving a data acquisition request of a cloud through a main acquisition node to match an auxiliary acquisition node in response to the data acquisition request to obtain a target node, the data acquisition request comprising a data acquisition strategy, and the auxiliary acquisition node comprising the data acquisition strategy; the main collection node is connected with a plurality of auxiliary collection nodes; subscribing the target node and / or the application service under the target node to receive corresponding service data, preprocessing the service data according to the data acquisition strategy, and feeding back the preprocessed service data to the cloud. According to the application, the service data is sent to the main acquisition node after data packaging and frequency reduction are carried out through the auxiliary acquisition node, so that the bus utilization rate can be improved, and the occupation of system resources by the auxiliary acquisition node is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of vehicle control, and in particular to a vehicle-mounted service data collection method, system, device and medium. Background Art

[0002] At present, the cross-domain fusion architecture in the automotive field usually integrates functions such as autonomous driving domain, chassis domain, body domain, gateway domain, etc., and the service requirements and implementation level of each domain are getting higher and higher. Big data collection has added the demand for service data collection on the original CAN collection technology, so as to analyze the data behavior in the service-oriented architecture.

[0003] However, most of the existing methods are based on CAN data collection, which collects bus data through a gateway and analyzes and identifies it on the vehicle side. Service-oriented data collection is less involved. How to realize service-oriented data collection on the vehicle side is an urgent problem that needs to be solved. Summary of the invention

[0004] In view of the above problems existing in the prior art, the present invention proposes a vehicle-mounted service data collection method, system, device and medium, which mainly solves the current lack of service data collection means, the inconvenience of analyzing data under the service-oriented architecture, and the inability to obtain timely feedback on the quality of vehicle-side application services, which in turn affects the user experience.

[0005] In order to achieve the above purpose and other purposes, the technical solution adopted by the present invention is as follows.

[0006] The present application also provides a vehicle-mounted service-oriented data collection method, which is applied to the vehicle side. The method includes: receiving a data collection request from the cloud through a main collection node, matching an auxiliary collection node in response to the data collection request, and obtaining a target node, wherein the data collection request includes a data collection strategy, and the main collection node is connected to multiple auxiliary collection nodes; subscribing to the target node and / or the application service under the target node to receive corresponding service data, and pre-processing the service data according to the data collection strategy and then feeding it back to the cloud.

[0007] In one embodiment of the present application, before receiving the data collection request from the cloud through the main collection node, it also includes: selecting at least one from a plurality of vehicle-side controllers as the main collection node, and the remaining vehicle-side controllers as the auxiliary collection nodes and respectively establishing communication connections with the main collection node to form a data collection network; wherein the auxiliary collection nodes correspond to multiple application services.

[0008] In one embodiment of the present application, in response to the data collection request, the auxiliary collection node is matched to obtain the target node, including: determining the target service according to the data collection strategy; and determining the corresponding auxiliary collection node as the target node according to the attribution of the target service.

[0009] In one embodiment of the present application, subscribing to the target node to receive corresponding service data includes: subscribing to the target node, and generating a data message according to the target service and sending it to the target node, so that the target node subscribes to the corresponding application service based on the data message to obtain the service data.

[0010] In one embodiment of the present application, the target node constructs a data table according to the data volume of the subscribed application service, so as to record the service data fed back by the subscribed application service through the data table, and uniformly packages and sends it to the main acquisition node.

[0011] In one embodiment of the present application, the main acquisition node stores the service data after receiving it, and shares the stored service data in response to a subscription request of the main acquisition node application other than the data acquisition request.

[0012] The present application also provides a vehicle-mounted service-oriented data collection method, characterized in that it is applied to the cloud, and the method includes: generating a data collection strategy according to data collection requirements; generating a data collection request according to the data collection strategy, and sending the data collection request to the main collection node on the vehicle side, so that the main collection node matches the auxiliary collection node in response to the data collection request to obtain a target node; subscribing to the target node and / or the application service under the target node through the main collection node to receive corresponding service data, and pre-processing the service data according to the data collection strategy and then feeding it back to the cloud, wherein the main collection node is connected to multiple auxiliary collection nodes.

[0013] The present application also provides a vehicle-mounted service-oriented data acquisition system, including: a cloud side, used to generate a data acquisition request according to a data acquisition strategy; a vehicle side, which includes a main acquisition node and multiple auxiliary acquisition nodes, and the main acquisition node and the auxiliary acquisition nodes are connected; the main acquisition node receives the data acquisition request, matches the auxiliary acquisition node in response to the data acquisition request, and obtains a target node; the main acquisition node subscribes to the target node and / or the application service under the target node to receive corresponding service data, and pre-processes the service data according to the data acquisition strategy and feeds it back to the cloud side.

[0014] The present application also provides a computer device, which includes a processor and a memory; the memory is used to store a computer program; and the processor is used to execute the vehicle-mounted service data collection method according to the computer program.

[0015] The present application also provides a computer-readable storage medium, which is used to store a computer program, and the computer program is used in the in-vehicle service data collection method.

[0016] As described above, the vehicle-mounted service data collection method, system, device and medium proposed in this application have the following beneficial effects.

[0017] By building a master-slave structure of main and auxiliary nodes on the vehicle side, targeted service data collection can be performed on the vehicle-side application services in response to data collection requests on the cloud side, so that the cloud side can perform data behavior analysis on the service data. The cloud side can flexibly implement data collection strategies to meet different service data collection needs and realize customized service data collection. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a flowchart of the vehicle service data collection method in one embodiment of the present application.

[0019] Figure 2 This is a schematic diagram of the overall architecture of the vehicle-side data acquisition network in one embodiment of the present application.

[0020] Figure 3 This is a schematic diagram of auxiliary procurement node data transmission in one embodiment of the present application.

[0021] Figure 4 This is a flow chart of a vehicle-based service data collection method in another embodiment of the present application.

[0022] Figure 5 This is a timing diagram of vehicle-based service data collection in one embodiment of the present application.

[0023] Figure 6 This is a module diagram of a vehicle-mounted service data collection system in one embodiment of the present application. Figure 7 Schematic diagram of the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0024] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0025] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0026] See also Figure 1 , Figure 1 The flowchart of the vehicle service data collection method in one embodiment of the present application is as follows. The vehicle service data collection method in one embodiment of the present application, which is applied to the vehicle side, includes the following steps:

[0027] Step S100, receiving a data collection request from the cloud through a main collection node, matching an auxiliary collection node in response to the data collection request, and obtaining a target node, wherein the data collection request includes a data collection strategy, and the main collection node is connected to a plurality of auxiliary collection nodes;

[0028] In one embodiment, one vehicle-side controller can be selected as the main acquisition node, and the remaining vehicle-side controllers can be used as auxiliary acquisition nodes. The main acquisition node and the auxiliary acquisition node can establish a communication connection through the Ethernet bus to form a data acquisition network. The vehicle-side controller may include a central controller, an autonomous driving domain controller, a chassis domain controller, etc. Of course, multiple main acquisition nodes can also be selected and set according to the business type or other acquisition requirements corresponding to the service data. Each main acquisition node is connected to the vehicle-side controller of the corresponding business type according to the business classification or cloud acquisition requirements to form multiple data acquisition networks. After receiving the data acquisition request from the cloud, each main acquisition node can automatically adapt according to the business type or service division rules. Of course, the selection and setting method of the specific main acquisition node and auxiliary acquisition node can also be flexibly adjusted according to the actual application requirements, which is not limited here.

[0029] See also Figure 2 , Figure 2 The overall architecture diagram of the vehicle-side data acquisition network in one embodiment of the present application. Taking the central controller as the main acquisition node as an example, the central controller can be connected to the vehicle controller, ADAS controller (autonomous driving domain controller) and other regional controllers through Ethernet. The central controller can be used as the main acquisition node, and each controller connected to the central controller can be used as an auxiliary acquisition node. The main acquisition node can subscribe to the auxiliary acquisition node, or directly subscribe to the application service in the auxiliary acquisition node; each auxiliary acquisition node can correspond to each application service. The application service belonging to the corresponding controller is the application service hanging under the corresponding auxiliary acquisition node, and the auxiliary acquisition node can also subscribe to its own internal application service to collect its own service data. Exemplarily, the main acquisition node and the auxiliary acquisition node, the auxiliary acquisition node and the application service, and the main acquisition node and the application service can be subscribed and published through the service-oriented communication protocol to transmit service data. The service-oriented communication protocol includes but is not limited to SOME / IP, DDS or other customized service-oriented communication protocols.

[0030] In one embodiment, the cloud can establish a communication connection with the main acquisition node on the vehicle side through the Internet of Vehicles module T-BOX. The cloud can generate a data acquisition request based on the actual service data acquisition requirements, and the data acquisition request includes a data acquisition strategy. The data acquisition strategy may include the application services that need to be collected and the screening method of service data, etc., which can be flexibly configured according to the actual application requirements and are not limited here.

[0031] In one embodiment, in response to the data collection request, the auxiliary procurement node is matched to obtain the target node, including: determining the target service according to the data collection strategy; determining the corresponding auxiliary procurement node as the target node according to the ownership of the target service. Exemplarily, the data collection strategy may be configured with a unique identifier of the application service that needs to be collected, that is, the unique identifier of the target service, so that the data collection request contains the unique identifier of the required application service, and the main procurement node may match the corresponding application service based on the unique identifier or determine the auxiliary procurement node to which the corresponding application service belongs. Specifically, the main procurement node may store a list of application services that can be provided by each auxiliary procurement node, and the main procurement node may determine which auxiliary procurement node the target service corresponding to the unique identifier belongs to by looking up a table, and use the auxiliary procurement node that matches the unique identifier as the target node.

[0032] Step S110, subscribing to the target node and / or the application service under the target node to receive corresponding service data, and pre-processing the service data according to the data collection strategy and then feeding back to the cloud.

[0033] In one embodiment, subscribing to the target node to receive the corresponding service data includes: subscribing to the target node, and generating a data message according to the target service and sending it to the target node, so that the target node subscribes to the corresponding application service based on the data message to obtain the service data. Specifically, after determining the target service required by the cloud, the main acquisition node matches one or more auxiliary acquisition nodes as target nodes based on the target service-related configuration information in the data acquisition strategy, and generates a data message according to the relevant configuration information of the target service and sends it to the target node. The target node determines the application service that needs to be collected by parsing the data message, and then subscribes to the corresponding application service to obtain the service data published by the application service. Each target node subscribes and collects data for the application service that belongs to it.

[0034] In one embodiment, the target node constructs a data table according to the data volume of the subscribed application service, so as to record the service data fed back by the subscribed application service through the data table, and send it to the main acquisition node after unified packaging. Specifically, in order to avoid the auxiliary acquisition node from frequently transmitting data with the main acquisition node and occupying too many system resources, the auxiliary acquisition node can construct a data table according to the data volume of the target service to be collected. When the data volume is lower than the set threshold, each collected service data can be transmitted separately, and when the data volume is greater than the set threshold, a data table can be established to record the service data corresponding to each target service. After completing the service data collection of all target services in the current auxiliary acquisition node, a data packet is generated based on the data table and sent to the main acquisition node. Only one transmission is required to complete the data collection. Of course, when the data volume is large enough, multiple data tables can also be constructed, and batch service data transmission can be performed by batch packaging and transmission. Exemplarily, data can be batched according to the priority of different application services, and the specific priority can be configured through the cloud. The specific data packaging and uploading method and frequency can also be set and adjusted according to actual application needs, which is not limited here. Of course, the auxiliary procurement node can also use the collected service data of multiple application services to construct a specific data structure, which is not limited to the form of a data table. For example, the data structure can be a one-dimensional vector. The specific data structure can be configured and adjusted according to application requirements, and there is no limitation here.

[0035] In one embodiment, after determining the target node to which the target service belongs, the main procurement node may also directly communicate with the target node, directly subscribe to the corresponding application service in the target node, and obtain the corresponding service data. Whether to obtain service data fed back by the auxiliary procurement node or to directly subscribe to the application service for data collection can be determined based on the data collection strategy configured in the cloud. If the target service to be collected in the data collection strategy is the application service belonging to a specific auxiliary procurement node, the main procurement node subscribes to the target node to obtain service data; if the data collection strategy includes not only application services belonging to a specific auxiliary procurement node, but also some application services belonging to unclassified controllers, the main procurement node can directly subscribe to the application service in the corresponding controller to directly collect service data. Please refer to Figure 3 , Figure 3This is a schematic diagram of data transmission of auxiliary procurement nodes in one embodiment of the present application. Taking the central controller as the main procurement node, the regional controller and other controllers as auxiliary procurement nodes as an example, the central controller needs to collect services 1, 2 and 3 in the regional controller, and also needs to collect services 5 and 6 in other controllers. The central controller subscribes to services 5 and 6 in the regional controller and other controllers. The regional controller can subscribe to services 1, 2 and 3 to obtain service 1 data, service 2 data and service 3 data, and then package the data and send it to the central controller. Services 4 and 6 in other controllers can directly send the subscribed service data to the central controller.

[0036] In one embodiment, the main acquisition node stores the service data after receiving it, and shares the stored service data in response to the subscription request of the main acquisition node application other than the data acquisition request. Specifically, the main acquisition node can store the service data fed back by the auxiliary acquisition node after receiving it. When the application belonging to the main acquisition node needs to call the corresponding service data, it can directly access the service data stored in the main acquisition node, and no longer needs to repeatedly access the auxiliary acquisition node for subscription. That is, the auxiliary acquisition node only needs to provide subscription data to the main acquisition node once. In addition to the target service currently required by the cloud in the main acquisition node, other applications also subscribe to the same application service of the auxiliary acquisition node, which will not increase the number of data packets of the auxiliary acquisition node, and can reduce the system resource occupancy of the auxiliary acquisition node. The auxiliary acquisition node sends the service data to the main acquisition node through data packaging and frequency reduction, which can improve the bus utilization rate and reduce the transmission processing overhead between the auxiliary acquisition node and the main acquisition node.

[0037] Based on the technical solution of the above embodiment of the present application, the cloud can configure the data collection strategy of the main acquisition node on the vehicle side through the vehicle-cloud interaction protocol. The main acquisition node subscribes to the service of the auxiliary acquisition node that needs to be collected through the service-oriented protocol. The main acquisition node can also directly subscribe to the application services in other controllers through the service-oriented protocol for data collection. The auxiliary acquisition node subscribes to the service data that needs to be collected from each local application service, and packages the service data and sends it to the main acquisition node through the service-oriented protocol. After receiving the service data of the auxiliary acquisition node, the main acquisition node filters or performs other pre-processing on the collected service data according to the data collection strategy and sends it to the cloud. The auxiliary acquisition node sends the service data to the main acquisition node after data packaging and frequency reduction, which can reduce the occupation of system resources by the auxiliary acquisition node; the cloud can flexibly configure the service data that needs to be collected, and collect data based on the distributed architecture of the data collection network, so as to accurately collect the required service data, and there is no redundant data occupying vehicle-side resources.

[0038] See also Figure 4 , Figure 4This is a flow chart of a vehicle-mounted service data collection method in another embodiment of the present application. The vehicle-mounted service data collection method of this embodiment is applied to the cloud, and the method includes the following steps:

[0039] Step S400: Generate a data collection strategy according to data collection requirements.

[0040] Specifically, data collection requirements can be flexibly configured on the cloud, such as the application services and regional controllers that need to be collected, the type and format of the collected data returned to the cloud, etc., and corresponding data collection strategies can be generated based on data collection requests.

[0041] Step S410, generates a data acquisition request according to the data acquisition strategy, and sends the data acquisition request to the main acquisition node on the vehicle side, so that the main acquisition node matches the auxiliary acquisition node in response to the data acquisition request to obtain the target node; subscribes to the target node and / or the application service under the target node through the main acquisition node to receive corresponding service data, and pre-processes the service data according to the data acquisition strategy and feeds it back to the cloud, wherein the main acquisition node is connected to multiple auxiliary acquisition nodes.

[0042] See also Figure 5 , Figure 5 This is a timing diagram of vehicle-mounted service-oriented data collection in one embodiment of the present application. Take the central controller as the main procurement node and the regional controller as the auxiliary procurement node as an example. The central controller is provided with a main procurement module, and the regional controller is provided with an auxiliary procurement module and a regional controller service. The specific process is as follows: the cloud configures the service-oriented collection strategy of the main procurement module on the vehicle side through the vehicle-cloud interaction protocol; the main procurement module subscribes to the service of the auxiliary procurement module that needs to be collected through SOME / IP, or the main procurement module directly subscribes to the service-oriented data to be collected from other controllers through SOME / IP; the auxiliary procurement module subscribes to the service data that needs to be collected from each local service program; the local service module of the auxiliary procurement node sends the service data to the auxiliary procurement module; the auxiliary procurement module packages the received local service data and sends it to the main procurement node through SOME / IP; the main procurement module receives the service data in other subscribed controllers; the main procurement module screens the collected service data according to the service-oriented collection strategy and sends it to the cloud.

[0043] In one embodiment, see Figure 6 , Figure 6This is a module diagram of an on-board service-oriented data acquisition system in one embodiment of the present application, the system includes: a cloud end 60, used to generate a data acquisition request according to a data acquisition strategy; a vehicle end 61, which includes a main acquisition node and multiple auxiliary acquisition nodes, and the main acquisition node and the auxiliary acquisition nodes are connected; the main acquisition node receives the data acquisition request, matches the auxiliary acquisition node in response to the data acquisition request, and obtains a target node; the main acquisition node subscribes to the target node and / or the application service under the target node to receive corresponding service data, and pre-processes the service data according to the data acquisition strategy and feeds it back to the cloud end.

[0044] The above-mentioned vehicle-mounted service data collection system can be implemented in the form of a computer program. The computer program can be implemented in the form of Figure 7 The computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0045] Each module in the above-mentioned vehicle-mounted service data collection system can be implemented in whole or in part by software, hardware and their combination. Each of the above-mentioned modules can be embedded in or independent of the terminal's memory in the form of hardware, or can be stored in the terminal's memory in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules. The processor can be a central processing unit (CPU), a microprocessor, a single-chip microcomputer, etc.

[0046] like Figure 7 The figure shows a schematic diagram of the internal structure of a computer device in one embodiment. A computer device is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program: receiving a data acquisition request from the cloud through a main acquisition node, matching an auxiliary acquisition node in response to the data acquisition request, and obtaining a target node, wherein the data acquisition request includes a data acquisition strategy, and the main acquisition node is connected to a plurality of auxiliary acquisition nodes; subscribing to the target node and / or the application service under the target node to receive corresponding service data, and pre-processing the service data according to the data acquisition strategy and feeding it back to the cloud.

[0047] In one embodiment, when the above-mentioned processor is executed, before receiving the data collection request from the cloud through the main collection node, it also includes: selecting at least one from a plurality of vehicle-side controllers as the main collection node, and the remaining vehicle-side controllers as the auxiliary collection nodes and respectively establishing communication connections with the main collection node to form a data collection network; wherein the auxiliary collection nodes correspond to multiple application services.

[0048] In one embodiment, when the above-mentioned processor is executed, the auxiliary procurement node is matched in response to the data acquisition request to obtain the target node, including: determining the target service according to the data acquisition strategy; determining the corresponding auxiliary procurement node as the target node according to the attribution of the target service.

[0049] In one embodiment, when the above-mentioned processor is executed, the subscription to the target node to receive corresponding service data includes: subscribing to the target node, and generating a data message according to the target service and sending it to the target node, so that the target node subscribes to the corresponding application service based on the data message to obtain the service data.

[0050] In one embodiment, when the above-mentioned processor is executed, the target node implemented builds a data table according to the data volume of the subscribed application service, so as to record the service data fed back by the subscribed application service through the data table, and uniformly packages it and sends it to the main acquisition node.

[0051] In one embodiment, when the above-mentioned processor is executed, the main acquisition node implemented stores the service data after receiving it, and shares the stored service data in response to a subscription request of the main acquisition node application other than the data acquisition request.

[0052] In one embodiment, the above-mentioned computer device can be used as a server, including but not limited to an independent physical server, or a server cluster composed of multiple physical servers. The computer device can also be used as a terminal, including but not limited to a mobile phone, a tablet computer, a personal digital assistant or a smart device. Figure 7 As shown, the computer device includes a processor, a non-volatile storage medium, an internal memory, a display screen, and a network interface connected via a system bus.

[0053] Among them, the processor of the computer device is used to provide computing and control capabilities to support the operation of the entire computer device. The non-volatile storage medium of the computer device stores an operating system and a computer program. The computer program can be executed by the processor to implement a vehicle-mounted service data collection method provided in the above embodiments. The internal memory in the computer device provides a cache operating environment for the operating system and computer program in the non-volatile storage medium. The display interface can display data through a display screen. The display screen can be a touch screen, such as a capacitive screen or an electronic screen, and can generate corresponding instructions by receiving a click operation acting on a control displayed on the touch screen.

[0054] Those skilled in the art will understand that Figure 7The structure of the computer device shown in the figure is only a block diagram of a partial structure related to the present application scheme, and does not constitute a limitation on the computer device to which the present application scheme is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0055] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: receiving a data acquisition request from the cloud through a main acquisition node, matching an auxiliary acquisition node in response to the data acquisition request, and obtaining a target node, wherein the data acquisition request includes a data acquisition strategy, and the main acquisition node is connected to multiple auxiliary acquisition nodes; subscribing to the target node and / or the application service under the target node to receive corresponding service data, and pre-processing the service data according to the data acquisition strategy and then feeding it back to the cloud.

[0056] In one embodiment, when the computer program is executed by the processor, before receiving the data collection request from the cloud through the main collection node, it also includes: selecting at least one from a plurality of vehicle-side controllers as the main collection node, and the remaining vehicle-side controllers as the auxiliary collection nodes and establishing communication connections with the main collection node respectively to form a data collection network; wherein the auxiliary collection nodes correspond to multiple application services.

[0057] In one embodiment, when the computer program is executed by a processor, the auxiliary procurement node is matched in response to the data acquisition request to obtain the target node, including: determining the target service according to the data acquisition strategy; and determining the corresponding auxiliary procurement node as the target node according to the attribution of the target service.

[0058] In one embodiment, when the computer program is executed by a processor, the subscription to the target node to receive corresponding service data includes: subscribing to the target node, and generating a data message based on the target service and sending it to the target node, so that the target node subscribes to the corresponding application service based on the data message to obtain the service data.

[0059] In one embodiment, when the computer program is executed by a processor, the target node implemented constructs a data table according to the data volume of the subscribed application service, so as to record the service data fed back by the subscribed application service through the data table, and uniformly packages it and sends it to the main acquisition node.

[0060] In one embodiment, when the computer program is executed by a processor, the main acquisition node implemented stores the service data after receiving it, and shares the stored service data in response to a subscription request of the main acquisition node application other than the data acquisition request.

[0061] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only memory (ROM), etc.

[0062] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. A vehicle-mounted service data collection method, characterized in that: Applied to the vehicle side, the method includes: Receiving a data collection request from the cloud through a main acquisition node, matching an auxiliary acquisition node in response to the data collection request, and obtaining a target node, wherein the data collection request includes a data collection strategy, and the main acquisition node is connected to a plurality of auxiliary acquisition nodes; Subscribe to the target node and / or the application service under the target node to receive corresponding service data, and pre-process the service data according to the data collection strategy and then feed it back to the cloud.

2. The vehicle-mounted service data collection method according to claim 1, characterized in that: Before receiving the data collection request from the cloud through the main collection node, it also includes: At least one is selected from a plurality of vehicle-side controllers as the main acquisition node, and the remaining vehicle-side controllers are selected as auxiliary acquisition nodes and respectively establish communication connections with the main acquisition node to form a data acquisition network; wherein the auxiliary acquisition nodes correspond to a plurality of application services.

3. The vehicle-mounted service data collection method according to claim 2, characterized in that: In response to the data collection request, matching the auxiliary collection node to obtain a target node includes: Determining target services according to the data collection strategy; According to the attribution of the target service, the corresponding auxiliary procurement node is determined as the target node.

4. The vehicle-mounted service data collection method according to claim 3, characterized in that: Subscribing to the target node to receive corresponding service data includes: Subscribe to the target node, and generate a data message according to the target service and send it to the target node, so that the target node subscribes to the corresponding application service based on the data message to obtain the service data.

5. The vehicle-mounted service data collection method according to claim 4, characterized in that: The target node constructs a data table according to the data volume of the subscribed application service, so as to record the service data fed back by the subscribed application service through the data table, and sends the data to the main acquisition node after unified packaging.

6. The vehicle-mounted service data collection method according to claim 1, characterized in that: The main acquisition node stores the service data after receiving it, and shares the stored service data in response to a subscription request of the main acquisition node application other than the data acquisition request.

7. A vehicle-mounted service data collection method, characterized in that: Applied to the cloud, the method includes: Generate data collection strategies based on data collection requirements; A data collection request is generated according to the data collection strategy, and the data collection request is sent to the main collection node on the vehicle side, so that the main collection node matches the auxiliary collection node in response to the data collection request to obtain the target node; the target node and / or the application service under the target node is subscribed to by the main collection node to receive the corresponding service data, and the service data is pre-processed according to the data collection strategy and then fed back to the cloud, wherein the main collection node is connected to multiple auxiliary collection nodes.

8. A vehicle-mounted service data collection system, characterized in that: include: The cloud is used to generate data collection requests according to the data collection strategy; The vehicle end includes a main mining node and a plurality of auxiliary mining nodes, wherein the main mining node and the auxiliary mining nodes are connected; The main acquisition node receives the data acquisition request, matches the auxiliary acquisition node in response to the data acquisition request, and obtains a target node; The main acquisition node subscribes to the target node and / or the application service under the target node to receive corresponding service data, and pre-processes the service data according to the data acquisition strategy and then feeds it back to the cloud.

9. A computer device, characterized in that: The device includes a processor and a memory; The memory is used to store computer programs; The processor is used to execute the vehicle-mounted service data collection method according to any one of claims 1 to 6 according to the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and the computer program is used in the vehicle-mounted service data collection method according to any one of claims 1-6.