Application deployment methods, distributed operating systems, electronic devices and storage media

By splitting the application installation package into capability modules, on-demand deployment in a distributed operating system is achieved, solving the problems of limited storage resources and network difficulties of IoT devices, and reducing server load.

CN115454454BActive Publication Date: 2026-11-10HUAWEI TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202110640601.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-06-08
Publication Date
2026-11-10
Estimated Expiration
2041-06-08

AI Technical Summary

Technical Problem

In a distributed operating system, IoT devices have limited storage resources, making it impossible to pre-install a large number of applications or update them in a timely manner. Some devices are unable to connect to the network, leading to difficulties in application deployment and high server load.

Method used

The application installation package is split into multiple capability modules, which interact with other devices through resource-rich IoT devices. Suitable capability modules are deployed as needed to reduce storage usage and solve network connectivity issues.

Benefits of technology

It reduces the storage resource consumption of IoT devices, solves the application deployment problem of devices that cannot connect to the network, and reduces the server load pressure.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115454454B_ABST
    Figure CN115454454B_ABST
Patent Text Reader

Abstract

This application provides an application deployment method, a distributed operating system, an electronic device, and a storage medium, relating to the field of electronic devices. The method is applied to a first device connected to a second device. The first device includes a first application, which includes multiple capability modules that can be installed. Each capability module has the ability to implement one or more functions. The method includes: the first device determining a first target capability module suitable for installation on the second device from among the multiple capability modules included in the first application, based on capability information of the second device; and the first device sending the first target capability module to the second device. This method can significantly reduce the storage resources occupied by the application installation package on the second device and can also solve application deployment problems for some second devices that cannot connect to the network.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of electronic devices, and more particularly to an application deployment method, a distributed operating system, an electronic device, and a storage medium. Background Technology

[0002] A distributed operating system refers to a new generation of full-scenario operating system composed of multiple Internet of Things (IoT) devices connected through a distributed network. In a distributed operating system, different IoT devices can work together efficiently and flexibly. For these IoT devices to work together in a distributed operating system, each IoT device needs to install corresponding applications to support the collaborative functions between them.

[0003] Currently, one way to install applications on IoT devices within a distributed operating system is for manufacturers to pre-install the corresponding applications before the devices leave the factory. However, in this approach, many IoT devices have limited storage resources, making it impossible to pre-install a large number of applications simultaneously. Furthermore, the pre-installed applications on IoT devices cannot be updated in a timely manner.

[0004] Another approach is for IoT devices to connect to the internet and download applications from a server (such as an app store server). However, in this method, some IoT devices that cannot connect to the internet cannot download applications from the server. Moreover, when there are a large number of IoT devices in a distributed operating system, a large number of IoT devices downloading applications from the server will increase the server's load. Summary of the Invention

[0005] This application provides an application deployment method, a distributed operating system, an electronic device, and a storage medium, which can greatly reduce the storage resources occupied by application installation packages on IoT devices and can also solve the application deployment problem of some IoT devices that cannot connect to the network.

[0006] In a first aspect, embodiments of this application provide an application deployment method, the method being applied to a first device. The first device is connected to a second device; the first device includes a first application, the first application including multiple capability modules that can be installed; each capability module has the capability to implement one or more functions. The method includes:

[0007] Based on the capability information of the second device, the first device determines a first target capability module suitable for installation on the second device from among multiple capability modules included in the first application. The first device then sends the first target capability module to the second device.

[0008] Both the first device and the second device are IoT devices.

[0009] The first device can be an IoT device with relatively abundant device resources (such as CPU resources, memory resources, storage resources, etc.) that can independently connect to the network and interact with humans, such as mobile phones, tablets, laptops and other IoT devices.

[0010] The second device can be any of the following IoT devices: mobile phone, tablet, writing tablet, wearable device (such as watch, bracelet, earphone), large screen (such as smart screen), laptop, augmented reality (AR) / virtual reality (VR) device (such as VR glasses), car (or in-vehicle device), camera, robot vacuum cleaner, rice cooker, speaker, treadmill, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc. For example, the second device can be an IoT device with fewer resources than the first device, unable to independently connect to the network and / or interact with humans, such as a writing tablet, earphones, VR glasses, in-vehicle device, rice cooker, speaker, treadmill, etc. Alternatively, the second device can be the same as the first device, with abundant resources, capable of independent network connection and human-computer interaction.

[0011] In this method, the application installation package in the first device is split into one or more capability modules according to different dimensions. The first device interacts with the second device to deploy the corresponding capability modules on the second device, enabling the second device to perform the corresponding functions. On the one hand, this can greatly reduce the storage resources occupied by the application installation package on the second device. On the other hand, it can also solve the application deployment problem for some second devices that cannot connect to the network.

[0012] In one possible design, before the first device determines a first target capability module suitable for installation on the second device from a plurality of capability modules included in the first application based on the capability information of the second device, the method further includes:

[0013] The first device receives a first message from the second device, the first message including the capability information of the second device.

[0014] In this design, the capability information of the second device can be reported to the first device through a first message, so that the first device can determine the first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device.

[0015] For example, the first device and the second device may each include a distributed network module. When the second device accesses the distributed network where the first device is located, the second device learns through its own distributed network module that the first device includes a distributed application installation package. Therefore, the second device can proactively send a first message to the first device. The distributed network module can be a separate chip or a software module integrated into the processor of the IoT device.

[0016] Optionally, the second device may access the distributed network where the first device is located for the first time, and / or, the second device may reconnect to the distributed network after being disconnected from it. For example, the second device may disconnect from the distributed network where the first device is located after a power outage or shutdown. Subsequently, when the second device is powered on again, it may send a first message to the first device.

[0017] In another possible design, before the first device receives the first message from the second device, the method further includes:

[0018] The first device sends a query request message to the second device, which is used to query the capability information of the second device.

[0019] In this design, the first device can actively send a query request message to the second device to trigger the second device to return a first message to the first device based on the query request message.

[0020] In some implementations, the first device sends a query request message to the second device, including:

[0021] When the second device establishes a connection with the first device, the first device sends a query request message to the second device.

[0022] In this implementation, the trigger condition for the first device to send a query request message to the second device is that the second device establishes a connection with the first device. For example, when the second device accesses the local area network where the first device is located, the first device can detect the access of the second device. When the first device detects the access of the second device, it can proactively send a query request message to the second device.

[0023] In other implementations, the first device sends a query request message to the second device, including:

[0024] The first device displays a first interface, which includes device identifiers of one or more second devices; the first device receives a first operation, which is to select a device identifier of a second device on the first interface; in response to the first operation, the first device sends a query request message to the second device.

[0025] In this implementation, the trigger condition for the first device to send a query request message to the second device is that the first device receives a first operation. For example, the first operation is that the user actively selects which or more second devices to send the query request message to on the first interface. The first device can respond to the user's first operation and send the query request message to the second devices actively selected by the user.

[0026] In some embodiments, each capability module included in the first application includes a configuration list corresponding to the capability module; the first device determines a first target capability module suitable for installation on the second device from among the multiple capability modules included in the first application based on the capability information of the second device, including:

[0027] Based on the capability information of the second device and the configuration list corresponding to each capability module included in the first application, the first device determines the first target capability module suitable for installation on the second device from among the multiple capability modules included in the first application.

[0028] For example, the configuration list corresponding to each capability module includes one or more of the following: the device type suitable for the capability module, the minimum device version requirement corresponding to the device type suitable for the capability module, the minimum device level suitable for the capability module, the hardware capability requirements required by the capability module, the CPU-ABI type supported by the capability module, and the scenario type applicable to the capability module.

[0029] For example, the capability information of the second device includes one or more of the following: device type, device version, device level, device hardware capabilities, and CPU-ABI type.

[0030] Device levels can be categorized based on factors such as the abundance of resources available to the IoT device, its ability to independently connect to the network, and / or its human-computer interaction capabilities. For example, IoT devices can be classified into levels 0 to 5, corresponding to L0 to L5, based on their capabilities in random access memory (RAM), read-only memory (ROM), and CPU. Higher-level IoT devices generally have stronger performance. No restrictions are placed on the method used to classify IoT devices.

[0031] In one possible design, before the first device sends the first target capability module to the second device, the method further includes:

[0032] The first device sends attribute information of the first target capability module to the second device; the first device receives a download request message from the second device, the download request message including the identification information of the first target capability module.

[0033] For example, the attribute information of the first target capability module includes one or more of the following: the capability name, version information, capability type, size of the first target capability module, number of times the first target capability module is used on the first device, and permissions required by the first target capability module.

[0034] In this design, the second device can decide whether to install the first target capability module based on its attribute information. When the second device decides to install the first target capability module, it can send a download request message to the first device. This download request message includes the identification information of the first target capability module. After receiving the download request message, the first device can send the first target capability module to the second device.

[0035] In another possible design, the method further includes: a first device displaying a second interface, the second interface including an installation prompt for the first target capability module; the first device receiving a second operation, the second operation being an operation to select the installation of the first target capability module; and the first device responding to the second operation by sending a second message to the second device, the second message being used to instruct the second device to install the first target capability module.

[0036] In this design, the user can choose whether to install the first target capability module on the second device via a second interface provided by the first device. When the first device receives the user's operation to install the first target capability module (i.e., the second operation), it can instruct the second device to install the first target capability module via a second message.

[0037] In some embodiments, the first device is also connected to a third device; the method further includes: the first device determining a second target capability module suitable for installation on the third device from a plurality of capability modules included in the first application based on the capability information of the third device; and the first device sending the second target capability module to the third device.

[0038] Optionally, the first target capability module and the second target capability module may be the same or different.

[0039] That is, in this embodiment, the first device can be connected to multiple different devices such as the second device and the third device. The first device can determine the target capability module suitable for installation on each device from the multiple capability modules included in the first application based on the capability information of the different devices connected to it, and send the target capability module suitable for installation on each device.

[0040] It is understandable that the specific implementation logic for the interaction between the first device and the third device, or even the fourth and fifth devices, can be referred to the interaction logic between the first device and the second device mentioned above, and will not be repeated here.

[0041] Secondly, embodiments of this application provide an application deployment apparatus, which can be applied to a first device to implement the application deployment method described in the first aspect. The functions of this apparatus can be implemented in hardware or by executing corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned functions. For example, the apparatus may include: a sending unit, a receiving unit, a processing unit, etc.

[0042] The sending unit, receiving unit, and processing unit can be used to cooperate in implementing the application deployment method described in the first aspect above. For example, the sending unit can be used to send a first target capability module to the second device. The receiving unit can be used to receive a first message from the second device. The processing unit can be used to determine, based on the capability information of the second device, a first target capability module suitable for installation on the second device from among multiple capability modules included in the first application.

[0043] It should be understood that the device can be used to implement all the functions of the application deployment method described in the first aspect above, and will not be elaborated further.

[0044] Thirdly, embodiments of this application provide an electronic device, including: a processor; a memory; and a computer program; wherein the computer program is stored in the memory, and when the computer program is executed by the processor, it causes the electronic device to implement the method as described in the first aspect and any possible implementation thereof.

[0045] Fourthly, embodiments of this application provide a computer-readable storage medium comprising a computer program that, when executed on an electronic device, causes the electronic device to implement the method described in the first aspect and any possible implementation thereof.

[0046] Fifthly, embodiments of this application also provide a computer program product, including computer-readable code, which, when executed in an electronic device, causes the electronic device to implement the method described in the first aspect and any possible implementation thereof.

[0047] The beneficial effects of the second to fifth aspects mentioned above can be referred to in the first aspect, and will not be repeated here.

[0048] Sixthly, embodiments of this application also provide an application deployment method, the method being applied to a second device connected to a first device; the first device includes a first application, the first application including multiple capability modules that can be installed; each capability module has the capability to implement one or more functions; the method includes:

[0049] The second device receives a first target capability module from the first device; the first target capability module is one of a plurality of capability modules included in the first application; the second device installs the first target capability module.

[0050] After the second device is equipped with the first target capability module, it can perform the corresponding functions through the first target capability module.

