Interaction methods and related devices

Abstract

The application provides an interaction method and related devices, the interaction method comprises: a first electronic device displays a first user interface, the first user interface comprises an option of a second electronic device; in response to a user operation on the option of the second electronic device, the first electronic device sends a first message to the second electronic device; in response to receiving the first message, the second electronic device displays a second user interface, the second user interface is used to ask a user whether to establish a data transmission link, the data transmission link is used to migrate data of the second electronic device to the first electronic device, and the second user interface comprises a first option; in response to a user operation on the first option, the second electronic device establishes the data transmission link with the first electronic device. The application can simplify the operation of the user and improve the user's experience of changing the machine.

Description

Interaction methods and related devices

[0001] This application is a divisional application. The original application has the application number 202410808075.6 and the original application date is June 20, 2024. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and in particular to an interaction method and related equipment. Background Technology

[0003] When users switch electronic devices, they can migrate data from the old device to the new device using applications such as phone cloning. Before data migration, a data transfer link needs to be established between the old and new devices to transfer the data to be migrated. Currently, users need to perform multiple operations on both the old and new devices to establish this data transfer link, which is cumbersome and reduces the user's experience when switching devices. Summary of the Invention

[0004] This application provides an interaction method and related device that can simplify user operations and improve the user's device switching experience.

[0005] In a first aspect, an interaction method is provided, applied to a communication system including a first electronic device and a second electronic device. The interaction method includes: the first electronic device displaying a first user interface, the first user interface including options of the second electronic device; in response to a user's operation on the options of the second electronic device, the first electronic device sending a first message to the second electronic device; in response to receiving the first message, the second electronic device displaying a second user interface, the second user interface for querying the user whether to establish a data transmission link, the data transmission link for migrating data from the second electronic device to the first electronic device, the second user interface including a first option; and in response to a user's operation on the first option, the second electronic device establishing the data transmission link with the first electronic device.

[0006] According to the interaction method provided in this application embodiment, the first electronic device can display the options of the second electronic device on a first user interface. When a user determines that data needs to be migrated from the second electronic device to the first electronic device, the user can directly click the option corresponding to the second electronic device. In response to the user's click operation, the first electronic device can send a first message to the second electronic device. In response to receiving the first message, the second electronic device automatically displays a second user interface (e.g., a pop-up window), which asks the user whether they agree to establish a data transmission link between the first and second electronic devices. When the user clicks the first option on the second user interface, the data transmission link establishment process can be directly triggered to establish the data transmission link.

[0007] The interaction method provided in this application eliminates the need for "device discovery" between two devices by scanning a QR code (or manually entering an account password), enabling the creation of data transmission links more simply and quickly. This simplifies user operations and improves the user's device switching experience.

[0008] In some examples, the first electronic device can send the first message to the second electronic device via any wired or wireless communication method. This application does not specifically limit the specific implementation method. For example, the first electronic device and the second electronic device maintain a near-field communication connection, and there is an underlying communication channel between them for transmitting control signaling. The first electronic device can send the first message to the second electronic device through this underlying communication channel. That is, a point-to-point communication method can be used to send and receive the first message.

[0009] In some examples, the first electronic device displays the first user interface in response to a user's operation on a data migration application such as phone cloning.

[0010] In some examples, the first electronic device can read a list of trusted devices from the management module and display the option of a trusted second electronic device on a second user interface. For example, the trusted devices here may be devices that have undergone data migration, quick device switching, or multi-screen collaboration with the first electronic device, but are not limited to these.

[0011] For example, the second electronic device may have undergone data migration, rapid device switching, or multi-screen collaboration with the first electronic device, and a "trust relationship" has been established in this business scenario. Therefore, the information of the second electronic device is saved in the trusted device list. When the first electronic device needs to display the first user interface, it can read the trusted device list and display the options of the second electronic device on the second user interface.

[0012] In some examples, a first electronic device can conduct business transactions with a second electronic device through a first application and establish a trust relationship. The management module can then store information about the second electronic device, such as recording it in a list of trusted devices. For example, the first application could be an application capable of performing the aforementioned data migration, fast device switching, or multi-screen collaboration services. For instance, the first application could be a terminal emulator or a mobile phone clone. Furthermore, the first application could be any application capable of conducting business transactions with the second electronic device and establishing a trust relationship (i.e., an application with high security requirements).

[0013] In some examples, a "trust relationship" exists between the second electronic device and the first electronic device. Alternatively, the second and first electronic devices may belong to the same user account, thus establishing a "trust relationship." For instance, the second and first electronic devices may be under the same Huawei account. Exemplarily, the first and second electronic devices may belong to the same user account and be of the same device type (e.g., both are mobile phones or tablets). Exemplarily, the second and first electronic devices may belong to the same user account and be within the same trust ring or the same trust list. Based on these trust relationships, information about the second electronic device can be recorded in the trusted device list. And / or, the first electronic device may display the options of the second electronic device on a second user interface.

[0014] In some examples, the first message can trigger the second electronic device to display a second user interface. This application does not specifically limit the specific content of the first message. For example, the first message may include the address of the first electronic device, the address of the second electronic device (for addressing), the identifier of the first electronic device, and the identifier of the service of the second electronic device that needs to be activated. For example, the service of the second electronic device that needs to be activated may be provided by a mobile phone clone, and therefore can also be understood or described as activating the mobile phone clone on the second electronic device, thereby enabling the display of the second user interface.

[0015] In some examples, the second user interface can appear as a floating window or a pop-up; that is, the second user interface can be displayed as a floating window, a pop-up, or a pop-up window. For example, if the second electronic device is currently displaying an interface (such as the main interface), upon receiving the first message, the second electronic device automatically pops up the second user interface in response to receiving the first message.

[0016] For example, the second electronic device has a phone clone installed. The ability of the second electronic device to display the second user interface can be granted by the phone clone. When the second electronic device receives the first message, even if the phone clone on the second electronic device is not opened, the second user interface, which exists in the form of a floating window, pop-up, or pop-up window, can be automatically popped up or displayed. In other words, the display of the second user interface does not depend on the user opening the phone clone, thereby simplifying the user's operation.

[0017] In some examples, the second user interface may also include a "Reject Connection" option. If the user refuses to establish the data transmission link, clicking the "Reject Connection" option can terminate the data transmission link establishment process. For example, in response to the user clicking the "Reject Connection" option, the second electronic device may also close or exit the second user interface.

[0018] For example, the "Reject Connection" option could be located in the upper right corner of the second user interface. If the user refuses to establish the data transmission link, they can click this option. The option, while closing the second user interface, instructs the second electronic device to terminate the data transmission link establishment process.

[0019] In some examples, the data transmission link can be a P2P link. Alternatively, it can be any existing or future high-speed data transmission link, such as a near link, NFC link, IR link, or ZigBee link. This application does not impose any special limitations on this. It should be understood that the data transmission link in the embodiments of this application can also be referred to as a data transmission channel, connection, or link, etc. The process of establishing the data transmission link is prior art and will not be elaborated here.

[0020] In one possible implementation, after the data transmission link is established, the method further includes: the first electronic device displaying a third user interface for a user to select data to be migrated; in response to the user's operation on the first data to be migrated, the first electronic device sending a request message for the first data to the second electronic device; and in response to the request message, the second electronic device sending the first data to the first electronic device via the data transmission link.

[0021] To improve the user experience of using new devices, the interaction method provided in this application selects the data to be migrated from the old device (i.e., the second electronic device) on the new device (i.e., the first electronic device), which is beneficial to improving the user's device switching experience.

[0022] In one possible implementation, before the second electronic device sends the first data to the first electronic device via the data transmission link, the method further includes: the first electronic device displaying a fourth user interface, the fourth user interface being used to instruct a user to input verification information of the second electronic device; in response to the verification information input by the user, the first electronic device sending the verification information to the second electronic device; the second electronic device verifying the user's identity based on the verification information; and the second electronic device sending first indication information to the first electronic device, the first indication information being used to indicate that the user's identity verification has passed.

[0023] According to the interaction method provided in the embodiments of this application, the second electronic device sends the first data to the first electronic device only after the user's identity verification is successful. This setting helps ensure data security and prevents data from being illegally obtained. To improve the user experience of the new device, this application verifies the user's identity on the new device (i.e., the first electronic device), which helps improve the user's device switching experience.

[0024] In some examples, after the first electronic device determines that the user's identity verification has passed based on the first indication information, in response to the determination, the first electronic device sends a request message for first data to the second electronic device.

[0025] In one possible implementation, the fourth user interface includes a password input box, and the verification information includes the password of the second electronic device entered by the user in the password input box, such as a lock screen password, which can be a six-digit numeric password, a four-digit numeric password, or a pattern password, but is not limited thereto. Furthermore, the verification information of the second electronic device can also be fingerprint information, facial information, or any other information capable of verifying the user's identity; this application does not impose any special limitations on this.

[0026] In one possible implementation, after the data transmission link is established, the method further includes: the second electronic device displaying a fifth user interface, the fifth user interface being used to instruct the user to perform a data migration operation on the first electronic device.

[0027] By setting the second electronic device to display the fifth user interface, users can be reminded to switch to the first electronic device (i.e., the new device) in a timely manner to perform subsequent data migration work, which helps to improve the user's device switching experience.

[0028] In one possible implementation, before the first electronic device displays the third user interface, the method further includes: the first electronic device receiving data list information from the second electronic device, the data list information being used to generate the third user interface.

[0029] In some examples, before displaying the third user interface, the first electronic device may receive a data list (directory) information sent by the second electronic device. This data list information is used to indicate the information of the files that the second electronic device can migrate to the first electronic device, such as the file type, name, file size, number of file items, etc., but not limited to this. The first electronic device generates and displays the third user interface based on the data list information. That is, the third user interface displays the above information to the user so that the user can select the data to be migrated.

