A terminal device interaction method and apparatus

Abstract

Embodiments of the present application provide a terminal device interaction method and device. In the method, a first terminal device receives a first sharing operation for a first public APP, and transmits a first sharing instruction based on the first sharing operation, and then receives and displays information of first data transmitted by a second terminal device; after receiving a second sharing operation for information of a first target data, the first terminal device transmits a second sharing instruction, the second sharing instruction being used to instruct to share the first target data; and the first terminal device receives the first target data transmitted by the second terminal device based on the second sharing instruction. In the scheme, a user only needs to perform a first sharing operation on a first public APP displayed by the first terminal device, and perform a second sharing operation on information of first data displayed by the first terminal device, so that the first terminal device can obtain first target data in the second terminal device, and the operation is simple and the efficiency of data interaction is high.

Description

Technical Field

[0001] This application relates to the field of terminal equipment technology, specifically to a terminal equipment interaction method and apparatus. Background Technology

[0002] With the development of interaction and communication technologies for terminal devices, multi-screen scenarios between multiple terminal devices are becoming increasingly diverse. For example, multi-screen collaboration between various terminal devices such as mobile phones, tablets, and televisions is now possible. Through multi-screen collaboration technology, the display screen of one terminal device can show the interface of another terminal device, meeting the user's need to view the interface of the other terminal device.

[0003] Furthermore, in some scenarios, a terminal device needs to interact with other terminal devices to share data across different devices. To meet this need, a method for terminal device interaction is provided. The two terminal devices interacting using this method need to have the same application (APP) installed, and the shared data is from that APP. Let's define these two terminal devices as a first terminal device and a second terminal device, and the first terminal device needs to obtain data from the second terminal device. In this method, the second terminal device needs to log in to a cloud storage software using a specific account, upload the data to be shared to the cloud storage software, and then the first terminal device logs in to the cloud storage software using the same account and downloads the data to be shared.

[0004] However, this method requires two terminal devices that need to interact with the data to log in to the cloud storage software sequentially using the same account. Furthermore, after logging in, the first terminal device needs to find the data to be shared and upload it, while the second terminal device needs to search for and download the data from the software after logging in. The operation is cumbersome and complex, and the efficiency of data interaction is low. Summary of the Invention

[0005] Existing terminal device interaction technologies suffer from cumbersome and complex operations, as well as low data exchange efficiency. To address this issue, embodiments of this application provide a terminal device interaction method and apparatus.

[0006] In a first aspect, embodiments of this application disclose a terminal device interaction method, including:

[0007] The first terminal device receives a first sharing operation for the first public application APP, wherein the APP installed on both the first terminal device and the second terminal device is a public APP;

[0008] Based on the first sharing operation, the first terminal device transmits a first sharing instruction, which is used to indicate that the first terminal device needs to share the data of the first public APP in the second terminal device;

[0009] The first terminal device receives and displays information about the first data transmitted by the second terminal device, wherein the first data is data that can be shared with the first terminal device in the first public APP of the second terminal device.

[0010] After receiving the second sharing operation for the first target data, the first terminal device transmits the second sharing instruction, where the first target data is the data in the first data, and the second sharing instruction is used to indicate sharing the first target data;

[0011] The first terminal device receives the first target data transmitted by the second terminal device based on the second shared instruction.

[0012] With the above solution, users only need to perform a first sharing operation on the first public APP displayed on the first terminal device and a second sharing operation on the information of the first data displayed on the first terminal device to enable the first terminal device to obtain the first target data in the second terminal device and realize data interaction. The operation is relatively simple and the data interaction efficiency is high.

[0013] An alternative design also includes:

[0014] The first terminal device identifies the public apps within its installed apps;

[0015] The first terminal device prominently displays the icon of the public APP included on its own screen.

[0016] Through the above scheme, the first terminal device identifies the common APP and highlights it on its own screen, thereby making it easier for users of the first terminal device to identify the common APP and the different APPs. Furthermore, it facilitates users to perform corresponding sharing operations on the identified common APP, thereby facilitating data sharing between different terminal devices and effectively improving the user experience.

[0017] In one optional design, the first terminal device determines the public apps within its installed apps, including:

[0018] The first terminal device obtains the desktop layout data of the second terminal device, and the desktop layout data of the second terminal device is used to indicate the installation package of the APP installed on the second terminal device;

[0019] If the first terminal device and the second terminal device have the same operating system, the first terminal device determines the common APP based on the name of the installation package of the APP it has installed and the name of the installation package of the APP installed on the second terminal device, wherein the APP indicated by the installation package with the same name is the common APP.

[0020] In one optional design, the first sharing operation includes an operation on a first icon, which is the icon of a first public APP installed in the first terminal device;

[0021] or,

[0022] The screen of the first terminal device includes a first area and a second area. The first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area. The first sharing operation includes an operation on a second icon, which is the icon of the first public APP in the first area.

[0023] In one optional design, the operation on the second icon is a drag operation on the second icon, which is used to drag the first icon to the second area.

[0024] An alternative design also includes:

[0025] After receiving the first sharing operation, the first terminal device displays a first selection box, which is used to indicate whether to share the data of the second terminal device to the first terminal device.

[0026] After receiving confirmation of the first selection box, the first terminal device then transmits the first sharing instruction.

[0027] With the above solution, the first terminal device transmits the first sharing instruction after receiving the confirmation operation for the first selection box, thereby effectively avoiding accidental operation.

[0028] An alternative design also includes:

[0029] The first terminal device receives a third sharing operation for the second public APP, the third sharing operation being used to instruct the sharing of the data of the second public APP of the first terminal device to the second terminal device;

[0030] The first terminal device displays information about the second data of the second public APP installed on itself. The second data is data in the second public APP of the first terminal device that can be shared with the second terminal device.

[0031] After receiving the fourth sharing operation, the first terminal device transmits the second target data indicated by the fourth sharing operation to the second terminal device, wherein the second target data is part of the second data.

[0032] Through the above scheme, the first terminal device can also transmit the second target data of the second public APP installed on itself to the second terminal device, thereby realizing the sharing of the second target data between the first terminal device and the second terminal device.

[0033] In one alternative design, the third sharing operation includes an operation on a third icon, which is the icon of a second public APP installed on the first terminal device.

[0034] In one optional design, if the screen of the first terminal device includes a first area and a second area, the first area is the area for displaying the interface of the second terminal device, and the second area is the area outside the first area, the third sharing operation is a drag operation on the third icon, and the drag operation on the third icon is used to drag the third icon to the first area.

[0035] An alternative design also includes:

[0036] If the screen of the first terminal device includes a first area and a second area, the first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area of ​​the screen, after receiving a selection operation for the third public APP in the first area, the first terminal device displays a second selection box, which is used to indicate whether to open the third public APP installed on the first terminal device.

[0037] After receiving confirmation for the second selection box, the first terminal device runs the third public APP that it has installed.

[0038] Through the above scheme, the first terminal device can run the third public APP it has installed after receiving the selection operation for the third public APP in the first area, thereby improving the user experience.

[0039] An alternative design also includes:

[0040] After receiving a negative operation for the second selection box, the first terminal device transmits a first running instruction to the second terminal device. The first running instruction is used to instruct the second terminal device to run the third public APP that it has installed.

[0041] An alternative design also includes:

[0042] After receiving the first target data, the first terminal device synchronizes the first target data to its own first public APP.

[0043] Through the above scheme, the first terminal device can use and view the first target data through the first public APP installed on itself.

[0044] Secondly, embodiments of this application provide a terminal device interaction method, including:

[0045] The second terminal device receives a first sharing instruction transmitted by the first terminal device. The first sharing instruction is used to indicate that the first terminal device needs to share the data of a first public APP in the second terminal device. The APP installed on both the first terminal device and the second terminal device is a public APP.

[0046] The second terminal device transmits information about the first data corresponding to the first sharing instruction, wherein the first data is data in the first public APP of the second terminal device that can be shared with the first terminal device;

[0047] The second terminal device receives a second sharing instruction, which instructs the first terminal device to share the first target data in the first data.

[0048] The second terminal device transmits the first target data.

[0049] An alternative design also includes:

[0050] The second terminal device identifies the public apps within the apps it has installed;

[0051] The second terminal device prominently displays the icon of the public APP included on its own screen.

[0052] An alternative design also includes:

[0053] The second terminal device receives second target data, which is a type of second data. The second data is data that can be shared with the second terminal device in the second public APP of the first terminal device.

[0054] An alternative design also includes:

[0055] After receiving the first running instruction, the second terminal device runs the third public APP that it has installed.

[0056] Thirdly, embodiments of this application provide a terminal device interaction apparatus, applied to a first terminal device, comprising:

[0057] Transceiver interface and processor;

