Cross-device content transmission method, electronic device, communication system, storage medium and program product

Abstract

The embodiment of the invention provides a cross-device content transmission method, electronic equipment, a communication system, a storage medium and a program product, and relates to the technical field of terminals. The method comprises the steps that first equipment displays first content; in response to a first operation of a user, the first device displays a first service icon and an icon of a second device, and the first service icon is used for indicating a first service provided by the first device; after a second operation of the user is received, the first device displays a picture corresponding to the first service; after a third operation of the user is received, the first device sends the first content to the second device; after fourth operation of the user is received, the first equipment displays a second service icon, and the second service icon is used for indicating the service provided by the second equipment; and when the user selects the second service icon, transferring the first content to the second service of the second equipment. In this way, the efficiency of transmitting the first content to the second device by the first device or transferring the first content to the service of the second device is high.

Description

Cross-device content transfer methods, electronic devices, communication systems, storage media and application products

[0001] This application relates to the field of terminal technology, and in particular to a cross-device content transmission method, electronic device, communication system, storage medium and program product.

[0002] With the increasing variety and number of terminal devices, users have a higher demand for cross-device content transfer. Currently, cross-device content transfer can be achieved through cloud applications and other methods.

[0003] For example, a user can log in to a cloud application account on a first device and upload target content to the cloud application; then, the user can log in to the same cloud application account on a second device and download the target content from the cloud application. In this way, the second device can access the target content from the first device. This target content can be, for example, a document, image, compressed file, or video.

[0004] However, this method of cross-device content transfer is cumbersome, resulting in a poor user experience.

[0005]

[0006] This application provides a method for cross-device content transmission, an electronic device, a communication system, a storage medium, and a program product, applicable to the field of terminal technology. This method can be applied to communication systems including a first device and a second device.

[0007] In response to a user's operation on the first content displayed on the first device, the first device can display the icon of the second device, the icon of the first service pushed by the first device, and the corresponding service icon of the second device. After receiving user input on different icons, the first device can send the second content to the second device, and the first device can also transfer the first content to the service of the second device. This simplifies cross-device content transfer and improves the user experience.

[0008] In a first aspect, embodiments of this application propose a cross-device content transmission method. This method is applied to a communication system including a first device and a second device. The method includes: the first device displaying a first interface, the first interface including first content, the first content including one or more of text, images, videos, audio, files, web pages, or links; in response to a user's first operation on the first content, the first device displaying a second interface, the second interface including a first area and a second area, the first area including a third interface corresponding to the first interface, the second area including a first service icon and an icon of the second device, the first service icon indicating a first service provided by the first device, and the icon of the second device indicating the second device; upon receiving a second operation from the user on the first service icon, the first device displaying a fourth interface, the fourth interface including a screen corresponding to the first service; upon receiving a third operation from the user on the icon of the second device, the first device sending the first content to the second device; upon receiving a fourth operation from the user on the icon of the second device, the first device displaying a second service icon, the second service icon indicating a service provided by the second device; and when the user selects the second service icon, the first device transferring the first content to the second service of the second device.

[0009] In this context, the first device can be understood as the sending end in the following text, and the second device can be understood as the receiving end in the following text. The first device and the second device establish a trust relationship (e.g., belong to the same trust ring). The first content can be understood as the first content or the second content in the following text, such as document 1, text information 801, or image 2001 in the following text. Text, web pages, or links can also be referred to as text information, etc.

[0010] In one possible implementation, the first interface is, for example, interface 8a hereinafter, and the first content is, for example, text 801. The first operation can be an input operation 5 on the text 801 (e.g., long-pressing the text 801) and dragging the icon 802 generated based on the input operation 5 to the two edges of the phone (without releasing the button). The second interface can be interface 8c.

[0011] The first area can be the area corresponding to image 803, and the third interface is the interface displayed in image 803. The second area can be area 804. The first service icon can be any one of the service icon lists 3. The icon for the second device can be, for example, icon 805 or icon 806.

[0012] The second operation could be, for example, continuing to drag icon 802 to the first service icon and releasing it. The third operation could be, for example, continuing to drag icon 802 to the icon of the second device and releasing it. The fourth operation could be, for example, continuing to drag icon 802 to the icon of the second device (e.g., icon 806) without releasing it. The second service icon could be any one of the service icon lists 4 in interface 8d, or it could be icon 1002 in interface 10a.

[0013] In another possible implementation, the first interface is, for example, interface 26a hereinafter, and the first content is, for example, text 2601. The first operation could be the user circling the text information 2601 "Art Exhibition..." with their knuckles. The second interface could be interface 26b.

[0014] The description of the second interface is similar to that of one possible implementation described above. The difference lies in that the second operation could be the user dragging text information from the selected area 2605 to the first service icon and releasing it, or the user clicking the first service icon, etc. The third operation could be the user dragging text information from the selected area 2605 to the icon of the second device and releasing it, or the user clicking the icon of the second device. The fourth operation could be the user dragging text information from the selected area 2605 to the icon of the second device without releasing it, or the user clicking button 818.

[0015] Optionally, the second interface further includes a first button; the method further includes: upon receiving an eleventh operation on the first button, the first device displays a second service icon. The first button is, for example, button 818 in interface 8c. The eleventh operation can be dragging icon 802 to the position of button 818 and holding it there. Alternatively, when the second interface is interface 26b, the eleventh operation can also be clicking button 818, or dragging text information from the selected area 2605 to the position of button 818 and holding it there.

[0016] The cross-device content transfer method of this application allows the first device to display an interface including a first service icon and a second device icon when the first device displays first content, in response to a user's action of dragging the first content to the side edges of the screen or selecting the first content with a knuckle. Thus, after the first device receives a second operation from the user on the first service icon, it can transfer the first content to the first service (a service provided by the first device) corresponding to the first service icon; after the first device receives a third operation from the user selecting the second device's icon, it can transfer the first content to the second device. Furthermore, after the first device receives a fourth operation from the user on the second device's icon, it can display the second service icon corresponding to the second device, so that in response to the user selecting the second service icon, the first device can transfer the first content to the service of the second device.

[0017] Therefore, based on the user's selection of different icons, the first device can transmit the first content to the second device, and can also easily transfer the first content to the services of the first device or the second device. The operation is simple and enables efficient cross-device transmission of various types of content.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, after receiving the user's third operation on the icon of the second device, the method further includes: the first device displaying a first prompt bar on the first interface, the first prompt bar being used to indicate the transmission progress of the first content; after the first content is transmitted, the first device switching the first prompt bar to a second prompt bar, the second prompt bar being used to indicate that the first content has been transmitted.

[0019] The first content can be document 1 as described below, the first interface can be interface 2a, and the second interface can be interface 2b. The icon of the second device can be icon 206. The first prompt bar can be prompt bar 301 in interface 3a, and the second prompt bar can be prompt bar 304 in interface 3b.

[0020] In this way, the first device can display the cross-device transmission progress of the first content to the user.

[0021] Optionally, when the first device displays the first prompt bar and receives user input (e.g., a click) on the first prompt bar, the first device switches the first prompt bar to card 1, card 1 is used to indicate the transmission progress of the first content and to instruct the second device; and / or, when the first device displays the second prompt bar and receives user input (e.g., a click) on the second prompt bar, the first device switches the second prompt bar to card 2, card 2 is used to indicate that the transmission of the first content is complete and to instruct the second device.

[0022] Among them, card 1 can be card 306 in interface 3c, and card 2 can be card 309 in interface 3d.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: after the second device begins receiving the first content, the second device displays a third prompt bar, which is used to indicate the transmission progress of the first content; after the second device successfully receives the first content, the second device switches the third prompt bar to a fourth prompt bar, which is used to indicate that the transmission of the first content is complete.

[0024] The second device can be understood as a tablet. The third prompt bar can be prompt bar 401 in interface 4a; the fourth prompt bar can be prompt bar 404 in interface 4b.

[0025] In this way, the second device can display the progress of receiving the first content.

[0026] Optionally, the method further includes: when the second device displays a third prompt bar and receives input from the user on the third prompt bar, the second device switches the third prompt bar to card 3, card 3 is used to indicate the transmission progress of the first content and to indicate the first device; and / or, when the second device displays a fourth prompt bar and receives input from the user on the fourth prompt bar, the second device switches the fourth prompt bar to card 4, card 4 is used to indicate that the transmission of the first content is complete and to indicate the first device.

[0027] Card 3 can be card 409 in Figure 4. Card 4 can be card 406 in interface 4c.

[0028] In conjunction with the first aspect, in some implementations of the first aspect, the first interface also includes second content, which may be the same as or different from the first content;

[0029] The method further includes: in response to a user's fifth operation on the second content, the first device displays a fifth interface, the fifth interface including a third area and a fourth area, the third area including the third interface, the fourth area including an icon of the third device, the icon of the third device being used to indicate the third device; upon receiving a sixth operation from the user on the icon of the third device, the first device displays a first prompt message, the first prompt message being used to indicate that cross-device transmission of the second content is not supported.

[0030] The second content could be, for example, text 801 in interface 8a. The fifth operation is similar to the first operation, and the fifth interface is similar to the second interface, for example, interface 8c. The icon for the third device could be, for example, icon 806 or icon 805. The sixth operation could be, for example, dragging icon 802 to the icon for the third device and releasing it. The first prompt message can be displayed in various ways, such as a pop-up window, card, capsule, notification, etc.

[0031] This allows the user to be notified if the transfer to the second device across devices has failed.

[0032] In conjunction with the first aspect, in some implementations of the first aspect, the second service icon is used to indicate the second service of the second device; when the user selects the second service icon, the first device transfers the first content to the second service of the second device, including: when the user selects the second service icon, the first device sends the first content to the second device so that the second device transfers the first content to the second service, and the first device displays a first card on the first interface, the first card being used to indicate the cross-device service preparation process; the first device switches the first card to a second card, the second card being used to indicate that the cross-device service is ready, and indicating to continue the operation on the second device.

[0033] The first content is document 1, the first interface is interface 2a, the second interface is interface 2c, and the icon for the second device is icon 206. The fourth operation could be, for example, the user dragging icon 202 to icon 206 without releasing it. The second service icon could be, for example, icon 701, icon 702, or icon 703. The first card could be card 705 in interface 7c, and the second card could be card 708 in interface 7d.

[0034] This allows you to notify users of the preparation progress of cross-device services.

[0035] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: after the second device receives the first content from the first device, the second device displays a sixth interface, the sixth interface including the screen corresponding to the second service.

[0036] For example, the second service icon can be icon 703 in interface 7b, and the screen corresponding to the second service can be the screen corresponding to social application 1. The sixth interface may include a pop-up window that displays the screen corresponding to social application 1.

[0037] In this way, the first piece of content is successfully transferred to the second service on the second device, and the user can directly open the first piece of content in the second service on the second device. This allows for a convenient transfer of the first piece of content to the services of the second device.

[0038] In conjunction with the first aspect, in some implementations of the first aspect, when a user selects the second service icon, the first device transfers the first content to the second service of the second device, including: when the user selects the second service icon, the first device sends the first content to the second device so that the second device transfers the first content to the second service, and the first device displays a third card on the first interface, the third card being used to indicate the cross-device service preparation process; the first device switches the third card to a fourth card, the fourth card being used to indicate that the cross-device service is ready, and to indicate to continue the operation on the second device.

[0039] The first interface is interface 8a, the second interface is interface 8c, and the second service icon can be icon 1001 in interface 10a. The user selects the second service icon, for example, by dragging icon 802 to the position of icon 1001 and releasing it. Alternatively, in a scenario where the user selects the service icon by circling their knuckles to activate the "Anywhere Door" feature, the user can select the second service icon by clicking icon 1001 or dragging icon 802 to the position of icon 1001 and releasing it. The third card can be card 1101 in interface 11a, and the fourth card can be card 1104 in interface 11b. The phone can switch the third card to the fourth card if it confirms that the tablet supports the cross-device service.

[0040] This allows the system to display the cross-device service preparation progress to the user and instruct the user to continue operating on the receiving end once the cross-device service is ready.

[0041] Optionally, the method further includes: when the first device displays the third card and receives user input on the third card, the first device switches the third card to a prompt bar 5, the prompt bar 5 being used to indicate the cross-device service preparation process; and / or,

[0042] When the first device displays the fourth card and receives user input on the fourth card, the first device switches the fourth card to prompt bar 6, which is used to indicate that the cross-device service is ready.

[0043] Among them, prompt bar 5 can be prompt bar 1106 in 11c; prompt bar 6 can be prompt bar 1109 in 11d.

[0044] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: before the second device receives the first content from the first device, the second device displays a seventh interface; after the second device receives the first content from the first device, the second device displays an eighth interface, the eighth interface including a fifth area, a sixth area, and a first content icon, the fifth area including a ninth interface corresponding to the seventh interface, the sixth area including a third service icon, the third service icon being used to indicate a second service, and the first content icon being used to indicate the first content; when a seventh operation by the user on the third service icon is received, the second device displays a tenth interface, the tenth interface including the screen corresponding to the second service.

[0045] The seventh interface can be interface 13a; the eighth interface can be the interface shown in Figure 17. The fifth area can be the area corresponding to image 1701, and the ninth interface can be the interface displayed by image 1701. The sixth area can be area 1702. The third service icon can be any one of the service icon list 5, such as icon 1711. The first content icon can be icon 1703. The seventh operation can be clicking icon 1711 or dragging icon 1703 to the position of icon 1711 and releasing it, etc. The tenth interface can be the interface shown in Figure 18. The screen corresponding to the second service can be the screen displayed in the floating window 1801.

[0046] In this way, users can select a second service on the second device, so that the first content can be directly transferred to the second service selected by the user.

[0047] In conjunction with the first aspect, in some implementations of the first aspect, before the second device displays the eighth interface, the method further includes: after the second device begins receiving first content from the first device, the second device displays a fifth card on the seventh interface, the fifth card being used to indicate the cross-device service preparation process; the second device switches the fifth card to a sixth card, the sixth card being used to indicate that the cross-device service is ready.

[0048] The fifth card can be card 1301 in interface 13b, and the sixth card can be card 1304 in interface 13c. The tablet can display the sixth card when it is determined that the AnyDoor can be successfully launched (or cross-device service is supported).

[0049] In this way, the second device can display the preparation progress of cross-device services to the user.

[0050] Optionally, the method further includes: when the second device displays the fifth card and receives input from the user on the fifth card, the second device switches the fifth card to a prompt bar 7, the prompt bar 7 being used to indicate that the cross-device service is ready; and / or, when the second device displays the sixth card and receives input from the user on the sixth card, the second device switches the sixth card to a prompt bar 8, the prompt bar 8 being used to indicate that the cross-device service is ready.

[0051] Among them, prompt bar 7 can be prompt bar 1306 in 13d; prompt bar 8 can be prompt bar 1309 in 13e.

[0052] In conjunction with the first aspect, in some implementations of the first aspect, when the second device receives the first content from the first device, the second device is in a locked screen state; the second device displays an eighth interface, including: the second device displays a first notification on the lock screen interface, the first notification being used to indicate that the cross-device service is ready; when the second device displays the first notification, the user's eighth operation is received, the second device unlocks, and the second device displays the eighth interface.

[0053] The first notification displayed on the lock screen can be interface 15b. The first notification can also be notification 1504. The eighth action can be the user's unlocking action, such as swiping up.

[0054] In this way, while the screen is locked, the user can confirm that the cross-device service is ready based on the first notification. This allows the second device to continue providing cross-device services based on the user's unlocking action.

[0055] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: after the second device receives the first content from the first device, the second device displays a seventh card, which is used to indicate a cross-device service interruption. The tablet can display the seventh card on a seventh interface.

[0056] The seventh card can be card 1401 in interface 14a. This allows the user to be prompted that the cross-device service has been interrupted and can be retried.

[0057] Optionally, the method further includes: when the second device displays the seventh card and receives user input on the seventh card, the second device switches the seventh card to a prompt bar 9, which is used to indicate an interruption of cross-device service. The prompt bar 9 can be, for example, the prompt bar 1404 in 14b.

[0058] In conjunction with the first aspect, in certain implementations of the first aspect, when a user selects the second service icon, the first device transfers the first content to the second service of the second device, including: when the user selects the second service icon, the first device sends the first content to the second device; the first device displays a first projection window, the first projection window including a first projection screen, the first projection screen including a seventh area, an eighth area, and a first content icon, the seventh area including a twelfth interface corresponding to the eleventh interface displayed before the second device receives the first content, the eighth area including a fourth service icon for indicating the second service, and the first content icon for indicating the first content; when the user's ninth operation on the fourth service icon is received, the first projection screen displayed in the first projection window switches to the screen corresponding to the second service.

[0059] The first device is a tablet, and the second device can be a mobile phone. The first interface can be interface 20a. The first content can be image 2001. The first operation can be a long press on image 2001 (without releasing the finger) and drag the generated icon 2002 to the edge of the tablet (without releasing the finger); or, the first operation can be a knuckle selection of image 2001. The second interface can be interface 20c. The icon for the second device can be icon 2006. The first service icon can be any one of the service icon lists 6.

[0060] When the first operation is to long press on image 2001 (without releasing it) and drag the generated icon 2002 to the edge of the tablet (without releasing it), the fourth operation can be to drag icon 2002 to icon 2006 without releasing it; when the first operation is to select image 2001 with a knuckle, the fourth operation can be to click button 2007.

