CN116560862A

CN116560862A - Application synchronization method and electronic equipment

Info

Publication number: CN116560862A
Application number: CN202210114806.8A
Authority: CN
Inventors: 周中晟
Original assignee: Petal Cloud Technology Co Ltd
Current assignee: Petal Cloud Technology Co Ltd
Priority date: 2022-01-30
Filing date: 2022-01-30
Publication date: 2023-08-08
Also published as: WO2023142869A1

Abstract

The application synchronization method and electronic equipment are provided. In the method, the first electronic equipment can realize communication among the first electronic equipment, the second electronic equipment and the server through one identifier of the first electronic equipment. The first electronic device, via the server, may synchronize at least one application installed in the second electronic device. And the first electronic device can synchronize at least one application installed in the first electronic device to the second electronic device through the server. Therefore, application synchronization between the electronic devices compatible with the device difference and the application difference is realized, the operation is quick and convenient, account sharing is not needed, and an additional hardware module is not needed to be added.

Description

Application synchronization method and electronic equipment

Technical Field

The application relates to the technical field of terminals, in particular to an application synchronization method and electronic equipment.

Background

Applications have been widely used by users in electronic devices. At present, application synchronization is often needed among different electronic devices, so that a user can conveniently and efficiently cooperatively use application programs in the different electronic devices.

In related art 1, different electronic devices generally use the same account number as a bridge to perform application synchronization. However, the related art 1 has many disadvantages: 1. after one electronic device updates the application, all electronic devices associated with the same account update the application, resulting in unnecessary application synchronization; 2. the requirements that a user does not want to log in an account and personal privacy data can not be met; 3. the method comprises the following steps that a plurality of accounts cannot be logged in on the same electronic device at the same time, so that the application corresponding to the plurality of accounts cannot be synchronized; 4. application synchronization cannot be performed among electronic devices of different device types and/or operating systems, and applications in different electronic devices cannot be compatible with different application versions.

In related art 2, the electronic device 1 and the electronic device 2 are typically associated by a near field communication (near field communication, NFC) hardware module between different electronic devices, so that the electronic device 2 synchronizes the screen of the electronic device 1. However, related art 2 has many drawbacks: 1. the essence of the association of the electronic device 1 and the electronic device 2 is that the screen of the electronic device 1 is displayed on the electronic device 2 for rendering, so that synchronization cannot be continued after the electronic device 1 and the electronic device 2 are disconnected. 2. The electronic device 2 only functions as a picture presentation and cannot actually run an application on the electronic device 2. 3. The device types of the electronic device 2 are limited, and cannot cover electronic devices of various device types. 4. The electronic device 1 needs to be provided with an NFC hardware module, which increases the cost of the synchronous application.

Disclosure of Invention

The application synchronization method, the electronic equipment and the communication system are used for realizing application synchronization between the electronic equipment compatible with the equipment difference and the application difference, are rapid and convenient to operate, do not need to rely on account sharing, and do not need to add additional hardware modules.

In a first aspect, the present application provides an application synchronization method, which is applied to a first electronic device.

The method comprises the following steps:

after receiving a first operation, sending a first message to a server, wherein the first operation is used for starting a synchronous application function of first electronic equipment, and the first message comprises a first identifier;

displaying a first interface, wherein the first interface comprises a first identifier;

receiving a second message from the server, the second message including information of at least one application, the at least one application being an application synchronized by the second electronic device to the first electronic device by the server based on the first identification;

at least one application is installed in the first electronic device based on the second message.

By the application synchronization method provided by the first aspect, the first electronic device can realize communication connection and mutual communication among the first electronic device, the second electronic device and the server based on the identifier generated by the first electronic device. Therefore, the first electronic device can synchronize at least one application installed in the second electronic device through the server, the difference between the device types among the electronic devices, the operating system among the electronic devices and the application names and application versions of the applications in the electronic devices is not required to be considered, the synchronization of the application names and the application versions among the electronic devices of various operating systems and the device types is realized through the transmission of application information, or the synchronization of the application names, the application versions and the application service conditions among the electronic devices of various operating systems and the device types is realized, account sharing is not required, additional hardware modules are not required to be added, the realization process is convenient and quick, the cost of synchronizing the application among the electronic devices is reduced, and the user experience of synchronizing the application among the electronic devices is improved.

In one possible design, the method further includes, prior to displaying the first interface:

a third message is received from the server, the third message indicating that the server has stored the first identification.

In one possible design, the first identifier in the first interface is a character code or a two-dimensional code, and the first identifier is obtained by the second electronic device through scanning and identifying the character code or the two-dimensional code.

Therefore, the first electronic device can respectively transmit the first identifier to the server and the second electronic device, and the first electronic device, the server and the second electronic device can share the same identifier to realize application synchronization.

In one possible design, installing at least one application in the first electronic device based on the second message includes:

displaying a second interface, the second interface comprising at least one application;

after receiving an operation of selecting a first application from at least one application by a user, the first application is installed in the first electronic device.

Therefore, the first electronic equipment can directly install at least one application by default, and can also install the application selected by the user from the at least one application based on the user wish, so that the synchronous application has more flexibility and user freedom.

In one possible design, the method further comprises:

generating a first identification based on the time window;

or generating a first identifier based on the time window and the device information of the first electronic device;

or generating a first identifier based on the time window and the encryption algorithm;

or generating a first identifier based on the time window, the device information of the first electronic device and the encryption algorithm;

the time window is a period of time including the current time, or the device information of the first electronic device is used for uniquely determining the first electronic device at the current time.

Thus, various implementations are provided for generating the first identifier, and uniqueness and randomness of the first identifier are ensured.

In one possible design, the first electronic device includes a second application, and the first operation is an operation triggered on one control for the second application.

In one possible design, the second application is an application marketplace or system setting.

Therefore, the first electronic device can utilize an application to start the function of synchronous application, and the operation is convenient and fast.

In one possible design, after installing the at least one application in the first electronic device based on the second message, the method further includes:

And displaying first content, wherein the first content is used for indicating the first electronic equipment to synchronously complete at least one application.

Thus, the first electronic device may alert the user that the first electronic device has completed application synchronization.

In one possible design, the method further comprises:

and sending a fourth message to the server, wherein the fourth message is used for informing the second electronic device that the first electronic device synchronously completes at least one application.

Thus, the second electronic device can remind the user that the first electronic device has completed application synchronization.

In one possible design mentioned in the first aspect, the second aspect and the third aspect, the at least one application includes a fourth application;

the information of the fourth application comprises an application name and an application version, the application version of the fourth application in the first electronic device is a first version, the first version is matched with the device type and the operating system of the first electronic device, the application version of the fourth application in the second electronic device is a second version, the second version is matched with the device type and the operating system of the second electronic device, and the first version and the second version are different;

or, the information of the fourth application includes an application name and an application version, the application name of the fourth application in the first electronic device is a first name, the application name of the fourth application in the second electronic device is a second name, the first name and the second name are used for indicating the fourth application, and the first name is different from the second name.

In one possible design mentioned in the first aspect, the second aspect and the third aspect, the first version is the latest version or an old version corresponding to the second version.

Therefore, the process of synchronizing various types of applications installed in the second electronic device by the first electronic device through the server can be realized without considering the difference of application names and application versions of the applications in the electronic devices.

In one possible design mentioned in the first aspect, the second aspect and the third aspect, the first electronic device is of a different device type than the second electronic device;

alternatively, the first electronic device is different from the operating system of the second electronic device.

Therefore, the process of synchronizing the applications installed in the second electronic device by the first electronic device through the server can be realized without considering the device types among the electronic devices and the difference among the operating systems among the electronic devices.

In a second aspect, the present application provides an application synchronization method applied to a second electronic device.

The method comprises the following steps:

acquiring a first identifier from a first electronic device;

displaying a third interface, wherein the third interface comprises an application installed in the second electronic equipment;

determining at least one application after receiving a second operation performed by the user on the third interface;

And sending a fifth message to the server, the fifth message comprising the first identification and information of the at least one application, the fifth message being for the server to synchronize the at least one application to the first electronic device based on the first identification.

By the application synchronization method provided in the second aspect, the second electronic device can be in communication connection with and communicate with the first electronic device and the server based on the identification generated by the first electronic device. Therefore, the first electronic equipment can synchronize at least one application installed in the second electronic equipment through the server, the difference among equipment types among the electronic equipment, operating systems among the electronic equipment and application names and application versions of applications in the electronic equipment is not required to be considered, the synchronization of various application names and application versions among the electronic equipment of various operating systems and equipment types is realized through the transmission of application information, or the synchronization of various application names, application versions and application service conditions among the electronic equipment of various operating systems and equipment types is realized, account sharing is not required to be relied on, an additional hardware module is not required to be added, the realization process is convenient and rapid, the cost of synchronizing the application among the electronic equipment is reduced, and the user experience of synchronizing the application among the electronic equipment is improved.

In one possible design, obtaining a first identification from a first electronic device includes:

the second identifier is identified by scanning and identifying the character code or the two-dimensional code displayed by the first electronic equipment;

based on the second identifier, the first identifier is obtained.

In one possible design, the obtaining the first identifier based on the second identifier includes:

displaying a fourth interface, wherein the fourth interface comprises a second identifier;

after the modified content is received within the preset time period, the second identifier is changed based on the modified content, and a first identifier is obtained;

or, after receiving an operation for determining that the second identifier is correct within a preset time period or after not receiving the modified content after the preset time period, determining that the second identifier is the first identifier.

Therefore, the second electronic device can assist the second electronic device to obtain the accurate first identification based on the user will, and the phenomenon that the second electronic device possibly has identification errors is fully considered.

In one possible design, when the second electronic device includes the third application, obtaining the first identification from the first electronic device includes:

and after receiving a third operation triggered on one control of the third application, acquiring the first identifier from the first electronic device, wherein the third operation is used for triggering the second electronic device to acquire the first identifier.

In one possible design, the third application is an application marketplace or system setting.

Therefore, the second electronic equipment can acquire the first identifier by using the third application, and the operation is convenient and fast.

In one possible design, the method further comprises:

receiving a sixth message from the server, the sixth message being for indicating that the first electronic device completes at least one application synchronously;

and displaying second content, wherein the second content is used for indicating the first electronic device to synchronously complete at least one application.

Thus, the second electronic device may alert the user that the first electronic device has completed application synchronization.

In a third aspect, the present application provides an application synchronization method, which is applied to a server.

The method comprises the following steps:

receiving a first message from a first electronic device, the first message including a first identification;

receiving a fifth message from the second electronic device, the fifth message including the first identification and information of the at least one application;

and sending a second message to the first electronic device, wherein the second message comprises at least one application, and the second message is used for the first electronic device to install the at least one application in the first electronic device.

In one possible design, after receiving the first message from the first electronic device, the method further includes:

Storing the first identification;

and sending a third message to the first electronic device, wherein the third message is used for indicating that the server stores the first identification.

In one possible design, the method further comprises:

receiving a fourth message from the first electronic device, the fourth message being used to instruct the first electronic device to synchronously complete at least one application;

and sending a sixth message to the second electronic device, wherein the sixth message is used for notifying the first electronic device that the second electronic device synchronously completes at least one application.

The advantages of the third aspect and the methods provided in the possible designs of the third aspect may be referred to in the foregoing first aspect and the possible embodiments of the first aspect and the advantages brought about by the foregoing second aspect and the possible embodiments of the second aspect, which are not described herein.

In a fourth aspect, the present application provides an application synchronization method, which is applied to a first electronic device.

Displaying a fifth interface, wherein the fifth interface comprises an application installed in the first electronic equipment;

determining at least one application after receiving a fourth operation performed by the user on the fifth interface;

after receiving the fifth operation, sending a seventh message to the server, wherein the fifth operation is used for starting a synchronous application function of the first electronic device, the seventh message comprises a third identifier and information of at least one application, and the at least one application is an application which is synchronized to the second electronic device by the server through the server based on the third identifier by the first electronic device;

And displaying a sixth interface, wherein the sixth interface comprises a third identifier.

By the application synchronization method provided in the fourth aspect, the first electronic device can realize communication connection and intercommunication among the first electronic device, the second electronic device and the server based on the identifier generated by the first electronic device. Therefore, the first electronic device can synchronize at least one application installed in the first electronic device to the second electronic device through the server, the difference among device types among the electronic devices, operating systems among the electronic devices and application names and application versions of the applications in the electronic devices is not needed to be considered, the synchronization of various application names and application versions among the electronic devices of various operating systems and device types is realized through the transmission of application information, or the synchronization of various application names, application versions and application service conditions among the electronic devices of various operating systems and device types is realized, account sharing is not needed, additional hardware modules are not needed to be added, the realization process is convenient and quick, the cost of synchronous application among the electronic devices is reduced, and the user experience of synchronous application among the electronic devices is improved.

In one possible design, the method further includes, prior to displaying the sixth interface:

an eighth message is received from the server, the eighth message indicating that the server has stored the third identification.

In one possible design, the third identifier in the sixth interface is a character code or a two-dimensional code, and the third identifier is obtained by the second electronic device by scanning and identifying the character code or the two-dimensional code.

Therefore, the first electronic device can respectively transmit the third identifier to the server and the second electronic device, and the first electronic device, the server and the second electronic device can share the same identifier to realize application synchronization.

In one possible design, the method further comprises:

generating a third identification based on the time window;

or generating a third identifier based on the time window and the device information of the first electronic device;

or generating a third identifier based on the time window and the encryption algorithm;

or generating a third identifier based on the time window, the device information of the first electronic device and the encryption algorithm;

Thus, various implementations are provided for generating the third identifier, and uniqueness and randomness of the third identifier are ensured.

In one possible design, the first electronic device includes a fifth application, the fifth operation being an operation triggered on one control for the fifth application.

In one possible design, the fifth application is an application marketplace or system setting.

In one possible design, the method further comprises:

receiving a ninth message from the server, the ninth message being for indicating that the second electronic device completes at least one application synchronously;

and displaying third content, wherein the third content is used for indicating the second electronic equipment to synchronously complete at least one application.

In a possible design mentioned in the fourth aspect, the fifth aspect and the sixth aspect, the at least one application includes a sixth application;

the information of the sixth application comprises an application name and an application version, the application version of the sixth application in the first electronic device is a first version, the first version is matched with the device type and the operating system of the first electronic device, the application version of the sixth application in the second electronic device is a second version, the second version is matched with the device type and the operating system of the second electronic device, and the first version and the second version are different;

Or, the information of the sixth application includes an application name, the application name of the sixth application in the first electronic device is a first name, the application name of the sixth application in the second electronic device is a second name, the first name and the second name are used for indicating the sixth application, and the first name is different from the second name.

In a possible design of the fourth, fifth and sixth aspects mentioned, the second version is the latest version or an old version corresponding to the first version.

Therefore, the process that the first electronic device synchronizes various types of applications installed in the first electronic device to the second electronic device through the server can be realized without considering the difference of application names and application versions of the applications in the electronic devices.

In one possible design mentioned in the fourth aspect, the fifth aspect and the sixth aspect, the first electronic device is of a different device type than the second electronic device;

Thus, a process of synchronizing an application installed in the first electronic device to the second electronic device through the server by the first electronic device can be realized without considering the difference between the device types between the electronic devices and the operating systems between the electronic devices.

In a fifth aspect, the present application provides an application synchronization method applied to a second electronic device.

The method comprises the following steps:

acquiring a third identifier from the first electronic device;

transmitting a tenth message to the server, the tenth message including the third identification;

receiving an eleventh message from the server, the eleventh message including information of at least one application, the at least one application being an application synchronized by the first electronic device to the second electronic device through the server based on the third identification;

at least one application is installed in the second electronic device based on the eleventh message.

By the application synchronization method provided in the fifth aspect, the second electronic device can maintain a communication connection and communicate with each other with the first electronic device and the server based on the identification generated by the first electronic device. Therefore, the first electronic device can synchronize at least one application installed in the first electronic device to the second electronic device through the server, the difference among device types among the electronic devices, operating systems among the electronic devices and application names and application versions of the applications in the electronic devices is not needed to be considered, the synchronization of various application names and application versions among the electronic devices of various operating systems and device types is realized through the transmission of application information, or the synchronization of various application names, application versions and application service conditions among the electronic devices of various operating systems and device types is realized, account sharing is not needed, additional hardware modules are not needed to be added, the realization process is convenient and quick, the cost of synchronous application among the electronic devices is reduced, and the user experience of synchronous application among the electronic devices is improved.

In one possible design, obtaining the third identification from the first electronic device includes:

the fourth identifier is identified by scanning and identifying the character code or the two-dimensional code displayed by the first electronic equipment;

and acquiring the third identifier based on the fourth identifier.

In one possible design, based on the fourth identification, obtaining the third identification includes:

displaying a seventh interface, the seventh interface including a fourth identifier;

after the modified content is received within the preset time period, the fourth identifier is changed based on the modified content, and a third identifier is obtained;

or, the fourth identifier is determined to be the third identifier after the correct operation for determining the fourth identifier is received within the preset time period or after the modified content is not received after the preset time period.

Therefore, the second electronic device can assist the second electronic device to obtain the accurate third identification based on the user will, and the phenomenon that the second electronic device possibly has identification errors is fully considered.

In one possible design, when the second electronic device includes the seventh application, obtaining the third identification from the first electronic device includes:

and after receiving a sixth operation triggered on one control of the seventh application, acquiring a third identifier from the first electronic device, wherein the sixth operation is used for triggering the second electronic device to acquire the third identifier.

In one possible design, the seventh application is an application marketplace or system setting.

Therefore, the second electronic device can acquire the third identifier by utilizing the seventh application, and the operation is convenient and fast.

In one possible design, installing at least one application in the second electronic device based on the eleventh message includes:

displaying an eighth interface, the eighth interface comprising at least one application;

and after receiving the operation of selecting the eighth application from the at least one application by the user, installing the eighth application in the second electronic device.

Therefore, the second electronic equipment can directly install at least one application by default, and can also install the application selected by the user from the at least one application based on the user wish, so that the synchronous application has more flexibility and user freedom.

In one possible design, after installing the at least one application in the second electronic device based on the eleventh message, the method further comprises:

and displaying fourth content, wherein the fourth content is used for indicating the second electronic equipment to synchronously complete at least one application.

Thus, the second electronic device may alert the user that the second electronic device has completed application synchronization.

In one possible design, the method further comprises:

A twelfth message is sent to the server, the twelfth message being used by the server to notify the first electronic device that the second electronic device completes at least one application in synchronization.

Thus, the first electronic device can remind the user that the second electronic device has completed application synchronization.

In a sixth aspect, the present application provides an application synchronization method, which is applied to a server.

The method comprises the following steps:

receiving a seventh message from the first electronic device, the seventh message comprising a third identification and information of the at least one application;

receiving a tenth message from the second electronic device, the tenth message including the third identification;

an eleventh message is sent to the second electronic device, the eleventh message including information of the at least one application, the eleventh message being for the second electronic device to install the at least one application in the second electronic device.

In one possible design, after receiving the seventh message from the first electronic device, the method further includes:

storing the third identification;

an eighth message is sent to the first electronic device, the eighth message indicating that the server has stored the third identification.

In one possible design, sending the eleventh message to the second electronic device includes:

determining an application name and an application version of at least one application in a second electronic device based on the mapping relationship and the application name and the application version of the at least one application in the first electronic device;

An eleventh message is sent to the second electronic device based on the application name and the application version of the at least one application in the second electronic device.

In one possible design, the method further comprises:

receiving a twelfth message from the second electronic device, the twelfth message being for indicating that the second electronic device completes at least one application synchronously;

and sending a ninth message to the first electronic device, wherein the ninth message is used for notifying the first electronic device that the second electronic device synchronously completes at least one application.

The advantages of the method provided in the sixth aspect and the possible designs of the sixth aspect may be referred to in the fourth aspect and the possible embodiments of the fifth aspect, which are not described herein.

In a seventh aspect, the present application provides an electronic device, including: a memory and a processor; the memory is used for storing program instructions; the processor is configured to invoke the program instructions in the memory, to cause the electronic device to perform the application synchronization method in any one of the possible designs of the first aspect and the first aspect, or to cause the electronic device to perform the application synchronization method in any one of the possible designs of the second aspect and the second aspect, or to cause the electronic device to perform the application synchronization method in any one of the possible designs of the fourth aspect and the fourth aspect, or to cause the electronic device to perform the application synchronization method in any one of the possible designs of the fifth aspect and the fifth aspect.

In an eighth aspect, the present application provides a server, comprising: a memory and a processor; the memory is used for storing program instructions; the processor is configured to invoke program instructions in the memory to cause the server to perform the application synchronization method in any of the possible designs of the third aspect and the third aspect, or to cause the server to perform the application synchronization method in any of the possible designs of the sixth aspect and the sixth aspect.

In a ninth aspect, the present application provides a communication system, comprising: the system comprises a first electronic device, a second electronic device and a server.

The first electronic device executes the application synchronization method in the first aspect and any one of the possible designs of the first aspect. The second electronic device performs the second aspect and the application synchronization method in any one of the possible designs of the second aspect. The server performs the third aspect and the application synchronization method in any one of the possible designs of the third aspect.

Alternatively, the first electronic device performs the application synchronization method in any one of the possible designs of the fourth aspect and the fourth aspect. The second electronic device performs the application synchronization method of the fifth aspect and any one of the possible designs of the fifth aspect. The server performs the application synchronization method of the sixth aspect and any one of the possible designs of the sixth aspect.

In a tenth aspect, the present application provides a chip system for use in an electronic device comprising a memory, a display screen, and a sensor; the chip system includes: a processor; when the processor executes the computer instructions stored in the memory, the electronic device performs the application synchronization method in any one of the possible designs of the first aspect and the first aspect, or the electronic device performs the application synchronization method in any one of the possible designs of the second aspect and the second aspect, or the electronic device performs the application synchronization method in any one of the possible designs of the fourth aspect and the fourth aspect, or the electronic device performs the application synchronization method in any one of the possible designs of the fifth aspect and the fifth aspect.

