Multi-dimensional perception intelligent connection method and device based on edge-cloud, electronic equipment and system

Abstract

The present disclosure relates to an end-to-end cloud-based multi-dimensional perception intelligent connection method and device, electronic equipment and system, and relates to the technical field of cloud services. The present disclosure solves the problem that in the related art, early warning information obtained by a user in a local cloud domain can only be limited within the local cloud domain, and a user cannot be provided with a more comprehensive alarm service with a wider coverage. The method is applied to a collaborative service platform of a second cloud domain, and the method comprises: receiving a first task request sent by a first cloud domain; wherein the first task request is used to instruct the 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 according to device resource information registered by the second cloud domain on the first cloud domain; receiving an alarm signal sent by a first edge domain; the alarm signal is sent by the target alarm device to the first edge domain when the target alarm device monitors that a target event occurs in an alarm area corresponding to the target alarm device; and sending the alarm signal to the first cloud domain.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of cloud services, and particularly relates to a multi-dimensional perception intelligent connection method and device based on edge-cloud, electronic equipment and system. BACKGROUND

[0002] With the rapid development of social economy, people's requirements for life and environmental safety are getting higher and higher. At present, some early warning devices are widely arranged at some boundary positions to give early warning of suspicious events occurring at the boundary positions. For example, based on the characteristics that optical fibers are less affected by environmental factors and have good durability, at present, the vibration optical fiber as an early warning device has been gradually applied to the safety monitoring system. By collecting the scattering signals of the optical fiber along the line, the strain changes of the monitored environment are reflected to realize real-time monitoring of strain in a large range and at any position, so as to issue a warning information when the strain changes abnormally due to suspicious events, to prompt the user that the monitored environment has a safety anomaly.

[0003] However, in the above early warning process, only the alarm device of the local cloud domain itself is relied on to give early warning of suspicious events, and the alarm devices of other cloud domains are not fully utilized, so that the early warning information obtained by the users of the local cloud domain is limited within the local cloud domain, and the users cannot be provided with alarm services with wider and more comprehensive coverage. SUMMARY

[0004] The present disclosure provides a multi-dimensional perception intelligent connection method and device based on edge-cloud, electronic equipment and system to at least solve the problem in the related art that the early warning information obtained by the users of the local cloud domain is limited within the local cloud domain, and the users cannot be provided with alarm services with wider and more comprehensive coverage. The technical solutions of the present disclosure are as follows.

[0005] In a first aspect, the present application provides a multi-dimensional perception intelligent connection method based on edge-cloud, applied to a system including an end device, an edge domain and a cloud domain. The end device includes a target alarm device, and the target alarm device belongs to the device resources of the first edge domain. The cloud domain includes a first cloud domain and a second cloud domain, and the target alarm device belongs to the device resources of the second cloud domain. The first cloud domain is any one cloud domain other than the second cloud domain. Each cloud domain corresponds to a collaborative service platform one by one. The method is applied to the collaborative service platform of the second cloud domain, and the method includes: receiving a first task request sent by the first cloud domain; wherein the first task request is used to instruct the second cloud domain to adopt the target alarm device to alarm a target event; the target alarm device is determined by the first cloud domain according to the device resource information of the second cloud domain registered on the first cloud domain; receiving 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 the target alarm device monitors that a target event occurs in the alarm area corresponding to the target alarm device; and sending the alarm signal to the first cloud domain.

[0006] In this embodiment, the cooperative service platform of the second cloud domain alarms the target event by using the target alarm device of the second cloud domain in response to the first task request sent by the cooperative service platform of the first cloud domain, and sends the alarm signal to the first cloud domain to complete the task of alarming the target event by using the transaction resources of the second cloud domain to cooperate with the first cloud domain.

[0007] In a possible implementation, the method further includes: sending a resource information registration request to the cooperative service platform of any other cloud domain; the resource information registration request is used to indicate a request to register the resource information of the cooperative service platform of any other cloud domain in the cooperative service platform of the second cloud domain; and associating the resource information returned by the cooperative 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 cooperative service platform of any other cloud domain in the cooperative service platform of the second cloud domain.

[0008] In a possible implementation, the end device further includes a collection device, which belongs to the device resources of the second cloud domain and the first edge domain; the target alarm device is pre-associated with a target master collection device and a target slave collection device; the alarm signal sent by the first edge domain is determined by the following manner: the first edge domain determines the target collection device from the target master collection device, the target slave collection device, and other collection devices around the alarm region; the first edge domain sends an information collection instruction to the target collection device, and the information collection instruction instructs the target collection device to collect the image of the alarm region; the first edge domain determines whether the target event is a preset alarm event according to the event information of the target event in the image collected by the target collection device; if the target event is the preset alarm event, the first edge domain alarms the target event and sends the alarm signal to the first cloud domain. In this embodiment, when the server of the target cloud domain receives the alarm signal, the target collection device associated with the target alarm device that sends the alarm signal is started to collect the image of the alarm region to determine the event information of the target event occurring in the alarm region, so as to determine whether to alarm the target event according to the event information. Through this embodiment, after the alarm signal is generated, the alarm prompt information is not directly sent; instead, the target event is reviewed according to the event information determined by the target collection device, so as to ignore the alarm signal caused by the invalid target event, and send the alarm prompt information for the alarm signal caused by the valid target event to prompt the user to process the target event, so that the user does not need to process the invalid target event, saving the user's time and improving the user's efficiency of processing the target event.

[0009] In a possible implementation, the first edge domain determines the target acquisition device from the target master acquisition device, the target slave acquisition device, and other acquisition devices around the alarm region, including: if the target master acquisition device is in an idle state, determining the target master 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, determining the target slave acquisition device as the target acquisition device; and if the target master acquisition device and the target slave acquisition device are both in a non-idle state, determining the target acquisition device according to distances between the other acquisition devices and the target alarm device and working states of the other acquisition devices.

[0010] In a possible implementation, the device resources of the first edge domain include a plurality of alarm devices, the plurality of alarm devices are distributed on the first edge domain according to a preset interval, and the alarm devices are in one-to-one correspondence with the master acquisition devices. The method further includes: regarding a preset number of alarm devices that are continuously distributed with the target alarm device as candidate alarm devices; and determining the master acquisition device associated with the candidate alarm devices as the target slave acquisition device of the target alarm device.

[0011] In a possible implementation, the target acquisition device is a spherical shooting device, and the method further includes: determining working parameters of the spherical shooting device according to the longitude and latitude of the spherical shooting device, the height of the spherical shooting device, the position of the alarm region, and the installation height of the target alarm device, where the working parameters include a horizontal angle, a vertical angle, and a zoom factor of the spherical shooting device; and sending the working parameters to the spherical shooting device, so that the spherical shooting device collects images of the alarm region based on the working parameters.

[0012] According to a second aspect of the embodiments of the present disclosure, a multi-dimensional perception intelligent connection device based on edge-cloud is provided, including: an instruction receiving unit configured to receive a first task request sent by a first cloud domain; where 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 according to device resource information of the second cloud domain registered on the first cloud domain; where an edge device includes the target alarm device, and the target alarm device belongs to device resources of a first edge domain; the cloud domain includes the first cloud domain and the second cloud domain, and the target alarm device belongs to device resources of the second cloud domain; the first cloud domain is any one cloud domain except the second cloud domain; each cloud domain is in one-to-one correspondence with a collaborative service platform; the instruction receiving unit is further 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 the target alarm device monitors that the target event occurs in an alarm region corresponding to the target alarm device; and an alarm unit configured to send the alarm signal to the first cloud domain.

[0013] In a possible implementation, the instruction sending unit is configured to send a resource information registration request to a collaborative service platform of any other cloud domain; the resource information registration request is used to indicate a request to register resource information of the collaborative service platform of the any other cloud domain in the collaborative service platform of the second cloud domain; and the instruction sending unit is further configured to associate the resource information returned by the collaborative service platform of the any other cloud domain with a cloud domain identifier of the any other cloud domain, so as to complete the registration of the resource information of the collaborative service platform of the any other cloud domain in the collaborative service platform of the second cloud domain.

[0014] 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 further includes an acquisition unit and an alarm unit, the acquisition unit is configured to determine a target acquisition device from the target master acquisition device, the target slave acquisition device, and other acquisition devices around the alarm area in the first edge domain; the end device further includes an acquisition device, and the acquisition device belongs to device resources of the second cloud domain and the first edge domain; the acquisition unit is configured to send an information acquisition instruction to the target acquisition device in the first edge domain, and the information acquisition instruction instructs the target acquisition device to acquire an image of the alarm area; the acquisition unit is further configured to determine whether the target event is a preset alarm event according to event information of the target event in the image acquired by the target acquisition device in the first edge domain; and the alarm unit is configured to alarm the target event in the first edge domain if the target event is the preset alarm event, and send the alarm signal to the first cloud domain.

