Travel map display method and device

Abstract

The invention relates to the technical field of travel maps, and particularly discloses a travel map display method and device, and the method comprises the steps: collecting vehicle data and platform data of vehicle driving; respectively converting the vehicle data and the platform data into metadata, and uploading the metadata to a communication data platform; outputting the metadata from the communication data platform to a map service platform according to time periods; and carrying out travel map display on the metadata by utilizing the map service platform. According to the travel map display method provided by the invention, the multi-data-source data is acquired, the vehicle machine data is analyzed, the other platform source data is screened to adapt to the metadata, and the metadata is uniformly output, so that the problems of high complexity and low performance of multi-data-source data processing are solved, and the availability and expansibility are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of itinerary maps, and in particular to a itinerary map display method and device. Background Art

[0002] The vehicle itinerary map display requires unified processing of data in different formats from different sources coming from the vehicle-computer communication terminal and other data platforms. At the same time, the front end needs to display the owner's itinerary on the vehicle-computer terminal and mobile phone terminal (Android and iOS), highlighting the city area reached.

[0003] Existing technical solutions cannot effectively process data from multiple data sources, and cannot maintain a unified display style on the vehicle platform, the user's client, and the system platform. At the same time, the existing rendering of city travel data is usually inefficient, and the rendering of the map lighting city effect is often stuck, affecting the user experience. Furthermore, the existing technical solutions are prone to data leakage due to the lack of a security authentication mechanism.

[0004] Therefore, we look forward to a technical solution that optimizes data stability, improves front-end rendering performance, and optimizes data security.

[0005] Based on this technical background, the present invention studies a method and device for displaying a trip map. Summary of the invention

[0006] In view of the shortcomings of the prior art, the present invention proposes a method and device for displaying a trip map. The method obtains data from multiple data sources, parses vehicle data, and filters data from other platforms to adapt metadata and output the metadata in a unified manner, thereby solving the problems of high complexity and low performance in data processing from multiple data sources and improving usability and scalability.

[0007] In order to achieve the above object, the present invention provides a first aspect of a method for displaying a trip map, comprising:

[0008] Collect vehicle data and platform data of vehicle driving;

[0009] The vehicle data and platform data are converted into metadata respectively and uploaded to the communication data platform;

[0010] Outputting the metadata from the communication data platform to the map service platform according to time periods;

[0011] The map service platform is used to display the metadata on a travel map.

[0012] A second aspect of the present invention provides a trip map display device, comprising:

[0013] The collection module is used to collect vehicle data and platform data during vehicle travel;

[0014] A conversion module, used for converting the vehicle data and platform data into metadata respectively and uploading them to the communication data platform;

[0015] An output module, used to output the metadata from the communication data platform to the map service platform according to time periods;

[0016] A display module is used to display the metadata on a trip map using the map service platform.

[0017] A third aspect of the present invention provides an electronic device, the electronic device comprising:

[0018] A memory storing executable instructions;

[0019] A processor, wherein the processor runs the executable instructions in the memory to implement the itinerary map display method described in the first aspect.

[0020] A fourth aspect of the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the itinerary map display method described in the first aspect.

[0021] The technical effects of the present invention include:

[0022] (1) The itinerary map display method proposed in the present invention obtains data from multiple data sources, parses vehicle data, and filters data from other platforms to adapt metadata and output the metadata in a unified manner, thereby solving the problems of high complexity and low performance of data processing from multiple data sources and improving usability and scalability.

[0023] (2) The itinerary map display method proposed in the present invention outputs unified itinerary data in the background, and displays it to multiple users on the front end based on the open API of the map service platform, thereby solving the problem of inconsistent effects of itinerary map displays on multiple ends and unifying the display style of the front end. At the same time, the cities involved are highlighted, and the frequencies of arrival at different cities are displayed in a hierarchical manner, thereby ensuring the display effect.

[0024] (3) The four-motor distributed electric drive method proposed in the present invention uses a thread pool to optimize loading efficiency, solves the problem of rendering jams when the number of cities is increased, and improves the efficiency of rendering city travel data.

[0025] Other features and advantages of the present invention will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The above and other objects, features and advantages of the present invention will become more apparent through a more detailed description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, wherein like reference numerals generally represent like components throughout the exemplary embodiments of the present invention.