[0058] The transceiver interface is used to receive a first sharing operation for a first public application APP, wherein the APP installed on both the first terminal device and the second terminal device is a public APP.

[0059] The processor is configured to determine a first sharing instruction based on the first sharing operation, wherein the first sharing instruction is configured to instruct the first terminal device to share data of the first public APP in the second terminal device;

[0060] The transceiver interface is also used to transmit the first sharing instruction and receive information about the first data transmitted by the second terminal device, wherein the first data is data that can be shared with the first terminal device in the first public APP of the second terminal device.

[0061] The processor is also configured to display information from the first data;

[0062] The transceiver interface is further configured to, after receiving a second sharing operation for information on the first target data, transmit a second sharing instruction, wherein the first target data is data in the first data, the second sharing instruction is used to indicate sharing the first target data, and receive the first target data transmitted by the second terminal device based on the second sharing instruction.

[0063] In an alternative design, the processor is further configured to identify public apps within its installed apps and highlight the icons of the public apps included on its screen.

[0064] In one optional design, the first sharing operation includes an operation on a first icon, which is the icon of a first public APP installed in the first terminal device;

[0065] or,

[0066] The screen of the first terminal device includes a first area and a second area. The first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area. The first sharing operation includes an operation on a second icon, which is the icon of the first public APP in the first area.

[0067] In an optional design, the transceiver interface is further configured to receive a third sharing operation for the second public APP, the third sharing operation being configured to instruct the sharing of data of the second public APP of the first terminal device to the second terminal device;

[0068] The processor is also configured to display information about the second data of the second public APP installed on itself, wherein the second data is data in the second public APP of the first terminal device that can be shared with the second terminal device.

[0069] The transceiver interface is further configured to, upon receiving the fourth sharing operation, transmit the second target data indicated by the fourth sharing operation to the second terminal device, wherein the second target data is part of the second data.

[0070] Fourthly, embodiments of this application provide a terminal device interaction apparatus, applied to a second terminal device, comprising:

[0071] Transceiver interface and processor;

[0072] The transceiver interface is used to receive a first sharing instruction transmitted by the first terminal device. The first sharing instruction is used to indicate that the first terminal device needs to share data of a first public APP in the second terminal device. The APP installed on both the first terminal device and the second terminal device is a public APP.

[0073] The processor is used to determine information about the first data corresponding to the first sharing instruction, wherein the first data is data that can be shared with the first terminal device in the first public APP of the second terminal device.

[0074] The transceiver interface is also used to transmit information from the first data, receive a second sharing instruction, and transmit first target data, wherein the second sharing instruction indicates that the first terminal device needs to share the first target data from the first data.

[0075] Fifthly, embodiments of this application provide a terminal device, including:

[0076] At least one processor and memory;

[0077] The memory is used to store program instructions;

[0078] The at least one processor is configured to invoke and execute program instructions stored in the memory, wherein when the processor executes the program instructions, it causes the apparatus to perform the method as described in the first aspect.

[0079] Sixthly, embodiments of this application provide a terminal device, including:

[0080] At least one processor and memory;

[0081] The memory is used to store program instructions;

[0082] The at least one processor is configured to invoke and execute program instructions stored in the memory, wherein when the processor executes the program instructions, it causes the apparatus to perform the method as described in the second aspect.

[0083] Seventhly, embodiments of this application provide a computer-readable storage medium, characterized in that,

[0084] The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in the first aspect.

[0085] Eighthly, embodiments of this application provide a computer-readable storage medium, characterized in that,

[0086] The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in the second aspect.

[0087] In a ninth aspect, embodiments of this application provide a computer program product containing instructions that, when the computer program product is run on an electronic device, cause the electronic device to perform the method described in the first aspect.

[0088] In a tenth aspect, embodiments of this application provide a computer program product containing instructions that, when the computer program product is run on an electronic device, cause the electronic device to perform the method described in the second aspect.

[0089] This application provides a terminal device interaction method and apparatus. In this method, when a first terminal device needs to share certain data from a second terminal device, the user of the first terminal device performs a first sharing operation on the first terminal device, causing the first terminal device to receive the first sharing operation for a first public APP. Then, through communication interaction between the first and second terminal devices, the screen of the first terminal device can display information about the first data, wherein the first data includes first target data that the first terminal device wishes to share. The user of the first terminal device then performs a second sharing operation, so that the first terminal device determines the first target data to be shared based on the second sharing operation. Then, through communication interaction between the first and second terminal devices, the first terminal device can obtain the first target data.

[0090] In the existing technology, if the first terminal device needs to obtain the first target data of the second terminal device, the second terminal device needs to log in to the software for cloud storage with a certain account, upload the data to be shared to the cloud storage software, and then the first terminal device logs in to the cloud storage software with the same account, and then finds and downloads the first target data. The operation is cumbersome and complicated, resulting in low efficiency of data interaction.

[0091] The method provided in this application embodiment allows users to acquire the first target data from the second terminal device simply by performing a first sharing operation on the first public APP displayed on the first terminal device and a second sharing operation on the information of the first data displayed on the first terminal device, thus achieving data interaction. Compared with existing technologies, this method requires fewer user operations, is more convenient, and consequently improves the efficiency of data interaction. Attached Figure Description

[0092] Figure 1 This is a schematic diagram of the structure of a terminal device disclosed in an embodiment of this application;

[0093] Figure 2 This is a schematic diagram illustrating the workflow of a terminal device interaction method disclosed in an embodiment of this application;

[0094] Figure 3 This is an interactive schematic diagram of a terminal device interaction method disclosed in an embodiment of this application;

[0095] Figure 4 This is a schematic diagram of an interface in the terminal device interaction method disclosed in an embodiment of this application.

[0096] Figure 5 This is another interface diagram of the terminal device interaction method disclosed in the embodiments of this application;

[0097] Figure 6(a) is a schematic diagram of another interface in the terminal device interaction method disclosed in the embodiments of this application;

[0098] Figure 6(b) is a schematic diagram of another interface in the terminal device interaction method disclosed in the embodiments of this application;

[0099] Figure 7 This is another interface diagram of the terminal device interaction method disclosed in the embodiments of this application;

[0100] Figure 8 This is a schematic diagram of the workflow of another terminal device interaction method disclosed in the embodiments of this application;

[0101] Figure 9 This is a schematic diagram of the workflow of another terminal device interaction method disclosed in the embodiments of this application;

[0102] Figure 10 This is a schematic diagram of the structure of a terminal device interaction device disclosed in an embodiment of this application;

[0103] Figure 11 This is a schematic diagram of the structure of a terminal device disclosed in an embodiment of this application. Detailed Implementation

[0104] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0105] The terminology used in the following embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, “at least one” and “one or more” refer to one, two, or more than two. The term “and / or” is used to describe the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can indicate: 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.

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

[0107] Existing terminal device interaction technologies suffer from cumbersome and complex operations, as well as low data exchange efficiency. To address this issue, embodiments of this application provide a terminal device interaction method and apparatus.

[0108] The method is applied to terminal devices, which may be mobile phones, tablets, laptops, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), smart wearable devices, and virtual reality devices, etc. This application embodiment does not impose any restrictions on them.

[0109] Taking a mobile phone as an example of the aforementioned terminal device. Figure 1 A schematic diagram of a mobile phone structure is shown.

[0110] The mobile phone may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a radio frequency module 150, a communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a screen 301, and a subscriber identification module (SIM) card interface 195, etc.

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

[0112] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0113] The controller can serve as the nerve center and command center of the mobile phone. Based on the instruction opcode and timing signals, the controller generates operation control signals to control the fetching and execution of instructions.

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

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

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

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

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

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

[0120] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the screen 301 and camera 193. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 110 and camera 193 communicate via the CSI interface to enable the phone's camera function. The processor 110 and screen 301 communicate via the DSI interface to enable the phone's display function.

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

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

[0123] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a limitation on the structure of the mobile phone. In other embodiments of this application, the mobile phone may also adopt different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

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

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

[0126] The wireless communication function of a mobile phone can be implemented through antenna 1, antenna 2, radio frequency module 150, communication module 160, modem processor, and baseband processor.

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

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

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

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

[0131] In some embodiments, antenna 1 of the mobile phone is coupled to radio frequency module 150, and antenna 2 is coupled to communication module 160, enabling the mobile phone to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0132] The mobile phone implements its display function through a GPU, screen 301, and application processor. The GPU is a microprocessor for image processing, connected to the screen 301 and the application processor. The GPU performs mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information. In this embodiment, the screen 301 may include a display and a touch device. The display outputs content to the user, and the touch device receives touch events input by the user on the screen 301.

