Vehicle data management method, server data management method and electronic equipment

Abstract

The invention relates to the technical field of data management, in particular to a data management method of a vehicle, a data management method of a server side and electronic equipment, and the method comprises the steps: obtaining a latest authorization status word of a current application; judging whether the current application starts data synchronization authorization or not based on the latest authorization status word; and if the current application starts the data synchronization authorization, synchronizing the data of the current application to the server, otherwise, reminding a user that the current application does not start the data synchronization authorization by using a preset reminding strategy. Therefore, the problem that data collection and synchronization functions at the two ends of a vehicle-mounted terminal and a mobile phone are lack of mature and complete solutions is solved, and data interaction is performed from more dimensions on the premise of protecting user data privacy.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a vehicle data management method, a server-side data management method, and an electronic device. Background Technology

[0002] Currently, the market lacks mature and comprehensive solutions for collecting, displaying, and synchronizing data between in-vehicle systems and mobile phones. This deficiency undoubtedly hinders the improvement of vehicle functionality and user experience to some extent. Summary of the Invention

[0003] This application provides a vehicle data management method, a server-side data management method, and an electronic device to address the lack of mature and complete solutions for the collection, display, and synchronization of data between vehicle-mounted systems and mobile phones. Under the premise of protecting user data privacy, it provides users with data display and interaction from more dimensions.

[0004] The first aspect of this application provides a vehicle data management method, including the following steps: obtaining the latest authorization status word of the current application; determining whether the current application has enabled data synchronization authorization based on the latest authorization status word; if the current application has enabled data synchronization authorization, then synchronizing the data of the current application to the server; otherwise, using a preset reminder strategy to remind the user that the current application has not enabled data synchronization authorization.

[0005] Optionally, when synchronizing the data of the current application to the server, the process includes: if a request to disable data synchronization authorization is received from the current application, then asking the user whether they are sure they want to disable the data synchronization authorization of the current application; if a confirmation instruction to disable the data synchronization authorization of the current application is received, then disabling the data synchronization authorization of the current application, stopping data synchronization, and deleting the synchronized data of the current application from the server.

[0006] Optionally, after synchronizing the data of the current application to the server, the process includes: receiving a request from the mobile device to disable data synchronization authorization for the current application; and updating the data synchronization authorization status of the current application in the vehicle based on the request to disable data synchronization authorization for the current application.

[0007] Optionally, after synchronizing the data of the current application to the server, the method further includes: obtaining a first data deletion request for the current application sent by the user; and deleting the first data of the current application in the vehicle according to the first data request.

[0008] Optionally, the above-described vehicle data management method further includes: receiving a data display instruction for the current application sent by a user; and displaying the data of the current application using the vehicle's display screen according to a preset display strategy based on the data display instruction.

[0009] Optionally, the data transmission protocol between the vehicle and the server is the MQTT communication protocol.

[0010] In the above implementation, the latest authorization status word of the current application is obtained; based on the latest authorization status word, it is determined whether the current application has enabled data synchronization authorization; if the current application has enabled data synchronization authorization, the data of the current application is synchronized to the server; otherwise, a preset reminder strategy is used to remind the user that the current application has not enabled data synchronization authorization. This solves the problem of the lack of mature and complete solutions for the collection, display, and synchronization of data on both the vehicle system and mobile phone, and provides users with data display and interaction from more dimensions while protecting user data privacy.

[0011] A second aspect of this application provides a server-side data management method, comprising: receiving a data synchronization authorization closure request for the current application sent by a mobile terminal; updating the data synchronization authorization status of the current application in the server based on the data synchronization authorization closure request for the current application; and deleting all data of the current application in the server.

[0012] Optionally, the above-described server-side data management method further includes: receiving a first data deletion request packet sent by the vehicle and a second data deletion request packet sent by the mobile terminal; and deleting the first and second data of the currently applied application in the server according to the first data deletion request packet and the second data deletion request packet.

[0013] Optionally, the data transmission protocol between the mobile device and the server is the HTTPS communication protocol.

[0014] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle data management method and the server data management method as described in the above embodiments.

