Data processing network, data processing method and related equipment

Abstract

The embodiment of the invention provides a data processing network, a data processing method and related equipment. The data processing network, the data processing method and the related equipment are used for realizing computing power collaboration among different intelligent equipment. The data processing network provided by the embodiment of the invention comprises a computing power demand module, a computing power management module and at least one computing execution module. The computing power demand module is used for issuing an execution request of the target task. And the computing power management module is used for acquiring the resource condition of the at least one computing execution device, and allocating the sub-tasks in the target task to the at least one computing execution module for execution according to the resource condition of the at least one computing execution module. And the at least one calculation execution module is used for processing the subtasks distributed by the computing power management module and feeding back processing results of the subtasks to the computing power management module. And the computing power management module is also used for integrating the processing results of the subtasks into the processing result of the target task and feeding back the processing result of the target task to the computing power demand module.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of data processing, and in particular to a data processing network, a data processing method and related equipment. BACKGROUND

[0002] Smart home is a comprehensive use of Internet of Things, cloud computing, mobile Internet, big data and other technologies, which effectively combines smart control of home devices, home environment perception, family health perception, home security perception, and information exchange, consumption services and other home life, to create a healthy, safe, comfortable, low-carbon and convenient personalized home life.

[0003] In the smart home solution, some smart devices need to perform some tasks (such as identifying features from video and audio data). Performing tasks consumes the computing power of smart devices. With the upgrading of the smart home solution, the computing power consumption of tasks is increasing, and the current smart devices may not be able to bear the increasing computing power consumption.

[0004] One solution is to upgrade the hardware of smart devices to improve computing power, but the cost of hardware upgrade is high. Another solution is to upload tasks to the cloud, perform tasks through the computing power of the cloud, and return the processing result of the task to the smart device. However, this approach has the risk of data leakage (for example, video data is uploaded to the cloud for processing, and the video data may be leaked during transmission). SUMMARY

[0005] Embodiments of the present application provide a data processing network, a data processing method and related equipment, which are used to realize computing power collaboration between different smart devices and meet the diversified smart demands of smart home scenarios.

[0006] In a first aspect, embodiments of the present application provide a data processing network. The data processing network includes a computing power demand module, a computing power management module and at least one computing execution module. The computing power management module and the at least one computing execution module are deployed on different devices. The computing power demand module is configured to publish an execution request of a target task. The computing power management module is configured to obtain resource conditions of the at least one computing execution device, and distribute sub-tasks in the target task to the at least one computing execution module for execution according to the resource conditions of the at least one computing execution module. The at least one computing execution module is configured to process the sub-tasks distributed by the computing power management module, and feed back processing results of the sub-tasks to the computing power management module. The computing power management module is further configured to integrate the processing results of the sub-tasks into a processing result of the target task, and feed back the processing result of the target task to the computing power demand module.

[0007] In the embodiments of the present application, different computing execution modules (workers) with computing power resources can inform the computing power management module (master) of their resource conditions, and the computing power management module (master) can assign target tasks to the computing execution modules (workers) with matching resources for processing. This method provides a unified resource management and calling protocol for different computing execution devices (workers, i.e., devices with computing power resources), so that the computing power management module (master) can manage the computing power of different devices and share the computing power among different devices, and the computing power can be allocated to the computing power demand module (driver) in need. Thus, the computing power of different smart devices can be coordinated, and the diversified smart demands of the smart home scenario can be met.

[0008] In an optional implementation, the computing power demand module and the computing power management module are deployed on the first device, and the at least one computing execution module is deployed on the at least one second device; or the computing power management module is deployed on the first device, the computing power demand module is deployed on the third device, and the at least one computing execution module is deployed on the at least one second device.

[0009] In the embodiments of the present application, the computing power demand module and the computing power management module can be deployed on the same device or different devices, which improves the flexibility of the network architecture. The computing power management module is usually deployed on a device located at a core position in the home network. The computing power demand module can be deployed on the device at the core position or on a device at another position in the home network, so that the network provided by the embodiments of the present application can be included in each position in the home network, thereby completing the target tasks published in each position.

[0010] In an optional implementation, the computing power management module is further configured to send an execution state of the target task to the computing power demand module.

[0011] In the embodiments of the present application, the computing power management module master serves as the core of computing power resource allocation, and can determine the execution progress and execution state of the target task. After the computing power demand module driver publishes the target task to the computing power management module master, the computing power management module master informs the computing power demand module driver of the execution state of the target task, so that the computing power demand module driver can learn the execution state of the target task in time.

[0012] In an optional implementation, the execution state includes at least one of the following: success, failure, execution progress, and processing result.

[0013] In the embodiments of the present application, the execution state can reflect whether the target task is successful (success / failure) or reflect the execution progress of the target task. If the target task is completed, the execution state can include the processing result of the target task.

[0014] In an optional implementation, the computing power demand module is further configured to query the execution state of the target task from the computing power management module.

[0015] Optionally, the computing power management module master can also actively send the execution state of the target task to the computing power demand module driver, which is not limited in the present application.

[0016] In an optional implementation, the computing power management module is further configured to: send at least one configuration information to the at least one computing execution module; and the at least one computing execution module is further configured to: initialize according to the at least one configuration information.

[0017] In the embodiments of the present application, the initialization of the computing execution module is realized through the configuration information from the computing power management module. The initial state of the computing execution module can be aligned by the computing power management module and the computing execution module, and the reliability of the scheme is improved.

[0018] In an optional implementation, the at least one computing execution module is further configured to: send a keep-alive message to the computing power management module; and the computing power management module is further configured to: send a keep-alive response message to the at least one computing execution module.

[0019] In the embodiments of the present application, the link connection between the computing execution module and the computing power management module is ensured to be normal through the keep-alive message and the keep-alive response message.

[0020] In an optional implementation, the computing power management module is further configured to: query the current resource situation of the at least one computing execution module; and the at least one computing execution module is further configured to: reply the current resource situation to the computing power management module.

[0021] In the embodiments of the present application, the computing power management module can adaptively adjust the sub-tasks allocated to the execution module according to the current resource situation of the computing execution module, ensure the completion effect of the sub-tasks, and thus improve the completion effect of the target task.

[0022] In an optional implementation, the computing power management module is further configured to: send a deregistration instruction to a target computing execution module in the at least one computing execution module.