[0051] In this method, the application installation package in the first device is split into one or more capability modules according to different dimensions. The first device interacts with the second device to deploy the corresponding capability modules on the second device, enabling the second device to perform the corresponding functions. On the one hand, this can greatly reduce the storage resources occupied by the application installation package on the second device. On the other hand, it can also solve the application deployment problem for some second devices that cannot connect to the network.

[0052] In one possible design, the method further includes: the second device sending a first message to the first device, the first message including capability information of the second device.

[0053] In this design, the capability information of the second device can be reported to the first device through a first message, so that the first device can determine the first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device.

[0054] In another possible design, before the second device sends the first message to the first device, the method further includes:

[0055] The second device receives a query request message from the first device, which is used to query the capability information of the second device.

[0056] In this design, the second device can send a first message to the first device after receiving a query request message from the first device.

[0057] In another possible design, the second device sends a first message to the first device, including:

[0058] When the second device establishes a connection with the first device, the second device sends a first message to the first device.

[0059] For example, the first device and the second device may each include a distributed network module. When the second device accesses the distributed network where the first device is located, the second device learns through its own distributed network module that the first device includes a distributed application installation package. Therefore, the second device can proactively send a first message to the first device. The distributed network module can be a separate chip or a software module integrated into the processor of the IoT device.

[0060] Optionally, the second device may access the distributed network where the first device is located for the first time, and / or, the second device may reconnect to the distributed network after being disconnected from it. For example, the second device may disconnect from the distributed network where the first device is located after a power outage or shutdown. Subsequently, when the second device is powered on again, it may send a first message to the first device.

[0061] Optionally, the capability information of the second device includes one or more of the following: device type, device version, device level, device hardware capabilities, and CPU-ABI type.

[0062] In some embodiments, before the second device receives the first target capability module from the first device, the method further includes:

[0063] The second device sends a download request message to the first device, the download request message including the identification information of the first target capability module.

[0064] In one possible design, the second device sends a download request message to the first device, including:

[0065] The second device receives attribute information of the first target capability module from the first device; the second device decides whether to install the first target capability module based on the attribute information of the first target capability module; when the second device decides to install the first target capability module, the second device sends a download request message to the first device.

[0066] In this design, the second device can decide whether to install the first target capability module based on its attribute information. When the second device decides to install the first target capability module, it can send a download request message to the first device. This download request message includes the identification information of the first target capability module. After receiving the download request message, the first device can send the first target capability module to the second device.

[0067] For example, the attribute information of the first target capability module includes one or more of the following: the capability name, version information, capability type, size of the first target capability module, number of times the first target capability module is used on the first device, and permissions required by the first target capability module.

[0068] Optionally, the second device includes preset decision conditions; the second device decides whether to install the first target capability module based on the attribute information of the first target capability module, including:

[0069] The second device determines, based on the attribute information of the first target capability module, that the first target capability module meets the decision conditions, and then decides to install the first target capability module.

[0070] For example, the decision conditions include one or more of the following: the remaining storage space of the second device is greater than the size of the first target capability module, the remaining battery power of the second device is greater than the first threshold, the second device is currently in a screen-off and charging state, the number of times the first target capability module has been used on the first device is greater than the second threshold, and the permissions required by the first target capability module do not include sensitive permissions.

[0071] In some embodiments, the method further includes: the second device modifying the decision conditions in response to a setting operation on the decision conditions.

[0072] In this embodiment, the user can actively set decision conditions on either the first or second device. The second device can modify the decision conditions in response to the user's setting. Then, the second device can decide whether to install a certain capability module based on the user-set decision conditions.

[0073] Optionally, the second device is equipped with a first target capability module, including:

[0074] The second device displays a third interface, which includes installation prompts for the first target capability module; the second device receives a third operation, which is to select the installation of the first target capability module; the second device responds to the third operation and installs the first target capability module.

[0075] In this design, the user can choose whether to install the first target capability module on the second device via a third interface provided by the second device. When the second device receives the user's selection to install the first target capability module (i.e., the third operation), it can install the first target capability module.

[0076] In the sixth aspect, the beneficial effects of some of the steps corresponding to the first aspect can be referred to in the first aspect, and will not be repeated here.

[0077] In a seventh aspect, embodiments of this application provide an application deployment apparatus, which can be applied to a second device to implement the application deployment method described in the sixth aspect. The functions of this apparatus can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned functions. For example, the apparatus may include: a sending unit, a receiving unit, a processing unit, etc.

[0078] The sending unit, receiving unit, and processing unit can be used to cooperate in implementing the application deployment method described in the sixth aspect above. For example, the sending unit can be used to send a first message to the first device. The receiving unit can be used to receive a first target capability module from the first device. The processing unit can be used to decide whether to install the first target capability module, etc.

[0079] It should be understood that the device can be used to implement all the functions of the application deployment method described in the sixth aspect above, and will not be elaborated further.

[0080] Eighthly, embodiments of this application provide an electronic device, including: a processor; a memory; and a computer program; wherein the computer program is stored in the memory, and when the computer program is executed by the processor, causes the electronic device to implement the method as described in the sixth aspect and any possible implementation thereof.

[0081] Ninthly, embodiments of this application provide a computer-readable storage medium comprising a computer program that, when executed on an electronic device, causes the electronic device to implement the method described in the sixth aspect and any possible implementation thereof.

[0082] In a tenth aspect, embodiments of this application also provide a computer program product, including computer-readable code, which, when executed in an electronic device, causes the electronic device to implement the method described in the sixth aspect and any possible implementation thereof.

[0083] The beneficial effects described in aspects seven through ten above can be found in aspect six, and will not be repeated here.

[0084] Eleventhly, embodiments of this application provide a distributed operating system, including: a first device and a second device, the first device and the second device being connected; the first device includes a first application, the first application including multiple capability modules that can be installed. The first device can determine a first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device, and send the first target capability module to the second device; the second device can receive and install the first target capability module.

[0085] After the second device is equipped with the first target capability module, it can perform the corresponding functions through the first target capability module.

[0086] Both the first device and the second device are IoT devices. The first device can be an IoT device with relatively abundant device resources (such as CPU resources, memory resources, storage resources, etc.) that can independently connect to the network and interact with humans, such as a mobile phone, tablet computer, or laptop computer.

[0087] The second device can be any of the following IoT devices: mobile phone, tablet, writing tablet, wearable device (such as watch, bracelet, earphone), large screen (such as smart screen), laptop, augmented reality (AR) / virtual reality (VR) device (such as VR glasses), car (or in-vehicle device), camera, robot vacuum cleaner, rice cooker, speaker, treadmill, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc. For example, the second device can be an IoT device with fewer resources than the first device, unable to independently connect to the network and / or interact with humans, such as a writing tablet, earphones, VR glasses, in-vehicle device, rice cooker, speaker, treadmill, etc. Alternatively, the second device can be the same as the first device, with abundant resources, capable of independent network connection and human-computer interaction.

[0088] In this distributed operating system, the application installation package on the first device is broken down into one or more capability modules according to different dimensions. The first device interacts with the second device to deploy the corresponding capability modules on the second device, enabling the second device to perform the corresponding functions. On the one hand, this can greatly reduce the storage resources occupied by the application installation package on the second device. On the other hand, it can also solve the application deployment problem for some second devices that cannot connect to the network.

[0089] Optionally, the second device may send a first message to the first device, the first message including the capability information of the second device. After receiving the first message, the first device may determine a first target capability module suitable for installation on the second device from among multiple capability modules included in the first application, based on the capability information of the second device included in the first message.

[0090] In this design, the capability information of the second device can be reported to the first device through a first message, so that the first device can determine the first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device.

[0091] In one possible design, the first device can send a query request message to the second device to query the capabilities of the second device. Upon receiving the query request message from the first device, the second device can send a first message to the first device.

[0092] In this design, the first device can actively send a query request message to the second device to trigger the second device to return a first message to the first device based on the query request message.

[0093] In some implementations, when the second device establishes a connection with the first device, the first device can send a query request message to the second device.

[0094] In this implementation, the trigger condition for the first device to send a query request message to the second device is that the second device establishes a connection with the first device. For example, when the second device accesses the local area network where the first device is located, the first device can detect the access of the second device. When the first device detects the access of the second device, it can proactively send a query request message to the second device.

[0095] In other implementations, the first device may display a first interface, which includes device identifiers of one or more second devices; the first device may receive a first operation, which is to select a device identifier of the second device on the first interface; and the first device may respond to the first operation by sending a query request message to the second device.

[0096] In this implementation, the trigger condition for the first device to send a query request message to the second device is that the first device receives a first operation. For example, the first operation is that the user actively selects which or more second devices to send the query request message to on the first interface. The first device can respond to the user's first operation and send the query request message to the second devices actively selected by the user.

[0097] In another possible design, when the second device establishes a connection with the first device, the second device can send a first message to the first device.

[0098] For example, the first device and the second device may each include a distributed network module. When the second device accesses the distributed network where the first device is located, the second device learns through its own distributed network module that the first device includes a distributed application installation package. Therefore, the second device can proactively send a first message to the first device. The distributed network module can be a separate chip or a software module integrated into the processor of the IoT device.

[0099] Optionally, the second device may access the distributed network where the first device is located for the first time, and / or, the second device may reconnect to the distributed network after being disconnected from it. For example, the second device may disconnect from the distributed network where the first device is located after a power outage or shutdown. Subsequently, when the second device is powered on again, it may send a first message to the first device.

[0100] In some embodiments, each capability module included in the first application includes a configuration list corresponding to the capability module; the first device determines a first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device, including: the first device determines a first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device and the configuration list corresponding to each capability module included in the first application.

[0101] For example, the configuration list corresponding to each capability module includes one or more of the following: the device type suitable for the capability module, the minimum device version requirement corresponding to the device type suitable for the capability module, the minimum device level suitable for the capability module, the hardware capability requirements required by the capability module, the CPU-ABI type supported by the capability module, and the scenario type applicable to the capability module.

[0102] For example, the capability information of the second device includes one or more of the following: device type, device version, device level, device hardware capabilities, and CPU-ABI type.

[0103] Device levels can be categorized based on factors such as the abundance of resources available to the IoT device, its ability to independently connect to the network, and / or its human-computer interaction capabilities. For example, IoT devices can be classified into levels 0 to 5, corresponding to L0 to L5, based on their capabilities in random access memory (RAM), read-only memory (ROM), and CPU. Higher-level IoT devices generally have stronger performance. No restrictions are placed on the method used to classify IoT devices.

[0104] In one possible design, the first device can send attribute information of a first target capability module to the second device; the second device can receive the attribute information of the first target capability module from the first device and decide whether to install the first target capability module based on the attribute information; when the second device decides to install the first target capability module, the second device can send a download request message to the first device. The first device can receive the download request message from the second device, and the download request message includes the identification information of the first target capability module. After receiving the download request message, the first device can send the first target capability module to the second device based on the identification information of the first target capability module.

[0105] For example, the attribute information of the first target capability module includes one or more of the following: the capability name, version information, capability type, size of the first target capability module, number of times the first target capability module is used on the first device, and permissions required by the first target capability module.

[0106] In this design, the second device can decide whether to install the first target capability module based on its attribute information. When the second device decides to install the first target capability module, it can send a download request message to the first device. This download request message includes the identification information of the first target capability module. After receiving the download request message, the first device can send the first target capability module to the second device.

[0107] Optionally, the second device includes preset decision conditions; the second device decides whether to install the first target capability module based on the attribute information of the first target capability module, including: when the second device determines that the first target capability module meets the decision conditions based on the attribute information of the first target capability module, it decides to install the first target capability module.

[0108] For example, the decision conditions include one or more of the following: the remaining storage space of the second device is greater than the size of the first target capability module, the remaining battery power of the second device is greater than the first threshold, the second device is currently in a screen-off and charging state, the number of times the first target capability module has been used on the first device is greater than the second threshold, and the permissions required by the first target capability module do not include sensitive permissions.

[0109] In some embodiments, the second device may modify the decision conditions in response to a setting operation on the decision conditions.

[0110] In this embodiment, the user can actively set decision conditions on either the first or second device. The second device can modify the decision conditions in response to the user's setting. Then, the second device can decide whether to install a certain capability module based on the user-set decision conditions.