[0015] In another possible implementation, the acquisition unit 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 according to distances between the other acquisition devices and the target alarm device and working states of the other acquisition devices if the target master acquisition device and the target slave acquisition device are both in non-idle states.

[0016] In another possible implementation, the collection unit is further specifically configured to take a preset number of the alarm devices continuously distributed with the target alarm device as candidate alarm devices; and take a preset number of master collection devices associated with the candidate alarm devices as the target slave collection devices of the target alarm device; wherein the device resources of the first edge domain include a plurality of alarm devices, the plurality of alarm devices are distributed on the first edge domain according to a preset interval, and the alarm devices are one-to-one corresponding to the master collection devices.

[0017] In another possible implementation, the collection unit is further configured to determine working parameters of the spherical shooting device according to the latitude and longitude of the spherical shooting device, the height of the spherical shooting device, the position of the alarm region, and the installation height of the target alarm device, wherein the working parameters include a horizontal angle, a vertical angle, and a zoom factor of the spherical shooting device; and send the working parameters to the spherical shooting device, so that the spherical shooting device collects images of the alarm region based on the working parameters; and the target collection device is the spherical shooting device.

[0018] According to a third aspect of the embodiments of the present disclosure, an electronic device is provided, including a processor and a memory for storing processor-executable instructions; wherein the processor is configured to execute the executable instructions to implement the edge-cloud-based multi-dimensional perception intelligent connection method according to the first aspect and any possible implementation thereof.

[0019] According to a fourth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the edge-cloud-based multi-dimensional perception intelligent connection method according to the first aspect and any possible implementation thereof; or when the instructions in the computer-readable storage medium are executed by a task processing device of a multi-cloud domain, the task processing device of the multi-cloud domain is enabled to perform the edge-cloud-based multi-dimensional perception intelligent connection method according to the first aspect and any possible implementation thereof.

[0020] According to a fifth aspect of the embodiments of the present disclosure, a computer program product is provided, including a computer program or instructions, the computer program or instructions are executed by a processor to perform the edge-cloud-based multi-dimensional perception intelligent connection method according to the first aspect and any possible implementation thereof.

[0021] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0022] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments consistent with the present disclosure and, together with the description, further serve to explain the principles of the disclosure without imposing on the disclosure limitations that are inconsistent with the principles of the disclosure.

[0023] Figure 1 is a schematic diagram of a cloud domain structure relationship according to an example embodiment;

[0024] Figure 2 is a schematic diagram of a cloud service system according to an example embodiment;

[0025] Figure 3 is a schematic diagram of a task processing subsystem of a multi-cloud domain according to an example embodiment;

[0026] Figure 4 is a schematic diagram of an alarm subsystem according to an example embodiment;

[0027] Figure 5 is a flowchart of a task processing method of a multi-cloud domain according to an example embodiment;

[0028] Figure 6 is a flowchart of another task processing method of a multi-cloud domain according to an example embodiment;

[0029] Figure 7 is a flowchart of another task processing method of a multi-cloud domain according to an example embodiment;

[0030] Figure 8 is a flowchart of another task processing method of a multi-cloud domain according to an example embodiment;

[0031] Figure 9 is a flowchart of a multi-dimensional perception and intelligent connection method based on edge-cloud according to an example embodiment;

[0032] Figure 10 is a flowchart of another multi-dimensional perception and intelligent connection method based on edge-cloud according to an example embodiment;

[0033] Figure 11 is a schematic diagram of a task processing apparatus of a multi-cloud domain according to an example embodiment;

[0034] Figure 12 is a schematic diagram of a multi-dimensional perception and intelligent connection apparatus based on edge-cloud according to an example embodiment;

[0035] Figure 13 is a schematic diagram of an electronic device according to an example embodiment. DETAILED DESCRIPTION

[0036] In order for those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be described clearly and completely below in conjunction with the drawings.

[0037] It should be noted that the terms "first", "second" and the like in the specification and claims of the present disclosure and the above-described drawings are used to distinguish similar objects, and do not necessarily have to describe a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present disclosure described herein can be implemented in an order other than that illustrated or described herein. The implementation described in the following exemplary embodiments does not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0038] Before the multi-cloud domain task processing method provided by the embodiments of the present disclosure is described in detail, the application scenarios and implementation environments involved in the embodiments of the present disclosure will be briefly introduced.

[0039] First, in order to facilitate the understanding of the present application, the related elements involved in the present application will be described.

[0040] End: a single sensing device that can collect single-dimensional information or multi-dimensional information and has certain processing capability for the collected information. It can be understood that a single sensing device can collect information data within the sensing area of a certain device. Among them, the sensing device can be a radar or a vibration optical fiber.

[0041] Edge: also known as the edge side of the cloud or edge domain or edge domain. Through the combination of multiple sensing devices, the data collected by multiple sensing devices in the local range corresponding to the edge (i.e. the area range enclosed by one edge) are analyzed in cooperation.

[0042] Cloud: also known as cloud domain. Access the data analysis results of multiple edges and the data collected by multiple sensing devices of multiple ends, gather multi-dimensional data, realize the fusion scheduling and management of various algorithms, computing power and data resources, and reasonably run the "device end and edge corresponding data". The area range corresponding to the cloud includes the sum of the area ranges enclosed by multiple edges.

[0043] Integrated collaborative service platform: abbreviated as collaborative service platform, corresponding to the server of each cloud, task-oriented, allowing other clouds to collaborate on the tasks of local clouds.

[0044] Vibration optical fiber unit number: a vibration optical fiber is divided into multiple units according to equal distances, and each unit is assigned a corresponding number. Each vibration optical fiber unit number is provided with a main collection device, and a main collection device and a plurality of other vibration optical fiber unit numbers around the main collection device establish an association relationship, that is, the main collection device is a slave collection device of the plurality of other vibration optical fiber unit numbers. For example, each ball machine can establish an association relationship with 10 vibration optical fiber unit numbers around it.

[0045] Secondly, the application scenarios related to the present disclosure are briefly introduced.

[0046] Cloud service is a service mode of providing dynamically scalable virtualized resources through Internet service. Cloud service has the advantages of low cost, high reliability, high scalability, high automation, virtualization, etc., therefore, cloud service technology has been widely used for resource storage and resource processing between networks such as the Internet by individuals or enterprises.

[0047] With the rapid development of social economy, people's requirements for safety of life and environment are getting higher and higher, at present, some early warning devices are widely arranged at some boundary positions to give early warning for suspicious events occurring at the boundary positions. For example, based on the characteristics of small influence of optical fiber on environmental factors and good durability, at present, vibration optical fiber as an early warning device has been gradually applied to safety monitoring systems, by collecting scattered signals along the optical fiber, to reflect the strain change of the monitoring environment, to realize real-time monitoring of strain in a large range and at any position, so as to issue early warning information when the strain change caused by suspicious events is abnormal, to prompt the user that the monitoring environment has a safety anomaly.

[0048] However, in the above early warning process, only the alarm device of the local cloud domain itself is relied on to give early warning for suspicious events, without fully utilizing the alarm devices of other cloud domains, so that the early warning information obtained by the users of the local cloud domain is limited within the local cloud domain, and the users cannot be provided with alarm services with wider and more comprehensive coverage.

[0049] In view of the above problems, the present disclosure provides a multi-dimensional perception intelligent connection method based on end-to-end cloud, the cooperative service platform of the second cloud domain responds to the first task request sent by the cooperative service platform of the first cloud domain, adopts the target alarm device of the second cloud domain to alarm the target event, and sends the alarm signal to the first cloud domain, to utilize the transaction resources of the second cloud domain to cooperate with the first cloud domain to complete the task of alarming the target event.

[0050] Based on the embodiment, when the resources of the first cloud domain cannot perform the alarm task, the collaborative service platform of the first cloud domain can determine a second cloud domain that can achieve the target task from other cloud domains through the resource conditions provided by each cloud domain, and send a task execution request to the collaborative service platform of the second cloud domain through the collaborative service platform of the first cloud domain, so that the second cloud domain collaborates with the first cloud domain to execute the target task, so that different cloud domains can collaboratively complete the task, so that the task range that a single cloud domain can perform is no longer limited by the resources of the cloud domain itself, but also depends on the resources of other cloud domains to collaboratively complete the alarm task.

[0051] Based on this, the local cloud domain or local cloud domain that independently executes local tasks is associated to implement cross-cloud domain collaborative execution of global tasks, avoid the problem that the task range of each cloud domain processing task is limited by the resources included in the cloud domain, improve the task range of each cloud domain processing task, and thus provide a wider and more comprehensive service for users of each cloud domain to improve user experience.