[0027] Figure 1 The figure is a flow chart of the itinerary map display method proposed in the present invention.

[0028] Figure 2 The present invention is a flowchart of a specific implementation of the itinerary map display method proposed in the present invention.

[0029] Figure 3 This is a schematic diagram of the data display process of a specific implementation of the itinerary map display method proposed in the present invention.

[0030] Figure 4 A schematic diagram of the thread optimization allocation process of a specific implementation of the itinerary map display method proposed in the present invention.

[0031] Figure 5 A schematic diagram of a dual authentication process for a specific implementation of the itinerary map display method proposed in the present invention. DETAILED DESCRIPTION

[0032] The preferred embodiments of the present invention will be described in more detail below. Although the preferred embodiments of the present invention are described below, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.

[0033] In the present invention, unless otherwise specified, the directional words used, such as "upper and lower", generally refer to the upper and lower parts of the device in normal use, and "inside and outside" refer to the outline of the device. In addition, the terms "first, second, third" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first, second, third" may explicitly or implicitly include one or more of the features. In the description of the present invention, "multiple" means two or more, unless otherwise clearly and specifically defined.

[0034] The present invention provides a method for displaying a route map. Figure 1 As shown, including:

[0035] Collect vehicle data and platform data of vehicle driving;

[0036] Convert the vehicle data and platform data into metadata respectively and upload them to the communication data platform;

[0037] Output metadata from the communication data platform to the map service platform according to time periods;

[0038] Use the map service platform to display the metadata on the itinerary map.

[0039] In the present invention, data from multiple data sources are obtained, vehicle computer data is parsed, and data from other platforms are screened to adapt metadata, and the metadata is uniformly output, which solves the problems of high complexity and low performance of data processing from multiple data sources and improves usability and scalability.

[0040] According to the present invention, the vehicle computer data is the trip details data recorded by a program in the vehicle computer;

[0041] Converting vehicle data into metadata and uploading it to the communication data platform includes:

[0042] After the trip, the vehicle data is converted into vehicle metadata;

[0043] When there is a network, upload the vehicle metadata to the communication data platform;

[0044] When there is no network, the vehicle metadata is stored in sequence, and after being acquired from the network, it is uploaded to the communication data platform in the order of storage.

[0045] According to the present invention, the platform data includes Tbox platform data and cloud platform data;

[0046] Converting platform data into metadata and uploading it to the communication data platform includes:

[0047] The cloud platform data is spliced ​​into the data primary key by the vehicle identification code and the timestamp at the end of the trip;

[0048] Convert cloud platform data into cloud platform metadata;

[0049] Upload the cloud platform metadata to the communication data platform and use the data primary key to determine if there is duplicate data.

[0050] According to the present invention, converting the vehicle computer data into vehicle computer metadata includes:

[0051] Determine the type of vehicle data;

[0052] Write a serialization protocol based on the type of vehicle data;

[0053] Use serialization protocol to convert vehicle computer data into binary format data;

[0054] Add header information at the beginning of the binary format data to form vehicle metadata.

[0055] Preferably, converting the cloud platform data into cloud platform metadata includes:

[0056] The cloud platform data is integrated using data warehouse or data lake technology to obtain integrated data.

[0057] Standardize the integrated data to obtain cloud platform metadata;

[0058] Standardization processing includes format conversion, coordinate system unification and unit unification.

[0059] According to the present invention, outputting metadata from the communication data platform to the map service platform according to time periods includes:

[0060] Integrate metadata into the map service platform by time period;

[0061] Use the API interface of the map service platform to upload and update metadata;

[0062] The format of metadata is json;

[0063] Using the map service platform to display the metadata on the itinerary map includes:

[0064] Design user interaction functions based on the needs of itinerary map display, and display itinerary maps on the vehicle terminal, iOS client, and Android terminal. The interactive function is used by users to customize the lighting effect of the arrival area on the map and customize the results of click events;

[0065] Dynamically create the number of threads in the thread pool according to the number of city lists, optimize the thread allocation for rendering tasks, and display the itinerary map;

[0066] Thread optimization allocation for rendering tasks includes:

[0067] When the number of threads in the thread pool does not reach the set value, a new thread is created in the thread pool for the input rendering task;