[0111] In another possible design, the first device may display a second interface, which includes installation prompts for the first target capability module; the first device may receive a second operation, which is to select to install the first target capability module; and the first device may respond to the second operation by sending a second message to the second device, which instructs the second device to install the first target capability module.

[0112] In this design, the user can choose whether to install the first target capability module on the second device via a second interface provided by the first device. When the first device receives the user's operation to install the first target capability module (i.e., the second operation), it can instruct the second device to install the first target capability module via a second message.

[0113] In another possible design, the second device can display a third interface, which includes installation prompts for the first target capability module; the second device can receive a third operation, which is to select to install the first target capability module; and the second device can install the first target capability module in response to the third operation.

[0114] In this design, the user can choose whether to install the first target capability module on the second device via a third interface provided by the second device. When the second device receives the user's selection to install the first target capability module (i.e., the third operation), it can install the first target capability module.

[0115] In some embodiments, the distributed operating system further includes: a third device, with the first device connected to the third device; the first device can determine a second target capability module suitable for installation on the third device from a plurality of capability modules included in the first application based on the capability information of the third device, and send the second target capability module to the third device; the third device can receive and install the second target capability module.

[0116] Optionally, the first target capability module and the second target capability module may be the same or different.

[0117] That is, in this embodiment, the first device can be connected to multiple different devices such as the second device and the third device. The first device can determine the target capability module suitable for installation on each device from the multiple capability modules included in the first application based on the capability information of the different devices connected to it, and send the target capability module suitable for installation on each device.

[0118] Similarly, in this distributed operating system, the first device can be used to implement all the functions in the application deployment method described in the first aspect above, and the second device can be used to implement all the functions in the application deployment method described in the sixth aspect above, which will not be elaborated here.

[0119] The beneficial effects of the eleventh aspect mentioned above can be referred to in the first and sixth aspects, and will not be repeated here.

[0120] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single embodiment. Rather, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution, or beneficial effect is included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions, and beneficial effects described in this embodiment can be combined in any suitable manner. Those skilled in the art will understand that embodiments can be implemented without one or more specific technical features, technical solutions, or beneficial effects of a particular embodiment. In other embodiments, additional technical features and beneficial effects may be identified in specific embodiments that do not embody all embodiments. Attached Figure Description

[0121] Figure 1 This is a schematic diagram illustrating one implementation scenario of the distributed operating system provided in an embodiment of this application;

[0122] Figure 2 A flowchart illustrating the application deployment method provided in this application embodiment;

[0123] Figure 3 A schematic diagram of the settings interface of the mobile phone 110 provided in an embodiment of this application;

[0124] Figure 4 A schematic diagram of the application collaboration interface of the mobile phone 110 provided in this application embodiment;

[0125] Figure 5 A schematic diagram illustrating the composition of the first social software application installation package provided in this application embodiment;

[0126] Figure 6 A schematic diagram illustrating the process by which the watch 120 decides whether to install the text chat capability deployment package, as provided in an embodiment of this application;

[0127] Figure 7 This application provides an architectural diagram of the first IoT device and the second IoT device as an embodiment of the present application.

[0128] Figure 8 This is a schematic diagram of the hardware composition of an IoT device provided in an embodiment of this application;

[0129] Figure 9 This is a schematic diagram of the structure of the application deployment device provided in the embodiments of this application;

[0130] Figure 10 Another structural schematic diagram of the application deployment device provided in the embodiments of this application. Detailed Implementation

[0131] The terminology used in the following embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, “at least one” and “one or more” refer to one or more (including two). The character “ / ” generally indicates that the preceding and following objects are in an “or” relationship.

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

[0133] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0134] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0135] A distributed operating system refers to a new generation of full-scenario operating system composed of multiple Internet of Things (IoT) devices connected through a distributed network. In a distributed operating system, different IoT devices can work together efficiently and flexibly.

[0136] IoT devices can include: mobile phones, tablets, writing tablets, wearable devices (such as watches, wristbands, and headphones), large screens (such as smart screens), laptops, augmented reality (AR) / virtual reality (VR) devices (such as VR glasses), cars (or in-vehicle devices), cameras, robot vacuums, rice cookers, speakers, treadmills, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs), etc.

[0137] For example, in one possible scenario, a user's home could include IoT devices such as mobile phones, refrigerators, smart screens, speakers, and watches. These devices can form a distributed operating system via a local area network (such as Wi-Fi), which can be called a distributed network. Based on this distributed network, these IoT devices can collaborate. For instance, a refrigerator can work with a mobile phone to provide shopping functionality, a smart screen can work with a mobile phone to provide video playback and call functionality, a speaker can work with a mobile phone to provide music playback functionality, and a watch can work with a mobile phone to provide sports and health monitoring functionality, etc.

[0138] For IoT devices in a distributed operating system to work collaboratively, each IoT device needs to install corresponding applications to support inter-device collaboration. For example, in the distributed operating system composed of the aforementioned mobile phone, refrigerator, smart screen, speaker, and watch, the refrigerator needs to install a shopping app, the smart screen needs to install video and calling apps, the speaker needs to install a music app, and the watch needs to install a fitness and health app, etc.

[0139] Currently, one way to install applications on IoT devices within a distributed operating system is for manufacturers to pre-install the corresponding applications before the devices leave the factory. However, in this approach, many IoT devices have limited storage resources, making it impossible to pre-install a large number of applications simultaneously. Furthermore, the pre-installed applications on IoT devices cannot be updated in a timely manner.

[0140] Another approach is for IoT devices to connect to the internet and download applications from a server (such as an app store server). However, in this method, some IoT devices that cannot connect to the internet cannot download applications from the server. Moreover, when there are a large number of IoT devices in a distributed operating system, a large number of IoT devices downloading applications from the server will increase the server's load.

[0141] Therefore, this application provides an application deployment method that can be applied to a distributed operating system. The distributed operating system includes a first IoT device and at least one second IoT device.

[0142] The first IoT device can be an IoT device with relatively abundant device resources (such as CPU resources, memory resources, storage resources, etc.) that can independently connect to the network and interact with humans. For example, the first IoT device can be an IoT device such as a mobile phone, tablet computer, or laptop computer.

[0143] The second IoT device can be any of the above-mentioned IoT devices. For example, the second IoT device can be an IoT device with fewer resources than the first IoT device, unable to independently connect to the network and / or interact with humans, such as a writing tablet, headphones, VR glasses, in-vehicle devices, rice cookers, speakers, treadmills, etc. Alternatively, the second IoT device can also be the same as the first IoT device, with more abundant resources, capable of independent network connectivity and human-computer interaction.

[0144] This application does not impose any restrictions on the specific types of the second IoT device and the first IoT device.

[0145] In this embodiment of the application, the first IoT device may also be referred to as the first device, and the second IoT device may also be referred to as the second device.

[0146] In some embodiments, IoT devices with abundant resources that can independently connect to the network and interact with humans can be referred to as rich devices. IoT devices with fewer resources that cannot independently connect to the network and / or interact with humans can be referred to as light devices. In the embodiments of this application, the first IoT device can be a rich device, and the second IoT device can be either a rich device or a light device.

[0147] Optionally, the operating system of the first IoT device and / or the second IoT device may be HarmonyOS. TM (harmony) system, Android TM (Android) system, iOS TM System, Windows TM System, Mac TM System, Linux TM System, EMUI TM Android Wear TM System, Lite OS TM Tizen TM System, watchOS TM Systems, etc. Alternatively, some IoT devices may not have an operating system; this is not a restriction.

[0148] For example, Figure 1 This is a schematic diagram illustrating one implementation scenario of the distributed operating system provided in an embodiment of this application. For example... Figure 1 As shown, in one possible implementation scenario, the distributed operating system may include: mobile phone 110, watch 120, smart screen 130, speaker 140, and refrigerator 150. Mobile phone 110 is connected to watch 120, smart screen 130, speaker 140, and refrigerator 150 via a router 160 to establish a local area network.

[0149] Figure 1 In the scenario shown, mobile phone 110 can be used as the first IoT device, and watch 120, smart screen 130, speaker 140 and refrigerator 150 can be used as the second IoT devices respectively.

[0150] In this embodiment, the first IoT device may include a distributed application installation package. This distributed application installation package may include one or more meta-capability deployment packages, and attribute information for each meta-capability deployment package. Each meta-capability deployment package can implement a corresponding function. As one possible implementation, for example, it can be designed to implement an independent function for each meta-capability deployment package. Each meta-capability deployment package may include a configuration manifest corresponding to that meta-capability deployment package, as well as dynamic libraries, resource files, and meta-capability business code used to implement the function of that meta-capability deployment package. As one possible implementation, each meta-capability deployment package may include one or more code-level installation sub-packages.

[0151] For example, a distributed application installation package could be the installation package for a social media application. This social media application's installation package could include meta-capability deployment packages such as text chat capability deployment packages, video call capability deployment packages, audio call capability deployment packages, and shopping capability deployment packages. Specifically, the text chat capability deployment package enables text chat functionality, the video call capability deployment package enables video call functionality, the audio call capability deployment package enables audio call functionality, and the shopping capability deployment package enables shopping functionality.

[0152] Figure 2 This is a flowchart illustrating the application deployment method provided in an embodiment of this application. Figure 2 As shown, the method may include S201-S205.

[0153] S201. The second IoT device sends a first message to the first IoT device, the first message including the capability information of the second IoT device.

[0154] In some embodiments, when the second IoT device accesses the distributed network (such as the local area network mentioned above) where the first IoT device is located, it can proactively send a first message to the first IoT device.

[0155] For example, each IoT device in a distributed operating system may include a distributed network module. IoT devices connected to the distributed network can synchronize data and information based on their respective distributed network modules. When a second IoT device connects to the distributed network where the first IoT device resides, the second IoT device learns through its own distributed network module that the first IoT device includes a distributed application installation package. Therefore, the second IoT device can proactively send a first message to the first IoT device. The distributed network module can be a separate chip or a software module integrated into the processor of the IoT device.

[0156] Optionally, the second IoT device may access the distributed network where the first IoT device is located for the first time, and / or, the second IoT device may disconnect from the distributed network and then reconnect. For example, the second IoT device may disconnect from the distributed network where the first IoT device is located after a power outage or shutdown. Subsequently, when the second IoT device is powered on again, it may send a first message to the first IoT device.

[0157] In other embodiments, when the second IoT device accesses the distributed network where the first IoT device is located, the first IoT device can send a query request message to the second IoT device, and after receiving the query request message, the second IoT device can return a first message to the first IoT device.

[0158] In some embodiments, the first IoT device may provide a display interface, which may include device identifiers (such as device names) of one or more second IoT devices connected to the first IoT device via a distributed network. Users can select which second IoT devices the first IoT device will collaborate with for application deployment on the display interface corresponding to the distributed application installation package. In response to the user's selection, the first IoT device may send a query request message to the selected second IoT device. Upon receiving the query request message, the selected second IoT device may return a first message to the first IoT device. The display interface including the device identifiers of one or more second IoT devices connected to the first IoT device via a distributed network can be referred to as the first interface, and the user's operation of selecting which second IoT devices the first IoT device will collaborate with for application deployment on this display interface can be referred to as the first operation.

[0159] For example, with the above Figure 1Taking the distributed operating system implementation scenario shown as an example, the first IoT device is a mobile phone 110, and the second IoT devices are a watch 120, a smart screen 130, a speaker 140, and a refrigerator 150. Figure 3 This is a schematic diagram of the settings interface of the mobile phone 110 provided in an embodiment of this application. Figure 4 This is a schematic diagram of the application collaboration interface of the mobile phone 110 provided in an embodiment of this application. Figure 3 As shown, the settings interface of phone 110 may include an application collaboration button 301 (or a device collaboration button), and other settings options (such as settings options 1 to 6). When the user clicks the application collaboration button 301, the phone can respond to the user's click on the application collaboration button 301 and display as shown in the image. Figure 4 The application collaboration interface shown is as follows. Figure 4 As shown, the application collaboration interface may include: the name of watch 120 as "Watch", the name of smart screen 130 as "Smart Screen", the name of speaker 140 as "Speaker", and the name of refrigerator 150 as "Refrigerator". Each device name also includes an on / off button. Users can click the on / off button after each device name to trigger mobile phone 110 to enable or disable the application collaboration function with that device. When a user clicks the on / off button after a device name, triggering mobile phone 110 to enable the application collaboration function with that device, the state of the on / off button after that device name will switch from off to on. The device whose on / off button is switched to on is the second IoT device selected by the user. Mobile phone 110 can respond to the user's operation of switching the state of the on / off button after the device name from off to on by sending a query request message to the corresponding device. For example: Figure 4 In this scenario, the user selects two IoT devices: a smartwatch 120 and a smart screen 130. The mobile phone 110 can send query request messages to both the smartwatch 120 and the smart screen 130. After receiving these query request messages, the smartwatch 120 and the smart screen 130 can return a first message to the mobile phone 110. Understandably, the first message returned by the smartwatch 120 includes its capability information, and the first message returned by the smart screen 130 includes its capability information.

