Cross-equipment navigation task synchronization method and device, equipment and storage medium

Abstract

The present application is applicable to the technical field of data transmission, and provides a cross-device navigation task synchronization method, apparatus and device, and a storage medium, the method comprising: if a first terminal satisfies a preset cross-device transmission condition, acquiring navigation data from a first navigation application through a first navigation circulation module; generating navigation synchronization information of the navigation data through a first navigation circulation module; the second terminal receives the navigation synchronization information sent by the first terminal and transmits the navigation synchronization information to a second navigation application through a second navigation circulation module; and updating the navigation task of the second navigation application according to the navigation synchronization information. According to the technical scheme provided by the invention, synchronization of cross-device navigation tasks can be realized, and a user does not need to perform task setting on the navigation application of the terminal for many times in a cross-device navigation scene, so that the navigation task setting efficiency is greatly improved, and repeated operation of the user is reduced.

Description

[0001] This application is a divisional application. The application number of the original application is 202111244792.3, and the original application date is October 25, 2021. The entire content of the original application entitled "Method, device, equipment and storage medium for synchronizing navigation tasks across devices" is incorporated by reference into this application. Technical Field

[0002] The present application belongs to the field of device control technology, and in particular, relates to a method, apparatus, device and storage medium for synchronizing navigation tasks across devices. Background Art

[0003] With the continuous development of navigation technology, the application scenarios of navigation technology are constantly increasing, from the initial car driving navigation, gradually developing to navigation for walking users, and even finely divided into application scenarios such as cycling navigation. Navigation applications have become one of the important applications that are indispensable in people's lives and work. Therefore, how to quickly and conveniently complete the navigation task has become a technical problem that needs to be solved urgently.

[0004] In existing navigation applications, users can set navigation destinations on the navigation application of the terminal. The navigation application can generate navigation tasks based on the user's location and the set navigation destination, and prompt the user's direction of travel during the user's movement to achieve the purpose of navigation. However, in the actual navigation process of the user, there may be a variety of different navigation scenarios, and the terminals used for navigation in different navigation scenarios are often different. For example, in the scenario of vehicle driving, the user can navigate through the navigation application in the vehicle terminal, while in the scenario of walking, the user uses a portable smartphone to complete the navigation task. Therefore, if the navigation process includes multiple different navigation scenarios, the user needs to set the navigation task multiple times in different terminals, which greatly increases the user's configuration operations and reduces the efficiency of setting the navigation task. Summary of the invention

[0005] The embodiments of the present application provide a method, apparatus, device and storage medium for synchronizing navigation tasks across devices, which can solve the problem that in the scenario of cross-device navigation, users need to set navigation tasks multiple times, the setting efficiency of navigation tasks is low, and users have to repeat settings.

[0006] In a first aspect, an embodiment of the present application provides a method for synchronizing navigation tasks across devices, including:

[0007] If the first terminal meets the preset cross-device transmission condition, the first terminal obtains the navigation data from the first navigation application;

[0008] The first terminal generates navigation synchronization information of the navigation data;

[0009] The second terminal receives the navigation synchronization information sent by the first terminal, and transmits the navigation synchronization information to a second navigation application;

[0010] The second terminal updates the navigation task of the second navigation application according to the navigation synchronization information.

[0011] In a possible implementation of the first aspect, the first terminal includes a first navigation flow module; the second terminal includes a second navigation flow module;

[0012] If the first terminal meets the preset cross-device transmission condition, the navigation data is obtained from the first navigation application, specifically: if the first terminal meets the preset cross-device transmission condition, the navigation data is obtained from the first navigation application through the first navigation flow module;

[0013] The first terminal generating the navigation synchronization information of the navigation data specifically includes: the first terminal generating the navigation synchronization information of the navigation data by using the first navigation flow module;

[0014] The second terminal receives the navigation synchronization information sent by the first terminal, and transmits the navigation synchronization information to the second navigation application. Specifically, the second terminal receives the navigation synchronization information sent by the first terminal, and transmits the navigation synchronization information to the second navigation application through a second navigation flow module.

[0015] The implementation of the embodiment of the present application has the following beneficial effects: when the first terminal detects that the cross-device transmission condition is met, the navigation data of the navigation task that has been turned on is automatically obtained from the first navigation application through the first navigation flow module local to the first terminal, and the navigation synchronization information corresponding to the navigation data is generated through the first navigation flow module, and the navigation synchronization information is sent to the second terminal, so as to realize the cross-device transmission of the navigation data. After receiving the above navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through the local second navigation flow module, and then the second terminal can update the navigation task of the second navigation application according to the navigation synchronization information, so as to realize the synchronization of the navigation tasks across devices. Compared with the existing navigation technology, the present application can realize the synchronization of the navigation tasks across devices. In the scenario where the cross-device navigation is required, the user does not need to set the task for the navigation application of the terminal multiple times, but can automatically realize the flow of navigation data through the navigation flow module to update the navigation task in the navigation application, thereby greatly improving the efficiency of setting the navigation task and reducing the repeated operations of the user. On the other hand, after the first navigation flow module in the first terminal obtains the navigation data from the first navigation application, it does not directly send the navigation data to the second navigation flow module of the second terminal, but converts the navigation data into corresponding navigation synchronization information. The navigation synchronization information can be transmitted in the navigation flow modules of different terminals, and then transmitted to the second navigation application through the second navigation flow module. It is not a direct transmission between the navigation applications in the two terminals. Therefore, there is no need to install the same navigation application on the first terminal and the second terminal. Navigation data flow across devices and applications can be realized, further improving the application scope of navigation task synchronization.

[0016] In a possible implementation manner of the first aspect, if the first terminal meets a preset cross-device transmission condition, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0017] The second terminal sends a communication tag to the first terminal through a second near field communication module in response to a touch operation between the second terminal and the first terminal; the communication tag carries a start mark of navigation task synchronization;

[0018] The first terminal starts the first navigation flow module in response to the communication tag, and obtains the navigation data from the first navigation application through the first navigation flow module.

[0019] In a possible implementation manner of the first aspect, before the second terminal sends the communication tag to the first terminal through the second near field communication module in response to the touch operation between the second terminal and the first terminal, the method further includes:

[0020] If the second terminal meets the preset tag writing condition, the second terminal sends a tag writing request to the tag service thread through the second navigation flow module;

[0021] The second terminal responds to the tag writing request through the tag service thread, adds the startup identifier to the communication tag, and writes the communication tag to the second near field communication module.

[0022] In a possible implementation of the first aspect, the second terminal is a vehicle intelligent control terminal installed on a vehicle; the first terminal is a user terminal carried by a user;

[0023] Correspondingly, if the first terminal meets the preset cross-device transmission condition, before obtaining the navigation data from the first navigation application through the first navigation flow module, the method further includes:

[0024] If the second terminal detects a door opening event of the vehicle, a communication connection is established with the first terminal;

[0025] The second terminal obtains a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtains a setting state of a second navigation flow module;

[0026] If the second navigation transfer module is in the activated state, the second terminal sends a navigation transfer notification to the first terminal, so that the first terminal sends the navigation synchronization information.

[0027] In a possible implementation manner of the first aspect, if the first terminal meets a preset cross-device transmission condition, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0028] The first terminal receives the navigation flow notification sent by the second terminal;

[0029] In response to the navigation flow notification, the first terminal obtains navigation data from the first navigation application through the first navigation flow module.

[0030] In a possible implementation of the first aspect, if the second terminal detects a door opening event of the vehicle, establishing a communication connection with the first terminal includes:

[0031] The second terminal identifies the connection status of each registered terminal in a preset registered device list through a second navigation flow module;

[0032] If the second terminal recognizes that the first terminal is in the registered device list and the connection state of the first terminal is a connectable state, then the second terminal establishes the communication connection with the first terminal based on the connection information associated with the first terminal in the registered device list;

[0033] If the second terminal recognizes that the first terminal is not in the registered device list, or the first terminal is in the registered device list and the connection state of the first terminal is unconnectable, sending a wake-up instruction to the first terminal through a second near field communication module;

[0034] Receiving a wake-up instruction sent by the second terminal through the second near field communication module. The first terminal receives a wake-up instruction sent by the second terminal through the second near field communication module;

[0035] In response to the wake-up instruction, the first terminal sends a wireless connection request to the second terminal to establish the communication connection with the second terminal.

[0036] In a possible implementation of the first aspect, the second terminal is a user terminal carried by a user; the first terminal is a vehicle intelligent control terminal installed on a vehicle;

[0037] Correspondingly, if the first terminal meets the preset cross-device transmission condition, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0038] If the first terminal detects a parking event related to the vehicle, a communication connection is established with the second terminal; the near field communication connection is used to send navigation synchronization information to the second terminal;

[0039] The first terminal obtains a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtains a setting state of the first navigation flow module;

[0040] If the first terminal recognizes that the first navigation flow module is in the activated state, the first terminal acquires navigation data from the first navigation application through the first navigation flow module.

[0041] In a possible implementation of the first aspect, if the first terminal detects a parking event related to the vehicle, establishing a communication connection with the second terminal includes:

[0042] The first terminal identifies the connection status of each registered terminal in a preset registered device list through the first navigation flow module;

[0043] If the first terminal recognizes that the second terminal is in the registered device list and the connection state of the second terminal is a connectable state, then the first terminal establishes the near field communication connection with the second terminal based on the connection information associated with the second terminal in the registered device list;

[0044] If the first terminal recognizes that the second terminal is not in the registered device list, or the second terminal is in the registered device list and the connection state of the second terminal is an unconnectable state, sending a wake-up instruction to the second terminal through the first near field communication module;

[0045] In response to the wake-up instruction, the second terminal sends a near field connection request to the first terminal to establish a near field communication connection with the first terminal.

[0046] In a possible implementation manner of the first aspect, the second terminal receives the navigation synchronization information sent by the first terminal, and transmits the navigation synchronization information to a second navigation application through a second navigation flow module, including:

[0047] The second terminal caches the navigation synchronization information in a cache area through the second navigation flow module, and detects a heartbeat signal of the communication connection with the first terminal;

[0048] If the second terminal does not receive the heartbeat signal within a preset effective time, it recognizes that the near field communication connection with the first terminal is disconnected, and transmits the navigation synchronization information to the second navigation application.

[0049] In a possible implementation manner of the first aspect, if the first terminal meets a preset cross-device transmission condition, before obtaining navigation data from the first navigation application through the first navigation flow module, the method further includes:

[0050] The first terminal generates a navigation task through the first navigation application in response to a navigation operation of a user; and the navigation data is generated based on the navigation task;

[0051] The first terminal receives, through the first navigation transfer module, a service registration instruction transmitted by the first navigation application; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices;

[0052] In response to the service registration instruction, the first terminal adds the first navigation application to the navigation synchronization application list and sets the first navigation flow module to a startup state; the startup state is used to send navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission condition is met.

[0053] In a possible implementation manner of the first aspect, after the second terminal receives the navigation synchronization information sent by the first terminal, transmits the navigation synchronization information to the second navigation application through the second navigation flow module, and updates the navigation task of the second navigation application according to the navigation synchronization information, the method further includes:

[0054] The second terminal sends navigation synchronization completion information to the first terminal through the second navigation flow module;

[0055] In response to the navigation synchronization completion information, the first terminal transmits an end instruction of the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0056] In a possible implementation manner of the first aspect, before the second terminal receives the navigation synchronization information sent by the first terminal, the method further includes:

[0057] The first terminal acquires a navigation application list of the second terminal; the navigation application list includes the second navigation application;

[0058] If the first terminal detects that there is a navigation application matching the first navigation application in the navigation application list, the navigation synchronization information is sent to the second terminal; the navigation application matching the first navigation application is specifically: an application that has the permission to transmit navigation data across devices with the first navigation application.

[0059] In a possible implementation manner of the first aspect, after the second terminal receives the navigation synchronization information sent by the first terminal, the method includes:

[0060] The second terminal detects whether there is a navigation application matching the first navigation application in the navigation application list;

[0061] If the second terminal detects that a navigation application that matches the first navigation application exists in the navigation application list, the navigation application that matches the first navigation application will be used as the second navigation application, and the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module will be performed; the navigation application that matches the first navigation application is specifically: an application that has the authority to transmit navigation data across devices with the second navigation application.

[0062] In a possible implementation manner of the first aspect, the second terminal updates the navigation task of the second navigation application according to the navigation synchronization information, including:

[0063] The second terminal determines a navigation destination based on the navigation synchronization information, and generates task update prompt information based on the navigation destination;

[0064] If the second terminal receives an update confirmation instruction based on the update prompt information feedback, the second terminal updates the navigation task based on the navigation destination.

[0065] In a second aspect, the present application provides a method for synchronizing navigation tasks across devices, which is applied to a first terminal and includes:

[0066] If the preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module;

[0067] Generate navigation synchronization information corresponding to the navigation data by the first navigation flow module;

[0068] The navigation synchronization information is sent to a second terminal, where the navigation synchronization information is used to update a navigation task of a second navigation application in the second terminal.

[0069] In this implementation, after the first terminal sends navigation synchronization information to the second terminal, the process of the second terminal updating the navigation task based on the navigation synchronization information is specifically as follows: the second terminal transmits the received navigation synchronization information to the second navigation application through the second navigation flow module, and updates the navigation task of the second navigation application according to the navigation synchronization information.

[0070] In a possible implementation of the second aspect, if a preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0071] In response to a touch operation with the second terminal, receiving a communication tag sent by a second near field communication module of the second terminal; the communication tag carries a start mark of navigation task synchronization;

[0072] In response to the communication tag, the first navigation flow module is started, and the navigation data is obtained from the first navigation application through the first navigation flow module.

[0073] In a possible implementation of the second aspect, the communication tag is obtained after the second terminal detects that the tag writing condition is met, sends a tag write request to the tag service thread through the second navigation flow module, responds to the tag write request through the tag service thread, adds the start identifier to the communication tag, and writes the communication tag to the second near-field communication module.

[0074] In a possible implementation of the second aspect, if a preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0075] receiving a navigation transfer notification sent by the second terminal; the navigation transfer notification is sent to the first terminal when the second terminal detects that the second navigation transfer module of the second terminal is in an activated state after the second terminal is connected to the first terminal;

[0076] In response to the navigation flow notification, navigation data is obtained from the first navigation application through the first navigation flow module.

[0077] In a possible implementation manner of the second aspect, before the receiving the navigation flow transfer notification sent by the second terminal, the method further includes:

[0078] Receiving a wake-up instruction sent by the second terminal through the second near field communication module;

[0079] In response to the wake-up instruction, a wireless connection request is sent to the second terminal to establish the communication connection with the second terminal.

[0080] In a possible implementation of the second aspect, the first terminal is a vehicle intelligent control terminal installed on a vehicle; the second terminal is a user terminal carried by a user;

[0081] Correspondingly, if the preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0082] If a parking event related to the vehicle is detected, a near field communication connection is established with the second terminal; the near field communication connection is used to send navigation synchronization information to the second terminal;

[0083] Obtaining a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtaining a setting state of the first navigation flow module;

[0084] If the first navigation flow module is in the activated state, the navigation data is obtained from the first navigation application through the first navigation flow module.

[0085] In a possible implementation manner of the second aspect, if a parking event related to the vehicle is detected, establishing a near field communication connection with the second terminal includes:

[0086] Identifying the connection status of each registered terminal in a preset registered device list through the second navigation flow module;

[0087] If the second terminal is in the registered device list and the connection state of the second terminal is a connectable state, establishing the near field communication connection with the second terminal based on the connection information associated with the second terminal in the registered device list;

[0088] If the second terminal is not in the registered device list, or the second terminal is in the registered device list and the connection state of the second terminal is an unconnectable state, a wake-up instruction is sent to the second terminal through the first near-field communication module, and the wake-up instruction is used to enable the second terminal to establish a communication connection with the first terminal.

[0089] In this implementation, after receiving the wake-up instruction sent by the first terminal, the second terminal establishes the communication connection with the first terminal in response to the wake-up instruction.

[0090] In a possible implementation manner of the second aspect, before acquiring navigation data from the first navigation application by the first navigation flow module if the preset cross-device transmission condition is met, the method further includes:

[0091] In response to a navigation operation of a user, generating a navigation task through the first navigation application; the navigation data is generated based on the navigation task;

[0092] receiving, through the first navigation transfer module, a service registration instruction transmitted by the first navigation application; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices;

[0093] In response to the service registration instruction, the first navigation application is added to the navigation synchronization application list, and the first navigation flow module is set to a startup state; the startup state is used to send navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission condition is met.

[0094] In a possible implementation manner of the second aspect, after sending the navigation synchronization information to the second terminal, the method further includes:

[0095] receiving navigation synchronization completion information fed back by the second terminal through the second navigation flow module;

[0096] In response to the navigation synchronization completion information, an end instruction regarding the navigation task is transmitted to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0097] In a possible implementation manner of the second aspect, before sending the navigation synchronization information to the second terminal, the method further includes:

[0098] Acquire a navigation application list of the second terminal; the navigation application list includes the second navigation application;

[0099] If the navigation application list contains a navigation application that matches the first navigation application, the navigation synchronization information is sent to the second terminal; the navigation application that matches the first navigation application is specifically an application that has permission to transmit navigation data across devices with the first navigation application.

[0100] In a third aspect, an embodiment of the present application provides a synchronization device for navigation tasks across devices, including:

[0101] A navigation data acquisition unit, configured to acquire navigation data from a first navigation application through a first navigation flow module if a preset cross-device transmission condition is met;

[0102] a navigation synchronization information generating unit, configured to generate navigation synchronization information corresponding to the navigation data through the first navigation flow module;

[0103] The navigation synchronization information sending unit is used to send the navigation synchronization information to the second terminal, where the navigation synchronization information is used to update the navigation task of the second navigation application in the second terminal.

[0104] In a possible implementation manner of the third aspect, the navigation data acquiring unit includes:

[0105] a communication tag receiving unit, configured to receive a communication tag sent by a second near field communication module of the second terminal in response to a touch operation with the second terminal; the communication tag carries a start mark for navigation task synchronization;

[0106] The navigation flow module starting unit is used to start the first navigation flow module in response to the communication tag, and obtain the navigation data from the first navigation application through the first navigation flow module.

[0107] In a possible implementation of the third aspect, the communication tag is obtained after the second terminal detects that the tag writing condition is met, sends a tag write request to the tag service thread through the second navigation flow module, responds to the tag write request through the tag service thread, adds the start identifier to the communication tag, and writes the communication tag to the second near-field communication module.

[0108] In a possible implementation manner of the third aspect, the navigation data acquiring unit includes:

[0109] a navigation transfer notification receiving unit, configured to receive a navigation transfer notification sent by the second terminal; the navigation transfer notification is sent to the first terminal when the second terminal detects that the second navigation transfer module of the second terminal is in an activated state after the second terminal is connected to the first terminal;

[0110] The navigation flow notification response unit is used to obtain navigation data from the first navigation application through the first navigation flow module in response to the navigation flow notification.

[0111] In a possible implementation manner of the third aspect, the navigation task synchronization device further includes:

[0112] A wake-up instruction receiving unit, configured to receive a wake-up instruction sent by the second terminal via the second near field communication module;