[0061] The second service icon can be icon 2101 in interface 21a. Selecting the second service icon can be done by clicking icon 2101 or dragging icon 2002 to the position of icon 2101 and releasing. The first projection window can be projection window 2103 in interface 21b. The first projection screen can be projection screen 2106. The seventh area can be understood as the area corresponding to image 2113. The eleventh interface can be understood as interface 8a, and the twelfth interface can be understood as the interface displayed by image 2113. The first content icon can be icon 2115. The eighth area can be area 2114. The fourth service icon can be icon 2120. The ninth operation can be clicking icon 2120 or dragging icon 2115 to the position of icon 2120 and releasing. The screen corresponding to the second service can be projection screen 2106 in the interface shown in Figure 22, i.e., the chat interface of social application 1.

[0062] In this way, users can operate on the first device to transfer the first content to a second service on the second device. Users do not need to switch devices, making the transfer of content from the first device to the second device highly efficient.

[0063] In conjunction with the first aspect, in some implementations of the first aspect, before the first device displays the first projection window, the method further includes: when the user selects the second service icon, the first device displays an eighth card on the first interface, the eighth card being used to indicate the cross-device service preparation process; the first device switches the eighth card to a ninth card, the ninth card being used to indicate that the cross-device service is ready; the first device displays the first projection window, including: when the display duration of the ninth card exceeds a first preset duration, or when a tenth operation on the ninth card is received, the ninth card disappears, and the first device displays the first projection window.

[0064] The first interface can be interface 20a, the eighth card can be card 1301 in interface 13b, and the ninth card can be card 1304 in interface 13c. The ninth card can be displayed after receiving the first screen projection from the second device. The tenth operation can be clicking card 1304, etc. The first preset duration can be a duration of 8, such as 300ms.

[0065] This allows you to notify users of the preparation progress of cross-device services.

[0066] Optionally, the method further includes: when displaying the eighth card, receiving user input on the eighth card, the first device switches the eighth card to a prompt bar 10, the prompt bar 10 indicating that cross-device service preparation is underway; and / or, when displaying the ninth card, receiving user input on the ninth card, the first device switches the ninth card to a prompt bar 11, the prompt bar 11 indicating that cross-device service preparation is complete. Wherein, prompt bar 10 can be prompt bar 1306; prompt bar 11 can be prompt bar 1309.

[0067] In conjunction with the first aspect, in some implementations of the first aspect, the eighth area also includes an icon of the fourth device; the method further includes: when the user selects the icon of the fourth device, the first projection screen displayed in the first projection window switches to the eleventh interface, and the first device instructs the second device to send the first content to the third device.

[0068] The icon for the fourth device can be, for example, icon 2116 in area 2114 of interface 21b. The fourth device is a PC. Selecting the icon for the fourth device can be done by dragging icon 2115 to the position of icon 2116 and releasing it, or by clicking icon 2116. Switching the first projection screen to the eleventh interface can be understood as the projection screen 2106 closing any door, i.e., the projection screen 2106 displays interface 8a. The tablet instructs the phone to send image 2001 to the PC.

[0069] In this way, based on user operations, the second device can continue to transmit the received first content to other devices.

[0070] In conjunction with the first aspect, in certain implementations of the first aspect, when a user selects the second service icon, the first device transfers the first content to the second service of the second device, including: when the user selects the second service icon, the first device sends the first content to the second device; the first device displays a tenth card, which is used to indicate that the cross-device service is ready and to instruct to continue the operation on the second device, so that the second device transfers the first content to the second service based on the user's operation of selecting the fifth service icon, the fifth service icon being used to indicate the second service.

[0071] The tenth card can be card 2301 in the interface shown in Figure 23. The fifth service icon can be the icon of the local service pushed by the mobile phone in the "Any Door Opening" interface displayed on the mobile phone. At this time, the process of the first content flowing to the second service of the second device is similar to the first method in the second scheme. The first device can display the tenth card when the first content transmission is completed and it is determined that the first device cannot display the first projection window.

[0072] In this way, when the first device cannot display the projection window to the second device, the first content can be transferred to the second service of the second device based on the user's operation on the second device.

[0073] In conjunction with the first aspect, in some implementations of the first aspect, the second interface further includes a first icon for indicating the first content, the first operation being an operation of dragging the first icon to the edge of the screen of the first device without releasing it, and the fourth operation being an operation of dragging the first icon to the icon position of the second device without releasing it; or, the first operation being an operation of selecting the first content with a knuckle.

[0074] Specifically, when the first operation is dragging the first icon to the edge of the first device screen without releasing it, the first operation could be, for example, in interface 8a, the user long-presses text 801 and drags the generated icon 802 to either side of the screen edge (without releasing it). That is, the first icon can be icon 802. The fourth operation could be dragging icon 802 to icon 806 without releasing it. When the first operation is selecting the first content with a knuckle, the first operation could be, in interface 26a, the user selecting text 2601 with a knuckle.

[0075] In this way, users can activate any door in multiple ways to make the first device display device icons and service icons, thereby transferring the first content to the second device or transferring services to the second device.

[0076] Secondly, embodiments of this application provide a cross-device content transmission apparatus, which can be an electronic device, or a chip or chip system within an electronic device. The cross-device content transmission apparatus may include a processing unit and a display unit. When the cross-device content transmission is an electronic device, the processing unit may be a processor, which can be used to generate various interfaces; the display unit may be a screen (or display screen), which can be used to display the various interfaces. The cross-device content transmission apparatus may further include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit can execute the instructions stored in the storage unit to cause the electronic device to implement a cross-device content transmission method described in the first aspect or any possible implementation of the first aspect. When the cross-device content transmission apparatus is a chip or chip system within an electronic device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit to cause the electronic device to implement a cross-device content transmission method described in the first aspect or any possible implementation of the first aspect. The storage unit may be a storage unit within the chip (e.g., a register, cache, etc.), or a storage unit located outside the chip within the electronic device (e.g., read-only memory, random access memory, etc.).

[0077] For example, a display unit is used to display a first interface, etc.

[0078] Thirdly, embodiments of this application provide an electronic device including a processor and a memory, the memory for storing code instructions, and the processor for running the code instructions to perform the methods described in the first aspect or any possible implementation of the first aspect.

[0079] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0080] Fifthly, embodiments of this application provide a computer program product including a computer program, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0081] Sixthly, this application provides a communication system, which includes a first device and a second device. The first device is used to perform the steps performed by the first device in the first aspect or any possible implementation of the first aspect; the second device is used to perform the steps performed by the second device in the first aspect or any possible implementation of the first aspect.

[0082] It should be understood that the second to sixth aspects of this application correspond to the technical solutions of the first aspect of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here.

[0083] Figure 1 is a schematic diagram of a trust ring device;

[0084] Figure 2 is a schematic diagram of the mobile phone interface during the process of transferring documents from the mobile phone to the tablet according to an embodiment of this application;

[0085] Figure 3 is a schematic diagram of the interface showing prompts and cards on the mobile phone during the process of transferring documents from the mobile phone to the tablet according to an embodiment of this application;

[0086] Figure 4 is a schematic diagram of the tablet interface during the process of transferring documents from a mobile phone to a tablet according to an embodiment of this application;

[0087] Figure 5 is a schematic diagram of another prompt bar displayed on the mobile phone during the process of transferring documents from the mobile phone to the tablet according to an embodiment of this application;

[0088] Figure 6 is a schematic diagram of the PC interface during the process of transferring documents from a mobile phone to a PC according to an embodiment of this application;

[0089] Figure 7 is a schematic diagram of the mobile phone interface during the service transfer of documents from the mobile phone to the tablet according to the embodiment of this application;

[0090] Figure 8 is a schematic diagram of the mobile phone interface during the process of transferring text from a mobile phone to a tablet according to an embodiment of this application;

[0091] Figure 9 is a schematic diagram of a process of transferring second content from a mobile phone to a tablet according to an embodiment of this application;

[0092] Figure 10 is a schematic diagram of the mobile phone interface during another text transfer process from a mobile phone to a tablet, provided in an embodiment of this application.

[0093] Figure 11 is a schematic diagram of the interface showing prompts and cards on the mobile phone during another text transfer process from a mobile phone to a tablet, provided in an embodiment of this application.

[0094] Figure 12 is a schematic diagram of the interface for displaying notifications when the mobile phone screen is locked, provided in an embodiment of this application;

[0095] Figure 13 is a schematic diagram of the tablet interface during the text transfer process from a mobile phone to a tablet according to an embodiment of this application;

[0096] Figure 14 is a schematic diagram of the tablet interface during another text transfer process from a mobile phone to a tablet according to an embodiment of this application;

[0097] Figure 15 is a schematic diagram of the interface when the tablet is locked during the service transfer of text from a mobile phone to a tablet according to an embodiment of this application.

[0098] Figure 16 is a schematic diagram of the interface when the tablet is locked during another text transfer process from a mobile phone to a tablet according to an embodiment of this application.

[0099] Figure 17 is a schematic diagram of the tablet interface during another text transfer process from a mobile phone to a tablet according to an embodiment of this application;

[0100] Figure 18 is a schematic diagram of the tablet interface during another text transfer process from a mobile phone to a tablet according to an embodiment of this application;

[0101] Figure 19 is a schematic diagram of a process of transferring second content from a tablet to a mobile phone according to an embodiment of this application;

[0102] Figure 20 is a schematic diagram of the tablet interface during the service transfer process from a tablet to a mobile phone according to an embodiment of this application.

[0103] Figure 21 is a schematic diagram of the tablet interface during another service transfer process from tablet to mobile phone provided in an embodiment of this application;

[0104] Figure 22 is a schematic diagram of the tablet interface after an image is transferred from a tablet to a mobile phone according to an embodiment of this application;

[0105] Figure 23 is a schematic diagram of the tablet interface during another service transfer process from tablet to mobile phone provided in an embodiment of this application;

[0106] Figure 24 is a schematic diagram of the interface of mobile phone A during the service transfer document from mobile phone A to mobile phone B according to an embodiment of this application;

[0107] Figure 25 is a schematic diagram of an interface for displaying more device icons on a mobile phone A according to an embodiment of this application;

[0108] Figure 26 is a schematic diagram of the mobile phone interface during the process of activating the Any Door by selecting text with a knuckle according to an embodiment of this application;

[0109] Figure 27 is a schematic diagram of the mobile phone interface during the process of launching any door by selecting an image with a knuckle according to an embodiment of this application;

[0110] Figure 28 is a schematic block diagram of the hardware architecture of an electronic device provided in an embodiment of this application.

[0111] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0112] 1. Electronic equipment

[0113] The electronic devices in this application embodiment may include handheld devices with facial recognition function, vehicle-mounted devices, etc. For example, some electronic devices include: mobile phones, tablets, PDAs, laptops, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0114] By way of example and not limitation, in this embodiment, the electronic device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0115] Furthermore, in this embodiment of the application, the electronic device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0116] The electronic devices in the embodiments of this application may also be referred to as: terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0117] In this embodiment, the electronic device or various network devices include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software.

[0118] 2. Other terms

[0119] In the embodiments of this application, terms such as "first" and "second" are used to distinguish identical or similar items with substantially the same function and purpose. For example, "first chip" and "second chip" are used only to distinguish different chips and do not limit their order of execution. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.

[0120] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0121] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, a--c, bc, or abc, where a, b, and c can be single or multiple.

[0122] 3. Anywhere Door

[0123] A "door to any platform" can be understood as a function that enables the flexible transfer of target content between multiple services or devices. The target content can be text, documents, compressed files, videos, images, or audio, etc. A door to any platform can also be called intelligent service push, etc., but this application does not limit the name of the door to any platform.

[0124] Any Door allows users to drag target content such as text, images, videos, or files on the screen to either side edge of the screen by long-pressing, and quickly access various quick services or applications, as described below.

[0125] 4. Select by knuckles

[0126] Knuckle selection refers to a gesture operation where a user selects a portion of the interface by tapping the screen with the knuckle of their finger and drawing a circle on the screen. For example, a user can use knuckle selection to activate a portal.

[0127] 5. Trust ring (magic ring)

[0128] This refers to one or more terminal devices logged into the same account and located on the same local area network, which have established a trust relationship. When multiple terminal devices are logged into the same account and their Bluetooth and Wi-Fi switches are both on, if the devices are close to each other, they can interconnect through a device discovery process, forming a trust ring. Any terminal device in the trust ring can view all the terminal devices included in the ring. For example, each terminal device's trust ring interface can display all the terminal devices in that trust ring.

[0129] For example, as shown in Figure 1a, assume that laptop 110, mobile phone 120, and tablet 130 are logged into the same personal account, and both Bluetooth and WiFi switches are turned on. Thus, when the three devices are close to each other, for example, all on the same WiFi network, laptop 110, mobile phone 120, and tablet 130 can interconnect. Alternatively, it can be described as laptop 110, mobile phone 120, and tablet 130 establishing a trust relationship. For any device in the trust ring, the other devices in the trust ring can be referred to as that device's trust ring devices. For example, the trust ring devices for laptop 110 are mobile phone 120 and tablet 130; the trust ring devices for mobile phone 120 are laptop 110 and tablet 130, etc.

[0130] The trust ring interface of each device in the laptop 110, mobile phone 120, and tablet 130 can display the icons of the three devices. Taking the trust ring interface of mobile phone 120 as an example, the trust ring interface of mobile phone 120 can be shown as interface b in Figure 1.

[0131] The trust ring interface of mobile phone 120 may include: device ball 1201 of mobile phone 120 (the local device), device ball 1101 of laptop 110, and device ball 1301 of tablet 130. Device balls can also be referred to as icons, identifiers, controls, etc. Besides the local device, each terminal device's device ball can also display information such as the device's name or model. For example, device ball 1101 includes the model number P10 of laptop 110, and device ball 1301 includes the model number V70 of tablet 130.

[0132] Therefore, users can identify multiple terminal devices with whom trust relationships are established in the trust ring interface.

[0133] With the development of terminal technology, the types and numbers of terminal devices are increasing. In multi-device scenarios, users' demand for flexible switching between devices is also growing.

[0134] For example, in some application scenarios, users may need to transfer documents, images, or compressed files from one terminal device to another. Taking file 1 as an example (both the sender and receiver are terminal devices), cross-device content transfer can currently be performed in the following two ways.

[0135] In the first method, data is transmitted via Bluetooth.

[0136] For example, the sending and receiving ends establish a Bluetooth connection; the user finds file 1 in the file management application on the sending end, and in response to the user's action of sharing file 1 to the receiving end via Bluetooth, file 1 can be transferred to the receiving end via Bluetooth. The user can then view the file in the receiving end's file management application.

[0137] In the second method, transmission is carried out through cloud applications.

[0138] Users can first log in to their cloud application account on the sending end and upload file 1 to the cloud application; then, users can log in to the same cloud application account on the receiving end and download the uploaded file 1 from that cloud application.

[0139] However, the cross-device content transfer methods shown above are cumbersome to operate, resulting in a poor user experience.

[0140] For example, in the first method described above, file 1 could be a file received from a friend when the sending client is running a social application 1 in the foreground. However, the user cannot directly send file 1 to the receiving client through the sending client's chat interface. Instead, they need to locate the file in the sending client's file management application first, and then send file 1 to the receiving client.

[0141] For the second method described above, both the sending and receiving ends need to have the same cloud application installed. Furthermore, during file transfer, the user needs to log in to the same cloud application account on both the sending and receiving ends.

[0142] In view of this, this application provides a cross-device content transmission method applied at a sending end, wherein the sending end and the receiving end establish a trust relationship. In response to a user's input operation on the first content to be transmitted, such as dragging the first content to the side edges of the screen, the sending end can activate a portal and display the receiving end's device icon; furthermore, in response to the user dragging the first content to the receiving end's device icon position, the sending end can transmit the first content to the receiving end. The first content may be, for example, an image, document, compressed file, video, or audio.

[0143] In this method, users do not need to search for the first content in the file management application on the sending end, nor do they need to switch devices to log in to their cloud application accounts. The operation steps are simple, which helps to improve the efficiency of cross-device content transfer and enhance the user experience.

[0144] First, it should be noted that in the embodiments of this application, the interface may also be referred to as a screen or page, etc., and this application does not make a specific limitation thereto.

[0145] The following section will detail how the sending end sends the first content to the receiving end through an arbitrary gate, using the mobile phone 120 in Figure 1 as the sending end and the tablet 130 in Figure 1 as the receiving end, and document 1 as the first content. For simplicity, the mobile phone 120 will be referred to as the mobile phone and the tablet 130 as the tablet in the following text.

[0146] Figure 2 is a schematic diagram of an interface for transferring document 1 from a mobile phone to a tablet according to an embodiment of this application.

[0147] As shown in interface 2a in Figure 2, interface 2a can be understood as the chat interface of the mobile phone. Interface 2a includes the icon 201 of document 1. In response to the user's input operation 1 on icon 201, such as long-pressing icon 210 (without releasing the button), the mobile phone switches from interface 2a to interface 2b.

[0148] As shown in interface 2b, in response to input operation 1 (while the hand is still pressed), the phone can generate icon 202 around icon 201. Icon 202 can be understood as a thumbnail of document 1. Icon 202 can be the same as icon 201, or it can be a smaller or larger version of icon 201.

