WO2023045736A1

WO2023045736A1 - Distributed data management method, electronic device, and system

Info

Publication number: WO2023045736A1
Application number: PCT/CN2022/116851
Authority: WO
Inventors: 帅煜韬
Original assignee: 华为技术有限公司
Priority date: 2021-09-24
Filing date: 2022-09-02
Publication date: 2023-03-30
Also published as: CN115857746A

Abstract

The present application relates to the technical field of terminals, and provides a distributed data management method, an electronic device, and a system. The present application can improve the efficiency of application management in a distributed system. The method comprises: detecting a first instruction input by a user, and sending data of a target application to a second electronic device associated with the first instruction, wherein the second electronic device and a first electronic device are in the same electronic device group, the first instruction is used for instructing to manage the target application of the second electronic device, and managing the target application comprises any one of the following: installing the target application, updating the target application, uninstalling the target application, deploying an icon of the target application, and deleting the icon of the target application.

Description

Distributed data management method, electronic device and system

This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on September 24, 2021, with the application number 202111124130.2, and the title of the invention is "distributed data management method, electronic equipment and system", the entire content of which is incorporated by reference in this application.

technical field

The present application relates to the technical field of terminals, and in particular to a distributed data management method, electronic equipment and a system.

Background technique

Currently, there are more and more types and numbers of electronic devices, and a user may own multiple electronic devices. Users can choose to install various application programs in each electronic device. Wherein, when the user needs to manage the application programs of multiple electronic devices, it usually needs to perform management operations on each electronic device respectively. Take the user installing application 1 on two electronic devices as an example. The user needs to open the application market on electronic device 1, search for application 1, and click Install. The user also needs to open the application market on electronic device 2, search for application 1, and Click Install.

It can be seen that the current application program management method is inefficient.

Contents of the invention

The application provides a distributed data management method, an electronic device and a system, which can improve the management efficiency of application programs in a distributed system.

In order to achieve the above object, the application provides the following technical solutions:

In a first aspect, the present application provides a distributed data management method, which is applied to a first electronic device or a component (such as a chip system) capable of realizing the functions of the first electronic device, and the method includes:

Detect the first instruction input by the user, and send the data of the target application to the second electronic device associated with the first instruction; wherein, the second electronic device and the first electronic device are in the same electronic device group; the first instruction is used to instruct management of the second electronic device 2. The target application of the electronic device; managing the target application includes any of the following: installing the target application, updating the target application, uninstalling the target application, deploying the icon of the target application, and deleting the icon of the target application.

The technical solution of the embodiment of the present application can manage the target application on the second electronic device through the first electronic device, which means that when the user manages the application on any electronic device, he can control other devices in the network as needed The same application on the Internet can be managed to enhance the user experience. Moreover, the user can manage the applications of other devices in the network in a unified manner on the same electronic device, without performing application management operations on each device, which reduces the operational complexity of user management applications, thereby improving the efficiency of application management.

In a possible design, deploying the icon of the target application includes: displaying the icon of the target application on a desktop. The icon is used to manage the target application in response to a third instruction input by the user.

After the icon of the target application is displayed on the desktop, the user can manage the target application of other devices in the network in a unified manner by operating the icon, thereby reducing the operation complexity of the user management application and improving the efficiency of application management.

In a possible design, the method further includes: according to the first instruction and the preset policy, determining the second electronic device associated with the first instruction from the electronic device group;

Wherein, the preset policy includes the type of the target application.

In this way, the first electronic device can automatically and intelligently select the second electronic device that requires application management (such as deploying the icon of the target application) according to a preset policy (such as but not limited to the type of the target application), without manual selection by the user The second electronic device can simplify user operations to a certain extent.

In a possible design, the first instruction is also used to indicate the identity of the second electronic device;

The method further includes: according to the first instruction, determining the second electronic device indicated by the first instruction from the electronic device group.

In a possible design, the first instruction is also used to instruct to manage a local target application.

That is to say, the user can instruct the first electronic device to manage the local target application and instruct the second electronic device to manage the target application of the second electronic device by inputting the first instruction to the first electronic device. Exemplarily, the user inputs a first instruction to the first electronic device, and the first instruction is used to instruct the first electronic device to install the music application, and instruct the second electronic device to install the music application. In another example, the user inputs a first instruction to the first electronic device, and the first instruction is used to instruct the first electronic device to install a music application, to instruct the second electronic device to deploy an icon of the music application, and to instruct the third electronic device to install an icon of the music application. Icon for music app.

In a possible design, the data of the target application includes the state of the target application to be managed in the second electronic device, and the state to be managed includes any of the following states: the target application to be installed, the target application to be updated, the target application to be uninstalled, the state to be managed The icon of the deployment target application and the icon of the target application to be deleted.

In a possible design, the data of the target application further includes any one or more of the following: an identification of the target application, an installation package of the target application, a download link of the target application, and an upgrade package of the target application.

In a possible design, after managing the local target application, the method further includes: sending the management state of the target application to the second electronic device; the management state includes any of the following states: the target application has been installed, the target application has been updated, Uninstalled target app, deployed target app's icon, deleted target app's icon.

In one possible design, the method also includes:

receiving a second instruction input by the user, and starting the preset mode according to the second instruction;

Manage local target applications, including: in the default mode, the electronic device manages target applications of preset types;

Wherein, the preset mode includes any of the following modes: child mode, youth mode, and power saving mode.

In this manner, it can be ensured that in the preset mode, some installations such as unsafe applications are blocked.

In one possible design, the method also includes:

A setting interface is presented, and the setting interface is used to set any one or more of the following: the function of enabling distributed data management, the UI effect of the icon of the target application, and the electronic device associated with the type of the target application.

In a second aspect, a distributed data management method is provided, which is applied to a second electronic device or a component (such as a chip system) capable of realizing a function of the second electronic device, and the method includes:

Receive the data of the target application from the first electronic device; wherein, the second electronic device and the first electronic device are in the same electronic device group; the first instruction is used to instruct to manage the target application of the second electronic device; the management of the target application includes any of the following One: install the target application, update the target application, uninstall the target application, deploy the icon of the target application, delete the icon of the target application;

Manage the target application according to the data of the target application.

In a possible design, deploying the icon of the target application includes: displaying the icon of the target application on the desktop, where the icon is used to manage the target application in response to a third instruction input by a user.

In a possible design, after the target application is managed, the method further includes: sending the management state of the target application to the first electronic device; the management state includes any of the following states: the target application has been installed, the target application has been updated, the target application has been uninstalled app, icon for deployed target app, icon for deleted target app.

In one possible design, the method also includes:

receiving a third instruction from the first electronic device, and turning on the preset mode according to the third instruction;

Managing the target application includes: in the preset mode, the electronic device manages the target application of the preset type;

In a possible design, managing the target application according to the data of the target application includes: managing the target application according to the data of the target application in an off-screen state.

In a third aspect, a distributed data management system is provided, which includes:

The first electronic device is configured to detect a first instruction input by a user, and send target application data to a second electronic device associated with the first instruction;

The second electronic device is configured to receive the data of the target application from the first electronic device, and manage the target application according to the data of the target application;

Wherein, the second electronic device is in the same electronic device group as the first electronic device; the first instruction is used to instruct to manage the target application of the second electronic device; managing the target application includes any of the following: installing the target application, updating the target application, Uninstall the target application, deploy the icon of the target application, delete the icon of the target application.

In a possible design, the first electronic device is further configured to receive a second instruction input by the user, and enable the preset mode according to the second instruction;

In a possible design, the second electronic device, configured to manage the target application according to the data of the target application, includes: managing the target application according to the data of the target application in an off-screen state.

In a fourth aspect, there is provided an electronic device, the electronic device includes a processor and a memory, and the memory is used to store computer program codes, the computer program codes include computer instructions, and when the processor executes the computer instructions, any of the following aspects of the first aspect of the present application can be executed. A method of possible design style.

In a fifth aspect, an electronic device is provided, the electronic device includes a processor and a memory, the memory is used to store computer program codes, the computer program codes include computer instructions, and when the processor executes the computer instructions, any of the following aspects of the second aspect of the present application can be performed. A method of possible design style.

In a sixth aspect, a distributed data management system is provided, including the electronic devices in the fourth and fifth aspects above.

In a seventh aspect, an embodiment of the present application provides a chip system, which is applied to an electronic device including the above-mentioned touch screen. The system-on-a-chip includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected by wires. The interface circuit is for receiving a signal from the memory of the electronic device and sending the signal to the processor, the signal including computer instructions stored in the memory. When the processor executes the computer instructions, the electronic device executes the method in any of the above aspects and any possible implementation manners thereof.

In an eighth aspect, the embodiment of the present application provides a computer storage medium, the computer storage medium includes computer instructions, and when the computer instructions are run on the electronic device, the electronic device is made to execute the method in any possible implementation manner of any aspect.

In a ninth aspect, the embodiments of the present application provide a computer program product, which, when the computer program product is run on a computer, causes the computer to execute the method of any of the above aspects and any possible implementation manner thereof.

Description of drawings

FIG. 1A is an architecture diagram of a distributed system provided by an embodiment of the present application;

FIG. 1B and FIG. 1C are interface diagrams during the distributed networking process provided by the embodiment of the present application;

2A and 2B are schematic structural diagrams of the device provided by the embodiment of the present application;

FIG. 3 is a schematic diagram of the software architecture of the device provided by the embodiment of the present application;

Fig. 4 is a set of interface diagrams provided by the embodiment of the present application;

FIG. 5A is another set of interface diagrams provided by the embodiment of the present application;

FIG. 5B is another set of interface diagrams provided by the embodiment of the present application;

FIG. 5C is another set of interface diagrams provided by the embodiment of the present application;

Figure 6 and Figure 7 are the interface diagrams provided by the embodiment of the present application;

8A-8D are schematic flowcharts of the distributed data management method provided by the embodiment of the present application;

9A-9C are interface diagrams provided by the embodiment of the present application;

FIG. 10 is another schematic flowchart of the distributed data management method provided by the embodiment of the present application;

Figures 11-16 are interface diagrams provided by the embodiment of this application;

FIG. 17 is another schematic flowchart of the distributed data management method provided by the embodiment of the present application;

Figure 18 is an interface diagram provided by the embodiment of this application;

FIG. 19 is a schematic structural diagram of an electronic device provided by the present application;

FIG. 20 is a schematic diagram of a chip system provided by the present application.

Detailed ways

The embodiment of the present application provides a distributed data management method, which is applied in a distributed system (distributed system) including multiple electronic devices. A distributed system can refer to a whole composed of multiple electronic devices. In a distributed system, after at least two electronic devices are connected through a wireless connection or a wired connection, they jointly perform tasks. Devices in a distributed system can be called distributed devices. The distributed system is in a distributed environment, and the distributed environment may be a local area network or a wide area network, which is not limited in this embodiment of the present application. The technical solutions of the embodiments of the present application can manage the data of multiple distributed devices in a distributed system in a unified manner. Distributed device data includes, but is not limited to, application program data.