[0030] In one possible implementation, before the first electronic device displays the first user interface, the first electronic device establishes a trusted connection with the second electronic device and saves information of the second electronic device; or, the first electronic device and the second electronic device are devices under the same user account.

[0031] In some examples, the first electronic device establishes a trusted connection with the second electronic device. This could be because the first electronic device and the second electronic device have previously conducted related business and established a "trust relationship" in that business scenario. Therefore, the information of the second electronic device can be saved, and the second electronic device can be displayed on the first user interface as a candidate device that may migrate data to the first electronic device.

[0032] For example, establishing a trusted connection between the first electronic device and the second electronic device may include, but is not limited to, data migration, quick device switching, or multi-screen collaboration between the two devices. For instance, the second electronic device may be a device that has previously performed data migration (e.g., phone cloning) with the first electronic device; or, the second electronic device may be a device that has previously performed quick device switching with the first electronic device; or, the second electronic device may also be a device that has previously performed multi-screen collaboration with the first electronic device.

[0033] In one possible implementation, before the first electronic device displays the first user interface, the first electronic device establishes a near-field communication connection with the second electronic device. For example, establishing this near-field communication connection may include the first and second electronic devices being near each other, such as the first and second electronic devices being close to each other, and both the WLAN module and / or Bluetooth module being enabled.

[0034] In one possible implementation, the verification information includes any one or more of the following: password, fingerprint information, facial information, and iris information.

[0035] In one possible implementation, the third user interface includes application information of the second electronic device, and / or file information in the second electronic device.

[0036] Secondly, an interaction method is provided, the method comprising: a first electronic device displaying a first user interface, the first user interface including options of a second electronic device; in response to a user's operation on an option of the second electronic device, the first electronic device sending a first message to the second electronic device; wherein the first message is used to trigger the second electronic device to display a second user interface, the second user interface being used to ask the user whether to establish a data transmission link, the data transmission link being used to migrate data of the second electronic device to the first electronic device, the second user interface including a first option, and when the second electronic device detects a user's operation on the first option, the second electronic device establishing the data transmission link with the first electronic device.

[0037] In one possible implementation, after the data transmission link is established, the method further includes: the first electronic device displaying a third user interface for a user to select data to be migrated; in response to the user's operation on the first data to be migrated, the first electronic device sending a request message for the first data to the second electronic device; and the first electronic device receiving the first data from the second electronic device through the data transmission link.

[0038] In one possible implementation, before the first electronic device receives the first data from the second electronic device via the data transmission link, the method further includes: the first electronic device displaying a fourth user interface, the fourth user interface being used to instruct a user to input verification information from the second electronic device; in response to the verification information input by the user, the first electronic device sending the verification information to the second electronic device, the verification information being used by the second electronic device to verify the user's identity; and the first electronic device receiving first indication information from the second electronic device, the first indication information being used to indicate that the user's identity verification has passed.

[0039] In one possible implementation, the fourth user interface includes a password input box, and the verification information includes the password of the second electronic device entered by the user in the password input box.

[0040] In one possible implementation, before the first electronic device displays the third user interface, the method further includes: the first electronic device receiving data list information from the second electronic device, the data list information being used to generate the third user interface.

[0041] In one possible implementation, before the first electronic device displays the first user interface, the first electronic device establishes a trusted connection with the second electronic device and saves information of the second electronic device; or, the first electronic device and the second electronic device are devices under the same user account.

[0042] In one possible implementation, the first electronic device establishes a near-field communication connection with the second electronic device before the first electronic device displays the first user interface.

[0043] In one possible implementation, the verification information includes any one or more of the following: password, fingerprint information, facial information, and iris information.

[0044] In one possible implementation, the third user interface includes application information of the second electronic device, and / or file information in the second electronic device.

[0045] Thirdly, an interaction method is provided, the method comprising: a second electronic device receiving a first message from a first electronic device, wherein the first message is sent in response to an operation by a user on an option of the second electronic device displayed on the first electronic device; in response to receiving the first message, the second electronic device displaying a second user interface for querying the user whether to establish a data transmission link, the data transmission link for migrating data from the second electronic device to the first electronic device, the second user interface including a first option; and in response to an operation by the user on the first option, the second electronic device establishing the data transmission link with the first electronic device.

[0046] In one possible implementation, after the data transmission link is established, the method further includes: the second electronic device receiving a request message for first data from the first electronic device, the first data being data selected by the user on the first electronic device to be migrated; in response to the request message, the second electronic device sending the first data to the first electronic device through the data transmission link.

[0047] In one possible implementation, before the second electronic device sends the first data to the first electronic device via the data transmission link, the method further includes: the second electronic device receiving verification information of the second electronic device input by the user on the first electronic device; the second electronic device verifying the user's identity based on the verification information; and the second electronic device sending first indication information to the first electronic device, the first indication information indicating that the user's identity verification has passed.

[0048] In one possible implementation, the verification information includes the password of the second electronic device that the user entered on the first electronic device.

[0049] In one possible implementation, after the data transmission link is established, the method further includes: the second electronic device displaying a fifth user interface, the fifth user interface being used to instruct the user to perform a data migration operation on the first electronic device.

[0050] In one possible implementation, before the second electronic device receives a request message for first data from the first electronic device, the method further includes: the second electronic device sending data list information to the first electronic device, the data list information being used to generate a user interface for the user to select the first data.

[0051] In one possible implementation, the verification information includes any one or more of the following: password, fingerprint information, facial information, and iris information.

[0052] Fourthly, a communication device is provided, comprising: a module (e.g., including a processing module and an interface module) for performing the steps of any possible implementation of the second aspect above, or a module (e.g., including a processing module and an interface module) for performing the steps of any possible implementation of the third aspect above.

[0053] Fifthly, a communication device is provided, the device comprising at least one processor and a memory, the at least one processor being configured to execute: the method provided by any possible implementation of the second aspect above, or the method provided by any possible implementation of the third aspect above.

[0054] In a sixth aspect, a communication device is provided, the device comprising at least one processor and interface circuitry, the at least one processor being configured to execute: the method provided by any possible implementation of the second aspect above, or the method provided by any possible implementation of the third aspect above.

[0055] In a seventh aspect, an electronic device is provided, which includes any of the communication devices provided in the fourth, fifth, or sixth aspects described above.

[0056] Eighthly, a computer program product is provided, comprising a computer program that, when executed by a processor, performs the method provided by any possible implementation of the second aspect above, or the method provided by any possible implementation of the third aspect above.

[0057] Ninthly, a chip is provided, the chip comprising: a processor for calling and running a computer program from a memory, causing a communication device having the chip installed to perform: the method provided by any possible implementation of the second aspect above, or the method provided by any possible implementation of the third aspect above.

[0058] In a tenth aspect, a communication system is provided, comprising: a first electronic device and a second electronic device, the first electronic device being configured to perform the method provided by any possible implementation of the second aspect above, and the method provided by any possible implementation of the third aspect above. Attached Figure Description

[0059] Figure 1 shows a set of user interface diagrams for a new device during the establishment of a data transmission link.

[0060] Figure 2 shows a set of user interface diagrams for the old equipment during the establishment of a data transmission link.

[0061] Figure 3 is a schematic diagram of a communication system provided in an embodiment of this application.

[0062] Figure 4 shows a set of user interface diagrams of electronic device 100 during the establishment of a data transmission link.

[0063] Figure 5 shows a set of user interface diagrams of electronic device 200 during the establishment of a data transmission link.

[0064] Figure 6 is a schematic diagram of the software modules of electronic device 100.

[0065] Figure 7 shows another set of user interface diagrams of electronic device 100 during the establishment of a data transmission link.

[0066] Figure 8 is a schematic flowchart of the interaction method 800 provided in an embodiment of this application.

[0067] Figure 9 is a schematic block diagram of a communication device provided in an embodiment of this application.

[0068] Figure 10 is a schematic block diagram of a communication device provided in an embodiment of this application.

[0069] Figure 11 is a schematic block diagram of an example chip system provided in an embodiment of this application. Detailed Implementation

[0070] The technical solutions of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them.

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

[0072] The term "comprising" in this document indicates the presence of the described feature, whole, step, operation, element, and / or component, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or collections thereof. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0073] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of this application, unless otherwise stated, "a plurality of" means two or more.

[0074] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0075] With the continuous development of information technology, the use of electronic devices such as mobile phones and tablets is becoming increasingly widespread, and the pace of electronic device upgrades is also accelerating. This, to some extent, increases the frequency with which users replace their electronic devices. When switching between old and new devices, data such as apps, files, photos, and videos can be migrated from the old device to the new one, helping users quickly adapt to the new device.

[0076] Data migration refers to the process of copying or transferring data from one electronic device to another. In some scenarios, data migration can also be called data cloning, which has a similar meaning. This application does not impose specific limitations on this.

[0077] Typically, before migrating data, you need to install an application that supports fast data migration, such as a phone cloning app, on both the new and old devices. Users then operate the phone cloning app on both devices to establish a data transfer link. This link is then used to migrate the data from the old device to the new device, facilitating a convenient device switch.

[0078] In other words, before data migration, a data transmission link needs to be established between the new and old devices to transmit the data to be migrated. This data transmission link can be, for example, a wireless fidelity point-to-point (Wi-Fi P2P) link. The following explanation, using a mobile phone as an electronic device and in conjunction with Figures 1 and 2, illustrates the process of establishing a data transmission link in this related technology.

[0079] Figure 1 illustrates a set of user interface diagrams for a new mobile phone during the establishment of a data transmission link. During the process of establishing a data transmission link between the old and new devices, the user can perform the operations shown in Figure 1 on the new mobile phone.

[0080] In this application, the term "user interface (UI)" refers to the medium through which an application or operating system interacts and exchanges information with a user. It converts the internal form of information into a form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). This source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.