[0023] In the embodiments of the present application, if the computing power management module determines that the computing power of a certain computing execution module is not needed, or a certain computing execution module will be offline from the data processing network, the deregistration of the computing execution module can be realized through the deregistration instruction.

[0024] In an optional implementation, the resource condition includes at least one of the following: a central processing unit (CPU), a neural processing unit (NPU), a storage, and a double data rate synchronous dynamic random access memory (DDR) memory.

[0025] In a second aspect, the embodiments of the present application provide a data processing method. The method is applied to a first device (a master device deploying a computing power management module) in a network. The network further includes at least one second device (a worker device deploying a computing execution device). The method includes: receiving at least one first message from the at least one second device, the at least one first message corresponding to the at least one second device in one-to-one correspondence, the first message including a resource condition of the corresponding second device; obtaining an execution request of a target task; sending a second message to a target device in the at least one second device, the second message being used to instruct the target device to process a target subtask in the target task, the target subtask being allocated according to a resource of the target device; and receiving a reporting message from the target device, the reporting message including a processing result of the target subtask.

[0026] The data processing network and the data processing method provided by the embodiments of the present application are a low-cost computing power collaboration scheme. The scheme can not only meet the diversified intelligent demands of smart home scenarios, but also realize the interconnection and intercommunication of Internet of Things (IoT) devices (i.e., different smart devices) in a family, and improve the user experience.

[0027] The scheme does not need to upgrade hardware, and has low cost. Moreover, the scheme can allocate the target task to the FTTR network device (for example, an FTTR master device, a slave device, or a smart device, as the second device) to complete the target task in the internal network of the family. The scheme does not need to upload the information in the family to the cloud for processing, and can protect the privacy of the family and reduce the risk of data leakage.

[0028] In an optional implementation, the step of obtaining the execution request of the target task includes: receiving a third message from a third device (deploying a computing power demand module), the third message being used to request to process the target task. After receiving the reporting message from the target device, the method further includes: sending a fourth message to the third device, the fourth message including a processing result of the target task, the processing result of the target task being obtained by integrating the processing results of the subtasks reported by the different second devices.

[0029] In an optional implementation, after the second message is sent to the target device in the at least one second device, the method further includes: sending a task status to a third device, the task status being used to indicate an execution status of the target task.

[0030] In an optional implementation, the execution status includes at least one of the following: success, failure, execution progress, and processing result.

[0031] In an optional implementation, before the task status is sent to the third device, the method further includes: receiving a query request from the third device, the query request being used to query the execution status of the target task.

[0032] In an optional implementation, before the execution request of the target task is acquired after the at least one first message is received from the at least one second device, the method further includes: sending at least one configuration message to the at least one second device, the at least one configuration message corresponding to the at least one second device in a one-to-one manner, the configuration message including configuration information of the corresponding second device, and the configuration information being used to implement initialization of the second device.

[0033] In an optional implementation, the method further includes: receiving a keep-alive message from the at least one second device; and sending a keep-alive response message to the at least one second device.

[0034] In an optional implementation, the method further includes: sending a query message to the at least one second device, the query message being used to query a current resource situation of the second device; and receiving a query response message from the at least one second device, the query response message being used to indicate the current resource situation of the second device.

[0035] In an optional implementation, the method further includes: sending a deregistration instruction to a target device in the at least one second device.

[0036] In an optional implementation, the resource situation includes at least one of the following: CPU, NPU, storage, and DDR memory.

[0037] In a third aspect, an embodiment of the present application provides a data processing method. The method is applied to a second device (the second device deploys a computing execution device worker) in a network. The network further includes a first device (the first device deploys a computing power management module master). The method includes: sending a first message to the first device, the first message including a resource situation of the second device; receiving a second message from the first device, the second message being used to indicate that the second device processes a target subtask in a target task, the target subtask being allocated according to the resource of the second device; and sending a report message to the first device, the report message including a processing result of the target subtask.

[0038] In an optional implementation, after the first message is sent to the first device, the method further includes: receiving a configuration message from the first device, the configuration message including configuration information of the second device; and implementing initialization of the second device according to the configuration information.

[0039] In an optional implementation, the method further includes: sending a keep-alive message to the first device; and receiving a keep-alive response message from the first device.

[0040] In an optional implementation, the method further includes: receiving a query message from the first device, the query message being used to query a current resource situation of the second device; and sending a query response message to the first device, the query response message being used to indicate the current resource situation of the second device.

[0041] In an optional implementation, the method further includes: receiving a deregistration instruction from the first device.

[0042] In an optional implementation, the resource situation includes at least one of the following: CPU, NPU, storage, and DDR memory.

[0043] In a fourth aspect, an embodiment of the present application provides a data processing method. The method is applied to a third device (the third device is deployed with a computing power demand module driver) in a network. The network further includes a first device (the first device is deployed with a computing power management module master) and at least one second device (the second device is deployed with a computing execution device worker). The method includes: sending a third message to the first device, the third message being used to request processing of a target task; and receiving a fourth message from the first device, the fourth message including a processing result of the target task, the processing result of the target task being an integrated processing result of subtasks reported by different second devices, and the subtasks processed by the different second devices all being included in the target task.

[0044] In an optional implementation, after the third message is sent to the first device, the method further includes: receiving a task state from the first device, the task state being used to indicate an execution state of the target task.

[0045] In an optional implementation, the execution state includes at least one of the following: success, failure, execution progress, and processing result.

[0046] In an optional implementation, before the task state is received from the first device, the method further includes: sending a query request to the first device, the query request being used to query the execution state of the target task.

[0047] In a fifth aspect, an embodiment of the present application provides a first device. The first device is included in a network, and the network further includes at least one second device. The first device includes a sending unit and a receiving unit. The receiving unit is configured to receive at least one first message from the at least one second device, the at least one first message corresponding to the at least one second device in a one-to-one manner, and the first message including resource information of the corresponding second device; and obtain an execution request of a target task. The sending unit is configured to send a second message to a target device in the at least one second device, the second message being used to instruct the target device to process a target subtask in the target task, and the target subtask being allocated according to resource of the target device. The receiving unit is further configured to receive a reporting message from the target device, and the reporting message including a processing result of the target subtask.