[0015] A fourth aspect of this application provides a computer program product having a computer program stored thereon, which is executed by a processor to implement the vehicle data management method and the server-side data management method as described in the above embodiments.

[0016] In the above implementation, a request to disable data synchronization authorization for the current application is received from the mobile device; based on the request, the data synchronization authorization status of the current application in the server is updated, and all data of the current application in the server is deleted. This solves the problem of the lack of mature and complete solutions for the collection, display, and synchronization of data on both the vehicle system and the mobile phone, and provides users with data display and interaction from more dimensions while protecting user data privacy.

[0017] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0018] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a flowchart illustrating a vehicle data management method according to an embodiment of this application; Figure 2 This is a flowchart of a data management method according to an embodiment of this application; Figure 3 This is a flowchart of a vehicle data management method according to an embodiment of this application; Figure 4 This is a flowchart illustrating the opening and closing of the authorization service according to one embodiment of this application; Figure 5 This is a flowchart illustrating the deletion of data on the vehicle side according to one embodiment of this application; Figure 6 This is a schematic diagram illustrating the deletion of data on a mobile device according to an embodiment of this application; Figure 7 This is an example diagram of a server-side data management method according to an embodiment of this application; Figure 8 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0019] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0020] The following description, with reference to the accompanying drawings, describes a vehicle data management method, a server-side data management method, and an electronic device according to embodiments of this application.

[0021] Specifically, Figure 1This is a flowchart illustrating a vehicle data management method provided in an embodiment of this application.

[0022] like Figure 1 As shown, the data management method for this vehicle includes the following steps: Centered on the server, it establishes bidirectional data communication, classifies communication data based on factors such as size, security, QoS, latency, and response requirements, establishes different communication links according to different requirements and applications, and provides communication capability services.

[0023] The in-vehicle infotainment system includes two functions: data collection and receipt display. The mobile app has data display and authorization cancellation functions.

[0024] In step S101, the latest authorization status word of the current application is obtained.

[0025] In step S102, it is determined whether the current application has enabled data synchronization authorization based on the latest authorization status word.

[0026] Specifically, such as Figure 2 As shown, after the vehicle is powered on, it establishes a communication connection with the server. When the user clicks on the current application on the vehicle's infotainment system, the vehicle obtains the latest authorization status word of the current application and checks whether data synchronization is enabled based on the latest authorization status word.

[0027] In step S103, if the current application has data synchronization authorization enabled, the data of the current application is synchronized to the server; otherwise, the user is reminded that the current application has not enabled data synchronization authorization using a preset reminder strategy.

[0028] like Figure 3 As shown, internet service providers require users to authorize the use of their applications before using them, clearly informing users of the purpose for which their personal information will be collected and used, and allowing users to choose whether to authorize. Vehicle data is user privacy data. When the application is opened without authorization, a privacy pop-up will be displayed to explain the permission request. The user will only begin collecting the user's driving data after clicking to agree to data synchronization authorization. If the application has not enabled data synchronization authorization, the user will be prompted to enable it.

[0029] For example, after the vehicle is powered on, the on-board terminal establishes a secure communication connection with the manufacturer's server.

[0030] The vehicle obtains the authorization status word (hexadecimal format) from the navigation application: 0x0001; Secondly: Vehicle parsing authorization status word 0x0001: The authorization status word for the navigation application is 0x0001, indicating that it has been authorized.

[0031] The vehicle has confirmed that the navigation application has enabled data synchronization authorization.

[0032] Finally: Perform synchronization or notification.

[0033] The vehicle reads the user's trip data from local storage in the navigation application.

[0034] The trip data is encrypted and uploaded to the server via the T-Box, and a successful synchronization confirmation is received from the server. The central control screen then displays a message: "Navigation data has been synchronized to the server."

[0035] If the navigation application is not authorized, for example, if the current authorization status word of the navigation application is 0x0002, trigger the alert policy: Strategy A: A notification pops up on the central control screen: "Navigation data synchronization is not enabled. Click settings to enable it."

[0036] Strategy B: Use voice prompts: "Please note that navigation data synchronization authorization is not enabled. You need to authorize it in the settings."