[0160] It should be understood that the above Figure 3 and Figure 4The implementation shown is merely illustrative. This application embodiment provides a display interface for the first IoT device, allowing the user to select which second IoT devices the first IoT device will collaborate with for application deployment; the specific method is not limited. For example, the display interface provided by the first IoT device may also include device identifiers (such as device name, device model, etc.) of one or more second IoT devices connected to the first IoT device via a distributed network. The user can directly click on one or more device identifiers on this display interface, and the first IoT device can respond to the user's click by sending a query request message to the second IoT device corresponding to the clicked device identifier.

[0161] It should be noted that, in this embodiment, the triggering conditions for the second IoT device to send a first message to the first IoT device are not limited to those described in the foregoing embodiments, and this application does not impose any restrictions on the triggering conditions for the second IoT device to send a first message to the first IoT device. For example, the second IoT device and the first IoT device can also trigger the above-mentioned S201 by "tap-to-pay". For example, the second IoT device and the first IoT device may each include a near field communication (NFC) chip. When the second IoT device is close to the first IoT device, an NFC connection can be established between the second IoT device and the first IoT device, triggering the process described in S201. As another example, the second IoT device can actively send a first message to the first IoT device upon first login or after reconnection. The role of the first IoT device can be determined by various IoT devices in the local area network according to election rules.

[0162] The second IoT device sends a first message to the first IoT device, which can be used to query the first IoT device for a suitable metadata deployment package to install on the second IoT device. After receiving the first message, the first IoT device can execute steps S202 and S203.

[0163] S202. The first IoT device determines the target meta-capability deployment package suitable for installation on the second IoT device based on the capability information of the second IoT device and the configuration list corresponding to each meta-capability deployment package in the distributed application installation package.

[0164] For example, a distributed installation package can be the first application.

[0165] S203. The first IoT device sends the attribute information of the target meta-capability deployment package to the second IoT device.

[0166] Accordingly, the second IoT device receives attribute information from the target meta-capability deployment package of the first IoT device.

[0167] For example, the attribute information of each meta-capability deployment package may include at least the following attributes: meta-capability name, version information, meta-capability type, size of the meta-capability deployment package (i.e., the storage space occupied by the meta-capability deployment package), number of times the meta-capability deployment package is used on the first IoT device, and permissions required by the meta-capability deployment package.

[0168] S204. The second IoT device decides whether to install the target meta-capability deployment package based on the attribute information of the received target meta-capability deployment package.

[0169] For example, the second IoT device may receive attribute information of one or more target meta-capability deployment packages. The second IoT device can decide to install one or more of these target meta-capability deployment packages based on the received attribute information.

[0170] S205. The second IoT device obtains the target meta-capability deployment package for decision installation from the first IoT device and installs it.

[0171] For example, when a second IoT device decides to install a certain target meta-capability deployment package, it can obtain the target meta-capability deployment package from the first IoT device and install it.

[0172] In this method, the application installation package in the first IoT device is split into one or more meta-capability deployment packages according to different dimensions. The first IoT device and the second IoT device interact via a local area network to deploy the corresponding meta-capability deployment packages on the second IoT device, enabling the second IoT device to perform corresponding functions. On the one hand, this can greatly reduce the storage resources occupied by the application installation package on the second IoT device. On the other hand, it can also solve the application deployment problem for some second IoT devices that cannot connect to the network.

[0173] The following is in conjunction with the above. Figure 1 The distributed operating system implementation scenario shown takes a mobile phone 110 as the first IoT device and a watch 120 as the second IoT device, with the mobile phone 110 including a first social software application installation package. Figure 2 The specific implementation of the application deployment method shown is illustrated by example.

[0174] For example, Figure 5 This is a schematic diagram illustrating the composition of the first social software application installation package provided in an embodiment of this application. (See diagram below.) Figure 5As shown, the first social software application installation package is a distributed application installation package, which may include: a text chat capability deployment package, a video call capability deployment package, an audio call capability deployment package, a shopping capability deployment package, and a package attribute information table (packinfo). Each meta-capability deployment package may include a configuration list corresponding to that meta-capability deployment package, as well as dynamic libraries, resource files, and meta-capability business code used to implement the functions of that meta-capability deployment package. The package attribute information table may include attribute information for the text chat capability deployment package, the video call capability deployment package, the audio call capability deployment package, and the shopping capability deployment package.

[0175] For example, the configuration manifest corresponding to each meta-capability deployment package can be named "config.json" file, the dynamic library used to implement the functionality of the meta-capability deployment package can be named "so", the resource file can be named "resource", and the dynamic library of meta-capability business code can be named "ability".

[0176] The text chat deployment package can independently implement text chat functionality, the video call deployment package can independently implement video call functionality, the audio call deployment package can independently implement audio call functionality, and the shopping deployment package can independently implement shopping functionality. Text chat capability can be considered the core (entry) capability of the first social networking application, while video call capability, audio call capability, and shopping capability can be considered additional capabilities of the first social networking application.

[0177] Watch 120 can send a first message to mobile phone 110, the first message including the capability information of watch 120. The specific triggering conditions for watch 120 to send the first message to mobile phone 110 are described in the foregoing embodiments.

[0178] After receiving the first message from the watch 120, the mobile phone 110 can determine the target meta-capability deployment package suitable for installation on the watch 120 based on the capability information of the watch 120 included in the first message and the configuration list corresponding to each meta-capability deployment package in the first social software application installation package.

[0179] For example, the capability information of watch 120 may include the device type, device version, device level, device hardware capabilities, central processing unit-application binary interface (CPU-ABI) type, etc.

[0180] For example, in the capability information of Watch 120, the device type can be Watch; the device version can be version 2.0 or 3.0; the device level can be Level 3; the device hardware capabilities can include Watch 120 supporting landscape and portrait modes, sound playback, Wi-Fi, Bluetooth, heart rate monitoring, etc.; the CPU-ABI type can include arm64-v8a, armeabi-v7a, X86, X86-64, mips, mips64, etc.

[0181] Device levels can be categorized based on factors such as the abundance of resources available to the IoT device, its ability to independently connect to the network, and / or its human-computer interaction capabilities. For example, IoT devices can be classified into levels 0 to 5, corresponding to L0 to L5, based on their capabilities in random access memory (RAM), read-only memory (ROM), and CPU. Higher-level IoT devices generally have stronger performance. No restrictions are placed on the method used to classify IoT devices.

[0182] For example, the configuration list corresponding to each meta-capability deployment package in the first social software application installation package may include: the device type suitable for the meta-capability deployment package, the minimum device version requirement corresponding to the device type suitable for the meta-capability deployment package, the minimum device level suitable for the meta-capability deployment package, the hardware capability requirements required for the meta-capability deployment package, the CPU-ABI type supported by the meta-capability deployment package, and the scenario type applicable to the meta-capability deployment package.

[0183] For example, the configuration list of the text chat capability deployment package may include: the suitable device types for the text chat capability deployment package are smart screens, watches, and refrigerators; the minimum device version requirement for the suitable device types is smart screen version 2.0, watch version 3.0, and refrigerator version 2.0; the minimum device level for the text chat capability deployment package is level 3; the hardware requirements for the text chat capability deployment package are a screen, Wi-Fi, and input; the CPU-ABI type supported by the text chat capability deployment package is arm64 and arm32 architecture; and the applicable scenario type for the text chat capability deployment package is chat scenarios.

[0184] The configuration list for the video call capability deployment package may include: the suitable device types for the video call capability deployment package are smart screens and watches; the minimum device version requirement for the suitable device types is smart screen version 2.0 and watch version 3.0; the minimum device level for the video call capability deployment package is level 4; the required hardware capabilities for the video call capability deployment package are a screen, microphone, and Wi-Fi; the CPU-ABI type supported by the video call capability deployment package is arm64 and arm32 architecture; and the applicable scenario type for the video call capability deployment package is video call scenarios.

[0185] The configuration list for the voice call capability deployment package may include: the suitable device types for the voice call capability deployment package are smart screens, watches, and speakers; the minimum device version requirements for the suitable device types are smart screen version 2.0, watch version 3.0, and speaker version 1.0; the minimum device level for the voice call capability deployment package is level 4; the required hardware capabilities for the voice call capability deployment package include a microphone and Wi-Fi; the CPU-ABI type supported by the voice call capability deployment package is arm64 and arm32 architecture; and the applicable scenario type for the voice call capability deployment package is a voice call scenario.

[0186] The configuration list for the shopping capability deployment package may include: the suitable device types for the shopping capability deployment package are smart screens, watches, and refrigerators; the minimum device version requirements for the suitable device types are smart screen version 2.0, watch version 3.0, and refrigerator version 1.0; the minimum device level for the shopping capability deployment package is level 3; the required hardware capabilities for the shopping capability deployment package include a microphone and Wi-Fi; the CPU-ABI type supported by the shopping capability deployment package is arm64 and arm32 architecture; and the applicable scenario type for the shopping capability deployment package is shopping scenarios.

[0187] It should be noted that the above descriptions of the capabilities of Watch 120 and the configuration list corresponding to the meta-capability deployment package are merely illustrative and are not intended to limit the scope of the information.

[0188] In some embodiments, the capability information of watch 120 may include one or more of the capability information listed above, or may include more types of capability information. The configuration list corresponding to the meta-capability deployment package may also include one or more of the information contained in the configuration lists listed above, or may include more types of information.

[0189] In addition, in some implementations, certain meta-capability deployment packages may be applicable to one or more scenario types. When a meta-capability deployment package is applicable to multiple scenario types, the configuration list corresponding to that meta-capability deployment package will include the various scenario types applicable to that meta-capability deployment package.

[0190] Optionally, each meta-capability deployment package may also include identification information for that meta-capability deployment package, such as the name of the meta-capability deployment package.

[0191] In one possible design, the configuration list corresponding to each meta-capability deployment package in the first social software application installation package may include multiple fields. These fields can be used to identify the device type suitable for the meta-capability deployment package, the minimum device version requirement corresponding to the device type suitable for the meta-capability deployment package, the minimum device level suitable for the meta-capability deployment package, the hardware capability requirements required for the meta-capability deployment package, the CPU-ABI type supported by the meta-capability deployment package, and the scenario type applicable to the meta-capability deployment package, etc.

[0192] For example, the configuration list corresponding to each meta-capability deployment package may include the following fields: name, deviceTypes, deviceVersions, deviceLevel, reqCapabilities, supportAbi, and moduleType. The name field identifies the name of the meta-capability deployment package; the deviceTypes field identifies the suitable device types; the deviceVersions field identifies the minimum device version requirement for the suitable device types; the deviceLevel field identifies the minimum device level suitable for the meta-capability deployment package; the reqCapabilities field identifies the required hardware capabilities; the supportAbi field identifies the CPU-ABI types supported by the meta-capability deployment package; and the moduleType field identifies the applicable scenario type.

[0193] Based on the aforementioned capability information of the watch 120 and the configuration list corresponding to each meta-capability deployment package in the first social software application installation package, the step of the mobile phone 110 determining the target meta-capability deployment package suitable for installation on the watch 120 according to the capability information of the watch 120 included in the first message and the configuration list corresponding to each meta-capability deployment package in the first social software application installation package may include:

[0194] Based on the capability information of the watch 120, the mobile phone 110 queries the configuration list corresponding to each meta-capability deployment package in the text chat capability deployment package, video call capability deployment package, audio call capability deployment package, and shopping capability deployment package to determine which meta-capability deployment packages the watch 120's capabilities can meet. Then, the mobile phone 110 can identify the meta-capability deployment packages that the watch 120's capabilities can meet as the target meta-capability deployment packages suitable for installation on the watch 120.

[0195] For example, mobile phone 110 can query the configuration list corresponding to the text chat capability deployment package based on the capability information of watch 120, and determine whether the device type of watch 120 is a suitable device type for the text chat capability deployment package, whether the device version of watch 120 meets (is higher than or equal to) the minimum device version requirement corresponding to the suitable device type of the text chat capability deployment package, whether the device level of watch 120 meets the minimum device version requirement corresponding to the suitable device type of the text chat capability deployment package, whether the hardware capabilities of watch 120 meet the hardware capability requirements required by the text chat capability deployment package, and whether the CPU-ABI type of watch 120 meets the CPU-ABI type supported by the text chat capability deployment package, etc. When all the above conditions are met, mobile phone 110 can determine that the text chat capability deployment package is a suitable target meta-capability deployment package for watch 120 to install.

[0196] Similarly, mobile phone 110 can determine whether the video call capability deployment package, audio call capability deployment package, and shopping capability deployment package are suitable target meta-capability deployment packages for installation on watch 120.

[0197] Understandably, the target meta-capability deployment package that the phone 110 ultimately determines to be suitable for the watch 120 installation may include one or more.

[0198] After determining a suitable target meta-capability deployment package for watch 120, mobile phone 110 can send the target meta-capability deployment package's attribute information to watch 120. Watch 120 can then decide whether to install the target meta-capability deployment package based on the received attribute information.

[0199] Optionally, when the mobile phone 110 determines that there are multiple target meta-capability deployment packages suitable for installation on the watch 120, the mobile phone 110 can package the attribute information of the multiple target meta-capability deployment packages and send them to the watch 120.

[0200] For example, the attribute information of each meta-capability deployment package may include at least the following attributes: meta-capability name, version information, meta-capability type, size of the meta-capability deployment package (i.e., the storage space occupied by the meta-capability deployment package), number of times the meta-capability deployment package is used on mobile phone 110 (i.e., the first IoT device), and permissions required by the meta-capability deployment package.

[0201] In some embodiments, the watch 120 may have preset decision conditions, and the watch 120 may determine whether to install the target meta-capability deployment package based on the attribute information of the received target meta-capability deployment package and the preset decision conditions.

[0202] For example, the decision conditions may include one or more of the following: the remaining storage space of watch 120 is greater than the size of the target meta-capability deployment package, the remaining battery power of watch 120 is greater than a first threshold, watch 120 is currently in a screen-off and charging state (the screen-off state has the least impact on the user), the number of times the target meta-capability deployment package has been used on mobile phone 110 is greater than a second threshold, and the permissions required by the target meta-capability deployment package do not include sensitive permissions (such as photo access permission, contact access permission, etc.).

[0203] For any target meta-capability deployment package, when the watch 120 determines that the target meta-capability deployment package meets the preset decision conditions based on the received attribute information of the target meta-capability deployment package and the preset decision conditions, it can determine to install the target meta-capability deployment package.

[0204] Taking the attribute information of the text chat capability deployment package received by Watch 120 as an example, Figure 6 This is a schematic diagram illustrating the process by which the watch 120 decides whether to install the text chat capability deployment package, as provided in an embodiment of this application. Figure 6 As shown, the process by which watch 120 decides whether to install the text chat capability deployment package based on the attribute information of the text chat capability deployment package and the preset decision conditions may include S601-S607.

[0205] S601. Determine whether the remaining storage space of watch 120 is greater than the size of the text chat capability deployment package.

[0206] If yes, proceed to S602; otherwise, proceed to S607.

[0207] S602. Determine whether the remaining battery power of watch 120 is greater than the first threshold.

[0208] For example, the first threshold can be 30%, 50%, 60%, etc., and there is no restriction on the size of the first threshold.

[0209] If yes, then execute S603; otherwise, jump to S607.

[0210] S603, Determine whether the watch 120 is currently in a screen-off and charging state.

[0211] If yes, proceed to S604; otherwise, proceed to S607.

[0212] S604. Determine whether the number of times the text chat capability deployment package is used on mobile phone 110 is greater than the second threshold.

[0213] For example, the second threshold can be 5 times, 10 times, 18 times, etc., and there is no restriction on the size of the second threshold.

[0214] If yes, proceed to S605; otherwise, proceed to S607.

[0215] S605. Determine whether the permissions required for the text chat capability deployment package include sensitive permissions.

[0216] If yes, proceed to S607; otherwise, execute S606.

[0217] S606. Confirm the installation of the text chat capability deployment package.

[0218] S607. Determine not to install the text chat capability deployment package.

[0219] It should be noted that the decision conditions given above are all illustrative examples, and this application does not limit the specific type and number of decision conditions preset in watch 120. For example, the decision conditions preset in watch 120 may only include that the remaining storage space of watch 120 is greater than the size of the target meta-capability deployment package. As another example, the decision conditions preset in watch 120 may also include other decision conditions.

[0220] That is, in this embodiment of the application, the preset decision conditions in the watch 120 may include at least one. Optionally, the decision conditions may be set based on multiple different dimensions such as security (e.g., user privacy), user experience, and installation success rate.

[0221] In other embodiments, users can also set decision conditions on the watch 120. The watch 120 can then determine whether to install the target meta-capability deployment package based on the user-set decision conditions. For example, users can pre-set the type of meta-capability deployment package to be automatically downloaded and installed, the size of the first threshold, the size of the second threshold, and the permissions required by the meta-capability deployment package, based on the specific implementation scenario of the distributed operating system and their own preferences. The watch 120 can modify the decision conditions in response to the setting operation. The watch 120 can determine whether to install the target meta-capability deployment package based on the received attribute information of the target meta-capability deployment package and the decision conditions set by the user. The specific judgment method is the same as or similar to the above embodiments and will not be repeated here.

[0222] Optionally, the user can also set the decision conditions for the watch 120 on the mobile phone 110, and the mobile phone 110 can configure the decision conditions set by the user for the watch 120. There are no restrictions on the way the user sets the decision conditions for the watch 120.

[0223] Optionally, in some implementations, when setting decision conditions, the user can also set different weights for different decision conditions. When the watch 120 determines whether to install the target meta-capability deployment package based on the attribute information of the received target meta-capability deployment package and the decision conditions set by the user, it can comprehensively calculate whether to install the target meta-capability deployment package by combining the weights corresponding to each decision condition.

[0224] In some embodiments, when the watch 120 includes a display interface that can interact with the user, after receiving the attribute information of the target meta-capability deployment package, the watch 120 can also display an installation prompt for the target meta-capability deployment package on the display interface, allowing the user to choose whether to install the target meta-capability deployment package. The watch 120 can confirm the installation of the target meta-capability deployment package in response to the user's selection to install it. Alternatively, it can confirm not to install the target meta-capability deployment package in response to the user's selection not to install it. The display interface on which the watch 120 displays the installation prompt for the target meta-capability deployment package can be referred to as a third interface; the user's selection to install the target meta-capability deployment package on this display interface can be referred to as a third operation.

[0225] When watch 120 does not include a user-interactive display interface, after receiving the attribute information of the target meta-capability deployment package, watch 120 can also display an installation prompt for the target meta-capability deployment package on the display interface of phone 110. For example, watch 120 can send an instruction message to phone 110, instructing phone 110 to display the installation prompt for the target meta-capability deployment package on its display interface. The user can choose whether to install the target meta-capability deployment package on the display interface of phone 110. Phone 110 can respond to the user's choice to install the target meta-capability deployment package by notifying watch 120 (e.g., by sending an instruction message). Alternatively, phone 110 can respond to the user's choice not to install the target meta-capability deployment package by notifying watch 120 that the user has chosen not to install it. Thus, watch 120 can determine whether to install the target meta-capability deployment package based on the notification result from phone 110. The display interface on phone 110 that displays the installation prompt for the target meta-capability deployment package can be referred to as the second interface; the user's choice to install the target meta-capability deployment package on this display interface can be referred to as the second operation. Mobile phone 110 can notify watch 120 user via a second message to select to install the target meta capability deployment package.

[0226] In some embodiments, when the watch 120 receives the attribute information of the target meta-capability deployment package, it can first determine whether the remaining storage space of the watch 120 is greater than the size of the target meta-capability deployment package. When the remaining storage space of the watch 120 is greater than the size of the target meta-capability deployment package, the watch 120 will display an installation prompt for the target meta-capability deployment package on the display interface (or through the display interface of the mobile phone 110).

[0227] Understandably, watch 120 may receive attribute information of one or more target meta-capability deployment packages. When watch 120 receives attribute information of multiple target meta-capability deployment packages, watch 120 can determine whether each target meta-capability deployment package is installed in the manner described in the foregoing embodiments.

[0228] Optionally, when watch 120 receives attribute information of a target meta-capability deployment package, if watch 120 already has the target meta-capability deployment package, watch 120 can determine whether the version of the target meta-capability deployment package in phone 110 is higher than the version of the target meta-capability deployment package already installed locally (i.e., watch 120). If the version of the target meta-capability deployment package in phone 110 is higher than the version of the target meta-capability deployment package already installed locally, watch 120 can also decide to install the target meta-capability deployment package. If the version of the target meta-capability deployment package in phone 110 is not higher than the version of the target meta-capability deployment package already installed locally, watch 120 can decide not to install the target meta-capability deployment package.

[0229] That is, in the embodiments of this application, the conditions for the watch 120 to decide whether to install the target meta-capability deployment package may also include: when the watch 120 has the target meta-capability deployment package installed locally, but the version of the target meta-capability deployment package in the mobile phone 110 is higher than the version of the target meta-capability deployment package installed locally.

[0230] Based on the attribute information of the received target meta-capability deployment package, watch 120 determines which target meta-capability deployment package needs to be installed. Then, it can obtain the target meta-capability deployment package to be installed from mobile phone 110 and install it.

[0231] Understandably, in the case where the target meta-capability deployment package is already installed locally on watch 120, but the version of the target meta-capability deployment package on phone 110 is higher than the version of the locally installed target meta-capability deployment package, when watch 120 installs the target meta-capability deployment package obtained from phone 110, it can actually be installed by updating the locally installed target meta-capability deployment package.

[0232] The following describes the process by which the watch 120 obtains the target metadata deployment package for decision-making and installation from the mobile phone 110, and then installs it.

[0233] For example, after the watch 120 determines the target meta-capability deployment package to be installed, it can send a download request message to the mobile phone 110. The download request message may include the identification information of the target meta-capability deployment package that the watch 120 has decided to install. After receiving the download request message from the watch 120, the mobile phone 110 can extract the corresponding target meta-capability deployment package from the first social software application installation package according to the identification information of the target meta-capability deployment package that the watch 120 has decided to install and send it to the watch 120. After receiving the target meta-capability deployment package, the watch 120 can install the target meta-capability deployment package.

[0234] For example, assuming watch 120 determines that the target meta-capability deployment packages to be installed include: an audio call capability deployment package and a shopping capability deployment package, watch 120 can send a download request message to mobile phone 110. This download request message can include the identification information of the audio call capability deployment package and the shopping capability deployment package. After receiving the download request message from watch 120, mobile phone 110 can extract (copy) the audio call capability deployment package and the shopping capability deployment package from the first social software application installation package based on their respective identification information and send them to watch 120. Upon receiving the audio call capability deployment package and the shopping capability deployment package, watch 120 can install them.

[0235] In some embodiments, the identification information of the target meta-capability deployment package that the watch 120 decides to install can be the name of the target meta-capability deployment package or the name of the meta-capability. For example, the watch 120 can extract the name of the meta-capability corresponding to the target meta-capability deployment package from the attribute information of the received target meta-capability deployment package and use it as the identification information of the target meta-capability deployment package.