[0149] In response to the user dragging icon 202 to the edge of the screen (without releasing it), the phone can switch from interface 2b to interface 2c.

[0150] As shown in interface 2c, interface 2c includes image 203 and region 204. Region 204 can be understood as the area outside image 203 in interface 2c.

[0151] The content in image 203 is the same as that in the chat interface (interface 2a). The difference is that the content displayed in image 203 can undergo three-dimensional transformations such as tilting, creating a visual effect on the screen that makes the original interface (interface 2a) appear to push inward.

[0152] It is understandable that in response to the user dragging icon 202 to either side of the screen (without releasing it), the phone can activate a portal. That is, the phone's chat interface changes shape, as shown in image 203. Furthermore, along with this change in chat interface shape, area 204 appears on the phone's screen.

[0153] Zone 204 displays the device icon list 1 for the phone's trusted ring devices and the service icon list 1 for local services.

[0154] In this context, the mobile phone trust ring device refers to a device that has established a trust relationship with the mobile phone. Examples include tablets and PCs that have established a trust relationship with the mobile phone. In this case, the device icon list 1 may include: icon 206 for the tablet and icon 205 for the PC. Icon 206 can indicate the tablet 130 in Figure 1; icon 205 can indicate the laptop 110 in Figure 1.

[0155] In addition, in area 204, text information describing the device type can be displayed around each device icon. For example, "My PC" below icon 205 and "My Tablet" below icon 206. This helps users identify the device type corresponding to each device icon.

[0156] It should be understood that in the embodiments of this application, the text information used to describe the device type can also be replaced with other text information, such as device model or device name, etc., and this application does not make specific limitations in this regard.

[0157] It should also be understood that the device icons displayed in area 204 are used to indicate devices that have established a trust relationship with the mobile phone (the device itself). That is, the device indicated by the device icon is logged into the same personal account as the mobile phone. Therefore, the device indicated by the device icon and the mobile phone can belong to the same user, and thus the text information displayed below each device icon can be "My" and the device type, such as My PC and My Tablet.

[0158] In addition to the device icon and the text below it describing the device type, each piece of text describing the device type may also be surrounded by a button 211. Button 211 can be used to trigger the phone to display the services provided by the Trust Ring device. See the description below for details.

[0159] Native services can refer to at least one service provided by the mobile phone. Native services can be pushed based on content (document 1) dragged by the user. Native services are services or applications supported by the mobile phone. For example, based on document 1, the native services pushed by the mobile phone include: YOYO Assistant, Favorites Space, Social Application 1, and Social Application 2. If the user drags content 2 (different from the first content), the native services displayed in area 204 may be the same as or different from those in interface 2c.

[0160] Correspondingly, the service icon list 1 in area 204 includes: YOYO Assistant icon 207, Favorites icon 208, Social Application 1 icon 209, and Social Application 2 icon 210.

[0161] In addition, in area 204, the service icons are surrounded by text information such as the name or description of each service. For example, YOYO Assistant is below icon 207, Favorites is below icon 207, Send to Friends is below icon 209, and Share to Social Circle 1 is below icon 210.

[0162] Understandably, the name or annotation displayed around the service icon can provide a brief description of each service, making it easier for users to determine the function of each service.

[0163] It should be noted that when the phone displays service icon list 1 and device icon list 1, the appearance of different device icons or service icons may change depending on the position of icon 202.

[0164] For example, as shown in interface 2c, because the icon 202 dragged by the user is closest to icon 207, icon 207 becomes larger, meaning the area of ​​icon 207 is larger than the areas of the other device and service icons. This allows the user to clearly identify the currently selected device or service icon.

[0165] It should be understood that, in the embodiments of this application, as the position of the icon (e.g., icon 202) is changed by the user dragging it, the device icon or service icon closest to the icon may also undergo other forms of change, such as shrinking, darkening the color, or changing to semi-transparent, etc., and this application does not make specific limitations in this regard.

[0166] Furthermore, icon 202 can be made smaller after the phone launches the "Anywhere Door" feature. For example, icon 202 is smaller in interface 2c (Anywhere Door launched) compared to interface 2b (Anywhere Door not launched). This way, icon 202 will not completely cover the device icon or service icon, helping the user to identify the currently selected device icon or service icon.

[0167] When the phone displays service icon list 1 and device icon list 1, as the user drags icon 202 to a different position (without releasing the finger), the device icon or service icon closest to icon 202 changes. For example, when the user drags icon 202 to the position of icon 206 (where icon 206 is closest to icon 202 or icon 202 covers icon 206), the phone can display a 2D interface.

[0168] As shown in interface 2d in Figure 2, for device icon list 1 and service icon list 1, when icon 202 is closest to (covers) icon 206, icon 206 becomes larger and icon 207 returns to its initial state.

[0169] When the phone displays a 2D interface, it indicates that icon 206 is selected. In response to the user releasing the finger, the phone can transfer document 1, indicated by icon 202, to the tablet.

[0170] Afterwards, users can find document 1 in the tablet's document management application.

[0171] It should be noted that, in addition to the document management application on the receiving end, other applications on the receiving end can also store the first content. These other applications can be determined based on the first content, for example, applications that frequently open (expand) the first content. For instance, when the first content is an image or video, after the image or video is transferred to the tablet, the user can also find the first content in applications such as the gallery; when the first content is a document, after the document is transferred to the tablet, the user can also find the first content in office applications. This makes it more convenient for users to view the first content on the receiving end.

[0172] It should also be noted that the sending and receiving interfaces shown in this application embodiment are merely examples. The top of the sending and receiving screens may also include a punch-hole area. For example, as shown in interfaces 2a to 2d in FIG2, the top of the mobile phone screen also includes a punch-hole area 212. The punch-hole area 212 may be capsule-shaped, and visually, for example, it may appear black (not shown in the interface of FIG2). Besides the center position at the top of the screen, the punch-hole area 212 may also be located on the left or right side of the top of the mobile phone screen. To keep the screen concise, punch-hole areas are not shown in the other interfaces provided in this application embodiment.

[0173] After transferring document 1 from the phone to the tablet, the phone can display the following interface.

[0174] In one possible scenario, in response to the user releasing their hand, the phone switches from interface 2d to interface 2a. That is, the phone closes the "Anywhere Door" and restores the interface before the "Anywhere Door" was activated.

[0175] In another possible scenario, in response to the user releasing their hand, the phone switches from interface 2d to interface 3a in Figure 3. That is, the phone can display a progress bar indicating the transfer progress of document 1, allowing the user to easily monitor the transfer progress.

[0176] As shown in interface 3a of Figure 3, in addition to the content of the chat interface (interface 2a), interface 3a also includes a notification bar 301. The notification bar 301 can be located at the top of the phone screen, and it can blend seamlessly with the punch-hole area, creating the visual effect of the punch-hole area being hidden. For example, when the punch-hole area is located in the center of the top of the screen, the notification bar 301 can also be located in the center of the top of the screen; or when the punch-hole area is located on the top left (or right) of the screen, the notification bar 301 can also be located on the top left (or right) of the screen.

[0177] It should be noted that in this embodiment, the notification bar can be in the form of a "capsule," and may also be referred to as a capsule, a dynamic capsule, or a floating capsule, etc. Furthermore, the notification bar can be integrated with the punch-hole area on the screen. For the sake of simplicity, this will not be elaborated further below.

[0178] The notification bar 301 includes icons 302 and 303.

[0179] Icon 302 can be understood as the icon of any door, used to indicate that document 1 was transmitted through any door.

[0180] Icon 303 can be understood as a representation of a progress bar, indicating the transfer progress of document 1 from the phone to the tablet. As the transfer progress of document 1 increases, the degree to which the thin-lined circle in icon 303 is covered by the thicker lines becomes more pronounced.

[0181] When document 1 is successfully transferred, the phone can switch from interface 3a to interface 3b.

[0182] As shown in interface 3b of Figure 3, compared to interface 3a, the notification bar 301 is replaced by notification bar 304. Notification bar 304 includes icon 302 and icon 305. Icon 305 can be used to indicate that document 1 has been transferred.

[0183] It should be noted that, in the embodiments of this application, the prompt bars are merely examples, and the icons included may be replaced with other styles. This application does not impose any specific limitations on this.

[0184] Furthermore, after the duration of the phone's display interface 3b exceeds one duration (e.g., 1 second), the phone switches from interface 3b to interface 2a. That is, after document 1 is transferred, the phone displays the notification bar 304 for one duration. After one duration, the notification bar 304 disappears, and the phone switches from interface 3b to interface 2a.

[0185] Furthermore, the prompt bar 301 and / or prompt bar 304 shown in Figure 3 can also be switched to card format. Details are as follows.

[0186] Optionally, when the phone displays interface 3a, in response to the user's input operation 2 (such as clicking) on ​​the prompt bar 301, the phone switches from interface 3a to interface 3c.

[0187] As shown in interface 3c, compared to interface 3a, the prompt bar 301 in interface 3a is replaced by card 306. Card 306 includes icon 307, icon 308, and text information.

[0188] It should be understood that, in this embodiment of the application, similar to the prompt bar, the card can also be integrated with the punch-hole area in the screen. For details, please refer to the description of the prompt bar above; it will not be repeated here.

[0189] Icon 307 can be used to indicate document 1, so that the user can determine the type of document 1. Icon 308 is similar to icon 303 and is used to indicate the transmission progress of document 1.

[0190] The text information in card 306 includes: Anywhere Door, Sending, 900.2KB, and Sent to My Tablet.

[0191] The "Any Door" parameter can be used to indicate the transmission method of document 1, as described below. "Sending" indicates that document 1 is in the process of transmission. "900.2KB" represents the total data size of document 1. "Sent to my tablet" indicates that document 1 is being transmitted to a tablet.

[0192] When the phone displays interface 3c and document 1 has finished transferring, the phone can switch from interface 3c to interface 3d. Alternatively, after document 1 has finished transferring, the phone switches from interface 3c to interface 3b; in response to user input operation 3 (such as clicking) on ​​prompt bar 304, the phone switches from interface 3b to interface 3d.

[0193] As shown in interface 3d, compared to interface 3b, the prompt bar 304 in interface 3b is replaced by card 309. Card 309 includes icon 307, icon 310, and text information.

[0194] Icon 310 is similar to icon 305 and is used to indicate that document 1 has been transferred.

[0195] The text information in card 309 includes: Anywhere Door, Successfully Sent, and Sent to My Tablet.

[0196] In this context, "successful transmission" indicates that document 1 has been successfully transmitted.

[0197] Furthermore, if the display duration of interface 3D exceeds duration 2 (e.g., 5 seconds), the phone can switch from interface 3D to interface 2a. That is, the phone displays card 309 for duration 2. After duration 2, card 309 disappears, and the phone displays interface 2a.

[0198] It should be understood that the prompts or cards shown in the embodiments of this application for displaying content transmission progress (or cross-device service preparation progress) are merely examples. The sending or receiving end may also display content transmission progress (or cross-device service preparation progress) through other forms of cards, prompts, notification messages, or pop-ups, and this application does not specifically limit this.

[0199] It should be noted that when the phone displays the service icon list 1 corresponding to the local services (e.g., interface 2c), in response to the user dragging icon 202 to an icon in the service icon list 1 and releasing it, the phone can display the screen of the service corresponding to that icon in full screen or a floating window. For example, if the icon is icon 209, the phone can display the screen of social application 1 in full screen or a floating window.

[0200] The arbitrary gate shown above will be explained below with reference to Figure 1.

[0201] The AnyDoor allows users to quickly access various services or devices by long-pressing target content on the screen and dragging it to the side edges of the screen. For example, referring to Figure 2, in response to the user's long-press operation on icon 201 (while the user is still pressing), the phone generates icon 202 (interface 2b); in response to the user's dragging of icon 202 to the side edges of the screen (while the user is still pressing), the phone displays device icon list 1 and service icon list 1 (interface 2c); in response to the user continuing to drag icon 202 to the position of icon 206 (while the user releases their finger), document 1 is transferred to the tablet.

[0202] The action of displaying device icon list 1 and service icon list 1 in response to the user dragging the target content to the edge of the screen can also be understood as: opening the "Any Door" (or activating the Any Door) in response to the user dragging the target content to the edge of the screen. For example, interfaces 2c and 2d show the state of the Any Door being open. When the Any Door is open, the terminal device can display: service icon list 1 of local services pushed based on the target content, and device icon list 1 of terminal devices that have established a trust relationship with this terminal device.

[0203] After the target content has been transmitted, the "Anywhere Door" can be closed. For example, after document 1 has been transmitted, the phone switches from interface 2d to interface 3a. At this time, the "Anywhere Door" closes, and the phone's interface no longer includes device icon list 1 and service icon list 1.

[0204] The above shows a schematic diagram of the mobile phone's interface during the process of transferring document 1 from the mobile phone to the tablet via the "AnyDoor" feature. The following is a detailed description of the tablet's interface during this process.

[0205] It is understandable that, in conjunction with interface 2d in Figure 2, in response to the user dragging icon 202 to icon 206 (at which point the user releases their grip), the phone begins transferring document 1 to the tablet. Assuming the tablet is displaying its desktop (i.e., the tablet is not locked) before the phone begins transferring document 1, then in response to the tablet receiving document 1, the tablet can switch from the desktop to interface 4a in Figure 4.

[0206] As shown in interface 4a, compared to the desktop, interface 4a also includes a tooltip 401. Tooltip 401 includes icons 402 and 403.

[0207] Icon 402 can be interpreted as an icon of any door, indicating that document 1 was transmitted to the tablet via any door. Icon 403 can represent the progress of the tablet receiving document 1.

[0208] When the tablet successfully receives document 1, the tablet can switch from interface 4a to interface 4b.

[0209] As shown in interface 4b, interface 4b includes a prompt bar 404. The prompt bar 404 includes icons 402 and 405. Icon 405 is used to indicate that document 1 was successfully received.

[0210] That is, the difference between interface 4b and interface 4a is that icon 403 is switched to icon 405.

[0211] Furthermore, after document 1 is successfully received, the prompt bar 404 automatically expands into card 406, that is, the tablet switches from interface 4b to interface 4c.

[0212] As shown in interface 4c, card 406 includes icon 407, icon 408, and text information.

[0213] Icon 407 indicates document 1. Icon 408 can be understood as a share button. For example, in response to a user clicking icon 408, the tablet can share the received document 1 to other devices or services supported by the tablet.

[0214] The text information in card 406 includes: Any Door, Successful Receive, and From H90.

[0215] "Received successfully" indicates that document 1 has been received. "From H90" indicates that document 1 was received from H90, which can be understood as the phone model.

[0216] Furthermore, after a duration of 3 seconds (e.g., 5 seconds), card 406 can disappear or switch to notification bar 404. When card 406 switches to notification bar 404, the tablet switches from interface 4c to interface 4b.

[0217] When switching from interface 4c to interface 4b, the 404 error message will disappear after a duration of 4 seconds (e.g., 5 seconds). Afterwards, the user can view the notification that document 1 was successfully received in the notification center.

[0218] It should be noted that the prompt bar 401 can also be switched to a card. For example, when the tablet display interface 4a is active, in response to the user's input operation 4 on the prompt bar 401 (such as a click operation), the prompt bar 401 can be switched to a card 409.

[0219] Card 409 includes icon 407, icon 410, and text information.

[0220] Icon 410, similar to icon 403, is used to indicate the progress of receiving document 1.

[0221] The text information on card 409 includes: Any Door, Receiving, Total 900.2KB, and From H90.

[0222] Here, "receiving" indicates that document 1 is being received but has not yet been successfully received; "total 900.2KB" indicates the total data size of document 1; "from H90" indicates that document 1 was received from H90, which can be understood as the model of a mobile phone.

[0223] It is understood that the text information shown in the card in this application embodiment is merely an example. The text information may include more content, such as including a percentage indicating the transmission progress (e.g., displaying 70%); or, the text information may include less content, such as excluding any door; or, the content in the text information may be replaced with other things, such as replacing the device model with the device name. This application does not make specific limitations in this regard.

[0224] In addition to the cards or notification bars shown above, the sender can also display the transmission progress to the user in other ways.

[0225] For example, after document 1 begins to be transferred to the tablet, the mobile phone can switch from interface 2d to interface 5a in Figure 5.

[0226] As shown in interface 5a, interface 5a includes a prompt bar 501, which can also be called a floating ball or floating capsule. The prompt bar 501 includes an icon 502. Icon 502 can be understood as a device ball representing a tablet, indicating that the receiving end is a tablet. Furthermore, icon 502 can also indicate the process of transferring document 1 to the tablet.

[0227] In response to the completion of transferring document 1 from the phone to the tablet, the phone can switch from interface 5a to interface 5b.

[0228] As shown in interface 5b, interface 5a includes a notification bar 503. The notification bar 503 includes an icon 504. Icon 504 indicates that document 1 has been successfully transferred.

[0229] Optionally, when the phone displays prompt bar 501, in response to user input on icon 502, such as a click, prompt bar 501 can switch to pop-up window 1, where the text information is similar to the text information of card 306 in interface 3c; and / or, when the phone displays prompt bar 503, in response to user input on icon 504, such as a click, prompt bar 503 can switch to pop-up window 2, where the text information is similar to the text information of card 309 in interface 3d. For simplicity, these will not be shown individually here.