[0133] In a mobile phone, the sensor module 180 may include one or more of the following: gyroscope, accelerometer, pressure sensor, barometric pressure sensor, magnetic sensor (e.g., Hall sensor), proximity sensor, proximity light sensor, fingerprint sensor, temperature sensor, touch sensor, pyroelectric infrared sensor, ambient light sensor, or bone conduction sensor. This application embodiment does not impose any limitations on these.

[0134] Mobile phones can achieve shooting functions through ISP, camera 193, video codec, GPU, flexible screen 301 and application processor.

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

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

[0137] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when a mobile phone is selecting a frequency, the DSP performs Fourier transforms on the frequency energy.

[0138] Video codecs are used to compress or decompress digital video. A mobile phone can support one or more video codecs. This allows the phone to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

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

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

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

[0142] Mobile phones can perform audio functions, such as music playback and recording, through components like the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

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

[0144] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. Mobile phones can use the speaker 170A to listen to music or make hands-free calls.

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

[0146] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. A mobile phone can have at least one microphone 170C. In some embodiments, a mobile phone can have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, a mobile phone can have three, four, or more microphones 170C, enabling sound signal collection, noise reduction, sound source identification, and directional recording, among other functions.

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

[0148] Button 190 includes a power button, volume buttons, etc. Button 190 can be a mechanical button or a touch button. The mobile phone can receive button input and generate key signal inputs related to the phone's user settings and function control.

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

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

[0151] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the mobile phone. The mobile phone can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external storage cards. The mobile phone interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the mobile phone uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the mobile phone and cannot be separated from the mobile phone.

[0152] In addition, an operating system runs on top of these components. Examples include Apple's iOS operating system, Google's Android open-source operating system, and Microsoft's Windows operating system. Applications can be installed and run on this operating system.

[0153] To clarify the solution provided in this application, the following description, in conjunction with the accompanying drawings and various embodiments, will illustrate the solution provided in this application.

[0154] This application provides a terminal device interaction method. This method is applied to a first terminal device, which can establish a communication connection with a second terminal device and exchange data through this communication connection. See also... Figure 2 The flowchart shown illustrates the terminal device interaction method provided in this application embodiment, which includes the following steps:

[0155] Step S11: The first terminal device receives a first sharing operation for the first public application APP.

[0156] In this case, if both the first terminal device and the second terminal device have a public APP installed, then the first public APP is an APP among the public APPs.

[0157] In the embodiments of this application, the first terminal device and the second terminal device may include various types. For example, the first terminal device may be a mobile phone, tablet computer, laptop computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), smart wearable device, and virtual reality device, etc.

[0158] In addition, the first terminal device and the second terminal device may be the same type of terminal device, or they may be different types of terminal devices. This application embodiment does not limit this.

[0159] To meet various user needs, multiple apps are often installed on a single terminal device. In this embodiment, the apps installed on the terminal device can be divided into common apps and different apps. If two terminal devices that need to interact with each other are designated as a first terminal device and a second terminal device, then the apps installed on both the first and second terminal devices are common apps, and the apps not installed on either the first or second terminal device are different apps.

[0160] Through data interaction, the first terminal device and the second terminal device can typically share data from a common app. In this case, if both the first terminal device and the second terminal device have a first common app installed, and the first terminal device needs to obtain data from the first common app installed on the second terminal device, then the first terminal device can receive the first sharing operation for the first common app.

[0161] In addition, in the embodiments of this application, the data of a certain APP usually refers to the application data of the APP. The application data of the APP refers to the data belonging to the APP and / or the data created by the APP, and may include data stored locally and data stored in the cloud.

[0162] Step S12: The first terminal device transmits a first sharing instruction based on the first sharing operation.

[0163] After receiving the first sharing operation, the first terminal device generates a first sharing instruction corresponding to the first sharing operation and transmits the first sharing instruction to the second terminal device.

[0164] The first sharing instruction is used to instruct the first terminal device to share data from the first public APP within the second terminal device.

[0165] Step S13: The first terminal device receives and displays the information of the first data transmitted by the second terminal device.

[0166] The first data refers to data that can be shared with the first terminal device in the first public APP of the second terminal device.

[0167] After receiving the first sharing instruction, the second terminal device can determine, based on the instruction, that the first terminal device wishes to share data from a first public app installed on it. In this case, the second terminal device can transmit information about the first data to the first terminal device so that the first terminal device can receive the information about the first data.

[0168] The information of the first data may include the name of the first data, etc. In addition, if the first data is a collection of data, the information of the first data may also include the names of each data in the collection.

[0169] For example, the first public app is an app for playing songs. The data of the first public app includes playlists set by the first public app. The information in the first data may include the names of each playlist and the names of the songs contained in each playlist. Accordingly, after receiving the information in the first data, the first terminal device may display the names of each playlist and the names of the songs contained in each playlist on the display screen.

[0170] Furthermore, the first data refers to data that can be shared with the first terminal device within the first public app of the second terminal device. In one feasible design, the first data may comprise all data contained in the first public app.

[0171] The first public app installed on the second terminal device often contains various types of data, and these different data have different levels of confidentiality. In another feasible design, if some data in the first public app installed on the second terminal device has high confidentiality and the second terminal device does not want to disclose it, the second terminal device can filter the data in its first public app before transmitting the information of the first data, determine the data with lower confidentiality, and use the data with lower confidentiality as data that can be shared with the first terminal device, and transmit the information of the first data to the first terminal device accordingly.

[0172] Furthermore, if the first data includes multiple types, the first terminal device can also classify the information after acquiring the information of the first data, and display the information of the first data of the same type in a group.

[0173] For example, if the first data includes three types: images, documents, and audio, after obtaining the information of the first data, the first terminal device can divide the first data into three groups according to the type of the first data: images, documents, and audio, and the information of the first data of the same type can be displayed in the corresponding group.

[0174] By classifying and displaying the information in the first data, it is easier for the user of the first terminal device to determine the type of the first data and to find the information they need from it.

[0175] Step S14: After receiving the second sharing operation for the information of the first target data, the first terminal device transmits the second sharing instruction.

[0176] Wherein, the first target data is the data in the first data, and the second sharing instruction is used to instruct the sharing of the first target data.

[0177] After the first terminal device displays the information of the first data, it is available for viewing by the user of the first terminal device. Once the user identifies the first target data that needs to be shared, they can perform a second sharing operation on the information of the first target data displayed on the first terminal device. This allows the first terminal device to receive the second sharing operation and determine the first target data based on the received second sharing operation. For example, the user can click on the first target data displayed on the screen; this click operation is the second sharing operation.

[0178] After receiving the second sharing operation, the first terminal device generates a corresponding second sharing instruction based on the second sharing operation and transmits the second sharing instruction to the second terminal device, so that the second terminal device transmits the data indicated by the second sharing instruction to the first terminal device according to the received second sharing instruction.

[0179] Step S15: The first terminal device receives the first target data transmitted by the second terminal device based on the second shared instruction.

[0180] After receiving the second sharing instruction, the second terminal device can determine the first target data that the first terminal device needs to share based on the second sharing instruction, and transmit the first target data to the first terminal device so that the first terminal device can obtain the first target data, thereby realizing the sharing of the first target data between the first terminal device and the second terminal device.

[0181] Steps S11 to S15 provide a terminal device interaction method. In this method, when a first terminal device needs to share certain data from a second terminal device, the user of the first terminal device performs a first sharing operation on the first terminal device, so that the first terminal device receives the first sharing operation for a first public APP. Then, through communication interaction between the first terminal device and the second terminal device, the screen of the first terminal device can display information of the first data, wherein the first data includes the first target data that the first terminal device wishes to share. The user of the first terminal device then performs a second sharing operation, so that the first terminal device determines the first target data to be shared according to the second sharing operation. Then, through communication interaction between the first terminal device and the second terminal device, the first terminal device can obtain the first target data.

[0182] In the existing technology, if the first terminal device needs to obtain the first target data of the second terminal device, the second terminal device needs to log in to the software for cloud storage with a certain account, upload the data to be shared to the cloud storage software, and then the first terminal device logs in to the cloud storage software with the same account, and then finds and downloads the first target data. The operation is cumbersome and complicated, resulting in low efficiency of data interaction.

[0183] The method provided in this application embodiment allows users to acquire the first target data from the second terminal device simply by performing a first sharing operation on the first public APP displayed on the first terminal device and a second sharing operation on the information of the first data displayed on the first terminal device, thus achieving data interaction. Compared with existing technologies, this method requires fewer user operations, is more convenient, and consequently improves the efficiency of data interaction.

[0184] Furthermore, in the solution provided in the embodiments of this application, the first terminal device can display information about the first data so that the user can select the data that they wish to share, thereby achieving selective data sharing.

