Method, device and storage medium for synchronizing navigation tasks across devices

Abstract

The application is suitable for the technical field of data transmission, and provides a synchronization method and device for navigation tasks across devices, equipment and a storage medium. The method comprises the following steps: if a first terminal meets a preset cross-device transmission condition, the first terminal acquires navigation data from a first navigation application through a first navigation flow conversion module; the first navigation flow conversion module generates navigation synchronization information of the navigation data; a second terminal receives the navigation synchronization information sent by the first terminal, and transmits the navigation synchronization information to a second navigation application through a second navigation flow conversion module; and the navigation task of the second navigation application is updated according to the navigation synchronization information. The technical scheme provided by the application can realize the synchronization of navigation tasks across devices. In the navigation scene across devices, the user does not need to set the task of the navigation application of the terminal for multiple times, so that the efficiency of setting the navigation task is greatly improved, and the repeated operation of the user is reduced.

Description

[0001] This application is a divisional application. The original application, application number 202111244792.3, was filed on October 25, 2021. The entire contents of the original application, entitled "Synchronization Method, Apparatus, Device and Storage Medium for Navigation Tasks Across Devices," are incorporated herein by reference. Technical Field

[0002] This application belongs to the field of equipment control technology, and in particular relates to methods, apparatus, devices and storage media for synchronizing navigation tasks across devices. Background Technology

[0003] With the continuous development of navigation technology, its application scenarios are constantly expanding. From its initial focus on car navigation, it has gradually evolved to provide navigation for pedestrians, and even further subdivided into application areas such as cycling navigation. Navigation applications have become an indispensable part of people's lives and work. Therefore, how to complete navigation tasks quickly and conveniently has become a pressing technical problem that needs to be solved.

[0004] Existing navigation applications allow users to set their destination on their mobile devices. The application then generates a navigation task based on the user's location and destination, providing directional guidance as the user travels. However, in actual navigation, various scenarios may arise, each requiring a different device. For example, a user might use a navigation app within a vehicle while driving, whereas a user might use a smartphone while walking. Therefore, if multiple navigation scenarios are involved, users need to set up navigation tasks multiple times on different devices, significantly increasing configuration complexity and reducing the efficiency of navigation task setup. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for synchronizing navigation tasks across devices. It can solve the problem that in navigation technology, users need to set navigation tasks multiple times in cross-device navigation scenarios, resulting in low efficiency in setting navigation tasks and increased repetitive settings by users.

[0006] In a first aspect, embodiments of this application provide a method for synchronizing navigation tasks across devices, comprising:

[0007] If the first terminal meets the preset cross-device transmission conditions, it obtains navigation data from the first navigation application.

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

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

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

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

[0012] If the first terminal meets the preset cross-device transmission conditions, it obtains navigation data from the first navigation application. Specifically, if the first terminal meets the preset cross-device transmission conditions, it obtains navigation data from the first navigation application through the first navigation transfer module.

[0013] The first terminal generates the navigation synchronization information of the navigation data specifically by generating the navigation synchronization information of the navigation data through the first navigation transfer module.

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

[0015] Implementing the embodiments of this application has the following beneficial effects: When the first terminal detects that the cross-device transmission conditions are met, the navigation data of the already started navigation task is automatically obtained from the first navigation application through the first navigation transfer module on the first terminal, and navigation synchronization information corresponding to the navigation data is generated through the first navigation transfer module. The navigation synchronization information is then sent to the second terminal, realizing the cross-device transmission of navigation data. After receiving the above-mentioned navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through the second navigation transfer module on its local side. Subsequently, the second terminal can update the navigation task of the second navigation application according to the navigation synchronization information, realizing the synchronization of navigation tasks across devices. Compared with existing navigation technologies, this application can realize the synchronization of navigation tasks across devices. In scenarios where cross-device navigation is required, users do not need to repeatedly set tasks for the terminal's navigation application. Instead, the navigation transfer module can automatically realize the flow of navigation data to update the navigation tasks in the navigation application, thereby greatly improving the efficiency of navigation task setting and reducing repetitive operations by users. On the other hand, after the first navigation transfer module in the first terminal obtains navigation data from the first navigation application, it does not directly send the navigation data to the second navigation transfer module of the second terminal. Instead, it converts the data into corresponding navigation synchronization information. This navigation synchronization information can be transmitted between navigation transfer modules of different terminals and then transmitted to the second navigation application through the second navigation transfer module. This is not a direct transmission between navigation applications within two terminals. Therefore, it is not necessary for the first terminal and the second terminal to have the same navigation application installed. This enables cross-device and cross-application navigation data transfer and further improves the application scope of navigation task synchronization.

[0016] In one possible implementation of the first aspect, if the first terminal meets preset cross-device transmission conditions, it obtains navigation data from the first navigation application through the first navigation transfer module, including:

[0017] In response to a touch operation with the first terminal, the second terminal sends a communication tag to the first terminal via a second near-field communication module; the communication tag carries a navigation task synchronization start identifier.

[0018] The first terminal responds to the communication tag, activates the first navigation transfer module, and obtains the navigation data from the first navigation application through the first navigation transfer module.

[0019] In one possible implementation of the first aspect, before the second terminal sends a communication tag to the first terminal via the second near-field communication module in response to a touch operation with the first terminal, the method further includes:

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

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

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

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

[0024] If the second terminal detects an opening event related to the vehicle door, it establishes a communication connection with the first terminal.

[0025] The second terminal obtains a list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, it obtains the setting status of the second navigation flow module.

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

[0027] In one possible implementation of the first aspect, if the first terminal meets preset cross-device transmission conditions, it obtains navigation data from the first navigation application through the first navigation transfer module, including:

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

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

[0030] In one possible implementation of the first aspect, if the second terminal detects an opening event related to the vehicle door, it establishes a communication connection with the first terminal, including:

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

[0032] 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, then based on the connection information associated with the first terminal in the registered device list, the second terminal establishes the communication connection with the first terminal.

[0033] If the second terminal detects that the first terminal is not in the registered device list, or the first terminal is in the registered device list and the connection status of the first terminal is unconnectable, then the second terminal sends a wake-up command to the first terminal through the second near-field communication module.

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

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

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

[0037] Correspondingly, if the first terminal meets the preset cross-device transmission conditions, it obtains navigation data from the first navigation application through the first navigation transfer module, including:

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

[0039] The first terminal obtains a list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, it obtains the setting status of the first navigation flow module.

[0040] If the first terminal detects that the first navigation transfer module is in the activated state, it obtains navigation data from the first navigation application through the first navigation transfer module.

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

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

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

[0044] If the first terminal detects that the second terminal is not in the registered device list, or if the second terminal is in the registered device list and the connection status of the second terminal is unconnectable, then the first terminal sends a wake-up command to the second terminal through the first near-field communication module.

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

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

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

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

[0049] In one possible implementation of the first aspect, before the first terminal obtains navigation data from the first navigation application through the first navigation transfer module if the first terminal meets the preset cross-device transmission conditions, the method further includes:

[0050] The first terminal responds to the user's navigation operation and generates a navigation task through the first navigation application; the navigation data is generated based on the navigation task.

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

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

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

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

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

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

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

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

[0059] In one possible implementation of the first aspect, after the second terminal receives the navigation synchronization information sent by the first terminal, the following steps are included:

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

[0061] If the second terminal detects that the navigation application list contains a navigation application that matches the first navigation application, it will use the navigation application that matches the first navigation application as the second navigation application and execute the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation transfer module; the navigation application that matches the first navigation application is specifically an application that has the permission to transmit navigation data across devices with the second navigation application.

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

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

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

[0065] Secondly, this application provides a method for synchronizing navigation tasks across devices, applied to a first terminal, comprising:

[0066] If the preset cross-device transmission conditions are met, navigation data is obtained from the first navigation application through the first navigation transfer module;

[0067] The navigation synchronization information corresponding to the navigation data is generated by the first navigation flow module;

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

[0069] In this implementation, after the first terminal sends navigation synchronization information to the second terminal, the process of the second terminal updating the navigation task based on the navigation synchronization information is as follows: the second terminal transmits 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 according to the navigation synchronization information.

[0070] In one possible implementation of the second aspect, the step of obtaining navigation data from the first navigation application through the first navigation transfer module if preset cross-device transmission conditions are met includes:

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

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

[0073] In one possible implementation of the second aspect, the communication tag is obtained by sending a tag writing request to the tag service thread through the second navigation flow module when the second terminal detects that the tag writing conditions are met, and by having the tag service thread respond to the tag writing request, add the start identifier to the communication tag, and write the communication tag to the second near-field communication module.

[0074] In one possible implementation of the second aspect, the step of obtaining navigation data from the first navigation application through the first navigation transfer module if preset cross-device transmission conditions are met includes:

[0075] Receive navigation flow notification sent by the second terminal; the navigation flow notification is sent to the first terminal after the second terminal is connected to the first terminal and the second navigation flow module of the second terminal is detected to be in the start state;

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

[0077] In one possible implementation of the second aspect, prior to receiving the navigation flow notification sent by the second terminal, the method further includes:

[0078] Receive the wake-up command sent by the second terminal through the second near-field communication module;

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

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

[0081] Correspondingly, if the preset cross-device transmission conditions are met, then obtaining navigation data from the first navigation application through the first navigation transfer module includes:

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

[0083] Get the list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, get the setting status of the first navigation flow module.

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

[0085] In one possible implementation of the second aspect, establishing a near-field communication connection with the second terminal upon detecting a parking event related to the vehicle includes:

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

[0087] If the second terminal is in the registered device list and the connection status of the second terminal is connectable, then based on the connection information associated with the second terminal in the registered device list, the near-field communication connection is established with the second terminal.

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

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

[0090] In one possible implementation of the second aspect, before obtaining navigation data from the first navigation application via the first navigation transfer module if preset cross-device transmission conditions are met, the method further includes:

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

[0092] The first navigation transfer module receives a service registration instruction transmitted by the first navigation application; the service registration instruction is used to authorize the first navigation application to have the permission to transmit navigation data between devices.

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

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

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

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

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

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

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

[0100] Thirdly, embodiments of this application provide a synchronization device for navigation tasks across devices, comprising:

[0101] The navigation data acquisition unit is used to acquire navigation data from the first navigation application through the first navigation transfer module if preset cross-device transmission conditions are met.

[0102] A navigation synchronization information generation unit is used to generate navigation synchronization information corresponding to the navigation data through the first navigation flow module;

[0103] A navigation synchronization information sending unit is used to send the navigation synchronization information to a second terminal, wherein the navigation synchronization information is used to update the navigation task of a second navigation application within the second terminal.

[0104] In one possible implementation of the third aspect, the navigation data acquisition unit includes:

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

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

[0107] In one possible implementation of the third aspect, the communication tag is obtained by sending a tag writing request to the tag service thread through the second navigation flow module when the second terminal detects that the tag writing conditions are met, and by having the tag service thread respond to the tag writing request, add the start identifier to the communication tag, and write the communication tag to the second near-field communication module.

[0108] In one possible implementation of the third aspect, the navigation data acquisition unit includes:

[0109] A navigation flow notification receiving unit is used to receive a navigation flow notification sent by the second terminal; the navigation flow notification is sent to the first terminal after the second terminal is connected to the first terminal and the second navigation flow module of the second terminal is detected to be in the start state;

[0110] A navigation flow notification response unit is used to respond to the navigation flow notification by obtaining navigation data from the first navigation application through the first navigation flow module.

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

[0112] A wake-up command receiving unit is used to receive a wake-up command sent by the second terminal through the second near-field communication module;

[0113] A wake-up command response unit is used to send a wireless connection request to the second terminal in response to the wake-up command, so as to establish the communication connection with the second terminal.

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

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

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

[0117] The first state recognition unit is used to obtain a list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, the setting state of the first navigation flow module is obtained.

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

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

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

[0121] A direct connection triggering unit is used to establish a near-field communication connection with the second terminal based on the connection information associated with the second terminal in the registered device list if the second terminal is in the registered device list and the connection status of the second terminal is a connectable state.

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

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

[0124] A navigation operation response unit is used to respond to a user's navigation operation and generate a navigation task through the first navigation application; the navigation data is generated based on the navigation task.

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

[0126] A service registration response unit is configured to, in response to the service registration instruction, add the first navigation application to the navigation synchronization application list and set the first navigation flow module to the start state; the start state is configured to send the navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission conditions are met.

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

[0128] The navigation synchronization completion information receiving unit is used to receive navigation synchronization completion information fed back by the second terminal through the second navigation flow module;

