Task processing method and device of multi-cloud domain, electronic equipment and storage medium

Abstract

The present disclosure relates to a multi-cloud domain task processing method and device, electronic equipment and storage medium, and relates to the technical field of cloud services. The present disclosure solves the problem that the service range of a cloud domain is limited by the resources included in the cloud domain, resulting in a small service range of the cloud domain and poor user experience. The method comprises the following steps: determining a second cloud domain from a plurality of cloud domains according to a target task and resource information corresponding to each cloud domain in the plurality of cloud domains, the resources of the second cloud domain including target resources for implementing the target task; the resource information of different cloud domains corresponds to different resources; sending a task execution request to a collaborative service platform of the second cloud domain, the task execution request being used to request the collaborative service platform of the second cloud domain to execute the target task based on the target resources; and receiving an execution result of the target task returned by the collaborative service platform of the second cloud domain, the execution result being sent in the case that the collaborative service platform of the second cloud domain accepts the task execution request.

Description

Technical Field

[0001] This disclosure relates to the field of cloud service technology, and in particular to multi-cloud domain task processing methods, apparatus, electronic devices and storage media. Background Technology

[0002] Cloud services are a service model that provides dynamically scalable virtualized resources via the internet. Cloud services offer advantages such as low cost, high reliability, high scalability, high automation, and virtualization. Therefore, cloud service technology has been widely used by individuals and businesses for resource storage and processing across networks such as the internet.

[0003] In the cloud service system of a network monitoring system, data acquisition devices (such as image acquisition devices or radar) send the acquired data resources to the cloud domain storage to which the data acquisition devices belong. Simultaneously, the cloud server in this cloud domain can process the acquired data resources to provide corresponding services. For example, when a client in this cloud domain needs to access the acquired data resources, the client directly retrieves the data resources from its own cloud domain and displays them to the client user. Alternatively, when the client needs to process the acquired data resources, the cloud server in this cloud domain will directly process the data resources and provide the processing results to the client user.

[0004] However, in the aforementioned technologies, cloud domain users can only access resources within the cloud domain to which the client belongs, and cannot access resources in other cloud domains. This limits the service scope of the cloud domain and fails to meet the growing service demands of users, significantly reducing the user experience when using the cloud domain. Summary of the Invention

[0005] This disclosure provides a multi-cloud domain task processing method, apparatus, electronic device, and storage medium to at least solve the problem in related technologies where the service range of a cloud domain is limited by the resources included in the cloud domain, resulting in a small service range and poor user experience. The technical solution of this disclosure is as follows:

[0006] Firstly, this application provides a multi-cloud domain task processing method applied to a collaborative service platform of a first cloud domain. Each cloud domain corresponds one-to-one with the collaborative service platform. The collaborative service platform of the first cloud domain registers resource information for each cloud domain, including one or more of device resource information, data resource information, and service resource information. The first cloud domain can be any one of the cloud domains. The method includes: determining a second cloud domain from the multiple cloud domains based on a target task and the resource information corresponding to each cloud domain; the resources of the second cloud domain include target resources used to implement the target task; different cloud domains correspond to different resources; sending a task execution request to the collaborative service platform of the second cloud domain, the task execution request requesting the collaborative service platform of the second cloud domain to execute the target task based on the target resources; and receiving the execution result of the target task returned by the collaborative service platform of the second cloud domain, the execution result being sent when the collaborative service platform of the second cloud domain accepts the task execution request.

[0007] In the above implementation, when the first cloud domain needs the collaboration of other cloud domains to complete a certain target task, the collaboration service platform of the first cloud domain determines the target cloud domain, namely the second cloud domain, that can execute the target task based on the resources provided by each cloud domain. The collaboration service platform of the first cloud domain sends a task execution request to the collaboration service platform of the second cloud domain, requesting the second cloud domain to collaborate with the first cloud domain to execute the target task. After accepting the execution request, the collaboration service platform of the second cloud domain, based on the target resources of the second cloud domain, collaboratively executes the target task and then sends the execution result to the collaboration service platform of the first cloud domain, thus collaborating with the first cloud domain to complete the execution of the target task.

[0008] Based on this implementation, when the resources of the first cloud domain cannot execute a certain target task, the collaborative service platform of the first cloud domain can determine a second cloud domain capable of performing the target task from other cloud domains based on the resource availability of each cloud domain. The first cloud domain's collaborative service platform then sends a task execution request to the second cloud domain's collaborative service platform, allowing the second cloud domain to collaborate with the first cloud domain to execute the target task. This enables different cloud domains to collaboratively complete tasks, ensuring that the scope of tasks that a single cloud domain can perform no longer solely depends on its own resources but can also rely on the resources of other cloud domains to collaboratively complete the target task. Therefore, the task processing method of this application avoids the problem of the task scope of each cloud domain being limited by the resources of that cloud domain, thus expanding the task scope of each cloud domain and providing users of each cloud domain with a wider and more comprehensive range of services, thereby improving the user experience.

[0009] In one possible implementation, before determining the second cloud domain from multiple cloud domains based on the target task and the resource information corresponding to each cloud domain, the process includes: sending a resource information registration request to the collaborative service platform of any other cloud domain; the resource information registration request instructing the request to register the resource information of the collaborative service platform of any other cloud domain on the collaborative service platform of the first cloud domain; associating the resource information returned by the collaborative service platform of any other cloud domain with the cloud domain identifier of any other cloud domain to complete the registration of the resource information of the collaborative service platform of any other cloud domain on the collaborative service platform of the first cloud domain.

[0010] In one possible implementation, determining a second cloud domain from multiple cloud domains based on the target task and resource information corresponding to each cloud domain in multiple cloud domains includes: determining a target service for serving the target task based on the target task initiated by the terminal device of the target user in the first cloud domain; determining a first candidate cloud domain from multiple cloud domains based on the service resource information of multiple cloud domains registered on the collaborative service platform of the first cloud domain, wherein the service resources of the first candidate cloud domain include the target service; and determining the second cloud domain from the first candidate cloud domain.

[0011] In one possible implementation, sending a task execution request to the collaborative service platform of the second cloud domain includes: identifying target data resources and / or target device resources in the second cloud domain associated with the target task; identifying target users in the first cloud domain associated with the target task; and sending a task execution request carrying the target data resources and / or target device resources, as well as the target user, to the collaborative service platform of the second cloud domain. The task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the target data resources and / or target device resources.

[0012] In one possible implementation, sending a task execution request to the collaborative service platform of the second cloud domain further includes: determining condition information associated with the target service; sending a task execution request carrying the condition information to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the condition information.

[0013] In one possible implementation, the first cloud domain and the second cloud domain correspond to the same level, but their upper-level cloud domains are different. Sending a task execution request to the collaborative service platform of the second cloud domain includes: sending a first request to the collaborative service platform of the upper-level cloud domain of the first cloud domain, the first request being used to request the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request; and, if the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, instructing the collaborative service platform of the upper-level cloud domain of the first cloud domain to send a second request to the collaborative service platform of the upper-level cloud domain of the second cloud domain, the second request being used to request the collaborative service platform of the upper-level cloud domain of the second cloud domain to approve the task execution request; and, if the collaborative service platform of the upper-level cloud domain of the second cloud domain approves the task execution request, instructing the collaborative service platform of the upper-level cloud domain of the second cloud domain to send a task execution request to the collaborative service platform of the second cloud domain.

[0014] In this implementation, both the first and second cloud domains belong to the same cloud domain layer as the devices collecting data resources within the overall cloud domain structure; therefore, they are typically at the same level. For scenarios where their corresponding upper-layer cloud domains have different structures, when the collaborative service platform in the first cloud domain sends a task execution request to the collaborative service platform in the second cloud domain, the second cloud domain's collaborative service platform can only successfully receive the request if both the collaborative service platforms in the upper-layer cloud domains of both the first and second cloud domains have approved it. Based on this, an approval process for task execution requests is implemented in scenarios where the upper-layer cloud domains of the two cloud domains are different, ensuring that the task execution request received by the second cloud domain's collaborative service platform is approved by both upper-layer cloud domains, thereby guaranteeing the rationality of the second cloud domain's collaborative service platform's execution of the target task.

[0015] In one possible implementation, the first cloud domain and the second cloud domain correspond to the same level, and the upper-level cloud domain of the first cloud domain and the second cloud domain are the same cloud domain. Sending a task execution request to the collaborative service platform of the second cloud domain includes: sending a third request to the collaborative service platform of the upper-level cloud domain of the first cloud domain. The third request is used to request the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request, and if the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-level cloud domain of the first cloud domain to send the task execution request to the second cloud domain.

[0016] In this implementation, for scenarios where both cloud service platforms share the same upper-layer cloud domain, when the collaborative service platform in the first cloud domain sends a task execution request to the collaborative service platform in the second cloud domain, the second cloud domain's collaborative service platform can only receive the request if the request is approved by the collaborative service platform in the upper-layer cloud domain of the first cloud domain. Based on this, an approval process for task execution requests is implemented in cloud domain scenarios where both cloud service platforms share the same upper-layer cloud domain, ensuring that the task execution requests received by the second cloud domain's collaborative service platform are approved by the same upper-layer cloud domain, thereby guaranteeing the rationality of the second cloud domain's collaborative service platform's execution of the target task.

[0017] In one possible implementation, the method further includes: receiving an execution request sent by a collaborative service platform of a third cloud domain, wherein the third cloud domain is a lower-level cloud domain of the first cloud domain or a cloud domain at the same level as the first cloud domain, and the execution request sent by the collaborative service platform of the third cloud domain instructs the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain to execute the task to be executed generated by the third cloud domain; if the third cloud domain corresponds to the same level as the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, executing the task to be executed using the resources registered by the collaborative service platform of the first cloud domain; if the level of the third cloud domain corresponds to the same level as the lower-level cloud domain of the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, sending an execution request to the collaborative service platform of the lower-level cloud domain of the first cloud domain.

[0018] This implementation method can process the execution request according to different task processing procedures based on the different hierarchical relationships of the cloud domain hierarchy between the third cloud domain and the first cloud domain. This allows the cloud domain that matches the resources required by the task to be executed to collaborate with the third cloud domain to execute the task. In this way, the resources registered on the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain can be used to collaboratively complete the task to be executed in the third cloud domain.

[0019] According to a second aspect of the present disclosure, a multi-cloud domain task processing apparatus is provided, wherein each cloud domain corresponds one-to-one with a collaborative service platform. The collaborative service platform of a first cloud domain registers resource information for each cloud domain, and the resource information includes one or more of device resource information, data resource information, and service resource information. The apparatus includes: a determining unit configured to determine a second cloud domain from the multiple cloud domains based on a target task and the resource information corresponding to each cloud domain in the multiple cloud domains, wherein the resources of the second cloud domain include target resources for implementing the target task; the resource information of different cloud domains corresponds to different resources; a sending unit configured to send a task execution request to the collaborative service platform of the second cloud domain, the task execution request being used to request the collaborative service platform of the second cloud domain to execute the target task based on the target resources; and a receiving unit configured to receive the execution result of the target task returned by the collaborative service platform of the second cloud domain, wherein the execution result is sent when the collaborative service platform of the second cloud domain accepts the task execution request.

[0020] In one possible implementation, the determining unit is further configured to send a resource information registration request to the collaborative service platform of any other cloud domain; the resource information registration request is used to indicate that the resource information of the collaborative service platform of any other cloud domain is registered on the collaborative service platform of the first cloud domain; the determining unit is further configured to associate the resource information returned by the collaborative service platform of any other cloud domain with the cloud domain identifier of any other cloud domain, so as to complete the registration of the resource information of the collaborative service platform of any other cloud domain on the collaborative service platform of the first cloud domain.

[0021] In one possible implementation, the determining unit is specifically configured to perform the following actions: determining a target service for serving the target task based on the target task initiated by the terminal device of the target user in the first cloud domain; determining a first candidate cloud domain from multiple cloud domains based on the service resource information of multiple cloud domains registered on the collaborative service platform of the first cloud domain, wherein the service resources of the first candidate cloud domain include the target service; and determining a second cloud domain from the first candidate cloud domain.

[0022] In one possible implementation, the sending unit is specifically configured to: determine the target data resources and / or target device resources associated with the target task in the second cloud domain; determine the target user associated with the target task in the first cloud domain; and send a task execution request carrying the target data resources and / or target device resources, as well as the target user, to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the target data resources and / or target device resources.