[0185] To clarify the solutions provided in the embodiments of this application, this application also provides Figure 3 , Figure 3 This is a schematic diagram illustrating the information exchange between the first terminal device and the second terminal device. (See also...) Figure 3 The terminal device interaction method provided in this application embodiment includes the following steps:

[0186] Step S21: The first terminal device receives the first sharing operation for the first public APP.

[0187] In this configuration, a communication connection is established between the first terminal device and the second terminal device, and the first terminal device wishes to share the first target data in the second terminal device.

[0188] Step S22: The first terminal device generates a first sharing instruction based on the first sharing operation and transmits the first sharing instruction to the second terminal device.

[0189] The first sharing instruction is used to instruct the first terminal device to share data from the first public APP within the second terminal device.

[0190] Step S23: The second terminal device receives the first sharing instruction.

[0191] Step S24: The second terminal device transmits information about the first data to the first terminal device.

[0192] The first data refers to data that can be shared with the first terminal device in the first public APP of the second terminal device.

[0193] Step S25: The first terminal device receives a second sharing operation for the first target data.

[0194] According to the second sharing operation, the first terminal device can determine the first target data in the first data that needs to be shared.

[0195] Step S26: The first terminal device generates and transmits the second shared instruction.

[0196] The second sharing instruction is used to instruct the sharing of the first target data in the first data.

[0197] Step S27: After receiving the second sharing instruction, the second terminal device transmits the first target data to the first terminal device.

[0198] Step S28: The first terminal device receives the first target data.

[0199] Through the above data interaction process, it can be determined that in the solution provided in this application embodiment, based on the interaction between the first terminal device and the second terminal device, the sharing of the first target data between the first terminal device and the second terminal device can be realized. Furthermore, in this process, the user only needs to perform a first sharing operation on the first public APP and a second sharing operation on the first target data, making the operation relatively simple and effectively improving the efficiency of terminal device interaction.

[0200] Furthermore, the solution provided in this application embodiment also includes the following steps:

[0201] The first terminal device identifies the public apps within its installed apps;

[0202] The first terminal device prominently displays the icon of the public APP included on its own screen.

[0203] In the solution provided in this application embodiment, the various apps installed on the terminal device are divided into common apps and differentiated apps. Data can be shared between the common apps on the first terminal device and the second terminal device. In this case, the first terminal device identifies the common apps and highlights them on its screen, making it easier for the user of the first terminal device to identify the common apps and differentiated apps. Furthermore, it facilitates the user's ability to perform corresponding sharing operations on the identified common apps, thereby enabling data sharing between different terminal devices and effectively improving the user experience.

[0204] In the solutions provided in this application embodiment, the icons of public apps can be highlighted in various ways. For example, the color of the public app icon can be deepened, the area of ​​the public app icon can be enlarged, and a highlight color can be set on the edge of the public app icon, etc. This application embodiment does not limit these methods.

[0205] In addition, the screen of the first terminal device can display the interface of the second terminal device. For example, multi-screen collaboration can be performed between the first terminal device and the second terminal device. Through multi-screen collaboration technology, the first terminal device determines the interface of the second terminal device and displays it on its own screen.

[0206] If the screen of the first terminal device displays the interface of the second terminal device, then the screen of the first terminal device includes a first area and a second area. The first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area. The second area can display the icons of various apps installed in the first terminal device, while the first area is used to display the icons of various apps installed in the second terminal device.

[0207] In this case, when the first terminal device highlights the icon of the public APP included in its own screen, it will also highlight the icon of the public APP installed on itself, as well as the icon of the public APP installed on the second terminal device included in its own screen (i.e., the icon of the public APP in the first area).

[0208] To clarify the scheme for highlighting the icon of a public APP on the first terminal device provided in this application embodiment, this application provides an example, and the corresponding schematic diagram is as follows: Figure 4 .

[0209] See Figure 4The diagram shown in this example illustrates that the first terminal device is a tablet computer, and the second terminal device is a mobile phone. Figure 4 The screen of the first terminal device includes a first area and a second area. The first area displays the interface of the second terminal device. The first terminal device and the second terminal device have two common apps. In this case, the icons of the common apps in the first area and the common apps in the second area are highlighted simultaneously. In this example, the highlighting method is to set a highlight color on the edge of the common app icon. Therefore, by viewing the screen of the first terminal device, the user can identify the common apps of the first terminal device and the second terminal device.

[0210] In the solution provided in this application embodiment, the first terminal device needs to determine the common apps within its installed apps. In one feasible implementation, the first terminal device determining the common apps within its installed apps may include the following steps: First, the first terminal device obtains the desktop layout data of the second terminal device, whereby the desktop layout data of the second terminal device is used to indicate the installation package of the apps installed on the second terminal device.

[0211] Then, if the first terminal device and the second terminal device have the same operating system, the first terminal device determines the common APP based on the name of the installation package of the APP it has installed and the name of the installation package of the APP installed on the second terminal device, wherein the APP indicated by the installation package with the same name is the common APP.

[0212] The desktop layout data of the second terminal device can be provided by the desktop launcher of the second terminal device. This data can be used to determine the relevant information of the installation packages of each APP displayed on the desktop of the second terminal device.

[0213] The operating systems of the first terminal device and the second terminal device can be the same. For example, the operating systems of the first terminal device and the second terminal device can both be Android, or both can both be HarmonyOS, or both can both be Emotion User Interface (EMUI), etc. This application embodiment does not limit this.

[0214] If the operating systems of the first terminal device and the second terminal device are the same, the installation package name of the same APP is usually the same in both terminals. In this case, the first terminal device determines the installation package name of each APP in the second terminal device based on the desktop layout data of the second terminal device, compares the installation package names of the APPs it has installed with those of the APPs in the second terminal device, and determines that APPs with the same installation package name in both terminals are common APPs, while other APPs are different APPs.

[0215] In addition, if the operating systems of the first terminal device and the second terminal device are different, after obtaining the desktop layout data, the first terminal device can analyze the installation packages of the second terminal device and the APP installed on itself, determine the functions that each APP can execute, and regard the APPs that can execute the same or similar functions in the two terminal devices as common APPs.

[0216] Alternatively, if the first terminal device and the second terminal device have different operating systems, a matching rule can be set in the first terminal device based on the differences between the installation packages of the apps in each operating system. This matching rule includes characteristics of the same app in different operating systems. For example, this matching rule may include the names of the installation packages of the same app in different operating systems. In this case, after obtaining the desktop layout data of the second terminal device, the first terminal device can determine the common app based on this matching rule.

[0217] Of course, the first terminal device can also determine the public APP through other means, and this application embodiment does not limit this.

[0218] During the interaction between the terminal devices, the first terminal device needs to receive a first sharing operation for the first public APP. This first sharing operation can take various forms.

[0219] In one possible implementation, the first sharing operation includes an operation on a first icon, which is the icon of a first public APP installed in the first terminal device.

[0220] The desktop of the first terminal device includes icons for various apps installed on the first terminal device, including a first icon. In this implementation, the first sharing operation is an operation targeting the first icon.

[0221] The operation on the first icon can take various forms, such as a single click, a double click, or dragging the first icon along a specific trajectory. This specific trajectory can be a line segment, a curve, or an arc, etc. For example, see [link to example]. Figure 5 ,set up Figure 5 The interface of the first terminal device includes a circular protrusion on the outer edge of the first icon. In this example, the first sharing operation may be dragging the first icon along a curve.

[0222] Alternatively, in another feasible implementation, the screen of the first terminal device includes a first area and a second area, the first area being the area where the interface of the second terminal device is displayed, and the second area being the area outside the first area. In this case, the first sharing operation may include an operation on a second icon, the second icon being the icon of the first public APP in the first area.

[0223] If the screen of the first terminal device displays the interface of the second terminal device, then the screen of the first terminal device includes a first area and a second area. The first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area. The second area can display the icons of various apps installed in the first terminal device, while the first area can display the icons of various apps installed in the second terminal device.

[0224] In this case, referring to the interface diagram shown in Figure 6(a), the operation on the second icon can be a drag operation on the second icon, which is used to drag the first icon to the second area.

[0225] Correspondingly, if the first terminal device receives a drag operation for the second icon, but the drag operation does not drag the second icon into the second area, the first terminal device usually does not consider the drag operation to be the first sharing operation.

[0226] Of course, the first sharing operation can also be other forms of operation, and this application embodiment does not limit this.

[0227] In addition, after receiving the first sharing operation, the first terminal device will also transmit a first sharing instruction and display information about the first data transmitted by the second terminal device. If the screen of the first terminal device includes a first area and a second area, the first terminal device will typically display information about the first data in the second area.