[0037] Strategy C: Force the display of an authorization confirmation pop-up the next time the user opens the navigation app.

[0038] Optionally, in some embodiments, when synchronizing the data of the current application to the server, the process includes: if a request to disable data synchronization authorization is received from the current application, then asking the user whether they are sure they want to disable the data synchronization authorization of the current application; if a confirmation instruction to disable the data synchronization authorization of the current application is received, then disabling the data synchronization authorization of the current application and stopping data synchronization.

[0039] The mobile client also allows you to modify the data synchronization authorization for the current application, meaning you can turn the data synchronization authorization for the current application off or on.

[0040] After the vehicle's infotainment system or mobile phone cancels the data synchronization authorization for the current application, the server will clear the data of the current application to meet the user's data confidentiality requirements. Of course, when the user performs the cancellation operation, the user will be asked whether they are sure they want to disable the data synchronization authorization for the current application. If the user confirms that they want to disable the data synchronization authorization for the current application, the data synchronization authorization for the current application will be disabled, data synchronization will stop, and the server will delete all data of the current application.

[0041] Optionally, in some embodiments, after synchronizing the data of the current application to the server, the process includes: receiving a request from the mobile device to disable data synchronization authorization for the current application; and updating the data synchronization authorization status of the current application in the vehicle based on the request to disable data synchronization authorization for the current application.

[0042] like Figure 4As shown, if a user cancels the data synchronization authorization for the current application on their mobile phone, the vehicle will also cancel the data synchronization authorization for the current application simultaneously.

[0043] For example, if a user turns off the synchronization switch for the navigation application in the "Data Synchronization Settings" on their mobile phone, after the vehicle terminal receives the data synchronization authorization request pushed by the mobile phone, the vehicle updates the data synchronization authorization status of the current application and writes the new data synchronization authorization status of the current application to the local secure storage.

[0044] Optionally, in some embodiments, after synchronizing the data of the current application to the server, the method further includes: obtaining a first data deletion request for the current application sent by the user; and deleting the first data of the current application in the vehicle according to the first data request.

[0045] Understandably, if a user enters the "Data Management" interface of the navigation application on the in-vehicle central control screen and selects to delete the first data, a confirmation pop-up window will appear on the vehicle's TV screen: "Confirm to delete local data?" After the user confirms, a first deletion request is generated, and the vehicle deletes only the first data of the current application that is currently cached locally according to the first deletion request.

[0046] For example, such as Figure 5 As shown, when a user selects to delete trip data for a specific day on the vehicle's infotainment system, the vehicle deletes the trip data for that day from the currently used application after receiving the user's request. Figure 6 As shown, when a user selects to delete single-trip data on their mobile phone, the vehicle deletes the currently used single-trip data from the vehicle after receiving the deletion request from the mobile phone.

[0047] For certain specific trips, users may need to delete data. Considering the different granularities of data display, the minimum deletion range for data on the in-vehicle app is one day, while the minimum deletion range for data on the mobile phone is a single trip.

[0048] Optionally, in some embodiments, the above-described vehicle data management method further includes: receiving a data display instruction for the current application sent by a user; and displaying the data of the current application using the vehicle's display screen according to a preset display strategy based on the data display instruction.

[0049] Considering the different user scenarios, the granularity of data display differs between the in-vehicle system and the mobile device.

[0050] The in-vehicle infotainment system has a large display screen, but it's suitable for displaying lower data densities. Larger fonts and images, along with wider layouts, can be used to make the content clearer, easier to read, and more aesthetically pleasing. Therefore, the in-vehicle infotainment system primarily displays monthly data.

[0051] Mobile applications display data with high density and convenient UI interaction, and the data is displayed in units of "single trip".

[0052] In special cases, when there is only one trip in a month, the data displayed on the in-vehicle system and the mobile phone overlaps. Considering the user's psychology, the accuracy of the data display needs to be consistent. Therefore, the in-vehicle system, the server, and the mobile phone all adhere to the same data accuracy requirements.

[0053] Optionally, in some embodiments, the data transmission protocol between the vehicle and the server is the MQTT communication protocol.