[0068] When the number of threads in the thread pool reaches the set value, the input rendering task is placed in the task queue and queued. If a thread in the thread pool is vacant, the input rendering task enters the thread in the order of the task queue for execution;

[0069] Rendering tasks include lighting up the map's layers, querying city coordinate ranges, and matching map overlay colors.

[0070] In the present invention, according to the unified itinerary data output of the background, the front end opens the API based on the map service platform and displays it to multi-terminal users, thereby solving the problem of inconsistent effects of itinerary maps displayed on multiple terminals and unifying the display style of the front end; at the same time, the cities involved are highlighted, and the frequency of arrival in different cities is displayed in a hierarchical manner to ensure the display effect.

[0071] According to the present invention, the collection of vehicle data and platform data, as well as the uploading and output of metadata, all comply with the MQTT protocol, using certificates and accounts for dual authentication;

[0072] Accessing the API interface includes the following operations:

[0073] Use the account and password to request user token information;

[0074] Add user token information;

[0075] After certificate verification;

[0076] The first trip map showcase includes:

[0077] Ask whether it supports using trip data for display;

[0078] Asks whether map rendering is supported.

[0079] In the present invention, a thread pool is used to optimize loading efficiency, which solves the problem of map lighting city rendering jams when the number of cities increases, and improves the efficiency of rendering city travel data.

[0080] The present invention will be described in more detail below through specific embodiments.

[0081] Embodiment 1:

[0082] like Figure 2 As shown, this embodiment proposes a method for displaying a trip map, which specifically includes the following steps:

[0083] 1. Data Collection:

[0084] There are two main data sources: one is the message data from the vehicle computer, and the other is the original data from the Tbox platform or other cloud platforms. Metadata needs to be set and the initial data needs to be processed uniformly to meet subsequent display requirements;

[0085] 1. Car data:

[0086] The in-vehicle program records the trip details and uploads them to the communication data platform in time after the trip if there is a network connection. If there is no network connection, the data will be stored in sequence and uploaded to the platform after the network connection is established.

[0087] 2. Other platform data:

[0088] After receiving the trip data, the third-party platform uses the VIN (vehicle identification code) + the trip end time timestamp as the data primary key, and forwards the data to this platform in a timely manner. When receiving the data, the primary key is used to judge to ensure that there is no duplicate data;

[0089] 2. Data storage and processing:

[0090] 1. Metadata definition:

[0091] Metadata is used to describe basic data related to the trip; all data must eventually be processed into a format that is compatible with metadata before it can be stored in the database;

[0092] The pseudo code of the data primary key is:

[0093] {recordId / / data primary key

[0094] arriveDay:2023-12-11 / / travel date

[0095] carVin=LNBSC12K0PZ037000, / / Vehicle VIN

[0096] cityId=500000, / / city ID

[0097] cityName=Chongqing, / / city name

[0098] driveEndLat=29.673997,driveEndLon=106.61766, / / end point longitude and latitude

[0099] provinceId=500000, / / Province ID

[0100] provinceName = Chongqing, / / Province name

[0101] updateTime = 2023-12-11 08:45:27 / / Date of last trip

[0102] };

[0103] 2. Processing of vehicle data:

[0104] Binary message serialization is the process of converting data into binary format for transmission over a network or storage on disk; the following are the basic steps of binary message serialization:

[0105] 1) Determine the data type: Before serialization, you need to determine the type of data to be transmitted, such as integer, floating point number, string, etc.;

[0106] 2) Write a serialization protocol: In order to convert data into binary format, you need to write a serialization protocol; the protocol should define how to convert each data type into binary format, and how to represent the length and order of the data type in the binary format;

[0107] 3) Convert the data into binary format: According to the serialization protocol, convert the data into binary format; for example, for integer type data, it may be necessary to divide it into multiple bytes and convert each byte into binary format;

[0108] 4) Add header information: In order to identify the serialized data type and length and other information, header information can be added at the beginning of the binary message; the header information can be fixed length or variable length, depending on the design of the serialization protocol;

[0109] 5) Send binary message: send the serialized data and header information together; the sending method can be network transmission or file storage, etc.;

[0110] 6) Deserialization: After receiving the binary message, the receiver needs to deserialize it according to the serialization protocol and convert the binary data back to the original data type;

[0111] It should be noted that different programming languages ​​and protocols may have different serialization methods, so in practical applications, it is necessary to choose the appropriate serialization method according to the specific situation;