[0228] In this case, refer to the interface diagram shown in Figure 6(b). In this diagram, a dashed box is included in the second area, containing information about at least one piece of first data for the user of the first terminal device to select. Furthermore, in the example corresponding to Figure 6(b), the first data includes multiple types, such as images and documents. Therefore, when displaying the information of the first data, data of the same type will be displayed in a group. Accordingly, in the interface shown in Figure 6(b), images and documents are displayed in separate groups.

[0229] Furthermore, to prevent accidental operation, the solution provided in this application embodiment may also include the following steps:

[0230] First, after receiving the first sharing operation, the first terminal device displays a first selection box, which is used to indicate whether to share the data of the second terminal device to the first terminal device.

[0231] Then, after receiving a confirmation operation for the first selection box, the first terminal device transmits the first sharing instruction. The confirmation operation indicates that data from the second terminal device needs to be shared with the first terminal device.

[0232] Users of the first terminal device may not wish to share data from the second terminal device, but may accidentally tap the first terminal device. The first terminal device may then interpret this accidental tap as a sharing operation. To avoid this situation, in the solution provided in this application embodiment, after receiving the first sharing operation, the first terminal device can display a first selection box, allowing the user to interact with the first selection box and choose whether to share data from the second terminal device to the first terminal device.

[0233] If a confirmation operation is received for the first selection box, it indicates that the user of the first terminal device wishes to access the data of the first public APP on the second terminal device. In this case, the first terminal device then transmits the first sharing instruction to the second terminal device. Conversely, if a negative operation is received for the first selection box, it indicates that the user of the first terminal device does not wish to access the data of the first public APP on the second terminal device. In this case, the first terminal device will not transmit the first sharing instruction.

[0234] In one example, the first terminal device is a tablet computer, and the second terminal device is a mobile phone. The first selection box can be as follows: Figure 7 As shown. See also Figure 7 The diagram shown is an interface diagram of the first terminal device, which displays a first area and a second area. The icons of the public apps in both areas are highlighted. Furthermore, after receiving the first sharing operation, the interface displays as follows: Figure 7 The first selection box shown includes a prompt for "Data synchronization to tablet" and two selection menus: "Yes" and "No".

[0235] In this case, the confirmation operation for the first selection box can be a selection operation for the "Yes" selection menu. Alternatively, if a selection operation for the "No" selection menu is received, this selection operation can be considered a negation operation for the first selection box.

[0236] The solution provided by the above embodiments of this application enables the first terminal device to obtain data from the second terminal device. Additionally, in some cases, the second terminal device may wish to obtain data stored in the first terminal device. To meet this requirement, see [link to relevant documentation]. Figure 8 The flowchart shown in this application illustrates that the method provided in this embodiment further includes the following steps:

[0237] Step S31: The first terminal device receives a third sharing operation for the second public APP.

[0238] The third sharing operation is used to instruct the sharing of data from the second public APP of the first terminal device to the second terminal device.

[0239] In this embodiment of the application, the user of the first terminal device wishes to share the data of the second public APP that they have installed to the second terminal device.

[0240] Step S32: The first terminal device displays the second data information of the second public APP installed on itself.

[0241] The second data refers to data that can be shared with the second terminal device in the second public APP of the first terminal device.

[0242] The information of the second data may be the name of the second data, and if the second data includes multiple types, the first terminal device may classify the second data when displaying the information of the second data, and display the second data of the same type in a group.

[0243] In addition, if the second public APP of the first terminal device includes a variety of data, and some of the data is highly confidential, and the first terminal device does not want to disclose this part of the data, the first terminal device can filter out the data that can be shared with the second terminal device, and then display the information of the filtered data.

[0244] Step S33: After receiving the fourth sharing operation, the first terminal device transmits the second target data indicated by the third sharing operation to the second terminal device, wherein the second target data belongs to the second data.

[0245] Through the above steps, the second terminal device can acquire the second target data, thereby enabling the sharing of data from the first terminal device to the second terminal device.

[0246] The third sharing operation typically includes an operation on a third icon, which is the icon of a second public APP installed on the first terminal device.

[0247] The desktop of the first terminal device includes icons for various apps installed on the first terminal device, including a third icon, and the third sharing operation can be in various forms.

[0248] In one feasible implementation, the third sharing operation can be a single click, a double click, or a dragging operation along a specific trajectory on the third icon. This specific trajectory can be a line segment, a curve, or an arc, etc.

[0249] Alternatively, in another feasible implementation, if the screen of the first terminal device includes a first area and a second area, the first area being the area where the interface of the second terminal device is displayed, and the second area being the area outside the first area, the third sharing operation is a drag operation on the third icon, the drag operation on the third icon being used to drag the third icon to the first area.

[0250] In this case, if the first terminal device receives a drag operation for the third icon, but the drag operation does not move the third icon from the second area to the first area, it is generally considered that the drag operation for the third icon is not a third sharing operation.

[0251] Users of the first terminal device may sometimes not want to share data of publicly installed apps with the second terminal device, but may accidentally tap the first terminal device, which could then interpret the tap as a sharing operation. To avoid this, in the solution provided in this application embodiment, after receiving the third sharing operation, the first terminal device can also display a selection box, allowing the user to interact with the selection box to choose whether to share the data from the first terminal device to the second terminal device.

[0252] In this scenario, after receiving a confirmation response to the selection box, the first terminal device then transmits the second target data to the second terminal device. Conversely, if a negative response is received to the selection box, the first terminal device temporarily halts the transmission of the second target data to the second terminal device.

[0253] The selection box displayed by the first terminal device after receiving the third sharing operation may be the same as the first selection box, or they may be different. This application embodiment does not limit this.

[0254] In addition, the embodiments of this application may also include the following steps:

[0255] First, if the screen of the first terminal device includes a first area and a second area, where the first area is the area where the interface of the second terminal device is displayed and the second area is the area outside the first area on the screen, the first terminal device displays a second selection box after receiving a selection operation for a third public APP in the first area.

[0256] The second selection box is used to indicate whether to open the third public APP installed on the first terminal device.

[0257] Then, after receiving a confirmation operation for the second selection box, the first terminal device runs the third public APP that it has installed.

[0258] In addition, after receiving a negative operation for the second selection box, the first terminal device transmits a first running instruction to the second terminal device. The first running instruction is used to instruct the second terminal device to run the third public APP installed on itself.

[0259] In the solution provided in this application embodiment, the first terminal device can display the interface of the second terminal device on its own screen. In this case, the first area used to display the interface of the second terminal device often includes a fourth icon of a third public APP installed on the second terminal device. The selection operation for the third public APP in the first area can be an operation on the fourth icon in the first area, which can be clicking or double-clicking the fourth icon, or dragging the fourth icon. Of course, the selection operation for the third public APP in the first area can also be other forms of operation, and this application embodiment does not limit this.

[0260] In some cases, users of the first terminal device often want to use a third-party public app. For example, the third-party public app could be an app for playing videos; when a user needs to watch videos, they often need to run the third-party public app. Furthermore, through the interaction between the first and second terminal devices, the third-party public app installed on the first terminal device can often obtain data from the third-party public app installed on the second terminal device.

[0261] Furthermore, sometimes the first terminal device has an advantage over the second terminal device. For example, the first terminal device may have a larger screen area, a clearer display, or a more powerful processor. In such cases, the first terminal device running its own installed third-party public app often provides a better user experience.

[0262] To address this issue, in the solution provided in this application embodiment, after receiving a selection operation for a third public APP in the first area, the first terminal device can display a second selection box to prompt the user to select whether the first terminal device should run the third public APP.

[0263] If a confirmation request is received for the second selection box, it indicates that the user wishes to run the third public app installed on the first terminal device. Therefore, after receiving the confirmation request for the second selection box, the first terminal device will run the third public app it has installed, so that the user of the first terminal device can understand the operation process of the third public app.

[0264] Furthermore, when the first terminal device is running the third public APP it has installed, it can usually display the interface of the third public APP it is running in the second area. Moreover, after receiving the corresponding operation, the first terminal device can also display the interface of the third public APP it is running in full screen.

[0265] In some cases, users often do not want to run a third public app installed on the first terminal device, and therefore will reject the third selection box. In this case, the solution provided in this application embodiment further includes the following steps:

[0266] Upon receiving a negative response to the second selection box, the first terminal device transmits a first execution instruction to the second terminal device. This first execution instruction instructs the second terminal device to run a third public app installed on itself. Upon receiving the first execution instruction, the second terminal device can then run the third public app it has installed.

[0267] Furthermore, in some cases, the user of the first terminal device may wish to directly run the same public app on the second terminal device after selecting it from the first area. In this case, the first terminal device can support a function switch. After receiving a setting operation, the first terminal device can display the function switch for the user to operate. If the first terminal device receives an operation to turn off the function switch, then after receiving a selection operation for the third public app in the first area, the first terminal device will no longer display the second selection box, but will directly transmit a first run command to the second terminal device, so that the second terminal device, upon receiving the first run command, will begin running the third public app it has installed.