[0054] The data transmission protocol between the vehicle and the server is the MQTT communication protocol, such as... Figure 2 As shown, MQTT (Message Queuing Telemetry Transport) is a lightweight publish / subscribe communication protocol commonly used for data transmission in the Internet of Things (IoT) and sensor networks. Based on the TCP / IP protocol, it is typically used for communication between devices in low-bandwidth, high-latency, or unstable network environments. The MQTT communication protocol is characterized by its lightweight nature, high efficiency, reliability, and flexibility, thus finding widespread application in IoT and sensor networks. Given the unstable network conditions of in-vehicle systems, this communication protocol is used for data exchange between the vehicle's infotainment system and the server, providing a smooth user experience, addressing user pain points, and meeting marketing needs.

[0055] According to the vehicle data management method proposed in this application, the latest authorization status word of the current application is obtained; based on the latest authorization status word, it is determined whether the current application has enabled data synchronization authorization; if the current application has enabled data synchronization authorization, the data of the current application is synchronized to the server; otherwise, a preset reminder strategy is used to remind the user that the current application has not enabled data synchronization authorization. This solves the problem of the lack of mature and complete solutions for the collection, display, and synchronization of data on both vehicle and mobile phone terminals, and provides users with data display and interaction from more dimensions while protecting user data privacy.

[0056] Next, the data management method for the server proposed according to the embodiments of this application is described with reference to the accompanying drawings.

[0057] Figure 7 This is a schematic diagram of a server-side data management method according to an embodiment of this application.

[0058] like Figure 7 As shown, the server-side data management method includes the following steps: In step S701, a request to disable data synchronization authorization for the current application is received from the mobile terminal.

[0059] In step S702, based on the current application's data synchronization authorization closure request, the data synchronization authorization status of the current application in the server is updated, and all data of the current application in the server is deleted.

[0060] Understandably, when a user turns data synchronization authorization for a certain application on or off in the "Data Synchronization Settings" on their mobile phone, the mobile phone sends a request to turn off data synchronization authorization for that application to the server. The server then updates the data synchronization authorization status of the current application and deletes all data of the current application from the server when it receives a request to turn off data synchronization authorization for the current application.

[0061] Optionally, in some embodiments, the above-described server-side data management method further includes: receiving a first data deletion request packet sent by a vehicle and a second data deletion request packet sent by a mobile terminal; and deleting the first data and the second data of the currently applied application in the server according to the first data deletion request packet and the second data deletion request packet.

[0062] Understandably, if a user selects "Delete the first data of the current application" on the vehicle's infotainment display, the vehicle simultaneously sends a first data deletion request packet to the server. The server then deletes the first data of the current application from its database based on the first data deletion request packet. If the user selects "Delete the second data of the current application" on their mobile phone, the mobile phone simultaneously sends a second data deletion request packet to the server. The server then deletes the second data of the current application from its database based on the second data deletion request packet. Finally, the server returns the deletion result of the first data to the vehicle and the deletion result of the second data to the mobile phone.

[0063] For example, such as Figure 5 As shown, when a user selects to delete trip data for a specific day on the vehicle's infotainment system, the server, upon receiving the user's request to delete trip data for that day, deletes the trip data for that day from the server's current application. Figure 6 As shown, when a user selects to delete single-trip data on their mobile device, the server deletes the single-trip data of the current application from the server after receiving the request to delete single-trip data from the mobile device.

[0064] In some embodiments, the data transmission protocol between the mobile device and the server is the HTTPS communication protocol.

[0065] The data transmission protocol between the mobile device and the server is HTTPS. Figure 2As shown, HTTPS (Hypertext Transfer Protocol Secure) is a secure communication protocol used for transmitting data over the network using SSL / TLS encryption. It is a secure version of the HTTP protocol, using SSL / TLS to encrypt data, thus ensuring the security and integrity of data transmitted between the client and server. Communication between the mobile phone and the server uses this protocol to ensure the security of the user's travel data.

[0066] According to the server-side data management method proposed in this application, a request to close the data synchronization authorization for the current application sent by the mobile terminal is received; based on the request, the data synchronization authorization status of the current application in the server is updated, and all data of the current application in the server is deleted. This solves the problem of the lack of mature and complete solutions for the collection, display, and synchronization of data on both vehicle-mounted systems and mobile phones. While protecting user data privacy, it provides users with data display and interaction from multiple dimensions, offering a smooth user experience, addressing user pain points, and meeting marketing needs.

