Vehicle data management method and device, server, and storage medium

Abstract

The application discloses a vehicle data management method and device, a server and a storage medium. The management method comprises the following steps: acquiring first vehicle data through a first type of service, wherein the first vehicle data is from a vehicle-mounted terminal; acquiring second vehicle data through a second type of service, wherein the second vehicle data is from a vehicle manufacturer platform, and the second vehicle data of the vehicle manufacturer platform is provided by the vehicle-mounted terminal; extracting target vehicle data from the first vehicle data and / or the second vehicle data, and sending the target vehicle data to a vehicle data demander platform. Thus, through the combination of two different sources of vehicle data corresponding to different services, various requirements of the new energy automobile industry for data communication can be flexibly coped with, effective data management is realized, and data maintenance is facilitated.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, apparatus, server, and storage medium for managing vehicle data. Background Technology

[0002] With the increasing intelligence and connectivity of automobiles, the application of big data involves all aspects of automakers. By remotely collecting big data from all vehicle models and systems, users can be provided with services such as vehicle status inquiries and maintenance suggestions to prevent malfunctions and improve the user experience. Simultaneously, big data can also be used in design and development to continuously improve vehicle quality and performance. Currently, the system architecture for vehicle data management is unable to meet the requirements of diversity, balance, and uncertainty in vehicle data sources, thus hindering effective management of vehicle data. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to overcome the shortcomings of the existing vehicle data management system architecture, which is unable to meet the requirements of diversity, balance and uncertainty of vehicle data sources and cannot achieve effective management of vehicle data. The present invention provides a vehicle data management method, device, server and storage medium.

[0004] The present invention solves the above-mentioned technical problems through the following technical solution:

[0005] A method for managing vehicle data, the method comprising:

[0006] The first vehicle data is obtained through the first type of service, and the first vehicle data comes from the vehicle terminal.

[0007] Second vehicle data is obtained through a second type of service. The second vehicle data comes from the vehicle manufacturer's platform, and the second vehicle data on the vehicle manufacturer's platform is provided by the vehicle terminal.

[0008] Extract target vehicle data from the first vehicle data and / or the second vehicle data, and send the target vehicle data to the vehicle data requester platform.

[0009] Optionally, after obtaining the first vehicle data through the first type of service, the process further includes:

[0010] The first vehicle data is processed according to a first preset rule; the first preset rule includes encryption rules and / or desensitization rules.

[0011] After obtaining the second vehicle data through the second type of service, it also includes:

[0012] The second vehicle data is processed according to the second preset rule; the second preset rule includes encryption rules and / or desensitization rules.

[0013] Optionally, it also includes:

[0014] The first vehicle data and the second vehicle data are stored in different storage spaces, and the data source of the first vehicle data or the second vehicle data stored in each storage space is the same; the data source includes at least one of the following: service source, vehicle terminal source, and vehicle manufacturer platform source.

[0015] Optionally, extracting target vehicle data from the first vehicle data and / or the second vehicle data includes:

[0016] In response to a vehicle data acquisition request, the corresponding target storage space is determined based on the data source information carried in the vehicle data acquisition request;

[0017] Extract data from the target storage space that matches the data type information carried in the vehicle data acquisition request as the target vehicle data.

[0018] Optionally, extracting target vehicle data from the first vehicle data and / or the second vehicle data includes:

[0019] Initial data corresponding to a preset field is extracted from the first vehicle data and / or the second vehicle data, and the preset field matches the permissions of the vehicle data requesting platform;

[0020] Target vehicle data is extracted from the initial data, and the target vehicle data is data that matches the search keywords provided by the vehicle data requesting platform.

[0021] Optionally, before obtaining the first vehicle data through the first type of service, the method further includes:

[0022] The system verifies the first signature data provided by the vehicle terminal based on the first public key, and triggers the first type of service to obtain the first vehicle data when the verification is successful; the first public key is provided by the vehicle terminal, and the first signature data is obtained by the vehicle terminal signing the target data according to the first private key corresponding to the first public key;

[0023] Alternatively, the system may obtain the first identity authentication information provided by the vehicle terminal, and trigger the first type of service to obtain the first vehicle data when it is determined that there is information in the stored registration information that matches the first identity authentication information.

[0024] or

[0025] Before obtaining the second vehicle data through the second type of service, the following is also included:

[0026] The second public key is used to verify the second signature data provided by the vehicle manufacturer platform, and the second type of service is triggered to obtain the second vehicle data when the verification is successful; the second public key is provided by the vehicle manufacturer platform, and the second signature data is obtained by the vehicle manufacturer platform signing the target data according to the second private key corresponding to the second public key;

[0027] Alternatively, the system may obtain the second identity authentication information provided by the vehicle manufacturer's platform, and trigger the second type of service to obtain the second vehicle data when it is determined that there is information in the stored registration information that matches the second identity authentication information.

[0028] Optionally, it also includes:

[0029] In response to a communication mode change request for an in-vehicle terminal, the system sends target communication mode information back to the vehicle manufacturer platform that sent the communication mode change request, so that the vehicle manufacturer platform changes the communication mode of the in-vehicle terminal to the target communication mode; the first vehicle data comes from the in-vehicle terminal whose communication mode is the target communication mode.

[0030] Optionally, the first type of service obtains the first vehicle data by communicating using the MQTT (Message Queuing Telemetry Transport) protocol or the MQTT-S (MQTT for Sensor Networks) protocol;

[0031] The second type of service is a cloud forwarding service, which uses a TCP (Transmission Control Protocol) long connection to obtain the second vehicle data;

[0032] The vehicle data demand-side platform includes at least one of the following: a battery swapping APP (application) big data platform, a battery swapping operation platform, and local government cloud platforms.

[0033] A method for managing vehicle data, the method comprising:

[0034] Acquire the first vehicle data from the vehicle terminal, and process the first vehicle data according to a preset rule to obtain the second vehicle data;

[0035] The second vehicle data is sent to the server, which then obtains the second vehicle data through a second type of service, extracts target vehicle data from the second vehicle data, and sends the target vehicle data to the vehicle data requester platform.

[0036] Optionally, the preset rules include retaining at least one of the following parameters in the first vehicle data: vehicle battery temperature, vehicle battery charge, vehicle battery status, vehicle location information, and vehicle mileage.

[0037] Optionally, it also includes:

[0038] Send a communication mode change request for the vehicle terminal to the server;

[0039] The server receives target communication mode information in response to the communication mode change request. The target communication mode is either the communication mode of a first type of service or the communication mode of a second type of service. The first type of service is used to obtain first vehicle data provided by the vehicle terminal.

[0040] The communication mode of the vehicle terminal is changed to the target communication mode, which is used to enable the vehicle terminal to establish a communication connection with the server.

[0041] A vehicle data management device, the management device comprising:

[0042] The first acquisition module is used to acquire first vehicle data through a first type of service, wherein the first vehicle data comes from the vehicle terminal.

[0043] The second acquisition module is used to acquire second vehicle data through a second type of service. The second vehicle data comes from the vehicle manufacturer's platform, and the second vehicle data of the vehicle manufacturer's platform is provided by the vehicle terminal.

[0044] The extraction module is used to extract target vehicle data from the first vehicle data and / or the second vehicle data, and send the target vehicle data to the vehicle data requester platform.

[0045] Optionally, the management device further includes a first data processing module and / or a second data processing module:

[0046] The first data processing module is used to process the first vehicle data according to a first preset rule; the first preset rule includes encryption rules and / or de-identification rules.

[0047] The second data processing module is used to process the second vehicle data according to a second preset rule; the second preset rule includes encryption rules and / or desensitization rules.

[0048] Optionally, the management device further includes a storage module;

[0049] The storage module is used to store the first vehicle data and the second vehicle data in different storage spaces, and the data source of the first vehicle data or the second vehicle data stored in each storage space is the same; the data source includes at least one of the following: service source, vehicle terminal source, and vehicle manufacturer platform source.

[0050] Optionally, the extraction module includes:

[0051] The determining unit is used to determine the corresponding target storage space in response to a vehicle data acquisition request, based on the data source information carried in the vehicle data acquisition request.

[0052] The extraction unit is used to extract data from the target storage space that matches the data type information carried in the vehicle data acquisition request as target vehicle data.

[0053] Optionally, the extraction module is specifically used for:

[0054] Initial data corresponding to a preset field is extracted from the first vehicle data and / or the second vehicle data, and the preset field matches the permissions of the vehicle data requesting platform;

[0055] Target vehicle data is extracted from the initial data, and the target vehicle data is data that matches the search keywords provided by the vehicle data requesting platform.

[0056] Optionally, the management device further includes:

[0057] The first authentication module is used to verify the first signature data provided by the vehicle terminal based on the first public key, and trigger the first type of service to obtain the first vehicle data when the verification is successful; the first public key is provided by the vehicle terminal, and the first signature data is obtained by the vehicle terminal signing the target data according to the first private key corresponding to the first public key; or, it obtains the first identity authentication information provided by the vehicle terminal, and triggers the first type of service to obtain the first vehicle data when it is determined that there is information matching the first identity authentication information in the registration information stored in the electronic device;

[0058] The second authentication module is used to verify the second signature data provided by the vehicle manufacturer platform based on the second public key, and to trigger the second type of service to obtain the second vehicle data when the verification is successful; the second public key is provided by the vehicle manufacturer platform, and the second signature data is obtained by the vehicle manufacturer platform signing the target data according to the second private key corresponding to the second public key; or, it obtains the second identity authentication information provided by the vehicle manufacturer platform, and triggers the second type of service to obtain the second vehicle data when it is determined that there is information matching the second identity authentication information in the registration information stored in the electronic device.

[0059] Optionally, the management device further includes:

[0060] The sending module is configured to respond to a communication mode change request for an in-vehicle terminal by sending target communication mode information to the vehicle manufacturer platform that sent the communication mode change request, so that the vehicle manufacturer platform changes the communication mode of the in-vehicle terminal to the target communication mode; the first vehicle data comes from the in-vehicle terminal whose communication mode is the target communication mode.

[0061] Optionally, the first type of service uses the MQTT protocol or the MQTT-S protocol to communicate and obtain the first vehicle data;

[0062] The second type of service is a cloud forwarding service, which uses a TCP long connection to obtain the second vehicle data;

[0063] The vehicle data acquisition party includes at least one of the following: battery swapping APP big data platform, battery swapping operation platform, and local government cloud platform.

[0064] A vehicle data management device, the management device comprising:

[0065] The acquisition module is used to acquire the first vehicle data from the vehicle terminal and process the first vehicle data according to a preset rule to obtain the second vehicle data.

[0066] The first sending module is used to send the second vehicle data to the server, so that the server can obtain the second vehicle data through a second type of service, extract target vehicle data from the second vehicle data, and send the target vehicle data to the vehicle data requester platform.

[0067] Optionally, the preset rule includes retaining at least one of the following parameters in the first vehicle data: vehicle battery temperature, vehicle battery charge, vehicle battery status, vehicle location information, and vehicle mileage.

[0068] Optionally, the management device further includes:

[0069] The second sending module is used to send a communication mode change request for the vehicle terminal to the server;

[0070] The receiving module is used to receive the target communication mode information fed back by the server in response to the communication mode change request;

[0071] The module is used to change the communication mode of the vehicle terminal to the target communication mode, which enables the vehicle terminal to establish a communication connection with the server.

[0072] A server includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the vehicle data management method described in any of the preceding claims.

[0073] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle data management method described in any of the preceding claims.

[0074] The positive and progressive effects of this invention are as follows: This invention combines two types of services from the in-vehicle terminal and the vehicle manufacturer's platform, realizes compatible management of the first vehicle data from the in-vehicle terminal and the second vehicle data from the vehicle manufacturer's platform, and provides the target vehicle data to the vehicle data requesting platform.

[0075] In this embodiment of the invention, two communication modes are combined: a first type of service communication mode and a second type of service communication mode. Based on the first type of service communication mode and the second type of service communication mode, the first vehicle data from the vehicle terminal and the second vehicle data from the vehicle manufacturer's platform are managed. This can flexibly meet the requirements of the current new energy vehicle industry for data communication, such as the diversity, balance and uncertainty of vehicle data sources, to achieve effective data management and facilitate data maintenance. Attached Figure Description

[0076] Figure 1a A flowchart illustrating a vehicle data management method provided as an exemplary embodiment of the present invention;

[0077] Figure 1b A flowchart illustrating another vehicle data management method provided as an exemplary embodiment of the present invention;

[0078] Figure 2 A flowchart illustrating another vehicle data management method provided as an exemplary embodiment of the present invention;

[0079] Figure 3a A flowchart illustrating another vehicle data management method provided as an exemplary embodiment of the present invention;

[0080] Figure 3b A schematic diagram of the system architecture used in a vehicle data management method provided as an exemplary embodiment of the present invention;

[0081] Figure 4 A schematic diagram of a vehicle data management device provided as an exemplary embodiment of the present invention;

[0082] Figure 5 A schematic diagram of a module for another vehicle data management device provided in an exemplary embodiment of the present invention;

[0083] Figure 6 This is a schematic diagram of a server module provided for an exemplary embodiment of the present invention. Detailed Implementation

[0084] The present invention will be further illustrated by way of embodiments below, but the present invention is not limited to the scope of the embodiments described herein.