[0230] The above illustrates the interface diagrams of the mobile phone and tablet during the process of transferring the first content from the mobile phone to the tablet. In some possible implementations, the sending end and / or receiving end can also be replaced with other device types. For example, in the case of the mobile phone transferring the first content to the PC, the interface of the mobile phone can be seen in Figures 2 and 3, and the interface of the PC can be shown in Figure 6.

[0231] It is understandable that, in conjunction with interface 2d in Figure 2, in response to the user dragging icon 202 to the position of icon 206 (at which point the user releases their grip), the mobile phone begins transferring document 1 to the PC. The mobile phone can display interface 2a or interface 3a. Correspondingly, assuming that before the mobile phone transfers document 1 to the PC, the PC displays the Smart Connect interface (i.e., the tablet is not locked), then in response to the PC starting to receive document 1, the PC can switch from the Smart Connect interface to interface 6a in Figure 6.

[0232] As shown in interface 6a, compared to the content in the smart interconnection interface, interface 6a also includes card 601. Card 601 includes icon 602, icon 603, indicator bar 604, button 605, button 606, and text information.

[0233] Icon 602 can be interpreted as the icon of any door, indicating that document 1 was transmitted to the PC through any door.

[0234] Icon 603 can be understood as the icon for document 1, so that users can identify the type of file they have received.

[0235] Indicator bar 604 can be understood as a possible form of progress bar, indicating the progress of PC receiving document 1.

[0236] Button 605 can be understood as a button used to pause the reception of document 1. For example, in response to a user's input operation on button 605 (such as a click operation), the transmission of document 1 is suspended. In addition, icon 605 can be switched to a button used to indicate that document 1 is in a paused transmission state.

[0237] Button 606 can be understood as a button used to close card 601. For example, in response to user input on button 606 (such as a click), card 601 can disappear. Furthermore, after card 601 disappears, when the PC successfully receives document 1, the PC may not display interface 6b, that is, it may not display card 607.

[0238] The text information in card 601 includes: 1 document, 60.92 / 900.2KB, and 25.62MB / s.

[0239] Here, 1 document represents the number of documents transmitted; in 60.92 / 900.2KB, 60.92 represents the amount of data in document 1 that has been received, and 900.2KB represents the total amount of data in document 1; 25.62MB / s represents the speed at which document 1 is received.

[0240] When the PC successfully receives document 1, the tablet can switch from interface 6a to interface 6b.

[0241] As shown in interface 6b, interface 6b includes card 606. Card 606 includes icon 602, icon 603, button 606, button 608, button 609, and text information.

[0242] In this context, button 608 can be understood as a button used to view the received document 1. For example, in response to the user clicking button 608, the PC can display the folder containing document 1, etc.

[0243] Button 609 can also be understood as a button used to close card 606. For example, in response to the user clicking button 609, card 607 can disappear.

[0244] The text information in card 606 includes: 1 document and "completed". "Completed" means that document 1 has been received.

[0245] It should be noted that the interfaces of the receiving end shown above (the tablets in Figures 4 and 5, and the PC in Figure 6) are all examples. The prompt bar or card indicating the progress of receiving document 1 can be displayed on any interface. For example, assuming the receiving end displays the interface of a game application before receiving document 1, the prompt bar or card indicating the progress of receiving document 1 will be displayed on the game application's interface. This application does not impose any specific limitations on this.

[0246] It is understandable that the device type of the sending end and / or receiving end can be other, and the first content transmitted by the sending end to the receiving end can also be other content, and the number of the first contents can be even greater.

[0247] For example, as shown in Table 1, the sending end can be a mobile phone or a tablet. That is, the mobile phone or tablet can activate any door and transmit the first content to the receiving end through the any door. The receiving end can be a mobile phone, tablet, or PC.

[0248] The first content may include, but is not limited to, one or more of the following: single or multiple images, single or multiple documents, single or multiple compressed files, single or multiple videos, or single or multiple audio files. Furthermore, the first content may also be a combination of one or more of the above types. For example, the first content may be a single document and a single compressed file, or the first content may be multiple images and a video, etc.

[0249] Table 1

[0250] The above describes the process by which the sending end transmits the first content to the receiving end through an arbitrary door. As can be seen from the above process, the cross-device content transmission method of this application, in response to the user's input operation on the first content, allows the sending end to activate an arbitrary door and transmit the first content to the receiving end through the arbitrary door. The user does not need to search for the first content in the sending end's file management or other applications, and the sending and receiving ends do not need to log in to the same cloud application account sequentially.

[0251] For example, referring to Figure 2, users can directly drag and drop document 1 in the chat interface to activate a portal on their phone, allowing them to send document 1 to the tablet. This eliminates the need for users to search for document 1 in their phone's file management app, and neither the phone nor the tablet needs to log into a cloud application account. This significantly improves the efficiency of transferring content across devices and enhances the user experience.

[0252] It should be noted that the interface for launching the "Anywhere Door" on the sending end can also be other interfaces. For example, when the sending end displays the interface of a gallery application, it can launch the "Anywhere Door" in response to the user's dragging and dropping of images and / or videos in the gallery application; or, when the sending end displays the interface of a short video application, it can launch the "Anywhere Door" in response to the user's dragging and dropping of images, etc. This application does not impose specific limitations on this.

[0253] To further enhance the convenience of cross-device content transfer, the sending end can also use a "gateway" to transmit second content to services supported by the receiving end. This allows the second content to be quickly displayed on the receiving end's services. For example, through the "gateway," the sending end can transmit the second content to a social application supported by the receiving end, such as [application name 1]. Thus, after receiving the second content, the user does not need to search for it in the receiving end's file management applications or other applications and then transmit it to a service supported by the receiving end.

[0254] For ease of distinction, the process of transmitting the first content through any door as shown in Figures 2 to 6 can be called cross-device file transfer; the service supported by the sending end transmitting the second content to the receiving end through any door can be called cross-device service, or the service in which the second content flows from the sending end to the receiving end, etc.

[0255] This application allows for the transmission of the second content to a service supported by the receiving end through two methods. These two methods are described in detail below.

[0256] In the first approach, the sending end can directly display service icons for various services pushed by the receiving end based on the second content. See Figures 7 and 8 for details.

[0257] In the second approach, the sending end can display the service entry point of the receiving end, instead of directly displaying the service icons of the various services pushed by the receiving end based on the second content. See Figures 9 to 25 for details.

[0258] First, taking a mobile phone as the sender, a tablet as the receiver, and document 1 as the second content as an example, we will explain the first solution.

[0259] Option 1

[0260] When the second content is document 1, the mobile phone can activate the Anywhere Door through the methods shown in interfaces 2a to 2d in Figure 2. When the mobile phone displays interface 2d, in response to the user dragging icon 202 to the position of icon 206 (without releasing the finger), and the icon 202 remaining at the position of icon 206 for more than a duration of 5 (without releasing the finger), the mobile phone can switch from interface 2d to interface 7a in Figure 7.

[0261] As shown in interface 7a, the difference from interface 2d is that, in addition to displaying the device icon list 1 for the trust ring device and the service icon list 1 for the local service, area 204 also displays the service icon list 2 for the receiving end service. The receiving end service is the service pushed by the receiving end based on the second content, that is, the service pushed by the tablet based on document 1.

[0262] Services pushed to the tablet based on document 1 include, for example, YOYO Assistant, Favorites Space, and Social Application 1. Correspondingly, the service icon list 2 includes the YOYO Assistant icon 701, the Favorites Space icon 702, and the Social Application 1 icon 703.

[0263] Furthermore, each service icon in the service icon list 2 is surrounded by its name or description. For example, the name below icon 701 is YOYO Assistant, the name below icon 702 is Collection Space, and the description below icon 703 is Send to a friend, etc.

[0264] It should be understood that, in this embodiment, the local service is the icon of the service pushed by the sending end based on the second content and the application installed by the sending end. The receiving end service is the service pushed by the receiving end based on the second content and the application installed by the receiving end. That is, the local service is related to the application installed by the sending end, and the receiving end service is related to the application installed by the receiving end. The local service and the receiving end service can be completely identical, partially identical, or completely different.

[0265] For example, combining the service icon list 2 corresponding to the receiving service and the service icon list 1 corresponding to the local service shown in interface 7a, if both the mobile phone and the tablet have the smart assistant YOYO installed, then both the local service and the receiving service can include the YOYO assistant, and both service icon list 2 and service icon list 1 include the icon of the YOYO assistant; if the mobile phone has social application 2 installed, then the local service can include social application 2, and service icon list 1 includes the icon 210 of social application 2; if the tablet does not have social application 2 installed, then the receiving service does not include social application 2, so service icon list 2 does not push the icon of social application 2.

[0266] To facilitate differentiation, each service icon in service icon list 2 is also surrounded by icon 704. Icon 704 can be a thumbnail of the receiving device. For example, when the receiving device is a tablet, icon 704 can be a thumbnail of the tablet. This helps users identify the service on the receiving device.

[0267] When the phone displays interface 7a, as the user drags icon 202 to a further location (without releasing the finger), the service icon closest to icon 202 changes. For example, when the user drags icon 202 to the location of icon 703 (without releasing the finger), the phone can display interface 7b.

[0268] As shown in interface 7b, in response to the operation of dragging icon 202 to the position of icon 703, icon 703 becomes larger and icon 206 returns to its initial state.

[0269] When the phone displays interface 7b, it indicates that the icon 703 of social application 1 is selected. At this time, in response to the user releasing the button, the phone can transfer document 1 indicated by icon 202 to the tablet, and the tablet launches social application 1 and uses document 1 in social application 1.

[0270] For example, the tablet can display the interface of social application 1, which may be a friend list interface, including a friend list; in response to the user's operation of selecting the icon of the first friend in the friend list, the tablet can display the chat interface corresponding to the first friend, and the tablet can send document 1 to the first friend.

[0271] Alternatively, before displaying the interface of social application 1 on the tablet, the tablet may also display the interface in Figure 4 to show the user the progress of receiving document 1.

[0272] It should be understood that, in the embodiments of this application, the process of the receiving end using the second content in the target service after receiving the second content from the sending end can also be referred to as the receiving end transferring the second content to the target service. For example, the process of the tablet receiving document 1 and using document 1 in social application 1 can be referred to as the tablet transferring document 1 to social application 1. For the sake of brevity, this will not be elaborated further below.

[0273] It should also be noted that after the receiving end successfully transfers the second content to the target service, the receiving end can display the target service interface in full-screen mode, or in a floating window mode (at which point the interface before the second content was successfully transferred to the target service can still be displayed in full-screen mode), or in a split-screen mode (i.e., the interface before the second content was successfully transferred to the target service and the target service interface are displayed in a split-screen mode). This application does not impose specific limitations on this.

[0274] Furthermore, the way the receiver displays the interface of the target service can vary depending on the target service selected by the user. For example, when the target service is an office application, the receiver can display the office application's interface in full screen; when the target service is a social application, the receiver can display the social application's interface as a floating window, and so on.

[0275] In addition, the following methods can be used to trigger the display of a list of service icons for the receiving service on the mobile phone 2.

[0276] For example, when the phone displays interface 2c (or interface 2d), in response to the user dragging icon 202 to the corresponding button 211 position on the tablet (without releasing the button), the phone can switch from interface 2c (or interface 2d) to interface 7a.

[0277] In other words, button 211 can be used to trigger the mobile phone to display the services provided by the trust ring device.

[0278] When the phone displays interface 7b, in response to the user releasing their hand, document 1 can be transferred from the phone to the social application 1 on the tablet. The phone can then display the following interface.

[0279] In one possible scenario, the phone switches from interface 7b to interface 2a (chat interface). That is, in response to transferring document 1 to the tablet, the phone reverts to the display interface before launching AnyDoor.

[0280] In another possible approach, the phone switches from interface 7b to interface 3a in Figure 3, and then the phone can also display other interfaces shown in Figure 3. Alternatively, the phone switches from interface 7b to interface 5a in Figure 5, and then the phone can also display interface 5b. Please refer to the description above for details, which will not be repeated here.

[0281] In another possible scenario, the phone switches from interface 7b to interface 7c. As shown in interface 7c, the phone closes the "Anywhere Door" and displays the chat interface of social application 1. Furthermore, interface 7c also includes card 705. Card 705 includes icon 706, icon 707, and text information.

[0282] Icon 706 can be interpreted as the icon of any door, indicating that the second content (document 1) was transmitted through any door. Icon 707 can be used to indicate that the second content has not yet been successfully transferred to the receiving end of the service.

[0283] The text information in card 705 may include: "Anywhere Door" and "Cross-Device Service Preparing". "Cross-Device Service Preparing" indicates that the second content has not yet been successfully transferred to the receiving end's service.

[0284] Subsequently, once the second content has been successfully transferred to the receiving end's service, the phone can switch from interface 7c to interface 7d.

[0285] As shown in interface 7d, the difference from interface 7c is that card 705 is switched to card 708. Card 708 includes icon 706, icon 709, and text information.

[0286] Icon 709 can be used to indicate that the second content has been successfully transferred to the receiving end of a service.

[0287] The text information in card 708 may include: "Anywhere Door and cross-device service are ready. Please continue using the tablet." This is used to notify the user that the second content has been successfully transferred to the tablet's service, and they can continue operating on the tablet.

[0288] Optionally, when the phone displays interface 7c, in response to the user's input operation 7 on card 705, such as swiping card 705 upwards or double-tapping card 705, the phone can switch card 705 to the prompt bar 301 shown in interface 3a; when the phone displays interface 7d, in response to the user's input operation 7 on card 708, such as swiping card 708 upwards or double-tapping card 708, the phone can switch card 708 to the prompt bar 305 shown in interface 3b.

[0289] It is understandable that in a service flow model where the second content is transferred from the sending end to the receiving end, the receiving end's file management application can also include the second content. Users can then search for the second content within the receiving end's file management application. Alternatively, when the second content is an image and / or video, in addition to the file management application, it can also be found in applications such as the receiving end's gallery.

[0290] It should be noted that, compared to the first content, the second content can also be text information. That is, the sending end can directly send text information to the receiving end's service. Referring to Figure 8, and still using a mobile phone as the sending end and a tablet as the receiving end as an example, the process of a mobile phone sending text information to a tablet's service through the "AnyDoor" will be explained in detail below.

[0291] As shown in Figure 8, interface 8a is the interface of the short video application. Interface 8a includes text 801. In response to the user's input operation 5 on text 801 (without releasing the finger), such as a long press on text 801, the phone switches from interface 8a to interface 8b.

[0292] As shown in interface 8b, the phone can display a thumbnail of text 801, i.e., icon 802, around text 801. In response to the user dragging icon 802 to the two edges of the phone (without releasing it), the phone activates the "Anywhere Door," that is, the "Anywhere Door" opens, and the phone can switch from interface 8b to interface 8c.

[0293] As shown in interface 8c, interface 8c includes image 803 and region 804. Region 804 can be understood as the area in interface 8c other than image 803.

[0294] The content included in image 803 is the same as that in the interface of the short video application (i.e., interface 8a). The difference is that the content displayed in image 803 can undergo three-dimensional transformations such as tilting, creating a visual effect on the screen that makes the original interface (interface 8a) appear to push inward.

[0295] Zone 804 displays a list of device icons for the Trust Ring device (2) and a list of service icons for local services (3).

[0296] The device icon list 2 includes icon 805 for a PC that has established a trust relationship with the mobile phone, and icon 806 for a tablet that has established a trust relationship with the mobile phone.

[0297] In area 804, each device icon is surrounded by text information describing its device type. For example, "My PC" below icon 805 and "My Tablet" below icon 806. This helps users identify the device type corresponding to each trust ring device.

[0298] In addition, in area 804, besides the text information describing the device type, each device type text is surrounded by a button 818. Button 818 can be used to trigger the phone to display the services provided by the trust ring device.

[0299] Native services can be understood as services provided by the mobile phone. Specifically, they are native services pushed by the phone based on text 801 dragged by the user. For example, native services pushed by the phone based on text 801 include: YOYO Assistant, Favorites, Search, Social App 1, Social App 2, Calendar, and Navigation, etc.

[0300] Correspondingly, the list of service icons for local services includes: YOYO Assistant icon 807, Favorites icon 808, Search icon 809, Social Application 1 icon 810, Social Application 2 icon 811, Calendar icon 812, and Navigation application icon 813, etc.

[0301] In addition, in area 804, the service icon list 3 is surrounded by the names or descriptions of each service. For example, YOYO Assistant is below icon 807, Favorites is below icon 808, Search is below icon 809, Send to Friends is below icon 810, Post to Social Circle 1 is below icon 811, Create Schedule is below icon 812, and Navigation is below icon 813.

[0302] It should be noted that, similar to the process shown in Figure 2, after the phone activates the "Anywhere Door" feature, the appearance of different device or service icons may change depending on the position of the icon 802 that the user is dragging (while still holding it). For example, as shown in interface 8c, in response to the user dragging icon 802 to the position of icon 807, icon 807 becomes larger. This allows the user to confirm that the currently selected service icon is icon 807.

[0303] Furthermore, compared to before the phone activates the "Anywhere Door" feature, after the phone activates the "Anywhere Door" feature, icon 802 can be semi-transparent and / or icon 802 can be smaller. For example, icon 802 in interface 8c is smaller than icon 802 in interface 8b, and icon 802 in interface 8c is semi-transparent. In this way, icon 802 will not completely cover the device icon or service icon, helping users to identify the currently selected device icon or service icon.