[0023] In one possible implementation, the sending unit is further specifically configured to: determine the condition information associated with the target service; send a task execution request carrying the condition information to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the condition information.

[0024] In one possible implementation, the first cloud domain and the second cloud domain correspond to the same level, but the upper-level cloud domains of the first cloud domain and the second cloud domain are different cloud domains. The sending unit is further specifically configured to send a first request to the collaborative service platform of the upper-level cloud domain of the first cloud domain. The first request is used to request the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request. If the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-level cloud domain of the first cloud domain to send a second request to the collaborative service platform of the upper-level cloud domain of the second cloud domain. The second request is used to request the collaborative service platform of the upper-level cloud domain of the second cloud domain to approve the task execution request. If the collaborative service platform of the upper-level cloud domain of the second cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-level cloud domain of the second cloud domain to send a task execution request to the collaborative service platform of the second cloud domain.

[0025] In one possible implementation, the first cloud domain and the second cloud domain correspond to the same level, and the upper-level cloud domains of the first cloud domain and the second cloud domain are the same cloud domain; the sending unit is further specifically configured to send a third request to the collaborative service platform of the upper-level cloud domain of the first cloud domain, the third request being used to request the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request, and, if the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, instruct the collaborative service platform of the upper-level cloud domain of the first cloud domain to send the task execution request to the second cloud domain.

[0026] In one possible implementation, the receiving unit is further configured to receive an execution request sent by a collaborative service platform of a third cloud domain, wherein the third cloud domain is a lower-level cloud domain of the first cloud domain or a cloud domain at the same level as the first cloud domain. The execution request sent by the collaborative service platform of the third cloud domain instructs the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain to execute the task to be executed generated by the third cloud domain. If the third cloud domain is at the same level as the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, the receiving unit executes the task to be executed using the resources registered by the collaborative service platform of the first cloud domain. If the level of the third cloud domain is the same as the level of the lower-level cloud domain of the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, the receiving unit sends an execution request to the collaborative service platform of the lower-level cloud domain of the first cloud domain.

[0027] According to a third aspect of the present disclosure, an electronic device is provided, comprising: a processor and a memory for storing processor-executable instructions; wherein the processor is configured to execute the executable instructions to implement a multi-cloud domain task processing method as described in the first aspect and any possible implementation thereof.

[0028] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided such that, when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to perform a multi-cloud domain task processing method as described in the first aspect and any possible implementation thereof; or when the instructions in the computer-readable storage medium are executed by a multi-cloud domain task processing device, the multi-cloud domain task processing device is able to perform a multi-cloud domain task processing method as described in the first aspect and any possible implementation thereof.

[0029] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program or instructions, which are executed by a processor as a multi-cloud domain task processing method as described in the first aspect and any possible implementation thereof.

[0030] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0031] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0032] Figure 1 This is a schematic diagram illustrating a cloud domain structure relationship according to an exemplary embodiment;

[0033] Figure 2 This is a schematic diagram illustrating a cloud service system according to an exemplary embodiment;

[0034] Figure 3 This is a schematic diagram illustrating a multi-cloud domain task processing subsystem according to an exemplary embodiment;

[0035] Figure 4 This is a schematic diagram illustrating an alarm subsystem according to an exemplary embodiment;

[0036] Figure 5 This is a flowchart illustrating a multi-cloud domain task processing method according to an exemplary embodiment;

[0037] Figure 6 This is a schematic diagram illustrating a multi-cloud domain task processing procedure according to an exemplary embodiment;

[0038] Figure 7 This is a schematic diagram illustrating another multi-cloud domain task processing procedure according to an exemplary embodiment;

[0039] Figure 8 This is a schematic diagram illustrating another multi-cloud domain task processing procedure according to an exemplary embodiment;

[0040] Figure 9 This is a flowchart illustrating another multi-cloud domain task processing method according to an exemplary embodiment;

[0041] Figure 10 This is a flowchart illustrating another multi-cloud domain task processing method according to an exemplary embodiment;

[0042] Figure 11 This is a flowchart illustrating another multi-cloud domain task processing method according to an exemplary embodiment;

[0043] Figure 12 This is a flowchart illustrating a multi-dimensional sensing and intelligent connectivity method based on edge-cloud according to an exemplary embodiment;

[0044] Figure 13 This is a flowchart illustrating another multi-dimensional sensing and intelligent connectivity method based on edge-cloud according to an exemplary embodiment;

[0045] Figure 14 This is a schematic diagram of a multi-cloud domain task processing apparatus according to an exemplary embodiment;

[0046] Figure 15 This is a schematic diagram illustrating a multi-dimensional sensing intelligent interconnection device based on edge cloud according to an exemplary embodiment;

[0047] Figure 16 This is a schematic diagram of an electronic device according to an exemplary embodiment. Detailed Implementation

[0048] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0049] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0050] Before providing a detailed description of the multi-cloud domain task processing method provided in the embodiments of this disclosure, let's briefly introduce the application scenarios and implementation environment involved in the embodiments of this disclosure.

[0051] First, to facilitate understanding of this application, the relevant elements involved in this application will now be described.

[0052] Terminal: A single sensing device capable of collecting one-dimensional or multi-dimensional information and processing it to a certain extent. In essence, a single sensing device can collect information data within a small area perceived by a particular device. This sensing device can be radar, vibration fiber optic, or video surveillance.

[0053] Edge: Also known as the edge side, edge region, or edge domain of the cloud. Through the combined and coordinated operation of multiple sensing devices, data collected by multiple sensing devices within a local area corresponding to the edge (i.e., the area enclosed by an edge) is analyzed.

[0054] Cloud: Also known as cloud domain. It integrates data analysis results from multiple edges and data collected by multiple sensing devices from multiple ends, aggregating multi-dimensional data to achieve the fusion, scheduling, and management of various algorithms, computing power, and data resources, and to ensure the rational operation of the data corresponding to the devices and edges. The area covered by the cloud includes the total area enclosed by multiple edges.

[0055] Integrated Collaborative Service Platform: Also known as the Collaborative Service Platform, it is configured to correspond to the servers of various clouds and is task-oriented, enabling other clouds to collaborate on tasks of the local cloud.

[0056] Vibrating fiber unit number: A vibrating fiber is divided into multiple units at equal intervals, and each unit is assigned a corresponding number. Each vibrating fiber unit number corresponds to a master acquisition device, and a master acquisition device establishes an association relationship with multiple other vibrating fiber unit numbers in its vicinity; that is, the master acquisition device is a slave acquisition device for multiple other vibrating fiber unit numbers. For example, taking a PTZ camera as the acquisition device, each PTZ camera can establish an association relationship with 10 surrounding vibrating fiber unit numbers.

[0057] Secondly, a brief introduction to the application scenarios involved in this disclosure will be given.

[0058] Cloud services are a service model that provides dynamically scalable virtualized resources via the internet. Cloud services offer advantages such as low cost, high reliability, high scalability, high automation, and virtualization. Therefore, cloud service technology has been widely used by individuals and businesses for resource storage and processing across networks such as the internet.

[0059] In the cloud service system of the network monitoring system, data resource acquisition devices (such as image acquisition devices or radar) send the acquired data resources to the cloud domain storage to which the data resource acquisition devices belong. At the same time, the cloud server in the cloud domain can also process the acquired data resources to provide corresponding services.

[0060] For example, when a client in the cloud domain needs to access the data resources collected above, the client directly accesses the data resources from the cloud domain to which the client belongs and displays the data resources to the client user. Or, when the client needs to process the data resources collected above, the cloud server in the cloud domain will directly process the data resources and provide the processing results to the client user.

[0061] However, in the aforementioned technologies, cloud domain users can only access resources within the cloud domain to which their client belongs, and cannot access resources in other cloud domains. This limits the service scope of the cloud domain and fails to meet the growing service demands of users, significantly reducing the user experience. Therefore, how to enable multiple cloud domains to provide resources and related services to users of a specific cloud domain has become an urgent technical problem to be solved.

[0062] To address the aforementioned issues, this disclosure provides a multi-cloud-domain task processing method. When the resources corresponding to the first cloud domain cannot execute a certain target task, the collaborative service platform of the first cloud domain determines the target cloud domain, i.e., the second cloud domain, that can execute the target task based on the resources available in each cloud domain. The collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the second cloud domain, requesting the second cloud domain to collaborate with the first cloud domain to execute the target task. After accepting the execution request, the collaborative service platform of the second cloud domain, based on the target resources of the second cloud domain, collaboratively executes the target task and then sends the execution result to the collaborative service platform of the first cloud domain, thus collaborating with the first cloud domain to complete the execution of the target task.

[0063] Based on this implementation method, when the resources of the first cloud domain cannot execute a certain target task, the collaborative service platform of the first cloud domain can determine the second cloud domain that can achieve the target task from other cloud domains based on the resource situation provided by each cloud domain. Then, by sending a task execution request from the collaborative service platform of the first cloud domain to the collaborative service platform of the second cloud domain, the second cloud domain can cooperate with the first cloud domain to execute the target task. This enables different cloud domains to cooperate in completing the task, so that the scope of tasks that a single cloud domain can execute no longer depends solely on the resources of the cloud domain itself, but can also rely on the resources of other cloud domains to cooperate in completing the target task.

[0064] Based on this, the task processing method disclosed herein associates each independent local cloud domain or local cloud domain that executes local tasks, so as to realize cross-cloud domain collaborative execution of global tasks, avoid the problem that the task scope of each cloud domain is limited by the resources of that cloud domain, improve the task scope of each cloud domain, and thus provide users of each cloud domain with a wider range and more comprehensive services, thereby improving the user experience.

[0065] Next, a brief introduction to the implementation architecture involved in this application will be given below.

[0066] Figure 1 This is a schematic diagram of a multi-cloud domain provided in this application. Figure 1 The hierarchical relationships between multiple cloud domains and the relationships between clouds, edges, and endpoints within a single cloud domain are illustrated. Examples include first-level clouds, second-level clouds (e.g., second-level cloud A, second-level cloud D), and third-level clouds (e.g., third-level cloud a, third-level cloud b, third-level cloud c, third-level cloud e, third-level cloud d).

[0067] Specifically, Figure 1 The cloud domains are hierarchically divided into Level 1, Level 2, Level 3, and so on (equivalent to administrative levels such as ministry, province, city, etc.). Network connectivity is bidirectional between cloud domains at each level, but only single-level interconnections exist between levels. For example, a Level 1 cloud only interconnects with a Level 2 cloud, not with a Level 3 cloud. For instance, the upper-level cloud domain corresponding to Level 3 cloud 'a' is the same as the upper-level cloud domain corresponding to Level 3 cloud 'b' (i.e., Level 2 cloud A); the upper-level cloud domain of Level 3 cloud 'd' and the upper-level cloud domain of Level 3 cloud 'a' belong to the same level but are different cloud domains; the upper-level cloud domain of Level 3 cloud 'd' (i.e., Level 2 cloud A) and the upper-level cloud domain corresponding to Level 3 cloud 'b' (i.e., Level 2 cloud D) belong to the same level but are different cloud domains. Each cloud domain corresponds to one cloud, one cloud corresponds to multiple edges, and one edge corresponds to multiple endpoints.

[0068] For example, a certain city C corresponds to cloud domain C, and city C includes M districts, such that the M districts correspond to M cloud domains. That is, cloud domain C is an upper-level cloud domain of the M cloud domains. Then, a server corresponding to an upper-level cloud domain can obtain resources from the lower-level cloud domains interconnected with it. These resources include one or more of the following: device resources, data resources, and service resources.

[0069] Figure 2 This is a schematic diagram of a cloud domain service system 20 provided in this application. The cloud domain service system includes various task processing subsystems 21 and alarm subsystems 22 corresponding to each cloud domain. The task processing subsystem 21 is used to enable servers in different cloud domains to collaboratively complete a specific task; each cloud domain corresponds to an alarm subsystem 22, which is used to call upon data collected from device resources within each edge of the corresponding cloud domain and to generate alarms using that collected data.