[0129] The navigation termination unit is used to respond to the navigation synchronization completion information by transmitting a navigation task termination instruction to the first navigation application through the first navigation flow module, so as to stop the navigation task of the first navigation application.

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

[0131] A navigation application list acquisition unit is used to acquire a navigation application list of the second terminal; the navigation application list includes the second navigation application;

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

[0133] Fourthly, embodiments of this application provide a method for synchronizing navigation tasks across devices, applied to a second terminal, comprising:

[0134] Receive navigation synchronization information sent by the first terminal; the navigation synchronization information is generated based on navigation data from the first navigation application within the first terminal;

[0135] The navigation synchronization information is transmitted to the second navigation application via the second navigation transfer module;

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

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

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

[0139] Receive the navigation synchronization information sent by the first terminal through the first navigation flow module.

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

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

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

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

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

[0145] If a door opening event related to the vehicle is detected, a communication connection is established with the first terminal;

[0146] Get the list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, get the setting status of the second navigation flow module.

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

[0148] In one possible implementation of the fourth aspect, establishing a communication connection with the first terminal upon detecting a door opening event related to the vehicle includes:

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

[0150] If the first terminal is in the registered device list and the connection status of the first terminal is connectable, then a communication connection is established with the first terminal based on the connection information associated with the first terminal in the registered device list.

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

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

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

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

[0155] The navigation synchronization information is cached in the cache area by the second navigation flow module, and the heartbeat signal of the communication connection with the first terminal is detected.

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

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

[0158] The system checks if a navigation application matching the first navigation application exists in the navigation application list; the navigation application list includes the first navigation application.

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

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

[0161] The navigation destination is determined based on the navigation synchronization information, and a task update prompt is generated based on the navigation destination.

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

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

[0164] The system sends navigation synchronization completion information to the first terminal, so that the first terminal responds to the navigation synchronization completion information and transmits a navigation task termination instruction to the first navigation application through the first navigation flow module, thereby stopping the navigation task of the first navigation application.

[0165] Fifthly, embodiments of this application provide a device for synchronizing navigation tasks across devices, comprising:

[0166] A navigation synchronization information receiving unit is used to receive navigation synchronization information sent by a first terminal; the navigation synchronization information is generated based on navigation data from a first navigation application within the first terminal.

[0167] A navigation synchronization information transmission unit is used to transmit the navigation synchronization information to a second navigation application through a second navigation transfer module;

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

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

[0170] A communication tag sending unit gate is used to send a communication tag to the first terminal via a second near-field communication module in response to a touch operation with the first terminal, so that the first terminal responds to the communication tag, starts a first navigation flow module, and obtains the navigation data from the first navigation application through the first navigation flow module; the communication tag carries a navigation task synchronization start identifier;

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

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

[0173] The tag write request unit is used to send a tag write request to the tag service thread through the second navigation flow module if the preset tag write conditions are met.

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

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

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

[0177] The door opening event triggering unit is used to establish a communication connection with the first terminal if a door opening event related to the vehicle is detected.

[0178] The second state recognition unit is used to obtain the navigation synchronization application list. If the navigation synchronization application list is not empty, the setting state of the second navigation flow module is obtained.

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

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

[0181] The connection status determination unit is used to identify the connection status of each registered terminal in the preset list of registered devices through the second navigation flow module;

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

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

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

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

[0186] An information caching unit is used to cache the navigation synchronization information in a cache area through the second navigation flow module and detect the heartbeat signal of the communication connection with the first terminal.

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

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

[0189] The matching application detection unit is used to detect whether there is a navigation application in the navigation application list that matches the first navigation application; the navigation application list includes the first navigation application;

[0190] The second navigation application identification unit is used to identify the navigation application matching the first navigation application if it detects that there is a navigation application matching the first navigation application in the navigation application list, and then to select the navigation application matching the first navigation application as the second navigation application and perform the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module; the navigation application matching the first navigation application is specifically an application that has the permission to transmit navigation data across devices with the second navigation application.

[0191] In one possible implementation of the fifth aspect, the navigation task update unit includes:

[0192] The update prompt information generation unit is used to determine the navigation destination based on the navigation synchronization information and generate task update prompt information based on the navigation destination;

[0193] An update confirmation instruction response unit is configured to update the navigation task based on the navigation destination if it receives an update confirmation instruction based on the update prompt information.

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

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

[0196] In a sixth aspect, embodiments of this application provide an electronic device, a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor executes the computer program to implement the synchronization method for cross-device navigation tasks as described in any of the second aspects above.

[0197] In a seventh aspect, embodiments of this application provide an electronic device, a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor executes the computer program to implement the synchronization method for cross-device navigation tasks as described in any of the fourth aspects above.

[0198] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program, characterized in that, when executed by a processor, the computer program implements the synchronization method for cross-device navigation tasks described in any of the second or fourth aspects above.

[0199] Ninthly, embodiments of this application provide a computer program product that, when run on an electronic device, causes the electronic device to perform the synchronization method for cross-device navigation tasks described in any of the second or fourth aspects above.

[0200] In a tenth aspect, embodiments of this application provide a chip system including a processor coupled to a memory, the processor executing a computer program stored in the memory to implement a synchronization method for a navigation task across devices as described in any of the second or fourth aspects.

[0201] In one aspect, embodiments of this application provide a cross-device navigation system, including a first terminal and a second terminal;

[0202] The first terminal is configured to obtain navigation data from the first navigation application through the first navigation transfer module if preset cross-device transmission conditions are met.

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

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

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

[0206] In one 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 if preset cross-device transmission conditions are met, including:

[0207] The second terminal is used to send a communication tag to the first terminal via a second near-field communication module in response to a touch operation with the first terminal; the communication tag carries a navigation task synchronization start identifier;

[0208] The first terminal is configured to respond to the communication tag, activate the first navigation transfer module, and obtain the navigation data from the first navigation application through the first navigation transfer module.

[0209] In one possible implementation of the eleventh aspect, the second terminal is further used for:

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

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

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

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

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

[0215] The second terminal is used to obtain a list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, the terminal obtains the setting status of the second navigation flow module.

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

[0217] In one 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 if preset cross-device transmission conditions are met, including:

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

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

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

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

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

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

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

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

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

[0227] Correspondingly, the first terminal is configured to obtain navigation data from the first navigation application through the first navigation transfer module if preset cross-device transmission conditions are met, including:

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

[0229] The first terminal is used to obtain a list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, the terminal obtains the setting status of the first navigation flow module.

[0230] The first terminal is configured to obtain navigation data from the first navigation application through the first navigation transfer module if it detects that the first navigation transfer module is in an active state.

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

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

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

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

[0235] The second terminal is configured to respond to the wake-up command by sending a near-field connection request to the first terminal to establish a near-field communication connection with the first terminal.

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

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

[0238] The second terminal is configured to disconnect the near-field communication connection with the first terminal and transmit the navigation synchronization information to the second navigation application if it does not receive the heartbeat signal within a preset effective time.

[0239] In one possible implementation of the eleventh aspect, the first terminal is further used for:

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

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

[0242] The first terminal is configured to, in response to the service registration instruction, add the first navigation application to the navigation synchronization application list and set the first navigation flow module to the start state; the start state is configured to send navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission conditions are met.

[0243] In one possible implementation of the eleventh aspect, the first terminal and the second terminal are further used for:

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

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

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

[0247] The first terminal is configured to obtain a list of navigation applications from the second terminal; the list of navigation applications includes the second navigation application.

[0248] The first terminal is configured to send the navigation synchronization information to the second terminal if it detects that a navigation application matching the first navigation application exists in the navigation application list; the navigation application matching the first navigation application is specifically an application that has the permission to transmit navigation data across devices with the first navigation application.

[0249] In one possible implementation of the eleventh aspect, the second terminal is also used for:

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

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

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

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

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

[0255] It is understood that the beneficial effects of aspects two through eleven above can be found in the relevant descriptions in aspect one above, and will not be repeated here. Attached Figure Description

[0256] Figure 1 This is a schematic diagram of a navigation route provided in one embodiment of this application;

[0257] Figure 2 This is an interactive flowchart of a cross-device navigation task synchronization method provided in an embodiment of this application;

[0258] Figure 3(a) is a schematic diagram of a scenario for cross-device transmission of navigation data provided in an embodiment of this application;

[0259] Figure 3(b) is a schematic diagram of a scenario for cross-device transmission of navigation data provided in another embodiment of this application.

[0260] Figure 4a This is a schematic diagram illustrating the initiation of a navigation task according to an embodiment of this application;

[0261] Figure 4b This is a schematic diagram illustrating the initiation of a navigation task provided in another embodiment of this application;

[0262] Figure 4cThis is a schematic diagram illustrating the initiation of a navigation task according to another embodiment of this application;

[0263] Figure 5 This is a schematic diagram showing the setting of the status switch of the first navigation flow module provided in an embodiment of this application;

[0264] Figure 6 This is a schematic diagram illustrating the application installation prompts on a second terminal according to an embodiment of this application;

[0265] Figure 7 This is a schematic diagram illustrating a modification of the navigation task provided in one embodiment of this application;

[0266] Figure 8 This is a schematic diagram illustrating the updating of a navigation task provided in an embodiment of this application;

[0267] Figure 9 This is a schematic diagram illustrating the termination of a navigation task according to an embodiment of this application;

[0268] Figure 10 This is a schematic diagram of a synchronization failure response provided in an embodiment of this application;

[0269] Figure 11 This is an interactive schematic diagram of a method for synchronizing navigation tasks across devices provided in an embodiment of this application;

[0270] Figure 12 This is a schematic diagram of a touch scenario between an in-vehicle terminal and a smartphone provided in an embodiment of this application;

[0271] Figure 13 This is an interactive schematic diagram of a navigation task synchronization method provided in an embodiment of this application;

[0272] Figure 14 This is a schematic diagram of the interface of an in-vehicle terminal provided in an embodiment of this application;

[0273] Figure 15 This is a flowchart illustrating the three-way interaction between a user terminal, an in-vehicle terminal, and a server, provided in an embodiment of this application.

[0274] Figure 16 This is an interactive schematic diagram of a navigation task synchronization method provided in an embodiment of this application;

[0275] Figure 17 This is a flowchart illustrating the implementation of a method for synchronizing navigation data across devices by a first terminal, as provided in an embodiment of this application.

[0276] Figure 18 This is a flowchart illustrating the implementation of a method for synchronizing navigation data across devices by a second terminal, as provided in an embodiment of this application.

[0277] Figure 19This is a structural block diagram of a cross-device navigation task synchronization device provided in an embodiment of this application;

[0278] Figure 20 This is a structural block diagram of a cross-device navigation task synchronization device provided in an embodiment of this application;

[0279] Figure 21 This is a schematic diagram of the structure of the final device provided in the embodiments of this application;

[0280] Figure 22 This is a software structure block diagram of the terminal device according to an embodiment of this application;

[0281] Figure 23 This is a structural block diagram of a terminal device provided in an embodiment of this application. Detailed Implementation

[0282] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

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

[0284] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0285] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0286] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0287] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0288] With the continuous development of navigation technology, the application scenarios of navigation applications are becoming increasingly widespread, covering all aspects of people's lives and work. However, while the application scenarios of navigation technology are constantly expanding, the complexity of these scenarios is also increasing. Within the same navigation route, there may be different navigation scenarios such as walking, cycling, driving, and public transportation. In different scenarios, different terminal navigation applications are often required. For example, in a walking navigation scenario, a user may use a navigation application on their smartphone; while in a driving navigation scenario, a user may use a navigation application on their in-vehicle terminal.

[0289] For example, let's take a navigation task as an example: When a user is traveling, if they need to go to a tourist attraction, they can enter the corresponding destination in a navigation application on any terminal. The navigation application can generate a corresponding navigation task based on the navigation destination and the initial location, and guide the user to the navigation destination in real time. Figure 1 A schematic diagram of a navigation route provided according to an embodiment of this application is shown. See also Figure 1 As shown, the navigation route starts at home and ends at a tourist attraction. The route includes sidewalks, roads, and highways. On the sidewalk sections (sections A and C), users must walk; while on the road and highway sections (section B), users must drive. Therefore, during the navigation process, the user first enters the destination (tourist attraction) into a navigation app on their smartphone and completes section A. Then, upon entering section B, the user can switch from walking to driving and navigate through the vehicle's in-vehicle navigation app, requiring them to re-enter the destination. Finally, upon entering section C, the user must again switch from driving to walking, and again enter the destination on their smartphone.

