Track report synchronization method and apparatus, and device, storage medium and program product

Abstract

The present application relates to the technical field of computers. Provided are a track report synchronization method and apparatus, and a device, a storage medium and a program product. In the method, a vehicle generates a track report on the basis of operating parameters recorded during travel in a track scenario and then uploads same to a server, and the server sends the track report to a terminal device on the basis of a terminal identifier, thereby improving the efficiency of track report synchronization performed between the vehicle and the terminal device.

Description

Synchronization methods, devices, equipment, storage media, and program products for track reports.

[0001] This application claims priority to Chinese Patent Application No. 202411029707.5, filed on July 30, 2024, entitled “Synchronization Method, Apparatus, Device, Storage Medium and Program Product for Track Reports”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to computer technology, and more particularly to a method, apparatus, device, storage medium, and program product for synchronizing track reports. Background Technology

[0003] With the advancement of computer technology, motorsports have received increasing attention. After completing a track lap, timely review of track reports is crucial for improving driving skills.

[0004] Currently, track reports are mainly generated by smart hardware. After a user completes a track lap, they usually need to ensure a successful connection between the vehicle and the terminal device via Bluetooth, local area network, or the Internet to obtain and view the track report.

[0005] However, in existing technical solutions, the efficiency of synchronizing track reports between vehicles and terminal devices still faces certain challenges. Summary of the Invention

[0006] This application provides a method, apparatus, device, storage medium, and program product for synchronizing track reports, in order to solve the technical problem of low synchronization efficiency of track reports between vehicles and terminal devices.

[0007] Firstly, this application provides a method for synchronizing track reports, applied to a vehicle, the method comprising:

[0008] Record the vehicle's operating parameters during its operation on the racetrack.

[0009] A track report is generated based on the operating parameters recorded during the driving process in the described track scenario;

[0010] Upload the track report to the server.

[0011] In one possible design of the first aspect, uploading the track report to the server includes:

[0012] If the vehicle is currently logged into an account, the track report and the currently logged-in account identifier will be associated and uploaded to the server.

[0013] In one possible design of the first aspect, the method further includes: displaying a report upload control associated with the track report;

[0014] Uploading the track report to the server includes: upon receiving a trigger operation based on the report upload control, if the vehicle is currently logged into an account, associating the track report with the currently logged-in account identifier and uploading it to the server.

[0015] In one possible design of the first aspect, the method further includes:

[0016] A QR code associated with the report identifier of the track report is generated, and the vehicle's infotainment interface is controlled to display the QR code, which is used by external terminals to obtain the track report.

[0017] In one possible design of the first aspect, after the vehicle's infotainment interface displays the QR code, the method further includes:

[0018] Receive the report identifier and account identifier sent by the server;

[0019] The track report corresponding to the report identifier and the account identifier are associated and uploaded to the server.

[0020] In one possible design of the first aspect, generating a QR code associated with the report identifier of the track report includes: generating a QR code associated with the report identifier of the track report when the vehicle is not logged into an account.

[0021] In one possible design of the first aspect, the QR code is also associated with the vehicle identifier.

[0022] In one possible design of the first aspect, the method further includes: associating and uploading the track report and the vehicle identification to the server.

[0023] In one possible design of the first aspect, the method further includes:

[0024] The track report is stored locally on the vehicle.

[0025] Uploading the track report to the server includes:

[0026] Once the network signal quality meets the requirements, the track report will be uploaded to the server.

[0027] In one possible design of the first aspect, before uploading the track report to the server, the method further includes:

[0028] Check if the data synchronization function is enabled;

[0029] If the data synchronization function is enabled, the track report will be uploaded to the server;

[0030] If the data synchronization function is not enabled, a prompt message will be pushed to remind the user to enable the data synchronization function.

[0031] After the data synchronization function is detected to be enabled, the track report is uploaded to the server.

[0032] Secondly, this application provides a method for synchronizing track reports, applied to a server, the method comprising:

[0033] Receive track reports uploaded by vehicles, which are generated based on the operating parameters recorded by the vehicles during their driving in a track setting;

[0034] Determine the terminal identifier of the target terminal;

[0035] The track report is sent to the target terminal based on the terminal identifier.

[0036] In one possible design of the second aspect, receiving the track report uploaded by the vehicle includes: receiving the track report and account identifier uploaded by the vehicle.

[0037] Sending the track report to the target terminal based on the terminal identifier includes: determining the terminal identifier associated with the account identifier, and sending the track report associated with the account identifier to the target terminal corresponding to the terminal identifier.

[0038] In one possible design of the second aspect, the method further includes: receiving the terminal identifier and the account identifier associated with the target terminal.

[0039] In one possible design of the second aspect, the method further includes:

[0040] Receive terminal identifier, account identifier, report identifier, and vehicle identifier uploaded by the associated terminal device;

[0041] The report identifier and the account identifier are associated and sent to the vehicle based on the vehicle identifier, instructing the vehicle to associate and upload the track report corresponding to the report identifier and the account identifier;

[0042] Sending the track report to the target terminal based on the terminal identifier includes: receiving the track report uploaded by the vehicle and the account identifier;

[0043] Determine the terminal identifier associated with the account identifier, and send the track report associated with the account identifier to the target terminal corresponding to the terminal identifier.

[0044] In one possible design of the second aspect, the method further includes:

[0045] Receive the track report and vehicle identifier uploaded by the vehicle;

[0046] Based on the race time recorded in the track report, the vehicle identification, and the race information table, the user information of the driver of the vehicle during the race time is determined. The race information table is used to store the driver information of each vehicle for each time period.

[0047] The determination of the terminal identifier of the target terminal includes:

[0048] Based on the user information, the terminal identifier of the target terminal is determined.

[0049] Thirdly, this application provides a method for synchronizing track reports, applied to a terminal device, the method comprising:

[0050] Generate a report retrieval request, the report retrieval request including a terminal identifier and an account identifier corresponding to the terminal device;

[0051] Send the report retrieval request to the server so that the server can retrieve the track report associated with the account identifier;

[0052] Receive the track report associated with the account identifier sent by the server.

[0053] In one possible design of the third aspect, prior to the generation of the report retrieval request, the method further includes:

[0054] In response to a QR code scan, obtain vehicle identification and report identification;

[0055] The report retrieval request also includes the vehicle identifier and the report identifier, so that the server can retrieve the track report corresponding to the report identifier from the target vehicle based on the vehicle identifier.

[0056] Fourthly, this application provides a track report synchronization device, applied to a vehicle, comprising:

[0057] The recording module is used to record the vehicle's operating parameters during its operation in a track environment.

[0058] The generation module generates a track report based on the running parameters recorded during the driving process in the track scenario.

[0059] The upload module uploads the track report to the server.

[0060] Fifthly, this application provides a synchronization device for track reports, applied to a server, comprising:

[0061] The receiving module is used to receive track reports uploaded by the vehicle, which are generated based on the operating parameters recorded by the vehicle during its driving in the track scenario;

[0062] The processing module is used to determine the terminal identifier of the target terminal;

[0063] The sending module is used to send the track report to the target terminal according to the terminal identifier.

[0064] Sixthly, this application provides a synchronization device for track reports, applied to a terminal device, comprising:

[0065] The generation module is used to generate a report retrieval request, wherein the report retrieval request includes a terminal identifier and an account identifier corresponding to the terminal device;

[0066] The sending module is used to send the report retrieval request to the server so that the server can retrieve the track report associated with the account identifier;

[0067] A receiving module is used to receive the track report associated with the account identifier sent by the server.

[0068] In a seventh aspect, this application provides a vehicle, including: a vehicle-mounted system, a processor, and a memory communicatively connected to the processor;

[0069] The memory stores computer-executed instructions;

[0070] The processor executes computer execution instructions stored in the memory to implement the synchronization method for track reports as described in any of the first aspects.

[0071] Eighthly, this application provides a server, including: a transceiver, a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions;

[0072] The processor executes computer execution instructions stored in the memory to implement the synchronization method for track reports as described in any of the second aspects.

[0073] Ninthly, this application provides a terminal device, including: a transceiver, a processor, and a memory communicatively connected to the processor; the memory stores computer-executed instructions;

[0074] The processor executes computer execution instructions stored in the memory to implement the synchronization method for track reports as described in any of the third aspects.

[0075] In a tenth aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement a synchronization method for track reports as described in any one of the first to third aspects.

[0076] In one aspect, this application provides a computer program product, including a computer program that, when executed by a processor, is used to implement a synchronization method for track reports as described in any one of the first to third aspects.

[0077] In a twelfth aspect, this application provides a computer program, which, when executed by a processor, performs the synchronization method for track reports as described in any one of the first to third aspects.

[0078] In a thirteenth aspect, this application provides a chip including a memory and a processor, wherein the memory stores code and data, the memory is coupled to the processor, and the processor runs a program in the memory such that the chip is used to perform the synchronization method for track reports as described in any one of the first to third aspects above.

[0079] This application provides a method, apparatus, device, storage medium, and program product for synchronizing track reports, relating to the field of computer technology and primarily applied in track scenarios. Specifically, after a vehicle generates a track report based on its operating parameters during driving, the report is synchronously uploaded to a server. The server identifies the terminal through the track report and accurately synchronizes the report to the corresponding terminal device. This method not only improves the efficiency of track report generation, ensuring the accuracy and timeliness of the report, but also enhances the reliability of track report transmission by uploading it to the server. Simultaneously, the server can achieve precise synchronization based on the terminal identifier, ensuring that the track report is accurately sent to the designated terminal device, thereby achieving efficient and reliable synchronization of track reports between the vehicle and the terminal device, comprehensively improving the user experience. Attached Figure Description

[0080] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application:

[0081] Figure 1 is a schematic diagram of an application scenario for a track report synchronization method provided in this application;

[0082] Figure 2 is a flowchart illustrating an embodiment of a track report synchronization method provided in this application;

[0083] Figure 3 is a flowchart illustrating a second embodiment of a track report synchronization method provided in this application;

[0084] Figure 4 is a flowchart illustrating a third embodiment of a track report synchronization method provided in this application;

[0085] Figure 5 is a flowchart illustrating a fourth embodiment of a track report synchronization method provided in this application;

[0086] Figure 6 is a schematic diagram of one presentation method of the report upload control provided in this application;

[0087] Figure 7 is a schematic diagram of a second presentation method of the report upload control provided in this application;

[0088] Figure 8 is a schematic diagram of a third presentation method of the report upload control provided in this application;