[0070] Figure 3 This is a schematic diagram of a multi-cloud domain task processing subsystem 21 provided in this disclosure, which corresponds to multiple cloud domains. For example... Figure 3 As shown, the task processing subsystem includes multiple servers 201 corresponding to multiple cloud domains and terminal devices 202 corresponding to users in each cloud domain. Servers 201 can establish connections with terminal devices 202 via wired or wireless networks. In this application, each cloud domain's server 201 can include an integrated collaborative service platform. Resources provided by each cloud domain are registered on the integrated collaborative service platform, and each integrated collaborative service platform corresponds to one collaborative service application. This collaborative service application can be installed on the user's terminal device 202, and the target resources provided by the integrated collaborative service platform or the processing results of the target resources can be displayed on the content display interface of the terminal device 202.

[0071] For example, each level of "cloud domain" registers the resources and tasks it can provide and execute with the local integrated collaborative service platform. The integrated collaborative service platform of the two interconnected levels of "cloud domains" authenticates and authorizes the task execution request by sending it, thereby achieving collaboration and secure mutual trust between multi-level cloud domains through the integrated collaborative service platform. This enables each level of "cloud domain" to discover various view tasks provided by other "cloud domains" across levels and cloud domains through the integrated collaborative service platform, and to request and invoke resources as needed.

[0072] Another example, taking any one of multiple cloud domains as the first cloud domain, illustrates the collaborative service process across different cloud domains. The resources provided by each cloud domain are registered on each integrated collaborative service platform, so that each platform stores the resource identifiers of the resources provided by each cloud domain. When a target terminal device corresponding to the first cloud domain requests the server 201 of the first cloud domain to execute a target task, there may be a situation where the first cloud domain does not contain the target resource, but other cloud domains can provide it. In this case, the server of the first cloud domain will determine the resource identifier of the target resource matching the target task based on the resource identifiers on the integrated collaborative service platforms corresponding to the servers of each cloud domain, thereby determining the second cloud domain and requesting the server of the second cloud domain to collaborate with the first cloud domain in executing the target task.

[0073] In some embodiments, the servers 201 in each cloud domain include or are connected to a database, and the data resources corresponding to each integrated collaborative service platform are stored in the database. Terminal devices 202 can access the data resources in the database through the servers 201 of their respective cloud domains. These data resources include data collected by various devices in the cloud domain and data after processing and analysis of the collected data.

[0074] Figure 4 This is a schematic diagram of an alarm subsystem 22 provided in this disclosure, corresponding to a cloud domain. For example... Figure 4 As shown, the alarm subsystem 22 includes multiple acquisition devices 221, multiple alarm devices 222, and servers 223 of target cloud domains to which the alarm devices belong. Both the alarm devices 222 and the acquisition devices 221 are end devices. The intelligent scheduling device of the edge domain of the target cloud domain calls the acquisition device 221 associated with the alarm device 222 to verify the alarm event corresponding to that alarm device 222, and sends the verified result to the collaborative service platform of the target cloud domain. The collaborative service platform of the target cloud domain then sends the verified result to the cloud domain requesting the target cloud to execute the alarm task, such as the first cloud domain. The intelligent scheduling device of the edge domain is used to verify the alarm events to be alarmed based on the data resources of the alarm devices (such as alarm signals) and the data resources collected by the acquisition devices (such as information about the image of the alarm area in the alarm signal), removing invalid alarm events to ensure the accuracy and validity of the sent alarm events. In the following text, the second cloud domain refers to the target cloud domain. Server 223 in the target cloud domain is the target server of server 201 in each cloud domain.

[0075] In some embodiments, each of the aforementioned servers 201 and the target server can be a single server, or a server cluster consisting of multiple servers. In some embodiments, the server cluster can also be a distributed cluster. This disclosure does not limit the specific implementation of the server 201.

[0076] The terminal device can be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR) / virtual reality (VR) device, etc., that can install and use content community applications (such as Kuaishou). This disclosure does not impose any special restrictions on the specific form of the terminal. It can interact with users through one or more methods such as keyboard, touchpad, touch screen, remote control, voice interaction, or handwriting devices.

[0077] Optionally, the above Figure 2 In the cloud service system shown, the server can connect to at least one terminal device. This disclosure does not limit the number or type of terminal devices.

[0078] The multi-cloud domain task processing method provided in this disclosure can be applied to the aforementioned... Figure 3 The server in the implementation architecture shown is illustrated below. For ease of understanding, the multi-cloud domain task processing method provided in this disclosure will be described in detail below with reference to the accompanying drawings.

[0079] It should be noted that before introducing the multi-dimensional sensing and intelligent connectivity method based on edge-cloud, the process of handling cross-domain task execution requests in the multi-cloud domain task processing method will be introduced first; then, the process of multi-dimensional sensing and intelligent connectivity will be introduced using the example of issuing alarms for target events as a target task. The following example of the first cloud domain's collaborative service platform sending a task execution request to the second cloud domain's collaborative service platform to complete a target task is only used to illustrate the task processing method. When the target task requires the collaboration of multiple target cloud domains, the first cloud domain's collaborative service platform can send multiple task requests to the collaborative service platforms of multiple target cloud domains simultaneously, and the following task processing method can be executed synchronously. To avoid repetition, it will not be elaborated further below.

[0080] Figure 5 This is a flowchart illustrating a multi-cloud domain task processing method according to an exemplary embodiment, such as... Figure 5 As shown, the multi-cloud domain task processing method can be used in the aforementioned multi-cloud domain task processing system, and includes the following steps.

[0081] Step S51: The collaborative service platform of the first cloud domain determines the second cloud domain from multiple cloud domains based on the target task and the resources corresponding to each cloud domain.

[0082] The resources include one or more of the following: service resources, equipment resources, and data resources. The resources corresponding to the second cloud domain include the target resources used to achieve the target task.

[0083] In some embodiments, the target task can be a view-type task, such as a video retrieval task, a video query task, or a video deployment task. For example, device resources can be sensing devices (such as vibration fiber optics or radar) corresponding to various endpoints within the cloud domain; data resources include data collected by each sensing device and data after data analysis and processing of the data collected by each sensing device (e.g., edge-related data resources).

[0084] Optionally, the second cloud domain is determined in the following ways: First, based on the target task initiated by the target user's terminal device in the first cloud domain, a target service for serving the target task is determined. Second, based on the service resource information of multiple cloud domains registered on the collaborative service platform of the first cloud domain, a first candidate cloud domain is determined from multiple cloud domains, wherein the service resources of the first candidate cloud domain include the target service. Third, the second cloud domain is determined from the first candidate cloud domain.

[0085] Specifically, each cloud domain's collaborative service platform registers resource identifiers for the resources that each cloud domain can provide. Typically, each cloud domain includes multiple resource identifiers. From the resource identifiers registered in each cloud domain, the target resource identifier that matches the target resource is determined. Based on the association between resource identifiers and various cloud domains, the target cloud domain associated with the target resource identifier is determined as the second cloud domain.

[0086] As one implementation method, prior to step S51, the following steps may be performed to enable other cloud domains to register resource information on the collaborative service platform of the first cloud domain. Specifically, firstly, the collaborative service platform of the first cloud domain sends a resource information registration request to the collaborative service platform of any other cloud domain. The resource information registration request instructs that the resource information of the collaborative service platform of any other cloud domain be registered on the collaborative service platform of the first cloud domain. Secondly, the resource information returned by the collaborative service platform of any other cloud domain is associated with the cloud domain identifier of any other cloud domain to complete the registration of the resource information of the collaborative service platform of any other cloud domain on the collaborative service platform of the first cloud domain.

[0087] S52, the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the second cloud domain.

[0088] Understandably, the collaborative service platform of the first cloud domain sends task execution requests through the collaborative service platforms of the upper-layer cloud domains of the first and second cloud domains. In implementation method one, step S52 can be specifically implemented as follows: First, the collaborative service platform of the first cloud domain determines the target data resources and / or target device resources associated with the target task in the second cloud domain. Second, the collaborative service platform of the first cloud domain further determines the target user associated with the target task in the first cloud domain. Third, the collaborative service platform of the first cloud domain sends a task execution request carrying the target data resources and / or target device resources, as well as the target user, to the collaborative service platform of the second cloud domain; wherein, the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the target data resources and / or target device resources.

[0089] In detail, the task execution request includes an application form. This application form contains: an application number, the applicant user ID (i.e., the target user ID), a list of authorized user information (including username, contact number, IP / MAC address, etc.), the purpose of resource use, the reason for the application, the resource usage period (long-term or temporary), a description of the specific resource location requested, resource control permissions (such as preview, playback, download, cloud domain operation control, control of the number of cloud domains using the target resource, control of voice intercom, etc.), and related control permission details (such as video playback time period, video download and transcoding type, number of concurrent video previews and recording playbacks, etc.).

[0090] Furthermore, in the second implementation method, step S52 can be further implemented as follows: determining the condition information associated with the target service; sending a task execution request carrying the condition information to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the condition information.

[0091] For example, the conditional information includes cross-domain collaborative deployment conditional information, specifically, such as deployment target information, deployment time period, deployment similarity, and other conditional information. This conditional information exists in the form of an application form.

[0092] The above task execution request is used to request the collaborative service platform of the second cloud domain to execute the target task based on the target resources.

[0093] S53, the collaborative service platform of the second cloud domain, accepts task execution requests and executes the target tasks.

[0094] It should be noted that the second cloud domain can directly utilize its data resources to execute the target task; alternatively, the second cloud domain can invoke resources from the corresponding "edge" and / or "end" to execute the target task. Accordingly, the specific implementation methods for executing the target task are as follows: First, the collaborative service platform on the edge corresponding to the second cloud domain can analyze the data resources provided by multiple devices on the end. The collaborative service platform of the second cloud domain can utilize the analysis results of the data resources from the collaborative service platform on the edge corresponding to the second cloud domain to execute the target task. Second, the collaborative service platform of the second cloud domain can also utilize the data resources provided by the device resources on the device end corresponding to the second cloud domain to execute the target task. Third, the collaborative service platform of the second cloud domain can also process the analysis results from the edge corresponding to the collaborative service platform of the second cloud domain and / or the data resources on the corresponding device end according to the execution rules matched with the target task to execute the target task. Therefore, this application does not specifically limit the method by which the second collaborative service platform executes the target task.

[0095] Understandably, the collaborative service platform in the second cloud domain can accept the task execution request to agree to collaborate with the first cloud domain to execute the target task; or it can reject the task execution request to refuse to collaborate with the first cloud domain to execute the target task.

[0096] As one possible implementation, if the collaborative service platform of the second cloud domain rejects the task execution request, a prompt message is received from the collaborative service platform of the second cloud domain. The prompt message is used to indicate that the second cloud domain refuses to execute the target task.

[0097] Each level of cloud domain's collaborative service platform has a corresponding collaborative administrator. This administrator assesses the accuracy and reasonableness of the requested content before executing the appropriate action: "Approve the task execution request" or "Reject the target task request."

[0098] Furthermore, the target resource information also includes the sharing permission information of the target resource, which is used to characterize the range of cloud domains that are allowed to share the resource to a preset number of cloud domains.

[0099] Based on this, the specific rejection method is as follows: The collaborative service platform of the first cloud domain receives a rejection sharing prompt message sent by the collaborative service platform of the second cloud domain. The rejection sharing prompt message indicates that sharing the target resource to the first cloud domain is not permitted. This rejection sharing request is sent when the collaborative service platform of the second cloud domain obtains that the number of cloud domains calling the target resource is greater than or equal to a preset number, and updates the sharing permission information of the target resource to include the sharing permission information that disallows sharing the target resource to the first cloud domain.

[0100] It should be noted that cross-cloud domain collaboration administrators can view the usage of target resources and corresponding target services by user groups formed by target users in the task execution request application form across the entire domain.

[0101] This rejection method supports control over resource retrieval methods across various dimensions and the number of cloud domains for target resource applications, such as the total number of retrievals, concurrent retrievals, total download paths, concurrent download paths, and playback multipliers. This helps avoid issues like insufficient service resources, resource contention, and control contention that can occur after frequent requests for cross-domain video resources and services.

[0102] For example, when the target service is a video retrieval service, the video retrieval method is controlled through cloud domain operation management, video preheating, video transcoding, emergency management, security auditing, etc. The specific control process is as follows.