[0048] In an optional implementation, the receiving unit is further configured to receive a third message from a third device (a computing power demand module driver), and the third message is used to request to process the target task. The sending unit is further configured to send a fourth message to the third device, and the fourth message including a processing result of the target task, the processing result of the target task being obtained by integrating processing results of subtasks reported by different second devices.

[0049] In an optional implementation, the sending unit is further configured to send a task state to the third device, and the task state is used to indicate an execution state of the target task.

[0050] In an optional implementation, the execution state includes at least one of the following: success, failure, execution progress, and processing result.

[0051] In an optional implementation, the receiving unit is further configured to receive a query request from the third device, and the query request is used to query the execution state of the target task.

[0052] In an optional implementation, the sending unit is further configured to send at least one configuration message to the at least one second device, the at least one configuration message corresponding to the at least one second device in a one-to-one manner, and the configuration message including configuration information of the corresponding second device, and the configuration information being used to implement initialization of the second device.

[0053] In an optional implementation, the receiving unit is further configured to receive a keep-alive message from the at least one second device. The sending unit is further configured to send a keep-alive response message to the at least one second device.

[0054] In an optional implementation, the sending unit is further configured to send a query message to the at least one second device, and the query message is used to query current resource information of the second device. The receiving unit is further configured to receive a query response message from the at least one second device, and the query response message is used to indicate the current resource information of the second device.

[0055] In an optional implementation, the sending unit is further configured to send a deregistration instruction to a target device in the at least one second device.

[0056] In an optional implementation, the resource condition includes at least one of the following: CPU, NPU, storage, and DDR memory.

[0057] In a sixth aspect, an embodiment of the present application provides a second device. The second device is included in a network, and the network further includes a first device. The second device includes a sending unit and a receiving unit. The sending unit is configured to send a first message to the first device, and the first message includes a resource condition of the second device. The receiving unit is configured to receive a second message from the first device, and the second message is used to instruct the second device to process a target subtask in a target task, and the target subtask is allocated according to the resource condition of the second device. The sending unit is further configured to send a reporting message to the first device, and the reporting message includes a processing result of the target subtask.

[0058] In an optional implementation, the receiving unit is further configured to receive a configuration message from the first device, and the configuration message includes configuration information of the second device; and the second device is initialized according to the configuration information.

[0059] In an optional implementation, the sending unit is further configured to send a keep-alive message to the first device. The receiving unit is further configured to receive a keep-alive response message from the first device.

[0060] In an optional implementation, the receiving unit is further configured to receive a query message from the first device, and the query message is used to query a current resource condition of the second device. The sending unit is further configured to send a query response message to the first device, and the query response message is used to indicate the current resource condition of the second device.

[0061] In an optional implementation, the receiving unit is further configured to receive a deregistration instruction from the first device.

[0062] In an optional implementation, the resource condition includes at least one of the following: CPU, NPU, storage, and DDR memory.

[0063] In a seventh aspect, an embodiment of the present application provides a third device. The third device is included in a network, and the network further includes a first device and at least one second device. The third device includes a sending unit and a receiving unit. The sending unit is configured to send a third message to the first device, and the third message is used to request processing of a target task. The receiving unit is configured to receive a fourth message from the first device, and the fourth message includes a processing result of the target task, and the processing result of the target task is an integrated processing result of subtasks reported by different second devices, and the subtasks processed by the different second devices are all included in the target task.

[0064] In an optional implementation, the receiving unit is further configured to receive a task status from the first device, the task status being used to indicate an execution status of the target task.

[0065] In an optional implementation, the execution status comprises at least one of the following: success, failure, execution progress, and processing result.

[0066] In an optional implementation, the sending unit is further configured to send a query request to the first device, the query request being used to query the execution status of the target task.

[0067] In an eighth aspect, an embodiment of the present application provides a smart device. The smart device comprises a processor and an interface circuit. Optionally, the smart device further comprises a memory. The processor is coupled with the memory and the interface circuit.

[0068] The interface circuit is configured to receive a signal from another device outside the smart device and transmit the signal to the processor, or send a signal from the processor to another device outside the smart device. The memory is configured to store a computer program or instructions.

[0069] When the processor executes the computer program or instructions, the communication device executes the method performed by the first device in the method embodiment.

[0070] Alternatively, when the processor executes the computer program or instructions, the communication device executes the method performed by the second device in the method embodiment.

[0071] Alternatively, when the processor executes the computer program or instructions, the communication device executes the method performed by the third device in the method embodiment.

[0072] In a ninth aspect, an embodiment of the present application provides a computer readable storage medium. The computer readable storage medium stores a program. When a computer executes the program, the computer executes the method in the second aspect or any possible implementation manner of the second aspect, the third aspect or any possible implementation manner of the third aspect, the fourth aspect or any possible implementation manner of the fourth aspect.

[0073] In a tenth aspect, an embodiment of the present application provides a computer program product. When the computer program product is executed on a computer, the computer executes the method in the second aspect or any possible implementation manner of the second aspect, the third aspect or any possible implementation manner of the third aspect, the fourth aspect or any possible implementation manner of the fourth aspect.

[0074] The beneficial effects of the third aspect to the tenth aspect are the same as those of the first aspect to the second aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0075] Figure 1 An architecture schematic diagram of a data processing network provided by an embodiment of the present application is shown in FIG. 1.

[0076] Figure 2 An architecture schematic diagram of a distributed computing power base provided by an embodiment of the present application is shown in FIG. 2.

[0077] Figure 3 A connection relationship schematic diagram of a data processing network provided by an embodiment of the present application is shown in FIG. 3.

[0078] Figure 4 A protocol interface schematic diagram of a data processing network provided by an embodiment of the present application is shown in FIG. 4.

[0079] Figure 5 A flow schematic diagram of a data processing method provided by an embodiment of the present application is shown in FIG. 5.

[0080] Figure 6a An architecture schematic diagram of a data processing network provided by an embodiment of the present application is shown in FIG. 6.

[0081] Figure 6b Another architecture schematic diagram of a data processing network provided by an embodiment of the present application is shown in FIG. 7.

[0082] Figure 7 A flow schematic diagram of a computing power management stage of a data processing method provided by an embodiment of the present application is shown in FIG. 8.

[0083] Figure 8 A flow schematic diagram of a computing power distribution stage of a data processing method provided by an embodiment of the present application is shown in FIG. 9.