[0113] The wake-up instruction corresponding unit is used to send a wireless connection request to the second terminal in response to the wake-up instruction to establish the communication connection with the second terminal.

[0114] In a possible implementation of the third aspect, the first terminal is a vehicle intelligent control terminal installed on a vehicle; the second terminal is a user terminal carried by a user;

[0115] Correspondingly, the navigation data acquisition unit includes:

[0116] a parking door opening trigger unit, configured to establish a near field communication connection with the second terminal if a parking event related to the vehicle is detected; the near field communication connection is used to send navigation synchronization information to the second terminal;

[0117] A first state identification unit, configured to obtain a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtain a setting state of the first navigation flow module;

[0118] The first startup state response unit is configured to obtain navigation data from the first navigation application through the first navigation flow module if the first navigation flow module is in the startup state.

[0119] In a possible implementation of the third aspect, the parking door opening triggering unit includes:

[0120] A connection status detection unit, configured to identify the connection status of each registered terminal in a preset registered device list through the second navigation flow module;

[0121] a direct connection triggering unit, configured to establish the near field communication connection with the second terminal based on the connection information associated with the second terminal in the registered device list if the second terminal is in the registered device list and the connection state of the second terminal is a connectable state;

[0122] A wake-up instruction sending unit is used to send a wake-up instruction to the second terminal through the first near-field communication module if the second terminal is not in the registered device list, or the second terminal is in the registered device list and the connection state of the second terminal is an unconnectable state, wherein the wake-up instruction is used to enable the second terminal to establish the communication connection with the first terminal.

[0123] In a possible implementation manner of the third aspect, the navigation task synchronization device further includes:

[0124] A navigation operation response unit, configured to generate a navigation task through the first navigation application in response to a user's navigation operation; the navigation data is generated based on the navigation task;

[0125] A service registration unit, configured to receive a service registration instruction transmitted by the first navigation application through the first navigation flow module; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices;

[0126] A service registration response unit is used to respond to the service registration instruction, add the first navigation application to the navigation synchronization application list, and set the first navigation flow module to a startup state; the startup state is used to send the navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission condition is met.

[0127] In a possible implementation manner of the third aspect, the navigation task synchronization device further includes:

[0128] A navigation synchronization completion information receiving unit, configured to receive navigation synchronization completion information fed back by the second terminal through the second navigation flow module;

[0129] A navigation ending unit is used to transmit an ending instruction about the navigation task to the first navigation application through the first navigation flow module in response to the navigation synchronization completion information, so as to stop the navigation task of the first navigation application.

[0130] In a possible implementation manner of the third aspect, the navigation task synchronization device further includes:

[0131] A navigation application list acquiring unit, configured to acquire a navigation application list of the second terminal; the navigation application list includes the second navigation application;

[0132] A navigation application matching unit is used to send the navigation synchronization information to the second terminal if a navigation application matching the first navigation application exists in the navigation application list; the navigation application matching the first navigation application is specifically: an application that has the permission to transmit navigation data across devices with the first navigation application.

[0133] In a fourth aspect, an embodiment of the present application provides a method for synchronizing navigation tasks across devices, which is applied to a second terminal and includes:

[0134] Receiving navigation synchronization information sent by a first terminal; the navigation synchronization information is generated based on navigation data of a first navigation application in the first terminal;

[0135] transmitting the navigation synchronization information to the second navigation application through the second navigation flow module;

[0136] The navigation task of the second navigation application is updated based on the navigation synchronization information.

[0137] In a possible implementation manner of the fourth aspect, the receiving navigation synchronization information sent by the first terminal includes:

[0138] In response to a touch operation with the first terminal, a communication tag is sent to the first terminal through a second near field communication module, so that the first terminal responds to the communication tag, starts a first navigation flow module, and obtains the navigation data from the first navigation application through the first navigation flow module; the communication tag carries a start mark of navigation task synchronization;

[0139] The navigation synchronization information is received, which is sent by the first terminal through the first navigation flow module.

[0140] In a possible implementation manner of the fourth aspect, before sending the communication tag to the first terminal through the second near field communication module in response to the touch operation with the first terminal, the method further includes:

[0141] If the preset tag writing condition is met, sending a tag writing request to the tag service thread through the second navigation flow module;

[0142] The tag service thread responds to the tag write request, adds the start identifier to the communication tag, and writes the communication tag to the second near field communication module.

[0143] In a possible implementation of the fourth aspect, the second terminal is a vehicle intelligent control terminal installed on the vehicle;

[0144] Correspondingly, before receiving the navigation synchronization information sent by the first terminal, the method further includes:

[0145] If a door opening event of the vehicle is detected, establishing a communication connection with the first terminal;

[0146] Obtaining a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtaining a setting state of the second navigation flow module;

[0147] If the second navigation flow module is in the activated state, a navigation flow notification is sent to the first terminal, so that the first terminal sends the navigation synchronization information.

[0148] In a possible implementation manner of the fourth aspect, if a door opening event of the vehicle is detected, establishing a communication connection with the first terminal includes:

[0149] Identifying the connection status of each registered terminal in a preset registered device list through the second navigation flow module;

[0150] If the first terminal is in the registered device list and the connection state of the first terminal is a connectable state, establishing the communication connection with the first terminal based on the connection information associated with the first terminal in the registered device list;

[0151] If the first terminal is not in the registered device list, or the first terminal is in the registered device list and the connection state of the first terminal is an unconnectable state, a wake-up instruction is sent to the first terminal through the second near-field communication module, and the wake-up instruction is used to enable the first terminal to establish the near-field communication connection with the second terminal.

[0152] In this implementation, after receiving the wake-up instruction sent by the second terminal, the first terminal will establish the near field communication connection with the second terminal in response to the wake-up instruction.

[0153] In a possible implementation of the fourth aspect, the second terminal is a user terminal carried by a user; the first terminal is a vehicle intelligent control terminal installed on a vehicle;

[0154] Correspondingly, the transmitting the navigation synchronization information to the second navigation application through the second navigation flow module includes:

[0155] caching the navigation synchronization information in a cache area through the second navigation flow module, and detecting a heartbeat signal of a communication connection with the first terminal;

[0156] If the heartbeat signal is not received within the preset effective time, it is recognized that the near field communication connection with the first terminal is disconnected, and the navigation synchronization information is transmitted to the second navigation application.

[0157] In a possible implementation manner of the fourth aspect, after the receiving the navigation synchronization information sent by the first terminal, the method further includes:

[0158] Detecting whether there is a navigation application matching the first navigation application in a navigation application list; the navigation application list includes the first navigation application;

[0159] If it is detected that there is a navigation application matching the first navigation application in the navigation application list, the navigation application matching the first navigation application will be used as the second navigation application, and the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module will be performed; the navigation application matching the first navigation application is specifically: an application that has the permission to transmit navigation data across devices with the second navigation application.

[0160] In a possible implementation manner of the fourth aspect, the updating the navigation task of the second navigation application based on the navigation synchronization information includes:

[0161] determining a navigation destination based on the navigation synchronization information, and generating task update prompt information based on the navigation destination;

[0162] If an update confirmation instruction based on the update prompt information feedback is received, the navigation task is updated based on the navigation destination.

[0163] In a possible implementation manner of the fourth aspect, after updating the navigation task of the second navigation application based on the navigation synchronization information, the method further includes:

[0164] Navigation synchronization completion information is sent to the first terminal, so that the first terminal responds to the navigation synchronization completion information and transmits an end instruction of the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0165] In a fifth aspect, an embodiment of the present application provides a synchronization device for navigation tasks across devices, including:

[0166] A navigation synchronization information receiving unit, configured to receive navigation synchronization information sent by a first terminal; the navigation synchronization information is generated based on navigation data of a first navigation application in the first terminal;

[0167] A navigation synchronization information transmission unit, configured to transmit the navigation synchronization information to a second navigation application via a second navigation flow module;

[0168] A navigation task updating unit is used to update the navigation task of the second navigation application based on the navigation synchronization information.

[0169] In a possible implementation manner of the fifth aspect, the navigation synchronization information receiving unit includes:

[0170] a communication tag sending unit door, configured to send a communication tag to the first terminal through a second near field communication module in response to a touch operation with the first terminal, so that the first terminal responds to the communication tag, starts a first navigation flow module, and obtains the navigation data from the first navigation application through the first navigation flow module; the communication tag carries a start mark for synchronizing the navigation task;

[0171] The touch operation feedback unit is used to receive the navigation synchronization information sent by the first terminal through the first navigation flow module.

[0172] In a possible implementation manner of the fifth aspect, the navigation task synchronization device further includes:

[0173] A tag writing request unit, configured to send a tag writing request to the tag service thread through the second navigation flow module if a preset tag writing condition is met;

[0174] A communication tag writing unit is used to respond to the tag writing request through the tag service thread, add the startup identifier to the communication tag, and write the communication tag to the second near field communication module.

[0175] In a possible implementation of the fifth aspect, the second terminal is a vehicle intelligent control terminal installed on the vehicle;

[0176] Correspondingly, the synchronization device of the navigation task also includes:

[0177] a door opening event triggering unit, configured to establish a communication connection with the first terminal if a door opening event related to the vehicle is detected;

[0178] A second state identification unit, configured to obtain a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtain a setting state of the second navigation flow module;

[0179] The second startup state response unit is configured to send a navigation flow notification to the first terminal if the second navigation flow module is in the startup state, so that the first terminal sends the navigation synchronization information.

[0180] In a possible implementation manner of the fifth aspect, the door opening event triggering unit includes:

[0181] A connection status determination unit, configured to identify the connection status of each registered terminal in a preset registered device list through the second navigation flow module;

[0182] a direct connection transmission unit, configured to establish the communication connection with the first terminal based on the connection information associated with the first terminal in the registered device list if the first terminal is in the registered device list and the connection state of the first terminal is a connectable state;

[0183] A wake-up execution unit is used to send a wake-up instruction to the first terminal through a second near-field communication module if the first terminal is not in the registered device list, or the first terminal is in the registered device list and the connection state of the first terminal is an unconnectable state, and the wake-up instruction is used to enable the first terminal to establish the near-field communication connection with the second terminal.

[0184] In a possible implementation of the fifth aspect, the second terminal is a user terminal carried by a user; the first terminal is a vehicle intelligent control terminal installed on a vehicle;

[0185] Correspondingly, the navigation synchronization information transmission unit includes:

[0186] an information caching unit, configured to cache the navigation synchronization information in a cache area through the second navigation flow module, and detect a heartbeat signal of the communication connection with the first terminal;

[0187] The heartbeat signal monitoring unit is used to identify and disconnect the near field communication connection with the first terminal if the heartbeat signal is not received within a preset effective time, and transmit the navigation synchronization information to the second navigation application.

[0188] In a possible implementation manner of the fifth aspect, the navigation task synchronization device further includes:

[0189] a matching application detection unit, configured to detect whether there is a navigation application matching the first navigation application in a navigation application list; the navigation application list includes the first navigation application;

[0190] A second navigation application identification unit is used to, if it is detected that a navigation application matching the first navigation application exists in the navigation application list, use the navigation application matching the first navigation application as the second navigation application, and execute the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module; the navigation application matching the first navigation application is specifically: an application that has the authority to transmit navigation data across devices with the second navigation application.

[0191] In a possible implementation manner of the fifth aspect, the navigation task updating unit includes:

[0192] an update prompt information generating unit, configured to determine a navigation destination based on the navigation synchronization information, and generate task update prompt information based on the navigation destination;

[0193] An update confirmation instruction response unit is used to update the navigation task based on the navigation destination if an update confirmation instruction based on the update prompt information feedback is received.

[0194] In a possible implementation manner of the fifth aspect, the navigation task synchronization device further includes:

[0195] The navigation synchronization completion information sending unit is used to send navigation synchronization completion information to the first terminal, so that the first terminal responds to the navigation synchronization completion information and transmits an end instruction about the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0196] In the sixth aspect, an embodiment of the present application provides an electronic device, a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that when the processor executes the computer program, the method for synchronizing navigation tasks across devices as described in any one of the second aspects above is implemented.

[0197] In the seventh aspect, an embodiment of the present application provides an electronic device, a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that when the processor executes the computer program, the method for synchronizing navigation tasks across devices as described in any one of the fourth aspects above is implemented.

[0198] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and wherein when the computer program is executed by a processor, the method for synchronizing navigation tasks across devices as described in any one of the second aspect or the fourth aspect is implemented.

[0199] In a ninth aspect, an embodiment of the present application provides a computer program product, which, when executed on an electronic device, enables the electronic device to execute the method for synchronizing navigation tasks across devices as described in any one of the second aspect or the fourth aspect.

[0200] In the tenth aspect, an embodiment of the present application provides a chip system, including a processor, which is coupled to a memory, and the processor executes a computer program stored in the memory to implement a method for synchronizing navigation tasks across devices as described in any one of the second aspect or the fourth aspect.

[0201] In an eleventh aspect, an embodiment of the present application provides a cross-device navigation system, including a first terminal and a second terminal;

[0202] The first terminal is configured to obtain navigation data from the first navigation application through the first navigation flow module if a preset cross-device transmission condition is met;

[0203] The first terminal is used to generate navigation synchronization information of the navigation data through the first navigation flow module;

[0204] The second terminal is used to receive the navigation synchronization information sent by the first terminal, and transmit the navigation synchronization information to a second navigation application through a second navigation flow module;

[0205] The second terminal updates the navigation task of the second navigation application according to the navigation synchronization information.

[0206] In a possible implementation of the eleventh aspect, the first terminal is configured to obtain navigation data from the first navigation application through the first navigation flow module if a preset cross-device transmission condition is met, including:

[0207] The second terminal is configured to send a communication tag to the first terminal through a second near field communication module in response to a touch operation between the second terminal and the first terminal; the communication tag carries a start mark for navigation task synchronization;

[0208] The first terminal is used to start the first navigation flow module in response to the communication tag, and obtain the navigation data from the first navigation application through the first navigation flow module.

[0209] In a possible implementation manner of the eleventh aspect, the second terminal is further configured to:

[0210] The second terminal is used to send a tag writing request to the tag service thread through the second navigation flow module if a preset tag writing condition is met;

[0211] The second terminal is used to respond to the tag writing request through the tag service thread, add the startup identifier to the communication tag, and write the communication tag to the second near field communication module.

[0212] In a possible implementation of the eleventh aspect, the second terminal is a vehicle intelligent control terminal installed on a vehicle; the first terminal is a user terminal carried by a user;

[0213] Correspondingly, the second terminal is further used for:

[0214] The second terminal is configured to establish a communication connection with the first terminal if a door opening event of the vehicle is detected;

[0215] The second terminal is used to obtain a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtain a setting state of the second navigation flow module;

[0216] The second terminal is configured to send a navigation flow notification to the first terminal if the second navigation flow module is in an activated state, so that the first terminal sends the navigation synchronization information.

[0217] In a possible implementation of the eleventh aspect, the first terminal is configured to obtain navigation data from the first navigation application through the first navigation flow module if a preset cross-device transmission condition is met, including:

[0218] The first terminal is configured to receive the navigation flow notification sent by the second terminal;

[0219] The first terminal is configured to obtain navigation data from the first navigation application through the first navigation flow module in response to the navigation flow notification.

[0220] In a possible implementation of the eleventh aspect, the second terminal is configured to establish a communication connection with the first terminal if a door opening event of the vehicle is detected, including:

[0221] The second terminal is used to identify the connection status of each registered terminal in the preset registered device list through the second navigation flow module;

[0222] the second terminal being configured to establish the communication connection with the first terminal based on the connection information associated with the first terminal in the registered device list if it is recognized that the first terminal is in the registered device list and the connection state of the first terminal is a connectable state;

[0223] The second terminal is configured to send a wake-up instruction to the first terminal through a second near field communication module if it is recognized that the first terminal is not in the registered device list, or the first terminal is in the registered device list and the connection state of the first terminal is an unconnectable state;

[0224] The first terminal is used to receive a wake-up instruction sent by the second terminal through the second near field communication module;

[0225] The first terminal is used to send a wireless connection request to the second terminal in response to the wake-up instruction, so as to establish the communication connection with the second terminal.

[0226] In a possible implementation of the eleventh aspect, the second terminal is a user terminal carried by a user; the first terminal is a vehicle intelligent control terminal installed on a vehicle;

[0227] Correspondingly, the first terminal is used to obtain navigation data from the first navigation application through the first navigation flow module if the preset cross-device transmission condition is met, including:

[0228] The first terminal is used to establish a communication connection with the second terminal if a parking event related to the vehicle is detected; the near field communication connection is used to send navigation synchronization information to the second terminal;

[0229] The first terminal is used to obtain a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtain a setting state of the first navigation flow module;

[0230] The first terminal is configured to obtain navigation data from the first navigation application through the first navigation flow module if it is recognized that the first navigation flow module is in the activated state.

[0231] In a possible implementation of the eleventh aspect, the first terminal is configured to establish a communication connection with the second terminal if a parking event related to the vehicle is detected, including:

[0232] The first terminal is used to identify the connection status of each registered terminal in a preset registered device list through the first navigation flow module;

[0233] the first terminal being configured to establish the near field communication connection with the second terminal based on the connection information associated with the second terminal in the registered device list if it is recognized that the second terminal is in the registered device list and the connection state of the second terminal is a connectable state;

[0234] The first terminal is configured to send a wake-up instruction to the second terminal through the first near field communication module if it is recognized that the second terminal is not in the registered device list, or the second terminal is in the registered device list and the connection state of the second terminal is an unconnectable state;

[0235] The second terminal is configured to send a near field connection request to the first terminal in response to the wake-up instruction, so as to establish a near field communication connection with the first terminal.

[0236] In a possible implementation manner of the eleventh aspect, the second terminal is configured to receive the navigation synchronization information sent by the first terminal, and transmit the navigation synchronization information to the second navigation application through a second navigation flow module, including:

[0237] The second terminal is configured to cache the navigation synchronization information in a cache area through the second navigation flow module, and detect a heartbeat signal of the communication connection with the first terminal;

[0238] The second terminal is used to identify and disconnect the near field communication connection with the first terminal if the heartbeat signal is not received within a preset effective time, and transmit the navigation synchronization information to the second navigation application.

[0239] In a possible implementation manner of the eleventh aspect, the first terminal is further configured to:

[0240] The first terminal is used to generate a navigation task through the first navigation application in response to a navigation operation of a user; the navigation data is generated based on the navigation task;

[0241] The first terminal is used to receive a service registration instruction transmitted by the first navigation application through the first navigation flow module; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices;

[0242] The first terminal is used to respond to the service registration instruction, add the first navigation application to the navigation synchronization application list, and set the first navigation flow module to the startup state; the startup state is used to send the navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission condition is met.

[0243] In a possible implementation manner of the eleventh aspect, the first terminal and the second terminal are further configured to:

[0244] The second terminal is used to send navigation synchronization completion information to the first terminal through the second navigation flow module;

[0245] The first terminal is used for transmitting an end instruction of the navigation task to the first navigation application through the first navigation flow module in response to the navigation synchronization completion information, so as to stop the navigation task of the first navigation application.