[0081] As shown in part (a) of Figure 1, the new phone in unlocked mode displays user interface 101. The user can click the "Phone Clone" icon in user interface 101. In response to the user's click, the new phone displays user interface 102 as shown in part (b) of Figure 1.

[0082] User interface 102 allows users to configure the current mobile phone, including options such as "This is the old device" and "This is the new device". When a user clicks the "This is the new device" option, the device is set as the "new device" for receiving data. In response to the user's click, the new mobile phone displays user interface 103 as shown in part (c) of Figure 1.

[0083] User interface 103 is used by the user to select the type of the old phone, including options corresponding to multiple types such as Huawei and other Android phones. For example, if the old phone is a Huawei phone, clicking the "Huawei" option allows the user to select the corresponding option based on the type of the old phone. In response to the user's click operation, the new phone displays user interface 104 as shown in part (d) of Figure 1.

[0084] The user interface 104 may include a QR code, which can be the QR code corresponding to the wireless local area networks (WLAN) created by the new mobile phone. The old mobile phone can scan the QR code to establish a communication connection between the new and old mobile phones, that is, to establish a data transmission link (such as a P2P link) or channel between the new and old mobile phones. In addition, the user interface 104 may also include the account (such as ALN-AL80%6562%CloudClone) and password (such as 14322222, XXXXXXXX) corresponding to the WLAN created by the new mobile phone, which can be used to support users to manually connect to the WLAN through the old mobile phone.

[0085] Figure 2 illustrates a set of user interface diagrams on the old mobile phone during the data transmission link establishment process. During the data transmission link establishment process between the old and new devices, the user can perform the operations shown in Figure 2 on the old mobile phone.

[0086] As shown in part (a) of Figure 2, the old phone in unlocked mode displays user interface 201. The user can click the "Phone Clone" icon in user interface 201. In response to the user's click, the old phone displays user interface 202 as shown in part (b) of Figure 2.

[0087] User interface 202 allows users to configure the current phone, including options such as "This is the old device" and "This is the new device." When a user clicks the "This is the old device" option, the device is set as the "old device" for sending data. In response to the user's click, the old phone displays user interface 203 as shown in part (c) of Figure 2.

[0088] User interface 203 is a QR code scanning interface, which can be used to allow users to scan QR codes displayed on the user interface 104 of the new phone. After the user successfully scans the QR code using the scanning box, the old phone displays user interface 204 as shown in part (d) of Figure 2. Alternatively, if the scan fails, the user can click the "Manual Connection" option on user interface 203, and then manually connect to the WLAN using the WLAN account and password displayed on user interface 104 on a new page.

[0089] User interface 204 can be used to guide the process of establishing a data transmission link (connection) between the old and new mobile phones. For example, user interface 204 may display a message such as "Connecting to new device". In addition, user interface 204 may also include animated graphics to show the current connection process between the new and old mobile phones, such as a dynamic radiation diagram of electromagnetic waves.

[0090] As can be seen from the relevant content in Figures 1 and 2 above, in the relevant technology, users need to perform multiple operations on the new and old devices, including clicking and scanning (manually entering account passwords), that is, they need to interact with the new and old devices multiple times before the data transmission link for transmitting the data to be migrated can be established. The whole operation process is cumbersome and inconvenient, thus reducing the user's device switching experience.

[0091] Based on this, the present application provides an interaction method that simplifies user operations during the establishment of a data transmission link, thereby improving device switching efficiency and enhancing the user's device switching experience.

[0092] Specifically, considering that the new phone may have been used by the user for some time before the data migration operation, and during this period of use, the new phone and the old phone may have already conducted relevant business and established a "trust relationship" based on this, and considering data security, data migration is usually only possible between two devices that have an existing "trust relationship".

[0093] Based on the above considerations, according to the interaction method provided in this application embodiment, the new mobile phone can use an old mobile phone with which a "trust relationship" has been established as a candidate device for data migration, and display it on the first user interface (e.g., user interface 103 shown in part (c) of Figure 1). When the user confirms that the data of the old mobile phone needs to be migrated to the new mobile phone, they can directly click the option corresponding to the old mobile phone on the first user interface. In response to the user's click operation, the new mobile phone can send a first message to the old mobile phone. In response to the receipt of the first message, the old mobile phone automatically displays a second user interface (e.g., a pop-up window), which asks the user whether they agree to establish a data transmission link between the new mobile phone and the old mobile phone. The user can directly trigger the establishment process of the data transmission link (e.g., a near-field P2P channel) by clicking the confirmation option on the second user interface to establish the data transmission link.

[0094] The interaction method provided in this application eliminates the need for "device discovery" between two devices by scanning a QR code (or manually entering an account password), enabling the creation of data transmission links more simply and quickly. This simplifies user operations and improves the user's device switching experience.

[0095] The interaction method provided in this application embodiment can be applied to the communication system 10 shown in FIG3. FIG3 is a schematic diagram of a communication system 10 provided in this application embodiment. As shown in FIG3, the communication system 10 may include an electronic device 100 and an electronic device 200. The electronic device 100 and the electronic device 200 may specifically be any electronic device capable of data migration, such as a mobile phone, tablet computer, laptop computer, smart TV (e.g., smart screen), ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), wearable electronic device, in-vehicle device, virtual reality device, etc.

[0096] Electronic devices 100 and 200 can have the same or different device forms. For example, electronic devices 100 and 200 can both be mobile phones, tablets, laptops, or smart TVs; or electronic devices 100 can be mobile phones and electronic devices 200 can be tablets or laptops, or electronic devices 100 can be tablets or laptops and electronic devices 100 can be mobile phones. This application does not limit the specific technology or device form used by electronic devices 100 and 200.

[0097] In this embodiment, both electronic device 100 and electronic device 200 are mobile phones, as an example. Electronic device 200 can be a sending device for transmitting data to be migrated, used to send the data to be migrated to electronic device 100. Therefore, electronic device 200 in this embodiment can also be referred to as a source electronic device, old device, data sender, or transmitter, etc. Electronic device 100 can be a receiving device for receiving data to be migrated, used to receive the data to be migrated sent from electronic device 200. Therefore, electronic device 100 in this embodiment can also be referred to as a destination electronic device, new device, data receiver, or receiver, etc.

[0098] For example, electronic device 200 can be an old device previously used by the user, and electronic device 100 can be a newly purchased device by the user. For instance, electronic device 200 can be the old mobile phone in Figure 2 above, and electronic device 100 can be the new mobile phone in Figure 1 above.

[0099] In some examples, electronic device 100 and electronic device 200 can log in to the same user account, meaning they are devices under the same user account. For example, electronic device 100 and electronic device 200 can log in to the same Huawei account. This user account can be a mobile phone number, email address, a custom username, etc.

[0100] In some examples, electronic device 100 and electronic device 200 can communicate with each other, for example, they can establish a wired connection or a wireless connection. The wireless connection may include at least one of the following connections: Bluetooth (BT) connection, WLAN connection, Wi-Fi P2P connection, near field communication (NFC) connection, infrared (IR) near link connection or ZigBee connection, etc. This application embodiment does not limit this.

[0101] In some examples, electronic device 100 and electronic device 200 may be configured with the same or different software operating systems (OS). The software operating system here includes, but is not limited to, those mentioned above. And so on. Among them, For example, using Huawei's HarmonyOS, both electronic device 100 and electronic device 200 can be configured with...

[0102] Before data migration can begin, a data transmission link needs to be established between electronic device 100 (the receiving electronic device) and electronic device 200 (the sending electronic device) to transmit the data to be migrated. Only after this data transmission link is successfully established can electronic device 200 send the data to be migrated to electronic device 100 via this link, and electronic device 100 receive the data sent by electronic device 200 via this link, thus completing the data migration.

[0103] Figure 4 illustrates a set of user interface diagrams for the electronic device 100 during the establishment of a data transmission link. This application embodiment will use a mobile phone as the electronic device and take the example of a user changing mobile phones and migrating data between the two phones to describe in detail the interaction method provided by this application embodiment.

[0104] During the process of establishing a data transmission link between electronic device 100 and electronic device 200, the user can perform the operations shown in Figure 4 on electronic device 100 (i.e., the new mobile phone). Part (a) of Figure 4 shows the user interface 401 displayed on the screen of electronic device 100 in unlocked mode. This user interface 401 can be, for example, the main interface or desktop of electronic device 100. This user interface 401 displays icons for various apps, such as clock, calendar, gallery, settings, and phone clone apps. It should be understood that this user interface 401 can also display icons for many other apps; this application does not limit this.

[0105] As shown in part (a) of Figure 4, the user can click the “Phone Clone” icon in the user interface 401. In response to the user’s click, the electronic device 100 displays the user interface 402 shown in part (b) of Figure 4.

[0106] User interface 402 allows users to configure the current device, including options such as "This is the old device" and "This is the new device". When a user clicks the "This is the new device" option, the electronic device 100 is configured as a "new device" for receiving data. In response to the user's click, the electronic device 100 displays the user interface 403 shown in part (c) of Figure 4.

[0107] User interface 403 is used by the user to select the type of old device, including "My Old Device" and "Other Old Device Types". "Other Old Device Types" includes options corresponding to multiple types such as Huawei and other Android devices.

[0108] The "My Old Devices" section includes options for at least one candidate device, including electronic device 200. Here, a candidate device can be any other device to which data can potentially be migrated. Each candidate device option can include an identifier corresponding to that device. For example, "Wang Lei's P30" shown in part (c) of Figure 4 could be an identifier for electronic device 200, while "Wang Lei's Mate 60 Pro" could be an identifier for another candidate device.