[0290] Therefore, when a navigation task includes multiple navigation scenarios, if different terminals are used to complete the navigation for different scenarios, the user will need to input the navigation destination multiple times on different terminals throughout the entire navigation task. This results in the user having to perform multiple repetitive navigation task settings operations, reducing navigation efficiency.

[0291] Example 1:

[0292] Therefore, in order to address the shortcomings of existing cross-device navigation task synchronization technologies, this application provides a cross-device navigation task synchronization method. The execution subject of this cross-device navigation task synchronization method can specifically be two terminal devices, namely a first terminal and a second terminal. The terminal device can be an electronic device such as a smartphone, a vehicle intelligent control terminal (hereinafter referred to as an in-vehicle terminal) installed in a vehicle, a tablet computer, a smartwatch, or a smart bracelet. The terminal device has a navigation application installed on it and can execute user-initiated navigation tasks through the navigation application.

[0293] It should be noted that the first terminal and the second terminal can be the same type of terminal, for example, the first terminal is a smartphone and the second terminal is also a smartphone; of course, the first terminal and the second terminal can also be different types of terminals, 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. There are no restrictions on the terminal types of the first terminal and the second terminal here. The appropriate terminal type can be selected according to the actual navigation scenario.

[0294] Figure 2 An interactive flowchart of a cross-device navigation task synchronization method according to an embodiment of this application is shown, and is described in detail below:

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

[0296] In this embodiment, the first terminal can be configured with corresponding cross-device transmission conditions. These conditions are used to notify the first terminal that the navigation task of the local first navigation application needs to be synchronized to other terminals (in this embodiment, the second terminal). For example, the first terminal can store a list of devices for cross-device transmission of navigation data. If the first terminal finds the wireless signal of any registered terminal in the list, it recognizes that the cross-device transmission conditions are met and executes operation S201. Alternatively, the first terminal can be configured with corresponding cross-device transmission trigger gestures. When the first terminal detects that a user-initiated touch operation matches a preset trigger gesture, it recognizes that the cross-device transmission conditions are met and executes operation S201. The specific cross-device transmission conditions can be configured according to actual usage and the terminal type corresponding to the first terminal. It should be noted that the number of cross-device transmission conditions can be one or more.

[0297] For example, Figure 3(a) shows a schematic diagram of a scenario for cross-device navigation data transmission provided in an embodiment of this application. Referring to Figure 3(a), a user holds a smartphone, and there is a vehicle equipped with an in-vehicle terminal within the vicinity of the smartphone. A navigation application (i.e., a first navigation application) is launched in the foreground of the smartphone. In this case, the user can initiate a swipe operation in the direction of the in-vehicle terminal in the operation interface corresponding to the navigation application, i.e., swipe trajectory 31. This swipe operation is a pre-set trigger for cross-device navigation data transmission. Therefore, when the smartphone detects that the user has initiated the above-mentioned long swipe operation, it determines that the preset cross-device transmission conditions are met and executes the operation S201.

[0298] For example, in a scenario involving a first terminal, there are multiple terminals capable of cross-device data transmission. Figure 3(b) illustrates a scenario of cross-device navigation data transmission provided by an embodiment of this application. As shown in Figure 3(b), in this scenario, a user holds a smartphone, and there are multiple vehicles equipped with in-vehicle terminals within the vicinity of the smartphone, i.e., multiple second terminals exist. In this case, the second terminal required for navigation task synchronization by the first terminal can be determined through any one of the following three methods:

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

[0300] Method 2: Determine the second terminal to be synchronized for navigation tasks based on the relative position between each second terminal and the first terminal. The first terminal can obtain the relative positional relationship with each second terminal through wireless signal strength or distance sensors, and determine the second terminal to be synchronized for navigation tasks based on the above relative positional relationship. This relative positional relationship can be the distance and orientation between the first terminal and each second terminal. For example, the first terminal can obtain the distance between itself and each second terminal and select the second terminal with the closest distance as the second terminal to be synchronized for navigation tasks. For example, if the distance between the smartphone and the in-vehicle terminal in vehicle A is 2m, the distance between the smartphone and the in-vehicle terminal in vehicle B is 1m, and the distance between the smartphone and the in-vehicle terminal in vehicle C is 1.5m, in this case, the first terminal can also select the in-vehicle terminal in vehicle B as the second terminal to be synchronized for navigation tasks.

[0301] Method 3: Determine the second terminal to be synchronized for navigation tasks based on the default priority order. The first terminal has pre-configured corresponding synchronization priorities for each second terminal. If multiple second terminals are detected simultaneously within the range, the second terminal with the highest synchronization priority can be selected as the second terminal to be synchronized. For example, Table 1 shows the correspondence table of synchronization priorities pre-stored by the first terminal. As shown in Table 1, the synchronization priority of the in-vehicle terminal in vehicle A is 1, the synchronization priority of the in-vehicle terminal in vehicle B is 2, and the synchronization priority of the in-vehicle terminal in vehicle C is 3. In this case, if the smartphone can simultaneously search for the above three in-vehicle terminals, since the synchronization priority of the in-vehicle terminal in vehicle A is the highest, the in-vehicle terminal in vehicle A will be selected as the second terminal for navigation task synchronization.

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

[0303] Table 1

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

[0305] In this embodiment, the first terminal can obtain navigation data related to the navigation task from the first navigation application through the first navigation flow module. This navigation data includes, but is not limited to, the navigation destination, navigation start point, route points, navigation route rules, and current location. Specifically, the route points are: between the navigation start point and the navigation destination, the user can set one or more route points. The generated navigation route will start from the navigation start point and end at the navigation destination, passing through each route point. The navigation route rules are specifically used to determine the user's preferences when generating the navigation route, such as different preferences like "highway priority," "least congested sections," or "lowest cost," so that the navigation application can generate a corresponding navigation route based on user preferences and real-time traffic conditions.

[0306] In one possible implementation, the first navigation transfer module can be a background program running within the application layer of the first terminal. In this case, the first navigation transfer module can obtain permission to retrieve navigation data from the first navigation application within the application layer. When it detects that the cross-device transmission conditions are met, it can obtain the corresponding navigation data from the first navigation application based on this permission.

[0307] In one possible implementation, the first navigation flow module may also run within the application framework layer of the first terminal, providing the first navigation application with a corresponding application programming interface (API) for navigation task synchronization, and obtaining corresponding navigation data from the first navigation application through the API.

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

[0309] See also Figure 2Furthermore, as another embodiment of this application, since the first terminal needs to respond to the user-initiated navigation task through the first navigation application before S201, based on this, before the first terminal obtains navigation data from the first navigation application through the first navigation transfer module if the preset cross-device transmission conditions are met, the following operations are also included: S200.1 to S200.3, which are described in detail below:

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

[0311] In this embodiment, the first terminal can run a first navigation application in the foreground. The user can initiate navigation operations within the interface generated by the first navigation application, such as inputting a navigation destination to generate a corresponding navigation task. During the execution of the navigation task, the first navigation application can generate corresponding navigation data. The user-initiated navigation operation can be a touch operation. For example, Figure 4a A schematic diagram illustrating the initiation of a navigation task according to an embodiment of this application is shown. See also... Figure 4a As shown in (1), the first terminal is specifically a smartphone, which has a navigation application installed, namely application 41. The user can launch application 41 by clicking the icon corresponding to application 41 and generate the corresponding navigation operation interface, such as... Figure 4a As shown in (2) above. The first terminal can receive the navigation destination entered by the user in area 42 (specifically the destination), such as "New World Plaza". If application 41 has obtained the location permission of the first terminal in advance, it can obtain the current location information of the first terminal through the location module configured in the first terminal and automatically fill the current location information into the starting point, i.e., area 43. Of course, the user can also adjust the starting point according to the actual situation, i.e., by clicking on area 43 to enter the corresponding starting point. Area 44 can select the navigation scenario to be navigated, such as driving scenario, public transportation scenario and walking scenario, etc. Figure 4a In (2), the driving scenario is selected. After all the above navigation tasks are set, the corresponding navigation task can be generated by clicking control 45 (i.e., start navigation). The first navigation application in the first terminal will then start navigating for the user. Figure 4a As shown in (3) of the text.

[0312] In one possible implementation, the user-initiated navigation operation described above can also be a voice navigation operation. For example, Figure 4b A schematic diagram illustrating the initiation of a navigation task according to another embodiment of this application is shown. See also Figure 4bAs shown in (1), the first terminal is specifically a smartphone. The navigation operation interface of the smartphone includes a voice navigation control 46. If the smartphone detects that the user clicks the control 46, it will enter the voice navigation trigger mode, such as... Figure 4b As shown in (2) above. In this state, the smartphone listens for voice commands issued by the user. For example, if the user says "I want to go to tourist attraction A", the smartphone recognizes that the user needs to navigate to tourist attraction A and generates a navigation route from the current location to tourist attraction A, such as... Figure 4b As shown in (3) of the text.

[0313] For example, Figure 4c A schematic diagram illustrating the initiation of a navigation task according to another embodiment of this application is shown. See also... Figure 4c As shown in (1), the first terminal is specifically a vehicle-mounted terminal, which can automatically enter the navigation interface after startup, such as... Figure 4c As shown in (1) above. The vehicle terminal can be configured with a corresponding voice activation command. If the system detects that the user has spoken the corresponding voice activation command, such as "Hi, my car," it will enter the voice navigation trigger mode. In this state, the vehicle terminal will listen to the user's voice commands. For example, if the user says "I want to go to tourist attraction A," the vehicle terminal will generate a navigation route to tourist attraction A, such as... Figure 4c As shown in (2) of the text.

[0314] In one possible implementation, the default scenario for the aforementioned navigation scenarios can be determined based on the terminal type. For example, if the terminal type is an in-vehicle terminal, the navigation scenario in the aforementioned navigation application can be selected as a driving scenario by default; if the terminal type is a portable terminal, the navigation scenario in the aforementioned navigation application can be selected as a walking scenario or a public transportation scenario by default, etc. The specific correspondence between the default scenario and the terminal type can be set according to the actual situation.

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

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

[0317] In S200.3, the first terminal responds to the service registration instruction by adding the first navigation application to the navigation synchronization application list and setting the first navigation flow module to the start state; the start state is used to send the navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission conditions are met.

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

[0319] In one possible implementation, the first terminal may have multiple navigation applications installed, such as Amap, Baidu Maps, and Google Maps. If a user launches these multiple navigation applications while using the first terminal, each navigation application sends a service registration instruction to the first navigation flow module. Therefore, the navigation synchronization application list stored in the first navigation flow module records multiple navigation applications. For example, Table 2 shows a schematic diagram of the navigation synchronization application list provided in an embodiment of this application. Referring to Table 2, after any navigation application in the first terminal launches and executes the corresponding navigation task, it sends a service registration instruction to the first navigation flow module. The first navigation flow module can associate and store the time of each received service registration instruction with the corresponding application identifier in the above-mentioned navigation synchronization application list. The first terminal can determine the launched navigation applications and the registration time of each navigation application through the navigation synchronization application list. If a navigation application performs multiple navigation tasks during the startup of the first terminal, it can send multiple service registration instructions to the first navigation flow module, as shown in items 1 and 4 of Table 2. For example, the Baidu Maps navigation application sent service registration instructions to the first navigation flow module at 14:00 and 17:11. In this case, the first navigation flow module can obtain the corresponding navigation data from the first navigation application with the latest registration time, such as Baidu Maps with a registration time of 17:11 in Table 2. Optionally, the first navigation flow module can obtain the corresponding navigation data from the currently running first navigation application in the foreground.

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

[0321] Table 2

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

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

[0324] In one possible implementation, the status switch of the first navigation flow module can also be manually configured by the user.

[0325] For example, Figure 5 This diagram illustrates the setting of the status switch of a first navigation flow module according to an embodiment of this application. (See also...) Figure 5 As shown in (a), the first terminal responds to a navigation operation initiated by the user, such as clicking the navigation control 51 in the first navigation application, and generates a navigation task corresponding to that navigation operation. At this time, the first terminal can generate a prompt box 52 to prompt the user whether to enable the navigation task synchronization service, such as... Figure 5 As shown in (b), the prompt box 52 contains an agree control 53 and a refuse control 54. If the first terminal detects that the user clicks the above-mentioned confirmation control 53, it recognizes that the user has confirmed the start of the navigation task synchronization service. Therefore, the above-mentioned first navigation flow module will be set to the on state.

