Registered edge device management
By registering the edge device manager, the problem of inefficient data capture of edge device is solved. By predicting the travel path and selecting the appropriate device to send workload, the accurate capture of the focus entity data is achieved and the possibility of data capture is improved.
Patent Information
- Application Number
- CN202380029215.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-22
- Filing Date
- 2023-03-16
- Publication Date
- 2024-11-05
AI Technical Summary
When edge devices acquire and process data, the practicality of the data is affected due to the limitations of the number, location and time of available devices, and control and management configurations limit their ability to provide additional functions.
By registering the edge device manager (REDM), the device data of the edge device collection is obtained, the travel path of the focus entity is predicted, and the appropriate edge device is selected based on the proximity to send the workload to capture the relevant data and send the captured data to User equipment.
Accurately capture data when the focus entity moves, improving the possibility that data is captured before the entity leaves its position, and enhancing the data capture capability of edge devices.
Smart Images

Figure CN118901235A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to network device management, and more particularly, to registered edge device management. Background Art
[0002] Edge devices may include various electronic devices that are connected to a network and configured to acquire data, process data, and send the processed data to a centralized location, such as a network server or a cloud-based edge device management center. For example, in some cases, production facilities may employ edge devices such as cameras, temperature sensors, and humidity sensors. In these cases, each edge device may acquire data about the manufacturing process, perform one or more calculations on the data, and send the processed data to a management center that is configured to monitor and analyze the manufacturing process. In another example, a government agency may employ edge devices such as cameras, temperature sensors, barometers, and / or air quality sensors. In this example, these edge devices may acquire data about matters such as traffic conditions, weather conditions, and / or environmental conditions in a certain place. The edge devices may process this data and send the processed data to a central management center.
[0003] The use of edge devices may include challenges. For example, in some cases, the usefulness of data generated by a collection of edge devices may be limited by factors such as the number of available edge devices near a location of interest, the location (e.g., viewing orientation) of one or more edge devices, and / or the time at which data was captured by one or more edge devices. In some cases, the control and / or management configuration of an edge device may limit its ability to provide additional functionality, such as performing additional workloads. Summary of the invention
[0004] Various aspects of the present disclosure are directed to a method that includes obtaining device data for a set of edge devices. The method may further include obtaining a predicted path of travel for a focus entity. The method may further include determining a first proximity of a first edge device to the predicted path of travel. The determination may be for a first edge device in the set of edge devices. The determination may be based on the device data. The method may further include selecting the first edge device. The selection may be based at least in part on the first proximity. The method may further include sending a workload to the first edge device. The sending may be in response to selecting the first edge device. The method may further include receiving first captured data obtained by the first edge device. The receiving may be in response to sending the workload. The method may further include sending the first captured data to an electronic user device.
[0005] Advantageously, the above aspects of the present disclosure can facilitate obtaining accurate data corresponding to a focus entity having a travel path by allowing edge devices in a set of edge devices to capture data based on the proximity of the edge device to the predicted travel path of the focus entity.
[0006] A further specific embodiment of the present disclosure including the aspects discussed in the above method further includes predicting that the path of travel includes a first location and a second location. The method may further include the focus entity being at the first location at a first time. The focus entity may be predicted to be at the second location at a second time. The second time may be after the first time. The method may further include selecting a second edge device from the set of edge devices. The selection may be based at least in part on a second proximity of the second edge device to the second location. The method may further include sending a workload to the second edge device. The sending may be in response to selecting the second edge device. The method may further include receiving second captured data. The second captured data may be acquired by the second edge device. The receiving may be in response to sending the workload to the second device. The method may further include sending the second captured data to the electronic user device.
[0007] Advantageously, the above-described aspects according to preferred embodiments of the present disclosure may allow multiple edge devices to accurately capture data about a focus entity over time as the focus entity moves.
[0008] A further embodiment of the present disclosure including the aspects discussed in the above method further includes sending the workload to the second edge device occurring at the intermediate time. The method may further include the second time being after the intermediate time.
[0009] Advantageously, the above aspects according to the preferred embodiments of the present disclosure can increase the likelihood that data about a focus entity is captured before the focus entity leaves a location, because the edge device can acquire the workload before the focus entity arrives at the location.
[0010] Other aspects of the present disclosure are directed to systems and computer program products configured to perform the above methods.
[0011] Various aspects of the present disclosure are directed to a method comprising obtaining device data for a set of edge devices. The method may further include obtaining a predicted path of travel for a focus entity. The method may further include determining that a subset is within a threshold distance of the predicted path of travel. The determination may be for a subset of the set of edge devices. The determination may be based on the device data. The subset may include mobile phones and cameras mounted on buildings. The method may further include sending a workload to the subset. The sending may be in response to the determination. The method may further include receiving a captured image. The captured image may be acquired by the subset. The receiving may be in response to sending the workload. The method may further include sending the captured image to an electronic user device.
[0012] Advantageously, the above-described aspects of the present disclosure may allow various types of edge devices to capture data about a focus entity having a path of travel.
[0013] Various aspects of the present disclosure are directed to a method that includes obtaining device data for a set of edge devices. The method may further include obtaining a workload request from an electronic user device. The method may further include obtaining a predicted path of travel for a focus entity. The method may further include determining that a subset of the set of edge devices is within a threshold distance of the predicted path of travel. The determination may be in response to the workload request. The subset may include a mobile phone. The subset may further include a camera mounted on a building. The method may further include sending a workload corresponding to the workload request to the subset. The sending may be in response to the determination. The method may further include receiving a captured image obtained by the subset. The receiving may be in response to sending the workload. The method may further include sending a captured image to the electronic user device. The sending may be in response to the workload request.
[0014] Advantageously, the above-described aspects of the present disclosure may allow various types of edge devices to capture images regarding a mobile focus entity and transmit the captured images to an electronic user device upon request.
[0015] This summary is not intended to describe every aspect, every implementation, and / or every example of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings included in this application are incorporated into this specification and constitute a part thereof. They illustrate embodiments of the present disclosure and are used to explain the principles of the present disclosure together with the description. The accompanying drawings only illustrate certain embodiments and do not limit the present disclosure.
[0017] Figure 1 An example computing environment with a registered edge device manager is depicted according to an embodiment of the present disclosure.
[0018] Figure 2A flow chart of an example method of performing registered edge device management according to an embodiment of the present disclosure is depicted.
[0019] Figure 3 Depicted are example geographic regions in which registered edge device management is implemented according to embodiments of the present disclosure.
[0020] Figure 4 Depicted are representative major components of a computer system that may be used in accordance with embodiments of the present disclosure.
[0021] Figure 5 A cloud computing environment according to an embodiment of the present disclosure is depicted.
[0022] Figure 6 Abstract model layers according to an embodiment of the present disclosure are depicted.
[0023] Although the present invention may be modified and adopted in other forms, its specific details have been illustrated by way of example in the accompanying drawings and described in detail. However, it should be understood that the present invention is not intended to be limited to the specific embodiments described. On the contrary, it is intended that the present invention is intended to cover all modifications, equivalents and substitutes within the spirit and scope of the present invention. DETAILED DESCRIPTION
[0024] Embodiments of the present disclosure relate to management of network devices, and more specifically, to registration edge device management. Although the present disclosure is not necessarily limited to such applications, various embodiments of the present disclosure may be understood by discussing various examples using this context.
[0025] Edge devices may include various electronic devices that are connected to a network and configured to acquire data, process data, and send processed data to a centralized location, such as a network server or a cloud-based edge device management center. For example, in some cases, production facilities may employ edge devices such as cameras, temperature sensors, and humidity sensors. In these cases, each edge device may acquire data about the manufacturing process, perform one or more calculations on the data, and send processed data to a management center that is configured to monitor and analyze the manufacturing process. In another example, a government agency may employ edge devices such as cameras, temperature sensors, barometers, and / or air quality sensors. In this example, these edge devices may acquire data about matters such as traffic conditions, weather conditions, and / or environmental conditions in a certain place. The edge devices may process this data and send the processed data to a central management center.
[0026] The use of edge devices may include challenges. For example, in some cases, the usefulness of data generated by a collection of edge devices may be limited by factors such as the number of available edge devices near a location of interest, the location (e.g., viewing orientation) of one or more edge devices, and / or the time at which data was captured by one or more edge devices. In some cases, the control and / or management configuration of an edge device may limit its ability to provide additional functionality, such as performing additional workloads.
[0027] To address these challenges and others, embodiments of the present disclosure include a Registered Edge Device Manager (REDM). In some embodiments, REDM can obtain device data for a set of edge devices registered with REDM and send workloads to a subset of these registered edge devices based on satisfying one or more conditions. In some embodiments, a set of edge devices can have respective sets of owners and / or supervisors who can choose to register the set of edge devices with REDM. For example, in some embodiments, a set of edge devices can include: (1) a set of outdoor cameras mounted on a commercial building, which has a first supervisor who manages the set of outdoor cameras; (2) a mobile phone with an integrated camera, which has a first owner; and (3) a residential doorbell camera, which has a second owner. In this example, the first supervisor, the first owner, and the second owner can respectively choose to register the set of outdoor cameras, the mobile phone, and the residential doorbell camera with REDM. Therefore, advantageously, embodiments of the present disclosure can employ multiple different types of edge devices with different functions. In some embodiments, REDM can obtain the predicted travel path of a focus entity, such as a storm system or a tornado, and send workloads to a subset of edge devices within a threshold near the focus entity. Therefore, advantageously, embodiments of the present disclosure may employ registered edge devices to capture data at a location relative to a moving focus entity. In some embodiments, REDM may send a workload to a subset of registered edge devices near a second location on a predicted path of travel. In these embodiments, REDM may perform such sending before the time at which the mobile focus entity is predicted to be at the second location. For example, continuing with the tornado example above, the predicted path of travel for the tornado may include the tornado being located in a first city at a first time, and in a second city at a second time. In this example, REDM may send a workload (e.g., instructions to capture image and audio data) to a registered edge device at the second location before the second time. Therefore, advantageously, embodiments of the present disclosure may employ registered edge devices to allow sufficient time for the moving focus entity to capture data.
[0028] Go to the attached picture, Figure 1A computing environment 100 is shown that includes at least one of each of the following: a registration edge device manager (REDM) 105, a registration edge device set 150, a resource data server 135, a user device 140, and a computing device 145. In some embodiments, at least one REDM 105, a registration edge device set 150, a resource data server 135, a user device 140, and a computing device 145 can exchange data with each other via a network 165. The registration edge device set 150 can include one or more registration edge devices. For example, in some embodiments, the registration edge device set 150 can include n registration edge devices, where n is an integer greater than zero. For example, in an embodiment where the set of registered edge devices 150 includes only a first registered edge device 150-1 having a capture device 155-1 and a data processor 160-1, n=1; in an embodiment where the set of registered edge devices 150 includes two registered edge devices (the first registered edge device 150-1 as described above and the second registered edge device 150-2 having a capture device 155-2 and a data processor 160-2), n=2; and so on. In some embodiments, one or more of the REDM 105, the set of registered edge devices 150, the resource data server 135, the user device 140, the computing device 145, and the network 165 may include a computer system, such as a computer system for Figure 4 The computer system 401.
[0029] refer to Figure 1 In some embodiments, REDM 105 may be included in software installed on a computer system of at least one of user device 140 and / or computing device 145. REDM 105 may include program instructions implemented by a processor, such as computing device 145, to perform operations related to Figure 2 The operation or operations in question.
[0030] In some embodiments, REDM 105 may include one or more modules, such as device data manager 110, workload manager 115, and capture data manager 125. In some embodiments, device data manager 110, workload manager 115, and capture data manager 125 may be integrated into a single module. In some embodiments, device data manager 110, workload manager 115, and / or capture data manager 125 may acquire data, analyze data, store data, and / or transmit data. In some embodiments, device data manager 110, workload manager 115, and capture data manager 125 may include program instructions implemented by a processor, such as a processor of computing device 145, to perform operations related to Figure 2For example, in some embodiments, the device data manager 110 may include a program for performing Figure 2 In some embodiments, the workload manager 115 may include a program instruction for executing operation 205. Figure 2 In some embodiments, the capture data manager 120 may include a program instruction for performing operations 210-250. Figure 2 The REDM 105 may autonomously execute the program instructions for operations 255 and 260 in FIG. Figure 2 The operations discussed; therefore, in embodiments where the registered edge device set 150 includes a large number of registered edge devices 150 - n , the REDM 105 can efficiently and accurately perform the operations of the method 200 .
[0031] In some embodiments, the set of registered edge devices 150 may include one or more electronic devices, such as cameras, mobile phones (e.g., smartphones), tablets, wearable technology (e.g., smart watches), sensors (e.g., temperature, humidity, air quality, and / or pressure sensors), and / or sound recording devices. In some embodiments, the set of registered edge devices 150 may include one or more cameras configured to capture images and / or sounds of public spaces. For example, such cameras may include cameras mounted on commercial buildings so that the cameras can capture images and / or sounds from areas near the commercial buildings, such as parking lots, roads, building entrances and / or exits, etc. In another example, such cameras may include cameras mounted on residential buildings, such as doorbell cameras, which can capture images and / or sounds near residential buildings, such as streets or cul-de-sacs in front of residential buildings. In another example, such cameras may include cameras mounted on physical structures such as bridges, utility poles, etc., which can capture images and / or sounds from areas such as highways, street intersections, etc. In some embodiments, such cameras may include cameras mounted on vehicles, which can capture images and / or sounds near such vehicles. Advantageously, the set of registered edge devices 150 may include multiple types of electronic devices that can acquire multiple types of data. In addition, in some embodiments, the registered edge devices in the registered edge device set 150 can have independent, different and / or unrelated owners and / or supervisors who own and / or manage such registered edge devices. Advantageously, as described below, REDM 105 can send workloads to edge devices registered by many different owners and / or supervisors. Therefore, in some embodiments, REDM 105 may not be limited to obtaining data from one or more edge devices owned and / or managed by a single entity.
[0032] In some embodiments, the registration edge device 150-n may include at least one capture device 155-n and / or a data processor 160-n. In some embodiments, the at least one capture device 155-n may include a sensor, an audio capture device, and / or an image capture device. For example, in an embodiment where the registration edge device 150-n is a smartphone, the smartphone may include multiple capture devices 155-n, such as an accelerometer, a camera, and / or a microphone. In another example, in an embodiment where the registration edge device 150-n is a camera, the camera may include multiple capture devices 155-n, such as temperature, humidity, and / or pressure sensors. In some embodiments, the at least one data processor 160-n may include a sensor, an audio capture device, and / or an image capture device. Figure 4 In some embodiments, the data processor 160-n may be configured to analyze, process, and / or perform calculations on data acquired by the registration edge device 150-n. For example, in some embodiments, the data processor 160-n may be configured to filter data acquired by the registration edge device 150-n. For example, in some embodiments, the registration edge device 150-n may include image analysis software that allows the data processor 160-n to perform functions such as blocking, cropping, and / or editing images captured by the registration edge device 150-n.
[0033] In some embodiments, at least one resource data server 135 may include one or more network servers. In some embodiments, at least one resource data server 135 may correspond to a service system, such as a weather service system, an emergency alert service system, and / or a police service system. In some embodiments, at least one resource data server 135 may include software configured to analyze data to predict the path of travel of a mobile focus entity, such as a storm system or a vehicle. For example, in some embodiments, a weather service system may analyze weather data through one or more resource data servers 135 to generate a predicted path of travel for a hurricane. In these embodiments, the predicted path of travel may include a prediction that the hurricane will be at a first location at a first time and at a second location at a subsequent second time. In another example, in some embodiments, a highway patrol service system may analyze data such as traffic patterns, road maps, global positioning system (GPS) coordinates, and / or vehicle speed and / or direction through one or more resource data servers 135 to generate a predicted travel path for a vehicle. In these embodiments, the predicted travel path may include a prediction that the vehicle will be at a first location at a first time and at a second location at a subsequent second time.
[0034] In some embodiments, at least one user device 140 may include a device such as a laptop, a tablet, a desktop computer, a mobile phone (e.g., a smartphone), a tablet, wearable technology (e.g., a smart watch), etc. In some embodiments, a user, such as an owner and / or supervisor of a user device 140, may send a workload request to REDM 105 from the user device 140, as discussed in further detail below. In some embodiments, such a user may be separate, different, and / or unrelated to the owner and / or supervisor who owns and / or manages the registered edge devices in the set of registered edge devices 150. In some embodiments, the owner and / or supervisor of the edge device may register the edge device with REDM 105 using the user device 140. According to embodiments of the present disclosure, such registration may allow REDM 105 to send workloads to the registered edge device.
[0035] In some embodiments, at least one computing device 145 may include devices such as computers, network servers, etc. In some embodiments, network 165 may be a wide area network (WAN), a local area network (LAN), the Internet, or an intranet. In some embodiments, network 165 may be connected to a computer or a network server. Figure 5 The cloud computing environments 50 discussed are substantially similar or identical.
[0036] Figure 2 1 is a flowchart of an example method 200 for performing registered edge device management according to an embodiment of the present disclosure. The method 200 may be performed by REDM, such as Figure 1 The REDM 105 execution in question.
[0037] Back to Figure 2In operation 205, in order to register the edge device with REDM, REDM may obtain device data corresponding to one or more characteristics of the edge device. In some embodiments, the device data may include one or more technical specifications of the edge device. For example, in some embodiments, the device data may include an identification of the device type (e.g., whether the device is a mobile phone, a mounted camera, or an air quality sensor), brand, and / or model. In some embodiments, the device data may specify one or more capture devices included by the edge device. For example, the device data of a smartphone edge device may indicate that the smartphone includes a camera and a microphone as capture devices. In some embodiments, the device data may indicate the data capture quality of the edge device, such as the range of image resolutions that the camera can capture. In some embodiments, the device data may indicate the processing capabilities of the data processor of the edge device, such as the processing speed of the data processor, the image analysis capability, and / or the image filtering capability. In some embodiments, the device data may include information about the speed at which the edge device transmits wireless data. In some embodiments, the device data may include information about the available power or storage capacity of the edge device. For example, in some embodiments, the device data for an edge device such as a smart watch may include the remaining battery power of the smart watch and / or the size of the available data storage space in the storage of the smart watch. In some embodiments, the device data may include location and / or direction information corresponding to the edge device. For example, in some embodiments, such information may include GPS coordinates and / or a location description (e.g., a camera at First Street and Main Avenue, a camera in the North Campus parking lot, etc.). In some embodiments, such information may include edge device information, such as the mounting height and / or orientation of a camera and / or the direction it can face. In some embodiments, device data may include the workload status of an edge device, such as whether the edge device is executing a workload request.
[0038] In some embodiments, the device data may be selected by the owner and / or supervisor of the edge device. For example, in some embodiments, such owners and / or supervisors may select the availability of edge devices to receive workloads from REDM. For example, in some embodiments, such owners and / or supervisors may specify one or more dates, times, and / or time periods when edge devices can receive workloads from REDM. For example, a supervisor of a parking lot camera set may specify that the camera set receives workloads from REDM between 10 and 11 a.m. every Tuesday. In another example, if the execution time of the workload does not exceed a certain threshold, such as a 30-second threshold, the supervisor may specify that the camera set receives workloads from REDM. In some embodiments, the owner and / or supervisor of the edge device may specify the urgency of satisfying the edge device to receive workloads from REDM. For example, in some embodiments, the owner of a doorbell camera may specify that the doorbell camera will not receive workloads from REDM unless the workload has an emergency classification. In some embodiments, the owner and / or supervisor of the edge device may limit the availability of the edge device according to the entity that submits the workload request to REDM. In some embodiments, the owner and / or regulator may submit device data indicating that the edge device will not receive workload from REDM until the owner and / or regulator provides specific consent for the workload, such as by sending a consent notification by the user device to REDM.
[0039] In some embodiments, operation 205 may include REDM from one or more edge devices and / or from one or more user devices (eg, user device 140, Figure 1 ) obtain device data. For example, in some embodiments, the owner and / or supervisor of one or more edge devices may choose to register such edge devices with REDM by sending device data to REDM through a user device. In some embodiments, operation 205 may include REDM storing the device data to a storage location of REDM.
[0040] In operation 210, REDM may obtain a workload request. A workload may refer to a set of tasks for a registered edge device, such as capturing images, audio, and / or sensor data (i.e., capturing data), processing such captured data, and sending such captured data to REDM. A workload request may refer to a request (e.g., a call, command, or program instruction) sent by REDM to one or more registered edge devices to perform the workload. In some embodiments, an entity, such as a private individual, an individual user, or a government agency, may request a workload through a user device (e.g., user device 140, Figure 1) sends a workload request to REDM. For example, in some embodiments, a workload request may include images of an area near a bicycle rack or a bicycle rack captured by a bicycle owner, where the owner's bicycle is locked. In this example, such images can help users prevent bicycles from being damaged or stolen. In another example, in some embodiments, a workload request may include images, temperature data, and air quality data of an area of the city collected by available cameras, temperature sensors, and air quality sensors after an earthquake, proposed by government authorities. In this example, such captured data can help government departments determine where to provide assistance.
[0041] In some embodiments, the workload request may include various types of data related to the workload request. For example, in some embodiments, the workload request may include location information of the focus entity and / or identification features of the focus entity. The focus entity may refer to entities such as people, animals, vehicles, or weather entities (such as storms, hurricanes, typhoons, tornadoes, etc.), which may be the subject of the workload request. For example, in the example involving bicycle racks discussed above, the focus entity may include bicycle racks and / or bicycles. As discussed in further detail below, in some embodiments, the focus entity may have a predicted path of travel.
[0042] In some embodiments, the workload request may include a description of the type of registered edge device that performs the workload. For example, in some embodiments, the workload request may specify an audio capture device to acquire audio data, or specify a mobile phone to acquire images without audio data. In some embodiments, the workload request may include the brand and / or model of the registered edge device that performs the workload. In some embodiments, the workload request may include data capture quality specifications for the registered edge device, such as a threshold image resolution for captured images. In some embodiments, the workload request may include specifications related to the processing capabilities corresponding to the registered edge device. For example, in some embodiments, the workload request may specify the type of image filter to be applied to the captured image. In some embodiments, the workload request may specify a threshold value for the wireless data transmission speed of the registered edge device. In these embodiments, such specifications may facilitate efficient data transmission when the time to acquire captured data is critical. In some embodiments, the workload request may include location and / or direction specifications for the registered edge device. For example, in some embodiments, the workload request may include a threshold distance from the focus entity in which the set of registered edge devices will be located. In some embodiments, the workload request may include a threshold distance from the predicted path of travel in which the set of registered edge devices will be located. In some embodiments, the workload request may include specifications for the date, time, and / or time period in which the registered edge device performs the workload. In some embodiments, a workload request may include specifications regarding the urgency of the workload. For example, in some embodiments, an entity transmitting a workload request to REDM may classify the workload as "non-urgent," "urgent," or "urgent" workload, where the "non-urgent" classification has the lowest urgency and the "urgent" classification has the highest urgency. In some embodiments, a workload request may specify the entity submitting the workload request to REDM.
[0043] In some embodiments, operation 210 may include REDM from a user device (eg, user device 140, Figure 1 ) obtains the workload request. For example, in some embodiments, the entity may submit the workload request to REDM through such a user device. In some embodiments, operation 210 may include REDM storing the workload request in a storage location of REDM.
[0044] In some embodiments, in operation 215, REDM may obtain a predicted travel path for the focus entity. In some embodiments, the predicted travel path may include a set of geographical locations where the mobile focus entity is predicted to appear and a set of times where the mobile focus entity is predicted to appear. For example, a predicted travel path for a vehicle traveling on a highway may include the vehicle being located in a first city at a first time and being located in a second city at a second time after the first time. In some embodiments, REDM may obtain a predicted travel path for the focus entity from a resource data server (e.g., resource data server 135, Figure 1 ) to obtain the predicted driving path. In some embodiments, REDM can obtain the predicted driving path from the user device (e.g., user device 140, Figure 1 ) obtains the predicted path of travel. For example, in some embodiments, the user may determine the predicted path of travel and send it to the REDM by such user device. In some embodiments, operation 215 may include the REDM storing the predicted path of travel in a storage location of the REDM.
[0045] In operation 220, REDM may determine whether one or more conditions corresponding to the workload request are met. In some embodiments, such determination may include REDM comparing and / or analyzing the data obtained in operations 205-215 to determine whether the corresponding data matches and / or exceeds one or more thresholds. For example, in some embodiments, in response to identifying that the type of registered edge device (e.g., smartphone) specified in the workload request matches the type of registered edge device (e.g., smartphone) included in the device data of the registered edge device, REDM may determine that the condition is met. In some embodiments, in response to identifying that the location (e.g., GPS coordinates) of the registered edge device specified in the device data of the registered edge device does not exceed a threshold distance from the focus entity or from the predicted path of travel of the focus entity, REDM may determine that the condition is met.
[0046] In operation 220, in response to determining that one or more conditions corresponding to the workload request are satisfied, REDM may continue to operation 225. Alternatively, in response to determining that such conditions are not satisfied, method 200 may end.
[0047] In operation 225, REDM may select one or more registered edge devices to which REDM may send the workload corresponding to the workload request. In some embodiments, operation 225 may include REDM selecting (e.g., identifying) a subset of the registered edge devices from the set of registered edge devices for which device data was obtained in operation 205.
[0048] In operation 230, REDM may send the workload to one or more registered edge devices selected in operation 225. In some embodiments, operation 230 may include REDM sending the data obtained in operation 210 to one or more registered edge devices. In some embodiments, operation 230 may include REDM issuing a command to one or more registered edge devices to perform the workload. In some embodiments, operation 230 may include REDM sending a notification to one or more registered edge devices. For example, in an embodiment where the registered edge device is a smartphone, REDM may send a text notification to the smartphone, requiring the owner and / or supervisor of the smartphone to perform the workload via the smartphone, such as capturing a one-minute long video recording of a street intersection near the smartphone.
[0049] In operation 235, in some embodiments, REDM may determine whether there are one or more changes in the data corresponding to the workload request. For example, in embodiments including a set of registered edge devices that capture data within a threshold distance of a moving focus entity or a predicted movement path, the location of the focus entity or the predicted location of the focus entity may change over time. In these embodiments, REDM may determine whether there are one or more changes in the data corresponding to the workload request.
[0050] In operation 235 , in response to determining that there are one or more changes in the data corresponding to the workload request, REDM may proceed to operation 240 . Alternatively, in response to determining that there are no such changes, REDM may proceed to operation 255 .
[0051] In operation 240, REDM may determine whether one or more conditions corresponding to the workload request are satisfied. Operation 240 may be the same or substantially similar to operation 220. Continuing with the example discussed above regarding capturing data within a threshold distance of a predicted path of travel, in operation 240, in response to identifying that the location of the registered edge device does not exceed the predicted second location of the mobile focus entity, REDM may determine that the condition is satisfied.
[0052] In operation 240, in response to determining that one or more conditions corresponding to the workload request are satisfied, REDM may proceed to operation 245. Alternatively, in response to determining that such conditions are not satisfied, REDM may proceed to operation 255.
[0053] In operation 245, REDM may select one or more newly registered edge devices to which REDM may send the workload corresponding to the workload request. In some embodiments, the newly registered edge devices may be different from the one or more registered edge devices selected in operation 225. Operation 245 may be the same or substantially similar to operation 225.
[0054] In operation 250, the REDM may send the workload to the one or more newly registered edge devices selected in operation 245. Operation 250 may be the same as or substantially similar to operation 230.
[0055] In operation 255, in response to the workload sent to one or more registered edge devices, REDM can receive captured data acquired by one or more registered edge devices. In some embodiments, operation 255 can include one or more registered edge devices sending captured data to REDM. In some embodiments, such captured data can include filtered images, such as images with blurred portions to protect personal privacy in the image. In these embodiments, the registered edge device can filter these images according to the filtering specifications contained in the workload. Such workloads are sent to the registered edge devices in operations 230 and / or 250.
[0056] In operation 260, REDM may send the captured data. For example, in some embodiments, REDM may send the captured data to a user device of the entity that submitted the workload request in operation 210. In some embodiments, operation 260 may include REDM deleting the captured data from storage of REDM and / or from one or more registered edge devices to promote data privacy.
[0057] Figure 3An example geographic area 300 for implementing registered edge device management according to an embodiment of the present disclosure is described. In this example, a focus entity 325, such as the eye of a hurricane, can be located at a first location 330 at a first time. In addition, in this example, a weather service can generate a predicted path of travel 320 for a hurricane. The predicted path of travel 320 can indicate that the hurricane will be located at a second location 340 at a second time after the first time. The predicted path of travel 320 can further indicate that the hurricane will be located at a third location 350 at a third time after the second time. In addition, in this example, an emergency response team can send a workload request to REDM via a user device. The workload request can specify a first area 335 with a radius of 10 kilometers around the first location 330; a second area 345 with a radius of 15 kilometers around the second location 340; and a third area 355 with a radius of 15 kilometers around the third location 350. The workload request can further specify that cameras within the first area 335, the second area 345, and the third area 355 capture outdoor images. In addition, in this example, REDM can identify the registered edge device sets 305, 310 and 315 that meet the workload request conditions. In addition, in this example, REDM can send the workload corresponding to the workload request to each registered edge device set 305, 310 and 315, thereby sending the workload to the registered edge device set 310 at a time before the second time, and sending the workload to the registered edge device set 315 at a time before the third time. In addition, in this example, in response to sending the workload, REDM can receive capture data from the registered edge device sets 305, 310 and 315. In addition, in this example, REDM can send capture data to the user device of the emergency response team. In this way, the emergency response team can obtain accurate and comprehensive information, thereby facilitating effective emergency response.
[0058] Figure 4 Depicted are representative major components of an exemplary computer system 401 that can be used according to embodiments of the present disclosure. The specific components depicted are for illustrative purposes only and are not necessarily the only such variations. Computer system 401 may include processor 410, memory 420, input / output interface (also referred to herein as I / O or I / O interface) 430, and main bus 440. Main bus 440 may provide a communication path for other components of computer system 401. In some embodiments, main bus 440 may be connected to other components, such as a dedicated digital signal processor (not shown).
[0059] The processor 410 of the computer system 401 may include one or more CPUs 412. In addition, the processor 410 may additionally include one or more storage buffers or caches (not shown) that provide temporary storage of instructions and data for the CPU 412. The CPU 412 may execute instructions about providing input from a cache or storage 420, and output the result to the cache or storage 420. The CPU 412 may include one or more circuits configured to perform one or more methods consistent with the embodiments of the present disclosure. In some embodiments, the computer system 401 may include multiple processors 410, which is a typical feature of relatively large systems. However, in other embodiments, the computer system 401 may be a single processor with a single CPU 412.
[0060] The storage 420 of the computer system 401 may include a storage controller 422 and a storage module (not shown) for temporary or permanent storage of data. In some embodiments, the storage 420 may include a random access semiconductor memory, a storage device, or a storage medium (volatile or non-volatile) for storing data and programs. The storage controller 422 may communicate with the processor 410 to facilitate the storage and retrieval of information in the storage module. The storage controller 422 may communicate with the I / O interface 430 to facilitate the storage and retrieval of input or output in the storage module. In some embodiments, the storage module may be a dual in-line storage module.
[0061] The I / O interface 430 may include an I / O bus 450, a terminal interface 452, a storage interface 454, an I / O device interface 456, and a network interface 458. The I / O interface 430 may connect the main bus 440 to the I / O bus 450. The I / O interface 430 may guide instructions and data from the processor 410 and the storage 420 to the various interfaces of the I / O bus 450. The I / O interface 430 may also guide instructions and data from the various interfaces of the I / O bus 450 to the processor 410 and the storage 420. The various interfaces may include a terminal interface 452, a storage interface 454, an I / O device interface 456, and a network interface 458. In some embodiments, the various interfaces may include a subset of the above interfaces (for example, an embedded computer system in an industrial application may not include a terminal interface 452 and a storage interface 454).
[0062] The logic modules in the entire computer system 401 - including but not limited to storage 420, processor 410 and I / O interface 430 - can communicate failures and changes of one or more components to a hypervisor or operating system (not shown). The hypervisor or operating system can allocate various available resources in the computer system 401 and track the location of data in storage 420 and the location of processes assigned to multiple CPUs 412. In embodiments that combine or rearrange elements, various aspects of the logic module functions can be combined or reallocated. These changes will be apparent to those skilled in the art.
[0063] It can be understood in advance that although the present disclosure includes a detailed description of cloud computing, the implementation of the teachings described herein is not limited to a cloud computing environment. Instead, the embodiments of the present invention can be implemented in conjunction with any other type of computing environment now known or later developed.
[0064] Cloud computing is a service delivery model that enables convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, storage, applications, virtual machines, and services) that can be quickly provisioned and released with minimal management effort or interaction with the service provider. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
[0065] Features are as follows:
[0066] On-demand self-service: Cloud consumers can unilaterally and automatically provision computing capabilities, such as server time and network storage, as needed, without requiring manual interaction with the service provider.
[0067] Wide Area Network Access: Capabilities are available over the network and accessed through standard mechanisms that facilitate use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
[0068] Resource pooling: A provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, where different physical and virtual resources are dynamically allocated and reallocated based on demand. There is a sense of location independence, as consumers typically do not control or know the exact location of the provided resources, but are able to specify the location at a higher level of abstraction (e.g., country, state, or data center).
[0069] Rapid elasticity: The ability to scale out quickly and scale in quickly can be provisioned quickly and elastically, in some cases automatically. To the consumer, the capacity available for provisioning often appears to be unlimited and can be purchased in any quantity at any time.
[0070] Metered Services: Cloud systems automatically control and optimize resource usage by leveraging metering capabilities at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to both the provider and consumer of the utilized service.
[0071] The service model is as follows:
[0072] Software as a Service (SaaS): The capability provided to consumers is to use the vendor's applications running on a cloud infrastructure. The applications are accessible from a variety of client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including the network, servers, operating systems, storage, or even individual application capabilities, except perhaps for limited user-specific application configuration settings.
[0073] Platform as a Service (PaaS): The capability provided to consumers is to deploy consumer-created or acquired applications created using programming languages and tools supported by the provider onto the cloud infrastructure. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possible configuration of the application hosting environment.
[0074] Infrastructure as a Service (IaaS): The capabilities provided to consumers are processing, storage, networking, and other basic computing resources on which consumers can deploy and run arbitrary software, which may include operating systems and applications. Consumers do not manage or control the underlying cloud infrastructure, but have control over the operating system, storage, deployed applications, and may have limited control over selected networking components (e.g., host firewalls).
[0075] The deployment model is as follows:
[0076] Private cloud: The cloud infrastructure is operated only for the organization. It can be managed by the organization or a third party and can exist on-premises or off-premises.
[0077] Community cloud: The cloud infrastructure is shared by several organizations and supports a specific community with shared concerns (e.g., mission, security requirements, policies, and compliance considerations). It can be managed by the organization or a third party and can exist on-premises or off-premises.
[0078] Public cloud: Cloud infrastructure is available to the general public or large industrial groups and is owned by an organization that sells cloud services.
[0079] Hybrid cloud: A cloud infrastructure is a combination of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technologies that enable data and application portability (e.g., cloud bursting for load balancing between clouds).
[0080] The cloud computing environment is service-oriented, with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the core of cloud computing is an infrastructure consisting of a network of interconnected nodes.
[0081] Now please refer to Figure 5 , depicts an illustrative cloud computing environment 50. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 10, and local computing devices used by cloud consumers, such as personal digital assistants (PDAs) or cellular phones 54A, desktop computers 54B, laptop computers 54C, and / or automotive computer systems 54N can communicate with these nodes 10. The nodes 10 can communicate with each other. They can be physically or virtually grouped in one or more networks, such as private clouds, community clouds, public clouds, or hybrid clouds as described above, or a combination thereof (not shown). This allows the cloud computing environment 50 to provide infrastructure, platforms, and / or software as a service without the cloud consumer having to maintain resources on a local computing device. It will be appreciated that Figure 5 The types of computing devices 54A-N shown are for illustration only, and computing node 10 and cloud computing environment 50 may communicate with any type of computerized device via any type of network and / or network-addressable connection (eg, using a web browser).
[0082] Reference now Figure 6 , showing the cloud computing environment 50 ( Figure 5 ) provides a set of functional abstraction layers. It should be understood in advance that Figure 6 The components, layers and functions shown are for illustration only, and the embodiments of the present invention are not limited thereto. As shown in the figure, the following layers and corresponding functions are provided:
[0083] The hardware and software layer 60 includes hardware and software components. Examples of hardware components include: host 61; server 62 based on RISC (Reduced Instruction Set Computer) architecture; server 63; blade server 64; storage device 65; and network and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.
[0084] Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities can be provided: virtual servers 71 ; virtual storage 72 ; virtual networks 73 , including virtual private networks; virtual applications and operating systems 74 ; and virtual clients 75 .
[0085] In one example, the management layer 80 may provide the functionality described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources for performing tasks within a cloud computing environment. Metering and pricing 82 provides cost tracking when resources are utilized in a cloud computing environment, as well as billing or invoicing for the consumption of these resources. In one example, these resources may include application software licenses. Security provides authentication for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management so that the required service levels are met. Service level agreement (SLA) planning and fulfillment 85 provides pre-scheduling and procurement of cloud computing resources, wherein future demand is anticipated based on the SLA.
[0086] The workload layer 90 provides examples of functions that can utilize the cloud computing environment. Examples of workloads and functions that can be provided by this layer include: mapping and navigation 91, software development and lifecycle management 92, virtual classroom education delivery 93, data analysis processing 94, transaction processing 95 and registered edge device management logic 96.
[0087] As discussed in more detail herein, it is contemplated that some or all of the operations of some embodiments of the methods described herein may be performed in an alternate order, or perhaps not performed at all; furthermore, multiple operations may occur concurrently or as internal parts of a larger process.
[0088] The present invention may be a system, method and / or computer program product at any possible level of technical detail integration. The computer program product may include a computer-readable storage medium (or medium) having computer-readable program instructions thereon, and the computer-readable program instructions are used to cause a processor to perform various aspects of the present invention.
[0089] Computer readable storage medium can be a tangible device capable of retaining and storing instructions used by an instruction execution device. Computer readable storage medium can be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer readable storage medium includes the following items: portable computer disk, hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanical encoding device such as a punch card or a raised structure in a groove with instructions recorded thereon, and any suitable combination of the foregoing. Computer readable storage medium as used herein should not be interpreted as a temporary signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated by a waveguide or other transmission medium (e.g., a light pulse by an optical fiber cable), or an electrical signal transmitted by a wire.
[0090] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in a computer-readable storage medium within the corresponding computing / processing device.
[0091] The computer-readable program instructions for performing the operation of the present invention can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, configuration data of integrated circuits, or source code or object code written in any combination of one or more programming languages (including object-oriented programming languages, such as Smalltalk, C++, etc.) and process programming languages (such as "C" programming language or similar programming languages). The computer-readable program instructions can be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer through any type of network (including local area network (LAN) or wide area network (WAN)), or can be connected to an external computer (for example, using an Internet service provider through the Internet). In certain embodiments, in order to perform various aspects of the present invention, the electronic circuit including, for example, a programmable logic circuit, a field programmable gate array (FPGA) or a programmable logic array (PLA) can execute the computer-readable program instructions by utilizing the state information of the computer-readable program instructions to personalize the electronic circuit.
[0092] Various aspects of the present invention are described herein with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to embodiments of the present invention. It will be understood that each frame of the flowchart and / or block diagram and the combination of frames in the flowchart and / or block diagram can be implemented by computer-readable program instructions.
[0093] These computer-readable program instructions can be provided to a processor of a computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / actions specified in one or more boxes of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, which instructions cause the computer, programmable data processing device and / or other equipment to work in a specific manner, so that the computer-readable storage medium in which the instructions are stored together includes an article of manufacture, which includes instructions for implementing aspects of the functions / actions specified in one or more boxes of the flowchart and / or block diagram.
[0094] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in one or more boxes of the flowchart and / or block diagram.
[0095] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention.To this, each frame in the flow chart or block diagram can represent the module, segment or part of instruction, which includes one or more executable instructions for realizing the specified logical function.In some alternative embodiments, the function noted in the frame may not occur in the order noted in the figure.For example, the two frames shown in succession can actually be completed as a step, and the mode of partial overlap or full overlap in time is performed simultaneously or substantially simultaneously, or these frames can sometimes be performed in reverse order, depending on the function involved.It will also be noted that the combination of each frame in the block diagram and / or flow chart and the frame in the block diagram and / or process can be realized by a dedicated hardware-based system that performs a specified function or action or performs a combination of special hardware and computer instructions.
[0096] The description of various embodiments of the present disclosure has been given for the purpose of illustration, but it is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein are selected to best explain the principles of the embodiments, practical applications, or technical improvements to existing technologies on the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.
[0097] Although the present disclosure has been described in the form of specific embodiments, it is expected that changes and modifications thereof will be apparent to those skilled in the art. Therefore, the following claims are intended to be interpreted as covering all changes and modifications within the true spirit and scope of the present disclosure.
[0098] Any advantages discussed in this disclosure are exemplary advantages, and embodiments of the present disclosure may achieve all, some, or any of the advantages discussed while remaining within the spirit and scope of the present disclosure.
[0099] A non-limiting list of examples is provided below to illustrate some aspects of the present disclosure. Example 1 is a computer-implemented method. The method includes obtaining device data for a set of edge devices; obtaining a predicted path of travel for a focus entity; for a first edge device in the set of edge devices, determining a first proximity of the first edge device to the predicted path of travel based on the device data; selecting the first edge device based at least in part on the first proximity; in response to selecting the first edge device, sending a workload to the first edge device; in response to sending the workload, receiving first captured data obtained by the first edge device; and sending the first captured data to an electronic user device.
[0100] Example 2 includes the method of Example 1, including or excluding the optional features. In this example, the predicted travel path includes a first location and a second location, the focus entity is located at the first location at a first time, and the focus entity is predicted to be located at the second location at a second time after the first time; the computer-implemented method further includes: selecting a second edge device from the set of edge devices based at least in part on a second proximity of the second edge device to the second location; in response to selecting the second edge device, sending a workload to the second edge device; in response to sending the workload to the second device, receiving second captured data acquired by the second edge device; and sending the second captured data to the electronic user device.
[0101] Example 3 includes the method of any one of Examples 1 to 2, including or excluding the optional features. In this example, sending the workload to the second edge device occurs at the intermediate time, and the second time is after the intermediate time.
[0102] Example 4 includes the method of any one of Examples 1 to 3, including or excluding the optional features. In this example, the device data includes additional data selected from the group consisting of: image capture resolution, image filtering capabilities, and data transmission speed; and selecting the first edge device is based at least in part on the additional data.
[0103] Example 5 includes the method of any one of Examples 1 to 4, including or excluding the optional features. In this example, the method includes: determining the first proximity includes determining that a first distance between the first edge device and the predicted path of travel does not exceed a threshold.
[0104] Example 6 includes the method of any one of Examples 1 to 5, including or excluding the optional features. In this example, the workload includes instructions to capture one or more images associated with the focus entity, and the first capture data includes the one or more captured images.
[0105] Example 7 includes the method of any one of Examples 1 to 6, including or excluding the optional features. In this example, the workload further includes an image filter specification, and the one or more captured images include one or more images filtered according to the filter specification.
[0106] Example 8 includes the method of any one of Examples 1 to 7, including or excluding the optional features. In this example, the focus entity includes a weather entity.
[0107] Example 9 is a computer-implemented method. The method includes: obtaining device data for a set of edge devices; obtaining a predicted path of travel of a focus entity; for a subset of the set of edge devices, determining based on the device data that the subset is within a threshold distance of the predicted path of travel, the subset comprising a mobile phone and a camera mounted on a building; in response to the determination, sending a workload to the subset; in response to sending the workload, receiving a captured image obtained by the subset; and sending the captured image to an electronic user device.
[0108] Example 10 is a computer-implemented method. The method includes: obtaining device data for a set of edge devices; obtaining a workload request from an electronic user device; obtaining a predicted path of travel of a focus entity; in response to the workload request, determining that a subset of the set of edge devices is within a threshold distance of the predicted path of travel, the subset including mobile phones and cameras mounted on a building; in response to the determination, sending a workload corresponding to the workload request to the subset; in response to sending the workload, receiving a captured image obtained by the subset; and in response to the workload request, sending the captured image to the electronic user device.
[0109] Example 11 is a system comprising: one or more processors; and one or more computer-readable storage media storing program instructions, which, when executed by the one or more processors, are configured to cause the one or more processors to perform a method according to any one of Examples 1 to 10.
[0110] Example 12 is a computer program product, which includes one or more computer-readable storage media, and program instructions stored together on the one or more computer-readable storage media, which can be executed by one or more processors to enable the one or more processors to perform a method according to any one of Examples 1 to 10.
Claims
1. A computer-implemented method comprising: Obtain device data for a collection of edge devices; Get the predicted travel path of the focus entity; for a first edge device in the set of edge devices, determining a first proximity of the first edge device to the predicted path of travel based on the device data; selecting the first edge device based at least in part on the first proximity; In response to selecting the first edge device, sending the workload to the first edge device; In response to sending the workload, receiving first captured data acquired by the first edge device; as well as The first captured data is transmitted to an electronic user device.
2. The computer-implemented method of claim 1 , wherein: The predicted travel path includes a first position and a second position, the focus entity is located at the first position at a first time, and the focus entity is predicted to be located at the second position at a second time after the first time; The computer-implemented method further comprises: selecting a second edge device in the set of edge devices based at least in part on a second proximity of the second edge device to the second location; In response to selecting the second edge device, sending the workload to the second edge device; receiving second captured data acquired by the second edge device in response to sending the workload to the second device; and The second captured data is transmitted to the electronic user device.
3. The computer-implemented method of claim 2, wherein: Sending the workload to the second edge device occurs at an intermediate time, the second time being after the intermediate time.
4. A computer-implemented method according to any one of the preceding claims, wherein: The device data includes additional data selected from the group consisting of: Image capture resolution; Image filtering capabilities; as well as The speed at which data is sent; and Wherein selecting the first edge device is based at least in part on the additional data.
5. A computer-implemented method according to any one of the preceding claims, wherein: Determining the first proximity includes determining that a first distance between the first edge device and the predicted path of travel does not exceed a threshold.
6. A computer-implemented method according to any one of the preceding claims, wherein: The workload includes instructions for capturing one or more images associated with the focus entity, and The first captured data includes one or more captured images.
7. The computer-implemented method of claim 6, wherein: The workload further includes image filter specifications, and Wherein the one or more captured images include one or more images filtered according to the filter specifications.
8. The computer-implemented method of claim 1 , wherein: The focus entity includes a weather entity.
9. The computer-implemented method of claim 1 , wherein: The determining step determines, for a subset of the set of edge devices, that the subset is within a threshold distance of the predicted path of travel, the subset including the first edge device, and the subset including a mobile phone and a camera mounted to a building; The sending step sends the workload to the subset; The receiving step receives the captured images acquired by the subset; as well as The sending the first captured data step sends the captured image to the electronic user device.
10. The computer-implemented method of claim 9, comprising: A workload request is obtained from the electronic user device, wherein the determining step is in response to the workload request, and sending the captured image is in response to the workload request.
11. A system comprising: one or more processors; as well as One or more computer-readable storage media storing program instructions, which when executed by one or more processors are configured to cause the one or more processors to perform a method comprising: Obtain device data for a collection of edge devices; Get the predicted travel path of the focus entity; for a first edge device in the set of edge devices, determining a first proximity of the first edge device to the predicted path of travel based on the device data; selecting the first edge device based at least in part on the first proximity; In response to selecting the first edge device, sending the workload to the first edge device; In response to sending the workload, receiving first captured data acquired by the first edge device; and The first captured data is transmitted to an electronic user device.
12. The system according to claim 11, wherein: The predicted travel path includes a first position and a second position, the focus entity is located at the first position at a first time, and the focus entity is predicted to be located at the second position at a second time after the first time; The system further comprises: selecting a second edge device in the set of edge devices based at least in part on a second proximity of the second edge device to the second location; In response to selecting the second edge device, sending the workload to the second edge device; receiving second captured data acquired by the second edge device in response to sending the workload to the second device; and The second captured data is transmitted to the electronic user device.
13. The system according to claim 12, wherein: Sending the workload to the second edge device occurs at an intermediate time, the second time being after the intermediate time.
14. A system according to any one of claims 11 to 13, wherein: The device data includes additional data selected from the group consisting of: Image capture resolution; Image filtering capabilities; as well as The speed at which data is sent; and Wherein selecting the first edge device is based at least in part on the additional data.
15. A system according to any one of claims 11 to 14, wherein: Determining the first proximity includes determining that a first distance between the first edge device and the predicted path of travel does not exceed a threshold.
16. A system according to any one of claims 11 to 15, wherein: The workload includes instructions for capturing one or more images associated with the focus entity, and The first captured data includes one or more captured images.
17. The system of claim 16, wherein: The workload further includes image filter specifications, and Wherein the one or more captured images include one or more images filtered according to the filter specifications.
18. A system according to any one of claims 11 to 17, wherein: The focus entity includes a weather entity.
19. A computer program product, the computer program product comprising one or more computer-readable storage media and program instructions stored together on the one or more computer-readable storage media, the program instructions being executable by one or more processors to cause the one or more processors to perform a method comprising: Obtain device data for a collection of edge devices; Get the predicted travel path of the focus entity; for a first edge device in the set of edge devices, determining a first proximity of the first edge device to the predicted path of travel based on the device data; selecting the first edge device based at least in part on the first proximity; In response to selecting the first edge device, sending the workload to the first edge device; In response to sending the workload, receiving first captured data acquired by the first edge device; as well as The first captured data is transmitted to an electronic user device.
20. The computer program product of claim 19, wherein: The predicted travel path includes a first position and a second position, the focus entity is located at the first position at a first time, and the focus entity is predicted to be located at the second position at a second time after the first time; The method further comprises: selecting a second edge device in the set of edge devices based at least in part on a second proximity of the second edge device to the second location; In response to selecting the second edge device, sending the workload to the second edge device; receiving second captured data acquired by the second edge device in response to sending the workload to the second device; and The second captured data is transmitted to the electronic user device.
21. The computer program product of claim 20, wherein: Sending the workload to the second edge device occurs at an intermediate time, the second time being after the intermediate time.
22. A computer program product according to any one of claims 19 to 21, wherein: The device data includes additional data selected from the group consisting of: Image capture resolution; Image filtering capabilities; as well as The speed at which data is sent; and Wherein selecting the first edge device is based at least in part on the additional data.
23. A computer program product according to any one of claims 19 to 22, wherein: Determining the first proximity includes determining that a first distance between the first edge device and the predicted path of travel does not exceed a threshold.
24. A computer program product according to any one of claims 19 to 23, wherein: The workload includes instructions for capturing one or more images associated with the focus entity, and The first captured data includes one or more captured images.
25. A computer program product according to any one of claims 19 to 24, wherein: The focus entity includes a weather entity.
26. A computer-implemented method comprising: Obtain device data for a collection of edge devices; Get the predicted travel path of the focus entity; for a subset of the set of edge devices, determining, based on the device data, that the subset is within a threshold distance of the predicted path of travel, the subset comprising a mobile phone and a camera mounted on a building; In response to the determining, sending the workload to the subset; receiving, in response to sending the workload, a captured image acquired by the subset; as well as The captured image is transmitted to an electronic user device.
27. A computer-implemented method comprising: Obtain device data for a collection of edge devices; obtaining a workload request from an electronic user device; Get the predicted travel path of the focus entity; In response to the workload request, determining that a subset of the set of edge devices is within a threshold distance of the predicted path of travel, the subset comprising a mobile phone and a camera mounted on a building; In response to the determining, sending a workload corresponding to the workload request to the subset; receiving, in response to sending the workload, a captured image acquired by the subset; as well as In response to the workload request, the captured image is sent to the electronic user device.
28. A computer program comprising program code means adapted to perform the method according to any one of claims 1 to 10 or claim 26 or claim 27 when said program is run on a computer.