[0109] In some examples, a candidate device can be a device with a "trust relationship" with electronic device 100, that is, electronic device 200 is a device with a "trust relationship" with electronic device 100. For example, electronic device 100 can obtain a list of trusted devices by reading a locally stored log file and display the trusted device as a candidate device on user interface 403.

[0110] In some examples, electronic device 200 and electronic device 100 have a "trust relationship". This means that electronic device 200 has already conducted relevant business with electronic device 100 before the user interface 403 is displayed, and a "trust relationship" has been established in the business scenario. Therefore, electronic device 200 can be displayed as a candidate device on user interface 403.

[0111] For example, specific business scenarios for establishing a "trust relationship" could include data migration, quick device switching, or multi-screen collaboration, but are not limited to these. For instance, electronic device 200 could be a device that has previously performed data migration (e.g., phone cloning) with electronic device 100; or, electronic device 200 could be a device that has performed quick device switching with electronic device 100, where quick device switching refers to electronic device 100 obtaining configuration information such as the lock screen password of electronic device 200 through a communication connection when setting up a new device, and then reusing this configuration information for services on electronic device 100; or, electronic device 200 could also be a device that has previously performed multi-screen collaboration with electronic device 100.

[0112] When electronic device 100 and electronic device 200 perform any of the aforementioned services (not limited to the examples above), a "trust relationship" is established between them. Electronic device 100 can save (record) relevant information of electronic device 200 to a corresponding log file. Thus, when electronic device 100 needs to display user interface 403, it can read this log file and display the corresponding options of electronic device 200 on user interface 403. For example, the relevant information of electronic device 200 may include device identifier, device address, etc., but is not limited to these.

[0113] Figure 6 is a schematic diagram of the software modules of electronic device 100. For example, as shown in Figure 6, electronic device 100 includes an application layer and a framework layer. The framework layer provides application programming interfaces (APIs) and programming frameworks for the applications in the application layer. The application layer includes multiple applications such as phone cloning and a first application. The framework layer includes a management module, which may be, for example, a distributed device management module. Electronic device 100 can conduct business transactions with electronic device 200 through the first application and establish a trust relationship. The management module can store information about electronic device 200, for example, recording the information of electronic device 200 in a list of trusted devices. When electronic device 100 needs to display user interface 403, phone cloning can read the list of trusted devices and display the options for electronic device 200 on user interface 403. For example, the first application here may be an application capable of performing the aforementioned data migration business, fast device switching business, or multi-screen collaboration business. For example, the first application may be a super terminal or phone cloning. Furthermore, the first application may also be any application capable of conducting business transactions with electronic device 200 and establishing a trust relationship (i.e., an application with high security requirements).

[0114] In some examples, electronic device 200 and electronic device 100 have a "trust relationship." Alternatively, electronic device 200 and electronic device 100 may belong to the same user account, thus establishing a "trust relationship." For example, electronic device 200 and electronic device 100 may be devices under the same Huawei account. For instance, electronic device 200 and electronic device 100 may belong to the same user account and be of the same device type (e.g., both are mobile phones or tablets). For instance, electronic device 200 and electronic device 100 may belong to the same user account and be within the same trust ring or the same trust list.

[0115] In some examples, the candidate device shown in part (c) of Figure 4 can be a device that has a "trust relationship" with electronic device 100 and is near-field online. That is, electronic device 200 not only has a "trust relationship" with electronic device 100, but also remains near-field online, so electronic device 200 can be displayed as a candidate device on user interface 403.

[0116] For example, keeping electronic device 200 online in the near field means that electronic device 200 is powered on and the WLAN module and / or Bluetooth module is turned on, so that electronic device 200 can be discovered or searched by electronic device 100.

[0117] As shown in part (c) of Figure 4, the user can click the option corresponding to the electronic device 200 (i.e., the option corresponding to "Wang Lei's P30"). In response to the user's click operation, since the electronic device 200 remains online in the near field, the electronic device 100 can send a first message to the electronic device 200. This first message is used to trigger the electronic device 200 to display the user interface 501.

[0118] Electronic device 100 can send a first message to electronic device 200 via any wired or wireless communication method. This application embodiment does not impose specific limitations on the implementation method. For example, electronic device 100 and electronic device 200 maintain a near-field communication connection, and there is an underlying communication channel between them for transmitting control signaling. Electronic device 100 can send the first message to electronic device 200 through this underlying communication channel. That is, point-to-point communication can be used to send and receive the first message.

[0119] In some examples, when a user clicks on the option corresponding to the electronic device 200 in the user interface 403, the electronic device 200 may display a new user interface (e.g., a pop-up window) in response to the user's click, which prompts the user to switch to the electronic device 200 for further operations.

[0120] At this point, the user's operation on electronic device 100 is temporarily complete, and the user can continue to operate on electronic device 200 to continue the data transmission link process.

[0121] Figure 5 illustrates a set of user interface diagrams for electronic device 200 during the establishment of a data transmission link. During the process of establishing a data transmission link between electronic device 100 and electronic device 200, the user can perform the operations shown in Figure 5 on electronic device 200.

[0122] As shown in part (a) of Figure 5, in response to receiving the first message, the electronic device 200 with the mobile phone clone installed automatically displays the user interface 501. The user interface 501 is used to ask the user whether they agree to establish a data transmission link between the electronic device 100 and the electronic device 200 to migrate data from the electronic device 200 to the electronic device 100. For example, the user interface 501 may include the identifier of the electronic device 100, "Wang Lei's Pura 70 Ultra," and prompts such as "After connection, local data can be migrated to the new device," thereby asking the user whether to establish the aforementioned data transmission link.

[0123] The first message can trigger the electronic device 200 to display the user interface 501. This application embodiment does not specifically limit the specific content of the first message. In some examples, the first message may include the address of the electronic device 100, the address of the electronic device 200 (for addressing), the identifier of the electronic device 100, and the identifier of the service of the electronic device 200 that needs to be activated. Here, the service of the electronic device 200 that needs to be activated can be provided by a mobile phone clone, and therefore can also be understood or described as activating the mobile phone clone on the electronic device 200, thereby enabling the display of the user interface 501.

[0124] In some examples, as shown in Figure 5, the user interface 501 can appear as a floating window or a pop-up window; that is, the user interface 501 can be displayed as a floating window, a pop-up window, or a pop-up window. For example, if the electronic device 200 is currently displaying a certain interface (e.g., the main interface), upon receiving the first message, the electronic device 200 automatically pops up the user interface 501 in response to receiving the first message.

[0125] For example, electronic device 200 has a phone clone installed. The ability of electronic device 200 to display the user interface 501 can be provided by the phone clone. When electronic device 200 receives the first message, even if the phone clone on electronic device 200 is not opened, the user interface 501 can automatically pop up or be displayed in the form of a floating window, pop-up box, or pop-up window. In other words, the display of user interface 501 does not depend on the user opening the phone clone, thereby simplifying the user's operation.

[0126] In some examples, the user interface 501 includes a "Connect" option, which the user can click to trigger the data transmission link establishment process if the user agrees to establish the data transmission link.

[0127] In some examples, the user interface 501 may also include a "Reject Connection" option. If the user refuses to establish the data transmission link, clicking the "Reject Connection" option can terminate the data transmission link establishment process. For example, in response to the user clicking the "Reject Connection" option, the electronic device 200 may also close or exit the user interface 501.

[0128] For example, the "Reject Connection" option could be located in the upper right corner of the user interface 501. If the user refuses to establish the data transmission link, they can click this option. The option, while closing the user interface 501, instructs the electronic device 200 to terminate the data transmission link establishment process.

[0129] When a user clicks the "Connect" option on user interface 501, the process of establishing the data transmission link is triggered. In response to the user's click, electronic device 200 displays user interface 502 as shown in part (b) of Figure 5.

[0130] The user interface 502 can be used to prompt the electronic device 100 and the electronic device 200 during the process of establishing a data transmission link (connection). For example, the user interface 502 may display a prompt message such as "Connecting". In addition, the user interface 502 may also include a dynamic diagram to show the current connection process between the electronic device 100 and the electronic device 200, such as a rotation dynamic diagram, a connection process dynamic diagram, or a dynamic radiation diagram of electromagnetic waves.

[0131] In some examples, similar to the aforementioned user interface 501, user interface 502, and user interfaces 503, 504, and 505 mentioned below, can all be displayed as floating windows, pop-ups, or pop-up windows. That is, user interfaces 501 to 505 can float above other interfaces (such as the main interface) and do not need to occupy the entire screen. As shown in Figure 5, user interfaces 501 to 505 can be displayed at the bottom of the display screen of electronic device 200. In other examples, user interfaces 501 to 505 can also be displayed in other positions such as the middle or top of the display screen. This application does not make any special limitations on this.

[0132] In some examples, user interfaces 501 to 505 can also be multiple interfaces displayed sequentially after the mobile phone clone on the electronic device 200 is opened (e.g., interfaces that fill the entire screen, similar to those shown in Figures 1, 2, and 4). That is, the user needs to open the mobile phone clone on the electronic device 200 to display user interfaces 501 to 505 sequentially, in order to complete the data transmission link establishment process and the subsequent data migration process. This application does not impose any special limitations on this.

[0133] In some examples, the data transmission link can be a P2P link. Alternatively, it can be any existing or future high-speed data transmission link, such as a near link, NFC link, IR link, or ZigBee link. This application does not impose any special limitations on this. It should be understood that the data transmission link in the embodiments of this application can also be referred to as a data transmission channel, connection, or link, etc. The process of establishing the data transmission link is prior art and will not be elaborated here.

[0134] As shown in section (c) of Figure 5, once the data transmission link is established, the electronic device 200 displays the user interface 503. The user interface 503 prompts the user to transfer to the electronic device 100 for subsequent file selection, identity verification, and other operations to complete the entire data migration process. Furthermore, the user interface 503 can also display prompts such as "This device must always be close to the new device and keep WLAN and Bluetooth enabled" to ensure that the data transmission link is not interrupted.