[0103] (1) Operation and control of cloud domains. The collaborative service platform of the first cloud domain satisfies cross-cloud domain access control, and provides the ability of hierarchical authorization control and cloud domain revocation to ensure that the cloud domain of the collaborative service platform of the target cloud domain is not interfered with by cross-domain requests. The cloud domain revocation operation is processed by using the monitoring target point information and the target device location before the record is executed, so as to satisfy the automatic and manual revocation operations of the collaborative service platform of the first cloud domain.

[0104] (2) Video preheating: In the collaborative service platform of the first cloud domain, video preheating capability is provided through video processing service. The cross-domain videos of key concern are pre-fetched and quality tested. Anomalies are detected and repaired in a timely manner to ensure that cross-domain video access achieves the effect of instant opening on the first screen, no lag, and no screen tearing.

[0105] (3) Video transcoding: In the collaborative service platform of the second cloud domain, transcoding capability is provided through network media service to transcode the video stream of cross-domain video access request, such as converting high-definition H.264 bitstream to H.265 or reducing bit rate, thereby reducing the network bandwidth occupation of cross-domain video access.

[0106] (4) Emergency control: Supports one-click revocation of permissions for target locations, one-click exclusive control of the collaborative service platform of the First Cloud Domain, and one-click exclusive control of video preview, playback locations, and downloads. Permission adjustment information will be directly pushed to the corresponding application submitter and actual user notification. A global whitelist or a whitelist for a single control task can be set.

[0107] (5) Security auditing supports full recording of cross-domain video scheduling services, including video preview, video playback, control of the collaborative service platform in the first cloud domain, video management, and other operations, while also covering relevant information of target users in the first cloud domain. For full recording of video operations on the access platform, it covers all streaming terminals, recording information such as the streaming terminal IP, video service type, start / end time, accessing user, audio and video stream information, and network status during the access process, facilitating subsequent tracing and investigation.

[0108] S54, the collaborative service platform of the first cloud domain receives the execution result of the target task returned by the collaborative service platform of the second cloud domain.

[0109] Specifically, after the collaborative service platform of the second cloud domain completes the target task using the target resources in the second cloud domain, it returns the execution result to the collaborative service platform of the first cloud domain.

[0110] It should be noted that after the collaborative service platform in the second cloud domain accepts a task execution request once, the collaborative service platform in the first cloud domain can use the execution result of the target task multiple times, which is the "one-time application, multiple uses" mode.

[0111] For example, taking video access as the target task, the various collaborative service platforms corresponding to multiple upper-level cloud domains forward the video access request. After the video access permission is approved, the target user in the first cloud domain can preview the video or play back the video recording in real time within the controlled permission period.

[0112] Additionally, it should be noted that after issuing a task execution request, the target user can also view the application progress, i.e., the approval progress, of the corresponding task execution request on the collaborative service platform of the First Cloud Domain.

[0113] In the above implementation, when the resources corresponding to the first cloud domain cannot execute a certain target task, the collaborative service platform of the first cloud domain determines the target cloud domain, namely the second cloud domain, that can execute the target task based on the resources available in each cloud domain. The collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the second cloud domain, requesting the second cloud domain to collaborate with the first cloud domain to execute the target task. After accepting the execution request, the collaborative service platform of the second cloud domain, based on the target resources of the second cloud domain, collaboratively executes the target task and then sends the execution result to the collaborative service platform of the first cloud domain, thus collaborating with the first cloud domain to complete the execution of the target task.

[0114] Based on this implementation, when the resources of the first cloud domain cannot execute a certain target task, the collaborative service platform of the first cloud domain can determine the second cloud domain that can achieve the target task from other cloud domains based on the resource situation provided by each cloud domain. Then, the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the second cloud domain, so that the second cloud domain can cooperate with the first cloud domain to execute the target task. This enables different cloud domains to cooperate to complete the task, so that the scope of tasks that a single cloud domain can execute no longer depends solely on the resources of the cloud domain itself, but can also rely on the resources of other cloud domains to cooperate in completing the target task.

[0115] When the resources in the first cloud domain are capable of executing a specific target task, the collaborative service platform of the first cloud domain executes that target task based on the resources of the first cloud domain. The execution process of the target task by the collaborative service platform of the first cloud domain is similar to that of the collaborative service platform of the second cloud domain, and will not be described again here.

[0116] Based on this, the task processing method disclosed herein avoids the problem that the task scope of each cloud domain is limited by the resources of that cloud domain, thereby increasing the task scope of each cloud domain and providing users of each cloud domain with a wider range and more comprehensive services to improve user experience.

[0117] As one implementation method, after executing S34 above, the following steps are performed: The collaborative service platform of the first cloud domain sends the execution result to the terminal device that initiated the task execution request in the first cloud domain. This terminal device can be one or more.

[0118] In some embodiments, the task execution request includes the terminal device identifier of the terminal device. After the collaborative service platform in the second cloud domain completes the target task, the execution result of the target task is returned to the terminal device corresponding to the terminal device identifier.

[0119] For example, the data resource includes video data; the target data is the target video data within the video data; sending the execution result to the terminal device includes: sending the processing result corresponding to the target video data to the terminal device, so that the terminal device displays the execution result corresponding to the target video data. The target task in the above embodiments includes two types of target tasks: a first target task and a second target task. Specifically, the target task includes a first target task that invokes the target resource and a second target task that processes the target data in the target resource using preset rules. Different target task types correspond to different execution results.

[0120] For example, if the first target task is to retrieve data collected by the target device, then the execution result corresponding to the first target task is the data collected by the target device or the address of the data collected by the target device.

[0121] In another example, if the second objective task is to perform objective processing on the objective data, then the execution result of the second objective task is the processing result of the objective data using preset rules, wherein the data resources corresponding to the second cloud domain include the objective data.

[0122] In one implementation, in the above-described step of determining the second cloud domain, the service resources of the first candidate cloud domain include a first target service, which is used to access data collected by the data acquisition device.

[0123] For example, taking the first target service for video retrieval service as an example, the target task is cross-domain video retrieval. The task execution request process of the above step S52 implementation method is described below.

[0124] In this implementation, the local cloud (city 1) sends a task execution request to the target cloud (city 2). The task execution request requests the retrieval of video resources from target locations within cloud city 2. Target locations are the target locations corresponding to target device resources and / or target data resources within the edges and / or endpoints of the target cloud domain. Target resource information is stored in a list format on the collaborative service platform.

[0125] like Figure 6 As shown, when sending a task execution request, the sending permission can be confirmed by inputting the description information of the target location. Specifically, the target user in City 1 inputs the description information of the target location on the collaborative service platform of City 1; then, the description information of the target location is confirmed by the collaborative service platforms corresponding to the upper-level cloud domain of City 1 (Province 1), the upper-level cloud domain of Province 1 (Ministry), the upper-level cloud domain of City 2 (Province 2), and each cloud domain of City 2, to confirm whether the description information of the target location meets the requirements, so as to confirm the existence of target device resources and / or target data resources.

[0126] Furthermore, after confirming that the description information of the target location meets the requirements in each cloud domain, the target access control information is then approved and confirmed. This target access control information describes the display permissions for using target device resources and / or target data resources. Specifically, the target user in City 1 inputs the target access control information on the collaborative service platform of City 1; then, the target access control information is approved and confirmed by the parent cloud domain of City 1 (Province 1), the parent cloud domain of Province 1 (Ministry), the parent cloud domain of City 2 (Province 2), and the respective collaborative service platforms corresponding to each cloud domain of City 2.

[0127] Based on this, the task execution request includes the target permission control information and the description information of the target location entered by the target user in the permission settings interface. The target permission control information includes one or more of the following: the display format, display mode, display quantity, and usage time of the target permission control information; according to the target permission control information, configure the permission information of the target data resources so that the target data resources sent to the target user are displayed in the target display mode; the target display mode is the display mode corresponding to the target permission control information.

[0128] It should be noted that after the target access control information is approved, during the video network sharing process from city 2 to city 1, the description information of the target location and the target access control information will be returned.

[0129] Specifically, such as Figure 7 The target user, as shown, initiates a cross-domain video access request through the collaborative service platform of City 1. This request is then forwarded through different collaborative service platforms in different cloud domains. Upon approval, the request returns a description of the target location and target access control information. The return process is as follows: Figure 7 As shown.

[0130] Furthermore, after the target access control information is approved and the description information of the target location and the target access control information are pushed back, such as... Figure 8 As shown, through the collaborative service platform, City 2 sends videos to target users in City 1 via different streaming paths, i.e., resource acquisition paths. These different paths are as follows: Figure 8 The path shown is Path 1, Path 2, or Path 3. Based on this, the collaborative service platform can determine the path to obtain the target resource based on the reachability of the link and the smoothness of the video. Simultaneously, the path to obtain the target resource can be set according to the needs of the target user. For example, multiple paths are displayed on the interface of the application corresponding to the collaborative service platform installed on the target user's terminal device, and the user selects one path as the target path to obtain the target resource.

[0131] In some embodiments, preset rules are formed based on condition information associated with the target service.

[0132] Based on this embodiment, as another implementation method, in the above-described step of determining the second cloud domain, the service resources of the first candidate cloud domain include a second target service. The second target service is used to perform target processing on the data collected by the data acquisition device using preset rules, and the data resources corresponding to the second cloud domain include target data.

[0133] In some implementations, the aforementioned preset rules include an acquisition path for acquiring target video data, rules for extracting preset features, rules for extracting preset object types, rules for extracting the similarity of preset objects, and rules for acquiring associated information. The associated information includes time information and location information. Target processing includes at least one or more of the following: acquiring target video data from the target video acquisition device based on the acquisition path; extracting target objects with preset features from the target video data based on the rules for extracting preset features; extracting target objects of the preset object type from the objects in the target video data based on the rules for extracting preset object types; extracting target objects from the objects in the target video data whose similarity to preset objects is greater than a similarity threshold based on the rules for extracting the similarity of preset objects; and acquiring the associated information of the target objects.

[0134] In one embodiment of generating the aforementioned preset rules, in response to an input instruction from a user account on the rule settings interface, preset rules are generated based on the rule information. The rule information includes one or more of the following: preset features, preset object types, similarity thresholds, and association information. The association information includes time information and location information.

[0135] For example, the second target task is a cross-domain collaborative deployment task. The cross-domain collaborative deployment task execution request can include deployment for facial recognition, vehicle identification, and ID card recognition. The target user, through the application corresponding to the local integrated collaborative service platform, obtains a list of cloud domains that can provide cross-domain collaborative deployment services, selects the target cloud domain for collaborative deployment, and enters the cross-domain collaborative deployment conditions on the displayed collaborative deployment page, thus forming the preset rules for the cross-domain collaborative deployment task. The cross-domain collaborative deployment conditions can include deployment target information, deployment time period, deployment similarity, and other conditional information.

[0136] For example, taking the second target service's cross-cloud domain deployment service as an example, the target task is cross-cloud domain deployment. The task execution request process under the second implementation method of step S52 above is explained as follows. In this example, the condition information can be understood as deployment conditions.

[0137] like Figure 6 and 7 As shown, when sending a task execution request, the deployment conditions input by the target user in City 1 can be approved and confirmed first. Specifically, the target user in City 1 inputs the condition information on the collaborative service platform of City 1; then, the condition information is approved and confirmed by the upper-level cloud domain of City 1 (Province 1), the upper-level cloud domain of Province 1 (Ministry), the upper-level cloud domain of City 2 (Province 2), and the respective collaborative service platforms corresponding to each cloud domain of City 2, to confirm that the target cloud domain can execute according to the deployment conditions.

[0138] The deployment conditions can exist in the form of an application form included in the task execution request. In this example, the application form includes: application number, ID of the target user, automatically read deployment method, reason for deployment application, deployment personnel, vehicle information, alarm receiving user scope (including username, contact number, etc. to receive alarms), and deployment period (long-term or temporary).

[0139] Furthermore, after the deployment conditions are approved, during the cross-cloud domain deployment service execution in City 2, the deployment conditions are returned to each cloud domain to instruct the target cloud domain to execute the deployment conditions. The return process is as follows: Figure 7 As shown.

[0140] Furthermore, after the deployment conditions are approved and returned to their respective cloud domains, City 2 executes the deployment service according to the conditions and sends the deployment results (i.e., execution results) to the target users in City 1 through different paths. These different paths are as follows: Figure 8 The path shown is Path 1, Path 2, or Path 3.