In an eleventh aspect, the present application provides a chip system applied to an electronic device including a memory and a sensor; the chip system includes: a processor; when the processor executes the computer instructions stored in the memory, the electronic device performs the application synchronization method in any one of the possible designs of the third aspect and the third aspect, or the electronic device performs the application synchronization method in any one of the possible designs of the sixth aspect and the sixth aspect.

In a twelfth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, causes an electronic device to implement the method of application synchronization in any of the above aspects and any of the possible designs of any of the aspects.

In a thirteenth aspect, the present application provides a computer program product comprising: executing instructions stored in a readable storage medium, the executing instructions readable by at least one processor of the electronic device, the executing instructions executable by the at least one processor causing the electronic device to implement the application synchronization method in any one of the aspects and any one of the possible designs of the aspect.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 2 is a signaling interaction diagram of an application synchronization method according to an embodiment of the present application;

fig. 3A-3J are schematic diagrams of a man-machine interaction interface according to an embodiment of the present application;

fig. 4A to fig. 4H are schematic diagrams of a man-machine interaction interface according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 6 is a signaling interaction diagram of an application synchronization method according to an embodiment of the present application;

Fig. 7A-7I are schematic diagrams of a man-machine interaction interface according to an embodiment of the present application;

FIGS. 8A-8C are diagrams illustrating a human-computer interaction interface according to an embodiment of the present application;

fig. 9A-9C are schematic diagrams of a man-machine interaction interface according to an embodiment of the present application;

FIGS. 10A-10B are schematic diagrams illustrating a human-computer interaction interface according to an embodiment of the present application;

fig. 11 is a signaling interaction diagram of an application synchronization method according to an embodiment of the present application;

fig. 12 is a signaling interaction diagram of an application synchronization method according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure;

fig. 14 is a software block diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c alone may represent: a alone, b alone, c alone, a combination of a and b, a combination of a and c, b and c, or a combination of a, b and c, wherein a, b, c may be single or plural. Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The terms "center," "longitudinal," "transverse," "upper," "lower," "left," "right," "front," "rear," and the like refer to an orientation or positional relationship based on that shown in the drawings, merely for convenience of description and to simplify the description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore should not be construed as limiting the present application.

The application synchronization method and the electronic device can realize at least one application synchronization among devices by using the same dynamic identifier to transfer application information on the premise of not depending on an account number, do not involve interaction of personal privacy data of users, do not need to add a new hardware module to interact data, do not consider differences of an operating system and device types among the electronic devices and differences of application versions of the applications in the electronic devices, are favorable for rapidly realizing synchronous application requirements of the users, and are also favorable for application use popularization.

Wherein, the above mentioned independent account number refers to a non-login account number or a non-public account number.

The type of the operating system of the electronic device is not limited in this application. For example, an Android system, a Linux system, a Windows system, an OpenEuler system, an iOS system, a hong OS system (harmony operating system, hong OS), and the like.

The electronic device may be a tablet computer, a mobile phone (such as a folding screen mobile phone, a large screen mobile phone, etc.), a notebook computer, a wearable device, a vehicle-mounted device, an augmented reality (augmented reality, AR)/Virtual Reality (VR) device, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (personal digital assistant, PDA), a smart television, a smart screen, a high-definition television, a 4K television, a smart speaker, a smart projector, etc., which is not limited in specific types of electronic devices.

The application synchronization method provided by the application is described in detail below with reference to the accompanying drawings and application scenes.

Scene one

In scenario one, one electronic device may synchronize, via a server, one or more applications installed in another electronic device.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application.

As shown in fig. 1, a communication system 10 of the present application may include: electronic device 11, electronic device 12, server 13, and server 14.

The electronic device 11 is respectively connected with the electronic device 12 and the server 13 in a communication way, the electronic device 12 is also connected with the server 13 in a communication way, and the server 14 is also connected with the server 13 or the electronic device 11 in a communication way.

The electronic device 11 and the electronic device 12 may be different types of operating systems, or may be the same type of operating system, and the foregoing operating systems may be referred to the description of the operating system of the electronic device, which is not described herein.

The electronic device 11 and the electronic device 12 may be different device types or the same device type.

The electronic device 11 and the electronic device 12 may be the same vendor or different vendors.

The communication connection referred to herein may comprise a wired communication connection, which may be such as an electrical cable, optical fiber, digital subscriber line (digital subscriber line, DSL), etc., and/or a wireless communication connection, which may be such as Bluetooth, infrared, wireless (Wi-Fi), microwave, etc.

Included in the electronic device 11 is a dynamic code generation (generate dynamic code) module. The dynamic code generation module may generate an identification 1, the identification 1 having a uniqueness, the identification 1 being used to uniquely determine that the electronic device 11 requests a synchronization application. The identifier 1 may be in a representation form such as a dynamic ID, and correspondingly, the identifier 1 may be displayed by using an optical character recognition (optical character recognition, OCR) picture or a two-dimensional code of the dynamic ID.

In some embodiments, the dynamic code generation module may generate the identification 1 based on a time window. Thus, the uniqueness and randomness of the identification 1 can be ensured.

In other embodiments, the dynamic code generation module may generate the identification 1 based on the time window and the device information of the electronic device 11. Therefore, on the basis of guaranteeing the uniqueness of the identifier 1, the randomness of the identifier 1 can be increased, so that the randomness of the identifier 1 is more thorough.

In other embodiments, the dynamic code generation module may generate the identification 1 based on a time window and an encryption algorithm. Therefore, on the basis of guaranteeing the uniqueness and randomness of the identifier 1, the privacy of the identifier 1 can be further improved, and the identifier 1 is guaranteed to be irreversible.

In other embodiments, the dynamic code generation module may generate the identification 1 based on the time window, the device information of the electronic device 11, and the encryption algorithm. Thus, the uniqueness, randomness, and privacy of the identification 1 can be ensured.

The time window mentioned above is random and dynamically changed, and the time window may be a period of time that dynamically changes, for example, a period of time including the current time, or may be a time, for example, the current time, which is not limited in the present application.

The above-mentioned device information of the electronic device 11 is used to uniquely identify the electronic device 11, and the device information may take a form such as a device identification number (identity document, ID) (may also be referred to as a serial number or an account number), a device model number, or a device number, which is not limited in this application.

The specific type of the encryption algorithm mentioned above is not limited in this application.

The electronic device 11 may communicate the identification 1 to the server 13, corresponding to step "1, identification 1" in fig. 1.

In some embodiments, the electronic device 11 may cache the identification 1 in the server 13 such that the server 13 may learn, based on the identification 1, that the electronic device 11 has requested a synchronized application, i.e., the electronic device 11 initiated a request to synchronize at least one application installed in other electronic devices.

The electronic device 11 may communicate the identification 1 to the electronic device 12, corresponding to step "2, identification 1" in fig. 1.

In some embodiments, the electronic device 11 may present an OCR picture or two-dimensional code of the dynamic ID to the electronic device 12. Included in the electronic device 12 is a dynamic code identification (extract dynamic code) module. The dynamic code recognition module can acquire the identification 1 by scanning and recognizing the OCR picture or the two-dimensional code of the dynamic ID.

The electronic device 12 may directly determine the identified identifier as identifier 1, or may verify that the identified identifier is identifier 1 by means of a user. Thus, the process of the electronic device 11 delivering the identification 1 to the electronic device 12 is completed.

Note that, the order in which the electronic device 11 transmits the identifier 1 to the server 13 and the electronic device 12 is not limited, and the electronic device may be executed sequentially or simultaneously.

In some embodiments, after electronic device 11 determines that identification 1 is stored in server 13, electronic device 11 may communicate identification 1 to electronic device 12. After determining that the identifier 1 is not stored in the server 13, the electronic device 11 may continue to pass the identifier 1 to the server 13 until it is determined that the identifier 1 is stored in the server 13. This ensures that the electronic device 11, the electronic device 12, and the server 13 share the same identifier 1.

The electronic device 12 may establish a communication connection with the electronic device 11 via the server 13 and communicate based on the identification 1 such that the electronic device 12 determines that the electronic device 11 has requested a synchronous application. Thus, the electronic device 12 can be matched with the electronic device 12 by means of the identification 1 generated by the electronic device 11 via the server 13.

And, the electronic device 12 may transmit, to the server 13, application information of each application in the electronic device 12 that needs to be synchronized, based on the identifier 1, corresponding to the step "3 in fig. 1, the identifier 1, the application information of each application in the electronic device 12 that needs to be synchronized.

Thus, based on the identification 1, the server 13 may determine that the electronic device 12 synchronizes applications to the electronic device 11, i.e. that there are applications for which the electronic device 11 needs to be synchronized.

Wherein each of the above-mentioned applications requiring synchronization refers to at least one application selected from applications installed in the electronic device 12 based on the user's intention.

Wherein the application information of each application may include at least an application name (which may also be referred to as an application package name) and an application version. In addition, the application information of each application may also include application business cases (also referred to as history cases).

When an application service of an application is an audio/video playing service, the application service condition refers to the playing progress of the audio/video in the application. The number, the size and other parameters of the audio and video are not limited.

When the application service of an application is a content display service, the application service condition refers to the browsing progress of an article/web page/document in the application. The number, size and other parameters of the articles/web pages/documents are not limited in the application.

When the application service of an application is a game service, the application service condition refers to the level record condition of the game board office in the application. The number, type, etc. parameters of the game play are not limited in this application.

When the application service of an application is a travel service, the application service condition refers to the travel record condition of a travel order in the application. The number, type and other parameters of the travel orders are not limited.

When the application service of an application is a purchase service, the application service condition refers to a purchase record condition of a record of a purchase order in the application. The number, type and other parameters of the purchase orders are not limited in the application.

The specific implementation manner of the application service case is not limited in this application.

The server 13 stores therein a mapping relationship between the electronic device of each operating system and application information of each application. The aforementioned mapping relationship may be stored in a database table, an array, a key-value pair (key-value), or the like.

For example, the server 13 may store the aforementioned mapping relationship in a wide-table manner as shown in table 1.

TABLE 1

Numbering device	Application name	Operating system 1	Operating system 2	Operating system 3	…
						1	Application b	Windows-5.2.1	Pad-18.5.3	Phone-15.8.1	…
2	Application c	Windows-2.3.1	Pad-3.1.2	Phone-12.3.1	…
						…	…	…	…	…	…

In the mapping relationship shown in table 1, in the electronic device of the operating system 1, the application version of the application b is Windows-5.2.1. In the electronic device of the operating system 2, the application version of the application b is Pad-18.5.3. In the electronic device of the operating system 3, the application version of application b is Phone-15.8.1.

In the mapping relationship shown in table 1, in the electronic device of the operating system 1, the application version of the application c is Windows-2.3.1. In the electronic device of the operating system 2, the application version of the application c is Pad-3.1.2. In the electronic device of the operating system 3, the application version of application c is Phone-12.3.1.

Thus, the server 13 can provide each electronic device with application information of each application having a mapping relationship with the operating system of the electronic device.

In some embodiments, the electronic device 11 may send a query request to the server 13 continuously or at random or at intervals, where the query request is used to query/check whether there is an application of the electronic device 11 that needs to be synchronized with the server 13, and the query request carries the identifier 1 and the operating system of the electronic device 11. The specific implementation manner of the foregoing query request is not limited in this application.

Upon receiving the application information of each application in the electronic device 12 that needs to be synchronized, which is transmitted by the electronic device 12, based on the identification 1, the server 13 may determine that there is an application that the electronic device 11 needs to be synchronized.

Thus, the server 13 can obtain the application information of each application to be synchronized in the electronic device 11 through the mapping relationship based on the operating system of the electronic device 11 and the application information of each application to be synchronized in the electronic device 12.

Any application version applied in the electronic device 11 may be the latest version or an old version, which is not limited in this application.

The server 13 may transmit to the electronic device 11 the application name of each application in the electronic device 11, or the application name and the application version, which need to be synchronized, corresponding to step "4" in fig. 1, the application information of each application in the electronic device 11.

The server 14 is used to provide installation packages for all applications. Among them, the server 14 may employ, for example, a content delivery network (content delivery network, CDN) server, or the like.

Upon receiving the application information of each application requiring synchronization in the electronic device 11, the electronic device 11 may request to download an installation package of each application requiring synchronization. Wherein the application name and application version of any one application may determine the installation package of the application.

In some embodiments, the electronic device 11 may send a download request 11 to the server 13, where the download request 11 is used to request to download an installation package of each application that needs to be synchronized, and the download request 11 carries device information of the electronic device 11 and application information of each application that needs to be synchronized in the electronic device 11. The specific implementation of the foregoing download request 11 is not limited herein. For example, the download request 11 may carry an application name, or an application name and an application version, of each application in the electronic device 11 that needs to be synchronized.

The server 13 may determine application information of each application in the electronic device 11 that needs to be synchronized and may send a download request 12 to the server 14, corresponding to step "51, request" in fig. 1. The download request 12 is used for requesting to download an installation package of each application to be synchronized, and the download request 12 carries application information of each application to be synchronized in the electronic device 11. The specific implementation of the download request 12 is not limited herein.

The server 14 sends a download response 11 to the server 13, corresponding to step "52, CDN address" in fig. 1. The download response 11 carries a CDN address, where the CDN address is used to indicate a download address/storage address of an installation packet of each application that needs to be downloaded. The specific implementation of the download response 11 is not limited herein.

The server 13 transmits a download response 12 to the electronic device 11 based on the device information of the electronic device 11, corresponding to step "6, CDN address" in fig. 1. The download response 12 carries a CDN address, where the CDN address is used to indicate a download address/storage address of an installation packet of each application that needs to be downloaded. The specific implementation of the download response 12 is not limited herein.

Thus, the electronic device 11 downloads the installation package of each application to be synchronized according to the CDN address, and based on the installation package of each application to be synchronized, corresponds to step "7 in fig. 1, the installation package of each application", and installs each application to be synchronized in the electronic device 11.

In other embodiments, the electronic device 11 may send a download request 13 to the server 14, corresponding to step "81, request" in fig. 1. The download request 13 is used for requesting to download an installation package of each application to be synchronized, and the download request 13 carries device information of the electronic device 11 and application information of each application to be synchronized in the electronic device 11. The specific implementation of the foregoing download request 13 is not limited herein.

The server 14 transmits a download response 13 to the electronic device 11 based on the device information of the electronic device 11, corresponding to step "82, CDN address" in fig. 1. The download response 13 carries a CDN address, where the CDN address is used to indicate a download address/storage address of an installation packet of each application that needs to be downloaded. The specific implementation of the download response 13 is not limited herein.

The installation package of each application that needs to be synchronized may use any version that can be downloaded and installed by the electronic device 11, such as the latest version.

In summary, the electronic device 11 may synchronize at least one application installed in the electronic device 12.

In addition, when the application information further includes an application service condition, the electronic device 11 may synchronize the application service condition of at least one application recorded in the electronic device 12, and may also synchronize the application service condition of at least one application installed in the electronic device 12 and the recorded at least one application, so that the user may use the application in the electronic device 12 in the electronic device 11 and execute the application service corresponding to the application according to the application service condition.

It should be noted that, the server 13 and the server 14 may be the same server, or may be different servers in a server cluster, which is not limited in this application.

Based on the above description, the electronic device 11 can synchronize at least one application installed in the electronic device 12, or synchronize an application service condition of at least one application recorded in the electronic device 12, or synchronize at least one application installed in the electronic device 12 and an application service condition of at least one application recorded by means of the identifier 1 through the server 13 and the server 14.

Next, in connection with fig. 2, taking an example that an application a is installed in the electronic device 11 and an application b, an application c, and an application d are installed in the electronic device 12, a specific implementation procedure of the electronic device 11 to synchronize the application c and the application d installed in the electronic device 12 will be described in detail.

The application a, the application b, the application c and the application d may be a system application or a third party application, which is not limited in this application. For example, application a may be an application market (AppGallery) in electronic device 11 and application b may be an application market (AppGallery) in electronic device 12.

Referring to fig. 2, fig. 2 is a signaling interaction diagram of an application synchronization method according to an embodiment of the present application.

As shown in fig. 2, the application synchronization method of the present application may include:

s11, the application a receives operation 1 on the control 1, wherein the operation 1 is used for starting a synchronous application function.

Wherein the control 1 is used to start a synchronous application function of the electronic device 11. The shape, position, size and other parameters of the control 1 are not limited in the application. Operation 1 may be an operation triggered on control 1, the types of operation 1 including, but not limited to, at least one of click, long press, double click, etc.

For example, the control 1 may be displayed in a user interface of the application a, or may be displayed on a card located in a main interface/minus one-screen interface of the electronic device 11 after the application a is started, which is not limited in this application.

S12, the application a responds to the operation 1 to generate an identification 1, wherein the identification 1 is used for uniquely determining the electronic device 11 to initiate the synchronous application request 1.

Upon receiving operation 1, application a may determine that electronic device 11 initiated synchronization application request 1 and may invoke a dynamic code generation module in electronic device 11 to generate identity 1.

The request 1 for synchronizing an application initiated by the electronic device 11 refers to a request initiated by the electronic device 11 to synchronize at least one application installed in other electronic devices.

The specific implementation of the identifier 1 is not limited in this application. The generation manner of the identifier 1 may refer to the description of the electronic device 11 for generating the identifier 1, which is not described herein.

S13, the application a sends a message 11 to the server 13, wherein the message 11 carries the identifier 1 or the identifier 1 and the device information of the electronic device 11.

Wherein the device information of the electronic device 11 is used for uniquely determining the electronic device 11. Thus, the server 13 can determine, based on the device information of the electronic device 11, that the message 13 is sent by the electronic device 11, can also determine that the identifier 1 corresponds uniquely to the electronic device 11, and can also establish a communication connection and communicate with the application a.

Note that, the device information of the electronic device 11 may be carried in the message 11 in S13, the message 13 in S17, or both the messages, which is not limited in this application. Thereby, the server 13 has obtained the device information of the electronic device 11.

S14, after receiving the message 11, the server 13 learns that the electronic device 11 initiates the synchronous application request 1 and stores the identifier 1.

Based on S13-S14, the application a may write and store the identifier 1 in the server 13, so that the server 13 knows that the electronic device 11 uniquely corresponding to the identifier 1 requests the synchronous application, which is beneficial for the server 13 to use the identifier 1 as a bridge for the synchronous application of the electronic device 12 to the electronic device 11.

S15, the server 13 sends a message 12 to the application a, where the message 12 is used to indicate that the server 13 has stored the identifier 1.

S16, after receiving the message 12, the application a displays the character code or the two-dimensional code of the identifier 1.

Based on S15-S16, the server 13, after storing the identity 1, may send a message 12 to the application a, so that the application a knows that the identity 1 is stored in the server 13. After determining that the identifier 1 is stored in the server 13, the application a may display a character code or a two-dimensional code of the identifier 1. Therefore, the electronic device 11 can transmit the identifier 1 to the server 13, which is beneficial to ensuring that the electronic device 11, the server 13 and the electronic device 12 can share the same identifier 1.

After a certain period of time, the application a does not receive the message 12, and may continue to execute S13, send the message 11 to the server 13, and may not execute S16 until the application a receives the message 12 from the server 13. In the resent message 11, the application a may not update the identifier 1, or may update the identifier 1, which is not limited in this application.

In some embodiments, the user may trigger an operation on a control in application a for updating identity 1, enabling application a to update identity 1.

The control used for updating the identifier 1 may be the control 1, or may be other controls in the application a except the control 1. The present application does not limit the shape, position, size, etc. of the control for updating the identifier 1. The types of operations on the control for updating identity 1 include, but are not limited to, at least one type of click, long press, double click, and the like.

After the end of the execution of S16 by the application a, the application a may execute S17 and S18.

The execution sequence of S17 and S18 is not limited, and may be executed sequentially or simultaneously.

S17, the application a sends a message 13 to the server 13, the message 13 is used for inquiring whether the application which needs to be synchronized by the electronic equipment 11 exists, and the message 13 carries the identifier 1 and equipment information of the electronic equipment 11.

The application a may send a message 13 to the server 13 continuously or sporadically or for a period of time each interval until the server 13 determines that there is an application for which the electronic device 11 needs to be synchronized, the server 13 may perform S28.

For example, the application a may send the message 13 to the server 13 at intervals in a polling manner, so that the server 13 can timely feed back the application requiring synchronization to the application a.

The device information of the electronic device 11 may be referred to the description of the embodiment S13, which is not described herein. Also, in the case where the device information of the electronic device 11 can be carried in the message 11 of S13, S17 may be optional.

S18, the application b obtains the identifier 1 by scanning and identifying the character code or the two-dimensional code of the identifier 1.

The application b can call a dynamic code identification module in the electronic equipment 12 to scan and identify the character code or the two-dimensional code of the identifier 1, and can acquire the identifier 1.

The method for scanning and identifying the character code or the two-dimensional code of the identifier 1 by the application b is not limited.

In some embodiments, when the screen of the electronic device 11 displays the character code or the two-dimensional code of the logo 1, the application b may scan against the screen of the electronic device 11 after receiving an operation on one control of the application b. Wherein the control has the functions of scanning and identifying. The specific implementation of the control is not limited in this application.

In other embodiments, the electronic device 11 may transmit the picture or the link of the character code or the two-dimensional code of the identifier 1 to the electronic device 12 through other electronic devices or servers, for example, share the picture or the link through an app on the electronic device 11, or share the picture or the web page corresponding to the character code or the two-dimensional code of the identifier 1 through a near field communication manner, so that the electronic device 12 may obtain the picture or the web page corresponding to the character code or the two-dimensional code of the identifier 1. Therefore, the application b can scan the picture or the webpage corresponding to the character code or the two-dimensional code of the identifier 1 when the scanning function is started. If the application b identifies correctly, the identified identity is identity 1. If application b identifies an error, then the identified identity is not identity 1. Thus, after application b recognizes an identity, such as identity 2, application b may determine the recognized identity as identity 1 using a variety of implementations.