[0085] This invention provides a method for managing vehicle data. The method runs on a server of a data manager. The server is deployed with a first type of service and a second type of service. The first type of service is defined as being able to acquire and process first vehicle data from an in-vehicle terminal, and the second type of service is defined as being able to acquire and process second vehicle data from a vehicle manufacturer's platform.

[0086] The number of Type I services deployed on the server can be one or more, and this embodiment of the invention does not impose a particular limitation on this. When multiple Type I services are deployed on the server, the multiple Type I services can simultaneously acquire the first vehicle data provided by multiple vehicle terminals to improve the efficiency of data acquisition.

[0087] The number of second-type services deployed on the server can be one or more, and this embodiment of the invention does not impose a particular limitation on this. When multiple second-type services are deployed on the server, the multiple second-type services can simultaneously acquire second vehicle data provided by multiple vehicle manufacturer platforms, or the multiple second-type services can simultaneously acquire a large amount of second vehicle data provided by a single vehicle manufacturer platform, thereby improving the efficiency of data acquisition.

[0088] The first and second types of services can adopt a distributed microservice architecture design, where the communication modes of the first and second types of services are each formed into separate point services, and then the point services are deployed in a cluster.

[0089] The aforementioned server can be a physical server or a virtual server, and can be a single server or a server cluster. This embodiment of the invention does not impose any particular limitation on this.

[0090] Figure 1a A flowchart of a vehicle data management method provided as an exemplary embodiment of the present invention is shown. This management method is applied to a server and includes the following steps:

[0091] Step 101: Obtain first vehicle data through the first type of service. The first vehicle data comes from the vehicle terminal.

[0092] The first vehicle data may include, but is not limited to: vehicle license plate information, vehicle identification number (VIN), user identity information of the vehicle, vehicle battery temperature, vehicle battery charge, vehicle battery status, vehicle location information, and vehicle mileage.

[0093] In one embodiment, the first type of service obtains the first vehicle data by communicating using the MQTT protocol or the MQTT-S protocol, or it may obtain the first vehicle data by using one or more other communication protocols in combination.

[0094] In one embodiment, before obtaining the first vehicle data through the first type of service, the permissions of the vehicle terminal providing the first vehicle data are authenticated. Specifically, the first signature data provided by the vehicle terminal is verified based on the first public key. If the verification is successful, it indicates that the vehicle terminal has the permission to provide the first vehicle data to the server for management, or that the server is authorized by the vehicle terminal to manage the first vehicle data of the vehicle terminal, and the server triggers the first type of service to obtain the first vehicle data. If the verification fails, it indicates that the vehicle terminal does not have the permission to provide the first vehicle data to the server for management, or that the server is not authorized by the vehicle terminal to manage the first vehicle data of the vehicle terminal, and the server does not obtain the first vehicle data of the vehicle terminal.

[0095] In this embodiment, the first public key is provided by the vehicle-mounted terminal, and the first signature data is obtained by the vehicle-mounted terminal signing the target data using the first private key corresponding to the first public key. The target data can be selected according to the actual situation and may be, but is not limited to, all or part of the data in the first vehicle data. Authentication of the vehicle-mounted terminal's permissions can be implemented through the first type of service or by defining another service; this embodiment of the invention does not impose any particular limitation on this.

[0096] In one embodiment, before obtaining the first vehicle data through the first type of service, the permissions of the vehicle terminal providing the first vehicle data are authenticated. Specifically, the first identity authentication information provided by the vehicle terminal is obtained. This first identity authentication information may include, but is not limited to, the vehicle terminal's account, password, and other information. The server determines whether there is information in the registration information stored therein that matches the first identity authentication information. If there is information in the registration information stored therein that matches the first identity authentication information, it means that the vehicle terminal has the permission to provide the first vehicle data to the server for management, or that the server is authorized by the vehicle terminal to manage the vehicle terminal's first vehicle data. In this case, the server triggers the first type of service to obtain the first vehicle data. If there is no information in the registration information stored therein that matches the first identity authentication information, it means that the vehicle terminal does not have the permission to provide the first vehicle data to the server for management, or that the server is not authorized by the vehicle terminal to manage the vehicle terminal's first vehicle data. In this case, the server does not obtain the vehicle terminal's first vehicle data.

[0097] The registration information stored on the server is generated by the vehicle terminal when registering with the server.

[0098] By authenticating the permissions of the vehicle-mounted terminal, it is possible to prevent the vehicle-mounted terminal from maliciously connecting to the server and consuming server resources.

[0099] In one embodiment, after obtaining the first vehicle data, the data is further processed according to a first preset rule. The first preset rule includes at least one of the following: encryption rule, desensitization rule, masking rule, conversion rule, etc. If the first vehicle data is processed according to the first preset rule, the first vehicle data stored on the server is processed data, thereby preventing the first vehicle data from being eavesdropped on or stolen on the server, thus avoiding data leakage.

[0100] It should be noted that performing any of the above processing on the first vehicle data can process all data in the first vehicle data or process sensitive and private data in the first vehicle data. Encryption rules, desensitization rules, masking rules, and conversion rules can be set according to actual conditions; the specific implementation process can be found in the relevant technical descriptions, which will not be repeated here. Data processing of the first vehicle data according to the first preset rule can be implemented through a first type of service or by defining another service; this embodiment of the invention does not impose any particular limitation on this.

[0101] In one embodiment, after obtaining the first vehicle data, the first vehicle data is stored in the server's storage space. If the first vehicle data comes from different sources, the first vehicle data is stored in different storage spaces, and the data source of the first vehicle data stored in each storage space is the same, so as to achieve data storage isolation and prevent data chaos.

[0102] For example, the first vehicle data of vehicle terminal A is stored in storage space a1, the first vehicle data of vehicle terminal B is stored in storage space b1, and the first vehicle data of vehicle terminal C is stored in storage space c1. If the data volume of vehicle terminal D is very large, and the capacity of one storage space is insufficient to store the first vehicle data of vehicle terminal D, then the first vehicle data of vehicle terminal D is stored in storage spaces d1 and e1.

[0103] Understandably, if the server processes the data of the first vehicle according to the first preset rule, the processed data of the first vehicle will be stored in the storage space.

[0104] The aforementioned data sources include one or more of the following: service sources, in-vehicle terminal sources, and vehicle manufacturer platform sources. The storage of the first vehicle data can be achieved through a first type of service, or by defining another service; this embodiment of the invention does not impose any particular limitation on this.

[0105] Step 102: Obtain the second vehicle data through the second type of service. The second vehicle data comes from the vehicle manufacturer's platform, and the second vehicle data on the vehicle manufacturer's platform is provided by the vehicle terminal.

[0106] In one embodiment, the second type of service is a cloud forwarding service that obtains second vehicle data using a TCP long connection. Alternatively, one or more other communication protocols can be combined to obtain the second vehicle data.

