Application sharing method, electronic equipment and storage medium
By receiving user operations and sending application sharing requests in multi-screen collaborative scenarios, the problem of application operations between devices is solved, and application sharing between devices is realized, and user experience and interoperability between devices is improved.
Patent Information
- Application Number
- CN202411030334.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2020-12-18
- Publication Date
- 2024-11-08
AI Technical Summary
The existing technology is difficult to implement cross-application operations between devices, especially in multi-screen collaboration scenarios. Users cannot directly call applications on another device to share cross-applications, such as when opening web pages on a tablet, they cannot pass. Share social software on your mobile phone.
Provide an application sharing method, by receiving user operations on the first electronic device, displaying application icons on the second electronic device, and sending application sharing requests to the second electronic device, to realize application sharing across devices, including establishing multiple applications. The screen collaboratively connects, displays a window of the second electronic device, minimizes the window, and receives and sends application information to simulate and query matching applications.
It realizes application sharing across devices, improves user experience, and allows users to operate applications on one device on another device, such as operating applications and files on mobile phones on tablets, enhancing interoperability between devices.
Smart Images

Figure CN118915939A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communication technology, and in particular to an application sharing method, an electronic device, and a storage medium. Background Art
[0002] With the continuous development of information technology, the Internet has become an important means of information dissemination. In addition, with the diversification of electronic devices, the interaction between electronic devices is increasing. In particular, multi-screen collaboration between electronic devices, for example, the display content of one electronic device can be displayed on the screen of another electronic device, or the file of one electronic device can be transferred to another electronic device. Summary of the invention
[0003] The embodiments of the present application provide an application sharing method and an electronic device. The present application also provides a computer-readable storage medium to provide an efficient application sharing method, which can realize application sharing across devices.
[0004] In a first aspect, an embodiment of the present application provides an application sharing method, which is applied to a first electronic device, where the first electronic device has installed a first application, including:
[0005] The first interface of the first application is displayed, and the first interface includes a first option; specifically, the first electronic device may be a display device with a larger screen, such as a tablet. The present application does not limit the specific form of the first electronic device. The first application may be an application with browsing content, such as a web page. The present application does not limit the specific type of the first application. The first option may be an option for operating the first application, such as sharing. The present application does not limit the specific form of the first option.
[0006] Receive a first operation of the user on the first option; specifically, the first operation can be a click, a double click, or a slide, and the present application does not limit the specific form of the first operation.
[0007] In response to the first operation, a first menu is displayed, and the first menu includes an icon of a second application, and the second application is an application installed on the second electronic device; specifically, the second electronic device may be a display device with a smaller screen, such as a mobile phone. The number of the second applications may be one or more. The second application may correspond to the task type of the first option. For example, if the first option is a sharing type, the second application may be a social software for sharing, such as Weibo, WeChat, etc. This application does not limit the specific form of the second application.
[0008] Receive a second operation of the user on the icon of the second application; specifically, the second operation can be a click, a double-click, or a slide, and the present application does not limit the specific form of the second operation.
[0009] In response to the second operation, a second application is determined, and an application sharing request is sent to the second electronic device, where the application sharing request is used to instruct the second electronic device to start the second application.
[0010] In this embodiment, by sharing the applications on the multi-screen collaborative device, it is possible to achieve application sharing across devices, thereby improving the user experience.
[0011] In one possible implementation manner, before receiving a first operation of the user on the first option, the method further includes:
[0012] A multi-screen collaborative connection is established with a second electronic device.
[0013] In this embodiment, a multi-screen collaborative connection is established between the first electronic device and the second electronic device, thereby enabling multi-screen collaboration between the two devices, and further enabling application sharing between the devices.
[0014] One possible implementation method also includes:
[0015] A second interface is displayed, where the second interface includes a window of a second electronic device.
[0016] In this embodiment, by displaying the window of the second electronic device in the first electronic device, the display content in the second electronic device can be remotely viewed, thereby improving the viewing experience of the user.
[0017] In one possible implementation, the second interface includes the second option, and after the second interface is displayed, the following further includes:
[0018] The device is configured to receive a third operation of the user on the second option; specifically, the second option may be a control corresponding to the second interface, for example, a minimize control. The third operation may be a click, a double click, or a slide, and the present application does not limit the specific form of the second operation.
[0019] In response to the third operation, the window of the second electronic device is minimized.
[0020] In this embodiment, by minimizing the window of the second electronic device, the function of hiding the window of the second electronic device can be achieved, thereby improving the viewing experience of the user.
[0021] One possible implementation method also includes:
[0022] The interface of the second application is displayed in the window of the second electronic device. Specifically, after the second electronic device starts the determined second application, it can also display the interface of the second application, thereby displaying the interface of the second application in the window of the second electronic device through multi-screen collaboration.
[0023] In this embodiment, by displaying the interface of the second application in the window of the second electronic device, it is possible to view the content in the second electronic device in the first electronic device, thereby improving the viewing experience of the user.
[0024] One possible implementation method also includes:
[0025] If the first electronic device has installed the third application, the first menu further includes an icon of the third application. Specifically, the third application may be an application program locally installed on the first electronic device corresponding to the task type of the first option.
[0026] In this embodiment, by displaying the icon of the third application in the first menu, the user can select the third application, thereby allowing the content of the current first application to be processed by the local application, which can increase the user's freedom of selection and further improve the user's usage experience.
[0027] One possible implementation method also includes:
[0028] The first menu also includes a first identifier, which is used to indicate that the second application is an application installed on the second electronic device. Specifically, the first identifier can be a mark that identifies the user source, for example, the name of the second electronic device. This application does not limit the specific form of the first identifier.
[0029] In this embodiment, by marking the source of the second application, the user can be informed of the source of the second application, thereby improving the flexibility of user operation.
[0030] One possible implementation method also includes:
[0031] The second application in the first menu is determined by the task type corresponding to the first option. Specifically, the task type may be a processing type of the content in the current first application, such as sharing, forwarding, etc. This application does not limit the specific form of the above task type.
[0032] In this embodiment, the second application is determined by the task type, which can improve the search efficiency for the second application.
[0033] In one possible implementation manner, before receiving a first operation of the user on the first option, the method further includes:
[0034] Receive first application information sent by the second electronic device, the first application information including installation package information of the second application. Specifically, the installation package information may be information related to the installation package, such as an icon, an installation package name, etc. It is understandable that the installation package information does not include the installation package itself.
[0035] In this embodiment, the second electronic device actively sends the first application information to the first electronic device, so that the first electronic device can obtain the second application in the second electronic device, thereby improving the search efficiency of the second application.
[0036] In one possible implementation manner, after receiving the first application information sent by the second electronic device, the method further includes:
[0037] A simulation is performed based on the first application information sent by the second electronic device to obtain a second application.
[0038] In this embodiment, after receiving the application information sent by the second electronic device, the first electronic device directly performs simulation, thereby improving the search efficiency of the second application.
[0039] In one possible implementation manner, after receiving the first application information sent by the second electronic device, the method further includes:
[0040] Based on the task type corresponding to the first option, the first application information is queried to obtain the second application information matching the task type; based on the second application information, simulation is performed to obtain the second application.
[0041] In this embodiment, the first electronic device only simulates the second application information matching the task type to obtain the second application, thereby reducing redundant second applications, reducing the memory occupancy rate in the first electronic device, and further improving the system efficiency of the first electronic device.
[0042] In one possible implementation manner, after responding to the first operation, the method further includes:
[0043] A query request is sent to the second electronic device based on the task type corresponding to the first option, wherein the query request is used to obtain application information of a second application installed on the second electronic device.
[0044] In this embodiment, the first electronic device actively requests the second electronic device for application information, thereby avoiding receiving redundant application information, thereby reducing the memory occupancy of the first electronic device and improving the system efficiency of the first electronic device.
[0045] In a second aspect, an embodiment of the present application provides an application sharing device, including:
[0046] A first display module, used to display a first interface of a first application, where the first interface includes a first option;
[0047] A first receiving module, used for receiving a first operation of a user on a first option;
[0048] A second display module, configured to display a first menu in response to the first operation, wherein the first menu includes an icon of a second application, and the second application is an application installed on the second electronic device;
[0049] A second receiving module, configured to receive a second operation of a user on an icon of a second application;
[0050] The sharing module is used to determine the second application in response to the second operation, and send an application sharing request to the second electronic device, where the application sharing request is used to instruct the second electronic device to start the second application.
[0051] In one possible implementation, the device further includes:
[0052] A connection module is used to establish a multi-screen collaborative connection with a second electronic device.
[0053] In one possible implementation, the device further includes:
[0054] The third display module is used to display the second interface, where the second interface includes a window of the second electronic device.
[0055] In one possible implementation manner, the second interface includes a second option, and the apparatus further includes:
[0056] The minimization module is used to receive a third operation of the user on the second option; the first electronic device minimizes the window of the second electronic device in response to the third operation.
[0057] In one possible implementation manner, the interface of the second application is displayed in a window of the second electronic device.
[0058] In one possible implementation manner, the first electronic device has installed a third application, and the first menu also includes an icon of the third application.
[0059] In one possible implementation manner, the first menu further includes a first identifier, and the first identifier is used to indicate that the second application is an application installed on the second electronic device.
[0060] In one possible implementation, the second application in the first menu is determined by the task type corresponding to the first option.
[0061] In one possible implementation, the device further includes:
[0062] The third receiving module is used to receive first application information sent by the second electronic device, where the first application information includes installation package information of the second application.
[0063] In one possible implementation, the device further includes:
[0064] The first simulation module is used to perform simulation based on the first application information sent by the second electronic device to obtain a second application.
[0065] In one possible implementation, the device further includes:
[0066] The second simulation module is used to query the first application information based on the task type corresponding to the first option to obtain the second application information matching the task type; and simulate based on the second application information to obtain the second application.
[0067] In one possible implementation, the device further includes:
[0068] The query module is used to send a query request to the second electronic device based on the task type corresponding to the first option, wherein the query request is used to obtain application information of the second application installed on the second electronic device.
[0069] In a third aspect, an embodiment of the present application provides a first electronic device, including:
[0070] A display screen; a processor; a memory; a plurality of applications; and a computer program, wherein the computer program is stored in the memory, and the computer program includes instructions, and when the instructions are executed by the first electronic device, the first electronic device performs the following steps:
[0071] Display a first interface of a first application, where the first interface includes a first option;
[0072] receiving a first operation of a user on a first option;
[0073] In response to the first operation, displaying a first menu, the first menu including an icon of a second application, the second application being an application installed on the second electronic device;
[0074] receiving a second operation of the user on the icon of the second application;
[0075] In response to the second operation, a second application is determined, and an application sharing request is sent to the second electronic device, where the application sharing request is used to instruct the second electronic device to start the second application.
[0076] In one possible implementation manner, when the instruction is executed by the first electronic device, the first electronic device further performs the following steps before performing the step of receiving a first operation of the user on the first option:
[0077] A multi-screen collaborative connection is established with a second electronic device.
[0078] In one possible implementation manner, when the instruction is executed by the first electronic device, the first electronic device further performs the following steps:
[0079] A second interface is displayed, where the second interface includes a window of a second electronic device.
[0080] In one possible implementation, the second interface includes a second option. When the instruction is executed by the first electronic device, the first electronic device further performs the following steps after performing the step of displaying the second interface:
[0081] receiving a third operation of the user on the second option;
[0082] In response to the third operation, the window of the second electronic device is minimized.
[0083] In one possible implementation manner, the interface of the second application is displayed in a window of the second electronic device.
[0084] In one possible implementation manner, the first electronic device has installed a third application, and the first menu also includes an icon of the third application.
[0085] In one possible implementation manner, the first menu further includes a first identifier, and the first identifier is used to indicate that the second application is an application installed on the second electronic device.
[0086] In one possible implementation manner, the second application in the first menu is determined by the task type corresponding to the first option.
[0087] In one possible implementation manner, when the instruction is executed by the first electronic device, the first electronic device further performs the following steps before performing the step of receiving a first operation of the user on the first option:
[0088] First application information sent by a second electronic device is received, where the first application information includes installation package information of a second application.
[0089] In one possible implementation, when the instruction is executed by the first electronic device, the first electronic device further performs the following steps after performing the step of receiving the first application information sent by the second electronic device:
[0090] A simulation is performed based on the first application information sent by the second electronic device to obtain a second application.
[0091] In one possible implementation, when the instruction is executed by the first electronic device, the first electronic device further performs the following steps after performing the step of receiving the first application information sent by the second electronic device:
[0092] Based on the task type corresponding to the first option, query the first application information to obtain second application information matching the task type;
[0093] A simulation is performed based on the second application program information to obtain a second application.
[0094] In one possible implementation manner, when the instruction is executed by the first electronic device, the first electronic device further performs the following steps after performing the step of responding to the first operation:
[0095] A query request is sent to the second electronic device based on the task type corresponding to the first option, wherein the query request is used to obtain application information of a second application installed on the second electronic device.
[0096] It should be understood that the second to third aspects of the present application are consistent with the technical solutions of the first aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here.
[0097] In a fourth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer-readable storage medium is run on a computer, the computer executes the method described in the first aspect.
[0098] In a fifth aspect, the present application provides a computer program, which, when executed by a computer, is used to execute the method described in the first aspect.
[0099] In one possible design, the program in the fifth aspect may be stored in whole or in part on a storage medium packaged together with the processor, or may be stored in whole or in part on a memory not packaged together with the processor. BRIEF DESCRIPTION OF THE DRAWINGS
[0100] Figure 1 An application scenario architecture diagram provided for an embodiment of the present application;
[0101] Figure 2 This is a schematic diagram of the structure of an embodiment of the electronic device of the present application;
[0102] Figure 3 A schematic diagram of the software architecture provided for an embodiment of the present application;
[0103] Figure 4A-4C A schematic diagram of a user interface provided in an embodiment of the present application;
[0104] Figure 5A-5C A schematic diagram of a multi-screen collaborative connection interface provided in an embodiment of the present application;
[0105] Fig. 6A and Figure 6B A schematic diagram of a multi-screen collaborative window provided in an embodiment of the present application;
[0106] Figure 7 A schematic diagram of minimizing a multi-screen collaborative window provided in an embodiment of the present application;
[0107] Figure 8 A flowchart of an application sharing method provided in an embodiment of the present application;
[0108] Fig. 9 and Fig.9A A schematic diagram of the interface operation of the application provided in the embodiment of the present application;
[0109] Fig.10 and Fig.11 A schematic diagram of a menu display interface provided in an embodiment of the present application;
[0110] Fig.12 A schematic diagram of multi-screen collaborative display provided in an embodiment of the present application;
[0111] Figure 13-Figure 15 A schematic diagram of the operation of a file opening scenario provided in an embodiment of the present application;
[0112] Fig.16 A schematic diagram of the structure of an application sharing device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0113] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.
[0114] The technical solution in the embodiment of the present application will be described below in conjunction with the drawings in the embodiment of the present application. In the description of the embodiment of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.
[0115] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.
[0116] With the continuous development of the multi-screen collaboration function between electronic devices, applications based on multi-screen collaboration are becoming more and more diverse. In the prior art, screen sharing between electronic devices can be achieved on the basis of multi-screen collaboration. For example, the screen information of one electronic device can be shared on the screen of another electronic device. Data sharing between electronic devices can also be achieved. For example, a file of one electronic device can be dragged and dropped to another electronic device. However, the prior art only shares visible data across devices, for example, sharing a file. The prior art cannot achieve cross-application operations across devices. For example, an electronic device cannot share applications by calling the application of another electronic device when starting its own application. For example, using multi-screen collaboration, after a tablet computer (referred to as a tablet) and a mobile phone are connected, the tablet computer will mirror the mobile phone window on the same screen. The user can operate mobile phone applications and files in the mobile phone window displayed on the tablet, view some notification messages (such as WeChat, text messages) on the mobile phone side in the tablet notification bar, and answer and hang up calls on the mobile phone side in the small window at the top of the tablet. The user can also operate in the mobile phone collaboration window on the tablet to make a call by mobile phone number or view files on the mobile phone, thereby operating mobile phone applications and files on the tablet. However, the existing technology has the problem of inconvenience in implementing cross-application operations across devices. When a user opens an application on a tablet, the application installed on the mobile phone cannot be directly called from the application to share across devices and applications. For example, when a user browses the web on a tablet, the web link cannot be shared through the social software on the mobile phone.
[0117] To this end, an embodiment of the present application proposes an application sharing method, which can realize application sharing across devices, thereby improving the user experience.
[0118] In order to better understand the application sharing method, electronic device and storage medium provided in the embodiment of the present application, the following first describes the architecture of the interactive system to which the application sharing method provided in the embodiment of the present application is applicable. Figure 1 , Figure 1 Schematic diagram of an interactive system provided by an embodiment of the present application. Figure 1 As shown, the system may include one or more first devices 11 ( Figure 1Only one of the first devices is shown in the figure) and one or more second devices 12 ( Figure 1 Only one of the second devices is shown exemplarily), wherein:
[0119] The first device 11 may install and run one or more applications (applications, APPs), which may be, for example, map, shopping, email, etc., or an application for mapping the display content of the first device 11 to the second device (the subsequent embodiments of this application refer to this application as a "collaborative assistant"). The application may also be referred to as an application.
[0120] The first device 11 may include but is not limited to any handheld electronic product based on an intelligent operating system, which can interact with a user through input devices such as a keyboard, a virtual keyboard, a touch pad, a touch screen, and a voice control device, such as a smart phone, a tablet computer, a handheld computer, a wearable electronic device, etc. Among them, the intelligent operating system includes but is not limited to any operating system that enriches the functions of the device by providing various applications to the device, such as Android, IOS, Windows, MAC and other systems.
[0121] The second device 12 may include but is not limited to a tablet computer, a personal computer, a desktop computer, a television, a car display, a projector display, etc. In this embodiment, the second device 12 can provide display services for the first device 11. The second device 12 needs to run a corresponding program to provide the display service, such as an application program that receives and saves information sent by the first device 11 (hereinafter referred to as a "collaborative assistant") and an application program that displays on the display screen of the second device 12 according to the information sent by the first device 11 (hereinafter referred to as a "window manager"), etc.
[0122] The second device 12 can establish a connection with the first device 11 through a data cable, Bluetooth or a wireless fidelity (WiFi) network to exchange data. Exemplarily, the first device 11 and the second device 12 can achieve communication connection through WiFi p2p technology. When the two devices are connected to the same network, the first device 11 can search and find the second device 12, and then receive the user's operation instructions to achieve communication connection with the second device 12. Or when the two devices are connected to the same network at the same time, the first device 11 can search and find the second device 12 and automatically establish a communication connection with the second device 12. The process of establishing a communication connection between the two devices will be described in detail below, which will not be described in detail here.
[0123] Combine the following Figure 2 First, an exemplary electronic device provided in the following embodiments of the present application is introduced. Figure 2 The electronic device 100 is a schematic diagram showing a structure of the electronic device 100. The electronic device 100 may be Figure 1 The first device 11 or the second device 12 shown in FIG.
[0124] The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 150, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.
[0125] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0126] The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and / or a neural-network processing unit (neural-network processing unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors. Among them, the controller can be the nerve center and command center of the electronic device 200. The controller can generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions.
[0127] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.
[0128] The execution of the application sharing method provided in the embodiment of the present application can be controlled by the processor 110 or completed by calling other components, such as calling the processing program of the embodiment of the present application stored in the internal memory 121, or calling the processing program of the embodiment of the present application stored in a third-party device through the external memory interface 120, to control the wireless communication module 160 to communicate data with other electronic devices, so as to realize application sharing among multiple electronic devices and enhance the user experience.
[0129] In some embodiments, the processor 110 may include one or more interfaces. The interface 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.
[0130] 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 groups of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface, thereby realizing the touch function of the electronic device 100.
[0131] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to achieve communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 via the I2S interface to achieve the function of answering a call through a Bluetooth headset.
[0132] The PCM interface can also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface to realize the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.
[0133] The UART interface is a universal serial data bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is generally used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.
[0134] The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate via the DSI interface to implement the display function of the electronic device 100.
[0135] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.
[0136] The USB interface 130 is an interface that complies with the USB standard specification, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and a peripheral device. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices, such as AR devices, etc.
[0137] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.
[0138] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.
[0139] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.
[0140] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.
[0141] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate 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 the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be arranged in the same device as the mobile communication module 150 or other functional modules.
[0142] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.
[0143] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through 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. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).
[0144] The electronic device 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.
[0145] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.
[0146] In the embodiment of the present application, the electronic device 100 can display a user interface through the display screen 194 .
[0147] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.
[0148] ISP is used to process the data fed back by camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to ISP for processing and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, ISP can be set in camera 193.
[0149] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.
[0150] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.
[0151] Video codecs are used to compress or decompress digital videos. The electronic device 100 may support one or more video codecs. Thus, the electronic device 100 may play or record videos in a variety of coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.
[0152] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.
[0153] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.
[0154] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the internal memory 121, and / or instructions stored in a memory provided in the processor.
[0155] The electronic device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.
[0156] The touch sensor 180K is also called a "touch panel". The touch sensor 180K can be set on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194.
[0157] In the embodiment of the present application, the electronic device 100 can receive user operations through the touch sensor 180K, such as single-click, double-click or sliding operations.
[0158] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.
[0159] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.
[0160] Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.
[0161] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195. The electronic device 100 can support 1 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, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.
[0162] based on Figure 2 The hardware structure diagram of the electronic device 100 of the embodiment of the present application is shown in FIG. 1 , and the software structure block diagram of the electronic device 100 and the first device of the embodiment of the present application is introduced below. Figure 3 shown.
[0163] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The present application embodiment takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100 and the first device.
[0164] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, kernel layer, and connection layer.
[0165] The application layer can include a series of application packages.
[0166] Among them, the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, short message and collaborative assistant.
[0167] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.
[0168] Among them, the application framework layer can include activity management services, application continuation flow services, installation package management services, application selector, window manager, resource manager and display framework, etc.
[0169] The activity management service is used to notify the collaborative assistant of the event of starting the simulation application, so that the collaborative assistant starts the corresponding simulation application.
[0170] The application connection transfer service is used to connect the electronic device 100 with the first device (eg Figure 1 The first device 11) shown in the figure notifies the "collaborative assistant" of each event of establishing a connection at the application layer, and can also be used to assist the "collaborative assistant" in obtaining data information in response to the instructions of the "collaborative assistant" at the application layer. Exemplarily, the data information obtained by the application continuation flow service includes the installation package information of the application installed on the first device. Exemplarily, the application continuation flow service can implement the "Onehop" service and the multicast source discovery protocol (MSDP) service, that is, the electronic device 100 can establish a communication connection with the first device based on the Onehop service and the MSDP service.
[0171] The installation package management service is used to manage the installation and uninstallation of application installation packages, as well as the parsing and query of installation package configuration information.
[0172] The application chooser is used to query available applications and invoke the application selected by the user.
[0173] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.
[0174] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.
[0175] The display framework is used to obtain the display data of the interface or window of the application being displayed in the electronic device 100, and send the display data of the interface or window to the "cooperative assistant" through the application connection flow service. It can also be used to obtain the display data received by the "cooperative assistant" from the first device (for example, Figure 1 Display data of the first device 11) shown, etc.
[0176] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, sensor driver and virtual device system.
[0177] The virtual device system is used to virtualize the devices in the first device in the electronic device 100. Exemplarily, through the virtual device system, the electronic device 100 can virtualize the touch screen of the first device, that is, the screen of the electronic device 100 can be used as the second screen of the first device (for example, the second screen can correspond to the collaborative window), and the screen of the first device itself can be used as the first screen, so that when the user operates on the second screen of the electronic device 100, the first device can receive the corresponding operation, that is, when the user operates on the above-mentioned second screen, it can be considered that the user operates on the first screen, thereby realizing the collaborative operation between the electronic device 100 and the first device.
[0178] Next, in combination with the first device (for example Figure 1 The scene in which the first device 11) transmits data to the electronic device 100 is used to exemplify the workflow of the software and hardware of the electronic device 100. It should be noted that the desktop of the electronic device 100 may be one or more user interfaces displayed in the main screen area after the electronic device is turned on and the system of the electronic device is successfully logged in. These user interfaces may include icons and names of applications installed on the electronic device.
[0179] After the user installs any application in the first device, the installation package information of the application can be stored in the installation package management service. The installation package information may include information such as the application icon and application capabilities, and the application capabilities are used to identify the content formats that the application can receive or the files formats that the application can open. It can be understood that the installation package information does not include the installation package itself.
[0180] The application transfer service can obtain the installation package information in the installation package management service, call the connection service of the connection layer, and send the installation package information to the electronic device 100 through the connection service.
[0181] After receiving the installation package information sent by the first device through the connection service, the electronic device 100 sends the installation package information to the application connection transfer service. Then, the electronic device 100 sends the installation package information to the collaborative assistant through the application connection transfer service.
[0182] After receiving the installation package information, the collaborative assistant in the electronic device 100 simulates the installation package and stores the installation package information in the installation package management service.
[0183] The user can perform a touch operation on the display screen 194 of the electronic device 100. When the touch sensor 180K in the electronic device 100 receives the user's touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, timestamp of the touch operation, and other information). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event.
[0184] Taking the touch operation as a touch single-click operation, and the control corresponding to the single-click operation is a control of the "browser" application as an example, the "browser" application calls the application connection flow service interface of the application framework layer, starts the "browser" application, and obtains the user interface (UI) of the "browser" application.
[0185] The user can also perform touch operations on the user interface of the above-mentioned "browser" application. For example, the user can click the control corresponding to the "share" function key to share the current page of the "browser" application. The touch sensor 180K in the electronic device 100 receives the user's touch operation, and the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event. The application selector in the application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event. Then, the application selector queries the installation package management service for available applications based on the current control (for example, the above-mentioned "share" control), and the available application can be an application for sharing the page of the above-mentioned "browser" application. The available application includes the application installed by the electronic device 100 itself (for example, the microblog application), and also includes the application installed by the first device (for example, the WeChat application). After receiving the query request of the application selector, the installation package management service returns one or more available application names to the application selector based on the stored installation package information.
[0186] Then, the user can further perform a touch operation on the user interface of the above-mentioned "browser" application to complete the operation of selecting an application from the above-mentioned one or more available applications. For example, the user can click the control corresponding to the "WeChat" icon to call the "WeChat" application. The touch sensor 180K in the electronic device 100 receives the user's touch operation, and the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event. The application selector in the application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event. Then, the application selector initiates a call request to the activity management service based on the current control (for example, the above-mentioned "WeChat" application control), wherein the call request can include the currently shared content (for example, the page of the above-mentioned "browser" application) and the name of the called application (for example, the above-mentioned "WeChat" application).
[0187] The activity management service receives the call request sent by the application selector, and sends the call request to the "collaborative assistant" application of the application layer to simulate the application of this request.
[0188] After the "Collaboration Assistant" application receives the call request sent by the activity management service, it simulates the application in the call request (for example, the above-mentioned "WeChat" application) and sends the name of the called application and the shared content to the first device through the connection service of the connection layer.
[0189] After receiving the name of the called application and the shared content through the connection service of the connection layer, the first device sends the name of the called application and the shared content to the application connection flow service.
[0190] The application continuation flow service can start the application based on the name of the called application program, and share the above-mentioned shared content in the application, thereby completing the data sharing between the electronic device 100 and the first device.
[0191] It should be noted that the second device (eg Figure 1 The hardware structure and software structure framework of the second device 12) shown in FIG. Figure 2 and Figure 3 Of course, the hardware structure and software structure framework of the first device and the second device (the above-mentioned electronic device 100) may not be completely the same, which is determined according to actual conditions and will not be repeated here.
[0192] Based on the above Figure 1 The system framework shown, Figure 2 The hardware framework of the device shown and Figure 3The device software framework shown, the embodiment of the present application provides an application sharing method and an electronic device. The device involved in the embodiment of the present application is installed with a "collaborative assistant" application. In the embodiment of the present application, it is necessary to transfer the application information of the first device to the second device under the condition that the "collaborative assistant" of the device is turned on.
[0193] "Collaboration Assistant" can be a service or function provided by a device, which can be used to establish a communication connection between a first device and a second device, to achieve data transmission between the first device and the second device, and to achieve command transmission between the second device and the first device, etc. For example, "Collaboration Assistant" can be an Android installation package (AndroidPackage, APK), which can be installed in the device in the form of a control or APP.
[0194] In a specific implementation, the three functions of establishing a communication connection between the first device and the second device, transmitting data between the first device and the second device, and transmitting instructions between the second device and the first device may not be integrated in one APK file, but may be implemented through one or more APK files.
[0195] It is understandable that "collaborative assistant" is just a term used in this embodiment, and its meaning has been recorded in this embodiment. Its name does not constitute any limitation to this embodiment.
[0196] The following is an illustrative introduction to some user interfaces (UI) provided by the first device and the second device in the embodiments of the present application. The term "user interface" in the specification, claims and drawings of the present application refers to a medium interface for interaction and information exchange between an application or an operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. A common form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operations displayed in a graphical manner. A GUI can be an interface element such as an icon, window, or control displayed on a display screen of an electronic device, wherein a control can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.
[0197] Figure 4A An exemplary user interface 41 on the second device for displaying applications installed on the second device is exemplarily shown.
[0198] The user interface 41 may include: a status bar 401, application icons 402, a page indicator 403, a tray 404 with common application icons, and other indicators ( Figure 4A ). Where:
[0199] The status bar 401 may include: one or more signal strength indicators 401A of wireless fidelity (Wi-Fi) signals, a Bluetooth indicator 401B, a battery status indicator 401C, and a time indicator 401D.
[0200] The application icons 402 include icons of a first application, a second application, a third application, a fourth application, a fifth application, a sixth application, and a seventh application, etc. These applications may be mailbox, mobile manager, gallery, Huawei Mall, video, Internet, clock, QQ, WeChat, Taobao, Amap, etc.
[0201] The page indicator 403 can be used to indicate which page the user is currently browsing. The user can slide the area of the application icon 402 left and right to browse the application icons in other pages. These pages can also be called the desktop of the second device.
[0202] The tray 404 with common application icons may display icons of an eighth application, a ninth application, a tenth application, an eleventh application, etc. These applications may be relatively common applications, such as settings, music, reading, and camera, etc.
[0203] In some embodiments, the user interface 41 may further include a navigation bar, wherein the navigation bar may include system navigation keys such as a return key, a home screen key, and a multitasking key. When it is detected that the user clicks the return key, the second device may display the previous page of the current page. When it is detected that the user clicks the home screen key, the second device may display the main interface. When it is detected that the user clicks the multitasking key, the second device may display the task that the user has recently opened. The naming of each navigation key may also be other, and this application does not limit this. Not limited to virtual keys, each navigation key in the navigation bar may also be implemented as a physical key.
[0204] In some other embodiments, the second device may further include a physical home screen key. The home screen key may be used to receive instructions from the user and return the currently displayed UI to the main interface, so that the user can view the home screen at any time. The above instructions may specifically be an operation instruction for the user to press the home screen key once, or an operation instruction for the user to press the home screen key twice in a short period of time, or an operation instruction for the user to long press the home screen key within a predetermined time. In some other embodiments of the present application, the home screen key may also be integrated with a fingerprint identifier so that fingerprint collection and identification can be performed when the home screen key is pressed.
[0205] Understandably, Figure 4A The user interface on the second device is merely illustrated as an example and should not constitute a limitation on the embodiments of the present application.
[0206] The following is an exemplary introduction to a method for opening the "collaborative assistant" on the second device provided in an embodiment of the present application.
[0207] Figure 4A and Figure 4B An operation of opening a “collaborative assistant” on a second device is exemplified.
[0208] like Figure 4A As shown, when the second device detects a downward sliding gesture on the status bar 401, in response to the gesture, the second device may display a window 405 on the user interface 41. Figure 4B As shown, a switch control 405A of the "collaborative assistant" may be displayed in window 405, and switch controls of other functions (such as WiFi, Bluetooth, flashlight, etc.) may also be displayed. When a touch operation (such as a click or touch operation on the switch control 405A) in window 405 is detected, the second device may turn on the "collaborative assistant" in response to the touch operation.
[0209] That is, the user can make a downward sliding gesture at the status bar 401 to open the window 405, and can conveniently turn on the "collaborative assistant" by clicking the switch control 405A of the "collaborative assistant" in the window 405. The switch control 405A of the "collaborative assistant" can be expressed in, but not limited to, text information and / or icons.
[0210] In one possible implementation, the "Collaborative Assistant" can also be displayed on the desktop of the second device in the form of an application icon like mailboxes, gallery and other applications. When the second device detects an operation such as a click or touch on the "Collaborative Assistant" icon, the "Collaborative Assistant" on the second device is opened.
[0211] In some embodiments of the present application, after the second device turns on the "collaborative assistant", a prompt message indicating that the "collaborative assistant" has been turned on may also be displayed in the status bar 401. For example, an icon of the "collaborative assistant" may be displayed in the status bar 401, or the text "collaborative assistant" may be directly displayed. Figure 4C ,exist Figure 4C In FIG. 4 , icon 406 is the icon of the “collaborative assistant”. It should be noted that the icon of the “collaborative assistant” is not limited to Figure 4B and Figure 4C The icon shown in is only an example, and this solution does not limit the specific form of the "collaborative assistant" icon.
[0212] In the embodiments of the present application, the method of enabling the "collaborative assistant" is not limited to the above-mentioned method. In some embodiments, the "collaborative assistant" can also be enabled in other ways. In other embodiments, the second device can also enable the "collaborative assistant" by default, for example, automatically enabling the "collaborative assistant" after booting.
[0213] The operation of enabling the "collaborative assistant" on the first device can refer to the operation of enabling the "collaborative assistant" on the second device, which will not be repeated here. After enabling the "collaborative assistant" of the first device and the second device, the first device can establish a communication connection with the second device and then transmit data to the second device.
[0214] The following exemplarily introduces some embodiments of a graphical user interface implemented in the process of establishing a communication connection between the first device and the second device after the "collaborative assistant" function is enabled on the first device and the second device.
[0215] First, the following describes, by way of example, a process in which the first device is a mobile phone and the second device is a tablet personal computer (Tablet PC), the first device and the second device discover each other and establish a connection through near field communication (NFC). The following describes the process of establishing a connection between the two devices in two cases.
[0216] Case 1: The first device and the second device are not logged in to the same system account.
[0217] In a specific embodiment, it is assumed that the first device and the second device are both devices of the same brand, but the two devices are not logged into the same system account after being turned on; or the first device and the second device are not devices of the same brand. In these cases, it indicates that the first device and the second device are devices with different accounts, that is, devices that are not logged into the same system account at the same time. At this time, the first device and the second device can be connected in the following way.
[0218] Specifically, both the first device and the second device have NFC functions. When the NFC functions of the first device and the second device are turned on, the first device can be brought close to or in contact with the second device. For example, a preset part of the first device, such as the back, can be brought close to or touch a preset position of the second device, such as a position with a sharing or connection tag. The first device and the second device can then discover each other, and the display screen of the first device can display the user interface of the discovered second device, such as Figure 5A The interface shown.
[0219] exist Figure 5AThe user interface shown includes a window 501 , which includes an icon 5011 of a discovered second device, a name 5012 of the second device, prompt information 5013 , a “connect” control 5014 and a “cancel” control 5015 .
[0220] Among them, the icon 5011 of the second device can be, for example, an icon of a tablet computer, etc. The name 5012 of the second device can be, for example, HUAWEI MatePad Pro X, etc. The prompt information 5013 can be used to explain to the user the role of the "connect" control 5014 and the function after the connection. For example, the prompt information 5013 can be "Click 'Connect' to turn on WLAN and Bluetooth. After connecting, you can operate the mobile phone on the HUAWEI MatePad Pro X and share data between devices." etc. The "connect" control 5014 can be used to send a connection confirmation request to the second device. The "cancel" control 5015 can be used to cancel the connection operation between the second device and the second device.
[0221] Optional, in Figure 5A After clicking the "connect" control 5014, WLAN and Bluetooth will be turned on, so the process of establishing a connection between the first device and the second device can be completed through Bluetooth. After the connection is successfully established, data interaction and sharing between the first device and the second device can be achieved through WLAN. After the connection is established through Bluetooth, data interaction between the first device and the second device in the form of WLAN can increase the speed of data interaction and improve the efficiency of mutual response.
[0222] exist Figure 5A In the user interface shown, the first device displays the following in response to the touch operation on the "connect" control 5014: Figure 5B The user interface is shown. Figure 5B In the embodiment, a window 502 is included in which a first device sends a connection confirmation request to a second device and waits for confirmation from the second device. The window 502 may also include an icon 5021 of the second device, a prompt message 5022 and a "cancel" control 5023.
[0223] The icon 5021 of the second device may be, for example, an icon of a tablet computer, etc. The prompt information 5022 is used to indicate that confirmation of the second device is being waited for. For example, the prompt information 5022 may be “Please confirm the connection on the HUAWEI MatePad Pro X…”, etc. The “Cancel” control 5023 may be used to cancel the connection operation between the first device and the second device.
[0224] exist Figure 5AIn the user interface shown, the first device sends a connection request to the second device in response to the touch operation on the "connect" control 5014. After receiving the connection request, the second device displays the following Figure 5C The user interface shown.
[0225] exist Figure 5C The user interface shown includes a confirmation window 503 for whether the second device is connected to the first device. The window 503 includes an icon 5031 of the second device, an icon 5032 of the first device, an association symbol 5033 between the second device and the first device, a prompt message 5034, a "reject" control 5035, and an "allow" control 5036.
[0226] Among them, the icon 5031 of the second device can be, for example, an icon of a tablet, etc. The icon 5032 of the first device can be, for example, an icon of a mobile phone, etc. The prompt information 5034 can be used to prompt whether to connect, explain to the user the role of the "Allow" control 5036 and the function after the connection, for example, the prompt information 5034 can be "Do you allow HUAWEI Nova 7 to connect to this computer. Click "Allow" to operate the mobile phone on the HUAWEI MatePad Pro X and share data between devices. This function will turn on WLAN and Bluetooth." etc. In the example, HUAWEI Nova 7 is the name of the first device, and the "Reject" control 5035 can be used to reject the connection with the second device. The "Allow" control 5036 can be used to establish a connection with the second device. Among them, HUAWEIMatePad Pro X is the name of the second device.
[0227] exist Figure 5C In the user interface shown, the second device confirms to establish a connection with the first device in response to a click or touch operation on the "Allow" control 5036. After the connection is established, the user interface diagram of the second device may be, for example, Fig. 6A The interface diagram shown indicates that a connection has been successfully established between the first device and the second device, that is, the information of the first device is transmitted to the second device and displayed on the display screen. Figure 6B The interface shown will be introduced in detail below and will not be described in detail here.
[0228] The first device and the second device can be connected to the same wireless network. If the first device and / or the second device has been connected to the wireless network, Figure 5A and / or Figure 5C In the interface shown, you do not need to connect to the wireless network again.
[0229] A specific implementation method of transmitting the information of the first device to the second device and displaying it on the display screen may include:
[0230] After the first device successfully establishes a connection with the second device, the first device's "application transfer service" (for example Figure 3 The application connection transfer service of the application framework layer in the first device) notifies the "cooperative assistant" of the first device (for example, Figure 3 The "cooperative assistant" in the application layer of the first device responds to the event notification through the resource manager of the first device (for example Figure 3 The resource manager of the application framework layer in the first device or the "application continuation flow service" of the first device obtains the first interface display information on the first device.
[0231] The first interface display information is information about the first user interface of the first application being displayed on the display screen of the first device, and the information may include data used by the first device to display the first user interface. Specifically, the first interface display information may include stack information of the first user interface being displayed on the display screen and data on the content displayed on the interface, etc. The stack information may include the package name and class name of the activity service of the displayed application, etc. The resource manager or "application continuation flow service" of the first device may be a "display framework" (e.g. Figure 3 The display framework of the application framework layer in the application framework layer is used to obtain the data of the content displayed on the interface.
[0232] After the "cooperative assistant" of the first device obtains the first interface display information, it can send the first interface display information to the second device via WLAN, that is, the wireless network connected above. The second device receives the first interface display information through its own "cooperative assistant" and sends the first interface display information to its own "display framework" through its own "application continuation flow service". The "display framework" mobilizes the window manager (for example, Figure 3 A window manager of the application framework layer in the application program) displays a window on a display screen, and the content displayed in the window includes the content displayed by the above-mentioned first user interface.
[0233] This window can be seen, for example, Fig. 6A The size of the window 601A matches the size of the display screen of the first device. Fig. 6A The window 601A shown in FIG. 601A may be referred to as a first window, but the content displayed in the first window is not limited to the content shown in the window 601A.
[0234] The above-mentioned first application can be any application installed in the first device. The first application can be a necessary application installed in the first device when it leaves the factory, such as a desktop application, a file management or setting system application. Alternatively, the first application can also be an optional application installed in the first device, such as a third-party application such as WeChat, Taobao, AutoNavi Maps or Meituan. The optional application is not limited to a third-party application, and can also be an application produced by the brand of the first device, such as Huawei's "Application Market" application. Some applications can sometimes be necessary system applications, and sometimes they can be optional applications. For example, Huawei's "Application Market" application can be a necessary system application for the first device in some possible embodiments.
[0235] In the embodiments of the present application, the first application is mainly illustrated by taking third-party applications such as WeChat as an example, but this does not constitute a limitation to the present technical solution.
[0236] For example, the window of the first device mapped to the second device can also be seen Figure 6B , Figure 6B The window 601B shown is the user interface of the "Application Market" application, that is, the user interface displayed in the first device is also the user interface of the "Application Market". It should be noted that Figure 6B The user interface displayed in window 601B may also be the user interface of other applications, for example, it may be the user interface of applications such as WeChat, QQ or Huawei Mall, etc. The specific application is not limited in this solution.
[0237] Similarly, in the embodiment of the present application, Figure 6B The window 601B shown in FIG. 601 may also be referred to as a second window, but the content displayed in the second window is not limited to the content shown in the window 601B.
[0238] Fig. 6A The window 601 shown in FIG. 6 is a schematic diagram of a desktop of the first device. The desktop of the first device is also an application, namely the above-mentioned desktop application. Therefore, Fig. 6A The window 601 shown in FIG. 6 can also be said to include a user interface of the desktop application of the first device.
[0239] It should be noted that in addition to the resource manager and the "collaborative framework", the "collaborative assistant" of the first device can also obtain the above-mentioned first interface display information through other modules of the application framework layer in response to the above-mentioned event notification, and the embodiment of the present application does not limit this.
[0240] Case 2: The first device and the second device log in to the same system account.
[0241] In a specific embodiment, it is assumed that the first device and the second device are devices of the same brand, and the two devices log in to the same system account after being turned on, that is, the two devices are same-account devices. In this case, the first device and the second device can be connected in the following manner.
[0242] Specifically, when the NFC functions of the first device and the second device are both turned on, the second device can be brought close to or in contact with the second device. For example, a preset part of the second device, such as the back, can be brought close to or touched to a preset position of the second device, such as a position with a sharing or connection tag. The first device and the second device can then discover each other, and the display screen of the second device can display the user interface of the discovered second device. For example, see Figure 5A The interface shown.
[0243] exist Figure 5A In the user interface shown, the second device sends a connection request to the second device in response to the touch operation on the "connect" control 5014. Because the first device and the second device are devices with the same account, a trust relationship is automatically established. After the second device receives the connection request sent by the second device, it will automatically confirm the connection. After the connection is confirmed, the connection between the two devices is completed. For example, at this time, the second device displays Fig. 6A or Figure 6B The user interface shown.
[0244] It should be noted that the method of establishing a communication connection between the first device and the second device to achieve data sharing also includes other methods, for example, it can also be achieved through Bluetooth, data cable or other methods of near-field communication NFC, etc., and the embodiments of the present application do not limit this.
[0245] The following describes some embodiments of a graphical user interface implemented on a second device after a connection is established between the first device and the second device, with the second device being a tablet computer as an example.
[0246] See also Fig. 6A and Figure 6B , Fig. 6A and Figure 6B 10. ... Fig. 6A Window 601A and Figure 6B Window 601B is shown. Window 601A and window 601B may be referred to as collaborative windows.
[0247] exist Fig. 6A and Figure 6BAs can be seen in FIG, the size of window 601A and window 601B does not match the size of the display screen of the second device. The mismatch may mean that the aspect ratio of window 601A and window 601B may be different from the aspect ratio of the display screen of the second device, or that window 601A and window 601B only occupy a part of the display screen of the second device.
[0248] exist Fig. 6A In addition to the user interface 601A1 mapped from the first device (the user interface 601A1 mapped from the first device can be called a mapping window 601A1), the middle window 601A can also include a title bar 601A2, which can include a hide control 6011, a minimize control 6012, a maximize control 6013 and the name 6014 of the first device.
[0249] The hiding control 6011 can be used to hide the window 601A. In response to a click or touch operation on the hiding control 6011, the second device hides the window 601A. Fig. 6A By clicking or touching the "collaborative assistant" icon 602 shown in the figure, the display interface of the recovery window 601A on the display screen is restored.
[0250] In a possible implementation, the hidden control 6011 can be used to disconnect the first device from the second device, and the second device can actively disconnect from the first device in response to a click or touch operation on the hidden control 6011. If the second device needs to re-establish a connection with the first device, please refer to the corresponding description of establishing a connection, which will not be repeated here.
[0251] The minimize control 6012 can be used to minimize the window 601A. In response to a click or touch operation on the minimize control 6012, the second device minimizes the window 601A, for example, minimizing the window 601A to the edge of the display screen of the second device. For example, see Figure 7 .exist Figure 7 In the example, the small window 701 is the minimized window 601A. For example, the small window 701 may include the name of the first device, such as HUAWEI Nova 7. It should be noted that the position of the small window 701 in the display screen of the second device is not limited to Figure 7 The position shown in can be any position of the edge of the display screen. The second device can restore the window 601A in response to a click or touch operation on the small window 701.
[0252] Alternatively, the minimize control 6012 can be used to switch the window 601A to run in the background, and when the window 601A needs to be displayed on the display screen, the window 601A is called out from the background.
[0253] The maximize control 6013 can be used to maximize the window 601A. In response to a click or touch operation on the maximize control 6013, the second device maximizes the window 601A, for example, fills the entire screen with the window 601A, etc. The use and function of the maximize control will be described in detail below and will not be described in detail here.
[0254] The name 6014 of the first device may be, for example, HUAWEI Nova 7, etc.
[0255] Figure 6B The composition and function of the window 601B in FIG. Fig. 6A The description of window 601A in FIG. 6 is not repeated here.
[0256] After the first device and the second device establish a communication connection, the first device can send the data of the user interface displayed on its own display screen and the information used to display the user interface to the second device through the "collaboration assistant" in real time. The second device can update the collaboration window in real time according to the acquired information, so that the content displayed in the collaboration window always includes the content currently displayed on the display screen of the first device.
[0257] Now combined Figure 8-Figure 15 The application sharing method of this application is described. Figure 8 This is a flow chart of an embodiment of the application sharing method of this application, such as Figure 8 As shown, the above application sharing method may include:
[0258] Step 101: Establish a multi-screen collaborative connection between a first device and a second device.
[0259] Specifically, the first device and the second device may be electronic devices with display screens, such as mobile phones, tablets, and computers. Preferably, the first device may be an electronic device with a small display screen, such as a mobile phone. The second device may be an electronic device with a large display screen, such as a tablet or a computer. This embodiment of the application is not limited to this.
[0260] The first device can establish a multi-screen collaborative connection with the second device. The specific process of establishing a multi-screen collaborative connection can refer to the above Figures 4A-5C When the first device establishes a multi-screen collaborative connection with the second device, the screen of the first device can be displayed in the screen of the second device. For example, the following can be obtained: Fig. 6A The multi-screen collaboration screen shown.
[0261] It is understandable that in the multi-screen collaborative connection state, the user can also operate in the multi-screen collaborative window on the second device screen to remotely control the application in the first device.
[0262] After the first device and the second device establish a multi-screen collaborative connection, the first device may send application information to the second device. Optionally, the first device may send application information to the second device in an active manner and a passive manner. The active manner includes steps 102A to 102C, and the passive manner includes steps 106A to 106C.
[0263] Next, taking the first device actively sending application information as an example, steps 102A to 102C are used for explanation.
[0264] Step 102A: The first device monitors application program changes.
[0265] Specifically, after the multi-screen collaborative connection is established between the first device and the second device, the first device can monitor the information changes of the application in the first device. For example, an installation package program can be executed on the first device to install an application. After the application is installed, an application icon can be generated on the interface of the first device, and the installation package information corresponding to the icon is stored in the first device.
[0266] When the installation package information in the first device changes, the first device can monitor the installation package information in the installation package management service through the application continuation flow service to obtain the change of the installation package information, thereby knowing the change of the application. Exemplarily, the first device can monitor the installation package information in the installation package management service through the application continuation flow service in the application framework layer, thereby determining the change of the application. In addition, the first device can also monitor the notification message to determine the change of the application. The notification message is used to notify the change of the application. For example, the installation package management service in the application framework layer of the first device can send a notification message to the application continuation flow service when the application is installed, uninstalled or upgraded to notify the change of the application.
[0267] It is understandable that the above-mentioned application changes may include adding a new application or deleting an application.
[0268] What is described above is that after the first device establishes a multi-screen collaborative connection with the second device, when the installation package information in the first device changes, the operation of triggering the first device to send application information.
[0269] Optionally, after establishing a multi-screen collaborative connection with the second device, the first device can also actively send the existing application information in the first device to the second device, that is, sending the application information does not need to rely on the condition that the installation package information changes, and the embodiment of the present application does not make any special limitations on this.
[0270] Step 102B: If the first device monitors changes in the application program, the application program information is obtained.
[0271] Specifically, when the first device monitors the information change of the application, the application information can be obtained by querying. Exemplarily, the first device can query the installation package information stored in the installation package management service, and can obtain the corresponding application information by querying the installation package information. Preferably, the first device can also obtain the installation package incremental information by querying. That is, the information of the newly installed application can be obtained by querying. For example, if the installation package management service contains installation package A and installation package B, and a new installation package C is added at this time, the first device can obtain the installation package incremental information (for example, installation package C information) by querying, that is, the application incremental information (for example, application C information) can be obtained; wherein, application C is the application corresponding to installation package C. There is no need to obtain the information of installation package A and installation package B, that is, there is no need to obtain the information of application A and application B. Among them, application A is the application corresponding to installation package A, and application B is the application corresponding to installation package B, thereby improving data transmission efficiency and saving system resources.
[0272] It is understandable that the first device may also obtain installation package reduction information, thereby sending the installation package reduction information to the second device. The installation package reduction information may be information about the uninstalled or deleted installation package.
[0273] The application information may include an application icon and a task type. The task type is used to identify the executable task type corresponding to the application. For example, an application may correspond to task types such as opening a file A, sharing a link B, editing a document C, or sending an email D.
[0274] Step 102C: The first device sends the application information to the second device.
[0275] Specifically, the first device can send the application information to the second device through the connection service of the connection layer. The connection service can be a connection channel based on WIFI, a connection channel based on Bluetooth, or a short-range wireless connection channel based on other forms, which is not limited in the embodiments of the present application.
[0276] In this embodiment, by actively sending the application information to the second device, the second device can be informed of the applications that can be simulated in advance, thereby improving the efficiency of the simulation.
[0277] When the second device receives the application information sent by the first device, it can construct a simulated application according to the application information. Optionally, the method of constructing the simulated application may include active construction and on-demand construction. The active construction method includes steps 103A and 103B, and the on-demand construction method includes step 107.
[0278] Next, the method of the second device actively constructing the application information is taken as an example to explain through steps 103A and 103B.
[0279] Step 103A: The second device receives the application information sent by the first device, and constructs a simulation application according to the application information.
[0280] Specifically, the second device can receive the application information sent by the first device through the application continuity flow service of the application framework layer, and can construct a simulated application according to the application information through the collaborative assistant of the application layer. Among them, the simulated application can be used to simulate the entrance of the application corresponding to the application information. In other words, the entrance of the application can be simulated in the second device through the collaborative assistant. For example, after the second device constructs the simulated application, the entrance of the application corresponding to the simulated application can be generated in the second device, and the application in the first device can be called through the entrance, so that the first device can start the application, and the user can view the content of the application through the multi-screen collaborative window in the second device.
[0281] In a specific implementation, after the collaborative assistant of the application layer of the second device receives the application information sent by the first device, it can determine whether there are any new or deleted applications in the application information received this time. Exemplarily, the application information received this time can be compared with the constructed simulated application. If there is any new application in the application information that has not been constructed as a simulated application in the collaborative assistant, a simulated application can be constructed for the new application in the collaborative assistant. If the collaborative assistant contains a simulated application corresponding to the name of an application that has been deleted or uninstalled in the application information, the simulated application can be deleted.
[0282] Step 103B: The second device stores the simulated application information.
[0283] Specifically, after the collaborative assistant in the application layer of the second device completes the construction of the simulated application, it can send the information of the simulated application to the installation package management service of the application framework layer so as to store the simulated application information in the installation package management service. The information of the simulated application may include a simulated application icon and a task type corresponding to the simulated application.
[0284] In this embodiment, the application information sent by the first device is actively constructed so that the corresponding simulation application can be quickly called, thereby improving the efficiency of the simulation.
[0285] Step 104 : In response to the detected first operation of the user for data sharing, the second device generates a data sharing task based on the first operation, wherein the data sharing task includes task data and a task type.
[0286] Specifically, the user can perform a data sharing operation in the second device to initiate a data sharing task. For example, the user can share the currently browsed web page when browsing the web on the display screen 194 in the second device. In response to the user's operation, the application manager of the application framework layer of the second device can create a data sharing task (for example, a web page sharing task). Among them, the data sharing task may include task data and task type. Exemplarily, the task type may include sharing type and playback type, etc. For example, the sharing type may include a task for sharing a web page, and the playback type may include a task for playing a video; the task data may include the address of the data, for example, the task data for sharing a web page may be the link address of the web page, and the task data for playing a video may be the link address of the video file, etc.
[0287] Let's take web page sharing as an example. Fig. 9 FIG. 9 is a schematic diagram of a user interface 900 of a second device, and a user can perform a webpage sharing operation on the user interface 900 of the second device. Fig. 9 , the user interface 900 includes a control 910 and a browsing area 920. The control 910 corresponds to the function options of the current page. Exemplarily, the function options may include sharing, sending or playing, etc. The browsing area 920 is used to display the content of the page currently browsed by the user. It can be understood that the display content in the above browsing area 920 can be the task data of this time. In addition, the user interface 900 can also include a multi-screen collaborative window 921. In a specific implementation, the multi-screen collaborative window 921 can be superimposed on the browsing area 920. The multi-screen collaborative window 921 is used to display the user interface of the first device. In some embodiments, the above-mentioned multi-screen collaborative window 921 can also be minimized, so that the following can be obtained: Fig.9A User interface 900A is shown. Fig.9A, user interface 900A includes control 910, browsing area 920 and small window 921A. Among them, small window 921A can be a window after the multi-screen collaboration window 921 is minimized. At this time, the user can operate control 910 in user interface 900A. Exemplarily, small window 921A may include the name of the first device, such as HUAWEI Nova 7, etc. It should be noted that the position of small window 921A in the display screen of the second device is not limited to Fig.9A The position shown in may be any position of the edge of the display screen. The second device may restore the window 921 in response to a click or touch operation on the small window 921A.
[0288] Step 105: The second device queries corresponding application information according to the task type.
[0289] Specifically, after the application continuation flow service of the second device creates a data sharing task, it can query the installation package management service of the second device according to the task type to obtain the application information corresponding to the task type, that is, the available applications corresponding to the data sharing task can be obtained. The application information can be information about one application or multiple applications. Exemplarily, taking the sharing type as an example, if the second device wants to share a link to a web page, it can query one or more application information corresponding to the sharing type. For example, it can query the social application corresponding to the sharing type. The application information may include the application information stored by the installation package program executed in the second device, and the simulated application information constructed by the second device after receiving the application information of the first device. That is to say, the installation package management service of the second device can include applications installed by itself and applications simulated based on the application information of the first device.
[0290] It should be noted that when the second device executes the installation package program to obtain the application, the second device can create corresponding application information for the application. The application information includes the application icon and the task type corresponding to the application. Therefore, the application information obtained by the second device executing the installation package program also includes the task type.
[0291] When the installation package management service of the second device queries the corresponding application information, the application information can be sent to the application continuation flow service. After receiving the above application information, the application continuation flow service can display the icon of the above application on the user interface of the second device for the user to select. Each icon can be the entrance of the application.
[0292] For example, Fig. 9For example, when the user performs a sharing operation, the second device receives the user's sharing operation and can obtain the following information: Fig.10 The user interface 1000 is shown. Fig.10 , the user interface 1000 includes an application selection area 1010. The application selection area 1010 may include one or more application icons 1011, wherein each application icon 1011 may correspond to an application name 1012. Preferably, in order to distinguish the ownership of each application, for example, whether the application is installed on the first device or the second device, an application source 1013 may be added after the application name 1012, and the application source 1013 may be used to identify the source of the application. Fig.10 As shown, the WeChat application is from a first device (eg, HUAWEI NOVA7), while the Weibo application and the QQ application are from a second device.
[0293] Optionally, the source of the application may be identified in other ways, such as representing the icon of the application from the first device with a first color and representing the icon of the application from the second device with a second color, which is not limited in the present application.
[0294] Optionally, the Weibo application and the QQ application can also add application sources respectively, for example, HUAWEI MatePad Pro X, to identify that the Weibo application and the QQ application are from the second device (for example, HUAWEI MatePad Pro X).
[0295] Optionally, the application selection area 1010 may also only include application icons from other devices. For example, the application selection area 1010 only displays the WeChat application icon 1011, WeChat application name 1012 and application source 1013 from the first device, but does not display the icons of the Weibo application and QQ application installed on this device.
[0296] Optionally, the presentation of the icon of the simulated application of the first device on the user interface of the second device can be achieved through a function switch. For example, a data sharing switch can be set in the second device. Among them, the data sharing switch can be used to control whether the second device can share across applications. Exemplarily, if the data sharing switch is in the on state, after the second device receives the user's data sharing operation, the user interface of the second device can present the simulated application icon of the first device for the user to select, thereby achieving data sharing. If the data sharing switch is in the off state, after the second device receives the user's data sharing operation, the user interface of the second device does not present the simulated application icon of the first device, thereby avoiding the interface from presenting too many application icons.
[0297] Likewise Fig. 9For example, when the user performs a sharing operation, the second device receives the user's sharing operation and can obtain the following information: Fig.11 The user interface 1100 is shown. Fig.11 , the user interface 1100 includes an application selection area 1110, and the application selection area 1110 may include one or more application icons 1111, wherein each application icon 1111 may correspond to an application name 1112. Because the user turns off the data sharing switch, that is, the application selection area 1110 only includes the applications installed in the second device, and does not include the simulated applications.
[0298] Furthermore, when the application information is queried in the second device, intelligent recommendations can also be made according to the task type. For example, some applications can be intelligently selected from the queried applications and presented in the user interface of the second device for the user to select, thereby avoiding the presentation of too many applications, making it impossible for the user to quickly select the required application. Among them, the intelligent recommendation can be determined based on the user's habits. Exemplarily, when the second device makes an application recommendation, it can detect the usage frequency of each application corresponding to the current task type, and can intelligently recommend applications that are greater than or equal to a preset frequency threshold. It can be understood that intelligent recommendations can also be made in other ways, and the embodiments of the present application are not limited to this.
[0299] In some embodiments, the first device does not actively send application information to the second device, so the installation package management service of the second device cannot query the corresponding simulated application information. At this time, the second device can send a query request to the first device to obtain the application information of the first device. That is, after the first device receives the query request sent by the second device, it passively sends the application information. Next, taking the passive sending of application information by the first device as an example, steps 106A to 106C are used to illustrate.
[0300] Step 106A: The second device sends a query request to the first device.
[0301] Specifically, the query request may include a task type.
[0302] Step 106B: The first device receives the query request sent by the second device and obtains application information.
[0303] Specifically, after receiving the query request sent by the second device, the first device can query according to the task type in the query request to obtain the corresponding application. Optionally, the first device can also query all installed applications. This embodiment of the present application does not specifically limit this.
[0304] Step 106C: The first device sends the application information to the second device.
[0305] Specifically, after the first device finds the above application, it can send the above application information to the second device. The above application information can be the information of the application corresponding to the task type in the first device, or it can be the information of all applications installed in the first device, which is not specifically limited in the embodiment of the present application.
[0306] In this embodiment, after receiving the query request from the second device, the first device sends the application information to the second device, which can avoid frequently sending the application information to the second device and avoid wasting resources.
[0307] In some embodiments, after receiving the application information actively sent by the first device, the second device may not construct the simulated application, and may store the application information, for example, storing the application information in the application continuation flow service. Exemplarily, the second device may construct part of the simulated application when the user initiates a task (for example, a sharing task). In other words, the second device may construct the simulated application in an on-demand manner. Next, taking the on-demand construction of the simulated application as an example, step 107 is used for explanation.
[0308] Step 107: The second device constructs a simulation application according to the application program information.
[0309] Specifically, the second device can receive the application information sent by the first device through the application continuation flow service of the application framework layer, and can construct a simulated application based on the application information through the collaborative assistant of the application layer. The application information can be the information of the application sent by the first device based on the request of the second device, for example, the type of the application can be a type corresponding to the task type. The second device can also query in the application continuation flow service to obtain the application information corresponding to the task type, and can construct a simulated application based on the application information obtained from the query.
[0310] It is understandable that this step 107 can be performed after step 105, that is, the second device can be constructed based on the stored simulation application corresponding to the task type; this step 107 can also be performed after step 106C, that is, the second device can be constructed based on the simulation application corresponding to the task type passively sent by the first device. This embodiment of the application does not specifically limit this.
[0311] In this embodiment, after the user initiates a task, the second device constructs a simulation application on demand according to the task type, which can avoid constructing redundant simulation applications and further avoid burdening the system of the second device.
[0312] Step 108: The second device detects a second operation of the user selecting an application, determines a simulated application, and initiates a data sharing request to the first device based on the simulated application.
[0313] Specifically, the user can select an application on the application selection interface displayed on the second device. For example, the user can select an application on the application selection interface displayed on the second device. Fig.10 For example, the user can click the icon 1011 of the simulation application, or double-click the icon of the simulation application, or slide on the icon of the simulation application to select the simulation application, which is not limited in the embodiment of the present application.
[0314] Step 109: The second device initiates a data sharing request to the first device based on the determined simulated application.
[0315] Specifically, in response to the user's operation of selecting a simulated application, the second device determines the simulated application selected by the user through the application selector of the application framework layer, and sends a call request to the activity management service based on the simulated application determined by the user. The call request may include the called application identifier and task data. Among them, the application identifier is used to identify the application, and the task data is used to identify the content shared this time. After receiving the above call request, the activity management service forwards the call request to the collaborative assistant of the application layer to achieve data sharing through collaborative operations. After receiving the above call request, the collaborative assistant can send a data sharing request to the first device through the connection service of the connection layer. The data sharing request can be used to call the application in the first device, thereby realizing the data sharing task, and the data sharing request may include the called application identifier and task data.
[0316] Step 110: The first device receives a data sharing request sent by the second device and starts an application.
[0317] Specifically, after the first device receives the data sharing request sent by the second device through the connection service of the connection layer, it sends the data sharing request to the application continuation flow service of the application framework layer. When the application continuation flow service receives the data sharing request, it obtains the application identifier and task data in the data sharing request, and based on the application identifier, starts the application corresponding to the application identifier (for example, the "WeChat" application). After the first device starts the application, the task data is displayed through the application, and the display screen can also be displayed through the multi-screen collaborative window of the second device, thereby completing data sharing. Exemplarily, if the user calls the video playback application of the first device in the second device, when the first device starts the video playback application, the user can watch the above video in the multi-screen collaborative window of the second device; or, if the user calls the social application of the first device in the second device, when the first device starts the social application, the user can share content in the multi-screen collaborative window of the second device.
[0318] Now combined Fig.12 To explain, Fig.10 For example, when the user selects an application on the first device (for example, the "WeChat" application), the following information can be obtained: Fig.12 User interface 1200. Reference Fig.12 The user interface 1200 includes a multi-screen collaborative window 1210, which is used to display the user interface of the first device (for example, the display interface after the "WeChat" application is started). Fig.12 As shown, the multi-screen collaboration window 1210 includes the launched application 1211 and the task data 1212 that has been shared this time.
[0319] Step 111: The second device simulates the application in the first device based on multi-screen collaboration, so that the task data is shared through the simulated application.
[0320] Specifically, after the first device starts the above application, the screen after the above application is started is displayed on the user interface of the first device. Based on the multi-screen collaboration between the first device and the second device, the user interface of the first device can be displayed in the multi-screen collaboration window of the second device. Further, in the multi-screen collaboration window in the second device, the user can also operate the running simulation application. For example, the user can click, slide, and other operations on the control of the simulation application. Through the virtual device system, the second device can send the above-mentioned events such as clicking or sliding on the control to the first device, wherein the event may include user operation information (for example, touch position) and shared content (for example, web link address or video playback address, etc.). The first device can trigger the corresponding operation event (for example, the operation event can be an operation such as clicking or sliding on the control), thereby executing the user's operation through the application in the first device (for example, sharing the web link in the second device through the social application in the first device), and then controlling the application on the first device through the operation on the second device. In this embodiment, the second device realizes application-based data sharing between devices by simulating the application in the first device, thereby improving the efficiency of data sharing and thus improving the user experience.
[0321] It is understandable that the above embodiment only schematically illustrates the scenario of web page sharing, and the embodiment of the present application is also applicable to the file opening scenario. The scenario shown in the above embodiment does not constitute a limitation to the present application.
[0322] Next, take the file opening scenario as an example and combine it with Figure 13-Figure 15 Provide explanation.
[0323] Fig.13 is a schematic diagram of a user interface 1300 of a second device, such as Fig.13 As shown, the user interface 1300 includes a multi-screen collaboration window 1310 and a desktop 1320 of the second device, and the desktop 1320 includes one or more files 1321 (eg, video files). The user can click on the file 1321 to open the file 1321.
[0324] When the user clicks on any file 1321, the following Fig.14The user interface 1400 shown includes a desktop 1410, and the desktop 1410 includes an application selection area 1420. The application selection area 1420 includes one or more available applications 1421. Exemplarily, the video application is not installed in the second device, so the video selected by the user cannot be opened. Therefore, the application 1421 (for example, "Huawei Video") installed on the first device can be displayed in the application selection area 1420, so that the user can select the application 1421 to complete the viewing of the video. Preferably, the application 1421 can also include description information 1422, which can be used to identify the source of the application. For example, the description information can be "My HUAWEI NOVA7", which is used to identify that the application is installed on the first device named "HUAWEI NOVA7".
[0325] Next, the user can click on application 1421 (for example, the "Huawei Video" application) on interface 1400, thereby sending a request to call the above application 1421 to the first device through multi-screen collaboration, for example, requesting the first device to start the "Huawei Video" application, wherein the request may also include the address of the video file that the user needs to play this time. After the first device receives the request to call the "Huawei Video" application from the second device, it can start the "Huawei Video" application. Then, the first device can find the corresponding video file according to the video file address in the above request, and play the video file requested by the user through the "Huawei Video" application, thereby obtaining the following result. Fig.15 The multi-screen collaboration diagram shown.
[0326] like Fig.15 As shown, the first device displays interface 1510, and the second device displays interface 1520. Interface 1510 includes an opened application 1511 (for example, the "Huawei Video" application), and a video file 1512 (for example, Video 1) selected by the user is played in the application 1511. Interface 1520 includes a multi-screen collaboration window 1521, which can display the same content as in interface 1510. For example, the multi-screen collaboration window 1521 can include an opened application 1522 (for example, the "Huawei Video" application), and a video file 1523 (for example, "Video 1") selected by the user is played in the application 1522, thereby enabling application sharing across devices.
[0327] Fig.16 This is a schematic diagram of the structure of an embodiment of the application sharing device of this application, such as Fig.16 As shown, the application sharing device 1600 may include: a first display module 1610, a first receiving module 1620, a second display module 1630, a second receiving module 1640 and a sharing module 1650; wherein
[0328] A first display module 1610, configured to display a first interface of a first application, where the first interface includes a first option;
[0329] The first receiving module 1620 is used to receive a first operation of a user on a first option;
[0330] The second display module 1630 is used to display a first menu in response to the first operation, where the first menu includes an icon of a second application, where the second application is an application installed on the second electronic device;
[0331] The second receiving module 1640 is used to receive a second operation of the user on the icon of the second application;
[0332] The sharing module 1650 is used to determine the second application in response to the second operation, and send an application sharing request to the second electronic device, where the application sharing request is used to instruct the second electronic device to start the second application.
[0333] In one possible implementation, the apparatus 1600 further includes: a connection module 1660; wherein,
[0334] The connection module 1660 is used to establish a multi-screen collaborative connection with a second electronic device.
[0335] In one possible implementation, the device 1600 further includes: a third display module 1670;
[0336] The third display module 1670 is used to display the second interface, where the second interface includes a window of the second electronic device.
[0337] In one possible implementation, the second interface includes a second option, and the apparatus 1600 further includes: a minimization module 1680; wherein,
[0338] The minimization module 1680 is used to receive a third operation of the user on the second option; in response to the third operation, minimize the window of the second electronic device.
[0339] In one possible implementation manner, the interface of the second application is displayed in a window of the second electronic device.
[0340] In one possible implementation manner, the first electronic device has installed a third application, and the first menu also includes an icon of the third application.
[0341] In one possible implementation manner, the first menu further includes a first identifier, and the first identifier is used to indicate that the second application is an application installed on the second electronic device.
[0342] In one possible implementation, the second application in the first menu is determined by the task type corresponding to the first option.
[0343] In one possible implementation, the apparatus 1600 further includes: a third receiving module 1690; wherein,
[0344] The third receiving module 1690 is configured to receive first application information sent by a second electronic device, where the first application information includes installation package information of a second application.
[0345] In one possible implementation, the apparatus 1600 further includes: a first simulation module 16A0; wherein,
[0346] The first simulation module 16A0 is used to perform simulation based on the first application information sent by the second electronic device to obtain a second application.
[0347] In one possible implementation, the above device further includes: a second simulation module 16B0; wherein,
[0348] The second simulation module 16B0 is used to query the first application information based on the task type corresponding to the first option to obtain the second application information matching the task type; and simulate based on the second application information to obtain the second application.
[0349] In one possible implementation, the apparatus further includes: a query module 16C0; wherein,
[0350] The query module 16C0 is used to send a query request to the second electronic device based on the task type corresponding to the first option, wherein the query request is used to obtain application information of the second application installed on the second electronic device.
[0351] Fig.16 The application sharing device provided in the illustrated embodiment can be used to execute the present application Figure 1-Figure 15 The technical solution of the method embodiment shown, its implementation principle and technical effects can be further referred to the relevant description in the method embodiment.
[0352] It should be understood that the above Fig.16The division of the modules of the application sharing device shown is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware. For example, the detection module can be a separately established processing element, or it can be integrated in a chip of an electronic device. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. In the implementation process, each step of the above method or each of the above modules can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.
[0353] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASIC), or one or more microprocessors (DSP), or one or more field programmable gate arrays (FPGA). For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
[0354] The present application also provides an electronic device, the device comprising a storage medium and a central processing unit, the storage medium may be a non-volatile storage medium, the storage medium stores a computer executable program, the central processing unit is connected to the non-volatile storage medium, and executes the computer executable program to implement the present application Figure 1 to Figure 15 The method provided by the illustrated embodiment.
[0355] In the above embodiments, the processor involved may include, for example, a CPU, a DSP, a microcontroller or a digital signal processor, and may also include a GPU, an embedded neural network processor (Neural-network Process Units; hereinafter referred to as: NPU) and an image signal processor (Image Signal Processing; hereinafter referred to as: ISP). The processor may also include necessary hardware accelerators or logic processing hardware circuits, such as ASIC, or one or more integrated circuits for controlling the execution of the program of the technical solution of the present application. In addition, the processor may have the function of operating one or more software programs, and the software programs may be stored in a storage medium.
[0356] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer-readable storage medium is run on a computer, the computer executes the present application. Figure 1 to Figure 15 The method provided by the illustrated embodiment.
[0357] The present application also provides a computer program product, which includes a computer program, which, when executed on a computer, enables the computer to execute the present application. Figure 1 to Figure 15 The method provided by the illustrated embodiment.
[0358] In the embodiments of the present application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent the existence of A alone, the existence of A and B at the same time, and the existence of B alone. Among them, A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can be represented by: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.
[0359] Those of ordinary skill in the art will appreciate that the various units and algorithm steps described in the embodiments disclosed herein can be implemented in a combination of electronic hardware, computer software, and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0360] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0361] In several embodiments provided in the present application, if any function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory; hereinafter referred to as: ROM), random access memory (Random Access Memory; hereinafter referred to as: RAM), disk or optical disk, and other media that can store program codes.
[0362] The above is only a specific implementation of the present application. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. The protection scope of the present application should be based on the protection scope of the claims.
Claims
1. An application sharing method, characterized in that: Applied to a first electronic device, the first electronic device has installed a first application, the method includes: Displaying a first interface of the first application, where the first interface includes a first option; receiving a first operation of the user on the first option; In response to the first operation, a first menu of the first application is displayed, the first menu including an icon of a second application; the icon of the second application is obtained by simulating the first electronic device based on the installation package information of the second application, and the second application is an application installed on the second electronic device; receiving a second operation of the user on the icon of the second application; In response to the second operation, determining the second application; An application sharing request is sent to the second electronic device, where the application sharing request is used to instruct the second electronic device to start the second application.
2. The method according to claim 1, characterized in that The installation package information includes an application icon and application capabilities of the second application.
3. The method according to claim 1 or 2, characterized in that The method further comprises: A second interface is displayed, where the second interface includes a window of the second electronic device.
4. The method according to claim 3, characterized in that The second interface includes a second option. After displaying the second interface, the method further includes: receiving a third operation of the user on the second option; In response to the third operation, the window of the second electronic device is minimized.
5. The method according to claim 3, characterized in that The interface of the second application is displayed in the window of the second electronic device.
6. The method according to any one of claims 1 to 5, characterized in that: The first electronic device has installed a third application, and the first menu also includes an icon of the third application.
7. The method according to any one of claims 1 to 6, characterized in that: The first menu also includes a first identifier, and the first identifier is used to indicate that the second application is an application installed on the second electronic device.
8. The method according to any one of claims 1 to 7, characterized in that: The second application in the first menu is determined by the task type corresponding to the first option.
9. The method according to any one of claims 1 to 8, characterized in that Before receiving a first operation of the user on the first option, the method further includes: Receive first application information sent by the second electronic device, where the first application information includes installation package information of the second application.
10. The method according to claim 9, characterized in that After receiving the first application information sent by the second electronic device, the method further includes: Searching the first application information based on the task type corresponding to the first option to obtain second application information matching the task type; A simulation is performed based on the second application information, and an icon of the second application is displayed in the first menu.
11. The method according to any one of claims 1 to 8, characterized in that: After responding to the first operation, the method further includes: A query request is sent to the second electronic device based on the task type corresponding to the first option, wherein the query request is used to obtain application information of a second application installed on the second electronic device.
12. The method according to claim 1, characterized in that The first electronic device does not have the second application installed.
13. The method according to claim 1, characterized in that The icon of the second application is used to simulate the entrance of the second application of the second electronic device.
14. An electronic device, characterized in that: include: Display screen; processor; Memory; And a computer program, wherein the computer program is stored in the memory, and the computer program includes instructions, and when the instructions are executed by the electronic device, the electronic device executes the application sharing method as described in any one of claims 1 to 13.
15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed on a computer, enables the computer to execute the application sharing method according to any one of claims 1 to 13.