[0052] Again, the implementation architecture related to the present application is briefly introduced below.

[0053] Figure 1 is a multi-cloud domain schematic diagram provided by the present application, Figure 1 shows the hierarchical relationship between multiple cloud domains and the relationship between cloud, edge and end of a single cloud domain, and exemplary includes a first-level cloud, a second-level cloud (such as second-level cloud A, second-level cloud D), a third-level cloud (such as third-level cloud a, third-level cloud b, third-level cloud c, third-level cloud e, third-level cloud d). Specifically, Figure 1 In the present application, each cloud domain is divided into first-level cloud, second-level cloud, third-level cloud, … (optionally, it can be equivalent to the administrative hierarchical relationship of the corresponding region: department, province, city, …) from top to bottom according to the hierarchical relationship, and the network level of each level of cloud domain is bidirectional network reachable, while the hierarchy only exists between the interconnection of single level, that is, only the adjacent upper cloud and lower cloud are interconnected, such as the first-level cloud only interconnects with the second-level cloud, and does not interconnect with the third-level cloud. For example, the upper cloud domain (i.e., second-level cloud A) corresponding to the third-level cloud a and the upper cloud domain (i.e., second-level cloud A) corresponding to the third-level cloud b belong to the same cloud domain; the upper cloud domain (i.e., second-level cloud D) of the third-level cloud d and the upper cloud domain (i.e., second-level cloud A) of the third-level cloud a belong to different cloud domains of the same level; the upper cloud domain (i.e., second-level cloud D) of the third-level cloud d and the upper cloud domain (i.e., second-level cloud A) corresponding to the third-level cloud b belong to different cloud domains of the same level. Among them, one cloud domain corresponds to one cloud, one cloud corresponds to multiple edges, and one edge corresponds to multiple ends.

[0054] Exemplarily, a certain C city region corresponds to a cloud domain C, the certain C city includes M districts, and the M districts correspond to M cloud domains. That is, the cloud domain C is an upper cloud domain of the M cloud domains. A server corresponding to an upper cloud domain can acquire resources of a lower cloud domain interconnected therewith. The resources include one or more of device resources, data resources, and service resources.

[0055] Figure 2 FIG. 1 is a schematic diagram of a cloud domain service system 20 provided by the present application. The cloud domain service system includes a task processing subsystem 21 corresponding to each cloud domain and an alarm subsystem 22 corresponding to each cloud domain. The task processing subsystem 21 is configured to enable servers of different cloud domains to cooperatively complete a certain task. Each cloud domain corresponds to an alarm subsystem 22, which is configured to call data collected by device resources within each edge corresponding to the cloud domain and use the collected data to perform alarm.

[0056] Figure 3 FIG. 2 is a schematic diagram of a task processing subsystem 21 of a multi-cloud domain provided by the present disclosure. The task processing subsystem 21 includes a plurality of servers 201 corresponding to a plurality of cloud domains and a terminal device 202 corresponding to a user of each cloud domain. The server 201 can establish a connection between the terminal device 202 through a wired network or a wireless network.

[0057] In the present application, the server 201 of each cloud domain can include an integrated collaborative service platform. Resources provided by each cloud domain are registered on the integrated collaborative service platform, and one integrated collaborative service platform corresponds to one collaborative service application program. The collaborative service application program can be installed on the terminal device 202 of the user, and the target resources provided by the integrated collaborative service platform or the processing results of the target resources are displayed on the content display interface of the terminal device 202.

[0058] Exemplarily, each level of “cloud domain” registers resources provided by the current cloud domain and tasks executable by the current cloud domain to the local integrated collaborative service platform. The integrated collaborative service platforms of two levels of “cloud domains” interconnected with each other authenticate and authorize a task execution request by sending the task execution request, thereby realizing cooperation and secure mutual trust between the integrated collaborative service platforms of the multi-level cloud domains. As a result, each level of “cloud domain” can discover various view tasks that can be provided by other “cloud domains” across levels and across cloud domains by means of the integrated collaborative service platform, and apply for and call resources on demand.

[0059] 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.

[0060] 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.

[0061] 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 the 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 sent 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.

[0062] 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 server 201.

[0063] The terminal device can be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) \ virtual reality (VR) device, or the like, which can install and use a content community application (such as Kuaishou), and the specific form of the terminal is not specially limited in the present disclosure. It can interact with the user through one or more ways such as a keyboard, a touchpad, a touch screen, a remote controller, voice interaction, or a handwriting device.

[0064] Optionally, the above Figure 2 In the cloud service system shown, the server can be connected with at least one terminal device. The number and type of the terminal device are not limited in the present disclosure.

[0065] The multi-cloud-domain task processing method provided by the embodiments of the present disclosure can be applied to the server in the implementation architecture shown. Figure 3 To facilitate understanding, the multi-cloud-domain task processing method provided by the present disclosure is specifically introduced below in combination with the accompanying drawings.

[0066] It should be noted that before introducing the multi-dimensional perception intelligent connection method based on edge-cloud, the process of processing the cross-domain task execution request in the multi-cloud-domain task processing method is introduced first; and then the multi-dimensional perception intelligent connection process is introduced by taking the target task of alarming the target event as an example. The following describes the task processing method by taking an example that the server of the first cloud domain sends a task execution request to the server of the second cloud domain to complete a target task. When the target task needs to be completed by multiple target cloud domains, the server of the first cloud domain can send multiple task requests to the servers of multiple target cloud domains at the same time, and the following task processing method can be executed synchronously. To avoid repeated description, the following will not be described in detail.

[0067] Figure 5 is a flowchart of a multi-cloud-domain task processing method according to an example embodiment, as Figure 5 The multi-cloud-domain task processing method can be used in the multi-cloud-domain task processing system described above, and includes the following steps.

[0068] S51, the collaborative service platform of the first cloud domain determines the second cloud domain from the multiple cloud domains according to the target task and the resources corresponding to each cloud domain in the multiple cloud domains.

[0069] The resources include one or more of a service resource, a device resource, and a data resource, and the resources corresponding to the second cloud domain include a target resource used to implement the target task.

[0070] In some embodiments, the target task can be a view type task, such as a video browsing task, a video query task, a video surveillance task, etc. For example, the device resource can be a sensing device (such as a vibration fiber or a radar) corresponding to each end of the cloud domain, and the data resource includes data collected by each sensing device and data (such as edge corresponding data resource) obtained by data analysis and data processing on the data collected by each sensing device.

[0071] Optionally, the second cloud domain is determined in the following manner: first, a target service used to serve the target task is determined according to the target task initiated by the terminal device of the target user in the first cloud domain; second, a first candidate cloud domain is determined from a plurality of cloud domains registered on the collaborative service platform of the first cloud domain according to service resource information of the plurality of cloud domains, wherein the service resource of the first candidate cloud domain includes the target service; and third, the second cloud domain is determined from the first candidate cloud domain.

[0072] Specifically, the resource identifier of each cloud domain is registered on the collaborative service platform of each cloud domain. Generally, each cloud domain includes a plurality of resource identifiers. The target resource identifier matching the target resource is determined from the resource identifiers registered by each cloud domain. The target cloud domain associated with the target resource identifier is determined as the second cloud domain according to the association relationship between the resource identifier and each cloud domain.

[0073] As an implementation, the following steps can be performed before the above step S51 to enable other cloud domains to complete the registration of resource information on the collaborative service platform of the first cloud domain. Specifically, first, 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 is used to indicate that the resource information of the collaborative service platform of any other cloud domain is requested to be registered on the first collaborative service platform. Second, 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 first cloud domain.

[0074] 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.

[0075] It can be understood that the collaborative service platform of the first cloud domain sends the task execution request through the collaborative service platform of the upper cloud domain of the first cloud domain and the collaborative service platform of the upper cloud domain of the second cloud domain.

[0076] 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 resource.

[0077] In an implementation, the step S52 can be implemented by the following steps. First, the collaborative service platform of the first cloud domain determines the target data resource and / or the target device resource associated with the target task in the second cloud domain. Second, the collaborative service platform of the first cloud domain 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 resource and / or the target device resource and the target user to the collaborative service platform of the second cloud domain, where 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 resource and / or the target device resource.

[0078] Further, in another implementation, the step S52 can be implemented by the following steps. The condition information associated with the target service is determined. The task execution request carrying the condition information is sent to the collaborative service platform of the second cloud domain, where 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.

[0079] S53, the collaborative service platform of the second cloud domain accepts the task execution request and executes the target task.

[0080] It should be noted that the second cloud domain can directly execute the target task by using the data resource of the second cloud domain, or the second cloud domain can execute the target task by calling the resource of the corresponding "edge" and / or the resource of the "end".

