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

Abstract

The present application is applied to the field of data transmission technology, and provides a cross-device navigation task synchronization method and apparatus, device, and storage medium. The method includes: when a pre-set cross-device transmission condition is satisfied, a first terminal obtains navigation data from a first navigation application through a first navigation transfer module, and generates navigation synchronization information of the navigation data through the first navigation transfer module; and a second terminal receives the navigation synchronization information sent by the first terminal, sends the navigation synchronization information to a second navigation application through a second navigation transfer module, and updates the navigation task of the second navigation application according to the navigation synchronization information. According to the technical solution provided in the present application, cross-device navigation task synchronization can be implemented. In a scenario where cross-device navigation needs to be performed, a user does not need to set the task of the navigation application of the terminal multiple times, so that the navigation task setting efficiency is greatly improved and the user's repeated operations are reduced.

Description

[Technical Field]

[0001] The present application relates to the field of device control technology, and in particular to a cross-device navigation task synchronization method and apparatus, a device, and a storage medium. [Background technology]

[0002] With the continuous development of navigation technology, the application scenarios of navigation technology are constantly increasing. Navigation has gradually evolved from the initial navigation for driving vehicles to navigation for pedestrian users, and has been further subdivided into application scenario areas such as cycling navigation. Navigation applications have become one of the important applications that are indispensable in people's lives and work processes. Therefore, how to complete navigation tasks quickly and conveniently has become a technical problem that needs to be solved urgently.

[0003] In existing navigation applications, a user may set a navigation destination in the navigation application of a terminal. The navigation application may generate a navigation task based on the user's location and the specified navigation destination, and prompt the user for travel directions during the user's travel process to achieve the navigation goal. However, a user's actual navigation process may include multiple different navigation scenarios, and different terminals are typically used for navigation in different navigation scenarios. For example, in a vehicle driving scenario, navigation may be performed for the user by using a navigation application of an in-vehicle terminal, while in a walking scenario, the navigation task may be completed for the user by using a smartphone that may be carried by the user. Therefore, when multiple different navigation scenarios are included in the navigation process, the user needs to set the navigation task multiple times on different terminals, which increases the user's setting operations and reduces the efficiency of navigation task setting. Summary of the Invention

[0004] The embodiments of the present application provide a navigation task synchronization method and apparatus, a device, and a storage medium, which can solve the following problems in navigation technology: In cross-device navigation scenarios, users need to set navigation tasks multiple times, which results in low navigation task setting efficiency and increases user repetitive setting.

[0005] According to a first aspect, an embodiment of the present application provides a method for synchronizing cross-device navigation tasks, comprising: The first terminal acquires navigation data from the first navigation application when a preset cross-device transmission condition is satisfied; The first terminal generates navigation synchronization information for the navigation data; A second terminal receives the navigation synchronization information sent by the first terminal and sends the navigation synchronization information to a second navigation application; The second terminal updates the navigation task of the second navigation application based on the navigation synchronization information; The present invention provides a synchronization method having the following steps.

[0006] In a possible implementation of the first aspect, the first terminal includes a first navigation transfer module and the second terminal includes a second navigation transfer module.

[0007] Specifically, the first terminal acquires navigation data from the first navigation application when the preset cross-device transmission condition is satisfied. The first terminal obtains navigation data from the first navigation application through the first navigation transfer module when a preset cross-device transmission condition is satisfied.

[0008] Specifically, the first terminal generates navigation synchronization information for navigation data. The first terminal generates navigation synchronization information of the navigation data through the first navigation transfer module.

[0009] The second terminal receiving the navigation synchronization information sent by the first terminal and sending the navigation synchronization information to the second navigation application specifically includes: The second terminal receives the navigation synchronization information sent by the first terminal through the second navigation transfer module, and sends the navigation synchronization information to the second navigation application.

[0010] The advantageous effects of implementing this embodiment of the present application are as follows: when the first terminal detects that the cross-device transmission condition is satisfied, the first terminal automatically obtains navigation data of the initiated navigation task from the first navigation application through the first terminal's local first navigation transfer module, generates navigation synchronization information corresponding to the navigation data through the first navigation transfer module, and sends the navigation synchronization information to the second terminal, thereby implementing cross-device navigation data transmission. After receiving the navigation synchronization information, the second terminal generates and sends the navigation synchronization information to the second navigation application through the local second navigation transfer module. The second terminal can then update the navigation task of the second navigation application based on the navigation synchronization information, thereby implementing cross-device navigation task synchronization. Compared with existing navigation technologies, cross-device navigation task synchronization can be implemented in the present application. In a scenario where cross-device navigation needs to be performed, the user does not need to set the task of the terminal's navigation application multiple times. Instead, the navigation data can be automatically transferred through the navigation transfer module to update the navigation task of the navigation application, thereby greatly improving navigation task setting efficiency and reducing user repetitive operations. Furthermore, after obtaining navigation data from the first navigation application, the local first navigation transfer module of the first terminal does not directly send the navigation data to the second navigation transfer module of the second terminal, but converts the navigation data into corresponding navigation synchronization information. The navigation synchronization information can be transmitted between the navigation transfer modules of different terminals. The navigation synchronization information is then transmitted to the second navigation application through the second navigation transfer module. The navigation synchronization information is not directly transmitted between the navigation applications of the two terminals.Therefore, the same navigation application does not need to be installed on the first terminal and the second terminal. In this way, cross-device and cross-application navigation data transfer can be implemented, thereby further improving the coverage of navigation task synchronization.

[0011] In a possible implementation of the first aspect, the first terminal acquires navigation data from the first navigation application through the first navigation transfer module when a preset cross-device transmission condition is satisfied, The second terminal transmits a communication label to the first terminal through the second short-range communication module in response to a touch operation by the first terminal, the communication label carrying a navigation task synchronization start identifier; In response to the communication label, the first terminal activates a first navigation transfer module and obtains navigation data from the first navigation application through the first navigation transfer module; Includes.

[0012] In a possible implementation of the first aspect, before the second terminal transmits the communication label to the first terminal through the second short-range communication module in response to the touch operation by the first terminal, the method includes: The second terminal sends a label writing request to the label service thread through the second navigation forwarding module when the preset label writing condition is satisfied; The second terminal responds to the label write request through the label service thread, adds the initiation identifier to the communication label, and writes the communication label to the second short-range communication module. Further includes:

[0013] In a possible implementation of the first aspect, the second terminal is an intelligent vehicle control terminal mounted in a vehicle, and the first terminal is a user terminal carried by a user.

[0014] Accordingly, before the first terminal obtains navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied, the method includes: establishing a communication connection by the second terminal to the first terminal when the second terminal detects a door opening event related to the vehicle; The second terminal obtains a navigation synchronization application list, and when the navigation synchronization application list is not empty, obtains a configuration status of the second navigation transfer module; When the second terminal has a second navigation transfer module in an on state, the second terminal sends a navigation transfer notification to the first terminal, causing the first terminal to send navigation synchronization information; Further includes:

[0015] In a possible implementation of the first aspect, the first terminal acquires navigation data from the first navigation application through the first navigation transfer module when a preset cross-device transmission condition is satisfied, The first terminal receives a navigation transfer notification sent by the second terminal; the first terminal acquires navigation data from the first navigation application through the first navigation transfer module in response to the navigation transfer notification; Includes.

[0016] In a possible implementation of the first aspect, when the second terminal detects a door opening event related to the vehicle, establishing a communication connection by the second terminal to the first terminal includes: The second terminal recognizes, through a second navigation forwarding module, the connection status of each registered terminal in the preset registered device list; If the second terminal recognizes that the first terminal is in the registered device list and the connection status of the first terminal is connectable, the second terminal establishes a communication connection to the first terminal based on connection information associated with the first terminal in the registered device list; When the second terminal recognizes that the first terminal is not in the registered device list, or that the first terminal is in the registered device list but the connection status of the first terminal is in an unconnectable state, the second terminal sends a wake-up command to the first terminal through the second short-range communication module; The first terminal receives a wake-up command transmitted by the second terminal through the second short-range communication module. 、 the first terminal transmitting a wireless connection request to the second terminal in response to the wake-up command to establish a communication connection to the second terminal; Includes.

[0017] In a possible implementation of the first aspect, the second terminal is a user terminal carried by a user and the first terminal is an intelligent vehicle control terminal mounted in a vehicle.

[0018] Correspondingly, the first terminal obtains navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied: When the first terminal detects a parking event related to the vehicle, the first terminal establishes a short-range communication connection to the second terminal, the short-range communication connection being used to send navigation synchronization information to the second terminal; The first terminal obtains a navigation synchronization application list, and when the navigation synchronization application list is not empty, obtains a configuration status of the first navigation transfer module; When the first terminal recognizes that the first navigation transfer module is in an on state, the first terminal obtains navigation data from the first navigation application through the first navigation transfer module; Includes.

[0019] In a possible implementation of the first aspect, when the first terminal detects a parking event related to the vehicle, establishing a near field communication connection by the first terminal to the second terminal includes: The first terminal recognizes, through a first navigation forwarding module, the connection status of each registered terminal in a preset registered device list; If the first terminal recognizes that the second terminal is in the registered device list and the connection status of the second terminal is connectable, the first terminal establishes a near field communication connection to the second terminal based on connection information associated with the second terminal in the registered device list; When the first terminal recognizes that the second terminal is not in the registered device list, or that the second terminal is in the registered device list but the connection status of the second terminal is in an unconnectable state, the first terminal sends a wake-up command to the second terminal through the first short-range communication module; the second terminal transmitting a short-range connection request to the first terminal in response to the wake-up command to establish a short-range communication connection to the first terminal; Includes.

[0020] In a possible implementation of the first aspect, the second terminal receiving the navigation synchronization information transmitted by the first terminal and transmitting the navigation synchronization information to the second navigation application through a second navigation transfer module includes: The second terminal caches the navigation data in a cache area through a second navigation transfer module, and detects a heartbeat signal of a communication connection to the first terminal; If the second terminal does not receive the heartbeat signal within a preset valid time, the second terminal recognizes that the short-range communication connection to the first terminal has been lost and sends navigation synchronization information to the second navigation application. Includes.

[0021] In a possible implementation of the first aspect, before the first terminal acquires navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied, the method includes: The first terminal generates a navigation task through a first navigation application in response to a user's navigation operation, and the navigation data is generated based on the navigation task; The first terminal receives, through a first navigation transfer module, a service registration command sent by a first navigation application, the service registration command being used to authorize the first navigation application to transmit navigation data between devices; In response to the service registration command, the first terminal adds the first navigation application to a navigation synchronization application list and sets a first navigation transfer module to an on state, the on state being used to send navigation synchronization information generated based on the first navigation application to the second terminal when a cross-device transmission condition is satisfied; Further includes:

[0022] In a possible implementation of the first aspect, after the second terminal receives the navigation synchronization information sent by the first terminal, sends the navigation synchronization information to the second navigation application through a second navigation transfer module, and updates the navigation task of the second navigation application based on the navigation synchronization information, the method includes: The second terminal sends navigation synchronization completion information to the first terminal through the second navigation transfer module; the first terminal, in response to the navigation synchronization completion information, sends an end command for the navigation task to the first navigation application through the first navigation transfer module to stop the navigation task of the first navigation application; Further includes:

[0023] In a possible implementation of the first aspect, before the second terminal receives the navigation synchronization information transmitted by the first terminal, the method comprises: The first terminal obtains a navigation application list of the second terminal, the navigation application list including the second navigation application; When the first terminal detects that a navigation application matching the first navigation application exists in the navigation application list, the first terminal sends navigation synchronization information to the second terminal, and the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application; Further includes:

[0024] In a possible implementation of the first aspect, after the second terminal receives the navigation synchronization information transmitted by the first terminal, the method includes: The second terminal detects whether a navigation application matching the first navigation application exists in the navigation application list; When the second terminal detects that a navigation application matching the first navigation application exists in the navigation application list, the second terminal uses the navigation application matching the first navigation application as the second navigation application, and performs an operation of sending navigation synchronization information to the second navigation application through a second navigation transfer module, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application; Includes.

[0025] In a possible implementation of the first aspect, the second terminal updating a navigation task of the second navigation application based on the navigation synchronization information includes: The second terminal determines a navigation destination based on the navigation synchronization information, and generates task update prompt information based on the navigation destination; When the second terminal receives an update confirmation command fed back based on the update prompt information, the second terminal updates the navigation task based on the navigation destination. Includes.

[0026] According to a second aspect, an embodiment of the present application provides a cross-device navigation task synchronization method, applied to a first terminal, comprising: Obtaining navigation data from the first navigation application through a first navigation transfer module when a preset cross-device transmission condition is satisfied; generating navigation synchronization information corresponding to the navigation data through a first navigation transfer module; Sending navigation synchronization information to the second terminal, where the navigation synchronization information is used to update a navigation task of a second navigation application of the second terminal; The present invention provides a synchronization method including:

[0027] 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 that the second terminal sends the received navigation synchronization information to the second navigation application through the second navigation transfer module, and updates the navigation task of the second navigation application based on the navigation synchronization information.

[0028] In a possible implementation of the second aspect, obtaining navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied includes: receiving a communication label transmitted by a second short-range communication module of the second terminal in response to a touch operation by the second terminal, the communication label carrying a navigation task synchronization start identifier; In response to the communicating label, activating a first navigation transfer module and obtaining navigation data from the first navigation application through the first navigation transfer module; Includes.

[0029] In a possible implementation of the second aspect, when the second terminal detects that the label writing condition is satisfied, the second terminal sends a label writing request to a label service thread through the second navigation forwarding module, responds to the label writing request through the label service thread, adds a start identifier to the communication label, and writes the communication label to the second short-range communication module, after which the communication label is obtained.

[0030] In a possible implementation of the second aspect, obtaining navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied includes: Receiving a navigation transfer notification sent by a second terminal, where after the second terminal is connected to the first terminal, the navigation transfer notification is sent to the first terminal when it is detected that a second navigation transfer module of the second terminal is in an on state; obtaining navigation data from the first navigation application through the first navigation transfer module in response to the navigation transfer notification; Includes.

[0031] In a possible implementation of the second aspect, before receiving the navigation transfer notification sent by the second terminal, the method comprises: receiving a wake-up command sent by the second terminal through a second short-range communication module; transmitting a wireless connection request to the second terminal in response to the wake-up command to establish a communication connection to the second terminal; Further includes:

[0032] In a possible implementation of the second aspect, the first terminal is an intelligent vehicle control terminal mounted in a vehicle, and the second terminal is a user terminal carried by a user.

[0033] Correspondingly, obtaining navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied includes: establishing a near field communication connection to a second terminal when a parking event related to the vehicle is detected, the near field communication connection being used to transmit navigation synchronization information to the second terminal; Obtaining a navigation synchronization application list, and when the navigation synchronization application list is not empty, obtaining a configuration status of a first navigation transfer module; When the first navigation transfer module is in an on state, obtaining navigation data from the first navigation application through the first navigation transfer module; Includes.

[0034] In a possible implementation of the second aspect, establishing a near field communication connection to the second terminal upon detecting a parking event related to the vehicle includes: Recognizing, through a second navigation forwarding module, the connection status of each registered terminal in the preset registered device list; If the second terminal is in the registered device list and the connection status of the second terminal is connectable, establishing a near field communication connection to the second terminal based on connection information associated with the second terminal in the registered device list; or When the second terminal is not in the registered device list, or when the second terminal is in the registered device list but the connection status of the second terminal is in an unconnectable state, sending a wake-up command to the second terminal through the first short-range communication module, the wake-up command being used to enable the second terminal to establish a communication connection to the first terminal; Includes.

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

[0036] In a possible implementation of the second aspect, if the preset cross-device transmission condition is satisfied, before obtaining navigation data from the first navigation application through the first navigation transfer module, the method includes: generating a navigation task through the first navigation application in response to a user navigation operation, wherein navigation data is generated based on the navigation task; receiving, via a first navigation transfer module, a service registration command sent by a first navigation application, the service registration command being used to authorize the first navigation application to transmit navigation data between devices; In response to the service registration command, adding the first navigation application to a navigation synchronization application list and setting a first navigation transfer module to an on state, the on state being used to send navigation synchronization information generated based on the first navigation application to the second terminal when a cross-device transmission condition is satisfied; Further includes:

[0037] In a possible implementation of the second aspect, after transmitting the navigation synchronization information to the second terminal, the method comprises: receiving navigation synchronization completion information fed back by the second terminal through a second navigation forwarding module; sending a termination command for the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, thereby stopping the navigation task of the first navigation application; Further includes:

[0038] In a possible implementation of the second aspect, before transmitting the navigation synchronization information to the second terminal, the method comprises: Obtaining a navigation application list of the second terminal, the navigation application list including the second navigation application; If a navigation application matching the first navigation application exists in the navigation application list, sending navigation synchronization information to the second terminal, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application; Further includes:

[0039] According to a third aspect, an embodiment of the present application comprises: a navigation data obtaining unit configured to obtain navigation data from the first navigation application through the first navigation transfer module when a preset cross-device transmission condition is satisfied; a navigation synchronization information generating unit configured to generate, through the first navigation transfer module, navigation synchronization information corresponding to the navigation data; a navigation synchronization information sending unit configured to send navigation synchronization information to a second terminal, the navigation synchronization information being used to update a navigation task of a second navigation application of the second terminal; and A cross-device navigation task synchronization device is provided.

[0040] In a possible implementation of the third aspect, the navigation data acquisition unit comprises: a communication label receiving unit configured to receive a communication label transmitted by a second short-range communication module of the second terminal in response to a touch operation by the second terminal, the communication label carrying a navigation task synchronization start identifier; and a navigation transfer module activation unit configured to activate the first navigation transfer module in response to the communicating label and obtain navigation data from the first navigation application through the first navigation transfer module; Includes.

[0041] In a possible implementation of the third aspect, when the second terminal detects that the label writing condition is satisfied, the second terminal sends a label writing request to a label service thread through the second navigation forwarding module, responds to the label writing request through the label service thread, adds a start identifier to the communication label, and writes the communication label to the second short-range communication module, after which the communication label is obtained.

[0042] In a possible implementation of the third aspect, the navigation data acquisition unit comprises: a navigation forwarding notification receiving unit configured to receive a navigation forwarding notification sent by a second terminal, where after the second terminal is connected to the first terminal, the navigation forwarding notification is sent to the first terminal when it is detected that a second navigation forwarding module of the second terminal is in an on state; and a navigation transfer notification response unit configured to retrieve navigation data from the first navigation application through the first navigation transfer module in response to the navigation transfer notification; Includes.

[0043] In a possible implementation of the third aspect, the navigation task synchronizer comprises: a wake-up command receiving unit configured to receive a wake-up command sent by the second terminal through the second short-range communication module; a wake-up command response unit configured to send a wireless connection request to the second terminal in response to the wake-up command so as to establish a communication connection to the second terminal; Further includes:

[0044] In a possible implementation of the third aspect, the first terminal is an intelligent vehicle control terminal mounted in a vehicle, and the second terminal is a user terminal carried by a user.

[0045] Correspondingly, the navigation data acquisition unit a parking door opening trigger unit configured to establish a short-range communication connection to a second terminal when a parking event related to the vehicle is detected, the short-range communication connection being used to transmit navigation synchronization information to the second terminal; and a first status recognition unit configured to obtain a navigation synchronization application list, and, if the navigation synchronization application list is not empty, obtain a configuration status of the first navigation transfer module; a first start state response unit configured to obtain navigation data from the first navigation application through the first navigation transfer module when the first navigation transfer module is in an on state; Includes.

[0046] In a possible implementation of the third aspect, the parking door opening trigger unit comprises: a connection status detection unit configured to recognize, through the second navigation forwarding module, the connection status of each registered terminal in the preset registered device list; a direct connection trigger unit configured to establish a close-range communication connection to the second terminal based on connection information associated with the second terminal in the registered device list when the second terminal is in the registered device list and a connection status of the second terminal is connectable; a wake-up command sending unit configured to send a wake-up command to the second terminal through the first short-range communication module when the second terminal is not in the registered device list or when the second terminal is in the registered device list but the connection status of the second terminal is in an unconnectable state, the wake-up command being used to enable the second terminal to establish a communication connection to the first terminal; Includes.

[0047] In a possible implementation of the third aspect, the navigation task synchronizer comprises: a navigation operation response unit configured to generate a navigation task through a first navigation application in response to a user's navigation operation, the navigation data being generated based on the navigation task; and a service registration unit configured to receive a service registration command sent by the first navigation application through the first navigation transfer module, the service registration command being used to authorize the first navigation application to have permission to transmit navigation data between devices; a service registration response unit configured to add the first navigation application to a navigation synchronization application list and set a first navigation transfer module to an ON state in response to the service registration command, the ON state being used to transmit navigation synchronization information generated based on the first navigation application to the second terminal when a cross-device transmission condition is satisfied; and Further includes:

[0048] In a possible implementation of the third aspect, the navigation task synchronizer comprises: a navigation synchronization completion information receiving unit configured to receive navigation synchronization completion information fed back by the second terminal through the second navigation forwarding module; a navigation termination unit configured to send a termination command for the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, thereby stopping the navigation task of the first navigation application; Further includes:

[0049] In a possible implementation of the third aspect, the navigation task synchronizer comprises: a navigation application list obtaining unit configured to obtain a navigation application list of the second terminal, the navigation application list including the second navigation application; and a navigation application matching unit configured to send navigation synchronization information to the second terminal when a navigation application matching the first navigation application exists in the navigation application list, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application; and Further includes:

[0050] According to a fourth aspect, an embodiment of the present application provides a cross-device navigation task synchronization method, the method being applied to a second terminal, comprising: receiving navigation synchronization information transmitted by the first terminal, wherein the navigation synchronization information is generated based on navigation data of a first navigation application of the first terminal; Sending the navigation synchronization information to a second navigation application through a second navigation forwarding module; updating a navigation task of the second navigation application based on the navigation synchronization information; Includes.

[0051] In a possible implementation of the fourth aspect, receiving navigation synchronization information transmitted by the first terminal includes: In response to a touch operation by the first terminal, send a communication label to the first terminal through the second short-range communication module, so that the first terminal activates a first navigation transfer module in response to the communication label and obtains navigation data from the first navigation application through the first navigation transfer module, wherein the communication label carries a navigation task synchronization start identifier; receiving navigation synchronization information sent by the first terminal through a first navigation transfer module; Includes.

[0052] In a possible implementation of the fourth aspect, before transmitting the communication label to the first terminal through the second short-range communication module in response to a touch operation by the first terminal, the method further comprises: sending a label write request to a label service thread through a second navigation forwarding module when a preset label write condition is satisfied; Responding to the label write request through the label service thread, adding the initiation identifier to the communication label, and writing the communication label to the second short-range communication module; Further includes:

[0053] In a possible implementation of the fourth aspect, the second terminal is an intelligent vehicle control terminal mounted in the vehicle.