[0246] In a possible implementation manner of the eleventh aspect, before the second terminal receives the navigation synchronization information sent by the first terminal, the method further includes:

[0247] The first terminal is used to obtain a navigation application list of the second terminal; the navigation application list includes the second navigation application;

[0248] The first terminal is used to send the navigation synchronization information to the second terminal if it is detected that there is a navigation application matching the first navigation application in the navigation application list; the navigation application matching the first navigation application is specifically: an application that has the authority to transmit navigation data across devices with the first navigation application.

[0249] In a possible implementation manner of the eleventh aspect, the second terminal is further configured to:

[0250] The second terminal is used to detect whether there is a navigation application matching the first navigation application in the navigation application list;

[0251] The second terminal is used to, if it is detected that a navigation application matching the first navigation application exists in the navigation application list, use the navigation application matching the first navigation application as the second navigation application, and execute the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module; the navigation application matching the first navigation application is specifically: an application that has the authority to transmit navigation data across devices with the second navigation application.

[0252] In a possible implementation manner of the eleventh aspect, the second terminal updates the navigation task of the second navigation application according to the navigation synchronization information, including:

[0253] The second terminal is used to determine a navigation destination based on the navigation synchronization information, and generate task update prompt information based on the navigation destination;

[0254] The second terminal is configured to update the navigation task based on the navigation destination if an update confirmation instruction based on the update prompt information feedback is received.

[0255] It can be understood that the beneficial effects of the second to eleventh aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0256] Figure 1 is a schematic diagram of a navigation route provided by an embodiment of the present application;

[0257] Figure 2 is an interactive flow chart of a method for synchronizing navigation tasks across devices provided by an embodiment of the present application;

[0258] FIG3( a ) is a schematic diagram of a scenario of transmitting navigation data across devices provided by an embodiment of the present application;

[0259] FIG. 3( b ) is a schematic diagram of a scenario of transmitting navigation data across devices provided by another embodiment of the present application.

[0260] Figure 4a is a schematic diagram of initiating a navigation task provided by an embodiment of the present application;

[0261] Figure 4b is a schematic diagram of initiating a navigation task provided by another embodiment of the present application;

[0262] Figure 4cis a schematic diagram of initiating a navigation task provided by another embodiment of the present application;

[0263] Figure 5 is a schematic diagram of setting a state switch of a first navigation flow module provided in an embodiment of the present application;

[0264] Figure 6 This is a schematic diagram of a prompt for installing an application on a second terminal provided by an embodiment of the present application;

[0265] Figure 7 is a schematic diagram of changing a navigation task provided by an embodiment of the present application;

[0266] Figure 8 is a schematic diagram of updating a navigation task provided by an embodiment of the present application;

[0267] Fig. 9 is a schematic diagram of ending a navigation task provided by an embodiment of the present application;

[0268] Fig.10 This is a schematic diagram of a response to a synchronization failure provided by an embodiment of the present application;

[0269] Fig.11 This is an interactive schematic diagram of a method for synchronizing navigation tasks across devices provided by an embodiment of the present application;

[0270] Fig.12 This is a schematic diagram of a touch scene between a vehicle-mounted terminal and a smart phone provided in an embodiment of the present application;

[0271] Fig.13 is an interactive schematic diagram of a navigation task synchronization method provided by an embodiment of the present application;

[0272] Fig.14 is a schematic diagram of an interface of a vehicle-mounted terminal provided in an embodiment of the present application;

[0273] Fig.15 This is a flow chart of the three-party interaction between the user terminal, the vehicle terminal and the server provided in one embodiment of the present application;

[0274] Fig.16 is an interactive schematic diagram of a navigation task synchronization method provided by an embodiment of the present application;

[0275] Fig.17 is a flowchart of a method for synchronizing navigation data across devices performed by a first terminal according to an embodiment of the present application;

[0276] Fig.18 is a flowchart of a method for synchronizing navigation data across devices performed by a second terminal provided in an embodiment of the present application;

[0277] Fig.19It is a structural block diagram of a synchronization device for navigation tasks across devices provided in an embodiment of the present application;

[0278] Fig. 20 It is a structural block diagram of a synchronization device for navigation tasks across devices provided in an embodiment of the present application;

[0279] Fig.21 It is a structural schematic diagram of the terminal device provided in the embodiment of the present application;

[0280] Fig. 22 is a software structure block diagram of a terminal device in an embodiment of the present application;

[0281] Fig.23 It is a structural block diagram of a terminal device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0282] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0283] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0284] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0285] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0286] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0287] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0288] With the continuous development of navigation technology, the applicable scenarios of navigation applications are becoming more and more extensive, covering all aspects of people's lives and work. However, as the applicable scenarios of navigation technology continue to expand, the complexity of the scenarios is also increasing. In the same navigation route, different navigation scenarios may include walking, cycling, driving, public transportation, etc. In different scenarios, different terminal navigation applications are often required for navigation. For example, in the walking navigation scenario, users may use the navigation application in the smartphone for navigation; in the driving navigation scenario, users may use the navigation application in the vehicle terminal to complete the navigation.

[0289] Exemplarily, take a navigation task as an example: when a user is traveling, if he needs to go to a tourist attraction, he can enter the corresponding destination in the navigation application in any terminal. The navigation application can generate a corresponding navigation task based on the navigation destination and the initial location, and instruct the user to move to the navigation destination in real time. Figure 1 FIG. 1 is a schematic diagram showing a navigation route provided by an embodiment of the present application. Figure 1 As shown, the starting point of the navigation route is home, and the destination is a tourist attraction. The navigation route includes sidewalks, roads, and highways. In the sidewalk sections of the navigation route, i.e., Section A and Section C, the user needs to walk; and in the road and highway sections, i.e., Section B, the user needs to drive. Therefore, during the entire navigation process, the user can first enter the destination, i.e., the tourist attraction, in the navigation application in the portable smartphone, and then complete the journey of Section A. Then, when the user completes Section A and enters Section B, the user can switch from walking to driving to complete the journey of Section B. Therefore, the user can navigate Section B through the navigation application in the vehicle-mounted terminal in the vehicle. In this case, the user needs to re-enter the destination in the navigation application of the vehicle-mounted terminal; finally, when the user completes Section B and enters Section C, the user needs to switch from driving to walking again. At this time, the user needs to re-enter the destination on the smartphone.

[0290] It can be seen from this that when a navigation task includes multiple navigation scenarios, if different navigation scenarios use different terminals to complete navigation, the user needs to enter the navigation destination multiple times on different terminals during the entire navigation task, which causes the user to perform multiple repeated navigation task setting operations, reducing navigation efficiency.

[0291] Embodiment 1:

[0292] Therefore, in order to solve the defects of the existing cross-device navigation task synchronization technology, the present application provides a cross-device navigation task synchronization method. The executors of the cross-device navigation task synchronization method can specifically be two terminal devices, namely a first terminal and a second terminal. The terminal device can be a smart phone, a vehicle intelligent control terminal installed on a vehicle (referred to as a vehicle-mounted terminal), a tablet computer, a smart watch, a smart bracelet and other electronic devices. A navigation application is installed in the terminal device, and the navigation task initiated by the user can be executed through the navigation application.

[0293] It should be noted that the first terminal and the second terminal can be terminals of the same type, for example, the first terminal is a smart phone and the second terminal is also a smart phone; of course, the first terminal and the second terminal can also be terminals of different types, for example, the first terminal is a smart phone and the second terminal is a vehicle-mounted terminal, or the first terminal can be a vehicle-mounted terminal and the second terminal is a smart phone. There is no restriction on the terminal types of the first terminal and the second terminal, and the appropriate terminal type can be selected according to the actual navigation scenario.

[0294] Figure 2 The following is an interactive flow chart of a method for synchronizing navigation tasks across devices provided by an embodiment of the present application, which is described in detail as follows:

[0295] In S201, if the first terminal meets the preset cross-device transmission condition, the first terminal obtains navigation data from the first navigation application through the first navigation flow module.

[0296] In this embodiment, the first terminal may be configured with a corresponding cross-device transmission condition, which is used to notify the first terminal that the navigation task of the local first navigation application needs to be synchronized to other terminals (the second terminal in this embodiment). For example, the first terminal may store a list of devices for transmitting navigation data across devices. If the first terminal searches for the wireless signal of any registered terminal in the above device list, it will identify that the cross-device transmission condition is met and execute the operation of S201; for another example, the first terminal may be configured with a corresponding trigger gesture for cross-device transmission. When the first terminal detects that the touch operation initiated by the user matches the preset trigger gesture, it will identify that the cross-device transmission condition is met and execute the operation of S201. The specific cross-device transmission condition can be configured according to the actual usage and the terminal type corresponding to the first terminal. It should be noted that the number of the above cross-device transmission conditions can be one or more.

[0297] Exemplarily, FIG3(a) shows a schematic diagram of a scenario for transmitting navigation data across devices provided by an embodiment of the present application. Referring to FIG3(a), a user holds a smart phone, and there is a vehicle equipped with a vehicle-mounted terminal within the surrounding area of ​​the smart phone. The navigation application (i.e., the first navigation application) is started in the foreground of the smart phone. In this case, the user can initiate a sliding operation in the operation interface corresponding to the navigation application in the direction of the vehicle-mounted terminal, i.e., a sliding track 31, wherein the sliding operation is a pre-set trigger for transmitting navigation data across devices. Therefore, when the smart phone detects that the user has initiated the above-mentioned long sliding operation, it determines that the preset cross-device transmission conditions are met and executes the operation of S201.

[0298] For another example, the scenario of the first terminal includes multiple terminals that can realize cross-device transmission. Figure 3(b) shows a schematic diagram of the scenario of cross-device transmission of navigation data provided by an embodiment of the present application. As shown in Figure 3(b), in this scenario, the user holds a smart phone, and there are multiple vehicles equipped with vehicle-mounted terminals within the surrounding range of the smart phone, that is, there are multiple second terminals. In this case, the second terminal that the first terminal needs to synchronize the navigation task can be determined in any of the following three ways, which are:

[0299] Method 1: Configure different cross-device transmission conditions for different second terminals. For example, the first terminal can configure different trigger gestures for different second terminals. As shown in Figure 3(b), the trigger gesture corresponding to the vehicle-mounted terminal in vehicle A is a left swipe; the trigger gesture corresponding to the vehicle-mounted terminal in vehicle B is an upward swipe; and the trigger gesture corresponding to the vehicle-mounted terminal in vehicle C is a right swipe. Based on this, the first terminal can obtain the sliding operation initiated by the user on the smartphone, and determine the second terminal required to synchronize the navigation task according to the trigger gesture matching the sliding operation. For example, in this embodiment, if the user initiates a long upward swipe, the first terminal can use the vehicle terminal in vehicle B as the second terminal for synchronization of the required navigation task.

[0300] Method 2: Determine the second terminal required for navigation task synchronization based on the relative position between each second terminal and the first terminal. The first terminal can obtain the relative position relationship with each second terminal through the signal strength of the wireless signal or the distance sensor, and determine the second terminal for navigation task synchronization based on the above relative position relationship. The relative position relationship can be the distance and orientation between each second terminal. For example, the first terminal can obtain the distance between each second terminal and select the second terminal closest to it as the second terminal for navigation task synchronization. For example, the distance between the smartphone and the vehicle-mounted terminal in vehicle A is 2m, the distance between the smartphone and the vehicle-mounted terminal in vehicle B is 1m, and the distance between the smartphone and the vehicle-mounted terminal in vehicle C is 1.5m. In this case, the first terminal can also use the vehicle-mounted terminal in vehicle B as the second terminal for navigation task synchronization.

[0301] Method 3: Determine the second terminal required for navigation task synchronization according to the priority order set by default. The first terminal has pre-configured corresponding synchronization priorities for each second terminal. If multiple second terminals are detected within the range at the same time, the second terminal with the highest synchronization priority can be selected as the second terminal required for synchronization according to the corresponding synchronization priority. By way of example, Table 1 shows a correspondence table in which the first terminal pre-stores synchronization priorities. As shown in Table 1, the synchronization priority corresponding to the on-board terminal in vehicle A is 1, the synchronization priority corresponding to the on-board terminal in vehicle B is 2, and the synchronization priority corresponding to the on-board terminal in vehicle C is 3. In this case, if the smartphone searches for the above three on-board terminals at the same time, in this case, since the synchronization priority of the on-board terminal of vehicle A is the highest, the on-board terminal of vehicle A is used as the second terminal for navigation task synchronization.

[0302] Terminal identification Synchronization priority Vehicle A 1 Vehicle B 2 Vehicle C 3 … …

[0303] Table 1

[0304] In this embodiment, the first terminal is configured with a first navigation transfer module and is installed with at least one first navigation application that can implement navigation tasks. The first navigation application is specifically an application running in the application layer of the first terminal, and the first navigation application can respond to navigation tasks initiated by the user. The first navigation transfer module is specifically used to synchronize navigation tasks across devices, and the transmission operation includes obtaining navigation data from the first navigation application in the first terminal.

[0305] In this embodiment, the first terminal can obtain navigation data related to the navigation task from the first navigation application through the first navigation flow module. For example, the navigation data includes but is not limited to: the navigation destination, navigation starting point, en route locations, navigation route rules, and current location of the navigation task. Among them, the key en route locations are specifically: between the navigation starting point and the navigation destination, the user can set one or more en route locations, and the generated navigation route will start from the above navigation starting point and end at the above navigation destination, and pass through various en route locations; among them, the navigation route rules are specifically used to determine the user preferences when generating the navigation route, such as "highway priority", "least congested road section" or "lowest cost" and other different preferences, so that the navigation application can generate the corresponding navigation route according to the user preferences and real-time traffic conditions.

[0306] In a possible implementation, the first navigation flow module may be a background program running in the application layer of the first terminal. In this case, the first navigation flow module may obtain permission to obtain navigation data from the first navigation application in the application layer, and when it is detected that the cross-device transmission condition is met, the corresponding navigation data may be obtained from the first navigation application based on the permission.

[0307] In one possible implementation, the first navigation flow module may also run in the application framework layer of the first terminal, and may provide the first navigation application with an application programming interface (API) for synchronizing corresponding navigation tasks, and obtain corresponding navigation data from the first navigation application through the above API interface.

[0308] In this embodiment, the first navigation application of the first terminal has responded to the navigation task initiated by the user before S201, that is, the first terminal is the terminal that is executing the navigation task.

[0309] Continue to see Figure 2Further, as another embodiment of the present application, since the first terminal needs to respond to the navigation task initiated by the user through the first navigation application before S201, based on this, if the first terminal meets the preset cross-device transmission conditions, before obtaining the navigation data from the first navigation application through the first navigation flow module, it also includes: S200.1~S200.3 operations, which are specifically described as follows:

[0310] In S200.1, the first terminal generates a navigation task through the first navigation application in response to a navigation operation of a user; and the navigation data is generated based on the navigation task.

[0311] In this embodiment, the first terminal can run the first navigation application in the foreground, and the user can initiate a navigation operation in the operation interface generated by the first navigation application, such as inputting a corresponding navigation destination to generate a corresponding navigation task, wherein during the execution of the navigation task, the first navigation application can generate corresponding navigation data. The navigation operation initiated by the user can be a touch operation. For example, Figure 4a FIG. 1 is a schematic diagram showing a method of initiating a navigation task provided by an embodiment of the present application. Figure 4a As shown in (1), the first terminal is specifically a smart phone, and a navigation application, namely application 41, is installed in the smart phone. The user can start application 41 by clicking the icon corresponding to application 41, and generate a corresponding navigation operation interface, such as Figure 4a As shown in (2) in the figure. The first terminal can receive the navigation destination entered by the user in area 42 (specifically the destination), such as "New World Plaza". If the application 41 has obtained the positioning authority of the first terminal in advance, the current location information of the first terminal can be obtained through the positioning module configured by the first terminal, and the current location information is automatically filled in the starting point, that is, area 43. Of course, the user can also adjust the starting point according to the actual situation, that is, by clicking on area 43 to enter the corresponding starting point. Area 44 can select the required navigation scene, such as driving scene, bus scene and walking scene, for example Figure 4a In (2), the driving scenario is selected. If all contents of the above navigation task are set, the corresponding navigation task can be generated by clicking the control 45 (i.e., start navigation), and the first navigation application in the first terminal will start navigating for the user, such as Figure 4a As shown in (3) in .

[0312] In a possible implementation, the navigation operation initiated by the user may also be a voice navigation operation. Figure 4b FIG. 2 shows a schematic diagram of initiating a navigation task provided by another embodiment of the present application. Figure 4bAs shown in (1), the first terminal is specifically a smart phone, and the navigation operation interface of the smart phone includes a voice navigation control 46. If the smart phone detects that the user clicks the above control 46, it will enter the voice navigation trigger mode, such as Figure 4b In this state, the smartphone will listen to the voice commands issued by the user. For example, if the user says "I want to go to tourist attraction A", the smartphone will recognize that the user needs to navigate to tourist attraction A and generate a navigation route from the current location to tourist attraction A, as shown in (2). Figure 4b As shown in (3) in .

[0313] For example, Figure 4c FIG. 2 shows a schematic diagram of initiating a navigation task provided by another embodiment of the present application. Figure 4c As shown in (1), the first terminal is specifically a vehicle-mounted terminal, which can automatically enter the navigation interface after startup, such as Figure 4c As shown in (1) in the figure. The vehicle terminal can be configured with a corresponding voice activation command. If it detects that the user says the corresponding voice activation command, such as "Hi, my car", it will enter the voice navigation trigger mode. In this state, the vehicle terminal will monitor the voice command issued by the user. For example, if the user says "I want to go to tourist attraction A", the vehicle terminal will generate a navigation route to tourist attraction A, such as Figure 4c As shown in (2) in .

[0314] In a possible implementation, the above navigation scenario can determine its corresponding default scenario according to the terminal type. For example, if the terminal type is a vehicle-mounted terminal type, the corresponding navigation scenario in the above navigation application can be selected as a driving scenario by default; if the terminal type is a portable terminal type, the corresponding navigation scenario in the above navigation application can be selected as a walking scenario by default, or as a public transportation scenario by default, etc. The specific correspondence between the default scenario and the terminal type can be set according to the actual situation.

[0315] In S200.2, the first terminal receives a service registration instruction transmitted by the first navigation application through the first navigation flow module; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices.

[0316] In this embodiment, in order for the first navigation flow module to obtain the corresponding navigation data from the first navigation application when navigation task synchronization is required later, the first navigation application will send a service registration instruction to the first navigation flow module. If the first navigation flow module is a background application running in the application layer of the first terminal, the first navigation application can send the above service registration instruction to the first navigation flow module through the virtual communication interface between programs in the application layer; if the first navigation flow module is a navigation manager running in the application framework layer of the first terminal, the service registration instruction sent by the first navigation application can be received through the API interface between the first navigation flow module and the first navigation application.

[0317] In S200.3, the first terminal responds to the service registration instruction, adds the first navigation application to the navigation synchronization application list, and sets the first navigation flow module to the startup state; the startup state is used to send the navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission condition is met.

[0318] In this embodiment, the first navigation flow module of the first terminal may store a navigation synchronization application list, and the navigation synchronization application list may record various application programs that have sent service registration instructions, such as the first navigation application mentioned above.