[0236] In other embodiments, after the watch 120 determines which target meta-capability deployment packages need to be installed, it can also package and send all or part of the attribute information of the target meta-capability deployment packages to the mobile phone 110. The attribute information of the target meta-capability deployment packages sent by the watch 120 to the mobile phone 110 can be used as the identification information of the target meta-capability deployment packages, and used to instruct the mobile phone 110 to decide which target meta-capability deployment packages to install.

[0237] Optionally, when the watch 120 decides to install multiple target meta-capability deployment packages, the mobile phone 110 can package the multiple target meta-capability deployment packages together and send them to the watch 120.

[0238] Optionally, to ensure security, when the mobile phone 110 sends the target meta-capability deployment package to the watch 120, it can extract the signature information of the first social software application installation package and distribute the signature information together with the target meta-capability deployment package to the watch 120.

[0239] In some embodiments, the step of deciding whether to install the target meta-capability deployment package on the watch 120 as described in the above embodiments can also be implemented on the mobile phone 110. For example, the mobile phone 110 may have preset decision conditions, and after determining that the target meta-capability deployment package is suitable for installation on the watch 120, the mobile phone 110 may not send the attribute information of the target meta-capability deployment package to the watch 120. The mobile phone 110 can obtain information such as the remaining storage space, remaining battery power, and whether the watch 120 is currently in a screen-off and charging state, and decide whether to install the target meta-capability deployment package based on the aforementioned information of the watch 120 and the attribute information of the target meta-capability deployment package. When the mobile phone 110 decides that the target meta-capability deployment package needs to be installed on the watch 120, the mobile phone 110 can actively send these target meta-capability deployment packages to the watch 120. This application does not impose any limitations on this.

[0240] Optionally, when the step of deciding whether to install the target meta-capability deployment package on the watch 120 can be implemented on the mobile phone 110, after deciding that the target meta-capability deployment package needs to be installed on the watch 120, the mobile phone 110 can also display the identification information of the target meta-capability deployment package to be installed on the watch 120 through a display interface. The user can click on one or more of the identification information of the target meta-capability deployment package on the display interface to trigger the mobile phone 110 to send the target meta-capability deployment package corresponding to the identification information selected by the user to the watch 120 for installation. That is, in this embodiment, the user can choose which target meta-capability deployment packages to install on the watch 110. The display interface on the mobile phone that displays the identification information of the target meta-capability deployment packages to be installed on the watch 120 can be called the second interface; the identification information of the target meta-capability deployment packages displayed on the second interface can be called the installation prompt, which is used to prompt the user whether to install the target meta-capability deployment packages corresponding to these identification information; the user's operation of clicking on one or more of the identification information of the target meta-capability deployment packages on the display interface can be called the second operation. After receiving the second operation, mobile phone 110 can send the target meta-capability deployment package corresponding to the user-selected identification information to watch 120 for installation via the second message.

[0241] The above embodiments are based on Figure 1Taking the distributed operating system implementation scenario shown as an example, the application deployment method provided in this application embodiment is illustrated by combining the interaction process between mobile phone 110 (first IoT device) and watch 120 (second IoT device). The interaction process between mobile phone 110 and smart screen 130, or mobile phone 110 and speaker 140, or mobile phone 110 and refrigerator 150 can refer to the above-described interaction process between mobile phone 110 and watch 120, and will not be described in detail here.

[0242] Furthermore, in this embodiment, the distributed application deployment package included in the first IoT device may include one or more (not limited to the aforementioned first social software application deployment package). When the number of distributed application deployment packages included in the first IoT device is multiple, for each distributed application deployment package, the first IoT device can distribute the meta-capability deployment package in the distributed application deployment package to the second IoT device in a manner similar to the aforementioned embodiment. The number of the second IoT devices can be multiple, and the first IoT device can distribute the multiple meta-capability deployment packages included in the distributed application deployment package to multiple second IoT devices respectively, so as to realize the collaboration of multiple second IoT devices in certain scenarios. When the first IoT device discovers multiple second IoT devices whose capabilities are compatible and can install a certain meta-capability deployment package based on the capability information sent by the second IoT devices, it can automatically decide or prompt the user to determine one or more second IoT devices that need to install the meta-capability deployment package. This embodiment does not limit the implementation scenarios of the distributed operating system to which the application deployment method can be applied, nor the number and type of distributed application deployment packages included in the first IoT device.

[0243] For example, in some implementation scenarios, a distributed operating system may include a mobile phone, a large screen, speakers, and a writing tablet. The mobile phone is connected to the large screen, speakers, and writing tablet respectively. The mobile phone pre-installs an online education application from vendor A, which includes a video capability deployment package, an interactive capability deployment package, and an audio capability deployment package. In this embodiment, the mobile phone can install the video capability deployment package on the large screen, the interactive capability deployment package on the writing tablet, and the audio capability deployment package on the speakers. The large screen, speakers, and writing tablet can collaboratively provide the user with the functionality of the online education application based on their respective installed capability modules.

[0244] For example, in other implementation scenarios, the distributed operating system may include a mobile phone, a large screen, and AR glasses. Using the application deployment method described in this application embodiment, the large screen can provide users with live streaming functionality, and the AR glasses can provide users with virtual try-on functionality. Alternatively, the distributed operating system may include a vehicle infotainment system and a mobile phone. Using the application deployment method described in this application embodiment, the vehicle infotainment system can provide users with navigation functionality, and the mobile phone can provide users with navigation audio playback functionality. Or, the distributed operating system may include a mobile phone, a smartwatch, and a treadmill. Using the application deployment method described in this application embodiment, the smartwatch can record running time and exercise habits for users, and the treadmill can automatically set running speed, etc.

[0245] In the application deployment method provided in this application embodiment, the second IoT device only needs to install the meta-capability deployment package to achieve the corresponding functions, and the storage space occupied by the application deployment package on the second IoT device can be greatly reduced. The way the first IoT device distributes the meta-capability deployment package to the second IoT device also greatly simplifies the application deployment process, making the deployment method simpler, faster, and more flexible. For example, IoT devices can complete the distributed application installation, update, and replacement deployment anytime and anywhere within the local area network according to the scenario, and can even allow users to install the application without noticing the process.

[0246] Furthermore, since the distributed application deployment package on the first IoT device consists of multiple meta-capability deployment packages, and some of these packages can be installed on different second IoT devices, this application deployment method can effectively improve the reusability of application installation packages, reduce the memory (storage) space occupied on the first IoT device, and achieve one-time download, multi-device deployment. For example, the above... Figure 5 The shopping capability deployment package shown in the first social software application installation package can be installed on either a refrigerator or a smart screen.

[0247] Optionally, in this embodiment of the application, for each type of distributed application installation package, the distributed operating system only needs to store one copy on a certain first IoT device.

[0248] It should be noted that the distributed application deployment package on the first IoT device needs to be downloaded from the server by the first IoT device. Other second IoT devices only need to obtain the corresponding metadata deployment package from the first IoT device for installation, thus reducing the download load on the server side.

[0249] Optionally, in some embodiments of this application, the first IoT device may have pre-set capability information of the second IoT device, or the first IoT device may query the capability information of the second IoT device from a server (such as the cloud). When the first IoT device detects a connection from the second IoT device, the first IoT device may automatically determine the target meta-capability deployment package suitable for installation on the second IoT device based on the capability information of the second IoT device and the configuration list corresponding to each meta-capability deployment package in the distributed application installation package. That is, in this embodiment, the second IoT device may not need to send a first message to the first IoT device.

[0250] Optionally, the first IoT device and the second IoT device may each start one or more services in their respective foundation processes to implement the interaction process between the first IoT device and the second IoT device as described in the embodiments of this application. The following example illustrates this by showing that the first IoT device and the second IoT device may each start a service in their respective foundations.

[0251] For example, Figure 7 This is a schematic diagram of the architecture of the first IoT device and the second IoT device provided in the embodiments of this application. Figure 7 As shown, the first IoT device may include applications such as Distributed Application 1 and Distributed Application 2, used to complete multi-device collaborative work in a distributed operating system. The first IoT device can start a package management service in its base process. The second IoT device can start a package decision service in its base process.

[0252] The first IoT device can implement the functions described in the foregoing embodiments through the package management service. The second IoT device can implement the functions described in the foregoing embodiments through the package decision service.

[0253] For example, the package management service can be used to determine the target meta-capability deployment package suitable for installation on the second IoT device based on the capability information of the second IoT device and the configuration list corresponding to each meta-capability deployment package in the distributed application installation package; and to send the attribute information of the target meta-capability deployment package to the second IoT device. The package decision service can be used to send a first message to the first IoT device; decide whether to install the target meta-capability deployment package based on the received attribute information of the target meta-capability deployment package; and to obtain the target meta-capability deployment package to be installed from the first IoT device and perform the installation.

[0254] Alternatively, please continue to refer to Figure 7 As shown, the first IoT device and the second IoT device may each include a query and download interface, and the first IoT device and the second IoT device can interact with each other through their query and download interfaces.

[0255] Optionally, the first and second IoT devices can also decide the specific type of service they launch based on whether a distributed application is included. For example, when distributed application 3 is installed on the second IoT device, the second IoT device can also launch a package management service in its base process, and the first IoT device can also launch a package decision service in its base process. The package management service launched by the second IoT device and the package decision service launched by the first IoT device can be used to cooperate in deploying the meta-capability deployment package of distributed application 3 to the first IoT device. That is, in this embodiment, the two IoT devices can decide the type of service they launch (such as package management service or package decision service) according to the application deployment needs (such as the first IoT device deploying to the second IoT device, or the second IoT device deploying to the first IoT device), and this application does not limit this.

[0256] The above embodiments illustrate the application deployment method provided in this application embodiment by taking the example that the first application included in the first IoT device can be divided into multiple capability modules (capability modules can also be called meta-capability modules, capability units, etc.), and each capability module consists of a meta-capability deployment package to implement an independent function.

[0257] Optionally, in some embodiments, some or all of the capability modules included in the first application may also be composed of multiple meta-capability deployment packages. When a capability module is composed of multiple meta-capability deployment packages, the capability module can be used to implement multiple corresponding functions.

[0258] For example, a distributed application installation package could be the installation package for a social media application. This social media application's installation package could include meta-capability deployment packages such as text chat capability deployment packages, video call capability deployment packages, audio call capability deployment packages, and shopping capability deployment packages. Among these, text chat capability deployment packages, video call capability deployment packages, and audio call capability deployment packages can form a social capability module, and shopping capability deployment packages can form an entertainment capability module, etc. There are no restrictions on the way capability modules are divided here.

[0259] In this embodiment, the first IoT device can, at the capability module level, determine a suitable target capability module (such as a first target capability module) for installation on the second IoT device from among multiple capability modules included in the first application, based on the capability information of the second IoT device, and send the first target capability module to the second IoT device. When the first target capability module consists of a single meta-capability deployment package, the second IoT device can implement one function corresponding to the first target capability module after installing it. When the first target capability module consists of multiple meta-capability deployment packages, the second IoT device can implement multiple functions corresponding to the first target capability module after installing it.

[0260] Optionally, the number of first target capability modules can be one or more.

[0261] Similarly, a distributed operating system can also include a third IoT device (the third IoT device has the same device form as the second IoT device). At the capability module level, the first IoT device, based on the capability information of the third IoT device, can determine a suitable target capability module (such as a second target capability module) from among multiple capability modules included in the first application, and send the second target capability module to the third IoT device. The second target capability module can consist of one or more meta-capability deployment packages, used to implement one or more functions.

[0262] Optionally, the number of second target capability modules can be one or more.

[0263] For example, taking a mobile phone as an IoT device, Figure 8 This is a schematic diagram of the hardware composition of the IoT device provided in the embodiments of this application.

[0264] like Figure 8 As shown, a mobile phone may include a processor 810, an external memory interface 820, an internal memory 821, a universal serial bus (USB) interface 830, a charging management module 840, a power management module 841, a battery 842, antenna 1, antenna 2, a mobile communication module 850, a wireless communication module 860, an audio module 870, a speaker 870A, a receiver 870B, a microphone 870C, a headphone jack 870D, a sensor module 880, buttons 890, a motor 891, an indicator 892, a camera 893, a display screen 894, and a subscriber identification module (SIM) card interface 895, etc.

[0265] The processor 810 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

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

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

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