[0304] When the phone displays interface 8c, as the user drags icon 802 to a different position (without releasing the button), for example, if the user drags icon 802 to the position of icon 806 and icon 802 remains at the position of icon 806 for more than duration 6 (without releasing the button), the phone can switch from interface 8c to interface 8d. Alternatively, in response to the user dragging icon 802 to the corresponding button 818 on the tablet (without releasing the button), the phone can switch from interface 8c to interface 8d.

[0305] As shown in interface 8d, the difference from interface 8c is that, in addition to displaying the device icon list 2 and service icon list 3 in area 804 of interface 8d, the service icon list 4 of the receiving end service is also displayed in area 804.

[0306] It should be understood that the device icon list 2 and service icon list 3 can be found in the description above, and will not be repeated here.

[0307] Here, "receiving end service" can be understood as the service supported by the receiving end. The receiving end service can be pushed based on text 801 dragged by the user. For example, the services pushed by the tablet (receiving end) based on text 801 include video application 1, video application 2, and video application 3. Then, the service icon list 4 for the receiving end service includes: icon 814 for video application 1, icon 815 for video application 2, and icon 816 for video application 3.

[0308] It is understood that, in the embodiments of this application, depending on the second content, the local service pushed by the sending end may be the same or different, and the receiving end service pushed by the receiving end may be the same or different.

[0309] For example, Figure 7 illustrates the process of document 1 being sent from a mobile phone to a tablet and then transferred to the tablet's service; Figure 8 illustrates the process of text 801 being sent from a mobile phone to a tablet and then transferred to the tablet's service. In both processes, the sending end that sends the second content is the same, and the receiving end that receives the second content is also the same.

[0310] The second difference in content can lead to different local services being pushed by the sending end. Referring to interface 7d, when the second content is document 1, the local services include YOYO Assistant, Favorites, Social App 1, and Social App 2, and the phone displays a list of service icons corresponding to these local services (list 1). Referring to interface 8d, when the second content is text 801, the local services include YOYO Assistant, Favorites, Search, and Social App 1, and the phone displays a list of service icons corresponding to these local services (list 3).

[0311] Similarly, the receiving services pushed to different receiving devices may also differ depending on the second content. Referring to interface 7d, when the second content is document 1, the receiving services include YOYO Assistant, Favorites Space, and Social Application 1, with the tablet displaying a list of service icons corresponding to these services (2). Referring to interface 8d, when the second content is text 801, the receiving services include video application 1, video application 2, and video application 3, with the tablet displaying a list of service icons corresponding to these services (4).

[0312] In addition, in area 804, the service icon list 4 is surrounded by the names or descriptions of each service. For example, Video 1 is below icon 814, Video 2 is below icon 815, and Video 3 is below icon 816. This helps users distinguish the services provided by the receiving end.

[0313] To facilitate the distinction between receiving end services and local services, icon 817 is displayed around the service icon list 4 for receiving end services. Icon 817 can be understood as a thumbnail of the receiving end. For example, when the receiving end is a tablet, icon 817 can be a thumbnail of the tablet. This helps users identify the services provided by tablets as icons 814 to 816.

[0314] Furthermore, in response to the user dragging icon 802 to the target service in the service icon list 4 (and then releasing the drag), the phone can send text 801 to the target service on the tablet. This target service could be, for example, any of the services in video application 1, video application 2, and video application 3.

[0315] For example, in response to the user dragging icon 802 to the position of icon 814 (without releasing the finger), the phone switches from interface 8d to interface 8e.

[0316] As shown in interface 8e, when icon 802 is dragged to the position of icon 814, icon 814 enlarges so that the user can confirm that the currently selected service icon is icon 814. When icon 814 is selected, in response to the user releasing the finger, the phone can send text 801 to the tablet, and text 801 can be transferred to the tablet's video application 1.

[0317] Correspondingly, the tablet can display the interface of video application 1 as a floating window, and the interface of video application 1 can be related to text 801. For example, it can be a video playback interface related to text 801; or, the interface of video application 1 can also be the main interface of video application 1, and the main interface includes text 801, etc.

[0318] It should be noted that, in the embodiments of this application, the device icon list of the trust ring device, the service icon of the receiving end service, and the service icon of the local service shown in each interface are all examples. The device icon list, the service icon of the receiving end service, and the service icon of the local service shown in each interface can also be replaced with other icons. Furthermore, the number of device icons, the service icon of the receiving end service, and the service icon of the local service shown in each interface can be more or less. This application does not impose specific limitations in this regard.

[0319] The above example, using a mobile phone as the sender and a tablet as the receiver, illustrates the process of transferring the second content from the sender to the target service on the receiver. In some possible implementations, when the sender is a tablet (a larger device) and the receiver is a mobile phone (a smaller device), the tablet can also transfer the second content to the target service on the mobile phone according to the process shown in Figure 7 or Figure 8. The difference lies in that after the second content is successfully transferred to the target service on the mobile phone, the tablet can display a projection window, which can be used to display the mobile phone screen, allowing the user to continue operating on the sender.

[0320] It should be understood that the way the tablet displays the phone screen through the projection window is similar to the implementation method of the second method in the second solution below, which can be referred to in the following description, and will not be repeated here.

[0321] The second approach involves the sending end initiating an "anywhere door" to display the receiving end's service entry point. In response to the user dragging and dropping the second content to the service entry point (and then releasing it), the sending end sends the second content to the receiving end. Here, the service entry point can be understood as the overall identifier for all services supported by the trust ring device.

[0322] Then, the second content can be transmitted to the target service at the receiving end in two ways.

[0323] When the sending end is a mobile phone (a smaller device) and the receiving end is a tablet (a larger device), the second content can be transmitted to the target service on the receiving end using the first method.

[0324] When the sending end is a tablet (a larger device) and the receiving end is a mobile phone (a smaller device), the second content can be transmitted to the target service on the receiving end through the second method.

[0325] The two methods will be explained in detail below.

[0326] The first method

[0327] For example, as shown in 9a of Figure 9, the mobile phone responds to the user's dragging of the second content and launches the "Anywhere Door". At this time, the interface displayed on the mobile phone may include the tablet icon, the My Tablet service icon, the service 11 icon, the service 12 icon, and the service 13 icon; the tablet can display any interface.

[0328] The tablet icon is the same as the receiving device icon. The tablet's service icon can be understood as the service entry point for the tablet (receiving device). Services 11, 12, and 13 are services provided by the phone based on secondary content push notifications; these are local services.

[0329] At this point, in response to the user dragging the second content to the service icon on their tablet and releasing it, the interface on both the phone and tablet can switch from the interface shown in 9a to the interface shown in 9b. That is, the phone closes the "anywhere door" (a feature that allows access to any service), while the tablet opens it, and the tablet displays the icon for the service pushed based on the second content.

[0330] Services 21, 22, 23, and 24 are services pushed to the tablet based on the second content. In response to a user dragging and dropping the second content to a target service among services 21, 22, 23, and 24, or in response to a user's input operation 6 (such as a click) on the target service, the second content can be transferred to that target service. The tablet can then display the interface of the target service.

[0331] Assuming the second content is text information, the process of the mobile phone starting the Anywhere Door can be shown in interfaces 8a to 8c in Figure 8.

[0332] When the phone displays interface 8c, in response to the user dragging icon 802 to the position of icon 806, and keeping icon 802 at the position of icon 806 for more than duration 6 (without releasing the button), the phone can switch from interface 8c to interface 10a in Figure 10. Alternatively, when the phone displays interface 8c, in response to the user dragging icon 802 to the position of the corresponding button 818 on the tablet (without releasing the button), the phone can switch from interface 8c to interface 10a in Figure 10.

[0333] As shown in interface 10a, among the device icons and service icons displayed in area 804, the selected device icon is icon 806, making icon 806 larger. Furthermore, area 804 also displays the tablet's service icon 1001. Icon 1001 can be understood as the tablet's service entry point. Additionally, icon 1002 is displayed around icon 1001. Icon 1002 can be a thumbnail of the tablet, allowing the user to clearly identify the tablet's service entry point corresponding to icon 1001.

[0334] In addition, area 804 also displays a list 3 of service icons for local services. Compared to the list 3 of service icons shown in interfaces 8c to 8e, the list 3 of service icons shown in interface 10a includes more service icons. For example, in addition to icons 807 to 813, interface 10a also includes an icon 1003 for social application 3, and a note for social application 3, namely "Post to Social Circle 2," is displayed below icon 1003. This allows users to confirm that by dragging and dropping the second content to icon 1003, they can share the second content to the social circle of the phone's social application 3.

[0335] When the phone displays interface 10a, in response to the user dragging icon 802 to the position of icon 1001, the phone can switch from interface 10a to interface 10b.

[0336] As shown in interface 10b, compared to interface 10a, because icon 802 is closer to icon 1001, icon 806 returns to its initial state, and icon 1001 becomes larger. This is to help the user determine that the currently selected icon is icon 1001.

[0337] When the phone displays interface 10b, in response to the user releasing their hand, the phone can transfer text 801 to the tablet. The phone can then switch from interface 10b to the following interface.

[0338] In Method 1, the phone can switch from interface 10b to interface 8a, which restores the display of the short video application interface.

[0339] In Method 2, after text 801 starts transmitting to the tablet, the phone screen is not locked, and the phone can switch from interface 10b to interface 11a in Figure 11.

[0340] In method 3, after text 801 begins to be transmitted to the tablet, the phone screen locks, and the phone can switch from interface 10b to interface 12a in Figure 12. Alternatively, after text 801 begins to be transmitted to the tablet, the phone can switch from interface 10b to interface 11a in Figure 11; then, in response to the phone screen locking, the phone switches from interface 11a to interface 12a.

[0341] First, referring to Figure 11, we will explain the interface displayed on the phone in Method 2 (phone screen unlocked).

[0342] As shown in interface 11a, the phone closes the "Anywhere Door" and displays the interface of a short video application. Interface 11a also includes a card 1101. Card 1101 includes icons 1102 and 1103, as well as text information.

[0343] It should be understood that card 1101 is similar to card 705 in interface 7c, as can be seen in the description above, and will not be repeated here.

[0344] It should be noted that, compared to card 705, the text information in card 1101 indicates that the tablet has not yet successfully activated the Anywhere Door.

[0345] Afterwards, once the tablet successfully launches the Anywhere Door, the phone can switch from interface 11a to interface 11b.

[0346] As shown in interface 11b, the difference from interface 11a is that card 1101 is switched to card 1104. Card 1104 includes icon 1102, icon 1105, and text information.

[0347] It should be understood that card 1104 is similar to card 708 in interface 7d, as described above, and will not be repeated here. It should be noted that, compared to card 708, the text information in card 1104 can also indicate that the tablet has successfully launched the Anywhere Door.

[0348] Optionally, when the mobile phone displays interface 11a, in response to the user's input operation 7 on card 1101, such as swiping card 1101 upwards or double-tapping card 1101, the mobile phone can switch card 1101 to the prompt bar 1106 shown in 11c.

[0349] The prompt bar 1106 includes icons 1107 and 1108. Icon 1107 is similar to icon 1102 and can be used to indicate the "Anywhere Door". Icon 1108 is similar to icon 1103 and can be used to indicate that the tablet has not yet successfully activated the "Anywhere Door".

[0350] Optionally, when the phone displays prompt bar 1106, in response to the tablet successfully launching AnyDoor, the phone can switch prompt bar 1106 to prompt bar 1109 as shown in 11d.

[0351] Alternatively, when the phone displays prompt bar 1106, in response to the tablet successfully launching AnyDoor, the phone displays interface 11b.

[0352] When the phone displays interface 11b (which can be switched from interface 11a or from an interface including the prompt bar 1106), in response to the user's input operation 8 on card 1104, such as swiping card 1104 upwards or double-tapping card 1104, the phone can switch card 1104 to the prompt bar 1109 shown in 11d.

[0353] The notification bar 1109 includes icons 1107 and 1110. Icon 1107 is similar to icon 1102. Icon 110 is similar to icon 1105 and can be used to indicate that the tablet has successfully launched the Anywhere Door.

[0354] Furthermore, after a duration of 7 seconds (e.g., 5 seconds), card 1105 or notification bar 1109 disappears. That is, the display duration of card 1105 or notification bar 1109 is 7 seconds. After a duration of 7 seconds, the phone can display interface 8a (the interface of the short video application).

[0355] The following section, with reference to Figure 12, explains the interface displayed on the phone in Method 2 (phone lock screen).

[0356] As shown in interface 12a, interface 12a can be understood as the phone's lock screen interface. Furthermore, interface 12a includes notification 1201. Notification 1201 is similar to card 1101.

[0357] Notification 1201 includes icon 1202, icon 1203, and text information.

[0358] Among them, icon 1202 is similar to icon 1102 and can be understood as the icon of any door. It can be used to indicate that the second content (text 801) is transmitted through any door.

[0359] Icon 1203 is similar to icon 1103, indicating that the tablet has not yet successfully launched the Anywhere Door.

[0360] The text information in Notice 1201 is the same as the text information in Card 1101, as described above, and will not be repeated here.

[0361] In response to the tablet successfully launching AnyDoor, the phone can switch from interface 12a to interface 12b.

[0362] As shown in interface 12b, interface 12b can also be understood as the phone's lock screen interface. Furthermore, interface 12b includes notification 1204. Notification 1204 is similar to card 1104 (the card in interface 11b).

[0363] Notification 1204 includes icon 1202, icon 1205, and text information.

[0364] Among them, icon 1205 is similar to icon 1105, which can indicate that the tablet has successfully launched the Anywhere Door.

[0365] The text information in Notice 1204 is the same as the text information in Card 1104, as described above, and will not be repeated here.

[0366] It is understandable that, regardless of whether the phone is locked, in addition to the card shown in Figure 11 and the notification shown in Figure 12, the phone's notification bar (swipe down on the notification bar interface) can also display notifications related to cross-device service preparation and cross-device service readiness. The notifications related to cross-device service preparation can be similar to notification 1201 in interface 12a, and the notifications related to cross-device service readiness can be similar to notification 1204 in interface 12b. Please refer to the description above; it will not be repeated here.

[0367] The above shows a schematic diagram of the mobile phone's interface during the process of text 801 being sent from the mobile phone to the tablet and then transferred to the target service pushed by the tablet. The following is a detailed description of the tablet's interface during this process.

[0368] The interface displayed on a tablet includes the following types.

[0369] In scenario 1, when the phone starts sending text 801 to the tablet, the tablet is not locked. The tablet's interface can be shown in Figure 13 or Figure 14.

[0370] Figure 13 shows the interface when the tablet successfully launches the Anywhere Door; Figure 14 shows the interface when the tablet fails to launch the Anywhere Door.

[0371] In scenario 2, when the phone starts sending text 801 to the tablet, the tablet is in a locked screen state. The tablet's interface can be shown in Figure 15 or Figure 16.

[0372] Figure 15 shows the interface when the tablet successfully launches the Anywhere Door; Figure 16 shows the interface when the tablet fails to launch the Anywhere Door.

[0373] First, referring to Figure 13, we will explain the interface when the tablet can successfully launch the Any Door in Case 1.

[0374] Suppose that before text 801 is sent from the phone to the tablet (the user releases the phone while it is displaying interface 10b), the tablet displays the interface of social application 4, as shown in interface 13a in Figure 13.

[0375] Subsequently, in response to the tablet starting to receive text 801, the tablet can switch from interface 13a to interface 13b.

[0376] As shown in interface 13b, compared to interface 13a, interface 13b also includes card 1301. Card 1301 includes icon 1302, icon 1303, and text information.

[0377] It should be understood that card 1301 is similar to card 1101 (the card in interface 11a), icon 1302 is similar to icon 1102, and icon 1303 is similar to icon 1103. Furthermore, the text information in card 1301 is the same as the text information in card 1101. For details, please refer to the description above; further elaboration will not be repeated here.

[0378] When the tablet displays interface 13b, it indicates that the tablet is not yet ready to activate the "Anywhere Door". For example, before the tablet can activate the "Anywhere Door", it needs to successfully receive text 801 from the mobile phone and determine the push service based on text 801. Therefore, the tablet can display interface 13b when it has not fully received text 801 and / or has not yet determined the push service.

[0379] When the tablet is ready to launch Any Door (and can successfully launch Any Door), that is, when the tablet can display the interface corresponding to Any Door, the tablet can switch from interface 13b to interface 13c.

[0380] As shown in interface 13c, the difference from interface 13b is that card 1301 is switched to card 1304. Card 1304 includes icon 1302, icon 1305, and text information.

[0381] It should be understood that card 1304 is similar to card 1104 (the card in interface 11b), except that the text information in card 1304 is different from that in card 1104. Since card 1304 is a card displayed on the tablet, the text information in card 1304 does not require further prompting to continue operation on the tablet. Therefore, the text information in card 1304 is: Cross-device service ready. This text information can be used to prompt the user that they can continue operation, so that the text 801 received by the tablet can be transferred to the service provided by the tablet. Furthermore, icon 1302 is similar to icon 1102 in card 1104, and icon 1305 is similar to icon 1105 in card 1104. For details, please refer to the description above; further elaboration will not be repeated here.

