An Internet of Vehicles data interaction method, device and computer program product

Abstract

The application discloses a kind of Internet of Vehicles data interaction method, device and computer program product, wherein, method includes: vehicle end obtains the file to be uploaded, and requests the storage link of the file to cloud server, the request carries the identification information of the file;Vehicle end is uploaded according to the storage link returned by cloud server to cloud resource storage system the file, and sends confirmation message to cloud server after uploading is completed, the confirmation message contains the identification information of the file of next request.This application embodiment, vehicle end directly obtains the storage link of the file to be uploaded from cloud server, directly uploads data to each cloud storage, without needing to care about multi-cloud access;Confirmation message and next request are combined simultaneously, reduce request cloud service, simplify the interaction process of vehicle end and cloud, reduce communication overhead, effectively reduce the storage and processing expense of cloud real-time data warehouse, realize cost saving and resource optimization.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, specifically to a vehicle networking data interaction method, device, and computer program product. Background Technology

[0002] In the field of connected vehicles, there are currently multiple ways to upload data, mainly including MQTT, HTTP, and file data upload.

[0003] Regarding file data uploads, there are many problems in practical applications. On the vehicle side, due to the differences in storage services among various cloud vendors, the vehicle side needs to be customized for different cloud vendors to achieve access. This process involves a lot of adaptation work, which is not only huge in workload but also extremely inefficient.

[0004] Currently, the common data upload solution for vehicles involves the vehicle application first serializing the business data, and then transmitting the data to the cloud using the MQTT protocol. When the amount of data to be uploaded by the vehicle is too large, it becomes very difficult to complete the data upload via long-connection MQTT due to limitations in hardware and the low efficiency of the MQTT channel itself. If file upload is used, the vehicle must notify the cloud of the upload result after each file upload to ensure data integrity and accuracy. Only after all confirmation steps are completed can the next file be transmitted in the same process, resulting in low transmission efficiency. Summary of the Invention

[0005] The technical problem to be solved by the embodiments of the present invention is to provide a method, device and computer program product for vehicle network data interaction, so as to reduce the development workload, improve the efficiency of accessing cloud storage vendors, and reduce real-time data warehouse costs.

[0006] To address the aforementioned technical problems, this invention provides a vehicle-to-everything (V2X) data interaction method, comprising the following steps:

[0007] The vehicle obtains the file to be uploaded and requests a storage link for the file from the cloud server. The request carries the file's identification information.

[0008] The vehicle uploads the file to the cloud resource storage system based on the storage link returned by the cloud server, and sends a confirmation message to the cloud server after the upload is completed. The confirmation message contains the identification information of the file to be requested next.

[0009] Preferably, the file is stored based on a time-series signal column, and its identification information includes at least the file name, which contains the timestamp information of the file's generation.

[0010] Preferably, after the vehicle sends a confirmation message to the cloud server, it receives a confirmation message from the cloud server, which includes the storage link of the file to be requested next.

[0011] Preferably, the method further includes: the vehicle sending a query request to a cloud server through an associated client, the request containing query conditions. This embodiment of the invention also provides a vehicle-to-everything (V2X) data interaction method, including the following steps:

[0012] The cloud server receives a storage link request sent by the vehicle, the storage link request carrying the identification information of the file to be uploaded;

[0013] The cloud server generates a storage key based on the identification information, requests authorization from the cloud resource storage system to generate a storage link, and returns the storage link to the vehicle.

[0014] The cloud server receives a confirmation message from the vehicle after the upload is completed. The confirmation message contains identification information for the file to be requested next.

[0015] Preferably, the method further includes: the cloud server generating a storage link for the next requested file based on the identification information of the file in the next request and returning it to the vehicle.

[0016] Preferably, the cloud server generates a storage key for the file based on the identification information, specifically including:

[0017] The cloud server extracts the file name and its timestamp information from the identification information, and generates the storage key by combining the vehicle model and VIN according to the hierarchical storage structure of vehicle model / VIN / timestamp / file name.

[0018] Preferably, the method further includes: the cloud server receiving a query request sent by the vehicle terminal through an associated client, parsing the query conditions contained in the request, and generating a query key based on the query conditions.

[0019] Preferably, the cloud server dynamically assembles the query key based on the query conditions, specifically including:

[0020] If the time range of the query file is determined to be within a certain hour range from the query conditions, the cloud server generates the query key based on the vehicle identification number (VIN) and the time information of that hour.

[0021] If the time range of the query file is found to span multiple hours within the same day, the cloud server generates the query key by using the date as a prefix and combining it with the vehicle identification number.

[0022] If the time range of the query file is found to span multiple days from the query conditions, the cloud server will split the time range into multiple single-day sub-ranges. For each single-day sub-range, the corresponding steps described above will be repeated according to whether it is within a certain hour or spans multiple hours. Finally, the query keys of all sub-ranges will be merged.

[0023] Preferably, the method further includes:

[0024] The cloud server uses the assembled query key to initiate a query request to the cloud resource storage system, requesting the return of a list of file identifiers that match the query key;

[0025] After receiving a query request from the cloud server, the cloud resource storage system searches for the file identifiers based on the provided query key and returns a list of matching file identifiers to the cloud server. The file identifiers in the list are arranged in chronological order.

[0026] The present invention also provides a vehicle-to-everything (V2X) data interaction device, which is installed in a vehicle and includes:

[0027] The request module is used to obtain the file to be uploaded and request the storage link of the file from the cloud server. The request carries the identification information of the file.

[0028] The upload module is used to upload the file to the cloud resource storage system according to the storage link returned by the cloud server, and send a confirmation message to the cloud server after the upload is completed. The confirmation message contains the identification information of the file to be requested next.

[0029] The present invention also provides a vehicle-to-everything (V2X) data interaction device, wherein the V2X data interaction device is configured on a cloud server, comprising:

[0030] The receiving module is used to receive a storage link request sent by the vehicle terminal, wherein the storage link request carries the identification information of the file to be uploaded;

[0031] The request module is used to generate a storage key based on the identification information, request authorization from the cloud resource storage system to generate a storage link, and return the storage link to the vehicle terminal.

[0032] The receiving module is also used to receive a confirmation message after the upload is completed on the vehicle side. The confirmation message contains identification information of the file to be requested next.

[0033] The present invention also provides a vehicle-to-everything (V2X) data interaction device, comprising:

[0034] One or more processors;

[0035] Memory;

[0036] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to perform the vehicle-to-everything (V2X) data interaction method.

[0037] The present invention also provides a computer program product, including computer instructions that instruct a computer device to perform an operation corresponding to the method.

[0038] Implementing this invention offers the following advantages: The invention enables the vehicle to directly obtain the storage link of the file to be uploaded from the cloud server and directly upload data to various cloud storage systems, eliminating the need to worry about multi-cloud access. Simultaneously, by combining confirmation messages with the next request, it reduces requests to cloud services, simplifies the interaction process between the vehicle and the cloud, reduces communication overhead, and effectively lowers the storage and processing costs of the real-time cloud data warehouse, achieving cost savings and resource optimization. Furthermore, this invention can seamlessly connect to object storage services from different cloud vendors, ensuring the flexibility and breadth of data uploads. Moreover, through the hierarchical storage structure and intelligent query mechanism proposed in this invention, rapid data retrieval is achieved, eliminating the need for cumbersome data parsing upon receiving files, thus replacing traditional real-time data warehouse solutions. This invention not only significantly improves data retrieval efficiency but also significantly reduces the storage cost of single-vehicle data, providing an efficient and economical solution for large-scale vehicle data storage and management. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a flowchart illustrating a vehicle-to-everything (V2X) data interaction method according to an embodiment of the present invention.

[0041] Figure 2 This is a flowchart illustrating a vehicle-to-everything (V2X) data interaction method according to Embodiment 2 of the present invention.

[0042] Figure 3 This is a schematic diagram illustrating the process of requesting and confirming a storage link in an embodiment of the present invention.

[0043] Figure 4 This is a schematic diagram of the file uploading process in an embodiment of the present invention.

[0044] Figure 5 This is a schematic diagram of the file query process in an embodiment of the present invention. Detailed Implementation

[0045] The following description of the embodiments is taken with reference to the accompanying drawings, which illustrate specific embodiments in which the invention can be implemented.

[0046] Please refer to Figure 1 As shown, Embodiment 1 of the present invention provides a vehicle-to-everything (V2X) data interaction method, comprising the following steps:

[0047] The vehicle obtains the file to be uploaded and requests a storage link for the file from the cloud server. The request carries the file's identification information.