[0135] Accordingly, as shown in part (d) of Figure 4, once the data transmission link is established, the electronic device 100 displays user interface 404. User interface 404 is used to notify the user on the electronic device 100 that the data transmission link has been established and the user can proceed to the next step of selecting migration files. The user can click the "Next" option in user interface 404, and in response to the click operation, the electronic device 100 displays user interface 405 as shown in part (e) of Figure 4.

[0136] It is worth mentioning that displaying the user interface 404 is an optional step for the electronic device 100. In some examples, the electronic device 100 may not display the user interface 404. For example, after confirming that the data transmission link has been established, the user interface 403 can directly jump to the user interface 405.

[0137] User interface 405 allows users to select data to be migrated from electronic device 200 on electronic device 100. This interface includes a list of data that can be transferred from electronic device 200 to electronic device 100, such as contacts, messages, calendars, gallery, applications and data, system settings, and other data types. Users select the data to be transferred from the data list and then click the "Start Migration" option. In response to the user's migration operation, electronic device 100 sends a data request message to electronic device 200, requesting the selected data from the second electronic device. To improve the user experience of the new device, this application allows users to select the data to be migrated from the old device (i.e., electronic device 200) on the new device (i.e., electronic device 100), which helps improve the user's device switching experience.

[0138] In some examples, the data request message may include an identifier of the data selected by the user.

[0139] In some examples, such as part (e) in Figure 4, the user interface 405 may also include a "select all" option, allowing the user to select all migrateable data with a single click, thus simplifying the user's operation.

[0140] In some examples, as shown in part (e) of Figure 4, the user interface 405 may also include indications such as the size of the selected data to be migrated and the required transfer time.

[0141] In some examples, before displaying the user interface 405, the electronic device 100 may receive a data list (directory) information sent by the electronic device 200. This data list information is used to indicate the information of files that the electronic device 200 can migrate to the electronic device 100, such as file type, name, file size, number of file items, etc., but not limited to this. The electronic device 100 generates and displays the user interface 405 based on the data list information, that is, the user interface 405 displays the above information to the user so that the user can select the data to be migrated.

[0142] In some examples, as shown in section (e) of Figure 4, the user interface 405 displays multiple file types such as contacts, messages, calendars, and photo galleries. When the user clicks on a file or the checkbox to the left of a file, the file is selected as the data to be migrated. Furthermore, each type (e.g., photo gallery or application) may include multiple files, and in some cases, clicking on a type can bring up a new window for further selection within that type of file.

[0143] Accordingly, when electronic device 200 receives the data request message, electronic device 200 begins to collect the data requested by electronic device 100 and sends the requested data to be migrated to electronic device 100 through the previously established data transmission link, and electronic device 100 receives the data from electronic device 200 based on the data transmission link.

[0144] During the data migration process, the electronic device 200 can display a user interface 504 as shown in part (d) of Figure 5. The user interface 504 is used to indicate to the user that data migration is in progress, such as displaying information like "Data migration in progress". In addition, the user interface 504 can also display prompts such as "This device must always be close to the new device and keep WLAN and Bluetooth enabled" to ensure that the transmission link is not interrupted during data transmission.

[0145] After the data migration is complete, the electronic device 200 can display a user interface 505 as shown in part (e) of Figure 5. The user interface 505 is used to indicate to the user that the data migration is complete. For example, the user interface 505 can display information such as "Migration Complete". The user interface 505 may include a "Complete" option, which the user can click. In response to the user's click operation, the user interface 505 closes or exits, thus completing the entire data migration process.

[0146] In some examples, considering that users will use the electronic device 200 less in the future, the user interface 505 may also display prompts such as "If the device is not used for a long time, it is recommended to charge it to 50% to 80% or manually turn it off to protect the battery" to protect the battery.

[0147] In some examples, considering that users may clean up the data on the electronic device 200 and then hand it over to others, the user interface 505 may also display a prompt message such as "If you need to clean up the data on this device, please log out of your Huawei account first to avoid data on other devices logged into this account being deleted synchronously" to ensure data security.

[0148] In some examples, after a user clicks the "Start Migration" option on user interface 405, in response to the user's migration operation, electronic device 100 displays user interface 406 as shown in part (f) of Figure 4. User interface 406 is used to verify the legitimacy of the user's identity on electronic device 200. Only after the identity verification is successful will electronic device 100 send the aforementioned data request message to electronic device 200, thus enabling the subsequent data migration work. This setting helps ensure data security and prevents unauthorized data acquisition. To improve the user experience of the new device, this application verifies the user's identity on the new device (i.e., electronic device 100), which helps improve the user's device switching experience.

[0149] As shown in part (f) of Figure 4, the user interface 406 includes a password input box. The user interface 406 is used to instruct the user to enter the password of the electronic device 200 (i.e., "Wang Lei's P30") in the password input box. The password may be, for example, the lock screen password of the electronic device 200, such as a six-digit password, a four-digit password, or a pattern password, but is not limited to these.

[0150] In some examples, electronic device 100 can send the user's input result in the password input box to electronic device 200. Electronic device 200 matches the input result with its own correct lock screen password. If the two match successfully, it considers the user's identity verification to be successful. At this time, electronic device 200 can send the identity verification information to electronic device 100. After electronic device 100 confirms that the user's identity verification is successful, it sends the aforementioned data request message to electronic device 200.

[0151] If the two fail to match, it is considered that the user's identity verification has failed. At this time, electronic device 200 can send the identity verification failure information to electronic device 100. After electronic device 100 determines that the user's identity verification has failed, it will not send the aforementioned data request message to electronic device 200, that is, stop the subsequent data migration process.

[0152] In some examples, electronic device 200 can also send its own lock screen password to electronic device 100, which then matches the user's input in the password input box with the correct lock screen password from electronic device 200 to verify the user's identity.

[0153] Figure 7 illustrates another set of user interface diagrams for the electronic device 100 during the establishment of a data transmission link. Based on the aforementioned content in Figures 4 and 5, Figure 7 shows some possible extensions of the embodiments of this application.

[0154] Figure 7(a) shows the user interface 701 of the electronic device 100, corresponding to the aforementioned user interface 403. In this embodiment, the candidate devices displayed in the user interface 701 can be devices that have a "trust relationship" with the electronic device 100 but are not near-field online, such as devices that the electronic device 100 cannot discover or search for via near-field communication. For example, in the "My Old Devices" section of the user interface 701, an option corresponding to the electronic device 200 (i.e., "Wang Lei's P30") is displayed. Since the electronic device 200 is not near-field online (e.g., Bluetooth and / or WLAN functions are not enabled), this option can be "grayscaled" to indicate that the option is currently unavailable. When the user clicks the option, in response to the user's click operation, the electronic device 100 displays the pop-up window 702 shown in Figure 7(b) on the current interface.

[0155] As shown in part (b) of Figure 7, pop-up window 702 is used to remind the user to perform relevant operations to keep electronic device 200 online in the near field. For example, pop-up window 602 includes prompts such as "This device is offline. Please bring the device close to this device and keep WLAN and Bluetooth enabled." After receiving the above information, the user can click the "Confirm" option on pop-up window 702, and pop-up window 702 will close in response to the click. After the user enables the Bluetooth and WLAN functions of electronic device 200 and brings electronic device 200 close to electronic device 100, electronic device 200 becomes "online." At this time, the corresponding option on electronic device 200 changes from a "grayscale" state to a normal display state, indicating that the option is available. At this time, the user can click the option again and then continue with the relevant processes shown in Figures 4 and 5 above.

[0156] As shown in section (c) of Figure 7, in some examples, electronic device 100 determines that there are currently no candidate devices. In this case, user interface 703 may not display the "My Old Devices" section, or it may display the "My Old Devices" section but not include any devices. In this situation, the user can select the type of electronic device 200 based on the "Select Old Device Type" option in user interface 703. For example, if electronic device 200 is a Huawei phone, clicking the "Huawei" option will, in response to the user's click, display an interface with a QR code (e.g., similar to the aforementioned user interface 104), allowing the user to establish the aforementioned data transmission link by scanning the QR code or manually entering the WLAN account and password.

[0157] Building upon the foregoing embodiments, this application further provides an interaction method applicable to a communication system including a first electronic device and a second electronic device. The communication system may be, for example, the communication system 10 shown in FIG3, the first electronic device may be, for example, the electronic device 100 shown in FIG3, 4, and 7, and the second electronic device may be, for example, the electronic device 200 shown in FIG3 and 5. FIG8 is a schematic flowchart of the interaction method 800 provided in this application. The interaction method 800, including steps 801 to 816, will be described below with reference to FIG8.

[0158] In step 801, the first electronic device displays a first user interface, which includes options for the second electronic device. For example, the first user interface may be the user interface 403 shown in FIG. 4 above.

[0159] In some examples, the first electronic device displays the first user interface in response to a user's operation on a data migration application such as phone cloning.

[0160] In some examples, the first electronic device can read a list of trusted devices from the management module and display the option of a trusted second electronic device on a second user interface. For example, the trusted devices here may be devices that have undergone data migration, quick device switching, or multi-screen collaboration with the first electronic device, but are not limited to these.

[0161] For example, the second electronic device may have undergone data migration, rapid device switching, or multi-screen collaboration with the first electronic device, and a "trust relationship" has been established in this business scenario. Therefore, the information of the second electronic device is saved in the trusted device list. When the first electronic device needs to display the first user interface, it can read the trusted device list and display the options of the second electronic device on the second user interface.