[0081] The execution of the target task is implemented in the following ways. First, the collaborative service platform of the corresponding edge of the second cloud domain can analyze the data resource provided by the multiple device resources on the end, and the collaborative service platform of the second cloud domain can use the analysis result of the data resource by the collaborative service platform of the corresponding edge of the second cloud domain to execute the target task. Second, the collaborative service platform of the second cloud domain can also use the data resource provided by the device resource on the corresponding device end of the second cloud domain to execute the target task. Third, the collaborative service platform of the second cloud domain can process the analysis result on the corresponding edge and / or the data resource on the corresponding device end according to the execution rule matched with the target task, to execute the target task. Therefore, the way of executing the target task by the second collaborative service platform is not limited in the present application.

[0082] Understandably, the cooperative service platform of the second cloud domain can accept the task execution request to agree to cooperate with the first cloud domain to execute the target task, or reject the task execution request to refuse to cooperate with the first cloud domain to execute the target task. For example, in a possible implementation, in the case where the cooperative service platform of the second cloud domain rejects the task execution request, prompt information returned by the cooperative service platform of the second cloud domain is received, and the prompt information is used to prompt the second cloud domain to refuse to execute the target task.

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

[0084] Specifically, after the cooperative service platform of the second cloud domain executes the target task by using the target resource in the second cloud domain, the execution result is returned to the cooperative service platform of the first cloud domain.

[0085] In the above implementation, when the resource corresponding to the first cloud domain cannot execute a certain target task, the cooperative service platform of the first cloud domain determines a target cloud domain, i.e., the second cloud domain, which can execute the target task according to the resources provided by each cloud domain. The cooperative service platform of the first cloud domain sends a task execution request to the cooperative service platform of the second cloud domain to request the second cloud domain to cooperate with the first cloud domain to execute the target task. After accepting the execution request, the cooperative service platform of the second cloud domain cooperates with the target resource in the second cloud domain to execute the target task, and then sends the execution result to the cooperative service platform of the first cloud domain to cooperate with the first cloud domain to complete the execution of the target task.

[0086] Based on the implementation, when the resource of the first cloud domain cannot execute a certain target task, the cooperative service platform of the first cloud domain can determine the second cloud domain which can execute the target task from other cloud domains according to the resources provided by each cloud domain, and send a task execution request to the cooperative service platform of the second cloud domain through the cooperative service platform of the first cloud domain, so that the second cloud domain cooperates with the first cloud domain to execute the target task, to enable different cloud domains to cooperatively complete the task, so that the range of tasks that can be executed by a single cloud domain no longer depends only on the resources of the cloud domain itself, but also on the resources of other cloud domains to cooperatively complete the target task.

[0087] When the resource of the first cloud domain can execute a certain target task, the cooperative service platform of the first cloud domain executes the target task according to the resource of the first cloud domain. The execution process of the cooperative service platform of the first cloud domain to execute the target task is similar to the execution process of the cooperative service platform of the second cloud domain to execute the target task, which will not be described here.

[0088] Based on this, the task processing method of the present disclosure avoids the problem that the task range of the task processed by each cloud domain is limited by the resources included in the cloud domain, improves the task range of the task processed by each cloud domain, thereby providing a wider and more comprehensive service for the users of each cloud domain to improve the user experience.

[0089] As an implementation, after the execution of the above S54, the following step is further executed: the collaborative service platform of the first cloud domain sends the execution result to the terminal device that initiates the task execution request of the first cloud domain. Wherein, the terminal device can be one or more.

[0090] In some embodiments, the task execution request includes a terminal device identifier of the terminal device thereof, and after the collaborative service platform of the second cloud domain executes the target task, the execution result of the target task is returned to the terminal device corresponding to the terminal device identifier.

[0091] Illustratively, the data resource includes video data; the target data is target video data in the video data; and sending the execution result to the terminal device includes: sending the processing result corresponding to the target video data to the terminal device, so as to enable the terminal device to display the execution result corresponding to the target video data.

[0092] The target task in the above implementation includes two types of target tasks: a first target task and a second target task. Specifically, the target task includes the first target task of calling the target resource and the second target task of processing the target data in the target resource by using a preset rule. Different target task types correspond to different execution results.

[0093] Illustratively, if the first target task is to review the 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.

[0094] Further, if the second target task is to perform a target processing on the target data, then the execution result corresponding to the second target task is the processing result of the target data by using the preset rule, wherein the data resource corresponding to the second cloud domain includes the target data.

[0095] In some embodiments, the preset rule is formed according to the condition information associated with the target service.

[0096] Illustratively, the service resource of the above first candidate cloud domain includes a first target service, and the first target service can be used to review the data collected by the data collection device. That is, the above first target service can be a video review service, and the target task is a cross-domain video review.

[0097] In another example, the service resource of the second candidate cloud domain includes a second target service, the second target service is configured to perform target processing on data collected by a data collection device according to a preset rule, and the data resource corresponding to the second cloud domain includes target data. That is, the second target service is a cross-cloud domain deployment service, and the target task is cross-cloud domain deployment.

[0098] In some embodiments, the preset rule includes an acquisition path for acquiring target video data, a rule for extracting a preset feature, a rule for extracting a preset object type, a rule for extracting a similarity of a preset object, and a rule for acquiring associated information, the associated information includes time information and location information, and the target processing includes at least one or more of the following: acquiring target video data from a target video collection device based on the acquisition path; extracting a target object having a preset feature from the target video data based on the rule for extracting the preset feature; extracting a target object of a preset object type from objects of the target video data based on the rule for extracting the preset object type; extracting a target object having a similarity greater than a similarity threshold with respect to a preset object from the objects of the target video data based on the rule for extracting the similarity of the preset object; and acquiring associated information of the target object.

[0099] In an embodiment of generating the preset rule, in response to an input instruction of rule information input by a user account in a rule setting interface, the preset rule is generated according to the rule information; the rule information includes one or more of the following: a preset feature, a preset object type, a similarity threshold, and associated information. The associated information includes time information and location information.

[0100] For example, the second target task is a cross-domain collaborative deployment task. The cross-domain collaborative deployment task execution request can include deployment of identification of a face, a vehicle, and an ID card, respectively. The target user obtains a list of each cloud domain capable of providing cross-domain collaborative deployment services through an application program corresponding to the local integrated collaborative service platform, selects a target cloud domain that needs to be collaboratively deployed, and inputs cross-domain collaborative deployment conditions in the displayed collaborative deployment page to form a preset rule of the cross-domain collaborative deployment task. The cross-domain collaborative deployment conditions can include deployment target information, deployment time period, and deployment similarity.

[0101] In the above embodiment, the data resource includes video data, the device resource includes a video collection device for collecting the video data, the target device is a target video collection device among the video collection devices, and the target data is target video data among the video data.

[0102] Exemplarily, the sending of the execution result to the terminal device includes: in a case where the target task is the first target task, sending the video data collected by the target video collection device or an address of the video data collected by the target video collection device to the terminal device, so that the terminal device displays the video data collected by the target video collection device; in a case where the target task is the second target task, sending the processing result corresponding to the target video data to the terminal device, so that the terminal device displays the processing result corresponding to the target video data.

[0103] In some embodiments, the permissions of performing tasks between different cloud domains at different levels are limited to each other. In actual application scenarios, the first cloud domain and the second cloud domain are both the same level of cloud domain layer corresponding to the device collecting data resources in the entire cloud domain structure, and therefore belong to the same level of cloud domain.

[0104] The above S52 is described in detail below in combination with two application scenarios.

[0105] In a first scenario, 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 correspond to the same level, and the upper cloud domains of the first cloud domain and the second cloud domain are different cloud domains.

[0106] As shown in FIG. 6, the first cloud domain sends a task execution request to the second cloud domain in the following manner. Figure 6

[0107] S61, the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the upper cloud domain of the first cloud domain.

[0108] S62, the collaborative service platform of the upper cloud domain of the first cloud domain approves the task execution request.

[0109] S63, the collaborative service platform of the upper cloud domain of the first cloud domain sends the task execution request to the collaborative service platform of the upper cloud domain of the second cloud domain.

[0110] The collaborative service platform of the upper cloud domain of the first cloud domain is configured to approve the task execution request and, in a case where the task execution request is approved, forward the task execution request to the collaborative service platform of the upper cloud domain of the second cloud domain.

[0111] S64, the collaborative service platform of the upper cloud domain of the second cloud domain approves the task execution request.

[0112] S65, the collaborative service platform of the second cloud domain receives the task execution request.