[0054] Accordingly, before receiving the navigation synchronization information sent by the first terminal, the method comprises: establishing a communication connection to the first terminal when a door opening event related to the vehicle is detected; Obtaining a navigation synchronization application list, and when the navigation synchronization application list is not empty, obtaining a configuration status of a second navigation transfer module; When the second navigation transfer module is in an on state, sending a navigation transfer notification to the first terminal to cause the first terminal to send navigation synchronization information; Further includes:

[0055] In a possible implementation of the fourth aspect, when a door opening event related to the vehicle is detected, establishing a communication connection to the first terminal includes: Recognizing, through a second navigation forwarding module, the connection status of each registered terminal in the preset registered device list; If the first terminal is in the registered device list and the connection status of the first terminal is connectable, establishing a communication connection to the first terminal based on connection information associated with the first terminal in the registered device list; or When the first terminal is not in the registered device list, or when the first terminal is in the registered device list but the connection status of the first terminal is in an unconnectable state, sending a wake-up command to the first terminal through the second short-range communication module, the wake-up command being used to enable the first terminal to establish a short-range communication connection to the second terminal; Includes.

[0056] In this implementation, after receiving a wake-up command sent by the second terminal, the first terminal establishes a close range communication connection to the second terminal in response to the wake-up command.

[0057] In a possible implementation of the fourth aspect, the second terminal is a user terminal carried by a user and the first terminal is an intelligent vehicle control terminal mounted in a vehicle.

[0058] Accordingly, transmitting the navigation synchronization information to the second navigation application through the second navigation forwarding module includes: Caching navigation data in a cache area through a second navigation transfer module, and detecting a heartbeat signal of a communication connection to the first terminal; If the heartbeat signal is not received within a preset valid time, the short-range communication connection to the first terminal is recognized as being lost, and navigation synchronization information is sent to the second navigation application. Includes.

[0059] In a possible implementation of the fourth aspect, after receiving the navigation synchronization information transmitted by the first terminal, the method comprises: detecting whether a navigation application matching the first navigation application exists in a navigation application list, the navigation application list including the first navigation application; If a navigation application matching the first navigation application exists in the navigation application list, use the navigation application matching the first navigation application as a second navigation application, and perform an operation of sending navigation synchronization information to the second navigation application through a second navigation transfer module, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application; Further includes:

[0060] In a possible implementation of the fourth aspect, updating 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; updating the navigation task based on the navigation destination when an update confirmation command is received that is fed back based on the update prompt information; Includes.

[0061] In a possible implementation of the fourth aspect, after updating the navigation task of the second navigation application based on the navigation synchronization information, the method comprises: The method further includes sending navigation synchronization completion information to the first terminal, and causing the first terminal to send an end command regarding the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, so as to stop the navigation task of the first navigation application.

[0062] According to a fifth aspect, an embodiment of the present application comprises: a navigation synchronization information receiving unit configured to receive navigation synchronization information transmitted by a first terminal, the navigation synchronization information being generated based on navigation data of a first navigation application of the first terminal; and a navigation synchronization information sending unit configured to send navigation synchronization information to a second navigation application through a second navigation transfer module; a navigation task updating unit configured to update a navigation task of the second navigation application based on the navigation synchronization information; A navigation task synchronization device is provided, which includes:

[0063] In a possible implementation of the fifth aspect, the navigation synchronization information receiving unit comprises: a communication label sending unit configured to, in response to a touch operation by the first terminal, send a communication label to the first terminal through the second short-range communication module, so that the first terminal, in response to the communication label, activates a first navigation transfer module and obtains navigation data from the first navigation application through the first navigation transfer module, wherein the communication label carries a navigation task synchronization start identifier; and a touch operation feedback unit configured to receive navigation synchronization information sent by the first terminal through the first navigation transfer module; Includes.

[0064] In a possible implementation of the fifth aspect, the navigation task synchronizer comprises: a label write request unit configured to send a label write request to a label service thread through a second navigation forwarding module when a preset label write condition is satisfied; a communication label writing unit configured to respond to a label writing request through a label service thread, add an initiation identifier to a communication label, and write the communication label to a second short-range communication module; Further includes:

[0065] In a possible implementation of the fifth aspect, the second terminal is an intelligent vehicle control terminal mounted in the vehicle.

[0066] Accordingly, the navigation task synchronizer a door-opening event trigger unit configured to establish a communication connection to the first terminal when a door-opening event related to the vehicle is detected; a second status recognition unit configured to obtain a navigation synchronization application list, and, when the navigation synchronization application list is not empty, obtain a setting status of the second navigation forwarding module; a second wake-up status response unit configured to, when the second navigation forwarding module is in an on state, send a navigation forwarding notification to the first terminal to cause the first terminal to send navigation synchronization information; Further includes:

[0067] In a possible implementation of the fifth aspect, the door open event trigger unit comprises: a connection status determining unit configured to recognize, through the second navigation forwarding module, a connection status of each registered terminal in the preset registered device list; a direct connection sending unit configured to establish a communication connection to the first terminal based on connection information associated with the first terminal in the registered device list, when the first terminal is in the registered device list and a connection status of the first terminal is connectable; a wake-up execution unit configured to send a wake-up command to the first terminal through the second short-range communication module when the first terminal is not in the registered device list or when the first terminal is in the registered device list but the connection status of the first terminal is in an unconnectable state, the wake-up command being used to enable the first terminal to establish a short-range communication connection to the second terminal; and Includes.

[0068] In a possible implementation of the fifth aspect, the second terminal is a user terminal carried by a user and the first terminal is an intelligent vehicle control terminal mounted in a vehicle.

[0069] Correspondingly, the navigation synchronization information sending unit: an information caching unit configured to cache navigation data in a cache area through a second navigation transfer module and detect a heartbeat signal of a communication connection to the first terminal; a heartbeat signal listening unit configured to recognize that a short-range communication connection to the first terminal has been lost if the heartbeat signal is not received within a preset valid time period, and to send navigation synchronization information to the second navigation application; Includes.

[0070] In a possible implementation of the fifth aspect, the navigation task synchronizer comprises: a matching application detection unit configured to detect whether a navigation application matching the first navigation application exists in a navigation application list, the navigation application list including the first navigation application; and a second navigation application recognition unit configured to perform an operation of using the navigation application matching the first navigation application as a second navigation application and sending navigation synchronization information to the second navigation application through a second navigation transfer module when a navigation application matching the first navigation application exists in the navigation application list, wherein the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application; Further includes:

[0071] In a possible implementation of the fifth aspect, the navigation task update unit 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; an update confirmation command response unit configured to update the navigation task based on the navigation destination when an update confirmation command fed back based on the update prompt information is received; Includes.

[0072] In a possible implementation of the fifth aspect, the navigation task synchronizer comprises: The communication device further includes a navigation synchronization completion information sending unit configured to send navigation synchronization completion information to the first terminal, so that the first terminal sends an end command regarding the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, thereby stopping the navigation task of the first navigation application.

[0073] According to a sixth aspect, an embodiment of the present application provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed, the processor performs a cross-device navigation task synchronization method according to any one of the implementations of the second aspect.

[0074] According to a seventh aspect, an embodiment of the present application provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed, the processor performs a cross-device navigation task synchronization method according to any one of the implementations of the fourth aspect.

[0075] According to an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, which, when executed by a processor, performs the cross-device navigation task synchronization method according to either the second aspect or the fourth aspect.

[0076] According to 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 perform the cross-device navigation task synchronization method according to either the second aspect or the fourth aspect.

[0077] According to a tenth aspect, an embodiment of the present application provides a chip system including a processor coupled to a memory, the processor executing a computer program stored in the memory to implement the cross-device navigation task synchronization method according to either the second or fourth aspect.

[0078] According to an eleventh aspect, an embodiment of the present application provides a cross-device navigation system including a first terminal and a second terminal.

[0079] The first terminal is configured to obtain navigation data from the first navigation application through the first navigation transfer module when a preset cross-device transmission condition is satisfied.

[0080] The first terminal is configured to generate navigation synchronization information of the navigation data through a first navigation transfer module.

[0081] The second terminal is configured to receive the navigation synchronization information sent by the first terminal, and send the navigation synchronization information to the second navigation application through a second navigation transfer module.

[0082] The second terminal updates the navigation task of the second navigation application based on the navigation synchronization information.

[0083] 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 transfer module when a preset cross-device transmission condition is satisfied, the second terminal is configured to transmit a communication label to the first terminal through the second short-range communication module in response to a touch operation by the first terminal, the communication label carrying a navigation task synchronization start identifier; the first terminal is configured to activate a first navigation transfer module in response to the communication label and obtain navigation data from the first navigation application through the first navigation transfer module; Includes.

[0084] In a possible implementation of the eleventh aspect, the second terminal the second terminal is configured to send a label writing request to the label service thread through the second navigation forwarding module when the preset label writing condition is satisfied; the second terminal is configured to respond to the label write request through the label service thread, add the initiation identifier to the communication label, and write the communication label to the second short-range communication module; It is further configured as follows.

[0085] In a possible implementation of the eleventh aspect, the second terminal is an intelligent vehicle control terminal mounted in a vehicle, and the first terminal is a user terminal carried by a user.

[0086] Correspondingly, the second terminal: the second terminal is configured to establish a communication connection to the first terminal when a door opening event related to the vehicle is detected; The second terminal is configured to obtain a navigation synchronization application list, and, when the navigation synchronization application list is not empty, obtain a setting status of the second navigation transfer module; The second terminal is configured to, when the second navigation forwarding module is in an on state, send a navigation forwarding notification to the first terminal to cause the first terminal to send navigation synchronization information; It is further configured as follows.

[0087] 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 transfer module when a preset cross-device transmission condition is satisfied, The first terminal is configured to receive a navigation transfer notification sent by the second terminal; the first terminal is configured to obtain navigation data from the first navigation application through a first navigation transfer module in response to the navigation transfer notification; Includes.

[0088] In a possible implementation of the eleventh aspect, the second terminal is configured to establish a communication connection to the first terminal when a door opening event related to the vehicle is detected, The second terminal is configured to recognize, through a second navigation forwarding module, a connection status of each registered terminal in the preset registered device list; the second terminal is configured to, when it recognizes that the first terminal is in the registered device list and that the connection status of the first terminal is in a connectable state, establish a communication connection to the first terminal based on connection information associated with the first terminal in the registered device list; the second terminal is configured to send a wake-up command to the first terminal through the second short-range communication module when it recognizes that the first terminal is not in the registered device list, or that the first terminal is in the registered device list but the connection status of the first terminal is in an unconnectable state; the first terminal is configured to receive a wake-up command sent by the second terminal through the second short-range communication module; the first terminal is configured to send a wireless connection request to the second terminal in response to the wake-up command to establish a communication connection to the second terminal; Includes.

[0089] In a possible implementation of the eleventh aspect, the second terminal is a user terminal carried by a user, and the first terminal is an intelligent vehicle control terminal mounted in a vehicle.

[0090] Correspondingly, the first terminal is configured to obtain navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied, the first terminal is configured to establish a close-range communication connection to the second terminal when the first terminal detects a parking event related to the vehicle, the close-range communication connection being used to send navigation synchronization information to the second terminal; The first terminal is configured to obtain a navigation synchronization application list, and, when the navigation synchronization application list is not empty, obtain a setting status of the first navigation transfer module; The first terminal is configured to obtain navigation data from the first navigation application through the first navigation transfer module when it is recognized that the first navigation transfer module is in an on state; Includes.

[0091] In a possible implementation of the eleventh aspect, the first terminal is configured to establish a near-field communication connection to the second terminal when a parking event related to the vehicle is detected, The first terminal is configured to recognize, through a first navigation forwarding module, a connection status of each registered terminal in a preset registered device list; the first terminal is configured to, when the first terminal recognizes that the second terminal is in the registered device list and that the connection status of the second terminal is in a connectable state, establish a near field communication connection to the second terminal based on connection information associated with the second terminal in the registered device list; When the first terminal recognizes that the second terminal is not in the registered device list, or that the second terminal is in the registered device list but the connection status of the second terminal is in an unconnectable state, the first terminal is configured to send a wake-up command to the second terminal through the first short-range communication module; the second terminal is configured to send a short-range connection request to the first terminal in response to the wake-up command to establish a short-range communication connection to the first terminal; Includes.

[0092] In a possible implementation of the eleventh aspect, the second terminal is configured to receive navigation synchronization information transmitted by the first terminal and transmit the navigation synchronization information to the second navigation application through a second navigation transfer module: The second terminal is configured to cache the navigation data in a cache area through a second navigation transfer module, and detect a heartbeat signal of a communication connection to the first terminal; The second terminal is configured to recognize that the short-range communication connection to the first terminal has been lost when the heartbeat signal is not received within a preset valid time, and to send navigation synchronization information to the second navigation application. Includes.

[0093] In a possible implementation of the eleventh aspect, the first terminal the first terminal is configured to generate a navigation task through a first navigation application in response to a user's navigation operation, and the navigation data is generated based on the navigation task; The first terminal is configured to receive, through a first navigation transfer module, a service registration command sent by the first navigation application, the service registration command being used to authorize the first navigation application to transmit navigation data between devices; the first terminal is configured to, in response to the service registration command, add the first navigation application to a navigation synchronization application list and set a first navigation transfer module to an on state, the on state being used to send navigation synchronization information generated based on the first navigation application to the second terminal when a cross-device transmission condition is satisfied; It is further configured as follows.

[0094] In a possible implementation of the eleventh aspect, the first terminal and the second terminal The second terminal is configured to send navigation synchronization completion information to the first terminal through a second navigation transfer module; the first terminal is configured to send a termination command for the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, to stop the navigation task of the first navigation application; It is further configured as follows.

[0095] In a possible implementation of the eleventh aspect, before the second terminal receives the navigation synchronization information transmitted by the first terminal, the second terminal: The first terminal is configured to obtain a navigation application list of the second terminal, the navigation application list including the second navigation application; and The first terminal is configured to send navigation synchronization information to the second terminal when it is detected that a navigation application matching the first navigation application exists in the navigation application list, and the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application; Further included are:

[0096] In a possible implementation of the eleventh aspect, the second terminal the second terminal is configured to detect whether a navigation application matching the first navigation application exists in the navigation application list; When the second terminal detects that a navigation application matching the first navigation application exists in the navigation application list, the second terminal is configured to use the navigation application matching the first navigation application as the second navigation application, and perform an operation of sending navigation synchronization information to the second navigation application through a second navigation transfer module, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application; It is further configured as follows.

[0097] In a possible implementation of the eleventh aspect, the second terminal updating a navigation task of the second navigation application based on the navigation synchronization information includes: The second terminal is configured to determine a navigation destination based on the navigation synchronization information, and generate task update prompt information based on the navigation destination; The second terminal is configured to update the navigation task based on the navigation destination when an update confirmation command is received that is fed back based on the update prompt information; Includes.

[0098] It can be understood that for the advantageous effects of the second to eleventh aspects, reference can be made to the relevant descriptions of the first aspect, and the details will not be described again here. [Brief explanation of the drawings]

[0099] [Figure 1] FIG. 1 is a schematic diagram of a navigation route according to an embodiment of the present application. [Figure 2A] 1 is a flowchart of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 2B] 1 is a flowchart of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 2C] 1 is a flowchart of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 3(a)-1] FIG. 1 is a schematic diagram of a cross-device navigation data transmission scenario according to an embodiment of the present application; [Figure 3(a)-2] FIG. 1 is a schematic diagram of a cross-device navigation data transmission scenario according to an embodiment of the present application; [Figure 3(b)-1] FIG. 10 is a schematic diagram of a cross-device navigation data transmission scenario according to another embodiment of the present application; [Figure 3(b)-2] FIG. 10 is a schematic diagram of a cross-device navigation data transmission scenario according to another embodiment of the present application; [Figure 4a(1)] FIG. 2 is a schematic diagram of a navigation task initiation according to an embodiment of the present application; [Figure 4a(2)] FIG. 2 is a schematic diagram of a navigation task initiation according to an embodiment of the present application; [Figure 4a(3)]FIG. 2 is a schematic diagram of a navigation task initiation according to an embodiment of the present application; [Figure 4b(1)] FIG. 2 is a schematic diagram of a navigation task initiation according to an embodiment of the present application; [Figure 4b(2)] FIG. 2 is a schematic diagram of a navigation task initiation according to an embodiment of the present application; [Figure 4b(3)] FIG. 2 is a schematic diagram of a navigation task initiation according to an embodiment of the present application; [Figure 4c] FIG. 2 is a schematic diagram of a navigation task initiation according to an embodiment of the present application; [Figure 5(a)] FIG. 10 is a schematic diagram of setting a status switch of a first navigation transfer module according to an embodiment of the present application; [Figure 5(b)] FIG. 10 is a schematic diagram of setting a status switch of a first navigation transfer module according to an embodiment of the present application; [Figure 5(c)] FIG. 10 is a schematic diagram of setting a status switch of a first navigation transfer module according to an embodiment of the present application; [Figure 5(d)] FIG. 10 is a schematic diagram of setting a status switch of a first navigation transfer module according to an embodiment of the present application; [Figure 6(a)] FIG. 10 is a schematic diagram of an application installation prompt of a second terminal according to an embodiment of the present application; [Figure 6(b)] FIG. 10 is a schematic diagram of an application installation prompt of a second terminal according to an embodiment of the present application; [Figure 7(a)] FIG. 2 is a schematic diagram of a change of a navigation task according to an embodiment of the present application. [Figure 7(b)] FIG. 2 is a schematic diagram of a change of a navigation task according to an embodiment of the present application. [Figure 8(a)] FIG. 2 is a schematic diagram of updating a navigation task according to an embodiment of the present application; [Figure 8(b)] FIG. 2 is a schematic diagram of updating a navigation task according to an embodiment of the present application; [Figure 8(c)] FIG. 2 is a schematic diagram of updating a navigation task according to an embodiment of the present application; [Figure 9(a)]FIG. 2 is a schematic diagram of the end of a navigation task according to an embodiment of the present application; [Figure 9(b)] FIG. 2 is a schematic diagram of the end of a navigation task according to an embodiment of the present application; [Figure 9(c)] FIG. 2 is a schematic diagram of the end of a navigation task according to an embodiment of the present application; [Figure 9(d)] FIG. 2 is a schematic diagram of the end of a navigation task according to an embodiment of the present application; [Figure 10(a)] FIG. 10 is a schematic diagram of a synchronization failure response according to an embodiment of the present application; [Figure 10(b)] FIG. 10 is a schematic diagram of a synchronization failure response according to an embodiment of the present application; [Figure 11A] FIG. 2 is a schematic diagram of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 11B] FIG. 2 is a schematic diagram of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 12] 1 is a schematic diagram of a touch scenario between an in-vehicle terminal and a smartphone according to an embodiment of the present application; [Figure 13A] FIG. 2 is a schematic diagram of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 13B] FIG. 2 is a schematic diagram of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 13C] FIG. 2 is a schematic diagram of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 13D] FIG. 2 is a schematic diagram of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 13E] FIG. 2 is a schematic diagram of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application; [Figure 14(a)] 2 is a schematic diagram of an interface of the in-vehicle terminal according to the embodiment of the present application; FIG. [Figure 14(b)]2 is a schematic diagram of an interface of the in-vehicle terminal according to the embodiment of the present application; FIG. [Figure 15] 1 is a flowchart of third-party interaction between a user terminal, an in-vehicle terminal, and a server according to an embodiment of the present application; [Figure 16A] FIG. 2 is a schematic diagram of interactions in a navigation task synchronization method according to an embodiment of the present application; [Figure 16B] FIG. 2 is a schematic diagram of interactions in a navigation task synchronization method according to an embodiment of the present application; [Figure 16C] 1 is a schematic diagram of interactions in a navigation task synchronization method according to an embodiment of the present application; [Figure 16D] FIG. 2 is a schematic diagram of interactions in a navigation task synchronization method according to an embodiment of the present application; [Figure 17] 2 is a flowchart of an implementation of a cross-device navigation data synchronization method performed by a first terminal according to an embodiment of the present application; [Figure 18] 2 is a flowchart of an implementation of a cross-device navigation data synchronization method performed by a second terminal according to an embodiment of the present application; [Figure 19] 1 is a block diagram of the structure of a cross-device navigation task synchronizer according to an embodiment of the present application; [Figure 20] 1 is a block diagram of the structure of a cross-device navigation task synchronizer according to an embodiment of the present application; [Figure 21] FIG. 1 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application; [Figure 22] FIG. 2 is a block diagram of the software structure of a terminal device according to an embodiment of the present application; [Figure 23] FIG. 2 is a block diagram of the structure of a terminal device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0100] In the following description, for purposes of explanation and not limitation, specific details, such as specific system structures and techniques, are given to provide a thorough understanding of the embodiments of the present application. However, those skilled in the art will recognize that the present application may be practiced in other embodiments without such specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so that the present application is not obscured by unnecessary detail.

[0101] It should be understood that the term "comprising" as used in this specification and the appended claims indicates the presence of stated 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 sets thereof.

[0102] It should also be understood that the term "and / or" as used in this specification and the appended claims indicates and includes any and all possible combinations of one or more of the associated listed items.

[0103] As used in this specification and the appended claims, the term "if" may be interpreted as "when," "and," "response to determining," or "response to detecting," depending on the context. Similarly, "if it is determined" or "if (a described condition or event) is detected" may be interpreted as "upon determining," "in response to determining," "upon (a described condition or event) is detected," or "in response to detecting (a described condition or event)," depending on the context.

[0104] Furthermore, in the description of this specification and the appended claims, the terms "first," "second," "third," etc. are merely for the purpose of distinguishing the description and should not be understood as an indication or suggestion of relative importance.

[0105] References to "an embodiment," "some embodiments," etc. described in the specification of this application mean that one or more embodiments of the application include the particular feature, structure, or characteristic described with reference to the embodiment. Thus, the appearance of statements such as "in an embodiment," "in some embodiments," "in some other embodiments," and "in other embodiments" in various places throughout this specification does not necessarily mean that all references to the same embodiments are included. Instead, such statements mean "one or more, but not all, embodiments," unless specifically emphasized otherwise. The terms "including," "having," and "having" and variations thereof all mean "including but not limited to," unless specifically emphasized otherwise.

[0106] With the continuous development of navigation technology, the application scenarios of navigation applications are increasing, covering all aspects of people's lives and work. However, as the application scenarios of navigation technology continue to increase, the complexity of the scenarios also increases accordingly. The same navigation route may include various navigation scenarios, such as walking, cycling, driving, and bus. In different scenarios, navigation usually needs to be performed by using navigation applications on different devices. For example, in a walking scenario, a user may use a navigation application on a smartphone for navigation. However, in a driving navigation scenario, a user may use a navigation application on an in-vehicle device to complete navigation.