[0162] In some examples, a first electronic device can conduct business transactions with a second electronic device through a first application and establish a trust relationship. The management module can then store information about the second electronic device, such as recording it in a list of trusted devices. For example, the first application could be an application capable of performing the aforementioned data migration, fast device switching, or multi-screen collaboration services. For instance, the first application could be a terminal emulator or a mobile phone clone. Furthermore, the first application could be any application capable of conducting business transactions with the second electronic device and establishing a trust relationship (i.e., an application with high security requirements).

[0163] In some examples, a "trust relationship" exists between the second electronic device and the first electronic device. Alternatively, the second and first electronic devices may belong to the same user account, thus establishing a "trust relationship." For instance, the second and first electronic devices may be under the same Huawei account. Exemplarily, the first and second electronic devices may belong to the same user account and be of the same device type (e.g., both are mobile phones or tablets). Exemplarily, the second and first electronic devices may belong to the same user account and be within the same trust ring or the same trust list. Based on these trust relationships, information about the second electronic device can be recorded in the trusted device list. And / or, the first electronic device may display the options of the second electronic device on a second user interface.

[0164] Step 802: The user interacts with the options on the second electronic device on the first user interface, such as by clicking or touching the option, but not limited to this.

[0165] Step 803: In response to the user's action on the options of the second electronic device, the first electronic device sends a first message to the second electronic device.

[0166] In some examples, the first electronic device can send the first message to the second electronic device via any wired or wireless communication method. This application does not specifically limit the specific implementation method. For example, the first electronic device and the second electronic device maintain a near-field communication connection, and there is an underlying communication channel between them for transmitting control signaling. The first electronic device can send the first message to the second electronic device through this underlying communication channel. That is, a point-to-point communication method can be used to send and receive the first message.

[0167] In some examples, the first message can trigger the second electronic device to display a second user interface. This application does not specifically limit the specific content of the first message. For example, the first message may include the address of the first electronic device, the address of the second electronic device (for addressing), the identifier of the first electronic device, and the identifier of the service of the second electronic device that needs to be activated. For example, the service of the second electronic device that needs to be activated may be provided by a mobile phone clone, and therefore can also be understood or described as activating the mobile phone clone on the second electronic device, thereby enabling the display of the second user interface.

[0168] In step 804, in response to receiving the first message, the second electronic device displays a second user interface. Based on the first message, the second electronic device obtains information about the first electronic device and includes a first option related to the first electronic device in the second user interface; based on the service identifier, it is determined that the first electronic device and the second electronic device need to establish a data migration service. This second user interface is used to ask the user whether to establish a data transmission link, which is used to migrate data from the second electronic device to the first electronic device. For example, the second user interface can be the user interface 501 shown in Figure 5 above, and the first option can be the "Connect" option in user interface 501.

[0169] In some examples, the second user interface can appear as a floating window or a pop-up; that is, the second user interface can be displayed as a floating window, a pop-up, or a pop-up window. For example, if the second electronic device is currently displaying an interface (such as the main interface), upon receiving the first message, the second electronic device automatically pops up the second user interface in response to receiving the first message.

[0170] For example, the second electronic device has a phone clone installed. The ability of the second electronic device to display the second user interface can be granted by the phone clone. When the second electronic device receives the first message, even if the phone clone on the second electronic device is not opened, the second user interface, which exists in the form of a floating window, pop-up, or pop-up window, can be automatically popped up or displayed. In other words, the display of the second user interface does not depend on the user opening the phone clone, thereby simplifying the user's operation.

[0171] In some examples, the second user interface may also include a "Reject Connection" option. If the user refuses to establish the data transmission link, clicking the "Reject Connection" option can terminate the data transmission link establishment process. For example, in response to the user clicking the "Reject Connection" option, the second electronic device may also close or exit the second user interface.

[0172] For example, the "Reject Connection" option could be located in the upper right corner of the second user interface. If the user refuses to establish the data transmission link, they can click this option. The option, while closing the second user interface, instructs the second electronic device to terminate the data transmission link establishment process.

[0173] In some examples, the data transmission link can be a P2P link. Alternatively, it can be any existing or future high-speed data transmission link, such as a near link, NFC link, IR link, or ZigBee link. This application does not impose any special limitations on this. It should be understood that the data transmission link in the embodiments of this application can also be referred to as a data transmission channel, connection, or link, etc. The process of establishing the data transmission link is prior art and will not be elaborated here.

[0174] Step 805: The user interacts with the first option on the second user interface, such as by clicking or touching the first option, but not limited to this.

[0175] Step 806: In response to the user's action on the first option, the second electronic device establishes the data transmission link. For example, the second electronic device may initiate the data transmission link establishment process, and the data transmission link is successfully established after one or more information exchanges with the first electronic device.

[0176] According to the interaction method provided in this application embodiment, the first electronic device can display the options of the second electronic device on a first user interface. When a user determines that data needs to be migrated from the second electronic device to the first electronic device, the user can directly click the option corresponding to the second electronic device. In response to the user's click operation, the first electronic device can send a first message to the second electronic device. In response to receiving the first message, the second electronic device automatically displays a second user interface (e.g., a pop-up window), which asks the user whether they agree to establish a data transmission link between the first and second electronic devices. When the user clicks the first option on the second user interface, the data transmission link establishment process can be directly triggered to establish the data transmission link.

[0177] The interaction method provided in this application eliminates the need for "device discovery" between two devices by scanning a QR code (or manually entering an account password), enabling the creation of data transmission links more simply and quickly. This simplifies user operations and improves the user's device switching experience.

[0178] As shown in Figure 8, after the data transmission link is established (i.e., after step 806), the interaction method 800 provided in this embodiment of the application further includes:

[0179] Step 807: The second electronic device sends data list information to the first electronic device. For example, the data list information may include information about files that the second electronic device can transfer to the first electronic device, such as file type, name, file size, number of file items, etc., but is not limited to these.

[0180] In step 808, the first electronic device generates and displays a third user interface based on the data list information. This third user interface is used for the user to select the data to be migrated. For example, this third user interface may be the user interface 405 in Figure 4 above.

[0181] The first electronic device receives the data list information, including, for example, application information of contacts and file information, such as application and data file information. Based on this data list information, it generates and displays a third user interface, which presents the aforementioned information to the user for selection of data to be migrated.

[0182] Step 809: The user performs an operation on the first data on the third user interface. That is, the user selects the first data on the third user interface as the data to be migrated. This operation may include, for example, clicking, selecting, etc., but is not limited to these.

[0183] Step 810: In response to the user's operation on the first data that needs to be migrated, the first electronic device sends a request message for the first data to the second electronic device.

[0184] In some examples, the data request message may include an identifier of the data selected by the user.

[0185] Step 811: In response to the request message, the second electronic device sends the first data to the first electronic device through the previously established data transmission link.

[0186] To enhance the user experience of using new devices, the interaction method 800 provided in this application selects the data to be migrated from the old device (i.e., the second electronic device) on the new device (i.e., the first electronic device), which is beneficial to improving the user's device switching experience.

[0187] As shown in Figure 8, before the second electronic device sends the first data to the first electronic device through the data transmission link, that is, before step 811, the interaction method 800 provided in this application embodiment further includes:

[0188] In step 812, the first electronic device displays a fourth user interface, which instructs the user to input verification information from the second electronic device. For example, the fourth user interface can be the user interface 406 shown in Figure 4, and the verification information from the second electronic device can be its lock screen password. That is, the fourth user interface includes a password input field, and the verification information includes the password of the second electronic device entered by the user in the password input field. Furthermore, the verification information from the second electronic device can also be any other information capable of verifying the user's identity, such as fingerprint information, facial information, or iris information. For example, the verification information can include one or more of the password, fingerprint information, facial information, and iris information entered by the user on the second electronic device; this application does not impose any special limitations on this.

[0189] Step 813: The user inputs the verification information of the second electronic device into the first electronic device. For example, the verification information of the second electronic device can be input through a touch screen, fingerprint recognition module, or camera, but is not limited to these.

[0190] Step 814: In response to the verification information input by the user, the first electronic device sends the verification information to the second electronic device.

[0191] Step 815: The second electronic device verifies the user's identity based on the verification information. That is, it verifies whether the user is the legal owner of the second electronic device and verifies the legitimacy of the user's identity with the second electronic device.

[0192] In step 816, the second electronic device sends a first indication message to the first electronic device, indicating that the user's identity verification has passed (successfully). This means the verification result indicates that the user is the legitimate owner of the second electronic device, and therefore the subsequent data migration work can continue (i.e., proceeding to steps 810 and 811).

[0193] According to the interaction method 800 provided in this application embodiment, the second electronic device sends the first data to the first electronic device only after the user's identity verification is successful. This setting helps ensure data security and prevents data from being illegally obtained. Furthermore, to improve the user experience of the new device, this application verifies the user's identity on the new device (i.e., the first electronic device), which improves the user's switching experience. In some examples, the first indication information indicates that the user's identity verification is successful, which can serve as the trigger condition for step 810. That is, when the first electronic device determines that the user's identity verification is successful based on the first indication information, in response to this determination, the first electronic device sends a request message for the first data to the second electronic device.

[0194] In some examples, the first indication information can be used to indicate that the user's identity verification failed (failed). At this time, the subsequent steps 810 and 811 are not executed, and the corresponding reminder information can be displayed on the screen of the first electronic device to remind the user that the identity verification failed and that the user can re-enter the verification information.

[0195] In some examples, the order of steps 808 and 812 can be reversed. In other words, the embodiments of this application do not impose any special limitation on the order of steps 808 and 812. For example, referring to Figures 4 and 8, the first electronic device can execute step 808 first, allowing the user to select data, and then verify the user's identity. At this time, in response to the user's completion of the operation on the first data to be migrated, the first electronic device can display the fourth user interface. Alternatively, the first electronic device can also execute step 812 first, allowing the user to verify their identity, and only execute step 808, allowing the data selection operation, after the identity verification is successful.