[0084] Figure 9 A structure schematic diagram of an intelligent device provided by an embodiment of the present application is shown in FIG. 10.

[0085] Figure 10 A structure schematic diagram of a first device provided by an embodiment of the present application is shown in FIG. 11.

[0086] Figure 11 A structure schematic diagram of a second device provided by an embodiment of the present application is shown in FIG. 12.

[0087] Figure 12 A structure schematic diagram of a third device provided by an embodiment of the present application is shown in FIG. 13. DETAILED DESCRIPTION

[0088] The embodiments of the present application are described below with reference to the accompanying drawings. It is known to those skilled in the art that the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems as technology develops and new scenarios appear.

[0089] The terms "first", "second", and the like in the description and in the claims of the present application and above-described drawings are used to distinguish similar objects and are not necessarily used to describe a specific sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances and that the embodiments of the present application are capable of functioning in other sequences than described or illustrated herein. Moreover, the terms "comprise", "have" and any variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of elements is not necessarily limited to those elements, but can include other elements not expressly listed or inherent to such process, method, system, article, or apparatus. Additionally, "at least one" means one or more, and "multiple" means two or more. The term "and / or" describes an association between associated objects, which means that there can be three kinds of relationships, for example, A and / or B, which means that A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects. "At least one of" or similar expressions means any combination of the items, including single or multiple combinations. For example, at least one of a, b, or c means a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be singular or plural.

[0090] In the field of smart home, smart devices are used to perform smart tasks. For example, a smart camera can perform the task of identifying features such as people, pets, etc. from video data, a smart light can perform the task of automatically turning on according to room brightness and time, etc.

[0091] With the upgrading of the smart home solution, the computing power consumption of the tasks performed by the smart devices is increasing, and the current smart devices may not be able to bear the increasing computing power consumption.

[0092] For example, a smart speaker is originally designed to implement smart conversation with a user. With the upgrading of the smart home solution, the smart speaker is required to implement voiceprint recognition for different users, and to adopt different conversation modes for different users (for example, an elderly conversation mode for elderly users, and a child conversation mode for children). Because the computing power consumption required by voiceprint recognition is large, the current computing power of the smart speaker cannot support voiceprint recognition, and the upgrading solution cannot be applied to the smart speaker.

[0093] There are mainly two kinds of current solutions, one is to upgrade the hardware, and update the smart device. However, the cost of hardware upgrade is high. The other idea is to upload the task to the cloud for execution, but there is a risk of information leakage in the process of uploading the task to the cloud.

[0094] For example, a smart speaker uploads voice data of a user to the cloud for voiceprint recognition, and the cloud feeds back the recognition result to the smart device. During the transmission of voice data from the smart speaker to the cloud, the voice data is at risk of leakage.

[0095] To solve the above problems, the embodiments of the present application provide a data processing network, a data processing method and related equipment. The data processing network provided by the embodiments of the present application provides a unified resource management and calling protocol for different smart devices, thereby realizing collaborative management and calling of computing power among different smart devices.

[0096] As shown in Figure 1 The data processing network provided by the embodiments of the present application includes a computing power demand module driver, a computing power management module master and at least one computing execution module worker.

[0097] Among them, the network has and only has one computing power management module master, the number of computing power demand modules driver in the network can be multiple, and the number of computing execution modules worker can also be multiple.

[0098] In an optional implementation, the computing power management module master and the computing execution module worker are deployed on different devices. The computing power demand module driver and the computing power management module master can be deployed on the same device, or can be deployed on different devices.

[0099] Optionally, the computing power management module master and the computing execution module worker can also be deployed on the same device, which is not limited by the present application.

[0100] In an example, the computing power management module master can be deployed on a fiber to the room (FTTR) master device, such as a main FTTR unit (MFU), an access controller (AC). With the core position of the FTTR master device in the smart home, the collaborative management and calling of computing power of each smart device in the smart home scene are realized.

[0101] The computing power demand module driver can be deployed on any smart device, FTTR master device or FTTR slave device (such as sub FTTR unit (SFU), access point (AP), etc.). The computing execution module worker can be deployed on any device with computing power resources, such as a smart device, an FTTR master device or an FTTR slave device, which is not limited by the present application.

[0102] In the embodiments of the present application, the computing power management module master has the functions of computing power management and computing power allocation. The computing power management refers to the management of the computing power resources of the plurality of computing execution modules worker in the network; the computing power allocation refers to the allocation of the tasks of the computing power management module master to one or more computing execution modules worker for execution.

[0103] Specifically, the computing power management module master can obtain the resource conditions of the at least one computing execution device worker, thereby realizing the centralized management of the computing power resources of the plurality of computing execution modules worker.

[0104] If a certain intelligent device in the network obtains the execution instruction of the target task, the computing power demand module driver deployed on the intelligent device can send the execution request of the target task to the computing power management module master. The computing power management module master can allocate the subtasks in the target task to the at least one computing execution module worker for execution according to the resource conditions of the at least one computing execution module worker. The at least one computing execution module worker can process the subtasks allocated by the computing power management module master and feed back the processing results of the subtasks to the computing power management module master. The computing power management module master integrates the processing results of the subtasks into the processing result of the target task and feeds back the processing result of the target task to the computing power demand module driver. Thus, the allocation of the computing power resources among the intelligent devices is realized.

[0105] In the embodiments of the present application, the resource conditions include at least one of the following: central processing unit CPU, neural network processing unit NPU, storage, double data rate synchronous dynamic random access memory DDR memory.

[0106] In Figure 1 In the network shown, the number of computing power management modules master is usually one, and is usually deployed at the core position in the home network (for example, on the FTTR master device of the FTTR network). The network can include one or more computing power demand modules driver and one or more computing execution modules worker. The computing power demand module driver can be deployed on the same device as the computing power management module master, or can be deployed on different devices. The computing execution module worker can be deployed on the same device as the computing power management module master, or can be deployed on different devices.

[0107] In the embodiments of the present application, the data processing network is also called distributed computing power (cooperative) base. As shown in Figure 2As shown, the upper-layer services such as intelligent storage, intelligent sensing, intelligent interaction, etc. can be implemented through the distributed computing power base. Specifically, the driver is used to run the above-mentioned services to generate corresponding target tasks. The distributed computing power base includes an FTTR master device (i.e. the master FTTR in Figure 2 ), an FTTR slave device (i.e. the slave FTTR in Figure 2 ), and a camera and other smart devices.