[0326] In another implementation, the navigation task synchronization switch of the first navigation flow module of the first terminal can be manually configured in the terminal's settings interface. For example, Figure 5 (c) shows the main interface of the first terminal, which includes a settings icon 55. After the first terminal detects that the user clicks the settings icon 54, it can generate the corresponding settings interface, such as... Figure 5 As shown in (d), in this settings interface, the user can configure multiple items on the first terminal, such as enabling the Bluetooth module, selecting the peripheral device connected to the Bluetooth module, or configuring the wireless network. This includes a switch setting for navigation task synchronization, i.e., control 56. The first terminal can respond to user-initiated click operations to change the state of the first navigation flow module, such as... Figure 5 In (d), the first navigation flow module is in the open state. If a user click operation on control 56 is detected, the first navigation flow module can be changed from the open state to the closed state.

[0327] In this embodiment, before the first terminal initiates a navigation operation on the first navigation application, it will automatically send a corresponding service registration instruction to the first navigation flow module. The first navigation flow module can add the first navigation application to the corresponding navigation synchronization application list and automatically set the first navigation flow module to the enabled state, thereby reducing the need for users to manually set the state of the first navigation flow module and improving the setting efficiency.

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

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

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

[0331] The first terminal can have different types of navigation applications installed. Since not all navigation applications support navigation task synchronization, the first navigation flow module can record a whitelist of applications that support navigation task synchronization or a blacklist of applications that do not support navigation task synchronization. The first terminal determines whether the first navigation application that initiates the navigation task is in the above application whitelist or in the corresponding application blacklist, thereby determining whether the first navigation application has the permission to synchronize navigation tasks. If the first navigation application is in the application whitelist (or not in the application blacklist), then the first navigation application is identified as having the permission to perform navigation tasks.

[0332] Regarding condition 2, since the first terminal can perform synchronous operations on different applications, in order to determine whether the current task to be synchronized is a navigation task, when the cross-device transmission condition is met, it can detect whether the first navigation application is an application running in the foreground. This will determine that the first terminal is executing a user-initiated navigation task and can view the navigation information output by the first navigation application in real time. Based on this, the navigation task can be synchronized, and the navigation task executed in the first navigation application can be synchronized to the navigation application of another terminal, namely the second navigation application of the second terminal.

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

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

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

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

[0337] In one possible implementation, the first navigation transfer module can preprocess the navigation data. This preprocessing includes, but is not limited to, data cleaning, data standardization, and / or data format conversion. Since 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 during cross-device navigation task synchronization, the first navigation transfer module can preprocess the navigation data to enable cross-device and cross-application navigation data transmission and thus complete navigation task synchronization. This allows the generated navigation synchronization information to be read by the second navigation application on the second terminal. The method for preprocessing the navigation data to generate the corresponding navigation synchronization information can be as follows:

[0338] Method 1: Data Standardization Processing. The first navigation flow module can convert navigation data into standard format data compatible with different types of navigation applications. The first navigation flow module stores a corresponding standard format template, which contains multiple information items. For example, Table 3 shows a schematic diagram of the standard format template provided in an embodiment of this application. As shown in Table 3, the standard format template configures corresponding fields for different information items. The first navigation flow module can extract the parameter values ​​corresponding to each information item from the navigation data and fill them into the corresponding fields to generate the corresponding standard format data, i.e., the navigation synchronization information mentioned above. The other end can obtain the corresponding data from the corresponding fields, thereby realizing cross-device and cross-application navigation data synchronization. The header can limit the data length corresponding to the standard format data. Since the number of intermediate locations is a variable, the more intermediate locations there are, the longer the data length of the corresponding standard format data. Therefore, the data length of the standard format data can be defined through the header, so as to ensure the standardization of the data format while also carrying certain custom content.

[0339] First Origin destination Navigation rules Midway Point 1 … 1 byte 2 bytes 2 bytes 2 bytes 2 bytes …

[0340] Table 3

[0341] Method 2: Data Format Conversion. The first navigation processing module can convert the navigation data obtained from the first navigation application into a data format compatible with the second navigation application, i.e., the aforementioned navigation synchronization information. In this case, the first terminal can send a navigation application detection request to the second terminal. The second terminal can respond to the navigation application detection request by adding the application identifier of the second navigation application to the response information. The first terminal parses the response information to obtain the application identifier of the second navigation application, determines the data format matched by the second navigation application, and converts the navigation data into the aforementioned data format, thereby generating the corresponding navigation synchronization information.

[0342] See also Figure 2 Furthermore, as another embodiment of this application, before the first terminal sends the navigation synchronization information to the second terminal, steps S202.1 to S202.2 may be included, as specifically described below:

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

[0344] In this embodiment, the first terminal can send an application list retrieval request to the second terminal. The application list retrieval request is specifically used to determine the navigation applications installed on the second terminal. In response to the application list retrieval request, the second terminal can add the application identifiers of each navigation application installed locally to the above-mentioned navigation application list and send it back to the first terminal. Since the second navigation application that needs to perform navigation task synchronization is also installed on the second terminal, the above-mentioned navigation application list also includes the second navigation application.

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

[0346] In this embodiment, after obtaining the list of navigation applications, the first terminal can determine whether the second terminal has an application installed that can perform cross-device navigation tasks, i.e., an application with the permission to transmit navigation data across devices with the first navigation application. If such an application exists, the first terminal can send navigation synchronization information to the second terminal. Conversely, if the second terminal does not have an application installed that can perform cross-device navigation tasks, even if the first terminal sends navigation synchronization information to the second terminal, the second terminal cannot synchronize navigation tasks based on the navigation synchronization information. Therefore, the first terminal will not send the aforementioned navigation synchronization information to the second terminal.

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

[0348] For example, Figure 6 This diagram illustrates a prompt for application installation on a second terminal according to an embodiment of this application. See also... Figure 6As shown in (a), the second terminal can specifically be an in-vehicle terminal. After the first terminal sends an application installation command to the second terminal, the second terminal can generate an application installation prompt message to ask the user whether they agree to install a navigation application that matches the first navigation application. This application installation prompt message includes an "agree" control 61 and a "decline" control 62. If the user clicks the "agree" control 61, the installation process of the navigation application capable of synchronizing navigation tasks proceeds, such as... Figure 6 As shown in (b) above, the installation progress and installation stage are displayed. After the second terminal completes the installation of the matching navigation application, it can resend a list of navigation applications to the first terminal. At this time, the first terminal can recognize that the list of navigation applications contains navigation applications that match the first navigation application and send the navigation synchronization information to the second terminal.

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

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

[0351] In this embodiment, a communication connection is established between the first terminal and the second terminal. This communication connection can be a wireless connection, such as a Bluetooth connection, a Near Field Communication (NFC) connection, or a Wireless Fidelity (WIFI) connection. Based on this communication connection, the second terminal can receive navigation synchronization information sent by the first terminal. Specifically, the first terminal can use the first navigation transfer module to call the wireless communication interface (i.e., the communication protocol corresponding to the wireless communication interface) to send navigation synchronization information to the second terminal. Correspondingly, the second terminal can also use the second navigation transfer module to call the corresponding wireless communication interface to receive the aforementioned navigation synchronization information.

[0352] See also Figure 2 As another embodiment of this application, after receiving the navigation synchronization information sent by the first terminal, the second terminal can also locally determine whether there are navigation applications capable of responding to navigation task synchronization. After the second terminal receives the navigation synchronization information sent by the first terminal, it may further include:

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

[0354] In S203.2, if the second terminal detects that there is a navigation application matching the first navigation application in the navigation application list, it will use the navigation application matching the first navigation application as the second navigation application and execute the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation transfer module; the navigation application matching the first navigation application is specifically an application that has the permission to transmit navigation data across devices with the second navigation application.

[0355] In this embodiment, besides the first terminal determining that the second terminal has a navigation application installed that can synchronize navigation tasks, the second terminal can also perform a feasibility check on its local navigation application for task synchronization, 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 there is a navigation application that matches the first navigation application among the locally installed navigation applications. If the second terminal has a navigation application that matches the first navigation application installed, that is, if there is a matching navigation application in the navigation application list of the second terminal, then the second terminal can use the matching navigation application as the navigation application for navigation task synchronization. Therefore, the second navigation flow module can send the received navigation synchronization information to the second navigation application.

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

[0357] In one possible implementation, before transmitting the navigation synchronization information to the second navigation application via the second navigation transfer module, the navigation synchronization information can be preprocessed to ensure compatibility with the second navigation application. This preprocessing includes, but is not limited to, data cleaning, data standardization, and / or data format conversion. The specific preprocessing method is similar to the preprocessing method used by the first terminal for navigation data; a detailed description can be found in the relevant description in S202, and will not be repeated here.

[0358] In one possible implementation, if multiple navigation applications are installed on the second terminal, and all of these applications match the first navigation application on the first terminal, the second terminal can determine the navigation application to be synchronized (i.e., the second navigation application) based on the startup time of each local navigation application. For example, the second navigation flow module can select the most recently launched navigation application as the second navigation application for navigation task synchronization. Optionally, in addition to determining the navigation application for synchronization based on startup time, the second navigation flow module can also determine the user's frequently used navigation applications based on the usage frequency of each navigation application installed on the second terminal, and use these frequently used applications as the second navigation application.

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

[0360] In this embodiment, after the second navigation flow module of the second terminal sends navigation synchronization information to the second navigation application, the second navigation application sets a navigation task corresponding to the first navigation application in the first terminal, thereby realizing navigation task synchronization between the first navigation application and the second navigation task. The aforementioned updating of the navigation task of the second navigation application includes two cases:

[0361] Scenario 1: The second navigation application does not execute the navigation task. In this case, the second terminal can create the corresponding navigation task based on the above navigation synchronization information.

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

[0363] For example, Figure 7 A schematic diagram illustrating a modification of the navigation task provided in one embodiment of this application is shown. See also... Figure 7 As shown in (a), before the second terminal synchronizes its navigation task, it is executing a navigation task to location A. At this time, the first terminal synchronizes its navigation task (the navigation task to location B) with the second terminal, sending the corresponding navigation synchronization information to the second terminal. The second terminal can then update the navigation task within its navigation application based on this synchronization information, thereby changing the destination from location A to location B. Figure 7 As shown in (b) of the diagram.

[0364] See also Figure 2Furthermore, as a possible implementation, before synchronizing the navigation task with the second navigation application, the user can be asked whether they agree to the synchronization operation. Based on this, the above S204 can specifically include the following steps:

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

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

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

[0368] For example, Figure 8 This illustration shows a schematic diagram of a navigation task update according to an embodiment of this application. After receiving navigation synchronization information, the second navigation application on the second terminal can parse the navigation synchronization information, determine the navigation destination specified in the information, and generate a corresponding task update prompt based on that destination. For example, if the navigation destination is tourist attraction B, a task update prompt will be generated. The content of this prompt may be displayed as "Continue the navigation task on phone UserA?", where UserA is the phone identifier of the smartphone, allowing the user to determine which device's navigation task should be synchronized to the second terminal. Figure 8 As shown in (a) above; the above prompt message can also be displayed as "Continue navigation task to tourist attraction B?", so that the user can confirm the specific destination of this updated navigation task. This task prompt message includes a confirmation control 81 and a cancellation control 82. If the second terminal detects that the user clicks the confirmation control 81 in the second navigation application, it can update the navigation task according to the navigation destination, such as... Figure 8 As shown in (b), after the user clicks the confirmation control 81, the navigation destination in the second navigation application can be changed to tourist attraction B. If the user clicks the cancel control 82, the original navigation destination will be retained, as shown in (b). Figure 8 As shown in (c), the navigation destination in the second navigation application remains tourist attraction A.

[0369] In this embodiment of the application, by generating corresponding task update prompt information to notify the user whether they agree to update the navigation task, the occurrence of missynchronization can be avoided, thereby improving the accuracy of navigation task synchronization.

[0370] See also Figure 2 Furthermore, as another embodiment of this application, after the second terminal updates the navigation task of the second navigation application according to the navigation synchronization information, it can notify the first terminal that the navigation task has been synchronized. That is, after S204, the following steps may also be included:

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

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

[0373] In this embodiment, after the second terminal completes the navigation task update, it can send a navigation synchronization completion message to the first terminal through the second navigation flow module. After receiving the navigation synchronization completion message from the second terminal, the first terminal can determine that the second terminal has completed the navigation task synchronization, that is, the navigation task has been transferred from the first terminal to the second terminal for execution. In this case, the first terminal can end the navigation task being executed locally. Therefore, the first navigation flow module can send an end command to the first navigation application. After receiving the end command, the first navigation application can stop the navigation task being executed in the first navigation application on the first terminal, thus realizing the transfer of the navigation task.