[0382] Optionally, when the tablet displays interface 13b, in response to the user's input operation 9 on card 1301, such as swiping card 1301 upwards or double-tapping card 1301, the tablet can switch card 1301 to the prompt bar 1306 shown in 13d.

[0383] The prompt bar 1306 includes icons 1307 and 1308. Icon 1307 is similar to icon 1302 and can be understood as the icon of the Anywhere Door, indicating that the second content (text 801) is transmitted through the Anywhere Door. Icon 1308 is similar to icon 1303 and can be used to indicate that the tablet has not yet successfully activated the Anywhere Door.

[0384] In one possible implementation, when the tablet displays prompt bar 1306, in response to the tablet being ready to activate any door, the tablet can switch from prompt bar 1306 to prompt bar 1309 as shown in 13e.

[0385] In another possible implementation, when the tablet displays the prompt bar 1306, the tablet displays interface 13c in response to the tablet being ready to launch the Anywhere Door.

[0386] When the tablet displays interface 13c (which can be switched from interface 13b or from an interface including the prompt bar 1306), in response to the user's input operation 10 on the card 1304, such as swiping the card 1304 upwards or double-tapping the card 1304, the tablet can switch the card 1304 to the prompt bar 1309 shown in 13e.

[0387] The notification bar 1309 includes icons 1307 and 1310. Icon 1307 is similar to icon 1302. Icon 130 is similar to icon 1305 and can be used to indicate that the tablet is ready to launch the Anywhere Door.

[0388] When the tablet displays interface 13b or interface 13c, the user can also operate the interface of social application 4 normally.

[0389] The following explanation, in conjunction with Figures 13 and 14, describes the interface of the tablet when it fails to launch the Anywhere Door in Case 1.

[0390] In one possible implementation, the tablet switches from interface 13a to interface 14a.

[0391] In other words, in response to text 801 starting to transmit to the tablet, if the tablet cannot receive text 801 or other abnormal situations, the tablet can switch from interface 13a to interface 14a.

[0392] In another possible implementation, the tablet switches from interface 13b to interface 14a.

[0393] That is, in response to text 801 starting to be transmitted to the tablet, the tablet switches from interface 13a to interface 13b. Subsequently, in response to the tablet failing to properly start the Anywhere Door, the tablet can switch from interface 13b to interface 14a.

[0394] As shown in interface 14a, interface 14a includes card 1401. Card 1401 includes icon 1402, icon 1403, and text information.

[0395] Icon 1402 can be used to indicate any door. Icon 1403 can be used to indicate that the any door failed to start.

[0396] The text information in card 1401 includes: "Anywhere Door" and "Cross-Device Service Interrupted, Please Retry." "Anywhere Door" corresponds to icon 1402, indicating that the second content (text 801) was transmitted through "Anywhere Door." "Cross-Device Service Interrupted" corresponds to icon 1403, indicating that the tablet failed to initiate "Anywhere Door."

[0397] Optionally, when the tablet displays interface 14a, in response to the user's input operation 11 on card 1401, such as swiping card 1401 upwards or double-tapping card 1401, the tablet can switch card 1401 to the prompt bar 1404 shown in 14b. The prompt bar 1404 includes icons 1405 and 1406.

[0398] Icon 1405, similar to icon 1402, indicates that the second content (text 801) was transmitted through the Any Door. Icon 1406, similar to icon 1403, indicates that the Any Door failed to start.

[0399] Furthermore, after a duration of 8 seconds (e.g., 5 seconds), card 1401 or notification bar 1404 disappears. That is, the display duration of card 1401 or notification bar 1404 is 8 seconds. After a duration of 8 seconds, the tablet can display interface 13a (the interface of social application 4).

[0400] Below, referring to Figure 15, we will explain the interface in Case 2 (tablet locked screen) where the tablet can successfully launch AnyDoor.

[0401] In other words, when the tablet receives text 801 from the phone, the tablet is in a locked screen state.

[0402] As shown in interface 15a, interface 15a is the tablet's lock screen interface. Interface 15a includes notification 1501. Notification 1501 includes icon 1502, icon 1503, and text information.

[0403] In this context, icon 1502 can be interpreted as the identifier of the Any Door, indicating that the text 801 received by the tablet is transmitted through the Any Door; icon 1503 can indicate that the tablet is preparing to launch the Any Door; the text information in notification 1501 could be, for example, "Cross-device service preparing." "Cross-device service preparing" indicates that the tablet is preparing to launch the Any Door, but the Any Door has not yet been successfully launched.

[0404] Once the tablet can successfully launch the Anywhere Door, that is, when the tablet is ready to launch the Anywhere Door, the tablet can switch from interface 15a to interface 15b.

[0405] As shown in interface 15b, interface 15b includes notification 1504. Notification 1504 includes icon 1502, icon 1505, and text information.

[0406] Icon 1505 indicates that the tablet is ready to launch the "Anywhere Door" feature. The text message in notification 1504 indicates that the cross-device service is ready. "Cross-device service ready" means the tablet has successfully launched the "Anywhere Door" feature.

[0407] Below, referring to Figure 16, we will explain the interface in Case 2 (tablet locked screen) where the tablet cannot successfully launch AnyDoor.

[0408] In one possible implementation, the tablet switches from the lock screen to the interface shown in Figure 16.

[0409] In other words, in response to the text 801 starting to transmit to the tablet, if the tablet cannot receive text 801 or other abnormal situations, the tablet can switch from the lock screen to the interface shown in Figure 16.

[0410] In another possible implementation, the tablet switches from interface 15a to the interface shown in FIG16.

[0411] That is, in response to the text 801 being transmitted to the tablet, the tablet displays interface 15a; subsequently, if the tablet cannot start the Anywhere Door normally, the tablet can switch from interface 15a to the interface shown in Figure 16.

[0412] As shown in Figure 16, the interface includes notification 1601. Notification 1601 includes icon 1602, icon 1603, and text information.

[0413] Icon 1602 can be interpreted as the identifier for the Anywhere Door. Icon 1603 indicates that the Anywhere Door failed to start. The text message in notification 1601 indicates a cross-device service interruption; please try again. A cross-device service interruption means that the tablet failed to successfully start the Anywhere Door, resulting in the second content not being able to be transmitted to the service provided by the tablet.

[0414] It is understandable that regardless of whether the tablet is locked (case 1 or case 2), the tablet's notification bar (swipe down on the notification bar interface) can display notifications regarding cross-device service preparation and cross-device service readiness. The notification regarding cross-device service preparation can be similar to notification 1501 in interface 15a, and the notification regarding cross-device service readiness can be similar to notification 1504 in interface 15b. Please refer to the description above; it will not be repeated here.

[0415] The following, referring to Figure 17, describes the interface displayed on the tablet after the Any Door is successfully activated, showing the screen after the Any Door is activated.

[0416] In one scenario, combined with scenario 1 above, that is, when the tablet is not locked, the tablet can switch from interface 13c to the interface shown in Figure 17.

[0417] In this situation, the tablet can, for example, switch from interface 13c to the interface shown in Figure 17 when the display duration of interface 13c exceeds 8 (e.g., 300ms).

[0418] Alternatively, in this case, when the tablet is displaying interface 13c (the tablet is not locked), in response to the user's input operation on card 1304, such as a click operation, the tablet can switch from interface 13c to the interface shown in Figure 17.

[0419] It should be understood that in the above situation, the card 1304 in interface 13c can also be replaced by the prompt bar 1309. This application does not specifically limit this.

[0420] In the second scenario, combined with scenario 2 above, when the tablet is locked and displaying interface 15b, in response to the user's unlocking operation, the tablet can switch from interface 15b to the interface shown in Figure 17.

[0421] As shown in Figure 17, this interface can be understood as the interface corresponding to the opening of any door. This interface includes image 1701 and area 1702 other than image 1701.

[0422] The content in image 1701 is the same as that in the interface of social application 4 (interface 13a). The difference is that the content displayed in image 1701 is tilted. Furthermore, image 1701 may be blurred or out of focus to indicate that the user cannot operate the interface of social application 4.

[0423] In addition, in the area corresponding to image 1701, the tablet also displays icon 1703 and prompt bar 1704, and icon 1703 and prompt bar 1704 cover image 1701.

[0424] Icon 1703 can be understood as a thumbnail of the second content (text 801). Icon 1703 can be displayed in the lower right corner of the area corresponding to image 1701.

[0425] The prompt bar 1704 may include text such as: "Click the icon to use the service." Alternatively, the text in the prompt bar 1704 may also include other text, such as "Click the icon / drag content to the icon to perform an operation," etc. The text in the prompt bar 1704 can be used to prompt the user to open secondary content from the services provided by the tablet through clicking or dragging.

[0426] Optionally, the prompt bar 1704 may be the content displayed when a user first uses the cross-device service. This cross-device service refers to the function of the sending end transmitting second content to the target service on the tablet through any door. That is, when the user uses the cross-device service again subsequently, the interface displayed on the tablet may not include the prompt bar 1704.

[0427] Zone 1702 includes a list of device icons for trust ring devices (3) and a list of service icons (5).

[0428] Among them, device icon list 3 includes icon 1705 for a mobile phone. In addition, text information describing the device type is displayed around the device icon. For example, "My Mobile Phone" is displayed below icon 1705.

[0429] In addition, in area 1702, a button 1706 is displayed around the text information describing the device type. In response to the user clicking button 1706, or in response to the user dragging icon 1703 to the position of button 1706, the tablet can display the phone's service entry.

[0430] In addition to the device identifier list, area 1702 also displays a list 5 of service icons for services pushed by the tablet based on text 801 (text indicated by icon 1703).

[0431] For example, services that can be pushed to a tablet based on text 801 may include: YOYO Assistant, Favorites, Shopping App, Social App 3, Calendar, and Navigation, etc.

[0432] It should be understood that the tablet (receiving end) push service is based on the applications installed on the tablet and text push notifications (801), while the mobile phone (sending end) push service is based on the applications installed on the mobile phone and text push notifications (801). The tablet push service (the local service in the interface of Figure 17) and the mobile phone push service (the local service in interface 10a of Figure 10) may be different. Alternatively, in some possible implementations, the sending end and receiving end can have the same push service based on the second content. For details, please refer to the description of the local service and the sending end service in the first scheme, which will not be repeated here.

[0433] Correspondingly, the service icon list 5 includes: YOYO Assistant icon 1707, Favorites icon 1708, Shopping app icon 1709, Social app 3 icon 1710, Create schedule icon 1711, and Navigation icon 1712.

[0434] Furthermore, in area 1702, the names or descriptions of each service are displayed around the service icons in service icon list 5. For example, YOYO Assistant is below icon 1707, Collection Space is below icon 1708, Instant Buy is below icon 1709, Social Circle 2 is below icon 1710, Creation Schedule is below icon 1711, and Navigation is below icon 1712.

[0435] In response to the user clicking the target service icon in service list 5, or in response to the user dragging icon 1703 to the target service icon position in service list 5 and releasing the finger, the tablet can close the door and display the target service screen in a floating window.

[0436] For example, when the tablet displays the interface shown in FIG17, in response to the user clicking icon 1711, or in response to the user dragging icon 1703 to the position of icon 1711 and releasing it, the tablet can display the interface shown in FIG18.

[0437] As shown in Figure 18, the tablet can close any door while still displaying the interface of the social application 4 in full screen, and the tablet can also display a floating window 1801. Floating window 1801 can display the screen corresponding to the created schedule.

[0438] It should be understood that Figure 18 is only an example, and the receiving end (tablet) can also display the target service in full-screen or split-screen mode. For the sake of simplicity, they will not be shown one by one here.

[0439] Therefore, the cross-device service described above allows for convenient transfer of secondary content from the sending end to the target service on the receiving end. Before sending the secondary content, the user does not need to search for it in the sending end's file management application; and after the secondary content is sent to the receiving end, the user does not need to search for it in the receiving end's file management application and then transfer it to the target service on the receiving end. This simple operation helps improve the user experience.

[0440] The process of transferring the second content from the mobile phone to the tablet service has been explained above with reference to Figures 9 to 18. The process of transferring the second content from the tablet to the mobile phone service will be explained in detail below with reference to Figures 19 to 23.

[0441] The second method

[0442] For example, as shown in 19a of Figure 19, the tablet initiates a portal in response to the user's dragging of second content. At this time, the interface displayed on the tablet may include the phone's icon, icons of all phone services, the icon of service 31, the icon of service 32, and the icon of service 33; the phone can display any interface.

[0443] The phone icon is the same as the receiving device icon. All phone service icons can be understood as service entry points for the phone (receiving device). Services 31, 32, and 33 are tablet services based on secondary content push; these are local services.

[0444] At this point, in response to the user dragging the second content to the icon position of all mobile services and releasing it, the mobile phone and tablet can switch from the interface shown in 19a to the interface shown in 19b.

[0445] In other words, the tablet's display interface can include screen mirroring of the phone's display interface. Furthermore, the mirrored phone display interface includes: secondary content and service icons for services provided by the phone.

[0446] Among them, services 41, 42, 43, and 44 are services that the mobile phone pushes based on the second content. In response to the user's operation of dragging and dropping the second content to the target service among services 41, 42, 43, and 44, the second content can be sent to the target service.

[0447] The following example uses a tablet sending a second piece of content to a mobile phone as an illustration to illustrate the interface for sending a second piece of content from a tablet to a mobile phone.

[0448] As shown in interface 20a in Figure 20, interface 20a is the interface of social application 4. Interface 20a includes image 2001. In response to user input operation 12 on image 2001, such as long-pressing image 2001 (without releasing the finger), the tablet can switch from interface 20a to interface 20b.

[0449] As shown in interface 20b, in response to input operation 12, a thumbnail of image 2001, i.e., icon 2002, can be generated around image 2001. In response to the user dragging icon 2002 to the edge of the tablet (without releasing the finger), the tablet can switch from interface 20b to interface 20c.

[0450] As shown in interface 20c, interface 20c includes image 2003 and region 2004. Region 2003 can be understood as the area in interface 20c other than image 2003.

[0451] The content in image 2003 is the same as that in the interface of social application 4 (i.e., interface 20a). The difference is that the content displayed in image 2003 undergoes a three-dimensional transformation, such as tilting, to create a visual effect on the screen that makes the original interface (interface 20a) appear to be pushed inward.

[0452] Zone 2004 displays a list of device icons for the Trust Ring device (4) and a list of service icons for local services (6).

[0453] The trust loop devices are the other devices that have established a trust relationship with the tablet. For example, PCs and mobile phones that form a trust loop with the tablet. Therefore, device icon list 4 includes: PC icon 2005 and mobile phone icon 2006.

[0454] In addition, in area 2004, each device icon is surrounded by text information describing the device type. For example, "My PC" below icon 2005 and "My Phone" below icon 2006. This helps users identify the device type corresponding to each device icon.

[0455] In addition to the device icon and the text below it describing the device type, a button 2007 can be displayed around each device type's text. Button 2007 can be used to trigger the tablet to display the service entry point for the Trust Ring device.

[0456] The native services provided by the tablet can be services pushed to the tablet based on the second content (image 2001). For example, the native services provided by the tablet include: YOYO Assistant, Favorites, Shopping App, and Social App 3.

[0457] Correspondingly, the service icon list 6 includes: the YOYO Assistant icon 2008, the Favorites icon 2009, the Shopping app icon 2010, and the Social app 3 icon 2011.

[0458] In addition, in region 2004, the service icon is surrounded by the name or description of each service. See interface 20c for details; further explanation is omitted here.

[0459] Optionally, when the tablet displays interface 20c, in response to the user dragging icon 2002 to the position of icon 2006, and icon 2002 remaining at the position of icon 2006 for more than a duration of 6 (without releasing the button), the tablet can switch from interface 20c to interface 21a as shown in Figure 21. Alternatively, in response to the user dragging icon 2002 to the position of the corresponding button 2007 on the phone (without releasing the button), the tablet can switch from interface 20c to interface 21a as shown in Figure 21.

[0460] As shown in interface 21a, compared to interface 20c, in area 2004, in addition to displaying the phone icon 2006 and the service icon list 6, icon 2101 is also displayed.

[0461] Icon 2101 can be used to indicate the mobile phone's service entry point. The icon 2101 is also surrounded by text information explaining the mobile phone service entry point, namely, all mobile phone services. Through icon 2101, users can navigate to the services provided by the mobile phone.

[0462] In addition, icon 2102 is displayed around icon 2101. Icon 2102 can be understood as a thumbnail of the phone, so that users can identify the service entry point of the phone corresponding to icon 2101.

[0463] When the tablet displays interface 21a, in response to the user's operation of dragging icon 2002 to the position of icon 2101 (and then releasing the finger), the tablet can transfer image 2001 to the mobile phone.

[0464] Furthermore, if the tablet can successfully display the screen mirroring from the phone, the tablet can display interface 13b and interface 13c.

[0465] That is, in response to the user dragging icon 2002 to the position of icon 2101 (and then releasing the finger), the tablet switches from interface 21a to interface 13b as shown in Figure 13. In response to the user's input operation 9 on card 1301, such as swiping card 1301 upwards or double-tapping card 1301, the tablet can also switch card 1301 to the prompt bar 1306 shown in Figure 13d.

[0466] When the tablet can successfully project the phone's display, the tablet can switch from interface 13b to interface 13c.

[0467] If the display duration of interface 13c exceeds duration 9 (e.g., 200ms), the tablet can switch from interface 13c to interface 21b.