[0268] Additionally, if a user wishes to prioritize running the third-party public app on the first terminal device, they can choose to enable this function. After receiving the operation to enable or disable this function, if the first terminal device receives a selection operation for the third-party public app in the first area, a second selection box will be displayed.

[0269] Furthermore, the solution provided in this application embodiment also includes the following steps:

[0270] After receiving the first target data, the first terminal device synchronizes the first target data to its own first public APP.

[0271] In this scenario, the first target data originates from a first public app installed on the second terminal device. Upon receiving the first target data, the first terminal device can synchronize it to its own first public app. After synchronization, the user of the first terminal device can view and use the first target data through the first public app installed on the first terminal device.

[0272] For example, if the first public app is a music playback app, the first target data may include playlists. The first terminal device synchronizes the first target data to its own first public app, that is, the first terminal device synchronizes the playlist to the first public app it has installed, realizing playlist synchronization and sharing between the first terminal device and the second terminal device. If the first public app is an app for displaying calendar information, and the app can mark schedules and events, then the first target data may include the marked schedules and events. After the synchronization of the first target data is completed, the schedules and events marked on the first public app on the second terminal device can be queried through the first public app installed on the first terminal device. If the first public app is a communication app, then the first target data may include contacts' address books, etc. In this case, after the synchronization of the first target data is completed, the contacts' address books stored in the first public app on the second terminal device can be queried through the first public app installed on the first terminal device.

[0273] Accordingly, embodiments of this application also provide a terminal device interaction method, which is applied to a second terminal device. See [link to related document]. Figure 9 The flowchart shown in this application illustrates the following steps in the method provided by this embodiment:

[0274] Step S41: The second terminal device receives the first sharing instruction transmitted by the first terminal device.

[0275] The first sharing instruction is used to instruct the first terminal device to share data of the first public APP in the second terminal device. The APP installed on both the first terminal device and the second terminal device is a public APP.

[0276] The first terminal device has a first public APP installed. After the first terminal device receives a first sharing operation for the first public APP installed on itself, the first terminal device can generate a first sharing instruction and transmit the first sharing instruction to the second terminal device.

[0277] Step S42: The second terminal device transmits information about the first data corresponding to the first shared instruction.

[0278] The first data refers to data that can be shared with the first terminal device within the first public APP of the second terminal device. The information in the first data may include the name of the first data, etc. Additionally, if the first data is a collection of data, the information in the first data may also include the names of each data item in the collection.

[0279] For example, the first public app is an app for playing songs. The data of the first public app includes playlists set by the first public app. The information in the first data may include the names of each playlist and the names of the songs contained in each playlist. Accordingly, after receiving the information in the first data, the first terminal device may display the names of each playlist and the names of the songs contained in each playlist on the display screen.

[0280] Furthermore, the first data refers to data that can be shared with the first terminal device within the first public app of the second terminal device. In one feasible design, the first data may comprise all data contained in the first public app.

[0281] The first public app installed on the second terminal device often contains various types of data, and these different data have different levels of confidentiality. In another feasible design, if some data in the first public app installed on the second terminal device has high confidentiality and the second terminal device does not want to disclose it, the second terminal device can filter the data in its first public app before transmitting the information of the first data, determine the data with lower confidentiality, and use the data with lower confidentiality as data that can be shared with the first terminal device, and transmit the information of the first data to the first terminal device accordingly.

[0282] After receiving the first data, the first terminal device displays the first data for the user to select. Furthermore, after receiving a second sharing operation for the first target data, the first terminal device can transmit a second sharing instruction to the second terminal device.

[0283] Step S43: The second terminal device receives the second sharing instruction.

[0284] The second sharing instruction instructs the first terminal device to share the first target data in the first data.

[0285] Step S44: The second terminal device transmits the first target data.

[0286] The first terminal device can receive the first target data transmitted by the second terminal device, thereby enabling the first terminal device and the second terminal device to share the first target data.

[0287] The solution provided in this application enables a first terminal device to acquire first target data from a second terminal device, thereby facilitating interaction between the two devices. Furthermore, during this process, the second terminal device executes corresponding operations based on received first and second sharing instructions, without requiring user intervention on the second terminal device. Therefore, compared to existing technologies, the solution provided in this application is simpler to implement and effectively improves the interaction efficiency of terminal devices.

[0288] In the solution provided in this application embodiment, the apps installed on the terminal device are divided into two types: common apps and differentiated apps. Specifically, if the two terminal devices that need to interact with each other are designated as a first terminal device and a second terminal device, then the apps installed on both the first and second terminal devices are common apps, and the apps not installed on either the first or second terminal device are differentiated apps.

[0289] In this case, the solution provided by the embodiments of this application may further include the following steps:

[0290] First, the second terminal device identifies the public apps within the apps it has installed;

[0291] Then, the second terminal device highlights the icon of the public APP included on its own screen.

[0292] During the interaction between the first terminal device and the second terminal device, data from a common APP can be shared. In this case, after identifying the common APP, the second terminal device will highlight the common APP on its own screen, thereby making it easier for the user of the second terminal device to identify the common APP and different APPs, facilitating data sharing between different terminal devices and effectively improving the user experience.

[0293] Furthermore, in the solutions provided in this application embodiment, the icons of public apps can be highlighted in various ways. For example, the color of the public app icon can be deepened, the area of ​​the public app icon can be enlarged, and a highlight color can be set on the edge of the public app icon, etc. This application embodiment does not limit this.

[0294] In this embodiment, the screen of the second terminal device may also display the interface of the first terminal device. For example, multi-screen collaboration can be performed between the first terminal device and the second terminal device. Through multi-screen collaboration technology, the second terminal device determines the interface of the first terminal device and displays the interface of the first terminal device on its own screen.

[0295] If the screen of the second terminal device displays the interface of the first terminal device, then the icons of the public apps highlighted on the second terminal device include the icons of the public apps included in the interface of the first terminal device displayed on its own screen.

[0296] Furthermore, the first terminal device sometimes needs to share its own data with the second terminal device. For example, the first terminal device needs to transmit the second target data of a second public app installed on it to the second terminal device. In this case, the first terminal device can transmit the second target data to the second terminal device.

[0297] Accordingly, the solution provided in this application embodiment also includes the following steps:

[0298] The second terminal device receives second target data, which is a type of second data. The second data is data that can be shared with the second terminal device in the second public APP of the first terminal device.

[0299] Through this step, the second terminal device can also obtain data from the first terminal device. Furthermore, after obtaining the second target data, the second terminal device can synchronize the second target data to its own installed second public app, allowing it to view and use the second target data through the second public app.

[0300] Furthermore, during the interaction between the first terminal device and the second terminal device, the first terminal device can also control the second terminal device. For example, a first area on the screen of the first terminal device is used as the interface of the second terminal device. After receiving a selection operation for the third public APP in the first area, the first terminal device can display a second selection box, and after receiving a negative operation for the second selection box, it can transmit a first running instruction to the second terminal device.

[0301] In this case, the embodiments of this application further include the following steps:

[0302] After receiving the first running instruction, the second terminal device runs the third public APP installed on it, thereby satisfying the user's control needs of the second terminal device.

[0303] The following are apparatus embodiments of this application, which can be used to execute the method embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the method embodiments of this application.

[0304] As an implementation of the above embodiments, this application discloses a terminal device interaction apparatus, which is applied to a first terminal device. See also Figure 10The schematic diagram shown illustrates that the terminal device interaction device disclosed in this application includes: a transceiver interface 200 and a processor 300.

[0305] The transceiver interface 200 is used to receive a first sharing operation for a first public application APP, wherein the APP installed on both the first terminal device and the second terminal device is a public APP.

[0306] The processor 300 is configured to determine a first sharing instruction based on the first sharing operation, wherein the first sharing instruction is configured to instruct the first terminal device to share data of the first public APP in the second terminal device;

[0307] The transceiver interface 200 is also used to transmit the first sharing instruction and receive information about the first data transmitted by the second terminal device, wherein the first data is data in the first public APP of the second terminal device that can be shared with the first terminal device.

[0308] The processor 300 is also used to display information about the first data;

[0309] The transceiver interface 200 is further configured to, after receiving a second sharing operation for information on the first target data, transmit a second sharing instruction, wherein the first target data is data in the first data, the second sharing instruction is used to indicate sharing the first target data, and receive the first target data transmitted by the second terminal device based on the second sharing instruction.

[0310] The first terminal device and the second terminal device may be the same type of terminal device, or they may be different types of terminal devices. This application embodiment does not limit this.