[0374] For example, Figure 9 A schematic diagram illustrating the termination of a navigation task according to an embodiment of this application is shown. See also... Figure 9 As shown in (a), after the first terminal sends navigation synchronization information to the second terminal through the first navigation transfer module, it can display a "Synchronizing" message locally and show the corresponding synchronization progress based on the normal synchronization time and the current waiting time. If the first terminal receives navigation synchronization completion information sent by the second terminal, it can generate a "Synchronization Complete" message, such as... Figure 9 As shown in (b), this indicates to the user that the second terminal has completed the navigation task synchronization. In this case, the first terminal can directly end the navigation task, for example, by exiting the first navigation application and returning to the first terminal's main interface, or by returning to the application's initial interface, such as... Figure 9As shown in (d) above. Optionally, after receiving the navigation synchronization completion information, the first terminal may generate a prompt message that includes an end confirmation control 91 asking the user whether to end the navigation task within the first navigation application, such as... Figure 9 As shown in (c), if the first terminal detects that the user clicks the aforementioned end confirmation control 91, it can end the navigation task of the first navigation application within the first terminal and return to the application's initial interface, such as... Figure 9 As shown in (d) above. Of course, the end confirmation control 91 can also display a corresponding valid waiting time. If the first terminal does not receive a user click on the above end confirmation control 91 within the valid waiting time, it can also end the navigation task being executed by the first navigation application in the first terminal.

[0375] In one possible implementation, the first terminal can be configured with a maximum waiting time. If the first terminal sends navigation synchronization information to the second terminal and does not receive navigation synchronization completion information from the second terminal within the maximum waiting time, the navigation task synchronization to the second terminal is identified as having failed. In this case, the first terminal can display a synchronization failure prompt message. For example, Figure 10 A schematic diagram illustrating a synchronization failure response according to an embodiment of this application is shown. See also... Figure 10 As shown in (a), if the first terminal does not receive navigation synchronization completion information within the maximum waiting time, it can display a corresponding synchronization failure message in the first navigation application. This message 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 clicks control 101, it resends navigation synchronization information to the second terminal so that the second terminal can re-synchronize the navigation task based on this information. If the first terminal detects that the user clicks control 102, it can generate terminal identifiers for other synchronizable terminals, such as... Figure 10 As shown in (b), the user can select a new terminal from the displayed terminals to synchronize the navigation task and send navigation synchronization information to it to achieve navigation task synchronization. If the first terminal detects that the user clicks control 103, it indicates that the navigation synchronization operation has been performed and returns to the original navigation task interface.

[0376] As can be seen from the above, the cross-device navigation task synchronization method provided in this application embodiment can automatically obtain navigation data of the already started navigation task from the first navigation application through the first navigation flow module configured locally on the first terminal when the first terminal detects that the cross-device transmission conditions are met. The first navigation flow module then generates navigation synchronization information corresponding to the navigation data and sends the navigation synchronization information to the second terminal, thus realizing cross-device transmission of navigation data. After receiving the navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through its local second navigation flow module. The second terminal can then update the navigation task of the second navigation application based on the navigation synchronization information, achieving cross-device navigation task synchronization. Compared with existing navigation technologies, this application can achieve cross-device navigation task synchronization. In scenarios requiring cross-device navigation, users do not need to repeatedly set tasks for the terminal's navigation application. Instead, the navigation flow module can automatically transfer navigation data to update the navigation task in the navigation application, thereby greatly improving the efficiency of navigation task setting and reducing repetitive user operations. On the other hand, after the first navigation transfer module in the first terminal obtains navigation data from the first navigation application, it does not directly send the navigation data to the second navigation transfer module of the second terminal. Instead, it converts the data into corresponding navigation synchronization information. This navigation synchronization information can be transmitted between navigation transfer modules of different terminals and then transmitted to the second navigation application through the second navigation transfer module. This is not a direct transmission between navigation applications within two terminals. Therefore, it is not necessary for the first terminal and the second terminal to have the same navigation application installed. This enables cross-device and cross-application navigation data transfer and further improves the application scope of navigation task synchronization.

[0377] Example 2:

[0378] Compared to Embodiment 1, the cross-device transmission condition in Embodiment 2 is a touch operation transmission condition, specifically describing the implementation process when two terminals trigger the synchronization of a navigation task through a touch operation. In this embodiment, the first terminal can be the terminal that initiates the touch operation (i.e., the terminal that actively approaches the other terminal, such as a user holding the first terminal and initiating a touch operation to the second terminal), or it can be a terminal that passively responds to the touch operation, such as a user controlling the second terminal to initiate a touch operation to the first terminal. For example, the following description uses a smartphone as the first terminal and an intelligent vehicle control terminal (referred to as an in-vehicle terminal) installed in a vehicle as the example.

[0379] In this embodiment, the user holds a smartphone and controls it to perform a touch operation with the in-vehicle terminal. Both the smartphone and the in-vehicle terminal are equipped with NFC modules, enabling them to establish a near-field communication connection for data exchange. For example, Figure 11 The diagram illustrates an interaction of a cross-device navigation task synchronization method according to an embodiment of this application. This synchronization method is applied to touch-triggered scenarios, and the specific interaction process is as follows:

[0380] In S1103, the vehicle terminal responds to a touch operation with the smartphone by sending a communication tag to the smartphone via the vehicle terminal's near-field communication module.

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

[0382] For example, Figure 12 This illustration shows a schematic diagram of a touch scenario between an in-vehicle terminal and a smartphone according to an embodiment of this application. See also... Figure 12 As shown, the user holds a smartphone and touches it with the vehicle terminal to activate the NFC modules in both terminals. The NFC modules then establish a near-field communication connection between the two terminals to transmit communication tags and subsequent navigation synchronization information.

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

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

[0385] Furthermore, as another embodiment of this application, before the vehicle terminal responds to the touch operation initiated by the smartphone, the vehicle terminal can pre-write the communication tag into the near-field communication module of the vehicle terminal, that is, before S1103, it can include S1101 to S1102, as specifically described below:

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

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

[0388] In this embodiment, when preset tag writing conditions are met, the vehicle-mounted terminal can send a tag writing request to the tag service through the second navigation flow module configured within the vehicle-mounted terminal, so as to write the corresponding communication tag to the near-field communication module of the vehicle-mounted terminal. Specifically, the aforementioned tag writing conditions can be vehicle-mounted terminal startup. For example, when the vehicle starts, the vehicle-mounted terminal installed in the vehicle will start simultaneously. At this time, the vehicle-mounted terminal will recognize that the preset tag writing conditions are met and execute the operation in S1101.

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

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

[0391] In S1104, the smartphone responds to the communication tag, activates the first navigation transfer module, and obtains the navigation data from the first navigation application through the first navigation transfer module.

[0392] In this embodiment, after receiving the communication tag sent by the vehicle terminal, the smartphone can parse the communication tag. If it detects that the communication tag carries a navigation synchronization start identifier, it can start the first navigation transfer module configured in the smartphone and obtain navigation data from the first navigation application through the first navigation transfer module.

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

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

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

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

[0397] In S1107, the smartphone generates navigation synchronization information for the navigation data through the first navigation transfer module.

[0398] Since the above-mentioned S1107 is implemented in exactly the same way as S202 in Embodiment 1, the specific description can be found in the relevant description of S202, and will not be repeated here.

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

[0400] Since the implementation of S1108 above is exactly the same as that of S203 in Embodiment 1, the specific description can be found in the relevant description of S203, and will not be repeated here. That is, S1108 can also determine whether a navigation application matching the first navigation application is installed locally. If a matching navigation application exists, it is identified as the second navigation application.

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

[0402] Optionally, S1109 may also include:

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

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

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

[0406] Optionally, S1109 may also include:

[0407] In S1110, the vehicle terminal sends navigation synchronization completion information to the smartphone through the second navigation transfer module;

[0408] In S1111, in response to the navigation synchronization completion information, the smartphone transmits an end command for the navigation task to the first navigation application through the first navigation flow module, thereby stopping the navigation task of the first navigation application.

[0409] Since S1110 is implemented in exactly the same way as S205 in Embodiment 1, and S1111 is implemented in exactly the same way as S206 in Embodiment 1, for detailed descriptions, please refer to the relevant descriptions of S205 and S206, which will not be repeated here.

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

[0411] Example 3:

[0412] Compared with Embodiment 1, the specific application scenario of this embodiment is to synchronize the navigation task on the user terminal carried by the user to the intelligent vehicle control terminal installed in the vehicle when the vehicle is started. Based on this, the first terminal is the user terminal carried by the user, and the second terminal is the vehicle terminal. Figure 13 An interactive schematic diagram of a navigation task synchronization method provided in an embodiment of this application is shown, and the specific description is as follows:

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

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

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

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

[0417] Compared with Embodiment 1, this embodiment further includes the following step before the user terminal obtains navigation data from the first navigation application through the first navigation transfer module, provided that the user terminal meets the preset cross-device transmission conditions:

[0418] In S1304, if the vehicle terminal detects a start event related to the vehicle, it establishes a communication connection with the user terminal.

[0419] In this embodiment, the application scenario involves a user switching from walking to driving after entering the vehicle. This requires synchronizing the navigation task on the user's terminal to the vehicle's onboard terminal. Therefore, the triggered event is the detection of vehicle startup. These startup events include vehicle door opening, vehicle ignition, or vehicle power button pressing, which can be used to determine the vehicle startup time. When the onboard terminal detects a vehicle startup event, it can recognize that the user's navigation scenario has changed. Therefore, the onboard terminal can establish a communication connection with the user's terminal. This communication connection can be established through a near-field communication module, such as a Bluetooth module, a Bluetooth Low Energy module, or a Wi-Fi module, which enables near-field wireless communication.

[0420] In this embodiment, the action of triggering event recognition is delegated to the vehicle terminal because it is difficult for the user terminal to identify whether the user has started the vehicle when synchronizing the navigation task to the vehicle terminal. However, by detecting the vehicle start event through the vehicle terminal, it is possible to determine more easily and accurately whether the user's navigation scenario has switched to the driving scenario. This can improve the accuracy of navigation task synchronization while reducing the difficulty of recognition.

[0421] In this embodiment, the user terminal and the vehicle terminal establish a wireless communication connection. If a wireless communication connection has been previously established between the user terminal and the vehicle terminal, both the user terminal and the vehicle terminal have recorded their connection information, which includes, but is not limited to, device identifier, connection key, and wireless network identifier. In this case, the vehicle terminal and the user terminal can establish a communication connection based on the recorded connection information.

[0422] For example, a Bluetooth communication connection is established between the user terminal and the vehicle terminal. The user terminal records the vehicle terminal's Bluetooth connection information, and the vehicle terminal also adds the user terminal to its authorized device list. Similarly, the vehicle terminal also stores the user terminal's Bluetooth connection information, and the user terminal also adds the vehicle terminal to its local authorized device list. If the vehicle terminal detects the user terminal's Bluetooth signal after a door opening event, it can search for the user terminal's Bluetooth signal. If detected, it sends a Bluetooth connection request to the user terminal using the user terminal's Bluetooth connection information. Since the vehicle terminal has the user terminal's authorized device list, the user terminal will accept the Bluetooth connection request and establish a Bluetooth communication connection with the vehicle terminal.

[0423] Furthermore, as another embodiment of this application, the method for establishing a communication connection between the user terminal and the vehicle terminal can be specifically implemented through the following steps:

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

[0425] In this embodiment, after detecting a vehicle door opening event, the vehicle-mounted terminal can search for wireless signals in the current scene via its wireless communication module. Based on the searched wireless signals, it can determine the connection status of each connected registered terminal in a pre-stored list of registered devices and feed the collected results back to the vehicle-mounted terminal's second navigation processing module. The second navigation processing module can then perform corresponding operations based on the connection status of each registered terminal. If a registered terminal's wireless signal is found in the current scene, the registered terminal can be identified as being in a connectable state, i.e., online. Conversely, if a registered terminal's wireless signal is found in the current scene, the registered terminal can be identified as being in a disconnectable state, i.e., offline.

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

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

[0428] In S1304.3, if the vehicle terminal detects that the user terminal is not in the registered device list, or the user terminal is in the registered device list and the connection status of the user terminal is unconnectable, then the vehicle terminal sends a wake-up command to the user terminal through the near-field communication module of the vehicle terminal.