[0048] The vehicle uploads the file to the cloud resource storage system based on the storage link returned by the cloud server, and sends a confirmation message to the cloud server after the upload is completed. The confirmation message contains the identification information of the file to be requested next.

[0049] As can be seen from the above steps, in this embodiment of the invention, the vehicle directly obtains the storage link of the file to be uploaded from the cloud server and directly uploads the data to each cloud storage without needing to worry about multi-cloud access; at the same time, the confirmation message and the next request are combined to reduce requests to cloud services, simplify the interaction process between the vehicle and the cloud, reduce communication overhead, and effectively reduce the storage and processing costs of the real-time data warehouse in the cloud, thus achieving cost savings and resource optimization.

[0050] Please refer to again Figure 2 As shown, Embodiment 2 of the present invention provides a vehicle-to-everything (V2X) data interaction method, comprising the following steps:

[0051] The cloud server receives a storage link request sent by the vehicle, the storage link request carrying the identification information of the file to be uploaded;

[0052] The cloud server generates a storage key based on the identification information, requests authorization from the cloud resource storage system to generate a storage link, and returns the storage link to the vehicle.

[0053] The cloud server receives a confirmation message from the vehicle after the upload is completed. The confirmation message contains identification information for the file to be requested next.

[0054] The vehicle-to-everything (V2X) data interaction method described above focuses on execution on the cloud server, requesting authorization to obtain the storage link of the file to be uploaded and sending it back to the vehicle, and receiving a confirmation message containing the identification information of the file to be requested next, so as to generate the storage link of the file to be requested next, thereby reducing waiting time.

[0055] Specifically, please combine Figure 3 , Figure 4As shown in this embodiment of the invention, the vehicle-side generated files are saved in a time-series database format as small files, i.e., based on time-series signal column storage. The filename contains detailed timestamp information at the time of file generation, in the format "yyyyMMddHHmmssSSS", representing year, month, day, hour, minute, second, and millisecond, respectively, ensuring that each file has a unique and easily identifiable time identifier. These files are saved as small files, rather than concentrating all data in one large file. The small file method facilitates fast data reading and writing, and also simplifies subsequent data processing and management.

[0056] Therefore, the file's identification information must at least include the filename, which contains a timestamp indicating when the file was generated. It's understandable that the vehicle model represents the type or style of the vehicle, while the VIN (Vehicle Identification Number) is the vehicle's unique identifier; thus, the file's identification information can also include the vehicle model and VIN. This identification information ensures the file's uniqueness and prevents data confusion or overwriting. Subsequently, the vehicle sends the generated identification information to the cloud server along with a storage link (URL) request.

[0057] After receiving a request from the vehicle, the cloud server extracts the filename and its timestamp from the identification information. Combining this with the vehicle model and VIN, it generates a storage key according to the rule "Vehicle Model / VIN / yyyyMMddHH / Filename". This storage key is used to locate the file in the cloud resource storage system. In object storage systems, too many leaf nodes (i.e., files) or a large number of files / folders in the same directory can slow down retrieval. The aforementioned rule design in this embodiment helps reduce path depth and the number of files / folders at the same level. By storing files hierarchically by vehicle model, VIN, and hour, storing too many files in a single directory can be avoided, thereby speeding up the query process.

[0058] After generating the storage key, the cloud server uses this key to send an authorization request to the cloud resource (such as cloud resources provided by various cloud vendors) storage system, including the necessary authentication information. After verifying the request, the cloud resource storage system generates a storage link (URL) for uploading files and returns this storage link to the cloud for the vehicle to upload files.

[0059] The cloud server returns a storage link to the vehicle, which then uploads the corresponding file to the cloud resource storage system using that link. Once the file upload is complete, the vehicle sends a confirmation message to the cloud server to notify it that the file upload was successful.

[0060] One innovation of this invention is that if there are other files to be uploaded to the vehicle, the confirmation message can include the identifier information of the next requested file. In this way, the cloud server, while confirming the current file, simultaneously generates the storage link for the next file and returns it to the vehicle, thereby shortening the time for uploading multiple files.

[0061] Specifically, after receiving the confirmation message from the vehicle, the cloud server can immediately begin preprocessing the storage of the next file based on the file identifier information included in the next request. This includes requesting cloud resource storage authorization and generating a storage link for the next file. In this way, the cloud server does not need to wait for the vehicle to initiate another request before processing the storage of the next file, thus saving time. Once the vehicle receives the storage link for the next file, it can immediately use that link to upload the next file. Furthermore, this process can continue continuously until all files have been uploaded.