[0311] In the embodiments of this application, the data of a certain APP usually refers to the application data of the APP. The application data of the APP refers to the data belonging to the APP and / or the data created by the APP, and may include data stored locally and data stored in the cloud.

[0312] This application provides a terminal device interactive transceiver interface and a processor device. This device is typically used in a first terminal device. Through this device, the user only needs to perform a first sharing operation on a first public APP displayed on the first terminal device and a second sharing operation on information from first data displayed on the first terminal device to enable the first terminal device to obtain first target data from a second terminal device, thus achieving data interaction. Compared with existing technologies, fewer user operations are required, the operation is simpler, and the efficiency of data interaction is correspondingly improved.

[0313] Furthermore, in the solution provided in this application embodiment, the processor is also used to determine the public apps within its installed apps and highlight the icons of the public apps included on its own screen.

[0314] In the solutions provided in this application embodiment, the first sharing operation can take various forms. In one feasible implementation, the first sharing operation includes an operation on a first icon, where the first icon is the icon of a first public APP installed in the first terminal device.

[0315] Alternatively, in another feasible implementation, the screen of the first terminal device includes a first area and a second area, the first area being the area where the interface of the second terminal device is displayed, the second area being the area outside the first area, and the first sharing operation including an operation on a second icon, the second icon being the icon of the first public APP in the first area.

[0316] Furthermore, in this embodiment of the application, the transceiver interface is also used to receive a third sharing operation for the second public APP, the third sharing operation being used to instruct the sharing of data of the second public APP of the first terminal device to the second terminal device;

[0317] The processor is also configured to display information about the second data of the second public APP installed on itself, wherein the second data is data in the second public APP of the first terminal device that can be shared with the second terminal device.

[0318] The transceiver interface is further configured to, upon receiving the fourth sharing operation, transmit the second target data indicated by the fourth sharing operation to the second terminal device, wherein the second target data is part of the second data.

[0319] Accordingly, this application also provides a terminal device interaction device, which is applied to a second terminal device, and the device includes: a transceiver interface and a processor;

[0320] The transceiver interface is used to receive a first sharing instruction transmitted by the first terminal device. The first sharing instruction is used to indicate that the first terminal device needs to share data of a first public APP in the second terminal device. The APP installed on both the first terminal device and the second terminal device is a public APP.

[0321] The processor is used to determine information about the first data corresponding to the first sharing instruction, wherein the first data is data that can be shared with the first terminal device in the first public APP of the second terminal device.

[0322] The transceiver interface is also used to transmit information from the first data, receive a second sharing instruction, and transmit first target data, wherein the second sharing instruction indicates that the first terminal device needs to share the first target data from the first data.

[0323] Correspondingly, in accordance with the methods described above, this application also discloses a terminal device. See also Figure 11 The structural diagram shown indicates that the terminal device includes:

[0324] At least one processor 1101 and memory,

[0325] The memory is used to store program instructions;

[0326] The processor is configured to call and execute program instructions stored in the memory, so that the terminal device performs [operations]. Figure 2 , Figure 3 and Figure 8 All or part of the steps in the corresponding embodiments.

[0327] Furthermore, the terminal device may also include a transceiver 1102 and a bus 1103, and the memory includes a random access memory 1104 and a read-only memory 1105.

[0328] The processor is coupled to the transceiver, random access memory (RAM), and read-only memory (ROM) via a bus. When the mobile terminal control device needs to be run, it is booted via the basic input / output system (BIS) embedded in the ROM or the bootloader in the embedded system, thus guiding the device into normal operation. Once in normal operation, the application program and operating system run in the RAM, enabling the terminal device to perform operations. Figure 2 , Figure 3 and Figure 8 All or part of the steps in the corresponding embodiments.

[0329] The apparatus of this invention can correspond to the above. Figure 2 , Figure 3 and Figure 8 The terminal device interaction device in the corresponding embodiment, and the processor in the device, etc., can implement 2. Figure 3 and Figure 8 For the sake of brevity, the functions of the driving behavior monitoring device in the corresponding embodiments and / or the various steps and methods implemented will not be described in detail here.

[0330] It should be noted that this embodiment can also be implemented using a general-purpose physical server combined with Network Function Virtualization (NFV) technology to create a network device, which is a virtual network device (e.g., a virtual host, virtual router, or virtual switch). The virtual network device can be a virtual machine (VM) running a program for sending announcement messages, and the VM is deployed on hardware (e.g., a physical server). A virtual machine refers to a complete computer system simulated by software, possessing full hardware system functionality and running in a completely isolated environment. Those skilled in the art can virtualize multiple network devices with the above-mentioned functions on a general-purpose physical server by reading this application. Further details are omitted here.

[0331] Correspondingly, in accordance with the methods described above, this application also discloses a terminal device. The terminal device includes:

[0332] At least one processor and memory,

[0333] The memory is used to store program instructions;

[0334] The processor is configured to call and execute program instructions stored in the memory, so that the terminal device performs [operations]. Figure 9 All or part of the steps in the corresponding embodiments.

[0335] Furthermore, the terminal device may also include a transceiver and a bus, and the memory includes random access memory and read-only memory.

[0336] The processor is coupled to the transceiver, random access memory (RAM), and read-only memory (ROM) via a bus. When the mobile terminal control device needs to be run, it is booted via the basic input / output system (BIS) embedded in the ROM or the bootloader in the embedded system, thus guiding the device into normal operation. Once in normal operation, the application program and operating system run in the RAM, enabling the terminal device to perform operations. Figure 9 All or part of the steps in the corresponding embodiments.

[0337] The apparatus of this invention can correspond to the above. Figure 9 The terminal device interaction device in the corresponding embodiment, and the processor in the device, etc., can implement... Figure 9 For the sake of brevity, the functions of the driving behavior monitoring device in the corresponding embodiments and / or the various steps and methods implemented will not be described in detail here.

[0338] It should be noted that this embodiment can also be implemented using a general-purpose physical server combined with Network Function Virtualization (NFV) technology to create a network device, which is a virtual network device (e.g., a virtual host, virtual router, or virtual switch). The virtual network device can be a virtual machine (VM) running a program for sending announcement messages, and the VM is deployed on hardware (e.g., a physical server). A virtual machine refers to a complete computer system simulated by software, possessing full hardware system functionality and running in a completely isolated environment. Those skilled in the art can virtualize multiple network devices with the above-mentioned functions on a general-purpose physical server by reading this application. Further details are omitted here.

[0339] In a specific implementation, embodiments of this application also provide a computer-readable storage medium, which includes instructions. Wherein, a computer-readable medium disposed in any device, when executed on a computer, can implement instructions including... Figure 2 , Figure 3 and Figure 8 All or part of the steps in the corresponding embodiments. The storage medium of the computer-readable medium may be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0340] Accordingly, embodiments of this application also provide a computer-readable storage medium including instructions. The computer-readable medium, disposed in any device, can implement instructions when executed on a computer. Figure 9 All or part of the steps in the corresponding embodiments. The storage medium of the computer-readable medium may be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0341] Additionally, another embodiment of this application discloses a computer program product containing instructions that, when executed on an electronic device, enable the electronic device to implement the following: Figure 2 , Figure 3 and Figure 8 All or part of the steps in the corresponding embodiments.

[0342] Additionally, another embodiment of this application discloses a computer program product containing instructions that, when executed on an electronic device, enable the electronic device to implement the following: Figure 9 All or part of the steps in the corresponding embodiments.

[0343] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital information processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital information processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital information processor core, or any other similar configuration.

[0344] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be disposed in an ASIC, which can be disposed in the UE. Optionally, the processor and storage medium can also be disposed in different components within the UE.

[0345] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0346] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0347] The same or similar parts between the various embodiments in this specification can be referred to interchangeably. Each embodiment focuses on the differences from other embodiments. In particular, the device and system embodiments are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to in the description of the method embodiments section.

[0348] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments of the present invention.

[0349] The same or similar parts between the various embodiments in this specification can be referred to mutually. In particular, the embodiments of the road constraint determination device disclosed in this application are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to the description in the method embodiments.

[0350] The embodiments of the present invention described above do not constitute a limitation on the scope of protection of the present invention.

Claims