[0141] In the above embodiments, data resources include video data, equipment resources include video acquisition devices for acquiring video data, target devices are target video acquisition devices among video acquisition devices, and target data are target video data among video data.

[0142] For example, sending the execution result to the terminal device includes: when the target task is a first target task, sending the video data or the address of the video data collected by the target video acquisition device to the terminal device so that the terminal device can display the video data collected by the target video acquisition device; when the target task is a second target task, sending the processing result corresponding to the target video data to the terminal device so that the terminal device can display the processing result corresponding to the target video data.

[0143] In some embodiments, the permissions for executing tasks are mutually restricted between cloud domains at different levels. After the collaborative administrators of each cloud domain judge the accuracy and reasonableness of the application content, they will then perform the corresponding "approval of task execution request" or "rejection of target task request" operation.

[0144] In practical applications, both the first and second cloud domains are at the same level as the devices that collect data resources within the overall cloud domain structure, and therefore they usually belong to the same level of cloud domain.

[0145] The following section provides a detailed explanation of S52 in two application scenarios.

[0146] Scenario 1: The upper cloud domain corresponding to the first cloud domain and the upper cloud domain corresponding to the second cloud domain belong to different cloud domain structure scenarios. That is, the first cloud domain and the second cloud domain have the same level, but the upper cloud domains of the first cloud domain and the second cloud domain are different cloud domains.

[0147] like Figure 9 The method by which the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the second cloud domain is as follows.

[0148] S91, the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the upper-layer cloud domain of the first cloud domain.

[0149] S92, the collaborative service platform of the upper-layer cloud domain of the first cloud domain has approved the task execution request.

[0150] S93, the collaborative service platform of the upper-layer cloud domain of the first cloud domain sends the task execution request to the collaborative service platform of the upper-layer cloud domain of the second cloud domain.

[0151] Among them, the collaborative service platform of the upper cloud domain of the first cloud domain is used to approve task execution requests, and if the task execution request is approved, it forwards the task execution request to the collaborative service platform of the upper cloud domain of the second cloud domain.

[0152] S94, the collaborative service platform of the upper-layer cloud domain of the second cloud domain has approved the task execution request.

[0153] S95, the collaborative service platform of the second cloud domain received the task execution request.

[0154] In S94 and S95 above, the collaborative service platform of the upper-layer cloud domain of the second cloud domain is used to approve task execution requests, and forward the task execution request to the collaborative service platform of the second cloud domain if the task execution request is approved.

[0155] For example, the collaborative service platform of the first cloud domain sends a first request to the collaborative service platform of the upper-level cloud domain of the first cloud domain. The first request is used to request the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request. If the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-level cloud domain of the first cloud domain to send a second request to the collaborative service platform of the upper-level cloud domain of the second cloud domain. The second request is used to request the collaborative service platform of the upper-level cloud domain of the second cloud domain to approve the task execution request. If the collaborative service platform of the upper-level cloud domain of the second cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-level cloud domain of the second cloud domain to send the task execution request to the collaborative service platform of the second cloud domain.

[0156] Based on the above Figure 1 The hierarchical relationship of the cloud domains is described below. In this embodiment, the first cloud domain is interconnected with its upper-level cloud domain, but not with the upper-level cloud domain of its upper-level cloud domain. The second cloud domain is interconnected with its upper-level cloud domain, but not with the upper-level cloud domain of its upper-level cloud domain. Here, interconnection indicates that two cloud domains can establish communication to jointly perform a certain task.

[0157] Figure 1 The upper cloud domain of Level 3 cloud a (i.e., Level 2 cloud A) and the upper cloud domain of Level 3 cloud d (i.e., Level 2 cloud D) belong to different cloud domains of the same level, which conforms to the above scenario one.

[0158] For example, taking "the collaborative service platforms of each level of cloud domain as an integrated collaborative service platform" as an example, the task processing flow between each level of cloud domain in Scenario 1 is explained as follows: Each level of "cloud domain" registers the resources that its level of cloud domain can provide and the tasks that can be executed to its local integrated collaborative service platform. Level 3 cloud a sends the task execution request to the integrated collaborative service platform of Level 2 cloud A through Level 3 cloud a's integrated collaborative service platform; Level 2 cloud A's integrated collaborative service platform sends the task execution request to the integrated collaborative service platform of Level 2 cloud D; Level 2 cloud D's integrated collaborative service platform sends the task execution request to the integrated collaborative service platform of Level 3 cloud d.

[0159] In this implementation, for scenarios where the upper-layer cloud domains of the two cloud domains have different cloud domain structures, when the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the second cloud domain, the collaborative service platform of the second cloud domain can successfully receive the task execution request only if both the collaborative service platforms of the upper-layer cloud domains of the first and second cloud domains approve the task execution request.

[0160] Based on this, an approval process for task execution requests was implemented in different cloud domain scenarios for the two upper-layer cloud domains, ensuring that the task execution requests received by the collaborative service platform of the second cloud domain are approved by both upper-layer cloud domains, thereby guaranteeing the rationality of the target task execution process of the collaborative service platform of the second cloud domain.

[0161] Scenario 2: The first cloud domain and the second cloud domain are at the same level, and the upper-level cloud domain of the first cloud domain and the second cloud domain are the same cloud domain.

[0162] like Figure 10 The collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the second cloud domain in the following steps.

[0163] S101, the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the upper-layer cloud domain of the first cloud domain.

[0164] S102, the collaborative service platform of the upper-layer cloud domain of the first cloud domain has approved the task execution request.

[0165] S103, the collaborative service platform of the upper-layer cloud domain of the first cloud domain sends the task execution request to the collaborative service platform of the second cloud domain.

[0166] S104, the collaborative service platform of the upper-layer cloud domain of the second cloud domain receives the task execution request.

[0167] Among them, the collaborative service platform of the upper cloud domain of the first cloud domain is used to approve task execution requests, and forward the task execution requests to the collaborative service platform of the second cloud domain if the task execution requests are approved.

[0168] For example, a third request is sent to the collaborative service platform of the upper-layer cloud domain of the first cloud domain. The third request is used to request the collaborative service platform of the upper-layer cloud domain of the first cloud domain to approve the task execution request, and if the collaborative service platform of the upper-layer cloud domain of the first cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-layer cloud domain of the first cloud domain to send the task execution request to the second cloud domain.

[0169] Based on the above Figure 1 An introduction to the hierarchical relationship of the cloud domains shown. Figure 1 The upper cloud domain of Level 3 Cloud a (i.e., Level 2 Cloud A) and the upper cloud domain of Level 3 Cloud b (i.e., Level 2 Cloud A) belong to different cloud domains of the same level, which conforms to Scenario 2 above.

[0170] For example, taking "the collaborative service platform of each level of cloud domain as an integrated collaborative service platform" as an example, the task processing flow between each level of cloud domain in Scenario 2 is explained as follows.

[0171] Each level of "cloud domain" registers the resources and tasks it can provide with the local integrated collaborative service platform. Level 3 cloud a sends task execution requests to the integrated collaborative service platform of Level 2 cloud A through its integrated collaborative service platform; Level 2 cloud A's integrated collaborative service platform sends task execution requests to the integrated collaborative service platform of Level 3 cloud b.

[0172] In this implementation, for cloud domain structures where both cloud domains have the same upper-level cloud domain, when the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the second cloud domain, the second cloud domain's collaborative service platform can only receive the task execution request if the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the request. Based on this, an approval process for task execution requests is implemented in cloud domain scenarios where both cloud domains have the same upper-level cloud domain, ensuring that the task execution requests received by the collaborative service platform of the second cloud domain are approved by the same upper-level cloud domain, thereby guaranteeing the rationality of the target task execution process by the collaborative service platform of the second cloud domain.

[0173] The following explanations, using the first objective task as video retrieval as an example, will cover the task collaboration process in both scenario one and scenario two.

[0174] When the collaborative service platform of Level 3 Cloud B requests access to target video data on a target device from the collaborative service platform of Level 3 Cloud D under another Level 2 Cloud D, the administrator of Level 2 Cloud A must first approve the target task. After approval, the task execution request is transferred to the collaborative service platform of Level 2 Cloud D. After approval by the administrator of Level 2 Cloud D, the task is then transferred to the collaborative service platform of the target cloud domain: the collaborative service platform of Level 3 Cloud D. After approval by the administrator of Level 3 Cloud D, the target user of Level 3 Cloud B can see the target video data provided by Level 3 Cloud D in the local video application of the corresponding terminal device.

[0175] When the collaborative service platform of Level 3 Cloud B requests access to target video data on the target device from the collaborative service platform of Level 3 Cloud A under the same Level 2 Cloud A, the administrator of Level 2 Cloud A must first approve the target task. After approval, the task execution request will be transferred to the collaborative service platform of Level 3 Cloud A. After the administrator of Level 3 Cloud A approves the request, the target user of Level 3 Cloud B can see the target video data provided by the collaborative service platform of Level 3 Cloud A in the local video application of the corresponding terminal device.