[0089] Figure 9 is a flowchart illustrating a fifth embodiment of a track report synchronization method provided in this application;

[0090] Figure 10 is a flowchart illustrating a sixth embodiment of a track report synchronization method provided in this application;

[0091] Figure 11 is a flowchart illustrating a seventh embodiment of a track report synchronization method provided in this application;

[0092] Figure 12 is a flowchart illustrating an eighth embodiment of a track report synchronization method provided in this application;

[0093] Figure 13 is a flowchart illustrating a ninth embodiment of a track report synchronization method provided in this application;

[0094] Figure 14 is a flowchart illustrating a method for synchronizing track reports provided in this application;

[0095] Figure 15 is a schematic diagram of the structure of a synchronization device for track reports according to a first embodiment of the present application;

[0096] Figure 16 is a schematic diagram of a second embodiment of a track report synchronization device provided in this application;

[0097] Figure 17 is a schematic diagram of the structure of a third embodiment of a track report synchronization device provided in this application;

[0098] Figure 18 is a schematic diagram of the structure of a fourth embodiment of a track report synchronization device provided in this application;

[0099] Figure 19 is a schematic diagram of a fifth embodiment of a track report synchronization device provided in this application;

[0100] Figure 20 is a structural schematic diagram of a vehicle provided in the application;

[0101] Figure 21 is a schematic diagram of the structure of a server provided in the application;

[0102] Figure 22 is a structural schematic diagram of a terminal device provided in the application.

[0103] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0104] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0105] With the rapid development of computer technology, the field of motorsports has received increasing attention. After completing a track lap, promptly reviewing the track report is crucial for improving driving skills.

[0106] Currently, track reports are primarily generated by smart hardware. After completing a track lap, users typically need to establish a successful connection between the vehicle and the terminal device via Bluetooth, local area network, or the internet to access and view the track report. Taking Bluetooth as an example, users need to pair their terminal device with the smart hardware via a Bluetooth link. After successful pairing, they can select one or more track reports and click the "Send to Terminal" button to view the track report on their terminal device.

[0107] However, existing technologies face limitations in terms of space and time when synchronizing track reports between vehicles and terminal devices. Specifically, existing technologies are time-consuming to acquire track reports and are limited by transmission distance; the vehicle and terminal device must be located in a preset position, making remote push impossible. Furthermore, existing technologies cannot simultaneously send multiple track reports. These limitations not only affect the user experience but also reduce the efficiency of track report synchronization between vehicles and terminal devices to some extent.

[0108] To address the aforementioned issues, the inventors, during their research on track report synchronization methods between vehicles and terminal devices, discovered that existing technologies rely solely on the vehicle and terminal device for synchronization, which is susceptible to network signal interference. For example, Bluetooth connections are slow and prone to interference when transmitting large amounts of data, LAN connections require additional network configuration and equipment support, and internet connections depend on network stability and bandwidth, potentially suffering from network latency and data loss. Therefore, the inventors considered setting up a server between the vehicle and terminal device as a relay station for track reports. Specifically, through the server, track reports can be uploaded to a stable relay platform, and then the server accurately synchronizes and sends the track reports to the corresponding terminal device based on the terminal device's address information. This not only effectively alleviates the network signal instability problem caused by direct connection between the vehicle and terminal device but also improves the synchronization efficiency of track reports between the vehicle and terminal device, comprehensively ensuring synchronization strategies in different scenarios and enhancing user experience.

[0109] Figure 1 is a schematic diagram illustrating an application scenario of the track report synchronization method provided in this application. As shown in Figure 1, the application scenario of the track report synchronization method provided in this application is a track scenario. This track scenario includes a vehicle 100, a server 101, and a terminal device 102. The vehicle 100 is equipped with a vehicle-mounted infotainment system 1001. Although Figure 1 only shows one vehicle 100, one server 101, and one terminal device 102, it should be understood that there can be two or more vehicles 100, servers 101, and terminal devices 102.

[0110] The vehicle-mounted unit 1001 in the vehicle 100 is connected to the server 101 via a communication network, and the server 101 is connected to the terminal device 102 via a communication network.

[0111] The vehicle infotainment system 1001 refers to the driving information and entertainment host installed inside the vehicle 100. It is mainly used to generate track reports based on the operating parameters recorded by the vehicle during driving and upload them to the server 101 through the communication network.

[0112] Server 101 is mainly used to receive track reports uploaded by vehicle-mounted system 1001, determine the address of terminal device 102, and send track reports to terminal device 102 through communication network. Server 101 can be a cloud server, a local server, or other types of server. This application does not specify the specific form and type of server 101.

[0113] The terminal device 102 is mainly used to receive track reports from the server 101 for users to view. The terminal device 102 can be a smartphone, tablet, or smartwatch, etc. This application does not specifically limit the specific form and type of the terminal device 102.

[0114] It should be noted that the above scenario is only an example of an application scenario provided by the embodiments of this application. The embodiments of this application do not limit the actual form of the various devices included in the scenario. In the specific application of the solution, it can be set according to actual needs.

[0115] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0116] Figure 2 is a flowchart illustrating an embodiment of a track report synchronization method provided in this application. As shown in Figure 2, the process of this track report synchronization method may include:

[0117] S201: Records the vehicle's operating parameters during its operation in a track environment.

[0118] In this step, when the vehicle is driving on the track, the in-vehicle system deployed inside the vehicle will record various operating parameters of the vehicle in real time during the driving process on the track.

[0119] Specifically, the operating parameters include, but are not limited to, speed data, acceleration data, braking data, steering data, and trajectory data. Speed ​​data records the vehicle's maximum speed, minimum speed, average speed, and speed changes across different sections of the track. Acceleration data records the vehicle's acceleration changes at different points in time. Braking data records the number of braking maneuvers, braking force, and the duration and effect of each braking action. Steering data records the vehicle's turning angle, steering effort, and steering smoothness at each turn on the track. Trajectory data records the vehicle's trajectory on the track.

[0120] It is worth noting that the recorded operating parameters not only provide crucial data support for the generation of subsequent track reports, but can also be used for post-race replay and analysis, helping drivers gain a deeper understanding of the vehicle's performance on the track and thus develop more effective driving strategies.

[0121] S202: Generate a track report based on the running parameters recorded during the driving process in the track scenario.

[0122] In this step, a track report is generated based on the running parameters recorded in step S201.

[0123] Specifically, based on the operating parameters recorded by the vehicle during its driving on the track, the in-vehicle infotainment system will generate real-time track reports. These reports will record the user's driving data on the track, helping them improve their lap times.

[0124] In one possible implementation, during the driving process of a vehicle in a racetrack scenario, the vehicle's onboard infotainment system processes, cleans, synchronizes, and stores the recorded operating parameters. It then uses temporal and spatial analysis methods to perform in-depth analysis of these parameters, generating a detailed racetrack report that includes speed curves, acceleration distributions, driving trajectories, tire wear, and driving behavior. The racetrack report can be presented in various formats, including but not limited to electronic documents and multimedia.

[0125] It is important to note that the generation of a track report requires the vehicle to be in a track environment. Methods for determining whether the vehicle is in a track environment include, but are not limited to, geographical location comparison and whether track mode is enabled.

[0126] In one possible implementation, the vehicle's GPS system can acquire the vehicle's geographical location in real time. The in-vehicle system stores a track database containing pre-recorded geographical location data for major racetracks worldwide, including boundary coordinates, start and finish lines, and other detailed information. As the vehicle moves, the in-vehicle location determination system continuously compares the real-time acquired geographical location with the location in the track database. When the vehicle's location matches the geographical location of a particular track to a certain threshold, the location determination system can determine that the vehicle is within a track environment.

[0127] In another possible implementation, considering that vehicles are typically equipped with multiple driving modes, such as Normal, Sport, and Track modes, the driver can manually select Track mode. When Track mode is activated, the vehicle's infotainment system automatically adjusts various vehicle settings, such as engine output and steering sensitivity, to adapt to the demands of track driving. Therefore, the infotainment system can detect whether the vehicle is in a track environment by checking if Track mode is active. If Track mode is activated, the infotainment system assumes the vehicle is engaged in track driving.

[0128] To further determine whether a vehicle is in a racetrack setting, onboard cameras and sensors can be used to detect features of the surrounding environment, such as racetrack markings and guardrails, to confirm whether the vehicle is in a racetrack setting.

[0129] In another possible implementation, to avoid the track mode being mistakenly activated, the vehicle's infotainment system, upon detecting that track mode is enabled, further obtains the vehicle's real-time location via GPS and compares it with locations in the track database to confirm the location match. Simultaneously, it combines this information with track markings identified by the onboard camera to ultimately confirm whether the vehicle is indeed in a track environment.

[0130] By combining these methods, the vehicle's infotainment system can accurately determine whether the vehicle is in a track environment. Once confirmed, the system initiates a track report generation process, collecting and processing various operational parameters in real time to produce a detailed track report. This report not only helps the team and driver understand their race performance but also provides crucial information for subsequent vehicle tuning and driving strategies.

[0131] S203: Upload the track report to the server.

[0132] In this step, according to step S202, after the track report is generated, the vehicle uploads the track report to the server in a timely manner.

[0133] Specifically, track reports are uploaded to the server using preset upload methods. These preset upload methods include, but are not limited to, wireless networks and dedicated data transmission protocols. Furthermore, track reports can be encrypted before uploading to ensure their security and integrity.

[0134] Optionally, track reports can be uploaded in preset formats. These preset formats include, but are not limited to, text files, spreadsheets, charts, or comprehensive reports, to facilitate subsequent analysis and processing.

[0135] Using the above upload methods and formats, track reports can be transmitted to the server quickly and securely.

[0136] It is worth noting that servers can include various types, including but not limited to cloud servers, local servers, and dedicated track data analysis servers. These servers can be used individually or in combination; this application does not specifically limit the type and form of the servers.

[0137] Cloud servers offer high availability and scalability, making them suitable for large-scale track report data processing and storage. Local servers are suitable for environments requiring high control and security, ensuring that track report data is transmitted and stored only within the internal network. Dedicated track data analysis servers may be equipped with specific software and hardware to optimize the processing, analysis, and storage of track data.

[0138] S204: Receive track reports uploaded by vehicles. Track reports are generated based on the operating parameters recorded by the vehicles during their driving in track scenarios.

[0139] In this step, based on step S203, after the vehicle uploads the track report to the server, the server will receive the track report uploaded by the vehicle. This track report is generated based on the operating parameters recorded by the vehicle during its driving in the track environment.