[0319] In one possible implementation, the first terminal may be installed with multiple navigation applications, such as Amap, Baidu Map, and Google Map. If the user starts the above multiple navigation applications while using the first terminal, each navigation application sends a service registration instruction to the first navigation flow module. Therefore, the navigation synchronization application list stored in the first navigation flow module records multiple navigation applications. For example, Table 2 shows a schematic diagram of the navigation synchronization application list provided by an embodiment of the present application. As shown in Table 2, after any navigation application in the first terminal is started and executes the corresponding navigation task, it will send a service registration instruction to the first navigation flow module. The first navigation flow module can associate the time of each received service registration instruction and the corresponding application identifier and store them in the above navigation synchronization application list. The first terminal can determine the navigation applications that have been started and the registration time of each navigation application through the navigation synchronization application list. Among them, if a navigation application performs multiple navigation tasks during the startup of the first terminal, it can send multiple service registration instructions to the first navigation flow module, such as the 1st and 4th items in Table 2. The navigation application Baidu Map sent service registration instructions to the first navigation flow module at two time points: 14:00 and 17:11. In this case, the first navigation flow module can obtain the corresponding navigation data from the first navigation application with the latest registration time, for example, the Baidu Map with a registration time of 17:11 in Table 2. Optionally, the first navigation flow module obtains the corresponding navigation data from the first navigation application currently running in the foreground.

[0320] Register your app Registration Time Baidu Map 14:00 2. Google Maps 15:14 3. Gaode Map 17:02 4. Baidu Maps 17:11 … …

[0321] Table 2

[0322] In this embodiment, each first navigation application that has sent a service registration instruction to the first navigation flow module constitutes the navigation application ecosystem of the first terminal. In this embodiment, the first terminal is specifically a terminal that initiates a navigation synchronization task. If in other scenarios, the first terminal can also be a terminal that responds to other terminals initiating a navigation synchronization task. In this case, the first terminal can select the first navigation application that has sent a service registration instruction from the navigation application ecosystem to synchronize the navigation task of the other terminal.

[0323] In this embodiment, after receiving the service registration instruction of the first navigation application, the first navigation flow module can set its task synchronization switch to the on state, so that when it is subsequently detected that the corresponding cross-device transmission conditions are met, it can automatically trigger the synchronization process of the navigation task, that is, execute operations S201 to S203.

[0324] In a possible implementation, the state switch of the first navigation flow module may also be manually configured by the user.

[0325] For example, Figure 5 FIG. 1 shows a schematic diagram of setting a state switch of a first navigation flow module provided in an embodiment of the present application. Figure 5 As shown in (a) of FIG. 1 , the first terminal responds to a navigation operation initiated by a user, such as clicking a navigation control 51 in a first navigation application, and generates a navigation task corresponding to the navigation operation. At this time, the first terminal can generate a prompt box 52 to prompt the user whether to start the navigation task synchronization service, such as Figure 5 As shown in (b), the prompt box 52 includes an approval control 53 and a rejection control 54. If the first terminal detects that the user clicks the confirmation control 53, it recognizes that the user confirms to start the navigation task synchronization service, and therefore sets the first navigation flow module to the on state.

[0326] In another implementation, the navigation task synchronization switch of the first navigation flow module of the first terminal can be manually configured in the setting interface of the terminal. Figure 5 (c) in FIG. 4 shows the main interface of the first terminal, which includes a setting icon 55. After detecting that the user clicks the setting icon 54, the first terminal can generate a corresponding setting interface, such as Figure 5 As shown in (d) in the setting interface, the user can set multiple items of the first terminal, such as turning on the Bluetooth module of the first terminal, or selecting the peripheral device connected to the Bluetooth module, or configuring the wireless network, which includes a switch setting for navigation task synchronization, that is, control 56. The first terminal can respond to a click operation initiated by the user to change the state of the first navigation flow module, such as Figure 5 In (d), the first navigation flow module is in an open state. If a click operation of the user on the control 56 is detected, the first navigation flow module can be changed from the open state to the closed state.

[0327] In an embodiment of the present application, before the first terminal performs navigation task synchronization, when initiating a navigation operation on the first navigation application, it will automatically send a corresponding service registration instruction to the first navigation flow module. The first navigation flow module can add the first navigation application to the corresponding navigation synchronization application list and automatically set the first navigation flow module to the on state, thereby reducing the user's manual setting of the state of the first navigation flow module and improving the setting efficiency.

[0328] Further, as another embodiment of the present application, when the first terminal detects that the preset cross-device transmission condition is met, it means that navigation task synchronization is required. In this case, in order to improve the success rate of navigation task synchronization, the first electronic device can determine whether the first navigation application meets the conditions for navigation task synchronization, specifically including the following two aspects:

[0329] Condition 1: Does the first navigation application have permission to synchronize navigation tasks?

[0330] Condition 2: Is the first navigation application currently running in the foreground of the first terminal?

[0331] Among them, different types of navigation applications can be installed in the first terminal. Since not all navigation applications support the navigation task synchronization service, in this case, the first navigation flow module can record an application whitelist that supports navigation task synchronization, or an application blacklist that does not support navigation task synchronization. The first terminal determines whether the first navigation application that currently initiates the navigation task is in the above-mentioned application whitelist, or whether it is in the corresponding application blacklist, so as to determine whether the first navigation application has the authority to synchronize the navigation task. If the first navigation application is in the application whitelist (or not in the application blacklist), it is recognized that the first navigation application has the authority to perform the navigation task.

[0332] For condition 2, since the first terminal can realize synchronization operations of different applications, in order to determine whether the current task that needs to be synchronized is a navigation task, when it is detected that the cross-device transmission conditions are met, it can be detected whether the first navigation application is the application running in the foreground. Then, it can be determined that the first terminal is executing the navigation task initiated by the user and watching the navigation information output by the first navigation application in real time. Based on this, the navigation task can be synchronized, and the navigation task executed in the first navigation application can be synchronized to the navigation application of another terminal, that is, the second navigation application of the second terminal.

[0333] In this embodiment, after detecting that the cross-device transmission condition is met, the first terminal may perform a preliminary conditional judgment on the first navigation application, thereby ensuring the success rate of navigation task synchronization and avoiding unnecessary synchronization operations.

[0334] In S202, the first terminal generates navigation synchronization information of the navigation data through the first navigation flow module.

[0335] In this embodiment, after the first terminal obtains the navigation data from the first navigation application through the first navigation flow module, the first terminal can generate corresponding navigation synchronization information from the navigation data.

[0336] In one possible implementation, the first navigation flow module may directly encapsulate the acquired navigation data and generate corresponding navigation synchronization information, that is, the first navigation flow module does not process the data content of the navigation data, but adds the header or tail of the corresponding data packet, etc., to generate the corresponding navigation synchronization information.

[0337] In one possible implementation, the first navigation flow module may preprocess the navigation data, and the preprocessing includes but is not limited to data cleaning, data standardization processing and / or data format conversion. Since in the process of synchronizing navigation tasks across devices, the first navigation application installed in the first terminal and the second navigation application installed in the second terminal may not be the same navigation application, in order to enable the transmission of navigation data across devices and across applications, thereby completing the synchronization of navigation tasks, the first navigation flow module may preprocess the navigation data, so that the generated navigation synchronization information can be read by the second navigation application in the second terminal. Among them, the method of preprocessing the navigation data to generate the corresponding navigation synchronization information can be:

[0338] Mode 1: Data standardization processing. The first navigation flow module can convert navigation data into standard format data that is compatible with different types of navigation applications. The first navigation flow module stores a corresponding standard format template, which contains multiple information items. For example, Table 3 shows a format diagram of the standard format template provided in an embodiment of the present application. As shown in Table 3, the standard format template is configured with corresponding fields for different information items. The first navigation flow module can extract the parameter values ​​corresponding to each information item from the navigation data and fill in the corresponding fields, and then generate the corresponding standard format data, that is, the above-mentioned navigation synchronization information. The opposite end can obtain the corresponding data from the corresponding fields, thereby realizing cross-device and cross-application navigation data synchronization. Among them, the header can limit the data length corresponding to the standard format data. Since the number of halfway points is a variable, the more the number of halfway points, the longer the data length of the corresponding standard format data. Therefore, the data length of the standard format data can be defined by the header, so that while ensuring the standardization of the data format, it can also carry certain custom content.

[0339] First Starting point destination Navigation rules Stopover 1 … 1 byte 2 bytes 2 bytes 2 bytes 2 bytes …

[0340] Table 3

[0341] Method 2: Data format conversion. The first navigation flow module can convert the format of the navigation data obtained from the first navigation application into a data format adapted to the second navigation application, namely, the above-mentioned navigation synchronization information. In this case, the first terminal can send a navigation application detection request to the second terminal, and the second terminal can respond to the navigation application detection request by adding the application identifier of the second navigation application to the response information. The first terminal parses the response information, obtains the application identifier of the second navigation application, determines the data format that matches the second navigation application, and converts the navigation data into the above-mentioned data format, thereby generating corresponding navigation synchronization information.

[0342] Continue to see Figure 2 Further, as another embodiment of the present application, before the first terminal sends the navigation synchronization information to the second terminal, S202.1 to S202.2 may be included, which are specifically described as follows:

[0343] In S202.1, the first terminal obtains a navigation application list of the second terminal; the navigation application list includes the second navigation application.

[0344] In this embodiment, the first terminal can send an application list acquisition request to the second terminal, and the application list acquisition request is specifically used to determine the navigation applications installed in the second terminal. In response to the application list acquisition request, the second terminal can add the application identifiers of each locally installed navigation application to the above-mentioned navigation application list, and feed it back to the first terminal. Since the second navigation application that needs to synchronize the navigation task is also installed in the second terminal, the second navigation application is also included in the above-mentioned navigation application list.

[0345] In S202.2, if the first terminal detects that there is a navigation application matching the first navigation application in the navigation application list, the navigation synchronization information is sent to the second terminal; the navigation application matching the first navigation application is specifically: an application that has the authority to transmit navigation data across devices with the first navigation application.

[0346] In this embodiment, after obtaining the list of navigation applications, the first terminal can determine whether the second terminal has installed an application that can implement cross-device navigation tasks, that is, an application that has the authority to transmit navigation data across devices with the first navigation application. If so, the first terminal can send navigation synchronization information to the second terminal; conversely, if the second terminal does not have installed an application that can implement cross-device navigation tasks, in this case, even if the first terminal sends the navigation synchronization information to the second terminal, the second terminal cannot synchronize the navigation task based on the navigation synchronization information. Based on this, the first terminal will not send the above-mentioned navigation synchronization information to the second terminal.

[0347] In one possible implementation, if there is no navigation application matching the first navigation application in the navigation application list, the first terminal may send an application installation instruction to the second terminal to prompt the second terminal to install a navigation application that has the authority to transmit navigation data across devices with the first navigation application.

[0348] For example, Figure 6 FIG. 1 shows a schematic diagram of providing a prompt for installing an application on a second terminal according to an embodiment of the present application. Figure 6As shown in (a) in the figure, the second terminal may be a vehicle-mounted terminal. After the first terminal sends an application installation instruction to the second terminal, the second terminal may generate an application installation prompt message to inquire whether the user agrees to install the navigation application matching the first navigation application. The application installation prompt message includes an approval control 61 and a rejection control 62. If it is detected that the user clicks the approval control 61, the installation process of the navigation application that can realize navigation task synchronization is carried out, such as Figure 6 As shown in (b) in the figure, the corresponding installation progress and the corresponding installation stage are displayed. After the second terminal has installed the matching navigation application, it can resend a navigation application list to the first terminal. At this time, the first terminal can identify that the navigation application list contains the navigation application that matches the first navigation application, and send the navigation synchronization information to the second terminal.

[0349] In an embodiment of the present application, before sending the navigation synchronization information to the second terminal, it is determined whether the second terminal has a navigation application that can respond to the navigation task synchronization. If the corresponding navigation application is installed, the navigation synchronization information is sent to the second terminal, thereby improving the success rate of the navigation task synchronization and avoiding unnecessary synchronization operations.

[0350] Continue to see Figure 2 In S203, the second terminal receives the navigation synchronization information sent by the first terminal, and transmits the navigation synchronization information to the second navigation application through the second navigation flow module.

[0351] In this embodiment, a communication connection is established between the first terminal and the second terminal, and the communication connection can be a wireless connection, such as a Bluetooth connection, a Near Field Communication (NFC) connection, a Wireless Fidelity (WIFI) connection, etc. Based on the communication connection between the two, the second terminal can receive navigation synchronization information sent by the first terminal. Among them, the first terminal can call the wireless communication interface through the first navigation flow module, that is, the communication protocol corresponding to the wireless communication interface, to send the navigation synchronization information to the second terminal, and correspondingly, the second terminal can also call the corresponding wireless communication interface through the second navigation flow module to receive the above navigation synchronization information.

[0352] Continue to see Figure 2 As another embodiment of the present application, after receiving the navigation synchronization information sent by the first terminal, the second terminal may also locally determine whether there is a navigation application that can respond to the navigation task synchronization. After the second terminal receives the navigation synchronization information sent by the first terminal, the method may also include:

[0353] In S203.1, the second terminal detects whether there is a navigation application matching the first navigation application in the navigation application list.

[0354] In S203.2, if the second terminal detects that a navigation application that matches the first navigation application exists in the navigation application list, the navigation application that matches the first navigation application will be used as the second navigation application, and the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module will be performed; the navigation application that matches the first navigation application is specifically: an application that has the authority to transmit navigation data across devices with the second navigation application.

[0355] In the present embodiment, in addition to the first terminal being able to determine whether the second terminal is installed with a navigation application that can realize navigation task synchronization, the second terminal can also perform a feasibility check on the task synchronization of the local navigation application, that is, determine whether the navigation synchronization information sent by the first terminal is compatible with the second navigation application installed by the second terminal. In this case, the second terminal can determine the application type of the first navigation application installed in the first terminal based on the navigation synchronization information sent by the first terminal, and determine whether there is a navigation application matching the first navigation application among the locally installed navigation applications. If a navigation application matching the first navigation application is installed in the second terminal, that is, there is a navigation application matching the first terminal in the navigation application list of the second terminal, at this time, the second terminal can use the matching navigation application as the navigation application for navigation task synchronization, and therefore, the second navigation flow module can send the received navigation synchronization information to the second navigation application.

[0356] In an embodiment of the present application, after the second terminal receives the navigation synchronization information, the second terminal can determine whether there is a local navigation application that can respond to the navigation task synchronization. If the corresponding navigation application is installed, the navigation synchronization information is sent to the corresponding navigation application, thereby improving the success rate of the navigation task synchronization and avoiding unnecessary synchronization operations.

[0357] In a possible implementation, before the navigation synchronization information is transmitted to the second navigation application through the second navigation flow module, the navigation synchronization information may be preprocessed so that the preprocessed information can be compatible with the second navigation application. The preprocessing includes but is not limited to data cleaning, data standardization processing and / or data format conversion. The specific method of preprocessing is similar to the preprocessing method of the first terminal for navigation data. For a specific description, please refer to the relevant description in S202, which will not be repeated here.

[0358] In one possible implementation, if multiple navigation applications are installed in the second terminal, and the multiple navigation applications all match the first navigation application of the first terminal, in this case, the second terminal can determine the navigation application for navigation task synchronization, that is, the second navigation application, based on the startup time of each local navigation application. For example, the second navigation flow module can select the most recently started navigation application as the second navigation application for navigation task synchronization. Optionally, in addition to determining the navigation application for navigation task synchronization based on the startup time, the second navigation flow module can also determine the user's frequently used navigation application based on the number of times each navigation application installed in the second terminal is used, and use the frequently used navigation application as the second navigation application.

[0359] Continue to see Figure 2 In S204, the second terminal updates the navigation task of the second navigation application according to the navigation synchronization information.

[0360] In this embodiment, after the second navigation flow module of the second terminal sends the navigation synchronization information to the second navigation application, the second navigation application sets the navigation task corresponding to the first navigation application in the first terminal, thereby realizing the navigation task synchronization between the first navigation application and the second navigation task. Among them, the above-mentioned updating of the navigation task of the second navigation application includes two situations:

[0361] Case 1: the second navigation application does not execute the task navigation task. In this case, the second terminal may create a corresponding navigation task based on the navigation synchronization information.

[0362] Case 2: Before synchronization, the second navigation application is executing another navigation task. In this case, the second terminal can change the navigation task of the second navigation application according to the above navigation synchronization information, so that the navigation task of the second navigation application is consistent with the navigation task executed by the first navigation application in the first terminal.

[0363] For example, Figure 7 FIG. 1 shows a schematic diagram of a navigation task change provided by an embodiment of the present application. Figure 7 As shown in (a) in FIG. 1 , before the second terminal performs navigation task synchronization, it is executing a navigation task of navigating to location A. At this time, the first terminal synchronizes the navigation task (navigation task of navigating to location B) with the second terminal, and sends the corresponding navigation synchronization information to the second terminal. At this time, the second terminal can update the navigation task in the second navigation application according to the navigation synchronization information, thereby changing the destination from location A to location B, as shown in FIG. Figure 7 As shown in (b) in .

[0364] Continue to see Figure 2Further, as a possible implementation, before synchronizing the navigation task of the second navigation application, the user may be asked whether he agrees to the synchronization operation. Based on this, the above S204 may specifically include the following steps:

[0365] In S204.1, the second terminal determines a navigation destination based on the navigation synchronization information, and generates task update prompt information based on the navigation destination.

[0366] In S204.2, if the second terminal receives an update confirmation instruction based on the update prompt information feedback, the second terminal updates the navigation task based on the navigation destination.

[0367] In this embodiment, before updating the navigation task of the second navigation application, the second terminal can generate corresponding task update prompt information to confirm whether the user agrees to the update operation of the navigation task. If the user agrees to the update operation of the navigation task, the corresponding consent operation can be initiated on the second terminal. The second terminal can generate a corresponding update confirmation instruction based on the consent operation. After receiving the update confirmation instruction, the second navigation application can update the navigation task through the navigation destination in the navigation synchronization information.

[0368] For example, Figure 8 A schematic diagram of updating a navigation task provided by an embodiment of the present application is shown. After receiving the navigation synchronization information, the second navigation application of the second terminal can parse the navigation synchronization information, determine the navigation destination specified in the navigation synchronization information, and generate corresponding task update prompt information based on the navigation destination. For example, if the navigation destination is tourist attraction B, a prompt message for task update is generated. The content of the prompt message can be displayed as "Do you want to continue the navigation task on mobile phone UserA?" UserA is the mobile phone ID of the smart phone, so that the user can determine which device's navigation task to synchronize to the second terminal. Figure 8 As shown in (a) of FIG. 1 ; the above prompt information can also be displayed as "Do you want to continue the navigation task to tourist attraction B?" so that the user can determine the specific destination of the updated navigation task. The task prompt information includes a confirmation control 81 and a cancel control 82. If the second terminal detects that the user clicks the confirmation control 81 in the second navigation application, the navigation task can be updated according to the navigation destination, such as Figure 8 As shown in (b) in FIG. 1 , after the user clicks the confirmation control 81, the navigation destination in the second navigation application can be changed to tourist attraction B. If the user clicks the cancel control 82, the original navigation destination is maintained, such as Figure 8 As shown in (c) in the figure, the navigation destination in the second navigation application continues to be tourist attraction A.