FIG. 1A is a schematic diagram of an exemplary distributed system provided by an embodiment of the present application. Referring to FIG. 1A, the system includes multiple electronic devices (FIG. 1A takes electronic devices 101-103 as an example). Wherein, an application program can be installed in each electronic device of the plurality of electronic devices.

Multiple electronic devices can establish a communication link. Optionally, connections between devices may be established according to various communication protocols. The communication protocol includes but is not limited to one or more of the following: a wireless fidelity (wireless fidelity, Wi-Fi) protocol, and a Bluetooth protocol for establishing a connection.

After the communication connection is established, data transmission can be performed between the devices. Data includes, but is not limited to, application data. The data of the application program includes but is not limited to: the identification of the application program, the name of the application program, the icon of the application program, the version of the application program, the identification of the associated device of the application program, and the state of the application program in the associated device. The status of the application program includes, but is not limited to, installed, pending installation, updated, pending update, uninstalled, pending uninstallation, icon deployed, icon pending deployment, icon deleted, icon pending deletion.

The installation state may further include the following states: multi-device installation state, local installation (or local installation). Multi-device installation may refer to installing an application on multiple electronic devices within an electronic device group. Local installation may refer to installing the application on the device, and optionally, deploying the icon of the application on other devices in the electronic device group.

The uninstallation status may include: multi-device uninstallation status and local uninstallation status. Multi-device uninstallation may refer to uninstalling the application on multiple electronic devices in the electronic device group. Local uninstallation may refer to uninstalling the application on the device.

Deployment state, which can mean that the app's icon is displayed on the device, but the app is not installed.

Devices associated with the application may include any one or more of the following devices: devices that have installed the application, devices that are to be installed, devices that have updated the application to the target version, and devices that have the application to be updated to the target version , the device on which the application is to be uninstalled, the device on which the application has been deployed, and the device on which the application is to be deployed.

It should be noted that the application can switch between various states. For example, it is possible to transition from a deployed state to an installed state. The transition between states can be referred to the subsequent embodiments in detail.

In the embodiment of the present application, an application that is only installed on the local machine and only deploys an application icon on the local machine is called a local machine application or a local application. An application installed on this machine and deploying application icons on this machine and other devices in the group; or an application installed on multiple electronic devices in the electronic device group is called a shared application.

Optionally, the above-mentioned multiple electronic devices that establish the connection may be multiple electronic devices that have an association relationship. Optionally, it can be multiple electronic devices logged in with the same account. For example, electronic devices that log in to the same Huawei account can establish a connection to form an electronic device group. Optionally, multiple electronic devices for establishing connection are located in the same local area network. In some other embodiments, the multiple electronic devices forming the electronic device group may not be located in the same local area network.

Alternatively, multiple electronic devices forming an electronic device group may not log in with the same account. Exemplarily, the multiple electronic devices forming the electronic device group may be electronic devices of family members, or electronic devices of work partners.

Optionally, in an electronic device group formed by electronic devices of different member types, the data that can be shared between electronic devices in the group is different. Exemplarily, for an electronic device group formed by electronic devices of family members, multiple electronic devices can share data on life, work, and the like. For example, data such as photo albums and memos can be shared between multiple electronic devices. For the electronic device group formed by the electronic devices of the working partners, work-related data can be shared among multiple electronic devices. For example, data such as meeting arrangements can be shared.

Based on the system architecture diagram shown in FIG. 1A above, in a possible implementation, when the electronic device 101, the electronic device 102, and the electronic device 103 communicate, it is necessary to verify or establish a trusted relationship between the electronic devices, so that Provide support for subsequent data synchronization as a prerequisite.

In some embodiments, the electronic device 101 can discover that one or more accounts logged in by other devices are the accounts of the electronic device 101 through the mobile network or the Internet, or that the accounts logged in by the one or more other devices are the accounts logged in by the electronic device 101 If the account is associated, the one or more other devices have a trust relationship with the electronic device 101 . The one or more other devices include the electronic device 102 and the electronic device 103 . Devices logged into the same account or associated accounts can obtain each other's device information and realize data communication. Wherein, the associated account may be an account authorized by the same account.

The above-mentioned account may be an account provided by the cloud server provider for the user, such as a Huawei account, or an account used to log in to an application program, such as an account of various communication software, an account of payment software, and the like.

In some embodiments, a trusted relationship can be established between electronic devices through manual addition, including, for example, touch and scan. Exemplarily, as shown in FIG. 1B , the user may enter the device management interface 310 from the setting application, and the device management interface 310 may include a list named "My Devices". Among them, "My Devices" includes the machine and speakers. The unit and the speaker can be devices with the same account (for example, sharing a Huawei account). Alternatively, the unit and the audio system can be devices with different accounts but authenticated bindings.

Optionally, the device management interface 310 may include a bind other device button 311 . In the embodiment of the present application, binding refers to the establishment of a trusted relationship between two devices, so that operations such as data synchronization between the devices can be performed. In response to the user's operation (for example, click operation) on the button 311 of binding other devices, the device binding interface 320 shown in Figure 1C is entered. The device binding interface 320 includes a list of devices that can be added after scanning. Select the device you want to bind in the addable device list. For example, room TV 321, tablet 322, and smart watch 323 shown in FIG. Binding button 321A or the binding button 322A corresponding to the tablet 322 or the binding button 323A corresponding to the smart watch 323 realizes binding to the room TV 321 or the tablet 322 or smart watch 323 .

Optionally, the device binding interface 320 also includes a tap to add button 324 and a scan to add button 325, which can be bound to electronic devices that have not been scanned by the electronic device. Exemplarily, in response to the user's operation on the touch add button 324, the electronic device turns on NFC, touches the ontag label on other devices with the back, and can realize the binding to other devices; The user operates the button 325, and the electronic device scans the two-dimensional code of other devices, which can realize the binding to other devices.

It should be understood that the positions, names and shapes of the respective elements (such as buttons, icons, text, etc.) in the UI interface corresponding to FIG. 1B and FIG. 1C are not fixed, and can be freely combined or designed according to requirements. . For example, button 311 in FIG. 1B may be replaced with button 324 and button 325 in FIG. 1C.

It should be pointed out that the mutual communication between devices to implement the solution of the embodiment of this application can be established on the basis of the same network; it can also be established on the basis of a trust relationship between devices, such as a common account, Associated account, binding relationship, etc.; it can also be based on the same network and established trust relationship, which is not limited in this application.

Optionally, the electronic device can be a mobile phone, a tablet computer, a desktop, a laptop, a handheld computer, a notebook computer, a netbook, a personal digital assistant (personal digital assistant, PDA), a television, etc. The specific form of the device is not particularly limited. FIG. 1A exemplarily shows the form of the electronic equipment by taking the electronic equipment 101 as a TV, the electronic equipment 102 as a tablet, and the electronic equipment 103 as a mobile phone, but this does not limit the form of the electronic equipment.

Exemplarily, FIG. 2A is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

The electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, Mobile communication module 150, wireless communication module 160, audio module 170, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (subscriber identification module, SIM) card interface 195 etc. .

It can be understood that, the structure shown in the embodiment of the present application does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown in the illustrations, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

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 processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

The controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.

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

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

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (serial data line, SDA) and a serial clock line (derail clock line, SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be respectively coupled to the touch sensor, the charger, the flashlight, the camera 193 and the like through different I2C bus interfaces. For example, the processor 110 can be coupled to the touch sensor through the I2C interface, so that the processor 110 and the touch sensor can communicate through the I2C bus interface to realize the touch function of the electronic device.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . MIPI interface includes camera serial interface (camera serial interface, CSI), display serial interface (display serial interface, DSI), etc. In some embodiments, the processor 110 communicates with the camera 193 through the CSI interface to realize the shooting function of the electronic device. The processor 110 communicates with the display screen 194 through the DSI interface to realize the display function of the electronic device.

The USB interface 130 is an interface conforming to the USB standard specification, specifically, it can be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like. The USB interface 130 can be used to connect a charger to charge the electronic device, and can also be used to transmit data between the electronic device and peripheral devices. It can also be used to connect headphones and play audio through them. This interface can also be used to connect other electronic devices, such as AR devices.

It can be understood that the interface connection relationship between the modules shown in the embodiment of the present application is only a schematic illustration, and does not constitute a structural limitation of the electronic device. In other embodiments of the present application, the electronic device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The wireless communication function of the electronic device can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in an electronic device can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied to electronic devices. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor, and convert them into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be set in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be set in the same device.

A modem processor may include a modulator and a demodulator. Wherein, the modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator sends the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal is passed to the application processor after being processed by the baseband processor. The application processor outputs sound signals through audio equipment, or displays images or videos through the display screen 194 . In some embodiments, the modem processor may be a stand-alone device. In some other embodiments, the modem processor may be independent from the processor 110, and be set in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite system, etc. (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the electronic device 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 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 (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC , FM, and/or IR techniques, etc. The GNSS may include a global positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a Beidou navigation satellite system (beidou navigation satellite system, BDS), a quasi-zenith satellite system (quasi -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).

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

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

Camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects it to the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other image signals. In some embodiments, the electronic device may include 1 or N cameras 193, where N is a positive integer greater than 1.

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. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. Such as saving music, video and other files in the external memory card.

The internal memory 121 may be used to store computer-executable program codes including instructions. The internal memory 121 may include an area for storing programs and an area for storing data. Wherein, the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like. The storage data area can store data (such as audio data, phone book, etc.) created during the use of the electronic device. 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 magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like. The processor 110 executes various functional applications and data processing of the electronic device by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be set in the processor 110 , or some functional modules of the audio module 170 may be set in the processor 110 . Electronic equipment can pass through the audio module 170, such as music playback, recording and so on. The audio module 170 may include a speaker, a receiver, a microphone, an earphone interface, and an application processor to implement audio functions.

The sensor module 180 may include a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

The keys 190 include a power key, a volume key and the like. The key 190 may be a mechanical key. It can also be a touch button. The electronic device can receive key input and generate key signal input related to user settings and function control of the electronic device.

The motor 191 can generate a vibrating reminder. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations applied to different applications (such as taking pictures, playing audio, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects for touch operations acting on different areas of the display screen 194 . Different application scenarios (for example: time reminder, receiving information, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

The indicator 192 can be an indicator light, and can be used to indicate charging status, power change, and can also be used to indicate messages, missed calls, notifications, and the like.

The SIM card interface 195 is used for connecting a SIM card. The SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to realize contact and separation with the electronic device. The electronic device can support 1 or N SIM card interfaces, where N is a positive integer greater than 1.

Exemplarily, FIG. 2B shows another exemplary structure of an electronic device. As shown in FIG. 2B , the electronic device includes: a processor 501 , a memory 502 , and a transceiver 503 . The implementation of the processor 501 and the memory 502 may refer to the implementation of the processor and the memory of the electronic device shown in FIG. 2A . The transceiver 503 is used for the electronic device to interact with other devices. The transceiver 503 may be a device based on communication protocols such as Wi-Fi, Bluetooth or other.

The foregoing FIG. 2A and FIG. 2B are only possible examples of the structure of the electronic device, and do not constitute a limitation on the structure of the electronic device.

Exemplarily, Fig. 3 shows an exemplary software architecture of an electronic device. The system may include four layers, from top to bottom are application program layer (abbreviated as application layer), application program framework layer (referred to as framework layer), system service layer, and kernel layer (also referred to as driver layer).

Wherein, the application layer may include a series of application program packages. In some embodiments of the present application, an application may be atomized. Specifically, an application may consist of one or more capabilities (ability, also called an atomic capability, etc.). Capabilities include but are not limited to feature capability (FA, also called meta-program) and meta-capability (atomic ability, AA, also called meta-service). FA has a UI interface, providing the ability to interact with users; AA has no UI interface, providing the ability to run tasks in the background and a unified data access abstraction. FA and AA may also have other names, which are not limited in this embodiment of the present application.

The application framework layer can provide API and programming framework for the application program of the application program layer. For example, a user interface (UI) framework, an ability framework, and a user program framework are provided.

The system service layer is a collection of core capabilities of the system, providing services to applications through the framework layer. This layer consists of the following parts:

System Basic Capability Subsystem Set: Provides basic capabilities for the operation, scheduling, and migration of distributed applications on multiple devices. It consists of distributed soft bus, distributed data management module, distributed task scheduling, and Ark multilingual runtime (not shown in the figure), public basic library (not shown in the figure), multi-mode input, graphics, security, artificial intelligence (artificial intelligence, AI) and other subsystems.

Among them, the distributed soft bus is a logical channel that can be used for communication between devices.

In some embodiments of the present application, the system service layer shown in FIG. 3 may further include an application management module and a decision-making module.

Wherein, the application management module is used for monitoring the state of the application program. When the state of the application changes (for example, when the user's instructions for installing, updating, and uninstalling the application are detected), operations such as installation, update, and uninstallation of the application are performed, and the state data of the application can be recorded in the distributed data management module .

In some embodiments of the present application, the distributed data management module can be used to receive and record the application state data, and after the state of the application changes, the application state data is synchronized to other electronic devices in the group.

The decision-making module is used to monitor the application state data in the distributed data management module. When it is detected that the state of the application has changed, the first policy for the application is determined, and the application management module is notified to perform a corresponding operation (such as installing the application) according to the first policy.

Optionally, module functions such as the application management module and the decision-making module may also be located at other levels. Optionally, the functions of the application management module and the decision-making module may be integrated into one module, such as a processing module. The embodiment of the present application does not limit the division mode of the modules and the specific functions implemented by each module.

Basic software service subsystem set: provide public and common software services for the system, composed of event notification, telephone, multimedia, DFX, MSDP&DV and other subsystems.

Enhanced software service subsystem set: provide the system with differentiated capability-enhanced software services for different devices, consisting of subsystems such as smart screen proprietary services, wearable proprietary services, and IoT proprietary services.

Hardware service subsystem set: provides hardware services, and is composed of subsystems such as location services, biometric identification, wearable proprietary hardware services, and IoT proprietary hardware services.

According to the deployment environment of different equipment forms, the basic software service subsystem set, the enhanced software service subsystem set, and the hardware service subsystem set can be tailored according to the granularity of the subsystem, and each subsystem can be tailored according to the granularity of the function.

The kernel layer is divided into kernel subsystem and driver subsystem.

Kernel subsystem: adopt multi-core design. The kernel abstract layer (kernel abstract layer, KAL) provides basic kernel capabilities to the upper layer by shielding multi-core differences, including process/thread management, memory management, file system, network management, and peripheral management.

Driver subsystem: Provides a unified peripheral access capability and a driver development and management framework.

The above FIG. 3 is only a possible example of the software architecture of the electronic device, and does not constitute a limitation on the software architecture of the electronic device.

The technical solutions of the embodiments of the present application can be used to manage data in a distributed system. Data management includes, but is not limited to, one or more of the following: installing applications in one or more distributed devices in a distributed system, updating applications in one or more devices in a distributed system, Uninstall apps from multiple devices, etc. First, the technical solution of the embodiment of the present application is described by taking the installation of an application scenario in a distributed system as an example.

In some embodiments, the user can install the application program on the electronic device through an application market or other means. Taking the installation of a music application on a tablet as an example, as shown in (a) of FIG. 4 , the user may click the icon of the application market. When the operation of clicking the application market icon by the user is detected, the tablet displays the application market interface shown in (b) of FIG. 4 , and the user can search and install music applications in the application market interface.

Exemplarily, as shown in (b) of Figure 4, in some examples, the user searches for the Huawei music application through the interface shown in (b) of Figure 4, and clicks the "install button", and the tablet detects that the user clicks the "install button". ” button, the music application needs to be installed locally by default, and the installation package of Huawei Music is downloaded from the server, and Huawei Music is installed locally. After the Huawei music application is installed locally, the tablet can display an interface as shown in (c) of FIG. 4 , and the interface includes an icon 403 of Huawei music. Exemplary, using a tablet

Taking the system as an example, the installation package of the tablet may be, but not limited to, an Android application package (Android application package, APK).

In other embodiments, if it is detected that the user clicks the "Install" button, the tablet can determine the device that needs to install the Huawei Music application according to the user's settings. For example, a device that needs to install the application to be installed is determined according to the type of the application to be installed. Exemplarily, if a user searches for a video application through the application market interface shown in (b) of FIG. It can be a device commonly used to watch videos such as a TV. For another example, if the user searches for a text editing application through the application market interface shown in (b) of FIG. 4 , and clicks the "Install" button, the tablet determines that the device that needs to install the text editing application can be a laptop or other commonly used office equipment. Optionally, when the tablet determines that the target application needs to be installed on other devices, it may instruct the other devices to install the target application.

Alternatively, the tablet may determine the device on which the music application needs to be installed according to the first instruction input by the user. The first instruction is used to indicate the device (that is, the second electronic device) that needs to manage the music application. Exemplarily, as shown in (b) of FIG. 11 , after detecting the operation instruction of the user clicking the "Install" button on the application market interface, the tablet may pop up a window 801, which can be used to select the music application to be installed or to deploy Device with music app icon. As shown in (b) of FIG. 11 , when it is detected that the user checks option 803, the tablet determines that a music application needs to be installed locally on the tablet.

The embodiment of the present application does not limit the specific manner of determining the target application device to be installed. It can be understood that after the tablet determines that the target application needs to be installed on other devices, it can instruct the other devices to install the target application. The specific implementation manner of the tablet instructing other devices to install the target application can be seen in the following embodiments.

Optionally, during the process of installing the music application through the application market or after the installation of the music application, the tablet can synchronize the data of the music application to other devices in the group through the distributed data management module. The data sets the distributed management portal, and the music application is managed through the distributed management portal. For example, for a certain device, it can control operations such as application installation, update, uninstallation, and deployment icons on other devices in the group through the distributed management portal.

As a possible implementation manner, the distributed management entry may be an application icon. Taking the application to be managed as an example of a music application, the tablet may determine an electronic device in the electronic device group that needs to deploy a music application icon. Taking the application management instruction as an example of installing a music application, as a possible implementation, the tablet determines the device on which the icon of the music application needs to be deployed according to the instruction input by the user. Exemplarily, as shown in (b) of FIG. 11 , after detecting the first instruction of the user to check option 802, the tablet may determine that an icon of Huawei Music needs to be deployed on the mobile phone.

It should be noted that the icon serving as the distributed management entry is different from the icon of the local application of the electronic device. The icon of the local application of the electronic device is generally only used to manage related operations of the local application in the electronic device (such as updating or installing or uninstalling the local application in the electronic device, etc.). Exemplarily, the Huawei video application shown in (c) of Figure 4 is a local application of the tablet, that is, the icon is only installed or deployed on the tablet, and the icon is not installed or deployed on other devices. Then, the user can press and hold the The Huawei Video icon triggers the tablet to pop up an uninstall option, and the user can click the uninstall option to trigger the tablet to uninstall the local Huawei Video app. It can be seen that the Huawei Video icon on the tablet can only be used to manage operations such as updating and uninstalling Huawei Video on the tablet. For a device, the icon on the device as a distributed management entry can be used to manage operations such as updating and uninstalling applications on other devices. Optionally, the icon is used to manage the target application in response to a third instruction input by the user. Exemplarily, still referring to (b) of FIG. 5A, the user can control the TV to install music applications by operating the icon 603 on the mobile phone (an icon serving as a distributed management entrance), that is, through a certain device in the distributed system, the The application of multiple devices in the entire distributed system is managed, and the management method is more flexible and convenient.

Alternatively, the tablet determines that the icon of the music application needs to be deployed in other electronic devices in the electronic device group, that is, the icon of the music application needs to be deployed globally. Exemplarily, after the tablet installs an application locally by default, the icon of the application is deployed on all other devices in the group, so that other devices can conveniently manage the application through the icon (management entry) of the application.

Alternatively, the tablet determines that the devices that need to deploy the music application icon (that is, the devices that need to provide management access) are certain devices in the group according to the preset policy. The preset policy includes, but is not limited to: the type of the target application, the usage frequency of similar applications of the target application in each device, the deployment authority of the electronic device, and the deployment authority of the electronic device for the target application. Here are just a few possible implementations of the preset policy, which do not constitute a limitation of the application management policy. The application management policy may be other, and all cases of the application management policy will not be exhaustively listed here.

Exemplarily, if the user searches for a video application through the application market interface shown in (b) of FIG. 4 and clicks the "Install" button, the tablet determines that the video application icon ( The device of the management portal) can be a device commonly used to watch videos such as a TV. Subsequently, the TV and other devices can conveniently manage the video application through the icon of the video application (ie, the management portal). For another example, if the user searches for a text editing application through the application market interface shown in (b) of Figure 4, and clicks the "Install" button, the tablet determines that the device that needs to deploy the text editing application icon can be a laptop or other commonly used office equipment. .

As another example, taking the target application as Huawei Music as an example, the tablet can count various music applications on each device in the group (the same type as the target application, for example, it can be

), deploy the Huawei Music icon on electronic devices with high frequency of music applications.

As another example, an electronic device allows other devices in the group to deploy application icons on itself, that is, it has the deployment permission of the application icon. Then, for the electronic device, other devices in the same group can choose to deploy music to the electronic device The icon of the application, so that the electronic device can conveniently manage music applications on other devices through the icon in the future.

As another example, an electronic device only allows other devices in the group to deploy icons of entertainment applications (such as video and music) on itself, and does not allow other devices to deploy icons such as mail applications and office applications on itself. devices, other devices in the same group can choose to deploy music application icons (management portals) to the electronic device, so that the electronic device can subsequently manage music applications on other devices through the icon.

For another example, the mobile phone may receive a second instruction input by the user, and turn on the preset mode according to the second instruction. Alternatively, the mobile phone may receive a third instruction from other devices in the network, and turn on the preset mode according to the third instruction. In the preset mode, the electronic device manages preset types of target applications. Preset modes include, but are not limited to, children's mode (or similar teenage mode) mode, power saving mode. Exemplarily, a parent may set the child's (or teenager's) device to only accept the deployment of educational application icons. As another example, it may be set that only icons of applications with low power consumption are accepted on devices with low power consumption.

The above only enumerates several possible ways to determine the devices that need to deploy the management portal. The embodiments of the present application do not limit the ways to determine the devices that need to deploy the target application management portal. Due to space limitations, all cases are not listed here.

In this embodiment of the application, after determining the electronic devices that need to deploy music application icons, the tablet can send music application data (referred to as application data) to these electronic devices, and the electronic devices can deploy music application icons according to the music application data. Optionally, the data of the application includes the identification of the application, the name of the application, and the icon of the application. The data of the application may also include but not limited to any one or more of the following data: the version of the application, the state of the application in the tablet (such as installed), the identification of the tablet, the state of the application in the mobile phone (such as pending deploy app icon).

Take the tablet as an example to determine that the icon of the music application needs to be deployed on the mobile phone, as shown in (b) and (d) of Figure 4, after detecting that the user clicks the "Install" button, in some examples, the tablet can, according to the icon such as the music application The type determines that the icon of the music application needs to be deployed on the mobile phone, and sends the deployment data of the music application to the mobile phone. As a possible way of setting the music application management portal, the mobile phone displays the icon 404 of the music application shown in (d) of FIG. For example, the user can trigger the mobile phone to control other devices to install, uninstall or update music applications by operating the icon 404 in the mobile phone.

Optionally, in order to distinguish the application icon used as the management entry from other application icons (such as local application icons), the icon 404 used as the management entry may have different user interface (user interface, UI) effects from the local application icons. Exemplarily, a thumbnail of the tablet is displayed at the lower right corner of the icon 404 to indicate that the application data related to the icon comes from the tablet. As another example, the icon 404 may also have a darker or lighter color than the local application icon, so as to be distinguished from the local application icon. The embodiment of the present application does not limit the specific UI effect of the application icon used as the management entry, as long as it can be distinguished from the local application icon.

Optionally, for the same application, the UI effects corresponding to the application icons in different states may be different. Taking icon 403 and icon 404 as an example, icon 403 indicates that the music application in the tablet is installed, and icon 404 indicates that the music application in the mobile phone is in deployment state, and the music application is not installed yet. Optionally, compared with the icon 403, the icon 404 adds a control 405 on the basis of the icon 403, which is used to indicate that the music application corresponding to the icon 404 is not installed locally. In the embodiment of the present application, other UI effects may also be used to distinguish application icons corresponding to different application states, which are not exhaustively listed here due to space limitations.

Optionally, the mobile phone may display the icon 404 according to the characteristics of the desktop layout and the like. The icon 404 and the icon 403 may have different sizes, aspect ratios, positions and the like. In this way, the icon 404 can have a better display effect, better meet the user's visual needs, and improve the interactive experience between the electronic device and the user.

It can be understood that, in the case that the electronic device has set an entry for managing the application program (such as an icon of the application program), the electronic device can manage the application program through the application program management entry. The process of managing applications by the electronic device through the application management portal (such as the icon of the application) is introduced as follows.

In some embodiments, the mobile phone can display icons of locally installed applications (usually not used as distributed management portals) and icons that can be used as distributed management portals in pages. As shown in (a) of Figure 5A, the mobile phone displays icons of application programs such as a library and a calculator installed on the machine on interface 601, as shown in (b) of Figure 5A, the mobile phone displays on interface 602 that can be used as a distributed management entrance Music 603, Weather and other applications icons.

Optionally, the icons displayed on the interface 602 as distributed management entrances may include icons of installed applications and icons of uninstalled applications. For example, if the music application is not installed, the corresponding music icon in the deployment state is displayed on the desktop. For another example, the browser application has been installed, and a corresponding installed browser icon is displayed on the desktop. Alternatively, among the icons serving as the distributed management entry, icons of installed applications and icons of uninstalled applications may also be displayed in pages.

In some other embodiments, the mobile phone may display an icon serving as a distributed management portal and an icon of a local application in the same interface. For example, in the same interface, not only the installed local applications such as gallery and calculator are displayed, but also applications such as music and weather that can be used as distributed management entrances are displayed.

Optionally, the user may select a management operation of the application program, and the management operation of the application program includes but is not limited to installation, update, and uninstallation. The tablet performs cross-device management of the application based on the management operation input by the user. Taking cross-device installation of applications (distributed installation of applications) as an example, as shown in (b) of FIG. It is used to select the application management operation to be performed. Exemplarily, when it is detected that the user clicks on the installation option, the mobile phone may display a window 605 shown in (c) of FIG. 5A , and the window 605 is used to select a device that needs to install the music application. Optionally, window 605 includes information about electronic devices (such as mobile phones and televisions) that do not have music applications installed. Exemplarily, after detecting an operation instruction (third instruction) for the user to check the options of the mobile phone and the TV, the mobile phone can manage the music application according to the third instruction. As a possible implementation, after the mobile phone detects the third instruction, it determines that the user wants to install the music application on the mobile phone and the TV, then the mobile phone installs the music application locally according to the user's installation intention, and controls the TV to install the music application .

As a possible implementation, the installation of the music application on the mobile phone may be implemented as follows: the mobile phone obtains the installation data of the music application from the devices in the group that have the music application installed, and installs the music application on the local machine according to the installation data. Wherein, the installation data includes but not limited to the installation package of the music application.

As a possible implementation manner, the mobile phone controls the TV to install the music application, which may explicitly instruct the TV to install the music application, or may implicitly instruct the TV to install the music application.

Optionally, the mobile phone implicitly instructs the TV to install the music application, which may be implemented as follows: the mobile phone sends data of the music application to the TV, and the data includes the status of the music application on the TV (to-be-installed status). In this way, after the TV obtains the data of the music application, it can know that the music application needs to be installed according to the application status therein, and then, the TV obtains the installation package of the music application and installs it.

Optionally, the mobile phone explicitly instructs the TV to install the music application, which may be implemented as: the mobile phone sends an instruction to install the music application to the TV, so as to instruct the TV to install the music application. After receiving the instruction, the television may know that the music application needs to be installed, and then, the television obtains the installation package of the music application and installs it.

As a possible implementation manner, the television may obtain the installation package of the music application from a device installed with the music application, from a server, or locally. Exemplarily, taking the previous scenario as an example, after the music application is installed on the tablet or during the process of installing the music application, the data of the music application (without carrying the installation data), such as the status of the music application in the tablet, is sent to the group that needs to deploy the music application icon. Devices, i.e. cell phones, TVs. The mobile phone can learn that the tablet has installed the music application according to the state data of the music application. In this implementation manner, when the TV needs to install the music application locally, it can obtain the installation data of the music application from the tablet. In another example, after the music application is installed on the tablet or during the installation process of the music application, the installation data of the music application is sent to the mobile phone and the TV. In this implementation manner, when the subsequent TV needs to install the music application locally, it can obtain the installation data of the music application locally.

Optionally, the installation package of the music application can be carried in the application data and sent to the mobile phone or the TV, or can be carried in different messages with the application data and sent to the mobile phone or the TV.

According to the technical solution of the embodiment of the present application, the user can directly manage the application programs on multiple electronic devices through the distributed management portal provided by the electronic device (such as the icon of the application program displayed on the desktop), without having to Performing operations separately reduces the complexity of application program management operations, thereby improving the efficiency of application program management.

In addition, compared with users who search and install applications on the TV through the remote control, the input experience of the remote control is poor, and the application management efficiency is low, in the embodiment of the present application, the installation process of the application on the TV can be controlled by the mobile phone ( For example, only the TV option is checked in the control 605 shown in (c) of FIG. 5A ), since the input capability of the mobile phone is usually higher than that of the remote controller, the efficiency of managing the application program through the mobile phone is higher. In addition, the application programs on multiple devices can be managed through the mobile phone, without operating the multiple electronic devices separately, or reducing the probability of separately operating the multiple electronic devices.

Optionally, after the music application is installed locally on the mobile phone, an icon 606 of the music application shown in (d) of FIG. 5A may be displayed on the desktop. Optionally, the

icons

606 and 603 may have different styles, so that the user can distinguish whether the music application is currently deployed or installed. Moreover, the icon 606 may also be different from the icon of the local application, so that the user can clearly distinguish the icons of the local application and the shared application.

Fig. 5A is mainly illustrated by first selecting the operation of the distributed management application, and then selecting the device requiring the distributed management application as an example. In some other embodiments, it is also possible to first select the device requiring the distributed management application, and then select the operation of the distributed management application. For example, referring to (b) of FIG. 5B , in one example, after detecting that the user presses (or performs other defined operations) on the music application icon 603 for a long time, the mobile phone may pop up a window 610 . After detecting that the user checks the mobile phone and TV options and clicks the "OK" button, the mobile phone may pop up a window 604 shown in (c) of FIG. 5B. After detecting that the user taps the "Install" button, the phone installs the music application locally and instructs the TV to install the music application. Exemplarily, after the music application is installed locally on the mobile phone, the icon 606 shown in (d) of FIG. 5B may be displayed on the desktop. Optionally, the UI style or UI effect of the icon 606 is different from that of the icon 603 .

In some other embodiments, the mobile phone can also provide a window through which the user can not only select the device to be managed by the distributed application, but also can be used to select the distributed operation (such as installation, uninstallation, etc.) to be performed. wait).

In some embodiments, in order to facilitate users to search for shared applications by device source, FIG. 5C shows another set of interfaces provided by the embodiment of the present application.

As shown in (a) of FIG. 5C, the mobile phone may display an interface 706, which may include electronic device labels, (eg, label 708, label 709, label 710). When a tab of a certain electronic device is selected, the mobile phone may display icons of applications installed on the device. For example, as shown in (a) in FIG. 5C , in response to detecting the user's operation of clicking the label 708 , the mobile phone may display icons of all shared applications. When there are many shared application icons, the interface 706 may also display a scroll bar 707 . In response to detecting that the user clicks on label 709, the mobile phone may display icons of applications installed on the tablet; in response to detecting that the user clicks on label 710, the mobile phone may display icons of applications installed on the computer.

It can be understood that at this time, the mobile phone may not display the thumbnail image of the electronic device used to identify the source of the application. As shown in (b) of FIG. 5C , the application icon displayed by the mobile phone on the interface 706 may not display the thumbnail image of the tablet computer.

In some embodiments, the user can select an application that needs to be managed in the interface shown in (b) of FIG. 5C , such as long pressing the icon of a music application. After detecting that the user has long pressed the icon of the music application, the mobile phone may pop up a window 604 . After detecting that the user tapped the uninstall option, the phone can instruct the tablet to uninstall the music application.

In some embodiments, as shown in FIG. 6 , after the TV detects an instruction from the mobile phone to install the music application, it may display a prompt box 609 for prompting whether to install the music application. In one example, if it is detected that the user clicks on the "Accept Install" option, the TV installs the music application. If it is detected that the user clicks on the option "refuse to install", the TV will not respond to the instruction of the mobile phone, and will not install the music application. If it is detected that the user clicks the "deploy icon", the TV only deploys the icon of the music application without installing the music application. After the icon of the music application is deployed, the icon can be used as a distributed management entry for the music application.

Figure 5A mainly takes the distributed management of music applications through the music application icon 603 in the deployed state (in this case, no music application has been installed yet) as an example. In other embodiments, the music application icon in the installed state ( Such as icon 606) manages music applications across devices. Exemplarily, as shown in (a) of Figure 7, the mobile phone has installed the music application, and the music application icon 606 of the installed state is displayed on the desktop, if it is detected that the user presses the icon 606 for a long time, the mobile phone pops up a window 607, and the window 607 Displays options to uninstall, update, install on other devices, etc. If it is detected that the user clicks on the "install on other devices" option, the mobile phone may pop up a window 608 shown in (b) of FIG. 7 for selecting a device that needs to install the music application. Optionally, window 608 includes devices without music applications installed, such as the TV shown in (b) of FIG. 7 .

The interaction between the various electronic devices in the distributed management application process is described as follows. Taking the electronic device group including a tablet, a mobile phone, and a TV as an example, as shown in FIG. 8A, the distributed data management method of the embodiment of the present application includes:

S101. The processing module of the mobile phone detects a first instruction to a music application (an example of a target application).

Optionally, the first instruction includes an installation operation, an update operation, or an uninstallation operation of the application.

Exemplarily, as shown in (b) of Figure 5A, the user clicks the install button, and selects the device that needs to install the music application in the interface shown in (c) of Figure 5A, the processing module of the mobile phone can detect that the user clicks on the "Install" button and the first instruction to check the mobile phone and TV in the window 605 . Wherein, the electronic equipment associated with the first instruction is a mobile phone or a television.

Figure 5A is an example of distributed management of applications by operating the icon 603 (distributed management entry) of the uninstalled application. In other embodiments, the user can also operate the icon (distributed management) of the installed application management portal) to perform distributed management on applications. Exemplarily, as shown in (a) of FIG. 7 , the user can long press the icon 606 to trigger a pop-up window 607 on the mobile phone, and the user can click "install on other devices" in the window 607 to trigger the pop-up ( b) Window 608 is shown. If it is detected that the user checks the TV option in window 608 and clicks the installation operation instruction of "OK", the mobile phone can determine that it is necessary to control the TV to install the music application.

S102. The processing module of the mobile phone acquires first data of the music application according to the first instruction, and locally installs the music application according to the first data.

The first data of the music application includes but not limited to: the identification of the music application, and the installation package of the music application. Optionally, when executing different application operations, the first data acquired by the mobile phone may be different. The embodiment corresponding to FIG. 8A is mainly described by taking an application scenario installed in a distributed system as an example. Optionally, the identification of the music application includes but is not limited to any one or more of the following: the name of the music application, the icon of the music application, and the version of the music application.

Exemplarily, as shown in (c) of FIG. 5A, the processing module of the mobile phone determines that the music application needs to be installed on the machine and the TV according to the installation operation instruction input by the user (that is, check the mobile phone and the TV, and click the "OK" button). Afterwards, the mobile phone can be controlled to obtain the first data of the music application from the server, such as any one or more of the following data: the identification of the music application, the installation package of the music application, and the download link of the music application. The mobile phone can locally install the music application according to the first data of the music application. Moreover, the mobile phone can control the TV to install music applications. For the specific implementation manner of controlling the TV to install the music application by the mobile phone, refer to steps S103-S106 in the following embodiments.

Exemplarily, as shown in (d) of FIG. 5A , after the mobile phone locally installs the music application, it may display an icon 606 of the music application on the desktop. Optionally, the icon can be used as an entry point for cross-device music management applications. Optionally, if the icon 606 is used as an entry point of the cross-device management application, the UI effect of the icon 606 is different from that of an ordinary application.

As another example, in the interface shown in (c) of FIG. 5A , the user can only check the TV and click the "OK" button. In this way, the mobile phone can determine that the user's installation intention is to install the music application on the TV. In this case, the mobile phone may not perform step S102, but directly perform the following step S103, so as to control the TV to install the music application through the mobile phone.

S103. The processing module of the mobile phone acquires the second data of the music application, and sends the second data of the music application to the distributed data management module.

The second data of the target application includes a state to be managed of the target application in the second electronic device, and the state to be managed includes any of the following states: the target application is to be installed, the target application is to be updated, The target application to be uninstalled, the icon of the target application to be deployed, and the icon of the target application to be deleted.

Optionally, the data of the target application further includes any one or more of the following: an identifier of the target application, an installation package of the target application, a download link of the target application, an upgrade package of the target application .

S104. The distributed data management module of the TV acquires the second data of the application from the distributed data management module of the mobile phone.

As a possible implementation manner, the distributed data management module of the mobile phone synchronizes the second data with the distributed data management module of the TV.

Optionally, the second data of the application includes, but is not limited to, any one or more of the following data: the identification of the application, the information of the device on which the application is installed, and the state of the application in each device in the group.

Optionally, when the application operations or application events are different, the second data may be the same or different. The situation is introduced as follows. The embodiment corresponding to FIG. 8A is mainly described by taking the application operation as installing an application as an example.

Wherein, the installation operation instruction input by the user may indicate local installation or multi-device installation. Exemplarily, taking the installation operation instruction to install applications on multiple devices as an example, as shown in (c) of Figure 5A, the user checks the mobile phone and TV options and clicks the "OK" button, then the mobile phone can The installation operation instruction determines that the music application needs to be installed in the mobile phone or the TV, and the second data sent by the mobile phone to the TV may include one or more data shown in Table 1.

Table 1 Second data

Wherein, as shown in Table 1, the second data may include information indicating that the music application is installed on the TV (such as information indicating that the status of the music application on the TV is pending installation), and the TV may know that the music application needs to be installed. Optionally, the second data may include an installation package of the music application, and the TV may download and install the installation package, thereby completing the installation of the music application.

As another example, take the installation operation instruction indicating that a music application needs to be installed locally on the mobile phone as an example. For example, in the window 605 shown in (c) of FIG. 5A, the user only checks the TV option and clicks the "OK" button, then, The mobile phone can determine that the music application needs to be installed on the TV according to the installation operation instruction input by the user, and then the mobile phone can send the second data shown in Table 2 to the TV to control the TV to install the music application.

Table 2 Second Data

S105. The processing module of the television acquires the second data from the distributed data management module.

As a possible implementation, when the application data in the distributed data management module is updated, the processing module is actively notified, or the processing module queries the distributed management module whether the application data is updated according to a certain policy, such as periodically.

S106. The television displays a prompt interface.

It should be noted that step S106 is an optional step. It can be understood that after receiving the second data of the music application from the mobile phone, the processing module of the TV may determine according to the second data that the user probably wants to install the music application on the TV. In this case, in order to further determine the user's installation intention, or to prevent the user's previous installation operation (first instruction) from being a wrong operation, the processing module of the TV can control the display module (such as a display screen) to display a prompt interface, prompting the user whether to Installing the music application on the TV, after detecting an instruction input by the user to install the music application on the TV, the TV locally installs the music application according to the installation intention of the user.

Exemplarily, as shown in FIG. 6 , after the television receives the second data of the music application from the mobile phone, a pop-up window 609 is used to prompt the user whether to install the music application on the television. In some examples, if it is detected that the user clicks the "accept installation" button, the television performs the following step S107. In some other examples, if it is detected that the user clicks on the "refuse to install" button, the TV does not install the music application. In some other examples, if it is detected that the user clicks on the "deploy icon", the TV only displays the icon of the music application on the desktop without installing the music application.

S107. The processing module of the television installs the music application according to the second data.

In some embodiments, after receiving the second data from the mobile phone, the processing module of the TV first determines the first strategy according to the second data and the state information of the local music application, and then determines the operation to be performed according to the first strategy.

Taking the management of music applications in a distributed system as an example, if the second data received by the TV from the mobile phone is as shown in Table 1 or Table 2 above, then the TV can application), it is learned that the music application needs to be installed on the TV. In this case, the processing module of the TV judges whether the music application of version 10.1 indicated in Table 1 or Table 2 has been installed locally. If there is no music application installed locally, the processing module of the TV determines that the first strategy is to install the application, and controls the TV to install the music application of version 10.1 according to the first strategy. If the music application is locally installed on the TV, but the installed version is not version 10.1, the processing module of the TV determines that the first strategy is to update the application, and controls the TV to update the version of the music application to version 10.1. If the music application of version 10.1 has been installed locally, the processing module of the TV determines the first strategy, and does not perform the installation operation according to the first strategy.

Optionally, the upgrade package required to upgrade the application version can be obtained from other devices in the group, or obtained from the application market.

In other embodiments, the networked devices share each other's application data. This way, the phone can know that the music app is not installed on the TV before instructing the TV to install the music app. Then, after receiving the second data from the mobile phone, the TV does not need to perform the above-mentioned step of judging the first strategy, but directly installs the music locally according to the state information in the second data (that is, the information indicating that the TV is waiting to install the music application). application.

S108. The processing module of the TV acquires the third data of the music application, and sends the third data of the music application to the distributed data management module.

Optionally, the third data is data related to the music application and changed. In the embodiment of the present application, when the application data of the TV changes, the processing module can update the changed application data to the distributed data management module, and then the distributed data management module will synchronize the updated application data to the devices in the device group. other devices so that other devices are notified of the app's latest data. Exemplarily, when the application changes from the deployed state to the installed state on the TV, the third data may be state information. In this way, the devices in the group can learn that the application in the TV has changed from the deployed state to the installed state. As another example, when an application is upgraded from a lower version to a higher version on the TV, the third data may be version information of the application.

S109. The distributed data management module of the TV sends the third data of the music application to the distributed data management module of the mobile phone.

It can be seen that the TV can notify other devices in the group of the changed application data in the TV, so that other devices can perform follow-up operations according to changes in the status of the application. The third data includes but is not limited to the management state of the music application; the management state includes any of the following states: the target application has been installed, the target application has been updated, the target application has been uninstalled, and the target application has been deployed. icon, the icon for which the target application has been deleted.

FIG. 8A illustrates the distributed data management method provided by the embodiment of the present application by taking installing an application in a distributed device in a distributed system as an example. For updating, uninstalling, and deploying icon scenarios in distributed devices, reference may be made to the embodiment corresponding to FIG. 8A . The interaction between electronic devices in the icon update, uninstall, and deployment scenarios are introduced respectively as follows.

1. Scenarios for updating applications in distributed systems

As shown in Figure 8B, in the application update scenario, the distributed data management process includes:

S201. The processing module of the mobile phone detects an update operation on the music application.

The interface 601 shown in (a) of FIG. 9A shows applications installed locally on the mobile phone, and the interface 701 shown in (b) of FIG. 9A shows shared applications. As shown in (b) of FIG. 9A , after detecting the user's operation of long pressing the music application icon 603 , the mobile phone pops up a window 702 . Window 702 may be used to select an application operation to perform. Application operations may include, but are not limited to, install, update, uninstall, deploy icon, uninstall icon.

In some examples, as shown in (b) of FIG. 9A , the user clicks the update button, triggering the mobile phone to jump to the interface shown in (c) of FIG. 9A , the interface includes window 703 . In the window 703 shown in (c) of FIG. 9A , the user selects the device that needs to update the music application, and the processing module of the mobile phone can detect that the user checks the update operation instruction of the mobile phone and the TV in the window 703 .

It should be noted that in Fig. 9A, the distributed operation (i.e. update application) is selected first, and then the device (i.e. mobile phone, TV) requiring distributed management application is selected. In other embodiments, the distributed operation can also be selected first Devices that manage applications, and then select the distributed management operation (that is, update applications).

Or, in some other embodiments, the mobile phone provides a window, which can be used to select a device and corresponding distributed management operations. Exemplarily, as shown in (b) of FIG. 9B , after detecting that the user has long pressed the music icon 603 , the mobile phone may pop up a window 705 . After detecting that the user checks the installation option under the mobile phone menu, checks the deployment option under the TV menu, and clicks the "OK" button, the mobile phone installs the music application locally and instructs the TV to deploy the icon of the music application.

Optionally, in the implementation manner of FIG. 9B , distributed management operations for different devices may be different. For example, for a mobile phone, the distributed management operation is to install an application, and for a TV, the distributed management operation is to deploy an application icon.

S202. The processing module of the mobile phone acquires an upgrade package of the music application according to the update operation, and locally updates the music application according to the upgrade package.

Optionally, the upgrade package can be obtained from a server, or from a device in the network that has stored the upgrade package.

It can be understood that this step S103 is an optional step. When this step is not performed, it can be understood that the mobile phone does not update the application locally, but remotely controls the TV to update the application. When this step is executed, it can be understood that the mobile phone not only updates the application locally, but also remotely controls the TV to update the application.

S203. The processing module of the mobile phone acquires the first state information of the music application, and sends the first state information of the music application to the distributed data management module.

Wherein, the first state information may be used to characterize the state of the application in the TV. Here, in the application update scenario, the first state information indicates that the application is in a state to be updated on the TV.

Optionally, the processing module of the mobile phone can also obtain other information of the music application, and send the other information of the music application to the distributed data management module. Other information includes, but is not limited to, any one or more of the following: identification of the music application, upgrade package of the music application, status of the music application in the mobile phone (for example, installed), and device identification of the mobile phone.

Exemplarily, Table 3 shows the data sent by the processing module to the distributed data management module. Wherein, these data include the first state information.

Table 3 Data in the distributed data management module

S204. The distributed data management module of the TV synchronizes the first state information to the distributed data management module of the mobile phone.

S205. The processing module of the TV acquires the first state information from the distributed data management module of the TV.

S206. The processing module of the TV controls the TV to display a prompt interface.

Wherein, the prompt interface is used to prompt whether to update the music application.

This step S206 is an optional step.

S207. The processing module of the television updates the music application according to the first state information.

Optionally, in the case of executing S206, after the processing module of the TV controls the TV to display the prompt interface, if an operation instruction from the user to update the music application is detected, step S207 is executed; otherwise, the processing module does not execute the application updating step.

In the case of not executing S206, the processing module may update the music application according to the first state information after acquiring the first state information. Exemplarily, if the first status information is as shown in Table 3 above, it means that the TV needs to update the version of the music application to a specified version. In this case, the processing module of the TV performs an application update operation. Wherein, the upgrade package required for updating the application can be obtained from the server, or obtained from other devices in the network.

S208. The processing module of the TV acquires the second state information of the music application, and sends the second state information of the music application to the distributed data management module.

Wherein, the second status information is used to indicate the latest status of the application on the TV. Here, after the TV updates the application version, the latest state of the application is the updated version.

Optionally, the processing module of the TV can also obtain other information of the music application, and send the other information of the music application to the distributed data management module.

S209. The distributed data management module of the TV synchronizes the second state information of the music application with the distributed data management module of the mobile phone.

In this way, other devices outside the group can learn the latest status of the target application on the TV. Optionally, other devices may perform subsequent distributed data management according to the latest state of the target application.

Optionally, the TV can also synchronize other application information with devices in the network such as mobile phones, so that the devices in the network can share each other's application information and perform distributed data management based on the application information.

2. Scenarios for deploying application icons in a distributed system

As shown in Figure 8C, in the application update scenario, the distributed data management process includes:

S301. The processing module of the tablet detects an operation on the deployment icon of the music application.

Exemplarily, as shown in (b) of FIG. 11 , after detecting that the user clicks the “Install” button, the tablet displays a window 801 . The user can check the option 803 in the window 801, and the processing module of the tablet can detect the user's instruction to deploy the icon of the music application.

S302. The processing module of the tablet acquires the first state information of the music application, and sends the first state information of the music application to the distributed data management module.

Wherein, the first state information may be used to characterize the state of the application in the TV. Here, in the application icon deployment scenario, the first status information indicates that the application is in the status of an icon to be deployed on the TV.

Optionally, the processing module of the mobile phone can also obtain other information of the music application, and send the other information of the music application to the distributed data management module. Other information includes, but is not limited to, any one or more of the following: identification of the music application, status of the music application in the mobile phone (for example, installed), and device identification of the mobile phone.

Exemplarily, Table 4 shows the data sent by the processing module to the distributed data management module. Wherein, these data include the first state information.

Table 4

S303. The distributed data management module of the tablet synchronizes the first state information with the distributed data management module of the mobile phone.

Still taking FIG. 11 as an example, after detecting that the user has checked the option 803 in the window 801, the tablet can synchronize the data of the music application to the mobile phone. The data of the music application includes first state information.

S304. The processing module of the mobile phone acquires the first state information from the distributed data management module.

S305. The processing module of the mobile phone controls the mobile phone to display a prompt interface.

Wherein, the prompt interface is used to prompt whether to deploy an icon of the music application.

This step S305 is an optional step.

S306. The processing module of the mobile phone deploys the icon of the music application according to the first state information.

Exemplarily, if the mobile phone obtains the data shown in Table 4 above from the tablet, it means that the icon of the music application (the icon corresponding to version 10.1) needs to be deployed on the TV. In this case, in some examples, the processing module of the TV determines whether the icon of version 10.1 has been locally deployed, and if the icon corresponding to version 10.1 has been locally deployed on the TV, the processing module of the TV may not send an installation instruction to the processing module. Or, if the TV does not deploy the icon of the music application, the processing module of the TV sends an installation instruction to the processing module, which is used to instruct the processing module to deploy the icon corresponding to version 10.1. Alternatively, if the TV is deployed with an icon of the music application, but the version is not version 10.1, the processing module sends an installation instruction to the processing module to instruct the processing module to deploy the icon corresponding to version 10.1. Or, in some other examples, the processing module does not perform steps such as determining the version, but directly deploys the icon of the music application locally according to the first state information shown in Table 4.

S307. The processing module of the mobile phone acquires the second state information of the music application, and sends the second state information of the music application to the distributed data management module.

Wherein, the second state information is used to indicate the latest state of the application on the mobile phone. Here, after the mobile phone deploys the application icon, the latest state of the application is the deployed application icon.

Optionally, the processing module of the mobile phone can also obtain other information of the music application, and send the other information of the music application to the distributed data management module.

S308. The distributed data management module of the mobile phone synchronizes the second state information of the music application with the distributed data management module of the tablet.

3. Scenarios of uninstalling applications in distributed systems

As shown in Figure 8D, in this scenario, the distributed data management method includes:

S401. The processing module of the mobile phone detects an application uninstallation operation on the music application.

Interface 601 shown in (a) of FIG. 9C shows applications installed locally on the mobile phone, and interface 701 shown in (b) of FIG. 9C shows shared applications. As shown in (b) of FIG. 9C , after detecting the user's operation of long pressing the music application icon 603 , the mobile phone pops up a window 702 . Window 702 may be used to select an application operation to perform.

In some examples, as shown in (b) of FIG. 9C , the user clicks the “Uninstall” button, triggering the mobile phone to jump to the interface shown in (c) of FIG. 9C , which includes a window 704 . In the window 704 shown in (c) of FIG. 9C , the user selects a device (such as a mobile phone and a TV) that needs to uninstall the music application, and the processing module of the mobile phone can detect that the user checks the uninstall operation instruction of the mobile phone and the TV in the window 704 .

It should be noted that in Figure 9C, the distributed management operation (i.e., uninstalling the application) is selected first, and then the device that needs the distributed management application (i.e., the mobile phone and the TV that needs to uninstall the application) is selected. In other embodiments, it can also be First select the device that needs the distributed management application, and then select the distributed management operation (that is, uninstall the application).

Or, in some other embodiments, the mobile phone provides a window, which can be used to select a device and a corresponding distributed management operation (that is, to uninstall an application).

S402. The mobile phone uninstalls the local music application.

This step is optional.

Exemplarily, in the window 704 shown in (c) of FIG. 9C , the user selects that the devices that need to uninstall music applications are mobile phones and TVs, and the mobile phones need to uninstall local music applications. If the user does not check the mobile phone option, the mobile phone does not need to uninstall the local music application.

S403. The processing module of the mobile phone acquires the first state information of the music application, and sends the first state information of the music application to the distributed data management module.

Wherein, the first state information may be used to characterize the state of the application in the TV. With reference to the example shown in FIG. 9C , here the first state information indicates that the application is in a state to be uninstalled on the TV.

Optionally, the processing module of the mobile phone can also obtain other information of the music application, and send the other information of the music application to the distributed data management module. Other information includes, but is not limited to, any one or more of the following: identification of the music application, status of the music application in the mobile phone (for example, installed), and device identification of the mobile phone. Optionally, the identification of the music application includes but is not limited to any one or more of the following: the name of the music application, the icon of the music application, and the version of the music application.

Exemplarily, Table 5 shows the data sent by the processing module to the distributed data management module. Wherein, these data include the first state information.

table 5

S404. The distributed data management module of the tablet synchronizes the first state information with the distributed data management module of the mobile phone.

S405. The processing module of the mobile phone acquires the first state information from the distributed data management module.

S406. The processing module of the mobile phone controls the mobile phone to display a prompt interface.

Wherein, the prompt interface is used to prompt whether to uninstall the music application.

This step S406 is an optional step.

S407. The processing module of the mobile phone uninstalls the music application according to the first state information.

S408. The processing module of the television acquires the second state information of the music application, and sends the second state information of the music application to the distributed data management module.

Wherein, the second status information is used to indicate the latest status of the application on the TV. Here, after the TV has uninstalled the application version, the latest status of the application is uninstalled.

S409. The distributed data management module of the TV synchronizes the second state information of the music application with the distributed data management module of the mobile phone.

Optionally, the functional modules in FIG. 8A-FIG. 8D may also be divided in other manners, and correspondingly, the method flow may be other. Exemplarily, the processing module can be divided into a decision-making module and an application management module. Taking the installation application scenario as an example, FIG. 10 shows a possible method embodiment. Refer to FIG. 10 for method embodiments in other scenarios. As shown in Figure 10, in the installation application scenario, the method includes:

S101a. The application management module of the mobile phone detects a first instruction for the music application.

Optionally, in different scenarios, the first instruction may be different. For example, in the scenario of installing an application, the first instruction may be an operation of installing the application.

S102a. The application management module of the mobile phone acquires first data of the music application according to the first instruction, and installs the music application locally according to the first data.

This step is optional.

S103a. The application management module of the mobile phone obtains the second data of the music application, and sends the second data to the distributed data management module of the mobile phone.

Wherein, the second data includes application state data. In an installation scenario, the application status may be that the application is to be installed.

S104. The distributed data management module of the TV acquires the second data from the distributed data management module of the mobile phone.

Wherein, the second data includes application state data.

S105a. The decision-making module of the TV acquires the second data from the distributed data management module of the TV.

S106a. The decision-making module of the TV controls the TV to display a prompt interface.

Optionally, the prompt interface is used to ask whether to install the music application.

S107a. The decision-making module of the television determines the second instruction according to the second data.

Exemplarily, in the scenario of installing an application, the second instruction may be an instruction to install an application.

Exemplarily, the decision module may determine the distributed application management operation (such as the operation of installing the application) that needs to be performed according to the application state in the second data. Optionally, the decision-making module may determine the second instruction according to other data in the second data, so as to instruct the application management module to perform corresponding distributed application management (such as installing applications) according to the second instruction. Other data in the second data includes, but is not limited to: the identification of the application, the installation package of the application, and the download link of the application.

S107b. The decision-making module sends a second instruction to the application management module.

Optionally, the second instruction carries any one or more of the following information: application identifier, storage path of the installation package, storage path of the application icon, and download link of the installation package. Wherein, the download link of the installation package may be a link for downloading the installation package from the server. The storage path of the installation package may be a local storage path of the installation package, and the storage path of the application icon may be a local storage path of the application icon.

In different scenarios, the first instruction may be different. For example, in the scenario of installing an application, the second instruction is an instruction for instructing the application management module to install the application.

S107c. The application management module installs the music application according to the first instruction.

S108. The application management module of the TV obtains the third data of the music application, and sends the third data to the distributed data management module of the TV.

S109. The distributed data management module of the TV sends the third data to the distributed data management module of the mobile phone.

The above-mentioned Figures 8A-8D mainly illustrate the distributed data management method of the embodiment of the application by taking several scenarios of application installation, update, and uninstallation as examples, and Figure 10 mainly uses several scenarios of application installation, update, and uninstallation as examples to illustrate the implementation It can be understood that the solution of the embodiment of the present application can also be applied to other scenarios (such as including but not limited to deleting application icons and deploying application icons). For the specific implementation of other scenarios, please refer to the above listed Scenes.

Fig. 11 shows another group of possible interface diagrams of the embodiment of the present application. Through this group interface, users can select devices to install or deploy applications. Exemplarily, as shown in (a) and (b) of FIG. 11 , after the tablet detects that the user opens the application market and presses and holds the "install" key, a window 801 pops up. As shown in (b) of FIG. 11 , after detecting that the user checks option 802 and option 803 , the tablet determines that the music application needs to be installed locally and the icon of the music application needs to be deployed on the mobile phone.

In some embodiments, the mobile phone can move the icon of the shared application to a type of folder on the desktop. Such folders may include icons of some or all shared applications. Exemplarily, as shown in (d) of FIG. 12 , the mobile phone may move the deployed music application icon to the shared application folder.

In some other embodiments, in order to reduce the occupation of the desktop display area, the icon of the shared application (which can be used as an icon for application cross-device management) can also be hidden. When the user needs to use the icon of the shared application, he can use the preset gesture Bring up the icon for the shared app. Exemplarily, as shown in (d) of FIG. 13 , initially, the desktop of the mobile phone does not display the icon of the shared application, and in response to the user's long-press operation on the blank space of the desktop, the mobile phone can display a folder 1001, and the folder 1001 includes Icons for apps that can be managed across devices.

It should be noted that, in the embodiment of the present application, when a certain device is used to manage applications on other devices, it is not necessary to operate on the other devices at the same time, and it is even possible to manage the applications on the other devices when the screen of the other device is off. . Exemplarily, as shown in (b) of FIG. 11 , after option 802 is checked, the tablet may instruct the mobile phone to deploy an icon of a music application. At this time, compared with the prior art that requires a series of operations to deploy the application on the mobile phone, such as turning on the screen of the mobile phone, searching and downloading the installation package in the application market, etc., in the technical solution of the embodiment of the present application, there is no need for the user to Pick up the mobile phone to operate, and even the mobile phone can be in the off-screen state. The mobile phone can automatically deploy the icon of the music application according to the instructions of the tablet, which reduces the operation complexity of the user when managing the music application across devices.

In some other embodiments, the technical solutions herein can also be applied to application management in children's mode. Exemplarily, as shown in (a) of FIG. 14 , after detecting that the user has long pressed the icon 1102 of the music application, the mobile phone may pop up a window 1101 . After detecting that the user clicks the "More" button in the window 1101, the mobile phone may pop up the window 1103 shown in (b) of FIG. 14 . Window 1103 is used to set application management options in the child mode. Wherein, the time management option is used to set the maximum usage time of the music application, the period of disabling, and the like. The network settings are used to set the network used by the music application, such as setting to only load music on the Wi-Fi network. Of course, in the child mode, options related to application management may also include other options, and are not limited to time management, network equipment, etc. as shown in (b) of FIG. 14 .

With the method of the embodiment of the present application, parents do not need to set the application management options of the children's mode through the multi-level menu, but directly set the application management options of the children's mode through the icon of the shared application, and the setting method is more convenient and flexible.

It should be noted that the tables listed in the embodiment of the present application are only exemplary formats of the application data in the embodiment of the present application, and the application data may also be in other formats. Moreover, the content of the application data is not limited to the content listed in the table.

In some other embodiments, the embodiment of the present application also provides a method for managing applications across devices. An electronic device can remotely control application-related operations on other electronic devices through a cross-device management portal. Exemplarily, as shown in (a) of FIG. 15 , after detecting that the user has long pressed the icon of the sharing application Huawei Video, the mobile phone may pop up a window 1102, and the window 1102 includes the "remote control" option. After detecting that the user clicks on the "remote control" option, the mobile phone may pop up an interface 1203 shown in (b) of FIG. 15 for selecting a device to be remotely controlled. After detecting that the user has checked the "TV" option, the mobile phone determines that it needs to control the Huawei video on the TV side through the Huawei video on the mobile phone side. Optionally, the mobile phone can send relevant interface information of Huawei Video to the TV, and the TV can draw the UI of Huawei Video according to the interface information. Exemplarily, as shown in (c) of FIG. 15 , after the mobile phone opens Huawei Video, the user searches for movie X in the search bar of Huawei Video, and the mobile phone can display the acquired related movies of Movie X. Like Movie 1, Movie 2, etc. The mobile phone can send the information of interface 1204 to the TV, so that the TV can display according to the information. Users can view movie recommendation information through a large-screen TV. Afterwards, as shown in (c) of FIG. 15 , the user drags the slide bar to refresh the interface. The mobile phone can send the information of the refreshed interface 1205 to the TV, so that the user can view the recommendation information of movies through the TV. It can be seen that through this solution, the user can control related operations of the shared application in the electronic device such as the TV through the shared application of the electronic device such as the mobile phone. On the one hand, compared with the operation of controlling Huawei video on the TV through the remote control (such as dragging the slider and turning pages), electronic devices such as mobile phones have stronger input capabilities, and the input experience is better. The operation of Huawei video has a better input experience and higher input efficiency. On the other hand, compared to operating the application locally on a small-screen device such as a mobile phone and watching the operation interface of the application locally, the viewing experience on a large-screen device such as a TV is better, which can improve the user's interactive experience.

Generally speaking, by controlling the operation of the application level across devices, the technical advantages of different devices can be obtained. For example, through the above-mentioned mobile phone to control the operation of Huawei video on the TV, it can not only obtain the high input efficiency of the mobile phone, but also obtain the high viewing experience of the TV.

In some other embodiments, the distributed data management module can also synchronize the information input by the user through the application to other devices in the network. Exemplarily, as shown in (a) of FIG. 16 , mobile phone A displays an icon 901 of the sharing application "note". After detecting the operation instruction of the user long pressing the icon 901 of the memo, the mobile phone A may pop up a window 902 for creating an item. After detecting that the user clicks on "create item", mobile phone A pops up a window 903 shown in (b) of Figure 16 for selecting a device that needs to create an item. If it is detected that the user checks the options of mobile phone A and mobile phone B, then mobile phone A determines that the user wants to create items locally and on mobile phone B. Then, the mobile phone A can pop up the creation item interface of the memo, and create the item according to the information input by the user, and synchronize the created item to the mobile phone B. Exemplarily, (c) of FIG. 16 shows multiple items created in mobile phone A. Wherein, item 905 is an item that needs to be synchronized to mobile phone B. In this solution, the user of mobile phone A can choose to create items on other devices through this device, so that user B of other devices can conveniently view the items recorded by user A of mobile phone A, so as to remind user B of matters that need attention. Moreover, in this solution, there is no need to create items on mobile phone A and mobile phone B separately, but items can be created on multiple devices that want to create items in the distributed system, which greatly reduces the complexity of implementation.

FIG. 16 uses mobile phone A to create items locally and mobile phone B as an example. In other examples, mobile phone A may not create items locally, but only controls the creation of items on other devices in the network.

In some other embodiments, the distributed data management module can also synchronize other information of the application to other devices in the network. Other information includes but is not limited to login account information.

Exemplarily, the distributed data management module of device A synchronizes the login account information of the application with device 2 in the network, so that after installing the application, device 2 can intelligently log in to the same account according to the login account information, avoiding The user manually enters the account information.

Optionally, the above-mentioned distributed data management module can distinguish data types when synchronizing data between devices, and encrypt and transmit some important data.

Or, optionally, the above-mentioned distributed data management module may determine whether to encrypt and transmit data according to the distance between devices. For example, if the distance between the two devices is less than the threshold, it is considered that the risk of data transmission is low, and the distributed data management module does not encrypt the data for transmission. Conversely, if the distance between the two devices is greater than or equal to the threshold, it is considered that the risk of data transmission is high, and the distributed data management module needs to encrypt the data for transmission.

Or, optionally, the distributed data management module determines whether to encrypt the data for transmission according to the trust relationship between the devices. For example, when a device is networked, identity verification is performed first, and only devices that pass the verification can join the electronic device group. Therefore, devices that join the same electronic device group have a trust relationship with each other by default. When data transmission is carried out within the electronic equipment group, the transmission may be unencrypted by default.

Or, optionally, the distributed data management module determines whether to encrypt and transmit data according to the networking relationship. For data transmission within the same network, it can be transmitted without encryption, and for data transmission across networks, encrypted transmission is performed.

(a) in Figure 5B, (a) in Figure 9B, (c) in Figure 11, (d) in Figure 11, (a) in Figure 12, (b) in Figure 12, (c) in Figure 12 , (a) in FIG. 13, (b) in FIG. 13, (c) in FIG. 13, (d) in FIG. description, this application will not repeat them.

The above-mentioned embodiments are mainly described by taking the user's selection of a device that requires distributed application management as an example. In other embodiments, the device may automatically instruct other devices in the group to install the target application during the process of locally installing the target application. application. Alternatively, during the process of locally uninstalling the target application, the device automatically instructs other devices in the group to uninstall the target application. Alternatively, during the process of locally updating the target application, the device automatically instructs other devices in the group to update the target application. Or, during the process of locally deploying the icon of the target application by the device, the device automatically instructs other devices in the group to deploy the icon of the target application. Alternatively, during the process of locally deleting the icon of the target application, the device automatically instructs other devices in the group to delete the icon of the target application. That is to say, the application management between devices is linked, and the application is managed on a certain device in the network, and the same management operation is performed on other devices in the network. Of course, the distributed management scenarios in this embodiment of the present application are not limited to scenarios such as application installation and uninstallation, but may also be other scenarios. Due to space limitations, all scenarios are not listed here.

Exemplarily, taking the installation application scenario as an example, FIG. 17 shows a manner of linkage management application between devices. After detecting the user's third instruction to install the music application on the mobile phone, the mobile phone can locally install the music application, and automatically instruct other devices in the network, such as a TV, to install the music application. It can be seen that in this method, the management operation of a certain device can be indirectly applied to other devices in the network, and there is no need for the user to select the device that needs to perform distributed management applications, which simplifies the interactive process of distributed data management.

In some embodiments, the terminal may provide an entry for setting a shared application. Exemplarily, as shown in (a) of FIG. 18 , when the user turns on the switch 1201 , it may further allow cross-device application management in multiple devices. After the user allows cross-device management to be enabled, as shown in (b) of Figure 18, the shared application, the UI effect of the shared application, and the electronic device associated with the target application can be set.

Some other embodiments of the present application provide an apparatus, and the apparatus may be the above-mentioned terminal or electronic equipment. The apparatus may include: a display screen, memory and one or more processors. The display screen, memory and processor are coupled. The memory is used to store computer program code comprising computer instructions. When the processor executes the computer instructions, the terminal may execute various functions or steps performed by the terminal in the foregoing method embodiments. The structure of the terminal may refer to the structure of the mobile phone shown in FIG. 2A or the terminal shown in FIG. 2B.

Wherein, the core structure of the terminal can be represented as the structure shown in FIG. 19 , and the terminal includes: a processing module 1301 , an input module 1302 , a storage module 1303 and a display module 1304 .

The processing module 1301 may include at least one of a central processing unit (CPU), an application processor (Application Processor, AP) or a communication processor (Communication Processor, CP). The processing module 1301 may perform operations or data processing related to control and/or communication of at least one of other elements of the user electronic device. Specifically, the processing module 1301 can be configured to control the content displayed on the main screen according to a certain trigger condition. The processing module 1301 is also used to process the input instruction or data, and determine the display style according to the processed data.

The input module 1302 is configured to obtain instructions or data input by the user, and transmit the obtained instructions or data to other modules of the electronic device. Specifically, the input mode of the input module 1302 may include touch, gesture, approaching the screen, etc., and may also be voice input. For example, the input module may be a screen of an electronic device, acquires user input operations, generates input signals according to the acquired input operations, and transmits the input signals to the processing module 1301 .

The storage module 1303 may include a volatile memory and/or a nonvolatile memory. The storage module is used to store at least one related instruction or data in other modules of the user terminal device. Optionally, the storage module can record relevant application data. Application data includes, but is not limited to, application status, application identification, installation packages, download links, and upgrade packages.

The display module 1304 may include, for example, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, an Organic Light Emitting Diode (OLED) display, a Micro Electro Mechanical System (MEMS) display or an electronic paper display. Used to display user-viewable content (eg, text, images, videos, icons, symbols, etc.).

Optionally, a communication module 1305 is also included, configured to support the personal terminal to communicate with other personal terminals (through the communication network). For example, the communication module can be connected to a network via wireless communication or wired communication to communicate with other personal terminals or a network server. The wireless communication may employ at least one of cellular communication protocols, such as Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Universal Mobile Communications System (UMTS), Wireless Broadband (WiBro), or Global System for Mobile Communications (GSM). Wireless communications may include, for example, short-range communications. The short-range communication may include at least one of wireless fidelity (Wi-Fi), Bluetooth, near field communication (NFC), magnetic stripe transmission (MST), or GNSS.

The embodiment of the present application also provides a chip system, as shown in FIG. 20 , the chip system includes at least one processor 1401 and at least one interface circuit 1402 . The processor 1401 and the interface circuit 1402 may be interconnected through wires. For example, interface circuit 1402 may be used to receive signals from other devices, such as memory of an electronic device. As another example, the interface circuit 1402 may be used to send signals to other devices (such as the processor 1401). Exemplarily, the interface circuit 1402 can read instructions stored in the memory, and send the instructions to the processor 1401 . When the instructions are executed by the processor 1401, the electronic device may be made to execute various steps in the foregoing embodiments. Of course, the chip system may also include other discrete devices, which is not specifically limited in this embodiment of the present application.

The embodiment of the present application also provides a computer storage medium, the computer storage medium includes computer instructions, and when the computer instructions are run on the above-mentioned electronic device, the electronic device is made to perform the various functions or steps performed by the mobile phone in the above-mentioned method embodiment .

The embodiment of the present application also provides a computer program product, which, when the computer program product is run on a computer, causes the computer to execute each function or step performed by the mobile phone in the method embodiment above.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be assigned by Completion of different functional modules means that the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be Incorporation or may be integrated into another device, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may be one physical unit or multiple physical units, that is, it may be located in one place, or may be distributed to multiple different places . Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium Among them, several instructions are included to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application. And aforementioned storage medium comprises: U disk, mobile hard disk, read only memory (read only memory, ROM), random access memory (random access memory, RAM), various mediums that can store program codes such as magnetic disc or optical disc.

The above content is only the specific implementation of the application, but the protection scope of the application is not limited thereto, and any changes or replacements within the technical scope disclosed in the application shall be covered within the protection scope of the application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A distributed data management system is characterized in that it includes:

The first electronic device is configured to detect a first instruction input by a user, and send target application data to a second electronic device associated with the first instruction;

a second electronic device, configured to receive data of a target application from the first electronic device, and manage the target application according to the data of the target application;

Wherein, the second electronic device and the first electronic device are in the same electronic device group; the first instruction is used to instruct to manage the target application of the second electronic device; managing the target application includes any of the following Item: install the target application, update the target application, uninstall the target application, deploy the icon of the target application, delete the icon of the target application.
The system according to claim 1, wherein the first electronic device is further configured to receive a second instruction input by a user, and enable a preset mode according to the second instruction;

The first electronic device is configured to manage target applications of a preset type in the preset mode;

Wherein, the preset mode includes any one of the following modes: child mode, youth mode, and power saving mode.
The system according to claim 1 or 2, wherein the second electronic device is configured to manage the target application according to the data of the target application, comprising: in the off-screen state, according to the target application data that manages the target application.
A distributed data management method, characterized in that it is applied to a first electronic device, the method comprising:

Detecting the first command input by the user;

sending the data of the target application to the second electronic device associated with the first instruction;

Wherein, the second electronic device and the first electronic device are in the same electronic device group; the first instruction is used to instruct to manage the target application of the second electronic device; managing the target application includes any of the following Item: install the target application, update the target application, uninstall the target application, deploy the icon of the target application, delete the icon of the target application.
The method according to claim 4, wherein the deploying the icon of the target application comprises: displaying the icon of the target application on the desktop, the icon being used to respond to a third instruction input by the user, Manage the target application.
The method according to claim 4 or 5, characterized in that the method further comprises: according to the first instruction and a preset policy, determining from the electronic device group the second instruction associated with the first instruction 2. electronic equipment;

Wherein, the preset policy includes the type of the target application.
The method according to claim 4 or 5, wherein the first instruction is also used to indicate the identity of the second electronic device;

The method further includes: determining the second electronic device from the group of electronic devices according to the first instruction.
The method according to any one of claims 4-7, wherein the first instruction is also used to instruct management of a local target application.
The method according to any one of claims 4-8, wherein the data of the target application includes a state to be managed of the target application in the second electronic device, and the state to be managed includes the following Any state: the target application is to be installed, the target application is to be updated, the target application is to be uninstalled, the icon of the target application is to be deployed, and the icon of the target application is to be deleted.
The method according to claim 9, wherein the data of the target application further includes any one or more of the following: the identification of the target application, the installation package of the target application, the download of the target application Link, upgrade package of the target application.
The method according to any one of claims 4-10, characterized in that, after managing the local target application, the method further comprises: sending the management status of the target application to the second electronic device The management state includes any of the following states: the target application has been installed, the target application has been updated, the target application has been uninstalled, the icon of the target application has been deployed, and the icon of the target application has been deleted.
The method according to any one of claims 4-11, further comprising:

receiving a second instruction input by the user, and enabling the preset mode according to the second instruction;

Managing a local target application includes: in the preset mode, the first electronic device manages a preset type of target application;

Wherein, the preset mode includes any one of the following modes: children's mode and youth mode.
The method according to any one of claims 4-12, further comprising:

A setting interface is presented, and the setting interface is used to set any one or more of the following: the function of enabling distributed data management, the user interface UI effect of the icon of the target application, and the electronic device associated with the type of the target application .
A distributed data management method, characterized in that it is applied to a second electronic device, the method comprising:

receiving data of a target application from a first electronic device; wherein, the second electronic device is in the same electronic device group as the first electronic device;

Manage the target application according to the data of the target application; the managing the target application includes any of the following: installing the target application, updating the target application, uninstalling the target application, deploying the target application icon, delete the icon of the target application.
The method according to claim 14, wherein the deploying the icon of the target application comprises: displaying the icon of the target application on the desktop, the icon being used to respond to a third instruction input by the user, Manage the target application.
The method according to claim 14 or 15, wherein the data of the target application includes a state to be managed of the target application in the second electronic device, and the state to be managed includes any of the following states: The target application is installed, the target application is to be updated, the target application is to be uninstalled, the icon of the target application is to be deployed, and the icon of the target application is to be deleted;

The data of the target application further includes any one or more of the following: an identifier of the target application, an installation package of the target application, a download link of the target application, and an upgrade package of the target application.
The method according to any one of claims 14-16, characterized in that, after the target application is managed, the method further comprises: sending the management status of the target application to the first electronic device; The management state includes any of the following states: the target application has been installed, the target application has been updated, the target application has been uninstalled, the icon of the target application has been deployed, and the icon of the target application has been deleted.
The method according to any one of claims 14-17, further comprising:

receiving a third instruction from the first electronic device, and enabling a preset mode according to the third instruction;

Managing the target application includes: in the preset mode, the second electronic device manages a preset type of target application;

Wherein, the preset mode includes any one of the following modes: child mode, youth mode, and power saving mode.
An electronic device, characterized in that the electronic device includes a memory and one or more processors; the memory is coupled to the processor; the memory is used to store computer program code, and the computer program code includes a computer Instructions, when said processors execute said computer instructions, cause said one or more said processors to perform the method according to any one of claims 4-18.
A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, wherein when the instructions are run on a terminal, the terminal is made to perform the operation described in any one of claims 4-18 described method.