[0140] Optionally, upon receiving a track report, the server will perform a series of operations to ensure its validity and accuracy. First, the server will parse and verify the received track report, checking its completeness and the correctness of the data format. Next, the server will determine the method for identifying the terminal identifier based on the presence of an account identifier in the track report, for subsequent report synchronization operations. Finally, the server will store the track report in a designated database or storage system to ensure its persistence and traceability. Simultaneously, the server may analyze and process the running parameters in the track report to generate more detailed reports.

[0141] S205: Determine the terminal identifier of the target terminal.

[0142] In this step, according to step S204, after receiving the track report uploaded by the vehicle, the server needs to further determine the terminal identifier of the target terminal to ensure that the track report can be accurately sent to the target terminal.

[0143] In one possible implementation, when the vehicle's infotainment system detects an account login, the content uploaded to the server includes not only the track report but also the account identifier generated when the user logs in. The account identifier is a unique identifier for the user account, used to ensure the traceability and ease of management of the track report. Specifically, when the vehicle's infotainment system detects an account login, it generates a corresponding account identifier based on the logged-in account and packages it along with the operating parameters into a track report, which is then uploaded to the server. Upon receiving the vehicle's track report, the server parses the account identifier and, based on a pre-stored mapping between account identifiers and terminal identifiers, determines the target terminal's identifier.

[0144] In another possible implementation, if the vehicle's infotainment system does not detect an account login, the content uploaded to the server will only include track reports. In this case, the terminal identifier can be determined in several ways, including but not limited to: QR code scanning, determination based on a race log, and triggering a button.

[0145] Specifically, the QR code scanning method refers to the terminal device scanning the QR code corresponding to the track report. The terminal device will then simultaneously upload the obtained report identifier, vehicle identifier, and terminal identifier to the server. The server will then determine the terminal identifier of the target terminal based on the terminal identifier uploaded by the terminal device.

[0146] The method of determining the target terminal based on the event record table refers to determining user information based on time, thereby obtaining the terminal identifier of the target terminal.

[0147] The triggering of the associated button method refers to the terminal device responding to the user's track report request by sending information containing the terminal identifier and account identifier to the server. The server can then determine the terminal identifier of the target terminal based on the terminal identifier sent by the terminal device.

[0148] Through these methods, the server can flexibly and accurately determine the terminal identifier of the target terminal, thereby ensuring that the track report can be sent to the target terminal in a timely and accurate manner, improving user experience and system reliability.

[0149] S206: Send the track report to the target terminal based on the terminal identifier.

[0150] In this step, according to step S205, after determining the terminal identifier of the target terminal, the server will accurately send the track report to the corresponding target terminal based on the terminal identifier.

[0151] Optionally, the server can verify the validity and permissions of the target terminal's identifier to ensure that only authorized terminal devices can receive track reports, thereby enhancing data transmission security. Simultaneously, the server can employ optimized transmission protocols or technologies to ensure that track reports are sent to the target terminal efficiently and promptly, minimizing transmission delays and data loss.

[0152] In one possible implementation, the server implements fault handling and tolerance mechanisms. For example, if an error or data loss is detected during transmission, the server will automatically retransmit or provide corresponding feedback to ensure the integrity and reliability of the track report. Furthermore, during transmission, the server records transmission logs or status information for subsequent review, providing strong support for the integrity and traceability of track report transmission.

[0153] These measures enable the server to effectively send track reports to the correct target terminals, providing users with accurate and timely track reports. This not only improves the user experience but also enhances the reliability and security of the transmission process.

[0154] Optionally, the server has the capability to send multiple track reports to different target terminals simultaneously. This means the server can process multiple track report transmission requests in parallel, significantly improving the efficiency of track report transmission. Through this parallel transmission mechanism, the server can simultaneously meet the needs of multiple users, ensuring that each user can obtain the latest track reports in a timely manner. This not only optimizes the user experience but also enhances the overall performance and reliability of the server, ensuring stable and efficient operation even under high concurrency.

[0155] The track report synchronization method provided in this application is mainly applied to track scenarios. Specifically, the track report is generated in real time based on the operating parameters recorded by the vehicle during driving, thereby effectively improving the efficiency of track report generation. After the track report is generated, it is promptly uploaded to the server, which then synchronizes the track report to the target terminal. The entire process is not limited by time and space, effectively improving the synchronization efficiency between the vehicle and the terminal device. In addition, the server has the ability to send the track report to multiple target terminals simultaneously, meeting the needs of multiple users to obtain track reports at the same time. Through this method, the track report can be transmitted to the target terminal efficiently and in a timely manner, ensuring that users can obtain the track report at any time and any place, thereby providing users with a more convenient and efficient service.

[0156] It is worth noting that, depending on the specific application scenario of the race track, there are multiple ways to synchronize race track reports from vehicles to the target terminal. The following will explain in detail how race track reports are synchronized to the target terminal under different circumstances.

[0157] Figure 3 is a flowchart illustrating a second embodiment of the track report synchronization method provided in this application, focusing on the scenario where an account login is detected before the vehicle generates a track report and the server pre-stores the mapping relationship between account identifiers and terminal identifiers. It is worth noting that this scenario is generally applicable to situations where the vehicle is driven by only one user. Specifically, as shown in Figure 3, the process of this track report synchronization method may include:

[0158] S301: If the vehicle is currently logged into an account, the track report and the currently logged-in account identifier will be associated and uploaded to the server.

[0159] In this step, if it is detected that the vehicle is currently logged into an account before uploading the track report to the server, the track report will be associated with the currently logged-in account identifier and then uploaded to the server.

[0160] It is worth noting that in order to enable the automatic synchronization of track reports to terminal devices, the data synchronization function in the vehicle needs to be enabled to ensure that the track reports can be uploaded to the server and synchronized to the terminal devices in a timely manner after they are generated.

[0161] Optionally, methods for determining whether a vehicle is currently logged into an account include, but are not limited to, account management systems, local storage, and online detection.

[0162] Specifically, the account management system is pre-deployed within the vehicle. This system includes modules such as a login page, authentication functions, and account status management. Once a user successfully logs in, the system records this information and continuously monitors the user's login status to ensure the vehicle can accurately identify the current user.

[0163] Local storage refers to the vehicle recording the current user login status in its local storage. This can be a simple flag (such as a boolean value) or a complex data structure to indicate whether a user is logged in. Through local storage, the vehicle can quickly and reliably retrieve the user's login status, reducing its reliance on network connectivity.

[0164] Network-based detection checks the login status on a remote server via a network connection. For example, a vehicle can send a verification request or token verification to the server to confirm whether the user is logged in. Upon receiving the request, the server verifies the user information based on its storage and returns the corresponding login status. This method not only ensures the real-time nature of the login status but also provides enhanced security, preventing unauthorized access.

[0165] Through these various methods, the vehicle can flexibly and accurately determine whether it is currently logged into an account, thus providing a reliable foundation for subsequent track report uploads and synchronization operations.

[0166] When uploading track reports and account identifiers to the server, they are typically packaged into data packets of a specific format and protected by secure transmission protocols and encryption mechanisms to ensure the privacy and integrity of the data.

[0167] Optionally, there are three ways to upload track reports to the server by associating them with the currently logged-in account ID.

[0168] The first method involves encapsulating the track report and the currently logged-in account identifier into a data packet of a specific format before uploading it to the server. This method ensures that the track report and account identifier remain consistent throughout the transmission process, facilitating server parsing and processing.

[0169] The second approach involves encapsulating the track report and the currently logged-in account identifier into separate data packets of a specific format, and then uploading them to the server simultaneously. This method allows for more flexible data processing and transmission. Upon receiving these two data packets, the server matches the track report with the account identifier based on the association information, thereby achieving effective data integration.

[0170] The third approach involves encapsulating the track report and the currently logged-in account ID into separate data packets of a specific format and uploading them to the server at different times. This method offers greater flexibility, allowing track reports and account IDs to be uploaded at different points in time. Upon receiving these data packets, the server matches the track report with the account ID according to pre-defined association rules, ensuring data accuracy and integrity. For example, each data packet contains the same identification information, ensuring the server can accurately identify and process these separately uploaded track reports and account IDs. When the server receives separately uploaded track reports and account IDs, it associates them by parsing the identification information in each data packet. This ensures that track reports and account IDs with the same identification information are correctly associated, supporting subsequent data processing and analysis.

[0171] Based on any of the above methods, the server will parse and verify the received data packet to ensure the integrity and relevance of the track report and account identifier.

[0172] S302: Receive track reports and account identifiers uploaded by the vehicle.

[0173] In this step, according to step S301, after the vehicle uploads the track report and the currently logged-in account identifier to the server, the server parses and verifies the data after receiving the track report and account identifier uploaded by the vehicle.

[0174] Specifically, during the parsing process, the server extracts the running parameters and account identification information from the track report, performs format checks and data verification to ensure the integrity and accuracy of the track report and account identification.

[0175] S303: Determine the terminal identifier associated with the account identifier and send the track report associated with the account identifier to the target terminal corresponding to the terminal identifier.

[0176] In this step, according to step S302, after receiving the track report and account identifier uploaded by the vehicle, the server will determine the terminal identifier based on the account identifier and then send the track report to the target terminal.

[0177] In one possible implementation, the server pre-stores a mapping relationship between account identifiers and terminal identifiers. When the server receives a track report and account identifier uploaded by a vehicle, it determines the terminal identifier corresponding to the account identifier based on the pre-stored mapping relationship and sends the track report associated with that account identifier to the corresponding target terminal.

[0178] Specifically, the server first parses the received data packets, extracting the track report and account identifier. Next, the server searches its internally stored mapping table to find the terminal identifier that matches the account identifier. In this way, the server can accurately identify the target terminal that needs to receive the track report.

[0179] Once the target terminal is identified, the server will efficiently and promptly send the track report to the target terminal according to the preset transmission protocol and synchronization strategy. This process may include verifying the validity and permissions of the target terminal to ensure the security and reliability of data transmission.

[0180] Through this mapping relationship, the server can flexibly and accurately synchronize track reports to the corresponding target terminals, ensuring that users can obtain the latest track information in a timely manner, thereby improving the user experience.

[0181] S304: Receive track reports associated with the account identifier sent by the server.

[0182] In this step, according to step S303, after the server sends the track report to the target terminal, the target terminal will receive the track report associated with the account identifier sent by the server.