[0062] This process reduces the number of interactions between the cloud server and the vehicle, thereby lowering communication overhead and latency. The cloud server can process multiple file storage requests in parallel without waiting for the vehicle to initiate requests one by one, thus improving overall upload efficiency. Simultaneously, the reduced waiting time enhances the responsiveness of the entire system and improves the user experience.

[0063] If there are no more files to upload on the vehicle side, the confirmation message does not need to include the identification information of the files to be requested next; that is, the confirmation message only indicates that the upload was successful.

[0064] Please refer to again Figure 5 As shown, when a file needs to be queried, the client associated with the vehicle sends a query request to the cloud server. This request includes query conditions such as vehicle model, VIN, and time range.

[0065] It should be noted that the client applications associated with the vehicle include the following forms:

[0066] In-vehicle infotainment (IVI) systems typically come equipped with a browser or dedicated application that allows the owner or passengers to access internet services or vehicle-related data via a touchscreen interface. In this case, the owner or passengers can use the browser or application within the IVI system to send query requests to a cloud server to retrieve the required vehicle data files.

[0067] Vehicle owner's mobile phone linked to the vehicle: The vehicle owner can remotely access and manage vehicle data through applications on their mobile phone (such as a vehicle management app or browser). When needing to query vehicle data files, the owner can open the application on their mobile phone, send a query request to the cloud server through the application, and receive and process the file data returned by the cloud server.

[0068] Other terminals: In addition to in-vehicle infotainment systems and car owners' mobile phones, other types of terminals can also be used to query and use vehicle data files. For example, vehicle data analysts or repair technicians use dedicated computers or tablets to access vehicle data on cloud servers for more in-depth analysis or diagnostics.

[0069] After receiving a query request, the cloud server first parses the query conditions in the request. Based on these query conditions, the cloud server dynamically assembles a query key according to predetermined rules or algorithms (such as concatenation, hashing, etc.) to match it with the corresponding file in the cloud resource storage system.

[0070] Specifically, the cloud server assembles different query keys based on the time range and sends query requests to the cloud resource storage system:

[0071] (1) The time range is within a certain hour:

[0072] When the cloud server receives a query request from a client and parses it to show that the time range is within a certain hour, the cloud server will dynamically assemble a query key based on the vehicle identification number (VIN) and the time information of that hour.

[0073] (2) If the time range spans multiple hours but not days, search by the day prefix:

[0074] If the time range spans multiple hours but is still within the same day, the cloud server will dynamically assemble a query key based on the day information (i.e., the date) and the vehicle identification number (VIN).

[0075] (3) If the time range spans multiple days, break it down according to the number of days spanned, and repeat the previous two steps:

[0076] When the time range spans multiple days, the cloud server splits this time range into multiple single-day sub-ranges, and then repeats the previously mentioned steps (2) or (3) for each single-day sub-range (depending on whether the sub-range spans hours), merges the query results of all sub-ranges, and performs the final filtering.

[0077] The cloud server uses a pre-assembled query key to initiate a query request to the cloud resource storage system, requesting a list of file identifiers that match the query key. It's important to note that the file identifier list refers to the set of file identifiers retrieved by the cloud resource storage system during the query process that match the query conditions (such as vehicle model, VIN, time range, etc.). The file identifier list contains multiple file identifiers, each corresponding to a file that meets the query conditions.

[0078] After receiving a query request from the cloud server, the cloud resource storage system searches for matching file identifiers based on the provided query key and returns a list of matching file identifiers to the cloud server. These file identifiers are used by the cloud resource storage system to identify files. The file identifiers in the list are arranged in chronological order.

[0079] After receiving the file identifier list from the cloud resource storage system, the cloud server performs further processing, such as filtering and sorting, to meet the query requirements. Once processing is complete, the cloud server returns the file identifier list to the client in chronological order.

[0080] After receiving the list of file identifiers from the cloud server, the client downloads the corresponding file from the cloud resource storage system based on the file identifier. After downloading the file, the client then parses the data in the file as needed, based on the file's content and format, as well as timestamps and signal information, and displays it to the user or performs further processing.