[0369] In the embodiment of the present application, corresponding task update prompt information is generated to notify the user whether to agree to update the navigation task, thereby avoiding the occurrence of erroneous synchronization and improving the accuracy of navigation task synchronization.

[0370] Continue to see Figure 2 Further, as another embodiment of the present application, after the second terminal updates the navigation task of the second navigation application according to the navigation synchronization information, the first terminal may be notified that the above navigation task has completed synchronization, that is, after S204, the following steps may also be included:

[0371] In S205, the second terminal sends navigation synchronization completion information to the first terminal through the second navigation flow module.

[0372] In S206, in response to the navigation synchronization completion information, the first terminal transmits an end instruction about the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0373] In this embodiment, after completing the update of the navigation task, the second terminal can send a navigation synchronization completion message to the first terminal through the second navigation flow module. After receiving the navigation synchronization completion message sent by the second terminal, the first terminal can determine that the second terminal has completed the synchronization of the navigation task, that is, the navigation task is transferred from the first terminal to the second terminal for execution. In this case, the first terminal can end the navigation task executed locally, and the first navigation flow module can send an end instruction to the first navigation application. After receiving the end instruction, the first navigation application can stop the navigation task being executed in the first navigation application of the first terminal, thereby realizing the transfer of the navigation task.

[0374] For example, Fig. 9 FIG. 1 is a schematic diagram showing a method of ending a navigation task provided by an embodiment of the present application. Fig. 9 As shown in (a) of FIG. 1 , after the first terminal sends the navigation synchronization information to the second terminal through the first navigation flow module, a prompt message of "synchronizing" can be displayed locally, and the corresponding synchronization progress can be displayed according to the time required for synchronization under normal circumstances and the current waiting time. If the first terminal receives the navigation synchronization completion information sent by the second terminal, a prompt message of "synchronization completed" can be generated, such as Fig. 9 As shown in (b) of FIG. 1 , the second terminal is prompted to the user that the second terminal has completed the synchronization of the navigation task. In this case, the first terminal can directly end the navigation task, for example, exit the first navigation application and return to the main interface of the first terminal, or return to the initial interface of the application, such as Fig. 9Optionally, after receiving the navigation synchronization completion information, the prompt information generated by the first terminal may include an end confirmation control 91 for asking the user whether to end the navigation task in the first navigation application, such as Fig. 9 As shown in (c) in FIG. 1 , if the first terminal detects that the user clicks the above-mentioned end confirmation control 91, the navigation task of the first navigation application in the first terminal can be ended and the initial interface of the application can be returned, such as Fig. 9 Of course, the end confirmation control 91 may also display a corresponding effective waiting time. If the first terminal does not receive a user click on the end confirmation control 91 within the effective waiting time, the navigation task being executed by the first navigation application in the first terminal may also be ended.

[0375] In a possible implementation, the first terminal may be configured with a maximum waiting time. If the first terminal does not receive navigation synchronization completion information fed back by the second terminal within the maximum waiting time when sending navigation synchronization information to the second terminal, it is recognized that the navigation task synchronization to the second terminal fails. In this case, the first terminal may display a prompt message of synchronization failure. For example, Fig.10 FIG. 1 shows a schematic diagram of a response to synchronization failure provided by an embodiment of the present application. Fig.10 As shown in (a), if the first terminal does not receive the navigation synchronization completion information within the maximum waiting time, the corresponding prompt information of synchronization failure can be displayed in the first navigation application. The prompt information can include a "retry" control 101, a "switch synchronization device" control 102, and a "cancel" control 103. If the first terminal detects that the user clicks on the control 101, the first terminal re-sends a navigation synchronization message to the second terminal so that the second terminal re-synchronizes the navigation task based on the navigation synchronization information; if the first terminal detects that the user clicks on the control 102, the terminal identifier of other terminals that can be synchronized can be generated, such as Fig.10 As shown in (b), the user can reselect the terminal that needs to synchronize the navigation task from the other terminals displayed, and send navigation synchronization information to it to achieve navigation task synchronization. If the first terminal detects that the user clicks on the control 103, it indicates the operation of exiting the navigation synchronization and returns to the original navigation task interface.

[0376] As can be seen from the above, a method for synchronizing navigation tasks across devices provided by an embodiment of the present application can automatically obtain navigation data of the navigation task that has been turned on from the first navigation application through the first navigation flow module locally configured in the first terminal when the first terminal detects that the cross-device transmission condition is met, and generates navigation synchronization information corresponding to the navigation data through the first navigation flow module, and sends the navigation synchronization information to the second terminal, thereby realizing the cross-device transmission of navigation data. After receiving the above navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through the local second navigation flow module, and then the second terminal can update the navigation task of the second navigation application according to the navigation synchronization information, thereby realizing the synchronization of navigation tasks across devices. Compared with the existing navigation technology, the present application can realize the synchronization of navigation tasks across devices. In the scenario where cross-device navigation is required, the user does not need to set tasks for the navigation application of the terminal multiple times, but can automatically realize the flow of navigation data through the navigation flow module to update the navigation tasks in the navigation application, thereby greatly improving the efficiency of navigation task setting and reducing the user's repeated operations. On the other hand, after the first navigation flow module in the first terminal obtains the navigation data from the first navigation application, it does not directly send the navigation data to the second navigation flow module of the second terminal, but converts the navigation data into corresponding navigation synchronization information. The navigation synchronization information can be transmitted in the navigation flow modules of different terminals, and then transmitted to the second navigation application through the second navigation flow module. It is not a direct transmission between the navigation applications in the two terminals. Therefore, there is no need to install the same navigation application on the first terminal and the second terminal. Navigation data flow across devices and applications can be realized, further improving the application scope of navigation task synchronization.

[0377] Embodiment 2:

[0378] Compared with the first embodiment, the cross-device transmission condition in the second embodiment is a touch operation transmission condition, that is, a specific description of the specific implementation process when two terminals trigger the synchronization of navigation tasks through touch operations. Among them, in this embodiment, the first terminal can be a terminal that initiates a touch operation (that is, a terminal that actively approaches another terminal), for example, a user holding the first terminal to initiate a touch operation to the second terminal, or it can be a terminal that passively responds to a touch operation, for example, a user controls the second terminal to initiate a touch operation to the first terminal. Exemplarily, the following is an example in which the first terminal is a smart phone and the second terminal is an intelligent vehicle control terminal installed on a vehicle (referred to as a vehicle-mounted terminal).

[0379] In this embodiment, the user holds a smart phone and controls the smart phone to perform a touch operation with the vehicle terminal. The smart phone and the vehicle terminal are equipped with NFC modules, and the two terminals can establish a near field communication connection through the NFC module to achieve data interaction. For example, Fig.11 The following is an interactive schematic diagram of a method for synchronizing navigation tasks across devices provided by an embodiment of the present application. The synchronization method is applied to a touch-triggered scenario. The specific interactive process is as follows:

[0380] In S1103, the vehicle-mounted terminal sends a communication tag to the smartphone via a near field communication module of the vehicle-mounted terminal in response to a touch operation with the smartphone.

[0381] In this embodiment, the user can control the smartphone to initiate a touch operation on the vehicle-mounted terminal. In this case, the distance between the NFC module in the vehicle-mounted terminal and the NFC module of the smartphone will be less than a preset distance threshold. Therefore, through the NFC module, a near-field communication connection can be established between the vehicle-mounted terminal and the smartphone. At this time, the vehicle-mounted terminal can send a pre-written communication tag to the smartphone through the established near-field communication connection.

[0382] For example, Fig.12 A schematic diagram of a touch scene between a vehicle-mounted terminal and a smart phone provided in an embodiment of the present application is shown. Fig.12 As shown, the user holds a smart phone, and the smart phone touches the vehicle-mounted terminal to activate the NFC modules in the two terminals, and establishes a near-field communication connection between the two through the NFC module to transmit the communication tag and subsequent navigation synchronization information.

[0383] In this embodiment, in order to start the synchronization process of the navigation task, the communication tag sent by the vehicle terminal can carry a start identifier for the synchronization of the navigation task. After the smartphone receives the communication tag containing the start identifier, it can determine that the cross-device transmission conditions are met and start the synchronization process of the navigation task.

[0384] In this embodiment, in addition to the start identifier of the navigation task synchronization, the communication tag may also include the terminal identifier of the vehicle-mounted terminal, the module identifier of the NFC module, etc. Of course, the vehicle-mounted terminal may also add the application identifier of the locally installed navigation application to the above-mentioned communication tag. The specific information contained in the communication tag can be adjusted according to actual conditions, and its content is not limited here.

[0385] Further, as another embodiment of the present application, before the vehicle terminal responds to the touch operation initiated by the smart phone, the vehicle terminal may pre-write the communication tag into the near field communication module of the vehicle terminal, that is, before S1103, it may include S1101 to S1102, which are specifically described as follows:

[0386] In S1101, if the vehicle terminal meets the preset tag writing condition, a tag writing request is sent to the tag service thread through the second navigation flow module.

[0387] In S1102, the vehicle-mounted terminal responds to the tag writing request through the tag service thread, adds the startup identifier to the communication tag, and writes the communication tag to the near field communication module of the vehicle-mounted terminal.

[0388] In this embodiment, when the preset tag writing condition is met, the vehicle terminal can first send a tag writing request to the tag service through the second navigation flow module configured in the vehicle terminal, so as to write the corresponding communication tag to the near field communication module of the vehicle terminal. Among them, the above-mentioned tag writing condition can be specifically the vehicle terminal startup, for example, when the vehicle is started, the vehicle terminal installed in the vehicle will be started at the same time, at this time, the vehicle terminal will identify the preset tag writing condition and execute the operation of S1101.

[0389] In this embodiment, a tag service thread is running in the vehicle terminal, and the tag service thread is specifically used to write a communication tag to the near-field communication module of the vehicle terminal. Therefore, when the second navigation flow module sends a tag write request to the tag service thread, it indicates that the vehicle terminal has started the synchronization service of the navigation task. Based on this, the tag service write thread can generate a start flag and add it to the communication tag, and write the communication tag with the start flag added to the near-field communication module of the vehicle terminal.

[0390] In an embodiment of the present application, when the tag writing conditions are met, a communication tag carrying the navigation task synchronization is written to the near-field communication module of the vehicle terminal through the tag service thread. When the communication tag is sent to the other end, the synchronization process of the navigation task can be automatically started, thereby reducing user operations and improving synchronization efficiency.

[0391] In S1104, the smartphone starts the first navigation flow module in response to the communication tag, and obtains the navigation data from the first navigation application through the first navigation flow module.

[0392] In this embodiment, after receiving the communication tag sent by the vehicle-mounted terminal, the smartphone can parse the communication tag. If it is detected that the communication tag carries a navigation synchronization startup identifier, the first navigation flow module configured in the smartphone can be started, and navigation data can be obtained from the first navigation application through the first navigation flow module.

[0393] Optionally, before the first navigation flow module obtains navigation data from the first navigation application, a precondition judgment may be performed, specifically including the following two judgment steps:

[0394] In S1105 , it is determined whether the first navigation application has permission to synchronize navigation tasks.

[0395] In S1106 , it is determined whether the first navigation application is currently running in the foreground of the smart phone.

[0396] If both judgment operations are yes, the first navigation flow module can obtain navigation data from the first navigation application. The specific judgment process and method can refer to the relevant description of S201 in the first embodiment, which will not be repeated here.

[0397] In S1107, the smart phone generates navigation synchronization information of the navigation data through the first navigation flow module.

[0398] Since the implementation method of the above S1107 is exactly the same as that of S202 in the first embodiment, the specific description can refer to the relevant description of S202, which will not be repeated here.

[0399] In S1108, the vehicle terminal receives the navigation synchronization information sent by the smart phone, and transmits the navigation synchronization information to the second navigation application through the second navigation flow module.

[0400] Since the implementation of S1108 is exactly the same as that of S203 in the first embodiment, the specific description can refer to the relevant description of S203, which will not be repeated here. That is, S1108 can also determine whether a navigation application matching the first navigation application is installed locally, and if there is a matching navigation application, it is identified as the second navigation application.

[0401] In S1109, the vehicle terminal updates the navigation task of the second navigation application according to the navigation synchronization information.

[0402] Optionally, S1109 may further include:

[0403] In S1109.1, the vehicle terminal determines a navigation destination based on the navigation synchronization information, and generates task update prompt information based on the navigation destination.

[0404] In S1109.2, if the vehicle terminal receives an update confirmation instruction based on the update prompt information feedback, the navigation task is updated based on the navigation destination.

[0405] Since S1109 is implemented in exactly the same way as S204 in Example 1, S1109.1 is implemented in exactly the same way as S204.1 in Example 1, and S1109.2 is implemented in exactly the same way as S204.2 in Example 1, for specific descriptions, please refer to the relevant descriptions of S204, S204.1 and S204.2, which will not be repeated here.

[0406] Optionally, after S1109, the following steps may also be included:

[0407] In S1110, the vehicle terminal sends navigation synchronization completion information to the smart phone through the second navigation flow module;

[0408] In S1111, in response to the navigation synchronization completion information, the smartphone transmits an end instruction regarding the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0409] Since S1110 is implemented in exactly the same manner as S205 in the first embodiment, and S1111 is implemented in exactly the same manner as S206 in the first embodiment, for specific descriptions, please refer to the relevant descriptions of S205 and S206, which will not be repeated here.

[0410] In an embodiment of the present application, when a wireless connection has not been established between the first terminal and the second terminal, a communication connection can be quickly established between the first terminal and the second terminal through a touch operation, and a start identifier carrying the navigation task synchronization is added to a communication tag, and the communication tag is sent to the first terminal through a near-field communication connection, thereby quickly starting the synchronization process of the navigation task and improving the synchronization efficiency of the navigation task.

[0411] Embodiment three:

[0412] Compared with the first embodiment, the application scenario of this embodiment is specifically to synchronize the navigation task on the user terminal carried by the user to the intelligent vehicle control terminal installed in the vehicle when the vehicle starts. Based on this, the first terminal is specifically the user terminal carried by the user, and the second terminal is the vehicle-mounted terminal. Fig.13 The following is an interactive diagram of a method for synchronizing navigation tasks provided by an embodiment of the present application, which is described in detail as follows:

[0413] In S1301, the user terminal generates a navigation task through the first navigation application in response to a user's navigation operation; the navigation data is generated based on the navigation task;

[0414] In S1302, the user terminal receives a service registration instruction transmitted by the first navigation application through the first navigation flow module; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices;

[0415] In S1303, the user terminal responds to the service registration instruction, adds the first navigation application to the navigation synchronization application list, and sets the first navigation flow module to the startup state; the startup state is used to send the navigation synchronization information generated based on the first navigation application to the vehicle terminal when the cross-device transmission conditions are met.

[0416] Since S1301 is implemented in exactly the same way as S200.1 in Example 1, S1302 is implemented in exactly the same way as S200.2 in Example 1, and S1303 is implemented in exactly the same way as S200.3 in Example 1, for specific descriptions, please refer to the relevant descriptions of S200.1 to S200.3, which will not be repeated here.

[0417] Compared with the first embodiment, this embodiment further includes, before obtaining navigation data from the first navigation application through the first navigation flow module if the user terminal meets the preset cross-device transmission condition:

[0418] In S1304, if the vehicle-mounted terminal detects a start-up event related to the vehicle, a communication connection is established with the user terminal.

[0419] In this embodiment, the application scenario is that after the user gets on the vehicle, the scene is switched from walking to driving. It is necessary to synchronize the navigation task on the user terminal to the vehicle's onboard terminal. Therefore, the triggered event is specifically the detection of vehicle startup. Among them, the above-mentioned startup events include vehicle door opening events, vehicle ignition events, or vehicle power button pressing events, etc., which can be used to determine the time when the vehicle is started. When the on-board terminal detects a startup event about the vehicle, it can be recognized that the user's navigation scene has changed. Therefore, the on-board terminal can establish a communication connection with the user terminal carried by the user. The communication connection can be a communication connection established through a near-field communication module, which can be a Bluetooth communication module, a low-power Bluetooth communication module, a WIFI module, or other modules that can realize near-field wireless communication.

[0420] In this embodiment, the action of triggering event recognition is handed over to the vehicle terminal to complete. This is because when the user terminal synchronizes the navigation task to the vehicle terminal, it is difficult to identify whether the user has started the vehicle. By detecting the vehicle start event through the vehicle terminal, it is possible to more easily and accurately determine that the user's navigation scene has switched to the driving scene, thereby improving the accuracy of navigation task synchronization while reducing the difficulty of recognition.

[0421] In this embodiment, the user terminal and the vehicle terminal specifically establish a wireless communication connection. If a wireless communication connection has been established between the user terminal and the vehicle terminal, the user terminal and the vehicle terminal have already recorded the connection information of both parties, and the connection information includes but is not limited to: device identification, connection key, wireless network identification, etc. In this case, the vehicle terminal and the user terminal can establish a communication connection between the two parties based on the recorded connection information.

[0422] For example, a Bluetooth communication connection is established between the user terminal and the vehicle terminal. The user terminal records the Bluetooth connection information of the vehicle terminal, and the vehicle terminal also adds the user terminal to the authorized device list. Similarly, the vehicle terminal also stores the Bluetooth connection information of the user terminal, and the user terminal also adds the vehicle terminal to its local authorized device list. If the vehicle terminal searches for the vehicle door opening event, it can search whether the Bluetooth signal of the user terminal is detected. If it is found, a Bluetooth connection request is sent to the user terminal through the Bluetooth connection information of the user terminal. Since the vehicle terminal is recorded in the authorized device list of the user terminal, the user terminal will agree to the Bluetooth connection request and establish a Bluetooth communication connection with the vehicle terminal.

[0423] Further, as another embodiment of the present application, the method of establishing a communication connection between the user terminal and the vehicle-mounted terminal can be specifically implemented by the following steps:

[0424] In S1304.1, the vehicle terminal identifies the connection status of each registered terminal in the preset registered device list through the second navigation flow module.

[0425] In this embodiment, after detecting the door opening event of the vehicle, the vehicle terminal can search for wireless signals in the current scene through the wireless communication module, so that the connection status of each connected registered terminal in the pre-stored registered device list can be determined based on the searched wireless signals, and the above-mentioned collection results are fed back to the second navigation flow module of the vehicle terminal, and the second navigation flow module can perform corresponding operations according to the corresponding connection status of each registered terminal. If the wireless signal of the registered terminal is searched in the current scene, it can be identified that the registered terminal is in a connectable state, that is, the device is in an online state; conversely, if the wireless signal of the registered terminal is searched in the current scene, it can be identified that the registered terminal is in a non-connectable state, that is, the device is offline.

[0426] In S1304.2, if the vehicle terminal recognizes that the user terminal is in the registered device list and the connection state of the user terminal is connectable, the communication connection is established with the user terminal based on the connection information associated with the user terminal in the registered device list.