[0112] 3. Data processing of other platforms:

[0113] 1) Data integration: Integrate multiple data sources, including but not limited to map data, user trajectory data, traffic flow data, etc.; data warehouse or data lake technologies can be used to store and manage data;

[0114] 2) Data standardization: standardize the integrated data, including format conversion, coordinate system, unit unification, etc., to ensure the accuracy and comparability of the data;

[0115] 3. Data output:

[0116] Integrate standardized data into the map service platform. You can use the platform's API interface to upload and update data in json format, and output maps to display relevant data fields.

[0117] The data field example pseudo code is:

[0118] [City(arrivalDay = 2023 - 12 - 11, carVin = LNBSC12K0PZ037000, cityId = 500000, cityName = Chongqing, driveEndLat = 29.673997, driveEndLon = 106.61766, gotoNums = 81, provinceId = 500000, provinceName = Chongqing, updateTime = 2023 - 12 - 11 08:45:27)];

[0119] A single piece of data within the City list combines metadata and statistical frequencies;

[0120] IV. Data Display:

[0121] To meet the need to display trip data using a map, after research, the Amap Open Platform API was selected for display; the custom style of Amap supports web js calls, Android clients, and ios clients, and can adapt to three display terminals to ensure the unity of the display effect; based on the Amap API, this method realizes the unified display of trip data across multiple operating systems, forming map visualization and function customization development; Amap supports the extraction and independent rendering of massive data, and the custom style and independent rendering of fine-grained control elements can meet the display and interaction of complex scenarios, such as Figure 3 shown;

[0122] 1. Interactive Function Design:

[0123] Design interactive functions according to requirements, such as map zooming, moving, searching, etc., to improve the user experience and the operability of the map; customize the lighting effect of the arrival area of the map and customize the processing of the results of defining click events;

[0124] 2. Dynamic Data Display Method Based on Thread Pool:

[0125] Optimization of lighting the map; lighting cities includes three parts: determining the lighting level, querying the city coordinate range, and matching colors for map coverage; finding the urbanization boundary and color rendering are relatively time-consuming operations, and when the city list is too large, the loading will be relatively slow;

[0126] For this situation, the method adopts an implementation plan of a thread pool, as Figure 4 shown; the thread pool aims to create multiple threads, and by reusing existing threads, reduce the resource consumption caused by the creation and destruction of threads in the system and improve the rendering speed of the map;

[0127] In this method, the minimum task unit includes the search and rendering of the city coordinate range; the metadata list of the cities that have been reached is traversed, and unit tasks are created in sequence; when a task arrives, it can be executed immediately without waiting for the creation of a new thread; it is convenient to control the number of concurrent threads; however, the thread pool does not create too many threads at the beginning, which may occupy too many resources and block the system or cause OOM and other conditions, thereby reducing the stability of the system; in the solution, the number of threads in the thread pool is dynamically created according to the number of city lists, effectively controlling threads, uniformly allocating and tuning, and improving resource utilization;

[0128] The efficiency comparison after using thread pool technology is shown in Table 1;

[0129] Table 1 Efficiency comparison after using thread pool technology

[0130]

[0131] By comparison, we can find that using thread pool can significantly improve rendering efficiency. The more cities need to be rendered, the more obvious the performance improvement.

[0132] 3. Security:

[0133] like Figure 5 As shown, for the collection of vehicle data, the MQTT protocol is used, and a double-layer authentication mechanism of certificates and accounts is used to ensure data security and privacy protection, and prevent data leakage and unauthorized access;

[0134] Data synchronization between platforms uses the MQTT protocol, certificate verification, and double verification of the account system to ensure data consistency and security;

[0135] When the front-end requests back-end interface data, it first uses the account password to request the user token information. The interface request needs to add token information, and the interface can be accessed only after the certificate is verified; this ensures the privacy of access and prevents private data from being stolen;

[0136] When the map is displayed for the first time, you will be asked whether it supports the use of travel data for display and whether it supports Amap rendering; it will only be displayed when both are agreed.

[0137] In this embodiment, the unified display method of multi-data source and multi-platform itinerary maps needs to comprehensively consider aspects such as data integration, standardization, integration, display, interactive design, performance optimization and security assurance to achieve visual data management and services.

[0138] Embodiment 2:

[0139] This embodiment provides a method for displaying a trip map. Figure 1 As shown, including:

[0140] Collect vehicle data and platform data of vehicle driving;

[0141] Convert the vehicle data and platform data into metadata respectively and upload them to the communication data platform;

[0142] Output metadata from the communication data platform to the map service platform according to time periods;

[0143] Use the map service platform to display the metadata on the itinerary map;

[0144] The vehicle computer data is the trip details data recorded by the program in the vehicle computer;

[0145] Converting vehicle data into metadata and uploading it to the communication data platform includes:

[0146] After the trip, the vehicle data is converted into vehicle metadata;

[0147] When there is a network, upload the vehicle metadata to the communication data platform;

[0148] When there is no network, the vehicle metadata is stored in sequence, and after being acquired from the network, it is uploaded to the communication data platform in the order of storage;

[0149] Platform data includes Tbox platform data and cloud platform data;

[0150] Converting platform data into metadata and uploading it to the communication data platform includes:

[0151] The cloud platform data is spliced ​​into the data primary key by the vehicle identification code and the timestamp at the end of the trip;

[0152] Convert cloud platform data into cloud platform metadata;

[0153] Upload the cloud platform metadata to the communication data platform and use the data primary key to determine if there is duplicate data;

[0154] Converting vehicle data into vehicle metadata includes:

[0155] Determine the type of vehicle data;

[0156] Write a serialization protocol based on the type of vehicle data;

[0157] Use serialization protocol to convert vehicle computer data into binary format data;

[0158] Add header information at the beginning of binary format data to form vehicle machine metadata;

[0159] Converting cloud platform data into cloud platform metadata includes:

[0160] Use data warehouse or data lake technology to integrate cloud platform data to obtain integrated data;

[0161] Standardize the integrated data to obtain cloud platform metadata;

[0162] Standardization processing includes format conversion, coordinate system unification and unit unification;

[0163] The metadata is exported from the communication data platform to the map service platform according to the time period, including:

[0164] Integrate metadata into the map service platform by time period;

[0165] Use the API interface of the map service platform to upload and update metadata;

[0166] The format of metadata is json;

[0167] Using the map service platform to display the metadata on the itinerary map includes:

[0168] Design user interaction functions based on the needs of itinerary map display, and display itinerary maps on the vehicle terminal, iOS client, and Android terminal. The interactive function is used by users to customize the lighting effect of the arrival area on the map and customize the results of click events;

[0169] Dynamically create the number of threads in the thread pool according to the number of city lists, optimize the thread allocation for rendering tasks, and display the itinerary map;

[0170] Thread optimization allocation for rendering tasks includes:

[0171] When the number of threads in the thread pool does not reach the set value, a new thread is created in the thread pool for the input rendering task;

[0172] When the number of threads in the thread pool reaches the set value, the input rendering task is placed in the task queue and queued. If a thread in the thread pool is vacant, the input rendering task enters the thread in the order of the task queue for execution;

[0173] Rendering tasks include lighting up the map’s layers, querying city coordinate ranges, and matching map overlay colors;

[0174] The collection of vehicle data and platform data, as well as the upload and output of metadata, all comply with the MQTT protocol, using certificates and accounts for dual authentication;

[0175] Accessing the API interface includes the following operations:

[0176] Use the account and password to request user token information;

[0177] Add user token information;

[0178] After certificate verification;

[0179] The first trip map showcase includes:

[0180] Ask whether it supports using trip data for display;

[0181] Asks whether map rendering is supported.

[0182] Embodiment three:

[0183] This embodiment provides a trip map display device, including:

[0184] The collection module is used to collect vehicle data and platform data during vehicle travel;

[0185] A conversion module, used to convert the vehicle data and platform data into metadata and upload them to the communication data platform;

[0186] An output module, used to output metadata from the communication data platform to the map service platform according to time periods;

[0187] A display module is used to display the metadata on a trip map using a map service platform;

[0188] Converting vehicle data into metadata and uploading it to the communication data platform includes:

[0189] After the trip, the vehicle data is converted into vehicle metadata;

[0190] When there is a network, upload the vehicle metadata to the communication data platform;

[0191] When there is no network, the vehicle metadata is stored in sequence, and after being acquired from the network, it is uploaded to the communication data platform in the order of storage;