[0081] Corresponding to the vehicle-to-everything (V2X) data interaction methods described in Embodiments 1 and 2 of the present invention, Embodiment 3 of the present invention also provides a V2X data interaction device, which is disposed in a vehicle and includes:

[0082] The request module is used to generate a file based on time series signal column storage and request a storage link for the file from the cloud server. The request carries the identification information of the file.

[0083] The upload module is used to upload the file to the cloud resource storage system according to the storage link returned by the cloud server, and send a confirmation message to the cloud server after the upload is completed. The confirmation message contains the identification information of the file to be requested next.

[0084] Corresponding to the vehicle-to-everything (V2X) data interaction methods described in Embodiments 1 and 2 of the present invention, Embodiment 4 of the present invention also provides a V2X data interaction device, which is disposed in a vehicle and includes:

[0085] The receiving module is used to receive a storage link request sent by the vehicle terminal, wherein the storage link request carries the identification information of the file to be uploaded;

[0086] The request module is used to generate a storage key based on the identification information, request authorization from the cloud resource storage system to generate a storage link, and return the storage link to the vehicle terminal.

[0087] The receiving module is also used to receive a confirmation message after the upload is completed on the vehicle side. The confirmation message contains identification information of the file to be requested next.

[0088] Corresponding to the vehicle-to-everything (V2X) data interaction methods described in Embodiments 1 and 2 of the present invention, Embodiment 5 of the present invention also provides a V2X data interaction device, comprising:

[0089] One or more processors;

[0090] Memory;

[0091] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to respectively execute the vehicle-to-everything (V2X) data interaction methods described in Embodiments 1 and 2 of the present invention.

[0092] Corresponding to the vehicle-to-everything (V2X) data interaction methods described in Embodiments 1 and 2 of the present invention, Embodiment 6 of the present invention also provides a computer program product, including computer instructions, which instruct computer devices to perform the operations corresponding to the V2X data interaction methods described in Embodiments 1 and 2 of the present invention, respectively.

[0093] Preferably, the computer instructions can be divided into one or more modules / units (such as computer program 1, computer program 2, ...), and the one or more modules / units are stored in the memory and executed by the processor to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing a specific function, and the instruction segments are used to describe the execution process of the computer program in the device.

[0094] Preferably, the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor, or the processor can be any conventional processor. The processor is the control center of the device, connecting various parts of the device through various interfaces and lines.

[0095] The memory mainly includes a program storage area and a data storage area. The program storage area can store the operating system, applications required for at least one function, etc., while the data storage area can store related data, etc. Furthermore, the memory can be a high-speed random access memory, or a non-volatile memory, such as a plug-in hard drive, a SmartMedia Card (SMC), a Secure Digital (SD) card, and a Flash Card, or other volatile solid-state storage devices.

[0096] It should be noted that the above-mentioned devices may include, but are not limited to, processors and memory, as will be understood by those skilled in the art.

[0097] For the working principle and process of the above embodiments, please refer to the description of Embodiment 1 of the present invention, which will not be repeated here.

[0098] As described above, compared with existing technologies, the advantages of this invention are as follows: This invention enables the vehicle to directly obtain the storage link of the file to be uploaded from the cloud server and directly upload data to various cloud storage systems, eliminating the need to worry about multi-cloud access. Simultaneously, by combining confirmation messages and the next request, it reduces requests to cloud services, simplifies the interaction process between the vehicle and the cloud, reduces communication overhead, and effectively lowers the storage and processing costs of the real-time cloud data warehouse, achieving cost savings and resource optimization. Furthermore, this invention can seamlessly connect to object storage services from different cloud vendors, ensuring the flexibility and breadth of data uploads. Moreover, through the hierarchical storage structure and intelligent query mechanism proposed in this invention, rapid data retrieval is achieved, eliminating the need for cumbersome data parsing upon receiving files, thus replacing traditional real-time data warehouse solutions. This invention not only greatly improves data retrieval efficiency but also significantly reduces the storage cost of single-vehicle data, providing an efficient and economical solution for large-scale vehicle data storage and management.

[0099] The above description is merely a preferred embodiment of the present invention and should not be construed as limiting the scope of the invention. Therefore, any equivalent variations made in accordance with the claims of the present invention are still within the scope of the present invention.

Claims