[0113] ​In S64 and S65, the collaborative service platform of the upper cloud domain of the second cloud domain is configured to approve the task execution request, and in the case that the task execution request is approved, the collaborative service platform of the upper cloud domain of the second cloud domain forwards the task execution request to the collaborative service platform of the second cloud domain.

[0114] For example, the collaborative service platform of the first cloud domain sends a first request to the collaborative service platform of the upper cloud domain of the first cloud domain, the first request is used to request the collaborative service platform of the upper cloud domain of the first cloud domain to approve the task execution request, and in the case that the task execution request is approved by the collaborative service platform of the upper cloud domain of the first cloud domain, the collaborative service platform of the upper cloud domain of the first cloud domain is instructed to send a second request to the collaborative service platform of the upper cloud domain of the second cloud domain, the second request is used to request the collaborative service platform of the upper cloud domain of the second cloud domain to approve the task execution request, and in the case that the task execution request is approved by the collaborative service platform of the upper cloud domain of the second cloud domain, the collaborative service platform of the upper cloud domain of the second cloud domain is instructed to send the task execution request to the collaborative service platform of the second cloud domain.

[0115] Based on the above introduction of the hierarchical relationship of the cloud domain, Figure 1 As shown in the hierarchical relationship of the cloud domain, in the embodiment, the first cloud domain is interconnected with the upper cloud domain of the first cloud domain, the first cloud domain is not interconnected with the upper cloud domain of the upper cloud domain of the first cloud domain, the second cloud domain is interconnected with the upper cloud domain of the second cloud domain, and the second cloud domain is not interconnected with the upper cloud domain of the upper cloud domain of the second cloud domain. Wherein, the interconnection is used to represent that the two cloud domains can establish communication to jointly execute a task.

[0116] Figure 1The upper cloud domain of the third-level cloud a (i.e., the second-level cloud A) and the upper cloud domain of the third-level cloud d (i.e., the second-level cloud D) belong to different cloud domains of the same level and meet the scenario one. For example, the task processing flow between the cloud domains in the scenario one is described as follows. The cloud domains of different levels register the resources and tasks that can be provided and executed in the local integrated collaborative service platform. The third-level cloud a sends a task execution request to the integrated collaborative service platform of the second-level cloud A through the integrated collaborative service platform of the third-level cloud a; the integrated collaborative service platform of the second-level cloud A sends the task execution request to the integrated collaborative service platform of the second-level cloud D; and the integrated collaborative service platform of the second-level cloud D sends the task execution request to the integrated collaborative service platform of the third-level cloud d. In this implementation mode, for the cloud domain structure scenario that the corresponding upper cloud domains of the two are different, 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 when the collaborative service platforms of the upper cloud domains of the first cloud domain and the second cloud domain both approve the task execution request. Based on this, the approval process of the task execution request in the cloud domain scenario that the upper cloud domains of the two are different is realized, and it is ensured that the task execution request received by the collaborative service platform of the second cloud domain is approved by both upper cloud domains, so as to ensure the rationality of the target task execution process of the collaborative service platform of the second cloud domain.

[0117] Scenario two, the levels corresponding to the first cloud domain and the second cloud domain are the same, and the upper cloud domains of the first cloud domain and the second cloud domain are the same cloud domain.

[0118] As shown in the first cloud domain, the collaborative service platform of the second cloud domain sends a task execution request to the collaborative service platform of the second cloud domain as follows. Figure 7

[0119] S71, the collaborative service platform of the first cloud domain sends a task execution request to the collaborative service platform of the upper cloud domain of the first cloud domain.

[0120] S72, the collaborative service platform of the upper cloud domain of the first cloud domain approves the task execution request.

[0121] S73, the collaborative service platform of the upper cloud domain of the first cloud domain sends the task execution request to the collaborative service platform of the second cloud domain.

[0122] S74, the collaborative service platform of the upper cloud domain of the second cloud domain receives the task execution request.

[0123] ​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.

[0124] 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.

[0125] 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.

[0126] For example, taking "the collaborative service platform of each level of cloud domain includes 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.

[0127] 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.

[0128] 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.

[0129] 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.

[0130] When the collaboration service platform of the third-level cloud b applies to review the target video data on the target device to the collaboration service platform of the third-level cloud d under another second-level cloud D, the administrator of the second-level cloud A needs to first approve the target task, and after the approval, the task execution request is transferred to the collaboration service platform of the second-level cloud D. After the administrator of the second-level cloud D approves, the task is transferred to the collaboration service platform of the target cloud domain: the collaboration service platform of the third-level cloud d. After the administrator of the third-level cloud d approves, the target user of the third-level cloud b can see the target video data provided by the third-level cloud d in the local video application of the corresponding terminal device.

[0131] When the collaboration service platform of the third-level cloud b applies to review the target video data on the target device to the collaboration service platform of the third-level cloud a under the same second-level cloud A, the administrator of the second-level cloud a needs to first approve the target task, and after the approval, the task execution request is transferred to the collaboration service platform of the third-level cloud a. After the administrator of the third-level cloud a approves, the target user of the third-level cloud b can see the target video data provided by the collaboration service platform of the third-level cloud a in the local video application of the corresponding terminal device.

[0132] Among them, the collaboration service platform of the target cloud domain (third-level cloud a or third-level cloud d) can configure privacy coding, whether to configure watermark, whether to bind the MAC / IP address of the target user, video data streaming link strategy, etc.

[0133] Through the above-mentioned manner, the target user of the third-level cloud a obtains the URL (uniform resource locator) of the video data preview according to the video acquisition device identifier of the cross-domain in the local video application, and initiates a video review task execution request. The video review task execution request is executed across the cloud domain through the collaboration service platform of the third-level cloud b to the collaboration service platform of the target cloud domain, and is forwarded to the target terminal corresponding to the video acquisition device of the target cloud domain, so as to complete the cross-domain video review task.

[0134] The following takes the second target task as an example of cross-domain collaborative deployment task, and the following describes the task collaboration process under the above-mentioned scene one and scene two.

[0135] The target user of the third-level cloud b obtains the list of each cloud domain that can provide cross-domain collaborative deployment service through the application program corresponding to the local integrated collaboration service platform, selects the target cloud domain that needs to be collaboratively deployed, and inputs the cross-domain collaborative deployment condition in the displayed collaborative deployment page, so as to form the preset rule of the cross-domain collaborative deployment task.

[0136] When the collaborative service platform of the third cloud b applies for cross-domain collaborative deployment to the collaborative service platform of the third cloud d under another second cloud D, the administrator of the second cloud A needs to first approve the target task, and after the approval, the task execution request is transferred to the second cloud D. After the administrator of the second cloud D approves, the task is transferred to the collaborative service platform of the target cloud domain: the collaborative service platform of the third cloud d. After the administrator of the third cloud d approves, the collaborative service platform of the third cloud d can execute the cross-domain collaborative deployment task.

[0137] When the collaborative service platform of the third cloud b applies for cross-domain collaborative deployment to the collaborative service platform of the third cloud a under the same second cloud A, the administrator of the second cloud a needs to first approve the target task, and after the approval, the task execution request is transferred to the collaborative service platform of the third cloud a. After the administrator of the third cloud a approves, the collaborative service platform of the third cloud a can execute the cross-domain collaborative deployment task.

[0138] The called collaborative service platform of the target cloud domain can read the collaborative deployment conditions through the local integrated collaborative service platform, and respond to the cross-domain collaborative deployment task according to the deployment capabilities that can be provided locally.

[0139] For example, the cross-domain collaborative deployment task execution request can include the deployment of face, vehicle, and ID card recognition respectively, but the target cloud domain only has the ability of face recognition deployment. Therefore, it can only feedback the face recognition deployment execution result, and not feedback the execution results of vehicle recognition deployment and ID card recognition deployment. The called target cloud domain allocates the cross-domain collaborative deployment task to the cloud, edge, and end of the target cloud domain according to 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 initiates the cross-domain collaborative deployment task through the integrated collaborative service platform, so that the target user can see the execution result of the cross-domain collaborative deployment feedback on the application of the terminal device.

[0140] As a possible implementation, the collaborative service platform of the first cloud domain can also cooperate with other cloud domains to execute tasks based on the resources of the first cloud domain. For example, Figure 8 As shown in the figure, taking the third cloud domain as an example, the collaborative service platform of the first cloud domain cooperates with the third cloud domain to complete the execution request of the user on the terminal device in the third cloud domain.

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

[0142] The execution request sent by the cooperation service platform of the third cloud domain is used to instruct the cooperation service platform of the first cloud domain or the cooperation service platform of the lower cloud domain of the first cloud domain to execute the to-be-executed task generated by the third cloud domain.