[0108] The master can be deployed on the master FTTR device to manage the computing power of each device in the distributed computing power base, i.e. to manage the computing power of the FTTR master device, the FTTR slave device, and the camera and other smart devices. If the upper-layer application issues a target task (i.e. the driver issues a target task), the master on the master FTTR device can aggregate the computing power of the FTTR master device, the FTTR slave device, and the third-party device (smart device, etc.) for use by the service layer.

[0109] Optionally, the service layer can include FTTR self-service, such as FTTR-NAS home user, and third-party device applications, such as home camera.

[0110] Embodiments of the present application also provide a unified protocol interface for each device in the distributed computing power base. As shown in Figure 3 , the driver provides an application programming interface (API) for the application layer, and the application layer submits a computing task to the Manger through the interface. The manger is responsible for managing all devices under the distributed computing power base, such as cameras, set-top boxes, etc. The driver publishes a target task to the manger through the protocol interface, and the manger distributes the target sub-task to the Worker device for execution through the protocol interface. The Worker executes the target sub-task issued by the Manger and feeds back the processing result of the target sub-task to the Manger through the protocol interface.

[0111] It is worth noting that the protocol interface between the above-mentioned driver and the manger, and the protocol interface between the manger and the worker, can be a message that sends specific content, such as the first message, the second message, etc. in the following.

[0112] It is worth noting that the protocol interface between the above-mentioned driver and the manger, and the protocol interface between the manger and the worker, are decoupled from the network layer, the transport layer, and the link layer protocol, and can adapt to multiple networking scenarios. For example, it can be connected with a remote control through the Bluetooth protocol as shown in Figure 4 , or connected with a camera through Wi-Fi.

[0113] Optionally, the driver can also send the execution status of the target task to the master through the protocol interface. Before this, the driver can query the execution status of the target task from the master. The execution status can include at least one of the following: success, failure, execution progress, and processing result.

[0114] Optionally, the master can also actively send the execution status of the target task to the driver, which is not limited in the present application.

[0115] Optionally, the master can also send at least one configuration information to at least one worker through the protocol interface; at least one worker can initialize according to at least one configuration information. Thus, the state alignment between master and worker is realized.

[0116] Optionally, at least one worker can also send a keep-alive message to the computing power management module, and the master sends a keep-alive response message to at least one worker. Thus, the link connection between master and worker is ensured to be normal.

[0117] Optionally, the master can also query the current resource situation of at least one worker through the protocol interface, and at least one worker returns the current resource situation to the master. In order to adaptively adjust the sub-tasks allocated to the worker according to the current resource situation of the worker, the completion effect of the sub-tasks is ensured, and the completion effect of the target task is improved.

[0118] Optionally, the master can also send a deregistration instruction to a target worker in at least one worker. Thus, the deregistration of the target worker in the network is realized.

[0119] Based on the network shown in Figures 1 to 3 The embodiment of the present application provides a computing power resource processing method, as shown in Figure 5 The method comprises the following steps:

[0120] 501. At least one second device sends a first message to the first device, and the first message includes the resource situation of the corresponding second device.

[0121] In the embodiment of the present application, the first device is a device in which the master is deployed. Optionally, the first device can be an FTTR master device, so that the master is in the core position of the home network.

[0122] The network comprises at least one worker, and the at least one worker can be deployed on different second devices. Optionally, the second device can be a smart device, an FTTR slave device, an FTTR master device, etc., and the present application does not limit this.

[0123] The second device can send a first message to the first device, and the first message is used to indicate the resource situation of the worker deployed on the second device.

[0124] After the first device obtains the resource situation of each worker through the first message, the first device can record the resource situation of each worker, and in the case of needing to execute a task, the first device can allocate sub-tasks to each worker according to the resource situation of each worker.

[0125] It is worth noting that in addition to the FTTR master device, the first device can also be other types of devices, such as a smart device such as a smart speaker, or an FTTR slave device, etc., and the present application does not limit this.

[0126] 502, the first device obtains an execution request of a target task.

[0127] Optionally, in addition to the master, the first device can also deploy a driver. For example Figure 6a As shown in the figure, the first device (FTTR master device) deploys a master, a driver and a worker. When the driver wants to execute a target task, the driver sends an execution request of the target task to the master, and the first device can obtain the execution request of the target task.

[0128] Optionally, if the master that publishes the target task is deployed on a third device outside the first device, the third device can send a third message to the first device. The third message is used to request to process the target task. For example Figure 6b As shown in the figure, the third device is a camera, the driver is deployed on the camera, the master is deployed on the FTTR master device, and the worker is deployed on the camera, the FTTR master device and the FTTR slave device.

[0129] 503, the first device sends a second message to a target device in the at least one second device, and the second message is used to instruct the target device to process a target sub-task in the target task, and the target sub-task is allocated according to the resource of the target computing device.

[0130] The first device can divide the target task into one or more target sub-tasks, and allocate the sub-tasks to appropriate workers for execution according to the resource situation of each worker.

[0131] Specifically, the first device divides the target task into target sub-tasks, determines workers from the plurality of workers for executing the target sub-tasks, and sends a second message to the workers for executing the target sub-tasks. The second message is used to instruct the second device receiving the second message to execute the corresponding target sub-task.

[0132] 504、The target device sends a reporting message to the first device, and the reporting message includes a processing result of the target sub-task.

[0133] The worker (located on the target device) assigned to the target sub-task executes the target sub-task, and then delivers the processing result of the target sub-task to the first device through the reporting message. The master in the first device can integrate the processing result of the target sub-task into a processing result of the target task, and feed back the processing result of the target task to the driver.

[0134] Optionally, if the master publishing the target task is deployed on a third device outside the first device, the first device can send a fourth message to the third device. The fourth message includes the processing result of the target task.

[0135] In the embodiment of the present application, different workers (deployed on the second device) with computing power resources can inform the master (deployed on the first device) of their resource conditions through the first message, and the master (the first device) can assign the target task to the resource-matched worker (the second device) for processing. This method provides a unified resource management and calling protocol for different computing execution devices (workers, i.e., devices with computing power resources), so that the master can manage the computing power of different devices, while realizing the sharing of computing power among different devices, and allocating the computing power to the driver device in need. Thus, the computing power of different smart devices is coordinated to meet the diversified smart demands of the smart home scene.