1. A terminal device interaction method, characterized in that, include: The first terminal device obtains the desktop layout data of the second terminal device. The application APP installed on both the first terminal device and the second terminal device is a common APP. The desktop layout data of the second terminal device is used to indicate the installation package of the APP installed on the second terminal device. If the first terminal device and the second terminal device have the same operating system, the first terminal device determines the common APP within the APP installed by itself based on the name of the installation package of the APP installed by itself and the name of the installation package of the APP installed by the second terminal device, wherein the APP indicated by the installation package with the same name is the common APP. The first terminal device receives the first sharing operation for the first public APP; Based on the first sharing operation, the first terminal device transmits a first sharing instruction, which is used to indicate that the first terminal device needs to share the data of the first public APP in the second terminal device; The first terminal device receives and displays information about the first data transmitted by the second terminal device, wherein the first data is data that can be shared with the first terminal device in the first public APP of the second terminal device. After receiving the second sharing operation for the first target data, the first terminal device transmits the second sharing instruction, where the first target data is the data in the first data, and the second sharing instruction is used to indicate sharing the first target data; The first terminal device receives the first target data transmitted by the second terminal device based on the second shared instruction.

2. The method according to claim 1, characterized in that, Also includes: The first terminal device prominently displays the icon of the public APP included on its own screen.

3. The method according to claim 1 or 2, characterized in that, The first sharing operation includes operations on a first icon, which is the icon of a first public APP installed in the first terminal device; or, The screen of the first terminal device includes a first area and a second area. The first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area. The first sharing operation includes an operation on a second icon, which is the icon of the first public APP in the first area.

4. The method according to claim 3, characterized in that, The operation on the second icon is a drag operation on the second icon, which is used to drag the first icon to the second area.

5. The method according to claim 1, characterized in that, Also includes: After receiving the first sharing operation, the first terminal device displays a first selection box, which is used to indicate whether to share the data of the second terminal device to the first terminal device. After receiving confirmation of the first selection box, the first terminal device then transmits the first sharing instruction.

6. The method according to claim 1, characterized in that, Also includes: The first terminal device receives a third sharing operation for the second public APP, the third sharing operation being used to instruct the sharing of the data of the second public APP of the first terminal device to the second terminal device; The first terminal device displays information about the second data of the second public APP installed on itself. The second data is data in the second public APP of the first terminal device that can be shared with the second terminal device. After receiving the fourth sharing operation, the first terminal device transmits the second target data indicated by the fourth sharing operation to the second terminal device, wherein the second target data is part of the second data.

7. The method according to claim 6, characterized in that, The third sharing operation includes an operation on a third icon, which is the icon of a second public APP installed on the first terminal device.

8. The method according to claim 7, characterized in that, If the screen of the first terminal device includes a first area and a second area, the first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area, the third sharing operation is a drag operation on the third icon, and the drag operation on the third icon is used to drag the third icon to the first area.

9. The method according to claim 1, characterized in that, Also includes: If the screen of the first terminal device includes a first area and a second area, the first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area of ​​the screen, after receiving a selection operation for the third public APP in the first area, the first terminal device displays a second selection box, which is used to indicate whether to open the third public APP installed on the first terminal device. After receiving confirmation for the second selection box, the first terminal device runs the third public APP that it has installed.

10. The method according to claim 9, characterized in that, Also includes: After receiving a negative operation for the second selection box, the first terminal device transmits a first running instruction to the second terminal device. The first running instruction is used to instruct the second terminal device to run the third public APP that it has installed.

11. The method according to claim 1, characterized in that, Also includes: After receiving the first target data, the first terminal device synchronizes the first target data to its own first public APP.

12. A terminal device interaction method, characterized in that, include: The second terminal device receives a first sharing instruction transmitted by the first terminal device. The first sharing instruction is used to indicate that the first terminal device needs to share the data of a first public APP in the second terminal device. The APP installed on both the first terminal device and the second terminal device is a public APP. The second terminal device transmits information about the first data corresponding to the first sharing instruction, wherein the first data is data in the first public APP of the second terminal device that can be shared with the first terminal device; The second terminal device receives a second sharing instruction, which instructs the first terminal device to share the first target data in the first data. The second terminal device transmits the first target data; The public apps installed on the first terminal device are determined by the first terminal in the following manner: The first terminal obtains the desktop layout data of the second terminal, and the desktop layout data of the second terminal is used to indicate the installation package of the APP installed on the second terminal device; If the first terminal device and the second terminal device have the same operating system, the first terminal device determines the common APP based on the name of the installation package of the APP it has installed and the name of the installation package of the APP installed on the second terminal device, wherein the APP indicated by the installation package with the same name is the common APP.

13. The method according to claim 12, characterized in that, Also includes: The second terminal device identifies the public apps within the apps it has installed; The second terminal device prominently displays the icon of the public APP included on its own screen.

14. The method according to claim 12, characterized in that, Also includes: The second terminal device receives second target data, which is a type of second data. The second data is data that can be shared with the second terminal device in the second public APP of the first terminal device.

15. The method according to claim 12, characterized in that, Also includes: After receiving the first running instruction, the second terminal device runs the third public APP that it has installed.

16. A terminal device interaction device, characterized in that, Applied to the first terminal device, including: Transceiver interface and processor; The transceiver interface is used to receive a first sharing operation for a first public application APP, wherein the APP installed on both the first terminal device and the second terminal device is a public APP. The processor is configured to determine a first sharing instruction based on the first sharing operation, wherein the first sharing instruction is configured to instruct the first terminal device to share data of the first public APP in the second terminal device; The transceiver interface is also used to transmit the first sharing instruction and receive information about the first data transmitted by the second terminal device, wherein the first data is data that can be shared with the first terminal device in the first public APP of the second terminal device. The processor is also configured to display information from the first data; The transceiver interface is further configured to, after receiving a second sharing operation for information on the first target data, transmit a second sharing instruction, wherein the first target data is data in the first data, the second sharing instruction is used to indicate sharing the first target data, and receive the first target data transmitted by the second terminal device based on the second sharing instruction; The processor is also configured to determine the public apps within its installed apps in the following manner: Obtain the desktop layout data of the second terminal device, which is used to indicate the installation package of the APP installed on the second terminal device; When the operating systems of the first terminal device and the second terminal device are the same, the first terminal device determines the common APP within the APP installed by itself based on the name of the installation package of the APP installed by itself and the name of the installation package of the APP installed by the second terminal device, wherein the APP indicated by the installation package with the same name is the common APP.

17. The apparatus according to claim 16, characterized in that, The processor is also used to highlight the icon of the public app included on its own screen.

18. The apparatus according to claim 16 or 17, characterized in that, The first sharing operation includes operations on a first icon, which is the icon of a first public APP installed in the first terminal device; or, The screen of the first terminal device includes a first area and a second area. The first area is the area where the interface of the second terminal device is displayed, and the second area is the area outside the first area. The first sharing operation includes an operation on a second icon, which is the icon of the first public APP in the first area.

19. The apparatus according to claim 16, characterized in that, The transceiver interface is also used to receive a third sharing operation for the second public APP, the third sharing operation being used to instruct the sharing of data of the second public APP of the first terminal device to the second terminal device; The processor is also configured to display information about the second data of the second public APP installed on itself, wherein the second data is data in the second public APP of the first terminal device that can be shared with the second terminal device. The transceiver interface is further configured to, upon receiving the fourth sharing operation, transmit the second target data indicated by the fourth sharing operation to the second terminal device, wherein the second target data is part of the second data.

20. A terminal device interaction device, characterized in that, Applied to second terminal devices, including: Transceiver interface and processor; The transceiver interface is used to receive a first sharing instruction transmitted by the first terminal device. The first sharing instruction is used to indicate that the first terminal device needs to share data of a first public APP in the second terminal device. The APP installed on both the first terminal device and the second terminal device is a public APP. The processor is used to determine information about the first data corresponding to the first sharing instruction, wherein the first data is data that can be shared with the first terminal device in the first public APP of the second terminal device. The transceiver interface is also used to transmit information of the first data, receive a second sharing instruction, and transmit the first target data, wherein the second sharing instruction indicates that the first terminal device needs to share the first target data in the first data; The public apps installed on the first terminal device are determined by the first terminal in the following manner: The first terminal obtains the desktop layout data of the second terminal, and the desktop layout data of the second terminal is used to indicate the installation package of the APP installed on the second terminal device; If the first terminal device and the second terminal device have the same operating system, the first terminal device determines the common APP based on the name of the installation package of the APP it has installed and the name of the installation package of the APP installed on the second terminal device, wherein the APP indicated by the installation package with the same name is the common APP.

21. A terminal device, characterized in that, include: At least one processor and memory, The memory is used to store program instructions; The processor is configured to call and execute program instructions stored in the memory to cause the terminal device to perform the terminal device interaction method according to any one of claims 1-11.

22. A terminal device, characterized in that, include: At least one processor and memory, The memory is used to store program instructions; The processor is configured to call and execute program instructions stored in the memory to cause the terminal device to perform the terminal device interaction method according to any one of claims 12-15.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the terminal device interaction method as described in any one of claims 1-11.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the terminal device interaction method as described in any one of claims 12-15.

Images