[0183] Specifically, after the server identifies the target terminal and successfully sends the track report, the target terminal will perform a data receiving operation.

[0184] In one possible implementation, the target terminal first monitors the transmission signal from the server and begins receiving data packets according to a preset communication protocol. The target terminal parses the received data packets to extract the track report associated with the account identifier. During the reception process, the target terminal verifies the data integrity and accuracy to ensure that no data loss or corruption occurred during transmission. After parsing, the target terminal stores the track report in its local storage system so that the user can access and view it at any time.

[0185] The track report synchronization method provided in this application focuses on the scenario where an account login is detected before the vehicle generates the track report, and the server pre-stores the mapping relationship between account identifiers and terminal identifiers. Specifically, based on the account identifier uploaded by the vehicle, the server can accurately and promptly determine the terminal identifier and efficiently synchronize the track report to the target terminal. Through this method, the target terminal can accurately and efficiently receive the track report sent by the server, providing users with timely and reliable track information, thereby improving the synchronization efficiency of track reports between vehicles and terminal devices and enhancing the user experience.

[0186] Figure 4 is a flowchart illustrating a third embodiment of a track report synchronization method provided in this application, focusing on the scenario where an account login is detected before the vehicle generates a track report, but the server has not pre-stored the mapping relationship between the account identifier and the terminal identifier. As shown in Figure 4, the process of this track report synchronization method may include:

[0187] S401: Generate a report retrieval request. The report retrieval request includes the terminal identifier and account identifier corresponding to the terminal device.

[0188] In this step, after receiving the track report and account identifier uploaded by the vehicle, the next step for the server is to determine the target terminal's identifier. However, unlike the track report synchronization method shown in Figure 3, the server does not pre-store the mapping relationship between account identifiers and terminal identifiers.

[0189] In one possible implementation, based on the above situation, the server can wait for the terminal device to send a report retrieval request in order to achieve accurate delivery of the track report.

[0190] Specifically, terminal devices are not limited by time and space, and can generate report retrieval requests anytime and anywhere based on user needs.

[0191] In one possible implementation, the report retrieval request includes a terminal identifier and an account identifier corresponding to the terminal device. Specifically, when a user initiates a report retrieval request on the terminal device, the terminal device automatically generates a request data packet. This data packet contains the terminal identifier and the account identifier so that the server can identify the source and target user of the request. The terminal identifier is typically a unique device identifier, such as the terminal device's media access control address or universally unique identifier, while the account identifier is a unique identifier registered by the user in the track-related software, such as a username or user ID.

[0192] S402: Sends a report retrieval request to the server so that the server can retrieve the track report associated with the account identifier.

[0193] In this step, according to step S401, after generating a report retrieval request, the terminal device will send the report retrieval request to the server via a network connection so that the server can retrieve the track report associated with the account identifier.

[0194] It is worth noting that the account identifier and terminal identifier in the report retrieval request can be encapsulated into separate data packets and uploaded to the server at the same time or at different times, or the account identifier and terminal identifier can be encapsulated into a single data packet and uploaded to the server together.

[0195] In one possible implementation, the terminal device first encapsulates the account identifier and terminal identifier in a data packet, typically in JSON or XML format. Then, via a wireless network, cellular network, or other available network connection, the terminal device establishes a communication channel with the server. Next, the terminal device sends the encapsulated data packet, containing necessary information such as the terminal identifier and account identifier, to the server's designated interface address using a preset network protocol. Upon receiving the request, the server returns an acknowledgment response, indicating that the request has been successfully received. In this way, the terminal device can efficiently and reliably send report retrieval requests to the server, ensuring that the server can promptly obtain and send the track report associated with the account identifier, meeting user needs.

[0196] S403: Receive the terminal identifier and account identifier uploaded by the target terminal.

[0197] In this step, according to step S402, after the terminal device sends the report acquisition request to the server, the server will receive the terminal identifier and account identifier uploaded by the target terminal, thereby providing strong support for the accurate delivery of the track report.

[0198] S404: Determine the terminal identifier associated with the account identifier and send the track report associated with the account identifier to the target terminal corresponding to the terminal identifier.

[0199] In this step, according to step S403, after receiving the terminal identifier and account identifier uploaded by the target terminal, the server determines the terminal identifier corresponding to the account identifier associated with the track report.

[0200] Specifically, after receiving a report retrieval request, the server parses the request data packet and extracts the terminal identifier and account identifier. Next, the server searches for and matches previously uploaded track reports based on the account identifier, associating these reports with the terminal identifier in the request. In this way, the server can accurately send track reports to the corresponding terminal devices.

[0201] This method ensures that the server can transmit track reports in a timely and accurate manner according to the requests of the terminal devices, thus meeting the user's needs.

[0202] The track report synchronization method provided in this application focuses on the scenario where an account is logged in and the server has not pre-stored the mapping relationship between account identifiers and terminal identifiers before the vehicle generates the track report. Specifically, based on the account identifiers uploaded by the vehicle and terminal device, the server can accurately and promptly determine the terminal identifier and efficiently synchronize the track report to the target terminal. This method enhances the server's flexibility and real-time performance, improves the accuracy of track report transmission and user experience, and reduces the server's storage burden.

[0203] Figure 5 is a flowchart illustrating a fourth embodiment of a track report synchronization method provided in this application, focusing on the scenario where an account login is detected after the vehicle generates a track report, and the server pre-stores the mapping relationship between account identifiers and terminal identifiers. It is worth noting that this scenario is generally applicable to situations where a vehicle is driven by multiple users. Specifically, as shown in Figure 5, the process of this track report synchronization method may include:

[0204] S501: Displays the report upload control associated with the track report.

[0205] In this step, when it is determined that a car is being driven by multiple people in turns, the track report data synchronization function will be temporarily disabled regardless of whether an account is currently logged into the vehicle. The track report data synchronization function will be re-enabled when it is determined that the track report needs to be synchronized to the terminal device.

[0206] Specifically, once all track reports have been generated, the vehicle's infotainment system will display a report upload control associated with each track report. This control is designed to remind users to upload the generated track reports, ensuring all reports are properly stored. This feature not only improves the user experience but also ensures the integrity of the track reports, enabling effective management and utilization even in multi-user driving scenarios.

[0207] Optionally, the report upload control can be presented in various ways, including but not limited to the following: each track report has its own independent report upload control, only one comprehensive report upload control is displayed, or both of the above methods are present. These different presentation methods are designed to provide flexibility, allowing users to choose the most suitable upload method according to their needs and preferences. Regardless of the method chosen, the track report upload process is ensured to be simple and efficient, further enhancing the user experience.

[0208] Figure 6 is a schematic diagram of one presentation method of the report upload control provided in this application. As shown in Figure 6, a report upload control is set after each track report. Specifically, track report 600 corresponds to report upload control 6001, track report 601 corresponds to report upload control 6011, track report 602 corresponds to report upload control 6021, and track report 603 corresponds to report upload control 6031. When any report upload control is triggered, the track report associated with that report upload control will be uploaded to the server.

[0209] Figure 7 is a schematic diagram of a second presentation method of the report upload control provided in this application. As shown in Figure 7, there is only one comprehensive report upload control after all track reports. Specifically, track reports 700, 701, 702, and 703 do not have a report upload button; instead, there is only one comprehensive report upload control 704. When one or more track reports are selected, the comprehensive report upload control 704 is triggered, and the selected track reports will be uploaded to the server synchronously.

[0210] Figure 8 is a schematic diagram of a third method for presenting the report upload control provided in this application. As shown in Figure 8, each track report is followed by a report upload control, and a comprehensive report upload control is also provided. Specifically, track report 800 corresponds to report upload control 8001, track report 801 corresponds to report upload control 8011, track report 802 corresponds to report upload control 8021, track report 803 corresponds to report upload control 8031, and a comprehensive report upload control 804 exists. Under this setting, users can choose the appropriate track report upload method according to their needs.

[0211] When each track report is assigned a separate report upload control, users can upload specific track reports one by one, thus managing and controlling the upload process more precisely. However, selecting a comprehensive report upload control simplifies the operation, allowing users to upload all selected track reports with a single click.

[0212] S502: Upon receiving a trigger operation based on the report upload control, if the vehicle is currently logged into an account, the track report and the currently logged-in account identifier will be associated and uploaded to the server.

[0213] In this step, according to step S501, when the vehicle receives the trigger operation based on the report upload control, it will determine the method of synchronizing the track report to the target terminal based on whether a login account exists.

[0214] Specifically, once all track reports have been generated, if the vehicle detects an account login and receives a trigger action based on the report upload control, the vehicle will associate the track report with the currently logged-in account identifier and upload it to the server. This process ensures the association between the track report and the user account, thereby facilitating subsequent track report management and analysis.

[0215] In one possible implementation, if the vehicle does not detect an account login, it will prompt the user to log in first, or after a preset time, the track report and vehicle identification will be uploaded to the server simultaneously. This can be referred to in steps S1101 to S1104, which will not be repeated here.

[0216] Once the server receives the track report and account identifier uploaded by the vehicle, it determines the terminal identifier corresponding to the account identifier based on the pre-stored mapping relationship between account identifiers and terminal identifiers, and sends the track report associated with that account identifier to the corresponding target terminal. The specific implementation process can be found in steps S303 to S304, and will not be elaborated upon here.

[0217] The track report synchronization method provided in this application is primarily applicable to scenarios where a vehicle is driven by multiple users taking turns. Specifically, the vehicle displays a report upload control, allowing users to select track reports to upload as needed. This method can flexibly handle the complexities of multi-user driving, ensuring that each user's track report is accurately recorded and managed. Furthermore, based on the provided report upload control, users can independently decide when and which track reports need to be uploaded, thereby improving the flexibility of track report management and user experience. In addition, this method effectively avoids potential track report confusion or conflicts caused by automatic synchronization, ensuring the accuracy and completeness of the track reports.

[0218] Based on the embodiment shown in Figure 8, in one possible implementation, if the server does not pre-store the mapping relationship between account identifier and terminal identifier, the method for the server to determine the terminal identifier after receiving the track report and account identifier uploaded by the vehicle is to wait for the terminal device to send a report acquisition request containing the terminal identifier and account identifier. The specific implementation of this process can be referred to steps S401 to S403, which will not be repeated here.