In some embodiments, application b may perform the following process:

and step 1, displaying the recognized character code or the two-dimensional code of the mark 2 by the application b. Therefore, the application b can display the character code or the two-dimensional code of the identifier 2 to the user, and the user can conveniently judge whether the character code of the identifier 1 is the same as the character code of the identifier 2 or whether the two-dimensional code of the identifier 1 is the same as the two-dimensional code of the identifier 2.

And 2, judging whether the modification content for modifying the identified identifier 2 is received in the duration 1 by the application b.

And 3, when receiving the modified content, determining the identifier 1 by the application b based on the modified content. Thus, application b may change the identified identity 2 to identity 1 based on user intent.

And 4, when the modified content is not received, the application b determines that the identified identifier 2 is the identifier 1. Thus, the application b determines the identified tag 2 as tag 1 based on the user's intention.

Thus, the application b can obtain the identification 1 generated by the electronic device 11 based on the user's wish.

In other embodiments, application b may directly determine that the identified tag 2 is the tag 1 when the electronic device 12 has a higher accuracy of identification.

In summary, application b may obtain identity 1.

S19, the application b sends a message 14 to the server 13, the message 14 is used for inquiring whether the server 13 stores the identifier 1, and the message 14 carries the identifier 1 and the device information of the electronic device 12.

Wherein the device information of the electronic device 12 is used to uniquely identify the electronic device 12. Thus, the server 13 can determine, based on the device information of the electronic device 12, that the message 14 was sent by the electronic device 12, and can also establish a communication connection with and communicate with the application b.

S20, the server 13 determines whether the identifier 1 is stored in the server 13 after receiving the message 14.

S21, after determining that the identifier 1 is stored in the server 13, the server 13 sends a message 15 to the application b, where the message 15 is used to indicate that the identifier 1 is stored in the server 13.

S22, after receiving the message 15, the application b determines that there is an electronic device (i.e. the electronic device 11) uniquely corresponding to the identifier 1, and initiates the synchronous application request 1.

Based on S19-S22, the application b may send a message 14 to the server 13, so that the server 13 may determine whether the identity 1 is stored in the server 13.

Upon determining that the identity 1 is stored in the server 13, the server 13 may send a message 15 to the application b so that the application b may determine that the electronic device 11 has requested a synchronized application.

Upon determining that the identifier 1 is not stored in the server 13, the server 13 may send a message to the application b indicating that the identifier 1 is not stored in the server 13, or may not send a message to the application b, so that the application b may determine that there is no electronic device corresponding to the identifier 1 requesting the synchronization application.

Thus, the application b may re-execute S18, acquire the identifier 1 again by scanning and identifying the character code or the two-dimensional code of the identifier 1, and continue executing S19-S22 until the application b determines that the electronic device 11 has requested the synchronization application. Thus, the application b can avoid the problem of erroneous identification by scanning and identifying again.

In addition, the application b may display a first hint content for reminding the user that the application b has failed to recognize. The first prompt content can display corresponding characters, symbols, voice, icons and the like in a popup window or icon mode. Thus, the user can scan the character code or the two-dimensional code of the logo 1 using the electronic device 12 conveniently, so that the application b can re-execute S18.

In summary, the application b can verify whether the electronic device 11 requests the synchronous application by storing the identifier 1 in the server 13, so as to realize the matching between the electronic device 11 and the electronic device 12, and ensure that the electronic device 11, the server 13 and the electronic device 12 share the same identifier 1.

It should be noted that S19 to S22 may be optional.

S23, the application b displays an application list, where the application list is used to indicate that the electronic device 12 includes at least the application c and the application d that can be synchronized.

After determining that there is a request for a synchronizable application by the electronic device 11, the application b may display an application list to facilitate presentation of at least one application synchronizable in the electronic device 12 to the user, such that the user can flexibly and conveniently select the application in the electronic device 12 to synchronize with the electronic device 11.

The application list is used to indicate that at least one application that can be synchronized is included in the electronic device 12, and any application in the application list may be displayed, for example, in a text, a letter, an icon, a user interface component (user interface module, a UI component), or the like.

S24, the application b receives an operation 2 on the application list, wherein the operation 2 is used for indicating that the application c and the application d need to be synchronized.

Wherein operation 2 may be an operation triggered on control 2 in the application list, the types of operation 2 include, but are not limited to, at least one type of click, long press, double click, etc. The shape, position, size and other parameters of the control 2 are not limited in the application.

For example, application b may display an icon of application c and a selection control of application c, an icon of application d and a selection control of application d, and a synchronization control in the application list. The application c selection control is used for providing an entry for selecting the application c, the application d selection control is used for providing an entry for selecting the application d, and the synchronization control is used for providing an entry for determining the selected application as an application needing synchronization.

After receiving the operation triggered on the selection control of the application c, the application b can determine that the user selects the application c. After receiving the operation triggered on the selection control of the application d, the application b can determine that the user selects the application d. After receiving the operation triggered on the synchronization control, the application b can determine that the application c and the application d selected by the user are the applications needing synchronization. The synchronous control is control 2, and the operation triggered on the synchronous control is operation 2.

S25, the application b determines application information of the application c in the electronic device 12 and application information of the application d in the electronic device 12 in response to the operation 2. Upon receiving operation 2, application b may determine application c and application d as applications that electronic device 12 synchronizes with electronic device 11, and may determine application information for each of application c and application d in electronic device 12.

Wherein the application information includes at least an application name and an application version. In addition, the application information may also include application business conditions. The specific implementation manner of the application information of each application can be referred to the foregoing description, and will not be repeated here.

S26, the application b sends a message 16 to the server 13, wherein the message 16 carries the identifier 1, the application information of the application c in the electronic device 12 and the application information of the application d in the electronic device 12.

S27, the server 13 determines, based on the identifier 1, that the electronic device 12 applies synchronously to the electronic device 11, and determines, based on the mapping relationship, application information of the application c in the electronic device 11 and application information of the application d in the electronic device 11.

Upon receipt of the message 16, the server 13 may parse the message 16. After obtaining the identification 1 from the message 16, the server 13 can learn that the electronic device 12 is synchronizing the application to the electronic device 11.

Thus, the server 13 can determine the application information of the application c in the electronic device 11 and the application information of the application d in the electronic device 11 through the mapping relationship based on the device information of the electronic device 11, the application information of the application c in the electronic device 12, and the application information of the application d in the electronic device 12.

Wherein, the server 13 can determine that the application version of the application c in the electronic device 11 is an old version through the mapping relationship based on the application version of the application c in the electronic device 12. At this time, the server 13 may recommend that the application c be the old version in the electronic device 11 to the electronic device 11, or may recommend that the application version of the application c in the electronic device 11 be the latest version to the electronic device 11.

The server 13 may determine that the application version of the application c in the electronic device 11 is the latest version through the mapping relationship based on the application version of the application c in the electronic device 12. At this time, the server 13 may recommend to the electronic device 11 that the application version of the application c in the electronic device 11 be the latest version.

Similarly, the server 13 may determine, based on the application version of the application d in the electronic device 12, that the application version of the application d in the electronic device 11 is an old version through the mapping relationship. At this time, the server 13 may recommend that the version of the application d in the electronic device 11 be the old version to the electronic device 11, or may recommend that the version of the application d in the electronic device 11 be the latest version to the electronic device 11.

The server 13 may determine that the application version of the application d in the electronic device 11 is the latest version through the mapping relationship based on the application version of the application d in the electronic device 12. At this time, the server 13 may recommend to the electronic device 11 that the application version of the application d in the electronic device 11 be the latest version.

The specific implementation manner of the above mentioned mapping relationship may be referred to the above mentioned description, and will not be repeated here.

S28, the server 13 sends a message 17 to the application a, wherein the message 17 carries application information of the application c in the electronic device 11 and application information of the application d in the electronic device 11.

Based on S27, the server 13 may carry the application information of the application c in the electronic device 11 and the application information of the application d in the electronic device 11 in the message 17, and transmit the message 17 to the application a based on the device information of the electronic device 11, so that the application a can quickly determine that the application c and the application d need to be synchronized.

It should be noted that, if the application b determines that the application information of the application c and/or the application d in the electronic device 12 includes the application name, the application version, and the application service condition, the message 16 sent by the application b in S26 to the server 13 carries the application name, the application version, and the application service condition of the application c and/or the application d in the electronic device 12. And, the message 17 sent by the server 13 in S28 to the application a carries the application name, the application version and the application service condition of the application c and/or the application d in the electronic device 11.

S291, after receiving the message 17, the application a determines that the application c and the application d need to be synchronized.

Application a, upon receiving message 17, may determine that electronic device 12 synchronized application c and application d installed in electronic device 12 with electronic device 11.

In some embodiments, application a may default to synchronizing (i.e., downloading and installing) application c and application d, and may perform S292.

In other embodiments, application a may also display a user interface that may be used to present to the user at least one content, such as an icon, application name, etc., of each application that needs to be synchronized, provide access to select at least one application, and provide access to determine the selected application. Application a may determine that application c and/or application d need to be synchronized based on user intent.

For ease of illustration, application c and application d are illustrated as applications of the electronic device 11 that need to be synchronized. Thus, application a may determine that application c and application d need to be synchronized, and may execute S292.

In addition, the application a may also determine whether the application c and the application d are installed in the electronic device 11, and whether the application version of the application c and/or the application d installed in the electronic device 11 needs to be updated. Thus, the user interface may also be used to present to the user the installation status of each application that needs to be synchronized, such as whether an application is installed in the electronic device 11, the version of the application that is installed in the electronic device 11, and so on.

S292, the application a sends a message 18 to the server 13 based on the application information of the application c in the electronic device 11 and the application information of the application d in the electronic device 11, and the message 18 is used for requesting to download the installation package of the application c and the installation package of the application d.

The specific implementation of the message 18 is not limited herein. For example, the message 18 may carry an application name of the application c in the electronic device 11 and an application name of the application d in the electronic device 11, or an application name and an application version of the application c in the electronic device 11 and an application name and an application version of the application d in the electronic device 11.

S293, the server 13 obtains the CDN address from the server 14, and sends a message 19 to the application a, where the message 19 carries the CDN address, and the CDN address is used to indicate a storage location of the installation package of the application c and the installation package of the application d.

S294, the application a downloads the installation package of the application c and the installation package of the application d based on the CDN address, installs the application c based on the installation package of the application c, and installs the application d based on the installation package of the application d.

In addition, after the application a successfully installs the application c and the application d, a second prompt content may be displayed, where the second prompt content is used to remind the user that the application c and the application d have been successfully installed. The second prompt content can display corresponding characters, symbols, voice, icons and the like in a popup window or icon mode.

In addition, after the application a successfully installs the application c and the application d, an indication message 11 may be sent to the server 13, where the indication message 11 is used to instruct the electronic device 12 to complete the application c and the application d synchronously. The server 13 may send an indication message 12 to the electronic device 12, the indication message 12 being used to indicate to the electronic device 12 that the application c and the application d are completed synchronously.

Thus, the electronic device 12 may display fifth prompting content for prompting the user of the electronic device 12 to complete application c and application d synchronously. The fifth prompting content can display corresponding characters, symbols, voice, icons and the like in a popup window or icon mode.

In addition, when the application information of the application c or the application d further includes an application service condition, after the application c or the application d is started, the tablet computer can execute the application service corresponding to the application c or the application d according to the application service condition.

For example, when the application c is a travel application, after the tablet computer starts the travel application, a travel order in the travel application can be found according to the travel record condition. When the application d is the sports health application, the tablet computer can display corresponding sports data in the sports health application according to the sports record condition after starting the sports health application.

Based on the description of the embodiment of fig. 2, electronic device 11 may synchronize multiple applications to electronic device 12. In addition, according to a similar description of the embodiment of fig. 2, the electronic device 11 may synchronize an application with the electronic device 12, which is not described herein.

Thus, the electronic device 11 may synchronize at least one application installed in the electronic device 12, may also synchronize application traffic conditions of the at least one application recorded in the electronic device 12, and may also synchronize application traffic conditions of the at least one application installed in the electronic device 12 and the at least one application recorded. In the first scenario, the electronic device 11, the electronic device 12 and the server 13 may implement communication connection and mutual communication between the electronic device 11, the electronic device 12 and the server 13 by using the identifier generated by the electronic device 11. Based on the identification, the electronic device 11 may notify the server 13 that the electronic device 11 has requested a synchronization application and query the server 13 as to whether there is an application that the electronic device 11 needs to synchronize. Based on the identification, the electronic device 12 may notify the server 13 that the electronic device 12 synchronized the application to the electronic device 11, and transmit application information in the electronic device 12 for each application that needs to be synchronized to the server 13. The server 13 may determine application information of each application to be synchronized in the electronic device 11 based on the mapping relationship, and transmit the application information of each application to be synchronized in the electronic device 11 to the electronic device 11. The electronic device 11 can acquire an installation package of each application requiring synchronization through the server 13 and the server 14, and install each application requiring synchronization in the electronic device 11.

Therefore, the electronic device 11 can synchronize at least one application installed in the electronic device 12 through the server 13 and the server 14 based on the identifier generated by the electronic device 11, without considering the differences among device types among the electronic devices, operating systems among the electronic devices, application names and application versions of the applications in the electronic devices, and the key is that through the transmission of application information, the synchronization of various application names and application versions among the electronic devices of various operating systems and device types is realized, or the synchronization of various application names, application versions and application service conditions among the electronic devices of various operating systems and device types is realized, the account sharing is not needed, additional hardware modules are not needed to be added, the realization process is convenient and quick, the cost of synchronizing the application among the electronic devices is reduced, and the user experience of synchronizing the application among the electronic devices is improved.

Based on the descriptions shown in fig. 1 to 2, a specific implementation procedure of the electronic device 11 to synchronize the application c and the application d installed in the electronic device 12 will be described with reference to fig. 3A to 3J and fig. 4A to 4H.

For convenience of explanation, in fig. 3A to 3J and fig. 4A to 4H, the electronic device 11 is taken as a tablet computer, the application a is taken as an application market 1 or a system setting 1 in the tablet computer, the electronic device 12 is taken as a mobile phone, the application b is taken as an application market 2 or a system application 2 in the mobile phone, the application c is a travel application in the mobile phone, the application d is a motion health application in the mobile phone, the server 13 is taken as a background server, and the server 14 is taken as a CDN server for illustration.

Referring to fig. 3A-3J, fig. 3A-3J are schematic diagrams of a man-machine interface according to an embodiment of the present application.

The tablet computer may display a user interface 11 as exemplarily shown in fig. 3A. Wherein the user interface 11 may be a home screen of a desktop, the user interface 11 may include, but is not limited to: status bars, navigation bars, calendar indicators, weather indicators, and a plurality of application icons, etc. The application icon includes at least: the icon 3011 of the application marketplace 1 may further include: such as an icon 3012 for system setup 1, an icon for a tablet manager, an icon for a browser, an icon for an email application, a memo icon, an icon for a gallery, an icon for a video playback application, and the like.

When the application a is the application market 1 in the tablet computer, the tablet computer may execute the following:

upon detecting a user-indicated operation to launch application marketplace 1 (e.g., clicking on icon 3011 of application marketplace 1), the tablet computer may display user interface 12, shown in an example of fig. 3B. Wherein the user interface 12 may be used to display a page (e.g., a main page) of the application marketplace 1.

In fig. 3B, the user interface 12 may include: control 302. Wherein the control 302 is in a first state, which may be used to provide an entry for starting the synchronized application function of the tablet computer.

Additionally, the user interface 12 may include therein: control 303, region 304, and region 305. Among other things, control 303 may be used to display applications installed in a tablet. The area 304 may be used to alert the user that the tablet may provide a synchronized application function. The area 305 may be used to provide an entry for the tablet login account and display the status of whether the tablet login account is logged in. For example, region 305 is used to indicate the status of the tablet computer not logged into the account.

Upon detecting that the user performs an operation such as clicking on control 302 in user interface 12 shown in fig. 3B, the tablet computer may generate identity 1 (the process may be described with reference to S11-S12 in fig. 2), and write and store identity 1 in the backend server (the process may be described with reference to S13 in fig. 2).

After determining that the identifier 1 is stored in the background server, the tablet computer may change from displaying the user interface 12 illustrated in fig. 3B to displaying the user interface 12 illustrated in fig. 3C (see description of S15-S16 in fig. 2 for this procedure).

In fig. 3C, the user interface 12 may be used to display the character code of the logo 1 and provide access to the synchronized application function of the closed tablet computer. In some embodiments, the control 302 switches from the first state to the second state, and may be used to provide access to the synchronized application functions of the closed tablet. Also, a region 3061 may also be included in the user interface 12. Wherein the region 3061 may be used to display a character code for identification 1. Additionally, a control 3062 may also be included in the user interface 12. Among other things, control 3062 can be used to provide entry for updating the character code for identification 1.

Alternatively, the tablet computer may change from displaying the user interface 12 shown in the example of fig. 3B to displaying the user interface 12 shown in the example of fig. 3D after determining that the identifier 1 is stored in the background server (the process may be described with reference to S15-S16 in fig. 2).

In fig. 3D, the user interface 12 may be used to display the two-dimensional code of the logo 1 and provide access to the synchronized application function of closing the tablet computer. In some embodiments, the control 302 switches from the first state to the second state, and may be used to provide access to the synchronized application functions of the closed tablet. Also, an area 3071 may also be included in the user interface 12. Wherein the area 3071 may be used to display the two-dimensional code of logo 1. In addition, controls 3072 may also be included in the user interface 12. Wherein control 3072 can be used to provide an entry to update the two-dimensional code for identification 1.

It should be noted that, the tablet personal computer may selectively display the character code of the identifier 1, may selectively display the two-dimensional code of the identifier 1, and may selectively display the character code and the two-dimensional code of the identifier 1, which is not limited in this application.

In addition, control 3062 or control 3072 is optional. In fig. 3C or fig. 3D, the tablet computer may automatically update the character code or the two-dimensional code of the identifier 1 after a period of time passes, or may update the character code or the two-dimensional code of the identifier 1 after detecting the operation triggered on the control 3062 or the control 3072, which is not limited in this application.

After the character code or the two-dimensional code of the identifier 1 is displayed on the tablet personal computer, a channel for acquiring the identifier 1 can be provided for the mobile phone, and whether the application of the tablet personal computer to be synchronized exists or not can be inquired to a background server through a period of time (such as 15 s) of the identifier 1, and the method can be also understood as: the tablet computer inquires of the background server whether the application market 2 in the mobile phone synchronizes the application information of the application b and the application information of the application c (the process can be described with reference to S17 in fig. 2).

When the application a sets 1 for the system in the tablet computer, the tablet computer may execute the following:

upon detecting a user-indicated operation to initiate system setting 1 (e.g., clicking on icon 3012 of system setting 1), the tablet computer may display user interface 13, shown in an example of fig. 3E. Wherein the user interface 13 may be used to display one page (e.g. the main page) of the system settings 1.

In fig. 3E, the user interface 13 may include: control 308. Among other things, control 308 may be used to provide access to launch the synchronized application functionality of the tablet.

Upon detecting that the user performs an operation such as clicking on control 308 in user interface 13 shown in fig. 3E, the tablet computer may generate identity 1 (the process may be described with reference to S11-S12 in fig. 2), and write and store identity 1 in the backend server (the process may be described with reference to S13 in fig. 2).

After determining that the identifier 1 is stored in the background server, the tablet computer may change from displaying the user interface 13 illustrated in fig. 3E to displaying the user interface 13 illustrated in fig. 3F (see description of S15-S16 in fig. 2 for this procedure).

In fig. 3F, the user interface 13 may be used to display the character code of the logo 1. In some embodiments, the user interface 13 may also include an area 3101 therein. Wherein the area 3101 may be used to display a character code of identification 1. Additionally, controls 3102 may also be included in the user interface 13. Among other things, control 3102 can be used to provide an entry for updating the character code of identification 1.

Alternatively, the tablet computer may change from displaying the user interface 13 shown in the example of fig. 3E to displaying the user interface 13 shown in the example of fig. 3G after determining that the identifier 1 is stored in the background server (the process may be described with reference to S15-S16 in fig. 2).

In fig. 3G, the user interface 13 may be used to display the character code of the logo 1. In some embodiments, region 3111 may also be included in user interface 13. Wherein region 3111 may be used to display a character code for identification 1. Additionally, controls 3112 may also be included in user interface 13. Among other things, control 3112 can be used to provide entry for updating the character code for identification 1.

In addition, in fig. 3F or fig. 3G, the user interface 13 may also be used to provide an entry for displaying the character code of the identifier 1, an entry for displaying the two-dimensional code of the identifier 1, and an entry for closing the synchronous application function of the tablet computer.

In some embodiments, the user interface 13 may include therein: control 3091 and control 3092. Among other things, control 3091 may be used to provide an entry for displaying the character code for identification 1. Control 3092 may be used to provide an entry to display the two-dimensional code for logo 1. The blank area in the user interface 13 is used to provide access to the synchronized application functions of the closed tablet.

Thus, after detecting that the user performs an operation such as clicking on the control 3092 in the user interface 13 shown in fig. 3F, the tablet computer may display the two-dimensional code of the identification 1 in the user interface 13 shown in fig. 3G. Upon detecting that the user performs an operation such as clicking on control 3091 in user interface 13 shown in fig. 3G, the tablet computer may display the character code of identification 1 in user interface 13 shown in fig. 3F. Therefore, the switching between the character code of the identifier 1 and the two-dimensional code of the identifier 1 is flexibly realized.