[0143] S82, in the case where the third cloud domain and the first cloud domain correspond to the same level, the cooperation service platform of the first cloud domain responds to the acceptance instruction of the execution request input by the management account of the first cloud domain, and executes the to-be-executed task by using the resources registered by the cooperation service platform of the first cloud domain.

[0144] S83, in the case where the level of the third cloud domain corresponds to the level of the lower cloud domain of the first cloud domain, the cooperation service platform of the first cloud domain responds to the acceptance instruction of the execution request input by the management account of the first cloud domain, and sends the execution request to the cooperation service platform of the lower cloud domain of the first cloud domain.

[0145] In detail, when the third cloud domain cannot complete the to-be-executed task, the cooperation service platform of the third cloud domain sends an execution request to the cooperation service platform corresponding to the cloud domain that can complete the to-be-executed task (i.e., the cooperation service platform of the first cloud domain or the cooperation service platform of the lower cloud domain of the first cloud domain), so as to make the cooperation service platform of the first cloud domain or the cooperation service platform of the lower cloud domain of the first cloud domain execute the execution request. Based on the different level relationship between the third cloud domain and the first cloud domain in the cloud domain level structure, the flow of executing the to-be-executed task is also different.

[0146] For example, in the case where the first cloud domain receives the task execution request of the cloud domain at the same level, i.e., in the case where the third cloud domain and the first cloud domain belong to the same level, the execution request needs to pass the approval of the cooperation service platform of the upper cloud domain of the third cloud domain and the cooperation service platform of the upper cloud domain of the first cloud domain in sequence, and then the cooperation service platform of the first cloud domain receives the execution request to execute the to-be-executed task by using the resources registered by the cooperation service platform of the first cloud domain.

[0147] For another example, in the case where the first cloud domain receives the task execution request of the cloud domain at the next level, i.e., in the case where the third cloud domain and the lower cloud domain of the first cloud domain belong to the same level, after the cooperation service platform of the upper cloud domain of the third cloud domain approves the execution request, the cooperation service platform of the first cloud domain receives the execution request, and then approves the execution request. After the approval, the cooperation service platform of the first cloud domain sends the execution request to the cooperation service platform of the lower cloud domain of the first cloud domain, so as to make the cooperation service platform of the lower cloud domain of the first cloud domain execute the to-be-executed task of the third cloud domain according to the resources registered by the cooperation service platform of the lower cloud domain of the first cloud domain.

[0148] 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.

[0149] In one implementation, the aforementioned target task can also issue alerts for target events. The following is an example... Figure 9 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.

[0150] 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.

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

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

[0153] 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.

[0154] S92, the collaborative service platform of the second cloud domain receives alarm signals sent by the first edge domain.

[0155] 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.

[0156] S93 sends an alarm signal to the first cloud domain.

[0157] It should be noted that the method is applied to a system including an end device, an edge domain and a cloud domain, the end device includes a target alarm device, the target alarm device belongs to device resources of the first edge domain; the cloud domain includes a first cloud domain and a second cloud domain, the target alarm device belongs to device resources of the second cloud domain; the first cloud domain is any one cloud domain except the second cloud domain; each cloud domain corresponds to a collaborative service platform.

[0158] Before step S91, the collaborative service platform of the second cloud domain can also complete resource information registration. Specifically, first, a resource information registration request is sent 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 requested to be registered in the collaborative service platform of the second cloud domain. Then, 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, 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.

[0159] As an implementation manner, the end device further includes a collection device, the collection device belongs to device resources of the second cloud domain; the target alarm device is pre-associated with a target master collection device and a target slave collection device. As shown in Figure 10 Before executing the above step S93, the collaborative service platform of the second cloud domain can also specifically implement the following steps to realize the alarm task of the target event.

[0160] Step S101, determining a target collection device from the target master collection device, the target slave collection device and other collection devices around the alarm area.

[0161] Step S102, sending an information collection instruction to the target collection device.

[0162] The information collection instruction instructs the target collection device to collect images of the alarm area.

[0163] Step S103, determining whether the target event is a preset alarm event according to event information of the target event in the image collected by the target collection device.

[0164] Step S104, if the target event is a preset alarm event, alarming the target event and sending an alarm signal to the first cloud domain.

[0165] In the embodiment, when the first edge domain of the target cloud domain receives the alarm signal, the target alarm device sending the alarm signal is determined first, and then the target acquisition device associated with the target alarm device is determined; then the associated target acquisition device is called to acquire the image of the alarm region to determine the event information of the target event occurring in the alarm region, so as to determine whether the target event is alarmed according to the event information. Through the embodiment, after the alarm signal is generated, the alarm prompt information is not directly sent; instead, the target event is reviewed according to the event information determined by the target acquisition device, so as to ignore the alarm signal caused by the invalid target event, and send the alarm prompt information for the alarm signal caused by the valid target event, so as to prompt the user to process the target event, so that the user does not need to process the invalid target event, saves the user's time, and improves the efficiency of the user in processing the target event.

[0166] As an embodiment for determining whether the target event is a preset alarm event, in a case where the type of the target object belongs to a preset type, the target event is determined to be a preset alarm event. In a case where the type of the target object does not belong to the preset type, the target event is determined to be a non-preset alarm event. The target event is that the target object is in the alarm region, and the event information includes the type of the target object.

[0167] For example, if the type of the target object is a human, the target event is determined to be a preset alarm event and the target event is a to-be-alarmed event. If the type of the target object is an object, 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 a user who is ready to process the alarm event.

[0168] In the embodiment, the invalid target event caused by the target object of the preset type is hidden, and the user does not need to be prompted to process, 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 mode.

[0169] As an embodiment, the above step S101 can be implemented in the following manner: if the target master acquisition device is in an idle state, 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, the target slave acquisition device is determined to be the target acquisition device; and if the target master acquisition device and the target slave acquisition device are both in a non-idle state, the target acquisition device is determined according to the distance between other acquisition devices and the target alarm device and the working state of the other acquisition devices.

[0170] The distance between each acquisition device associated with the target alarm device and the alarm region is less than a preset distance.

[0171] Specifically, the target alarm device is pre-associated with a corresponding target master acquisition device and a target slave acquisition. When the target alarm device sends an alarm signal, the target master acquisition device and the target slave acquisition pre-associated with the target alarm device are called. When the target master acquisition device is in a non-idle state, the target slave acquisition device in an idle state is called as a target acquisition device. When the target slave acquisition device is also in a non-idle state, other acquisition devices in a non-working state within a preset range are called to acquire the alarm area.

[0172] For example, the acquisition device in an idle state is determined as a candidate acquisition device, and the candidate acquisition device with the smallest distance to the alarm area is determined as the target acquisition device.

[0173] As an implementation, the device resources of the first edge domain include a plurality of alarm devices, the plurality of alarm devices are distributed on the first edge domain according to a preset interval, and the alarm devices are one-to-one corresponding to the master acquisition devices. The target slave acquisition device is determined by the following manner: first, a preset number of alarm devices continuously distributed with the target alarm device are determined as candidate alarm devices; and then, the master acquisition devices corresponding to the candidate alarm devices are determined as the target slave acquisition devices of the target alarm device.

[0174] For example, taking the alarm device as a vibrating optical fiber and the acquisition device as a ball machine as an example, the association relationship between the alarm device and the acquisition device is described as follows.

[0175] Specifically, one vibrating optical fiber is equally divided into a plurality of units, that is, one vibrating optical fiber includes a plurality of vibrating optical fiber units. One ball machine is arranged as a master acquisition device corresponding to each vibrating optical fiber unit, that is, one master ball machine is arranged at the opposite position of each vibrating optical fiber unit. At the same time, each vibrating optical fiber unit corresponds to a different unit number, and generally, each unit number is arranged according to the position distribution order of each vibrating optical fiber unit. For example, one vibrating optical fiber is divided into 500 vibrating optical fiber units in sequence, and the corresponding numbers are 1, 2, 3, …, 500. Hereinafter, the vibrating optical fiber units with the unit numbers 1 to 500 are simply referred to as vibrating optical fiber unit 1 to vibrating optical fiber unit 500. If one vibrating optical fiber unit corresponds to 10 slave ball machines, then the slave ball machines associated with each vibrating optical fiber unit are the master ball machines of the other 10 vibrating optical fiber units with the numbers continuous to the number of the vibrating optical fiber unit. For example, the 10 slave ball machines associated with the vibrating optical fiber unit 1 are the master ball machines of the vibrating optical fiber units 2 to 11. For another example, the 10 slave ball machines associated with the vibrating optical fiber unit 2 are the master ball machines of the vibrating optical fiber units 2, 3 to 11.