[0468] It should be noted that interfaces 13b and 13c are optional. In some possible implementations, after the tablet starts sending image 2001 to the phone, and the tablet is in a locked state, the tablet can switch from interface 21a to interface 15a in Figure 15 (indicating cross-device service ready); and when the tablet can successfully project the phone's display interface, the tablet can switch from interface 15a to interface 15b (indicating cross-device service ready); while the tablet is displaying interface 15b, in response to the user's unlocking operation, the tablet can switch from interface 15b to interface 21b.

[0469] Alternatively, in some possible implementations, in response to the user dragging icon 2002 to the position of icon 2101 (and then releasing the finger), the tablet switches from interface 21a to interface 13b shown in Figure 13 (the screen is not locked at this time); in response to the screen locking operation, the tablet switches from interface 13b to interface 15a; and when the tablet can successfully project the display interface of the mobile phone, the tablet can switch from interface 15a to interface 15b; when the tablet displays interface 15b, in response to the user unlocking the tablet, the tablet can switch from interface 15b to interface 21b.

[0470] Furthermore, it should be noted that regardless of whether the tablet is locked, the tablet's notification bar (swipe down on the notification bar interface) can also display notifications regarding cross-device service preparation and cross-device service readiness. The notification regarding cross-device service preparation is similar to notification 1501 in interface 15a, and the notification regarding cross-device service readiness is similar to notification 1504 in interface 15b. Please refer to the description above; it will not be repeated here.

[0471] Interface 21b is the interface displayed after the tablet successfully projects the phone's screen.

[0472] As shown in interface 21b, the tablet closes the door, and interface 21b includes a projection window 2103.

[0473] The projection window 2103 includes a touch bar 2104, a navigation bar 2105, and a projection screen 2106 located between the touch bar 2104 and the navigation bar 2105.

[0474] The touch bar 2104 includes buttons 2107, 2108 and 2109.

[0475] Button 2107 can be understood as a pause button, used to pause the screen mirroring of the tablet to the phone's display. Button 2108 can be understood as a minimize button, used to minimize the mirroring window 2103. Button 2109 can be understood as a close button, used to close the mirroring window 2103.

[0476] The navigation bar 2105 includes buttons 2110, 2111, and 2112.

[0477] Button 2110 can be understood as a back button, used to display the previous phone screen on the screen mirroring screen 2106. Button 2111 can be used to display the phone's desktop on the screen mirroring screen 2106. Button 2112 can be used to display the phone's multitasking cards on the screen mirroring screen 2106.

[0478] The screen mirroring screen 2106 can display the screen transmitted from the mobile phone in real time. Furthermore, the screen mirroring screen 2106 can be a heterogeneous projection of the mobile phone screen, meaning the projected screen 2106 can be different from the actual screen displayed on the mobile phone. The mobile phone can draw a screen in a virtual display and send it to the tablet so that the projected screen 2106 displays the screen drawn by the mobile phone, without affecting the normal screen-off or use of the mobile phone. Alternatively, the screen mirroring screen 2106 can be a homogeneous projection of the mobile phone screen, meaning the projected screen 2106 is the same as the actual screen displayed on the mobile phone.

[0479] The projected screen 2106 includes an image 2113, an area 2114, and an icon 2115 overlaid on the image 2113. The icon 2115 can be understood as a thumbnail of the image 2001 received by the mobile phone.

[0480] The content in image 2113 is the same as that in the interface of the short video application (interface 8a). The difference is that the content displayed in image 2113 can undergo three-dimensional transformations such as tilting. Furthermore, image 2113 can be blurred or out of focus to indicate that the user cannot operate the interface of the short video application.

[0481] In zone 2114, a list of device icons 5 for trusted ring devices with mobile phones and a list of service icons 7 for local services provided by the mobile phones can be displayed.

[0482] Among them, the trust ring device of the mobile phone is that which has established a trust relationship with the mobile phone. For example, a tablet that has established a trust relationship with the mobile phone. Therefore, the device icon list 5 includes the tablet icon 2116. And below the icon 2116 is the text information to describe the device type: My Tablet.

[0483] For example, in response to a user dragging icon 2115 to the position of icon 2116 and releasing it, or in response to a user clicking icon 2116, image 2001 can be sent to the tablet. And the projection window 2103 in interface 21b can disappear.

[0484] It is understandable that, when device icons for other devices are displayed in area 2114, in response to the user clicking on another device's icon or dragging icon 2115 to the location of another device's icon and releasing the button, the second content received by the mobile phone (image 2001) can be sent to the other device. For example, assuming that a PC icon is also displayed in area 2114 above icon 2116, in response to the user clicking on the PC icon or dragging icon 2115 to the location of the PC icon and releasing the button, image 2001 can be sent from the mobile phone to the PC. For simplicity, these examples will not be shown here.

[0485] In addition, button 2117 is displayed around my tablet. Button 2117 can be used to trigger the service entry point of the tablet displayed on the phone.

[0486] The native services provided by the mobile phone can be based on images received by the phone. For example, the native services provided by the mobile phone include: YOYO Assistant, Favorites, Social Applications, Shopping Applications, Calendar Creation, and Navigation, etc.

[0487] Correspondingly, the service icon list 7 (icons of native services provided by the phone) includes: YOYO Assistant icon 2109, Favorites icon 2110, Social Application 1 icon 2111, Shopping Application icon 2112, Schedule creation icon 2113, and Navigation icon 2114.

[0488] Furthermore, in area 2105, the names or descriptions of each service are displayed around the service icons in the service icon list 7. For example, YOYO Assistant is below icon 2109, Favorites Space is below icon 2110, Send to a Friend is below icon 2111, Instant Purchase is below icon 2112, Create Schedule is below icon 2113, and Navigation is below icon 2114.

[0489] In response to the user clicking the target service icon in the service list 7, or in response to the user dragging icon 2106 to the target service icon in the service list 7 and releasing it, the projection screen 2106 can display the forehead protector corresponding to the target service.

[0490] For example, suppose the target service icon is social application 1 in service list 7. In response to the user clicking icon 2120, or in response to the user dragging icon 2115 to the position of icon 2120, the tablet can display the interface shown in Figure 22.

[0491] As shown in Figure 22, the difference from interface 21b lies in the content displayed in the projection screen 2106. In the interface shown in Figure 22, the content displayed in projection screen 2106 can be understood as projection of the phone's chat interface. Furthermore, projection screen 2106 includes the icon 2201 corresponding to the image 2001 sent to a friend via social application 1.

[0492] As can be seen, by operating the tablet, the user can send image 2001 from social application 4 to social application 1 on the phone. On the one hand, the user doesn't need to save image 2001 and then search for it in the tablet's gallery or file management application; instead, they can directly operate on image 2001 within the interface of social application 4 displayed on the tablet, making the operation process simple.

[0493] On the other hand, by operating the tablet, image 2001 can be directly sent to the mobile phone's social application 1. This means the user doesn't need to search for the received image 2001 in the phone's gallery or file management application and then send it to a friend via social application 1. This makes sending the second content (image 2001) to the receiving end (mobile phone) more efficient, thus improving the user experience.

[0494] The above describes the tablet's display interface when the tablet successfully projects the phone's screen.

[0495] In some possible implementations, the tablet may fail to project the phone's display.

[0496] In scenario one, the tablet failed to project the phone's screen, but the phone was able to successfully launch the Anywhere Door.

[0497] In scenario two, the tablet failed to successfully project the phone's screen, and the phone failed to launch the "Anywhere Door" feature, resulting in a cross-device service interruption.

[0498] In scenario one, the tablet displays different interfaces when the screen is locked and unlocked.

[0499] In one example, when the tablet displays interface 21a, in response to the user dragging icon 2002 to the position of icon 2101 (and then releasing the finger), the tablet switches from interface 21a to interface 13b; when the tablet is in an unlocked state and the tablet has not successfully cast the screen to the phone, the tablet can switch from interface 13b to the interface shown in Figure 23.

[0500] As shown in Figure 23, the interface includes card 2301. Card 2301 includes icon 2302, icon 2304, and text information.

[0501] Icon 2302 can be interpreted as a "doorway" symbol, indicating that the tablet transmits second content to the phone's service via the doorway. Icon 2303 indicates that the second content has been transmitted to the phone, and the phone can successfully activate the doorway. The text information in card 2301 includes: "Cross-device service ready, please continue using your phone." This text information is used to prompt the user that the tablet has not successfully projected the phone's display interface and that further operation on the phone is required to send the second content to the service provided by the phone.

[0502] It should be noted that in the above examples, the tablet's failure to successfully project the phone's display could be due to the phone being locked. In this case, in response to the user unlocking the phone, the tablet can switch from the interface shown in Figure 23 to interface 21b shown in Figure 21. That is, in response to the user unlocking the phone, the phone unlocks and can display the interface corresponding to any door opening (similar to the projection screen 2106 in interface 21b); and the tablet can successfully project the phone's display (displaying interface 21b).

[0503] In another example, when the tablet displays interface 21a, in response to the user dragging icon 2002 to the position of icon 2101 (and then releasing the finger), the tablet switches from interface 21a to interface 13b; in response to the user's screen lock operation, the tablet can switch from interface 13b to interface 15a; when the tablet is in a locked state and the tablet has not successfully cast the screen to the phone, the tablet can switch from interface 15a to lock screen interface 1. The difference between lock screen interface 1 and interface 15a is that the text information in card 1501 is switched to "Cross-device service ready, please continue with your phone" to prompt the user to continue with their phone.

[0504] It should be noted that in the above example, the tablet's failure to successfully project the phone's display could be due to the phone being locked. In this case, in response to the user unlocking the phone, the phone can display the interface corresponding to the door opening (similar to the projection screen 2106 in interface 21b), and the tablet can also switch from lock screen interface 1 to interface 15b (the lock screen state indicates that cross-device services are ready); in response to the user unlocking the tablet, the tablet can switch from interface 15b to interface 21b. That is, in response to the user unlocking the tablet, the tablet can successfully project the phone's display (displaying interface 21b).

[0505] Furthermore, when the phone is locked, and the tablet begins transmitting second content to the phone via the "Anywhere Door" (Figure 2001), the phone can display interface 12a as shown in Figure 12. Upon successful activation of the "Anywhere Door," the phone switches from interface 12a to interface 12b, or from interface 12a to an interface similar to interface 12b, the difference being that the text information in card 1204 can be replaced with "Cross-device service ready," thus informing the user of the progress of the cross-device content transmission.

[0506] Furthermore, when the phone is not locked, and the tablet begins transmitting second content to the phone via the "Anywhere Door" (Figure 2001), the phone can display interface 11a as shown in Figure 11. Upon successful activation of the "Anywhere Door," the phone switches from interface 11a to interface 11b, or from interface 11a to an interface similar to interface 11b, where the text information in card 1104 can be replaced with "Cross-device service ready." This serves to inform the user of the progress of the cross-device content transmission.

[0507] In scenario two, the phone failed to successfully launch the "Anywhere Door," causing cross-device content transfer to be unable to continue.

[0508] For example, when the tablet displays interface 21a, in response to the user dragging icon 2002 to the position of icon 2101 (and then releasing the finger), the tablet switches from interface 21a to interface 13b; in response to the phone failing to successfully launch the "Anywhere Door" feature, the tablet switches from interface 13b to interface 14a as shown in Figure 14. The card 1401 in interface 14a can also be switched to the prompt bar 1404 shown in 14b. Interfaces 13b and 14a can be referred to in the description above, and will not be repeated here.

[0509] The above describes the service transfer methods for the second content from a mobile phone to a tablet (first method) and from a tablet to a mobile phone (second method). It should be noted that the embodiments of this application do not limit the device types of the sending and receiving ends to be different. In some possible implementations, the device types of the sending and receiving ends can also be the same.

[0510] The following explanation, using Figures 24 and 25 as examples, describes how the second content is transferred from the sending end to the receiving end, with both the sending and receiving ends being mobile phones and the second content being document 1.

[0511] For ease of distinction, the sending end will be referred to as mobile phone A, and the receiving end as mobile phone B.

[0512] When the chat interface (interface 2a) of the social application 1 is displayed on mobile phone A, in response to the user's input operation 1 on the icon 201 of document 1 (without releasing the finger at this time), mobile phone A switches from interface 2a to interface 2b; in response to the user's input operation 2 on dragging icon 202 to the edge of the screen (without releasing the finger at this time), mobile phone A can switch from interface 2b to interface 24a as shown in Figure 24.

[0513] Interface 24a is similar to interface 2c, except for the list of device icons and the list of service icons.

[0514] As shown in interface 24a, area 204 displays a list 6 of device icons for the trusted ring device of mobile phone A, and a list 8 of service icons for the local services of mobile phone A.

[0515] The device icon list 6 includes PC icon 2401, tablet icon 2401, and mobile phone B icon 2403. That is, in addition to the PC and tablet, mobile phone B has also established a trust relationship with mobile phone A. For example, the trust ring includes mobile phone A, mobile phone B, PC, and tablet.

[0516] Each device icon is also surrounded by text information describing the device type. For example, PC is below icon 2401, My Tablet is below icon 2402, and Phone B is below icon 2403.

[0517] Furthermore, button 2404 is included around the text information describing the device type. Button 2404 can be used to trigger mobile phone A to display the service entry for the trust ring device.

[0518] The native services of mobile phone A are services pushed by mobile phone A based on document 1. For example, the native services of mobile phone A include: YOYO Assistant, Favorites, Social Application 1, Social Application 2, Create Schedule, Navigation, and Social Application 3.

[0519] Correspondingly, the service icon list 8 includes: YOYO Assistant icon 2405, Favorites icon 2406, Social Application 1 icon 2407, Social Application 2 icon 2408, Create Schedule icon 2409, Navigation icon 2410, and Social Application 3 icon 2411.

[0520] Furthermore, the service icon is surrounded by the name or description of each service. See interface 24a for details; further explanation is omitted here.

[0521] When mobile phone A displays interface 24a, in response to the user dragging icon 202 to any device icon in the device icon list 6 and releasing it, document 1 can be transferred from mobile phone A to the device indicated by that device icon. For example, in response to the user dragging icon 202 to icon 2403 and releasing it, document 1 can be transferred from mobile phone A to mobile phone B. This process is similar to the process of transferring document 1 from a mobile phone to a tablet shown in Figure 2.

[0522] Alternatively, Document 1 can be transferred to the services of the Trust Ring device in the following ways.

[0523] When mobile phone A displays interface 24a, in response to the user dragging icon 202 to icon 2403 and keeping icon 202 at the position of icon 2403 for more than duration 6 (without releasing the button), mobile phone A switches from interface 24a to interface 24b; or, in response to the user dragging icon 202 to the position of button 2404, mobile phone A switches from interface 24a to interface 24b.

[0524] As shown in interface 24b, compared to interface 24a, area 204 also displays an icon for the service entry of mobile phone B: icon 2412. Icon 2412 is also displayed around it. Icon 2413 can be a thumbnail of mobile phone B.

[0525] Furthermore, since interface 24b displays a service entry icon for mobile phone B compared to interface 24a, the number of service icons displayed in area 204 is reduced. That is, icon 2411 is not displayed in area 204 of interface 24a.

[0526] When interface 24b is displayed on phone A, in response to the user dragging icon 202 to at least the position of icon 2412 and releasing it, phone A transmits document 1 to phone B. Furthermore, in response to further user actions on phone B, document 1 can be transferred to phone B's services. The subsequent transfer process of document 1 within phone B's services can be found in the description of the first method in the second scheme, and will not be repeated here.

[0527] It should be noted that the device icons and service icons shown in the interfaces of this application's embodiments are merely examples. More services can be promoted by the sending or receiving end. This application does not impose specific limitations on this.

[0528] For example, when there are many trust ring devices, the list of device icons shown in each interface may not display all the icons of the trust ring devices. For instance, referring to interface 24a in Figure 24, interface 24a displays a portion of icon 2401. That is, for mobile phone A, the trust ring devices include PC, tablet, and mobile phone B, and the trust ring devices may include even more.

[0529] Assuming the trust ring device also includes mobile phone C, as shown in Figure 25, in response to the user dragging icon 202 to the top of the screen (without releasing it), the device icon list 6 and service icon list 8 displayed in area 204 can slide down so that mobile phone A can display the icon of mobile phone C in area 204.

[0530] Similarly, when a large number of services are pushed on the sending or receiving end, the list of service icons displayed on each interface may not show all the service icons.

[0531] For example, referring to interface 24b in Figure 24, compared to interface 24a, interface 24b does not include the icon 2411 of social application 3. That is, for mobile phone A, social application 3 is still pushed based on document 1, but the icon of social application 3 is not displayed in the service icon list of interface 24b. In response to the user dragging icon 202 to the bottom of the screen (without releasing it), the device icon list 6 and service icon list 8 displayed in area 204 can slide upwards so that mobile phone A can display the icon 2411 of social application 3 in area 204.

[0532] It should be understood that, in the embodiments of this application, when the terminal device fails to fully display the device icon (or service icon), the interface displayed by the terminal device may show a portion of the content of a device icon (or service icon) to prompt the user that there are still undisplayed device icons (or service icons). Alternatively, the interface displayed by the terminal device may not include a portion of the content of the device icon (or service icon). This application does not impose specific limitations on this.

[0533] In the solutions shown above, the example described is that the user drags the target content (first content or second content) to the edge of the screen to start any door.