[0107] In one embodiment, before obtaining the second vehicle data through the second type of service, the permissions of the vehicle manufacturer platform providing the second vehicle data are authenticated. Specifically, the second signature data provided by the vehicle manufacturer platform is verified based on the second public key. If the verification is successful, it indicates that the vehicle manufacturer platform has the permission to provide the second vehicle data to the server for management, or that the server is authorized by the vehicle manufacturer platform to manage the second vehicle data of the vehicle manufacturer platform. In this case, the server triggers the second type of service to obtain the second vehicle data. If the verification fails, it indicates that the vehicle manufacturer platform does not have the permission to provide the second vehicle data to the server for management, or that the server is not authorized by the vehicle manufacturer platform to manage the second vehicle data of the vehicle manufacturer platform. In this case, the server does not obtain the second vehicle data of the vehicle manufacturer platform.

[0108] In this embodiment, the second public key is provided by the vehicle manufacturer platform, and the second signature data is obtained by the vehicle manufacturer platform signing the target data using the second private key corresponding to the second public key. The target data can be selected according to actual circumstances and may include, but is not limited to, all or part of the second vehicle data, license plate information of vehicles belonging to the vehicle manufacturer platform, vehicle identification number (VIN), or a combination of at least two of the above types of data. Authentication of the vehicle manufacturer platform's permissions can be implemented through the second type of service or by defining another service; this embodiment of the invention does not impose any particular limitations on this.

[0109] In one embodiment, before obtaining the second vehicle data through the second type of service, the permissions of the vehicle manufacturer platform providing the second vehicle data are authenticated. Specifically, the second identity authentication information provided by the vehicle manufacturer platform is obtained. This second identity authentication information may include, but is not limited to, the vehicle manufacturer platform's account and password. The server determines whether there is information in the registration information stored on the server that matches the second identity authentication information. If there is information in the registration information stored on the server that matches the second identity authentication information, it means that the vehicle manufacturer platform has the permission to provide the second vehicle data to the server for management, or the server is authorized by the vehicle manufacturer platform to manage the second vehicle data of the vehicle manufacturer platform. In this case, the server triggers the second type of service to obtain the second vehicle data. If there is no information in the registration information stored on the server that matches the second identity authentication information, it means that the vehicle manufacturer platform does not have the permission to provide the second vehicle data to the server for management, or the server is not authorized by the vehicle manufacturer platform to manage the second vehicle data of the vehicle manufacturer platform. In this case, the server does not obtain the second vehicle data of the vehicle manufacturer platform.

[0110] The registration information stored on the server is generated by the vehicle manufacturer's platform when registering on the server.

[0111] By authenticating the permissions of the vehicle manufacturer's platform, it is possible to prevent the vehicle manufacturer's platform from maliciously connecting to the server and consuming server resources.

[0112] In one embodiment, after obtaining the second vehicle data, the second vehicle data is further processed according to a second preset rule. The second preset rule includes at least one of the following rules: encryption rule, desensitization rule, masking rule, and conversion rule. If the first vehicle data is processed according to the first preset rule, the first vehicle data stored on the server is processed data, thereby preventing the first vehicle data from being eavesdropped on or stolen on the server, thus avoiding data leakage.

[0113] It should be noted that performing any of the above-mentioned processing on the second vehicle data can process all data in the second vehicle data or process sensitive and private data in the second vehicle data. Encryption rules, desensitization rules, masking rules, and conversion rules can be set according to actual conditions; the specific implementation process can be found in the relevant technical descriptions, which will not be repeated here. Data processing of the second vehicle data according to the second preset rules can be implemented through a second type of service or by defining another service; this embodiment of the invention does not impose any particular limitation on this.

[0114] In one embodiment, after obtaining the second vehicle data, the second vehicle data is stored in the server's storage space. If the second vehicle data comes from different sources, the second vehicle data is stored in different storage spaces, and the data source of the second vehicle data stored in each storage space is the same, so as to achieve physical data isolation and prevent data chaos.

[0115] For example, the second vehicle data of vehicle manufacturer platform A is stored in storage space a2, the second vehicle data of vehicle manufacturer platform B is stored in storage space b2, and the second vehicle data of vehicle manufacturer platform C is stored in storage space c2. If the data volume of vehicle manufacturer platform D is very large, and the capacity of one storage space is insufficient to store the second vehicle data of vehicle manufacturer platform D, then the second vehicle data of vehicle manufacturer platform D is stored in storage spaces d2 and e2.

[0116] Understandably, if the server processes the second vehicle data according to the second preset rule, the processed second vehicle data will be stored in the storage space.

[0117] The aforementioned data sources include one or more of the following: service sources, in-vehicle terminal sources, and vehicle manufacturer platform sources. Storage of the second vehicle data can be achieved through a second type of service or by defining another service; this embodiment of the invention does not impose any particular limitation on this.

[0118] In one embodiment, if the second vehicle data provided by the vehicle manufacturer's platform is data processed by at least one of the following methods: encryption, desensitization, masking, conversion, etc., on the first vehicle data provided by the vehicle terminal, the second type of service can directly store the second vehicle data after obtaining it, without needing to process the second vehicle data according to the second preset rule.

[0119] The execution order of the steps for obtaining the first vehicle data and the steps for obtaining the second vehicle data is not limited; both steps are executed before the target data is extracted. Except... Figure 1aIn addition to the step of obtaining the first vehicle data being executed first and then the step of obtaining the second vehicle data being executed, the steps of obtaining the first vehicle data and obtaining the second vehicle data can be executed in parallel, or the step of obtaining the second vehicle data can be executed first and then the step of obtaining the first vehicle data can be executed.

[0120] In one embodiment, the execution order of the steps to obtain the first vehicle data and the second vehicle data is determined by considering the server's resource usage and the priority of the vehicle data. In scenarios where both the first and second vehicle data need to be obtained, if the server has relatively few occupied resources, a large amount of remaining resources, and can simultaneously satisfy the needs of both the first and second types of services to obtain vehicle data, see [reference needed]. Figure 1b The steps for obtaining the first vehicle data and the steps for obtaining the second vehicle data are executed in parallel. If the remaining resources of the server can only satisfy the data acquisition for one type of service, then the order in which the steps for obtaining the first vehicle data or the steps for obtaining the second vehicle data are executed is determined based on data priority. The data priority can be set according to the actual situation, for example, based on the order in which data acquisition requests are received; or, by identifying the priority of vehicle data.

[0121] Step 103: Extract the target vehicle data from the first vehicle data and / or the second vehicle data, and send the target vehicle data to the vehicle data requester platform.

[0122] The vehicle data demand-side platforms include at least one of the following: battery swapping APP big data platforms, battery swapping operation platforms, and local government cloud platforms. The extraction and transmission of target vehicle data can be implemented by defining a service, such as defining a data forwarding service to achieve the extraction and transmission of target vehicle data.