[0176] As an alarm manner, the S104 can be implemented in the following manner: when it is determined that the plurality of target events are all preset alarm events within a preset time length, performing deduplication processing on the plurality of target events according to event information of each target event in the plurality of target events, to obtain at least one target event after the deduplication processing; and performing alarm according to the at least one target event obtained after the deduplication processing.

[0177] As an example of the alarm manner, target events with the same target object in the plurality of target events are combined into one target event according to information of the target object corresponding to each target event in the plurality of target events. The target event is that the target object is in an alarm region, and the event information of the target event includes the information of the target object.

[0178] In this example, the target objects of the plurality of target events can be determined to be the same in the following manner: the information of the target object includes a similarity of the target object to a preset object; and the target objects corresponding to two or more target events are the same in a case where the similarity of the target objects corresponding to the two or more target events to the same preset object is greater than or equal to a similarity threshold.

[0179] In some embodiments, the information of the preset object is obtained from a preset object library. The preset object corresponding to the target object is determined according to the information of the preset object. If the information of the target object cannot obtain the information of the corresponding preset object, the preset object storage library is updated according to the information of the target object to generate new preset object information.

[0180] Optionally, in a case where the information of the target object cannot obtain the information of the corresponding preset object, if the information of the target object is consistent with preset permitted object information, the information of the target object is not updated to the preset object storage library; and if the information of the target object is not consistent with the preset permitted object information, the information of the target object is updated to the preset object storage library.

[0181] For example, it is determined that the image of the target object matches the image of the white list object by more than a matching threshold, and the image of the target object is not updated to the preset object storage library. It is determined that the image of the target object matches the image of the white list object by less than or equal to the matching threshold, and the image of the target object is updated to the preset object storage library.

[0182] In some embodiments, the target acquisition device is a spherical shooting device. The spherical shooting device is also called a spherical camera.

[0183] 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 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 of the spherical imaging device are determined. The operating parameters include 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.

[0184] 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.

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

[0186] Based on the Law of Cosines of the Spherical Surface: cos(c)=cos(a)×cos(b)+sin(a)×sin(b)×cos(C) Formula (1) Where, ∠a=90-B w ; ∠b=90-A w ;∠C=B j -A j Substituting into formula (1), we get formula (2):

[0187] ∠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)

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

[0189]

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

[0191] 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.w The longitude coordinates of the PTZ camera's location; A j The coordinates of the PTZ camera's position are latitude and longitude.

[0192] (2) Determine the vertical angle T

[0193] 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′.

[0194]

[0195]

[0196] 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 hx from the ground, and the alarm position on the alarm device is at a height of h2 from the ground.

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

[0198] 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).

[0199]

[0200] Where k and b are known constants.

[0201] 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.

[0202] This disclosure also provides an embodiment such as Figure 11 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.

[0203] The determining unit is configured to determine, according to the target task and resource information corresponding to each cloud domain in the plurality of cloud domains, a second cloud domain from the plurality of cloud domains, resources of the second cloud domain including target resources for implementing the target task; the resource information of different cloud domains corresponding to different resources; the sending unit 112 is configured to send, to a collaborative service platform of the second cloud domain, a task execution request, 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 the receiving unit 113 is configured to receive an execution result of the target task returned by the collaborative service platform of the second cloud domain, the execution result being sent by the collaborative service platform of the second cloud domain in a case where the task execution request is accepted.

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

[0205] In a possible implementation, the determining unit 111 is specifically configured to determine, according to a target task initiated by a terminal device of a target user in the first cloud domain, a target service for serving the target task; determine, from a plurality of cloud domains, a first candidate cloud domain according to service resource information of the plurality of cloud domains registered on the collaborative service platform of the first cloud domain, service resources of the first candidate cloud domain including the target service; and determine a second cloud domain from the first candidate cloud domain.

[0206] In a possible implementation, the sending unit 112 is specifically configured to determine target data resources and / or target device resources associated with the target task in the second cloud domain; determine a target user associated with the target task in the first cloud domain; and send, to the collaborative service platform of the second cloud domain, a task execution request carrying the target data resources and / or the target device resources and the target user; the task execution request being 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 the target device resources.

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

[0208] 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.

[0209] 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.

[0210] 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.

[0211] This disclosure also provides an embodiment such as Figure 12 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.

[0212] 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.

[0213] 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.

[0214] 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 determine the target acquisition device from 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 from the first edge domain to the target acquisition device, 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 will issue an alarm for the target event and send an alarm signal to the first cloud domain.

[0215] In another possible implementation, the collection unit 134 is specifically configured to determine the target master collection device as the target collection device if the target master collection device is in an idle state; determine the target slave collection device as the target collection device if the target master collection device is in a non-idle state and the target slave collection device is in an idle state; and determine the target collection device according to distances between other collection devices and the target alarm device and working states of the other collection devices if the target master collection device and the target slave collection device are both in non-idle states.

[0216] In another possible implementation, the collection unit 134 is further specifically configured to determine, as the target slave collection device of the target alarm device, a preset number of master collection devices associated with a preset number of candidate alarm devices continuously distributed with the target alarm device, and determine the target collection device according to working states of the other collection devices, where the device resources in the first edge domain include a plurality of alarm devices, the plurality of alarm devices are distributed on the first edge domain according to a preset interval, and the alarm devices are one-to-one corresponding to the master collection devices.

[0217] In another possible implementation, the collection unit 134 is further configured to determine, according to the latitude and longitude of the spherical shooting device, the height of the spherical shooting device, the position of the alarm region, and the installation height of the target alarm device, a working parameter of the spherical shooting device, where the working parameter includes a horizontal angle, a vertical angle, and a zoom factor of the spherical shooting device; and send the working parameter to the spherical shooting device, so that the spherical shooting device collects an image of the alarm region based on the working parameter; and the target collection device is the spherical shooting device.

[0218] Figure 13 is a schematic diagram of an electronic device provided by the present disclosure. As shown in Figure 13 The electronic device 50 can 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 in the following embodiments.

[0219] In addition, the electronic device 50 can further include a communication bus 502, at least one communication interface 504, an input device 506, and an output device 505.

[0220] The processor 501 can be a central processing unit (CPU), a micro processing unit (MPU), an ASIC, or one or more integrated circuits for controlling program execution of the present disclosure.

[0221] The communication bus 502 can include a path for transmitting information between the above components.

[0222] 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.

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

[0224] 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.

[0225] 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.

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

[0227] In a specific implementation, as one example, electronic device 50 may include multiple processors, such as... Figure 13 Processors 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).

[0228] The electronic device is as follows Figure 13The shown include: a processor 501 and a memory 503 for storing instructions executable by the processor 501; wherein the processor 501 is configured to execute the executable instructions to implement the multi-cloud domain task processing method or the edge-cloud-based multi-dimensional perception intelligent connection method of any of the possible implementation manners described above. And can achieve the same technical effects, to avoid repetition, here will not repeat.

[0229] The embodiments of the present disclosure also provide a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device can execute the multi-cloud domain task processing method or the edge-cloud-based multi-dimensional perception intelligent connection method of any of the possible implementation manners described above. And can achieve the same technical effects, to avoid repetition, here will not repeat.

[0230] The embodiments of the present disclosure also provide a computer program product, including a computer program or instructions, the computer program or instructions are executed by the processor to execute the multi-cloud domain task processing method or the edge-cloud-based multi-dimensional perception intelligent connection method of any of the possible implementation manners described above. And can achieve the same technical effects, to avoid repetition, here will not repeat.

[0231] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses or adaptations of the present disclosure following the general principles thereof and including such departures from the present disclosure that come within known used or customary practice in the art. The specification and examples are to be regarded as illustrative only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0232] It should be understood that the present disclosure is not limited to the precise construction that has been described and shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the present disclosure. The scope of the present disclosure is limited only by the claims that follow.

Claims