[0136] The data processing network and the data processing method provided in the embodiments of the present application are a low-cost computing power coordination scheme. They can not only meet the diversified smart demands of the smart home scene, but also realize the interconnection and intercommunication of the Internet of Things (IoT) devices (i.e., different smart devices) in the home, and improve the user experience.

[0137] This scheme does not need to upgrade the hardware, and has low cost. Moreover, the scheme assigns the target task to the FTTR network device (such as the FTTR master device, the slave device or the smart device) for completion, and the target task can be completed in the home internal network. The information in the home does not need to be uploaded to the cloud for processing, which can protect the privacy of the home and reduce the risk of data leakage.

[0138] In the embodiments of the present application, in order to distribute and execute the target task in the home network, two stages of power management and power distribution need to be experienced, which will be described respectively as follows:

[0139] I. Power management stage

[0140] As shown in Figure 7 , the power management stage includes:

[0141] 701. The worker sends a first message to the master to report the resource situation.

[0142] The power management stage mainly includes the corresponding process of the worker and the master. For the convenience of description, the FTTR master device and the slave device (such as SFU or AP) are taken as examples of the first device and the second device in the embodiments of the present application. That is, the master is deployed on the FTTR master device, and the worker is deployed on the FTTR slave device.

[0143] In the initialization stage, the worker (deployed on the FTTR slave device, i.e., the second device) can send a first message to the master (deployed on the FTTR master device, i.e., the first device) to register the power resource of the FTTR slave device to the FTTR master device through the first message.

[0144] Optionally, the first message can include which power (such as: central processing unit CPU / network processing unit NPU / codec, etc.) the FTTR slave device has, and can also include the size of the power.

[0145] Optionally, the first message can be a Register frame or other types of messages, which are not limited in the present application.

[0146] 702. The master issues an identifier of the worker.

[0147] After the FTTR master device receives the first message from the FTTR slave device, it can allocate an identifier to the FTTR slave device, which is used to indicate different workers in the network.

[0148] Optionally, the identifier can be an Agent ID. The FTTR master device can notify the FTTR slave device of the identifier through a Register Ack frame.

[0149] 703. The master sends a configuration message to the worker, and the configuration message includes the configuration information of the worker.

[0150] The FTTR master device can send a configuration message to the FTTR slave device, and the configuration message includes the configuration information of the FTTR slave device, which is used to implement the initialization of the FTTR slave device.

[0151] Optionally, the configuration information can include the number of computing instances of the FTTR slave device, the keep-alive period, etc.

[0152] Optionally, the configuration message can be an Agent Config frame.

[0153] 704. The worker sends a response message to the master.

[0154] After receiving the configuration message from the FTTR master device, the FTTR slave device initializes its related functions according to the configuration information and sends a response message to the FTTR master device. Optionally, the response message can be an Agent Config Ack frame.

[0155] Through the above steps, the FTTR master device has completed the management of the computing power of the FTTR slave device. That is, the computing power management module master obtains the resource situation of at least one computing execution device worker, and can realize centralized management of the computing power resources of multiple computing execution modules workers.

[0156] Optionally, the third-party device such as a home set-top box or a smart TV can also access the data processing network (also referred to as a distributed computing power base) provided by the embodiments of the present application based on the above interaction process.

[0157] 705. The worker sends a keep-alive message to the master.

[0158] The FTTR slave device can send a keep-alive message (Keep Live message) to the FTTR master device according to the keep-alive period.

[0159] 706. The master replies to the worker with a keep-alive response message.

[0160] After receiving the keep-alive message, the FTTR master device sends a keep-alive response message (Keep Live Ack message) to the FTTR slave device to ensure that the link connection between the master FTTR device and the slave FTTR device is normal.

[0161] 707. The master sends a query message to the worker.

[0162] After the computing power is managed, the FTTR master device can send a query message to the FTTR slave device, and the query message is used to query the current resource situation of the second device. Optionally, the query message can be a Query frame, which is used to query the current remaining computing power resource situation of the worker.

[0163] 708. The worker sends a query response message to the master.

[0164] The FTTR slave device sends a query response message to the FTTR master device, and feeds back the current resource situation of the FTTR slave device to the FTTR master device.

[0165] 709、The master sends a deregistration message to the worker.

[0166] After the computing power is managed, the FTTR master device can select to remove a certain FTTR slave device in the network from the distributed computing power base according to the networking situation. Therefore, the FTTR master device sends a deregistration message to the FTTR slave device to be removed. Optionally, the deregistration message can be an UnRegister frame.

[0167] Optionally, the deregistration message can include the Agent ID of the FTTR slave device to be removed from the distributed computing power base, so that the FTTR slave device with the Agent ID determines the deregistration.

[0168] 710、The worker sends a deregistration response message to the master.

[0169] After the deregistration is completed, the FTTR slave device sends a deregistration response message to the FTTR master device.

[0170] In the embodiments of the present application, the IOT device can access the FTTR distributed computing power base based on the above protocol process, and realize the centralized management of computing power resources.

[0171] II. Computing power allocation phase.

[0172] As shown in Figure 8 , the computing power allocation phase includes:

[0173] 801、The driver sends a third message to the master.

[0174] Taking a network attached storage (NAS) scenario as an example, when a user uploads a photo to the FTTR-NAS, the NAS smart album application (driver) can send a third message to the FTTR master device, and the third message is used to request processing of a target task (such as a task of classifying images).

[0175] Optionally, the third message can be a Job Commit frame.

[0176] 802、The master sends a response message of the third message to the driver.

[0177] The FTTR master device responds to the NAS smart album application with a Job Commit Ack frame.

[0178] 803、master sends a second message to the worker.

[0179] The master obtains the computing power resource conditions of each worker in the computing power management stage. Therefore, the master can allocate a subtask in the target task to at least one worker (referred to as a target device) for execution according to the resource conditions of the at least one computing execution module worker, and send a second message to the target device. The second message is used to instruct the target device to process a target subtask in the target task, and the target subtask is allocated according to the resource of the target device.

[0180] Optionally, the second message can be a Job Dispatch frame.

[0181] 804、worker sends a response message of the second message to the master.