[0107] For example, a navigation task is used as an example for description. During a trip, a user needs to go to a tourist attraction and can input the corresponding destination into a navigation application of any terminal. The navigation application can generate a corresponding navigation task based on the navigation destination and an initial location and prompt the user to go to the navigation destination in real time. FIG. 1 is a schematic diagram of a navigation route according to an embodiment of the present application. Referring to FIG. 1, the starting point of the navigation route is a house, the destination is a tourist attraction, and the navigation route includes sidewalks, roads, and highways. In the sidewalk sections of the navigation route, i.e., sections A and C, the user needs to travel by foot. In the road and highway sections, i.e., section B, the user needs to travel by driving. Therefore, in the entire navigation process, the user needs to first input the destination, i.e., the tourist attraction, into the navigation application of the portable smartphone and complete walking in section A. Then, when the user completes walking in section A and arrives in section B, the user can switch from walking to driving to complete driving in section B. Therefore, navigation of section B can be performed for the user by using the navigation application of the in-vehicle terminal of the vehicle. In this case, the user needs to input the destination into the navigation application of the in-vehicle device again. Finally, when the user completes driving in section B and arrives at section C, the user needs to switch from driving to walking. In this case, the user needs to input the destination into the smartphone again.

[0108] When a navigation task includes multiple navigation scenarios, and navigation is completed by using different terminals in different navigation scenarios, the user needs to input the navigation destination on different terminals multiple times during the entire navigation task process, which results in the user having to repeat the navigation task setting operation multiple times, thereby reducing navigation efficiency. [Example]

[0109] Therefore, to overcome the shortcomings of existing cross-device navigation task synchronization technologies, the present application provides a cross-device navigation task synchronization method. The cross-device navigation task synchronization method can be specifically performed by two terminal devices, namely, a first terminal and a second terminal. The terminal devices can be electronic devices such as a smartphone, an intelligent vehicle control terminal (abbreviated as an in-vehicle terminal) installed in a vehicle, a tablet computer, a smart watch, or a smart band. A navigation application is installed on the terminal device. A navigation task initiated by a user can be performed by using the navigation application.

[0110] It should be noted that the first terminal and the second terminal may be the same type of terminal. For example, the first terminal is a smartphone and the second terminal is also a smartphone. Alternatively, the first terminal and the second terminal may be different types. For example, the first terminal is a smartphone and the second terminal is an in-vehicle terminal, or the first terminal is an in-vehicle terminal and the second terminal is a smartphone. Here, the terminal types of the first terminal and the second terminal are not limited, and an appropriate terminal type may be selected according to the actual navigation scenario.

[0111] 2A, 2B, and 2C are flowcharts of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application. The details are as follows:

[0112] S201: A first terminal obtains navigation data from a first navigation application through a first navigation transfer module when a preset cross-device transmission condition is satisfied.

[0113] In this embodiment, a corresponding cross-device transmission condition may be set for the first terminal. The cross-device transmission condition is used to notify the first terminal that the local navigation task of the first navigation application needs to be synchronized with another terminal (the second terminal in this embodiment). For example, the first terminal may store a cross-device navigation data transmission device list. If the first terminal finds the wireless signal of any registered terminal in the device list, the first terminal recognizes that the cross-device transmission condition is satisfied and performs the operation of step S201. As another example, a corresponding cross-device transmission trigger gesture may be set for the first terminal. If the first terminal detects that a touch control operation initiated by a user matches the preset trigger gesture, the first terminal recognizes that the cross-device transmission condition is satisfied and performs the operation of step S201. The cross-device transmission condition may be specifically set based on the terminal type and actual usage status corresponding to the first terminal. It should be noted that there may be one or more cross-device transmission conditions.

[0114] For example, FIGS. 3(a)-1 and 3(a)-2 are schematic diagrams of a cross-device navigation data transmission scenario according to an embodiment of the present application. Referring to FIGS. 3(a)-1 and 3(a)-2, a user holds a smartphone, and a vehicle equipped with an in-vehicle terminal is located within the surrounding area of ​​the smartphone. A navigation application (i.e., a first navigation application) is running in the foreground of the smartphone. In this case, the user may initiate a slide operation, i.e., a slide track 31, in the direction toward the in-vehicle terminal on an operation interface corresponding to the navigation application. The slide operation is a preset trigger gesture for cross-device navigation data transmission. Therefore, upon detecting that the user has initiated a long slide operation, the smartphone determines that the preset cross-device transmission condition is satisfied and performs the operation of step S201.

[0115] As another example, a scenario of a first terminal includes multiple terminals capable of implementing cross-device transmission. FIGS. 3(b)-1 and 3(b)-2 are schematic diagrams of a cross-device navigation data transmission scenario according to an embodiment of the present application. As shown in FIGS. 3(b)-1 and 3(b)-2, in this scenario, a user holds a smartphone, and within the surrounding area of ​​the smartphone, there are multiple vehicles equipped with in-vehicle terminals. In other words, there are multiple second terminals. In this case, the second terminal with which the first terminal needs to synchronize navigation tasks can be determined in one of the following three ways. The three ways are as follows:

[0116] Method 1: Different cross-device transmission conditions are set for different second terminals. For example, the first terminal may set different trigger gestures for different second terminals. As shown in FIG. 3(b)-1, the trigger gesture corresponding to the in-vehicle terminal of vehicle A is a leftward slide, the trigger gesture corresponding to the in-vehicle terminal of vehicle B is an upward slide, and the trigger gesture corresponding to the in-vehicle terminal of vehicle C is a rightward slide. Based on this, the first terminal may obtain a slide operation initiated by the user on the smartphone and determine the second terminal with which the navigation task needs to be synchronized based on the slide operation and the trigger gesture that matches the slide operation. For example, in this embodiment, when the user initiates a long upward slide operation, the first terminal may use the in-vehicle terminal of vehicle B as the second terminal with which the navigation task needs to be synchronized.

[0117] Method 2: The second terminal with which the navigation task needs to be synchronized is determined based on the relative position between each second terminal and the first terminal. The first terminal may acquire the relative positional relationship between the first terminal and each second terminal based on the signal strength of a wireless signal or by using a distance sensor or other method, and determine the second terminal with which the navigation task will be synchronized based on the relative positional relationship. The relative positional relationship may be the distance between the first terminal and each second terminal and the orientation of the first terminal and each second terminal. For example, the first terminal may acquire the distance between the first terminal and each second terminal and select the second terminal closest to the first terminal as the second terminal with which the navigation task will be synchronized. For example, the distance between the smartphone and the in-vehicle terminal of vehicle A is 2 m, the distance between the smartphone and the in-vehicle terminal of vehicle B is 1 m, and the distance between the smartphone and the in-vehicle terminal of vehicle C is 1.5 m. In this case, the first terminal may further use the in-vehicle terminal of vehicle B as the second terminal with which the navigation task will be synchronized.

[0118] Method 3: The second terminal with which the navigation task needs to be synchronized is determined based on a default priority. The first terminal sets a corresponding synchronization priority for each second terminal in advance. If multiple second terminals are simultaneously detected within range, the second terminal with the highest synchronization priority may be selected as the second terminal with which synchronization needs to be performed based on the corresponding synchronization priority. For example, Table 1 shows a synchronization priority correspondence table pre-stored by the first terminal. As shown in Table 1, the synchronization priority corresponding to the onboard terminal of vehicle A is 1, the synchronization priority corresponding to the onboard terminal of vehicle B is 2, and the synchronization priority corresponding to the onboard terminal of vehicle C is 3. In this case, if the smartphone simultaneously finds the above three onboard terminals, the onboard terminal of vehicle A has the highest synchronization priority, so the onboard terminal of vehicle A is used as the second terminal with which the navigation task needs to be synchronized. [Table 1]

[0119] In this embodiment, a first navigation transfer module is configured for a first terminal, and at least one first navigation application capable of performing a navigation task is installed on the first terminal. The first navigation application is specifically an application running on an application layer of the first terminal. The first navigation application is capable of responding to a navigation task initiated by a user. The first navigation transfer module is specifically configured to perform cross-device navigation task synchronization. The transmission operation includes obtaining navigation data from the first navigation application of the first terminal.

[0120] In this embodiment, the first terminal may obtain navigation data related to the navigation task from the first navigation application through the first navigation transfer module. For example, the navigation data may include the navigation destination, navigation start point, waypoints, navigation route rules, current location, etc. of the navigation task. Specifically, there are important waypoints between the navigation start point and the navigation destination. The user may set one or more waypoints. The generated navigation route uses the navigation start point as the starting point, the navigation destination as the end point, and passes through each waypoint. The navigation route rules are specifically used to determine user preferences when generating a navigation route, such as "high speed priority," "minimum congestion space," or "lowest cost." The navigation application may then generate a corresponding navigation route based on the user preferences and real-time road conditions.

[0121] In a possible implementation, the first navigation transfer module may be a background program running on an application layer of the first terminal, in which case the first navigation transfer module may obtain permission from the application layer to obtain navigation data from the first navigation application, and when it detects that a cross-device transmission condition is satisfied, may obtain corresponding navigation data from the first navigation application based on the permission.

[0122] In a possible implementation, the first navigation transfer module may alternatively be executed in an application framework layer of the first terminal, and may provide a corresponding application programming interface (API) for navigation task synchronization to the first navigation application, and obtain corresponding navigation data from the first navigation application through the API interface.

[0123] In this embodiment, before step S201, the first navigation application of the first terminal is responding to a navigation task initiated by a user, in other words, the first terminal is a terminal that is currently performing a navigation task.

[0124] Still referring to Figures 2A, 2B and 2C, in another embodiment of the present application, the first terminal first needs to respond to a navigation task initiated by a user through the first navigation application before step S201. Based on this, before the first terminal obtains navigation data from the first navigation application through the first navigation transfer module if the cross-device transmission condition is satisfied, the method further includes operations from step S200.1 to step S200.3. The specific description is as follows:

[0125] S200.1: The first terminal generates a navigation task through a first navigation application in response to a user's navigation operation. Navigation data is generated based on the navigation task.

[0126] In this embodiment, the first terminal may run a first navigation application in the foreground. The user may initiate a navigation operation in the operation interface generated by the first navigation application, for example, by inputting a corresponding navigation objective to generate a corresponding navigation task. In the process of executing the navigation task, the first navigation application may generate navigation data corresponding to the navigation task. The navigation operation initiated by the user may be a touch control operation. For example, FIGS. 4a(1), 4a(2), and 4a(3) are schematic diagrams illustrating the initiation of a navigation task according to an embodiment of the present application. Referring to FIG. 4a(1), the first terminal is specifically a smartphone. A navigation application, i.e., application 41, is installed on the smartphone. The user may launch application 41 by tapping an icon corresponding to application 41, thereby generating a corresponding navigation operation interface shown in FIG. 4a(2). The first terminal may receive a navigation destination, e.g., "New World Plaza," input by the user in area 42 (specifically, destination). If the application 41 has previously obtained the location permission of the first terminal, the application 41 may obtain the current location information of the first terminal by using the location module set in the first terminal, and automatically write the current location information into the start location, i.e., area 43. Of course, the user may further adjust the start location according to the actual case, i.e., input the corresponding start location by tapping area 43. In area 44, a navigation scenario in which navigation needs to be performed, such as a driving scenario, a bus scenario, or a walking scenario, may be selected. For example, in FIG. 4a(2), the driving scenario is selected.After all the contents of the navigation task are set, the corresponding navigation task can be generated by tapping control 45 (i.e., Start Navigation), and the first navigation application of the first terminal will begin navigating the user, as shown in Figure 4a(3).

[0127] In a possible implementation, the navigation operation initiated by the user may alternatively be a voice navigation operation. For example, FIGS. 4b(1), 4b(2), and 4b(3) are schematic diagrams illustrating the initiation of a navigation task according to an embodiment of the present application. Referring to FIG. 4b(1), the first terminal is specifically a smartphone, and the smartphone's navigation operation interface includes a voice navigation control 46. When the smartphone detects that the user taps the control 46, the smartphone enters a voice navigation trigger mode shown in FIG. 4b(2). In this state, the smartphone listens for voice commands sent by the user. For example, if the user says, "I want to go to tourist attraction A," the smartphone recognizes that navigation to tourist attraction A needs to be performed for the user and generates a navigation route corresponding to navigation from the current location to tourist attraction A, as shown in FIG. 4b(3).

[0128] For example, FIG. 4c is a schematic diagram of the initiation of a navigation task according to another embodiment of the present application. Referring to (1) of FIG. 4c, the first terminal is specifically an in-vehicle terminal. As shown in (1) of FIG. 4c, after being activated, the in-vehicle terminal can automatically enter a navigation interface. A corresponding voice activation command can be set for the in-vehicle terminal. When the in-vehicle terminal detects that the user has uttered a corresponding voice activation command, such as "Hi, my car," the in-vehicle terminal enters a voice navigation trigger mode. In this state, the in-vehicle terminal listens to voice commands sent by the user. For example, as shown in (2) of FIG. 4c, if the user says, "I want to go to tourist attraction A," the in-vehicle terminal generates a navigation route to tourist attraction A.

[0129] In a possible implementation, a default scenario corresponding to a navigation scenario may be determined based on the terminal type. For example, if the terminal type is an in-vehicle terminal type, the corresponding navigation scenario in the navigation application may be selected as a driving scenario by default. If the terminal type is a portable terminal type, the corresponding navigation scenario in the navigation application may be selected as a walking scenario by default, or as a bus scenario by default. The specific relationship between the default scenario and the terminal type may be set according to actual cases.

[0130] S200.2: The first terminal receives a service registration command sent by the first navigation application through the first navigation transfer module. The service registration command is used to authorize the first navigation application to transmit navigation data between devices.

[0131] In this embodiment, the first navigation application sends a service registration command to the first navigation transfer module so that the first navigation transfer module can obtain corresponding navigation data from the first navigation application when navigation task synchronization needs to be performed thereafter. If the first navigation transfer module is a background program running on the application layer of the first terminal, the first navigation application may send the service registration command to the first navigation transfer module through a virtual communication interface between programs on the application layer. If the first navigation transfer module is a navigation manager running on the application framework layer of the first terminal, the service registration command sent by the first navigation application may be received through an API interface between the first navigation transfer module and the first navigation application.

[0132] S200.3: In response to the service registration command, the first terminal adds the first navigation application to a navigation synchronization application list and sets a first navigation transfer module to an ON state, which is used to send navigation synchronization information generated based on the first navigation application to the second terminal when a cross-device transmission condition is satisfied.

[0133] In this embodiment, the first navigation transfer module of the first terminal may store a navigation synchronization application list. The navigation synchronization application list may record each application that sends a service registration command, such as the first navigation application.

[0134] In a possible implementation, multiple navigation applications, such as Amap, Baidu Maps, and Google Maps, may be installed on the first terminal. If a user launches multiple navigation applications during the use of the first terminal, each navigation application sends a service registration command to the first navigation transfer module. Therefore, the multiple navigation applications are recorded in a navigation synchronization application list maintained by the first navigation transfer module. For example, Table 2 is a schematic diagram of a navigation synchronization application list according to an embodiment of the present application. Referring to Table 2, after launching and executing a corresponding navigation task, any navigation application on the first terminal may associate the time of each received service registration command with the corresponding application identifier and store the association in the navigation synchronization application list. The first terminal may determine the launched navigation applications and the registration time of each navigation application based on the navigation synchronization application list. If a navigation application performs multiple navigation tasks during the launch process of the first terminal, the navigation application may send multiple service registration commands to the first navigation transfer module. For example, based on the first and fourth entries in Table 2, the navigation application Baidu Maps has sent service registration instructions to the first navigation transfer module at two time points, 14:00 and 17:11. In this case, the first navigation transfer module may obtain corresponding navigation data from the first navigation application with the latest registration time, for example, Baidu Maps, which has the registration time of 17:11 in Table 2. Optionally, the first navigation transfer module obtains corresponding navigation data from the first navigation application currently running in the foreground. [Table 2]

[0135] In this embodiment, each first navigation application that sends a service registration command to the first navigation transfer module forms a navigation application ecosystem of the first terminal. In this embodiment, the first terminal is specifically a terminal that initiates a navigation synchronization task. In other scenarios, the first terminal may be a terminal that responds to a navigation synchronization task initiated by another terminal. In this case, the first terminal may select the first navigation application that sent the service registration command from the navigation application ecosystem to synchronize the navigation task with the peer end.

[0136] In this embodiment, after receiving the service registration command of the first navigation application, the first navigation transfer module can set the task synchronization switch of the first navigation transfer module to an ON state. Therefore, when it is subsequently detected that the corresponding cross-device transmission condition is satisfied, the navigation task synchronization procedure can be automatically triggered. In other words, the operations from step S201 to step S203 are performed.

[0137] In a possible implementation, the status switch of the first navigation transfer module may also be manually set by the user.

[0138] For example, Figures 5(a), 5(b), 5(c), and 5(d) are schematic diagrams illustrating the setting of a status switch of a first navigation transfer module according to an embodiment of the present application. Referring to Figure 5(a), the first terminal responds to a navigation operation initiated by a user. For example, the user taps a navigation control 51 of the first navigation application to generate a navigation task corresponding to the navigation operation. In this case, the first terminal may generate a prompt box 52 to prompt the user whether to enable the navigation task synchronization service. As shown in Figure 5(b), the prompt box 52 includes an accept control 53 and a decline control 54. When the user consent When the first terminal detects that the control 53 is tapped, it recognizes that the user has confirmed that the navigation task synchronization service is enabled, and the first navigation transfer module is set to an on state.

[0139] In another implementation, the navigation task synchronization switching of the first navigation transfer module of the first terminal may be manually set in the setting interface of the terminal. For example, FIG. 5(c) shows the home screen of the first terminal. The home screen includes a setting icon 55. When the user clicks the setting icon 55 After detecting a tap on control 56, the first terminal may generate a corresponding setting interface shown in FIG. 5(d). In the setting interface, the user can configure multiple items of the first terminal, such as enabling the Bluetooth module of the first terminal, selecting peripheral devices connected to the Bluetooth module, or configuring a wireless network. The first terminal may respond to the tap operation initiated by the user to change the status of the first navigation transfer module. As shown in FIG. 5(d), the first navigation transfer module is in an on state. If a tap operation performed by the user on control 56 is detected, the first navigation transfer module may be changed from an on state to an off state.

[0140] In this embodiment of the present application, before performing navigation task synchronization, when starting a navigation operation for a first navigation application, the first terminal automatically sends a corresponding service registration command to the first navigation transfer module. The first navigation transfer module can add the first navigation application to the corresponding navigation synchronization application list and automatically set the first navigation transfer module to an on state. In this way, the user does not need to manually set the status of the first navigation transfer module, thereby improving setting efficiency.

[0141] In addition, in another embodiment of the present application, when the first terminal detects that the preset cross-device transmission condition is satisfied, it indicates that navigation task synchronization needs to be performed. In this case, in order to improve the success rate of navigation task synchronization, Terminal can determine whether the first navigation application satisfies the navigation task synchronization condition, including the following two aspects:

[0142] Condition 1: Does the primary navigation application have navigation task synchronization permission?

[0143] Condition 2: Is the first navigation application currently running in the foreground on the first device?

[0144] Different types of navigation applications may be installed on the first terminal. Not all navigation applications support the navigation task synchronization service, so in this case, the first navigation transfer module may store an application trust list that supports navigation task synchronization or an application block list that does not support navigation task synchronization. The first terminal determines whether the first navigation application currently initiating the navigation task is in the application trust list or the corresponding application block list to determine whether the first navigation application has navigation task synchronization permission. If the first navigation application is in the application trust list (i.e., not in the application block list), the first navigation application can initiate the navigation task synchronization. synchronization It is recognized that you have permission.

[0145] Regarding condition 2, since the first terminal can perform different application synchronization operations, if it is detected that the cross-device transmission condition is satisfied, it can detect whether the first navigation application is an application running in the foreground to determine whether the navigation task currently needs to be synchronized. In this case, it can be determined that the first terminal is executing a navigation task initiated by the user and is viewing navigation information output by the first navigation application in real time. Based on this, navigation task synchronization can be performed to synchronize the navigation task running in the first navigation application with the navigation application of another terminal, i.e., the second navigation application of the second terminal.

[0146] In this embodiment, after detecting that the cross-device transmission conditions are satisfied, the first terminal may perform prerequisite determination for the first navigation application to ensure the success rate of navigation task synchronization and avoid unnecessary synchronization operations.

[0147] S202: The first terminal generates navigation synchronization information of the navigation data through a first navigation transfer module.

[0148] In this embodiment, after obtaining navigation data from the first navigation application through the first navigation transfer module, the first terminal may generate corresponding navigation synchronization information based on the navigation data.

[0149] In a possible implementation, the first navigation transfer module may directly encapsulate the acquired navigation data and then generate the corresponding navigation synchronization information. In other words, the first navigation transfer module does not perform any processing on the data content of the navigation data, but adds a header or a tail of the corresponding data packet to generate and acquire the corresponding navigation synchronization information.

[0150] In a possible implementation, the first navigation transfer module may preprocess the navigation data. The preprocessing may include, but is not limited to, data cleaning, data standardization, and / or data format conversion. During cross-device navigation task synchronization, the first navigation application installed on the first terminal and the second navigation application installed on the second terminal may not be the same navigation application. To perform cross-device and cross-application navigation data transmission to further complete the navigation task synchronization, the first navigation transfer module may preprocess the navigation data so that the generated navigation synchronization information can be read by the second navigation application of the second terminal. A method for preprocessing the navigation data to generate corresponding navigation synchronization information may be as follows.

[0151] Method 1: Data Standardization Processing. The first navigation transfer module may convert navigation data into data in a standard format that can be compatible with different types of navigation applications. The first navigation transfer module stores a corresponding standard format template. The standard format template includes multiple information items. For example, Table 3 is a schematic diagram of the format of a standard format template according to an embodiment of the present application. As shown in Table 3, corresponding fields are set for different information items in the standard format template. The first navigation transfer module may extract parameter values ​​corresponding to each information item from the navigation data and write the parameters into the corresponding fields to generate corresponding data in a standard format, i.e., navigation synchronization information. A peer end can obtain the corresponding data from the corresponding fields, thereby achieving cross-device and cross-application navigation data synchronization. A header may limit the data length corresponding to the standard format data. Because the number of relay points is variable, more relay points correspond to an increasingly longer data length of the standard format data. Therefore, the data length of the standard format data may be defined using a header, so that specific customized content can be conveyed when the data format standardization is ensured. [Table 3]

[0152] Method 2: Data Format Conversion. The first navigation transfer module may perform format conversion on the navigation data obtained from the first navigation application to convert the navigation data into a data format adapted to the second navigation application, i.e., navigation synchronization information. In this case, the first terminal may send a navigation application detection request to the second terminal. In response to the navigation application detection request, the second terminal may add an application identifier of the second navigation application to response information. The first terminal parses the response information to obtain the application identifier of the second navigation application, determines a data format consistent with the second navigation application, converts the navigation data into the data format, and generates corresponding navigation synchronization information.

[0153] Still referring to Figures 2A, 2B and 2C, in another embodiment of the present application, steps S202.1 and S202.2 may be further included before the first terminal sends the navigation synchronization information to the second terminal. A specific description is as follows:

[0154] S202.1: The first terminal obtains a navigation application list of the second terminal, where the navigation application list includes the second navigation application.

[0155] In this embodiment, the first terminal may send an application list acquisition request to the second terminal. The application list acquisition request is specifically used to determine the navigation applications installed on the second terminal. In response to the application list acquisition request, the second terminal may add the application identifiers of each locally installed navigation application to a navigation application list and feed the navigation application list back to the first terminal. Because the second navigation application for which navigation task synchronization needs to be performed is also installed on the second terminal, the navigation application list also includes the second navigation application.

[0156] S202.2: The first terminal sends navigation synchronization information to the second terminal when the first terminal detects that a navigation application matching the first navigation application exists in the navigation application list, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application.

[0157] In this embodiment, after obtaining the navigation application list, the first terminal may determine whether an application capable of performing a cross-device navigation task, that is, an application with permission to perform cross-device navigation data transmission with the first navigation application, is installed on the second terminal. If an application capable of performing a cross-device navigation task is installed on the second terminal, the first terminal may send navigation synchronization information to the second terminal. Otherwise, if an application capable of performing a cross-device navigation task is not installed on the second terminal, in this case, even if the first terminal sends navigation synchronization information to the second terminal, the second terminal cannot perform navigation task synchronization based on the navigation synchronization information. In this case, the first terminal does not send navigation synchronization information to the second terminal.

[0158] In another implementation, if a navigation application matching the first navigation application does not exist 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 of an application having a prompt for performing cross-device navigation data transmission with the first navigation application.

[0159] For example, FIGS. 6(a) and 6(b) are schematic diagrams of an application installation prompt of a second terminal according to an embodiment of the present application. Referring to FIG. 6(a), the second terminal may specifically be an in-vehicle terminal. After the first terminal sends an application installation command to the second terminal, the second terminal may generate application installation prompt information to query whether the user agrees to install a navigation application matching the first navigation application. The application installation prompt information includes a consent control 61 and a denial control 62. When it is detected that the user taps the consent control 61, an installation procedure for a navigation application capable of implementing navigation task synchronization is executed, and a corresponding installation process and corresponding installation phase are displayed, as shown in FIG. 6(b). After the installation of the matching navigation application is completed, the second terminal may newly send a navigation application list to the first terminal. In this case, the first terminal recognizes that the navigation application list includes a navigation application matching the first navigation application, and may send navigation synchronization information to the second terminal.

[0160] In this embodiment of the present application, before sending navigation synchronization information to the second terminal, the first terminal first determines whether the second terminal has a navigation application that can respond to navigation task synchronization, and if a corresponding navigation application is installed on the second terminal, sends the navigation synchronization information to the second terminal, so as to improve the success rate of navigation task synchronization and avoid unnecessary synchronization operations.

[0161] Still referring to Figures 2A, 2B and 2C, in step S203, the second terminal receives the navigation synchronization information sent by the first terminal and sends the navigation synchronization information to the second navigation application through a second navigation transfer module.

[0162] In this embodiment, the first terminal establishes a communication connection with the second terminal. The communication connection may be a wireless connection, such as a Bluetooth connection, a Near Field Communication (NFC) connection, or a Wireless Fidelity (Wi-Fi) connection. Based on the communication connection between the first terminal and the second terminal, the second terminal can receive navigation synchronization information sent by the first terminal. The first terminal can send the navigation synchronization information to the second terminal by invoking a wireless communication interface through a first navigation transfer module, i.e., a communication protocol corresponding to the wireless communication interface. Correspondingly, the second terminal can also receive the navigation synchronization information by invoking a corresponding wireless communication interface through a second navigation transfer module.

[0163] 2A, 2B, and 2C, in another embodiment of the present application, after receiving the navigation synchronization information sent by the first terminal, the second terminal may 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 following steps may be further included:

[0164] S203.1: The second terminal detects whether a navigation application matching the first navigation application exists in the navigation application list.

[0165] S203.2: When the second terminal detects that a navigation application matching the first navigation application exists in the navigation application list, the second terminal uses the navigation application matching the first navigation application as the second navigation application and performs an operation of sending navigation synchronization information to the second navigation application through a second navigation transfer module. The navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application.

[0166] In this embodiment, the first terminal can determine whether a navigation application capable of implementing navigation task synchronization is installed on the second terminal. Furthermore, the second terminal can also check the feasibility of task synchronization for 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 on the second terminal. In this case, the second terminal can determine the application type of the first navigation application installed on the first terminal based on the navigation synchronization information sent by the first terminal, and determine whether a navigation application matching the first navigation application exists among the locally installed navigation applications. If a navigation application matching the first navigation application is installed on the second terminal, that is, the first Navigation ApplicationsIf a navigation application matching the navigation task synchronization information exists in the navigation application list of the second terminal, the second terminal may use the matching navigation application as the navigation application for navigation task synchronization. Accordingly, the second navigation transfer module may send the received navigation synchronization information to the second navigation application.

[0167] In this embodiment of the present application, after the second terminal receives the navigation synchronization information, the second terminal determines whether the second terminal has a navigation application locally that can respond to the navigation task synchronization, and if the corresponding navigation application is installed on the second terminal, the navigation synchronization information can be sent to the corresponding navigation application, so as to improve the success rate of the navigation task synchronization and avoid unnecessary synchronization operations.

[0168] In a possible implementation, before sending the navigation synchronization information to the second navigation application, the second navigation transfer module may further preprocess the navigation synchronization information 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 preprocessing method is the same as the method in which the first terminal preprocesses navigation data. For a specific description, please refer to the relevant description of step S202. The details will not be described again here.

[0169] In a possible implementation, if multiple navigation applications are installed on the second terminal and all of the multiple navigation applications match the first navigation application of the first terminal, the second terminal may determine a navigation application for navigation task synchronization, i.e., a second navigation application, based on the startup time of each local navigation application. For example, the second navigation transfer module may select a navigation application that was recently launched as the second navigation application for navigation task synchronization. Optionally, the second navigation transfer module may determine a navigation application for navigation task synchronization based on the startup time, and may further determine a navigation application that is commonly used by the user based on the number of times each navigation application installed on the second terminal is used, and use the commonly used navigation application as the second navigation application.

[0170] Still referring to FIGS. 2A, 2B and 2C, in step S204, the second terminal updates the navigation task of the second navigation application based on the navigation synchronization information.

[0171] In this embodiment, after the second navigation transfer module of the second terminal sends the navigation synchronization information to the second navigation application, the second navigation application synchronizes the first navigation application with the second navigation application. application and setting a corresponding navigation task for the first navigation application of the first terminal to perform navigation task synchronization between the first navigation application and the second navigation application. Updating the navigation task for the second navigation application includes two cases.

[0172] Case 1: Secondary navigation application is ,NaIn this case, the second terminal may generate a corresponding navigation task based on the navigation synchronization information.

[0173] Case 2: Before synchronization, the second navigation application is executing another navigation task. In this case, the second terminal may change the navigation task of the second navigation application based on the navigation synchronization information so that the navigation task of the second navigation application is consistent with the navigation task being executed by the first navigation application of the first terminal.

[0174] For example, Figures 7(a) and 7(b) are schematic diagrams of changing a navigation task according to an embodiment of the present application. Referring to Figure 7(a), before performing navigation task synchronization, the second terminal is executing a navigation task for navigation to location A. In this case, the first terminal synchronizes the navigation task (navigation task for navigation to location B) with the second terminal and sends corresponding navigation synchronization information to the second terminal. In this case, as shown in Figure 7(b), the second terminal may update the navigation task of the second navigation application based on the navigation synchronization information to change the destination from location A to location B.

[0175] 2A, 2B, and 2C, in a possible implementation, before the navigation task synchronization is performed for the second navigation application, the user may be asked whether to agree to the synchronization operation. Based on this, step S204 may specifically include the following steps:

[0176] 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.

[0177] S204.2: The second terminal updates the navigation task based on the navigation destination when the second terminal receives an update confirmation command fed back based on the update prompt information.

[0178] In this embodiment, before updating the navigation task of the second navigation application, the second terminal may generate corresponding task update prompt information to determine whether the user agrees to the update operation on the navigation task. If the user agrees to the update operation on the navigation task, the user may initiate a corresponding consent operation on the second terminal. The second terminal may generate a corresponding update confirmation command based on the consent operation. After the second navigation application receives the update confirmation command, the navigation task may be updated based on the navigation destination in the navigation synchronization information.

[0179] For example, FIGS. 8(a), 8(b), and 8(c) are schematic diagrams illustrating updating a navigation task according to an embodiment of the present application. After receiving the navigation synchronization information, the second navigation application of the second terminal may 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, the task update prompt information is generated. The content of the prompt information may be displayed as "Do you want to continue the navigation task on your mobile phone UserA?" Here, as shown in FIG. 8(a), UserA is a mobile phone identifier of a smartphone to help the user determine a specific device to synchronize the navigation task with the second terminal. The prompt information may also be displayed as "Do you want to continue the navigation task to tourist attraction B?" to help the user determine a specific destination of the navigation task to be updated this time. The task prompt information includes a confirmation control 81 and a cancel control 82. When detecting that the user taps the confirmation control 81 in the second navigation application, the second terminal may update the navigation task based on the navigation destination. As shown in Figure 8(b), after the user taps confirmation control 81, the navigation destination of the second navigation application may be changed to tourist attraction B. If the user taps cancel control 82, the original navigation destination is maintained. As shown in Figure 8(c), the navigation destination of the second navigation application remains tourist attraction A.

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

[0181] 2A, 2B, and 2C, in another embodiment of the present application, after updating the navigation task of the second navigation application based on the navigation synchronization information, the second terminal may notify the first terminal that the navigation task synchronization is completed. In other words, after step S204, the following steps may be included:

[0182] S205: The second terminal sends navigation synchronization completion information to the first terminal through the second navigation transfer module.

[0183] S206: In response to the navigation synchronization completion information, the first terminal sends a termination command for the navigation task to the first navigation application through the first navigation transfer module, to stop the navigation task of the first navigation application.

[0184] In this embodiment, after the navigation task update is completed, the second terminal may send navigation synchronization completion information to the first terminal through the second navigation transfer module. After receiving the navigation synchronization completion information sent by the second terminal, the first terminal may determine that the second terminal has completed navigation task synchronization, that is, the navigation task continues on the second terminal for execution from the first terminal. In this case, the first terminal may terminate the navigation task that was being executed locally. Therefore, the first navigation transfer module may send a termination command to the first navigation application. After receiving the termination command, the first navigation application may stop the navigation task being executed in the first navigation application of the first terminal. In this way, the navigation task is transferred.

[0185] For example, Figures 9(a), 9(b), 9(c), and 9(d) are schematic diagrams illustrating the end of a navigation task according to an embodiment of the present application. Referring to Figure 9(a), after sending navigation synchronization information to the second terminal through the first navigation transfer module, the first terminal may locally display prompt information "synchronizing" and display the corresponding synchronization process based on the time consumed for synchronization and the current waiting time in a general case. As shown in Figure 9(b), when the first terminal receives navigation synchronization completion information sent by the second terminal, the first terminal may generate prompt information "synchronization completed" to prompt the user that the second terminal has completed navigation task synchronization. In this case, the first terminal may directly end the navigation task, for example, exit the first navigation application and return to the home screen of the navigation task, or return to the initial interface of the application as shown in Figure 9(d). Optionally, as shown in FIG. 9(c), after the first terminal receives the navigation synchronization completion information, the generated prompt information may include an end confirmation control 91 to query the user whether to end the navigation task of the first navigation application. When the first terminal detects that the user has tapped the end confirmation control 91, the first terminal may end the navigation task of the first navigation application of the first terminal and return to the initial interface of the application shown in FIG. 9(d). Indeed, the end confirmation control 91 may further display a corresponding valid waiting time. If the first terminal does not receive a tap on the end confirmation control 91 by the user within the valid waiting time, the first terminal may also end the currently running navigation task of the first navigation application of the first terminal.

[0186] In a possible implementation, a maximum waiting time may be set for the first terminal. If the first terminal transmits navigation synchronization information to the second terminal and does not receive navigation synchronization completion information fed back by the second terminal within the maximum waiting time, the first terminal recognizes that navigation task synchronization to the second terminal has failed. In this case, the first terminal may display prompt information indicating that synchronization has failed. For example, FIGS. 10(a) and 10(b) are schematic diagrams of synchronization failure responses according to an embodiment of the present application. Referring to FIG. 10(a), if the first terminal does not receive navigation synchronization completion information within the maximum waiting time, the first terminal may display corresponding synchronization failure prompt information in the first navigation application. The prompt information may include a "retry" control 101, a "switch synchronization device" control 102, and a "cancel" control 103. If the first terminal detects that the user has tapped the control 101, the first terminal resends the navigation synchronization information to the second terminal so that the second terminal performs navigation task synchronization again based on the navigation synchronization information. When the first terminal detects that the user taps control 102, a terminal identifier of another terminal with which synchronization may be performed may be generated, as shown in Fig. 10(b). The user may newly select a terminal with which navigation task synchronization needs to be performed from the other displayed terminals, and send navigation synchronization information to that terminal to perform navigation task synchronization. When the first terminal detects that the user taps control 103, it indicates exiting the navigation synchronization operation and returning to the original interface of the navigation task.

[0187] From the above, it can be seen that in the cross-device navigation task synchronization method provided in this embodiment of the present application, when the first terminal detects that the cross-device transmission condition is satisfied, the first terminal automatically obtains navigation data of the initiated navigation task from the first navigation application through a local first navigation transfer module of the first terminal, generates navigation synchronization information corresponding to the navigation data through the first navigation transfer module, and transmits the navigation synchronization information to the second terminal, thereby achieving cross-device navigation data transmission. After receiving the navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through a local second navigation transfer module. The second terminal can then update the navigation task of the second navigation application based on the navigation synchronization information to achieve cross-device navigation task synchronization. Compared with existing navigation technologies, cross-device navigation task synchronization can be implemented in the present application. In a scenario where cross-device navigation needs to be performed, the user does not need to set the task of the terminal's navigation application multiple times. Instead, the navigation data can be automatically transferred through the navigation transfer module to update the navigation task of the navigation application, thereby greatly improving the efficiency of the navigation task set and reducing the user's repetitive operations. Moreover, after obtaining the navigation data from the first navigation application, the first navigation transfer module of the first terminal does not directly send the navigation data to the second navigation transfer module of the second terminal, but converts the navigation data into corresponding navigation synchronization information. The navigation synchronization information can be transferred between the navigation transfer modules of different terminals. The navigation synchronization information is then sent to the second navigation application through the second navigation transfer module. The navigation synchronization information is not directly transferred between the navigation applications of the two terminals.Therefore, the same navigation application does not need to be installed on the first terminal and the second terminal. In this way, cross-device and cross-application navigation data transfer can be implemented, thereby further improving the coverage of navigation task synchronization. [Example]

[0188] Compared with Example 1, the cross-device transmission condition in Example 2 is a touch operation transmission condition. Specifically, Example 2 specifically describes a specific implementation procedure when navigation task synchronization is triggered between two terminals by a touch operation. In this embodiment, the first terminal may be a terminal that initiates a touch operation (i.e., a terminal that actively approaches another terminal). For example, a user holds the first terminal to initiate a touch operation to the second terminal. Alternatively, the first terminal may be a terminal that passively responds to the touch operation. For example, a user controls the second terminal to initiate a touch operation to the first terminal. For example, the following example is used for explanation: the first terminal is a smartphone, and the second terminal is an intelligent vehicle control terminal (abbreviated as an in-vehicle terminal) installed in a vehicle.

[0189] In this embodiment, a user holds a smartphone and controls the smartphone to perform a touch operation on the in-vehicle terminal. The smartphone and the in-vehicle terminal are configured with NFC modules. The two terminals can establish a short-range communication connection through the NFL to exchange data. For example, FIGS. 11A and 11B are schematic diagrams of interactions in a cross-device navigation task synchronization method according to an embodiment of the present application. The synchronization method is applied to a touch-trigger scenario. A specific interaction process is as follows:

[0190] S1103: In response to a touch operation by the smartphone, the in-vehicle terminal transmits a communication label to the smartphone through the short-range communication module of the in-vehicle terminal.

[0191] In this embodiment, a user can control the smartphone to initiate a touch operation on the in-vehicle terminal. In this case, the distance between the NFC module of the in-vehicle terminal and the NFC module of the smartphone is shorter than a preset distance threshold. Therefore, a short-range communication connection can be established between the in-vehicle terminal and the smartphone through the NFC module. In this case, the in-vehicle terminal can send a pre-written communication label to the smartphone through the established short-range communication connection.

[0192] For example, Figure 12 is a schematic diagram of a touch scenario between an in-vehicle terminal and a smartphone according to an embodiment of the present application. Referring to Figure 12, a user holds the smartphone, and the smartphone touches the in-vehicle terminal to activate the NFC modules of the two terminals, and establish a short-range communication connection between the two terminals through the NFC modules, thereby transmitting the communication label and subsequent navigation synchronization information.

[0193] In this embodiment, to start the synchronization procedure of the navigation task, the communication label sent by the in-vehicle terminal may carry a navigation task synchronization start identifier. After receiving the communication label including the start identifier, the smartphone may determine that the cross-device transmission condition is satisfied and start the synchronization procedure of the navigation task.

[0194] In this embodiment, in addition to the navigation task synchronization start identifier, the communication label may further include a terminal identifier of the in-vehicle terminal, a module identifier of the NFC module, etc. Indeed, the in-vehicle terminal may further add an application identifier of a locally installed navigation application to the communication label. The information specifically included in the communication label may be adjusted according to actual cases. The content of the communication label is not limited here.

[0195] In addition, in another embodiment of the present application, before the in-vehicle terminal responds to the touch operation initiated by the smartphone, the in-vehicle terminal may write a communication label in the short-range communication module of the in-vehicle terminal in advance. In other words, steps S1101 and S1102 may be included before step S1103. A detailed description is as follows:

[0196] S1101: The vehicle-mounted terminal sends a label writing request to the label service thread through the second navigation forwarding module if a preset label writing condition is satisfied.

[0197] S1102: The vehicle-mounted terminal responds to the label write request through the label service thread, adds the start identifier to the communication label, and writes the communication label to the short-range communication module of the vehicle-mounted terminal.

[0198] In this embodiment, the in-vehicle terminal first sends a label service request to the in-vehicle terminal through a second navigation transfer module configured in the in-vehicle terminal when a preset label writing condition is satisfied. thread , and writes the corresponding communication label to the short-range communication module of the in-vehicle terminal. The label writing condition may specifically be that the in-vehicle terminal is turned on. For example, when the vehicle is turned on, the in-vehicle terminal installed in the vehicle is turned on at the same time. In this case, the in-vehicle terminal recognizes that the preset label writing condition is satisfied and performs the operation of step S1101.

[0199] In this embodiment, the label service thread runs on the in-vehicle terminal. The label service thread is specifically used to write a communication label to the short-range communication module of the in-vehicle terminal. Therefore, when the second navigation transfer module sends a label write request to the label service thread, it indicates that the in-vehicle terminal starts a navigation task synchronization service. Based on this, the label service write thread can generate a start identifier, add the start identifier to the communication label, and write the communication label with the start identifier added to the short-range communication module of the in-vehicle terminal.

[0200] In this embodiment of the present application, when the label writing condition is satisfied, the label service thread writes a communication label carrying navigation task synchronization to the short-range communication module of the vehicle-mounted terminal. Therefore, when the communication label is sent to the peer end, the navigation task synchronization procedure can be started automatically, thereby reducing user operations and improving synchronization efficiency.

[0201] S1104: In response to the communication label, the smartphone launches a first navigation transfer module and obtains navigation data from a first navigation application through the first navigation transfer module.

[0202] In this embodiment, after receiving the communication label transmitted by the in-vehicle terminal, the smartphone may parse the communication label, and if the smartphone detects that the communication label carries a navigation synchronization start identifier, the smartphone may activate and configure a first navigation transfer module of the smartphone and obtain navigation data from the first navigation application through the first navigation transfer module.

[0203] Optionally, before the first navigation transfer module obtains navigation data from the first navigation application, a prerequisite determination may be performed. The following two determination steps may be specifically included:

[0204] S1105: Determine whether the first navigation application has navigation task synchronization permission.

[0205] S1106: Determine whether a first navigation application is currently running in the foreground on the smartphone.

[0206] If both determination operations are positive, the first navigation transfer module can obtain navigation data from the first navigation application.For specific process and determination method, please refer to the relevant description of step S201 in embodiment 1.Details will not be described again here.

[0207] S1107: The smart phone generates navigation synchronization information of the navigation data through the first navigation transfer module.

[0208] The implementation of step S1107 is completely the same as that of step S202 in embodiment 1, so for specific explanation, please refer to the relevant description of step S202, and the details will not be described again here.

[0209] S1108: The in-vehicle terminal receives the navigation synchronization information sent by the smart phone, and sends the navigation synchronization information to the second navigation application through the second navigation transfer module.

[0210] The implementation of step S1108 is completely the same as that of step S203 in the first embodiment, so for a specific description, please refer to the relevant description of step S203. The details will not be described again here. In other words, in step S1108, the in-vehicle terminal can also determine whether a navigation application matching the first navigation application is locally installed on the in-vehicle terminal 2, and if a matching navigation application exists, recognize the matching navigation application as the second navigation application.

[0211] S1109: The in-vehicle terminal updates the navigation task of the second navigation application based on the navigation synchronization information.

[0212] Optionally, step S1109 further includes:

[0213] S1109.1: The in-vehicle terminal determines a navigation destination based on the navigation synchronization information, and generates task update prompt information based on the navigation destination.

[0214] S1109.2: The in-vehicle terminal updates the navigation task based on the navigation destination when the in-vehicle terminal receives an update confirmation command fed back based on the update prompt information.

[0215] The implementation of step S1109 is completely the same as that of step S204 in Example 1. The implementation of step S1109.1 is completely the same as that of step S204.1 in Example 1. The implementation of step S1109.2 is completely the same as that of step S204.2 in Example 1. For specific descriptions, please refer to the relevant descriptions of steps S204, S204.1 and S204.2. The details will not be described again here.

[0216] Optionally, after step S1109, the following may be further included:

[0217] S1110: The in-vehicle terminal transmits navigation synchronization completion information to the smartphone through the second navigation transfer module.

[0218] S1111: In response to the navigation synchronization completion information, the smartphone sends a termination command for the navigation task to the first navigation application through the first navigation transfer module to stop the navigation task of the first navigation application.

[0219] The implementation of step S1110 is completely the same as that of step S205 in embodiment 1. The implementation of step S1111 is completely the same as that of step S206 in embodiment 1. For specific descriptions, please refer to the relevant descriptions of steps S205 and S206. The details will not be described again here.

[0220] In this embodiment of the present application, if a wireless connection has not been established between the first terminal and the second terminal, a communication connection between the first terminal and the second terminal can be immediately established through a touch operation. A navigation task synchronization start identifier is added to the communication label. The communication label is sent to the first terminal through a short-range communication connection to immediately start a navigation task synchronization procedure, thereby improving the efficiency of navigation task synchronization. [Example]