[0123] The server extracts the target vehicle data according to the needs of each vehicle data requesting platform and sends it to each vehicle data requesting platform.

[0124] In one embodiment, the extraction and transmission of target vehicle data are performed upon request. That is, upon receiving a data retrieval request from the vehicle data requesting platform, the server extracts the target vehicle data from the first vehicle data and / or the second vehicle data, and then sends the target vehicle data to the vehicle data requesting platform. The data retrieval request sent by the vehicle data requesting platform may carry keywords, and the extracted target vehicle data is the data matching the keywords.

[0125] In one embodiment, the vehicle data acquisition request may also carry data source information and data type information, with the target vehicle data being data that matches the data source information and data type information.

[0126] In a scenario where the first vehicle data and the second vehicle data are stored in different storage spaces according to their data sources, when retrieving target data, the corresponding target storage space is determined based on the data source information carried in the vehicle data retrieval request, and data that matches the data type information carried in the vehicle data retrieval request is extracted from the target storage space as the target vehicle data.

[0127] In one embodiment, the extraction and transmission of target vehicle data are performed according to pre-defined extraction and transmission rules. This can be done periodically or at regular intervals. The extraction and transmission rules may also define at least one data parameter from keywords, data source information, and data type information. The target vehicle data is the data that matches the data parameters defined in the extraction and transmission rules. The extraction and transmission rules can be set according to actual needs, and this application does not impose any particular limitations on them.

[0128] In this embodiment of the invention, two communication modes are combined: a first type of service communication mode and a second type of service communication mode. Based on the first type of service communication mode and the second type of service communication mode, the first vehicle data from the vehicle terminal and the second vehicle data from the vehicle manufacturer's platform are managed. This can flexibly meet the various requirements of the current new energy vehicle industry for data communication and achieve effective data management.

[0129] In one embodiment, the server can modify the communication module of the in-vehicle terminal according to a request from the vehicle manufacturer's platform. Specifically, based on the communication mode change request for the in-vehicle terminal, the server sends target communication mode information back to the vehicle manufacturer's platform that sent the communication mode change request, so that the vehicle manufacturer's platform can change the communication mode of the in-vehicle terminal to the target communication mode according to the target communication mode information. The target communication mode is either the communication mode of a first type of service or the communication mode of a second type of service. The target communication mode information includes at least one of the following parameters: communication mode address, communication protocol, data field format, etc.

[0130] If a vehicle-mounted terminal is currently using the first type of service communication mode, it directly establishes a communication connection with the server, and the server obtains the first vehicle data from the terminal through the first type of service. The vehicle manufacturer's platform can change the communication mode of the vehicle-mounted terminal to the second type of service communication mode. After the communication mode change, the vehicle-mounted terminal establishes a communication connection with the vehicle manufacturer's platform and provides the first vehicle data to the platform.

[0131] If a vehicle-mounted terminal is currently using the second type of service communication mode, it establishes a communication connection with the vehicle manufacturer's platform. The terminal sends first vehicle data to the platform, which processes it according to preset rules to obtain second vehicle data, which is then sent to the server. The vehicle manufacturer's platform can change the terminal's communication mode to the first type of service communication mode. After the mode change, the terminal directly establishes a communication connection with the server and provides the first vehicle data to the server.

[0132] Figure 2 A flowchart illustrating another vehicle data management method provided as an exemplary embodiment of the present invention, the method being applied to a vehicle manufacturer's platform, the method comprising the following steps:

[0133] Step 201: Obtain the first vehicle data from the vehicle terminal and process the first vehicle data according to preset rules to obtain the second vehicle data.

[0134] In one embodiment, the preset rule includes retaining at least one of the following parameters from the first vehicle data: vehicle battery temperature, vehicle battery charge, vehicle battery status, vehicle location information, and vehicle mileage.

[0135] In one embodiment, the preset rules include at least one of the following rules: encryption rules, desensitization rules, masking rules, conversion rules, etc.

[0136] The above preset rules can be set according to the actual situation.

[0137] Step 202: Send the data of the second vehicle to the server.

[0138] The server obtains second vehicle data through a second type of service, extracts target vehicle data from the second vehicle data, and sends the target vehicle data to the vehicle data requester platform.

[0139] In one embodiment, the vehicle manufacturer platform can request the server to change the communication mode of the vehicle terminal. Specifically, the vehicle manufacturer platform sends a communication mode change request for the vehicle terminal to the server, receives the target communication mode information from the server in response to the communication mode change request, and then changes the communication mode of the vehicle terminal to the target communication mode according to the target communication mode information. The target communication mode is either the communication mode of the first type of service or the communication mode of the second type of service.

[0140] Figure 3a A flowchart illustrating another vehicle data management method provided in an exemplary embodiment of the present invention. Figure 3bThis is a schematic diagram of a system architecture for a vehicle data management method provided as an exemplary embodiment of the present invention. The diagram further illustrates the vehicle data management process through the interaction of an in-vehicle terminal, a vehicle manufacturer's platform, a server, and a vehicle data requester's platform. The management method includes the following steps:

[0141] Step 301: Vehicle terminal a sends the first vehicle data to the server.

[0142] Step 302: The server obtains the first vehicle data of the vehicle terminal a through the first type of service.

[0143] It should be noted that the diagram only uses vehicle terminal a as an example. In actual application, the server can connect to multiple vehicle terminals, that is, the server obtains the first vehicle data of multiple vehicle terminals through the first type of service.

[0144] Before the server obtains the first vehicle data, it can authenticate the permissions of the vehicle terminal a. For the specific authentication method, please refer to the explanation of step 101, which will not be repeated here.

[0145] After the server obtains the data of the first vehicle, it can process the data of the first vehicle according to the first preset rule. For the specific data processing method, please refer to the explanation of step 101, which will not be repeated here.

[0146] After the server obtains the data of the first vehicle, it stores the data of the first vehicle in the storage space. For the specific data storage method, please refer to the explanation of step 101, which will not be repeated here.

[0147] Step 303: Vehicle terminal b sends the first vehicle data to the vehicle manufacturer's platform.

[0148] It should be noted that the diagram only uses vehicle terminal b as an example for illustration. In actual application, the vehicle manufacturer's platform can connect to multiple vehicle terminals.

[0149] Step 304: The vehicle manufacturer's platform generates the second vehicle data based on the first vehicle data.

[0150] The specific implementation process of the vehicle manufacturer's platform generating second vehicle data based on the first vehicle data is explained in the section on step 201, and will not be repeated here.

[0151] Step 305: The vehicle manufacturer's platform sends the second vehicle data to the server.

[0152] It should be noted that the diagram only uses one vehicle manufacturer platform as an example. In actual applications, the server can connect to multiple vehicle manufacturer platforms.