[0269] The external storage interface 820 can be used to connect an external storage card, such as a Micro SD card, to expand the phone's storage capacity. The external storage card communicates with the processor 810 through the external storage interface 820 to perform data storage functions. For example, it can save files such as pictures, music, and videos to the external storage card.

[0270] The internal memory 821 can be used to store computer executable program code, which includes instructions. The processor 810 executes various functional applications and data processing of the mobile phone by running the instructions stored in the internal memory 821. For example, when the mobile phone is used as a first IoT device, the processor 810 can execute various functions of the first IoT device in the application deployment method provided in this application embodiment by running the instructions stored in the internal memory 821.

[0271] The internal memory 821 may further include a program storage area and a data storage area. The program storage area may store the operating system, at least one application required for a function (such as a first social software application), etc. The data storage area may store data created during the use of the mobile phone (such as image data, phonebook data, etc.). Furthermore, the internal memory 821 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0272] The charging management module 840 receives charging input from the charger. While charging the battery 842, the charging management module 840 can also power the mobile phone via the power management module 841. The power management module 841 connects the battery 842, the charging management module 840, and the processor 810. The power management module 841 can also receive input from the battery 842 to power the mobile phone.

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

[0274] Alternatively, the mobile phone can access the distributed network of the distributed operating system via wireless functionality.

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

[0276] The sensor module 880 may include a pressure sensor 880A, a gyroscope sensor 880B, a barometric pressure sensor 880C, a magnetic sensor 880D, an accelerometer sensor 880E, a proximity sensor 880F, a proximity light sensor 880G, a fingerprint sensor 880H, a temperature sensor 880J, a touch sensor 880K, an ambient light sensor 880L, a bone conduction sensor 880M, etc.

[0277] The display screen 894 is used to display images, videos, etc. The display screen 894 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the mobile phone may include one or N displays 894, where N is a positive integer greater than 1. For example, the display screen 894 can be used to display an application interface, or display any display interface that the mobile phone can display in the application deployment method described in the foregoing embodiments.

[0278] The mobile phone implements its display function through a GPU, a display screen 894, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 894 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 810 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0279] Understandable Figure 8 The structure shown does not constitute a specific limitation on the mobile phone. In some embodiments, the mobile phone may also include... Figure 8 This could mean having more or fewer components, combining some components, separating some components, or having different component arrangements. Or, Figure 8 Some of the components shown can be implemented in hardware, software, or a combination of both.

[0280] Additionally, when IoT devices are tablets, writing tablets, wearable devices (such as watches, wristbands, and headphones), large screens (such as smart screens), laptops, augmented reality (AR) / virtual reality (VR) devices (such as VR glasses), cars (or in-vehicle systems), cameras, robot vacuums, rice cookers, speakers, treadmills, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), and other devices, the specific structures of these other IoT devices can also be referenced. Figure 8 As shown. For example, other IoT devices could be... Figure 8 The components were added or removed based on the given structure, which will not be elaborated here.

[0281] It should be understood that the above embodiments are merely illustrative examples of the application deployment method provided in this application. In other possible implementations, some execution steps may be omitted or added to the above embodiments, or the order of some steps in the above embodiments may be adjusted, and this application does not impose any limitations on these aspects.

[0282] Corresponding to the application deployment method described in the foregoing embodiments, this application provides an application deployment apparatus. This apparatus can be applied to a first device to implement the steps that the first device (i.e., the first IoT device) can perform in the application deployment method described in the foregoing embodiments. The function of this apparatus can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0283] For example, Figure 9 This is a schematic diagram of the application deployment device provided in an embodiment of this application. Figure 9 As shown, the device may include a sending unit 901, a receiving unit 902, and a processing unit 903. The sending unit 901, receiving unit 902, and processing unit 903 can be used to cooperate in implementing the steps performed by the first device in the application deployment method described in the foregoing embodiments. For example, the sending unit 901 can be used to send a first target capability module to the second device. The receiving unit 902 can be used to receive a first message from the second device. The processing unit 903 can be used to determine a first target capability module suitable for installation on the second device from among multiple capability modules included in the first application, based on the capability information of the second device.

[0284] It should be understood that the device may also include other modules or units for implementing the steps performed by the first device in the application deployment method described in the foregoing embodiments, such as a display unit, which are not shown here one by one.

[0285] Optionally, embodiments of this application also provide an application deployment apparatus, which can be applied to a second device to implement the steps performed by the second device (i.e., the second IoT device) in the methods described in the foregoing method embodiments. The functionality of this apparatus can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned functions.

[0286] For example, Figure 10 Another structural schematic diagram of the application deployment device provided in the embodiments of this application. For example... Figure 10 As shown, the device may include a sending unit 1001, a receiving unit 1002, and a processing unit 1003. The sending unit 1001, receiving unit 1002, and processing unit 1003 can be used to cooperate in implementing the steps performed by the second device in the application deployment method described in the foregoing embodiments. For example, the sending unit 1001 can be used to send a first message to the first device. The receiving unit 1002 can be used to receive a first target capability module from the first device. The processing unit 1003 can be used to decide whether to install the first target capability module, etc.

[0287] It should be understood that the device may also include other modules or units for implementing the steps performed by the second device in the application deployment method described in the foregoing embodiments, such as a display unit, which are not shown here one by one.

[0288] It should be understood that the division of units (or modules) in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely in software through processing element calls; all units can be implemented entirely in hardware; or some units can be implemented in software through processing element calls, while others can be implemented in hardware.

[0289] For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, invoked and executed by a processing element within the device. Furthermore, these units can be integrated in whole or in part, or implemented independently. The processing element described here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In implementation, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software invoked by the processing element.

[0290] In one example, the unit in the above device may be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0291] For example, when the units in the device can be implemented through a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. Alternatively, these units can be integrated together to form a system-on-a-chip (SOC).

[0292] In one implementation, the units that implement the corresponding steps in the above methods can be implemented in the form of a processing element scheduler. For example, the device may include a processing element and a storage element, wherein the processing element calls a program stored in the storage element to execute the steps performed by the first or second device in the method embodiments described above. The storage element may be a storage element located on the same chip as the processing element, i.e., an on-chip storage element.

[0293] In another implementation, the program for performing the above methods can be located on a storage element on a different chip than the processing element, i.e., an off-chip storage element. In this case, the processing element calls or loads the program from the off-chip storage element onto the on-chip storage element to call and execute the steps performed by the first or second device in the method embodiments described above.

[0294] For example, embodiments of this application may also provide an apparatus, such as an electronic device. The electronic device may include: a processor; a memory; and a computer program; wherein the computer program is stored in the memory, and when the computer program is executed by the processor, it causes the electronic device to perform the steps executed by the first or second device as described in the foregoing embodiments. The memory may be located within or outside the electronic device. The processor may include one or more processors.

[0295] For example, the electronic device can be any of the following IoT devices: mobile phone, tablet, writing tablet, wearable device (such as watch, bracelet, earphone), large screen (such as smart screen), laptop, augmented reality (AR) / virtual reality (VR) device (such as VR glasses), car (or in-vehicle device), camera, robot vacuum cleaner, rice cooker, speaker, treadmill, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc.

[0296] In another implementation, the unit that implements the steps of the above method can be configured as one or more processing elements, which can be integrated circuits, such as one or more ASICs, or one or more DSPs, or one or more FPGAs, or combinations of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.

[0297] For example, this application also provides a chip that can be applied to the aforementioned electronic device. The chip includes one or more interface circuits and one or more processors; the interface circuits and processors are interconnected via lines; the processor receives and executes computer instructions from the memory of the electronic device through the interface circuits to implement the steps performed by the first device or the second device as described in the foregoing embodiments.

[0298] This application also provides a computer program product, including computer-readable code, which, when run in an electronic device, causes the electronic device to perform the steps executed by the first device or the second device as described in the foregoing embodiments.

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

[0300] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0301] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium.

[0302] Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product, such as a program. This software product is stored in a program product, such as a computer-readable storage medium, and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0303] For example, embodiments of this application may also provide a computer-readable storage medium comprising a computer program that, when executed on an electronic device, causes the electronic device to perform the steps executed by the first or second device as described in the foregoing embodiments.

[0304] Optionally, embodiments of this application also provide a distributed operating system, including: a first device and a second device, connected together; the first device includes a first application, which includes multiple capability modules that can be installed. The first device can determine a first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device, and send the first target capability module to the second device; the second device can receive and install the first target capability module. After the second device installs the first target capability module, it can implement corresponding functions through the first target capability module.

[0305] Both the first device and the second device are IoT devices. The first device can be an IoT device with relatively abundant device resources (such as CPU resources, memory resources, storage resources, etc.) that can independently connect to the network and interact with humans, such as a mobile phone, tablet computer, or laptop computer.

[0306] The second device can be any of the following IoT devices: mobile phone, tablet, writing tablet, wearable device (such as watch, bracelet, earphone), large screen (such as smart screen), laptop, augmented reality (AR) / virtual reality (VR) device (such as VR glasses), car (or in-vehicle device), camera, robot vacuum cleaner, rice cooker, speaker, treadmill, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc. For example, the second device can be an IoT device with fewer resources than the first device, unable to independently connect to the network and / or interact with humans, such as a writing tablet, earphones, VR glasses, in-vehicle device, rice cooker, speaker, treadmill, etc. Alternatively, the second device can be the same as the first device, with abundant resources, capable of independent network connection and human-computer interaction.

[0307] In this distributed operating system, the application installation package on the first device is broken down into one or more capability modules according to different dimensions. The first device interacts with the second device to deploy the corresponding capability modules on the second device, enabling the second device to perform the corresponding functions. On the one hand, this can greatly reduce the storage resources occupied by the application installation package on the second device. On the other hand, it can also solve the application deployment problem for some second devices that cannot connect to the network.

[0308] Optionally, the second device may send a first message to the first device, the first message including the capability information of the second device. After receiving the first message, the first device may determine a first target capability module suitable for installation on the second device from among multiple capability modules included in the first application, based on the capability information of the second device included in the first message.

[0309] In this design, the capability information of the second device can be reported to the first device through a first message, so that the first device can determine the first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device.

[0310] In one possible design, the first device can send a query request message to the second device to query the capabilities of the second device. Upon receiving the query request message from the first device, the second device can send a first message to the first device.

[0311] In this design, the first device can actively send a query request message to the second device to trigger the second device to return a first message to the first device based on the query request message.

[0312] In some implementations, when the second device establishes a connection with the first device, the first device can send a query request message to the second device.

[0313] In this implementation, the trigger condition for the first device to send a query request message to the second device is that the second device establishes a connection with the first device. For example, when the second device accesses the local area network where the first device is located, the first device can detect the access of the second device. When the first device detects the access of the second device, it can proactively send a query request message to the second device.

[0314] In other implementations, the first device may display a first interface, which includes device identifiers of one or more second devices; the first device may receive a first operation, which is to select a device identifier of the second device on the first interface; and the first device may respond to the first operation by sending a query request message to the second device.

[0315] In this implementation, the trigger condition for the first device to send a query request message to the second device is that the first device receives a first operation. For example, the first operation is that the user actively selects which or more second devices to send the query request message to on the first interface. The first device can respond to the user's first operation and send the query request message to the second devices actively selected by the user.

[0316] In another possible design, when the second device establishes a connection with the first device, the second device can send a first message to the first device.

[0317] For example, the first device and the second device may each include a distributed network module. When the second device accesses the distributed network where the first device is located, the second device learns through its own distributed network module that the first device includes a distributed application installation package. Therefore, the second device can proactively send a first message to the first device. The distributed network module can be a separate chip or a software module integrated into the processor of the IoT device.

[0318] Optionally, the second device may access the distributed network where the first device is located for the first time, and / or, the second device may reconnect to the distributed network after being disconnected from it. For example, the second device may disconnect from the distributed network where the first device is located after a power outage or shutdown. Subsequently, when the second device is powered on again, it may send a first message to the first device.

[0319] In some embodiments, each capability module included in the first application includes a configuration list corresponding to the capability module; the first device determines a first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device, including: the first device determines a first target capability module suitable for installation on the second device from the multiple capability modules included in the first application based on the capability information of the second device and the configuration list corresponding to each capability module included in the first application.