[0429] In this embodiment, if the user terminal is offline, there are two possibilities. The first possibility is that the user terminal is in a screen-off or standby state, and the wireless communication module within the user terminal has not been woken up. The second possibility is that the user terminal has established a wireless communication connection with another terminal, and therefore the corresponding connection status is an unconnectable state. In this case, the vehicle terminal can wake up the mobile phone via a soft bus, that is, by sending a wake-up command to the user terminal through the near-field communication module of the vehicle terminal to adjust the connection status of the user terminal.

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

[0431] In S1304.5, the user terminal responds to the wake-up command by sending a wireless connection request to the vehicle terminal to establish the communication connection with the vehicle terminal.

[0432] In this embodiment, the user terminal receives the wake-up command through its local near-field communication module (i.e., the user terminal's near-field communication module), and then adjusts the connection status of the local near-field communication module to a connectable state. In this case, the user terminal can establish a communication connection with the vehicle terminal. Therefore, it can send a wireless connection request to the vehicle terminal through its near-field communication module. After receiving the wireless connection request, the vehicle terminal can update the device information of the user terminal in its locally stored list of registered devices and establish a communication connection with the user terminal.

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

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

[0435] In this embodiment, after establishing a communication connection with the user terminal, the vehicle terminal can identify whether it has a navigation application that supports navigation task synchronization installed. Navigation applications that support navigation task synchronization are recorded in the aforementioned navigation synchronization application list. Therefore, after establishing a communication connection with the user terminal, the vehicle terminal can identify whether the navigation application list is empty. If the navigation application list is not empty, it indicates that the vehicle terminal supports navigation task synchronization. In this case, the vehicle terminal can obtain the setting status corresponding to the second navigation flow module.

[0436] In this embodiment, in addition to requiring the navigation application installed in the vehicle terminal to support the synchronous operation of navigation tasks, it is also required that the user has enabled the synchronous service of navigation tasks. In this case, the vehicle terminal needs to identify the setting status of the second navigation transfer module. If its setting status is in the started state, it is recognized that the user has enabled the synchronous service of navigation tasks and the operation of S1306 is executed; otherwise, if the second navigation transfer module is identified as being in the closed state, it means that the user has not enabled the synchronous service of navigation tasks. In this case, the vehicle terminal will end the synchronous operation of navigation tasks.

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

[0438] In this embodiment, when the vehicle terminal detects that the second navigation flow module is in an activated state, it can send a navigation flow notification to the user terminal, thereby initiating the synchronization process of the navigation task. For example, Figure 14 A schematic diagram of the interface of an in-vehicle terminal according to an embodiment of this application is shown. After the in-vehicle terminal is started, if it detects that the user terminal is in a connectable state, it can directly establish a communication connection with the user terminal and display the current connection status on the interface, such as... Figure 14As shown in (a), this interface displays the terminal identifier of the user terminal that the in-vehicle terminal is connecting to, such as "UserA," and the current connection status, such as "Connected." At this time, if the in-vehicle terminal has an application that supports navigation task synchronization installed and the navigation task synchronization service is enabled, a second navigation application that supports navigation task synchronization and is installed locally can be launched, such as... Figure 14 As shown in (b) above, it displays the current synchronization progress, such as the message 141, "Synchronizing with navigation tasks on User A".

[0439] In one possible implementation, if the user terminal and the vehicle terminal are logged into the same user account, the communication connection established between the user terminal and the vehicle terminal is specifically a server-based communication connection, meaning that the user terminal and the vehicle terminal can interact with each other based on the server.

[0440] For example, the transmission of navigation flow notifications between the user terminal and the vehicle terminal will be used as an example for illustration. Figure 15 A flowchart illustrating the three-way interaction between a user terminal, an in-vehicle terminal, and a server according to an embodiment of this application is shown. See also... Figure 15 As shown, when a user's account is logged into the in-vehicle terminal and the terminal is detected to be in a connectable state (i.e., the same user account is logged in and the account is online), the in-vehicle terminal can send the aforementioned navigation transfer notification to the server. This notification carries the account identifier of the user account logged into the in-vehicle terminal. Upon receiving the navigation transfer notification, the server forwards it to another terminal logged into the same user account, namely the aforementioned user terminal. Therefore, the communication connection between the user terminal and the vehicle terminal can be a server-based connection.

[0441] Compared with Embodiment 1, in this embodiment, if the user terminal meets the preset cross-device transmission conditions, the acquisition of navigation data from the first navigation application through the first navigation transfer module specifically includes S1307 to S1308:

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

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

[0444] In this embodiment, after receiving the navigation flow notification from the vehicle terminal, the user terminal triggers the navigation task synchronization process, obtaining the corresponding navigation data from the first navigation application through the first navigation flow module. Of course, the user terminal can also perform pre-condition checks, such as whether the first navigation application has synchronization permissions for navigation tasks and whether it is allowed in the foreground. If so, the first navigation flow module can obtain navigation data from the first navigation application. The specific method by which the first navigation flow module obtains navigation data can be found in the relevant description of S201, and will not be repeated here.

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

[0446] In this embodiment, S1309 is implemented in exactly the same way as S203 in Embodiment 1. For a detailed description, please refer to the relevant description of S203, which will not be repeated here.

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

[0448] In this embodiment, S1310 is implemented in exactly the same way as S204 in Embodiment 1. For a detailed description, please refer to the relevant description of S204, which will not be repeated here.

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

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

[0451] Following S1310, the process may further include: the vehicle terminal sending navigation synchronization completion information to the user terminal via the second navigation transfer module; and the user terminal responding to the navigation synchronization completion information by transmitting an end command for the navigation task to the first navigation application via the first navigation transfer module, thereby stopping the navigation task of the first navigation application.

[0452] In this embodiment, by detecting the opening of the vehicle door, the user terminal can automatically synchronize the navigation task to the vehicle terminal, thereby achieving the purpose of continuing the navigation task from the user terminal to the vehicle terminal, reducing user operations and improving navigation efficiency.

[0453] Example 4:

[0454] Compared with Embodiment 1, the specific application scenario of this embodiment is to synchronize the navigation task on the intelligent vehicle control terminal installed in the vehicle to the user terminal carried by the user after the vehicle is parked. Based on this, the first terminal is specifically the vehicle terminal and the second terminal is the user terminal carried by the user. Figure 16 An interactive schematic diagram of a navigation task synchronization method provided in an embodiment of this application is shown, and the specific description is as follows:

[0455] In S1601, the vehicle terminal responds to the user's navigation operation and generates a navigation task through the first navigation application; the navigation data is generated based on the navigation task.

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

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

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

[0459] Compared with Embodiment 1, in this embodiment, if the vehicle terminal meets the preset cross-device transmission conditions, it obtains navigation data from the first navigation application through the first navigation transfer module, specifically including S1604 to S1606:

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

[0461] In this embodiment, the in-vehicle terminal is the terminal currently performing the navigation task. If the navigation scenario is not switched, the in-vehicle terminal will remain in a driving state. If the vehicle stops (e.g., at 0 speed and a door is detected to be open), or the vehicle is turned off, or the vehicle's power is switched off, it can be recognized that the user has switched from driving to walking, indicating a change in the navigation scenario. The navigation task needs to be synchronized to another terminal, namely the user's portable terminal. In this case, the in-vehicle terminal will establish communication with the user terminal.

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

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

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

[0465] In S1604.3, if the vehicle terminal detects that the user terminal is not in the registered device list, or the user terminal is in the registered device list and the connection status of the user terminal is unconnectable, then the vehicle terminal sends a wake-up command to the user terminal through the near-field communication module of the vehicle terminal.

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

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

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

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

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

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

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

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

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

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

[0476] Furthermore, as another embodiment of this application, the above-described S1608 may specifically include:

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

[0478] In this embodiment, after the vehicle terminal sends navigation synchronization information to the user terminal, the user terminal may not immediately perform navigation task synchronization. Instead, it can cache the navigation synchronization information in a cache area and detect the heartbeat signal between the user terminal and the vehicle terminal to maintain the activity of the near-field communication connection. Since in some scenarios, when a user parks and opens the door, they are actually just getting out of the car to rest, rather than switching navigation scenarios, the user terminal can detect the heartbeat signal to determine whether the user has left the vehicle and thus whether to update the navigation task of the local second navigation application.

[0479] Since the connection between the vehicle terminal and the user terminal is generally a near-field communication connection, and the two near-field communication connections are usually maintained by heartbeat signals, the heartbeat signals are sent at preset time intervals. The above time interval is a value that is less than the effective time mentioned below. Therefore, if the distance between the vehicle terminal and the user terminal is within the communication range, the two parties will continuously send heartbeat signals at preset time intervals to maintain the above near-field communication connection. The user terminal can detect the above heartbeat signals to determine whether the user has moved away from the vehicle.

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

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

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

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

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

[0485] In this embodiment, after the vehicle terminal detects a parking and door closing event initiated by the user, it triggers the synchronization of the navigation task, which enables the navigation task on the vehicle terminal to be automatically synchronized to the user terminal, eliminating the need for the user to frequently set the navigation destination and improving the efficiency of navigation task synchronization.

[0486] Example 5:

[0487] Examples 1, 2, 3, and 4 illustrate the implementation process of the cross-device navigation data synchronization method provided in this application from the perspective of interaction between the first terminal and the second terminal. Unlike Examples 1 to 4, Example 5 illustrates the implementation process of the cross-device navigation data synchronization method provided in this application from the perspective of the first terminal alone. Figure 17 A flowchart illustrating the implementation of a method for synchronizing navigation data across devices by a first terminal, according to an embodiment of this application, is shown. The specific description is as follows:

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

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

[0490] In step S1703, the navigation synchronization information is sent to the second terminal. This navigation synchronization information is used to update the navigation task of the second navigation application within the second terminal. Specifically, after receiving the navigation synchronization information, the second terminal transmits the received navigation synchronization information to the second navigation application via the second navigation transfer module, and updates the navigation task of the second navigation application according to the navigation synchronization information.

[0491] In this embodiment, S1701 is implemented in exactly the same way as S201 in Embodiment 1. In this embodiment, S1702 is implemented in exactly the same way as S202 in Embodiment 1. In this embodiment, S1703 is implemented in exactly the same way as S203 in Embodiment 1. For a detailed description, please refer to the relevant descriptions of S201 to S203, which will not be repeated here.

[0492] Optionally, if preset cross-device transmission conditions are met, obtaining navigation data from the first navigation application through the first navigation transfer module includes:

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

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

[0495] In this embodiment, the implementation of the above two steps is exactly the same as that of S1103 and S1104 in Embodiment 2. For a detailed description, please refer to the relevant descriptions of S1103 and S1104, which will not be repeated here.

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

[0497] Optionally, if preset cross-device transmission conditions are met, obtaining navigation data from the first navigation application through the first navigation transfer module includes:

[0498] Receive navigation flow notification sent by the second terminal; the navigation flow notification is sent to the first terminal after the second terminal is connected to the first terminal and the second navigation flow module of the second terminal is detected to be in the start state;

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

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

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

[0502] Receive the wake-up command sent by the second terminal through the second near-field communication module;

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

[0504] In this embodiment, the implementation of the above two steps is exactly the same as that of S1304.4 and S1304.5 in Embodiment 3. For a detailed description, please refer to the relevant descriptions of S1304.4 to S1304.5, which will not be repeated here.

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

[0506] Correspondingly, if the preset cross-device transmission conditions are met, then obtaining navigation data from the first navigation application through the first navigation transfer module includes:

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

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

[0509] In this embodiment, the implementation of the above two steps is exactly the same as that of S1604 and S1605 in Embodiment 4. For a detailed description, please refer to the relevant descriptions of S1604 to S1605, which will not be repeated here.

[0510] Optionally, the step of establishing a near-field communication connection with the second terminal if a parking event concerning the vehicle is detected includes:

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

[0512] If the second terminal is in the registered device list and the connection status of the second terminal is connectable, then based on the connection information associated with the second terminal in the registered device list, the near-field communication connection is established with the second terminal.

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

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

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

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

[0517] The first navigation transfer module receives a service registration instruction transmitted by the first navigation application; the service registration instruction is used to authorize the first navigation application to have the permission to transmit navigation data between devices.

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

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

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

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

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

[0523] In this embodiment, the above two steps are implemented in exactly the same way as S205 and S206 in Embodiment 1. For a detailed description, please refer to the relevant descriptions of S205 to S206, which will not be repeated here.

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

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

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

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

[0528] In this embodiment, when the cross-device transmission conditions are met, the first terminal can automatically obtain navigation data of the already started navigation task from the first navigation application through its local first navigation transfer module, generate navigation synchronization information corresponding to the navigation data through the first navigation transfer module, and send the navigation synchronization information to the second terminal, thus realizing cross-device transmission of navigation data. After receiving the navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through its 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, achieving cross-device navigation task synchronization. Compared with existing navigation technologies, this application can achieve cross-device navigation task synchronization. In scenarios requiring cross-device navigation, users do not need to repeatedly set tasks for the terminal's navigation application; instead, the navigation transfer module can automatically transfer navigation data to update the navigation tasks in the navigation application, thereby greatly improving the efficiency of navigation task setting and reducing repetitive user operations. On the other hand, after the first navigation transfer module in the first terminal obtains navigation data from the first navigation application, it does not directly send the navigation data to the second navigation transfer module of the second terminal. Instead, it converts the data into corresponding navigation synchronization information. This navigation synchronization information can be transmitted between navigation transfer modules of different terminals and then transmitted to the second navigation application through the second navigation transfer module. This is not a direct transmission between navigation applications within two terminals. Therefore, it is not necessary for the first terminal and the second terminal to have the same navigation application installed. This enables cross-device and cross-application navigation data transfer and further improves the application scope of navigation task synchronization.

[0529] Example 6:

[0530] Examples 1, 2, 3, and 4 illustrate the implementation process of the cross-device navigation data synchronization method provided in this application from the perspective of interaction between the first terminal and the second terminal. Unlike Examples 1 to 4, Example 6 illustrates the implementation process of the cross-device navigation data synchronization method provided in this application from the perspective of the second terminal alone. Figure 18 A flowchart illustrating the implementation of a method for synchronizing navigation data across devices by a second terminal, according to an embodiment of this application, is shown. The specific description is as follows:

[0531] In S1801, navigation synchronization information sent by the first terminal is received; the navigation synchronization information is generated based on navigation data from the first navigation application within the first terminal.

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

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

[0534] In this embodiment, S1801 and S1802 are implemented in exactly the same way as S203 in Embodiment 1, and S1803 is implemented in exactly the same way as S204. For a detailed description, please refer to the relevant descriptions of S203 and S204, which will not be repeated here.

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

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

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

[0538] Receive the navigation synchronization information sent by the first terminal through the first navigation flow module.

[0539] In this embodiment, the above steps are implemented in exactly the same way as S1110 in Embodiment 2. For a detailed description, please refer to the relevant description of S1110, which will not be repeated here.

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

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

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

[0543] In this embodiment, the above two steps are implemented in exactly the same way as S1101 to S1102 in Embodiment 2. For a detailed description, please refer to the relevant descriptions of S1101 to S1102, which will not be repeated here.

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

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

[0546] If a door opening event related to the vehicle is detected, a communication connection is established with the first terminal;

[0547] Get the list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, get the setting status of the second navigation flow module.

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

[0549] In this embodiment, the above three steps are implemented in exactly the same way as S1304 to S1306 in Embodiment 3. For a detailed description, please refer to the relevant descriptions of S1304 to S1306, which will not be repeated here.

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

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

[0552] If the first terminal is in the registered device list and the connection status of the first terminal is connectable, then a communication connection is established with the first terminal based on the connection information associated with the first terminal in the registered device list.

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

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

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

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

[0557] The navigation synchronization information is cached in the cache area by the second navigation flow module, and the heartbeat signal of the near-field communication connection with the first terminal is detected.

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

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

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

[0561] The system checks if a navigation application matching the first navigation application exists in the navigation application list; the navigation application list includes the first navigation application.

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

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

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

[0565] The navigation destination is determined based on the navigation synchronization information, and a task update prompt is generated based on the navigation destination.

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

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

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

[0569] The system sends navigation synchronization completion information to the first terminal, so that the first terminal responds to the navigation synchronization completion information and transmits a navigation task termination instruction to the first navigation application through the first navigation flow module, thereby stopping the navigation task of the first navigation application.

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

[0571] Example 7:

[0572] Corresponding to the cross-device navigation task synchronization method described in Embodiment 5 above, Figure 19 A structural block diagram of a cross-device navigation task synchronization device provided in an embodiment of this application is shown. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0573] Reference Figure 19 The synchronization mechanism for the cross-device navigation task includes:

[0574] The navigation data acquisition unit 191 is used to acquire navigation data from the first navigation application through the first navigation transfer module if the preset cross-device transmission conditions are met.

[0575] The navigation synchronization information generation unit 192 is used to generate navigation synchronization information corresponding to the navigation data through the first navigation flow module;

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

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

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

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

[0580] Optionally, the communication tag is obtained when the second terminal detects that the tag writing conditions are met, by sending a tag writing request to the tag service thread through the second navigation flow module, and by the tag service thread responding to the tag writing request, adding the start identifier to the communication tag, and writing the communication tag to the second near-field communication module.

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

[0582] A navigation flow notification receiving unit is used to receive a navigation flow notification sent by the second terminal; the navigation flow notification is sent to the first terminal after the second terminal is connected to the first terminal and the second navigation flow module of the second terminal is detected to be in the start state;

[0583] A navigation flow notification response unit is used to respond to the navigation flow notification by obtaining navigation data from the first navigation application through the first navigation flow module.

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

[0585] A wake-up command receiving unit is used to receive a wake-up command sent by the second terminal through the second near-field communication module;

[0586] A wake-up command response unit is used to send a wireless connection request to the second terminal in response to the wake-up command, so as to establish the communication connection with the second terminal.

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

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

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

[0590] The first state recognition unit is used to obtain a list of navigation synchronization applications. If the list of navigation synchronization applications is not empty, the setting state of the first navigation flow module is obtained.

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

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

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

[0594] A direct connection triggering unit is used to establish a near-field communication connection with the second terminal based on the connection information associated with the second terminal in the registered device list if the second terminal is in the registered device list and the connection status of the second terminal is a connectable state.

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

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

[0597] A navigation operation response unit is used to respond to a user's navigation operation and generate a navigation task through the first navigation application; the navigation data is generated based on the navigation task.

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

[0599] A service registration response unit is configured to, in response to the service registration instruction, add the first navigation application to the navigation synchronization application list and set the first navigation flow module to the start state; the start state is configured to send the navigation synchronization information generated based on the first navigation application to the second terminal when the cross-device transmission conditions are met.

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

[0601] The navigation synchronization completion information receiving unit is used to receive navigation synchronization completion information fed back by the second terminal through the second navigation flow module;

[0602] The navigation termination unit is used to respond to the navigation synchronization completion information by transmitting a navigation task termination instruction to the first navigation application through the first navigation flow module, so as to stop the navigation task of the first navigation application.

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

[0604] A navigation application list acquisition unit is used to acquire a navigation application list of the second terminal; the navigation application list includes the second navigation application;

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

[0606] Therefore, the cross-device navigation task synchronization device provided in this application embodiment can also automatically obtain navigation data of the already started navigation task from the first navigation application through the first navigation transfer module on the first terminal when the first terminal detects that the cross-device transmission conditions are met. It then 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, thus realizing cross-device transmission of navigation data. After receiving the navigation synchronization information, the second terminal can generate and transmit the navigation synchronization information to the second navigation application through its 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, achieving cross-device navigation task synchronization. Compared with existing navigation technologies, this application can achieve cross-device navigation task synchronization. In scenarios requiring cross-device navigation, users do not need to repeatedly set tasks for the terminal's navigation application. Instead, the navigation transfer module can automatically transfer navigation data to update the navigation task in the navigation application, thereby greatly improving the efficiency of navigation task setting and reducing repetitive user operations. On the other hand, after the first navigation transfer module in the first terminal obtains navigation data from the first navigation application, it does not directly send the navigation data to the second navigation transfer module of the second terminal. Instead, it converts the data into corresponding navigation synchronization information. This navigation synchronization information can be transmitted between navigation transfer modules of different terminals and then transmitted to the second navigation application through the second navigation transfer module. This is not a direct transmission between navigation applications within two terminals. Therefore, it is not necessary for the first terminal and the second terminal to have the same navigation application installed. This enables cross-device and cross-application navigation data transfer and further improves the application scope of navigation task synchronization.

[0607] Example 8:

[0608] Corresponding to the cross-device navigation task synchronization method described in Embodiment 5 above, Figure 20 A structural block diagram of a cross-device navigation task synchronization device provided in an embodiment of this application is shown. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0609] Reference Figure 20The synchronization mechanism for the cross-device navigation task includes:

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

[0611] The navigation synchronization information transmission unit 202 is used to transmit the navigation synchronization information to the second navigation application through the second navigation transfer module;

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

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

[0614] A communication tag sending unit gate is used to send a communication tag to the first terminal via a second near-field communication module in response to a touch operation with the first terminal, so that the first terminal responds to the communication tag, starts a first navigation flow module, and obtains the navigation data from the first navigation application through the first navigation flow module; the communication tag carries a navigation task synchronization start identifier;

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

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

[0617] The tag write request unit is used to send a tag write request to the tag service thread through the second navigation flow module if the preset tag write conditions are met.

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

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

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

[0621] The door opening event triggering unit is used to establish a communication connection with the first terminal if a door opening event related to the vehicle is detected.

[0622] The second state recognition unit is used to obtain the navigation synchronization application list. If the navigation synchronization application list is not empty, the setting state of the second navigation flow module is obtained.

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

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

[0625] The connection status determination unit is used to identify the connection status of each registered terminal in the preset list of registered devices through the second navigation flow module;

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

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

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

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

[0630] An information caching unit is used to cache the navigation synchronization information in a cache area through the second navigation flow module and detect the heartbeat signal of the communication connection with the first terminal.

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

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

[0633] The matching application detection unit is used to detect whether there is a navigation application in the navigation application list that matches the first navigation application; the navigation application list includes the first navigation application;

[0634] The second navigation application identification unit is used to identify the navigation application matching the first navigation application if it detects that there is a navigation application matching the first navigation application in the navigation application list, and then to select the navigation application matching the first navigation application as the second navigation application and perform the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow module; the navigation application matching the first navigation application is specifically an application that has the permission to transmit navigation data across devices with the second navigation application.

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

[0636] The update prompt information generation unit is used to determine the navigation destination based on the navigation synchronization information and generate task update prompt information based on the navigation destination;

[0637] An update confirmation instruction response unit is configured to update the navigation task based on the navigation destination if it receives an update confirmation instruction based on the update prompt information.

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

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

[0640] The cross-device navigation task synchronization method provided in this application embodiment can be applied to terminal devices such as smartphones, tablets, wearable devices, vehicle terminals, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). This application embodiment does not impose any restrictions on the specific type of terminal device.

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

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

[0643] Terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a 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, etc.

[0644] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0645] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0646] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

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

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

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

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

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

[0652] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to enable music playback through Bluetooth headphones.

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

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

[0655] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge terminal device 100, and can also be used for data transfer between terminal device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other terminal devices, such as AR devices.

[0656] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0657] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the terminal device 100. While charging the battery 142, the charging management module 140 can also supply power to the terminal device via the power management module 141.

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

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

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

[0661] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0662] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0663] The wireless communication module 160 can provide solutions for wireless communication applications on the terminal device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0664] 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, enabling terminal device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The 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 satellite-based augmentation systems (SBAS).

[0665] The terminal device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information. Specifically, the display screen 194 can display the generated detection report, allowing the user to view it.

[0666] Display screen 194 is used to display images, videos, etc. Display screen 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 miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, terminal device 100 may include one or N displays 194, where N is a positive integer greater than 1. Display screen 194 may include a touch panel and other input devices.

[0667] Terminal device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0668] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0669] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion 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 image signals in standard RGB, YUV, or other formats. In some embodiments, the terminal device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0670] A digital signal processor (DSP) is used to process digital signals. Besides digital image signals, it can also process other digital signals. For example, when terminal device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0671] Video codecs are used to compress or decompress digital video. Terminal device 100 may support one or more video codecs. Thus, terminal device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0672] NPU stands for Neural Network (NN) Computing Processor. By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in terminal devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0673] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

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

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

[0676] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0677] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The terminal device 100 can listen to music or make hands-free calls through the speaker 170A. Specifically, the speaker 170A can be used to output prompts to notify the user of the part of the electronic scale that needs to be touched.