[0176] Among them, the collaborative administrator of the collaborative service platform of the target cloud domain (Level 3 Cloud A or Level 3 Cloud D) also automatically identifies the target resources in order to set security and performance for the target resources. The specific settings are as follows: (1) Perform privacy masking on the target video data. For example, mask sensitive areas and sensitive personnel in the target video. (2) Configure whether preheating is required. For example, judge whether to perform stream preheating based on the load of the target resource forwarding service of the current cloud domain and the lower cloud domain. (3) Configure whether to configure watermark. For example, watermark content, watermark display form and watermark type can be set. The watermark content includes the requester's IP, MAC address, username and custom content. The watermark display form includes watermark position, watermark font, transparency, number of watermarks, watermark color, rotation angle, etc. The watermark type includes display watermark and implicit watermark. (4) Configure whether to bind the MAC / IP address of the target user. For example, bind the user's username (i.e., the target user's username) with the MAC or IP address to prevent unauthorized users from using the account to view videos across domains. (5) Configure the video data retrieval link. For example, the system default line can be used, or the user can manually adjust the retrieval line of the point. (6) Configure task management. For example, view the usage of resources and corresponding service resources by users and user groups across the entire domain, call the management plan and perform related controls, or manually intervene for emergency management.

[0177] In this way, the target user in Level 3 Cloud A obtains the URL (Uniform Resource Locator) for video data preview based on the cross-domain video capture device identifier in their local video application, and initiates a video retrieval task execution request. This request is then routed through the collaborative service platform of Level 3 Cloud B to the collaborative service platform of the target cloud domain, forwarding the video retrieval task to the corresponding video capture device in the target cloud domain, thus completing the cross-domain video retrieval task.

[0178] The following descriptions, using the second objective task as an example of cross-domain collaborative deployment, will explain the task collaboration process under both scenario one and scenario two.

[0179] The target users of Level 3 Cloud b can obtain a list of cloud domains that can provide cross-domain collaborative deployment services through the application corresponding to the local integrated collaborative service platform. They can then select the target cloud domain for collaborative deployment and enter the cross-domain collaborative deployment conditions on the displayed collaborative deployment page to form the preset rules for the cross-domain collaborative deployment task.

[0180] When the collaborative service platform of Level 3 Cloud B requests cross-domain collaborative deployment from the collaborative service platform of Level 3 Cloud D under another Level 2 Cloud D, the administrator of Level 2 Cloud A must first approve the target task. After approval, the task execution request is transferred to Level 2 Cloud D. After the administrator of Level 2 Cloud D approves it, the task is then transferred to the collaborative service platform of the target cloud domain: the collaborative service platform of Level 3 Cloud D. After the administrator of Level 3 Cloud D approves it, the collaborative service platform of Level 3 Cloud D can execute the cross-domain collaborative deployment task.

[0181] When the collaborative service platform of Level 3 Cloud B requests cross-domain collaborative deployment from the collaborative service platform of Level 3 Cloud A under the same Level 2 Cloud A, the administrator of Level 2 Cloud A must first approve the target task. After approval, the task execution request will be transferred to the collaborative service platform of Level 3 Cloud A. After the administrator of Level 3 Cloud A approves the task, the collaborative service platform of Level 3 Cloud A can execute the cross-domain collaborative deployment task.

[0182] The collaborative service platform of the target cloud domain can read the collaborative deployment conditions through the integrated collaborative service platform of the target cloud domain, and respond to the cross-domain collaborative deployment task based on the deployment capabilities that the target cloud domain can provide.

[0183] For example, a cross-domain collaborative deployment task execution request may include deployment for facial recognition, vehicle recognition, and ID card recognition respectively. However, if the target cloud domain only has the capability for facial recognition deployment, it can only report the execution result of facial recognition deployment, without reporting the execution results of vehicle recognition deployment and ID card recognition deployment. The invoked target cloud domain allocates the cross-domain collaborative deployment task to the edge and terminal of the target cloud domain for execution based on the resource situation of the target cloud domain, and feeds back the execution result of the cross-domain collaborative deployment to the terminal device corresponding to the target user who initiated the cross-domain collaborative deployment task through the integrated collaborative service platform, so that the target user can see the cross-domain collaborative deployment execution result reported by the cross-domain on the application of the terminal device.

[0184] As one possible implementation, the collaborative service platform of the first cloud domain can also collaborate with other cloud domains to perform tasks based on the resources of the first cloud domain. For example... Figure 11 As shown, taking the third cloud domain as a lower-level cloud domain of the first cloud domain or a cloud domain at the same level as the first cloud domain as an example, the following explanation is given on how the collaborative service platform of the first cloud domain collaboratively completes the execution request of the task to be executed initiated by the user on the terminal device in the third cloud domain.

[0185] S111, the collaborative service platform of the first cloud domain receives the execution request sent by the collaborative service platform of the third cloud domain.

[0186] The execution request sent by the collaborative service platform of the third cloud domain is used to instruct the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain to execute the pending task generated by the third cloud domain.

[0187] S112, when the third cloud domain and the first cloud domain correspond to the same level, the collaborative service platform of the first cloud domain responds to the acceptance instruction for the execution request entered by the management account of the first cloud domain, and uses the resources registered by the collaborative service platform of the first cloud domain to execute the task to be executed.

[0188] S113, when the level of the third cloud domain is the same as the level of the lower cloud domain of the first cloud domain, the collaborative service platform of the first cloud domain responds to the acceptance instruction for the execution request input by the management account of the first cloud domain and sends the execution request to the collaborative service platform of the lower cloud domain of the first cloud domain.

[0189] In detail, when the third cloud domain cannot complete the task to be executed, the collaborative service platform of the third cloud domain sends an execution request to the collaborative service platform of the cloud domain that can complete the task (i.e., the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain), so that the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain executes the execution request. Because the third cloud domain and the first cloud domain are located in different hierarchical structures, their processes for executing the task are also different.

[0190] For example, in a scenario where the first cloud domain receives a task execution request from a cloud domain at the same level, that is, when the third cloud domain and the first cloud domain are at the same level, the execution request needs to be approved by both the collaborative service platform of the upper-level cloud domain of the third cloud domain and the collaborative service platform of the upper-level cloud domain of the first cloud domain before the collaborative service platform of the first cloud domain will receive the execution request and call the resources registered by the collaborative service platform of the first cloud domain to execute the task to be executed.

[0191] In another example, in a scenario where the first cloud domain receives a task execution request from a lower-level cloud domain—that is, when the third cloud domain and the lower-level cloud domain of the first cloud domain are at the same level—after the collaborative service platform of the upper-level cloud domain of the third cloud domain approves the execution request, the collaborative service platform of the first cloud domain receives the execution request, approves it, and after approval, sends the execution request to the collaborative service platform of the lower-level cloud domain of the first cloud domain, so that the collaborative service platform of the lower-level cloud domain of the first cloud domain can execute the task to be executed in the third cloud domain according to the resources registered by the collaborative service platform of the lower-level cloud domain of the first cloud domain.

[0192] This implementation method can process the execution request according to different task processing flows based on the different hierarchical relationships of the cloud domain hierarchy between the third cloud domain and the first cloud domain, so that the cloud domain that matches the resources required by the task to be executed can cooperate with the third cloud domain to execute the task to be executed. This enables the use of resources registered on the collaborative service platform of the first cloud domain or resources registered on the collaborative service platform of the lower-level cloud domain of the first cloud domain to collaboratively complete the task to be executed in the third cloud domain.

[0193] In one implementation, the aforementioned target task can also issue alerts for target events. The following is an example... Figure 12 The flowchart illustrating a multi-dimensional sensing intelligent connectivity method details the process by which a collaborative service platform in a second cloud domain collaborates with a first cloud domain to execute a target task. The multi-dimensional sensing intelligent connectivity method provided in this application can be applied to the aforementioned... Figure 3 and Figure 4 The collaborative service platform for the target cloud domain in the implementation architecture shown.

[0194] It should be noted that the collaborative service platform of the target cloud domain executes the target task initiated by users of other cloud domains through this multi-dimensional perception and intelligent connection method. The collaborative service platform of the target cloud domain can also execute tasks initiated by users of the target cloud domain with the same task requirements as the target task through this multi-dimensional perception and intelligent connection method. The execution steps are the same for both. To avoid repetition, the following will not elaborate on different scenarios for initiating tasks.

[0195] S121, the collaborative service platform of the second cloud domain receives the first task request sent by the first cloud domain.

[0196] The first task request mentioned above can be understood as an example of a task execution request in the above embodiments.

[0197] The first task request is used to instruct the second cloud domain to use the target alarm device to alarm the target event; the target alarm device is determined by the first cloud domain based on the device resource information of the second cloud domain registered on the first cloud domain.

[0198] S122, the collaborative service platform of the second cloud domain receives the alarm signal sent by the first edge domain.

[0199] The alarm signal is sent by the target alarm device to the first edge domain when it detects a target event occurring in the alarm area corresponding to the target alarm device.

[0200] S123, send an alarm signal to the first cloud domain.

[0201] It should be noted that this method is applied to a system that includes end devices, edge domains, and cloud domains. End devices include target alarm devices, which belong to the device resources of the first edge domain. Cloud domains include a first cloud domain and a second cloud domain, and the target alarm devices belong to the device resources of the second cloud domain. The first cloud domain can be any cloud domain other than the second cloud domain. Each cloud domain corresponds one-to-one with the collaborative service platform.

[0202] Before step S121, the collaborative service platform of the second cloud domain can also complete resource information registration. Specifically, it first sends a resource information registration request to the collaborative service platform of any other cloud domain; this resource information registration request is used to instruct the collaborative service platform of any other cloud domain to register its resource information on the collaborative service platform of the second cloud domain. Then, it associates the resource information returned by the collaborative service platform of any other cloud domain with the cloud domain identifier of any other cloud domain to complete the registration of the resource information of the collaborative service platform of any other cloud domain on the collaborative service platform of the second cloud domain.

[0203] As one implementation, the terminal device also includes a data acquisition device, which belongs to the device resources of the second cloud domain; the target alarm device is pre-associated with a target master data acquisition device and a target slave data acquisition device. Before performing the above step S123, such as Figure 13 As shown, the collaborative service platform of the second cloud domain can also implement the following steps to achieve alerts for target events:

[0204] Step S131: Determine the target acquisition device from the target main acquisition device, the target slave acquisition device, and other acquisition devices around the alarm area.

[0205] Step S132: Send an information acquisition command to the target acquisition device.

[0206] The information acquisition command instructs the target acquisition device to acquire images of the alarm area.

[0207] Step S133: Determine whether the target event is a preset alarm event based on the event information of the target event in the image acquired by the target acquisition device.

[0208] Step S134: If the target event is a preset alarm event, then an alarm is triggered on the target event and an alarm signal is sent to the first cloud domain.

[0209] In this embodiment, when the first edge domain of the target cloud domain receives an alarm signal, it first determines the target alarm device that sent the alarm signal and the target acquisition device associated with the target alarm device; then it calls the associated target acquisition device to acquire an image of the alarm area to determine the event information of the target event that occurred in the alarm area, and then determines whether to issue an alarm for the target event based on the event information.

[0210] In this implementation method, after an alarm signal is generated, an alarm prompt message is not sent directly. Instead, the target event is reviewed based on the event information determined by the target acquisition device to ignore alarm signals caused by invalid target events. For alarm signals caused by valid target events, an alarm prompt message is sent to prompt the user to handle the target event. This way, the user no longer needs to handle invalid target events, saving user time and improving the efficiency of the user in handling target events.

[0211] As one implementation method for determining whether a target event is a preset alarm event, if the type of the target object belongs to a preset type, the target event is determined to be a preset alarm event. If the type of the target object does not belong to a preset type, the target event is determined to be a non-preset alarm event. Here, the target event is defined as the target object being within the alarm area, and the event information includes the type of the target object.

[0212] For example, taking a preset type of "person" as an example, if the target object is of type "person", then the target time is determined to be a preset alarm event and the target event is a pending alarm event. If the target object is of type "object", then the target event is determined to be a non-preset alarm event and the target event does not need to be alarmed to the user. The user is the user who is preparing to process the alarm event.

[0213] In this implementation, invalid target events caused by a preset type of target object are hidden without prompting the user to handle them, thereby reducing the number of target events caused by invalid target objects received by the user and improving the effectiveness and accuracy of the alarm.

[0214] As one implementation method, step S131 can be specifically implemented in the following way: if the target master acquisition device is in an idle state, then the target master acquisition device is determined to be the target acquisition device; if the target master acquisition device is in a non-idle state and the target slave acquisition device is in an idle state, then the target slave acquisition device is determined to be the target acquisition device; if both the target master acquisition device and the target slave acquisition device are in a non-idle state, then the target acquisition device is determined based on the distance between other acquisition devices and the target alarm device and the working status of other acquisition devices.

[0215] Among them, the distance between each acquisition device associated with the target alarm device and the alarm area is less than the preset distance.

[0216] Specifically, the target alarm device is pre-associated with corresponding target master acquisition devices and target slave acquisition devices. When the target alarm device issues an alarm signal, it calls the pre-associated target master acquisition device and target slave acquisition device. If the pre-associated target master acquisition device is not idle, the target slave acquisition device in an idle state is called as the target acquisition device. If the target slave acquisition device is also not idle, other non-working acquisition devices within a preset range are called to collect data on the alarm area.

[0217] For example, an idle acquisition device is identified as a candidate acquisition device; the candidate acquisition device with the smallest distance from the alarm area is identified as the target acquisition device.

[0218] In one implementation, the device resources of the first edge domain include multiple alarm devices, which are distributed on the first edge domain at preset intervals, and each alarm device corresponds one-to-one with a main acquisition device. The target slave acquisition device is determined in the following way: Specifically, a preset number of alarm devices continuously distributed with the target alarm device are selected as candidate alarm devices; then, the main acquisition device corresponding to the candidate alarm device is determined as the target slave acquisition device of the target alarm device.

[0219] For example, taking a vibration fiber optic alarm device and a PTZ camera as the acquisition device, the relationship between the alarm device and the acquisition device is explained as follows.

[0220] Specifically, a vibrating optical fiber is divided into multiple units at equal intervals, meaning a vibrating optical fiber comprises multiple vibrating optical fiber units. Each vibrating optical fiber unit corresponds to a PTZ camera as the master acquisition device; that is, a master PTZ camera is positioned relative to each vibrating optical fiber unit. Each vibrating optical fiber unit also corresponds to a different unit number, typically arranged according to the positional distribution of the various vibrating optical fiber units. For example, if a vibrating optical fiber is divided into 500 vibrating optical fiber units, their corresponding numbers are 1, 2, 3…500. Hereinafter, vibrating optical fiber units numbered 1 to 500 will be referred to as vibrating optical fiber unit 1 to vibrating optical fiber unit 500. If one vibrating optical fiber unit corresponds to 10 slave PTZ cameras, then the slave PTZ cameras associated with each vibrating optical fiber unit are the master PTZ cameras of the 10 other vibrating optical fiber units with consecutive numbers. For example, the 10 slave PTZ cameras associated with vibrating optical fiber unit 1 are the master PTZ cameras corresponding to vibrating optical fiber units 2 through 11, respectively. For example, the 10 slave PTZ cameras associated with the vibration fiber unit 2 are: the master PTZ cameras corresponding to vibration fiber unit 2, vibration fiber unit 3 to vibration fiber unit 11 respectively.

[0221] As an alarm method, the above S134 can be implemented in the following way: when multiple target events are determined to be preset alarm events within a preset time period, the multiple target events are deduplicated according to the event information of each target event, and at least one target event is obtained after deduplication; an alarm is issued according to the at least one target event obtained after deduplication.

[0222] As an example of an alarm method, based on the information of the target object corresponding to each of multiple target events, target events with the same target object are merged into one target event. Here, a target event is defined as one where the target object is within the alarm area, and the event information of the target event includes the target object's information.

[0223] In this example, it can be determined that the target objects of multiple target events are the same in the following way: the information of the target object includes the similarity between the target object and the preset object; if the similarity between the target objects corresponding to two or more target events and the same preset object is greater than or equal to the similarity threshold, the target objects corresponding to the two or more target events are the same.

[0224] In some implementations, the information of the preset object is obtained from a preset object library. The preset object corresponding to the target object is determined based on the preset object information. If the information of the target object is not available for a corresponding preset object, the preset object library is updated based on the target object information to generate new preset object information.

[0225] Optionally, if the information of the target object cannot be obtained from the corresponding preset object information, if the information of the target object matches the preset licensed object information, the information of the target object will not be updated to the preset object repository; if the information of the target object does not match the preset licensed object information, the information of the target object will be updated to the preset object repository.

[0226] For example, if the matching degree between the image of the target object and the image of the whitelisted objects is determined to be greater than a matching threshold, then the image of the target object will not be updated to the preset object repository. If the matching degree between the image of the target object and the image of the whitelisted objects is determined to be less than or equal to the matching threshold, then the image of the target object will be updated to the preset object repository.

[0227] In some implementations, the target acquisition device is a spherical imaging device. This spherical imaging device is also called a PTZ camera.

[0228] To ensure that the target acquisition device can detect event information in the alarm area, the accurate information acquisition range is determined in the following ways, and the operating parameters of the target acquisition device are adjusted in the following ways: Based on the position of the spherical imaging device and the position of the alarm area, the operating parameters of the spherical imaging device are determined, including the horizontal angle, vertical angle, and zoom magnification of the spherical imaging device; the operating parameters are then sent to the spherical imaging device so that it can acquire images of the alarm area based on the operating parameters.

[0229] As a specific implementation method for determining operating parameters: First, determine the latitude and longitude coordinates B(B) of the alarm location on the alarm device based on the alarm area. w B j ), and obtain the latitude and longitude coordinates A(A) of the PTZ camera's location. w A j Then, determine the horizontal angle, vertical angle, and zoom level of the spherical imaging device according to the following formulas.