In addition, control 3102 or control 3112 is optional. In fig. 3F or fig. 3G, the tablet computer may automatically update the character code or the two-dimensional code of the identifier 1 after a period of time passes, or may update the character code or the two-dimensional code of the identifier 1 after detecting the operation triggered on the control 3102 or the control 3112, which is not limited in this application.

After the character code or the two-dimensional code of the identifier 1 is displayed, the tablet personal computer can provide a channel for acquiring the identifier 1 for the mobile phone, and can query a background server through a period of time (such as 15 s) of each interval of the identifier 1 to determine whether an application of the tablet personal computer to be synchronized exists, and the method can be also understood as: the tablet computer inquires of the background server whether the application market 2 in the mobile phone synchronizes the application information of the application (see description of S17 in fig. 2 for this procedure).

In summary, the tablet computer may invoke the dynamic code generation module in the tablet computer to generate the identifier 1 by means of the application marketplace 1 or the system setting 1 in the tablet computer. The tablet personal computer can transmit the identification 1 to the background server, and the identification 1 can be transmitted to the mobile phone by displaying the character code or the two-dimensional code of the identification 1.

Based on the above description, the mobile phone can synchronize the application installed in the mobile phone selected by the user to the tablet computer through the background server based on the identifier 1, and the specific process can include the following steps:

Referring to fig. 4A to fig. 4H, fig. 4A to fig. 4H are schematic diagrams of a man-machine interaction interface according to an embodiment of the present application.

When the application b is the application market 2 in the mobile phone, the mobile phone can execute the following contents:

the handset may display a user interface 21 as exemplarily shown in fig. 4A. Wherein the user interface 21 may be a home screen of a desktop, the user interface 11 may include, but is not limited to: status bars, navigation bars, calendar indicators, weather indicators, and a plurality of application icons, etc. The application icon includes at least: icon 4011 of application marketplace 2 may further include: such as icons for smart life, music, cell phone housekeeping, memo, travel applications, sports health applications, etc.

Upon detecting a user-indicated operation to launch the application marketplace 2 (e.g., clicking on the icon 4011 of the application marketplace 2), the handset may display the user interface 22, which is shown in an example of fig. 4B. Wherein the user interface 22 may be used to display a page (e.g., a home page) of the application marketplace 2.

In fig. 4B, the user interface 22 may include: control 402. Among other things, control 402 may be used to provide access to the scanning functionality of the handset.

Upon detecting a user-indicated operation (e.g., clicking on control 402) identifying the character code of identifier 1 shown in fig. 3C/3F, the handset may display the user interface 23 shown in fig. 4C as an example. Wherein the user interface 23 may be used to provide access to align and scan character codes and to display preview results of the aligned character codes.

Therefore, the mobile phone can read the character code of the identifier 1 by aligning and scanning the character code of the identifier 1 through the application market 2 in the mobile phone.

In some embodiments, the handset may change from displaying the user interface 23 shown in the example of fig. 4C to displaying the user interface 25 shown in the example of fig. 4E after scanning for the character code of the logo 1 shown in fig. 3C/3F. The user interface 25 may be used to display the results of the scanning of the character codes and to provide access to adjust the results of the scanning, among other things.

In fig. 4E, the user interface 25 may include: area 404, control 4051, and control 4052. The area 404 is in an unmodified state and can be used for displaying a scanning result, where the scanning result is a character code corresponding to an identified identifier, and the identified identifier is obtained by the mobile phone by scanning the character code of the identifier 1. Control 4051 may be used to provide a portal for modifying the scan results. Control 4052 may be used to provide a portal to confirm the scan results.

Upon detecting a user-indicated operation to modify the scan results (e.g., clicking on control 4051), the handset may change from displaying the user interface 25 illustrated in the example of fig. 4E to displaying the user interface 25 illustrated in the example of fig. 4F. Where the region 404 is in a modifiable state, it may be used to provide entry of the entered character code and display the modified scan result.

After the user modifies the scan result within a certain period of time, after detecting the operation indicated by the user to confirm the scan result after the modification (for example, clicking the control 4052 in the user interface 25 shown in fig. 4F), the mobile phone may modify the identified identifier based on the modified scan result, and may obtain the identifier 1.

After the user does not modify the scan result, the mobile phone may determine the identified identifier corresponding to the scan result as identifier 1 after detecting the operation indicated by the user to confirm the scan result (e.g. clicking on the control 4052 in the user interface 25 shown in fig. 4E/4F).

It should be noted that, fig. 4E and fig. 4F are optional, and provide a confirmation scan result and flexible modification scan result for the user to determine whether the identified identifier is identifier 1 and determine the channel of identifier 1, so that accuracy of identifying identifier 1 by the mobile phone is improved.

Alternatively, the handset may display the user interface 24 illustrated in the example of fig. 4D after detecting a user-indicated operation (e.g., clicking on the control 402) to identify the two-dimensional code of the identification 1 illustrated in fig. 3D/3G. The user interface 24 may be used to provide access to align and scan the two-dimensional code and display preview results of the aligned two-dimensional code.

When the application b is the system application 2 in the mobile phone, the mobile phone can execute the following contents:

upon detecting a user-indicated operation to launch the system application 2 (e.g., sliding to the right in the user interface 21 of fig. 4A), the handset may display a user interface 26 as exemplarily shown in fig. 4G. Wherein the user interface 26 may be a negative one-screen interface, the user interface 26 may include, but is not limited to: status bars, navigation bars, calendar indicators, weather indicators, and search boxes 403 with scanning functionality, etc.

After detecting the operation of identifying the character code of the identifier 1 shown in fig. 3C/3F indicated by the user (e.g., clicking the search box 403 with scanning function), the mobile phone may display the user interface 23 shown in fig. 4C. Wherein the user interface 23 may be used to provide access to align and scan character codes and preview the alignment results of the character codes.

Alternatively, after detecting the operation of identifying the two-dimensional code of the identifier 1 shown in fig. 3D/3G indicated by the user (for example, clicking the search box 403 with the scanning function), the mobile phone may display the user interface 24 shown in fig. 4D. The user interface 24 may be used to provide an entry for aligning and scanning the two-dimensional code and preview the alignment result of the two-dimensional code.

Therefore, the mobile phone aligns and scans the two-dimensional code of the identifier 1 through the system application 2 in the mobile phone, and the two-dimensional code of the identifier 1 can be read.

In summary, the mobile phone can call the dynamic code identification module in the mobile phone by means of the application market 2 or the system application 2 in the mobile phone, aim at and scan the character code or the two-dimensional code of the identifier 1, read the character code or the two-dimensional code of the identifier 1, and identify the character code or the two-dimensional code of the identifier 1, so as to obtain the identifier 1 (the process can be described with reference to S18 in fig. 2).

In addition, the mobile phone can determine whether the identified identifier is the identifier 1 generated by the tablet computer by means of the user, and the specific implementation manner of the mobile phone can be referred to the description of the embodiments of fig. 4E-4F, which is not repeated here.

In some embodiments, after acquiring the identifier 1, the mobile phone may transmit the identifier 1 and device information of the mobile phone to the background server (this process may refer to the description of S19 in fig. 2), so that the background server determines whether the identifier 1 is stored in the background server, to help the mobile phone determine that the tablet computer (i.e. the electronic device uniquely corresponding to the identifier 1) requests the synchronization application (this process may refer to the description of S20-S22 in fig. 2).

After determining that the tablet has requested a sync application, the handset may display the user interface 27 shown in the example of fig. 4H (see description of S23 in fig. 2 for this process). Wherein the user interface 27 may be used to display at least one content, such as an icon, an application name, etc., of each application installed in the handset in the application list, provide an entry for selecting each application, and provide an entry for determining the selected application.

In fig. 4H, the user interface 27 may include: region 4061, region 4062, and control 407. Wherein the region 4061 may be used to provide access to a selected travel application. The region 4062 is used to provide access to select sports health applications. Control 407 is used to provide access to the application for which selection is determined.

After detecting the operation (such as clicking the control 407) indicated by the user to determine the selected travel application and the sports health application, the mobile phone may determine the application information of the travel application in the mobile phone and the application information of the sports health application in the mobile phone (see the description of S24-S25 in fig. 2 for this process).

The mobile phone may transmit the identification 1, the application information of the travel application in the mobile phone, and the application information of the sports health application in the mobile phone to the background server (the process may be described with reference to S26 in fig. 2).

The background server may determine application information of the travel application in the tablet computer and application information of the sports health application in the tablet computer based on the identifier 1 and the mapping relationship (the process may be described with reference to S27 in fig. 2).

After receiving the query of the tablet computer, and determining that the application market 2 in the mobile phone synchronizes the application to the tablet computer, the background server may transmit the application name of the travel application in the tablet computer and the application name of the sports health application in the tablet computer to the tablet computer, or may transmit the application name and the application version of the travel application in the tablet computer and the application name and the application version of the sports health application in the tablet computer to the tablet computer (the process may be described with reference to S28 in fig. 2).

For convenience of explanation, the application version of the travel application in the tablet computer is an old version, and the application version of the sports health application in the tablet computer is a latest version.

The tablet computer may determine that the travel application and the sports health application need to be synchronized by default based on the application information of the travel application in the tablet computer and the application information of the sports health application in the tablet computer, and may also determine that the travel application and/or the sports health application need to be synchronized based on the user' S intention (the process may be described with reference to S291 in fig. 2).

Referring to fig. 3H, after determining that the mobile phone synchronizes the travel application and the sports health application with the tablet, the tablet may display a window 313 illustrated in fig. 3H on the user interface 12 illustrated in fig. 3C/3D.

Wherein window 313 may be used to display content such as icons, application names, etc. of each application (i.e., travel application and sports health application) that needs to be synchronized, and provide an entry for selecting whether at least one application is downloaded and installed from among all applications that need to be synchronized.

In addition, the window 313 may also be used to display an installation status of each application (i.e., the travel application and the sports health application) that needs to be synchronized, such as whether the travel application is installed in the tablet computer, an application version in which the travel application is installed in the tablet computer, and the like.

In fig. 3H, window 313 may further include: region 3141, region 3142, and control 315. The area 3141 may be used to display content such as icons, application names, etc. of the travel application, and provide an entry to select or not select the travel application, and display that the travel application is not installed in the tablet computer. The region 3142 may be used to display content of the sports health application, such as icons, application names, etc., as well as provide access to select or not select the sports health application, and to display that the sports health application is installed in a tablet computer. Control 3153 may be used to provide access to the application for which selection is determined, as well as to provide access to closing window 313 after a period of time (e.g., 5 s) has elapsed.

Therefore, based on user will, the tablet personal computer can provide the user with the function of selecting at least one application from all applications to be synchronized for downloading and installing, namely, the user can select the travel application for downloading and installing, can select the sports health application for downloading and installing, and can also select the travel application and the sports health application for downloading and installing.

After detecting the operation (such as clicking the control 315) indicated by the user to select the travel application and the sports health application, the tablet computer may download and install the travel application and the sports health application.

The tablet computer may request the background server for downloading the installation package of the travel application and the installation package of the sports health application in batch (the process may be described with reference to S292 in fig. 2).

The background server can obtain the CDN address from the CDN server and transmit the CDN address to the tablet computer. Wherein the CDN address is used to indicate the storage locations of the installation package of the travel application and the installation package of the sports health application (see description of S293 in fig. 2 for this procedure). The specific representation mode of the CDN address is not limited in the present application.

The tablet computer may download the installation package of the travel application and the installation package of the sports health application based on the CDN address, and may install the travel application and the sports health application in the tablet computer based on the installation package of the travel application and the installation package of the sports health application (this process may be described with reference to S294 in fig. 2).

The tablet computer may display the download and installation process of the travel application and the sports health application. For ease of illustration, application a is illustrated as application market 1 in a tablet computer.

Referring to fig. 3I-3J, the tablet computer may display the user interface 12 shown in the exemplary fig. 3I during download and installation. The user interface 12 may be used to display the synchronization progress of each application (i.e., the travel application and the sports health application) that needs to be synchronized, i.e., each application that needs to be synchronized is being downloaded or installed by the tablet.

In fig. 3I, the control 302 switches from the second state to the third state, which may be used to indicate that the tablet is synchronizing applications. Also, the user interface 12 may further include: a region 3121 and a region 3122. The region 3121 is in a synchronization state, and can be used to display the synchronization progress of the travel application. The region 3122 is in a synchronized state and may be used to display the progress of the synchronization of the sports health application.

After the tablet computer is installed, the display of the user interface 12 shown in the example of fig. 3I may be changed from displaying the user interface 12 shown in the example of fig. 3J. The user interface 12 may be used to display each application (i.e. the travel application and the sports health application) that the tablet computer has completed synchronization and needs to be synchronized, i.e. each application that the tablet computer has installed in the tablet computer and needs to be synchronized.

In fig. 3J, the control 302 switches from the third state to the fourth state, which may be used to indicate that the tablet has completed the sync application. Also, the user interface 12 may further include: a region 3121 and a region 3122.

The region 3121 may be used to indicate that the tablet computer has completed synchronizing the travel application when switching from the in-sync state to the completed sync state. In addition, the region 3121 can also be used to indicate the application version of the application that appears.

For example, when the application version of the tablet computer for installing the travel application is an old version, the update "upper corner mark shown in the area 3121 in fig. 3J is used to indicate that the application version of the travel application can be updated, so that the user selects whether to continue updating the application version of the travel application in the tablet computer based on his own will.

The region 3122, which switches from the in-sync state to the completed sync state, may be used to indicate that the tablet computer has completed the synchronized sports health application. In addition, the region 3122 may also be used to indicate an application version of the sports health application.

For example, when the application version of the tablet installed running the health application is the latest version, the area 3122 in fig. 3J does not show an "update" superscript for indicating that the application version of the sports health application is the latest version.

It should be noted that, in addition to the above implementation manner, the tablet pc may download and install, by default, an application of the mobile phone that needs to be synchronized by the mobile phone, and does not provide a function of selecting the application that needs to be synchronized for the user. In addition, the tablet computer can transmit an indication that the tablet computer synchronously completes travel application and sports health application to the background server. The background server can transmit an instruction for synchronously completing the travel application and the sports health application to the mobile phone, so that the mobile phone reminds the user of synchronously completing the travel application and the sports health application to the mobile phone.

In addition, when the mobile phone transmits the application information of the travel application in the mobile phone to the background server, wherein the application information comprises an application name, an application version and an application service condition, the background server can also transmit the application information of the travel application in the tablet computer to the tablet computer, wherein the application information comprises the application name, the application version and the application service condition.

Therefore, after the travel application is started, the tablet personal computer can find out a travel order in the travel application according to the travel record condition, and can display a page corresponding to the travel order to a user in the travel application.

Correspondingly, when the mobile phone transmits the application information of the motion health application in the mobile phone to the background server, wherein the application information comprises the application name, the application version and the application service condition, the background server can also transmit the application information of the motion health application in the tablet computer to the tablet computer, wherein the application information comprises the application name, the application version and the application service condition.

Therefore, after the tablet personal computer starts the sports health application, the sports data in the sports health application can be searched according to the sports data recording condition, and a page corresponding to the sports data can be displayed to a user in the sports health application.

In summary, the tablet pc can synchronize at least one application installed in the mobile phone through the background server and the CDN server based on the identifier 1, or can synchronize an application service condition of at least one application recorded in the mobile phone, or can synchronize at least one application installed in the mobile phone and an application service condition of at least one application recorded in the mobile phone.

Scene two

In scenario two, one electronic device may synchronize one or more applications installed in one electronic device to another electronic device through a server.

Referring to fig. 5, fig. 5 is a schematic structural diagram of a communication system according to an embodiment of the present application.

As shown in fig. 5, the communication system 20 of the present application may include: electronic device 21, electronic device 22, server 23, and server 24.

The electronic device 21 is communicatively connected to the electronic device 22 and the server 23, respectively, the electronic device 22 is also communicatively connected to the server 23, and the server 24 is also communicatively connected to the server 23 or the electronic device 21.

The electronic device 21 and the electronic device 22 may be different types of operating systems, or may be the same type of operating system, and the foregoing operating systems may be referred to the description of the operating system of the electronic device, which is not described herein.

The electronic device 21 and the electronic device 22 may be different device types or the same device type.

The electronic device 21 and the electronic device 22 may be the same vendor or different vendors.

Included in the electronic device 21 is a dynamic code generation (generate dynamic code) module. The dynamic code generation module may generate an identification 3, the identification 3 having a uniqueness, the identification 3 being used to uniquely determine that the electronic device 21 requests a synchronous application. The identifier 3 may be in a representation form such as a dynamic ID, and correspondingly, the identifier 3 may be displayed by using an optical character recognition (optical character recognition, OCR) picture or a two-dimensional code of the dynamic ID.

The specific generation manner of the identifier 3 may refer to the generation manner of the identifier 1 mentioned in fig. 2, and will not be described herein.

The electronic device 21 may transfer the identification 3 and the application information of each application to be synchronized to the electronic device 22 in the electronic device 21 to the server 23, which correspond to the steps "1, identification 3, application information of each application to be synchronized to the electronic device 22 in the electronic device 21" in fig. 5, respectively.

Wherein each of the above-mentioned applications requiring synchronization refers to at least one application selected from applications installed in the electronic device 21 based on the user's intention.

Wherein the application information of each application may include at least an application name and an application version. In addition, the application information of each application may further include an application service case (also referred to as a history case), where the application service case may refer to a description of the application service case in the first scenario, which is not described herein.

In some embodiments, the electronic device 21 may cache the identifier 3 and the application information of each application in the electronic device 21 that needs to be synchronized to the electronic device 22 in the server 23, so that the server 23 may learn, based on the identifier 3, that the electronic device 21 has requested to synchronize the applications, i.e. that the electronic device 21 has initiated a request to synchronize at least one application installed in the electronic device 22 to other electronic devices, and also that the server 23 has learned which applications the electronic device 21 has synchronized to other electronic devices.

The electronic device 21 may communicate the identification 3 to the electronic device 22, corresponding to step "2, identification 3" in fig. 5.

In some embodiments, the electronic device 21 may present an OCR picture or two-dimensional code of the dynamic ID to the electronic device 22. Included in the electronic device 22 is a dynamic code identification (extract dynamic code) module. The dynamic code recognition module can acquire the identifier 3 by scanning and recognizing the OCR picture or the two-dimensional code of the dynamic ID.

The electronic device 22 may directly determine the identified identifier as identifier 3, or may verify with the user whether the identified identifier is identifier 3. Thus, the process of the electronic device 21 delivering the identification 3 to the electronic device 22 is completed.

Note that, the order in which the electronic device 21 transmits the identifier 3 to the server 23 and the electronic device 22 is not limited, and the electronic device may be executed sequentially or simultaneously.

In some embodiments, after electronic device 21 determines that identification 3 is stored in server 23, electronic device 21 may communicate identification 3 to electronic device 22. After determining that the identifier 3 is not stored in the server 23, the electronic device 21 may continue to pass the identifier 3 to the server 23 until it is determined that the identifier 3 is stored in the server 23. This ensures that the electronic device 21, the electronic device 22, and the server 23 share the same identifier 3.

The electronic device 22 can establish a communication connection with the electronic device 21 and communicate via the server 23 based on the identification 3 such that the electronic device 22 determines that the electronic device 21 has requested a synchronous application. The electronic device 22 can transmit the identifier 3 and the device information of the electronic device 22 to the server 23 based on the identifier 3, and corresponds to step "3 and identifier 3" in fig. 5. Thus, the electronic device 22 can realize the matching between the electronic device 21 and the electronic device 22 through the server 23 by means of the identification 3 generated by the electronic device 21.

In some embodiments, the electronic device 22 may send a query request to the server 23 for querying/checking the server 23 for the presence of an application that needs to synchronize the electronic device 21, the query request carrying the identification 3 and the operating system of the electronic device 22. The specific implementation manner of the foregoing query request is not limited in this application.

The server 23 stores the mapping relationship between the electronic device of each operating system and the application information of each application, and the specific implementation manner thereof can be referred to the description of the mapping relationship stored in the server 13, which is not described herein.

Thus, the server 23 can determine, based on the identification 3, that the electronic device 22 requests to synchronize the applications installed in the electronic device 21, i.e. that there are applications that the electronic device 22 needs to synchronize.

The server 23 can obtain application information of each application to be synchronized in the electronic device 22 through the mapping relationship based on the operating system of the electronic device 22 and the application information of each application to be synchronized in the electronic device 22.

Any application version applied in the electronic device 22 may be the latest version or an old version, which is not limited in this application.

The server 23 may transmit to the electronic device 22 the identification 3 and the application name of each application in the electronic device 22 that needs to be synchronized, or the application name and the application version, corresponding to step "4 in fig. 5, the identification 3 and the application information of each application in the electronic device 22".

The server 24 is used to provide an installation package for all applications, and its specific implementation can be found in the aforementioned description of the server 14, which is not described herein.

Upon receiving the identification 3, the electronic device 22 may request to download an installation package for each application that needs to be synchronized based on the application information in the electronic device 22 for each application that needs to be synchronized. Wherein the application name and application version of any one application may determine the installation package of the application.

In some embodiments, the electronic device 22 may send a download request 21 to the server 23, where the download request 21 is used to request to download an installation package of each application that needs to be synchronized, and the download request 21 carries device information of the electronic device 22 and application information of each application that needs to be synchronized in the electronic device 22. The specific implementation of the foregoing download request 21 is not limited herein. For example, the download request 21 may carry, in addition to the device information of the electronic device 22, an application name, or an application name and an application version of each application in the electronic device 22 that needs to be synchronized.

The server 23 may determine application information of each application in the electronic device 22 that needs to be synchronized and may send a download request 22 to the server 24, corresponding to step "51, request" in fig. 5. The download request 22 is used for requesting to download an installation package of each application to be synchronized, and the download request 2 carries application information of each application to be synchronized in the electronic device 22. The specific implementation of the download request 22 is not limited herein.