[0182] The worker module gives a response to the master module through a Job Dispatch Ack frame after receiving the computing task, and starts the computing task to execute the allocated target subtask.

[0183] 805、worker sends a keep-alive message to the master.

[0184] During the execution of the target subtask, the worker sends a keep-alive message (for example, a Keep Live frame) to the master to maintain the heart beat.

[0185] Optionally, the worker can report the status of the target subtask in real time through the heart beat frame until the completion of the computing.

[0186] 806、master sends a keep-alive response message to the worker.

[0187] Optionally, the keep-alive response message can be a Keep Live Ack frame.

[0188] 807、master sends a fourth message to the driver.

[0189] After the master detects that the target subtask is executed, the master integrates the processing results of the subtasks reported by different second devices (workers) into the processing result of the target task, and reports the processing result of the target task to the NAS intelligent album application through a fourth message.

[0190] Optionally, the fourth message can be a Job Complete frame.

[0191] 808、driver sends a query request to the master.

[0192] During the execution of the target task, the NAS smart album application (driver) can also send a query request (for example, a Query command) to the master. The query request is used to query the execution status of the target task.

[0193] 809、The master sends a task status to the driver.

[0194] The master sends the execution status of the target task to the driver task status.

[0195] Optionally, the execution status includes at least one of the following: success, failure, execution progress, and processing result.

[0196] 810、The driver sends a termination instruction to the master.

[0197] If the driver wants to terminate the execution of the target task, it can send a termination instruction (for example, a JobStop command) to the master.

[0198] 811、The master sends a termination instruction to the driver.

[0199] The master sends a termination instruction (for example, a Job Stop command) to the driver (target device) that executes the target subtask.

[0200] 812、The driver sends a termination response (for example, a Job Stop Ack) to the master.

[0201] After receiving the termination instruction, the driver sends a termination response to the master and terminates the execution of the target subtask.

[0202] 813、The master sends a termination response to the driver.

[0203] After receiving the termination response from the target device, the master sends a termination response (for example, a JobStop Ack) to the driver.

[0204] In the embodiments of the present application, by allocating computing power, computing power is allocated to the driver device that needs it. Thus, the computing power of different smart devices is coordinated to meet the diversified smart demands of the smart home scenario.

[0205] The above describes the computing power resource processing method provided by the embodiments of the present application, and the following describes a device for implementing the method:

[0206] The embodiments of the present application also provide a smart device. As Figure 9As shown, the smart device 900 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It can be understood that the interface circuit 920 can be a transceiver or an input / output interface.

[0207] Optionally, the smart device 900 can further include a memory 930 for storing instructions executed by the processor 910 or storing input data required by the processor 910 to run instructions or storing data generated after the processor 910 runs instructions.

[0208] When the above smart device 900 is a first device in the embodiments shown in Figures 5 to 8 or a chip applied to the first device, the smart device 900 implements the functions of the first device in the above method embodiments.

[0209] When the above smart device 900 is a second device in the embodiments shown in Figures 5 to 8 or a chip applied to the second device, the smart device 900 implements the functions of the second device in the above method embodiments.

[0210] When the above smart device 900 is a third device in the embodiments shown in Figures 5 to 8 or a chip applied to the third device, the smart device 900 implements the functions of the third device in the above method embodiments.

[0211] Optionally, the smart device 900 can be an FTTR master device, an FTTR slave device, or a smart camera, a smart door lock, etc. The present application does not limit this.

[0212] The embodiments of the present application provide a first device, as shown in Figure 10 The first device 1000 includes a sending unit 1010 and a receiving unit 1020.

[0213] The receiving unit 1020 is configured to receive at least one first message from at least one second device, the at least one first message corresponding to the at least one second device in a one-to-one manner, the first message including resource conditions of the corresponding second device; and obtain an execution request of a target task.

[0214] The sending unit 1010 is configured to send a second message to a target device in the at least one second device, the second message being used to instruct the target device to process a target subtask in the target task, the target subtask being allocated according to resources of the target device.

[0215] The receiving unit 1020 is further configured to receive a reporting message from the target device, the reporting message including a processing result of the target subtask.

[0216] The first device 1000 is configured to implement Figures 5 to 8The computing resource processing method shown in any of the embodiments.

[0217] The second device provided in the embodiments of the present application comprises Figure 11 The second device 1100 shown in the figure comprises a sending unit 1110 and a receiving unit 1120.

[0218] The sending unit 1110 is configured to send a first message to the first device, and the first message comprises resource conditions of the second device.

[0219] The receiving unit 1120 is configured to receive a second message from the first device, and the second message is used to indicate a target subtask in a target task, and the target subtask is allocated according to the resource conditions of the second device.

[0220] The sending unit 1110 is further configured to send a reporting message to the first device, and the reporting message comprises a processing result of the target subtask.

[0221] The second device 1100 is configured to implement the computing resource processing method shown in any of the embodiments. Figures 5 to 8

[0222] The third device provided in the embodiments of the present application comprises Figure 12 The third device 1200 shown in the figure comprises a sending unit 1210 and a receiving unit 1220.

[0223] The sending unit 1210 is configured to send a third message to the first device, and the third message is used to request processing of a target task.

[0224] The receiving unit 1220 is configured to receive a fourth message from the first device, and the fourth message comprises a processing result of the target task, and the processing result of the target task is an integrated processing result of subtasks reported by different second devices, and the subtasks processed by the different second devices are all included in the target task.

[0225] The third device 1200 is configured to implement the computing resource processing method shown in any of the embodiments. Figures 5 to 8

[0226] The computer readable storage medium provided in the embodiments of the present application comprises a program, and when a computer executes the program, the method shown in any of the embodiments is executed. Figures 5 to 8

[0227] The computer readable storage medium can be a U disk, a mobile hard disk, a floppy disk, an optical disk, a memory card or other types of storage medium, and the present application does not limit the computer readable storage medium.

[0228] The computer program product provided in the embodiments of the present application comprises a program, and when the computer program product is executed on a computer, the computer executes the method shown in any of the embodiments.​​​Figures 5 to 8 The method shown in any one of the embodiments.

[0229] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0230] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0231] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0232] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0233] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Claims