[0230] (1) Determine the horizontal angle P of the spherical shooting device.

[0231] Based on the spherical cosine theorem, cos(c)=cos(a)×cos(b)+sin(a)×sin(b)×cos(C) Formula (1)

[0232] Where ∠a=90-B w ; ∠b=90-A w ;∠C=B j -A j Substituting into formula (1), we get:

[0233] ∠c=arccos(cos(90-B w )×cos(90-A w )+sin(90-B w )×sin(90-A w )×cos(B j -A j ))Formula (2)

[0234] According to the sine law for a sphere, the value of ∠A can be obtained as follows:

[0235]

[0236] The horizontal angle of the PTZ camera pointing north is: P = ∠A – α (Formula 4)

[0237] Wherein, the PTZ camera is at an angle α with the north direction; B w B represents the longitude coordinates of the alarm location. j A represents the latitude and longitude coordinates of the alarm location. wThe longitude coordinates of the PTZ camera's location; A j The coordinates of the PTZ camera's position are latitude and longitude.

[0238] (2) Determine the vertical angle T

[0239] The distance between the ground projection point B' of the latitude and longitude coordinates A of the PTZ camera's position and the latitude and longitude coordinates B of the alarm position is LAB.

[0240]

[0241]

[0242] Wherein, the height difference between point B and B' is LBB′h2-h1, ∠BB′A is approximately 90°, the position of the PTZ camera is at a height of h1 above the ground, and the alarm position on the alarm device is at a height of h2 above the ground.

[0243] (3) Determine the zoom ratio Z of the PTZ camera.

[0244] Based on the direct proportional relationship between the zoom factor of the PTZ camera and the target distance LAB, the zoom factor Z of the PTZ camera is determined by the following formula (7).

[0245]

[0246] Where k and b are known constants.

[0247] To achieve the above functions, the multi-cloud domain task processing device and alarm device include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art will readily recognize that, based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0248] This disclosure also provides an embodiment such as Figure 14 The multi-cloud domain task processing device 10 shown has each cloud domain corresponding to a collaborative service platform. The collaborative service platform of the first cloud domain registers resource information for each cloud domain, including one or more of the following: device resource information, data resource information, and service resource information. The device includes: a determining unit 111, a sending unit 112, and a receiving unit 113.

[0249] The determining unit is configured to determine a second cloud domain from multiple cloud domains based on the target task and the resource information corresponding to each cloud domain in multiple cloud domains. The resources of the second cloud domain include target resources used to implement the target task. The resource information of different cloud domains corresponds to different resources. The sending unit 112 is configured to send a task execution request to the collaborative service platform of the second cloud domain. The task execution request is used to request the collaborative service platform of the second cloud domain to execute the target task based on the target resources. The receiving unit 113 is configured to receive the execution result of the target task returned by the collaborative service platform of the second cloud domain. The execution result is sent when the collaborative service platform of the second cloud domain accepts the task execution request.

[0250] In one possible implementation, the determining unit 111 is further configured to send a resource information registration request to the collaborative service platform of any other cloud domain; the resource information registration request is used to indicate that the resource information of the collaborative service platform of any other cloud domain is registered on the collaborative service platform of the first cloud domain; the determining unit 111 is further configured to associate the resource information returned by the collaborative service platform of any other cloud domain with the cloud domain identifier of any other cloud domain, so as to complete the registration of the resource information of the collaborative service platform of any other cloud domain on the collaborative service platform of the first cloud domain.

[0251] In one possible implementation, the determining unit 111 is specifically configured to perform the following actions: determining a target service for serving the target task based on the target task initiated by the terminal device of the target user in the first cloud domain; determining a first candidate cloud domain from multiple cloud domains based on the service resource information of multiple cloud domains registered on the collaborative service platform of the first cloud domain, wherein the service resources of the first candidate cloud domain include the target service; and determining a second cloud domain from the first candidate cloud domain.

[0252] In one possible implementation, the sending unit 112 is specifically configured to: determine the target data resources and / or target device resources associated with the target task in the second cloud domain; determine the target user associated with the target task in the first cloud domain; and send a task execution request carrying the target data resources and / or target device resources, as well as the target user, to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the target data resources and / or target device resources.

[0253] In one possible implementation, the sending unit 112 is further specifically configured to determine the condition information associated with the target service; send a task execution request carrying the condition information to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the condition information.

[0254] In one possible implementation, the first cloud domain and the second cloud domain correspond to the same level, and the upper-level cloud domains of the first cloud domain and the second cloud domain are different cloud domains; the sending unit 112 is further specifically configured to send a first request to the collaborative service platform of the upper-level cloud domain of the first cloud domain. The first request is used to request the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request, and if the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, instruct the collaborative service platform of the upper-level cloud domain of the first cloud domain to send a second request to the collaborative service platform of the upper-level cloud domain of the second cloud domain. The second request is used to request the collaborative service platform of the upper-level cloud domain of the second cloud domain to approve the task execution request, and if the collaborative service platform of the upper-level cloud domain of the second cloud domain approves the task execution request, instruct the collaborative service platform of the upper-level cloud domain of the second cloud domain to send a task execution request to the collaborative service platform of the second cloud domain.

[0255] In one possible implementation, the first cloud domain and the second cloud domain correspond to the same level, and the upper-level cloud domains of the first cloud domain and the second cloud domain are the same cloud domain; the sending unit 112 is further specifically configured to send a third request to the collaborative service platform of the upper-level cloud domain of the first cloud domain, the third request being used to request the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request, and, if the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, instruct the collaborative service platform of the upper-level cloud domain of the first cloud domain to send the task execution request to the second cloud domain.

[0256] In one possible implementation, the receiving unit 113 is further configured to receive an execution request sent by a collaborative service platform of a third cloud domain, wherein the third cloud domain is a lower-level cloud domain of the first cloud domain or a cloud domain at the same level as the first cloud domain. The execution request sent by the collaborative service platform of the third cloud domain instructs the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain to execute the task to be executed generated by the third cloud domain. If the third cloud domain is at the same level as the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, the unit executes the task to be executed using the resources registered by the collaborative service platform of the first cloud domain. If the level of the third cloud domain is the same as the level of the lower-level cloud domain of the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, the unit sends an execution request to the collaborative service platform of the lower-level cloud domain of the first cloud domain.

[0257] This disclosure also provides an embodiment such as Figure 15 The multi-dimensional sensing intelligent interconnection device 13 shown includes: an instruction receiving unit 131, an instruction sending unit 132, an alarm unit 133, and an acquisition unit 134.

[0258] The instruction receiving unit 131 is configured to receive a first task request sent by a first cloud domain; wherein the first task request is used to instruct a second cloud domain to use a target alarm device to alarm a target event; the target alarm device is determined by the first cloud domain based on the device resource information registered by the second cloud domain on the first cloud domain; wherein the end device includes the target alarm device, and the target alarm device belongs to the device resource of the first edge domain; the cloud domain includes the first cloud domain and the second cloud domain, and the target alarm device belongs to the device resource of the second cloud domain; the first cloud domain is any cloud domain other than the second cloud domain; each cloud domain corresponds one-to-one with the collaborative service platform; the instruction receiving unit 131 is also configured to receive an alarm signal sent by the first edge domain; the alarm signal is sent by the target alarm device to the first edge domain when it detects a target event occurring in the alarm area corresponding to the target alarm device; the alarm unit 133 is configured to send an alarm signal to the first cloud domain.

[0259] In one possible implementation, the instruction sending unit 132 is configured to send a resource information registration request to the collaborative service platform of any other cloud domain; the resource information registration request is used to indicate that the resource information of the collaborative service platform of any other cloud domain is registered on the collaborative service platform of the second cloud domain; the instruction sending unit 132 is also configured to associate the resource information returned by the collaborative service platform of any other cloud domain with the cloud domain identifier of any other cloud domain, so as to complete the registration of the resource information of the collaborative service platform of any other cloud domain on the collaborative service platform of the second cloud domain.

[0260] In another possible implementation, the target alarm device is pre-associated with a target master acquisition device and a target slave acquisition device; the device also includes an acquisition unit 134 and an alarm unit 133. The acquisition unit 134 is configured to identify the target acquisition device from among the target master acquisition device, the target slave acquisition device, and other acquisition devices around the alarm area in the first edge domain; wherein, the end device also includes an acquisition device, which belongs to the device resources of the second cloud domain; the acquisition unit 134 is configured to send an information acquisition command to the target acquisition device from the first edge domain, the information acquisition command instructing the target acquisition device to acquire images of the alarm area; the acquisition unit 134 is also configured to determine whether the target event is a preset alarm event based on the event information of the target event in the image acquired by the target acquisition device; the alarm unit 133 is configured to, if the target event is a preset alarm event, then the first edge domain alarms the target event and sends an alarm signal to the first cloud domain.

[0261] In another possible implementation, the acquisition unit 134 is specifically configured to determine the target master acquisition device as the target acquisition device if the target master acquisition device is in an idle state; determine the target slave acquisition device as the target acquisition device if the target master acquisition device is in a non-idle state and the target slave acquisition device is in an idle state; and determine the target acquisition device based on the distance between other acquisition devices and the target alarm device, as well as the working status of other acquisition devices, if both the target master acquisition device and the target slave acquisition device are in a non-idle state.

[0262] In another possible implementation, the acquisition unit 134 is further specifically configured to: select a preset number of alarm devices that are continuously distributed with the target alarm device as candidate alarm devices; determine a preset number of master acquisition devices associated with the candidate alarm devices as target slave acquisition devices of the target alarm device; and determine the target acquisition device based on the working status of other acquisition devices, wherein the device resources of the first edge domain include multiple alarm devices, the multiple alarm devices are distributed on the first edge domain at a preset interval, and the alarm devices correspond one-to-one with the master acquisition devices.