[0192] Platform data includes Tbox platform data and cloud platform data;

[0193] Converting platform data into metadata and uploading it to the communication data platform includes:

[0194] The cloud platform data is spliced ​​into the data primary key by the vehicle identification code and the timestamp at the end of the trip;

[0195] Convert cloud platform data into cloud platform metadata;

[0196] Upload the cloud platform metadata to the communication data platform and use the data primary key to determine if there is duplicate data;

[0197] Converting vehicle data into vehicle metadata includes:

[0198] Determine the type of vehicle data;

[0199] Write a serialization protocol based on the type of vehicle data;

[0200] Use serialization protocol to convert vehicle computer data into binary format data;

[0201] Add header information at the beginning of binary format data to form vehicle machine metadata;

[0202] Converting cloud platform data into cloud platform metadata includes:

[0203] Use data warehouse or data lake technology to integrate cloud platform data to obtain integrated data;

[0204] Standardize the integrated data to obtain cloud platform metadata;

[0205] Standardization processing includes format conversion, coordinate system unification and unit unification;

[0206] The metadata is exported from the communication data platform to the map service platform according to the time period, including:

[0207] Integrate metadata into the map service platform by time period;

[0208] Use the API interface of the map service platform to upload and update metadata;

[0209] The format of metadata is json;

[0210] Using the map service platform to display the metadata on the itinerary map includes:

[0211] Design user interaction functions based on the needs of itinerary map display, and display itinerary maps on the vehicle terminal, iOS client, and Android terminal. The interactive function is used by users to customize the lighting effect of the arrival area on the map and customize the results of click events;

[0212] Dynamically create the number of threads in the thread pool according to the number of city lists, optimize the thread allocation for rendering tasks, and display the itinerary map;

[0213] Thread optimization allocation for rendering tasks includes:

[0214] When the number of threads in the thread pool does not reach the set value, a new thread is created in the thread pool for the input rendering task;

[0215] When the number of threads in the thread pool reaches the set value, the input rendering task is placed in the task queue and queued. If a thread in the thread pool is vacant, the input rendering task enters the thread in the order of the task queue for execution;

[0216] Rendering tasks include lighting up the map’s layers, querying city coordinate ranges, and matching map overlay colors;

[0217] The collection of vehicle data and platform data, as well as the upload and output of metadata, all comply with the MQTT protocol, using certificates and accounts for dual authentication;

[0218] Accessing the API interface includes the following operations:

[0219] Use the account and password to request user token information;

[0220] Add user token information;

[0221] After certificate verification;

[0222] The first trip map showcase includes:

[0223] Ask whether it supports using trip data for display;

[0224] Asks whether map rendering is supported.

[0225] Embodiment 4:

[0226] An embodiment of the present invention provides an electronic device including a memory and a processor.

[0227] A memory storing executable instructions;

[0228] The processor runs the executable instructions in the memory to implement the itinerary map display method.

[0229] The memory is used to store non-temporary computer-readable instructions. Specifically, the memory may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may, for example, include random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may, for example, include read-only memory (ROM), hard disk, flash memory, etc.

[0230] The processor may be a central processing unit (CPU) or other forms of processing units with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device to perform desired functions. In one embodiment of the present invention, the processor is used to run the computer-readable instructions stored in the memory.

[0231] Those skilled in the art should be able to understand that in order to solve the technical problem of how to obtain a good user experience, the present embodiment may also include well-known structures such as a communication bus and an interface, and these well-known structures should also be included in the protection scope of the present invention.

[0232] For detailed description of this embodiment, reference may be made to the corresponding descriptions in the aforementioned embodiments, which will not be repeated here.

[0233] Embodiment five:

[0234] An embodiment of the present invention provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, a method for displaying a trip map is implemented.

[0235] The computer-readable storage medium according to the embodiment of the present invention stores non-transitory computer-readable instructions, and when the non-transitory computer-readable instructions are executed by a processor, all or part of the steps of the above-mentioned methods of the embodiments of the present invention are executed.

[0236] The above-mentioned computer-readable storage media include, but are not limited to: optical storage media (e.g., CD-ROM and DVD), magneto-optical storage media (e.g., MO), magnetic storage media (e.g., magnetic tape or mobile hard disk), media with built-in rewritable non-volatile memory (e.g., memory card) and media with built-in ROM (e.g., ROM box).