[0219] This embodiment provides a track report synchronization method, focusing on the scenario where, after a vehicle generates a track report, an account login is detected, but the server has not pre-stored the mapping relationship between account identifiers and terminal identifiers. In this case, the vehicle provides a report upload control for the user to select the track report to upload. Simultaneously, the terminal device sends a report retrieval request containing both the account identifier and the terminal identifier to the server. This method flexibly handles situations where the server has not pre-stored the mapping relationship between account identifiers and terminal identifiers, ensuring the smooth upload and synchronization process of the track report. Furthermore, the terminal device sending a report retrieval request containing both the account identifier and the terminal identifier to the server ensures the accurate association between the track report and the terminal identifier, avoiding track report confusion.

[0220] Figure 9 is a flowchart illustrating a fifth embodiment of a track report synchronization method provided in this application, focusing on the scenario where the vehicle is not logged in with an account and the server pre-stores the mapping relationship between account identifiers and terminal identifiers. As shown in Figure 9, the process of this track report synchronization method may include:

[0221] S901: Generates a QR code associated with the report identifier of the track report and controls the vehicle's infotainment interface to display the QR code, which is used by external terminals to obtain the track report.

[0222] In this step, once the vehicle generates a track report and no account login is detected, the vehicle's infotainment system will display a QR code corresponding to each track report. This QR code is associated with both the track report's identifier and the vehicle's identifier, and is used by external terminals to access the track report.

[0223] Specifically, after the vehicle generates a track report, it assigns a unique report identifier to each report. This report identifier is a unique identifier for the track report, used to ensure the accuracy and uniqueness of the report. Simultaneously, the vehicle also generates a QR code associated with the report identifier, which is displayed on the vehicle's infotainment system. Users can scan this QR code using an external device, which will then retrieve the report identifier.

[0224] It is worth noting that displaying the QR code is mainly for situations where users do not want to log in to their account to access their vehicle.

[0225] S902: In response to a QR code scanning operation, obtain vehicle identification and report identification.

[0226] In this step, according to step S901, when the vehicle's infotainment interface displays the QR code corresponding to each track report, the vehicle will continuously monitor whether an external terminal is scanning any of the QR codes.

[0227] If an external terminal scans a QR code, the vehicle will immediately respond to the scan and send the vehicle identifier and report identifier associated with the QR code to the terminal device that performed the scan. The vehicle identifier is a unique identifier used to identify a specific vehicle. It can take various forms, including but not limited to vehicle identification numbers, license plate numbers, internal system identifiers, or identifiers of specific hardware devices. The vehicle identifier ensures that the server can subsequently identify which vehicle generated the track report.

[0228] These identifiers will be used in subsequent data transmission and track report acquisition processes to ensure that external terminals can accurately obtain the corresponding track reports.

[0229] S903: Generate a report retrieval request. The report retrieval request includes the account identifier, vehicle identifier, and report identifier.

[0230] In this step, according to step S902, after the terminal device obtains the vehicle identifier and the report identifier, the terminal device will generate a report acquisition request containing the account identifier, the vehicle identifier, and the report identifier.

[0231] The account identifier is used to identify the user account currently logged into the terminal device, ensuring the accurate association between the track report and the account identifier. The vehicle identifier is used to identify the specific vehicle that generated the track report, ensuring the accuracy and uniqueness of the track report. The report identifier is used to identify the specific track report, ensuring that the terminal device can accurately obtain the required report data.

[0232] It is worth noting that, in this case, the terminal identifier is not included in the report retrieval request. The acquisition of the terminal identifier can be found in step S303, and will not be repeated here.

[0233] S904: Sends a report retrieval request to the server so that the server can retrieve the track report associated with the account identifier.

[0234] In this step, according to step S903, after generating the report retrieval request, the terminal device will send a report retrieval request to the server so that the server can retrieve the track report associated with the account identifier.

[0235] It is worth noting that the account identifier, vehicle identifier, and report identifier information in the report retrieval request may be sent to the server in ways including, but not limited to, associated uploads and separate uploads. This application does not impose specific restrictions on this.

[0236] S905: Receives account identifiers, report identifiers, and vehicle identifiers uploaded by the terminal device.

[0237] In this step, according to step S904, after the terminal device sends a report retrieval request to the server, the server will receive the report retrieval request including the account identifier, report identifier, and vehicle identifier.

[0238] In one possible implementation, upon receiving a report retrieval request, the server typically performs a series of verification and authentication steps. First, the server verifies the legitimacy of the account identifier to ensure the request originates from a valid and registered user account. Next, the server checks the report identifier and vehicle identifier to ensure these identifiers are valid and match records in the server's database.

[0239] S906: Associate the report identifier and account identifier with the vehicle identifier and send them to the vehicle to instruct the vehicle to associate and upload the track report corresponding to the report identifier and the account identifier.

[0240] In this step, according to step S905, when the server receives a report retrieval request containing an account identifier, a report identifier, and a vehicle identifier, the server will associate the report identifier and the account identifier with the vehicle identifier and send them to the vehicle, so as to instruct the vehicle to associate and upload the track report corresponding to the report identifier and the account identifier.

[0241] Specifically, after the server parses and verifies the various identifiers in the report retrieval request, it locates the specific vehicle based on the vehicle identifier in the request. The server then generates an instruction containing the report identifier and account identifier and sends this instruction to the corresponding vehicle.

[0242] In the instructions, the report identifier explicitly specifies the track report to be uploaded, while the account identifier indicates which user account the track report should be associated with. The server uses this method to ensure that vehicles can accurately identify and process track report upload requests.

[0243] S907: Receive the report identifier and account identifier sent by the server.

[0244] In this step, according to step S906, after the server associates the report identifier and account identifier with the vehicle identifier and sends them to the vehicle, the designated vehicle will receive the report identifier and account identifier sent by the server.

[0245] In one possible implementation, after receiving the report identifier and account identifier associated with the server, the vehicle will perform a verification process to ensure the accuracy, security, and integrity of the data. Specifically, the vehicle first verifies the existence of the corresponding track report in its local storage based on the report identifier and checks the integrity of the data. Next, the vehicle verifies the legitimacy and permissions of the account identifier to ensure that the account has the right to access and upload the corresponding track report. After completing all verification steps, the vehicle prepares and encrypts the track report data packet to ensure the security of the data during transmission, and finally uploads it to the server.

[0246] S908: Associate the track report and account identifier corresponding to the report identifier and upload them to the server.

[0247] In this step, according to step S907, after the vehicle receives the report identifier and account identifier sent by the server, the vehicle will locate the specific track report stored locally based on the report identifier and associate the track report with the account identifier to ensure that the uploaded track report can be correctly bound to the target account.

[0248] In one possible implementation, the process of a vehicle uploading track reports and account identifiers includes: First, the vehicle integrates the track report data and account identifier into a single data packet and encrypts the packet. Next, the vehicle establishes a secure communication connection with the server, through which it sends the encrypted data packet. Upon receiving the data packet, the server decrypts and verifies it to ensure the integrity and legitimacy of the data. Finally, the server sends a confirmation message to the vehicle, indicating successful data upload. Through these steps, the vehicle can ensure the accurate uploading of track reports and the correct association of account identifiers, thus ensuring the security and integrity of the track reports.

[0249] When the server has a pre-stored mapping relationship between account identifiers and terminal identifiers, the method for obtaining the terminal identifier is to determine the terminal identifier corresponding to the account identifier in the report retrieval request based on the mapping relationship, thereby accurately synchronizing the track report to the target terminal corresponding to the terminal identifier. The specific implementation process can be found in steps S303 to S304, and will not be repeated here.

[0250] The track report synchronization method provided in this application focuses on the scenario where the vehicle is not logged into an account and the server pre-stores the mapping relationship between account identifiers and terminal identifiers. Specifically, by displaying a QR code, users can easily obtain the track report using an external terminal, thus avoiding the problem of track report synchronization failure due to not being logged into an account. Simultaneously, the QR code is associated with the track report's identifier, ensuring the accuracy and uniqueness of the track report. Furthermore, this method improves the convenience and efficiency of track report transmission, enabling users to quickly obtain and view track reports.

[0251] Based on the embodiment shown in Figure 9, in one possible implementation, if the server does not pre-store the mapping relationship between account identifier and terminal identifier, the method for the server to determine the terminal identifier after receiving the track report and account identifier uploaded by the vehicle is to wait for the terminal device to send a report acquisition request containing the terminal identifier and account identifier. The specific implementation of this process can be referred to steps S401 to S403, which will not be repeated here.

[0252] The track report synchronization method provided in this embodiment focuses on the scenario where the vehicle is not logged into an account and the server has not pre-stored the mapping relationship between account identifiers and terminal identifiers. In this situation, the vehicle generates and displays a QR code for external terminal devices to scan. This method eliminates the need for the vehicle to pre-login to an account or for the server to pre-store the mapping relationship between account identifiers and terminal identifiers, thus simplifying the operation process and improving flexibility and user experience. Users only need to scan the QR code with their terminal devices to complete the track report retrieval request, avoiding the cumbersome account login steps.

[0253] Figure 10 is a flowchart illustrating a sixth embodiment of a track report synchronization method provided in this application, focusing on the scenario where the vehicle is not logged in and the server has not pre-stored the mapping relationship between account identifiers and terminal identifiers. It is worth noting that the process shown in Figure 10 differs from that shown in Figure 9 in that the report retrieval request uploaded by the terminal device includes the terminal identifier in addition to the account identifier, report identifier, and vehicle identifier. Specifically, as shown in Figure 10, the process of this track report synchronization method may include:

[0254] S1001: Generate a report retrieval request. The report retrieval request includes the terminal identifier, account identifier, vehicle identifier, and report identifier corresponding to the terminal device.

[0255] In this step, after the terminal device responds to the scanning operation of the QR code and obtains the vehicle identifier and report identifier, the terminal device will combine the account identifier and terminal identifier to generate a report retrieval request.

[0256] The terminal identifier is usually a unique device identifier, such as the media access control address or universally unique identifier of the terminal device. This terminal identifier can uniquely identify the target terminal, thereby ensuring that subsequent track reports can be sent to the correct terminal device accurately.

[0257] S1002: Send a report retrieval request to the server so that the server can retrieve the track report associated with the account identifier.

[0258] In this step, based on step S1001, the terminal device generates a report retrieval request including a terminal identifier, an account identifier, a vehicle identifier, and a report identifier. After generating the report retrieval request, the terminal device sends the report retrieval request to the server via a secure communication protocol.

[0259] In one possible implementation, to ensure data security during transmission, the terminal device encrypts the report retrieval request to prevent it from being intercepted or tampered with during transmission.