1. A data processing network, characterized by Comprising: a computing power demand module, a computing power management module, and at least one computing execution module, the computing power management module and the at least one computing execution module being deployed on different devices; the computing power demand module is configured to issue an execution request of a target task; the computing power management module is configured to obtain resource conditions of the at least one computing execution device, and distribute sub-tasks in the target task to the at least one computing execution module for execution according to the resource conditions of the at least one computing execution module; the at least one computing execution module is configured to process the sub-tasks distributed by the computing power management module, and feed back processing results of the sub-tasks to the computing power management module; the computing power management module is further configured to integrate the processing results of the sub-tasks into a processing result of the target task, and feed back the processing result of the target task to the computing power demand module.

2. The network of claim 1, wherein: the computing power demand module and the computing power management module are both deployed on a first device, and the at least one computing execution module is deployed on at least one second device; or the computing power management module is deployed on a first device, the computing power demand module is deployed on a third device, and the at least one computing execution module is deployed on at least one second device.

3. The network of claim 1 or 2, wherein, the computing power management module is further configured to: send an execution status of the target task to the computing power demand module.

4. The network of claim 3, wherein, The execution status includes at least one of: success, failure, execution progress, and processing result.

5. The network of claim 3 or 4, wherein, the computing power demand module is further configured to: query the execution status of the target task from the computing power management module.

6. The network of any one of claims 1 to 5, wherein: the computing power management module is further configured to send at least one configuration information to the at least one computing execution module; the at least one computing execution module is further configured to initialize according to the at least one configuration information.

7. The network of any one of claims 1 to 6, characterized in that; the at least one computing execution module is further configured to send a keep-alive message to the computing power management module; the computing power management module is further configured to send a keep-alive response message to the at least one computing execution module.

8. The network of any one of claims 1 to 7, wherein: the computing power management module is further configured to query current resource conditions from the at least one computing execution module; the at least one computing execution module is further configured to reply the current resource conditions to the computing power management module.

9. The network of any one of claims 1 to 8, wherein: the computing power management module is further configured to send a deregistration instruction to a target computing execution module in the at least one computing execution module.

10. A data processing method, characterized by, A first device applied to a network, the network further comprising at least one second device, the method comprising: receiving at least one first message from the at least one second device, the at least one first message corresponding to the at least one second device one by one, the first message comprising resource conditions of the corresponding second device; obtaining an execution request of a target task; sending a second message to a target device of the at least one second device, the second message being used to instruct the target device to process a target subtask of the target task, the target subtask being allocated according to resources of the target device; receiving a report message from the target device, the report message including a processing result of the target subtask.

11. The method of claim 10, wherein, The method further includes: receiving a third message from a third device, the third message being used to request to process the target task; after the receiving the report message from the target device, the method further includes: sending a fourth message to the third device, the fourth message including the processing result of the target task, the processing result of the target task being obtained by integrating processing results of subtasks reported by different second devices.

12. The method of claim 11, wherein, after the sending the second message to the target device of the at least one second device, the method further includes: sending a task status to the third device, the task status being used to indicate an execution status of the target task.

13. The method of claim 12, wherein, before the sending the task status to the third device, the method further includes: receiving a query request from the third device, the query request being used to query the execution status of the target task.

14. The method according to any one of claims 10 to 13, characterized in that, before the acquiring the execution request of the target task, the method further includes: sending at least one configuration message to the at least one second device, the at least one configuration message corresponding to the at least one second device one by one, the configuration message including configuration information of the corresponding second device, the configuration information being used to implement initialization of the second device.

15. The method according to any one of claims 10 to 14, characterized in that, The method further includes: receiving a keep-alive message from the at least one second device; sending a keep-alive response message to the at least one second device.

16. The method according to any one of claims 10 to 15, characterized in that, The method further includes: sending a query message to the at least one second device, the query message being used to query current resource conditions of the second device; receiving a query response message from the at least one second device, the query response message being used to indicate the current resource conditions of the second device.

17. The method according to any one of claims 10 to 16, characterized in that, The method further includes: sending a deregistration instruction to a target device of the at least one second device.

18. A data processing method, characterized by, The method is applied to a second device in a network, the network further including a first device, and the method includes: sending a first message to the first device, the first message including resource conditions of the second device; receiving a second message from the first device, the second message being used to instruct the second device to process a target subtask of a target task, the target subtask being allocated according to resources of the second device; sending a report message to the first device, the report message including a processing result of the target subtask.

19. The method of claim 18, wherein, after the sending the first message to the first device, the method further includes: receiving a configuration message from the first device, the configuration message including configuration information of the second device; implementing initialization of the second device according to the configuration information.

20. The method of claim 18 or 19, wherein, The method further includes: sending a keep-alive message to the first device; receiving a keep-alive response message from the first device.

21. The method of any one of claims 18-20, wherein, The method further includes: receiving a query message from the first device, the query message being used to query the current resource condition of the second device; sending a query response message to the first device, the query response message being used to indicate the current resource condition of the second device.

22. The method of any one of claims 18-21, wherein, The method further includes: receiving a deregistration instruction from the first device.

23. A data processing method, characterized by, The method is applied to a third device in a network, the network further including a first device and at least one second device, and the method includes: sending a third message to the first device, the third message being used to request processing of a target task; receiving a fourth message from the first device, the fourth message including a processing result of the target task, the processing result of the target task being obtained by integrating processing results of subtasks reported by different second devices, and the subtasks processed by the different second devices being all included in the target task.

24. The method of claim 23, wherein, After the sending of the third message to the first device, the method further includes: receiving a task state from the first device, the task state being used to indicate an execution state of the target task.

25. The method of claim 24, wherein, Before the receiving of the task state from the first device, the method further includes: sending a query request to the first device, the query request being used to query the execution state of the target task.

26. A smart device, comprising: The processor and the interface circuit are coupled with each other; The interface circuit is configured to receive a signal from another device other than the smart device and transmit the signal to the processor, or send a signal from the processor to the another device other than the smart device; The processor is configured to execute the method in any one of claims 10-17 or 18-22 or 23-25.

27. A computer readable storage medium, characterized in that, The computer readable storage medium stores a program, and when the computer executes the program, the method in any one of claims 10-17 or 18-22 or 23-25 is executed.

28. A computer program product, characterised in that, When the computer program product is executed on the computer, the computer executes the method in any one of claims 10-17 or 18-22 or 23-25.

Images