[0221] Compared with Example 1, the application scenario of this embodiment is specifically that when the vehicle is activated, the navigation task of the user terminal carried by the user is synchronized with the intelligent vehicle control terminal installed in the vehicle. Based on this, the first terminal is specifically the user terminal carried by the user, and the second terminal is the vehicle-mounted terminal. Figures 13A, 13B, 13C, 13D, and 13E are schematic diagrams of interactions in the navigation task synchronization method according to an embodiment of the present application. A specific description is as follows:

[0222] S1301: In response to a user's navigation operation, a user terminal generates a navigation task through a first navigation application, and generates navigation data based on the navigation task.

[0223] S1302: The user terminal receives a service registration command sent by the first navigation application through the first navigation transfer module, which is used to authorize the first navigation application to transmit navigation data between devices.

[0224] S1303: In response to the service registration command, the user terminal adds the first navigation application to a navigation synchronization application list and sets a first navigation transfer module to an ON state, which is used to send navigation synchronization information generated based on the first navigation application to the in-vehicle terminal when a cross-device transmission condition is satisfied.

[0225] The implementation of step S1301 is completely the same as that of step S200.1 in embodiment 1. The implementation of step S1302 is completely the same as that of step S200.2 in embodiment 1. The implementation of step S1303 is completely the same as that of step S200.3 in embodiment 1. For specific descriptions, please refer to the relevant descriptions of steps S2001.1 to S200.3. The details will not be described again here.

[0226] Compared with Example 1, before the user terminal obtains navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied, this embodiment further includes:

[0227] S1304: The in-vehicle terminal establishes a communication connection to the user terminal when a wake-up event related to the vehicle is detected.

[0228] In this embodiment, the application scenario is that after a user gets into a vehicle, a transition from a walking scenario to a driving scenario is initiated. In this case, the navigation task of the user terminal needs to be synchronized with the vehicle's onboard terminal. Therefore, the trigger event specifically is detecting that the vehicle is started. The start-up event may include a vehicle door opening event, a vehicle ignition event, a vehicle power button press event, etc., and may be used to determine the vehicle start-up time. When a start-up event related to the vehicle is detected, the onboard terminal may recognize that the user's navigation scenario has changed. Therefore, the onboard terminal may establish a communication connection with the user terminal carried by the user. The communication connection may be established by a short-range communication module. The short-range communication module may be a module capable of implementing short-range wireless communication, such as a Bluetooth communication module, a Bluetooth low energy communication module, or a Wi-Fi module.

[0229] In this embodiment, the operation of recognizing the trigger event is completed by the in-vehicle terminal. The reason is as follows: in a scenario where a user terminal synchronizes a navigation task with the in-vehicle terminal, it is relatively difficult to recognize whether the user has started the vehicle. However, if a vehicle start-up event is detected using the in-vehicle terminal, the in-vehicle terminal can easily and accurately determine that the user's navigation scenario is switched to a driving scenario, thereby improving the accuracy of navigation task synchronization and reducing the difficulty of recognition.

[0230] In this embodiment, the wireless communication connection is specifically established between the user terminal and the in-vehicle terminal. When the wireless communication connection is established between the user terminal and the in-vehicle terminal, the user terminal and the in-vehicle terminal record connection information of the user terminal and the in-vehicle terminal. The connection information includes, but is not limited to, a device identifier, a connection key, a wireless network identifier, etc. In this case, the in-vehicle terminal and the user terminal can establish a communication connection between the in-vehicle terminal and the user terminal based on the recorded connection information.

[0231] For example, when a Bluetooth communication connection is established between the user terminal and the in-vehicle terminal, the user terminal records the Bluetooth connection information of the in-vehicle terminal and adds the user terminal to its authorized device list. Similarly, the in-vehicle terminal also stores the Bluetooth connection information of the user terminal and adds the in-vehicle terminal to its local authorized device list. When the in-vehicle terminal finds and detects a vehicle door opening event, the in-vehicle terminal may find whether the Bluetooth signal of the user terminal is detected. If the Bluetooth signal of the user terminal is found, the in-vehicle terminal sends a Bluetooth connection request to the user terminal based on the Bluetooth connection information of the user terminal. Because the in-vehicle terminal is recorded in the authorized device list of the user terminal, the user terminal agrees to the Bluetooth connection request and establishes a Bluetooth communication connection to the in-vehicle terminal.

[0232] Furthermore, in another embodiment of the present application, the method for establishing a communication connection between a user terminal and an in-vehicle terminal may be specifically implemented by using the following steps:

[0233] S1304.1: The in-vehicle terminal recognizes the connection status of each registered terminal in the preset registered device list through the second navigation forwarding module.

[0234] In this embodiment, after detecting a vehicle door opening event, the in-vehicle terminal can search for a wireless signal in the current scenario through the wireless communication module. Therefore, the in-vehicle terminal can determine the connection status of each connected registered terminal in the pre-stored registered device list based on the found wireless signal, and feed back the collected result to the second navigation transfer module of the in-vehicle terminal. The second navigation transfer module can perform corresponding operations based on the connection status corresponding to each registered terminal. If the wireless signal of a registered terminal can be found in the current scenario, the registered terminal can be recognized as being in a connectable state, that is, the device is in an online state. In contrast, if the wireless signal of a registered terminal cannot be found in the current scenario, the second navigation transfer module can perform corresponding operations based on the connection status corresponding to each registered terminal. do not have In this case, the registered terminal may be recognized as being in an unreachable state, that is, the device may be recognized as being in an offline state.

[0235] S1304.2: If the in-vehicle terminal recognizes that the user terminal is in the registered device list and the connection status of the user terminal is connectable, the in-vehicle terminal establishes a communication connection to the user terminal based on connection information associated with the user terminal in the registered device list.

[0236] In this embodiment, if the user terminal is online, that is, if the user terminal and the in-vehicle terminal are in a connectable state, the in-vehicle terminal may send connection information related to the user terminal to the user terminal. The connection information has been recorded in the local memory by the in-vehicle terminal during a previous connection process between the user terminal and the in-vehicle terminal. Therefore, after receiving the connection information, the user terminal may recognize that the request to establish the current wireless connection is valid. Therefore, the user terminal responds to the connection request and establishes a communication connection to the in-vehicle terminal.

[0237] S1304.3: If the in-vehicle terminal recognizes that the user terminal is not in the registered device list, or that the user terminal is in the registered device list but the connection status of the user terminal is in an unconnectable state, the in-vehicle terminal sends a wake-up command to the user terminal through the near-field communication module of the in-vehicle terminal.

[0238] In this embodiment, when 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 of the user terminal is not activated. The other possibility is that the user terminal has established a wireless communication connection to another terminal, and the corresponding connection status is in an unconnectable state. In this case, the in-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 short-range communication module of the in-vehicle terminal to adjust the connection status of the user terminal.

[0239] S1304.4: The user terminal receives a wake-up command sent by the vehicle-mounted terminal through the near-field communication module of the vehicle-mounted terminal.

[0240] S1304.5: In response to the wake-up command, the user terminal transmits a wireless connection request to the vehicle-mounted terminal to establish a communication connection to the vehicle-mounted terminal.

[0241] In this embodiment, the user terminal receives a wake-up command through a local short-range communication module (i.e., the short-range communication module of the user terminal) and then adjusts the connection status of the local short-range communication module to a connectable state. In this case, the user terminal can establish a communication connection to the in-vehicle terminal. Accordingly, the user terminal can send a wireless connection request to the in-vehicle terminal through the short-range communication module of the user terminal. After receiving the wireless connection request, the in-vehicle terminal can update the device information of the user terminal in a locally stored registered device list and can establish a communication connection to the user terminal.

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

[0243] S1305: The vehicle-mounted terminal obtains a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtains the configuration status of the second navigation transfer module.

[0244] In this embodiment, after establishing a communication connection to the user terminal, the in-vehicle terminal can determine whether a navigation application that supports navigation task synchronization is installed on the in-vehicle terminal. Navigation applications that support navigation task synchronization are recorded in a navigation synchronization application list. Therefore, after establishing a communication connection to the user terminal, the in-vehicle terminal can determine whether the navigation application list is empty. If the navigation application list is not empty, this indicates that the in-vehicle terminal supports navigation task synchronization operations. In this case, the in-vehicle terminal can obtain a configuration status corresponding to the second navigation transfer module.

[0245] In this embodiment, the navigation application installed in the in-vehicle terminal needs to support the navigation task synchronization operation. In addition, the user also needs to enable the navigation task synchronization service. In this case, the in-vehicle terminal needs to recognize the setting status corresponding to the second navigation transfer module. If the setting status of the second navigation transfer module is in the ON state, the in-vehicle terminal recognizes that the user has enabled the navigation task synchronization service and performs the operation of step S1306. In contrast, if the in-vehicle terminal recognizes that the second navigation transfer module is in the OFF state, it indicates that the user has not enabled the navigation task synchronization service. In this case, the in-vehicle terminal terminates the navigation task synchronization operation.

[0246] S1306: When the second navigation forwarding module is in an on state, the vehicle-mounted terminal sends a navigation forwarding notification to the user terminal, so that the user terminal sends navigation synchronization information.

[0247] In this embodiment, when the in-vehicle terminal detects that the second navigation transfer module is in an on state, the in-vehicle terminal may send a navigation transfer notification to the user terminal to initiate a navigation task synchronization procedure. For example, FIGS. 14(a) and 14(b) are schematic diagrams of an interface of an in-vehicle terminal according to an embodiment of the present application. After the in-vehicle terminal is started, if the in-vehicle terminal recognizes that the user terminal is in a connectable state, the in-vehicle terminal may directly establish a communication connection to the user terminal and display the current connection status on the interface. As shown in FIG. 14(a), the interface displays the terminal identifier of the user terminal connected to the in-vehicle terminal, e.g., "UserA," and the current connection status, e.g., "Connected." In this case, if a navigation application supporting navigation task synchronization is installed on the in-vehicle terminal and the navigation task synchronization service is enabled, a second navigation application locally installed on the in-vehicle terminal and supporting navigation task synchronization may be started. As shown in FIG. 14(b), the current synchronization progress, e.g., "Synchronizing with navigation task for UserA," is displayed.

[0248] In a possible implementation, when the same user account is logged in on the user terminal and the in-vehicle terminal, the communication connection established between the user terminal and the in-vehicle terminal is specifically a server-based communication connection, in other words, the user terminal and the in-vehicle terminal may exchange data based on the server.

[0249] For example, an example in which a navigation forwarding notification is transmitted between a user terminal and an in-vehicle terminal is used for explanation. FIG. 15 is a flowchart of third-party interaction between a user, an in-vehicle terminal, and a server according to an embodiment of the present application. As shown in FIG. 15, a user's user account is logged in on the in-vehicle terminal. When it is detected that the user terminal is in a connectable state (i.e., the same user account is logged in on the user terminal and the user account is in an online state), the in-vehicle terminal may send a navigation forwarding notification to the server. The navigation forwarding notification carries an account identifier of the logged-in user account on the in-vehicle terminal. After receiving the navigation forwarding notification, the server forwards the navigation forwarding notification to another terminal in which the same user account is logged in, i.e., the user terminal. It can be seen that the communication connection between the user terminal and the in-vehicle terminal may be a communication connection established based on the server.

[0250] Compared with Example 1, the user terminal in this embodiment specifically obtains navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission conditions are satisfied, and specifically includes steps S1307 and S1308.

[0251] S1307: The user terminal receives the navigation transfer notification sent by the in-vehicle terminal.

[0252] S1308: In response to the navigation transfer notification, the user terminal obtains navigation data from the first navigation application through the first navigation transfer module.

[0253] In this embodiment, after receiving the navigation transfer notification sent by the vehicle terminal, the user terminal triggers a navigation task synchronization procedure and obtains corresponding navigation data from the first navigation application through the first navigation transfer module. Of course, the user terminal may also perform a determination of prerequisites, such as whether the first navigation application has navigation task synchronization permission and whether the first navigation application is allowed to be in the foreground. If so, the first navigation transfer module may obtain navigation data from the first navigation application. For specific methods by which the first navigation transfer module obtains navigation data, please refer to the relevant description of step S201. Details will not be described again here.

[0254] S1309: The user terminal generates navigation synchronization information of the navigation data through the first navigation transfer module.

[0255] The implementation of step S1309 in this embodiment is completely the same as that of step S203 in Example 1, so for specific explanation, please refer to the relevant description of step S203, and the details will not be described again here.

[0256] S1310: The vehicle-mounted terminal receives the navigation synchronization information sent by the user terminal, and sends the navigation synchronization information to the second navigation application through the second navigation transfer module.

[0257] The implementation of step S1310 in this embodiment is completely the same as that of step S204 in Example 1, so for specific explanation, please refer to the relevant description of step S204, and the details will not be described again here.

[0258] S1311: The in-vehicle terminal updates the navigation task of the second navigation application based on the navigation synchronization information.

[0259] Step S1311 may include: the in-vehicle terminal determining a navigation destination based on the navigation synchronization information; generating task update prompt information based on the navigation destination; and updating the navigation task based on the navigation destination when an update confirmation command fed back is received based on the update prompt information.

[0260] After step S1310, the method may further include: the in-vehicle terminal sends navigation synchronization completion information to the user terminal through the second navigation transfer module, and the user terminal sends a termination command for the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, to stop the navigation task of the first navigation application.

[0261] In this embodiment of the present application, when a door opening event is detected from the vehicle, the user terminal can automatically synchronize the navigation task with the in-vehicle terminal so that the navigation task is continued from the user terminal to the in-vehicle terminal, thereby reducing user operations and improving navigation efficiency. [Example]

[0262] Compared with Example 1, the application scenario of this embodiment is specifically that after a vehicle is parked, the navigation task of the intelligent vehicle control terminal installed in the vehicle is synchronized with the user terminal carried by the user. Based on this, the first terminal is specifically an in-vehicle terminal, and the second terminal is a user terminal carried by the user. Figures 16A, 16B, 16C, and 16D are schematic diagrams of interactions in the navigation task synchronization method according to an embodiment of the present application. A specific description is as follows:

[0263] S1601: The in-vehicle terminal generates a navigation task for a first navigation application in response to a user's navigation operation, and generates navigation data based on the navigation task.

[0264] S1602: The in-vehicle terminal receives a service registration command sent by the first navigation application through the first navigation transfer module, which is used to authorize the first navigation application to transmit navigation data between devices.

[0265] S1603: In response to the service registration command, the in-vehicle terminal adds the first navigation application to the navigation synchronization application list and sets the first navigation transfer module to an ON state, which is when the cross-device transmission condition is satisfied. User It is used to transmit navigation synchronization information generated based on the first navigation application to the terminal.

[0266] The implementation of step S1601 is completely the same as that of step S200.1 in embodiment 1. The implementation of step S1602 is completely the same as that of step S200.2 in embodiment 1. The implementation of step S1603 is completely the same as that of step S200.3 in embodiment 1. For specific descriptions, please refer to the relevant descriptions of steps S2001.1 to S200.3. The details will not be described again here.

[0267] Compared with Example 1, the in-vehicle terminal in this embodiment specifically obtains navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied, including steps S1604 to S1606.

[0268] S1604: The in-vehicle terminal establishes a communication connection to the user terminal when the in-vehicle terminal detects a parking event related to the vehicle. The short-range communication connection is used to send navigation synchronization information to the user terminal.

[0269] In this embodiment, the in-vehicle terminal is the terminal executing the navigation task. If the navigation scenario is not switched, the in-vehicle terminal is always in a driving state. In this case, if the vehicle is parked, for example, if the driving speed is 0 and the vehicle angle is detected to be open, or if the vehicle stalls, or if the vehicle is turned off, it can be recognized that the user switches from a driving state to a walking state. In other words, the navigation scenario changes. The navigation task needs to be synchronized with another terminal, that is, a user terminal carried by the user. In this case, the in-vehicle terminal establishes communication with the user terminal.

[0270] Furthermore, in another embodiment of the present application, the in-vehicle terminal establishing a communication connection to the user terminal may specifically include the following steps:

[0271] S1604.1: The in-vehicle terminal recognizes the connection status of each registered terminal in the preset registered device list through the first navigation transfer module.

[0272] S1604.2: If the in-vehicle terminal recognizes that the user terminal is in the registered device list and the connection status of the user terminal is connectable, the in-vehicle terminal establishes a short-range communication connection to the user terminal based on connection information associated with the user terminal in the registered device list.

[0273] S1604.3: If the in-vehicle terminal recognizes that the user terminal is not in the registered device list, or that the user terminal is in the registered device list but the connection status of the user terminal is in an unconnectable state, the in-vehicle terminal sends a wake-up command to the user terminal through the near-field communication module of the in-vehicle terminal.

[0274] S1604.4: The user terminal sends a short-range connection request to the vehicle-mounted terminal in response to the wake-up command, so as to establish a short-range communication connection to the vehicle-mounted terminal.

[0275] Specifically, the implementation of steps S1604.1 to S1604.4 is completely the same as that of steps S1304.1 to S1304.5 in Example 3. For specific explanations, please refer to the relevant descriptions of steps S1304.1 to S1304.5. The details will not be described again here.

[0276] S1605: The vehicle-mounted terminal obtains a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtains the configuration status of the first navigation transfer module.

[0277] Specifically, the implementation of step S1605 is completely the same as that of step S1305 in the third embodiment. be For a specific explanation, see step S130 of 5 Please refer to the related description, and the details will not be repeated here.

[0278] S1606: When the in-vehicle terminal recognizes that the first navigation transfer module is in an on state, the in-vehicle terminal obtains navigation data from the first navigation application through the first navigation transfer module.

[0279] In this embodiment, if the in-vehicle terminal recognizes that the corresponding task synchronization service is enabled locally, then a navigation task activation procedure can be triggered. Because the in-vehicle terminal is the terminal executing the navigation task, the navigation task of the in-vehicle terminal needs to be synchronized with another device, i.e., the user terminal. In this case, the in-vehicle terminal can obtain the navigation task of the first navigation application through the local first navigation transfer module.

[0280] S1607: The vehicle-mounted terminal generates navigation synchronization information of the navigation data through the first navigation transfer module.

[0281] Specifically, the implementation of step S1607 is completely the same as that of step S202 in embodiment 1. For specific explanation, please refer to the relevant description of step S202. The details will not be described again here.

[0282] S1608: The user terminal receives the navigation synchronization information sent by the in-vehicle terminal, and sends the navigation synchronization information to the second navigation application through the second navigation transfer module.

[0283] Specifically, the implementation of step S1608 is completely the same as that of step S203 in embodiment 1. For specific explanations, please refer to the relevant description of step S203. The details will not be described again here.

[0284] Furthermore, in other embodiments of the present application, step S1608 may specifically include:

[0285] S1608.1: The user terminal caches the navigation synchronization information in a cache area through a second navigation transfer module, and detects a heartbeat signal of a communication connection to the vehicle-mounted terminal.

[0286] In this embodiment, after the in-vehicle terminal transmits the navigation synchronization information to the user terminal, the user terminal may not immediately perform the navigation task synchronization operation, but may first cache the navigation synchronization information in a cache area and detect a heartbeat signal between the user terminal and the vehicle terminal, which is used to maintain the activity of the short-range communication connection. In some scenarios, the user parks the vehicle and opens the door. In reality, the user only gets out of the vehicle to take a break and does not switch the navigation scenario. Therefore, the user terminal may detect the heartbeat signal to determine whether the user has gotten out of the vehicle, and then determine whether to update the local navigation task of the second navigation application.

[0287] A short-range communication connection is generally established between an in-vehicle terminal and a user terminal, and the short-range communication connection is generally maintained between the two short-range communication connections through a heartbeat signal. The heartbeat signal is generated at a preset time interval. The time interval is less than the subsequent valid time. Therefore, if the distance between the in-vehicle terminal and the user terminal is within a communication range, the two communicating parties continuously transmit a heartbeat signal at the preset time interval to maintain the short-range communication connection. The user terminal can detect the heartbeat signal to determine whether the user has left the vehicle.

[0288] S1608.2: If the heartbeat signal is not received within a preset valid time, the user terminal recognizes that the short-range communication connection to the in-vehicle terminal has been interrupted, and sends navigation synchronization information to the second navigation application.

[0289] In this embodiment, if the user terminal does not receive the heartbeat signal sent by the in-vehicle terminal within a preset valid time, it indicates that the user terminal has left the communication range of the in-vehicle terminal or the in-vehicle terminal has been closed, and it can be determined that the navigation task needs to be continued locally. Therefore, the obtained navigation synchronization information is 2 The navigation synchronization information can be transmitted to the second navigation application through the navigation transfer module, so that the second navigation application updates the navigation task based on the navigation synchronization information. The navigation can be continued for the user by the user terminal, so that the navigation can be continued from the in-vehicle terminal to the user terminal.

[0290] In this embodiment of the present application, the user terminal first caches the navigation synchronization information in the cache area, and then detects the heartbeat signal between the user terminal and the in-vehicle terminal. open Furthermore, based on whether the heartbeat signal is detected within a valid time, the user terminal can determine whether the user has left the vehicle, thereby improving the accuracy of navigation task synchronization and avoiding malfunctions.

[0291] S1609: The user terminal updates the navigation task of the second navigation application based on the navigation synchronization information.

[0292] Since the implementation of step S1609 in this embodiment is completely the same as that of step S204 in Example 1, for specific explanation, please refer to the relevant description of step S204. The details will not be described again here. It should be noted that before updating the navigation task, the user terminal may also generate corresponding prompt information, and update the navigation task after receiving the update confirmation command.

[0293] In this embodiment of the present application, the parking door initiated by the user open After detecting the event, the vehicle-mounted terminal triggers navigation task synchronization. In this way, the navigation task of the vehicle-mounted terminal can be automatically synchronized with the user terminal, so that the user does not need to set the navigation destination frequently, thereby improving the efficiency of navigation task synchronization. [Example]

[0294] Examples 1, 2, 3, and 4 describe the implementation procedure of the cross-device navigation data synchronization method provided herein from the perspective of interaction between a first terminal and a second terminal. Different from Examples 1 to 4, Example 5 describes the implementation procedure of the cross-device navigation data synchronization method provided herein from the starting point of a single side of the first terminal. Figure 17 is a flowchart of the implementation of the cross-device navigation data synchronization method performed by the first terminal according to an embodiment of the present application. A specific description is as follows:

[0295] S1701: If a preset cross-device transmission condition is satisfied, obtain navigation data from a first navigation application through a first navigation transfer module.

[0296] S1702: Generate navigation synchronization information corresponding to the navigation data through a first navigation transfer module.

[0297] S1703: Send navigation synchronization information to the second terminal, where the navigation synchronization information is used to update a navigation task of a second navigation application of the second terminal. After receiving the navigation synchronization information, the second terminal sends the received navigation synchronization information to the second navigation application through a second navigation transfer module, and updates the navigation task of the second navigation application based on the navigation synchronization information.