[0260] During the report retrieval request transmission process, the terminal device continuously monitors the network connection status to ensure that the request can be sent successfully. If the network connection is interrupted or unstable, the terminal device will automatically retry sending the report retrieval request until it is confirmed that the report retrieval request has been successfully sent to the server.

[0261] S1003: Receive terminal identifier, account identifier, report identifier, and vehicle identifier uploaded by the associated terminal device.

[0262] In this step, after the terminal device sends a report acquisition request to the server based on step S1002, the server will receive the terminal identifier, account identifier, report identifier, and vehicle identifier uploaded by the terminal device.

[0263] The process of obtaining track reports based on vehicle identifiers, report identifiers, and account identifiers can be found in steps S907 to S908, and will not be repeated here.

[0264] After the server obtains the track report corresponding to the report identifier, it determines the target terminal device based on the terminal identifier contained in the report retrieval request. In this way, the server can accurately identify the specific terminal device requesting the track report. Subsequently, the server sends the track report to the target terminal device via a secure communication protocol.

[0265] In one possible implementation, the server encrypts the track report data during transmission to ensure the confidentiality and integrity of the data and prevent it from being intercepted or tampered with.

[0266] After receiving the track report, the terminal device will first decrypt and verify it to ensure the integrity and accuracy of the data. Once verification is successful, the terminal device will parse and display the track report, allowing users to view detailed track report information.

[0267] In this way, the server can accurately send track reports to the target terminal device, ensuring the security and reliability of data transmission, while also ensuring that users can obtain and view the track reports they need in a timely manner.

[0268] The track report synchronization method provided in this application focuses on the scenario where the vehicle is not logged into an account and the server does not pre-store the mapping relationship between account identifiers and terminal identifiers. In this case, the vehicle provides a QR code for the terminal device to scan, thereby simplifying user operation and improving convenience. Simultaneously, the terminal device sends a report retrieval request containing the vehicle identifier, report identifier, account identifier, and terminal identifier to the server in one go, thereby reducing communication overhead and improving transmission efficiency. Furthermore, the server accurately retrieves the track report based on the report retrieval request and determines the target terminal device based on the terminal identifier, accurately sending the track report to that terminal to ensure the accuracy and reliability of data transmission. Through this method, even without pre-stored account identifier and terminal identifier mapping relationships, accurate synchronization and transmission of track reports can still be achieved.

[0269] Figure 11 is a flowchart illustrating a seventh embodiment of a track report synchronization method provided in this application, focusing on how to synchronize the track report to the target terminal based on the race information table. It is worth noting that this scenario primarily applies to situations where the user is not logged into their account and leaves the venue directly after completing the race. Specifically, as shown in Figure 11, the process of this track report synchronization method may include:

[0270] S1101: Associate and upload track reports and vehicle identification information to the server.

[0271] This step primarily considers scenarios where the user does not log into their account throughout the competition and leaves the venue directly after finishing the competition.

[0272] In this scenario, to ensure that the track report can be synchronized to the target terminal in a timely manner, the vehicle will first associate the track report with the vehicle identifier and then upload this information to the server in real time via the network.

[0273] S1102: Receive track reports and vehicle identifiers uploaded by the vehicle association.

[0274] In this step, based on step S1101, the server promptly receives the track report and vehicle identification uploaded by the vehicle association.

[0275] Specifically, after receiving the track report and vehicle identification uploaded by the vehicle association, the server will immediately store and process them to ensure that the association between the track report and the vehicle identification is accurately recorded.

[0276] This real-time reception and storage mechanism not only ensures the timeliness and integrity of the data, but also lays the foundation for subsequent track report retrieval and transmission. In this way, even if a user leaves the venue without logging into their account after the race, the server can still effectively manage and store track report information.

[0277] S1103: Based on the race time, vehicle identification, and race information table recorded in the track report, determine the user information of the vehicle driven during the race time. The race information table is used to store the driver information of each vehicle for each time period.

[0278] In this step, according to step S1102, after receiving the vehicle identifier and track report uploaded by the vehicle association, the server will perform further data processing.

[0279] Specifically, the server parses the race time information in the track report and combines it with vehicle identifiers to locate the specific race record. The server accesses the race information table, which stores information about the drivers of each vehicle for each time period, recording detailed information about all races, including the time of each race, the participating vehicles, and the corresponding user information.

[0280] By matching the race times in the track report with records in the race information table, the server can determine the user information of the driver of the vehicle during a specific race period. Specifically, the server retrieves records in the race information table corresponding to the vehicle identifier and race time to obtain the user information for that time period. This process includes cross-validation and matching of multiple data sources to ensure the accuracy of the obtained user information. Once the user information is determined, the server associates and stores this information with the track report, providing a basis for subsequent report retrieval and transmission.

[0281] S1104: Determine the terminal identifier of the target terminal based on the user information.

[0282] In this step, according to step S1103, after the server determines the user information based on the event information table, it will further process the data to determine the terminal identifier of the target terminal.

[0283] Specifically, the server extracts detailed records related to user information from the event information table. These records include, but are not limited to, user account information and contact information.

[0284] The server uses this user information to query the user database to find the terminal device associated with that user. The user database typically stores each user's account information and corresponding terminal identifier. By matching user information, the server can accurately locate the terminal device used by the user and extract the corresponding terminal identifier.

[0285] Optionally, the user database records the user's account identifier, registered mobile phone number, email address, and terminal identifier of the bound terminal device, etc.

[0286] S206: Send the track report to the target terminal based on the terminal identifier.

[0287] In this step, according to step S1104, after the server determines the terminal identifier based on the user information, it associates the terminal identifier with the previously obtained track report and sends the track report to the target terminal device, thereby ensuring that the track report can be accurately transmitted to the user's terminal device.

[0288] The track report synchronization method provided in this application focuses on how to synchronize track reports to target terminals based on race information tables. Specifically, the server accurately identifies the user information of the driving vehicle using race time, race information tables, and vehicle identifiers, ensuring that the track report is correctly transmitted to the corresponding terminal device. This method effectively manages and processes track report data, ensuring that users can obtain and view detailed information in a timely manner. Even if the user does not log in to their account and leaves the venue directly after the race, the track report can still be successfully transmitted to the user's terminal, thereby improving the user experience.

[0289] Figure 12 is a flowchart illustrating an eighth embodiment of a track report synchronization method provided in this application. As shown in Figure 12, the process of the track report synchronization method may include:

[0290] S1201: Check if the data synchronization function is enabled.

[0291] In this step, enabling the data synchronization function is crucial for synchronizing track reports between the vehicle and the terminal device when the vehicle is in a track environment. This data synchronization function refers to the vehicle automatically synchronizing track report data to the terminal device.

[0292] Specifically, enabling the data synchronization function ensures that track reports can be transmitted from the vehicle to the terminal device in real time and accurately, thereby providing users with timely track data analysis and feedback.

[0293] In one possible implementation, the vehicle initiates the data synchronization function through its built-in system settings or user interface.

[0294] S1202: If the data synchronization function is enabled, the track report will be uploaded to the server.

[0295] In this step, according to step S1201, if the data synchronization function is detected to be enabled, the vehicle will synchronize the generated track report to the server. Subsequently, the server will send the track report to the designated terminal device. Through this process, the track report can be successfully transmitted from the vehicle to the terminal device, ensuring that users can obtain and view track data in a timely manner.

[0296] S1203: If the data synchronization function is not enabled, a prompt message will be pushed to remind the user to enable the data synchronization function.

[0297] In this step, according to step S1201, if the data synchronization function is detected to be not enabled, the vehicle will push a prompt message. This prompt message is intended to remind the user to enable the data synchronization function to ensure that the track report can be transmitted smoothly.

[0298] Specifically, when the vehicle detects that the data synchronization function is off, it will immediately generate and send a prompt message to the vehicle's display interface. This prompt message will clearly inform the user that the data synchronization function needs to be enabled in order to achieve real-time synchronization and transmission of track reports. In this way, the vehicle can promptly remind the user to take necessary actions to ensure the normal operation of the data synchronization function.

[0299] S1204: After detecting that the data synchronization function is enabled, upload the track report to the server.

[0300] In this step, according to step S1203, when the vehicle detects that the data synchronization function has been enabled, it will immediately upload the track report to the server.

[0301] Specifically, the vehicle's built-in system continuously monitors the status of the data synchronization function. Once it confirms that the function has been activated, the vehicle automatically initiates the track report upload process. Through a network connection, the vehicle transmits the track report to the server in real time. The server can then promptly receive and process the track report, preparing it for subsequent data analysis and transmission.

[0302] The track report synchronization method provided in this application primarily emphasizes the importance of enabling the data synchronization function. Specifically, enabling the data synchronization function is a key step in achieving real-time transmission and accurate synchronization of track reports. When the vehicle is in a track environment, enabling the data synchronization function ensures that the track report is immediately uploaded to the server after generation and further transmitted to the user's terminal device. This process not only guarantees the timeliness and accuracy of the track report but also provides users with immediate track data analysis and feedback.

[0303] Figure 13 is a flowchart illustrating a ninth embodiment of a track report synchronization method provided in this application. As shown in Figure 13, the process of this track report synchronization method may include:

[0304] S1301: Track report stored locally on the vehicle.

[0305] In this step, based on step S202, after the vehicle generates a track report based on the operating parameters recorded during the driving process in the track scenario, the track report is stored locally.

[0306] The local storage track report provides instant access and rapid response, enhances data security and integrity, reduces reliance on the network and related costs, and facilitates personalized analysis and long-term historical data comparison, thereby improving user experience and data management efficiency.

[0307] In one possible implementation, during local storage of the track report, the vehicle's built-in system encrypts and compresses the report to save storage space and protect data privacy and security. Simultaneously, the vehicle's built-in system generates a log entry for upload failure, detailing the time, cause, and relevant network status information. This log information will aid in subsequent troubleshooting and system optimization.

[0308] It's worth noting that if the vehicle is privately owned, users can delete track reports at any time as needed, allowing for better management and control of their data and ensuring privacy and data security. If the vehicle is publicly owned, a time period for deleting track reports can be set, automatically deleting them within the preset time frame. This not only helps protect user privacy and prevent data misuse but also effectively manages storage space, avoiding storage pressure caused by the long-term accumulation of large amounts of data. Furthermore, regularly deleting track reports ensures efficient vehicle operation and reduces unnecessary data redundancy.