[0237] The trip map display method proposed in the embodiment of the present invention obtains data from multiple data sources, parses vehicle data, filters data from other platforms to adapt metadata, and outputs the metadata in a unified manner, thereby solving the problems of high complexity and low performance of data processing from multiple data sources and improving usability and scalability.

[0238] The embodiments of the present invention have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments.

Claims

1. A method for displaying a trip map, characterized in that: include: Collect vehicle data and platform data of vehicle driving; The vehicle data and platform data are converted into metadata respectively and uploaded to the communication data platform; Outputting the metadata from the communication data platform to the map service platform according to time periods; The map service platform is used to display the metadata on a travel map.

2. The method according to claim 1, characterized in that The vehicle computer data is the trip details data recorded by the program in the vehicle computer; Converting the vehicle data into metadata and uploading it to the communication data platform includes: After the trip is completed, converting the vehicle computer data into vehicle computer metadata; When there is a network, uploading the vehicle machine metadata to the communication data platform; When there is no network, the vehicle machine metadata is stored in sequence, and after being acquired from the network, it is uploaded to the communication data platform in the order of storage.

3. The method according to claim 1, characterized in that The platform data includes Tbox platform data and cloud platform data; Converting the platform data into metadata and uploading it to the communication data platform includes: The cloud platform data is spliced ​​by the vehicle identification code and the timestamp at the end of the trip to form a data primary key; Converting the cloud platform data into cloud platform metadata; The cloud platform metadata is uploaded to the communication data platform, and the data primary key is used to determine whether there is duplicate data.

4. The method according to claim 2, characterized in that: Converting the vehicle computer data into vehicle computer metadata includes: Determining the type of the vehicle computer data; Writing a serialization protocol based on the type of the vehicle computer data; Using the serialization protocol, converting the vehicle computer data into binary format data; Add header information at the beginning of the binary format data to form vehicle metadata.

5. The method according to claim 3, characterized in that: Converting the cloud platform data into cloud platform metadata includes: The cloud platform data is integrated using data warehouse or data lake technology to obtain integrated data. Standardizing the integrated data to obtain cloud platform metadata; The standardization process includes format conversion, coordinate system unification and unit unification.

6. The method according to claim 1, characterized in that Outputting the metadata from the communication data platform to the map service platform according to the time period includes: Integrating the metadata into a map service platform according to time periods; Utilize the API interface of the map service platform to upload and update metadata; The metadata is in json format; Using the map service platform to display the metadata on a travel map includes: Design user interaction functions according to the needs of itinerary map display, and display itinerary maps on the vehicle terminal, iOS client and Android terminal. The interactive functions are used by users to customize the lighting effect of the arrival area on the map and customize the results of click events; Dynamically create the number of threads in the thread pool according to the number of city lists, optimize the thread allocation for rendering tasks, and display the itinerary map; Thread optimization allocation for rendering tasks includes: When the number of threads in the thread pool does not reach the set value, a new thread is created in the thread pool for the input rendering task; When the number of threads in the thread pool reaches the set value, the input rendering task is placed in the task queue and queued. If a thread in the thread pool is vacant, the input rendering task enters the thread in the order of the task queue for execution; The rendering tasks include lighting up the map layers, querying the city coordinate range and matching the map overlay colors.

7. The method according to claim 6, characterized in that The collection of vehicle data and platform data, as well as the upload and output of metadata, all comply with the MQTT protocol, using certificates and accounts for dual authentication; Accessing the API interface includes the following operations in sequence: Use the account and password to request user token information; Add user token information; After certificate verification; The first trip map showcase includes: Ask whether it supports using trip data for display; Asks whether map rendering is supported.

8. A trip map display device, characterized in that: include: The collection module is used to collect vehicle data and platform data during vehicle travel; A conversion module, used for converting the vehicle data and platform data into metadata respectively and uploading them to the communication data platform; An output module, used to output the metadata from the communication data platform to the map service platform according to time periods; A display module is used to display the metadata on a trip map using the map service platform.

9. An electronic device, characterized in that: The electronic device comprises: A memory storing executable instructions; A processor, wherein the processor runs the executable instructions in the memory to implement the itinerary map display method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the itinerary map display method described in any one of claims 1 to 7 is implemented.

Images