The server 24 sends a download response 21 to the server 23, corresponding to step "52, CDN address" in fig. 5. The download response 21 carries a CDN address, where the CDN address is used to indicate a download address/storage address of an installation packet of each application that needs to be downloaded. The specific implementation of the download response 21 is not limited herein.

The server 23 sends a download response 22 to the electronic device 22 based on the device information of the electronic device 22, corresponding to step "6, CDN address" in fig. 5. The download response 22 carries a CDN address, where the CDN address is used to indicate a download address/storage address of an installation packet of each application that needs to be downloaded. The specific implementation of the download response 22 is not limited herein.

Thus, the electronic device 22 downloads the installation package of each application to be synchronized according to the CDN address, and based on the installation package of each application to be synchronized, corresponds to step "7, installation package of each application" in fig. 5, and installs each application to be synchronized in the electronic device 22.

In other embodiments, the electronic device 22 may send a download request 23 to the server 24, corresponding to step "81, request" in fig. 5. The download request 23 is used for requesting to download an installation package of each application to be synchronized, and the download request 23 carries device information of the electronic device 22 and application information of each application to be synchronized in the electronic device 22. The specific implementation of the foregoing download request 23 is not limited herein.

The server 24 sends a download response 23 to the electronic device 22 based on the device information of the electronic device 22, corresponding to step "82, CDN address" in fig. 5. The download response 3 carries a CDN address, where the CDN address is used to indicate a download address/storage address of an installation packet of each application that needs to be downloaded. The specific implementation of the download response 23 is not limited herein.

The installation package of each application that needs to be synchronized may use any version that the electronic device 22 can download and can install, such as the latest version.

In summary, the electronic device 21 may synchronize at least one application installed in the electronic device 21 to the electronic device 22.

In addition, when the application information further includes an application service condition, the electronic device 21 may synchronize the application service condition of at least one application recorded in the electronic device 21 to the electronic device 22, and may synchronize at least one application installed in the electronic device 21 and the recorded application service condition of at least one application to the electronic device 22, so that the user may use the application in the electronic device 21 in the electronic device 22 and execute the corresponding application service in the application according to the application service condition.

It should be noted that, the server 23 and the server 24 may be the same server, or may be different servers in a server cluster, which is not limited in this application.

Based on the above description, the electronic device 21 can synchronize at least one application installed in the electronic device 21 to the electronic device 22 through the server 23 and the server 24 by means of the identifier 3, or synchronize application service conditions of at least one application recorded in the electronic device 21 to the electronic device 22, or synchronize at least one application installed in the electronic device 21 and application service conditions of at least one application to the electronic device 22.

Next, in connection with fig. 6, taking an example that an application a is installed in the electronic device 21 and an application b, an application e, and an application f are installed in the electronic device 22, a specific implementation process in which the electronic device 21 synchronizes the application e and the application f installed in the electronic device 21 to the electronic device 22 will be described in detail.

The application a, the application b, the application e and the application f may be a system application or a third party application, which is not limited in this application. For example, application a may be an application market (AppGallery) in electronic device 21 and application b may be an application market (AppGallery) in electronic device 22.

Referring to fig. 6, fig. 6 is a signaling interaction diagram of an application synchronization method according to an embodiment of the present application.

As shown in fig. 6, the application synchronization method of the present application may include:

S31, the application a receives an operation 3, wherein the operation 3 is used for indicating the application e and the application f which need to be synchronized and starting a synchronous application function.

The type of operation 3 includes, but is not limited to, at least one type of click, long press, double click, etc. Operation 3 may be an operation triggered on control 3, control 3 being used to provide an application that determines the selected application as requiring synchronization and to provide a portal for launching the synchronized application functionality of electronic device 21. The shape, position, size, etc. of the control 3 are not limited in this application, for example, the control 3 may be displayed in a user interface of the application a.

For example, application a may display an icon for application e and a selection control for application e, an icon for application f and a selection control for application f, and control 3. The selection control of the application e is used for providing an entry for selecting the application e, and the selection control of the application f is used for providing an entry for selecting the application f.

After receiving the operation triggered on the selection control of the application e, the application a can determine that the user selects the application e. After receiving the operation triggered on the selection control of the application f, the application a can determine that the user selects the application f. After receiving the operation 3 triggered on the control 3, the application a can determine that the application e and the application f selected by the user are applications needing to be synchronized, and determine to start the synchronized application function of the electronic device 21.

S32, the application a responds to the operation 3, determines application information of the application e in the electronic device 21 and application information of the application f in the electronic device 21, and generates an identifier 3, wherein the identifier 3 is used for uniquely determining the electronic device 21 to initiate the synchronous application request 2.

After receiving operation 3, the application a may determine the application e and the application f as applications synchronized by the electronic device 21 to the electronic device 22, and may determine application information of each of the application e and the application f in the electronic device 21.

Wherein the application information includes an application name and an application version. In addition, the application information may also include application business conditions. The specific implementation manner of the application information of each application can be referred to the foregoing description, and will not be repeated here.

And, upon receiving operation 3, application a may determine that electronic device 21 initiated synchronization application request 2 and may invoke a dynamic code generation module in electronic device 21 to generate identification 3.

The synchronization application request 2 initiated by the electronic device 21 refers to a request initiated by the electronic device 21 to synchronize at least one application installed in the electronic device 21 to other electronic devices.

The specific implementation of the identifier 3 is not limited in this application. The generation manner of the identifier 3 may refer to the description of the electronic device 21 generating the identifier 3, which is not described herein.

S33, the application a sends a message 21 to the server 23, wherein the message 21 carries the identifier 3, application information of the application e in the electronic device 21 and application information of the application f in the electronic device 21.

S34, after receiving the message 21, the server 23 learns that the electronic device 21 initiates the synchronous application request 2, and stores the identifier 3, the application information of the application e in the electronic device 21, and the application information of the application f in the electronic device 21.

Based on S32-S34, the application a may write and store the identifier 3, the application information of the application e in the electronic device 21, and the application information of the application f in the electronic device 21 in the server 23, so that the server 23 knows that the electronic device 21 uniquely corresponding to the identifier 3 requests the synchronization application, and the server 23 knows that the application requested to be synchronized by the electronic device 21 includes the application e and the application f, which is beneficial for the server 23 to synchronize the application to the electronic device 22 by taking the identifier 3 as a bridge for the electronic device 21.

S35, the server 23 sends a message 22 to the application a, where the message 22 is used to indicate that the server 23 has stored the identifier 3.

S36, after receiving the message 22, the application a displays the character code or the two-dimensional code of the identifier 3.

Based on S35-S36, the server 23, after storing the identity 3, may send a message 22 to the application a, so that the application a knows that the identity 3 is stored in the server 23. After determining that the identifier 3 is stored in the server 23, the application a may display a character code or a two-dimensional code of the identifier 3. Thus, the electronic device 21 can transmit the identifier 3 to the server 23, which is beneficial to ensuring that the electronic device 21, the server 23 and the electronic device 22 can share the same identifier 3.

After a certain period of time, the application a does not receive the message 22, and may continue to execute S34, send the message 21 to the server 23, and may not execute S37 until the application a receives the message 22 from the server 23. In the resent message 21, the application a may not update the identifier 3, or may update the identifier 3, which is not limited in this application.

In some embodiments, the user may trigger an operation on a control in application a for updating identity 3, enabling application a to update identity 3.

The control used for updating the identifier 3 may be the control 4, or may be other controls in the application a except the control 4. The present application does not limit the shape, position, size, etc. of the control for updating the identifier 3. The types of operations on the controls for updating the identity 3 include, but are not limited to, at least one type of click, long press, double click, etc.

S37, the application b obtains the identifier 3 by scanning and identifying the character code or the two-dimensional code of the identifier 3.

The application b can call a dynamic code identification module in the electronic equipment 22 to scan and identify the character code or the two-dimensional code of the identifier 3, and can acquire the identifier 3.

The application b does not limit the manner of scanning and identifying the character code or the two-dimensional code of the identifier 3.

In some embodiments, when the screen of the electronic device 21 displays the character code or the two-dimensional code of the logo 3, the application b may scan against the screen of the electronic device 21 after receiving an operation on one control of the application b. Wherein the control has the functions of scanning and identifying. The specific implementation of the control is not limited in this application.

In other embodiments, the electronic device 21 may transmit the picture or the link of the character code or the two-dimensional code of the identifier 3 to the electronic device 22 through other electronic devices or servers, for example, share the picture or the link through an app on the electronic device 21, or share the picture or the web page corresponding to the character code or the two-dimensional code of the identifier 3 through a near field communication manner, so that the electronic device 22 may obtain the picture or the web page corresponding to the character code or the two-dimensional code of the identifier 3. Therefore, the application b can scan the picture or the webpage corresponding to the character code or the two-dimensional code of the identifier 3 when the scanning function is started.

If the application b recognizes correctly, the recognized identity is identity 3. If application b identifies an error, then the identified identity is not identity 3. Thus, after application b recognizes an identity, such as identity 4, application b may determine the recognized identity as identity 3 using a variety of implementations.

In some embodiments, application b may perform the following process:

and step 1, displaying the recognized character code or the two-dimensional code of the mark 4 by the application b. Therefore, the application b can display the character code or the two-dimensional code of the identifier 4 to the user, and the user can conveniently judge whether the character code of the identifier 3 is the same as the character code of the identifier 4 or whether the two-dimensional code of the identifier 3 is the same as the two-dimensional code of the identifier 4.

And 2, judging whether the modification content for modifying the identified identifier 4 is received in the duration 2 by the application b.

And 3, when receiving the modified content, the application b determines the identifier 3 based on the modified content. Thus, the application b may modify the identified identity 4 to the identity 3 based on the user's wishes.

And 4, when the modified content is not received, the application b determines that the identified identifier 4 is the identifier 3. Thus, the application b determines the identified identity 4 as the identity 3 based on the user's intention.

Thus, the application b can obtain the identification 3 generated by the electronic device 21 based on the user's wish.

In other embodiments, the application b has higher recognition accuracy, and the recognized mark 4 can be directly determined to be the mark 3.

In summary, application b may obtain identity 3.

S38, the application b sends a message 23 to the server 23, wherein the message 23 is used for inquiring whether the server 23 stores the identifier 3, and the message 23 carries the identifier 3 and the device information of the electronic device 22.

Wherein the device information of the electronic device 22 is used to uniquely identify the electronic device 22. Thus, the server 23 can determine, based on the device information of the electronic device 22, that the message 23 was sent by the electronic device 22, and can also establish a communication connection with and communicate with the application b.

S39, the server 23 determines whether the identifier 3 is stored in the server 23 after receiving the message 23.

S40, after determining that the server 23 has stored the identifier 3, the server 23 determines, based on the identifier 3, that the electronic device 22 requests to synchronize the application installed in the electronic device 21, and determines, based on the mapping relationship, application information of the application e in the electronic device 22 and application information of the application f in the electronic device 22.

After receiving the message 23, the server 23 may parse the message 23. After obtaining the identification 3 from the message 23, the server 23 can learn that the electronic device 22 requests a synchronization application from the electronic device 21.

Thus, the server 23 can determine the application information of the application e in the electronic device 22 and the application information of the application f in the electronic device 22 by the mapping relationship based on the device information of the electronic device 21, the application information of the application e in the electronic device 21, and the application information of the application f in the electronic device 21.

Wherein, the server 23 can determine that the application version of the application e in the electronic device 22 is an old version according to the mapping relation based on the application version of the application e in the electronic device 21. At this time, the server 23 may recommend that the application e be the old version in the electronic device 22 to the electronic device 22, or may recommend that the application version of the application e be the latest version in the electronic device 22 to the electronic device 22.

The server 23 may determine that the application version of the application e in the electronic device 22 is the latest version through the mapping relationship based on the application version of the application e in the electronic device 21. At this time, the server 23 may recommend to the electronic device 22 that the application version of the application e in the electronic device 22 be the latest version.

Similarly, the server 23 may determine, based on the application version of the application f in the electronic device 21, that the application version of the application f in the electronic device 22 is an old version through the mapping relationship. At this time, the server 23 may recommend that the application version of the application f in the electronic device 22 be the old version to the electronic device 22, or may recommend that the application version of the application f in the electronic device 22 be the latest version to the electronic device 22.

The server 23 may determine that the application version of the application f in the electronic device 22 is the latest version based on the application version of the application f in the electronic device 21 through the mapping relationship. At this time, the server 23 may recommend to the electronic device 22 that the application version of the application f in the electronic device 22 be the latest version.

S41, the server 23 sends a message 24 to the application b, wherein the message 24 is used for indicating that the identifier 3 is stored in the server 23, and the message 24 carries application information of the application e in the electronic device 22 and application information of the application f in the electronic device 22.

Based on S38-S39, the application b may send a message 23 to the server 23 so that the server 23 may determine whether the identity 3 is stored in the server 23.

Upon determining that the identity 3 is stored in the server 23, the server 23 may sequentially execute S40-S41, so that the application b may determine that the electronic device 21 has requested a synchronized application.

Upon determining that the identifier 3 is not stored in the server 23, the server 23 may send a message to the application b indicating that the identifier 3 is not stored in the server 23, or may not send a message to the application b, so that the application b may determine that there is no electronic device corresponding to the identifier 3 requesting the synchronization application.

Thus, application b may re-execute S37, again by scanning and identifying the character code or two-dimensional code of identifier 3, obtain identifier 3, and continue executing S38-S41 until server 23 sends message 24 to application b. Thus, the application b can avoid the problem of erroneous identification by scanning and identifying again.

In addition, the application b may display third prompt content for reminding the user that the application b has failed to recognize. The third prompting content can display corresponding characters, symbols, voice, icons and the like in a popup window or icon mode. Thus, the user can scan the character code or the two-dimensional code of the logo 3 using the electronic device 22 conveniently, so that the application b can re-execute S37.

In summary, the application b can verify whether the electronic device 21 requests the synchronous application by storing the identifier 3 in the server 23, so as to realize the matching between the electronic device 21 and the electronic device 22, and ensure that the electronic device 21, the server 23 and the electronic device 22 share the same identifier 3.

It should be noted that, if the application a determines that the application information of the application e and/or the application f in the electronic device 21 includes the application name, the application version, and the application service condition, the message 21 sent by the application a in S33 to the server 23 carries the application name, the application version, and the application service condition of the application e and/or the application f in the electronic device 21. And, the message 24 sent by the server 23 in S41 to the application b carries the application name, the application version and the application service condition of the application e and/or the application f in the electronic device 22.

S42, after receiving the message 24, the application b determines that there is an electronic device (i.e. the electronic device 21) uniquely corresponding to the identifier 3 that initiates the synchronization application request 2, and determines that the application e and the application f need to be synchronized.

Application b, upon receiving message 24, may determine that electronic device 21 is to synchronize application e and application f installed in electronic device 21 with electronic device 22.

In some embodiments, application b may default to synchronizing application e and application f and may execute S43.

In other embodiments, application b may also display a user interface that may be used to present to the user at least one content, such as an icon, application name, etc., of each application that needs to be synchronized, provide access to select at least one application, and provide access to determine the selected application. Application b may determine synchronization application e and/or application f based on user intent.

For ease of illustration, application e and application f are illustrated as applications of the electronic device 22 that require synchronization. Thus, the application b may determine that the application e and the application f need to be synchronized, and may execute S43.

In addition, the application b may also determine whether the application e and the application f are installed in the electronic device 22, and whether the application version of the application e and/or the application f installed in the electronic device 22 needs to be updated. Thus, the user interface may also be used to present to the user the installation status of each application that needs to be synchronized, such as whether an application is installed in the electronic device 22, the version of the application that is installed in the electronic device 22, and so on.

In addition, when the application information of the application e and/or the application f further includes an application service condition, the application b may determine to synchronize the application e, the application f, and the application service condition of the application e and/or the application f.

S43, the application b sends a message 25 to the server 23 based on the application information of the application e in the electronic device 22 and the application information of the application f in the electronic device 22, where the message 25 is used for requesting to download the installation package of the application e and the installation package of the application f.

The specific implementation of the message 25 is not limited herein. For example, the message 25 may carry an application name of the application e in the electronic device 2 and an application name of the application f in the electronic device 22, or an application name and an application version of the application e in the electronic device 22 and an application name and an application version of the application f in the electronic device 2.

S44, the server 23 obtains the CDN address from the server 24 and sends a message 26 to the application b, wherein the message 26 carries the CDN address, and the CDN address is used for indicating the storage positions of the installation package of the application e and the installation package of the application f.

S45, the application b downloads an installation package of the application e and an installation package of the application f based on the CDN address, installs the application e based on the installation package of the application e, and installs the application f based on the installation package of the application f.

In addition, after the application b successfully installs the application e and the application f, a fourth prompt content can be displayed, and the fourth prompt content is used for reminding the user that the application e and the application f have been successfully installed. The fourth prompting content can display corresponding characters, symbols, voice, icons and the like in a popup window or icon mode.

In addition, after the application b successfully installs the application e and the application f, an indication message 21 may be sent to the server 23, where the indication message 21 is used to instruct the electronic device 22 to complete the application e and the application f synchronously. The server 23 may send an indication message 22 to the electronic device 21, the indication message 22 being for indicating that the electronic device 22 has completed the application e and the application f synchronously.

Thus, the electronic device 21 may display sixth prompt for prompting the user of the electronic device 22 to complete the application e and the application f synchronously. The sixth prompting content can display corresponding characters, symbols, voice, icons and the like in a popup window or icon mode.

In addition, when the application information of the application e and/or the application f further includes an application service condition, the application b may store the application service condition of the application e and/or the application f in the electronic device 22, so that after the mobile phone starts the application e or the application f, the mobile phone may execute the corresponding application service in the application e or the application f according to the application service condition.

For example, when the application e is an email application, after the email application is started, the mobile phone can find the email in the email application according to the email recording condition. When the application f is a video playing application, after the mobile phone starts the video playing application, the corresponding video in the video playing application can be played according to the video playing progress.

Based on the description of the embodiment of fig. 6, the electronic device 21 may synchronize a plurality of applications installed in the electronic device 21 to the electronic device 12. In addition, according to a similar description of the embodiment of fig. 6, the electronic device 21 may synchronize an application installed in the electronic device 21 with the electronic device 12, which is not described herein.

Thus, the electronic device 21 may synchronize at least one application installed in the electronic device 21 to the electronic device 22, may synchronize application service conditions of the at least one application recorded in the electronic device 21 to the electronic device 22, and may also synchronize the at least one application installed in the electronic device 21 and the recorded application service conditions of the at least one application to the electronic device 22.

In the second scenario, the electronic device 21, the electronic device 22 and the server 23 can implement communication connection and intercommunication between the electronic device 21, the electronic device 22 and the server 23 by means of the identifier generated by the electronic device 21. Based on the identification, the electronic device 21 may notify the server 23 that the electronic device 21 has requested the synchronization application, and transmit application information of each application in the electronic device 21 that needs to be synchronized to the server 23. Based on the identification, the electronic device 22 may inform the server 23 that the electronic device 22 needs to synchronize applications installed in the electronic device 21. The server 23 may determine application information of each application requiring synchronization in the electronic device 22 based on the mapping relationship, and transmit the application information of each application requiring synchronization in the electronic device 22 to the electronic device 22. The electronic device 22 can acquire an installation package of each application requiring synchronization through the server 23 and the server 24, and install each application requiring synchronization in the electronic device 22.

Therefore, the electronic device 21 can synchronize at least one application installed in the electronic device 21 to the electronic device 22 through the server 23 and the server 24 based on the identifier generated by the electronic device 21, without considering the differences among device types among the electronic devices, operating systems among the electronic devices, application names and application versions of applications in the electronic devices, and the key is that through the transmission of application information, the synchronization of various application names and application versions among the electronic devices of various operating systems and device types is realized, or the synchronization of various application names, application versions and application service conditions among the electronic devices of various operating systems and device types is realized, account sharing is not needed, no additional hardware modules are needed to be added, the realization process is convenient and quick, the cost of synchronizing the application among the electronic devices is reduced, and the user experience of synchronizing the application among the electronic devices is improved.

Based on the descriptions shown in fig. 5 to 6, a specific implementation procedure in which the electronic device 21 synchronizes the application e and the application f installed in the electronic device 21 to the electronic device 22 is described in conjunction with fig. 7A to 7I and fig. 8A to 8C.

For convenience of explanation, in fig. 7A-7I and fig. 8A-8C, the electronic device 21 is taken as a tablet computer, the application a is taken as an application market 1 or a system application 2 in the tablet computer, the electronic device 22 is taken as a mobile phone, the application b is taken as an application market 2 or a system application 2 in the mobile phone, the application e is taken as an email application in the tablet computer, the application f is taken as a video playing application in the tablet computer, the server 23 is taken as a background server, and the server 24 is taken as a CDN server for illustration.

Referring to fig. 7A-7I, fig. 7A-7I are schematic diagrams of a man-machine interface according to an embodiment of the present application.

based on the description of the embodiment of fig. 3A-3B, the tablet computer may display a user interface 12 as exemplarily shown in fig. 3B.

In fig. 3B, the user interface 12 may include: control 302, control 303, region 304, and region 305. Wherein control 302 is in a first state, and can be used to provide an entry for starting a synchronous application function of the tablet computer, and control 303 can be used to display an installed application in the tablet computer. The area 304 may be used to alert the user that the tablet may provide a synchronized application function. The area 305 may be used to provide an entry for the tablet login account and display the status of whether the tablet login account is logged in. For example, region 305 is used to indicate the status of the tablet computer not logged into the account.

Upon detecting a user-indicated operation to view an application installed in the tablet (e.g., clicking on control 303), the tablet may change from displaying the user interface 12 illustrated in the example of fig. 3B to displaying the user interface 12 illustrated in the example of fig. 7A.