[0427] In this embodiment, if the user terminal is online, that is, it is connectable to the vehicle-mounted terminal, in this case, the vehicle-mounted terminal can send connection information associated with the user terminal to the user terminal. The above connection information is recorded in the local memory of the vehicle-mounted terminal during the historical connection between the user terminal and the vehicle terminal. Therefore, after receiving the above connection information, the user terminal can recognize that the request to establish this wireless connection is legal, so the user terminal will respond to this connection request and establish a communication connection with the vehicle-mounted terminal.

[0428] In S1304.3, if the vehicle terminal recognizes that the user terminal is not in the registered device list, or the user terminal is in the registered device list and the connection state of the user terminal is not connectable, a wake-up command is sent to the user terminal through the near field communication module of the vehicle terminal.

[0429] In this embodiment, if the user terminal is offline, there are two possibilities. The first possibility is that the user terminal is in a screen-off state or a standby state, and the wireless communication module in the user terminal is not awakened. The other possibility is that the user terminal has established a wireless communication connection with other terminals, so the corresponding connection state is an unconnectable state. In this case, the vehicle terminal can wake up the mobile phone through the soft bus, that is, send a wake-up command to the user terminal through the near field communication module of the vehicle terminal to adjust the connection state of the user terminal.

[0430] In S1304.4, the user terminal receives a wake-up instruction sent by the vehicle-mounted terminal through the near field communication module of the vehicle-mounted terminal.

[0431] In S1304.5, the user terminal sends a wireless connection request to the vehicle-mounted terminal in response to the wake-up instruction to establish the communication connection with the vehicle-mounted terminal.

[0432] In this embodiment, the user terminal receives the above wake-up instruction through the local near-field communication module (i.e., the near-field communication module of the user terminal), and then adjusts the connection state of the local near-field communication module to a connectable state. In this case, the user terminal can establish a communication connection with the vehicle terminal, so a wireless connection request can be sent to the vehicle terminal through the near-field communication module of the user terminal. After receiving the wireless connection request, the vehicle terminal can update the device information of the user terminal in the locally stored registered device list, and establish a communication connection with the user terminal.

[0433] In an embodiment of the present application, the vehicle-mounted terminal first determines whether the user terminal is currently in a connectable state through the connection status of each registered device in the registered device list. If so, it directly connects. If it is in an unconnectable state, it sends a wake-up command to change the connection status of the user terminal and reconnect, thereby improving the success rate of the wireless connection.

[0434] In S1305, the vehicle terminal obtains a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtains the setting status of the second navigation flow module.

[0435] In this embodiment, after the vehicle terminal establishes a communication connection with the user terminal, it can identify whether it has installed a navigation application that supports navigation task synchronization, and the navigation application that supports navigation task synchronization will be recorded in the above navigation synchronization application list. Therefore, after the vehicle terminal establishes a communication connection with the user terminal, it can identify whether the navigation application list is empty. If the navigation application list is not empty, it means that the vehicle terminal supports the synchronization operation of the navigation task. In this case, the vehicle terminal can obtain the setting status corresponding to the second navigation flow module.

[0436] In this embodiment, in addition to requiring the navigation application installed in the vehicle terminal to support the synchronous operation of the navigation task, it is also required that the user has turned on the synchronization service of the navigation task. In this case, the vehicle terminal needs to identify the setting status corresponding to the second navigation flow module. If its setting status is the startup state, it is recognized that the user has turned on the synchronization service of the navigation task and executes the operation S1306; on the contrary, if it is identified that the second navigation flow module is in the closed state, it means that the user has not turned on the synchronization service of the navigation task. In this case, the vehicle terminal will end the synchronization operation of the navigation task.

[0437] In S1306, if the second navigation flow module is in the activated state, the vehicle terminal sends a navigation flow notification to the user terminal, so that the user terminal sends the navigation synchronization information.

[0438] In this embodiment, when the vehicle terminal detects that the second navigation flow module is in the activated state, it can send a navigation flow notification to the user terminal, so as to start the synchronization process of the navigation task. Fig.14 The following is a schematic diagram of the interface of the vehicle terminal provided by an embodiment of the present application. After the vehicle terminal is started, if it is recognized that the user terminal is in a connectable state, it can directly establish a communication connection with the user terminal and display the current connection status in the interface, such as Fig.14As shown in (a) of FIG. 1 , the interface displays the terminal identifier of the user terminal to which the vehicle terminal is connected, such as "UserA", and the current connection status, such as "Connected". At this time, if the vehicle terminal is installed with an application that supports navigation task synchronization, and the navigation task synchronization service is enabled, the second navigation application that supports navigation task synchronization installed locally can be started, such as Fig.14 As shown in (b) in the figure, the current synchronization progress is displayed, such as prompt information 141, "Synchronizing with the navigation task on UserA".

[0439] In one possible implementation, if the user terminal and the vehicle terminal are logged in to the same user account, the communication connection established between the user terminal and the above-mentioned vehicle terminal is specifically a server-based communication connection, that is, the user terminal and the vehicle terminal can exchange data based on the server.

[0440] For example, the transmission of navigation flow notification between a user terminal and a vehicle terminal is used as an example for explanation. Fig.15 The flowchart of the three-party interaction between the user terminal, the vehicle terminal and the server provided by an embodiment of the present application is shown. Fig.15 As shown, a user account of a user is logged in to the vehicle terminal. When it is detected that the user terminal is in a connectable state (i.e., the same user account is logged in to the user terminal and the user account is online), in this case, the vehicle terminal can send the above navigation flow notification to the server, and the navigation flow notification carries the account identifier of the user account logged in to the vehicle terminal. After receiving the above navigation flow notification, the server forwards it to another terminal logged in to the same user account, i.e., the above user terminal. It can be seen that the communication connection between the user terminal and the vehicle terminal can be a communication connection established based on the server.

[0441] Compared with the first embodiment, in this embodiment, if the user terminal meets the preset cross-device transmission condition, obtaining navigation data from the first navigation application through the first navigation flow module specifically includes S1307 to S1308:

[0442] In S1307, the user terminal receives the navigation flow notification sent by the vehicle-mounted terminal.

[0443] In S1308, in response to the navigation flow notification, the user terminal obtains navigation data from the first navigation application through the first navigation flow module.

[0444] In this embodiment, after receiving the navigation flow notification sent by the vehicle terminal, the user terminal triggers the navigation task synchronization process, and obtains the corresponding navigation data from the first navigation application through the first navigation flow module. Of course, the user terminal can also make a precondition judgment, such as whether the first navigation application has the synchronization authority for the navigation task, and whether it is allowed in the foreground. If so, the first navigation flow module can obtain navigation data from the first navigation application. Among them, the specific way in which the first navigation flow module obtains navigation data can be found in the relevant description of S201, which will not be repeated here.

[0445] In S1309, the user terminal generates navigation synchronization information of the navigation data through the first navigation flow module.

[0446] The implementation method of S1309 in this embodiment is exactly the same as that of S203 in the first embodiment. For a specific description, please refer to the relevant description of S203, which will not be repeated here.

[0447] In S1310, the vehicle terminal receives the navigation synchronization information sent by the user terminal, and transmits the navigation synchronization information to the second navigation application through the second navigation flow module.

[0448] The implementation method of S1310 in this embodiment is exactly the same as that of S204 in the first embodiment. For a specific description, please refer to the relevant description of S204, which will not be repeated here.

[0449] In S1311, the vehicle terminal updates the navigation task of the second navigation application according to the navigation synchronization information.

[0450] Among them, S1311 may include: the vehicle terminal determines the navigation destination based on the navigation synchronization information, and generates task update prompt information based on the navigation destination; if an update confirmation instruction based on the update prompt information feedback is received, the navigation task is updated based on the navigation destination.

[0451] Among them, after S1310, it may also include: the vehicle terminal sends navigation synchronization completion information to the user terminal through the second navigation flow module; the user terminal responds to the navigation synchronization completion information, and transmits an end instruction about the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0452] In an embodiment of the present application, by detecting that the vehicle door is open, the user terminal can automatically synchronize the navigation task to the vehicle terminal, thereby achieving the purpose of connecting the navigation task from the user terminal to the vehicle terminal, reducing user operations and improving navigation efficiency.

[0453] Embodiment 4:

[0454] Compared with the first embodiment, the application scenario of this embodiment is specifically to synchronize the navigation task on the intelligent vehicle control terminal installed in the vehicle to the user terminal carried by the user after the vehicle stops. Based on this, the first terminal is specifically the vehicle-mounted terminal, and the second terminal is the user terminal carried by the user. Fig.16 The following is an interactive diagram of a method for synchronizing navigation tasks provided by an embodiment of the present application, which is described in detail as follows:

[0455] In S1601, the vehicle terminal generates a navigation task through the first navigation application in response to a navigation operation of the user; the navigation data is generated based on the navigation task;

[0456] In S1602, the vehicle terminal receives a service registration instruction transmitted by the first navigation application through the first navigation flow module; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices;

[0457] In S1603, the vehicle terminal responds to the service registration instruction, adds the first navigation application to the navigation synchronization application list, and sets the first navigation flow module to the startup state; the startup state is used to send the navigation synchronization information generated based on the first navigation application to the vehicle terminal when the cross-device transmission conditions are met.

[0458] Since S1601 is implemented in exactly the same way as S200.1 in Example 1, S1602 is implemented in exactly the same way as S200.2 in Example 1, and S1603 is implemented in exactly the same way as S200.3 in Example 1, for specific descriptions, please refer to the relevant descriptions of S200.1 to S200.3, which will not be repeated here.

[0459] Compared with the first embodiment, if the vehicle terminal in this embodiment meets the preset cross-device transmission condition, obtaining navigation data from the first navigation application through the first navigation flow module specifically includes S1604 to S1606:

[0460] In S1604, if the vehicle-mounted terminal detects a parking event related to the vehicle, it establishes a communication connection with the user terminal; the near field communication connection is used to send navigation synchronization information to the user terminal.

[0461] In this embodiment, the vehicle terminal is the terminal that is executing the navigation task. If the navigation scene is not switched, the vehicle terminal will remain in the driving state. At this time, if the vehicle stops, such as the driving speed is 0, and the door is detected to be opened, or the vehicle is turned off, or the vehicle power is turned off, it can be recognized that the user has switched from the driving state to the walking state, that is, the navigation scene has changed, and the navigation task needs to be synchronized to other terminals, that is, the user terminal carried by the user. In this case, the vehicle terminal will establish communication with the user terminal.

[0462] Further, as another embodiment of the present application, establishing a communication connection between the vehicle-mounted terminal and the user terminal may specifically include the following steps:

[0463] In S1604.1, the vehicle terminal identifies the connection status of each registered terminal in the preset registered device list through the first navigation flow module;

[0464] In S1604.2, if the vehicle terminal recognizes that the user terminal is in the registered device list and the connection state of the user terminal is a connectable state, the near field communication connection is established with the user terminal based on the connection information associated with the user terminal in the registered device list.

[0465] In S1604.3, if the vehicle terminal recognizes that the user terminal is not in the registered device list, or the user terminal is in the registered device list and the connection state of the user terminal is not connectable, a wake-up instruction is sent to the user terminal through the near field communication module of the vehicle terminal;

[0466] In S1604.4, the user terminal sends a near field connection request to the vehicle-mounted terminal in response to the wake-up instruction to establish a near field communication connection with the vehicle-mounted terminal.

[0467] Specifically, the implementation method of S1604.1 to S1604.4 is exactly the same as the implementation method of S1304.1 to S1304.5 in Example 3. For specific descriptions, please refer to the relevant descriptions of S1304.1 to S1304.5, which will not be repeated here.

[0468] In S1605, the vehicle terminal obtains a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtains the setting status of the first navigation flow module.

[0469] Specifically, the implementation method of S1605 is exactly the same as the implementation method of S1305 in Example 3, and the implementation method of S1606 is exactly the same as the implementation method of S1306 in Example 3. For specific descriptions, please refer to the relevant descriptions of S1305 to S1306, which will not be repeated here.

[0470] In S1606, if the vehicle terminal recognizes that the first navigation flow module is in the activated state, the navigation data is obtained from the first navigation application through the first navigation flow module.

[0471] In this embodiment, if the vehicle terminal recognizes that the synchronization service of the corresponding navigation task is enabled locally, in this case, the navigation task startup process can be triggered. Since the vehicle terminal is a terminal that has executed the navigation task, it is necessary to synchronize the navigation task in the vehicle terminal to other devices, that is, the user terminal. In this case, the vehicle terminal can obtain navigation data from the first navigation application through the local first navigation flow module.

[0472] In S1607, the vehicle terminal generates navigation synchronization information of the navigation data through the first navigation flow module.

[0473] Specifically, the implementation method of S1607 is exactly the same as the implementation method of S202 in the first embodiment. For a specific description, please refer to the relevant description of S202, which will not be repeated here.

[0474] In S1608, the user terminal receives the navigation synchronization information sent by the vehicle-mounted terminal, and transmits the navigation synchronization information to the second navigation application through the second navigation flow module.

[0475] Specifically, the implementation method of S1608 is exactly the same as the implementation method of S203 in the first embodiment. For a specific description, please refer to the relevant description of S203, which will not be repeated here.

[0476] Further, as another embodiment of the present application, the above S1608 may specifically include:

[0477] In S1608.1, the user terminal caches the navigation synchronization information in a cache area through the second navigation flow module, and detects a heartbeat signal of the communication connection with the vehicle-mounted terminal.

[0478] In this embodiment, after the vehicle terminal sends the navigation synchronization information to the user terminal, the user terminal may not immediately perform the synchronization operation of the navigation task, but caches the navigation synchronization information in the cache area first, and detects the heartbeat signal between the user terminal and the vehicle terminal for maintaining the activity of the near field communication connection. In some scenarios, when the user stops the car and opens the door, he actually just gets off the car to rest, rather than switching the navigation scene. Therefore, the user terminal can determine whether the user has left the vehicle by detecting the heartbeat signal, and then determine whether to update the navigation task of the local second navigation application.

[0479] Since a near-field communication connection is generally established between the vehicle-mounted terminal and the user terminal, and the two near-field communication connections are generally maintained through a heartbeat signal, a heartbeat signal will occur at a preset time interval, and the above time interval is a value less than the following effective time. Therefore, if the distance between the vehicle-mounted terminal and the user terminal is within the communicative range, the communicating parties will continue to send heartbeat signals at preset time intervals to maintain the above near-field communication connection, and the user terminal can determine whether the user is away from the vehicle by detecting the above heartbeat signal.

[0480] In S1608.2, if the user terminal does not receive the heartbeat signal within the preset effective time, it recognizes that the near field communication connection with the vehicle terminal is disconnected, and the navigation synchronization information is transmitted to the second navigation application.

[0481] In this embodiment, if the user terminal does not receive the heartbeat signal sent by the vehicle terminal within the preset effective time, it means that the user terminal has left the communication range of the vehicle terminal, or the vehicle terminal has been turned off. It can be determined that the navigation task needs to be continued locally. Therefore, the acquired navigation synchronization information can be transmitted to the second navigation application through the first navigation flow module, so that the second navigation application updates the navigation task according to the above navigation synchronization information. The user can continue to navigate through the user terminal, thereby realizing the navigation connection from the vehicle terminal to the user terminal.

[0482] In an embodiment of the present application, the user terminal first caches the navigation synchronization information in a cache area, and then detects the heartbeat signal between the vehicle-mounted terminal. In addition to triggering the navigation task synchronization operation through the parking and door closing event, it is also possible to determine whether the user has moved away from the vehicle by detecting the heartbeat signal within the effective time, thereby improving the accuracy of navigation task synchronization and avoiding misoperation.

[0483] In S1609, the user terminal updates the navigation task of the second navigation application according to the navigation synchronization information.

[0484] The implementation of S1609 in this embodiment is exactly the same as the implementation of S204 in the first embodiment. For a specific description, please refer to the relevant description of S204, which will not be repeated here. It should be noted that the user terminal can also generate corresponding update prompt information before updating the navigation task, and update the navigation task after receiving the update confirmation instruction.

[0485] In an embodiment of the present application, after the vehicle terminal detects a parking door closing event initiated by the user, it triggers the synchronization of the navigation task, so that the navigation task on the vehicle terminal can be automatically synchronized to the user terminal, without the user frequently setting the navigation destination, thereby improving the efficiency of navigation task synchronization.

[0486] Embodiment five:

[0487] Embodiments 1, 2, 3 and 4 illustrate the implementation process of the method for synchronizing navigation data across devices provided by the present application from the perspective of interaction between the first terminal and the second terminal. Unlike Embodiments 1 to 4, Embodiment 5 illustrates the implementation process of the method for synchronizing navigation data across devices provided by the present application from the perspective of the first terminal alone. Fig.17 The following is a flowchart showing a method for synchronizing navigation data across devices performed by a first terminal according to an embodiment of the present application. The specific description is as follows:

[0488] In S1701, if the preset cross-device transmission condition is met, the navigation data is obtained from the first navigation application through the first navigation flow module.

[0489] In S1702, navigation synchronization information corresponding to the navigation data is generated by the first navigation flow module.

[0490] In S1703, the navigation synchronization information is sent to the second terminal, and the navigation synchronization information is used to update the navigation task of the second navigation application in the second terminal. After receiving the navigation synchronization information, the second terminal transmits the received navigation synchronization information to the second navigation application through the second navigation flow module, and updates the navigation task of the second navigation application according to the navigation synchronization information.

[0491] The implementation of S1701 in this embodiment is exactly the same as that of S201 in the first embodiment, the implementation of S1702 in the embodiment is exactly the same as that of S202 in the first embodiment, and the implementation of S1703 in the embodiment is exactly the same as that of S203 in the first embodiment. For specific descriptions, please refer to the relevant descriptions of S201 to S203, which will not be repeated here.

[0492] Optionally, if a preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0493] In response to a touch operation with the second terminal, receiving a communication tag sent by a second near field communication module of the second terminal;

[0494] In response to the communication tag, the first navigation flow module is started, and the navigation data is obtained from the first navigation application through the first navigation flow module.

[0495] In this embodiment, the implementation method of the above two steps is exactly the same as the implementation method of S1103 and S1104 in the second embodiment. For specific descriptions, please refer to the relevant descriptions of S1103 and S1104, which will not be repeated here.

[0496] Optionally, when the second terminal detects that a tag writing condition is met, the communication tag sends a tag writing request to the tag service thread through the second navigation flow module, and the tag service thread writes the tag to the second near-field communication module in response to the tag writing request.

[0497] Optionally, if a preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0498] receiving a navigation transfer notification sent by the second terminal; the navigation transfer notification is sent to the first terminal when the second terminal detects that the second navigation transfer module of the second terminal is in an activated state after the second terminal is connected to the first terminal;

[0499] In response to the navigation flow notification, navigation data is obtained from the first navigation application through the first navigation flow module.

[0500] In this embodiment, the implementation methods of the above two steps are exactly the same as the implementation methods of S1306 and S1307. For specific descriptions, please refer to the relevant descriptions of S1306 to S1307, which will not be repeated here.

[0501] Optionally, before receiving the navigation flow transfer notification sent by the second terminal, the method further includes:

[0502] Receiving a wake-up instruction sent by the second terminal through the second near field communication module;

[0503] In response to the wake-up instruction, a wireless connection request is sent to the second terminal to establish the communication connection with the second terminal.