[0678] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the terminal device 100 answers a phone call or voice message, the receiver 170B can be brought close to the listener's ear to hear the voice.

[0679] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Terminal device 100 may be equipped with at least one microphone 170C. In some embodiments, terminal device 100 may be equipped with two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, terminal device 100 may be equipped with three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0680] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0681] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194, for example, the terminal device can obtain the user's weight through pressure sensor 180A. There are many types of pressure sensor 180A, such as resistive pressure sensor, inductive pressure sensor, capacitive pressure sensor, etc. Capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Terminal device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, terminal device 100 detects the intensity of the touch operation based on pressure sensor 180A. Terminal device 100 can also calculate the touch position based on the detection signal of pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example, when a touch operation with a touch operation intensity less than a first pressure threshold is applied to the SMS application icon, a command to view SMS messages is executed. When a touch operation with a strength greater than or equal to the first pressure threshold is applied to the SMS application icon, the instruction to create a new SMS message is executed.

[0682] The gyroscope sensor 180B can be used to determine the motion attitude of the terminal device 100. In some embodiments, the gyroscope sensor 180B can determine the angular velocity of the terminal device 100 around three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the terminal device 100's shake, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the terminal device 100 through reverse movement, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing game scenarios.

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

[0684] The magnetic sensor 180D includes a Hall sensor. The terminal device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip cover. In some embodiments, when the terminal device 100 is a flip phone, the terminal device 100 can detect the opening and closing of the flip cover using the magnetic sensor 180D. Then, based on the detected opening and closing state of the cover or the flip cover, features such as automatic flip unlocking can be set.

[0685] The 180E accelerometer can detect the magnitude of acceleration of the terminal device 100 in various directions (typically three axes). When the terminal device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the attitude of the terminal device, and can be applied to applications such as landscape / portrait switching and pedometers.

[0686] A distance sensor 180F is used to measure distance. The terminal device 100 can measure distance via infrared or laser. In some embodiments, during a shooting scene, the terminal device 100 can utilize the distance sensor 180F to measure distance for rapid focusing.

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

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

[0689] The fingerprint sensor 180H is used to collect fingerprints. The terminal device 100 can use the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering calls with fingerprints, etc.

[0690] Temperature sensor 180J is used to detect temperature. In some embodiments, terminal device 100 uses the temperature detected by temperature sensor 180J to execute a temperature handling strategy. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, terminal device 100 reduces the performance of the processor located near temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is below another threshold, terminal device 100 heats battery 142 to prevent abnormal shutdown of terminal device 100 due to low temperature. In still other embodiments, when the temperature is below yet another threshold, terminal device 100 boosts the output voltage of battery 142 to prevent abnormal shutdown due to low temperature.

[0691] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of terminal device 100, in a different position than display screen 194.

[0692] The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire vibration signals from the vibrating bone segments of the human vocal cords. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure signals. In some embodiments, the bone conduction sensor 180M can also be incorporated into headphones to form bone conduction headphones. The audio module 170 can parse the voice signals from the vibrating bone segments of the vocal cords acquired by the bone conduction sensor 180M to realize voice functionality. The application processor can parse heart rate information from the blood pressure signals acquired by the bone conduction sensor 180M to realize heart rate detection functionality.

[0693] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Terminal device 100 can receive button input and generate key signal inputs related to user settings and function control of terminal device 100.

[0694] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

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

[0696] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate 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 Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the terminal device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100.

[0697] The software system of terminal device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses the layered architecture Android system as an example to exemplify the software structure of terminal device 100.

[0698] Figure 22 This is a software structure block diagram of a terminal device according to an embodiment of this application.

[0699] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. 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.

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

[0701] like Figure 22 As shown, the application package can include applications such as camera, calendar, map, WLAN, Bluetooth, music, video, SMS, email, WeChat, and WPS.

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

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

[0704] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0705] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

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

[0707] A phone manager is used to provide communication functions for terminal devices. For example, it manages call status (including connection and disconnection).

[0708] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0709] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights.

[0710] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

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

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

[0713] The system layer can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0714] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0715] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

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

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

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

[0719] The following example, using a scene of capturing a photograph, illustrates the workflow of the software and hardware of the terminal device 100.

[0720] When 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 a raw input event (including touch coordinates, timestamp of the touch operation, etc.). The raw input event is stored in the kernel layer. The application framework layer retrieves the raw input event from the kernel layer and identifies the control corresponding to the input event. Taking a single touch operation as an example, where the corresponding control is the camera application icon, the camera application calls the interface of the application framework layer to launch the camera application, and then calls the kernel layer to launch the camera driver, capturing still images or videos through camera 193.

[0721] Figure 23 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Figure 23 As shown, the terminal device 23 of this embodiment includes: at least one processor 230 ( Figure 23 The diagram shows only one processor, memory 231, and computer program 232 stored in the memory 231 and executable on the at least one processor 230, wherein the processor 230 executes the computer program 232 to implement the steps in the above embodiments of the synchronization method for any of the various cross-device navigation tasks.

[0722] The terminal device 23 can be a desktop computer, laptop, handheld computer, or cloud server, etc. This terminal device may include, but is not limited to, a processor 230 and a memory 231. Those skilled in the art will understand that... Figure 23 This is merely an example of terminal device 23 and does not constitute a limitation on terminal device 23. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0723] The processor 230 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

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

[0725] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0726] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0727] This application also provides a terminal device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor executes the computer program to implement the steps in any of the above method embodiments.

[0728] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.

[0729] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the above-described method embodiments.

[0730] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0731] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

[0733] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

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

[0735] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for synchronizing navigation tasks across devices, applied to a first terminal, characterized in that, The method comprises the steps of: if a preset cross-device transmission condition is met, obtaining navigation data from a first navigation application through a first navigation flow transfer module; generating navigation synchronization information corresponding to the navigation data through the first navigation flow transfer module; 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 in the second terminal; after the navigation synchronization information is sent to the second terminal, the method further comprises the steps of: receiving navigation synchronization completion information fed back by the second terminal through a second navigation flow transfer module; in response to the navigation synchronization completion information, transmitting an end instruction about the navigation task to the first navigation application through the first navigation flow transfer module to stop the navigation task of the first navigation application.

2. The transmission method of claim 1, wherein, The step of obtaining the navigation data from the first navigation application through the first navigation flow transfer module if the preset cross-device transmission condition is met comprises the steps of: in response to a touch operation between the first terminal and the second terminal, receiving a communication tag sent by a second near field communication module of the second terminal, the communication tag carrying a start identifier of navigation task synchronization; in response to the communication tag, starting the first navigation flow transfer module and obtaining the navigation data from the first navigation application through the first navigation flow transfer module.

3. The transmission method of claim 2, wherein, The communication tag is obtained in the following manner: when the second terminal detects that a tag writing condition is met, a tag writing request is sent to a tag service thread through the second navigation flow transfer module, the start identifier is added to the communication tag in response to the tag writing request by the tag service thread, and the communication tag is written into the second near field communication module.

4. The transmission method of claim 1, wherein, The step of obtaining the navigation data from the first navigation application through the first navigation flow transfer module if the preset cross-device transmission condition is met comprises the steps of: receiving a navigation flow transfer notification sent by the second terminal, the navigation flow transfer notification being sent to the first terminal after the second terminal is connected to the first terminal and when a second navigation flow transfer module of the second terminal is detected to be in a start state; in response to the navigation flow transfer notification, obtaining the navigation data from the first navigation application through the first navigation flow transfer module.

5. The transmission method of claim 4, wherein, Before the navigation flow transfer notification sent by the second terminal is received, the method further comprises the steps of: receiving a wake-up instruction sent by a second near field communication module of the second terminal; in response to the wake-up instruction, sending a wireless connection request to the second terminal to establish the communication connection with the second terminal.

6. The transmission method of claim 1, wherein, The first terminal is a vehicle intelligent control terminal installed on a vehicle, and the second terminal is a user terminal carried by a user. The step of obtaining the navigation data from the first navigation application through the first navigation flow transfer module if the preset cross-device transmission condition is met comprises the steps of: if a parking event about the vehicle is detected, establishing a near field communication connection with the second terminal, the near field communication connection being used to send navigation synchronization information to the second terminal; obtaining a navigation synchronization application list, and if the navigation synchronization application list is not empty, obtaining a setting state of the first navigation flow transfer module; If the first navigation flow conversion module is in an activated state, navigation data is acquired from the first navigation application through the first navigation flow conversion module.

7. The transmission method according to any one of claims 1-6, characterized in that, Before the navigation synchronization information is sent to the second terminal, the method further includes: acquiring a navigation application list of the second terminal, the navigation application list containing the second navigation application; if the navigation application list contains a navigation application matched with the first navigation application, sending the navigation synchronization information to the second terminal, the first navigation application matched with the second navigation application being an application having a right to transmit navigation data across devices with the first navigation application.

8. A method for synchronizing navigation tasks across devices, applied to a second terminal, characterized in that, The method includes: receiving navigation synchronization information sent by a first terminal; the navigation synchronization information being generated based on navigation data of a first navigation application in the first terminal; transmitting the navigation synchronization information to a second navigation application through a second navigation flow conversion module; updating a navigation task of the second navigation application based on the navigation synchronization information; after the navigation task of the second navigation application is updated based on the navigation synchronization information, the method further includes: sending navigation synchronization completion information to the first terminal, so that the first terminal, in response to the navigation synchronization completion information, transmits an end instruction about the navigation task to the first navigation application through the first navigation flow conversion module to stop the navigation task of the first navigation application.

9. The transmission method of claim 8, wherein, The receiving navigation synchronization information sent by the first terminal includes: in response to a touch operation between the first terminal and the second terminal, sending a communication tag to the first terminal through a second near field communication module, so that the first terminal, in response to the communication tag, activates a first navigation flow conversion module and acquires the navigation data from the first navigation application through the first navigation flow conversion module; the communication tag carries an activation identifier of navigation task synchronization; receiving the navigation synchronization information sent by the first terminal through the first navigation flow conversion module.

10. The transmission method of claim 9, wherein, Before the sending the communication tag to the first terminal through the second near field communication module in response to the touch operation between the first terminal and the second terminal, the method further includes: if a preset tag writing condition is met, sending a tag writing request to a tag service thread through the second navigation flow conversion module; in response to the tag writing request through the tag service thread, adding the activation identifier to the communication tag and writing the communication tag to the second near field communication module.

11. The transmission method of claim 8, wherein, The second terminal is a vehicle intelligent control terminal installed on a vehicle; Before the receiving navigation synchronization information sent by a first terminal, the method further includes: if a door opening event about the vehicle is detected, establishing a communication connection with the first terminal; acquiring a navigation synchronization application list, and if the navigation synchronization application list is not empty, acquiring a setting state of a second navigation flow conversion module; if the second navigation flow conversion module is in an activated state, sending a navigation flow conversion notification to the first terminal, so that the first terminal sends the navigation synchronization information.

12. The transmission method of claim 8, wherein, The second terminal is a user terminal carried by a user; and the first terminal is a vehicle intelligent control terminal installed on a vehicle. The navigation synchronization information is transmitted to a second navigation application through a second navigation flow conversion module, including: The navigation synchronization information is buffered in a cache area through the second navigation flow conversion module, and a heartbeat signal of a communication connection between the first terminal is detected; If the heartbeat signal is not received within a preset valid time, it is identified that the near field communication connection with the first terminal is disconnected, and the navigation synchronization information is transmitted to the second navigation application.

13. The transmission method according to any one of claims 8-12, characterized by, After the navigation synchronization information sent by the first terminal is received, further including: It is detected whether there is a navigation application matching the first navigation application in a navigation application list; the navigation application list contains the first navigation application; If it is detected that the navigation application list has a navigation application matching the first navigation application, the navigation application matching the first navigation application is taken as the second navigation application, and the operation of transmitting the navigation synchronization information to the second navigation application through the second navigation flow conversion module is performed; the navigation application matching the first navigation application is specifically: an application having a right to transmit navigation data across devices with the second navigation application.

14. The transmission method according to any one of claims 8-13, characterized by, The navigation task of the second navigation application is updated based on the navigation synchronization information, including: A navigation destination is determined based on the navigation synchronization information, and task update prompt information is generated based on the navigation destination; If an update confirmation instruction fed back based on the update prompt information is received, the navigation task is updated based on the navigation destination.

15. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor implements the method of any one of claims 1-7 when executing the computer program.

16. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor implements the method of any one of claims 8-14 when executing the computer program.

Images