In fig. 7A, the user interface 12 may further include: region 701, control 702, and control 703. The area 701 is in an unselected state, and may be used to display at least one content of an application installed in the tablet computer, such as an icon, an application name, and the like. For example, an icon of an email application and an icon of a video playback application are displayed in the area 701. Control 702 may be used to provide an interface into a synchronizable application in a selection tablet. The control 703 is in a non-triggering state, and is used for providing an entry for starting the synchronous application function of the tablet computer after selecting an application needing to be synchronized.

Upon detecting a user-indicated operation to initiate a synchronized application function of the tablet (e.g., clicking on control 702), the tablet may change from displaying the user interface 12 illustrated in the example of fig. 7A to displaying the user interface 12 illustrated in the example of fig. 7B.

In the user interface 12 of fig. 7B, the region 701 may be switched from a non-selectable state to a selectable state, which may be used to provide access to select applications installed in the tablet. For example, a selection box of an email application and a selection box of a video playback application are displayed in the region 701.

Upon detecting the user-indicated operation of selecting the email application and the video playback application (e.g., clicking on the selection box of the email application and the selection box of the video playback application displayed in the area 701), the tablet computer may change from displaying the user interface 12 illustrated in the example of fig. 7B to displaying the user interface 12 illustrated in the example of fig. 7C (this process may be described with reference to S31 in fig. 6).

In the user interface 12 of fig. 7B, an opposite hook is displayed in the selection box of the email application and the selection box of the video playback application in the area 701, for indicating that the user has selected the email application and the video playback application. The control 703 switches from the non-triggerable state to the triggerable state for providing access to initiate the synchronized application functions of the tablet.

Thus, the tablet computer may determine that the applications requiring synchronization include an email application and a video playback application, and determine application information of the email application in the tablet computer and application information of the video playback application in the tablet computer (see description of S32 in fig. 6 for this procedure).

After detecting the operation of the synchronous email application and the video playing application indicated by the user (e.g. clicking on the control 703), the tablet computer may generate the identifier 3 (this process may refer to the description of S32 in fig. 6), and write and store the identifier 3, the application information of the email application in the tablet computer, and the application information of the video playing application in the tablet computer in the background server (this process may refer to the description of S33 in fig. 6).

After determining that the identifier 3 is stored in the background server, the tablet computer may display a window 704 (see description of S34-S36 in fig. 6) exemplarily shown in fig. 7D on the user interface 12 shown in fig. 7C.

In fig. 7D, window 704 may be used to display the character code for logo 3. Additionally, window 704 may also be used to provide access to editing window 704, such as closing, zooming in, zooming out, etc.

In some embodiments, the window 704 may include a region 7051 therein. Wherein the region 7051 may be used to display the character code of the logo 3. In addition, a control 7052 can also be included in window 704. Among other things, control 7052 may be used to provide entry for updating the character code for identification 3.

Alternatively, after determining that the identifier 3 is stored in the background server, the tablet computer may display the window 706 illustrated in the example of fig. 7E on the user interface 12 illustrated in fig. 7C.

In fig. 7E, window 706 may be used to display the two-dimensional code for logo 3. Additionally, window 706 may also be used to provide access to editing window 706, such as closing, zooming in, zooming out, etc.

In some embodiments, the window 706 may include a region 7071 therein. Wherein, the region 7071 may be used to display the two-dimensional code of the logo 3. In addition, a control 7072 may also be included in the window 706. Wherein, control 7072 can be used to provide entry to update the two-dimensional code of logo 3.

It should be noted that, the tablet personal computer may selectively display the character code of the identifier 3, may selectively display the two-dimensional code of the identifier 3, and may selectively display the character code and the two-dimensional code of the identifier 3, which is not limited in this application.

In addition, control 7052 or control 7072 is optional. In fig. 7D or fig. 7E, the tablet computer may automatically update the character code or the two-dimensional code of the identifier 3 after a period of time passes, or may update the character code or the two-dimensional code of the identifier 3 after detecting the operation triggered on the control 7052 or the control 7072, which is not limited in this application.

Therefore, after the character code or the two-dimensional code of the identifier 3 is displayed, the tablet personal computer can provide a channel for acquiring the identifier 3 for the mobile phone.

When the application a is the system application 1 in the tablet computer, the tablet computer may execute the following:

based on the description of the embodiment of fig. 3A, the tablet computer may display the user interface 11 exemplarily shown in fig. 3A.

In fig. 3A, the user interface 11 may include: an icon 3011 of the application marketplace 1, an icon 3012 of the system settings 1, an icon of a tablet manager, an icon of a browser, an icon of an email application, an icon of a memo, an icon of a gallery, an icon of a video play application, and the like.

Upon detecting a user-indicated operation (e.g., pressing a blank area in the user interface 11 for a long time) to initiate a synchronized application function of the tablet, the tablet may change from displaying the user interface 11 illustrated in the example of fig. 3A to displaying the user interface 11 illustrated in the example of fig. 7F. The user interface 11 may be used to display at least one content, such as an icon, an application name, etc., of the synchronizable application in the tablet. For example, icons of an email application and icons of a video playback application are displayed in the user interface 11.

In fig. 7F, the user interface 11 may include: region 7081, region 7082, and control 709. Wherein the region 7081 may be used to provide an entry for selecting an email application, such as a selection box in which the email application is displayed in the region 7081. The region 7082 may be used to provide an entry for selecting a video playback application, such as a selection box in which the video playback application is displayed in the region 7082. The control 709 is in a non-triggered state and is used for providing an entry for starting the synchronous application function of the tablet computer after selecting the application needing to be synchronized.

Upon detecting the user-indicated operation of selecting the email application and the video playback application (e.g., clicking on the selection box of the email application displayed in the area 7081 and the selection box of the video playback application displayed in the area 7082), the tablet computer may change from displaying the user interface 11 illustrated in the example of fig. 7F to displaying the user interface 11 illustrated in the example of fig. 7G (this process may be described with reference to S31 in fig. 6).

In the user interface 11 of fig. 7G, a pair of hooks is displayed in the selection frame of the email application in the region 7081 and the selection frame of the video playback application in the region 7082, for indicating that the user has selected the email application and the video playback application. Control 709 switches from the non-triggerable state to the triggerable state for providing access to initiate the synchronized application functions of the tablet.

After detecting the operation of synchronizing the email application and the video playing application indicated by the user (e.g., clicking the control 709), the tablet computer may determine that the applications to be synchronized include the email application and the video playing application, determine the application information of the email application in the tablet computer and the application information of the video playing application in the tablet computer (the process may refer to the description of S32 in fig. 6), generate the identifier 3 (the process may refer to the description of S32 in fig. 6), and write and store the identifier 3, the application information of the email application in the tablet computer, and the application information of the video playing application in the tablet computer in the background server (the process may refer to the description of S33 in fig. 6).

After determining that the identifier 3 is stored in the background server, the tablet computer may display a window 710 (see description of S34-S36 in fig. 6) exemplarily shown in fig. 7H on the user interface 11 shown in fig. 7G.

In fig. 7H, window 710 may be used to display the character code for logo 3. Additionally, window 710 may also be used to provide access to editing window 710, such as closing, zooming in, zooming out, etc.

In some embodiments, region 7111 may be included in window 710. Wherein the region 7111 may be used to display a character code of the logo 3. In addition, a control 7112 may also be included in window 710. Among other things, control 7112 may be used to provide entry for updating the character code of logo 3.

Alternatively, after determining that the identifier 3 is stored in the background server, the tablet computer may display a window 712 shown in fig. 7I as an example on the user interface 11 shown in fig. 7G.

In fig. 7I, window 712 may be used to display a two-dimensional code for logo 3. In addition, window 712 may also be used to provide access to editing window 712, such as closing, zooming in, zooming out, etc.

In some embodiments, region 7131 may be included in window 712. Wherein, the region 7131 may be used to display the two-dimensional code of the logo 3. In addition, controls 7132 may also be included in window 712. Among other things, control 7132 may be used to provide entry for updating the two-dimensional code of logo 3.

In addition, control 7112 or control 7132 is optional. In fig. 7H or fig. 7I, the tablet computer may automatically update the character code or the two-dimensional code of the identifier 3 after a period of time passes, or may update the character code or the two-dimensional code of the identifier 3 after detecting the operation triggered on the control 7112 or the control 7122, which is not limited in this application.

In summary, the tablet computer can call the dynamic code generation module in the tablet computer to generate the identifier 3 by means of the application market 1 in the tablet computer. The tablet personal computer can transmit the identifier 3, the application information of the email application in the tablet personal computer and the application information of the video playing application in the tablet personal computer to the background server, and the identifier 3 can be transmitted to the mobile phone by displaying the character code or the two-dimensional code of the identifier 3.

Based on the above description, the mobile phone can synchronize applications installed in the tablet computer selected by the user through the background server based on the identifier 3, and the specific process can include the following steps:

based on the description of the embodiment of fig. 4A to fig. 4H, the mobile phone can call the dynamic code identification module in the mobile phone by means of the application market 2 or the system application 2 in the mobile phone, aim at and scan the character code or the two-dimensional code of the identifier 3, read the character code or the two-dimensional code of the identifier 3, and identify the character code or the two-dimensional code of the identifier 3, so as to obtain the identifier 3 (the process can be described with reference to S37 in fig. 6).

In some embodiments, after acquiring the identifier 3, the mobile phone may transmit the identifier 3 and device information of the mobile phone to the background server, so that the background server determines whether the identifier 3 is stored in the background server (see the description of S38 in fig. 6 for this procedure).

After determining that the background server stores the identifier 3, the background server can determine application information of the email application in the mobile phone and application information of the video playing application in the mobile phone based on the identifier 3 and the mapping relationship (the process can be described in S39-S40 in fig. 6).

The background server may transmit the application information of the email application in the mobile phone and the application name of the video playing application in the mobile phone to the mobile phone, or may transmit the application name and the application version of the email application in the mobile phone and the application name and the application version of the video playing application in the mobile phone to the mobile phone (the process may be described with reference to S41 in fig. 6).

For convenience of explanation, the application version of the email application in the tablet computer is taken as the latest version, and the application version of the video playing application in the tablet computer is taken as an old version as an example for illustration.

Thus, the handset may determine that there is a tablet (i.e., an electronic device that uniquely corresponds to the identity 3) requesting a synchronized application. Also, the mobile phone may determine by default that the email application and the video playback application need to be synchronized, or may determine that the email application and/or the video playback application need to be synchronized based on the user' S intention (this process may be described with reference to S42 in fig. 6).

For ease of illustration, and for purposes of illustration, a synchronous email application and video playback application are illustrated.

The mobile phone may request the background server to download the installation package of the email application and the installation package of the video playback application in batch based on the application information of the email application in the mobile phone and the application information of the video playback application in the mobile phone (this process may be described with reference to S43 in fig. 6).

The background server may obtain the CDN address from the CDN server and transmit the CDN address to the handset (see description of S44 in fig. 6 for this procedure). The CDN address is used for indicating the storage positions of the installation package of the email application and the installation package of the video playing application. The specific representation mode of the CDN address is not limited in the present application.

The handset can download an installation package of the email application and an installation package of the video playing application based on the CDN address, and can install the email application and the video playing application in the handset based on the installation package of the email application and the installation package of the video playing application (this process may be described with reference to S45 in fig. 6).

The mobile phone computer can display the downloading and installing processes of the email application and the video playing application. For ease of illustration, application a is illustrated as application market 1 in a cell phone.

Referring to fig. 8A-8C, fig. 8A-8C are schematic diagrams of a man-machine interface according to an embodiment of the present application.

The handset may display the user interface 31 shown in the example of fig. 8A before downloading and installing the application that needs to be synchronized.

Wherein the user interface 31 may be used to display content such as icons, application names, etc. of each application (i.e., email application and video playback application) that needs to be synchronized, and to provide an entry for selecting whether at least one application is downloaded and installed from among all applications that need to be synchronized.

In addition, the user interface 31 may also be used to display the installation status of each application (i.e., email application and video playback application) that needs to be synchronized, such as whether the video playback application is installed in a cell phone, the version of the application in which the video playback application is installed in a cell phone, and so on.

In fig. 8A, the user interface 31 may include: region 801, region 802, and control 803. The area 801 may be used to display content, such as icons, application names, etc., of email applications, and to provide access to select or not select email applications, as well as to display email applications installed in a tablet computer. Region 802 may be used to display content of a video playback application, such as an icon, application name, etc., as well as provide access to select or not select a video playback application, and to display that a video playback application is not installed in a tablet computer. Control 803 may be used to provide access to the application for which selection is determined, and to provide access to close user interface 31 over a period of time (e.g., 5 s).

Therefore, based on the user will, the mobile phone can provide the user with the function of selecting at least one application from all applications to be synchronized for downloading and installing, namely the user can select an email application for downloading and installing, can select a video playing application for downloading and installing, and can also select the email application and the video playing application for downloading and installing.

The mobile phone may download and install the email application and the video playback application upon detecting a user-indicated operation (e.g., clicking on control 803) to select the email application and the video playback application.

In addition, the handset may display the user interface 32 shown in the example of fig. 8B during download and installation. The user interface 32 may be used to display the synchronization progress of each application (i.e., email application and video playback application) that needs to be synchronized, i.e., each application that needs to be synchronized is being downloaded or installed by the handset.

In fig. 8B, the user interface 32 may further include: region 804 and region 805. Where region 804 is in a synchronized state, it may be used to display the synchronization progress of the email application. The area 805 is in a synchronized state and may be used to display the progress of the video playback application.

After the handset is installed, it may be changed from displaying the user interface 32 illustrated in the example of fig. 8B to displaying the user interface 32 illustrated in the example of fig. 8C. The user interface 32 may be used to indicate that the mobile phone has completed each application (i.e., the email application and the video playing application) that needs to be synchronized, i.e., the mobile phone installs each application in the mobile phone that needs to be synchronized.

In the user interface 32 of fig. 8C, the area 801, which switches from the in-sync state to the completed sync state, may be used to indicate that the handset has completed synchronizing the email application. For example, the handset may install the latest version of the completed email application.

In the user interface 32 of fig. 8C, the area 802, which switches from the in-sync state to the completed sync state, may be used to indicate that the handset has completed the synchronized video playback application. For example, the cell phone may install an old version of the completed video playback application such that the user selects whether to continue updating the application version of the video playback application in the cell phone based on his own will.

It should be noted that, in addition to the above implementation manner, the mobile phone may download and install the application of the tablet computer that needs to be synchronized by default, and the function of selecting the application that needs to be synchronized is not provided for the user.

In addition, the mobile phone can transmit an indication that the mobile phone completes the email application and the video playing application synchronously to the background server. The background server can transmit an instruction of synchronously completing the email application and the video playing application to the tablet computer, so that the tablet computer reminds a user of synchronously completing the email application and the video playing application.

In addition, when the tablet computer transmits the application information of the email application in the tablet computer to the background server, wherein the application information comprises the application name, the application version and the application service condition, the background server can also transmit the application information of the email application in the mobile phone to the mobile phone, wherein the application information comprises the application name, the application version and the application service condition.

Therefore, after the mobile phone starts the email application, the email in the email application can be searched according to the email recording condition, and the page corresponding to the email can be displayed to the user in the email application.

Correspondingly, when the tablet personal computer transmits application information of the video playing application in the tablet personal computer to the background server, wherein the application information comprises an application name, an application version and an application service condition, the background server can also transmit the application information of the video playing application in the mobile phone to the mobile phone, wherein the application information comprises the application name, the application version and the application service condition.

Therefore, after the mobile phone starts the video playing application, the video in the video playing application can be played according to the video playing progress.

In summary, the tablet computer can synchronize at least one application installed in the tablet computer to the mobile phone through the background server and the CDN server based on the identifier 3, or can synchronize application service conditions of at least one application recorded in the tablet computer to the mobile phone, or can synchronize application service conditions of at least one application installed in the tablet computer and at least one recorded application to the mobile phone.

Based on the descriptions shown in fig. 5 to 6, a specific implementation procedure in which the electronic device 21 synchronizes the application service situation of the application g recorded in the electronic device 21 or the application g and the application service situation of the application g installed in the electronic device 21 to the electronic device 22 is described in conjunction with fig. 9A to 9C and fig. 10A to 10B.

For convenience of explanation, in fig. 9A-9C and fig. 10A-10B, the electronic device 21 is a tablet computer, the application a is a video playing application in the tablet computer, the electronic device 22 is a mobile phone, the application B is an application market 2 or a system application 2 in the mobile phone, the server 23 is a background server, and the server 24 is a CDN server for illustration.

Referring to fig. 9A-9C, fig. 9A-9C are schematic diagrams of a man-machine interface according to an embodiment of the present application.

Based on the description of the embodiment of fig. 3A, the tablet computer may display a user interface 11 as exemplarily shown in fig. 3A.

Upon detecting a user-indicated operation to launch a video playback application (e.g., an icon of the video playback application in the electrode user interface 11), the tablet computer may launch the video playback application and may display the user interface 41 illustrated in the example of fig. 9A. The user interface 41 may be used to present videos in the video playing application, and provide an entry indicating the video playing application and the application service condition of the video playing application that need to be synchronized, and to start the synchronous application function of the tablet computer.

In fig. 9A, video a in the video playback application is played back in the user interface 41. Also included in the user interface 41 is: control 901. The control 901 may be used to provide a video playing progress indicating a video playing application requiring synchronization and a video a in the video playing application, and an entry for starting a synchronization application function of the tablet computer.

After detecting the operation of synchronizing the video playing application and the video playing progress of the video a indicated by the user (for example, clicking the control 901), the tablet computer may determine that the application to be synchronized includes the video playing application, determine application information of the video playing application in the tablet computer (this process may be described with reference to S32 in fig. 6), generate the identifier 3 (this process may be described with reference to S32 in fig. 6), and write and store the application information of the identifier 3 and the video playing application in the tablet computer in the background server (this process may be described with reference to S33 in fig. 6).

After determining that the identifier 3 is stored in the background server, the tablet computer may display a window 902 (see description of S34-S36 in fig. 6) exemplarily shown in fig. 9B on the user interface 41 shown in fig. 9A.

In fig. 9B, window 902 may be used to display the character code for logo 3. Additionally, window 902 may also be used to provide access to editing window 902, such as closing, zooming in, zooming out, and the like.

In some embodiments, region 9031 may be included in window 902. Wherein the area 9031 may be used to display the character code of the logo 3. In addition, controls 9032 may also be included in window 902. Wherein control 9032 may be used to provide entry for updating the character code of logo 3.

Alternatively, after determining that the identifier 3 is stored in the background server, the tablet computer may display a window 904 as illustrated in the example of fig. 9C on the user interface 41 illustrated in fig. 9A.

In fig. 9C, window 904 may be used to display the two-dimensional code for logo 3. Additionally, window 904 may also be used to provide access to editing window 904, such as closing, zooming in, zooming out, and the like.

In some embodiments, the window 904 may include a region 9051 therein. Wherein the area 9051 may be used to display the two-dimensional code of the logo 3. In addition, controls 9052 may also be included in window 904. Wherein, the control 9052 may be used to provide an entry to update the two-dimensional code of the identification 3.

In addition, control 9032 or control 9052 is optional. In fig. 9B or fig. 9C, the tablet computer may automatically update the character code or the two-dimensional code of the identifier 3 after a period of time passes, or may update the character code or the two-dimensional code of the identifier 3 after detecting the operation triggered on the control 9032 or the control 9052, which is not limited in this application.

In summary, the tablet computer can call the dynamic code generation module in the tablet computer to generate the identifier 3 by means of the application market 1 in the tablet computer. The tablet personal computer can transmit the identifier 3 and application information of video playing application in the tablet personal computer to the background server, and the identifier 3 can be transmitted to the mobile phone by displaying the character code or the two-dimensional code of the identifier 3.

After determining that the background server stores the identifier 3, the background server can determine application information of the video playing application in the mobile phone based on the identifier 3 and the mapping relationship (the process can be described in S39-S40 in fig. 6).

The background server may transmit the application name of the video playing application in the mobile phone and the video playing progress of the video a, or the application name, the application version, and the video playing progress of the video a to the mobile phone (the process may be described with reference to S41 in fig. 6).

Thus, the handset may determine that there is a tablet (i.e., an electronic device that uniquely corresponds to the identity 3) requesting a synchronized application. And, the mobile phone can determine that the tablet computer synchronizes the video playing application and the video playing progress of the video a to the mobile phone.

The cell phone can store the video playing progress of the video a, and the cell phone can determine whether the video playing application needs to be synchronized. (the process can be described with reference to S42 in fig. 6).

In one embodiment, upon determining that the video playback application is not installed in the handset, the handset may determine that a synchronized video playback application is required.

In one embodiment, when it is determined that the video playing application is installed in the mobile phone and the application version of the video playing application installed in the mobile phone is later than the version of the video playing application transmitted by the background server in the mobile phone, the mobile phone can determine that the video playing application needs to be synchronized, so that the problem that the video a cannot be played is avoided.

In addition to the above, the handset may determine that no video playback application needs to be installed.

When the mobile phone determines that the video playing application needs to be synchronized, based on the application information of the video playing application in the mobile phone, the mobile phone may request the background server to download the installation package of the video playing application in batch (the process may be described with reference to S43 in fig. 6).

The background server may obtain the CDN address from the CDN server and transmit the CDN address to the handset (see description of S44 in fig. 6 for this procedure). The CDN address is used for indicating the storage position of the installation package of the video playing application. The specific representation mode of the CDN address is not limited in the present application.

The mobile phone can download the installation package of the video playing application based on the CDN address, and can install the video playing application in the mobile phone based on the installation package of the video playing application, and store the video playing progress of the video a in the mobile phone (the process can be described with reference to S45 in fig. 6), so that the mobile phone can play the video a in the video playing application according to the video playing progress of the video a.