[0196] In some examples, after the data transmission link is established (i.e., after step 806), the interaction method 800 provided in this application embodiment further includes:

[0197] The second electronic device displays a fifth user interface, which instructs the user to perform data migration operations on the first electronic device. For example, the fifth user interface can be user interface 503 as shown in Figure 5. By setting the second electronic device to display the fifth user interface, the user can be reminded to switch to the first electronic device (i.e., the new device) in a timely manner to perform subsequent data migration work, thus improving the user's device switching experience.

[0198] In some examples, before the first electronic device displays the first user interface, the first electronic device establishes a trusted connection with the second electronic device and saves information of the second electronic device; or, the first electronic device and the second electronic device are devices under the same user account.

[0199] Here, the first electronic device establishes a trusted connection with the second electronic device. This could be because the first electronic device and the second electronic device have conducted relevant business and established a "trust relationship" in that business scenario. Therefore, the information of the second electronic device can be saved, and the second electronic device can be displayed on the first user interface as a candidate device that may migrate data to the first electronic device.

[0200] For example, establishing a trusted connection between the first electronic device and the second electronic device may include, but is not limited to, data migration, quick device switching, or multi-screen collaboration between the two devices. For instance, the second electronic device may be a device that has previously performed data migration (e.g., phone cloning) with the first electronic device; or, the second electronic device may be a device that has previously performed quick device switching with the first electronic device; or, the second electronic device may also be a device that has previously performed multi-screen collaboration with the first electronic device.

[0201] In some examples, a near-field communication (NFC) connection is established between the first electronic device and the second electronic device before the first electronic device displays the first user interface. For instance, establishing this NFC connection may include the first and second electronic devices being near each other, such as being close to each other and both the WLAN module and / or Bluetooth module being enabled.

[0202] It should be understood that the above description is merely to help those skilled in the art better understand the embodiments of this application, and is not intended to limit the scope of the embodiments of this application. Based on the examples given above, those skilled in the art can obviously make various equivalent modifications or changes. For example, some steps in the above method embodiments may be unnecessary, or new steps may be added. Alternatively, any combination of two or more of the above embodiments may be used. Such modifications, changes, or combinations also fall within the scope of the embodiments of this application.

[0203] It should also be understood that the methods, situations, categories, and classifications of embodiments in this application are for the convenience of description only and should not constitute a special limitation. Various methods, categories, situations, and features in embodiments can be combined without contradiction.

[0204] It should also be understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0205] It should also be understood that the above description of the embodiments of this application focuses on highlighting the differences between the various embodiments. Any similarities or differences not mentioned can be referred to each other. For the sake of brevity, they will not be repeated here.

[0206] The methods of the embodiments of this application have been described in detail above with reference to Figures 1 to 8. The electronic devices of the embodiments of this application will now be described in detail with reference to Figures 9 and 10.

[0207] This application embodiment can divide the various devices (including the first electronic device and the second electronic device mentioned above) into functional modules according to the above method embodiment. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0208] It should be noted that the relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0209] The communication device (including the first electronic device and the second electronic device described above) provided in this application embodiment is used to execute the interaction method provided in the above method embodiment, and therefore can achieve the same effect as the above implementation method. When using integrated units, the electronic device (including the first electronic device and the second electronic device described above) may include a processing module, a storage module, and a communication module. The processing module can be used to control and manage the actions of the electronic device or server. For example, it can be used to support the electronic device in executing the steps executed by the processing unit. The storage module can be used to support the storage of program code and data, etc. The communication module can be used to support communication between the electronic device and other devices.

[0210] The processing module can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination of functions that implement computing capabilities, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc. The storage module can be a memory. The communication module can specifically be a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip, or other devices that interact with other electronic devices.

[0211] For example, FIG9 shows a schematic diagram of the hardware structure of a communication device 900 provided in this application. The communication device 900 can be the aforementioned electronic device (e.g., the first electronic device or the second electronic device described above). Alternatively, the aforementioned electronic device (e.g., the first electronic device or the second electronic device described above) can include the communication device 900 shown in FIG9. As shown in FIG9, the communication device 900 may include a processor 910, an external memory interface 920, an internal memory 921, a universal serial bus (USB) interface 930, a charging management module 940, a power management module 941, a battery 942, an antenna 1, an antenna 2, a mobile communication module 950, a wireless communication module 960, a display screen 970, a touch sensor 980, etc.

[0212] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the communication device 900. In other embodiments of this application, the communication device 900 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0213] For example, the communication device 900 may also include an audio module, a speaker, a receiver, a microphone, a headphone jack, a sensor module, etc.

[0214] Processor 910 may include one or more processing units. For example, processor 910 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent components or integrated into one or more processors. In some embodiments, communication device 900 may also include one or more processors 910. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0215] In some embodiments, the processor 910 may include one or more interfaces. These interfaces may include an inter-integrated circuit (I2C) interface, an integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM card interface, and / or a USB interface, etc. The USB interface 930 is a USB standard-compliant interface, specifically a Mini USB interface, a Micro USB interface, a USB Type-C interface, etc. The USB interface 930 can be used to connect a charger to charge the communication device 900, and can also be used for data transfer between the communication device 900 and peripheral devices.

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

[0217] The wireless communication function of the communication device 900 can be implemented through antenna 1, antenna 2, mobile communication module 960, wireless communication module 950, modem processor, and baseband processor.

[0218] The wireless communication module 960 can provide solutions for wireless communication applications on the communication device 900, including Wi-Fi, Bluetooth (BT), and wireless data transmission modules (e.g., 433MHz, 868MHz, 919MHz). The wireless communication module 950 can be one or more devices integrating at least one communication processing module. The wireless communication module 960 receives electromagnetic waves via antenna 2, filters and frequency-modulates the electromagnetic wave signals, and sends the processed signal to processor 910. The wireless communication module 960 can also receive signals to be transmitted from processor 910, frequency-modulate and amplify them, and then convert them into electromagnetic waves for radiation via antenna 2. For example, the wireless communication module 960 can be used in scenarios involving near-field device transmission and near-field shared Wi-Fi information transmission.

[0219] The mobile communication module 950 can provide solutions for wireless communication, including 2G / 4G / 4G / 4G, applied to the communication device 900. The mobile communication module 950 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 950 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 950 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 950 may be housed in the processor 910. In some embodiments, at least some functional modules of the mobile communication module 950 and at least some modules of the processor 910 may be housed in the same device. For example, the mobile communication module 950 can be used in scenarios involving far-field shared Wi-Fi information transmission.

[0220] The external memory interface 920 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the communication device 900. The external memory card communicates with the processor 910 through the external memory interface 920 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0221] Internal memory 921 can be used to store one or more computer programs, which include instructions. Processor 910 can execute the instructions stored in internal memory 921, thereby causing communication device 900 to perform the interactive methods, various applications, and data processing provided in some embodiments of this application. Internal memory 921 may include a code storage area and a data storage area. The code storage area may store the operating system. The data storage area may store data created during the use of communication device 900. In addition, internal memory 921 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage components, flash memory components, universal flash storage (UFS), etc. In some embodiments, processor 910 can execute instructions stored in internal memory 921 and / or instructions stored in memory disposed in processor 910 to cause communication device 900 to perform the interactive methods provided in embodiments of this application.

[0222] The communication device 900 implements display functions through a GPU, a display screen 970, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 970 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 910 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0223] The display screen 970 is used to display images, videos, etc. The display screen 970 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a minimized display, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the communication device 900 may include one or more display screens 970.

[0224] Touch sensor 980, also known as a "touch panel," can be located on display screen 970. The touch sensor 980 and display screen 970 together form a touchscreen, also known as a "touch screen." Touch sensor 980 detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 970. In some embodiments, touch sensor 980 may also be located on the surface of communication device 900, in a different position than display screen 980.

[0225] In this embodiment, the display screen 970 is used to display the user interface of a system or application, such as the user interface of applications like mobile phone cloning or HyperTerminal. The touch sensor 980 enables interaction with the user, such as receiving touch commands to operate or control options or controls on the user interface.

[0226] It should be understood that the specific process of the communication device 900 performing the above-mentioned corresponding steps is described in the previous text in conjunction with the relevant descriptions of the execution steps of each electronic device (e.g., the first electronic device or the second electronic device). For the sake of brevity, it will not be repeated here.

[0227] Figure 10 shows a schematic block diagram of another example of a communication device 1000 provided in an embodiment of this application. This communication device 1000 can correspond to the electronic devices (first electronic devices or second electronic devices) described in the various embodiments of method 800 described above. It can also be a chip or component applied to an electronic device. Furthermore, each module or unit in the communication device 1000 is used to execute the various actions or processing procedures performed by the electronic devices described in the various embodiments of method 800. As shown in Figure 10, the communication device 1000 may include a processing unit 1010 and a communication unit 1020. Optionally, the communication device 1000 may also include a storage unit 1030.

[0228] It should be understood that the specific process of each unit in the communication device 1000 performing the above-mentioned corresponding steps is described in the previous text in conjunction with the relevant description of the electronic device (first electronic device or second electronic device) performing the steps in the various embodiments of Figures 1 to 8. For the sake of brevity, it will not be repeated here.

[0229] Optionally, the communication unit 1020 may include a receiving unit (module) and a transmitting unit (module) for performing the steps of receiving and transmitting information by the electronic device in the foregoing method embodiments. The storage unit 1030 is used to store instructions executed by the processing unit 1010 and the communication unit 1020. The processing unit 1010, the communication unit 1020, and the storage unit 1030 are communicatively connected. The storage unit 1030 stores instructions, the processing unit 1010 executes the instructions stored in the storage unit, and the communication unit 1020 performs specific signal transmission and reception under the drive of the processing unit 1010.