[0298] The implementation of step S1701 in this embodiment is completely the same as that of step S201 in Example 1. The implementation of step S1702 in this embodiment is completely the same as that of step S202 in Example 1. The implementation of step S1703 in this embodiment is completely the same as that of step S203 in Example 1. For specific descriptions, please refer to the relevant descriptions of steps S201 to S203. The details will not be described again here.

[0299] Optionally, obtaining navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied includes: receiving a communication label transmitted by a second short-range communication module of the second terminal in response to a touch operation by the second terminal; In response to the communicating label, activating a first navigation transfer module and obtaining navigation data from the first navigation application through the first navigation transfer module; Includes.

[0300] The implementation of the above two steps in this embodiment is completely the same as that of steps S1103 and S1104 in Example 2. For specific explanations, please refer to the relevant descriptions of steps S1103 and S1104. The details will not be described again here.

[0301] Optionally, the communication label is written to the second short-range communication module by the label service thread in response to the label write request when the second terminal detects that the label write condition is satisfied and sends the label write request to the label service thread through the second navigation forwarding module.

[0302] Optionally, obtaining navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied includes: Receiving a navigation transfer notification sent by a second terminal, where after the second terminal is connected to the first terminal, the navigation transfer notification is sent to the first terminal when it is detected that a second navigation transfer module of the second terminal is in an on state; obtaining navigation data from the first navigation application through the first navigation transfer module in response to the navigation transfer notification; Includes.

[0303] The implementation of the above two steps in this embodiment is completely the same as that of steps S1306 and S1307. For specific explanations, please refer to the relevant descriptions of steps S1306 and S1307. The details will not be described again here.

[0304] Optionally, before receiving the navigation transfer notification sent by the second terminal, receiving a wake-up command sent by the second terminal through a second short-range communication module; transmitting a wireless connection request to the second terminal in response to the wake-up command to establish a communication connection to the second terminal; may further be included.

[0305] The implementation of the above two steps in this embodiment is completely the same as that of steps S1304.4 and S1304.5 in Example 3. For specific explanations, please refer to the relevant descriptions of steps S1304.4 and S1304.5. The details will not be described again here.

[0306] Optionally, the first terminal is an intelligent vehicle control terminal mounted in a vehicle, and the second terminal is a user terminal carried by a user.

[0307] Correspondingly, obtaining navigation data from the first navigation application through the first navigation transfer module when the preset cross-device transmission condition is satisfied includes: establishing a near field communication connection to a second terminal when a parking event related to the vehicle is detected, the near field communication connection being used to transmit navigation synchronization information to the second terminal; When the first navigation transfer module is in an on state, obtaining navigation data from the first navigation application through the first navigation transfer module; Includes.

[0308] The implementation of the above two steps in this embodiment is completely the same as that of steps S1604 and S1605. For specific explanations, please refer to the relevant descriptions of steps S1604 and S1605. The details will not be described again here.

[0309] Optionally, establishing a near field communication connection to the second terminal upon detecting a parking event related to the vehicle includes: Recognizing, through a second navigation forwarding module, the connection status of each registered terminal in the preset registered device list; If the second terminal is in the registered device list and the connection status of the second terminal is connectable, establishing a near field communication connection to the second terminal based on connection information associated with the second terminal in the registered device list; or When the second terminal is not in the registered device list, or when the second terminal is in the registered device list but the connection status of the second terminal is in an unconnectable state, sending a wake-up command to the second terminal through the first short-range communication module, the wake-up command being used to enable the second terminal to establish a communication connection to the first terminal; Includes.

[0310] The implementation of the above two steps in this embodiment is completely the same as that of steps S1604.1 and S1604.4 in Example 4. For specific explanations, please refer to the relevant descriptions of steps S1604.1 and S1604.4. The details will not be described again here.

[0311] Correspondingly, when the preset cross-device transmission condition is satisfied, before obtaining navigation data from the first navigation application through the first navigation transfer module, generating a navigation task through the first navigation application in response to a user navigation operation, wherein navigation data is generated based on the navigation task; receiving, via a first navigation transfer module, a service registration command sent by a first navigation application, the service registration command being used to authorize the first navigation application to transmit navigation data between devices; In response to the service registration command, adding the first navigation application to a navigation synchronization application list and setting a first navigation transfer module to an on state, the on state being used to send navigation synchronization information generated based on the first navigation application to the second terminal when a cross-device transmission condition is satisfied; may further be included.

[0312] The implementation of the above three steps in this embodiment is completely the same as those of steps S2001 to S2003 in Example 1. For specific explanations, please refer to the relevant descriptions of steps S2001 to S2003. The details will not be described again here.

[0313] Optionally, after sending the navigation synchronization information to the second terminal, receiving navigation synchronization completion information fed back by the second terminal through a second navigation forwarding module; sending a termination command for the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, thereby stopping the navigation task of the first navigation application; may further be included.

[0314] The implementation of the above two steps in this embodiment is completely the same as that of steps S205 and S206 in Example 1. For specific explanations, please refer to the relevant descriptions of steps S205 and S206. The details will not be described again here.

[0315] Optionally, before sending the navigation synchronization information to the second terminal, Obtaining a navigation application list of the second terminal, the navigation application list including the second navigation application; If a navigation application matching the first navigation application exists in the navigation application list, sending navigation synchronization information to the second terminal, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application; may further be included.

[0316] The implementation of the above two steps in this embodiment is completely the same as that of steps S203.1 and S203.2 in Example 1. For specific explanations, please refer to the relevant descriptions of steps S203.1 and S203.2. The details will not be described again here.

[0317] In this embodiment, when the first terminal detects that the cross-device transmission condition is satisfied, the first terminal automatically obtains navigation data of the initiated navigation task from the first navigation application through a first navigation transfer module local to the first terminal, generates navigation synchronization information corresponding to the navigation data through the first navigation transfer module, and transmits the navigation synchronization information to the second terminal, thereby implementing cross-device navigation data transmission. After receiving the navigation synchronization information, the second terminal generates and transmits the navigation synchronization information to the second navigation application through a second navigation transfer module local to the first terminal. The second terminal can then update the navigation task of the second navigation application based on the navigation synchronization information, thereby implementing cross-device navigation task synchronization. Compared with existing navigation technologies, cross-device navigation task synchronization can be implemented in this application. In a scenario where cross-device navigation needs to be performed, the user does not need to set the task of the navigation application of the terminal multiple times. Instead, the navigation data can be automatically transferred through the navigation transfer module to update the navigation task of the navigation application, thereby significantly improving navigation task setting efficiency and reducing user repetitive operations. Furthermore, after obtaining navigation data from the first navigation application, the local first navigation transfer module of the first terminal does not directly send the navigation data to the second navigation transfer module of the second terminal, but converts the navigation data into corresponding navigation synchronization information. The navigation synchronization information can be transmitted between the navigation transfer modules of different terminals. The navigation synchronization information is then transmitted to the second navigation application through the second navigation transfer module. The navigation synchronization information is not directly transmitted between the navigation applications of the two terminals.Therefore, the same navigation application does not need to be installed on the first terminal and the second terminal. In this way, cross-device and cross-application navigation data transfer can be implemented, thereby further improving the coverage of navigation task synchronization. [Example]

[0318] Examples 1, 2, 3, and 4 describe the implementation procedure of the cross-device navigation data synchronization method provided herein from the perspective of interaction between a first terminal and a second terminal. Different from Examples 1 to 4, Example 6 describes the implementation procedure of the cross-device navigation data synchronization method provided herein from the starting point of a single side of the second terminal. Figure 18 is a flowchart of the implementation of the cross-device navigation data synchronization method performed by the second terminal according to an embodiment of the present application. A specific description is as follows:

[0319] S1801: Receive navigation synchronization information sent by a first terminal, where the navigation synchronization information is generated based on navigation data of a first navigation application of the first terminal.

[0320] S1802: Send navigation synchronization information to a second navigation application through a second navigation transfer module.

[0321] S1803: Update the navigation task of the second navigation application based on the navigation synchronization information.

[0322] The implementation of steps S1801 and S1802 in this embodiment is completely the same as that of step S203 in Example 1. The implementation of step S1803 is completely the same as that of step S204 in Example 1. For specific descriptions, please refer to the relevant descriptions of steps S203 and S204. The details will not be described again here.

[0323] Optionally, receiving the navigation synchronization information transmitted by the first terminal includes: In response to a touch operation by the first terminal, transmitting a communication label to the first terminal through the second short-range communication module, and causing the first terminal to activate a first navigation transfer module in response to the communication label and obtain navigation data from the first navigation application through the first navigation transfer module.

[0324] The implementation of the above steps in this embodiment is completely the same as that of step S1103 in Example 2. For specific explanations, please refer to the relevant description of step S1103. The details will not be described again here.

[0325] The navigation synchronization information sent by the first terminal through the first navigation transfer module is received.

[0326] The implementation of the above steps in this embodiment is completely the same as that of step S1110 in Example 2. For specific explanations, please refer to the relevant description of step S1110. The details will not be described again here.

[0327] Optionally, before transmitting the communication label to the first terminal through the second short-range communication module in response to the touch operation by the first terminal, sending a label write request to a label service thread through a second navigation forwarding module when a preset label write condition is satisfied; Responding to a label write request through a label service thread and writing the communication label to the second short-range communication module; Further included are:

[0328] The implementation of the above two steps in this embodiment is completely the same as that of steps S1101 and S1102 in Example 2. For specific explanations, please refer to the relevant descriptions of steps S1101 and S1102. The details will not be described again here.

[0329] Optionally, the second terminal is an intelligent vehicle control terminal mounted in the vehicle.

[0330] Accordingly, before receiving the navigation synchronization information sent by the first terminal, establishing a communication connection to the first terminal when a door opening event related to the vehicle is detected; Obtaining a navigation synchronization application list, and when the navigation synchronization application list is not empty, obtaining a configuration status of a second navigation transfer module; When the second navigation transfer module is in an on state, sending a navigation transfer notification to the first terminal to cause the first terminal to send navigation synchronization information; Further included are:

[0331] The implementation of the above three steps in this embodiment is completely the same as those of steps S1304 to S1306 in Example 3. For specific explanations, please refer to the relevant descriptions of steps S1304 to S1306. The details will not be described again here.

[0332] Optionally, establishing a communication connection to the first terminal when a door opening event related to the vehicle is detected includes: Recognizing, through a second navigation forwarding module, the connection status of each registered terminal in the preset registered device list; If the first terminal is in the registered device list and the connection status of the first terminal is connectable, establishing a communication connection to the first terminal based on connection information associated with the first terminal in the registered device list; or When the first terminal is not in the registered device list, or when the first terminal is in the registered device list but the connection status of the first terminal is in an unconnectable state, sending a wake-up command to the first terminal through the second short-range communication module, the wake-up command being used to enable the first terminal to establish a short-range communication connection to the second terminal; Includes.

[0333] The implementation of the above three steps in this embodiment is completely the same as those of steps S1304.1 to S1304.3 in Example 3. For specific explanations, see step S1304. .1 From S130 4.3 Please refer to the relevant explanation in the previous section, and the details will not be repeated here.

[0334] Optionally, the second terminal is a user terminal carried by a user, and the first terminal is an intelligent vehicle control terminal mounted in a vehicle.

[0335] Accordingly, transmitting the navigation synchronization information to the second navigation application through the second navigation forwarding module includes: Caching navigation data in a cache area through a second navigation transfer module, and detecting a heartbeat signal of a communication connection to the first terminal; If the heartbeat signal is not received within a preset valid time, the short-range communication connection to the first terminal is recognized as being lost, and navigation synchronization information is sent to the second navigation application. Includes.

[0336] The implementation of the above two steps in this embodiment is completely the same as that of steps S1608.1 and S1608.2 in Example 4. For specific explanations, please refer to the relevant descriptions of steps S1608.1 and S1608.2. The details will not be described again here.

[0337] Optionally, after receiving the navigation synchronization information sent by the first terminal, detecting whether a navigation application matching the first navigation application exists in a navigation application list, the navigation application list including the first navigation application; If a navigation application matching the first navigation application exists in the navigation application list, use the navigation application matching the first navigation application as a second navigation application, and perform an operation of sending navigation synchronization information to the second navigation application through a second navigation transfer module, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application; Further included are:

[0338] The implementation of the above two steps in this embodiment is completely the same as that of steps S203.1 and S203.2 in Example 1. For specific explanations, please refer to the relevant descriptions of steps S203.1 and S203.2. The details will not be described again here.

[0339] Optionally, updating 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; updating the navigation task based on the navigation destination when an update confirmation command is received that is fed back based on the update prompt information; Includes.

[0340] The implementation of the above two steps in this embodiment is completely the same as that of steps S204.1 and S204.2 in Example 1. For specific explanations, please refer to the relevant descriptions of steps S204.1 and S204.2. The details will not be described again here.

[0341] Optionally, updating the navigation task based on the navigation destination when an update confirmation instruction fed back based on the update prompt information is received includes: The method includes sending navigation synchronization completion information to the first terminal, and the first terminal sending an end command regarding the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, so as to stop the navigation task of the first navigation application.

[0342] The implementation of the above two steps in this embodiment is completely the same as that of step S205 in Example 1. For specific explanations, please refer to the relevant description of step S205. The details will not be described again here. [Example]

[0343] Corresponding to the cross-device navigation task synchronization method described in Example 5, Figure 19 is a block diagram of the structure of a cross-device navigation task synchronization device according to an embodiment of the present application. For simplicity of description, only parts relevant to this embodiment of the present application are shown.

[0344] Referring to FIG. 19, the cross-device navigation task synchronizer a navigation data obtaining unit 191 configured to obtain navigation data from the first navigation application through the first navigation transfer module when a preset cross-device transmission condition is satisfied; a navigation synchronization information generating unit 192 configured to generate, through the first navigation transfer module, navigation synchronization information corresponding to the navigation data; a navigation synchronization information sending unit 193 configured to send navigation synchronization information to the second terminal, the navigation synchronization information being used to update a navigation task of a second navigation application of the second terminal; Includes.

[0345] Optionally, the navigation data acquisition unit 191 comprises: a communication label receiving unit configured to receive a communication label transmitted by a second short-range communication module of the second terminal in response to a touch operation by the second terminal, the communication label carrying a navigation task synchronization start identifier; and a navigation transfer module activation unit configured to activate the first navigation transfer module in response to the communicating label and obtain navigation data from the first navigation application through the first navigation transfer module; Includes.

[0346] Optionally, when the second terminal detects that the label writing condition is satisfied, the second terminal sends a label writing request to the label service thread through the second navigation forwarding module, responds to the label writing request through the label service thread, adds a start identifier to the communication label, and writes the communication label to the second short-range communication module, after which the communication label is obtained.

[0347] Optionally, the navigation data acquisition unit 191 comprises: a navigation forwarding notification receiving unit configured to receive a navigation forwarding notification sent by a second terminal, where after the second terminal is connected to the first terminal, the navigation forwarding notification is sent to the first terminal when it is detected that a second navigation forwarding module of the second terminal is in an on state; and a navigation transfer notification response unit configured to retrieve navigation data from the first navigation application through the first navigation transfer module in response to the navigation transfer notification; Includes.

[0348] Optionally, the navigation task synchronizer comprises: a wake-up command receiving unit configured to receive a wake-up command sent by the second terminal through the second short-range communication module; a wake-up command response unit configured to send a wireless connection request to the second terminal in response to the wake-up command so as to establish a communication connection to the second terminal; Further includes:

[0349] Optionally, the first terminal is an intelligent vehicle control terminal mounted in a vehicle, and the second terminal is a user terminal carried by a user.

[0350] Accordingly, the navigation data acquisition unit 191 a parking door opening trigger unit configured to establish a short-range communication connection to a second terminal when a parking event related to the vehicle is detected, the short-range communication connection being used to transmit navigation synchronization information to the second terminal; and a first status recognition unit configured to obtain a navigation synchronization application list, and, if the navigation synchronization application list is not empty, obtain a configuration status of the first navigation transfer module; a first start state response unit configured to obtain navigation data from the first navigation application through the first navigation transfer module when the first navigation transfer module is in an on state; Includes.

[0351] Optionally, the parking door opening trigger unit comprises: a connection status detection unit configured to recognize, through the second navigation forwarding module, the connection status of each registered terminal in the preset registered device list; a direct connection trigger unit configured to establish a close-range communication connection to the second terminal based on connection information associated with the second terminal in the registered device list when the second terminal is in the registered device list and a connection status of the second terminal is connectable; a wake-up command sending unit configured to send a wake-up command to the second terminal through the first short-range communication module when the second terminal is not in the registered device list or when the second terminal is in the registered device list but the connection status of the second terminal is in an unconnectable state, the wake-up command being used to enable the second terminal to establish a communication connection to the first terminal; Includes.

[0352] Optionally, the navigation task synchronizer comprises: a navigation operation response unit configured to generate a navigation task through a first navigation application in response to a user's navigation operation, the navigation data being generated based on the navigation task; and a service registration unit configured to receive a service registration command sent by the first navigation application through the first navigation transfer module, the service registration command being used to authorize the first navigation application to have permission to transmit navigation data between devices; a service registration response unit configured to add the first navigation application to a navigation synchronization application list and set a first navigation transfer module to an ON state in response to the service registration command, the ON state being used to transmit navigation synchronization information generated based on the first navigation application to the second terminal when a cross-device transmission condition is satisfied; and Further includes:

[0353] Optionally, the navigation task synchronizer comprises: a navigation synchronization completion information receiving unit configured to receive navigation synchronization completion information fed back by the second terminal through the second navigation forwarding module; a navigation termination unit configured to send a termination command for the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, thereby stopping the navigation task of the first navigation application; Further includes:

[0354] Optionally, the navigation task synchronizer comprises: a navigation application list obtaining unit configured to obtain a navigation application list of the second terminal, the navigation application list including the second navigation application; and a navigation application matching unit configured to send navigation synchronization information to the second terminal when a navigation application matching the first navigation application exists in the navigation application list, where the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application; and Further includes:

[0355] Therefore, when the first terminal detects that the cross-device transmission condition is satisfied, the cross-device navigation task synchronization device provided in this embodiment of the present application automatically obtains navigation data of the initiated navigation task from the first navigation application through a local first navigation transfer module of the first terminal, generates navigation synchronization information corresponding to the navigation data through the first navigation transfer module, and transmits the navigation synchronization information to the second terminal, thereby implementing cross-device navigation data transmission. After receiving the navigation synchronization information, the second terminal generates and transmits the navigation synchronization information to the second navigation application through a local second navigation transfer module. The second terminal can then update the navigation task of the second navigation application based on the navigation synchronization information, thereby implementing cross-device navigation task synchronization. Compared with existing navigation technologies, cross-device navigation task synchronization can be implemented in the present application. In a scenario where cross-device navigation needs to be performed, the user does not need to set the task of the navigation application of the terminal multiple times. Instead, the navigation data can be automatically transferred through the navigation transfer module to update the navigation task of the navigation application, thereby significantly improving navigation task setting efficiency and reducing user repetitive operations. Furthermore, after obtaining navigation data from the first navigation application, the local first navigation transfer module of the first terminal does not directly send the navigation data to the second navigation transfer module of the second terminal, but converts the navigation data into corresponding navigation synchronization information. The navigation synchronization information can be transmitted between the navigation transfer modules of different terminals. The navigation synchronization information is then transmitted to the second navigation application through the second navigation transfer module. The navigation synchronization information is not directly transmitted between the navigation applications of the two terminals.Therefore, the same navigation application does not need to be installed on the first terminal and the second terminal. In this way, cross-device and cross-application navigation data transfer can be implemented, thereby further improving the coverage of navigation task synchronization. [Example]

[0356] Example 6 20 is a block diagram of the structure of a cross-device navigation task synchronization apparatus according to an embodiment of the present application, corresponding to the cross-device navigation task synchronization method described in

[0044] For simplicity of description, only parts relevant to this embodiment of the present application are shown.

[0357] Referring to FIG. 20, the cross-device navigation task synchronizer a navigation synchronization information receiving unit 201 configured to receive navigation synchronization information sent by a first terminal, where the navigation synchronization information is generated based on navigation data of a first navigation application of the first terminal; and a navigation synchronization information sending unit 202 configured to send navigation synchronization information to a second navigation application through a second navigation transfer module; a navigation task updating unit 203 configured to update the navigation task of the second navigation application based on the navigation synchronization information; Includes.

[0358] Optionally, the navigation synchronization information receiving unit 201 comprises: a communication label sending unit configured to, in response to a touch operation by the first terminal, send a communication label to the first terminal through the second short-range communication module, so that the first terminal, in response to the communication label, activates a first navigation transfer module and obtains navigation data from the first navigation application through the first navigation transfer module, wherein the communication label carries a navigation task synchronization start identifier; and a touch operation feedback unit configured to receive navigation synchronization information sent by the first terminal through the first navigation transfer module; Includes.

[0359] Optionally, the navigation task synchronizer comprises: a label write request unit configured to send a label write request to a label service thread through a second navigation forwarding module when a preset label write condition is satisfied; a communication label writing unit configured to respond to a label writing request through a label service thread, add an initiation identifier to a communication label, and write the communication label to a second short-range communication module; Further includes:

[0360] Optionally, the second terminal is an intelligent vehicle control terminal mounted in the vehicle.

[0361] Accordingly, the navigation task synchronizer a door-opening event trigger unit configured to establish a communication connection to the first terminal when a door-opening event related to the vehicle is detected; a second status recognition unit configured to obtain a navigation synchronization application list, and, when the navigation synchronization application list is not empty, obtain a setting status of the second navigation forwarding module; a second wake-up status response unit configured to, when the second navigation forwarding module is in an on state, send a navigation forwarding notification to the first terminal to cause the first terminal to send navigation synchronization information; Further includes:

[0362] Optionally, the door open event trigger unit comprises: a connection status determining unit configured to recognize, through the second navigation forwarding module, a connection status of each registered terminal in the preset registered device list; a direct connection sending unit configured to establish a communication connection to the first terminal based on connection information associated with the first terminal in the registered device list, when the first terminal is in the registered device list and a connection status of the first terminal is connectable; a wake-up execution unit configured to send a wake-up command to the first terminal through the second short-range communication module when the first terminal is not in the registered device list or when the first terminal is in the registered device list but the connection status of the first terminal is in an unconnectable state, the wake-up command being used to enable the first terminal to establish a short-range communication connection to the second terminal; and Includes.

[0363] Optionally, the second terminal is a user terminal carried by a user, and the first terminal is an intelligent vehicle control terminal mounted in a vehicle.

[0364] Correspondingly, the navigation synchronization information sending unit 202: an information caching unit configured to cache navigation data in a cache area through a second navigation transfer module and detect a heartbeat signal of a communication connection to the first terminal; a heartbeat signal listening unit configured to recognize that a short-range communication connection to the first terminal has been lost if the heartbeat signal is not received within a preset valid time period, and to send navigation synchronization information to the second navigation application; Includes.