[0309] While storing the track report locally, the vehicle will monitor the network signal quality in real time. If the network signal quality does not meet the preset requirements and / or the track report upload fails, the vehicle will not be able to successfully upload the track report to the server.

[0310] In this context, "network signal quality not meeting preset requirements" means that the current network signal strength or quality is below the system's minimum standard. This may include weak signal strength, high network latency, low data transmission rate, etc. In this situation, the vehicle monitors the network signal in real time and uploads the track report once the network signal meets the preset requirements.

[0311] A track report upload failure means that the vehicle failed to successfully upload the track report to the server. This could be due to network interruption, server unavailability, packet loss, or other reasons. In this situation, the vehicle can continue to try uploading the track report to the server, or manual intervention can be provided.

[0312] S1302: After the network signal quality meets the requirements, upload the track report to the server.

[0313] In this step, according to step S1301, after the vehicle stores the track report locally, it uploads the track report to the server once the network signal quality meets the quality requirements.

[0314] In one possible implementation, if the vehicle detects an account login before the network signal quality reaches a preset level, it will automatically re-attempt to associate the locally stored track report with the currently logged-in account identifier and upload it to the server once the network signal quality recovers and meets the preset requirements. During the re-upload process, the vehicle will prioritize data transmission during periods of higher network signal strength to improve the upload success rate. It is worth noting that even if the track report has been successfully uploaded to the server, the vehicle will still store it locally. This approach not only ensures multiple backups of the track report, improving its security and reliability, but also guarantees that users can access and view the track report at any time, even when the network connection is unstable or server access is restricted. Furthermore, locally stored track reports provide users with a faster reading and analysis experience, reducing inconvenience caused by network latency. Through dual local and server storage, users can enjoy more efficient, stable, and secure data management services.

[0315] In another possible implementation, if the vehicle does not detect an account login before the network signal quality reaches the preset requirements, the vehicle will respond to the user's operation to log in to the account after the network signal quality recovers and reaches the preset requirements, and will associate the track report selected by the user with the currently logged-in account identifier and upload it to the server.

[0316] The method for users to select track reports can be found in steps S501 to S502, and will not be repeated here.

[0317] In another possible implementation, if the vehicle does not detect an account login before the network signal quality reaches the preset requirements, the vehicle will respond to the terminal device's QR code scanning operation and upload the track report to the server after the network signal quality recovers and reaches the preset requirements. Specific implementation details can be found in steps S901 to S908 and steps S1001 to S1003, and will not be elaborated further here.

[0318] The track report synchronization method provided in this application stores the track report locally on the vehicle after it is generated, and uploads it to the server once the network signal quality meets the requirements. This method enhances the reliability of the track report, ensuring that it is properly preserved even in the event of poor or interrupted network signal, thus preventing data loss. Simultaneously, users can access and view the track report locally at any time, enjoying a faster reading and analysis experience without relying on a network connection. Furthermore, uploading the track report only after the network signal quality meets the requirements optimizes the use of network resources, reduces transmission failures and retransmissions, and improves overall operational efficiency. Dual storage—local and server—further enhances the security and reliability of the track report, providing multiple backups to ensure effective data protection under any circumstances.

[0319] Figure 14 is a flowchart illustrating a method for synchronizing track reports according to this application. As shown in Figure 14, the process of this method for synchronizing track reports may include:

[0320] S1401: Generate track report.

[0321] In this step, the vehicle generates a track report based on the operating parameters recorded during its driving in the track scenario. Specific implementation details can be found in steps S201 to S202, and will not be repeated here. It is worth noting that the generated track report is stored locally on the vehicle.

[0322] S1402: Is the data synchronization function enabled?

[0323] In this step, the automatic synchronization of the track report to the target terminal is contingent upon the data synchronization function being enabled. Specific implementation details can be found in steps S1201 to S1204, and will not be repeated here. If the data synchronization function is not enabled, proceed to step S1403. If the data synchronization function is enabled, proceed to step S1404.

[0324] S1403: Displays a prompt message, reminding the user to enable the data synchronization function.

[0325] In this step, if the data synchronization function is not enabled, a prompt message will be displayed on the vehicle's infotainment system, reminding the user to enable the data synchronization function. Based on the user's needs, determine whether to enable the data synchronization function.

[0326] S1404: Log in to your account?

[0327] In this step, assuming data synchronization is enabled, it is necessary to further check whether a login account exists for the vehicle to ensure that the track report is accurately sent to the target terminal. If a login account exists, the track report is uploaded to the server, and step S1406 is executed. If no login account exists, step S1405 is executed.

[0328] S1405: Display the QR code and / or associated button corresponding to the track report.

[0329] In this step, if no account is logged in, the vehicle's infotainment system displays a QR code corresponding to the track report for the terminal device to scan. For details on this implementation, please refer to steps S901 to S908, which will not be repeated here. Alternatively, the vehicle's infotainment system displays an association button. After logging in, the user can select the track report to upload to the server. For details on this implementation, please refer to steps S501 to S502, which will not be repeated here.

[0330] S1406: Was the track report successfully uploaded?

[0331] In this step, while the vehicle is uploading the track report to the server, it is necessary to continuously check whether the track report has been successfully uploaded to the server. If the upload fails, proceed to step S1407; if the upload is successful, proceed to step S1408.

[0332] S1407: Analyze the reasons for the upload failure and re-upload the track report.

[0333] In this step, if the vehicle fails to successfully upload the track report to the server, it is necessary to analyze the reason for the upload failure and re-upload the track report. Specific implementation steps can be found in step S1302, and will not be repeated here.

[0334] S1408: Vehicle synchronizes track reports to the target terminal.

[0335] In this step, the server sends the corresponding track report to the target terminal based on the terminal identifier, thereby enabling the vehicle to synchronize the track report to the target terminal. The methods for determining the terminal identifier include, but are not limited to, the association between account identifiers and terminal identifiers pre-stored in the server, and report retrieval requests containing both the terminal identifier and account identifier sent by the terminal device to the server.

[0336] This method can improve the synchronization efficiency of track reports between vehicles and terminal devices, effectively solving the synchronization pain points in scenarios such as personal racing and event racing.

[0337] Figure 15 is a schematic diagram of an embodiment of a track report synchronization device provided in this application. As shown in Figure 15, the track report synchronization device 1500 includes:

[0338] The recording module 1501 is used to record the operating parameters of the vehicle during its driving in a track setting.

[0339] The generation module 1502 generates a track report based on the running parameters recorded during the driving process in the track scenario;

[0340] Upload module 1503 uploads the track report to the server.

[0341] Optionally, the upload module 1503 is also used for:

[0342] If the vehicle is currently logged into an account, the track report and the currently logged-in account identifier will be associated and uploaded to the server.

[0343] Optionally, the upload module 1503 is also used for:

[0344] Upon receiving a trigger action based on the report upload control, if the vehicle is currently logged into an account, the track report and the currently logged-in account identifier will be associated and uploaded to the server.

[0345] Optionally, the upload module 1503 is also used for:

[0346] Associate the track report and account ID corresponding to the report ID and upload them to the server.

[0347] Optionally, the QR code can also be associated with a vehicle identification number.

[0348] Optionally, the upload module 1503 is also used for:

[0349] The track report and vehicle identification are linked and uploaded to the server.

[0350] Optionally, the upload module 1503 is also used for:

[0351] Once the network signal quality meets the requirements, the track report will be uploaded to the server.

[0352] Optionally, the upload module 1503 is also used for:

[0353] If data synchronization is enabled, the track report will be uploaded to the server.

[0354] Optionally, the upload module 1503 is also used for:

[0355] Once the data synchronization function is detected as enabled, the track report will be uploaded to the server.

[0356] The track report synchronization device provided in this application embodiment can be used to execute the track report synchronization method in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0357] Figure 16 is a schematic diagram of a second embodiment of a track report synchronization device provided in this application. Based on the track report synchronization device shown in Figure 15, this track report synchronization device 1500 further includes:

[0358] Processing module 1504 is used for:

[0359] Displays the report upload control associated with the track report.

[0360] Optionally, the processing module 1504 is also used for:

[0361] Generate a QR code associated with the track report's identifier and control the vehicle's infotainment system to display the QR code. The QR code is used by external terminals to access the track report.

[0362] Receiver module 1505 is used for:

[0363] The report identifier and account identifier sent by the receiving server are associated with it.

[0364] Optionally, the processing module 1504 is also used for:

[0365] When the vehicle is not logged into an account, a QR code associated with the report identifier of the track report is generated.

[0366] Optionally, the processing module 1504 is also used for:

[0367] Track reports are stored locally on the vehicle.

[0368] Optionally, the processing module 1504 is also used for:

[0369] Check if the data synchronization function is enabled.

[0370] Optionally, the processing module 1504 is also used for:

[0371] If the data synchronization function is not enabled, a notification message will be pushed to remind the user to enable the data synchronization function.

[0372] The track report synchronization device provided in this application embodiment can be used to execute the track report synchronization method in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0373] Figure 17 is a schematic diagram of a third embodiment of a track report synchronization device provided in this application. As shown in Figure 17, the track report synchronization device 1700 includes:

[0374] The receiving module 1701 is used to receive the track report uploaded by the vehicle. The track report is generated based on the running parameters recorded by the vehicle during its driving in the track scenario.

[0375] Processing module 1702 is used to determine the terminal identifier of the target terminal;

[0376] The sending module 1703 is used to send the track report to the target terminal based on the terminal identifier.

[0377] Optionally, the receiver module 1701 is also used for:

[0378] Receive track reports and account identifiers uploaded by the vehicle;

[0379] Optionally, the transmitting module 1703 is also used for:

[0380] Identify the terminal identifier associated with the account identifier and send the track report associated with the account identifier to the target terminal corresponding to the terminal identifier.

[0381] Optionally, the receiver module 1701 is also used for:

[0382] Receive the terminal identifier and account identifier uploaded by the target terminal.

[0383] Optionally, the receiver module 1701 is also used for:

[0384] Receive terminal identifiers, account identifiers, report identifiers, and vehicle identifiers uploaded by the associated terminal devices.

[0385] Optionally, the transmitting module 1703 is also used for:

[0386] The report identifier and account identifier are associated and sent to the vehicle based on the vehicle identifier, instructing the vehicle to associate and upload the track report corresponding to the report identifier and the account identifier;

[0387] Optionally, the receiver module 1701 is also used for:

[0388] Receive track reports and account identifiers uploaded by the vehicle;

[0389] Optionally, the sending module 1703 is also used for:

[0390] Identify the terminal identifier associated with the account identifier and send the track report associated with the account identifier to the target terminal corresponding to the terminal identifier.

[0391] Optionally, the receiving module 1701 is also used to: receive track reports and vehicle identifiers uploaded by the vehicle association.

[0392] Optionally, the processing module 1702 is also used for:

[0393] Based on the race time, vehicle identification, and race information table recorded in the track report, the user information of the vehicle driver during the race time is determined. The race information table is used to store the driver information of each vehicle for each time period.

[0394] Based on user information, determine the terminal identifier of the target terminal.

[0395] The track report synchronization device provided in this application embodiment can be used to execute the track report synchronization method in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0396] Figure 18 is a schematic diagram of a fourth embodiment of a track report synchronization device provided in this application. As shown in Figure 18, the track report synchronization device 1800 includes:

[0397] The generation module 1801 is used to generate a report retrieval request, which includes a terminal identifier and an account identifier corresponding to the terminal device.

[0398] The sending module 1802 is used to send a report retrieval request to the server so that the server can retrieve the track report associated with the account identifier;

[0399] The receiving module 1803 is used to receive track reports associated with account identifiers sent by the server.

[0400] Optionally, the report retrieval request may also include a vehicle identifier and a report identifier, so that the server can retrieve the track report corresponding to the report identifier from the target vehicle based on the vehicle identifier.

[0401] The track report synchronization device provided in this application embodiment can be used to execute the track report synchronization method in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0402] Figure 19 is a structural schematic diagram of a fifth embodiment of a track report synchronization device provided in this application. As shown in Figure 19, based on the track report synchronization device 1800 shown in Figure 18, the track report synchronization device 1800 further includes:

[0403] Response module 1804 is used for:

[0404] In response to a QR code scan, obtain vehicle identification and report identification.

[0405] The track report synchronization device provided in this application embodiment can be used to execute the track report synchronization method in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0406] Figure 20 is a structural schematic diagram of a vehicle provided in the application. As shown in Figure 20, the vehicle 2000 may specifically include a vehicle-mounted unit 2001, a processor 2002, and a memory 2003. The vehicle-mounted unit 2001 is used to transmit data with a server and terminal devices, and the memory 2003 stores computer execution instructions. The processor 2002 executes the computer execution instructions stored in the memory 2003 to implement the track report synchronization method in the above embodiment.

[0407] Figure 21 is a schematic diagram of the structure of a server provided in the application. As shown in Figure 21, the server 2100 may specifically include a transceiver 2101, a processor 2102, and a memory 2103. The transceiver 2101 is used to transmit data with vehicles and terminal devices, and the memory 2103 stores computer execution instructions. The processor 2102 executes the computer execution instructions stored in the memory 2103 to implement the track report synchronization method in the above embodiment.

[0408] Figure 22 is a schematic diagram of the structure of a terminal device provided in the application. As shown in Figure 22, the terminal device 2200 may specifically include a transceiver 2201, a processor 2202, and a memory 2203. The transceiver 2201 is used to transmit data with the server and the vehicle, and the memory 2203 stores computer execution instructions. The processor 2202 executes the computer execution instructions stored in the memory 2203 to implement the track report synchronization method in the above embodiment.

[0409] This embodiment provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the track report synchronization method in the above embodiment.

[0410] This embodiment also provides a computer program product, including a computer program that, when executed by a processor, implements the synchronization method for track reports provided in any of the above embodiments.

[0411] This embodiment also provides a chip, which includes a memory and a processor. The memory stores code and data, and the memory is coupled to the processor. The processor runs a program in the memory, enabling the chip to execute the synchronization method for track reports provided in the various embodiments described above.

[0412] This embodiment also provides a computer program, which, when executed by a processor, is used to perform the synchronization method for track reports provided in the foregoing various embodiments.

[0413] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0414] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method of synchronizing a track report, characterized by, The method applied to a vehicle comprises: Recording operation parameters of the vehicle during driving in a race track scenario; Generating a race track report according to the operation parameters recorded during driving in the race track scenario; Uploading the race track report to a server.

2. The method of claim 1, wherein, The uploading of the race track report to the server comprises: If the vehicle has logged in an account, uploading the race track report and the account identification currently logged in to the server.

3. The method according to claim 1 or 2, characterized in that, The method further comprises displaying a report uploading control associated with the race track report. The uploading of the race track report to the server comprises: after receiving a triggering operation based on the report uploading control, if the vehicle has logged in an account, uploading the race track report and the account identification currently logged in to the server.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: Generating a two-dimensional code associated with a report identification of the race track report, and controlling a vehicle machine interface of the vehicle to display the two-dimensional code, the two-dimensional code being used for an external terminal to obtain the race track report.

5. The method of claim 4, wherein, After the control of the vehicle machine interface of the vehicle to display the two-dimensional code, the method further comprises: Receiving the report identification and the account identification associatedly sent by the server; Uploading the race track report corresponding to the report identification and the account identification to the server.

6. The method of claim 4, wherein, The generation of the two-dimensional code associated with the report identification of the race track report comprises: when the vehicle has not logged in an account, generating the two-dimensional code associated with the report identification of the race track report.

7. The method according to any one of claims 4 to 6, characterized in that, The two-dimensional code is further associated with a vehicle identification.

8. The method according to any one of claims 1 to 7, characterized in that, The method further comprises uploading the race track report and the vehicle identification to the server.

9. The method according to any one of claims 1 to 8, characterized in that, The method further comprises: Storing the race track report locally in the vehicle; The uploading of the race track report to the server comprises: Uploading the race track report to the server after the network signal quality reaches a quality requirement.

10. The method according to any one of claims 1 to 9, characterized in that, Before the uploading of the race track report to the server, the method further comprises: Detecting whether a data synchronization function is enabled; If the data synchronization function is enabled, uploading the race track report to the server; If the data synchronization function is not enabled, pushing a prompt information, the prompt information being used for prompting a user to enable the data synchronization function; After detecting that the data synchronization function is enabled, uploading the race track report to the server.

11. A method of synchronizing a track report, characterized by, The method applied to a server comprises: Receiving a race track report uploaded by a vehicle, the race track report being generated according to operation parameters recorded by the vehicle during driving in a race track scenario; Determining a terminal identification of a target terminal; Sending the race track report to the target terminal according to the terminal identification.

12. The method of claim 11, wherein, The receiving of the race track report uploaded by the vehicle comprises: receiving the race track report and an account identification associatedly uploaded by the vehicle; The sending of the race track report to the target terminal according to the terminal identification comprises: determining the terminal identification associated with the account identification, and sending the race track report associated with the account identification to the target terminal corresponding to the terminal identification.

13. The method of claim 12, wherein, The method further comprises receiving the terminal identification and the account identification associatedly uploaded by the target terminal.

14. The method according to any one of claims 11 to 13, characterized in that, The method further comprises: The terminal device receiving terminal device is associated with the terminal identifier, the account identifier, the report identifier, the vehicle identifier; According to the vehicle identifier, the report identifier and the account identifier are associated and sent to the vehicle to instruct the vehicle to associate upload the track report corresponding to the report identifier and the account identifier; According to the terminal identifier, the track report is sent to the target terminal, including: receiving the track report and the account identifier associated with the vehicle upload; Determine the terminal identifier associated with the account identifier, and send the track report associated with the account identifier to the target terminal corresponding to the terminal identifier.

15. The method according to any one of claims 11 to 14, characterized in that, The method further comprises: Receiving the track report and vehicle identifier associated with the vehicle upload; According to the event time recorded in the track report, the vehicle identifier and the event information table, the user information driving the vehicle in the event time is determined, and the event information table is used to store the driving personnel information of each vehicle in each time period; The method further comprises: According to the user information, the terminal identifier of the target terminal is determined.

16. A method of synchronizing a track report, characterized by, Applied to a terminal device, the method comprises: Generating a report acquisition request, the report acquisition request comprising a terminal identifier corresponding to the terminal device and an account identifier; Sending the report acquisition request to a server for the server to acquire a track report associated with the account identifier; Receiving the track report associated with the account identifier sent by the server.

17. The method of claim 16, wherein, Before the report acquisition request is generated, the method further comprises: In response to a scanning operation on a two-dimensional code, a vehicle identifier and a report identifier are acquired; The report acquisition request further comprises the vehicle identifier and the report identifier, so that the server acquires a track report corresponding to the report identifier from a target vehicle according to the vehicle identifier.

18. A synchronization apparatus of a track report, characterized by, Applied to a vehicle, comprising: A recording module for recording running parameters of a vehicle during driving in a track scene; A generating module for generating a track report according to the running parameters recorded during driving in the track scene; An uploading module for uploading the track report to a server.

19. A synchronization apparatus of a track report, characterized by, Applied to a server, comprising: A receiving module for receiving a track report uploaded by a vehicle, the track report being generated according to running parameters recorded by the vehicle during driving in a track scene; A processing module for determining a terminal identifier of a target terminal; A sending module for sending the track report to the target terminal according to the terminal identifier.

20. A synchronization apparatus of a track report, characterized by, Applied to a terminal device, comprising: A generating module for generating a report acquisition request, the report acquisition request comprising a terminal identifier corresponding to the terminal device and an account identifier; A sending module for sending the report acquisition request to a server for the server to acquire a track report associated with the account identifier; A receiving module for receiving the track report associated with the account identifier sent by the server.

21. A vehicle characterized by comprising: Comprising: A car machine, a processor, and a memory in communication connection with the processor; The memory stores computer execution instructions; The processor executes the computer-executable instructions stored in the memory to implement the synchronization method of the track report according to any one of claims 1-10.

22. A server, comprising: Comprise: a transceiver, a processor, and a memory connected to the processor in communication; the memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the synchronization method of the track report according to any one of claims 11-15.

23. A terminal device, comprising: Comprise: a transceiver, a processor, and a memory connected to the processor in communication; the memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the synchronization method of the track report according to any one of claims 16-17.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the synchronization method of the track report according to any one of claims 1-17.

25. A computer program product, characterised in that, The computer program is executed by a processor to implement the synchronization method of the track report according to any one of claims 1-17.

26. A computer program, characterized in that, When the computer program is executed by the processor, it is used to execute the synchronization method of the track report according to any one of claims 1-17.

27. A chip, characterized by The chip comprises a memory and a processor, the memory stores codes and data, the memory is coupled to the processor, and the processor runs the program in the memory so that the chip is used to execute the synchronization method of the track report according to any one of claims 1-17.

Images