1. A method for data interaction in the Internet of Vehicles (IoV), characterized in that, Includes the following steps: The vehicle obtains the file to be uploaded and requests a storage link for the file from the cloud server. The request carries the file's identification information. The vehicle uploads the file to the cloud resource storage system based on the storage link returned by the cloud server, and sends a confirmation message to the cloud server after the upload is completed. The confirmation message contains the identification information of the file to be requested next.

2. The method according to claim 1, characterized in that, The file is stored based on a time-series signal column, and its identification information includes at least the file name, which contains the timestamp information of the file's generation.

3. The method according to claim 1, characterized in that, After the vehicle sends a confirmation message to the cloud server, it receives a confirmation message from the cloud server, which includes the storage link of the file to be requested next.

4. The method according to claim 1, characterized in that, Also includes: The vehicle sends a query request to the cloud server through the associated client, and the request contains query conditions.

5. A method for data interaction in the Internet of Vehicles, characterized in that, Includes the following steps: The cloud server receives a storage link request sent by the vehicle, the storage link request carrying the identification information of the file to be uploaded; The cloud server generates a storage key based on the identification information, requests authorization from the cloud resource storage system to generate a storage link, and returns the storage link to the vehicle. The cloud server receives a confirmation message from the vehicle after the upload is completed. The confirmation message contains identification information for the file to be requested next.

6. The method according to claim 5, characterized in that, Also includes: Based on the identifier information of the file requested in the next request, the cloud server generates a storage link for the file requested in the next request and returns it to the vehicle.

7. The method according to claim 5, characterized in that, The cloud server generates a storage key for the file based on the identification information, specifically including: The cloud server extracts the file name and its timestamp information from the identification information, and generates the storage key by combining the vehicle model and VIN according to the hierarchical storage structure of vehicle model / VIN / timestamp / file name.

8. The method according to claim 5, characterized in that, Also includes: The cloud server receives a query request sent by the vehicle through an associated client, parses the query conditions contained in the request, and generates a query key based on the query conditions.

9. The method according to claim 8, characterized in that, The cloud server generates a query key based on the query conditions, specifically including: If the time range of the query file is determined to be within a certain hour range from the query conditions, the cloud server generates the query key based on the vehicle identification number (VIN) and the time information of that hour. If the time range of the query file is found to span multiple hours within the same day, the cloud server generates the query key by using the date as a prefix and combining it with the vehicle identification number. If the time range of the query file is found to span multiple days from the query conditions, the cloud server will split the time range into multiple single-day sub-ranges. For each single-day sub-range, the corresponding steps described above will be repeated according to whether it is within a certain hour or spans multiple hours. Finally, the query keys of all sub-ranges will be merged.

10. The method according to claim 8, characterized in that, Also includes: The cloud server uses the generated query key to initiate a query request to the cloud resource storage system, requesting the return of a list of file identifiers that match the query key; After receiving a query request from the cloud server, the cloud resource storage system searches for the file identifiers based on the provided query key and returns a list of matching file identifiers to the cloud server. The file identifiers in the list are arranged in chronological order.

11. A vehicle-to-everything (V2X) data interaction device, characterized in that, The vehicle-to-everything (V2X) data interaction device is installed in the vehicle and includes: The request module is used to obtain the file to be uploaded and request the storage link of the file from the cloud server. The request carries the identification information of the file. The upload module is used to upload the file to the cloud resource storage system according to the storage link returned by the cloud server, and send a confirmation message to the cloud server after the upload is completed. The confirmation message contains the identification information of the file to be requested next.

12. A vehicle-to-everything (V2X) data interaction device, characterized in that, The vehicle-to-everything (V2X) data interaction device is located on a cloud server and includes: The receiving module is used to receive a storage link request sent by the vehicle terminal, wherein the storage link request carries the identification information of the file to be uploaded; The request module is used to generate a storage key based on the identification information, request authorization from the cloud resource storage system to generate a storage link, and return the storage link to the vehicle terminal. The receiving module is also used to receive a confirmation message after the upload is completed on the vehicle side. The confirmation message contains identification information of the file to be requested next.

13. A vehicle-to-everything (V2X) data interaction device, characterized in that, include: One or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to perform the vehicle-to-everything (V2X) data interaction method as described in any one of claims 1 to 10.

14. A computer program product, characterized in that, Includes computer instructions that instruct a computer device to perform an operation corresponding to the method as described in any one of claims 1 to 10.

Images