[0504] In this embodiment, the implementation methods of the above two steps are exactly the same as the implementation methods of S1304.4 and S1304.5 in the third embodiment. For specific descriptions, please refer to the relevant descriptions of S1304.4 to S1304.5, which will not be repeated here.

[0505] Optionally, the first terminal is a vehicle intelligent control terminal installed on a vehicle; the second terminal is a user terminal carried by a user;

[0506] Correspondingly, if the preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes:

[0507] If a parking event related to the vehicle is detected, a near field communication connection is established with the second terminal; the near field communication connection is used to send navigation synchronization information to the second terminal;

[0508] If the first navigation flow module is in the activated state, the navigation data is obtained from the first navigation application through the first navigation flow module.

[0509] In this embodiment, the implementation methods of the above two steps are exactly the same as the implementation methods of S1604 and S1605 in the fourth embodiment. For specific descriptions, please refer to the relevant descriptions of S1604 to S1605, which will not be repeated here.

[0510] Optionally, if a parking event related to the vehicle is detected, establishing a near field communication connection with the second terminal includes:

[0511] Identifying the connection status of each registered terminal in a preset registered device list through the second navigation flow module;

[0512] If the second terminal is in the registered device list and the connection state of the second terminal is a connectable state, establishing the near field communication connection with the second terminal based on the connection information associated with the second terminal in the registered device list;

[0513] If the second terminal is not in the registered device list, or the second terminal is in the registered device list and the connection state of the second terminal is an unconnectable state, a wake-up instruction is sent to the second terminal through the first near-field communication module, and the wake-up instruction is used to enable the second terminal to establish the communication connection with the first terminal.

[0514] In this embodiment, the implementation method of the above three steps is exactly the same as the implementation method of S1604.1 to S1604.4 in the fourth embodiment. For specific descriptions, please refer to the relevant descriptions of S1604.1 to S1604.4, which will not be repeated here.

[0515] Optionally, before obtaining navigation data from the first navigation application through the first navigation flow module if the preset cross-device transmission condition is met, the method further includes:

[0516] In response to a navigation operation of a user, generating a navigation task through the first navigation application; the navigation data is generated based on the navigation task;

[0517] receiving, through the first navigation transfer module, a service registration instruction transmitted by the first navigation application; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices;

[0518] In response to the service registration instruction, the first navigation application is added to the navigation synchronization application list, and the first navigation flow module is set to a startup state; the startup state is used to send navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission condition is met.

[0519] In this embodiment, the above three steps are implemented in exactly the same manner as S200.1 to S200.3 in the first embodiment. For specific descriptions, please refer to the relevant descriptions of S200.1 to S200.3, which will not be repeated here.

[0520] Optionally, after sending the navigation synchronization information to the second terminal, the method further includes:

[0521] receiving navigation synchronization completion information fed back by the second terminal through the second navigation flow module;

[0522] In response to the navigation synchronization completion information, an end instruction regarding the navigation task is transmitted to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0523] In this embodiment, the above two steps are implemented in exactly the same manner as S205 and S206 in the first embodiment. For specific descriptions, please refer to the relevant descriptions of S205 to S206, which will not be repeated here.

[0524] Optionally, before sending the navigation synchronization information to the second terminal, the method further includes:

[0525] Acquire a navigation application list of the second terminal; the navigation application list includes the second navigation application;

[0526] If the navigation application list contains a navigation application that matches the first navigation application, the navigation synchronization information is sent to the second terminal; the navigation application that matches the first navigation application is specifically an application that has permission to transmit navigation data across devices with the first navigation application.

[0527] In this embodiment, the above two steps are implemented in exactly the same manner as S203.1 and S203.2 in the first embodiment. For specific descriptions, please refer to the relevant descriptions of S203.1 to S203.2, which will not be repeated here.

[0528] In this embodiment, the first terminal can also automatically obtain the navigation data of the navigation task that has been turned on from the first navigation application through the first navigation flow module local to the first terminal when detecting that the cross-device transmission conditions are met, and generate navigation synchronization information corresponding to the navigation data through the first navigation flow module, and send the navigation synchronization information to the second terminal, thereby realizing the cross-device transmission of the navigation data. After receiving the above navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through the local second navigation flow module, and then the second terminal can update the navigation task of the second navigation application according to the navigation synchronization information, thereby realizing the synchronization of navigation tasks across devices. Compared with the existing navigation technology, the present application can realize the synchronization of navigation tasks across devices. In the scenario where cross-device navigation is required, the user does not need to set tasks for the terminal's navigation application multiple times, but can automatically realize the flow of navigation data through the navigation flow module to update the navigation tasks in the navigation application, thereby greatly improving the efficiency of navigation task setting and reducing the user's repeated operations. On the other hand, after the first navigation flow module in the first terminal obtains the navigation data from the first navigation application, it does not directly send the navigation data to the second navigation flow module of the second terminal, but converts the navigation data into corresponding navigation synchronization information. The navigation synchronization information can be transmitted in the navigation flow modules of different terminals, and then transmitted to the second navigation application through the second navigation flow module. It is not a direct transmission between the navigation applications in the two terminals. Therefore, there is no need to install the same navigation application on the first terminal and the second terminal. Navigation data flow across devices and applications can be realized, further improving the application scope of navigation task synchronization.

[0529] Embodiment six:

[0530] Embodiments 1, 2, 3 and 4 illustrate the implementation process of the cross-device navigation data synchronization method provided by the present application from the perspective of interaction between the first terminal and the second terminal. Unlike Embodiments 1 to 4, Embodiment 6 illustrates the implementation process of the cross-device navigation data synchronization method provided by the present application from the perspective of the second terminal. Fig.18 The following is a flowchart showing a method for synchronizing navigation data across devices performed by a second terminal according to an embodiment of the present application. The specific description is as follows:

[0531] In S1801, receiving navigation synchronization information sent by a first terminal; the navigation synchronization information is generated based on navigation data of a first navigation application in the first terminal;

[0532] In S1802, the navigation synchronization information is transmitted to the second navigation application through the second navigation flow module;

[0533] In S1803, the navigation task of the second navigation application is updated based on the navigation synchronization information.

[0534] In this embodiment, S1801 and S1802 are implemented in exactly the same manner as S203 in the first embodiment, and S1803 is implemented in exactly the same manner as S204. For specific descriptions, please refer to the relevant descriptions of S203 and S204, which will not be repeated here.

[0535] Optionally, the receiving navigation synchronization information sent by the first terminal includes:

[0536] In response to a touch operation with the first terminal, a communication tag is sent to the first terminal through a second near field communication module, so that the first terminal responds to the communication tag, starts a first navigation flow module, and obtains the navigation data from the first navigation application through the first navigation flow module.

[0537] In this embodiment, the above steps are implemented in exactly the same manner as S1103 in Embodiment 2. For specific descriptions, please refer to the relevant descriptions of S1103, which will not be repeated here.

[0538] The navigation synchronization information is received, which is sent by the first terminal through the first navigation flow module.

[0539] In this embodiment, the above steps are implemented in exactly the same manner as S1110 in the second embodiment. For specific descriptions, please refer to the relevant descriptions of S1110, which will not be repeated here.

[0540] Optionally, before sending the communication tag to the first terminal through the second near field communication module in response to the touch operation with the first terminal, the method further includes:

[0541] If the preset tag writing condition is met, sending a tag writing request to the tag service thread through the second navigation flow module;

[0542] The tag service thread responds to the tag write request to write the communication tag to the second near field communication module.

[0543] In this embodiment, the above two steps are implemented in exactly the same manner as S1101 to S1102 in the second embodiment. For specific descriptions, please refer to the relevant descriptions of S1101 to S1102, which will not be repeated here.

[0544] Optionally, the second terminal is a vehicle intelligent control terminal installed on the vehicle;

[0545] Correspondingly, before receiving the navigation synchronization information sent by the first terminal, the method further includes:

[0546] If a door opening event of the vehicle is detected, establishing a communication connection with the first terminal;

[0547] Obtaining a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtaining a setting state of the second navigation flow module;

[0548] If the second navigation flow module is in the activated state, a navigation flow notification is sent to the first terminal, so that the first terminal sends the navigation synchronization information.

[0549] In this embodiment, the above three steps are implemented in exactly the same manner as S1304 to S1306 in the third embodiment. For specific descriptions, please refer to the relevant descriptions of S1304 to S1306, which will not be repeated here.

[0550] Optionally, if a door opening event of the vehicle is detected, establishing a communication connection with the first terminal includes:

[0551] Identifying the connection status of each registered terminal in a preset registered device list through the second navigation flow module;

[0552] If the first terminal is in the registered device list and the connection state of the first terminal is a connectable state, establishing the communication connection with the first terminal based on the connection information associated with the first terminal in the registered device list;

[0553] If the first terminal is not in the registered device list, or the first terminal is in the registered device list and the connection state of the first terminal is an unconnectable state, a wake-up instruction is sent to the first terminal through the second near-field communication module, and the wake-up instruction is used to enable the first terminal to establish the near-field communication connection with the second terminal.

[0554] In this embodiment, the above three steps are implemented in exactly the same manner as S1304.1 to S1304.3 in Embodiment 3. For specific descriptions, please refer to the relevant descriptions of S1304 to S1306, which will not be repeated here.

[0555] Optionally, the second terminal is a user terminal carried by a user; the first terminal is a vehicle intelligent control terminal installed on a vehicle;

[0556] Correspondingly, the transmitting the navigation synchronization information to the second navigation application through the second navigation flow module includes:

[0557] Cache the navigation synchronization information in a cache area through the second navigation flow module, and detect a heartbeat signal of a near field communication connection with the first terminal;

[0558] If the heartbeat signal is not received within the preset effective time, it is recognized that the near field communication connection with the first terminal is disconnected, and the navigation synchronization information is transmitted to the second navigation application.

[0559] In this embodiment, the above two steps are implemented in exactly the same manner as S1608.1 and S1608.2 in Embodiment 4. For specific descriptions, please refer to the relevant descriptions of S1608.1 to S1608.2, which will not be repeated here.

[0560] Optionally, after receiving the navigation synchronization information sent by the first terminal, the method further includes:

[0561] Detecting whether there is a navigation application matching the first navigation application in a navigation application list; the navigation application list includes the first navigation application;

[0562] If it is detected that there is a navigation application matching the first navigation application in the navigation application list, the navigation application matching the first navigation application will be used as the second navigation application, and the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module will be performed; the navigation application matching the first navigation application is specifically: an application that has the permission to transmit navigation data across devices with the second navigation application.

[0563] In this embodiment, the above two steps are implemented in exactly the same manner as S203.1 to S203.2 in the first embodiment. For specific descriptions, please refer to the relevant descriptions of S203.1 to S203.2, which will not be repeated here.

[0564] Optionally, updating the navigation task of the second navigation application based on the navigation synchronization information includes:

[0565] determining a navigation destination based on the navigation synchronization information, and generating task update prompt information based on the navigation destination;

[0566] If an update confirmation instruction based on the update prompt information feedback is received, the navigation task is updated based on the navigation destination.

[0567] In this embodiment, the above two steps are implemented in exactly the same manner as S204.1 to S204.2 in the first embodiment. For specific descriptions, please refer to the relevant descriptions of S204.1 to S204.2, which will not be repeated here.

[0568] Optionally, if an update confirmation instruction based on the update prompt information feedback is received, updating the navigation task based on the navigation destination includes:

[0569] Navigation synchronization completion information is sent to the first terminal, so that the first terminal responds to the navigation synchronization completion information and transmits an end instruction of the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0570] In this embodiment, the above steps are implemented in exactly the same manner as S205 in the first embodiment. For a specific description, please refer to the relevant description of S205, which will not be repeated here.

[0571] Embodiment seven:

[0572] Corresponding to the method for synchronizing navigation tasks across devices described in the fifth embodiment above, Fig.19 A structural block diagram of a synchronization device for navigation tasks across devices provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0573] Reference Fig.19 , the synchronization device of the cross-device navigation task includes:

[0574] The navigation data acquisition unit 191 is configured to acquire navigation data from the first navigation application through the first navigation flow module if a preset cross-device transmission condition is met;

[0575] A navigation synchronization information generating unit 192, configured to generate navigation synchronization information corresponding to the navigation data through the first navigation flow module;

[0576] The navigation synchronization information sending unit 193 is used to send the navigation synchronization information to the second terminal, where the navigation synchronization information is used to update the navigation task of the second navigation application in the second terminal.

[0577] Optionally, the navigation data acquiring unit 191 includes:

[0578] a communication tag receiving unit, configured to receive a communication tag sent by a second near field communication module of the second terminal in response to a touch operation with the second terminal; the communication tag carries a start mark for navigation task synchronization;

[0579] The navigation flow module starting unit is used to start the first navigation flow module in response to the communication tag, and obtain the navigation data from the first navigation application through the first navigation flow module.

[0580] Optionally, the communication tag is obtained after the second terminal detects that the tag writing condition is met, sends a tag write request to the tag service thread through the second navigation flow module, responds to the tag write request through the tag service thread, adds the start identifier to the communication tag, and writes the communication tag to the second near-field communication module.

[0581] Optionally, the navigation data acquiring unit 191 includes:

[0582] a navigation transfer notification receiving unit, configured to receive a navigation transfer notification sent by the second terminal; the navigation transfer notification is sent to the first terminal when the second terminal detects that the second navigation transfer module of the second terminal is in an activated state after the second terminal is connected to the first terminal;

[0583] The navigation flow notification response unit is used to obtain navigation data from the first navigation application through the first navigation flow module in response to the navigation flow notification.

[0584] Optionally, the navigation task synchronization device further includes:

[0585] A wake-up instruction receiving unit, configured to receive a wake-up instruction sent by the second terminal via the second near field communication module;

[0586] The wake-up instruction corresponding unit is used to send a wireless connection request to the second terminal in response to the wake-up instruction to establish the communication connection with the second terminal.

[0587] Optionally, the first terminal is a vehicle intelligent control terminal installed on a vehicle; the second terminal is a user terminal carried by a user;

[0588] Correspondingly, the navigation data acquisition unit 191 includes:

[0589] a parking door opening trigger unit, configured to establish a near field communication connection with the second terminal if a parking event related to the vehicle is detected; the near field communication connection is used to send navigation synchronization information to the second terminal;

[0590] A first state identification unit, configured to obtain a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtain a setting state of the first navigation flow module;

[0591] The first startup state response unit is configured to obtain navigation data from the first navigation application through the first navigation flow module if the first navigation flow module is in the startup state.

[0592] Optionally, the parking door opening trigger unit includes:

[0593] A connection status detection unit, configured to identify the connection status of each registered terminal in a preset registered device list through the second navigation flow module;

[0594] a direct connection triggering unit, configured to establish the near field communication connection with the second terminal based on the connection information associated with the second terminal in the registered device list if the second terminal is in the registered device list and the connection state of the second terminal is a connectable state;

[0595] A wake-up instruction sending unit is used to send a wake-up instruction to the second terminal through the first near-field communication module if the second terminal is not in the registered device list, or the second terminal is in the registered device list and the connection state of the second terminal is an unconnectable state, wherein the wake-up instruction is used to enable the second terminal to establish the communication connection with the first terminal.

[0596] Optionally, the navigation task synchronization device further includes:

[0597] A navigation operation response unit, configured to generate a navigation task through the first navigation application in response to a user's navigation operation; the navigation data is generated based on the navigation task;

[0598] A service registration unit, configured to receive a service registration instruction transmitted by the first navigation application through the first navigation flow module; the service registration instruction is used to authorize the first navigation application to have the authority to transmit navigation data between devices;

[0599] A service registration response unit is used to respond to the service registration instruction, add the first navigation application to the navigation synchronization application list, and set the first navigation flow module to a startup state; the startup state is used to send the navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission condition is met.

[0600] Optionally, the navigation task synchronization device further includes:

[0601] A navigation synchronization completion information receiving unit, configured to receive navigation synchronization completion information fed back by the second terminal through the second navigation flow module;

[0602] A navigation ending unit is used to transmit an ending instruction about the navigation task to the first navigation application through the first navigation flow module in response to the navigation synchronization completion information, so as to stop the navigation task of the first navigation application.

[0603] Optionally, the synchronization device for the navigation task further includes:

[0604] A navigation application list acquiring unit, configured to acquire a navigation application list of the second terminal; the navigation application list includes the second navigation application;

[0605] A navigation application matching unit is used to send the navigation synchronization information to the second terminal if a navigation application matching the first navigation application exists in the navigation application list; the navigation application matching the first navigation application is specifically: an application that has the permission to transmit navigation data across devices with the first navigation application.

[0606] Therefore, the synchronization device for navigation tasks across devices provided in the embodiment of the present application can also automatically obtain the navigation data of the navigation task that has been turned on from the first navigation application through the first navigation flow module local to the first terminal when the first terminal detects that the cross-device transmission conditions are met, and generate navigation synchronization information corresponding to the navigation data through the first navigation flow module, and send the navigation synchronization information to the second terminal, thereby realizing the cross-device transmission of navigation data. After receiving the above-mentioned navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through the local second navigation flow module, and then the second terminal can update the navigation task of the second navigation application according to the navigation synchronization information, thereby realizing the synchronization of navigation tasks across devices. Compared with the existing navigation technology, the present application can realize the synchronization of navigation tasks across devices. In the scenario where cross-device navigation is required, the user does not need to set tasks for the navigation application of the terminal multiple times, but can automatically realize the flow of navigation data through the navigation flow module to update the navigation tasks in the navigation application, thereby greatly improving the efficiency of navigation task setting and reducing the user's repeated operations. On the other hand, after the first navigation flow module in the first terminal obtains the navigation data from the first navigation application, it does not directly send the navigation data to the second navigation flow module of the second terminal, but converts the navigation data into corresponding navigation synchronization information. The navigation synchronization information can be transmitted in the navigation flow modules of different terminals, and then transmitted to the second navigation application through the second navigation flow module. It is not a direct transmission between the navigation applications in the two terminals. Therefore, there is no need to install the same navigation application on the first terminal and the second terminal. Navigation data flow across devices and applications can be realized, further improving the application scope of navigation task synchronization.

[0607] Embodiment eight:

[0608] Corresponding to the method for synchronizing navigation tasks across devices described in the fifth embodiment above, Fig. 20 A structural block diagram of a synchronization device for navigation tasks across devices provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0609] Reference Fig. 20, the synchronization device of the cross-device navigation task includes:

[0610] The navigation synchronization information receiving unit 201 is used to receive navigation synchronization information sent by the first terminal; the navigation synchronization information is generated based on the navigation data of the first navigation application in the first terminal;

[0611] A navigation synchronization information transmission unit 202, configured to transmit the navigation synchronization information to a second navigation application via a second navigation flow module;

[0612] The navigation task updating unit 203 is configured to update the navigation task of the second navigation application based on the navigation synchronization information.

[0613] Optionally, the navigation synchronization information receiving unit 201 includes:

[0614] a communication tag sending unit door, configured to send a communication tag to the first terminal through a second near field communication module in response to a touch operation with the first terminal, so that the first terminal responds to the communication tag, starts a first navigation flow module, and obtains the navigation data from the first navigation application through the first navigation flow module; the communication tag carries a start mark for synchronizing the navigation task;