The mobile phone can play the video a in the video playing application according to the video playing progress of the video a.

In other embodiments, based on the above description, the mobile phone can synchronize the video playing progress of video a in the video playing application based on the identifier 3.

For example, the mobile phone can call a dynamic code identification module in the mobile phone by means of an application market or a system application in the mobile phone, and the identifier 3 can be obtained by scanning and identifying a character code or a two-dimensional code of the identifier 3 displayed by the tablet computer. The mobile phone can acquire the video playing progress of the video a from the server based on the identifier 3. Therefore, after receiving the operation for indicating to play the video a in the video playing application, the mobile phone can play the video a in the installed video playing application according to the video playing progress of the video a.

Referring to fig. 10A-10B, fig. 10A-10B are schematic diagrams of a man-machine interface according to an embodiment of the present application.

Based on the description of the embodiment of fig. 4A, the handset may display the user interface 21 shown in the example of fig. 4A.

Among these, the user interface 21 may include: an icon 4011 of the application market 2, an icon of a smart life, an icon of music, an icon of a cell phone manager, an icon of a memo, an icon of a travel application, an icon of a sports health application, and the like.

After the video playing application is installed, the mobile phone may display the user interface 21 illustrated in the example of fig. 4A from the user interface 21 illustrated in the example of fig. 10A. Wherein, the icon 4012 of the video playing application is newly added in the user interface 21.

After detecting the operation of starting the video playing application indicated by the user (for example, clicking on the icon 4012 of the video playing application), the mobile phone may start the video playing application, and may display the user interface 51 shown in fig. 10B. The user interface 51 may be used to present the video in the video playing application according to the video playing progress of the video a.

In fig. 10B, the video a is played in accordance with the video play progress of the video a in the user interface 51. It can be seen that the video playing progress of the video a in the user interface 51 of fig. 10B is the same as the video playing progress of the video a in the user interface 41 of fig. 9A, so that the user can watch the video a according to the video playing progress of the video a in the tablet computer in the video playing application of the mobile phone.

In summary, the tablet computer can synchronize an application installed in the tablet computer and an application service condition of the application to the mobile phone through the background server and the CDN server based on the identifier 3.

Based on the foregoing description, the application synchronization method provided in the present application will be described in detail by taking the electronic device 11, the electronic device 12, and the server 13 in the communication system 10 shown in fig. 1 in scenario one as an example.

Referring to fig. 11, fig. 11 is a signaling interaction diagram of an application synchronization method according to an embodiment of the present application.

As shown in fig. 11, the application synchronization method of the present application may include:

s101, after receiving a first operation, the first electronic device sends a first message to the server, wherein the first operation is used for starting a synchronous application function of the first electronic device, and the first message comprises a first identifier.

The specific implementation of the first electronic device may be referred to the description of the electronic device 11 mentioned in scenario one, and the specific implementation of the server may be referred to the description of the server 13 mentioned in scenario one.

The specific implementation of S101 may be referred to the description of the S11-S13 embodiment shown in fig. 2 in scenario one. The first operation may include, but is not limited to: click, double click, long press, etc., the specific implementation of the first operation may be referred to the description of operation 1 in S11 shown in fig. 2 in scenario one. The specific implementation of the first message can be seen from the description of the message 11 in S13 shown in fig. 2 in scenario one. The first identifier is used for uniquely determining that the first electronic device initiates the synchronous application request 1, and a specific implementation of the first identifier can be referred to as description of the identifier 1 mentioned in scenario one.

S102, the first electronic equipment displays a first interface, and the first interface comprises a first identifier.

The specific implementation of S102 may be referred to the description of the S16 embodiment shown in fig. 2 in scenario one. The specific implementation manner of the first interface may be referred to the description of displaying the character code or the two-dimensional code of the identifier 1 in S16 shown in fig. 2 in the first scenario.

For example, the first interface may be a user interface displayed in a screen of the first electronic device, or may be a picture or web page shared by the first electronic device to the second electronic device.

In some embodiments, the first identifier in the first interface may be a character code or a two-dimensional code, so that the second electronic device can conveniently obtain the first identifier by scanning and identifying the character code or the two-dimensional code.

S103, the second electronic device acquires the first identification from the first electronic device.

The specific implementation of the second electronic device may be referred to in scenario one for the description of the electronic device 12. The specific implementation of S103 can be seen from the description of the embodiment S18 shown in fig. 2 in scenario one.

The first electronic device and the second electronic device are different electronic devices. In some embodiments, the device types of the first electronic device and the second electronic device may be the same or different. The operating systems of the first electronic device and the second electronic device may be the same or different.

S104, the second electronic equipment displays a third interface, and the third interface comprises an application installed in the second electronic equipment.

The specific implementation of S104 may be referred to the description of the embodiment S23 shown in fig. 2 in scenario one. The third interface may be specifically implemented by referring to the description of displaying the application list in S23 shown in fig. 2 in scenario one.

S105, the second electronic device determines at least one application after receiving a second operation executed by the user on the third interface.

The specific implementation of S105 may be referred to the description of the S24-S25 embodiment shown in fig. 2 in scenario one. The second operation may include, but is not limited to: clicking, double clicking, long pressing, etc., a second operation may be used to determine an application that the user selects to synchronize from among applications installed in the second electronic device, and a specific implementation of the second operation may be described with reference to operation 2 in S24-S25 shown in fig. 2 in scenario one. The number and type of at least one application is not limited in this application.

For example, the at least one application may include application c and application d in S24-S25 shown in fig. 2, and may also be one application installed in the second electronic device.

S106, the second electronic device sends a fifth message to the server, wherein the fifth message comprises the first identification and information of the at least one application, and the fifth message is used for synchronizing the at least one application to the first electronic device based on the first identification.

The specific implementation of S106 may be referred to as description of the S26 embodiment shown in fig. 2 in scenario one. The fifth message is specifically described with reference to message 16 in S26 shown in fig. 2 in scenario one.

Wherein the at least one application is an application synchronized by the second electronic device to the first electronic device via the server based on the first identification. The information of the at least one application may be used to determine each application and an application version of each application.

For example, when at least one application includes application c and application d in S24 to S25 shown in fig. 2, the information of at least one application includes: application information of application c in the electronic device 12 and application information of application d in the electronic device 12. Wherein the application information of each application may include at least an application name and an application version. In addition, the application information of each application may further include: and (5) applying the service condition.

And S107, the server sends a second message to the first electronic device, wherein the second message comprises information of at least one application.

The specific implementation of S107 may be referred to the description of the embodiment S27-S28 shown in fig. 2 in scenario one. The second message is specifically implemented as described in the context of message 17 in S28 shown in fig. 2 in scenario one.

S108, the first electronic device installs at least one application in the first electronic device based on the second message.

The specific implementation of S108 may be referred to the description of the embodiments S291-S294 shown in fig. 2 in scenario one.

According to the application synchronization method, communication connection and mutual communication among the first electronic equipment, the second electronic equipment and the server can be achieved through the first electronic equipment based on the identification generated by the first electronic equipment. Therefore, the first electronic device can synchronize at least one application installed in the second electronic device through the server, the difference between the device types among the electronic devices, the operating system among the electronic devices and the application names and application versions of the applications among the electronic devices is not required to be considered, the synchronization of the application names and the application versions among the electronic devices of various operating systems and the device types is realized through the transmission of application information, or the synchronization of the application names, the application versions and the application service conditions among the electronic devices of various operating systems and the device types is realized, account sharing is not required, additional hardware modules are not required to be added, the realization process is convenient and quick, the cost of synchronizing the application among the electronic devices is reduced, and the user experience of synchronizing the application among the electronic devices is improved.

In some embodiments, the server may store the first identification after receiving the first message. After the server has stored the first identification, the server may send a third message to the first electronic device, the third message indicating that the server has stored the first identification. Upon receiving the third message, the first electronic device may determine that the server has stored the first identification. The first electronic device may display the first interface.

The specific implementation of the above process can be referred to the description of the S14-S16 embodiment shown in fig. 2 in scenario one. The third message is specifically implemented as described in the context of message 12 in S15 shown in fig. 2 in scenario one.

In some embodiments, upon determining that at least one application needs to be synchronized, the first electronic device may display a second interface, the second interface including the at least one application. Thus, the application that the first electronic device needs to synchronize can be presented to the user, and the user can be further provided with an entry for selecting the application that needs to synchronize.

After receiving an operation of selecting a first application from at least one application by a user, the first electronic device installs the first application in the first electronic device.

The specific implementation of the above process may be referred to the description of the S291 embodiment shown in fig. 2 in scenario one. The specific implementation of the second interface may be referred to in S291 shown in fig. 2 in scenario one, and the application a may also display a description of a user interface.

Wherein the first application may be from one or more of the at least one application. For example, when the at least one application includes application c and application d in S291 shown in fig. 2 in scenario one, the first application may be application c and/or application d.

In S101, after receiving the first operation, the first electronic device may generate a first identifier, and then send the first identifier to the server. Thereby, the uniqueness and randomness of the first identity is ensured such that the server can uniquely determine that the first electronic device initiates the synchronization application request 1 based on the first identity.

The specific implementation of the above process may be referred to the description of the embodiment of fig. 1 and the embodiments of S12-S13 shown in fig. 2 in scenario one.

The specific implementation manner of generating the first identifier by the first electronic device is not limited in this application.

In some embodiments, the first electronic device may generate the first identification based on the time window. Thus, the uniqueness and randomness of the first identification can be ensured.

In other embodiments, the first electronic device may generate the first identification based on the time window and device information of the first electronic device. Therefore, on the basis of guaranteeing the uniqueness of the first identifier, the randomness of the first identifier can be increased, so that the randomness of the first identifier is more thorough.

In other embodiments, the first electronic device may generate the first identification based on the time window and an encryption algorithm. Therefore, on the basis of guaranteeing the uniqueness and the randomness of the first identifier, the privacy of the first identifier can be further improved, and the first identifier is guaranteed to be irreversible.

In other embodiments, the first electronic device may generate the first identification based on the time window, device information of the first electronic device, and an encryption algorithm. Thus, the uniqueness, randomness, and privacy of the first identification can be ensured.

The time window is random and dynamically changed, and the time window may be a period of time including the current time, or the current time. The device information of the first electronic device is used to uniquely identify the first electronic device, and the device information may take the form of a representation such as a device ID, a device model number, or a device number. The specific type of encryption algorithm mentioned above is not limited in this application.

In some embodiments, the first electronic device may include a second application, the first operation being an operation triggered on one control for the second application.

The specific implementation of the second application may be referred to the description of the application a shown in fig. 2 in the first scenario, and the specific implementation of one control of the second application may be referred to the description of the control 1 in S11 shown in fig. 2 in the first scenario.

For example, the second application may be an application marketplace or a system setting. In addition, the second application may also be other applications besides an application marketplace or a system setting.

In some embodiments, the first electronic device may display first content after the at least one application is successfully installed, the first content being used to instruct the first electronic device to complete the at least one application in synchronization.

The specific implementation of the above procedure may be referred to the description of the S294 embodiment shown in fig. 2 in scenario one. The specific implementation of the first content may be referred to the description of the second hint content in S294 shown in fig. 2 in scenario one.

In addition, after the first electronic device successfully installs the at least one application, a fourth message may be further sent to the server, where the fourth message is used to inform the second electronic device that the first electronic device completes the at least one application synchronously.

The specific implementation of the above procedure may be referred to the description of the S294 embodiment shown in fig. 2 in scenario one. A specific implementation of the fourth message may be referred to the description of the indication message 11 in S294 shown in fig. 2 in scenario one.

After receiving the fourth message, the server may send a sixth message to the second electronic device, where the sixth message is used to instruct the first electronic device to complete at least one application synchronously.

The specific implementation of the above procedure may be referred to the description of the S294 embodiment shown in fig. 2 in scenario one. A specific implementation of the sixth message may be referred to the description of the indication message 12 in S294 shown in fig. 2 in scenario one.

The second electronic device may display second content indicating that the first electronic device is synchronized to complete the at least one application.

The specific implementation of the above procedure may be referred to the description of the S294 embodiment shown in fig. 2 in scenario one. The specific implementation of the first content may be referred to the description of the fifth hint content in S294 shown in fig. 2 in scenario one.

In S103, the second electronic device may acquire the first identifier from the first electronic device in a plurality of manners.

In some embodiments, the second electronic device may identify the second identifier by scanning and identifying a character code or a two-dimensional code displayed by the first electronic device. The second electronic device may obtain the first identification based on the second identification.

The specific implementation of the above process may be referred to the description of the S18 embodiment shown in fig. 2 in scenario one. The specific implementation of the second identifier may be referred to the description of identifier 2 in S18 shown in fig. 2 in scenario one.

Consider the phenomenon that the second electronic device may have a recognition error. Thus, the second electronic device may display a fourth interface, the fourth interface including the second identifier.

After receiving the modified content within the preset time period, the second electronic device may determine that the second electronic device identifies an error. The second electronic device can change the second identifier based on the modified content to obtain the first identifier.

And the second electronic device can determine that the second electronic device is correctly identified after receiving the operation for determining that the second identifier is correct within the preset time period or after not receiving the modified content after the preset time period. The second electronic device may determine that the second identification is the first identification.

The specific implementation manner of the above process may refer to the application b in S18 shown in fig. 2 in the first scenario, to determine whether a description of the modification content for modifying the identified identifier 2 is received within the duration 1. For a specific implementation of the preset duration, see description of duration 1 in S18 shown in fig. 2 in scenario one.

It should be noted that the second electronic device has higher recognition accuracy, and the second electronic device may directly determine the second identifier as the first identifier.

Thus, the second electronic device can obtain the first identification transmitted by the first electronic device based on the user wish.

In some embodiments, the second electronic device includes a third application. The specific type of the third application is not limited herein. For example, the third application is an application marketplace or a system setting. In addition, the third application may also be other applications besides an application marketplace or a system setting.

After receiving a third operation triggered on a control of a third application, the second electronic device can acquire the first identifier from the first electronic device, and the third operation is used for triggering the second electronic device to acquire the first identifier.

Wherein, the specific implementation of the third application can be referred to the description of the application b shown in fig. 2 in the first scenario, the specific implementation of one control of the third application can be referred to the description of one control of the application b in S18 shown in fig. 2 in the first scenario, and the specific implementation of the third operation can be referred to the description of the operation triggered on one control of the application b in S18 shown in fig. 2 in the first scenario.

In some embodiments, the at least one application includes a fourth application. Wherein the information of the fourth application includes an application name and an application version.

The application version of the fourth application in the first electronic device is a first version, the first version is matched with the device type and the operating system of the first electronic device, the application version of the fourth application in the second electronic device is a second version, and the second version is matched with the device type and the operating system of the second electronic device.

The application name of the fourth application in the first electronic device is a first name, the application name of the fourth application in the second electronic device is a second name, and the first name and the second name are used for indicating the fourth application.

Thus, the server may determine the second name and the second version based on the mapping relationship, the first name, and the first version.

The specific implementation manner of the above process may refer to the server 13 in S27 shown in fig. 2 in scenario one, which determines, based on the mapping relationship, the description of the application information of the application c in the electronic device 11 and the application information of the application d in the electronic device 11. The specific implementation of the mapping relationship can be seen from the description of the embodiment of fig. 1 and the embodiment of S27 shown in fig. 2 in scenario one.

Wherein the first version and the second version may be the same or different. For example, the first version is the latest version or one old version corresponding to the second version.

Wherein the first name and the second name may be the same or different. For example, the first name may be music and the second name may be music.

Based on the foregoing description, the application synchronization method provided in the present application will be described in detail by taking the electronic device 21, the electronic device 22, and the server 23 in the communication system 20 shown in fig. 5 in the second scenario as an example.

Referring to fig. 12, fig. 12 is a signaling interaction diagram of an application synchronization method according to an embodiment of the present application.

As shown in fig. 12, the application synchronization method of the present application may include:

s201, the first electronic device displays a fifth interface, and the fifth interface comprises an application installed in the first electronic device.

The specific implementation of the first electronic device may be referred to as description of the electronic device 21 mentioned in scenario two.

The specific implementation of S201 may be referred to the description of the S31 embodiment shown in fig. 6 in scenario two. The application installed in the first electronic device may be one or more, and the application installed in the first electronic device may be displayed in the fifth interface in a variety of ways. For a specific implementation of the fifth interface, see S31 shown in fig. 6 in scenario two, the application b may display a description of the interfaces corresponding to the application e and the application f.

S202, the first electronic device determines at least one application after receiving a fourth operation executed by a user on a fifth interface.

The specific implementation of S202 may be referred to the description of the S31 embodiment shown in fig. 6 in scenario two. The fourth operation may include, but is not limited to: clicking, double clicking, long pressing, etc., the fourth operation may be used to determine an application that is synchronized by the user from the selections in the applications installed in the first electronic device, and a specific implementation of the fourth operation may be referred to in S31 shown in fig. 6 in scenario two, the description of the operation triggered on the selection control of application e or the operation triggered on the selection control of application f. The number and type of at least one application is not limited in this application.

For example, the at least one application may include the application e and the application f in S31 shown in fig. 6, and may also be one application installed in the first electronic device.

And S203, the first electronic equipment sends a seventh message to the server after receiving a fifth operation, wherein the fifth operation is used for starting the synchronous application function of the first electronic equipment, and the seventh message comprises a third identifier and information of at least one application.

The specific implementation of the server may be referred to the description of the server 23 mentioned in the second scenario, and the specific implementation of the second electronic device may be referred to the description of the electronic device 22 mentioned in the second scenario.

The first electronic device and the second electronic device are different electronic devices.

In some embodiments, the device types of the first electronic device and the second electronic device may be the same or different. The operating systems of the first electronic device and the second electronic device may be the same or different.

The specific implementation of S203 may be referred to the description of the embodiment S31 shown in fig. 6 in scenario two. The fifth operation may include, but is not limited to: click, double click, long press, etc., the specific implementation of the fifth operation can be seen from the description of operation 3 in S31-S32 shown in fig. 6 in scenario two. The seventh message is specifically implemented as described in the message 21 in S33 shown in fig. 6 in scenario two. The third identifier is used for uniquely determining that the first electronic device initiates the synchronous application request 2, and a specific implementation of the third identifier can be seen from the description of the identifier 3 mentioned in the second scenario.

Wherein the at least one application is an application synchronized by the first electronic device to the second electronic device via the server based on the third identification. The information of the at least one application may be used to determine each application and an application version of each application.

For example, when at least one application includes the application e and the application f in S31 shown in fig. 6, the information of at least one application includes: application information of application e in the electronic device 21 and application information of application f in the electronic device 21. Wherein the application information of each application may include at least an application name and an application version. In addition, the application information of each application may further include: and (5) applying the service condition.

S204, the first electronic device displays a sixth interface, and the sixth interface comprises a third identifier.

The specific implementation of S204 may be referred to the description of the embodiment S36 shown in fig. 6 in scenario two. The specific implementation manner of the sixth interface may be referred to the description of displaying the character code or the two-dimensional code of the identifier 3 in S36 shown in fig. 6 in the second scenario.

For example, the sixth interface may be a user interface displayed in a screen of the first electronic device, or may be a picture or web page shared by the first electronic device to the second electronic device.

In some embodiments, the third identifier in the first interface may be a character code or a two-dimensional code, so that the second electronic device can conveniently obtain the third identifier by scanning and identifying the character code or the two-dimensional code.

S205, the second electronic device acquires the third identification from the first electronic device.

The specific implementation of S205 may be referred to the description of the S37 embodiment shown in fig. 6 in scenario two.

S206, the second electronic device sends a tenth message to the server, wherein the tenth message comprises the third identifier.

The specific implementation of S206 may be referred to the description of the embodiment S38 shown in fig. 6 in scenario two. The tenth message is specifically implemented as described in the message 23 in S38 shown in fig. 6 in scenario two.

S207, the server sends an eleventh message to the second electronic device, wherein the eleventh message comprises information of at least one application, and the eleventh message is used for the second electronic device to install the at least one application in the second electronic device.

The specific implementation of S207 may be described with reference to the embodiment S39-S41 shown in fig. 6 in scenario two. The twenty-first message is specifically implemented as described with respect to message 24 in S41 shown in fig. 6 in scenario two.

S208, the second electronic device installs at least one application in the second electronic device based on the eleventh message.

The specific implementation of S208 may be referred to the description of the S42-S44 embodiment shown in fig. 6 in scenario two.

According to the application synchronization method, communication connection and mutual communication among the first electronic equipment, the second electronic equipment and the server can be achieved through the first electronic equipment based on the identification generated by the first electronic equipment. Therefore, the first electronic device can synchronize at least one application installed in the first electronic device to the second electronic device through the server, the difference among device types among the electronic devices, operating systems among the electronic devices and application names and application versions of the applications in the electronic devices is not needed to be considered, the synchronization of various application names and application versions among the electronic devices of various operating systems and device types is realized through the transmission of application information, or the synchronization of various application names, application versions and application service conditions among the electronic devices of various operating systems and device types is realized, account sharing is not needed, additional hardware modules are not needed to be added, the realization process is convenient and quick, the cost of synchronous application among the electronic devices is reduced, and the user experience of synchronous application among the electronic devices is improved.

In some embodiments, the server may store the third identification and information of the at least one application after receiving the seventh message. After the server has stored the third identification, the server may send an eighth message to the first electronic device, the eighth message indicating that the server has stored the third identification. Upon receiving the eighth message, the first electronic device may determine that the server has stored the third identification. The first electronic device may display the sixth interface.

The specific implementation of the above process may be referred to the description of the S33-S36 embodiment shown in fig. 6 in scenario two. For a specific implementation of the eighth message, see the description of the message 22 in S35 shown in fig. 6 in scenario two.