[0067] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include: The memory 801, the processor 802, and the computer program stored on the memory 801 and capable of running on the processor 802.

[0068] When the processor 802 executes the program, it implements the vehicle data management method and the server-side data management method provided in the above embodiments.

[0069] Furthermore, electronic devices also include: Communication interface 803 is used for communication between memory 801 and processor 802.

[0070] The memory 801 is used to store computer programs that can run on the processor 802.

[0071] The memory 801 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0072] If the memory 801, processor 802, and communication interface 803 are implemented independently, then the communication interface 803, memory 801, and processor 802 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized into address buses, data buses, control buses, etc. For ease of representation, Figure 8 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0073] Optionally, in a specific implementation, if the memory 801, processor 802, and communication interface 803 are integrated on a single chip, then the memory 801, processor 802, and communication interface 803 can communicate with each other through an internal interface.

[0074] The processor 802 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0075] This application also provides a computer program product on which a computer program is stored. When the program is executed by a processor, it implements the above-described vehicle data management method and server-side data management method.

[0076] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0077] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0078] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0079] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequential list of executable instructions for implementing logical functions, and can be specifically implemented in any computer program product for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer program product" can be any means that can contain, store, communicate, propagate, or transmit a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples of computer program products (a non-exhaustive list) include the following: an electrical connection having one or N wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic device, and portable optical disc read-only memory (CDROM). Furthermore, the computer program product can even be paper or other suitable medium on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0080] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0081] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer program product, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0082] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer program product.

[0083] The computer program product mentioned above may be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A vehicle data management method, characterized in that, Includes the following steps: Get the latest authorization status word for the current application; Based on the latest authorization status word, determine whether the current application has enabled data synchronization authorization; If the current application has enabled data synchronization authorization, then the data of the current application is synchronized to the server; otherwise, a preset reminder strategy is used to remind the user that the current application has not enabled data synchronization authorization.

2. The vehicle data management method according to claim 1, characterized in that, When synchronizing the data of the current application to the server, the following is included: If a request to disable data synchronization authorization for the current application is received, the user is asked whether they are sure they want to disable data synchronization authorization for the current application. If a confirmation instruction to disable data synchronization authorization for the current application is received, then disable data synchronization authorization for the current application and stop data synchronization.

3. The vehicle data management method according to claim 2, characterized in that, After synchronizing the data of the current application to the server, the process includes: Receive a request from the mobile device to disable data synchronization for the current application; Based on the current application's request to disable data synchronization authorization, update the data synchronization authorization status of the current application in the vehicle.

4. The vehicle data management method according to claim 1, characterized in that, After synchronizing the data of the current application to the server, the process also includes: Get the first data deletion request sent by the user for the current application; The first data request is used to delete the first data currently being used in the vehicle.

5. The vehicle data management method according to claim 1, characterized in that, Also includes: Receive user-sent instructions to display the data of the current application; Based on the data display instructions, the vehicle's display screen is used to display the data of the current application using a preset display strategy.

6. The vehicle data management method according to claim 1, characterized in that, The data transmission protocol between the vehicle and the server is the MQTT communication protocol.

7. A server-side data management method, characterized in that, Includes the following steps: Receive a request from the mobile device to disable data synchronization authorization for the current application; Based on the current application's request to disable data synchronization authorization, update the data synchronization authorization status of the current application on the server and delete all data of the current application on the server.

8. The server-side data management method according to claim 7, characterized in that, Also includes: Receive the first data deletion request packet sent by the vehicle and the second data deletion request packet sent by the mobile terminal; Delete the first and second data of the current application in the server according to the first data deletion request packet and the second data deletion request packet.

9. The server-side data management method according to claim 8, characterized in that, The data transmission protocol between the mobile device and the server is the HTTPS communication protocol.

10. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the vehicle data management method as described in any one of claims 1-6 and the server data management method as described in any one of claims 7-9.

Images