[0153] Step 306: The server obtains the second vehicle data through the second type of service.

[0154] Before the server obtains the data of the second vehicle, it can authenticate the permissions of the vehicle manufacturer's platform. For details on the authentication method, please refer to the explanation of step 102, which will not be repeated here.

[0155] After the server obtains the second vehicle data, it can process the second vehicle data according to the second preset rules. For the specific data processing method, please refer to the explanation of step 102, which will not be repeated here.

[0156] After the server obtains the data of the second vehicle, it stores the data of the second vehicle in the storage space. For the specific data storage method, please refer to the explanation of step 102, which will not be repeated here.

[0157] Step 307: The server extracts the target vehicle data from the first vehicle data and / or the second vehicle data.

[0158] Step 308: Send the target vehicle data to the vehicle data requester platform.

[0159] For details on how the server extracts target vehicle data and sends target vehicle CNC data, please refer to the explanation of step 103; it will not be repeated here.

[0160] It should be noted that the diagram only uses one vehicle data demand-side platform as an example. In actual applications, the server can connect to multiple vehicle data demand-side platforms.

[0161] In one embodiment, the vehicle manufacturer's platform can change the communication mode between vehicle terminal a and vehicle terminal b. The specific implementation process is described in the above embodiments and will not be repeated here.

[0162] It should be noted that steps 301 to 302 are steps to obtain the first vehicle data, and steps 303 to 306 are steps to obtain the second vehicle data. The steps to obtain the first vehicle data and the steps to obtain the second vehicle data are independent of each other, and there is no limitation on the execution order, let alone the execution order shown in the figure. Steps 301 to 302 and steps 303 to 306 can be executed synchronously.

[0163] Corresponding to the aforementioned vehicle data management method embodiments, the present invention also provides embodiments of vehicle data management devices.

[0164] Figure 4 A schematic diagram of a vehicle data management device provided as an exemplary embodiment of the present invention, the management device comprising:

[0165] The first acquisition module 41 is used to acquire first vehicle data through a first type of service, wherein the first vehicle data comes from the vehicle terminal.

[0166] The second acquisition module 42 is used to acquire second vehicle data through a second type of service. The second vehicle data comes from the vehicle manufacturer's platform, and the second vehicle data of the vehicle manufacturer's platform is provided by the vehicle terminal.

[0167] Extraction module 43 is used to extract target vehicle data from the first vehicle data and / or the second vehicle data, and send the target vehicle data to the vehicle data requester platform.

[0168] Optionally, the management device further includes a first data processing module and / or a second data processing module:

[0169] The first data processing module is used to process the first vehicle data according to a first preset rule; the first preset rule includes encryption rules and / or de-identification rules.

[0170] The second data processing module is used to process the second vehicle data according to a second preset rule; the second preset rule includes encryption rules and / or desensitization rules.

[0171] Optionally, the management device further includes a storage module;

[0172] The storage module is used to store the first vehicle data and the second vehicle data in different storage spaces, and the data source of the first vehicle data or the second vehicle data stored in each storage space is the same; the data source includes at least one of the following: service source, vehicle terminal source, and vehicle manufacturer platform source.

[0173] Optionally, the extraction module includes:

[0174] The determining unit is used to determine the corresponding target storage space in response to a vehicle data acquisition request, based on the data source information carried in the vehicle data acquisition request.

[0175] The extraction unit is used to extract data from the target storage space that matches the data type information carried in the vehicle data acquisition request as target vehicle data.

[0176] Optionally, the extraction module is specifically used for:

[0177] Initial data corresponding to a preset field is extracted from the first vehicle data and / or the second vehicle data, and the preset field matches the permissions of the vehicle data requesting platform;

[0178] Target vehicle data is extracted from the initial data, and the target vehicle data is data that matches the search keywords provided by the vehicle data requesting platform.

[0179] Optionally, the management device further includes:

[0180] The first authentication module is used to verify the first signature data provided by the vehicle terminal based on the first public key, and trigger the first type of service to obtain the first vehicle data when the verification is successful; the first public key is provided by the vehicle terminal, and the first signature data is obtained by the vehicle terminal signing the target data according to the first private key corresponding to the first public key; or, it obtains the first identity authentication information provided by the vehicle terminal, and triggers the first type of service to obtain the first vehicle data when it is determined that there is information matching the first identity authentication information in the registration information stored in the electronic device;

[0181] The second authentication module is used to verify the second signature data provided by the vehicle manufacturer platform based on the second public key, and to trigger the second type of service to obtain the second vehicle data when the verification is successful; the second public key is provided by the vehicle manufacturer platform, and the second signature data is obtained by the vehicle manufacturer platform signing the target data according to the second private key corresponding to the second public key; or, it obtains the second identity authentication information provided by the vehicle manufacturer platform, and triggers the second type of service to obtain the second vehicle data when it is determined that there is information matching the second identity authentication information in the registration information stored in the electronic device.

[0182] Optionally, the management device further includes:

[0183] The sending module is configured to respond to a communication mode change request for an in-vehicle terminal by sending target communication mode information to the vehicle manufacturer platform that sent the communication mode change request, so that the vehicle manufacturer platform changes the communication mode of the in-vehicle terminal to the target communication mode; the first vehicle data comes from the in-vehicle terminal whose communication mode is the target communication mode.

[0184] Optionally, the first type of service uses the MQTT protocol or the MQTT-S protocol to communicate and obtain the first vehicle data;

[0185] The second type of service is a cloud forwarding service, which uses a TCP long connection to obtain the second vehicle data;

[0186] The vehicle data acquisition party includes at least one of the following: battery swapping APP big data platform, battery swapping operation platform, and local government cloud platform.

[0187] Figure 5A schematic diagram of another vehicle data management device provided as an exemplary embodiment of the present invention, the management device comprising:

[0188] The acquisition module 51 is used to acquire the first vehicle data of the vehicle terminal and process the first vehicle data according to a preset rule to obtain the second vehicle data.

[0189] The first sending module 52 is used to send the second vehicle data to the server, so that the server can obtain the second vehicle data through a second type of service, extract target vehicle data from the second vehicle data, and send the target vehicle data to the vehicle data requester platform.

[0190] Optionally, the preset rule includes retaining at least one of the following parameters in the first vehicle data: vehicle battery temperature, vehicle battery charge, vehicle battery status, vehicle location information, and vehicle mileage.

[0191] Optionally, the management device further includes:

[0192] The second sending module is used to send a communication mode change request for the vehicle terminal to the server;

[0193] The receiving module is used to receive the target communication mode information fed back by the server in response to the communication mode change request;

[0194] The module is used to change the communication mode of the vehicle terminal to the target communication mode, which enables the vehicle terminal to establish a communication connection with the server.