[0534] In some possible implementations, the terminal device can also launch the "Anywhere Door" in other ways, such as by selecting with a knuckle. The following explanation, using a mobile phone as the sending end, illustrates the method of launching the "Anywhere Door" by selecting with a knuckle, with reference to Figures 26 and 27.

[0535] As shown in interface 26a of Figure 26, assuming that before activating the "Anywhere Door" feature, the phone displays the interface of a short video application. In response to the user's action of circling the text information 2601 "Art Exhibition..." with their knuckle, the phone can recognize the content around the circled area, confirm that the selected content is the text information 2601, and then the phone can switch from interface 26a to interface 26b.

[0536] The action of selecting a portion of the interface by using the user's knuckle is called knuckle selection. As shown in interface 26a, the path selected by the knuckle can be an irregular curve, such as curve 2602.

[0537] Furthermore, the content selected by the knuckle can be all the text information 2601; or, the content selected by the knuckle can be part of the text information 2601. For example, if "art exhibition" is selected by the knuckle selection operation, and the remaining text information "2024.3.23..." is not selected, the mobile phone can also recognize all the text information 2601 based on the selected part of the text information.

[0538] It should be noted that "all text information" mentioned above does not necessarily refer to all text information on the phone's display screen, but rather to the text information adjacent to the selected portion. For example, considering interface 26a, "A Day at the Art Museum" is not adjacent to text information 2601. Therefore, if the phone selects part or all of the text information 2601 based on the path selected by the knuckle, it can recognize all of the text information 2601, but may not recognize "A Day at the Art Museum".

[0539] In response to a knuckle selection action, the phone can launch any door. For example, as shown in interface 26b, interface 26b includes an image 2603, a region 2604, and a selection area 2605 that covers the image 2603.

[0540] It should be understood that image 2603 is similar to image 803 in interface 8c, and the content displayed in area 2604 is similar to the content displayed in area 804 of interface 8c. Please refer to the description above, which will not be repeated here.

[0541] The text within the selected area 2605 can be in a selected state, allowing users to perform operations such as copying the text within the selected area 2605.

[0542] It should be understood that the text within the selected area 2605 can be horizontal. Alternatively, the text within the selected area 2605 can also be slanted, like the rest of the content in image 2603. This application does not impose any specific limitations on this.

[0543] When the phone displays interface 26b, in response to the user clicking button 818, or in response to the user dragging text information from the selected area 2605 to the button 818 position and not releasing it, the service pushed by the trusted ring device (e.g., a tablet) can be displayed in area 2604. The interface displayed on the phone at this time is similar to interface 8d in Figure 8, except that the interface displayed on the phone at this time does not include icon 802, and the selected area 2605 is covered on image 803.

[0544] Furthermore, in response to the user dragging the text information in the selected area 2605 to the target service icon (the service pushed by the tablet) (and then releasing the finger), or in response to the user clicking the target service icon (the service pushed by the tablet), the text information in the selected area 2605 can be transferred to the target service on the tablet. This process is similar to that shown in Figure 8, and can be referred to the description above, so it will not be repeated here.

[0545] Alternatively, when the phone displays interface 26b, in response to the user clicking button 818, the service entry of the trust ring device (e.g., a tablet) can be displayed in area 2604. The interface displayed on the phone in this case is similar to interface 10a in Figure 10, except that the interface displayed on the phone does not include icon 802, and the image 803 is covered by a selection area 2605.

[0546] Furthermore, in response to the user dragging and dropping the text information in the selected area 2605 to the service entry point on the tablet and releasing it, or in response to the user clicking the service entry point, the text information in the selected area 2605 can be transferred to the tablet. The user can then select the target service pushed by the tablet, so that the text information in the selected area 2605 flows to the target service pushed by the tablet. This process is similar to the process shown in Figures 10 to 18 (first scheme), and can be referred to the description above, which will not be repeated here.

[0547] In addition to text messages, mobile phones can also recognize one or more images based on the content selected by the knuckle.

[0548] For example, as shown in interface 27a of Figure 27, assuming that the phone displays the interface of a short video application before activating the "Anywhere Door" feature. In response to the user's action of selecting person 2701 with their knuckles, the phone can recognize the content around the selected area, determine that the selected content is person 2701, and then the phone can switch from interface 27a to interface 27b.

[0549] The content selected by the knuckle can be all or part of the target object. The phone can then identify the selected content and the surrounding area to recognize the complete target object. For example, in conjunction with interface 27a, the content selected by the knuckle can be part of a person 2701. The phone can then identify the selected part of the person 2701 and the surrounding area to recognize the complete person 2701.

[0550] Interface 27b can be understood as the interface corresponding to opening the "Anywhere Door". Interface 27b is similar to interface 8c in Figure 8. The difference is that, since the phone activates the "Anywhere Door" based on a knuckle selection operation, interface 27b can display a selection box 2703 to show the user the currently selected area.

[0551] The selected area 2703 includes the complete target object recognized by the mobile phone, that is, the complete person 2703. Furthermore, the area selected by the selected area 2703 can be understood as an image extracted by the mobile phone based on the selected content. Subsequently, based on user operations, the mobile phone can transmit this image to the receiving end, and the image can also be transferred to the receiving end's service. For details, please refer to the description above; it will not be repeated here.

[0552] It should be noted that when the sending end is a tablet or other device type, the "Anywhere Door" can also be launched by selecting with a knuckle. The process of launching the "Anywhere Door" using a tablet or other device by selecting with a knuckle is similar to that shown in Figure 26 or Figure 27, as described above, and will not be repeated here.

[0553] In this embodiment of the application, during the process of the second content flowing from the sending end to the receiving end, even if the second content is not text information, it can still be transmitted to the file management application on the receiving end. That is, the user can find the second content in the file management application on the receiving end.

[0554] Furthermore, when the second content is text information, it cannot be stored in the receiving end's file management application. That is, text information can be transferred from the sending end to the receiving end's service, but it cannot be sent to the receiving end's file management application. For example, referring to interface 8d in Figure 8, in response to the user dragging icon 802 to the position of icon 806 and releasing it, the mobile phone can display a prompt message informing the user that text information cannot be transmitted.

[0555] It should be noted that, in the embodiments of this application, switching from one interface to another at the sending end (or receiving end) does not limit the display of other interfaces during the transition from one interface to another. During the process of switching from one interface to another at the sending end (or receiving end), other interfaces can still be displayed, for example, through display animations. It should also be noted that the embodiments shown in this application can be executed by an electronic device (sending end or receiving end), or by a chip, chip system, or processor that supports cross-device content transmission methods, or by a logic module or software capable of implementing all or part of the functions of an electronic device. This application does not impose specific limitations in this regard.

[0556] It should be understood that the sequence numbers in the above embodiments do not imply the order of execution. The execution order of each process should be determined by its function and internal logic.

[0557] The cross-device content transmission method according to the embodiments of this application has been described above. The apparatus for performing the above method provided in the embodiments of this application is described below. Those skilled in the art will understand that the methods and apparatus can be combined with and referenced in each other, and the related apparatus provided in the embodiments of this application can perform the steps in the above method.

[0558] Figure 28 is a schematic diagram of the structure of the electronic device 2800 provided in an embodiment of this application. As shown in Figure 28, the electronic device 2800 may include a processor 2810, an external memory interface 2820, an internal memory 2821, a universal serial bus (USB) interface 2830, a charging management module 2840, a power management module 2841, a battery 2842, an antenna 1, an antenna 2, a mobile communication module 2850, a wireless communication module 2860, an audio module 2870, a sensor module 2880, a button 2890, an indicator 2892, a camera 2893, and a display screen 2894, etc.

[0559] The audio module 2870 may include, but is not limited to, a speaker, a receiver, a microphone, and a headphone jack.

[0560] The sensor module 2880 may include, but is not limited to, one or more of the following sensors: pressure sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, and bone conduction sensor, etc.

[0561] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 2800. In other embodiments of this application, the electronic device 2800 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.

[0562] Processor 2810 may include one or more processing units, such as 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). Optionally, processor 2810 may also include memory for storing instructions and data. The different processing units may be independent devices or integrated into one or more processors.

[0563] The wireless communication function of electronic device 2800 can be implemented through antenna 1, antenna 2, mobile communication module 2850, wireless communication module 2860, modem processor and baseband processor, etc.

[0564] Electronic device 2800 implements display functions through a GPU, display screen 2894, and application processor. The GPU is a microprocessor for image processing, connecting the display screen 2894 and the application processor. The GPU performs mathematical and geometric calculations for graphics rendering. Processor 2828 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0565] The display screen 2894 is used to display images, videos, etc. In some embodiments, the electronic device 2800 may include one or N display screens 2894, where N is a positive integer greater than 1.

[0566] For example, display screen 2894 can display the interfaces described in the above method embodiments.

[0567] The external memory interface 2820 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 2800. The internal memory 2821 can be used to store computer executable program code, which includes instructions.

[0568] This application also provides a communication system, which includes a first device and a second device. The first device can be used to perform the steps performed by the sending end in the above method embodiments; the second device can be used to perform the steps performed by the receiving end in the above method embodiments.

[0569] The cross-device content transmission method provided in this application can be applied to electronic devices with communication functions. Electronic devices include terminal devices, and the specific device form of the terminal device can be referred to the above-described related information, which will not be repeated here.

[0570] This application provides a terminal device, which includes a processor and a memory; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory, causing the terminal device to perform the above-described method.

[0571] This application provides a chip. The chip includes a processor, which is used to call a computer program in memory to execute the technical solutions in the above embodiments. Its implementation principle and technical effects are similar to those in the related embodiments described above, and will not be repeated here.

[0572] This application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, it implements the methods described above. The methods described in the above embodiments can be implemented wholly or partially by software, hardware, firmware, or any combination thereof. If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted over the computer-readable medium. The computer-readable medium can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium accessible by a computer.

[0573] In one possible implementation, a computer-readable medium may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage or other magnetic storage devices, or any other medium targeted to carry or to store the required program code in the form of instructions or data structures, and accessible by a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disks and optical discs include optical discs, laser discs, optical discs, Digital Versatile Discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0574] This application provides a computer program product, which includes a computer program that, when run, causes a computer to perform the above-described method.

[0575] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable device to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing device, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0576] The above specific embodiments further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of the present invention should be included within the scope of protection of the present invention.

Claims

A method for cross-device content transmission, characterized in that, An application in a communication system, the communication system including a first device and a second device, the method comprising: the first device displaying a first interface, the first interface including first content, the first content including one or more of text, images, videos, audio, files, web pages, or links; responding to a first operation by a user on the first content, the first device displaying a second interface, the second interface including a first area and a second area, the first area including a third interface corresponding to the first interface, the second area including a first service icon and an icon of the second device, the first service icon indicating a first service provided by the first device, and the icon of the second device indicating the second device; upon receiving a second operation by the user on the first service icon, the first device displaying a fourth interface, the fourth interface including a screen corresponding to the first service; upon receiving a third operation by the user on the icon of the second device, the first device sending the first content to the second device; upon receiving a fourth operation by the user on the icon of the second device, the first device displaying a second service icon, the second service icon indicating a service provided by the second device; and upon the user selecting the second service icon, the first device transferring the first content to the second service of the second device. The method according to claim 1, characterized in that, After receiving a third operation from the user on the icon of the second device, the method further includes: the first device displaying a first prompt bar on the first interface, the first prompt bar indicating the transmission progress of the first content; after the first content is transmitted, the first device switching the first prompt bar to a second prompt bar, the second prompt bar indicating that the first content has been transmitted. The method according to claim 1 or 2, characterized in that, The method further includes: after the second device starts receiving the first content, the second device displays a third prompt bar, which is used to indicate the transmission progress of the first content; after the second device successfully receives the first content, the second device switches the third prompt bar to a fourth prompt bar, which is used to indicate that the first content transmission is complete. The method according to any one of claims 1 to 3, characterized in that, The first interface further includes second content, which may be the same as or different from the first content; the method further includes: in response to a fifth operation by the user on the second content, the first device displays a fifth interface, the fifth interface including the third area and a fourth area, the third area including the third interface, the fourth area including an icon of the third device, the icon of the third device being used to indicate the third device; when a sixth operation by the user on the icon of the third device is received, the first device displays a first prompt message, the first prompt message being used to indicate that cross-device transmission of the second content is not supported. The method according to any one of claims 1 to 4, characterized in that, The second service icon is used to indicate the second service of the second device; The step of transferring the first content to the second service of the second device after the user selects the second service icon includes: after the user selects the second service icon, the first device sends the first content to the second device so that the second device transfers the first content to the second service, and the first device displays a first card on the first interface, the first card being used to indicate the cross-device service preparation process; The first device switches the first card to a second card, which indicates that the cross-device service is ready and indicates that operation can continue on the second device. The method according to claim 5, characterized in that, The method further includes: after the second device receives the first content from the first device, the second device displays a sixth interface, the sixth interface including the screen corresponding to the second service. The method according to any one of claims 1 to 4, characterized in that, The step of transferring the first content to the second service of the second device after the user selects the second service icon includes: after the user selects the second service icon, the first device sends the first content to the second device so that the second device transfers the first content to the second service, and the first device displays a third card on the first interface, the third card being used to indicate the cross-device service preparation process; the first device switches the third card to a fourth card, the fourth card being used to indicate that the cross-device service is ready and to indicate that the operation continues on the second device. The method according to claim 7, characterized in that, The method further includes: before the second device receives the first content from the first device, the second device displays a seventh interface; after the second device receives the first content from the first device, the second device displays an eighth interface, the eighth interface including a fifth area, a sixth area, and a first content icon, the fifth area including a ninth interface corresponding to the seventh interface, the sixth area including a third service icon, the third service icon being used to indicate the second service, and the first content icon being used to indicate the first content; when a seventh operation by the user on the third service icon is received, the second device displays a tenth interface, the tenth interface including the screen corresponding to the second service. The method according to claim 8, characterized in that, Before the second device displays the eighth interface, the method further includes: after the second device starts receiving the first content from the first device, the second device displays a fifth card on the seventh interface, the fifth card being used to indicate that the cross-device service is ready; the second device switches the fifth card to a sixth card, the sixth card being used to indicate that the cross-device service is ready. The method according to any one of claims 7 to 9, characterized in that, When the second device receives the first content from the first device, the second device is in a locked screen state; The second device displays an eighth interface, including: the second device displays a first notification on the lock screen, the first notification being used to indicate that cross-device services are ready; When the second device displays the first notification, it receives the user's eighth operation, unlocks the second device, and displays the eighth interface. The method according to claim 7, characterized in that, The method further includes: after the second device receives the first content from the first device, the second device displays a seventh card, the seventh card being used to indicate a cross-device service interruption. The method according to any one of claims 1 to 4, characterized in that, The step of transferring the first content to the second service of the second device after the user selects the second service icon includes: after the user selects the second service icon, the first device sends the first content to the second device; the first device displays a first projection window, the first projection window includes a first projection screen, the first projection screen includes a seventh area, an eighth area and a first content icon, the seventh area includes a twelfth interface corresponding to the eleventh interface displayed before the second device receives the first content, the eighth area includes a fourth service icon for indicating the second service, and the first content icon is used to indicate the first content; after receiving a ninth operation from the user on the fourth service icon, the first projection screen displayed in the first projection window switches to the screen corresponding to the second service. The method according to claim 12, characterized in that, Before the first device displays the first projection window, the method further includes: when the user selects the second service icon, the first device displays an eighth card on the first interface, the eighth card being used to indicate the cross-device service preparation process; the first device switches the eighth card to a ninth card, the ninth card being used to indicate that the cross-device service is ready; the first device displays the first projection window, including: when the display duration of the ninth card exceeds a first preset duration, or when a tenth operation is received on the ninth card, the ninth card disappears, and the first device displays the first projection window. The method according to claim 12 or 13 is characterized in that, The eighth area also includes an icon for the fourth device; the method further includes: when the user selects the icon for the fourth device, the first screen projection screen displayed in the first projection window switches to the eleventh interface, and the first device instructs the second device to send the first content to the third device. The method according to any one of claims 1 to 4, characterized in that, The step of transferring the first content to the second service of the second device after the user selects the second service icon includes: after the user selects the second service icon, the first device sends the first content to the second device; the first device displays a tenth card, which is used to indicate that the cross-device service is ready and to indicate to continue the operation on the second device, so that the second device transfers the first content to the second service based on the user's operation of selecting the fifth service icon, which is used to indicate the second service. The method according to any one of claims 1 to 15, characterized in that, The second interface also includes a first icon for indicating the first content, the first operation being dragging the first icon to the edge of the first device screen without releasing it, the fourth operation being dragging the first icon to the icon position of the second device without releasing it; or, the first operation being selecting the first content with a knuckle. An electronic device, characterized in that, The electronic device includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, and the one or more processors invoking the computer instructions to cause the electronic device to perform the method as described in any one of claims 1 to 16. A communication system, characterized in that, The communication system includes a first device and a second device, wherein the first device is configured to perform the steps performed by the first device in the method as described in any one of claims 1 to 16; and the second device is configured to perform the steps performed by the second device in the method as described in any one of claims 1 to 16. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 16. A computer program product, characterized in that, The computer program product includes computer program code that, when run on an electronic device, causes the electronic device to perform the method as described in any one of claims 1 to 16.

Images