[0230] It should be understood that the communication unit 1020 may be a transceiver, an input / output interface, or an interface circuit, for example, it may be implemented by the wireless communication module 960 in the embodiment shown in FIG9. The storage unit may be a memory, for example, it may be implemented by the external memory interface 920 and the internal memory 921 in the embodiment shown in FIG9. The processing unit 1010 may be the processor 910 in the embodiment shown in FIG9, or it may be implemented by the processor 910, the external memory interface 920, and the internal memory 921.

[0231] It should also be understood that the communication device 1000 shown in FIG10 can be an electronic device (e.g., a first electronic device or a second electronic device), or the electronic device (a first electronic device or a second electronic device) can include the communication device 1000 shown in FIG10.

[0232] This application also provides a chip system, as shown in FIG11, which includes at least one processor 1110 and at least one interface circuit 1120. The processor 1110 and the interface circuit 1120 are interconnected via lines. For example, the interface circuit 1120 can be used to receive signals from other devices (e.g., a server). As another example, the interface circuit 1120 can be used to send signals to other devices (e.g., the processor 1110). Exemplarily, the interface circuit 1120 can read instructions stored in memory and send those instructions to the processor 1110. When the instructions are executed by the processor 1110, the chip system can perform the various steps performed by the electronic device (first electronic device or second electronic device) in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in this application.

[0233] It should also be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, while others are implemented in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, and its function can be called and executed by a processing element within the device. Here, the processing element can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0234] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the methods described above, such as one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. Furthermore, these units can be integrated together to implement a system-on-a-chip (SOC).

[0235] This application also provides an apparatus that performs the functions of the electronic device (first electronic device or second electronic device) in any of the methods described above. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above function. For example, a display module or unit, a determination module or unit, a calculation module or unit, a sending module or unit, a receiving module or unit, etc.

[0236] This application also provides a computer-readable storage medium for storing computer program code, the computer program including instructions for executing any of the interactive methods provided in the embodiments of this application. The readable medium may be a read-only memory (ROM) or a random access memory (RAM), and this application does not impose any limitations on this.

[0237] This application also provides a computer program product including instructions that, when executed, cause an electronic device (a first electronic device or a second electronic device) to perform a corresponding operation in the above-described interaction method.

[0238] This application also provides a communication system, which includes: a first electronic device and a second electronic device as described in the above method example.

[0239] This application also provides an electronic device, which includes the above-described communication device 900 or communication device 1000.

[0240] This application also provides a chip located in a communication device, the chip including a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, pins, or circuits. The processing unit can execute computer instructions to cause the communication device to perform the interaction method provided in the above-described embodiments of this application.

[0241] Optionally, the computer instructions are stored in a storage unit.

[0242] Optionally, the storage unit can be an internal storage unit within the chip, such as a register or cache. Alternatively, it can be an external storage unit located within the terminal, such as a ROM or other types of static storage devices capable of storing static information and instructions, such as random access RAM. The processor mentioned above can be a CPU, microprocessor, ASIC, or one or more integrated circuits used to control the execution of a program for transmitting the aforementioned feedback information. The processing unit and the storage unit can be decoupled and located on different physical devices, connected via wired or wireless means to implement their respective functions, thereby supporting the system chip in implementing the various functions described in the above embodiments. Alternatively, the processing unit and the memory can also be coupled to the same device.

[0243] In this embodiment, the electronic device (first electronic device or second electronic device), computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0244] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be RAM, which is used as an external cache. RAM has various different types, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0245] In this application, various objects such as messages / information / devices / network elements / systems / apparatus / actions / operations / processes / concepts may be named. It is understood that these specific names do not constitute a limitation on the relevant objects. The names may be changed depending on the scenario, context, or usage habits. The understanding of the technical meaning of the technical terms in this application should be mainly determined from their functions and technical effects embodied / performed in the technical solution.

[0246] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

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

[0248] The methods in the embodiments of this application can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server integrating one or more available media.

[0249] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

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

[0252] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0253] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical disks.

[0254] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An interaction method, characterized in that, An interaction method is applied to a communication system including a first electronic device and a second electronic device. The interaction method includes: the first electronic device acquiring trusted device information, the trusted device information including the second electronic device; based on the trusted device information, the first electronic device displaying a first user interface of a first application, the first user interface including options of the second electronic device, wherein the first application includes a data migration function, the data migration function being used to migrate data from the second electronic device to the first electronic device or the data migration function being used to migrate data from the first electronic device to the second electronic device; in response to a user's operation on the options of the second electronic device, the first electronic device sending a first message to the second electronic device, wherein the first message includes the address of the first electronic device, the address of the second electronic device, and the address of the first electronic device. The first electronic device identifies itself and the second electronic device identifies itself; in response to receiving the first message, the second electronic device determines, based on the service identifier, that the first electronic device and the second electronic device need to establish a data migration service and displays a second user interface, which asks the user whether to establish a data transmission link, and includes a first option; in response to the user's operation on the first option, the second electronic device establishes the data transmission link with the first electronic device; the second electronic device and the first electronic device perform data migration through the data transmission link; before the first electronic device displays the first user interface, the first electronic device establishes a trusted connection with the second electronic device and saves the information of the second electronic device; or, the first electronic device and the second electronic device are devices under the same user account.

2. The interaction method according to claim 1, characterized in that, The method further includes: the first electronic device displaying a third user interface for a user to select data to be migrated; in response to the user's operation on the first data to be migrated, the first electronic device sending a request message for the first data to the second electronic device; and in response to the request message, the second electronic device sending the first data to the first electronic device via the data transmission link.

3. The interaction method according to claim 2, characterized in that, Before the second electronic device sends the first data to the first electronic device via the data transmission link, the method further includes: the first electronic device displaying a fourth user interface, the fourth user interface being used to instruct a user to input verification information of the second electronic device; in response to the verification information input by the user, the first electronic device sending the verification information to the second electronic device; the second electronic device verifying the user's identity based on the verification information; and the second electronic device sending a first indication information to the first electronic device, the first indication information being used to indicate that the user's identity verification has passed.

4. The interaction method according to claim 3, characterized in that, The verification information includes any one or more of the following: password, fingerprint information, facial information, and iris information.

5. The interaction method according to any one of claims 1-4, characterized in that, After the data transmission link is established, the method further includes: the second electronic device displays a fifth user interface, which is used to instruct the user to perform a data migration operation on the first electronic device.

6. The interaction method according to any one of claims 2-4, characterized in that, Before the first electronic device displays the third user interface, the method further includes: the first electronic device receiving data list information from the second electronic device, the data list information being used to generate the third user interface.

7. The interaction method according to any one of claims 2-4, characterized in that, The third user interface includes application information of the second electronic device, and / or file information in the second electronic device.

8. The interaction method according to any one of claims 1-4, characterized in that, Before the first electronic device displays the first user interface, the first electronic device establishes a near-field communication connection with the second electronic device.

9. An interaction method, characterized in that, The method includes: acquiring trusted device information, the trusted device information including a second electronic device; based on the trusted device information, a first electronic device displays a first user interface of a first application, the first user interface including options of the second electronic device; wherein the first application includes a data migration function, the data migration function being used to migrate data from the second electronic device to the first electronic device or the data migration function being used to migrate data from the first electronic device to the second electronic device; in response to a user's operation on the options of the second electronic device, the first electronic device sends a first message to the second electronic device, wherein the first message includes the address of the first electronic device, the address of the second electronic device, the identifier of the first electronic device, and the service identifier of the second electronic device; wherein the service identifier is used to determine that the first electronic device and the second electronic device need to establish a data migration service and trigger the second electronic device to display a second user interface, the second user interface being used to ask the user whether to establish a data transmission link, the second user interface including a first option, and when the second electronic device detects the user's operation on the first option, the second electronic device establishes the data transmission link with the first electronic device; before the first electronic device displays the first user interface, the first electronic device establishes a trusted connection with the second electronic device and saves the information of the second electronic device; or, the first electronic device and the second electronic device are devices under the same user account.

10. The interaction method according to claim 9, characterized in that, After the data transmission link is established, the method further includes: the first electronic device displaying a third user interface for the user to select data to be migrated; in response to the user's operation on the first data to be migrated, the first electronic device sending a request message for the first data to the second electronic device; and the first electronic device receiving the first data from the second electronic device through the data transmission link.

11. The interaction method according to claim 10, characterized in that, Before the first electronic device receives the first data from the second electronic device via the data transmission link, the method further includes: the first electronic device displaying a fourth user interface, the fourth user interface being used to instruct a user to input verification information from the second electronic device; in response to the verification information input by the user, the first electronic device sending the verification information to the second electronic device, the verification information being used by the second electronic device to verify the user's identity; and the first electronic device receiving first indication information from the second electronic device, the first indication information being used to indicate that the user's identity verification has passed.

12. The interaction method according to claim 11, characterized in that, The verification information includes any one or more of the following: password, fingerprint information, facial information, and iris information.

13. The interaction method according to any one of claims 10-12, characterized in that, Before the first electronic device displays the third user interface, the method further includes: the first electronic device receiving data list information from the second electronic device, the data list information being used to generate the third user interface.

14. The interaction method according to any one of claims 9-12, characterized in that, Before the first electronic device displays the first user interface, the first electronic device establishes a near-field communication connection with the second electronic device.

15. The interaction method according to any one of claims 10-12, characterized in that, The third user interface includes application information of the second electronic device, and / or file information in the second electronic device.

16. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory being used to store instructions, and the processor being used to read the instructions to execute the method as described in any one of claims 9-15.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 9-15.

18. A computer program product, characterized in that, The computer program product includes: instructions for performing the method as described in any one of claims 9-15.

19. A chip, characterized in that, Includes: a processor for retrieving and running a computer program from memory, causing a communication device on which the chip is mounted to perform: the method as described in any one of claims 9-15.

Images