[0320] For example, the configuration list corresponding to each capability module includes one or more of the following: the device type suitable for the capability module, the minimum device version requirement corresponding to the device type suitable for the capability module, the minimum device level suitable for the capability module, the hardware capability requirements required by the capability module, the CPU-ABI type supported by the capability module, and the scenario type applicable to the capability module.

[0321] For example, the capability information of the second device includes one or more of the following: device type, device version, device level, device hardware capabilities, and CPU-ABI type.

[0322] Device levels can be categorized based on factors such as the abundance of resources available to the IoT device, its ability to independently connect to the network, and / or its human-computer interaction capabilities. For example, IoT devices can be classified into levels 0 to 5, corresponding to L0 to L5, based on their capabilities in random access memory (RAM), read-only memory (ROM), and CPU. Higher-level IoT devices generally have stronger performance. No restrictions are placed on the method used to classify IoT devices.

[0323] In one possible design, the first device can send attribute information of a first target capability module to the second device; the second device can receive the attribute information of the first target capability module from the first device and decide whether to install the first target capability module based on the attribute information; when the second device decides to install the first target capability module, the second device can send a download request message to the first device. The first device can receive the download request message from the second device, and the download request message includes the identification information of the first target capability module. After receiving the download request message, the first device can send the first target capability module to the second device based on the identification information of the first target capability module.

[0324] For example, the attribute information of the first target capability module includes one or more of the following: the capability name, version information, capability type, size of the first target capability module, number of times the first target capability module is used on the first device, and permissions required by the first target capability module.

[0325] In this design, the second device can decide whether to install the first target capability module based on its attribute information. When the second device decides to install the first target capability module, it can send a download request message to the first device, which includes the identification information of the first target capability module. After receiving the download request message, the first device can send the first target capability module to the second device.

[0326] Optionally, the second device includes preset decision conditions; the second device decides whether to install the first target capability module based on the attribute information of the first target capability module, including: when the second device determines that the first target capability module meets the decision conditions based on the attribute information of the first target capability module, it decides to install the first target capability module.

[0327] For example, the decision conditions include one or more of the following: the remaining storage space of the second device is greater than the size of the first target capability module, the remaining battery power of the second device is greater than the first threshold, the second device is currently in a screen-off and charging state, the number of times the first target capability module has been used on the first device is greater than the second threshold, and the permissions required by the first target capability module do not include sensitive permissions.

[0328] In some embodiments, the second device may modify the decision conditions in response to a setting operation on the decision conditions.

[0329] In this embodiment, the user can actively set decision conditions on either the first or second device. The second device can modify the decision conditions in response to the user's setting. Then, the second device can decide whether to install a certain capability module based on the user-set decision conditions.

[0330] In another possible design, the first device may display a second interface, which includes installation prompts for the first target capability module; the first device may receive a second operation, which is to select to install the first target capability module; and the first device may respond to the second operation by sending a second message to the second device, which instructs the second device to install the first target capability module.

[0331] In this design, the user can choose whether to install the first target capability module on the second device via a second interface provided by the first device. When the first device receives the user's operation to install the first target capability module (i.e., the second operation), it can instruct the second device to install the first target capability module via a second message.

[0332] In another possible design, the second device can display a third interface, which includes installation prompts for the first target capability module; the second device can receive a third operation, which is to select to install the first target capability module; and the second device can install the first target capability module in response to the third operation.

[0333] In this design, the user can choose whether to install the first target capability module on the second device via a third interface provided by the second device. When the second device receives the user's selection to install the first target capability module (i.e., the third operation), it can install the first target capability module.

[0334] In some embodiments, the distributed operating system further includes: a third device, with the first device connected to the third device; the first device can determine a second target capability module suitable for installation on the third device from a plurality of capability modules included in the first application based on the capability information of the third device, and send the second target capability module to the third device; the third device can receive and install the second target capability module.

[0335] Optionally, the first target capability module and the second target capability module may be the same or different.

[0336] That is, in this embodiment, the first device can be connected to multiple different devices such as the second device and the third device. The first device can determine the target capability module suitable for installation on each device from the multiple capability modules included in the first application based on the capability information of the different devices connected to it, and send the target capability module suitable for installation on each device.

[0337] Similarly, in this distributed operating system, the first device can be used to implement all the functions implemented by the first device in the aforementioned method embodiments, and the second device can be used to implement all the functions implemented by the second device in the aforementioned sixth aspect, which will not be elaborated here.

[0338] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An application deployment method, characterized in that, The method is applied to a first IoT device, which is connected to a second IoT device; the first IoT device includes a first application, which includes multiple capability modules that can be installed. The capability module has the ability to implement one or more functions; the method includes: The first IoT device determines a first target capability module suitable for installation on the second IoT device from among the multiple capability modules included in the first application, based on the capability information of the second IoT device. The first IoT device sends the attribute information of the first target capability module to the second IoT device; The first IoT device receives a download request message from the second IoT device, the download request message including the identification information of the first target capability module; The first IoT device sends the first target capability module to the second IoT device.

2. The method according to claim 1, characterized in that, Before the first IoT device determines a first target capability module suitable for installation on the second IoT device from among multiple capability modules included in the first application based on the capability information of the second IoT device, the method further includes: The first IoT device receives a first message from the second IoT device, the first message including the capability information of the second IoT device.

3. The method according to claim 2, characterized in that, Before the first IoT device receives the first message from the second IoT device, the method further includes: The first IoT device sends a query request message to the second IoT device, the query request message being used to query the capability information of the second IoT device.

4. The method according to claim 3, characterized in that, The first IoT device sends a query request message to the second IoT device, including: When the second IoT device establishes a connection with the first IoT device, the first IoT device sends a query request message to the second IoT device.

5. The method according to claim 3, characterized in that, The first IoT device sends a query request message to the second IoT device, including: The first IoT device displays a first interface, which includes device identifiers of one or more second IoT devices. The first IoT device receives a first operation, which is to select the device identifier of the second IoT device on the first interface; In response to the first operation, the first IoT device sends a query request message to the second IoT device.

6. The method according to any one of claims 1-5, characterized in that, The first application includes a configuration list for each capability module; The first IoT device determines a first target capability module suitable for installation on the second IoT device from among multiple capability modules included in the first application, based on the capability information of the second IoT device, including: The first IoT device determines a first target capability module suitable for installation on the second IoT device from among the multiple capability modules included in the first application, based on the capability information of the second IoT device and the configuration list corresponding to each capability module included in the first application.

7. The method according to claim 6, characterized in that, The configuration list for each capability module includes one or more of the following: the device type suitable for the capability module, the minimum device version requirement corresponding to the device type suitable for the capability module, the minimum device level suitable for the capability module, the hardware capability requirements required by the capability module, the CPU-ABI type supported by the capability module, and the scenario types applicable to the capability module.

8. The method according to claim 6, characterized in that, The capability information of the second IoT device includes one or more of the following: device type, device version, device level, device hardware capabilities, and CPU-ABI type.

9. The method according to claim 1, characterized in that, The attribute information of the first target capability module includes one or more of the following: The first target capability module's capability name, version information, capability type, size of the first target capability module, number of times the first target capability module is used on the first IoT device, and permissions required by the first target capability module.

10. The method according to claim 1, characterized in that, The method further includes: The first IoT device displays a second interface, which includes installation prompts for the first target capability module; The first IoT device receives a second operation, which is to select the installation of the first target capability module; In response to the second operation, the first IoT device sends a second message to the second IoT device, the second message being used to instruct the second IoT device to install the first target capability module.

11. The method according to any one of claims 1-5, characterized in that, The first IoT device is also connected to a third device; the method further includes: The first IoT device determines a second target capability module suitable for installation on the third device from among the multiple capability modules included in the first application, based on the capability information of the third device. The first IoT device sends the second target capability module to the third device.

12. An application deployment method, characterized in that, The method is applied to a second IoT device, which is connected to a first IoT device; the first IoT device includes a first application, which includes multiple capability modules that can be installed. The capability module has the ability to implement one or more functions; the method includes: The second IoT device receives attribute information from the first target capability module of the first IoT device; The second IoT device sends a download request message to the first IoT device, the download request message including the identification information of the first target capability module; the second IoT device receives the first target capability module from the first IoT device; the first target capability module is one of a plurality of capability modules included in the first application; The second IoT device is equipped with the first target capability module.

13. The method according to claim 12, characterized in that, The method further includes: The second IoT device sends a first message to the first IoT device, the first message including the capability information of the second IoT device.

14. The method according to claim 13, characterized in that, Before the second IoT device sends the first message to the first IoT device, the method further includes: The second IoT device receives a query request message from the first IoT device, the query request message being used to query the capability information of the second IoT device.

15. The method according to claim 13, characterized in that, The second IoT device sends a first message to the first IoT device, including: When the second IoT device establishes a connection with the first IoT device, the second IoT device sends a first message to the first IoT device.

16. The method according to any one of claims 13-15, characterized in that, The capability information of the second IoT device includes one or more of the following: device type, device version, device level, device hardware capabilities, and CPU-ABI type.

17. The method according to claim 12, characterized in that, The second IoT device sends a download request message to the first IoT device, including: The second IoT device decides whether to install the first target capability module based on the attribute information of the first target capability module. When the second IoT device decides to install the first target capability module, the second IoT device sends the download request message to the first IoT device.

18. The method according to claim 17, characterized in that, The attribute information of the first target capability module includes one or more of the following: The first target capability module's capability name, version information, capability type, size of the first target capability module, number of times the first target capability module is used on the first IoT device, and permissions required by the first target capability module.

19. The method according to claim 17, characterized in that, The second IoT device includes preset decision conditions; The second IoT device decides whether to install the first target capability module based on the attribute information of the first target capability module, including: The second IoT device determines, based on the attribute information of the first target capability module, that the first target capability module meets the decision conditions, and then decides to install the first target capability module.

20. The method according to claim 19, characterized in that, The decision conditions include one or more of the following: The remaining storage space of the second IoT device is greater than the size of the first target capability module; the remaining battery power of the second IoT device is greater than the first threshold; the second IoT device is currently in a screen-off and charging state; the number of times the first target capability module has been used on the first IoT device is greater than the second threshold; and the permissions required by the first target capability module do not include sensitive permissions.

21. The method according to claim 19, characterized in that, The method further includes: The second IoT device modifies the decision conditions in response to the setting operation of the decision conditions.

22. The method according to any one of claims 12-15, characterized in that, The second IoT device is equipped with the first target capability module, including: The second IoT device displays a third interface, which includes installation prompts for the first target capability module; The second IoT device receives a third operation, which is the operation of selecting to install the first target capability module; In response to the third operation, the second IoT device installs the first target capability module.

23. A distributed operating system, characterized in that, include: A first IoT device and a second IoT device are connected; the first IoT device includes a first application, and the first application includes multiple capability modules that can be installed. The first IoT device determines a first target capability module suitable for installation on the second IoT device from among multiple capability modules included in the first application based on the capability information of the second IoT device, and sends the attribute information of the first target capability module to the second IoT device. The second IoT device receives the attribute information of the first target capability module and sends a download request message to the first IoT device according to the attribute information of the first target capability module. The download request message includes the identification information of the first target capability module. The first IoT device receives the download request message and sends the first target capability module to the second IoT device; The second IoT device receives and installs the first target capability module.

24. The system according to claim 23, characterized in that, Also includes: A third device, wherein the first IoT device is connected to the third device; The first IoT device determines a second target capability module suitable for installation on the third device from among the multiple capability modules included in the first application based on the capability information of the third device, and sends the second target capability module to the third device. The third device receives and installs the second target capability module.

25. An electronic device, characterized in that, include: processor; Memory; And a computer program; wherein the computer program is stored on the memory, and when the computer program is executed by the processor, causes the electronic device to perform the method as claimed in any one of claims 1-11, or the method as claimed in any one of claims 12-22.

26. A computer-readable storage medium comprising a computer program, characterized in that, When the computer program is run on an electronic device, it causes the electronic device to perform the method as described in any one of claims 1-11, or the method as described in any one of claims 12-22.

Citation Information

Patent Citations

  • Equipment matching method, equipment and system

    CN111756604A