[0263] In another possible implementation, the acquisition unit 134 is further configured to determine the operating parameters of the spherical imaging device based on the latitude and longitude of the spherical imaging device, the height of the spherical imaging device, its position relative to the alarm area, and the installation height of the target alarm device. The operating parameters include the horizontal angle, vertical angle, and zoom level of the spherical imaging device. The operating parameters are then sent to the spherical imaging device so that the spherical imaging device can acquire an image of the alarm area based on the operating parameters. The target acquisition device is the spherical imaging device.

[0264] Regarding the apparatus in the above embodiments, the specific manner in which each unit module performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0265] Figure 16 This is a schematic diagram of an electronic device provided in this disclosure. (For example...) Figure 16 The electronic device 50 may include at least one processor 501 and a memory 503 for storing processor-executable instructions. The processor 501 is configured to execute the instructions in the memory 503 to implement the multi-cloud domain task processing method described in the following embodiments.

[0266] In addition, electronic device 50 may also include communication bus 502, at least one communication interface 504, input device 506 and output device 505.

[0267] Processor 501 may be a processor (central processing unit, CPU), microprocessor unit, ASIC, or one or more integrated circuits for controlling the execution of programs according to the present disclosure.

[0268] The communication bus 502 may include a path for transmitting information between the aforementioned components.

[0269] Communication interface 504 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0270] Input device 506 is used to receive input signals and output device 505 is used to output signals.

[0271] Memory 503 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory may exist independently and be connected to the processing unit via a bus. Memory may also be integrated with the processing unit.

[0272] The memory 503 stores instructions for executing the present invention, and the processor 501 controls the execution of these instructions. The processor 501 executes the instructions stored in the memory 503 to implement the functions of the method disclosed herein.

[0273] In a specific implementation, as one example, the processor 501 may include one or more CPUs, for example... Figure 16 CPU0 and CPU1 in the CPU.

[0274] In a specific implementation, as one example, the electronic device 10 may include multiple processors, such as... Figure 12Processors 501 and 507 are shown in the diagram. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here can refer to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).

[0275] The electronic device is as follows Figure 16 The diagram includes a processor 501 and a memory 503 for storing executable instructions of the processor 501. The processor 501 is configured to execute the executable instructions to implement a multi-cloud domain task processing method or a multi-dimensional sensing and intelligent connectivity method based on edge-cloud as described in any of the possible embodiments above. Furthermore, it achieves the same technical effect, and to avoid repetition, it will not be described in detail here.

[0276] This disclosure also provides a computer-readable storage medium, which, when executed by a processor of an electronic device, enables the electronic device to perform a multi-cloud domain task processing method or a multi-dimensional sensing and intelligent connectivity method based on edge-cloud as described in any of the possible embodiments above. The same technical effects can be achieved, and to avoid repetition, further details are omitted here.

[0277] This disclosure also provides a computer program product, including a computer program or instructions, which are executed by a processor as a multi-cloud domain task processing method or an edge-cloud based multi-dimensional sensing and intelligent connectivity method according to any of the possible implementations described above. These methods achieve the same technical effects, and to avoid repetition, they will not be described again here.

[0278] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0279] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A multi-cloud domain task processing method, characterized in that, The collaborative service platform is applied to the first cloud domain. Each cloud domain corresponds to the collaborative service platform. The collaborative service platform of the first cloud domain is registered with the resource information of each cloud domain. The resource information includes one or more of the following: device resource information, data resource information, and service resource information. The first cloud domain is any one of the cloud domains, and the method includes: Based on the target task initiated by the terminal device of the target user in the first cloud domain, determine the target service used to serve the target task; Based on the service resource information of multiple cloud domains registered on the collaborative service platform of the first cloud domain, a first candidate cloud domain is determined from the multiple cloud domains, and the service resources of the first candidate cloud domain include the target service; A second cloud domain is determined from the first candidate cloud domains, and the resources of the second cloud domain include target resources for implementing the target task; the resource information of different cloud domains corresponds to different resources; Send a task execution request to the collaborative service platform of the second cloud domain; Receive the execution result of the target task returned by the collaborative service platform of the second cloud domain, wherein the execution result is sent by the collaborative service platform of the second cloud domain upon accepting the task execution request; The step of sending a task execution request to the collaborative service platform of the second cloud domain includes: Identify the target data resources and / or target device resources in the second cloud domain that are associated with the target task; Send a task execution request carrying the target data resources and / or target device resources to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the target data resources and / or target device resources.

2. The task processing method according to claim 1, characterized in that, Before determining the second cloud domain from the multiple cloud domains based on the target task and the resource information corresponding to each cloud domain, the process includes: Send a resource information registration request to the collaborative service platform of any other cloud domain; the resource information registration request is used to indicate that the resource information of the collaborative service platform of any other cloud domain is registered on the collaborative service platform of the first cloud domain. The resource information returned by the collaborative service platform of any other cloud domain is associated with the cloud domain identifier of any other cloud domain to complete the registration of the resource information of the collaborative service platform of any other cloud domain on the collaborative service platform of the first cloud domain.

3. The task processing method according to claim 1, characterized in that, Sending the task execution request to the collaborative service platform of the second cloud domain further includes: Determine the condition information associated with the target service; A task execution request carrying the condition information is sent to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the condition information.

4. The task processing method according to any one of claims 1 to 3, characterized in that, The first cloud domain and the second cloud domain correspond to the same level, but the upper-level cloud domains of the first cloud domain and the second cloud domain are different cloud domains. Sending the task execution request to the collaborative service platform of the second cloud domain includes: A first request is sent to the collaborative service platform of the upper-layer cloud domain of the first cloud domain. The first request is used to request the collaborative service platform of the upper-layer cloud domain of the first cloud domain to approve the task execution request. If the collaborative service platform of the upper-layer cloud domain of the first cloud domain approves the task execution request, it is instructed to send a second request to the collaborative service platform of the upper-layer cloud domain of the second cloud domain. The second request is used to request the collaborative service platform of the upper-layer cloud domain of the second cloud domain to approve the task execution request. If the collaborative service platform of the upper-layer cloud domain of the second cloud domain approves the task execution request, it is instructed to send the task execution request to the collaborative service platform of the upper-layer cloud domain of the second cloud domain.

5. The task processing method according to any one of claims 1 to 3, characterized in that, The first cloud domain and the second cloud domain correspond to the same level, and the upper-level cloud domain of the first cloud domain and the second cloud domain is the same cloud domain. Sending the task execution request to the collaborative service platform of the second cloud domain includes: A third request is sent to the collaborative service platform of the upper-level cloud domain of the first cloud domain. The third request is used to request the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request. If the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-level cloud domain of the first cloud domain to send the task execution request to the second cloud domain.

6. The task processing method according to any one of claims 1 to 3, characterized in that, The method further includes: The system receives an execution request sent by a collaborative service platform of a third cloud domain, wherein the third cloud domain is a lower-level cloud domain of the first cloud domain or a cloud domain at the same level as the first cloud domain. The execution request sent by the collaborative service platform of the third cloud domain instructs the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain to execute the task to be executed generated by the third cloud domain. When the third cloud domain corresponds to the same level as the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, the task to be executed is executed using the resources registered by the collaborative service platform of the first cloud domain. If the level of the third cloud domain is the same as the level of the lower cloud domain of the first cloud domain, in response to receiving the acceptance instruction for the execution request input by the management account of the first cloud domain, the execution request is sent to the collaborative service platform of the lower cloud domain of the first cloud domain.

7. A multi-cloud domain task processing device, characterized in that, Each cloud domain corresponds one-to-one with a collaborative service platform. The collaborative service platform of the first cloud domain registers resource information for each cloud domain. The resource information includes one or more of the following: device resource information, data resource information, and service resource information. The device includes: The determining unit is configured to: determine a target service for serving the target task initiated by a terminal device of a target user in the first cloud domain; determine a first candidate cloud domain from the multiple cloud domains based on service resource information of multiple cloud domains registered on the collaborative service platform of the first cloud domain, wherein the service resources of the first candidate cloud domain include the target service; determine a second cloud domain from the first candidate cloud domain, wherein the resources of the second cloud domain include target resources for implementing the target task; the resource information of different cloud domains corresponds to different resources; The sending unit is configured to send a task execution request to the collaborative service platform of the second cloud domain; The receiving unit is configured to receive the execution result of the target task returned by the collaborative service platform of the second cloud domain, wherein the execution result is sent by the collaborative service platform of the second cloud domain upon accepting the task execution request; The step of sending a task execution request to the collaborative service platform of the second cloud domain includes: Identify the target data resources and / or target device resources in the second cloud domain that are associated with the target task; Send a task execution request carrying the target data resources and / or target device resources to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the target data resources and / or target device resources.

8. The task processing apparatus according to claim 7, characterized in that, The task processing device is also configured to: The determining unit is further configured to send a resource information registration request to the collaborative service platform of any other cloud domain; the resource information registration request is used to indicate that the resource information of the collaborative service platform of any other cloud domain is registered on the collaborative service platform of the first cloud domain. The determining unit is further configured to associate the resource information returned by the collaborative service platform of the other cloud domain with the cloud domain identifier of the other cloud domain, so as to complete the registration of the resource information of the collaborative service platform of the other cloud domain on the collaborative service platform of the first cloud domain. The sending unit is further specifically configured to perform the determination of condition information associated with the target service; Send a task execution request carrying the condition information to the collaborative service platform of the second cloud domain; the task execution request is used to request the collaborative service platform of the second cloud domain to execute the target service based on the condition information; The sending unit is further specifically configured to send a first request to the collaborative service platform of the upper-level cloud domain of the first cloud domain. The first request requests the collaborative service platform of the upper-level cloud domain of the first cloud domain to approve the task execution request. If the collaborative service platform of the upper-level cloud domain of the first cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-level cloud domain of the first cloud domain to send a second request to the collaborative service platform of the upper-level cloud domain of the second cloud domain. The second request requests the collaborative service platform of the upper-level cloud domain of the second cloud domain to approve the task execution request. If the collaborative service platform of the upper-level cloud domain of the second cloud domain approves the task execution request, it instructs the collaborative service platform of the upper-level cloud domain of the second cloud domain to send the task execution request to the collaborative service platform of the second cloud domain. Wherein, the first cloud domain and the second cloud domain correspond to the same level, and the upper-level cloud domains of the first cloud domain and the second cloud domain are different cloud domains. The sending unit is further specifically configured to send a third request to the collaborative service platform of the upper-layer cloud domain of the first cloud domain. The third request is used to request the collaborative service platform of the upper-layer cloud domain of the first cloud domain to approve the task execution request, and, if the collaborative service platform of the upper-layer cloud domain of the first cloud domain approves the task execution request, instruct the collaborative service platform of the upper-layer cloud domain of the first cloud domain to send the task execution request to the second cloud domain; wherein the first cloud domain and the second cloud domain correspond to the same level, and the upper-layer cloud domain of the first cloud domain and the second cloud domain are the same cloud domain; The receiving unit is further configured to receive an execution request sent by a collaborative service platform of a third cloud domain, wherein the third cloud domain is a lower-level cloud domain of the first cloud domain or a cloud domain at the same level as the first cloud domain. The execution request sent by the collaborative service platform of the third cloud domain instructs the collaborative service platform of the first cloud domain or the collaborative service platform of the lower-level cloud domain of the first cloud domain to execute the task to be executed generated by the third cloud domain. If the third cloud domain is at the same level as the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, the receiving unit executes the task to be executed using the resources registered by the collaborative service platform of the first cloud domain. If the level of the third cloud domain is the same as the level of the lower-level cloud domain of the first cloud domain, in response to receiving an acceptance instruction for the execution request input by the management account of the first cloud domain, the receiving unit sends the execution request to the collaborative service platform of the lower-level cloud domain of the first cloud domain.

9. An electronic device, characterized in that, include: A processor and a memory for storing processor-executable instructions; wherein the processor is configured to execute the executable instructions to implement the multi-cloud domain task processing method as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is able to perform the multi-cloud domain task processing method as described in any one of claims 1 to 6.

11. A task processing system, characterized in that, The system includes multiple cloud domains and multiple collaborative service platforms corresponding to the multiple cloud domains; the system executes the multi-cloud domain task processing method as described in any one of claims 1 to 6.

Images