1. A method for multi-dimensional perception and intelligent connection based on edge-cloud, characterized in that, The application is applied to a system including an end device, an edge domain and a cloud domain, the cloud domain includes a first cloud domain and a second cloud domain, the first cloud domain is any one cloud domain except the second cloud domain; each cloud domain corresponds to a collaborative service platform; the end device includes a target alarm device, the target alarm device belongs to a device resource of the first edge domain, the target alarm device belongs to a device resource of the second cloud domain, and the first edge domain belongs to the second cloud domain; The method is applied to a collaborative service platform of the second cloud domain, and the method includes: receiving a resource information registration request sent by a collaborative service platform of the first cloud domain, the resource information registration request being used to indicate a request to register resource information of the collaborative service platform of the second cloud domain on the collaborative service platform of the first cloud domain; returning resource information to the collaborative service platform of the first cloud domain, so that the collaborative service platform of the first cloud domain associates the resource information with a cloud domain identifier of the second cloud domain, to complete the registration of the resource information of the collaborative service platform of the second cloud domain on the collaborative service platform of the first cloud domain; receiving a first task request sent by the first cloud domain; wherein the first task request carries a target device resource, the target device resource is a device resource associated with a target task determined by the collaborative service platform of the first cloud domain, the target task includes alarming a target event, and the first task request is used to indicate a request to alarm the target event by the target alarm device of the second cloud domain; the target alarm device is determined by the first cloud domain according to the device resource information of the second cloud domain registered on the first cloud domain, and the target device resource includes the target alarm device; receiving 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 the target alarm device monitors that the target event occurs in an alarm area corresponding to the target alarm device; sending the alarm signal to the first cloud domain. 2.The multi-dimensional perception and intelligence method of claim 1, wherein, The method further includes: sending a resource information registration request to a collaborative service platform of any other cloud domain; the resource information registration request is used to indicate a request to register resource information of the collaborative service platform of the any other cloud domain on the collaborative service platform of the second cloud domain; associating resource information returned by the collaborative service platform of the any other cloud domain with a cloud domain identifier of the any other cloud domain, to complete the registration of the resource information of the collaborative service platform of the any other cloud domain on the collaborative service platform of the second cloud domain.

3. The multi-dimensional perception and intelligence method of claim 1, wherein, The end device further includes a collection device, the collection device belongs to a device resource of the second cloud domain and the first edge domain; the target alarm device is pre-associated with a target master collection device and a target slave collection device; the alarm signal sent by the first edge domain is determined by the following way: the first edge domain determines a target collection device from the target master collection device, the target slave collection device and other collection devices around the alarm area. The first edge domain sends an information collection instruction to the target collection device, the information collection instruction instructing the target collection device to collect images of the alarm area; The first edge domain determines whether the target event is a preset alarm event according to event information of the target event in the images collected by the target collection device; If the target event is the preset alarm event, the first edge domain alarms the target event and sends the alarm signal to the first cloud domain.

4. The multi-dimensional perception intelligent connection method according to claim 3, wherein, The first edge domain determines a target collection device from the target master collection device, the target slave collection device, and other collection devices around the alarm area, including: If the target master collection device is in an idle state, the target master collection device is determined as the target collection device; If the target master collection device is in a non-idle state and the target slave collection device is in an idle state, the target slave collection device is determined as the target collection device; If the target master collection device and the target slave collection device are both in a non-idle state, a target collection device is determined according to distances between the other collection devices and the target alarm device and working states of the other collection devices.

5. The multi-dimensional perception and intelligence method of claim 3, wherein, The device resources of the first edge domain include a plurality of alarm devices, the plurality of alarm devices are distributed on the first edge domain according to a preset interval, the alarm devices correspond to master collection devices one by one, and the method further includes: A preset number of alarm devices continuously distributed with the target alarm device are determined as candidate alarm devices; Master collection devices associated with the candidate alarm devices are determined as the target slave collection device of the target alarm device. 6.The multi-dimensional perception intelligent connection method according to any one of claims 3 to 5, characterized in that, The target collection device is a spherical shooting device, and the method further includes: Working parameters of the spherical shooting device are determined according to longitude and latitude of the spherical shooting device, a height of the spherical shooting device, a position of the alarm area, and an installation height of the target alarm device, the working parameters including a horizontal angle, a vertical angle, and a zoom factor of the spherical shooting device; The working parameters are sent to the spherical shooting device, so that the spherical shooting device collects images of the alarm area based on the working parameters.

7. An end-to-end cloud based multi-dimensional perception intelligent connected device, characterized in that, The device includes: The instruction receiving unit is configured to receive a resource information registration request sent by a collaborative service platform of a first cloud domain, the resource information registration request being used to indicate that resource information of a collaborative service platform of a second cloud domain is requested to be registered in the collaborative service platform of the first cloud domain; The sending unit is configured to return resource information to the collaborative service platform of the first cloud domain, so that the collaborative service platform of the first cloud domain associates the resource information with a cloud domain identifier of the second cloud domain, to complete registration of the resource information of the collaborative service platform of the second cloud domain on the collaborative service platform of the first cloud domain; and The sending unit is configured to return resource information to the collaborative service platform of the first cloud domain, so that the collaborative service platform of the first cloud domain associates the resource information with a cloud domain identifier of the second cloud domain, to complete registration of the resource information of the collaborative service platform of the second cloud domain on the collaborative service platform of the first cloud domain. The instruction receiving unit is further configured to receive a first task request sent by a first cloud domain; the first task request carries target device resources determined by a collaborative service platform of the first cloud domain and associated with a target task, the target task includes alarming a target event, and the first task request is used to instruct the second cloud domain to use a target alarm device to alarm the target event; the target alarm device is determined by the first cloud domain according to device resource information registered by the second cloud domain on the first cloud domain, and the target device resources include the target alarm device; the end device includes the target alarm device, and the target alarm device belongs to device resources of a first edge domain; the cloud domains include the first cloud domain and the second cloud domain, and the target alarm device belongs to device resources of the second cloud domain; the first cloud domain is any one cloud domain except the second cloud domain; each cloud domain is one-to-one corresponding to a collaborative service platform; The instruction receiving unit is further 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 the target alarm device monitors that the target event occurs in an alarm area corresponding to the target alarm device, and the first edge domain belongs to the second cloud domain; The alarm unit is configured to send the alarm signal to the first cloud domain.

8. The multi-dimensional sensory awareness smart connected device of claim 7, wherein, The device further includes an instruction sending unit and an acquisition unit; The instruction sending unit is configured to send a resource information registration request to a collaborative service platform of any other cloud domain; the resource information registration request is used to instruct to register resource information of the collaborative service platform of the any other cloud domain on the collaborative service platform of the second cloud domain; The instruction sending unit is further configured to associate the resource information returned by the collaborative service platform of the any other cloud domain with a cloud domain identifier of the any other cloud domain, to complete the registration of the resource information of the collaborative service platform of the any other cloud domain on the collaborative service platform of the second cloud domain; The acquisition unit is configured to determine a target acquisition device from a target master acquisition device, a target slave acquisition device, and other acquisition devices around the alarm area by the first edge domain; the end device further includes an acquisition device, and the acquisition device belongs to device resources of the second cloud domain and the first edge domain; the target alarm device is pre-associated with the target master acquisition device and the target slave acquisition device; The acquisition unit is configured to send an information acquisition instruction to the target acquisition device by the first edge domain, and the information acquisition instruction instructs the target acquisition device to acquire an image of the alarm area; The acquisition unit is further configured to determine whether the target event is a preset alarm event according to event information of the target event in the image acquired by the target acquisition device by the first edge domain; The alarm unit is configured to alarm the target event by the first edge domain and send the alarm signal to the first cloud domain if the target event is the preset alarm event. The collection unit is specifically configured to determine the target master collection device as the target collection device if the target master collection device is in an idle state; determine the target slave collection device as the target collection device if the target master collection device is in a non-idle state and the target slave collection device is in an idle state; and determine the target collection device according to distances between the other collection devices and the target alarm device and working states of the other collection devices if the target master collection device and the target slave collection device are both in non-idle states. The collection unit is further specifically configured to take a preset number of alarm devices continuously distributed with the target alarm device as candidate alarm devices, and determine a master collection device associated with the candidate alarm devices as the target slave collection device of the target alarm device. The device resources of the first edge domain include a plurality of alarm devices, the plurality of alarm devices are distributed on the first edge domain according to a preset interval, and the alarm devices correspond to master collection devices one by one. The collection unit is further configured to determine working parameters of a spherical shooting device according to latitude and longitude of the spherical shooting device, a height of the spherical shooting device, a position of the alarm region, and an installation height of the target alarm device, wherein the working parameters include a horizontal angle, a vertical angle, and a zoom factor of the spherical shooting device; send the working parameters to the spherical shooting device, so that the spherical shooting device collects images of the alarm region based on the working parameters; and the target collection device is the spherical shooting device.

9. An electronic device, comprising: Comprise: A processor and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the executable instructions to implement the multi-dimensional perception intelligent connection method according to any one of claims 1 to 6.

10. An end-to-end cloud based multi-dimensional perception intelligent system, characterized in that, Comprise an end device, an edge domain, and a cloud domain, the end device comprises a target alarm device, the target alarm device belongs to device resources of the first edge domain; the cloud domain comprises a first cloud domain and a second cloud domain, the target alarm device belongs to device resources of the second cloud domain; the first cloud domain is any one cloud domain other than the second cloud domain; each cloud domain corresponds to a collaborative service platform one by one, and the collaborative service platform of the second cloud domain implements the multi-dimensional perception intelligent connection method according to any one of claims 1 to 6.

Images