[0365] Optionally, the navigation task synchronizer comprises: a matching application detection unit configured to detect whether a navigation application matching the first navigation application exists in a navigation application list, the navigation application list including the first navigation application; and a second navigation application recognition unit configured to perform an operation of using the navigation application matching the first navigation application as a second navigation application and sending navigation synchronization information to the second navigation application through a second navigation transfer module when a navigation application matching the first navigation application exists in the navigation application list, wherein the navigation application matching the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application; Further includes:

[0366] Optionally, the navigation task update unit 203: 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; an update confirmation command response unit configured to update the navigation task based on the navigation destination when an update confirmation command fed back based on the update prompt information is received; Includes.

[0367] Optionally, the navigation task synchronizer comprises: The communication device further includes a navigation synchronization completion information sending unit configured to send navigation synchronization completion information to the first terminal, so that the first terminal sends an end command regarding the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information, thereby stopping the navigation task of the first navigation application.

[0368] The cross-device navigation task synchronization method provided in this embodiment of the present application may be applied to terminal devices such as mobile phones, tablet computers, wearable devices, in-vehicle terminals, augmented reality (AR) devices / virtual reality (VR) devices, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, or personal digital assistants (PDAs), etc. The specific types of terminal devices are not limited by the embodiments of the present application.

[0369] For example, the terminal device may be a base station (STATION, ST) in a WLAN, or may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (STP) telephone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device, other processing device connected to a wireless modem, a computer, a laptop computer, a handheld communication device or handheld computing device, and / or other devices used for communication in wireless systems and next generation communication systems, such as a mobile terminal of a 5G network or a mobile terminal of a future evolved Public Land Mobile Network (PLMN) network.

[0370] FIG. 21 is a schematic diagram of the structure of the terminal device 100. As shown in FIG.

[0371] 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 loudspeaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identity module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, an optical proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

[0372] It is understood that the structure depicted in this embodiment of the present application does not constitute a specific limitation on the terminal device 100. In some other embodiments of the present application, the terminal device 100 may include more or fewer components than shown in the figure, combine some components, separate some components, or have a different component arrangement. The components shown may be implemented by hardware, software, or a combination of software and hardware.

[0373] Processor 110 may include one or more processing units. For example, processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, a neural network processing unit (NPU), etc. Different processing units may be separate components or may be integrated into one or more processors.

[0374] The controller may generate operation control signals based on the instruction operation code and the time sequence signal to complete the control of instruction fetching and instruction execution.

[0375] A memory may also be located in the processor 110 and configured to store instructions and data. In some embodiments, the memory in the processor 110 is a cache. The memory may store instructions or data that are currently being used or are used periodically by the processor 110. When the processor 110 needs to use the instructions or data again, the processor 110 may retrieve the instructions or data directly from the memory. This avoids repeated accesses, reduces the latency of the processor 110, and improves system efficiency.

[0376] In some embodiments, processor 110 may include one or more interfaces, which 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, a universal serial bus (USB) interface, etc.

[0377] The I2C interface is a bidirectional synchronous serial bus and includes one serial data line (SDA) and one serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be separately coupled to the touch sensor 180K, a charger, a flash, the camera 193, etc. through different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K through an I2C interface, whereby the processor 110 communicates with the touch sensor 180K through the I2C bus interface to implement touch functions of the terminal device 100.

[0378] The I2S interface may be configured to perform audio communication. In some embodiments, processor 110 may include multiple groups of I2S buses. Processor 110 may be coupled to audio module 170 through the I2S bus to perform communication between processor 110 and audio module 170. In some embodiments, audio module 170 may send audio signals to wireless communication module 160 through the I2S interface to perform a function of answering an incoming call via a Bluetooth headset.

[0379] The PCM interface may also be configured to perform audio communications and to sample, quantize, and encode analog signals. In some embodiments, audio module 170 may be coupled to wireless communication module 160 through a PCM bus interface. In some embodiments, audio module 170 may also send audio signals to wireless communication module 160 through the PCM interface to perform functions such as answering an incoming call via a Bluetooth headset. Both the I2S interface and the PCM interface may be configured to perform audio communications.

[0380] The UART interface is a universal serial data bus configured to perform asynchronous communication. The bus may be a bidirectional communication bus. The bus converts data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is generally configured to connect the processor 110 to the wireless communication module 160. For example, the processor 110 communicates with a Bluetooth module of the wireless communication module 160 through the UART interface to implement a Bluetooth headset function. In some embodiments, the audio module 170 may send audio signals to the wireless communication module 160 through the UART interface to implement a function for playing music through a Bluetooth headset.

[0381] The MIPI interface may be configured to connect the processor 110 to peripheral components such as a display 194 or a camera 193. MIPI interfaces include a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 communicates with the camera 193 through the CSI interface to implement a photo-taking function of the terminal device 100. The processor 110 communicates with the display 194 through the DSI interface to implement a display function of the terminal device 100.

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

[0383] The USB interface 130 is an interface conforming to the USB standard, and may specifically be a miniUSB interface, a microUSB interface, a USB type C interface, etc. The USB interface 130 may be configured to connect to a charger to charge the terminal device 100, to transmit data between the terminal device 100 and a peripheral device, or to connect to a headset to play audio through the headset. Alternatively, the interface may be configured to connect to another terminal device, for example, an AR device.

[0384] It can be understood that the interface connection relationships between modules shown in this embodiment of the present application are merely examples for explanation and do not constitute limitations on the structure of the terminal device 100. In some other embodiments of the present application, the terminal device 100 may alternatively use different interface connection methods or a combination of multiple interface connection methods of the above embodiments.

[0385] The charging management module 140 is configured to receive a 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 the charging input of the wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive the wireless charging input through a wireless charging coil of the terminal device 100. When charging the battery 142, the charging management module 140 may further supply power to the terminal device by using the power management module 141.

[0386] Power management module 141 is configured to connect to battery 142, charging management module 140, and processor 110. Power management module 141 receives input from battery 142 and / or charging management module 140 and provides power to processor 110, internal memory 121, display 194, camera 193, wireless communication module 160, etc. Power management module 141 may be further configured to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage and impedance). In some other embodiments, power management module 141 may alternatively be located in processor 110. In some other embodiments, power management module 141 and charging management module 140 may alternatively be located in the same device.

[0387] The wireless communication functions of the terminal device 100 may be implemented by using antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, baseband processor, etc.

[0388] Antenna 1 and Antenna 2 are configured to transmit and receive electromagnetic signals. Each antenna of terminal device 100 may be configured to cover one or more communication frequency bands. Different antennas may be further multiplexed to increase antenna utilization. For example, Antenna 1 may be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, antennas may be used in combination with tuning switches.

[0389] Mobile communication module 150 may provide a wireless communication solution applicable to terminal device 100, including 2G / 3G / 4G / 5G, etc. Mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. Mobile communication module 150 may receive electromagnetic waves via antenna 1, perform processing such as filtering or amplification on the received electromagnetic waves, and send the electromagnetic waves to a modem processor for demodulation. Mobile communication module 150 may further amplify signals modulated by the modem processor and convert the signals into electromagnetic waves for emission by antenna 1. In some embodiments, at least some functional modules of mobile communication module 150 may be located in processor 110. In some embodiments, at least some functional modules of mobile communication module 150 may be located in the same device as at least some modules of processor 110.

[0390] The modem processor may include a modulator and a demodulator. The modulator is configured to modulate a frequency baseband signal to be transmitted into a mid- to high-frequency signal. The demodulator is configured to demodulate a received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then sends the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal is processed by the baseband processor and then sent to the application processor. The application processor outputs an acoustic signal through an audio device (such as, but not limited to, loudspeaker 170A, receiver 170B, etc.) or an image or video through display 194. In some embodiments, the modem processor may be an independent component. In some other embodiments, the modem processor may be separate from processor 110 and located in the same device as mobile communication module 150 or other functional modules.

[0391] The wireless communication module 160 may be applied to the terminal device 100 to provide wireless communication solutions including wireless local area networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (GNSS), frequency modulation (FM), near field communication (NFC) technology, infrared (IR) technology, and the like. The wireless communication module 160 may be one or more components incorporating at least one communication processing module. The wireless communication module 160 receives electromagnetic signals through the antenna 2, performs frequency modulation and filtering on the electromagnetic signals, and sends the processed signals to the processor 110. The wireless communication module 160 may further receive signals to be transmitted from the processor 110, perform frequency modulation and amplification on the signals, and convert the signals into electromagnetic signals for emission by the antenna 2.

[0392] In some embodiments, antenna 1 of terminal device 100 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160, thereby enabling terminal device 100 to communicate with networks and other devices by using wireless communication technologies that 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, IR technologies, etc. GNSS may include the global positioning system (GPS), the global navigation satellite system (GLONASS), the BeiDou navigation satellite system (BDS), the quasi-zenith satellite system (QZSS), and / or the satellite-based augmentation system (SBAS).

[0393] The terminal device 100 implements display functions through a GPU, a display 194, an application processor, etc. The GPU is a microprocessor for image processing and is connected to the display 194 and the application processor. The GPU is configured to perform mathematical and geometric calculations and render images. The processor 110 may include one or more GPUs that execute program instructions to generate or modify display information. The display 194 can specifically display the generated detection report, allowing a user to view the detection report by using the display 194.

[0394] The display 194 is configured to display images, videos, etc. The display 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini-LED, a micro-LED, a micro-OLED, a quantum-dot light-emitting diode (QLED), etc. In some embodiments, the terminal device 100 may include one or N displays 194, where N is a positive integer greater than 1. The display 194 may include a touch panel and other input devices.

[0395] The terminal device 100 may implement a photography function using an ISP, a camera 193, a video codec, a GPU, a display 194, an application processor, and the like.

[0396] The ISP is configured to process data fed back by the camera 193. For example, during photography, the shutter is pressed, light travels through the lens to the camera's photosensitive elements, the light signal is converted into an electrical signal, and the camera's photosensitive elements transmit the electromagnetic signal to the ISP for processing, converting the electrical signal into a visible image. The ISP may also perform algorithmic optimization for image noise, brightness, and complexion. The ISP may also optimize parameters such as exposure and color temperature for the photography scenario. In some embodiments, the ISP may be located in the camera 193.

[0397] The camera 193 is configured to capture still images or video. An optical image of an object is generated by a lens and projected onto a photosensitive element. The photosensitive element may 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, which is then transmitted to an ISP, which converts the electrical signal into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into an image signal in a standard format, such as RGB or YUV. In some embodiments, the terminal device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0398] The digital signal processor is configured to process digital signals and may process other digital signals in addition to digital image signals. For example, when the terminal device 100 selects a frequency, the digital signal processor is configured to perform a Fourier transform on the frequency energy.

[0399] A video codec is configured to compress or decompress digital video. The terminal device 100 may support one or more video codecs. In this manner, the terminal device 100 may play or record video in multiple coding formats, such as Moving Picture Experts Group (MPEG)-1, MPEG-2, MPEG-3, and MPEG-4.

[0400] The NPU is a neural network (NN) computing processor that can process input information at high speed by referencing the structure of biological neural networks, such as the communication patterns between neurons in the human brain, and can also continuously self-learn. The NPU can implement intelligent cognition applications for the terminal device 100, such as image recognition, face recognition, speech recognition, and text understanding.

[0401] The external memory interface 120 may be configured to connect to an external memory card, such as a microSD card, to expand the storage capacity of the terminal device. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, music and video files may be stored on the external memory card.

[0402] The internal memory 121 may be configured to store computer-executable program code. The executable program code includes instructions. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store an operating system, applications required by at least one function (e.g., a sound playback function and an image playback function), etc. The data storage area may store data generated in the process of using the terminal device 100 (e.g., audio data or a photo book). Furthermore, the internal memory 121 may include high-speed random access memory and may further include non-volatile memory, such as at least one magnetic disk storage device, flash storage device, universal flash storage (UFS), etc. The processor 110 executes instructions stored in the internal memory 121 and / or instructions stored in a memory located in the processor to perform various functional applications and data processing of the terminal device 100.

[0403] The terminal device 100 may perform audio functions, such as playing or recording music, through an audio module 170, a loudspeaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, an application processor, and the like.

[0404] Audio module 170 is configured to convert digital audio information into analog audio signals for output, and to convert analog audio signals into digital audio signals. Audio module 170 may further be configured to encode and decode audio signals. In some embodiments, audio module 170 may be located in processor 110, or some functional modules of audio module 170 may be located in processor 110.

[0405] The loudspeaker 170A, also referred to as a "speaker," is configured to convert audio electrical signals into acoustic signals. The terminal device 100 can be used to answer hands-free calls or listen to music through the loudspeaker 170A. In particular, the loudspeaker 170A can be configured to output prompt information to notify the user of parts that need to be touched on the electronic scale.

[0406] The receiver 170B, also called an "earphone," is configured to convert an electrical audio signal into an acoustic signal. When using the terminal device 100 to make a call or receive voice information, the receiver 170B may be placed near a person's ear to hear the sound.

[0407] The microphone 170C, also referred to as a "microphone," is configured to convert acoustic signals into electrical signals. When making a call or sending a voice message, a user may make a sound with their mouth near the microphone 170C to input an acoustic signal into the microphone 170C2. At least one microphone 170C may be disposed in the terminal device 100. In some other embodiments, two microphones 170C may be disposed in the terminal device 100 to collect acoustic signals and further implement a noise reduction function. In some other embodiments, three, four, or more microphones 170C may alternatively be disposed in the terminal device 100 to collect acoustic signals, implement noise reduction, recognize sound sources, implement directional recording functions, and the like.

[0408] The headset jack 170D is configured to connect to a preferred headset and may be a USB interface 130, or may be a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0409] The pressure sensor 180A is configured to detect a pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display 194. For example, the terminal device may acquire the user's weight using the pressure sensor 180A. There are several types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates having a conductive material. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The terminal device 100 determines the strength of the pressure based on the change in capacitance. When a touch operation is performed on the display 194, the terminal device 100 detects the strength of the touch operation using the pressure sensor 180A. The terminal device 100 may further calculate the touch position based on the detection signal from the pressure sensor 180A. In some embodiments, touch operations performed on the same touch position but with different touch operation strengths may correspond to different operation commands. For example, if a touch operation is performed on the SMS message application icon with a touch strength less than the first pressure threshold, a command to view an SMS message is executed, or if a touch operation is performed on the SMS message application icon with a touch strength equal to or greater than the first pressure threshold, a command to create a new SMS message is executed.

[0410] The gyro sensor 180B may be configured to determine the motion attitude of the terminal device 100. In some embodiments, the angular velocity of the terminal device 100 around three axes (i.e., the x-axis, the y-axis, and the z-axis) may be determined by using the gyro sensor 180B. The gyro sensor 180B may be configured to implement image stabilization during photography. For example, when the shutter is pressed, the gyro sensor 180B detects the angle at which the terminal device 100 shakes, and calculates the distance that the lens module needs to compensate based on the angle, allowing the lens to offset the shaking of the terminal device 100 with an opposite movement to implement image stabilization. The gyro sensor 180B may also be used in navigation scenarios and motion-sensing game scenarios.

[0411] The barometric pressure sensor 180C is configured to measure barometric pressure. In some embodiments, the terminal device 100 calculates altitude based on the barometric pressure values ​​measured by the barometric pressure sensor 180C to assist in positioning and navigation.

[0412] The magnetic sensor 180D includes a Hall sensor. The terminal device 100 detects the opening and closing of the flip cover and the leather case by the magnetic sensor 180D. In some embodiments, when the terminal device 100 is a flip phone, the terminal device 100 may detect the opening and closing of the flip cover by the magnetic sensor 180D. Furthermore, functions such as automatic unlocking of the flip card are set based on the detected opening and closing state of the flip cover or the detected opening and closing state of the leather case.

[0413] The acceleration sensor 180E can detect acceleration in various directions (usually on three axes) of the terminal device 100. The magnitude and direction of weight can be detected when the terminal device 100 is stationary. The acceleration sensor 180E may be further configured to recognize the orientation of the terminal device, and is used for applications such as switching between landscape and portrait orientations or as a pedometer.

[0414] The distance sensor 180F is configured to measure distance. The terminal device 100 may measure distance by using infrared light or a laser. In some embodiments, in a photography scenario, the terminal device 100 may measure distance by using the distance sensor 180F to implement high-speed focusing.

[0415] The optical proximity sensor 180G may include, for example, a light-emitting diode (LED) and a photodetector, such as a photodiode. The light-emitting diode may be an infrared light-emitting diode. The terminal device 100 emits infrared light outward using the light-emitting diode. The terminal device 100 detects infrared light reflected from a nearby object using the photodiode. When sufficient reflected light is detected, the terminal device 100 may determine that an object is present near the terminal device 100. When insufficient reflected light is detected, the terminal device 100 may determine that no object is present near the terminal device 100. The optical proximity sensor 180G allows the terminal device 100 to detect when a user is holding the terminal device 100 near their ear for a call and automatically turn off the screen to save power. The optical proximity sensor 180G may also be used in leather case mode or pocket mode to automatically lock or unlock the screen.

[0416] The ambient light sensor 180L is configured to detect ambient light intensity. The terminal device 100 may adaptively adjust the brightness of the display 194 based on the detected ambient light intensity. The ambient light sensor 180L may also be configured to automatically adjust white balance during photography. The ambient light sensor 180L may further cooperate with the optical proximity sensor 180G to detect whether the terminal device 100 is in a packet to prevent accidental touches.

[0417] The fingerprint sensor 180H is configured to collect fingerprints, and the terminal device 100 may use the collected fingerprint characteristics to implement fingerprint-based unlocking, application lock access, fingerprint-based photo taking, fingerprint-based call answering, etc.

[0418] The temperature sensor 180J is configured to detect temperature. In some embodiments, the terminal device 100 executes a temperature handling policy based on the temperature detected by the temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the terminal device 100 reduces the performance of a processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In some other embodiments, when the temperature is lower than a temperature-type threshold, the terminal device 100 heats the battery 142 to avoid an abnormal shutdown of the terminal device 100 caused by a low temperature. In some other embodiments, when the temperature is lower than yet another threshold, the terminal device 100 boosts the output voltage of the battery 142 to avoid an abnormal shutdown caused by a low temperature.

[0419] The touch sensor 180K is also referred to as a "touch component." The touch sensor 180K may be disposed on the display 194, whereby the touch sensor 180K and the display 194 constitute a touch screen, also referred to as a "touch control screen." The touch sensor 180K is configured to detect touch operations on or near the touch screen. The touch sensor may forward the detected touch operations to an application processor to determine a touch event type. A visual output related to the touch operation may be provided using the display 194. In some other embodiments, the touch sensor 180K may alternatively be disposed on the surface of the terminal device 100 at a location different from the location of the display 194.

[0420] The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, the bone conduction sensor 180M may acquire a vibration signal of the vibrating bones of the human vocal cords. The bone conduction sensor 180M may also be in contact with the human pulse to receive a blood pressure pulsation signal. In some embodiments, the bone conduction sensor 180M may alternatively be disposed in a headset to acquire a bone conduction headset. The audio module 170 may implement a voice function by parsing an audio signal based on the vibration signal of the vibrating bones of the vocal cords acquired by the bone conduction sensor 180M. The application processor may implement a heartbeat detection function by parsing heartbeat information based on the blood pressure pulsation signal acquired by the bone conduction sensor 180M.

[0421] The buttons 190 include a power button, a volume button, etc. The buttons 190 may be mechanical buttons or touch buttons. The terminal device 100 may receive button inputs and generate button signal inputs related to user settings and function control of the terminal device 100.

[0422] The motor 191 may generate a vibration prompt. The motor 191 may be configured to provide an incoming call vibration prompt or touch vibration feedback. For example, touch operations performed for different applications (e.g., taking a photo and playing audio) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects for touch operations performed on different areas of the display 194. Different application scenarios (e.g., time reminders, information receipt, alarm clocks, and games) may also correspond to different vibration feedback effects. The touch vibration feedback may be further customized.

[0423] Indicator 192 may be an indicator light and may be configured to indicate charging status or charging power, or may be configured to indicate messages, missed calls, notifications, and the like.

[0424] The SIM card interface 195 is configured to connect to a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to implement contact with or separation from the terminal device 100. The terminal device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support a nano-SIM card, a micro-SIM card, a SIM card, etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The multiple cards can be the same type or different types. The SIM card interface 195 is compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with an external storage card. The terminal device 100 interacts with a network through the SIM card to implement functions such as telephone calls and data communications. In some embodiments, the terminal device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card may be embedded in the terminal device 100 and cannot be separated from the terminal device 100.

[0425] The software system of the terminal device 100 may use a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the present application, an Android system having a layered architecture is used as an example to describe the software structure of the terminal device 100.

[0426] FIG. 22 is a block diagram of the software structure of a terminal device according to an embodiment of the present application.

[0427] In a layered architecture, software is divided into layers. Each layer has a distinct role and task. The layers communicate with each other through software. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime system layer, and the kernel layer.

[0428] The application layer may include a series of application packages.

[0429] As shown in FIG. 22, the application package may include applications such as camera, calendar, map, WLAN, Bluetooth, music, video, messaging, email, web chat, and WPS.

[0430] 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.

[0431] As shown in FIG. 22, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0432] A window manager is configured to manage window programs. It can get the size of the display, determine if there is a status bar, perform screen locking, take screenshots, etc.

[0433] Content providers are configured to store and retrieve data and make the data accessible to applications. Data can include video, images, music, calls and receipts, search history and bookmarks, phone books, etc.

[0434] A view system includes visual controls, such as controls that display text and controls that display images. View systems can be configured to configure applications. A display interface can include one or more views. For example, a display interface that includes an SMS message notification icon can include a text display view and an image display view.

[0435] The telephone manager is configured to provide management of the communication functions of the terminal device, for example, call status (answer, reject, etc.).

[0436] The resource manager provides various resources such as localized strings, icons, images, layout files, and video files for the application.

[0437] The notification manager may be configured to allow applications to display notification information in the status bar and to convey notification messages. The notification manager may disappear automatically after a short pause without user interaction. For example, the notification manager may be configured to notify of download completion, provide message notifications, etc. The notification manager may alternatively be a notification that appears in the system's top status bar in the form of a graph or scrollbar text, e.g., a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, text information may be displayed in the status bar, a prompt tone may be provided, the terminal device may vibrate, or an indicator light may flash.

[0438] The Android runtime includes a kernel library and a virtual machine, and is responsible for scheduling and managing the Android system.

[0439] The kernel library contains two parts: the functions that need to be called in the Java language, and the Android kernel library.

[0440] The application layer and the application framework layer are executed in a virtual machine, which executes the Java files of the application layer and the application framework layer as binary files, and is configured to implement functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0441] The system layer may include multiple functional modules, for example, a surface manager, a media library, a three-dimensional graphics processing library (for example, OpenGL ES), and a two-dimensional graphics engine (for example, SGL).

[0442] The surface manager is configured to manage the display subsystem and provide a blend of two-dimensional and three-dimensional layers for multiple applications.