[0615] The touch operation feedback unit is used to receive the navigation synchronization information sent by the first terminal through the first navigation flow module.

[0616] Optionally, the synchronization device for the navigation task further includes:

[0617] A tag writing request unit, configured to send a tag writing request to the tag service thread through the second navigation flow module if a preset tag writing condition is met;

[0618] A communication tag writing unit is used to respond to the tag writing request through the tag service thread, add the startup identifier to the communication tag, and write the communication tag to the second near field communication module.

[0619] Optionally, the second terminal is a vehicle intelligent control terminal installed on the vehicle;

[0620] Correspondingly, the synchronization device of the navigation task also includes:

[0621] a door opening event triggering unit, configured to establish a communication connection with the first terminal if a door opening event related to the vehicle is detected;

[0622] A second state identification unit, configured to obtain a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtain a setting state of the second navigation flow module;

[0623] The second startup state response unit is configured to send a navigation flow notification to the first terminal if the second navigation flow module is in the startup state, so that the first terminal sends the navigation synchronization information.

[0624] Optionally, the door opening event triggering unit includes:

[0625] A connection status determination unit, configured to identify the connection status of each registered terminal in a preset registered device list through the second navigation flow module;

[0626] a direct connection transmission unit, configured to establish the communication connection with the first terminal based on the connection information associated with the first terminal in the registered device list if the first terminal is in the registered device list and the connection state of the first terminal is a connectable state;

[0627] A wake-up execution unit is used to send a wake-up instruction to the first terminal through a second near-field communication module if the first terminal is not in the registered device list, or the first terminal is in the registered device list and the connection state of the first terminal is an unconnectable state, and the wake-up instruction is used to enable the first terminal to establish the communication connection with the second terminal.

[0628] Optionally, the second terminal is a user terminal carried by a user; the first terminal is a vehicle intelligent control terminal installed on a vehicle;

[0629] Correspondingly, the navigation synchronization information transmission unit 202 includes:

[0630] an information caching unit, configured to cache the navigation synchronization information in a cache area through the second navigation flow module, and detect a heartbeat signal of the communication connection with the first terminal;

[0631] The heartbeat signal monitoring unit is used to identify and disconnect the near field communication connection with the first terminal if the heartbeat signal is not received within a preset effective time, and transmit the navigation synchronization information to the second navigation application.

[0632] Optionally, the synchronization device for the navigation task further includes:

[0633] a matching application detection unit, configured to detect whether there is a navigation application matching the first navigation application in a navigation application list; the navigation application list includes the first navigation application;

[0634] A second navigation application identification unit is used to, if it is detected that a navigation application matching the first navigation application exists in the navigation application list, use the navigation application matching the first navigation application as the second navigation application, and execute the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module; the navigation application matching the first navigation application is specifically: an application that has the authority to transmit navigation data across devices with the second navigation application.

[0635] Optionally, the navigation task updating unit 203 includes:

[0636] an update prompt information generating unit, configured to determine a navigation destination based on the navigation synchronization information, and generate task update prompt information based on the navigation destination;

[0637] An update confirmation instruction response unit is used to update the navigation task based on the navigation destination if an update confirmation instruction based on the update prompt information feedback is received.

[0638] Optionally, the synchronization device for the navigation task further includes:

[0639] The navigation synchronization completion information sending unit is used to send navigation synchronization completion information to the first terminal, so that the first terminal responds to the navigation synchronization completion information and transmits an end instruction about the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

[0640] The method for synchronizing navigation tasks across devices provided in the embodiments of the present application can be applied to terminal devices such as smart phones, tablet computers, wearable devices, vehicle-mounted terminals, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), etc. The embodiments of the present application do not impose any restrictions on the specific types of terminal devices.

[0641] For example, the terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a computer, a laptop computer, a handheld communication device, a handheld computing device, and / or other devices for communicating on a wireless system and a next-generation communication system, such as a mobile terminal in a 5G network or a mobile terminal in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0642] Fig.21 A schematic structural diagram of a terminal device 100 is shown.

[0643] The terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0644] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0645] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0646] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0647] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0648] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0649] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface, thereby realizing the touch function of the terminal device 100.

[0650] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to achieve communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 via the I2S interface to achieve the function of answering a call through a Bluetooth headset.

[0651] The PCM interface can also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface to realize the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0652] The UART interface is a universal serial data bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is generally used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

[0653] The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the shooting function of the terminal device 100. The processor 110 and the display screen 194 communicate via the DSI interface to implement the display function of the terminal device 100.

[0654] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0655] The USB interface 130 is an interface that complies with the USB standard specification, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the terminal device 100, and can also be used to transmit data between the terminal device 100 and peripheral devices. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other terminal devices, such as AR devices, etc.

[0656] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic illustration and does not constitute a structural limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0657] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the terminal device 100. While the charging management module 140 is charging the battery 142, it may also power the terminal device through the power management module 141.

[0658] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0659] The wireless communication function of the terminal device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0660] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0661] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the terminal device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0662] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0663] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the terminal device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0664] In some embodiments, the antenna 1 of the terminal device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the terminal device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0665] The terminal device 100 realizes the display function through GPU, display screen 194, and application processor etc. GPU is a microprocessor for image processing, connecting display screen 194 and application processor. GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or change display information. Wherein, the above-mentioned display screen 194 can specifically display the generated test report so that the user can view the test report through the display screen 194.

[0666] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the terminal device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1. The display screen 194 may include a touch panel and other input devices.

[0667] The terminal device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0668] ISP is used to process the data fed back by camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to ISP for processing and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, ISP can be set in camera 193.

[0669] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the terminal device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0670] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the terminal device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0671] Video codecs are used to compress or decompress digital videos. The terminal device 100 may support one or more video codecs. Thus, the terminal device 100 may play or record videos in various coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0672] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of the terminal device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0673] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0674] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the terminal device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the terminal device 100 by running instructions stored in the internal memory 121, and / or instructions stored in a memory provided in the processor.

[0675] The terminal device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0676] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

[0677] The speaker 170A, also called a "speaker", is used to convert an audio electrical signal into a sound signal. The terminal device 100 can listen to music or listen to a hands-free call through the speaker 170A. In particular, the speaker 170A can be used to output prompt information to inform the user of the part that needs to be touched by the electronic scale.

[0678] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the terminal device 100 receives a call or voice message, the voice can be received by placing the receiver 170B close to the ear.

[0679] Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The terminal device 100 can be provided with at least one microphone 170C. In other embodiments, the terminal device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the terminal device 100 can also be provided with three, four or more microphones 170C to realize the collection of sound signals, noise reduction, identification of sound sources, realization of directional recording function, etc.

[0680] The earphone interface 170D is used to connect a wired earphone and can be a USB interface 130 or a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0681] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. For example, the terminal device can obtain the user's weight through the pressure sensor 180A. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The terminal device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation acts on the display screen 194, the terminal device 100 detects the touch operation intensity according to the pressure sensor 180A. The terminal device 100 can also calculate the touch position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to a first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0682] The gyroscope sensor 180B can be used to determine the motion posture of the terminal device 100. In some embodiments, the angular velocity of the terminal device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the terminal device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the terminal device 100 through reverse movement to achieve anti-shake. The gyroscope sensor 180B can also be used for navigation and somatosensory game scenes.

[0683] The air pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

[0684] The magnetic sensor 180D includes a Hall sensor. The terminal device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the terminal device 100 is a flip phone, the terminal device 100 can detect the opening and closing of the flip cover according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, the flip cover automatic unlocking and other features are set.

[0685] The acceleration sensor 180E can detect the magnitude of the acceleration of the terminal device 100 in various directions (generally three axes). When the terminal device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the terminal device and applied to applications such as horizontal and vertical screen switching and pedometers.

[0686] The distance sensor 180F is used to measure the distance. The terminal device 100 can measure the distance by infrared or laser. In some embodiments, when shooting a scene, the terminal device 100 can use the distance sensor 180F to measure the distance to achieve fast focusing.

[0687] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal device 100 emits infrared light outward through the light emitting diode. The terminal device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the terminal device 100. When insufficient reflected light is detected, the terminal device 100 can determine that there is no object near the terminal device 100. The terminal device 100 can use the proximity light sensor 180G to detect that the user holds the terminal device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode, and pocket mode automatically unlocks and locks the screen.

[0688] The ambient light sensor 180L is used to sense the ambient light brightness. The terminal device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the terminal device 100 is in a pocket to prevent accidental touch.

[0689] The fingerprint sensor 180H is used to collect fingerprints. The terminal device 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0690] The temperature sensor 180J is used to detect temperature. In some embodiments, the terminal device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the terminal device 100 reduces the performance of the processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the terminal device 100 heats the battery 142 to avoid abnormal shutdown of the terminal device 100 due to low temperature. In other embodiments, when the temperature is lower than another threshold, the terminal device 100 performs a boost on the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

[0691] The touch sensor 180K is also called a "touch control device". The touch sensor 180K can be set on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the terminal device 100, which is different from the position of the display screen 194.

[0692] The bone conduction sensor 180M can obtain a vibration signal. In some embodiments, the bone conduction sensor 180M can obtain a vibration signal of a vibrating bone block of the vocal part of the human body. The bone conduction sensor 180M can also contact the human pulse to receive a blood pressure beat signal. In some embodiments, the bone conduction sensor 180M can also be set in an earphone and combined into a bone conduction earphone. The audio module 170 can parse out a voice signal based on the vibration signal of the vibrating bone block of the vocal part obtained by the bone conduction sensor 180M to realize a voice function. The application processor can parse the heart rate information based on the blood pressure beat signal obtained by the bone conduction sensor 180M to realize a heart rate detection function.

[0693] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The terminal device 100 may receive key input and generate key signal input related to user settings and function control of the terminal device 100.

[0694] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0695] Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0696] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and separated from the terminal device 100 by inserting the SIM card interface 195 or pulling it out from the SIM card interface 195. The terminal device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the terminal device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100.

[0697] The software system of the terminal device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present invention takes the Android system of the layered architecture as an example to exemplify the software structure of the terminal device 100.

[0698] Fig. 22 It is a software structure block diagram of the terminal device of an embodiment of the present application.

[0699] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the system layer of the Android runtime (Android runtime), and the kernel layer.

[0700] The application layer can include a series of application packages.

[0701] like Fig. 22 As shown, the application package may include camera, calendar, map, WLAN, Bluetooth, music, video, short message, mailbox, WeChat, WPS and other applications.

[0702] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0703] like Fig. 22 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

[0704] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0705] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0706] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0707] The phone manager is used to provide communication functions for terminal devices, such as the management of call status (including answering, hanging up, etc.).

[0708] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0709] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, the terminal device vibrates, the indicator light flashes, etc.

[0710] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

[0711] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0712] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0713] The system layer may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0714] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

[0715] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0716] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis and layer processing, etc.

[0717] A 2D graphics engine is a drawing engine for 2D drawings.

[0718] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

[0719] The following is an illustrative description of the software and hardware workflow of the terminal device 100 in conjunction with the capture and photo shooting scene.

[0720] When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, timestamp of the touch operation, and other information). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event. For example, if the touch operation is a touch single-click operation and the control corresponding to the single-click operation is the control of the camera application icon, the camera application calls the interface of the application framework layer to start the camera application, and then starts the camera driver by calling the kernel layer to capture static images or videos through the camera 193.

[0721] Fig.23 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. Fig.23 As shown, the terminal device 23 of this embodiment includes: at least one processor 230 ( Fig.23 Only one processor is shown in the figure), a memory 231, and a computer program 232 stored in the memory 231 and executable on the at least one processor 230, wherein the processor 230 implements the steps in the above-mentioned synchronization method embodiment of any individual cross-device navigation task when executing the computer program 232.

[0722] The terminal device 23 may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The terminal device may include, but is not limited to, a processor 230 and a memory 231. Those skilled in the art will appreciate that Fig.23 It is only an example of the terminal device 23 and does not constitute a limitation on the terminal device 23. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components, for example, it may also include input and output devices, network access devices, etc.

[0723] The processor 230 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0724] In some embodiments, the memory 231 may be an internal storage unit of the terminal device 23, such as a hard disk or memory of the terminal device 23. In other embodiments, the memory 231 may also be an external storage device of the terminal device 23, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device 23. Further, the memory 231 may also include both an internal storage unit and an external storage device of the terminal device 23. The memory 231 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program. The memory 231 may also be used to temporarily store data that has been output or is to be output.

[0725] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0726] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0727] An embodiment of the present application also provides a terminal device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor implements the steps in any of the above-mentioned method embodiments when executing the computer program.

[0728] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0729] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0730] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium can at least include: any entity or device that can carry the computer program code to the camera / terminal device, recording medium, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, RandomAccess Memory), electric carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0731] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0732] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0733] In the embodiments provided in the present application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0734] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0735] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for synchronizing navigation tasks across devices, applied to a first terminal, characterized in that: include: If the preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module; Generate navigation synchronization information corresponding to the navigation data by the first navigation flow module; The navigation synchronization information is sent to a second terminal, where the navigation synchronization information is used to update a navigation task of a second navigation application in the second terminal.

2. The synchronization method according to claim 1, characterized in that: If the preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes: In response to a touch operation with the second terminal, receiving a communication tag sent by a second near field communication module of the second terminal; the communication tag carries a start mark of navigation task synchronization; In response to the communication tag, the first navigation flow module is started, and the navigation data is obtained from the first navigation application through the first navigation flow module.

3. The synchronization method according to claim 2, characterized in that: The communication tag is obtained after the second terminal detects that the tag writing condition is met, sends a tag writing request to the tag service thread through the second navigation flow module, responds to the tag writing request through the tag service thread, adds the startup identifier to the communication tag, and writes the communication tag to the second near-field communication module.

4. The synchronization method according to claim 1, characterized in that: If the preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes: receiving a navigation transfer notification sent by the second terminal; the navigation transfer notification is sent to the first terminal when the second terminal detects that the second navigation transfer module of the second terminal is in an activated state after the second terminal is connected to the first terminal; In response to the navigation flow notification, navigation data is obtained from the first navigation application through the first navigation flow module.

5. The synchronization method according to claim 4, characterized in that: Before receiving the navigation flow transfer notification sent by the second terminal, the method further includes: Receiving a wake-up instruction sent by the second terminal through the second near field communication module; In response to the wake-up instruction, a wireless connection request is sent to the second terminal to establish the communication connection with the second terminal.

6. The synchronization method according to claim 1, characterized in that: The first terminal is a vehicle intelligent control terminal installed on the vehicle; the second terminal is a user terminal carried by the user; If the preset cross-device transmission condition is met, obtaining navigation data from the first navigation application through the first navigation flow module includes: If a parking event related to the vehicle is detected, a near field communication connection is established with the second terminal; the near field communication connection is used to send navigation synchronization information to the second terminal; Obtaining a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtaining a setting state of the first navigation flow module; If the first navigation flow module is in the activated state, the navigation data is obtained from the first navigation application through the first navigation flow module.

7. The synchronization method according to any one of claims 1 to 6, characterized in that: After sending the navigation synchronization information to the second terminal, the method further includes: receiving navigation synchronization completion information fed back by the second terminal through the second navigation flow module; In response to the navigation synchronization completion information, an end instruction regarding the navigation task is transmitted to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

8. The synchronization method according to any one of claims 1 to 7, characterized in that: Before sending the navigation synchronization information to the second terminal, the method further includes: Acquire a navigation application list of the second terminal; the navigation application list includes the second navigation application; If the navigation application list contains a navigation application that matches the first navigation application, the navigation synchronization information is sent to the second terminal; the navigation application that matches the first navigation application is specifically an application that has permission to transmit navigation data across devices with the first navigation application.

9. A method for synchronizing navigation tasks across devices, applied to a second terminal, characterized in that: include: Receiving navigation synchronization information sent by the first terminal; The navigation synchronization information is generated based on navigation data of a first navigation application in the first terminal; transmitting the navigation synchronization information to the second navigation application through the second navigation flow module; The navigation task of the second navigation application is updated based on the navigation synchronization information.

10. The synchronization method according to claim 9, characterized in that: The receiving navigation synchronization information sent by the first terminal includes: In response to a touch operation with the first terminal, a communication tag is sent to the first terminal through a second near field communication module, so that the first terminal responds to the communication tag, starts a first navigation flow module, and obtains the navigation data from the first navigation application through the first navigation flow module; the communication tag carries a start mark of navigation task synchronization; The navigation synchronization information is received, which is sent by the first terminal through the first navigation flow module.

11. The synchronization method according to claim 10, characterized in that: Before sending the communication tag to the first terminal through the second near field communication module in response to the touch operation with the first terminal, the method further includes: If the preset tag writing condition is met, sending a tag writing request to the tag service thread through the second navigation flow module; The tag service thread responds to the tag write request, adds the start identifier to the communication tag, and writes the communication tag to the second near field communication module.

12. The synchronization method according to claim 9, characterized in that: The second terminal is a vehicle intelligent control terminal installed on the vehicle; Before receiving the navigation synchronization information sent by the first terminal, the method further includes: If a door opening event of the vehicle is detected, establishing a communication connection with the first terminal; Obtaining a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtaining a setting state of the second navigation flow module; If the second navigation flow module is in the activated state, a navigation flow notification is sent to the first terminal, so that the first terminal sends the navigation synchronization information.

13. The synchronization method according to claim 9, characterized in that: The second terminal is a user terminal carried by a user; the first terminal is a vehicle intelligent control terminal installed on a vehicle; The transmitting the navigation synchronization information to the second navigation application through the second navigation flow module includes: caching the navigation synchronization information in a cache area through the second navigation flow module, and detecting a heartbeat signal of a communication connection with the first terminal; If the heartbeat signal is not received within the preset effective time, it is recognized that the near field communication connection with the first terminal is disconnected, and the navigation synchronization information is transmitted to the second navigation application.

14. The synchronization method according to any one of claims 9 to 13, characterized in that: After receiving the navigation synchronization information sent by the first terminal, the method further includes: Detecting whether there is a navigation application matching the first navigation application in a navigation application list; the navigation application list includes the first navigation application; If it is detected that there is a navigation application matching the first navigation application in the navigation application list, the navigation application matching the first navigation application will be used as the second navigation application, and the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module will be performed; the navigation application matching the first navigation application is specifically: an application that has the permission to transmit navigation data across devices with the second navigation application.

15. The synchronization method according to any one of claims 9 to 14, characterized in that: The updating of the navigation task of the second navigation application based on the navigation synchronization information includes: determining a navigation destination based on the navigation synchronization information, and generating task update prompt information based on the navigation destination; If an update confirmation instruction based on the update prompt information feedback is received, the navigation task is updated based on the navigation destination.

16. The synchronization method according to claims 9-15, characterized in that: After the navigation task of the second navigation application is updated based on the navigation synchronization information, the method further includes: Navigation synchronization completion information is sent to the first terminal, so that the first terminal responds to the navigation synchronization completion information and transmits an end instruction of the navigation task to the first navigation application through the first navigation flow module to stop the navigation task of the first navigation application.

17. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 8 is implemented.

18. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 9 to 16 is implemented.

Images