In S203, after receiving the fifth operation, the first electronic device may generate a third identifier, and then send the third identifier to the server. Thereby, the uniqueness and randomness of the third identity is ensured such that the server can uniquely determine that the first electronic device initiates the synchronization application request 2 based on the third identity.

The specific implementation of the above process may be described with reference to the embodiment of fig. 5 and the embodiment of S32 shown in fig. 6 in scenario two.

The specific implementation manner of generating the third identifier by the first electronic device is not limited in this application.

In some embodiments, the first electronic device may generate the third identification based on the time window. Thus, the uniqueness and randomness of the third identity can be ensured.

In other embodiments, the first electronic device may generate the third identification based on the time window and device information of the first electronic device. Therefore, on the basis of guaranteeing the uniqueness of the third identifier, the randomness of the third identifier can be increased, so that the randomness of the third identifier is more thorough.

In other embodiments, the first electronic device may generate the third identification based on the time window and an encryption algorithm. Therefore, on the basis of guaranteeing the uniqueness and the randomness of the third identifier, the privacy of the third identifier can be further improved, and the third identifier is guaranteed to be irreversible.

In other embodiments, the first electronic device may generate the third identification based on the time window, the device information of the first electronic device, and the encryption algorithm. Thus, the uniqueness, randomness, and privacy of the third identification can be ensured.

The time window is random and dynamically changed, and the time window is a period of time containing the current time or the current time. The device information of the first electronic device is used to uniquely identify the first electronic device, and the device information may take the form of a representation such as a device ID, a device model number, or a device number. The specific type of encryption algorithm mentioned above is not limited in this application.

In some embodiments, the first electronic device may include a fifth application, the fifth operation being an operation triggered on one control for the fifth application.

The specific implementation of the fifth application may be referred to the description of the application a shown in fig. 6 in the second scenario, and the specific implementation of one control of the fifth application may be referred to the description of the control 3 in S31 shown in fig. 6 in the second scenario.

For example, the fifth application may be an application marketplace or a system setting. In addition, the fifth application may also be other applications besides an application marketplace or a system setting.

In some embodiments, the second electronic device may display fourth content after the at least one application is successfully installed, the fourth content being used to instruct the second electronic device to complete the at least one application in synchronization.

The specific implementation of the above process may be referred to the description of the S45 embodiment shown in fig. 6 in scenario two. The specific implementation of the fourth content may be referred to the description of the fourth hint content in S45 shown in fig. 6 in scenario two.

In addition, after the second electronic device successfully installs the at least one application, the twelfth message may be further sent to the server, where the twelfth message is used to inform the first electronic device that the second electronic device completes the at least one application synchronously.

The specific implementation of the above process may be referred to the description of the S45 embodiment shown in fig. 6 in scenario two. A specific implementation of the twelfth message can be seen from the description of the indication message 21 in S45 shown in fig. 6 in scenario two.

After receiving the twelfth message, the server may send a ninth message to the first electronic device, where the ninth message is used to notify the first electronic device that the second electronic device completes at least one application synchronously.

The specific implementation of the above process may be referred to the description of the S45 embodiment shown in fig. 6 in scenario two. A specific implementation of the sixth message may be referred to the description of the indication message 22 in S45 shown in fig. 6 in scenario two.

The first electronic device may display third content indicating that the second electronic device is synchronized to complete the at least one application.

The specific implementation of the above process may be referred to the description of the S45 embodiment shown in fig. 6 in scenario two. The specific implementation of the third content may be referred to the description of the sixth hint content in S45 shown in fig. 6 in scenario two.

In S205, the second electronic device may obtain the third identifier from the first electronic device in a variety of manners.

In some embodiments, the second electronic device may identify the fourth identifier by scanning and identifying a character code or a two-dimensional code displayed by the first electronic device. The second electronic device may obtain the third identifier based on the fourth identifier.

The specific implementation of the above process may be referred to the description of the S37 embodiment shown in fig. 6 in scenario two. The specific implementation of the fourth identifier may be referred to the description of identifier 4 in S37 shown in fig. 6 in scenario two.

Consider the phenomenon that the second electronic device may have a recognition error. Thus, the second electronic device may display a seventh interface, the seventh interface comprising the fourth identification.

After receiving the modified content within the preset time period, the second electronic device may determine that the second electronic device identifies an error. The second electronic device may change the fourth identifier based on the modified content to obtain a third identifier.

And the second electronic device can determine that the second electronic device is correctly identified after receiving the operation for determining that the fourth identifier is correct within the preset time period or after not receiving the modified content after the preset time period. The second electronic device may determine that the fourth identifier is the third identifier.

The specific implementation manner of the above process may refer to S37 shown in fig. 6 in the second scenario, where the application b determines whether a description of the modification content for modifying the identified identifier 4 is received within the duration 2. For a specific implementation of the preset duration, see description of duration 2 in S37 shown in fig. 6 in scenario two.

It should be noted that the second electronic device has higher recognition accuracy, and the second electronic device may directly determine the fourth identifier as the third identifier.

Thus, the second electronic device can obtain the third identification transmitted by the first electronic device based on the user wish.

In some embodiments, the second electronic device includes a seventh application. The specific type of the seventh application is not limited herein. For example, the seventh application is an application marketplace or a system setting. In addition, the seventh application may also be other applications besides an application marketplace or a system setting.

After receiving a sixth operation triggered on one control of the seventh application, the second electronic device may acquire the third identifier from the first electronic device, where the sixth operation is used to trigger the second electronic device to acquire the third identifier.

The specific implementation of the seventh application may be referred to the description of the application b shown in fig. 6 in the second scenario, the specific implementation of one control of the seventh application may be referred to the description of one control of the application b in S37 shown in fig. 6 in the second scenario, and the specific implementation of the sixth operation may be referred to the description of the operation triggered on one control of the application b in S37 shown in fig. 6 in the second scenario.

In some embodiments, upon determining that at least one application needs to be synchronized, the second electronic device may display an eighth interface, the eighth interface including the at least one application. Thus, the application that the second electronic device needs to synchronize can be presented to the user, and the user can be further provided with an entry for selecting the application that wants to synchronize.

Upon receiving an operation of selecting the eighth application from the at least one application by the user, the second electronic device may install the eighth application in the second electronic device.

The specific implementation of the above process may be referred to the description of the S42 embodiment shown in fig. 6 in scenario two. The eighth interface may be specifically implemented by referring to S42 shown in fig. 6 in scenario two, where the application b may also display a description of a user interface.

Wherein the eighth application may be from one or more of the at least one application. For example, when the at least one application includes application e and application f in S42 shown in fig. 6 in scenario two, the eighth application may be application e and/or application f.

In some embodiments, the at least one application includes a sixth application, and the information of the sixth application includes an application name and an application version.

The application version of the sixth application in the first electronic device is a first version, the first version is matched with the device type and the operating system of the first electronic device, the application version of the sixth application in the second electronic device is a second version, and the second version is matched with the device type and the operating system of the second electronic device.

The application name of the sixth application in the first electronic device is a first name, the application name of the sixth application in the second electronic device is a second name, and the first name and the second name are used for indicating the sixth application.

The specific implementation manner of the above process may refer to the server 23 in S40 shown in fig. 6 in the second scenario, which determines, based on the mapping relationship, the description of the application information of the application e in the electronic device 22 and the application information of the application f in the electronic device 22. The specific implementation of the mapping relationship can be seen from the description of the embodiment of fig. 5 and the embodiment of S40 shown in fig. 6 in the second scenario.

Wherein the first version and the second version may be the same or different. For example, the second version is the latest version or one old version corresponding to the first version.

Based on the description of the foregoing embodiments, the electronic device is taken as an example of a tablet pc, and the electronic device related to the present application is described with reference to fig. 13.

Fig. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 13, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, a user identification module (subscriber identification module, SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, 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, and the like.

It is to be understood that the structure illustrated herein does not constitute a specific limitation on the electronic device 100. In other embodiments, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a memory, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller may be a neural hub and a command center of the electronic device 100, among others. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

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

The I2C interface is a bi-directional synchronous serial bus comprising a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc., respectively, through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, such that the processor 110 communicates with the touch sensor 180K through an I2C bus interface to implement a touch function of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, the processor 110 may contain multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through the I2S interface, to implement a function of answering a call through the bluetooth headset.

PCM interfaces may also be used for audio communication to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface to implement a function of answering a call through the bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus for asynchronous communications. The bus may be a bi-directional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is typically used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through a UART interface, to implement a function of playing music through a bluetooth headset.

The MIPI interface may be used to connect the processor 110 to peripheral devices such as a display 194, a camera 193, and the like. The MIPI interfaces include camera serial interfaces (camera serial interface, CSI), display serial interfaces (display serial interface, DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the photographing functions of electronic device 100. The processor 110 and the display 194 communicate via a DSI interface to implement the display functionality of the electronic device 100.

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

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transfer data between the electronic device 100 and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices, etc.

It should be understood that the connection between the modules illustrated in the present application is merely illustrative, and does not limit the structure of the electronic device 100. In other embodiments, the electronic device 100 may also employ different interfaces in the above embodiments, or a combination of interfaces.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating 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. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, antenna 1 and mobile communication module 150 of electronic device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that electronic device 100 may communicate with a network and other devices through wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The electronic device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer executable program code including instructions. The processor 110 executes various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device 100 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like.

The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When electronic device 100 is answering a telephone call or voice message, voice may be received by placing receiver 170B in close proximity to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The gyro sensor 180B may be used to determine a motion gesture of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the electronic device 100, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the electronic device 100 through the reverse motion, so as to realize anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude from barometric pressure values measured by barometric pressure sensor 180C, aiding in positioning and navigation.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip machine, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The electronic equipment gesture recognition method can also be used for recognizing the gesture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, the electronic device 100 may range using the distance sensor 180F to achieve quick focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it may be determined that there is an object in the vicinity of the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there is no object in the vicinity of the electronic device 100. The electronic device 100 can detect that the user holds the electronic device 100 close to the ear by using the proximity light sensor 180G, so as to automatically extinguish the screen for the purpose of saving power. The proximity light sensor 180G may also be used in holster mode, pocket mode to automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 may utilize the collected fingerprint feature to unlock the fingerprint, access the application lock, photograph the fingerprint, answer the incoming call, etc.

The temperature sensor 180J is for detecting temperature. In some embodiments, the electronic device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, when the temperature is below another threshold, the electronic device 100 heats the battery 142 to avoid the low temperature causing the electronic device 100 to be abnormally shut down. In other embodiments, when the temperature is below a further threshold, the electronic device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures.

The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e.: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Taking an Android system with a layered architecture as an example, the application exemplifies a software structure of the electronic device 100.

Fig. 14 is a software block diagram of an electronic device according to an embodiment of the present application. As shown in fig. 14, the layered architecture divides the software into several layers, each with a clear role and division of work. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer (APP), an application framework layer (APP framework), an Zhuoyun row (Android run) and system library (library), and a kernel layer (kernel).

The application layer may include a series of application packages.

As shown in fig. 14, the application package may include Applications (APP) such as camera, gallery, calendar, call, map, navigation, WLAN, bluetooth, music, video, game, chat, shopping, travel, instant messaging (e.g., short message), smart home, device control, etc. Among them, the application program mentioned in the present application may also be referred to as an application.

The intelligent home application can be used for controlling or managing home equipment with networking function. For example, home appliances may include electric lights, televisions, and air conditioners. For another example, the home appliances may also include a burglarproof door lock, a speaker, a floor sweeping robot, a socket, a body fat scale, a desk lamp, an air purifier, a refrigerator, a washing machine, a water heater, a microwave oven, an electric cooker, a curtain, a fan, a television, a set-top box, a door and window, and the like.

In addition, the application package may further include: the home screen (i.e. desktop), the negative screen, the control center, the notification center, etc. application programs.

The negative one screen, which may be referred to as "-1 screen", refers to a User Interface (UI) that slides the screen rightward on the main screen of the electronic device until it slides to the leftmost split screen. For example, the negative screen may be used to place shortcut service functions and notification messages, such as global search, shortcut entries (payment codes, weChat, etc.) for a page of an application, instant messaging and reminders (express information, expense information, commute road conditions, driving travel information, schedule information, etc.), and attention dynamics (football stand, basketball stand, stock information, etc.), etc. The control center is an up-slide message notification bar of the electronic device, that is, a user interface displayed by the electronic device when a user starts an up-slide operation at the bottom of the electronic device. The notification center is a drop-down message notification bar of the electronic device, i.e., a user interface displayed by the electronic device when a user begins to operate downward on top of the electronic device.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in fig. 14, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

Window managers (window manager) are used to manage window programs such as manage window states, attributes, view (view) additions, deletions, updates, window order, message collection and processing, and the like. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like. And, the window manager accesses the portal of the window for the outside world.

The content provider is used to store and retrieve data and make such data accessible to the application. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The telephony manager is used to provide the communication functions of the electronic device 100. Such as the management of call status (including on, hung-up, etc.).

A resource manager (resource manager) provides various resources for applications such as localization strings, icons, pictures, layout files of user interfaces (layout xml), video files, fonts, colors, identification numbers (identity document, IDs) of user interface components (user interface module, UI components) (also known as serial numbers or account numbers), etc. And the resource manager is used for uniformly managing the resources.

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

The android runtime includes a core library and virtual machines. And the Android running process is responsible for scheduling and managing the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of the Android system.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media library (media library), three-dimensional graphics processing library (e.g., openGLES), 2D graphics engine (e.g., SGL), image processing library, etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio video encoding formats, such as: MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The workflow of the software and hardware of the electronic device 100 is illustrated below in connection with a scenario in which sound is played using a smart speaker.

When touch sensor 180K receives a touch operation, a corresponding hardware interrupt is issued to the kernel layer. The kernel layer processes the touch operation into the original input event (including information such as touch coordinates, time stamp of touch operation, etc.). The original input event is stored at the kernel layer. The application framework layer acquires an original input event from the kernel layer, and identifies a control corresponding to the input event. Taking the touch operation as a touch click operation, taking a control corresponding to the click operation as an example of a control of an intelligent sound box icon, the intelligent sound box application calls an interface of an application framework layer, starts the intelligent sound box application, further starts audio driving by calling a kernel layer, and converts an audio electric signal into a sound signal by a loudspeaker 170A.

Illustratively, the present application provides an electronic device comprising: a memory and a processor; the memory is used for storing program instructions; the processor is configured to invoke the program instructions in the memory to cause the electronic device to perform the application synchronization method of the previous embodiments.

Illustratively, the present application provides a chip system for use with an electronic device including a memory, a display screen, and a sensor; the chip system includes: a processor; when the processor executes the computer instructions stored in the memory, the electronic device performs the application synchronization method of the previous embodiments.

Illustratively, the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes an electronic device to implement the application synchronization method in the previous embodiments.

Illustratively, the present application provides a computer program product comprising: executing instructions, the executing instructions being stored in a readable storage medium, from which at least one processor of the electronic device can read the executing instructions, the at least one processor executing the executing instructions causing the electronic device to implement the application synchronization method in the previous embodiments.

In the above-described embodiments, all or part of the functions may be implemented by software, hardware, or a combination of software and hardware. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer readable storage medium. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by a computer program to instruct related hardware, the program may be stored in a computer readable storage medium, and the program may include the above-described method embodiments when executed. And the aforementioned storage medium includes: ROM or random access memory RAM, magnetic or optical disk, etc.

Claims

1. An application synchronization method, applied to a first electronic device, the method comprising:

after receiving a first operation, sending a first message to a server, wherein the first operation is used for starting a synchronous application function of the first electronic equipment, and the first message comprises a first identifier;

displaying a first interface, wherein the first interface comprises the first identifier;

receiving a second message from the server, the second message including information of at least one application that a second electronic device synchronizes to the first electronic device through the server based on the first identification;

installing the at least one application in the first electronic device based on the second message.

2. The method of claim 1, wherein prior to displaying the first interface, the method further comprises:

3. The method according to claim 1 or 2, wherein the first identifier in the first interface is a character code or a two-dimensional code, and the first identifier is obtained by the second electronic device by scanning and identifying the character code or the two-dimensional code.

4. A method according to any of claims 1-3, wherein the installing the at least one application in the first electronic device based on the second message comprises:

displaying a second interface, the second interface comprising the at least one application;

after receiving an operation of selecting a first application from the at least one application by a user, installing the first application in the first electronic device.

5. The method according to any one of claims 1-4, further comprising:

generating the first identification based on a time window;

or generating the first identifier based on a time window and device information of the first electronic device;

Or generating the first identifier based on a time window and an encryption algorithm;

or generating the first identifier based on a time window, device information of the first electronic device and an encryption algorithm;

6. The method of any of claims 1-5, wherein the first electronic device comprises a second application, the first operation being an operation triggered on one control for the second application.

7. The method of claim 6, wherein the second application is an application marketplace or a system setting.

8. The method of any of claims 1-7, wherein after installing the at least one application in the first electronic device based on the second message, the method further comprises:

and displaying first content, wherein the first content is used for indicating the first electronic equipment to synchronously finish the at least one application.

9. The method of claim 8, wherein the method further comprises:

And sending a fourth message to the server, wherein the fourth message is used for informing the server to the second electronic device that the first electronic device synchronously completes the at least one application.

10. An application synchronization method, applied to a second electronic device, the method comprising:

acquiring a first identifier from a first electronic device;

determining at least one application after receiving a second operation performed by a user on the third interface;

and sending a fifth message to a server, wherein the fifth message comprises the first identifier and information of the at least one application, and the fifth message is used for synchronizing the at least one application to the first electronic device based on the first identifier by the server.

11. The method of claim 10, wherein the obtaining the first identification from the first electronic device comprises:

the second identifier is identified by scanning and identifying the character code or the two-dimensional code displayed by the first electronic device;

and acquiring the first identifier based on the second identifier.

12. The method of claim 11, wherein the obtaining the first identifier based on the second identifier comprises:

Displaying a fourth interface, wherein the fourth interface comprises the second identifier;

after receiving the modified content within a preset time period, changing the second identifier based on the modified content to obtain the first identifier;

or, after receiving an operation for determining that the second identifier is correct within a preset time period or after not receiving modified content after the preset time period, determining that the second identifier is the first identifier.

13. The method of any of claims 10-12, wherein, when the second electronic device includes a third application, the obtaining the first identification from the first electronic device comprises:

14. The method of claim 13, wherein the third application is an application marketplace or a system setting.

15. The method according to any one of claims 10-14, further comprising:

receiving a sixth message from the server, the sixth message being for indicating that the first electronic device completes the at least one application synchronously;

And displaying second content, wherein the second content is used for indicating the first electronic equipment to synchronously finish the at least one application.

16. The method of any one of claims 1-15, wherein the at least one application comprises a fourth application;

the information of the fourth application comprises an application name and an application version, the application version of the fourth application in the first electronic device is a first version, the first version is matched with the device type and the operating system of the first electronic device, the application version of the fourth application in the second electronic device is a second version, the second version is matched with the device type and the operating system of the second electronic device, and the first version is different from the second version;

17. The method of claim 16, wherein the first version is a latest version or an old version corresponding to the second version.

18. The method according to any one of claims 1 to 17, wherein,

the first electronic device is different from the second electronic device in device type;

19. An application synchronization method, applied to a first electronic device, the method comprising:

displaying a fifth interface, wherein the fifth interface comprises an application installed in the first electronic device;

determining at least one application after receiving a fourth operation performed by a user on the fifth interface;

after receiving a fifth operation, sending a seventh message to a server, wherein the fifth operation is used for starting a synchronous application function of the first electronic device, the seventh message comprises a third identifier and information of at least one application, and the at least one application is an application which is synchronized to a second electronic device by the server through the first electronic device based on the third identifier;

displaying a sixth interface, wherein the sixth interface comprises the third identifier.

20. The method of claim 19, wherein prior to displaying the sixth interface, the method further comprises:

21. The method according to claim 19 or 20, wherein the third identifier in the sixth interface is a character code or a two-dimensional code, and the second electronic device is configured to obtain the third identifier by scanning and identifying the character code or the two-dimensional code.

22. The method according to any one of claims 19-21, further comprising:

generating the third identification based on a time window;

or generating the third identifier based on a time window and device information of the first electronic device;

or generating the third identifier based on a time window and an encryption algorithm;

or generating the third identifier based on a time window, device information of the first electronic device and an encryption algorithm;

23. The method of any of claims 19-22, wherein the first electronic device comprises a fifth application, the fifth operation being an operation triggered on one control of the fifth application.

24. The method of claim 23, wherein the fifth application is an application marketplace or a system setting.

25. The method according to any one of claims 19-24, further comprising:

receiving a ninth message from the server, the ninth message being for indicating that the second electronic device completes the at least one application synchronously;

and displaying third content, wherein the third content is used for indicating the second electronic equipment to synchronously finish the at least one application.

26. The method of any of claims 19-25, wherein the at least one application comprises a sixth application;

the information of the sixth application comprises an application name and an application version, the application version of the sixth application in the first electronic device is a first version, the first version is matched with the device type and the operating system of the first electronic device, the application version of the sixth application in the second electronic device is a second version, the second version is matched with the device type and the operating system of the second electronic device, and the first version is different from the second version;

27. The method of claim 26, wherein the second version is a latest version or an old version corresponding to the first version.

28. The method of any one of claims 19-27, wherein,

29. An electronic device, comprising: a memory and a processor;

the memory is used for storing program instructions;

the processor is configured to invoke the program instructions in the memory, to cause the electronic device to perform the application synchronization method of any of claims 1-9, 16-18, or to cause the electronic device to perform the application synchronization method of any of claims 10-18, or to cause the electronic device to perform the application synchronization method of any of claims 19-28.

30. A computer readable storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the application synchronization method of any one of claims 1-9, 16-18, or cause the electronic device to perform the application synchronization method of any one of claims 10-18; alternatively, the computer instructions, when run on a server, cause the server to perform the application synchronization method of any of claims 19-28.