[0443] The media library supports playback and recording in multiple widely used audio and video formats, still images, etc. The media library may support multiple audio and video coding formats, for example, MPEG-4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0444] The 3D graphics processing library is configured to implement 3D graphics drawing, image rendering, compositing, layer processing, and the like.

[0445] The 2D graphics engine is a drawing engine for 2D drawing.

[0446] The kernel layer is a layer between the hardware and the software, and includes at least a display driver, a camera driver, an audio driver, and a sensor driver.

[0447] The following describes an example of the software and hardware operating procedures of the terminal device 100 with reference to a photography scenario.

[0448] When the touch sensor 180K receives a touch operation, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into an original input event (including information such as the touch coordinates and time stamp of the touch operation). The original input event is stored in the kernel layer. The application framework layer obtains the original input event from the kernel layer and recognizes the control corresponding to the input event. For example, the touch operation is a single tap operation, and the control corresponding to the single tap operation is the control of a camera application icon. The camera application calls an interface of the application framework layer to launch the camera application. Then, a camera driver is launched by calling the kernel layer, and a still image or video is captured by using the camera 193.

[0449] 23 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application. As shown in FIG. 23, the terminal device 23 of the present application includes at least one processor 230 (FIG. 23 shows only one processor), a memory 231, and a computer program 232 that is stored in the memory 231 and can be executed by the at least one processor 230. When the computer program 232 is executed, the processor 230 performs any of the steps of the above-described embodiments of the cross-device navigation task synchronization method.

[0450] The terminal device 23 may be a computing device such as a desktop computer, a notebook computer, a palmtop computer, 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 is merely an example of the terminal device 23 and does not constitute a limitation on the terminal device. The terminal device 23 may include more or fewer components than those shown, or some components may be combined, or different components may be used. For example, the terminal device 23 may further include an input / output device or a network access device.

[0451] Processor 230 may be a central processing unit (CPU). Processor 230 may alternatively be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor.

[0452] In some embodiments, memory 231 may be an internal storage unit of terminal device 23, such as a hard disk drive or internal storage of terminal device 23. In some other embodiments, memory 231 may alternatively be an external storage device of terminal device 23, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, or a flash card provided with terminal device 23. Furthermore, memory 231 may include both an internal storage unit of terminal device 23 and an external storage device. Memory 231 is configured to store, for example, program code of computer programs, such as an operating system, applications, a boot loader, data, other programs, etc. Memory 231 may further be configured to temporarily store data that has been output or that is to be output.

[0453] It should be noted that the contents of the above-mentioned devices / units, such as information exchange and execution process thereof, are based on the same concept as the method embodiments of the present application. For the specific functions and technical effects of the contents, please refer to the method embodiments. The details will not be described again here.

[0454] Those skilled in the art will clearly understand that the above division into functional units or modules is used merely as an example for convenience and concise description. In actual applications, the above functions may be allocated to different functional units or modules for implementation according to requirements. In other words, the internal structure of the device is divided into different functional units or modules for implementing all or part of the above-described functions. The functional units and modules of the embodiments may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit. Moreover, the specific names of the functional units and modules are merely intended to facilitate distinction between the functional units and modules and are not intended to limit the scope of protection of the present application. For the specific operation processes of the units or modules of the above system, please refer to the corresponding processes in the above method embodiments. Details will not be described again here.

[0455] An embodiment of the present application further provides a terminal device, which includes at least one processor, a memory, and a computer program stored in the memory and executable by the at least one processor, which, when executed, causes the processor to perform any one of the steps of the above-described method embodiments.

[0456] The embodiments of the present application further provide a computer-readable storage medium, which stores a computer program, which, when executed by a processor, can perform the steps of the above-described method embodiments.

[0457] An embodiment of the present application provides a computer program product, which, when executed on a mobile terminal, enables the mobile terminal to perform the steps of the above method embodiments.

[0458] When an integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on this understanding, all or part of the procedures in the method embodiments of the present application may be implemented by a computer program instructing associated hardware. The computer program may be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above method embodiments may be implemented. The computer program includes computer program code. The computer program code may be in source code format, object code format, executable file format, any intermediate format, etc. The computer-readable medium may include at least any entity or device capable of carrying computer program code to a photography apparatus / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier wave signal, a telecommunications signal, and a software distribution medium, such as a USB flash drive, a removable hard disk, a magnetic disk, or an optical disk. In some jurisdictions, a computer-readable medium may not be an electrical carrier wave signal or a telecommunications signal according to law or patent practice.

[0459] In the above embodiments, the description of each embodiment has its own focus, and for the parts not described in detail or recorded in the embodiments, please refer to the relevant descriptions of other embodiments.

[0460] Those skilled in the art may realize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is implemented by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but it should not be considered that the implementation goes beyond the scope of the present application.

[0461] In the embodiments provided herein, it should be understood that the disclosed apparatus / network devices and methods may be implemented in other ways. For example, the described embodiments of the apparatus / network devices are merely examples. For example, the division into modules or units is merely a logical division of function, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into other systems, or some features may be omitted or not implemented. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented through some interface. Indirect couplings or communication connections between apparatuses or units may be implemented in electronic, mechanical, or other forms.

[0462] The units described as separate parts may or may not be physically separated, and the parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual requirements to achieve the objectives of the solutions of the embodiments.

[0463] The above embodiments are not intended to limit the present application, but merely to describe the technical solutions of the present application. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that, without departing from the spirit and scope of the technical solutions of the embodiments of the present application, they can still modify the technical solutions described in the above embodiments or equivalently replace some technical features thereof. These modifications and replacements should fall within the protection scope of the present application.

[0464] This application claims priority to Chinese Patent Application No. 202111244792.3, filed with the State Intellectual Property Office of the People's Republic of China on October 25, 2021, for the invention entitled "CROSS-DEVICE NAVIGATION TASK SYNCHRONIZATION METHOD AND APPARATUS, DEVICE, AND STORAGE MEDIUM." The prior Chinese application is hereby incorporated by reference in its entirety.

Claims

1. 1. A method for synchronizing cross-device navigation tasks, comprising: Obtaining navigation data from the first navigation application through a first navigation transfer module by the first terminal when a preset cross-device transmission condition is satisfied; generating, by the first terminal, navigation synchronization information for the navigation data through the first navigation transfer module; receiving, by a second terminal, the navigation synchronization information sent by the first terminal, and sending the navigation synchronization information to a second navigation application through a second navigation transfer module; updating, by the second terminal, a navigation task of the second navigation application based on the navigation synchronization information; and The above-mentioned, when the cross-device transmission condition preset by the first terminal is satisfied, obtaining navigation data from the first navigation application through the first navigation transfer module includes: transmitting, by the second terminal, a communication label to the first terminal through a second short-range communication module in response to a touch operation by the first terminal, the communication label carrying a navigation task synchronization start identifier; activating, by the first terminal, the first navigation transfer module in response to the communication label, and obtaining the navigation data from the first navigation application through the first navigation transfer module; having Synchronization method.

2. Before transmitting a communication label by the second terminal to the first terminal through a second short-range communication module in response to a touch operation by the first terminal, the method further includes: sending a label write request to a label service thread through the second navigation forwarding module when a preset label write condition is satisfied by the second terminal; by the second terminal, responding to the label write request through the label service thread, adding the navigation task synchronization start identifier to the communication label, and writing the communication label to the second short-range communication module; Further comprising: The synchronization method of claim 1 .

3. The second terminal is an intelligent vehicle control terminal mounted in a vehicle, and the first terminal is a user terminal carried by a user; When the cross-device transmission condition preset by the first terminal is satisfied, before obtaining navigation data from the first navigation application through the first navigation transfer module, the method includes: establishing, by the second terminal, a communication connection to the first terminal when the second terminal detects a door opening event related to the vehicle; Obtaining, by the second terminal, a navigation synchronization application list, and, when the navigation synchronization application list is not empty, obtaining a configuration status of the second navigation transfer module; sending a navigation transfer notification to the first terminal by the second terminal when the second navigation transfer module is in an on state, so that the first terminal transmits the navigation synchronization information; Further comprising: The synchronization method of claim 1 .

4. The above-mentioned, when the cross-device transmission condition preset by the first terminal is satisfied, obtaining navigation data from the first navigation application through the first navigation transfer module includes: receiving, by the first terminal, the navigation transfer notification sent by the second terminal; obtaining, by the first terminal, the navigation data from the first navigation application through the first navigation transfer module in response to the navigation transfer notification; having The synchronization method according to claim 3 .

5. Establishing a communication connection to the first terminal by the second terminal when the second terminal detects a door opening event related to the vehicle includes: Recognizing, by the second terminal through the second navigation transfer module, the connection status of each registered terminal in a preset registered device list; establishing, by the second terminal, the communication connection to the first terminal based on connection information associated with the first terminal in the registered device list if the second terminal recognizes that the first terminal is in the registered device list and the connection status of the first terminal is connectable; or When 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 but the connection status of the first terminal is in an unconnectable state, the second terminal sends a wake-up command to the first terminal through a second short-range communication module; receiving, by the first terminal, the wake-up command transmitted by the second terminal through the second short-range communication module; transmitting, by the first terminal, a wireless connection request to the second terminal in response to the wake-up command to establish the communication connection to the second terminal; having The synchronization method according to claim 3 .

6. The second terminal is a user terminal carried by a user, and the first terminal is an intelligent vehicle control terminal installed in a vehicle; The above-mentioned, when the cross-device transmission condition preset by the first terminal is satisfied, obtaining navigation data from the first navigation application through the first navigation transfer module includes: establishing, by the first terminal, a close-range communication connection to the second terminal when the first terminal detects a parking event related to the vehicle, the close-range communication connection being used to transmit the navigation synchronization information to the second terminal; Obtaining, by the first terminal, a navigation synchronization application list, and, when the navigation synchronization application list is not empty, obtaining a configuration status of the first navigation transfer module; and acquiring, by the first terminal, the navigation data from the first navigation application through the first navigation transfer module when the first terminal recognizes that the first navigation transfer module is in an on state; having The synchronization method of claim 1 .

7. Establishing, by the first terminal, a short-range communication connection to the second terminal when the first terminal detects a parking event related to the vehicle, Recognizing, by the first terminal through the first navigation transfer module, the connection status of each registered terminal in a preset registered device list; If the first terminal recognizes that the second terminal is in the registered device list and that the connection status of the second terminal is connectable, establishing, by the first terminal, the close range communications connection to the second terminal based on connection information associated with the second terminal in the registered device list; or When 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 but the connection status of the second terminal is in an unconnectable state, the first terminal sends a wake-up command to the second terminal through a first short-range communication module; sending, by the second terminal, a close-range connection request to the first terminal in response to the wake-up command to establish the close-range communication connection to the first terminal; having The synchronization method according to claim 6.

8. The receiving, by the second terminal, the navigation synchronization information transmitted by the first terminal and transmitting the navigation synchronization information to a second navigation application through a second navigation transfer module, Caching the navigation data in a cache area by the second terminal through the second navigation transfer module, and detecting a heartbeat signal of the close range communication connection to the first terminal; If the second terminal does not receive the heartbeat signal within a preset valid time, the second terminal recognizes that the short-range communication connection to the first terminal has been lost, and sends the navigation synchronization information to the second navigation application. having The synchronization method according to claim 6.

9. When the cross-device transmission condition preset by the first terminal is satisfied, before obtaining navigation data from the first navigation application through the first navigation transfer module, the method includes: generating, by the first terminal, a navigation task through the first navigation application in response to a user's navigation operation, wherein the navigation data is generated based on the navigation task; receiving, by the first terminal through the first navigation transfer module, a service registration command sent by the first navigation application, the service registration command being used to authorize the first navigation application to transmit navigation data between devices; In response to the service registration command, adding the first navigation application to a navigation synchronization application list and setting the first navigation transfer module to an on state by the first terminal, the on state being 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 satisfied; Further comprising: A synchronization method according to any one of claims 1 to 8.

10. After receiving, by the second terminal, the navigation synchronization information sent by the first terminal, and sending the navigation synchronization information to a second navigation application through a second navigation transfer module, and updating a navigation task of the second navigation application based on the navigation synchronization information, the method includes: Sending navigation synchronization completion information to the first terminal through the second navigation transfer module by the second terminal; by the first terminal, in response to the navigation synchronization completion information, sending a termination command for the navigation task to the first navigation application through the first navigation transfer module to stop the navigation task of the first navigation application; Further comprising: A synchronization method according to any one of claims 1 to 8.

11. Before receiving, by the second terminal, the navigation synchronization information transmitted by the first terminal, the method further comprises: obtaining, by the first terminal, a navigation application list of the second terminal, the navigation application list including the second navigation application; By the first terminal, when the first terminal detects that a navigation application matching the first navigation application exists in the navigation application list, sending the navigation synchronization information to the second terminal, the navigation application matching the first navigation application being specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application; Further comprising: A synchronization method according to any one of claims 1 to 8.

12. After receiving, by the second terminal, the navigation synchronization information transmitted by the first terminal, the method further comprises: detecting, by the second terminal, whether a navigation application matching the first navigation application exists in a navigation application list; When the second terminal detects that the navigation application that matches the first navigation application exists in the navigation application list, the second terminal uses the navigation application that matches the first navigation application as the second navigation application and performs an operation of sending the navigation synchronization information to the second navigation application through the second navigation transfer module, where the navigation application that matches the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application; having A synchronization method according to any one of claims 1 to 8.

13. The step of updating the navigation task of the second navigation application based on the navigation synchronization information by the second terminal includes: determining, by the second terminal, a navigation destination based on the navigation synchronization information, and generating task update prompt information based on the navigation destination; updating, by the second terminal, the navigation task based on the navigation destination when the second terminal receives an update confirmation command fed back based on the task update prompt information; having A synchronization method according to any one of claims 1 to 8.

14. A cross-device navigation task synchronization method applied to a first terminal, comprising: Obtaining navigation data from the first navigation application through a first navigation transfer module when a preset cross-device transmission condition is satisfied; generating, through the first navigation transfer module, navigation synchronization information corresponding to the navigation data; sending the navigation synchronization information to a second terminal, the navigation synchronization information being used to update a navigation task of a second navigation application of the second terminal; and The above-mentioned, when the preset cross-device transmission condition is satisfied, obtaining navigation data from the first navigation application through the first navigation transfer module includes: receiving a communication label transmitted by a second short-range communication module of the second terminal in response to a touch operation by the second terminal, the communication label carrying a navigation task synchronization start identifier; activating the first navigation transfer module in response to the communication label and obtaining the navigation data from the first navigation application through the first navigation transfer module; having Synchronization method.

15. The second terminal When the second terminal detects that a label writing condition is satisfied, it sends a label writing request to a label service thread through a second navigation forwarding module; Responding to the label write request through the label service thread, adding the navigation task synchronization start identifier to the communication label, and writing the communication label to the second short-range communication module, The communication label is obtained. The synchronization method of claim 14.

16. The above-mentioned, when the preset cross-device transmission condition is satisfied, obtaining navigation data from the first navigation application through the first navigation transfer module includes: receiving a navigation transfer notification sent by the second terminal, wherein after the second terminal establishes a communication connection to the first terminal, the navigation transfer notification is sent to the first terminal when it is detected that a second navigation transfer module of the second terminal is in an on state; obtaining the navigation data from the first navigation application through the first navigation transfer module in response to the navigation transfer notification; having The synchronization method of claim 14.

17. Before receiving the navigation transfer notification sent by the second terminal, the method further comprises: receiving a wake-up command sent by the second terminal through a second short-range communication module; transmitting a wireless connection request to the second terminal in response to the wake-up command to establish the communication connection to the second terminal; Further comprising: The synchronization method of claim 16.

18. The first terminal is an intelligent vehicle control terminal mounted in a vehicle, and the second terminal is a user terminal carried by a user; The above-mentioned, when the preset cross-device transmission condition is satisfied, obtaining navigation data from the first navigation application through the first navigation transfer module includes: establishing a near field communication connection to the second terminal when a parking event is detected related to the vehicle, the near field communication connection being used to transmit the navigation synchronization information to the second terminal; Obtaining a navigation synchronization application list, and when the navigation synchronization application list is not empty, obtaining a configuration status of the first navigation transfer module; When the first navigation transfer module is in an on state, obtaining the navigation data from the first navigation application through the first navigation transfer module; having The synchronization method of claim 14.

19. Establishing a short-range communication connection to the second terminal when detecting a parking event related to the vehicle includes: Recognizing, through a second navigation forwarding module, the connection status of each registered terminal in the preset registered device list; if the second terminal is in the registered device list and a connection status of the second terminal is connectable, establishing the near field communication connection to the second terminal based on connection information associated with the second terminal in the registered device list; or If the second terminal is not in the registered device list, or if the second terminal is in the registered device list but a connection status of the second terminal is in an unconnectable state, sending a wake-up command to the second terminal through a first short-range communication module, the wake-up command being used to enable the second terminal to establish the short-range communication connection to the first terminal; having 20. The synchronization method of claim 18.

20. The above-mentioned, when the preset cross-device transmission condition is satisfied, obtaining navigation data from the first navigation application through the first navigation transfer module includes: generating a navigation task through the first navigation application in response to a user's navigation operation, wherein the navigation data is generated based on the navigation task; receiving, via the first navigation transfer module, a service registration command sent by the first navigation application, the service registration command being used to authorize the first navigation application to transmit navigation data between devices; In response to the service registration command, adding the first navigation application to a navigation synchronization application list and setting the first navigation transfer module to an on state, the on state being 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 satisfied; having 20. A synchronization method according to any one of claims 14 to 19.

21. After transmitting the navigation synchronization information to the second terminal as described above, the method further comprises: receiving navigation synchronization completion information fed back by the second terminal through a second navigation transfer module of the second terminal; sending a termination command for the navigation task to the first navigation application through the first navigation transfer module in response to the navigation synchronization completion information to terminate the navigation task of the first navigation application; Further comprising:

20. A synchronization method according to any one of claims 14 to 19.

22. Before transmitting the navigation synchronization information to the second terminal, the method further comprises: obtaining a navigation application list of the second terminal, the navigation application list including the second navigation application; If a navigation application that matches the first navigation application exists in the navigation application list, sending the navigation synchronization information to the second terminal, and the navigation application that matches the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the first navigation application; Further comprising:

20. A synchronization method according to any one of claims 14 to 19.

23. A cross-device navigation task synchronization method applied to a second terminal, comprising: receiving navigation synchronization information transmitted by a first terminal, the navigation synchronization information being generated based on navigation data of a first navigation application of the first terminal; Sending the navigation synchronization information to a second navigation application through a second navigation transfer module; updating a navigation task of the second navigation application based on the navigation synchronization information; and and The receiving of the navigation synchronization information transmitted by the first terminal includes: In response to a touch operation by the first terminal, transmitting a communication label to the first terminal through a second short-range communication module, so that the first terminal activates a first navigation transfer module in response to the communication label and obtains the navigation data from the first navigation application through the first navigation transfer module, wherein the communication label carries a navigation task synchronization start identifier; receiving the navigation synchronization information sent by the first terminal through the first navigation transfer module; having Synchronization method.

24. Before transmitting a communication label to the first terminal through a second short-range communication module in response to a touch operation by the first terminal, the method further includes: sending a label write request to a label service thread through the second navigation forwarding module if a preset label write condition is satisfied; responding to the label write request through the label service thread, adding the navigation task synchronization start identifier to the communication label, and writing the communication label to the second short-range communication module; Further comprising:

24. The synchronization method of claim 23.

25. The second terminal is an intelligent vehicle control terminal mounted in a vehicle; Before receiving the navigation synchronization information transmitted by the first terminal, the method further comprises: establishing a communication connection to the first terminal when a door opening event related to the vehicle is detected; Obtaining a navigation synchronization application list, and when the navigation synchronization application list is not empty, obtaining a configuration status of the second navigation transfer module; When the second navigation transfer module is in an on state, sending a navigation transfer notification to the first terminal to cause the first terminal to send the navigation synchronization information; Further comprising:

24. The synchronization method of claim 23.

26. Establishing a communication connection to the first terminal when a door opening event related to the vehicle is detected includes: Recognizing the connection status of each registered terminal in a preset registered device list through the second navigation forwarding module; If the first terminal is in the registered device list and a connection status of the first terminal is connectable, establishing the communication connection to the first terminal based on connection information associated with the first terminal in the registered device list; or If the first terminal is not in the registered device list, or if the first terminal is in the registered device list but a connection status of the first terminal is in an unconnectable state, sending a wake-up command to the first terminal through a second short-range communication module, the wake-up command being used to enable the first terminal to establish the communication connection to the second terminal; having 26. The synchronization method of claim 25.

27. The second terminal is a user terminal carried by a user, and the first terminal is an intelligent vehicle control terminal installed in a vehicle; The step of transmitting the navigation synchronization information to the second navigation application through a second navigation transfer module includes: Caching the navigation data in a cache area through the second navigation transfer module, and detecting a heartbeat signal of a communication connection to the first terminal; If the heartbeat signal is not received within a preset valid time, it is recognized that the short-range communication connection to the first terminal has been lost, and the navigation synchronization information is sent to the second navigation application. having 24. The synchronization method of claim 23.

28. After receiving the navigation synchronization information transmitted by the first terminal as described above, the method includes: detecting whether a navigation application matching the first navigation application exists in a navigation application list, the navigation application list including the first navigation application; If the navigation application that matches the first navigation application exists in the navigation application list, use the navigation application that matches the first navigation application as the second navigation application, and perform an operation of sending the navigation synchronization information to the second navigation application through the second navigation transfer module, where the navigation application that matches the first navigation application is specifically an application that has permission to perform cross-device navigation data transmission with the second navigation application; having 28. A synchronization method according to any one of claims 23 to 27.

29. updating the navigation task of the second navigation application based on the navigation synchronization information, determining a navigation destination based on the navigation synchronization information and generating task update prompt information based on the navigation destination; updating the navigation task based on the navigation destination when an update confirmation command is received based on the task update prompt information; having 28. A synchronization method according to any one of claims 23 to 27.

30. After updating the navigation task of the second navigation application based on the navigation synchronization information, the method further comprises: The method further includes transmitting navigation synchronization completion information to the first terminal, and the first terminal transmitting a termination command for the navigation task to the first navigation application through a first navigation transfer module of the first terminal in response to the navigation synchronization completion information, so as to terminate the navigation task of the first navigation application.

28. A synchronization method according to any one of claims 23 to 27.

31. Memory and a processor; a computer program stored in the memory and executable by the processor; When the computer program is executed, the processor performs the method of claim 14. Electronic devices.

32. Memory and a processor; a computer program stored in the memory and executable by the processor; When the computer program is executed, the processor performs the method of claim 23. Electronic devices.

33. An electronic device according to claim 31; The electronic device according to claim 32; Cross-device navigation task synchronization system.

34. storing a computer program; When the computer program is executed by a processor, the method according to claim 14 or the method according to claim 23 is performed. A computer-readable storage medium.

Images