[0195] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The above embodiments of a vehicle data management device can also achieve the corresponding technical effects of the embodiments of a vehicle data management method, which have been described in detail above and will not be repeated here. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the present invention according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0196] Figure 6 This is a schematic diagram of the structure of a server shown in an example embodiment of the present invention, illustrating a block diagram of an exemplary server 60 suitable for implementing embodiments of the present invention. Figure 6The server 60 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0197] like Figure 6 As shown, server 60 can be represented as a general-purpose computing device. Components of server 60 may include, but are not limited to: at least one processor 61, at least one memory 62, and a bus 63 connecting different system components (including memory 62 and processor 61).

[0198] Bus 63 includes a data bus, an address bus, and a control bus.

[0199] The memory 62 may include volatile memory, such as random access memory (RAM) 621 and / or cache memory 622, and may further include read-only memory (ROM) 623.

[0200] The memory 62 may also include a program tool 625 (or utility) having a set (at least one) program module 624, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0201] The processor 61 performs various functional applications and data processing, such as the methods provided in any of the above embodiments, by running computer programs stored in the memory 62.

[0202] Server 60 can also communicate with one or more external devices 64 (e.g., keyboard, pointing device, etc.). This communication can be performed via input / output (I / O) interface 65. Furthermore, the model-generating server 60 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 66. As shown, network adapter 66 communicates with other modules of the model-generating server 60 via bus 63. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the model-generating server 60, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems.

[0203] It should be noted that although several units / modules or sub-units / modules of the server are mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of the present invention, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0204] The above-described embodiment of a server 60, through the processor 61 running a computer program stored in the memory 62, performs various functional applications and data processing, and can also achieve the corresponding technical effects of an embodiment of a vehicle data management method, as described in detail above, and will not be repeated here.

[0205] This embodiment provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method provided in any of the above embodiments.

[0206] The readable storage medium may be more specifically adopted, including but not limited to: portable disk, hard disk, random access memory, read-only memory, erasable programmable read-only memory, optical storage device, magnetic storage device, or any suitable combination thereof.

[0207] In a possible implementation, the present invention can also be implemented as a program product comprising program code, which, when the program product is run on a terminal device, causes the terminal device to perform steps implementing the method provided in any of the above embodiments.

[0208] The program code for executing the present invention can be written in any combination of one or more programming languages. The program code can be executed entirely on the user device, partially on the user device, as a standalone software package, partially on the user device and partially on a remote device, or entirely on a remote device.

[0209] By implementing the above embodiments using a computer-readable storage medium, the corresponding technical effects of the embodiments of a vehicle data management method can also be achieved, as has been described in detail above and will not be repeated here.

[0210] While specific embodiments of the present invention have been described above, those skilled in the art should understand that these are merely illustrative examples, and the scope of protection of the present invention is defined by the appended claims. Those skilled in the art can make various changes or modifications to these embodiments without departing from the principles and essence of the present invention, but all such changes and modifications fall within the scope of protection of the present invention.

Claims

1. A method for managing vehicle data, characterized in that, The management method includes: The first vehicle data is obtained through the first type of service, and the first vehicle data comes from the vehicle terminal. Second vehicle data is obtained through a second type of service. The second vehicle data comes from the vehicle manufacturer's platform, and the second vehicle data on the vehicle manufacturer's platform is provided by the vehicle terminal. Extract target vehicle data from the first vehicle data and / or the second vehicle data, and send the target vehicle data to the vehicle data requester platform; Extracting target vehicle data from the first vehicle data and / or the second vehicle data includes: In response to a vehicle data acquisition request, the corresponding target storage space is determined based on the data source information carried in the vehicle data acquisition request; When the first vehicle data and the second vehicle data are stored in different storage spaces according to their data sources, data that matches the data type information carried in the vehicle data acquisition request is extracted from the target storage space as the target vehicle data.

2. The vehicle data management method according to claim 1, characterized in that, After obtaining the first vehicle data through the first type of service, it also includes: The first vehicle data is processed according to a first preset rule; the first preset rule includes encryption rules and / or desensitization rules. After obtaining the second vehicle data through the second type of service, it also includes: The second vehicle data is processed according to the second preset rule; the second preset rule includes encryption rules and / or desensitization rules.

3. The vehicle data management method according to claim 1, characterized in that, Also includes: The first vehicle data and the second vehicle data are stored in different storage spaces, and the data source of the first vehicle data or the second vehicle data stored in each storage space is the same; the data source includes at least one of the following: service source, vehicle terminal source, and vehicle manufacturer platform source.

4. The vehicle data management method according to claim 1, characterized in that, Extracting target vehicle data from the first vehicle data and / or the second vehicle data includes: Initial data corresponding to a preset field is extracted from the first vehicle data and / or the second vehicle data, and the preset field matches the permissions of the vehicle data requesting platform; Target vehicle data is extracted from the initial data, and the target vehicle data is data that matches the search keywords provided by the vehicle data requesting platform.

5. The vehicle data management method according to claim 1, characterized in that, Before obtaining the first vehicle data through the first type of service, the following is also included: The system verifies the first signature data provided by the vehicle terminal based on the first public key, and triggers the first type of service to obtain the first vehicle data when the verification is successful; the first public key is provided by the vehicle terminal, and the first signature data is obtained by the vehicle terminal signing the target data according to the first private key corresponding to the first public key; Alternatively, the system may obtain the first identity authentication information provided by the vehicle terminal, and trigger the first type of service to obtain the first vehicle data when it is determined that there is information in the stored registration information that matches the first identity authentication information. or Before obtaining the second vehicle data through the second type of service, the following is also included: The second public key is used to verify the second signature data provided by the vehicle manufacturer platform, and the second type of service is triggered to obtain the second vehicle data when the verification is successful; the second public key is provided by the vehicle manufacturer platform, and the second signature data is obtained by the vehicle manufacturer platform signing the target data according to the second private key corresponding to the second public key; Alternatively, the system may obtain the second identity authentication information provided by the vehicle manufacturer's platform, and trigger the second type of service to obtain the second vehicle data when it is determined that there is information in the stored registration information that matches the second identity authentication information.

6. The vehicle data management method according to claim 1, characterized in that, Also includes: In response to a communication mode change request for an in-vehicle terminal, the system feeds back target communication mode information to the vehicle manufacturer platform that sent the communication mode change request, so that the vehicle manufacturer platform changes the communication mode of the in-vehicle terminal to the target communication mode; the target communication mode is either the communication mode of a first type of service or the communication mode of a second type of service.

7. The vehicle data management method according to claim 1, characterized in that, The first type of service obtains the first vehicle data by communicating using the MQTT protocol or the MQTT-S protocol; The second type of service is a cloud forwarding service, which uses a TCP long connection to obtain the second vehicle data; The vehicle data demand-side platform includes at least one of the following: a battery swapping APP big data platform, a battery swapping operation platform, and local government cloud platforms.

8. A method for managing vehicle data, characterized in that, The management method includes: Acquire the first vehicle data from the vehicle terminal, and process the first vehicle data according to a preset rule to obtain the second vehicle data; The second vehicle data is sent to the server, so that the server can obtain the second vehicle data through the second type of service, extract the target vehicle data from the second vehicle data, and send the target vehicle data to the vehicle data demander platform. The server is used to perform: In response to a vehicle data acquisition request, the corresponding target storage space is determined based on the data source information carried in the vehicle data acquisition request; When the first vehicle data and the second vehicle data are stored in different storage spaces according to their data sources, data that matches the data type information carried in the vehicle data acquisition request is extracted from the target storage space as the target vehicle data.

9. The vehicle data management method according to claim 8, characterized in that, The preset rules include retaining at least one of the following parameters from the first vehicle data: vehicle battery temperature, vehicle battery charge, vehicle battery status, vehicle location information, and vehicle mileage.

10. The vehicle data management method according to claim 8, characterized in that, Also includes: Send a communication mode change request for the vehicle terminal to the server; Receive the target communication mode information from the server in response to the communication mode change request; The communication mode of the vehicle terminal is changed to the target communication mode according to the target communication mode information. The target communication mode is either the communication mode of the first type of service or the communication mode of the second type of service. The first type of service is used to obtain the first vehicle data provided by the vehicle terminal.

11. A vehicle data management device, characterized in that, The management device includes: The first acquisition module is used to acquire first vehicle data through a first type of service, wherein the first vehicle data comes from the vehicle terminal. The second acquisition module is used to acquire second vehicle data through a second type of service. The second vehicle data comes from the vehicle manufacturer's platform, and the second vehicle data of the vehicle manufacturer's platform is provided by the vehicle terminal. The extraction module is used to extract target vehicle data from the first vehicle data and / or the second vehicle data, and send the target vehicle data to the vehicle data demander platform; The extraction module includes: The determining unit is used to determine the corresponding target storage space in response to a vehicle data acquisition request, based on the data source information carried in the vehicle data acquisition request. The extraction unit is used to extract data from the target storage space that matches the data type information carried in the vehicle data acquisition request as target vehicle data, when the first vehicle data and the second vehicle data are stored in different storage spaces according to the data source.

12. The vehicle data management device according to claim 11, characterized in that, The management device further includes a first data processing module and / or a second data processing module: The first data processing module is used to process the first vehicle data according to a first preset rule; the first preset rule includes encryption rules and / or de-identification rules. The second data processing module is used to process the second vehicle data according to the second preset rules; The second preset rule includes encryption rules and / or desensitization rules.

13. The vehicle data management device according to claim 11, characterized in that, The management device also includes a storage module; The storage module is used to store the first vehicle data and the second vehicle data in different storage spaces, and the data source of the first vehicle data or the second vehicle data stored in each storage space is the same; the data source includes at least one of the following: service source, vehicle terminal source, and vehicle manufacturer platform source.

14. The vehicle data management device according to claim 11, characterized in that, The extraction module is specifically used for: Initial data corresponding to a preset field is extracted from the first vehicle data and / or the second vehicle data, and the preset field matches the permissions of the vehicle data requesting platform; Target vehicle data is extracted from the initial data, and the target vehicle data is data that matches the search keywords provided by the vehicle data requesting platform.

15. The vehicle data management device according to claim 11, characterized in that, The management device further includes: The first authentication module is used to verify the first signature data provided by the vehicle terminal based on the first public key, and trigger the first type of service to obtain the first vehicle data when the verification is successful; the first public key is provided by the vehicle terminal, and the first signature data is obtained by the vehicle terminal signing the target data according to the first private key corresponding to the first public key; or, it obtains the first identity authentication information provided by the vehicle terminal, and triggers the first type of service to obtain the first vehicle data when it is determined that there is information matching the first identity authentication information in the pre-stored registration information; The second authentication module is used to verify the second signature data provided by the vehicle manufacturer platform based on the second public key, and to trigger the second type of service to obtain the second vehicle data when the verification is successful; the second public key is provided by the vehicle manufacturer platform, and the second signature data is obtained by the vehicle manufacturer platform signing the target data according to the second private key corresponding to the second public key; or, it obtains the second identity authentication information provided by the vehicle manufacturer platform, and triggers the second type of service to obtain the second vehicle data when it is determined that there is information matching the second identity authentication information in the pre-stored registration information.

16. The vehicle data management device according to claim 11, characterized in that, The management device further includes: The sending module is configured to respond to a communication mode change request for an in-vehicle terminal by sending target communication mode information to the vehicle manufacturer platform that sent the communication mode change request, so that the vehicle manufacturer platform changes the communication mode of the in-vehicle terminal to the target communication mode; the first vehicle data comes from the in-vehicle terminal whose communication mode is the target communication mode.

17. The vehicle data management device according to claim 11, characterized in that, The first type of service uses the MQTT protocol or the MQTT-S protocol to communicate and obtain the first vehicle data; The second type of service is a cloud forwarding service, which uses a TCP long connection to obtain the second vehicle data; The vehicle data demand-side platform includes at least one of the following: battery swapping APP big data platform, battery swapping operation platform, and local government cloud platform.

18. A vehicle data management device, characterized in that, The management device includes: The acquisition module is used to acquire the first vehicle data from the vehicle terminal and process the first vehicle data according to a preset rule to obtain the second vehicle data. The first sending module is used to send the second vehicle data to the server, so that the server can obtain the second vehicle data through the second type of service, extract target vehicle data from the second vehicle data, and send the target vehicle data to the vehicle data demander platform. The server is used to perform: In response to a vehicle data acquisition request, the corresponding target storage space is determined based on the data source information carried in the vehicle data acquisition request; When the first vehicle data and the second vehicle data are stored in different storage spaces according to their data sources, data that matches the data type information carried in the vehicle data acquisition request is extracted from the target storage space as the target vehicle data.

19. The vehicle data management device according to claim 18, characterized in that, The preset rules include retaining at least one of the following parameters from the first vehicle data: vehicle battery temperature, vehicle battery charge, vehicle battery status, vehicle location information, and vehicle mileage.

20. The vehicle data management device according to claim 18, characterized in that, The management device further includes: The second sending module is used to send a communication mode change request for the vehicle terminal to the server; The receiving module is used to receive the target communication mode information fed back by the server in response to the communication mode change request; The module is used to change the communication mode of the vehicle terminal to the target communication mode, which enables the vehicle terminal to establish a communication connection with the server.

21. A server, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the vehicle data management method according to any one of claims 1 to 7.

22. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the vehicle data management method according to any one of claims 1 to 10.

Images